Gentoo Forums
Gentoo Forums
Gentoo Forums
Quick Search: in
[Solved] Gnome 3.8 deadlocks
View unanswered posts
View posts from last 24 hours
View posts from last 7 days

 
Reply to topic    Gentoo Forums Forum Index Desktop Environments
View previous topic :: View next topic  
Author Message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 490
Location: "Hemp"shire, UK

PostPosted: Sun Dec 08, 2013 9:21 pm    Post subject: [Solved] Gnome 3.8 deadlocks Reply with quote

From time to time, Gnome 3.8 will deadlock, and on examination of the logs, I see this:

Dec 08 17:47:54 silicon gnome-session[19237]: (gnome-settings-daemon:19289): dconf-CRITICAL **: unable to create file '/run/user/1000/dconf/user': Permission denied. dconf will not work properly.

Lots and lots of those.

When that happens Gnome 3.8 deadlocks, and I have to switch to the text console and kill X. Then delete the /run/user/1000/dconf/user file and start X again.

Does anyone knows why, and if there is a resolution for this issue?

Thanks
Alex
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.


Last edited by alexbuell on Thu Dec 12, 2013 10:04 pm; edited 1 time in total
Back to top
View user's profile Send private message
ulenrich
Veteran
Veteran


Joined: 10 Oct 2010
Posts: 1480

PostPosted: Mon Dec 09, 2013 11:26 pm    Post subject: Reply with quote

As Guru you should have been able to have look at permissions before you removed
/run/user/1000/dconf/user file
If you had such Permission denied error.
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 490
Location: "Hemp"shire, UK

PostPosted: Tue Dec 10, 2013 8:57 pm    Post subject: Reply with quote

ulenrich wrote:
As Guru you should have been able to have look at permissions before you removed
/run/user/1000/dconf/user file
If you had such Permission denied error.


I did just that, it showed the file as owned by root:root. I changed it back to alex:alex, and things started working again. Within a next few mins, everything hung again.

So I did this:

watch -n 60 chown alex:alex /run/user/1000/dconf/user

Basically changes the file's ownership back to alex:alex every 60 seconds/ Works quite nicely but why does this happens? Is it a bug I should report?
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
comprookie2000
Retired Dev
Retired Dev


Joined: 25 Jul 2004
Posts: 925
Location: Sun City Center, Florida

PostPosted: Tue Dec 10, 2013 9:16 pm    Post subject: Reply with quote

Whats the output of;
Code:

# systemctl status dbus

_________________
http://dev.gentoo.org/~dabbott/
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 490
Location: "Hemp"shire, UK

PostPosted: Tue Dec 10, 2013 10:02 pm    Post subject: Reply with quote

comprookie2000 wrote:
Whats the output of;
Code:

# systemctl status dbus


Here it is:
Code:

 # systemctl status dbus
dbus.service - D-Bus System Message Bus
   Loaded: loaded (/usr/lib64/systemd/system/dbus.service; static)
   Active: active (running) since Tue 2013-12-10 18:58:24 GMT; 3h 3min ago
 Main PID: 16443 (dbus-daemon)
   CGroup: /system.slice/dbus.service
           ├─16443 /usr/bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation
           ├─16546 /usr/sbin/console-kit-daemon --no-daemon
           ├─16862 /usr/libexec/udisks-daemon
           └─16865 udisks-daemon: not polling any devices

Dec 10 21:29:43 silicon dbus-daemon[16443]: helper(pid 21447): completed with exit code 0
Dec 10 21:29:43 silicon dbus-daemon[16443]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:12.0/ata4/host3/targe...ck/sdb
Dec 10 21:59:43 silicon dbus-daemon[16443]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:12.0/ata3/ho...ck/sda
Dec 10 21:59:43 silicon dbus-daemon[16443]: helper(pid 21520): launched job udisks-helper-ata-smart-collect on /dev/sda
Dec 10 21:59:43 silicon dbus-daemon[16443]: **** Refreshing ATA SMART data for /sys/devices/pci0000:00/0000:00:12.0/ata4/ho...ck/sdb
Dec 10 21:59:43 silicon dbus-daemon[16443]: helper(pid 21521): launched job udisks-helper-ata-smart-collect on /dev/sdb
Dec 10 21:59:43 silicon dbus-daemon[16443]: helper(pid 21521): completed with exit code 0
Dec 10 21:59:43 silicon dbus-daemon[16443]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:12.0/ata4/host3/targe...ck/sdb
Dec 10 21:59:43 silicon dbus-daemon[16443]: helper(pid 21520): completed with exit code 0
Dec 10 21:59:43 silicon dbus-daemon[16443]: **** EMITTING CHANGED for /sys/devices/pci0000:00/0000:00:12.0/ata3/host2/targe...ck/sda
Hint: Some lines were ellipsized, use -l to show in full.

_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
ulenrich
Veteran
Veteran


Joined: 10 Oct 2010
Posts: 1480

PostPosted: Tue Dec 10, 2013 10:13 pm    Post subject: Reply with quote

alexbuell wrote:
ulenrich wrote:
permissions before you removed
/run/user/1000/dconf/user file
If you had such Permission denied error.


I did just that, it showed the file as owned by root:root. I changed it back to alex:alex, and things started working again. Within a next few mins, everything hung again.

So I did this:

watch -n 60 chown alex:alex /run/user/1000/dconf/user

Basically changes the file's ownership back to alex:alex every 60 seconds/ Works quite nicely but why does this happens? Is it a bug I should report?

Look at your
/usr/lib/tmpfiles.d/systemd.conf
Code:
#  This file is part of systemd.
#
#  systemd is free software; you can redistribute it and/or modify it
#  under the terms of the GNU Lesser General Public License as published by
#  the Free Software Foundation; either version 2.1 of the License, or
#  (at your option) any later version.

# See tmpfiles.d(5) for details

d /run/user 0755 root root ~10d
F /run/utmp 0664 root utmp -

f /var/log/wtmp 0664 root utmp -
f /var/log/btmp 0600 root utmp -

d /var/cache/man - - - 30d

d /run/systemd/ask-password 0755 root root -
d /run/systemd/seats 0755 root root -
d /run/systemd/sessions 0755 root root -
d /run/systemd/users 0755 root root -
d /run/systemd/machines 0755 root root -
d /run/systemd/shutdown 0755 root root -

F /run/nologin 0644 - - - "System is booting up. See pam_nologin(8)"

m /var/log/journal 2755 root systemd-journal - -
m /var/log/journal/%m 2755 root systemd-journal - -
m /run/log/journal 2755 root systemd-journal - -

If there is no error in format, then seach for errors regarding tmpfiles as root user in
journalctl -b
Back to top
View user's profile Send private message
comprookie2000
Retired Dev
Retired Dev


Joined: 25 Jul 2004
Posts: 925
Location: Sun City Center, Florida

PostPosted: Tue Dec 10, 2013 10:43 pm    Post subject: Reply with quote

Hi Alex,
This looks like the bug, don't know why I don't get it here myself;
https://bugzilla.redhat.com/show_bug.cgi?id=753882#c56

I am not using consolkit, but I don't think that has anything to do with it anyway.
Code:

$ echo $XDG_RUNTIME_DIR
/run/user/1000

# echo $XDG_RUNTIME_DIR
/run/user/1000


[ebuild R ] gnome-base/gnome-3.8.0-r1:2.0 USE="bluetooth cdr classic cups extras -accessibility -flashback" 0 kB
[ebuild R ] sys-apps/systemd-208-r2:0/1 USE="acl filecaps firmware-loader gudev introspection kmod pam policykit python tcpd -audit -cryptsetup -doc -gcrypt -http -lzma -qrcode (-selinux) {-test} -vanilla -xattr" ABI_X86="(64) (-32) (-x32)" PYTHON_SINGLE_TARGET="python2_7" PYTHON_TARGETS="python2_7" 0 kB

Code:

amd64testbox ~ # ls -l /run/user/1000/dconf/user
-rw------- 1 david users 2 Dec 10 16:08 /run/user/1000/dconf/user

_________________
http://dev.gentoo.org/~dabbott/
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 490
Location: "Hemp"shire, UK

PostPosted: Wed Dec 11, 2013 7:52 pm    Post subject: Reply with quote

I think I cracked it. First I forced off consolekit USE flag and rebuilt anything needing rebuilding.
Then I uncommented this line:

Code:

session        optional        pam_systemd.so


(by removing the dash in front of that line)

Problem hasn't returned for the last 24 hours ...
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
comprookie2000
Retired Dev
Retired Dev


Joined: 25 Jul 2004
Posts: 925
Location: Sun City Center, Florida

PostPosted: Wed Dec 11, 2013 8:46 pm    Post subject: Reply with quote

alexbuell wrote:

Then I uncommented this line:

Code:

session        optional        pam_systemd.so




What file was that in?
_________________
http://dev.gentoo.org/~dabbott/
Back to top
View user's profile Send private message
potuz
Guru
Guru


Joined: 30 Jan 2010
Posts: 378

PostPosted: Wed Dec 11, 2013 9:44 pm    Post subject: Reply with quote

alexbuell wrote:
I think I cracked it. First I forced off consolekit USE flag and rebuilt anything needing rebuilding.
Then I uncommented this line:

Code:

session        optional        pam_systemd.so


(by removing the dash in front of that line)

Problem hasn't returned for the last 24 hours ...

That's very weird since in any case the purpose of pam_systemd.so is to actually set those permissions right :)
http://www.freedesktop.org/software/systemd/man/pam_systemd.html

Ahh just read that you *un*commented it... at first sight I thought the opposite :)
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 490
Location: "Hemp"shire, UK

PostPosted: Sat Dec 21, 2013 11:23 am    Post subject: Reply with quote

I still had hangs ... which only an alt-fX switch to console and a quick chown temporarily solved.

Enabling CONFIG_CONNECTOR and CONFIG_PROC_EVENTS in kernel seems to have improved matters considerably ...

The jury's still out on Gnome 3.x though ...
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
comprookie2000
Retired Dev
Retired Dev


Joined: 25 Jul 2004
Posts: 925
Location: Sun City Center, Florida

PostPosted: Sat Dec 21, 2013 7:42 pm    Post subject: Reply with quote

Did you select systemd in your kernel conf?
Code:

Kernel configuration
Quick setup using gentoo-sources

Gentoo Linux --->
        Support for init systems, system and service managers --->
                [*] systemd

Thats from the wiki :)
https://wiki.gentoo.org/wiki/Systemd

Maybe those options need to be included.
_________________
http://dev.gentoo.org/~dabbott/
Back to top
View user's profile Send private message
alexbuell
Guru
Guru


Joined: 18 Jul 2002
Posts: 490
Location: "Hemp"shire, UK

PostPosted: Sun Mar 09, 2014 11:19 pm    Post subject: Reply with quote

comprookie2000 wrote:
Did you select systemd in your kernel conf?
Code:

Kernel configuration
Quick setup using gentoo-sources

Gentoo Linux --->
        Support for init systems, system and service managers --->
                [*] systemd

Thats from the wiki :)
https://wiki.gentoo.org/wiki/Systemd

Maybe those options need to be included.


Yes, that definitely one of those options that needs to be forcibly selected... not sure why it wasn't explicitly enable, maybe installing systemd should list those CONFIG_* variables needing to be enabled?
_________________
Cheers,
Alex.

Linux - the best text adventure game ever.
Back to top
View user's profile Send private message
jhon987
Apprentice
Apprentice


Joined: 18 Nov 2013
Posts: 297

PostPosted: Mon Jun 23, 2014 6:10 pm    Post subject: Reply with quote

check out this guy's solution: http://gawainlynch.com/gnome-shell-crashes-after-su/

What do you think?
Back to top
View user's profile Send private message
Nitro_146
Apprentice
Apprentice


Joined: 02 Mar 2005
Posts: 221
Location: Digne les bains, France

PostPosted: Mon Oct 20, 2014 9:39 pm    Post subject: Reply with quote

Hi,

I am facing the same problem for some time.

Anyone had success in solving it ?

The above solution does not work for me.
_________________
Linux, cause booting is for adding new hardware
Back to top
View user's profile Send private message
Display posts from previous:   
Reply to topic    Gentoo Forums Forum Index Desktop Environments All times are GMT
Page 1 of 1

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum