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
Hi: I've been running KDE in Fedora <= 30 and SL <= 7.7 for years. I
just ran $ printenv and found that, in both, QTDIR, QTINC, PATH, QTLIB
are all going through /usr/lib64/qt-3.3
MythTV (from rpms built locally and running from konsole tabs) tells me
it is compiled with and using Qt version 5.12.5 in F30 and 5.9.7 in SL7
I have been having a few OSD-related problems with its development
branch recently and wonder if they might be related to those outdated
environment variables - but just updating them feels reckless.
I just installed Kst plot software 2.0.8-23.fc30 on Fedora 30.
It has a 'Data wizard' that brings up a dialog, and that has another
button that brings up the standard file open dialog so that we can
select a plot data file. I now see that the file open dialog does not
allow to select files. It only allows to select directories. And that
does not help as the wizard will proceed only if it gets a valid file.
I had used Kst on Fedora long back and it used to work fine.
Any idea why this is happening?
1. bug in Kst source code
2. Something wrong with the file open dialog as it seems to be
based on Qt4/KDE4 (or whatever)
3. Kst has plugin support and the file selection logic is tied to
available plugins and for some reason ASCII file handling is broken
Any help is highly appreciated.
How do I get this thing to shut up? I update my system using dnf from
the command line and don't want to change, but this widget keeps
popping up notifications and its configuration panel doesn't have a
toggle to turn it off.
What do I need to uninstall?
I'd like to work on bringing plasma-5.17.x officially to f31 (and possibly f30 too).
kde frameworks 5.64.0 is on the way to testing (which we'll also build against here).
Any concerns or objections?
It had to happen sooner or later, I suppose. I had kept an off-line
password manager called PwManager. This one description survives:
The summary says it all: "this project is orphaned and deprecated." (It
had seen no update since 2015.) And now it won't load in F31, though it
did in F30 and the versions immediately before it.
I had moved most, but by no means all, of my passwords to LastPass, the
cross-platform cloud-based password manager. But I had a few that I did
/not/ want to put into the cloud.
Can anyone suggest a way to get at them? Or should I just write them off
as gone for good?
Review Request: polkit-qt-1 - Qt bindings for PolicyKit -
Fyi, ^^ newer polkit-qt releases dropped support for qt4, so this new one
will track latest developments, and existing polkit-qt will (continue to)
track legacy/qt4 support only
Need to do some similar work for phonon (ie, latest phonon release dropped
support for qt4) affecting both phonon, and backends (gstreamer). will
consider to drop support for qt4-based vlc backend (for f32+)