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 650787 - Gnome-shell crashes with custom xorg.conf
Gnome-shell crashes with custom xorg.conf
Status: RESOLVED DUPLICATE of bug 648156
Product: gnome-shell
Classification: Core
Component: general
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
Depends on:
Reported: 2011-05-22 10:31 UTC by Steven Webb
Modified: 2011-05-22 16:00 UTC
See Also:
GNOME target: ---
GNOME version: ---

~/.xsession-errors (9.87 KB, text/plain)
2011-05-22 10:31 UTC, Steven Webb
xorg.conf (3.39 KB, text/plain)
2011-05-22 10:32 UTC, Steven Webb

Description Steven Webb 2011-05-22 10:31:27 UTC
Created attachment 188329 [details]

If I let X automatically configure itself gnome-session works correctly. However, when I manually specify an xorg.conf gnome-shell crashes, displays an error saying something went wrong, and has a logout button. If I launch gnome-shell from a terminal (with export DISPLAY=:0) I get the following errors:

Window manager warning: Log level 8: gtk_style_context_get: assertion `priv->widget_path != NULL' failed
gnome-shell: /build/buildd/cairo-1.10.2/src/cairo-pattern.c:764: cairo_pattern_reference: Assertion `((*&(&pattern->ref_count)->ref_count) > 0)' failed.

I've attached ~/.xsession-errors. As GDM is starting correctly I believe my xorg.conf is correct.

I'm using Ubuntu 11.04 with the closed source nVidia driver.

Cheers for the great work in Gnome 3.

Comment 1 Steven Webb 2011-05-22 10:32:17 UTC
Created attachment 188330 [details]
Comment 2 Rui Matos 2011-05-22 11:09:00 UTC
Does this happen if you use only a single screen in your X configuration?
Comment 3 Steven Webb 2011-05-22 12:02:31 UTC
No. Only with two monitors. I can get either my laptop screen or the external monitor working with an xorg.conf.
Comment 4 Rui Matos 2011-05-22 16:00:22 UTC
Ok, so this is already known. I recommend you to use nvidia's twinview feature instead of separate X screens as a workaround for now.

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