Gnome crash when on battery

Agamemnon · 2012-01-30 19:01:17

Hi!
I have a weird problem on my laptop.
When it's plugged on AC, everything is ok, but when it is on battery, Gnome3 crash quickly into "Oops screen".
My laptop is a core2duo with wifi iwlagn, laptop-mode tool activated when unplugged, systemd, and all packages up to date.
Any idea?

quasifilmie · 2012-01-30 19:49:30

Sounds like a problem with the video card and power management. Any relevant logs. xsession-errors?

Agamemnon · 2012-01-31 09:54:37

My video card driver is R600. I have set the power on "mid" by a rule in rc.local. It's strange because before, I never had any problem with power managment.

Here is my xsessions-errors.log:

/etc/gdm/Xsession: Beginning session setup...
localuser:alex being added to access control list
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- gnome-session
GNOME_KEYRING_CONTROL=/tmp/keyring-lvBqXz
GPG_AGENT_INFO=/tmp/keyring-lvBqXz/gpg:0:1
GNOME_KEYRING_PID=1007
GNOME_KEYRING_CONTROL=/tmp/keyring-lvBqXz
GPG_AGENT_INFO=/tmp/keyring-lvBqXz/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-lvBqXz/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-lvBqXz
GPG_AGENT_INFO=/tmp/keyring-lvBqXz/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-lvBqXz/ssh
GNOME_KEYRING_CONTROL=/tmp/keyring-lvBqXz
GPG_AGENT_INFO=/tmp/keyring-lvBqXz/gpg:0:1
SSH_AUTH_SOCK=/tmp/keyring-lvBqXz/ssh
(gnome-settings-daemon:1003): color-plugin-WARNING **: failed to connect to colord: Erreur lors de l'appel de StartServiceByName pour org.freedesktop.ColorManager : GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit colord.service failed to load: No such file or directory. See system logs and 'systemctl status colord.service' for details.
Failed to play sound: File or data not found
(gnome-settings-daemon:1003): PackageKit-WARNING **: failed to get properties: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(gnome-settings-daemon:1003): PackageKit-WARNING **: failed: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(gnome-settings-daemon:1003): updates-plugin-WARNING **: could not get properties
(gnome-settings-daemon:1003): PackageKit-WARNING **: failed to set proxy: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(gnome-settings-daemon:1003): PackageKit-WARNING **: Failed to get transaction list: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(gnome-settings-daemon:1003): PackageKit-WARNING **: failed to set root: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(gnome-settings-daemon:1003): updates-plugin-WARNING **: failed to set proxies: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
(gnome-settings-daemon:1003): updates-plugin-WARNING **: failed to set install root: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
** Message: applet now removed from the notification area
Initializing tracker-miner-fs...
Initializing tracker-store...
Tracker-Message: Setting up monitor for changes to config file:'/home/alex/.config/tracker/tracker-store.cfg'
Tracker-Message: Setting up monitor for changes to config file:'/home/alex/.config/tracker/tracker-miner-fs.cfg'
(gnome-shell:1122): folks-DEBUG: individual-aggregator.vala:310: Setting primary store IDs to defaults.
Tracker-Message: Setting up monitor for changes to config file:'/home/alex/.config/tracker/tracker-store.cfg'
Starting log:
File:'/home/alex/.local/share/tracker/tracker-store.log'
Starting log:
File:'/home/alex/.local/share/tracker/tracker-miner-fs.log'
(gnome-shell:1122): folks-DEBUG: individual-aggregator.vala:338: Primary store IDs are 'eds' and 'system'.
JS LOG: GNOME Shell started at Tue Jan 31 2012 10:36:47 GMT+0100 (CET)
(tracker-store:1149): Tracker-CRITICAL **: D-Bus service name:'org.freedesktop.Tracker1' is already taken, perhaps the daemon is already running?
** Message: applet now embedded in the notification area
JS ERROR: !!! Exception was: TypeError: Shell.util_icon_from_string is not a function
JS ERROR: !!! lineNumber = '1300'
JS ERROR: !!! fileName = '"/usr/share/gnome-shell/js/ui/telepathyClient.js"'
JS ERROR: !!! stack = '"()@/usr/share/gnome-shell/js/ui/telepathyClient.js:1300
("Erreur de connexion","gtk-dialog-error")@/usr/share/gnome-shell/js/ui/telepathyClient.js:1281
MultiNotificationSource("Erreur de connexion","gtk-dialog-error")@/usr/share/gnome-shell/js/ui/telepathyClient.js:1271
()@/usr/share/gnome-shell/js/ui/telepathyClient.js:474
([object _private_TelepathyGLib_Account],[object _private_GLib_ParamSpec])@/usr/share/gnome-shell/js/ui/telepathyClient.js:461
"'
JS ERROR: !!! message = '"Shell.util_icon_from_string is not a function"'
(nautilus:1240): Tracker-DEBUG: Initializing tracker-tags extension

(tracker-miner-fs:1150): Tracker-WARNING **: Couldn't properly parse desktop file 'file:///usr/share/applications/brasero-nautilus.desktop': 'Desktop file doesn't contain type'
Could not check applicable rules for http://google.fr/
Could not check applicable rules for http://www.google.fr/
Could not check applicable rules for http://www.google.fr/
Error: found duplicate rule name GoogleMaps in file /home/alex/.mozilla/firefox/kwy0onl1.default/extensions/https-everywhere@eff.org/chrome/content/rules/GoogleMaps.xml~HEAD
gnome-session[975]: WARNING: Application 'gnome-settings-daemon.desktop' killed by signal
(gnome-settings-daemon:4879): color-plugin-WARNING **: failed to connect to colord: Erreur lors de l'appel de StartServiceByName pour org.freedesktop.ColorManager : GDBus.Error:org.freedesktop.systemd1.LoadFailed: Unit colord.service failed to load: No such file or directory. See system logs and 'systemctl status colord.service' for details.

Agamemnon · 2012-01-31 10:02:29

Mhh.. Don't know if it's usefull but after a crash, I get this in xsession-error:

JS ERROR: !!! message = '"Shell.util_icon_from_string is not a function"'
Avertissement du gestionnaire de fenêtres : CurrentTime used to choose focus window; focus window may not be correct.
Avertissement du gestionnaire de fenêtres : Got a request to focus the no_focus_window with a timestamp of 0. This shouldn't happen!
** Message: applet now embedded in the notification area

andesho91 · 2012-02-01 16:12:41

Hi, I seem to be having an issue with GNOME along these lines, where basically GNOME crashes after about 20 minutes. How do I find the xsession-errors?

Agamemnon · 2012-02-02 07:41:41

andesho91 wrote:

Hi, I seem to be having an issue with GNOME along these lines, where basically GNOME crashes after about 20 minutes. How do I find the xsession-errors?

xsession-errors is a hiden file which is in your user directory. Basically ~/.xsession-errors

Luminary · 2012-02-15 09:27:07

Hi, I've been having this problem for quite a while now. It exists in Gnome, GDM, and Cinnamon (what I actually use). I'm not sure how to go about fixing it, but it also happened in Ubuntu (to a lesser extent).

I'll explain the process.
1. Unplug charger from laptop.
2. (usually happens) Within a few minutes gtk applications go to fallback mode. [This is all that happened in Ubuntu as far as I can tell]
3. Within a few more minutes Gnome/Cinnamon crashes to the "oops" screen.
4. If left on GDM, the background of that will be replaced with the oops screen as well.

I'll replicate it tomorrow, and try to post some logs to see if you guys can help me.

andesho91 · 2012-02-15 10:08:04

Hmm... for me, GNOME3 would just slow down to the point until it became unusable. Since I last posted, I reinstalled GNOME3, whacked on Cinammon and then hacked a load out of my Linux Mint Katya installation from the extensions, themes and so on from there and now it seems to be running fine (unless I activate the Smart Overview extension, but that is no matter).

Luminary · 2012-02-16 03:10:18

I'm not sure how to fix it.

I looked at the xsession-errors file after making it happen, at the bottom, basically everything I had running returned a "this resource is not currently available" error, or something like that.

Agamemnon · 2012-02-26 11:06:00

Mhh.. It's strange...
I've tested many stuff but it always crash...
I think that it crash when Gnome try to deactivate the screen or decrease the screen light to save battery life.
But I don't know how to tweak this...

Agamemnon · 2012-02-26 11:45:05

Mhh.. I've found how to disable dpms and now it works like a charm... I've posted a bug report now that I know what is the cause of the crash.

Arch Linux

#1 2012-01-30 19:01:17

Gnome crash when on battery

#2 2012-01-30 19:49:30

Re: Gnome crash when on battery

#3 2012-01-31 09:54:37

Re: Gnome crash when on battery

#4 2012-01-31 10:02:29

Re: Gnome crash when on battery

#5 2012-02-01 16:12:41

Re: Gnome crash when on battery

#6 2012-02-02 07:41:41

Re: Gnome crash when on battery

#7 2012-02-15 09:27:07

Re: Gnome crash when on battery

#8 2012-02-15 10:08:04

Re: Gnome crash when on battery

#9 2012-02-16 03:10:18

Re: Gnome crash when on battery

#10 2012-02-26 11:06:00

Re: Gnome crash when on battery

#11 2012-02-26 11:45:05

Re: Gnome crash when on battery

Board footer