[SOLVED] KDE systemsettings: Houston, we have a problem
DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
As of this morning systemsettings no longer works. I checked around and found the issue. It's described in Debian bug #793574. As of now, no solution. Anyone else have this problem?
jdk
Yes, I do indeed use apt-listbugs. As you can easily see from the bug report, it was reported on Saturday. I had not rebooted my machine for a number of days until early this morning.
KDE is certainly meeting our expectations; mysql has managed to disable the Amarok database. I only posted this on the (unfounded?) expectation that it might be useful to someone.
jdk
I posted the 'apt-listbugs' question in case it was useful to someone too
You can downgrade to the old packages if you still have them in your cache, or get them from snapshots.debian.org, or just wait until fixed versions are uploaded (downgrades can be problematic - especially during a big transition).
Can take a while to filter through to testing though, so another option is to grab the fixes from sid when they appear.
edit: as another aside, 'checkrestart' from the debian-goodies package can be handy to run after an upgrade.
Last edited by descendant_command; 07-27-2015 at 04:46 AM.
Thanks. Yes the solution given in the link I posted above, suggested downgrading from the current version of systemsettings (called systemsettings5). I followed your suggestion and installed the checkrestart package. Here are the results:
Code:
~$ sudo checkrestart
Found 1 processes using old versions of upgraded files
(1 distinct program)
(1 distinct packages)
These processes (1) do not seem to have an associated init script to restart them:
ksysguardd:
3497 /usr/bin/ksysguardd
If memory servers (and it does less and less these days) ksysguard was a recently updated package that was mentioned in apt-listbugs. Anyway, these things usually get cleared up in a few days so I'll be patient.
jdk
Yeah, systemsettings has been broken for a few weeks on my machine (using Sid). I haven't needed to use it lately, so no problem.
However, last week my desktop got useless after upgrading kde-window-manager to version 4:5.3.2-2 (bug report here), so I had to downgrade. (I'm using apt-listbugs, but for some reason it didn't notify me of this bug this time, or maybe I didn't pay attention).
Didn't know about Amarok and mysql. So far I haven't had any issues with it, but I'll watch out for bugs when upgrading Amarok or mysql (I'm heavily Amarok-dependent! ).
Anyway, I guess we need to be careful in the next few weeks with the upgrade to KDE5.
Latest update: now my wifi connection has disappeared from the system tray. At least the wifi is still working. I can't remember ever having so many problems with Testing before.
jdk
Debian KDE systemsettings bug severity raised to Grave
Debian have merged the following bugs: 790703, 791606, 791699, 793539, 793878 and raised the severity level to Grave.
Solution? Be patient. Note that this is labelled specifically as a Testing (Stretch) bug.
jdk
Other than KDE apps not honoring font changes, systemsettings has been working for me. KDE5 has just been a little buggy in general due to the transition. Sometimes KDE hangs, resets the wallpaper, and continues like normal.
So I rebooted this morning to see if all the upgrades would make a difference. They most certainly did. The KDE desktop is unusable. Windows do not have any controls in the control (docking, full-screen, reducing and closing). There is no working K-menu in the lower-left corner. Fortunately, I have a couple of fall-back desktops. I am now using a gnome minimalist desktop which is at least functional. When will this end.
jdk
So I rebooted this morning to see if all the upgrades would make a difference. They most certainly did. The KDE desktop is unusable. Windows do not have any controls in the control (docking, full-screen, reducing and closing). There is no working K-menu in the lower-left corner. Fortunately, I have a couple of fall-back desktops. I am now using a gnome minimalist desktop which is at least functional. When will this end.
jdk
That's the same problem I experienced when upgrading kde-window-manager to v. 4:5.3.2-2. Downgrading it to v. 4:4.11.13-2 solved the problem.
That's the same problem I experienced when upgrading kde-window-manager to v. 4:5.3.2-2. Downgrading it to v. 4:4.11.13-2 solved the problem.
Thanks, I'll give it a try. Can you tell me the exact command(s) you used to do this. I'm worrying about falling into a dependency/broken-package hell.
cheers,
jdk
This is what my bash history shows, but I don't remember whether I downgraded directly from the testing repository (which had the previous version by that time), or downloaded the package and installed locally from my computer:
In any case, the procedure was to remove the latest version of kde-window-manager first and install the previous version, either by adding Stable to your sources.list, or by downloading the package from the Stable repository and installing it locally (I think this was what worked for me at the end).
Thanks Odiseo. I notice that Sid now has 4:5.3.2-3. Maybe I'll first try going up stream and see if that fixes the problem. I'll report back on the results.
jdk
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.