X unusable

Bug #67794 reported by Despair
2
Affects Status Importance Assigned to Milestone
control-center (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-control-center

~/.fonts.conf makes gnome-settings-daemon freeze up, which causes most gnome applications to render as white noninteractive boxes.
~/.Xmodmap pops up a dialog asking whether it should be loaded every gnome startup.
The combination blocks launching of launcher apps, or anything later in gnome. When not using gnome-session, it's sometimes possible to kill gnome-settings-daemon & start it again a couple of times and eventually it may work, and gnome applications executed afterwards will run, but crash randomly.

Without .Xmodmap, no dialog during early startup, so it sometimes starts apps successfully but is unstable. Possibly a race in g-s-d?

This is very frustrating, as I use custom settings in fonts.conf for non-gnome apps, and they work fine... I use equivalent settings in the font properties in gnome.

Other really fun bit is that renaming .Xmodmap to DOTXmodmap, gnome continued to find it and ask if I wanted to load it. Finally had to hide it in a subdirectory to make it stop popping up a dialog during early startup...

Revision history for this message
Despair (despair) wrote :
Revision history for this message
Despair (despair) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug. Please describe one issue by bug only. That .fonts.conf works fine for me. Could you get a backtrace of gnome-settings-daemon while it's frozen? Does it hang applications runned out of GNOME? What applications did you try?

Changed in control-center:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Despair (despair) wrote :

It is one issue, arising from multiple bugs. The individual bugs are hard to replicate seperately, but in combination lock up gnome-session 100% of the time on my machine. The issue is the bug interaction. At least that was my tired reasoning for dropping all 4 bugs into 1 report. The Xmodmap popup by itself is just a minor annoyance, though the automagic finding of all might-be-modmap configs is very odd, seems liable to be an unnecessary slowdown to gnome startup.

I'll try to get a backtrace later today.

You wind up with a blank white window, a movable mouse cursor, and nothing you can do. Doesn't reach loading keybindings, and nothing is clickable.
I was unable to try any applications while launching a gnome session from gdm.
With both of those config files installed (or renamed and being found anyways... ugh) I had to launch a KDE session to be able to do anything at all.

For applications I tried gnome-terminal, gaim, xchat and gnome-control-center. xchat & gaim would sometimes lock up independently of others. Sometimes everything went at once. Erratic behavior, very exciting.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you get that backtrace?

Revision history for this message
Daniel Holbach (dholbach) wrote :

We are closing this bug report as it lacks the information, which was described in the previous comments, we need to investigate the problem further. However, please reopen it if you can give us the missing information and don't hesitate to submit bug reports in the future.

Changed in control-center:
status: Needs Info → Rejected
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.