After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 548590 - Infinite restart when /tmp partition full
Infinite restart when /tmp partition full
Status: RESOLVED DUPLICATE of bug 350535
Product: gdm
Classification: Core
Component: general
2.22.x
Other All
: Normal critical
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2008-08-20 08:12 UTC by Aidan Delaney
Modified: 2010-06-16 23:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description Aidan Delaney 2008-08-20 08:12:18 UTC 
Steps to reproduce:
1. Do something stupid to fill the partition containing /tmp
2. Restart GDM (init 3 && init 5, or reboot machine)
3. Notice that GDM constantly restarts with the following error

 gconfd (gdm-6825): Resource problem creating '/tmp/orbit-gdm'

Presumably gdm should catch this gconfd error and display an error with steps for an appropriate resolution.


Stack trace:


Other information:
Running Fedora 9, I don't know how much F9 gdm differs from the upstream.  Please advise if I should file this downstream.
Comment 1 William Jon McCann 2008-08-21 15:37:21 UTC 
Thanks for the report.  Can you attach the log files from /var/log/gdm for this display?  Thanks!
Comment 2 ultramancool 2010-01-27 07:11:44 UTC 
I recently had a copy of gdm running with /tmp full and ran into all sorts of strange issues, primarily gconfd not starting causing config issues all over with it. If we could just display a warning or something it would be very helpful, it took me around an hour to figure this problem out!
Comment 3 William Jon McCann 2010-06-16 23:44:26 UTC 

*** This bug has been marked as a duplicate of bug 350535 ***