[Bug 341605] New: powersave refuses to hibernate the machine, pm-hibernate suceeds.
https://bugzilla.novell.com/show_bug.cgi?id=341605 Summary: powersave refuses to hibernate the machine, pm-hibernate suceeds. Product: openSUSE 10.3 Version: Final Platform: i686 OS/Version: openSUSE 10.3 Status: NEW Severity: Normal Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: robin.listas@telefonica.net QAContact: qa@suse.de Found By: --- Created an attachment (id=183326) --> (https://bugzilla.novell.com/attachment.cgi?id=183326) pm-suspend.log from a sucessfull hibernate from command line 'pm-hibernate' This machine is a P-IV desktop that has been correctly hibernating daily for generations of suse's at the brief touch of the power button; now, in 10.3, it complains and refuses to obey: Nov 4 02:36:12 nimrodel powersaved[5044]: WARNING (suspendToDisk:474) ACPI S3 state not available However, it hibernates just fine if I issue the command 'pm-hibernate' - therefore, this proves that the machine and the OS are perfectly capable of cooperation to hibernate the PC. If in Gnome Power Management Preferences (which I have to call from the command line, I can't find the menu entry for gnome-control), General tab, Actions, I change "when the power button is pressed" to "Hibernate", now when I press the power button the machine starts to hybernate (I get the screen blanker) but doesn't go further, it prompts for my user password. Later in the log, I find this: Nov 14 14:01:28 nimrodel gnome-power-manager: (cer) Hibernating computer because the power button has been pressed Nov 14 14:01:31 nimrodel gnome-power-manager: (cer) Resuming computer Nov 14 14:01:31 nimrodel gnome-power-manager: (cer) hibernate failed It prompts for my password, and then I see a half hidden window on the bottom right, tittled "Sleep Problem", that says "do not show this again" "Visit" - the rest is hidden by the plastic edge of the monitor; I mean, the message is off the screen. It doesn't say what the "problem" may be. However, if I press "Visit", firefox opens in http://people.freedesktop.org/~hughsient/quirk/, Hal Quirk Site. It mentions an "quirk-checker.sh" script, that I download and run: nimrodel:~ # quirk-checker.sh Checking your system... CRITICAL ERROR: No supported distro More info: nimrodel:~ # s2ram -n Machine unknown This machine can be identified by: sys_vendor = "NETWORK" sys_product = " " sys_version = " " bios_version = "" See http://suspend.sf.net/s2ram-support.html for details. If you report a problem, please include the complete output above. In kde the menu or buttons to suspend or hibernate are not present or grayed. It doesn't matter if I'm root. Who/what is lying to powersave to tell it that this machine can not hibernate? What/where can I change so that it does hibernate, as it did under 10.2, 10.1, 9.3, etc...? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605
Cyril Hrubis
https://bugzilla.novell.com/show_bug.cgi?id=341605#c1
Holger Macht
Nov 4 02:36:12 nimrodel powersaved[5044]: WARNING (suspendToDisk:474) ACPI S3 state not available
When does this message occur?
However, it hibernates just fine if I issue the command 'pm-hibernate' - therefore, this proves that the machine and the OS are perfectly capable of cooperation to hibernate the PC.
Please post the output of $ cat /sys/power/state
If in Gnome Power Management Preferences (which I have to call from the command line, I can't find the menu entry for gnome-control), General tab, Actions, I change "when the power button is pressed" to "Hibernate", now when I press the power button the machine starts to hybernate (I get the screen blanker) but doesn't go further, it prompts for my user password. Later in the log, I find this:
Nov 14 14:01:28 nimrodel gnome-power-manager: (cer) Hibernating computer because the power button has been pressed Nov 14 14:01:31 nimrodel gnome-power-manager: (cer) Resuming computer Nov 14 14:01:31 nimrodel gnome-power-manager: (cer) hibernate failed
It prompts for my password, and then I see a half hidden window on the bottom right, tittled "Sleep Problem", that says "do not show this again" "Visit" - the rest is hidden by the plastic edge of the monitor; I mean, the message is off the screen. It doesn't say what the "problem" may be.
Does 'powersave -U' work as user whenever it doesn't work with gnome-power-manager? Does it work when Hibernate got selected manually from the gnome-power-manager menu?
Who/what is lying to powersave to tell it that this machine can not hibernate?
Can you check if pmtools are installed? Note: The powersave daemon doesn't do any suspend anymore. We switched to pm-utils starting from 10.2. It's just that the powersave daemon can still trigger a suspend.
What/where can I change so that it does hibernate, as it did under 10.2, 10.1, 9.3, etc...?
Please also post the output of... $ lshal | grep can_hibernate -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c2
Carlos Robinson
(In reply to comment #0 from Carlos Robinson)
Nov 4 02:36:12 nimrodel powersaved[5044]: WARNING (suspendToDisk:474) ACPI S3 state not available
When does this message occur?
Not always. When I press the power switch once, if gnome is not active. I am getting (today, for instance) a related message when unfreezing after command pm-hibernate: Nov 19 11:33:36 nimrodel kernel: Restarting tasks ... done. Nov 19 11:33:36 nimrodel kernel: swsusp: Basic memory bitmaps freed Nov 19 11:33:36 nimrodel kernel: input: Power Button (FF) as /class/input/input63 Nov 19 11:33:36 nimrodel kernel: evdev: no more free evdev devices Nov 19 11:33:36 nimrodel kernel: input: failed to attach handler evdev to device input63, error: -23 Nov 19 11:33:36 nimrodel kernel: ACPI: Power Button (FF) [PWRF] Nov 19 11:33:36 nimrodel kernel: input: Power Button (CM) as /class/input/input64 Nov 19 11:33:36 nimrodel kernel: evdev: no more free evdev devices Nov 19 11:33:36 nimrodel kernel: input: failed to attach handler evdev to device input64, error: -23 Nov 19 11:33:36 nimrodel kernel: ACPI: Power Button (CM) [PWRB] Nov 19 11:33:36 nimrodel kernel: input: Sleep Button (CM) as /class/input/input65 Nov 19 11:33:36 nimrodel kernel: evdev: no more free evdev devices Nov 19 11:33:36 nimrodel kernel: input: failed to attach handler evdev to device input65, error: -23 Nov 19 11:33:36 nimrodel kernel: ACPI: Sleep Button (CM) [SLPB]
However, it hibernates just fine if I issue the command 'pm-hibernate' - therefore, this proves that the machine and the OS are perfectly capable of cooperation to hibernate the PC.
Please post the output of $ cat /sys/power/state
nimrodel:~ # cat /sys/power/state standby disk
Does 'powersave -U' work as user whenever it doesn't work with gnome-power-manager?
cer@nimrodel:~> powersave -U User is not allowed for hal-power-hibernate according to PolicyKit. /etc/PolicyKit/PolicyKit.conf is the default, almost empty file.
Does it work when Hibernate got selected manually from the gnome-power-manager menu?
Not even if the session belongs to root. I tried that from day one.
Who/what is lying to powersave to tell it that this machine can not hibernate?
Can you check if pmtools are installed?
nimrodel:~ # rpm -q pmtools pmtools-20061026-44 (investigating a little) (reading the readme) nimrodel:~/pmtools.notes # acpidump -t FACP -b | acpitbl Signature: FACP Length: 116 Revision: 0x01 Checksum: 0xa1 OEMID: MSISYS OEM Table ID: MSI ACPI OEM Revision: 0x42302e31 Creator ID: AWRD Creator Revision: 0x00000000 FIRMWARE_CTRL: 0x3fff0000 DSDT: 0x3fff30c0 INT_MODEL: 0x00 SCI_INT: 9 SMI_CMD: 0x000000b2 ACPI_ENABLE: 0xa1 ACPI_DISABLE: 0xa0 S4BIOS_REQ: 0x00 PM1a_EVT_BLK: 0x00004000 PM1b_EVT_BLK: 0x00000000 PM1a_CNT_BLK: 0x00004004 PM1b_CNT_BLK: 0x00000000 PM2_CNT_BLK: 0x00000000 PM_TMR_BLK: 0x00004008 GPE0_BLK: 0x0000402c GPE1_BLK: 0x00004028 PM1_EVT_LEN: 4 PM1_CNT_LEN: 2 PM2_CNT_LEN: 0 PM_TM_LEN: 4 GPE0_BLK_LEN: 4 GPE1_BLK_LEN: 4 GPE1_BASE: 16 P_LVL2_LAT: 90 P_LVL3_LAT: 900 FLUSH_SIZE: 0 FLUSH_STRIDE: 0 DUTY_OFFSET: 1 DUTY_WIDTH: 1 DAY_ALRM: 0x0d MON_ALRM: 0x00 CENTURY: 0x00 Flags: 0x000004a5
Note: The powersave daemon doesn't do any suspend anymore. We switched to pm-utils starting from 10.2. It's just that the powersave daemon can still trigger a suspend.
Ok. Just that in this machine, with OS 10.3, it doesn't trigger in any "normal" way, I have to manually call pm-hibernate.
What/where can I change so that it does hibernate, as it did under 10.2, 10.1, 9.3, etc...?
Please also post the output of... $ lshal | grep can_hibernate
nimrodel:~/pmtools.notes # lshal | grep can_hibernate power_management.can_hibernate = true (bool)
info.product = 'Computer' (string) info.subsystem = 'unknown' (string) power_management.acpi.linux.version = '20070126' (string) power_management.can_hibernate = true (bool) power_management.can_standby = true (bool) power_management.can_suspend = false (bool) power_management.can_suspend_hybrid = false (bool) power_management.can_suspend_to_disk = true (bool) power_management.can_suspend_to_ram = false (bool) power_management.is_powersave_set = false (bool) power_management.type = 'acpi' (string) smbios.bios.release_date = '08/28/2001' (string) smbios.bios.vendor = 'Award Software International, Inc.' (string) smbios.bios.version = '6.00 PG' (string) smbios.chassis.manufacturer = '' (string) smbios.chassis.type = 'Desktop' (string) smbios.system.manufacturer = 'NETWORK' (string) smbios.system.product = '' (string) smbios.system.serial = '' (string) smbios.system.uuid = 'Not Present' (string) smbios.system.version = '' (string) system.chassis.manufacturer = '' (string) system.chassis.type = 'Desktop' (string) system.firmware.release_date = '08/28/2001' (string) system.firmware.vendor = 'Award Software International, Inc.' (string) system.firmware.version = '6.00 PG' (string) system.formfactor = 'desktop' (string) system.hardware.primary_video.product = 272 (0x110) (int) system.hardware.primary_video.vendor = 4318 (0x10de) (int) system.hardware.product = '' (string) system.hardware.serial = '' (string) system.hardware.uuid = 'Not Present' (string) system.hardware.vendor = 'NETWORK' (string) system.hardware.version = '' (string) system.kernel.machine = 'i686' (string) system.kernel.name = 'Linux' (string) system.kernel.version = '2.6.22.12-0.1-cer' (string) system.product = ' ' (string) system.vendor = 'NETWORK' (string) Thanks for your interest :-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c3
Holger Macht
https://bugzilla.novell.com/show_bug.cgi?id=341605#c4
Carlos Robinson
The message about a not available S3 sleep mode (suspend to ram) is correct then. Suspend to disk, aka hibernate, is ACPI S4.
then, where is the correct place to tell the computer to hibernate when I press the power button? In /etc/powersave/events I have (and it worked in 10.2): EVENT_BUTTON_POWER="suspend_to_disk" but you say powersaved is not used, and I don't see anything usable in '/usr/lib/pm-utils' Where, then, do I configure that? At this moment, nothing at all happens if I press it; a few days back gnome tried to hibernate (and failed). But it is detected: nimrodel:~ # acpi_listen button/power PWRF 00000080 00000002
Can you please check if ConsoleKit is running (rcconsolekit status)?
nimrodel:~ # rcconsolekit status Checking for service ConsoleKit daemon running nimrodel:~ #
Did you have all available online updates installed?
Yes, all official updates are installed. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c5
Holger Macht
(In reply to comment #3 from Holger Macht)
The message about a not available S3 sleep mode (suspend to ram) is correct then. Suspend to disk, aka hibernate, is ACPI S4.
then, where is the correct place to tell the computer to hibernate when I press the power button?
It should be gnome-power-manager or kpowersave.
Does 'powersave -U' work as user whenever it doesn't work with
gnome-power-manager?
cer@nimrodel:~> powersave -U User is not allowed for hal-power-hibernate according to PolicyKit.
This seems like the root cause. Does powersave -U work as root?
/etc/PolicyKit/PolicyKit.conf is the default, almost empty file.
This (/usr/share/PolicyKit/policy/hal-power.policy) should be responsible.
Who/what is lying to powersave to tell it that this machine can not hibernate?
Nobody does. It just tells that _S3_ (s2ram) is not available, which is correct. Please also post the output of ck-list-sessions.
Nov 19 11:33:36 nimrodel kernel: Restarting tasks ... done. Nov 19 11:33:36 nimrodel kernel: swsusp: Basic memory bitmaps freed Nov 19 11:33:36 nimrodel kernel: input: Power Button (FF) as /class/input/input63 Nov 19 11:33:36 nimrodel kernel: evdev: no more free evdev devices Nov 19 11:33:36 nimrodel kernel: input: failed to attach handler evdev to device input63, error: -23 Nov 19 11:33:36 nimrodel kernel: ACPI: Power Button (FF) [PWRF] Nov 19 11:33:36 nimrodel kernel: input: Power Button (CM) as /class/input/input64 Nov 19 11:33:36 nimrodel kernel: evdev: no more free evdev devices Nov 19 11:33:36 nimrodel kernel: input: failed to attach handler evdev to device input64, error: -23 Nov 19 11:33:36 nimrodel kernel: ACPI: Power Button (CM) [PWRB] Nov 19 11:33:36 nimrodel kernel: input: Sleep Button (CM) as /class/input/input65 Nov 19 11:33:36 nimrodel kernel: evdev: no more free evdev devices Nov 19 11:33:36 nimrodel kernel: input: failed to attach handler evdev to device input65, error: -23 Nov 19 11:33:36 nimrodel kernel: ACPI: Sleep Button (CM) [SLPB]
Timo, have you seen this before? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c6
Carlos Robinson
(In reply to comment #4 from Carlos Robinson)
(In reply to comment #3 from Holger Macht)
then, where is the correct place to tell the computer to hibernate when I press the power button?
It should be gnome-power-manager or kpowersave.
But in runlevel 3 in 10.2 the hibernation could trigger with the power button. Surely this behavior has to be independent of the desktop. In any case, in gnome-power-manager the actions defined for both the power button and suspend are "hibernate". In KDE, I think the settings were grayed out (see below).
Does 'powersave -U' work as user whenever it doesn't work with
gnome-power-manager?
cer@nimrodel:~> powersave -U User is not allowed for hal-power-hibernate according to PolicyKit.
This seems like the root cause. Does powersave -U work as root?
Yes. I have a windomaker session started in console 8, and tried there. It triggers the same response as pm-hibernate, with the green splash screen with a progress bar. By the way, after aborting the hibernation (backspace) the mouse click in windowmaker stopped working. More. I have started a second session (in console 8) as **root**, using kde this time. I don't see any kpowersave icon in the task bar. I search for "kpower" or "power" in the control panel, there is none. I start "powersave" in a konsole, and I'm told it is already running. So I kill it, and restart it again: I get the prompt back, but nothing to be seen anywhere. Where is the kpowersave program, applet, or whatever it is, that I can find it and configure it? I'm root, so I'm allowed anything. Finally, the "leave" menu only offers logout and end. No suspend or hibernate anywhere.
/etc/PolicyKit/PolicyKit.conf is the default, almost empty file.
This (/usr/share/PolicyKit/policy/hal-power.policy) should be responsible.
It contains this:
<policy id="hal-power-hibernate">
<description>Hibernate the system</description>
<message>System policy prevents hibernating the system</message>
<defaults>
Who/what is lying to powersave to tell it that this machine can not hibernate?
Nobody does. It just tells that _S3_ (s2ram) is not available, which is correct.
Well, both gnome and kde refuse to hibernate, and the machine is perfectly capable of hibernating. I do it several times per day, by command line. Something somewhere is telling those programs not to hibernate.
Please also post the output of ck-list-sessions.
nimrodel:~ # ck-list-sessions nimrodel:~ # cer@nimrodel:~> ck-list-sessions cer@nimrodel:~> Nothing, no output. Where should I look? And there is no help at all: cer@nimrodel:~> pinfo ck-list-sessions Przemek's Info Viewer v0.6.9 Error: could not open info file, trying manual Error: No manual page found cer@nimrodel:~> ck-list-sessions --help Usage: ck-list-sessions [OPTION...] Help Options: -?, --help Show help options Application Options: -V, --version Version of this application And it doesn't say what those "options" may be... What? Now error console 10 has dissapeared? Can that be related to any of the above tests? :-O -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c7
--- Comment #7 from Carlos Robinson
(In reply to comment #0 from Carlos Robinson)
Nov 4 02:36:12 nimrodel powersaved[5044]: WARNING (suspendToDisk:474) ACPI S3 state not available
When does this message occur?
Confirmation: In runlevel 3, after pressing the power button - I tried right after a reboot: Nov 20 02:22:54 nimrodel powersaved[5002]: WARNING (suspendToDisk:474) ACPI S3 state not available Notice that it says suspend to disk (ie, hibernate) even if it also says acpi S3. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c8
--- Comment #8 from Carlos Robinson
What? Now error console 10 has dissapeared? Can that be related to any of the above tests? :-O
I don't know if it is related. I noticed that "xine" halted in mid initialization, no idea why, but it's not the first time, and seems to be related to testing hibernation. I had to exit the gnome session, but it also stopped without exiting completely. I had to kill it (ctrl-alt-backspace). Logged in again, but the initialization also stopped near the start (no message). As I said, not the first time, but tonight console 10 had also dissapeared. So I rebooted... it's the only cure I know, and I hate it. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c9
Holger Macht
Nov 20 02:22:54 nimrodel powersaved[5002]: WARNING (suspendToDisk:474) ACPI S3 state not available
Notice that it says suspend to disk (ie, hibernate) even if it also says acpi S3.
Oh, that's an evil bug. Thanks for the pointer. Can you please try the packages from ftp://ftp.suse.com/pub/people/hmacht/10.3/powersave/ Restart the powersave daemon after installing and check if the power button now works like expected. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c10
--- Comment #10 from Carlos Robinson
https://bugzilla.novell.com/show_bug.cgi?id=341605#c11
Carlos Robinson
(In reply to comment #7 from Carlos Robinson)
Nov 20 02:22:54 nimrodel powersaved[5002]: WARNING (suspendToDisk:474) ACPI S3 state not available
Notice that it says suspend to disk (ie, hibernate) even if it also says acpi S3.
Oh, that's an evil bug. Thanks for the pointer.
Can you please try the packages from ftp://ftp.suse.com/pub/people/hmacht/10.3/powersave/
Done. I have now: nimrodel:/xtr/cer/download/updates/people/hmacht/10.3/powersave/i386 # rpm -q -a | grep -i powersave wmpowersave-0.2.9-14 powersave-0.15.17-10.1 kpowersave-0.7.3-5 powersave-libs-0.15.17-10.1
Restart the powersave daemon after installing and check if the power button now works like expected.
Yes, it does! At least it does if gnome is closed, or if I'm in runlevel 3. However, if gnome is open, then it doesn't (see below more info). In text mode I see this in the kernel log (successful hibernate via power button): Nov 20 12:44:44 nimrodel kernel: swsusp: Basic memory bitmaps created Nov 20 13:43:50 nimrodel kernel: Stopping tasks ... done. : Shrinking memory... done (74546 pages freed) : Freed 298184 kbytes in 0.85 seconds (350.80 MB/s) : Suspending console(s) : pnp: Device 00:0e disabled. : pnp: Device 00:0d disabled. : pnp: Device 00:09 disabled. : pnp: Device 00:08 disabled. : ACPI: PCI interrupt for device 0000:02:02.2 disabled : ACPI: PCI interrupt for device 0000:02:02.1 disabled : ACPI: PCI interrupt for device 0000:02:02.0 disabled : ACPI: PCI interrupt for device 0000:00:1f.5 disabled : swsusp: critical section: : swsusp: Need to copy 115029 pages : Intel machine check architecture supported. : Intel machine check reporting enabled on CPU#0. : CPU0: Intel P4/Xeon Extended MCE MSRs (12) available : CPU0: Thermal monitoring enabled : PCI: Setting latency timer of device 0000:00:1e.0 to 64 : PM: Writing back config space on device 0000:00:1f.5 at offset 1 (was 2800005, writing 2800001) : ACPI: PCI Interrupt 0000:00:1f.5[B] -> GSI 17 (level, low) -> IRQ 19 : PCI: Setting latency timer of device 0000:00:1f.5 to 64 : eth0: link up, 100Mbps, full-duplex, lpa 0x45E1 : ACPI: PCI Interrupt 0000:02:02.0[A] -> GSI 18 (level, low) -> IRQ 16 : usb usb1: root hub lost power or was reset : ACPI: PCI Interrupt 0000:02:02.1[B] -> GSI 19 (level, low) -> IRQ 18 : usb usb3: root hub lost power or was reset : ACPI: PCI Interrupt 0000:02:02.2[C] -> GSI 16 (level, low) -> IRQ 17 : usb usb2: root hub lost power or was reset : pnp: Device 00:08 activated. : pnp: Device 00:09 activated. : pnp: Failed to activate device 00:0b. : pnp: Failed to activate device 00:0c. : pnp: Device 00:0d activated. : pnp: Device 00:0e activated. : hda: selected mode 0x45 : hdb: selected mode 0x45 : hdc: selected mode 0x42 : hdd: selected mode 0x45 : Restarting tasks ... done. : swsusp: Basic memory bitmaps freed Nov 20 13:43:51 nimrodel kernel: input: Power Button (FF) as /class/input/input9 : ACPI: Power Button (FF) [PWRF] : input: Power Button (CM) as /class/input/input10 : ACPI: Power Button (CM) [PWRB] : input: Sleep Button (CM) as /class/input/input11 : ACPI: Sleep Button (CM) [SLPB] Now this is curious. After a second sucesful attempt (in runlevel 3), I notice that the numbers increase: Nov 20 13:44:50 nimrodel kernel: input: Power Button (FF) as /class/input/input12 kernel: ACPI: Power Button (FF) [PWRF] kernel: input: Power Button (CM) as /class/input/input13 kernel: ACPI: Power Button (CM) [PWRB] kernel: input: Sleep Button (CM) as /class/input/input14 kernel: ACPI: Sleep Button (CM) [SLPB] Is this normal? I also tried again in gnome, as user: doesn't work. I get the screen saver, then I'm asked for my password, and I get what you can see in the next attachment. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c12
--- Comment #12 from Carlos Robinson
https://bugzilla.novell.com/show_bug.cgi?id=341605#c13
--- Comment #13 from Carlos Robinson
I also tried again in gnome, as user: doesn't work. I get the screen saver, then I'm asked for my password, and I get what you can see in the next attachment.
Forgot to mention: as you can see in the screen capture, the error box is clipped at the right-bottom end of the screen. No, I did not move it, nor can I (I tried). The link works. Is that a different bug? I can submit it if you want. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c14
Holger Macht
(In reply to comment #9 from Holger Macht)
Restart the powersave daemon after installing and check if the power button now works like expected.
Yes, it does! At least it does if gnome is closed, or if I'm in runlevel 3.
Ok, good. So the first issue is fixed. (In reply to comment #11 from Carlos Robinson)
Nov 20 13:44:50 nimrodel kernel: input: Power Button (FF) as /class/input/input12 kernel: ACPI: Power Button (FF) [PWRF] kernel: input: Power Button (CM) as /class/input/input13 kernel: ACPI: Power Button (CM) [PWRB] kernel: input: Sleep Button (CM) as /class/input/input14 kernel: ACPI: Sleep Button (CM) [SLPB]
Is this normal?
Yes.
Please also post the output of ck-list-sessions.
nimrodel:~ # ck-list-sessions nimrodel:~ #
cer@nimrodel:~> ck-list-sessions cer@nimrodel:~>
Nothing, no output. Where should I look?
So this seems to be the culprit. This actually should be fixed along with the last dbus update, but unfortunately seems not to. Please do: log out rcxdm stop rconsolekit restart rcxdm start log in now ck-list-sessions should list your user session and hopefully it works. (In reply to comment #13 from Carlos Robinson)
(In reply to comment #11 from Carlos Robinson) Forgot to mention: as you can see in the screen capture, the error box is clipped at the right-bottom end of the screen. No, I did not move it, nor can I (I tried). The link works.
Is that a different bug? I can submit it if you want.
Yes, please. Assignt to rodrigo@novell.com, taking me into CC. Please explicitly state in the new bug that you do _not_ complain about sleep not working, but just about the window drifting out of the screen. Thanks. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c15
Carlos Robinson
(In reply to comment #11 from Carlos Robinson)
So this seems to be the culprit. This actually should be fixed along with the last dbus update, but unfortunately seems not to.
Please do:
log out rcxdm stop rconsolekit restart rcxdm start log in
now ck-list-sessions should list your user session and hopefully it works.
Mixed results... First I tried ck-list-sessions again, got this: cer@nimrodel:~> cat ck-list-sessions Session1: uid = '0' realname = 'root' seat = 'Seat1' session-type = '' active = FALSE x11-display = '' x11-display-device = '' display-device = '/dev/tty1' remote-host-name = '' is-local = TRUE on-since = '2007-11-20T01:22:37Z' idle-since-hint = '2007-11-20T12:45:41Z' which is funny, not consistent with yesterday's results. Then I logged out, switched to runlevel 3, restarted rcconsolekit, switched to runlevel 5, logged back in, tried, and got this: cer@nimrodel:~> ck-list-sessions cer@nimrodel:~> I suspended via pm-hibernate (as root), came back, and tried again: cer@nimrodel:~> ck-list-sessions cer@nimrodel:~> The first results above I had saved to a file before login out, to compare what I got with results after restarting consolekit. Those results show that I'm logged in as root in tty1, which is true, but I'm also logged in as cer in tty2, and there is a graphical gnome session as cer, with dozens of terminals open (both gnome terminal and xterm). It doesn't matter if I execute that ck-... as user or root.
(In reply to comment #13 from Carlos Robinson)
(In reply to comment #11 from Carlos Robinson) Forgot to mention: as you can see in the screen capture, the error box is clipped at the right-bottom end of the screen. No, I did not move it, nor can I (I tried). The link works.
Is that a different bug? I can submit it if you want.
Yes, please. Assignt to rodrigo@novell.com, taking me into CC. Please explicitly state in the new bug that you do _not_ complain about sleep not working, but just about the window drifting out of the screen. Thanks.
Done: Bug 343480 -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c16
Holger Macht
https://bugzilla.novell.com/show_bug.cgi?id=341605#c17
--- Comment #17 from Carlos Robinson
https://bugzilla.novell.com/show_bug.cgi?id=341605#c18
--- Comment #18 from Holger Macht
https://bugzilla.novell.com/show_bug.cgi?id=341605#c19
--- Comment #19 from Carlos Robinson
I do not know if this is supposed to work. Please login via gdm or kde, the standard way (please try with your new user as the only one) first and see if that helps.
Yes, that's what I was going to do and did (I had to close firefox to do so). There is no difference. The new user X11 session, as the only X11 session active doesn't show in ck-list..., but the text sessions do. I tried KDE, and the exit button doesn't offer hybernate or suspend, only logout. Didn't try gnome, but if I can do so. I'll have to exit this user first. Hold on. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c20
--- Comment #20 from Carlos Robinson
The new user X11 session, as the only X11 session active doesn't show in ck-list..., but the text sessions do.
I tried KDE, and the exit button doesn't offer hybernate or suspend, only logout. Didn't try gnome, but if I can do so. I'll have to exit this user first.
Hold on.
Ok, same thing. The new user (cer3), as the only user logged in X11, gnome, doesn't show in ck-list... It is logged in text mode. Should I try exiting that? Hold on again... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c21
--- Comment #21 from Holger Macht
https://bugzilla.novell.com/show_bug.cgi?id=341605#c22
--- Comment #22 from Carlos Robinson
Ok, same thing. The new user (cer3), as the only user logged in X11, gnome, doesn't show in ck-list...
It is logged in text mode. Should I try exiting that?
Hold on again...
Same thing: Only the text sessions do show in ck-list-sessions. If I exit all text sessions, the output of ck-list-sesssions is empty. The only other thing I can think of, is that I'm using wdm, not kdm nor gdm (I want my login program to be agnostic). If you think that may be related, I have another partition with a 10.3 system installed fresh, not upgraded (the one I used for factory testing, which is currently 10.3; I haven't updated to factory that one). That system uses kdm, and can not suspend automatically, only manually, but I haven't tried ck-list... there. (In reply to comment #21 from Holger Macht) Ok, will try gdm and kdm. Hold on... -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c23
Carlos Robinson
(In reply to comment #21 from Holger Macht)
Ok, will try gdm and kdm. Hold on...
Bingo, that was it! Uau! :-))) I switched to kdm instead of wdm. I logged in as my normal user, and: cer@nimrodel:~> ck-list-sessions Session1: uid = '500' realname = 'Carlos E. Robinson Mayordomo' seat = 'Seat1' session-type = '' active = TRUE x11-display = ':0' x11-display-device = '/dev/tty7' display-device = '' remote-host-name = '' is-local = TRUE on-since = '2007-11-27T14:24:22Z' I then opened gnome-power-manager, clicked on hibernate and it did! I aborted, then touched the main power button, and it also hibernated! (I aborted before completing). So, the culprit all the time has been wdm - I assure you it worked in 10.2 and before, so there is a bug in there. Shall I open a new bugzilla against wdm, or do you do it? Or is it ck-list-sessions the culprit? I guess it should get the info regardless of the method used to log in. Now I'm going off to a delayed lunch - all this reporting ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c24
Holger Macht
(In reply to comment #22 from Carlos Robinson)
(In reply to comment #21 from Holger Macht)
Ok, will try gdm and kdm. Hold on...
Bingo, that was it!
Uau! :-)))
Great! ;)
So, the culprit all the time has been wdm - I assure you it worked in 10.2 and before, so there is a bug in there. Shall I open a new bugzilla against wdm, or do you do it?
We did not have ConsoleKit support in 10.2. I'm reassigning this bug. I'm not sure what needs to be done in a login manager to get support for ConsoleKit, but I doubt it would mean much work. Rodrigo, maybe you can answer this question for the wdm maintainer? -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c25
--- Comment #25 from Carlos Robinson
We did not have ConsoleKit support in 10.2.
I'm reassigning this bug. I'm not sure what needs to be done in a login manager to get support for ConsoleKit, but I doubt it would mean much work.
I'm wondering what should happen if nobody is logged in locally? For instance, if pressing the power button will hibernate. In runlevel 3, it works (Comment #11). I'll try again some other time, I have some "real things" to do now ;-) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=341605#c26
Rodrigo Moya
https://bugzilla.novell.com/show_bug.cgi?id=341605#c27
--- Comment #27 from Vladimir Nadvornik
https://bugzilla.novell.com/show_bug.cgi?id=341605
Vladimir Nadvornik
participants (1)
-
bugzilla_noreply＠novell.com