nntp (aka, usenet) client in kde?
by Gene Smith
I currently use t-bird with an nntp account pointing to gmane to read
this list and sereral others. Does kde have an nntp client program of
any sort? I don't see it as a possible new account type in kmail. Also,
search with kpackagekit yields nothing with "usenet" or "nntp" that is
kde specific.
-gene
3 years, 3 months
KDE Telepathy Bonjour account: This IM Account cannot be created - a
Telepathy Connection Manager named 'salut' is missing or it cannot
handle
protocol 'local-xmpp'. Please try installing salut with your package manager.
by Dennis Schridde
Hi!
I was trying to setup a Bonjour (local XMPP) account in KDE Plasma System Settings for KDE Telepathy. In `System Settings > Online Accounts > Create`, I clicked "Bonjour" in the list on the right. This action was answered with an error dialogue box: "This IM Account cannot be created - a Telepathy Connection Manager named 'salut' is missing or it cannot handle protocol 'local-xmpp'. Please try installing salut with your package manager." However, `telepathy-salut` is already installed on my machine. Does anyone have an idea how to debug this, or where I would find the actual error message that led to this?
I am using Fedora 27 KDE, with telepathy-salut currently being at version 0.8.1 (release 12.fc27), telepathy-mission control at version 5.16.4 (epoch 1, release 4.fc27) and ktp-accounts-kcm at version 17.12.1(release 1.fc27).
Best regards,
Dennis
3 years, 12 months
time to orphan/retire unmaintained uncommon kde4 language bindings?
by Rex Dieter
Looking over some broken deps reports, I came across some old packages:
kdebindings
smokeqt
smokekde
qyoto (csharp/mono)
kimono (csharp/mono)
ruby-qt
ruby-korundum
perl-Qt
Of these, the only one that's not a pure leaf package is perl-Qt (debconf-
kde depends on it).
any comment or objection to considering orphaning most (all minus
smokeqt/perl-Qt) or all of these ?
-- Rex
4 years
Emacs key binding in KDE Plasma 5?
by Sherman Grunewagen
Just moved from Fedora 21 to F25. Under F21 I had a file ~/.gtkrc-2.0 which contained
gtk-key-theme-name = "Emacs"
This enabled basic Emacs cursor motion keyboard commands in text input boxes throughout KDE,
Firefox, &c. (Outside of input boxes, KDE shortcuts ruled.)
How can I get this same behaviour for Plasma 5 w/in F25? From reading around, I've created
~/.config/gtk-3.0/settings.ini
and inserted
[Settings]
gtk-key-theme-name = Emacs
in this empty file. This has given the desired result in Firefox and Thunderbird,
but not w/in arbitrary text boxes in KDE (e.g. Alt-F2). The ~/.gtkrc-2.0 file is still
intact, by the way. It seems to have no effect. Any ideas?
-Sherman
4 years
SDDM Themes not working
by Gerald B. Cox
I find that I now cannot select themes - and I'm getting either a solid
white or blue background when SDDM starts.
When I tried to test, this is what I received:
sddm-greeter --theme /usr/share/sddm/themes/01-fedora-breeze
[11:43:09.032] (II) GREETER: High-DPI autoscaling not Enabled
[11:43:09.108] (EE) GREETER: Socket error: "QLocalSocket::connectToServer:
Invalid name"
[11:43:09.109] (EE) GREETER: Cannot connect to the daemon - is it running?
[11:43:09.317] (II) GREETER: Loading
file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml...
[11:43:09.317] (WW) GREETER:
file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml: No such file or
directory
[11:43:09.317] (WW) GREETER:
file:///usr/share/sddm/themes/01-fedora-breeze/Main.qml: No such file or
directory
[11:43:09.317] (WW) GREETER: Fallback to embedded theme
Wanted to see if there was a quick fix or if this is known before I create
a bug report.
I didn't see anything on bugzilla, but might have missed it.
Thanks!
4 years, 3 months
Problems with Akregator / web engine
by Syam Krishnan
Hi..
I am having some problems with deleting articles in Akregator.
If I had opened some specific type of articles, from then on, deleting
articles takes a long time. For example, it takes 1-2 seconds for
deleting 10 articles. 3-4 seconds for 40 articles etc. This started last
year or so, but I was unaware as to what was triggering it.
Now I can reproduce the problem. If I open any article from Slashdot
feed or an article that has an embedded video (although it doesn't play
in Akregator anyway), then all subsequent article deletions take a long
time and at times cause a graphics reset. Even closing Akregator takes a
long time and finally crashes.
If I don't open any such offending articles in a session, then
everything is OK.
I'm running nVidia proprietary driver and I don't have any other
problems in general. Only with Akregator and deleting articles.
Any ideas on what could be the culprit?
Syam
4 years, 11 months
Updated from the kde testing copr last night, and now ---
by Peter Gueckel
there is no more plasma!
I don't recall the names/numbers of the update, but there were 62 packages. Since there had also been a new 4.17 kernel in the update just minutes previously and I hadn't rebooted, I did this update, too, and powered off for the night. This morning, using both the new 4.17 kernel and the last of the 4.16 kernels, trying both plasma on xorg and on wayland, I log in and there us just a black display with a mouse pointer.
I had to resort to gnome in order to be able to have a desktop at all.
That happened? Is there some undocumented dependency that did not get pulled into the update that I need to install? I tried doing an update just moments ago, but it says the system is up-to-date.
4 years, 11 months
Fedora KDE GUI updater and firmwares
by Germano Massullo
I have been told that gnome updater installs also new versions of
bios/firmware on machines (probably using fwupd). Do you know if Fedora
KDE Spin GUI updater does that too?
Best regards
4 years, 11 months
Release blocking status and *so many* default applications
by Matthew Miller
As everyone knows, the KDE Plasma desktop is a release-blocking
artifact for Fedora releases. KDE is important to us, and we don't want
to go out the door with it broken.
But, there's a problem that's coming up more and more. One of the
release criteria is that all of the default applications need to have
their basic functionality tested.* This is particularly a problem with
KDE, because the SIG has decided to ship so many applications
(apparently three web browswers, now).
I'd like to propose that we either:
1) significantly reduce the number of default apps to a more managable
number, or
2) remove this particular blocking test from KDE in particular.
In either case, it would really be helpful to have more release-time
validation of shipped applications from the KDE sig.
* https://fedoraproject.org/wiki/Fedora_28_Final_Release_Criteria#Default_a...
--
Matthew Miller
<mattdm(a)fedoraproject.org>
Fedora Project Leader
4 years, 11 months
