Bug 670854 - gdm broken on Rawhide install
Summary: gdm broken on Rawhide install
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: rawhide
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: jmccann
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d4ccc38577f72f15f923376287c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-19 14:45 UTC by Paolo Bonzini
Modified: 2015-01-14 23:26 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-01-24 04:52:58 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (17.26 KB, text/plain)
2011-01-19 14:45 UTC, Paolo Bonzini
no flags Details
extract of /var/log/messages (215.94 KB, text/plain)
2011-01-19 14:48 UTC, Paolo Bonzini
no flags Details

Description Paolo Bonzini 2011-01-19 14:45:49 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gdm-simple-greeter
component: gdm
executable: /usr/libexec/gdm-simple-greeter
kernel: 2.6.37-2.fc15.x86_64
package: gdm-1:2.91.4-1.fc15
reason: Process /usr/libexec/gdm-simple-greeter was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Rawhide)
time: 1295447217
uid: 42

How to reproduce
-----
gdm does not work on this installation.  As soon as I try to enter runlevel 5, gdm-simple-greeter keeps crashing.

Right after the Rawhide install, gdm came up correctly.  It started failing after I ran the following commands:

groupadd -g 501
useradd -u 501 -g 501 pbonzini

The /home/pbonzini directory was preexisting, since the /home partition is shared with other Linux installs on this machine.

Comment 1 Paolo Bonzini 2011-01-19 14:45:52 UTC
Created attachment 474284 [details]
File: backtrace

Comment 2 Paolo Bonzini 2011-01-19 14:48:15 UTC
Created attachment 474285 [details]
extract of /var/log/messages

Comment 3 Paolo Bonzini 2011-01-24 04:52:44 UTC
I cannot reproduce it anymore with gdm-2.91.4-5.


Note You need to log in before you can comment on or make changes to this bug.