Reply to topic

Kubuntu 13.10: Two new issues after upgrade from 13.04

User avatar Annorax
Registered Member
Posts
16
Karma
0
OS
Hello all,

I recently upgraded from Kubuntu 13.04 to 13.10 and I see a couple new issues (KDE version is now 4.11.2). I'm not sure if these are KDE related or not so I apologize in advance if this is the wrong place to ask.

1.) Pressing the Power button immediately turns off the computer despite me asking it to prompt me for a dialog. This worked in 13.04. I found the bug below and ran "sudo apt-get install qt5-default qttools5-dev-tools" but it still doesn't work. Does anyone know of this issue or how to fix it?Hello all,

I recently upgraded from Kubuntu 13.04 to 13.10 and I see a couple new issues:

1.) Pressing the Power button immediately turns off the computer despite me asking it to prompt me for a dialog. This worked in 13.04. I found the bug below and ran "sudo apt-get install qt5-default qttools5-dev-tools" but it still doesn't work. Does anyone know of this issue or how to fix it?

https://bugs.launchpad.net/ubuntu/+s...e/+bug/1124149

2.) For any screensaver except a blank screen, the process stays active and consumes a lot of CPU even after it turns off. Multiple processes stay running. I tried Googling for any known issues but didn't find anything. Does anyone know of this issue or how to fix i

https://bugs.launchpad.net/ubuntu/+s...e/+bug/1124149

2.) For any screensaver except a blank screen, the process stays active and consumes a lot of CPU even after it turns off. Multiple processes stay running. I tried Googling for any known issues but didn't find anything. Does anyone know of this issue or how to fix it?
User avatar Annorax
Registered Member
Posts
16
Karma
0
OS
1.) I've managed to fix the first issue by commenting the last line of /etc/acpi/powerbtn.sh:

#/sbin/shutdown -h now "Power button pressed"

I don't really understand why this works but it does... so here's a possible solution for anyone who finds this post.

3.) I also noticed another issue - whenever I log it, I get the gear icon in the taskbar telling me I have updates when I really don't. This happens every time I log in. Any ideas?
wolfi323
Registered Member
Posts
229
Karma
0
OS
Annorax wrote:2.) For any screensaver except a blank screen, the process stays active and consumes a lot of CPU even after it turns off. Multiple processes stay running. I tried Googling for any known issues but didn't find anything. Does anyone know of this issue or how to fix it?

That's a known issue: https://bugs.kde.org/show_bug.cgi?id=224200
How to fix it?
Well, if I knew, I already _would_ have fixed it... ;)

You can kill the screensavers with kill, killall or the system monitor f.e.
But they don't take any CPU time here.
And, btw., not _all_ screensavers stay in memory, only specific ones.
So if you select a different one, you might not have the problem.

Annorax wrote:3.) I also noticed another issue - whenever I log it, I get the gear icon in the taskbar telling me I have updates when I really don't. This happens every time I log in. Any ideas?

Does it really _tell_ you there are updates? Or is just the icon visible?
If it's the latter, that's normal, the icon is set to be "Always visible" by default (at least here on openSUSE).
You can change that in the System Tray's Settings (right-click on the small up-arrow on the right end) under "Entries".
See also here: http://userbase.kde.org/Plasma/SystemTray#Settings
User avatar Annorax
Registered Member
Posts
16
Karma
0
OS
2.) I found that bug too and it seems similar but in my case, the screensaver process continues to consume at least 30% of my CPU after the screensaver is done. I'm also on KDE 4.11.2 and this is for 4.10 (fixed in 4.10.2). What screensavers work for you? I've tried a couple (my favorite is KDE Asciiquarium) and they all have this problem.

3.) This might be more of a Kubuntu issue than KDE the more I think about it. Whenever I log in, the little gear is in my taskbar saying I have updates. When I click it, after a couple moments it comes up saying I have no updates and the last check was like 8 hours ago or so. Then the icon goes away until next login.
wolfi323
Registered Member
Posts
229
Karma
0
OS
Annorax wrote:2.) I found that bug too and it seems similar but in my case, the screensaver process continues to consume at least 30% of my CPU after the screensaver is done. I'm also on KDE 4.11.2 and this is for 4.10 (fixed in 4.10.2). What screensavers work for you? I've tried a couple (my favorite is KDE Asciiquarium) and they all have this problem.

No, it is _not_ fixed in 4.10.2, the bug is still open. The fix that went into 4.10.2 didn't help with those screensavers, therefore the bug was reopened again. And nothing has been done in this area up to now (4.11.2).

The screensavers I'm aware of that have this problem are: (those are mentioned in the bug report as well)
  • blank screen (kblankscrn.kss)
  • Asciiquarium (kdeasciiquarium.kss)
  • kswarm.kss
Most of the others should work, but I can't check right now. Especially the Clock is reported to work in the bug report.
If you have that issue with _all_ screensavers and they keep using 30% CPU, it might be something else then... I cannot reproduce that here.

3.) This might be more of a Kubuntu issue than KDE the more I think about it. Whenever I log in, the little gear is in my taskbar saying I have updates. When I click it, after a couple moments it comes up saying I have no updates and the last check was like 8 hours ago or so. Then the icon goes away until next login.

Ah, ok. Sorry can't help you with this one then.
This works fine here on openSUSE.
User avatar bcooksley
Administrator
Posts
18586
Karma
83
OS
One thing you could try is attaching a debugger to one of the hung screensavers - and generating a backtrace to see where it is stuck.
Please note that X based screensavers have been removed from Plasma Workspaces 2 (Qt 5 version) in favour of a new QML based replacement, so this issue will not exist there.


System Settings and Device Actions KCM maintainer
Image
User avatar Annorax
Registered Member
Posts
16
Karma
0
OS
bcooksley wrote:One thing you could try is attaching a debugger to one of the hung screensavers - and generating a backtrace to see where it is stuck.
Please note that X based screensavers have been removed from Plasma Workspaces 2 (Qt 5 version) in favour of a new QML based replacement, so this issue will not exist there.


How would I use a debugger on the screensaver process? Apologies for the basic question - I'm new to a lot of this.

Are the KDE screensavers the same as the X screensavers? Again, apologies for the simple questions. Can you please elaborate on that? Do you know if there's a way to use Plasma Workspace 2 with Qt 5 on Kubuntu 13.10?
User avatar bcooksley
Administrator
Posts
18586
Karma
83
OS
KDE offers multiple methods for operating screensavers - however the vast majority are based on X based screensaver technology - and are hence known as "X Screensavers".

In terms of invoking a debugger - you essentially need to use gdb and attach it to the process of one of the hung screensavers.
You can get the "Process ID" or "PID" from the System Monitor, after which you can run "gdb -p <PID>" to attach GDB to it.


System Settings and Device Actions KCM maintainer
Image

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], boudewijn, brand, doublerainbow64, edmael, Exabot [Bot], franku, Google [Bot], Hans, i4dnf, jgrulich, jstaniek, khsien, koriun, lazyit, lbaran, Majestic-12 [Bot], metzman, MiceAreVeryNice, MSNbot Media, nezumi, ooker, pedrorodriguez, Tuukka, Yahoo [Bot]