First of all thank you for your help. Let me start from scratch: 1. System Used: RedHat 8.0 2. GNOME-2.0 3. KDE-3.0.3 4. XFree86-4.2.0 I tried to upgrade from GTK-2.0.0 to GTK-2.2.0. After the upgrade, I tried to login to my gnome session but, I couldn't see the desktop icon and when I press the main menu, I see blank menu with icons only. No applications run from the menu or the task bar icons, except the following: The Gimp 1.2.3 Evolution 1.0.8 and here is the .xsession-errors after logging using gnome: ========================================================== SESSION_MANAGER=local/shaffei.eth:/tmp/.ICE-unix/4076 Loaded background '0x8098c18 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 FAMOpen failed, FAMErrno=0 The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 45 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 46 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Multiple segmentation faults occurred; can't display error dialog FAMOpen failed, FAMErrno=0 The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 45 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 46 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Multiple segmentation faults occurred; can't display error dialog FAMOpen failed, FAMErrno=0 The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 45 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) FAMOpen failed, FAMErrno=0 The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 45 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 46 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Multiple segmentation faults occurred; can't display error dialog FAMOpen failed, FAMErrno=0 The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 45 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 46 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Multiple segmentation faults occurred; can't display error dialog FAMOpen failed, FAMErrno=0 The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 45 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) FAMOpen failed, FAMErrno=0 The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 45 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 46 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Multiple segmentation faults occurred; can't display error dialog FAMOpen failed, FAMErrno=0 The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 45 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 46 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Multiple segmentation faults occurred; can't display error dialog FAMOpen failed, FAMErrno=0 The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 45 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) FAMOpen failed, FAMErrno=0 The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 45 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) FAMOpen failed, FAMErrno=0 The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 45 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'nautilus' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 46 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) Multiple segmentation faults occurred; can't display error dialog (magicdev:4142): GLib-GObject-WARNING **: cannot create instance of abstract (non-instantiatable) type `GtkWidget' (gnome-panel:4146): GLib-GObject-WARNING **: cannot create instance of abstract (non-instantiatable) type `GtkWidget' The program 'gnome_segv' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 43 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) The program 'gnome_segv' received an X Window System error. This probably reflects a bug in the program. The error was 'BadLength (poly request too large or internal Xlib length erro'. (Details: serial 43 error_code 16 request_code 156 minor_code 20) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) (pam-panel-icon:4148): Gdk-WARNING **: GdkWindow 0x1400002 unexpectedly destroyed ========================================================================= When I try to login using KDE session, it works fine but I can't launch for example any of the gnome-games, the game crashes and when I try to submit the bug. The bug-buddy crashes too. Here is the output of .xsession errors after logging into KDE: ========================================================================= DCOPServer up and running. Mutex destroy failure: Device or resource busy Mutex destroy failure: Device or resource busy mcop warning: user defined signal handler found for SIG_PIPE, overriding mcop warning: user defined signal handler found for SIG_PIPE, overriding QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/DigitalClock) Negative sizes (2,-4) are not possible QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/QLabel) Negative sizes (59,-4) are not possible QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/DigitalClock) Negative sizes (2,-4) are not possible QWidget::setMinimumSize: The smallest allowed size is (0,0) QWidget::setMaximumSize: (unnamed/QLabel) Negative sizes (59,-4) are not possible Mutex destroy failure: Device or resource busy QObject::connect: No such slot KWrited::block_in(const char*,int) QObject::connect: (sender name: 'unnamed') QObject::connect: (receiver name: 'unnamed') QFont::setPixelSize: Pixel size <= 0 (-1) QMenuData::removeItem: Index -1 out of range QMenuData::removeItem: Index -1 out of range X Error of failed request: BadWindow (invalid Window parameter) Major opcode of failed request: 25 (X_SendEvent) Resource id in failed request: 0x1200005 Serial number of failed request: 1908 Current serial number in output stream: 2009 kdeinit: Fatal IO error: client killed kdeinit: sending SIGHUP to children. KLauncher: Exiting on signal 1 kdeinit: sending SIGTERM to children. kdeinit: Exit. ============================================================================ I think I gave you many information regarding the case I'm facing. Please do not hesitate to ask me for more info. On Mon, 2003-06-16 at 17:51, Peter "Firefly" Lund wrote: > Disclaimer: I don't have any intimate knowledge of Nautilus whatsoever. > I do know something about bug hunting and the X protocol, though. > > On Mon, 16 Jun 2003, Ibrahim El-Shafei wrote: > > > On Redhat 8.0, XFree86-4.2.0 > > I'm using NVIDIA Geforce2 factory drivers. if this may help. > > It won't help me but it might provide a clue for others. > > > While logging into any account using the GNOME session. And if I try to > > open any GTK application it crashes. > > This sounds a bit muddy. > > As a programmer I would like to know precisely which applications work and > which don't... and how they break if they don't work. Then I could go > look at how they use X differently. > > Have you tried KDE? What happens then? WindowMaker? > What if you start X with just a simple window manager and start various X > programs - can you run gv? xmms? xcalc? xmag? - what if you start a Gnome > program like gnumeric from that simple X environment? etc... > > (I don't know if you are comfortable enough in a Unix/Linux environment to > do the above - it would help if you could) > > > Galeon 1.2.5 is working but I don't know is it based on GTK 1 or 2. > > The Gimp 1.2.3 is also working. > > Ok, some GTK+ programs work, then. In other words "And if I try to open > any GTK application it crashes" is not an entirely true statement. Before > you can expect anybody to really dig into this, I think you need to > provide cleaner data. > > -Peter > > We bomb for peace on Mondays, Wednesdays and Fridays. We bring democracy by bypassing > the UN voting process on Tuesdays, Thursdays and Saturdays...- Rogerborg -- Ibrahim El-Shafei "HimaTech" Love means having to say I'm sorry every 5 minutes.
