You are not logged in.

#1 2012-11-28 16:37:55

west88
Member
Registered: 2012-11-28
Posts: 3

Suspending to RAM in gnome

Hi all,

This is my first experience with Arch and all has been well expect for suspending to ram via gnome-power-manager. pm-suspend works perfectly fine and writes to /var/log/pm-suspend.log as expected, but when i suspend via gnome (or the sleep button on my keyboard), the PC goes to sleep just fine, but it is frozen when I attempt to resume (black screen, can't blindly switch to another vterm, keyboard doesn't seem to be working).

From reading the various wiki's, my understanding was that gnome-power-manager should be using pm-suspend behind the scenes by sending a message to upower over dbus. This doesn't seem to be the case as no records are written to /var/log/pm-suspend.log when i suspend through gnome.

I'm using the stock arch kernel w/ the proprietary amd drivers and KMS disabled (nomodeset). Again, everything works fine when pm-suspend is called in a vterm or through gnome console.

Any insight/help would be greatly appreciated, thanks

Offline

#2 2012-11-28 16:47:22

Ramses de Norre
Member
From: Leuven - Belgium
Registered: 2007-03-27
Posts: 1,289

Re: Suspending to RAM in gnome

I think gnome uses logind now, doesn't it?
Anything suspend-related in journalctl?

Offline

#3 2012-11-28 18:39:30

teateawhy
Member
From: GER
Registered: 2012-03-05
Posts: 1,006
Website

Re: Suspending to RAM in gnome

Try if you can suspend with systemd. # systemctl suspend

Offline

#4 2012-11-29 05:18:44

west88
Member
Registered: 2012-11-28
Posts: 3

Re: Suspending to RAM in gnome

systemctl suspend has the same behaviour, definately the cause. Looked in journalctl but there is nothing related to suspend in the that i can see:

-- Reboot --
Nov 28 20:58:05 mark-desktop pulseaudio[706]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file
Nov 28 20:58:05 mark-desktop gnome-session[642]: Gtk-WARNING: Theme parsing error: gtk-apps.css:67:50: Error opening file: No such file or directory
Nov 28 20:58:07 mark-desktop pulseaudio[732]: [pulseaudio] pid.c: Daemon already running.
Nov 28 20:58:07 mark-desktop goa[780]: goa-daemon version 3.6.2 starting [main.c:112, main()]
Nov 28 20:58:17 mark-desktop gnome-keyring-daemon[640]: keyring alias directory: /home/mark/.local/share/keyrings
-- Reboot --
Nov 28 21:09:46 mark-desktop pulseaudio[688]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file
Nov 28 21:09:47 mark-desktop gnome-session[624]: Gtk-WARNING: Theme parsing error: gtk-apps.css:67:50: Error opening file: No such file or directory
Nov 28 21:09:49 mark-desktop goa[761]: goa-daemon version 3.6.2 starting [main.c:112, main()]
Nov 28 21:11:51 mark-desktop gnome-keyring-daemon[622]: keyring alias directory: /home/mark/.local/share/keyrings


The reboot in the middle of the 28th was because i could not successfully return from suspend and had to reset. Know where to go from here?

Offline

#5 2012-11-30 18:04:32

west88
Member
Registered: 2012-11-28
Posts: 3

Re: Suspending to RAM in gnome

Can't seem to find any resources on how to further diagnose this problem, anybody have any suggestions? Is it possible to switch the upower backend from systemd-suspend to pm-suspend?

Offline

Board footer

Powered by FluxBB