Bug 150428 - gnome-session or metacity problem
Summary: gnome-session or metacity problem
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-session
Version: 3
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-03-06 11:40 UTC by Thilo Pfennig
Modified: 2007-11-30 22:11 UTC (History)
0 users

Fixed In Version: gnome-session-2.10.0-2
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-12-16 15:14:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Thilo Pfennig 2005-03-06 11:40:14 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.6)
Gecko/20050302 Firefox/1.0.1 Fedora/1.0.1-1.3.2

Description of problem:
I can not login with gnome-session any more after changing my graphics
card and mainboard.

Version-Release number of selected component (if applicable):
gnome-session-2.8.0-4 metacity-2.8.6-2

How reproducible:
Always

Steps to Reproduce:
(Not reproducible on all machines!)
1. try to log in as normal user with GNOME


    

Actual Results:  While loading Metacity that is displyes on the splash
screen there is not much progress. After a very long time some startup
applications are loaded. There is no window manager!

Expected Results:  Metacity should be loaded quickly and then nautilus
and then the startup apps.

Additional info:

I only have this error on one user. I have tried to delete .gconf* or
.gnome* - but hat does not change anything. i can log in as root with
gnome or any other user. I can not detect any errors.

I can start a good looking gnome session with "gnome-session
--failsafe" if I start this with the right $DISPLAY set from console.

KDE is also running fine.

I think this should never happen. It leaves the user no choice but
deleting the whole directory.

Comment 1 Thilo Pfennig 2005-12-16 15:14:09 UTC
this was a result of mixing FC3 with FC4testing3 if I recall correctly.


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