I was curious about something. KDE has its own crash handling system.
How does this community track any metrics around code stability if
upstream gets reports? Kontact has segfaulted 20 times on me today.
Each time it says it cannot generate a bug report. Abrtd does not seem
to pick up anything. Shouldn't it? How does this community track
when a recent update suddenly starts making things crash? Kontact was
fine 3 weeks ago. I updated today (3 weeks of patches) and its crashing
all the time to the point its unusable. It won't generate a bug report,
abrtd seems not to notice either.
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
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).
Looking over some broken deps reports, I came across some old packages:
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 ?
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
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?
I know that RHEL8 isn't out yet, but I'd like to run KDE on my RHEL8
Beta. Even if it's just the basic KDE desktop.
I'm fine building it myself, but I'm having a hard time figuring out
the rebuild flow.
If I (or anyone) were to rebuild KDE for RHEL8, where do I start? and
then what's next?
There are base QT5 packages in RHEL8 beta. Do you think I would need
to rebuild QT5? Or just start with RHEL8's QT5 packages.
I am having trouble getting qDebug() output displayed in the
'application output' tab in Qt Creator.
I am aware of the need to explicitly enable Qt message logging and have
the following in my ~/.config/QtProject/qtlogging.ini:
But even with this, Qt Creator does not show any qDebug() messages. I am
getting these messages if I run the application from Konsole. Just not
in Qt creator.
Any Idea on what can be done to fix this?
I'm on Fedora 29, Qt 5.11.3, Qt Creator v4.7.2.
Thanks and regards,
After the upgrade to F30 I cannot print double sided in Okular with my
HP printer. I used to have dulex options enabled in the printing dialog,
but they're now disabled.
Anyone can confirm this issue with other printers?
KDE framework 5.55.0
HP Color Laserjet Pro M252dw