Bug 9594

Summary:	hald reports hibernation failure
Product:	hal	Reporter:	Martin Pitt <martin.pitt>
Component:	hald	Assignee:	David Zeuthen (not reading bugmail) <zeuthen>
Status:	RESOLVED INVALID	QA Contact:
Severity:	normal
Priority:	high
Version:	unspecified
Hardware:	x86 (IA32)
OS:	Linux (All)
URL:	https://launchpad.net/ubuntu/+source/hal/+bug/51225
Whiteboard:
i915 platform:		i915 features:

Description Martin Pitt 2007-01-10 04:10:37 UTC

In the Ubuntu bug report, gnome-power-manager checks the result of calling hal's
Hibernate function which reports failure for that user. It does not seem to have
an obvious ill effect, however, the debug log [1] shows some errors between
hibernate and resume.

[1] http://librarian.launchpad.net/4223555/hal.log

Comment 1 Danny Kukawka 2007-02-09 06:35:10 UTC

Which error do you mean exactly?

Comment 2 Martin Pitt 2007-04-17 05:05:39 UTC

Hibernation process seems to start at 00:30:43.687. Then I see

  21:12:56.363 [E] hald_runner.c:320: Malformed or unexpected reply message

I also see some 'Permission denied: Rescan: not privileged' and 'probe-input.c:181: Error: EVIOCGID failed: Inappropriate ioctl for device
' messages, but they might be unrelated, since they happen before as well.

Comment 3 Danny Kukawka 2008-03-05 01:07:10 UTC

Is this problem still there?

Comment 4 Martin Pitt 2008-03-05 23:57:56 UTC

I asked the original reporters to test the current git snapshot packages on the Ubuntu development release. A week ago it was confirmed to still apply to Ubuntu 7.10 (with hal 0.5.9.1). I'll report back here if there is some reply to the Ubuntu bug.

Comment 5 Maciej Piechotka 2009-06-15 08:25:33 UTC

hal 0.5.12 rc1, gentoo, ususpend - gpm reports hibernation error despite full sucess. No error message in logs.

Comment 6 Martin Pitt 2009-07-12 23:45:01 UTC

Closing. This is stale, and irrelevant in the devkit-power world anyway.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.