kde power button configuration ignored
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
KDE Base |
Unknown
|
Medium
|
|||
acpid (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Bug Description
Even though in 'power management' I have 'when power button pressed' set to 'suspend to disk' set in all profiles (and can confirm which is selected via the system tray icon), nothing happens when I press the power button.
This worked in KDE 4.x under 9.10, appears broken by using the 10.4 beta.
Hardware is a Dell Inspiron 1525 laptop.
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #1 |
Philip Muškovac (yofel) wrote : | #2 |
I think powerdevil should be responsible for that.
tags: | added: lucid |
affects: | ubuntu → kdebase-workspace (Ubuntu) |
Changed in kdebase: | |
status: | Unknown → New |
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #3 |
Worse under Ubuntu 10.4 beta 2's packages, now the screen changes to a Kubuntu
logo with animated dots underneath and hangs there.
CTRL-ALT-F1 swaps to text console but the keyboard doesn't respond when I try
to login.
I *suspect* it's trying to reboot, and the hang is due to my CIFS mounts not
being pulled down before the wireless is, but that's a different bug; it should
be hibernating, not rebooting.
Using the 'suspend to disk' option on the logout dialogue all is well.
This was rock solid under 9.10 with Kubuntu backports of the same KDE4
version...
Jon Packard (jonpackard) wrote : | #4 |
I am experiencing similar behavior using Kubuntu Lucid Beta 2. Even though power button is set to give the logout dialog in all power profiles, instead the system is powered off.
summary: |
- kde power button + kde power button configuration ignored |
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #5 |
Using buttons added to the main menu panel work fine too.
Still broken in 10.4 release :-( Only now it's worse because when the Kubuntu logo comes up, the machine is now hard-locked (num lock, caps lock do not light the LEDs and ctrl-alt-del or ctrl-alt-F1 ignored) and I have to hold down the power button to power down.
Settings are still set to hibernate in all profiles on button press.
Jon, what's your hardware ?
Jon Packard (jonpackard) wrote : Re: [Bug 553557] Re: kde power button configuration ignored | #6 |
@Tom
I was running Kubuntu on a Dell Latitude D630 (Core2Duo with Intel
graphics), but have gone back to Ubuntu shortly after commenting on this
bug. No problems on Ubuntu 10.04.
On Fri, Apr 30, 2010 at 1:48 PM, Tom Chiverton <bugs.launchpad
falkensweb.com> wrote:
> Using buttons added to the main menu panel work fine too.
>
> Still broken in 10.4 release :-( Only now it's worse because when the
> Kubuntu logo comes up, the machine is now hard-locked (num lock, caps lock
> do not light the LEDs and ctrl-alt-del or ctrl-alt-F1 ignored) and I have to
> hold down the power button to power down.
> Settings are still set to hibernate in all profiles on button press.
>
> Jon, what's your hardware ?
>
> --
> kde power button configuration ignored
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in KDE Base Components: New
> Status in “kdebase-workspace” package in Ubuntu: New
>
> Bug description:
> Even though in 'power management' I have 'when power button pressed' set to
> 'suspend to disk' set in all profiles (and can confirm which is selected via
> the system tray icon), nothing happens when I press the power button.
>
> This worked in KDE 4.x under 9.10, appears broken by using the 10.4 beta.
>
> Hardware is a Dell Inspiron 1525 laptop.
>
> To unsubscribe from this bug, go to:
> https:/
>
Adam Porter (alphapapa) wrote : | #7 |
I doubt that this is a bug in KDE itself, especially since it worked in the Lucid betas. It would probably be good to close the bug on the KDE tracker so it doesn't waste the KDE folks' time. This is almost surely a bug in Kubuntu.
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #8 |
Adam: It didn't work for me in the Lucid betas.
It worked for me last using Kubuntu's KDE4.4 backports PPA on their 9.10 release.
Running the stock Kubuntu 10.4 (since first beta) it has never worked.
However, Jon's comment in #6 seems to concur with you...
Philip Muškovac (yofel) wrote : | #9 |
Ok, it works fine here, but this sounds familiar. Just to make sure this isn't related to acpi, please edit /etc/acpi/
/sbin/shutdown -h now "Power button pressed"
with something like
#/sbin/shutdown -h now "Power button pressed"
touch /tmp/powerbutto
and check if it works then and if you have a "powerbutton.fail" file in /tmp.
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #10 |
Confirmed, you are spot on, something is causing that script to fail to spot KDE is running, and it *was* falling though to the end.
I'll poke at it and see if I can locate what goes wrong... initial testing by putting the code from the main script into the command line (konsole) indicates it's in the support functions.
falken@wopr:~$ . /usr/share/
falken@wopr:~$ getXuser() {
> user=`pinky -fw | awk '{ if ($2 == ":'$displaynum'" || $(NF) == ":'$displaynum'" ) { print $1; exit; } }'`
> if [ x"$user" = x"" ]; then
> startx=`pgrep -n startx`
> if [ x"$startx" != x"" ]; then
> user=`ps -o user --no-headers $startx`
> fi
> fi
> if [ x"$user" != x"" ]; then
> userhome=`getent passwd $user | cut -d: -f6`
> export XAUTHORITY=
> else
> export XAUTHORITY=""
> fi
> export XUSER=$user
> }
falken@wopr:~$ getXconsole
Couldn't get a file descriptor referring to the console
falken@wopr:~$ echo $XUSER
falken@wopr:~$
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #11 |
That single line of output comes from the first line of the getXconsole method in /usr/share/
falken@wopr:~$ fgconsole
Couldn't get a file descriptor referring to the console
falken@wopr:~$
The strace shows some permission denied errors for opening devices in /dev/ but I dunno if that's normal or not. I think that that means getXuser (which is overridden in the main powerbutn.sh) is never called, and so XUSER is never set. This means the script falls down to the bottom.
Bah.
falken@wopr:~$ strace fgconsole
execve(
brk(0) = 0x8693000
access(
mmap2(NULL, 8192, PROT_READ|
access(
open("/
fstat64(3, {st_mode=
mmap2(NULL, 126614, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb779e000
close(3) = 0
access(
open("/
read(3, "\177ELF\
fstat64(3, {st_mode=
mmap2(NULL, 1415592, PROT_READ|
mprotect(0x408000, 4096, PROT_NONE) = 0
mmap2(0x409000, 12288, PROT_READ|
mmap2(0x40c000, 10664, PROT_READ|
close(3) = 0
mmap2(NULL, 4096, PROT_READ|
set_thread_
mprotect(0x409000, 8192, PROT_READ) = 0
mprotect(0x804a000, 4096, PROT_READ) = 0
mprotect(0xe1a000, 4096, PROT_READ) = 0
munmap(0xb779e000, 126614) = 0
brk(0) = 0x8693000
brk(0x86b4000) = 0x86b4000
open("/
open("/
fstat64(3, {st_mode=
mmap2(NULL, 4096, PROT_READ|
read(3, "# Locale name alias data base.\n#"..., 4096) = 2570
read(3, "", 4096) = 0
close(3) = 0
munmap(0xb77bc000, 4096) = 0
open("/
open("/
fstat64(3, {st_mode=
mmap2(NULL, 373, PROT_READ, MAP_PRIVATE, 3, 0) = 0xb77bc000
close(3) = 0
open("/
fstat64(3...
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #12 |
- powerbtn.sh Edit (2.0 KiB, text/x-sh)
Scratch #11, wasn't running as root, which of course the powerbtn.sh would be :-)
Cut'n'paste tests now show
... as before ...
root@wopr:~# getXconsole
root@wopr:~# echo $XUSER
falken
root@wopr:~# test "$XUSER" != "" && pidof dcopserver > /dev/null && test -x /usr/bin/dcop && /usr/bin/dcop --user $XUSER kded kded loadedModules | grep -q klaptopdaemon
root@wopr:~# echo $?
1
root@wopr:~# test "$XUSER" != "" && test -x /usr/bin/qdbus && test -r /proc/$(pidof kded4)/environ && su - $XUSER -c "eval $(echo -n 'export '; cat /proc/$(pidof kded4)/environ |tr '\0' '\n'|grep DBUS_SESSION_
-bash: test: too many arguments
Ahh ha ! That is the line that's meant to spot KDE4 and poke it... it looks like a horrible undocument mess to me though.
root@wopr:~# pidof kded4
14371 2153 1955
root@wopr:~# ps -efww|grep kded4
falken 1955 1 0 May01 ? 00:01:23 kdeinit4: kded4 [kdeinit]
falken 2153 1955 0 May01 ? 00:00:00 [kded4] <defunct>
root 14371 1 0 May03 ? 00:00:02 kdeinit4: kded4 [kdeinit]
root 20826 20690 0 22:43 pts/1 00:00:00 grep kded4
I found the process I think it should be asking for, and it looks like it should work:
root@wopr:~# cat /proc/1955/environ |tr '\0' '\n'|grep DB
DBUS_SESSION_
root@wopr:~# su - $XUSER -c "eval export DBUS_SESSION_
/modules/powerdevil
root@wopr:~#
As a suggestion, the final test should replace 'pidof kded4' with 'ps -efww|grep kded4|grep $XUSER|grep -v grep|grep -v defunct
' or similar.
I do not believe the defunct is the problem, rather there are many kded4's (one for me, one for root, one for every user logged in ?). I've filtered out defunct ones anyway, and also restricted it to the current X user name. This should more reliably locate the one KDE instance we are interested in.
This appears to work:
PIDOFKDE4=`ps -efww|grep kded4|grep $XUSER|grep -v grep|grep -v defunct|tr -s ' '|awk '{print $2}'`
if pidof x $PMS > /dev/null ||
( test "$XUSER" != "" && pidof dcopserver > /dev/null && test -x /usr/bin/dcop && /usr/bin/dcop --user $XUSER kded kded loadedModules | grep -q klaptopdaemon) ||
( test "$XUSER" != "" && test -x /usr/bin/qdbus && test -r /proc/$
echo hello
fi
Attached is a a version of powerbtn.sh that works for me.
Someone with more Bash voodoo might want to take a look at this.
Using this version, with a power button press, hibernate and resume betwen the two ls's :
root@wopr:~# ls -lah /tmp/powerbutto
-rw-r--r-- 1 root root 0 2010-05-03 22:01 /tmp/powerbutto
root@wopr:~# date
Tue May 4 23:10:10 BST 2010
root@wopr:~# ls -lah /tmp/powerbutto
-rw-r--r-- 1 root root 0 2010-05-03 22:01 /tmp/powerbutto
root@wopr:~# date
Tue May 4 23:12:20 BST 2010
this...
affects: | kdebase-workspace (Ubuntu) → acpid (Ubuntu) |
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #13 |
- powerbtn.sh Edit (2.1 KiB, text/x-sh)
There was an acpid update today, here are my suggested changes merged into the new version.
Tom Helner (duffman) wrote : | #14 |
Since my upgrade to 10.04 I am seeing the exact behavior as Tom describes above.
This line in /etc/acpi/
( test "$XUSER" != "" && test -x /usr/bin/qdbus && test -r /proc/$(pidof kded4)/environ && su - $XUSER -c "eval $(echo -n 'export '; cat /proc/$(pidof kded4)/environ |tr '\0' '\n'|grep DBUS_SESSION_
Which causes "/sbin/shutdown -h now "Power button pressed"" to be run.
As Tom describes, changing powerbtn.sh to use the following works for me:
PIDOFKDE4=`ps -efww|grep kded4|grep $XUSER|grep -v grep|grep -v defunct|tr -s ' '|awk '{print $2}'`
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #15 |
https:/
However, I think that's a different issue as I've now hibernated twice, and still have just the one defunct process.
There's nothing in the KDE issue tracker, so I've opened https:/
I think these ACPI scripts need to be more robust weather it's a common issue or not however.
Changed in kdebase: | |
status: | New → Invalid |
Philip Muškovac (yofel) wrote : | #16 |
Switched tracked upstream report.
Changed in kdebase: | |
status: | Invalid → Unknown |
Changed in kdebase: | |
status: | Unknown → New |
Manuel Bärenz (turion) wrote : | #17 |
I am experiencing a kind of the same bug: I have two kded4's and one of them defunct.
When I press the power button, the computer immediately shuts down.
But playing on the /etc/acpi/
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #18 |
I assume you've double checked the KDE power settings, but other than that I can't think of anything else unless it's a separate issue.
Manuel Bärenz (turion) wrote : | #19 |
I checked it a few more times with different settings and found out, that it actually kind of works:
When I disable the powerbtn.sh, the system still shuts down without asking, but it seems to log out from the kde session at least. This holds for the kde setting "Shut down on power button pressed".
If I change the kde setting to e.g. "logout", it correctly shows the logout screen.
If I now enable the script handicapped, to say with the shutdown command replaced by "touch sometestfile", the file sometestfile is produced every time I press the power button, of course regardless of the kde setting. This is the expected buggy behaviour.
I have, by the way, lucid running on an Compaq nx6325 with an AMD64 processor.
So in conclusion, my situation: The bug is there, it's in the script powerbtn.sh, as described by previous. However, kde in some way watches separately if the power button pressed and interprets it correctly according to the settings.
So why is the script still kept? My workaround is disabling it.
42 comments hidden Loading more comments | view all 101 comments |
In KDE Bug Tracking System #236490, Laurent Bonnaud (laurent-bonnaud) wrote : | #62 |
On Fri, 2010-07-23 at 17:11 +0200, Tom Chiverton wrote:
> No, suspend and resume does not trigger extra ones
[...]
> I have hibernated several times since
suspend and hibernate are not the same thing. Did you really try both ?
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #63 |
Comment #16: Yes.
description: | updated |
In KDE Bug Tracking System #236490, Bugs+kde (bugs+kde) wrote : | #64 |
*** This bug has been confirmed by popular vote. ***
Changed in kdebase: | |
status: | New → Confirmed |
43 comments hidden Loading more comments | view all 101 comments |
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #20 |
A new version of /etc/acpi/
From my testing of pressing the power button, the action I have set in KDE is now honoured.
From testing the new script directly, it returns a 0 in the place I expect, and calling the methods as intended also works OK.
root@wopr:~# . /usr/share/
root@wopr:~# `CheckPolicy`
0: command not found
root@wopr:~# if ( [ `CheckPolicy` = 0 ] || CheckUPowerPolicy ); then echo "exiting"; fi
exiting
root@wopr:~#
44 comments hidden Loading more comments | view all 101 comments |
In KDE Bug Tracking System #236490, Forgetful-tan (forgetful-tan) wrote : | #65 |
I have the same issue in my kubuntu 10.04 system, KDE version 4.4.2 .
I found that my issue may due to I'm using encrypted home directory. I used encryptfs bring by ubuntu. I found that each time when I'm doing login to my encrypted-home accounts, it left a [kded4] defunct process. When using su to this user and logout, it printed 'Sessions still open, not unmounting' .
I found that encryptfs used a pam plugin to function that auto mount/unmount home . In the pam config, there is line like
session optional pam_ecryptfs.so unwrap
When I commented these line out and login again, the defunct process went away. And when I uncommented them, the problem happened again.
Hope this information will help the debugging.
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #66 |
I don't have an encrypted /home, though it is on a different partition it's just configured in /etc/fstab as normal.
Even so, I do have a similar line:
falken@wopr:~$ grep pam_ecr /etc/pam.d/* /etc/pam.conf
/etc/pam.
/etc/pam.
/etc/pam.
/etc/pam.
falken@wopr:~$
I wonder what the effect of removing them is ?
In KDE Bug Tracking System #236490, jakartadean (jakartadean) wrote : | #67 |
I'm running a fairly new kubuntu 10.04 installation on a new netbook, and I get thousands of defunct kded4 processes. I rebooted about 4 hours ago and just now ran "ps aux | grep kded4 | wc" which shows 1,561 lines. My /home directory is encrypted. kde is version 4.4.2, and kernel is 2.6.32-24
In KDE Bug Tracking System #236490, jakartadean (jakartadean) wrote : | #68 |
I've posted the above to https:/
46 comments hidden Loading more comments | view all 101 comments |
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #21 |
Workaround (at least of 10.10) is to simply uninstall the acpid and acip-support packages (including configuration files i.e. 'purge').
No ill effects observed yet, but I've not really checked battery life or anything.
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #22 |
Sorry, this is still busted.
If you remove (and purge) acpid and acpi-support and reinstall them (on 10.10), it still breaks.
I commented the last line of /etc/acpi/
falken@wopr:/tmp$ ls -lah
total 48K
drwxrwxrwt 9 root root 12K 2010-11-10 21:47 .
drwxr-xr-x 26 root root 4.0K 2010-11-05 21:27 ..
drwx------ 2 falken falken 4.0K 2010-11-10 21:47 .esd-1000
drwxrwxrwt 2 root root 4.0K 2010-11-10 21:47 .ICE-unix
drwx------ 2 falken falken 4.0K 2010-11-10 21:47 kde-falken
drwx------ 2 falken falken 4.0K 2010-11-10 21:47 ksocket-falken
drwx------ 2 falken falken 4.0K 2010-11-10 21:47 pulse-s6YhteYQrpJA
drwx------ 2 falken falken 4.0K 2010-11-10 21:47 ssh-rVZOMZ1835
-r--r--r-- 1 root root 11 2010-11-10 21:46 .X0-lock
drwxrwxrwt 2 root root 4.0K 2010-11-10 21:46 .X11-unix
...press power button, hibernates, press power button and machine resumes...
falken@wopr:/tmp$ ls -lah
.
.
.
-rw-r--r-- 1 root root 0 2010-11-10 21:49 fail
.
.
.
Simple testing confirms the X session detected appears to be busted *again*.
root@wopr:~# [ -r /usr/share/
root@wopr:~# getXuser() {
> user=`pinky -fw | awk '{ if ($2 == ":'$displaynum'" || $(NF) == ":'$displaynum'" ) { print $1; exit; } }'`
> if [ x"$user" = x"" ]; then
> startx=`pgrep -n startx`
> if [ x"$startx" != x"" ]; then
> user=`ps -o user --no-headers $startx`
> fi
> fi
> if [ x"$user" != x"" ]; then
> userhome=`getent passwd $user | cut -d: -f6`
> export XAUTHORITY=
> else
> export XAUTHORITY=""
> fi
> export XUSER=$user
> }
root@wopr:~#
root@wopr:~# [ -r /usr/share/
root@wopr:~# PMS="gnome-
root@wopr:~# PMS="$PMS guidance-
#now the main if statement from powerbtn.sh, modified to echo what is going on:
root@wopr:~# if pidof x $PMS > /dev/null || ( test "$XUSER" != "" && pidof dcopserver > /dev/null && test -x /usr/bin/dcop && /usr/bin/dcop --user $XUSER kded kded loadedModules | grep -q klaptopdaemon) || ( test "$XUSER" != "" && test -x /usr/bin/qdbus && test -r /proc/$(pidof kded4)/environ && su - $XUSER -c "eval $(echo -n 'export '; cat /proc/$(pidof kded4)/environ |tr '\0' '\n'|grep DBUS_SESSION_
fail
root@wopr:~#
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #23 |
Oh, look, and it's because of the exact same bug the last update fixed:
root@wopr:~# pidof kded4
2383 2008
root@wopr:~#
Where's the 'regression' option :-)
Adam Porter (alphapapa) wrote : | #24 |
:( Well, at least we'll have Unity and Wayland soon. Those will
distract us from these bugs, right? Right? ...
On Wed, Nov 10, 2010 at 16:03, Tom Chiverton <email address hidden> wrote:
> Oh, look, and it's because of the exact same bug the last update fixed:
> root@wopr:~# pidof kded4
> 2383 2008
> root@wopr:~#
>
> Where's the 'regression' option :-)
>
> --
> kde power button configuration ignored
> https:/
> You received this bug notification because you are a direct subscriber
> of the bug.
>
Adam Porter (alphapapa) wrote : | #25 |
So...two releases later...still not fixed.
Changed in acpid (Ubuntu): | |
status: | New → Confirmed |
Adam Porter (alphapapa) wrote : | #26 |
By the way, I'd really like to know why fixing this bug was declined for Lucid, an LTS. This is actually a DATA LOSS bug, because if someone presses the power button, even by accident (children? pets?), the system will power off WITHOUT SAVING DATA. This is unacceptable, and yet another example of extremely poor handling of bugs by Ubuntu.
tags: | added: maverick |
tags: | added: dataloss |
42 comments hidden Loading more comments | view all 101 comments |
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #69 |
Still happens with 4.5.4
In KDE Bug Tracking System #236490, Peter Kelder (peter-kelder-quicknet) wrote : | #70 |
Same here on kubuntu 10.10/kde 4.5.1
42 comments hidden Loading more comments | view all 101 comments |
michael (reeves-87) wrote : | #27 |
- powerbth.diff Edit (1.5 KiB, text/plain)
This patch should resolve the issue. I modified powerbtn.sh to account for multiple kded4 instances running and added a little documentation explaining this since it seems to be a repeat problem.
tags: | added: patch |
43 comments hidden Loading more comments | view all 101 comments |
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #71 |
Not fixed in 4.6
In KDE Bug Tracking System #236490, Arthur Țițeică (arthur-titeica) wrote : | #72 |
It's not happening here on a clean install of Kubuntu 10.10 x64 and straight upgrade to KDE 4.6 from PPA.
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #73 |
falken@wopr:~$ ps -efw|grep kded4
falken 2037 1 0 Jan28 ? 00:00:08 kdeinit4: kded4 [kdeinit]
falken 2321 2037 0 Jan28 ? 00:00:00 [kded4] <defunct>
falken 5892 2257 0 13:40 pts/0 00:00:00 grep kded4
falken@wopr:~$
This is 32bit Kubutnu 10.10 (upgraded every 6 months from 9.4) with 4.6 from their backports PPA.
Changed in kdebase: | |
importance: | Unknown → Medium |
In KDE Bug Tracking System #236490, Tais P. Hansen (taisph) wrote : | #74 |
I don't know if anybody noticed this but turning off notifications such as popups and sounds on system events, drastically reduces the zombies at least on my laptop.
In KDE Bug Tracking System #236490, Tais P. Hansen (taisph) wrote : | #75 |
I think I may have found the culprit. Stopping and disabling the "Notification Helper" in the KDE Services Configuration seems to prevent further defunct kded processes.
In KDE Bug Tracking System #236490, Lamarque (lamarque) wrote : | #76 |
*** Bug 239965 has been marked as a duplicate of this bug. ***
In KDE Bug Tracking System #236490, Andrej-cremoznik-4 (andrej-cremoznik-4) wrote : | #77 |
I can confirm Tais P. Hansen's findings. A quick google search shows Notification Helper as a Kubuntu app so it's a downstream issue.
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #78 |
Be aware doing so kills
"Notifications for upgrade information, when available.
...
Notifications for when upgrades require a reboot to complete." according to http://
In KDE Bug Tracking System #236490, Ralf Jung (0tlwui8x-post-kj985rvy) wrote : | #79 |
Is (K)Ubuntu aware of the issue, i.e. is this reported in their launchpad system?
In KDE Bug Tracking System #236490, Tais P. Hansen (taisph) wrote : | #80 |
Yes. It initially started in launchpad and was sent upstream.
There's apparently now a fix buried in a bzr tree somewhere.
51 comments hidden Loading more comments | view all 101 comments |
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #28 |
Still busted in natty, but I can't see the nominate button...
Adam Porter (alphapapa) wrote : | #29 |
$ pidof kded4
9332 9331 9328 9327 3159 2789
$ pg kded4
2789 ? Sl 0:15 kdeinit4: kded4 [kdeinit]
3159 ? Z 0:00 [kded4] <defunct>
4402 pts/1 D+ 0:00 grep --color=auto -i kded4
9327 ? Z 0:00 [kded4] <defunct>
9328 ? Z 0:00 [kded4] <defunct>
9331 ? Z 0:00 [kded4] <defunct>
9332 ? Z 0:00 [kded4] <defunct>
What a mess. Yet it would seem so simple to ignore the defunct processes (why do they still exist as zombies??). Please don't tell me that this bug is going to be in yet another Kubuntu release.
Like Tom said: where's the nominate button gone?
Malte S. Stretz (mss) wrote : | #30 |
There are actually two bugs mangled here. The do-not-
BTW, I see/saw this bug under different circumstances: Back when NM still sucked, I had to use kvpnc to connect to a VPN. That one had to be started as root, causing a second kded process to be spawned (owned by root). That one would break the powerbtn.sh script. I think it still happens sometimes accidently with other apps.
The last few lines in the powerbtn.sh script is a big WTF BTW.
50 comments hidden Loading more comments | view all 101 comments |
In KDE Bug Tracking System #236490, Laurent Bonnaud (laurent-bonnaud) wrote : | #81 |
This bug was specific to Kubuntu and has been fixed in natty.
49 comments hidden Loading more comments | view all 101 comments |
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #31 |
Yeah, to an extent it doesn't matter why the other kded's are there, the script hasn't been programmed defensively, and although it was fixed at some point, those changes have been reverted, making it worse irrespective of it KDE fix their issue or not (it might be fixed in Natty, hard to tell because it was so intermittent for me).
Adam Porter (alphapapa) wrote : | #32 |
I think this bug needs to be marked as Critical importance for the acpi (Ubuntu) package, because this is a data-loss bug! Instant system shutdown without confirmation or prompting to save data is...data-loss! This *needs* to be fixed before Natty is released.
tags: | added: natty |
49 comments hidden Loading more comments | view all 101 comments |
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #82 |
Not fixed in Natty for me:
falken@wopr:~$ ps -efw|grep kded
falken 1975 1 0 21:34 ? 00:00:05 kdeinit4: kded4 [kdeinit]
falken 2287 1975 0 21:36 ? 00:00:00 [kded4] <defunct>
This is after I went back and re-enabled the notification service.
In KDE Bug Tracking System #236490, Jonathan Riddell (jr) wrote : | #83 |
"11.04ubuntu3 now uploaded for anyone running 11.04 Beta 1. Upgrade to kubuntu-
In KDE Bug Tracking System #236490, Jonathan Riddell (jr) wrote : | #84 |
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #85 |
Not resolved. See comment at your link.
In KDE Bug Tracking System #236490, Cfeck (cfeck) wrote : | #86 |
What is the status of this bug? Does it still happen with a recent KDE version, such as 4.6.5 or 4.7.x? Please add a comment.
In KDE Bug Tracking System #236490, Dusty-w (dusty-w) wrote : | #87 |
I'm using KDE 4.7.0 (4.7.1 has not yet been packaged for Natty) and the problem is still there.
I had to disable all my cronjobs.
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #88 |
Yup, still busted here in 11.04 Kubuntu:
falken@wopr:/tmp$ ps -efww|grep kded ; dpkg -l|grep kdebase-workspace
falken 2833 1 0 Sep14 ? 00:00:08 kdeinit4: kded4 [kdeinit]
falken 3530 2833 0 Sep14 ? 00:00:00 [kded4] <defunct>
falken 10386 3378 0 16:12 pts/0 00:00:00 grep kded
ii kdebase-workspace 4:4.6.5-
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #89 |
Still occurs with Kubuntu 11.10 beta 2 (version 4:4.7.1-0ubuntu2) !
falken@wopr:/tmp$ ps -efww|grep kded
falken 2316 1 0 11:28 ? 00:00:02 kdeinit4: kded4 [kdeinit]
falken 2714 2316 0 11:29 ? 00:00:00 [kded4] <defunct>
falken 3778 2598 0 13:05 pts/0 00:00:00 grep kded
falken@wopr:/tmp$
55 comments hidden Loading more comments | view all 101 comments |
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #33 |
Busted in 11.11 beta 2 still
tags: | added: oneiric |
56 comments hidden Loading more comments | view all 101 comments |
In KDE Bug Tracking System #236490, Cfeck (cfeck) wrote : | #90 |
Tom, does comment #29 fix it for you? If not, you probably would have to go through http://
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #91 |
#29 fixed it in earlier KDEs, it appears to have been turned back on for me. I've turned it off and will report back.
Disabling this service isn't a proper fix, of course, just identifying the cause.
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #92 |
Yeah, work around seems to work.
In KDE Bug Tracking System #236490, Cfeck (cfeck) wrote : | #93 |
The "Notification Helper" is a Ubuntu-specific package. Please report this problem to https:/
In KDE Bug Tracking System #236490, Bugs-kde-org-6 (bugs-kde-org-6) wrote : | #94 |
Already reported (https:/
In KDE Bug Tracking System #236490, Cfeck (cfeck) wrote : | #95 |
The kubuntu-
In KDE Bug Tracking System #236490, Cfeck (cfeck) wrote : | #96 |
Reading all comments I see no indication that this bug is present without the kubuntu-
In KDE Bug Tracking System #236490, Cfeck (cfeck) wrote : | #97 |
By quickly looking at the source for the mentioned package, it leaks KProcess instances everywhere.
Changed in kde-baseapps: | |
status: | Confirmed → Unknown |
62 comments hidden Loading more comments | view all 101 comments |
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #34 |
Why has this changed status ?
Philip Muškovac (yofel) wrote : | #35 |
The upstream bug was changed to resovled/
---
Ubuntu Bug Squad volunteer triager
http://
62 comments hidden Loading more comments | view all 101 comments |
In KDE Bug Tracking System #236490, Cfeck (cfeck) wrote : | #98 |
Tom, at least apportevent.cpp needs to be fixed, too.
61 comments hidden Loading more comments | view all 101 comments |
michael (reeves-87) wrote : | #36 |
This bug appears to have been fixed as side effect of a security update that just posted today. The targeted fix was LP#893821.
aboaboit (andrea-borgia-deactivatedaccount) wrote : | #37 |
With yesterday's updates to Kubuntu 11.10 (64bit), it now works on my EEEpc 1215p. Only (minor) glitch, which might as well depend on the specific hw I have, is that the dialog box pops up after 10 seconds or so. This only happens the first time, though.
Dennis Schridde (devurandom) wrote : | #38 |
(In reply to comment #37)
> the dialog box pops up after 10 seconds or so. This only happens the first time, though.
Have a look at bug #713198
Adam Porter (alphapapa) wrote : | #39 |
It's a shame that data-loss wasn't reason enough to get it fixed. It took a much more obscure security bug, one that's very unlikely to occur in the real world. The data-loss angle is an everyday risk: press the power button, expecting to get prompted to shutdown, and watch all your X apps get killed, instead.
Hey, I'm glad they fixed the security aspect, but let's be realistic here: If a user has the ability to run processes on the system, and the system is a laptop or desktop running KDE 4, most likely the user has physical access to the system, and he could snoop-on or erase data without having to jump through such obscure hoops. On the other hand, the data-loss aspect could happen because of a cat or a dog or a two-year-old--or a forgetful adult.
*sigh* Priorities...
Tom Chiverton (bugs-launchpad-net-falkensweb) wrote : | #40 |
This is busted in 12.04 beta again. Pressing the power button just activates the screen saver instead of hibernate.
58 comments hidden Loading more comments | view all 101 comments |
In KDE Bug Tracking System #236490, X-wstephenson (x-wstephenson) wrote : | #99 |
*** Bug 282490 has been marked as a duplicate of this bug. ***
Changed in acpid (Ubuntu): | |
status: | Confirmed → Fix Released |
In KDE Bug Tracking System #236490, dogshu (dogshu) wrote : | #100 |
This bug still exists on Gentoo with KDE 4.14.3. I see no notification-helper packages installed.
thud ~ # date
Thu Aug 27 20:29:20 EDT 2015
thud ~ # equery list kde-apps/
* Searching for kdebase-meta in kde-apps ...
[IP-] [ ] kde-apps/
thud ~ # ps aux | grep Z
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 948 0.0 0.2 10836 2216 pts/0 S+ 20:29 0:00 grep --colour=auto Z
jim 11078 0.0 0.0 0 0 ? Z Aug20 0:00 [kded4] <defunct>
jim 22581 0.0 0.0 0 0 ? Z Aug23 0:00 [kded4] <defunct>
jim 22692 0.0 0.0 0 0 ? Z Aug23 0:00 [kded4] <defunct>
jim 22727 0.0 0.0 0 0 ? Z Aug23 0:00 [kded4] <defunct>
jim 22785 0.0 0.0 0 0 ? Z Aug23 0:00 [kded4] <defunct>
jim 22823 0.0 0.0 0 0 ? Z Aug23 0:00 [kded4] <defunct>
jim 23014 0.0 0.0 0 0 ? Z Aug23 0:00 [kded4] <defunct>
jim 23022 0.0 0.0 0 0 ? Z Aug23 0:00 [kded4] <defunct>
jim 23060 0.0 0.0 0 0 ? Z Aug23 0:00 [kded4] <defunct>
jim 23122 0.0 0.0 0 0 ? Z Aug23 0:00 [kded4] <defunct>
jim 23125 0.0 0.0 0 0 ? Z Aug23 0:00 [kded4] <defunct>
jim 30718 0.0 0.0 0 0 ? Z Aug16 0:00 [kded4] <defunct>
jim 30791 0.0 0.0 0 0 ? Z Aug16 0:00 [kded4] <defunct>
jim 30866 0.0 0.0 0 0 ? Z Aug16 0:00 [kded4] <defunct>
thud ~ # equery list '*helper*'
* Searching for *helper* ...
[IP-] [ ] net-libs/
thud ~ #
In KDE Bug Tracking System #236490, dogshu (dogshu) wrote : | #101 |
FYI, this box does not run a local X. I run some KDE apps (konsole, konqueror) under icewm in an x2go session. However, right now there is no x2go server running, either. Here's my full process list. I note lots of dbus-daemon and kdeinit4 processes running as well.
thud ~ # ps aux
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
root 1 0.0 0.1 4208 1024 ? Ss Aug09 0:33 init [3]
root 2 0.0 0.0 0 0 ? S Aug09 1:14 [kthreadd]
root 3 0.0 0.0 0 0 ? S Aug09 2:16 [ksoftirqd/0]
root 5 0.0 0.0 0 0 ? S< Aug09 0:00 [kworker/0:0H]
root 7 0.0 0.0 0 0 ? S Aug09 14:09 [rcu_sched]
root 8 0.0 0.0 0 0 ? S Aug09 0:00 [rcu_bh]
root 9 0.0 0.0 0 0 ? S Aug09 0:09 [migration/0]
root 10 0.0 0.0 0 0 ? S Aug09 0:08 [migration/1]
root 11 0.0 0.0 0 0 ? S Aug09 2:05 [ksoftirqd/1]
root 13 0.0 0.0 0 0 ? S< Aug09 0:00 [kworker/1:0H]
root 14 0.0 0.0 0 0 ? S Aug09 0:08 [migration/2]
root 15 0.0 0.0 0 0 ? S Aug09 2:12 [ksoftirqd/2]
root 17 0.0 0.0 0 0 ? S< Aug09 0:00 [kworker/2:0H]
root 18 0.0 0.0 0 0 ? S Aug09 0:10 [migration/3]
root 19 0.0 0.0 0 0 ? S Aug09 2:08 [ksoftirqd/3]
root 21 0.0 0.0 0 0 ? S< Aug09 0:00 [kworker/3:0H]
root 22 0.0 0.0 0 0 ? S< Aug09 0:00 [khelper]
root 23 0.0 0.0 0 0 ? S Aug09 0:00 [kdevtmpfs]
root 24 0.0 0.0 0 0 ? S< Aug09 0:00 [netns]
root 25 0.0 0.0 0 0 ? S< Aug09 0:00 [perf]
root 26 0.0 0.0 0 0 ? S< Aug09 0:00 [writeback]
root 27 0.0 0.0 0 0 ? SN Aug09 0:00 [khugepaged]
root 28 0.0 0.0 0 0 ? S< Aug09 0:00 [crypto]
root 29 0.0 0.0 0 0 ? S< Aug09 0:00 [kintegrityd]
root 30 0.0 0.0 0 0 ? S< Aug09 0:00 [bioset]
root 31 0.0 0.0 0 0 ? S< Aug09 0:00 [kblockd]
root 32 0.0 0.0 0 0 ? S< Aug09 0:00 [ata_sff]
root 33 0.0 0.0 0 0 ? S< Aug09 0:00 [devfreq_wq]
root 34 0.0 0.0 0 0 ? S Aug09 1:41 [kworker/0:1]
root 39 0.1 0.0 0 0 ? S Aug09 37:56 [kswapd0]
root 40 0.0 0.0 0 0 ? S Aug09 0:00 [fsnotify_mark]
root 47 0.0 0.0 0 0 ? S< Aug09 0:00 [kthrotld]
root 48 0.0 0.0 0 0 ? S< Aug09 0:00 [acpi_thermal_pm]
root 49 0.0 0.0 0 0 ? S< Aug09 0:00 [bioset]
root 50 0.0 0.0 0 0 ? S< Aug09 0:00 [deferwq]
root 107 0.0 0.0 0 0 ? S Aug09 1:25 [kworker/1:2]
root 366 0.0 0.5 83532 5516 ? Ss 20:17...
Also reported w/KDE directly @ https:/ /bugs.kde. org/show_ bug.cgi? id=233007