Gnome terminal won't load (amd64, nvidia driver, xinerama)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gnome-terminal (Ubuntu) |
Invalid
|
Undecided
|
Ubuntu Desktop Bugs |
Bug Description
Binary package hint: gnome-terminal
When running the nvidia proprietry drivers on my amd64 installation of ubuntu edgy, with xinerama enabled over 3 monitors (2 cards) gnome-terminal won't run.
I understand this may be to do with the nvidia driver but there is an x error so I'd like to look into it as far as possible and if it leads there i'll contact them directly.
Disabling xinerama fixes the problem, running the open source drivers seems to but I haven't managed to get the system set up right with them anyway so that point is kind of moot.
Anyway, I've been trying to generate a stack trace but I seem to be missing lots of symbols. Can anyone suggest what to do to get some more information here?
james@simba:~/gt$ gdb gnome-terminal
GNU gdb 6.4.90-debian
Copyright (C) 2006 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "x86_64-
(gdb) break gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (gdk_x_error) pending.
(gdb) run --sync
Starting program: /usr/bin/
[Thread debugging using libthread_db enabled]
[New Thread 47277566731920 (LWP 22037)]
Breakpoint 2 at 0x2affa5ad6ea0: file gdkmain-x11.c, line 607.
Pending breakpoint "gdk_x_error" resolved
[Switching to Thread 47277566731920 (LWP 22037)]
Breakpoint 2, gdk_x_error (display=0x572ef0, error=0x7fff060
607 gdkmain-x11.c: No such file or directory.
in gdkmain-x11.c
(gdb) bt
#0 gdk_x_error (display=0x572ef0, error=0x7fff060
#1 0x00002affa5fa1cf6 in _XError () from /usr/lib64/
#2 0x00002aff00000000 in ?? ()
#3 0x0000000000572ef0 in ?? ()
#4 0x0000000002e00001 in ?? ()
#5 0x0000000000000088 in ?? ()
#6 0x0000000000004e02 in ?? ()
#7 0x00000000001dc258 in ?? ()
#8 0x00007fff0605de00 in ?? ()
#9 0x0000000000000088 in ?? ()
#10 0x0000000000000089 in ?? ()
#11 0x00007fff0605ddc4 in ?? ()
#12 0x00002affa5f5f000 in ?? ()
#13 0x00002affa4a55094 in _dl_rtld_di_serinfo () from /lib64/
#14 0x00002affa4a5acb2 in _dl_make_
#15 0x00002affa5fa38f9 in _XReply () from /usr/lib64/
#16 0x00007fff0605de20 in ?? ()
#17 0x0000000000000000 in ?? ()
(gdb)
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.