Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#7986 - GNOME stopped working after pacman -Syu
Attached to Project:
Arch Linux
Opened by Ondrej Jirman (megous) - Monday, 10 September 2007, 11:36 GMT
Last edited by Jan de Groot (JGC) - Monday, 10 September 2007, 22:06 GMT
Opened by Ondrej Jirman (megous) - Monday, 10 September 2007, 11:36 GMT
Last edited by Jan de Groot (JGC) - Monday, 10 September 2007, 22:06 GMT
|
DetailsDescription:
After upgrade GNOME no longer works. More exactly works in very reduced mode (no panel, defualt theme, etc.) because nothing can conenct to gconf. Xsesssion log is full of CORBA related errors. /etc/gdm/PreSession/Default: Registering your session with wtmp and utmp /etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "megi" /etc/gdm/Xsession: Beginning session setup... /etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- /usr/bin/gnome-session GConf Error: Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/UNKNOWN:1.0 GConf Error: Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/UNKNOWN:1.0 ...... Window manager warning: Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/UNKNOWN:1.0 ** (gnome-panel:7384): WARNING **: Error getting value of '/apps/panel/global/disable_force_quit': Adding client to server's list failed, CORBA error: IDL:omg.org/CORBA/UNKNOWN:1.0 ...... etc. nothing else unusual is in the log. No dynamic lybrary related errors or anything. Steps to reproduce: pacman -Syu run any app that requires gconf or restart X session |
This task depends upon
Closed by Jan de Groot (JGC)
Monday, 10 September 2007, 22:06 GMT
Reason for closing: Works for me
Additional comments about closing: this must have been an issue where gconfd was exiting, but didn't clean up its sockets yet, while another one was started at the same time.
Monday, 10 September 2007, 22:06 GMT
Reason for closing: Works for me
Additional comments about closing: this must have been an issue where gconfd was exiting, but didn't clean up its sockets yet, while another one was started at the same time.
[2007-09-10 12:57] starting full system upgrade
[2007-09-10 12:58] upgraded gnome-build (0.1.7-1 -> 0.2.0-1)
[2007-09-10 12:58] upgraded graphviz (2.14-2 -> 2.14.1-1)
[2007-09-10 12:58] upgraded anjuta (2.2.0-3 -> 2.2.1-1)
[2007-09-10 12:58] warning: /etc/httpd/conf/extra/httpd-vhosts.conf installed as /etc/httpd/conf/extra/httpd-vhosts.conf.pacnew
[2007-09-10 12:58] warning: /etc/httpd/conf/extra/httpd-ssl.conf installed as /etc/httpd/conf/extra/httpd-ssl.conf.pacnew
[2007-09-10 12:58] upgraded apache (2.2.4-2 -> 2.2.6-1)
[2007-09-10 12:58] upgraded binutils (2.17.50.0.18-1 -> 2.18-2)
[2007-09-10 12:58]
[2007-09-10 12:58] ==> deluge post_upgrade message:
[2007-09-10 12:58]
[2007-09-10 12:58] ==> After upgrading your Deluge installation, it
[2007-09-10 12:58] ==> may fail to start. If this happens to you, you
[2007-09-10 12:58] ==> need to remove your ~/.config/deluge directory
[2007-09-10 12:58] ==> (but make a backup first!)
[2007-09-10 12:58] ==> to allow Deluge to rebuild it's configuration
[2007-09-10 12:58] ==> file.
[2007-09-10 12:58]
[2007-09-10 12:58] upgraded deluge (0.5.4.1-1 -> 0.5.5-1)
[2007-09-10 12:58] upgraded libpng (1.2.18-1 -> 1.2.20-1)
[2007-09-10 12:58] upgraded dosbox (0.70-2 -> 0.72-1)
[2007-09-10 12:58] upgraded poppler (0.5.91-1 -> 0.6-1)
[2007-09-10 12:58] upgraded poppler-glib (0.5.91-1 -> 0.6-1)
[2007-09-10 12:58] upgraded evince (0.8.3-1 -> 2.19.92-1)
[2007-09-10 12:58] upgraded libgsf (1.14.6-1 -> 1.14.7-1)
[2007-09-10 12:58] upgraded net-snmp (5.4-1 -> 5.4.1-1)
user.log:
Sep 10 12:58:24 gconfd (megi-5981): Received signal 15, shutting down cleanly
Sep 10 12:58:24 gconfd (megi-5981): Exiting
Sep 10 12:58:30 gconfd (megi-6346): starting (version 2.18.0.1), pid 6346 user 'megi'
Sep 10 12:58:30 gconfd (megi-6346): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Sep 10 12:58:30 gconfd (megi-6346): Resolved address "xml:readwrite:/home/megi/.gconf" to a writable configuration source at position 1
Sep 10 12:58:30 gconfd (megi-6346): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Sep 10 12:58:32 gconfd (megi-6346): Received signal 15, shutting down cleanly
Sep 10 12:58:32 gconfd (megi-6346): Exiting
Sep 10 12:58:32 gconfd (megi-6356): starting (version 2.18.0.1), pid 6356 user 'megi'
Sep 10 12:58:32 gconfd (megi-6356): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Sep 10 12:58:32 gconfd (megi-6356): Resolved address "xml:readwrite:/home/megi/.gconf" to a writable configuration source at position 1
Sep 10 12:58:32 gconfd (megi-6356): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Sep 10 12:58:43 gconfd (megi-6356): Received signal 15, shutting down cleanly
Sep 10 12:58:43 gconfd (megi-6356): Exiting
Sep 10 12:58:44 gconfd (megi-6384): starting (version 2.18.0.1), pid 6384 user 'megi'
Sep 10 12:58:44 gconfd (megi-6384): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Sep 10 12:58:44 gconfd (megi-6384): Resolved address "xml:readwrite:/home/megi/.gconf" to a writable configuration source at position 1
Sep 10 12:58:44 gconfd (megi-6384): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Sep 10 12:58:47 gconfd (megi-6384): Received signal 15, shutting down cleanly
Sep 10 12:58:47 gconfd (megi-6384): Some clown returned undeclared exception 'IDL:ConfigException:1.0'
Sep 10 12:58:47 gconfd (megi-6384): Some clown returned undeclared exception 'IDL:ConfigException:1.0'
Sep 10 12:58:47 gconfd (megi-6388): starting (version 2.18.0.1), pid 6388 user 'megi'
Sep 10 12:58:47 gconfd (megi-6388): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-megi/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Sep 10 12:58:47 gconfd (megi-6384): Some clown returned undeclared exception 'IDL:ConfigException:1.0'
Sep 10 12:59:10 gconfd (megi-6384): Some clown returned undeclared exception 'IDL:ConfigException:1.0'
Sep 10 12:59:10 gconfd (megi-6454): starting (version 2.18.0.1), pid 6454 user 'megi'
Sep 10 12:59:10 gconfd (megi-6454): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-megi/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Sep 10 12:59:10 gconfd (megi-6384): Some clown returned undeclared exception 'IDL:ConfigException:1.0'
Sep 10 12:59:10 gconfd (megi-6384): Some clown returned undeclared exception 'IDL:ConfigException:1.0'
Sep 10 12:59:10 gconfd (megi-6456): starting (version 2.18.0.1), pid 6456 user 'megi'
Sep 10 12:59:10 gconfd (megi-6456): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-megi/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Sep 10 12:59:10 gconfd (megi-6384): Some clown returned undeclared exception 'IDL:ConfigException:1.0'
Sep 10 12:59:10 gconfd (megi-6384): Some clown returned undeclared exception 'IDL:ConfigException:1.0'
Sep 10 12:59:10 gconfd (megi-6458): starting (version 2.18.0.1), pid 6458 user 'megi'
But it's interesting how the situation could have been triggered by pacman -Syu
in the first place. I guess that three packages requested restart of gconfd
and something gone bad after third one. Probably some race or something.
Simple system restart would have solved the problem too.