Arch Linux

br4

Member

Registered: 2007-12-27

Posts: 38

After the last update of Gnome X doesn`t start

hi again,

here ist my errors.log

Apr  9 21:06:35 myhost gdm-binary[3438]: ERROR: Resource problem creating '/tmp/orbit-nobody' aborting...
Apr  9 21:06:35 myhost gdm-binary[3439]: ERROR: Resource problem creating '/tmp/orbit-nobody' aborting...
Apr  9 21:06:41 myhost gdm-binary[3460]: ERROR: Resource problem creating '/tmp/orbit-nobody' aborting...
Apr  9 21:06:41 myhost gdm-binary[3461]: ERROR: Resource problem creating '/tmp/orbit-nobody' aborting...
Apr  9 21:06:48 myhost gdm-binary[3482]: ERROR: Resource problem creating '/tmp/orbit-nobody' aborting...
Apr  9 21:06:48 myhost gdm-binary[3483]: ERROR: Resource problem creating '/tmp/orbit-nobody' aborting...
Apr  9 21:09:19 myhost pnpacpi: exceeded the max number of mem resources: 12
Apr  9 21:09:19 myhost intel_rng: FWH not detected
Apr  9 21:09:19 myhost usb 2-2: device descriptor read/all, error -71
Apr  9 21:09:21 myhost sd 2:0:0:0: [sdb] Assuming drive cache: write through
Apr  9 21:09:21 myhost sd 2:0:0:0: [sdb] Assuming drive cache: write through
Apr  9 21:09:31 myhost gdm-binary[3536]: ERROR: Resource problem creating '/tmp/orbit-nobody' aborting...
Apr  9 21:09:31 myhost gdm-binary[3537]: ERROR: Resource problem creating '/tmp/orbit-nobody' aborting...

and messages.log

Apr  9 19:16:08 gconfd (fd-4169): starting (version 2.22.0), pid 4169 user 'fd'
Apr  9 19:16:08 gconfd (fd-4169): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Apr  9 19:16:08 gconfd (fd-4169): Resolved address "xml:readwrite:/home/fd/.gconf" to a writable configuration source at position 1
Apr  9 19:16:08 gconfd (fd-4169): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Apr  9 19:16:08 gconfd (fd-4170): starting (version 2.22.0), pid 4170 user 'fd'
Apr  9 19:16:08 gconfd (fd-4170): Failed to get lock for daemon, exiting: Failed to lock '/tmp/gconfd-fd/lock/ior': probably another process has the lock, or your operating system has NFS file locking misconfigured (Resource temporarily unavailable)
Apr  9 19:16:09 gconfd (fd-4169): Resolved address "xml:readwrite:/home/fd/.gconf" to a writable configuration source at position 0
Apr  9 19:16:14 gconfd (fd-4169): Exiting
Apr  9 19:16:14 gconfd (fd-4196): starting (version 2.22.0), pid 4196 user 'fd'
Apr  9 19:16:14 gconfd (fd-4196): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Apr  9 19:16:14 gconfd (fd-4196): Resolved address "xml:readwrite:/home/fd/.gconf" to a writable configuration source at position 1
Apr  9 19:16:14 gconfd (fd-4196): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Apr  9 19:16:21 gconfd (fd-4196): Exiting

[]the update starts/or just after it[]

Apr  9 19:41:56 gconfd (fd-4693): starting (version 2.22.0), pid 4693 user 'fd'
Apr  9 19:41:56 gconfd (fd-4693): Failed to get lock for daemon, exiting: Failed to get a lock: couldn't create directory `/tmp/gconfd-fd/lock': No space left on device
Apr  9 19:41:56 gconfd (fd-4695): starting (version 2.22.0), pid 4695 user 'fd'
Apr  9 19:41:56 gconfd (fd-4695): Failed to get lock for daemon, exiting: Failed to get a lock: couldn't create directory `/tmp/gconfd-fd/lock': No space left on device
Apr  9 19:41:56 gconfd (fd-4697): starting (version 2.22.0), pid 4697 user 'fd'
Apr  9 19:41:56 gconfd (fd-4697): Failed to get lock for daemon, exiting: Failed to get a lock: couldn't create directory `/tmp/gconfd-fd/lock': No space left on device
Apr  9 19:41:56 gconfd (fd-4699): starting (version 2.22.0), pid 4699 user 'fd'
.
.
.
.
Apr  9 19:45:27 gconfd (fd-7773): Failed to get lock for daemon, exiting: Failed to get a lock: couldn't create directory `/tmp/gconfd-fd/lock': No space left on device
Apr  9 19:45:27 myhost gdm-binary[3370]: WARNING: Command failed /usr/bin/reboot: Failed to execute child process "/usr/bin/reboot" (No such file or directory)
Apr  9 19:45:27 myhost shutdown[7778]: shutting down for system reboot
Apr  9 19:45:28 myhost init: Switching to runlevel: 6

[]after the restart[]

Apr  9 19:47:29 myhost gdm-binary[3473]: Gtk-WARNING: Locale not supported by C library.     Using the fallback 'C' locale.
Apr  9 19:47:29 myhost gdm-binary[3349]: WARNING: failsafe dialog failed (inhibitions: 0 0)
Apr  9 19:47:29 myhost gdm-binary[3474]: Gtk-WARNING: Locale not supported by C library.     Using the fallback 'C' locale.
Apr  9 19:47:29 myhost gdm-binary[3349]: WARNING: failsafe dialog failed (inhibitions: 0 1)
Apr  9 19:47:29 myhost gdm-binary[3475]: Gtk-WARNING: Locale not supported by C library.     Using the fallback 'C' locale.
Apr  9 19:47:29 myhost gdm-binary[3475]: Gtk-WARNING: Ignoring the separator setting
Apr  9 19:47:48 myhost dhcpcd[3265]: eth0: trying to use old lease in `/var/lib/dhcpcd/dhcpcd-eth0.info'
Apr  9 19:47:48 myhost dhcpcd[3265]: eth0: probing for an IPV4LL address
Apr  9 19:47:48 myhost gdm-binary[3516]: Gtk-WARNING: Locale not supported by C library.     Using the fallback 'C' locale.
Apr  9 19:47:48 myhost gdm-binary[3349]: WARNING: failsafe dialog failed (inhibitions: 0 0)
Apr  9 19:47:48 myhost gdm-binary[3517]: Gtk-WARNING: Locale not supported by C library.     Using the fallback 'C' locale.
Apr  9 19:47:48 myhost gdm-binary[3349]: WARNING: failsafe dialog failed (inhibitions: 0 1)
Apr  9 19:47:48 myhost gdm-binary[3518]: Gtk-WARNING: Locale not supported by C library.     Using the fallback 'C' locale.
Apr  9 19:47:48 myhost gdm-binary[3518]: Gtk-WARNING: Ignoring the separator setting
Apr  9 19:47:49 myhost dhcpcd[3265]: eth0: using IPV4LL address 169.254.61.86
Apr  9 19:47:49 myhost dhcpcd[3265]: eth0: adding IP address 169.254.61.86/16
Apr  9 19:47:49 myhost dhcpcd[3265]: eth0: exiting

hope some one can explain to me what happend and help me fix it.

Last edited by br4 (2008-04-09 18:36:07)

axion419

Member

Registered: 2007-04-12

Posts: 185

Re: After the last update of Gnome X doesn`t start

Are you running the testing repo?  I am just guessing, but I saw the thread and though maybe this could be it.  on the frontpage it mentions.

"Dangerous dbus update for testing

There's a dangerous dbus update coming up for the testing repository. The package itself isn't so special, as it works fine, but the fact that every dbus-daemon process on your system will crash during the upgrade can lead to unpleasant surprises.

Testing users: please be aware of this and run your upcoming upgrades from a plain text console instead of from X. One of the unpleasant surprises is that xorg-server in testing goes down with dbus while it's upgrading, leading to loss of important work or an interrupted package upgrade process."

Just wondering if you are running testing, and run HAL as a daemon then this could be the problem.  Im just guessing, that update might have already came through.

br4

Member

Registered: 2007-12-27

Posts: 38

Re: After the last update of Gnome X doesn`t start

i`m not running testing but i updated dbus(i also read the article but it wasn`t from testing and i thought  it was fixed or there would be a new article for all users)  , don`t tell me its because of it...
-hal is running as a daemon

JGC

Developer

Registered: 2003-12-03

Posts: 1,664

Re: After the last update of Gnome X doesn`t start

Apr  9 21:06:35 myhost gdm-binary[3438]: ERROR: Resource problem creating '/tmp/orbit-nobody' aborting...

What are your permissions for /tmp?

For the dbus upgrade: it only crashes running dbus apps, not the ones you'll start after recovering from a dbus crash.

br4

Member

Registered: 2007-12-27

Posts: 38

Re: After the last update of Gnome X doesn`t start

axion419 and JGC thanks for the reply

it appears i have run out of space because i removed a file and it works now. But i still don`t understand why? I clean pacman`s cache and i have nothing new on the / drive but  free space is disappearing.

Last edited by br4 (2008-04-10 16:58:53)