Gaim crashes when sending/receivin files. .xsessionerrors says: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2a00984 aMule 2.0.0 RC8 keeps on sending error messages to .xsessionerros. After 1-2 days .xsessionerrors's size is over 50 MB because of this. Distro is Mandrake 10.1 Official up-to-date.
I've fixed the gaim crash in CVS. Not sure about the problem with aMule. I can't test it here, because it refuses to compile, and I can't find a binary package that works :P I'll test it later.
With Fedora Core 3 using the same software, Gaim, and OpenOffice freeze/crash when bringing up the "save as" window, before the window is displayed.
I think bugs 2831 and 3393 depends (or are duplicates of) this bug. I can get both (almost 100% of the time) Firefox 1.0.6 and Thunderbird 1.0.6 to crash if I switch to a virtual desktop which does not contain those applications and klick on something in the kicker (e.g. application buttons or the K-menu) in KDE 3.4 and GTK/QT 0.6 and Baghira 0.6e. But I can safely use kicker (click on buttons, using the K-menu, ...) without Firefox or Thunderbird crashing if I access it on the same virtual desktop Firefox runs. When Firefox/Thunderbird crash they spew out messages like this in $HOME/.xsession-errors QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::hide() to Baghira::DeMaximizer::hide() QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::hide() to Baghira::DeMaximizer::hide() QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::hide() to Baghira::DeMaximizer::hide() No running windows found QObject::disconnect: Unexpected null parameter QObject::connect: Cannot connect (null)::hide() to Baghira::DeMaximizer::hide() (Gecko:8408): Gdk-CRITICAL **: gdk_pixbuf_get_from_drawable: assertion `gdk_window_is_viewable (src)' failed (Gecko:8408): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_n_channels: assertion `pixbuf != NULL' failed --- 8< many Gdk-errors removed 8< --- (Gecko:8408): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_height: assertion `pixbuf != NULL' failed (Gecko:8408): GdkPixbuf-CRITICAL **: gdk_pixbuf_get_rowstride: assertion `pixbuf != NULL' failed (Gecko:8408): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed /usr/libexec/mozilla-launcher: line 116: 8408 Segmentation fault "$mozbin" "$@" firefox-bin exited with non-zero status (139)
I'm seeing firefox/gimp crashes w/ gtk-qt-engine (cvs build) + baghira-0.71 (see https://bugs.freedesktop.org/show_bug.cgi?id=3393#c1)
I'm using gtk-qt-engine-0.6cvs20050709 and baghira 0.7 In this configuration I have some serious problems, not as many as before, but still enough. So here's what I discovered sofar: with eclipse it's the following methods which cause a crash of the application: C [libgdk-x11-2.0.so.0+0x54c2b] gdk_window_set_back_pixmap+0x11b C [libgdk-x11-2.0.so.0+0x16355] gdk_drawable_get_colormap+0x25 Then with gimp, I have observed those error messages: (gimp-2.3:23888): Gdk-CRITICAL **: gdk_drawable_get_colormap: assertion `GDK_IS_DRAWABLE (drawable)' failed (gimp-2.3:23888): Gdk-CRITICAL **: gdk_drawable_set_colormap: assertion `GDK_IS_DRAWABLE (drawable)' failed (gimp-2.3:23888): Gdk-CRITICAL **: gdk_drawable_get_depth: assertion `GDK_IS_DRAWABLE (drawable)' failed (gimp-2.3:23888): Gdk-CRITICAL **: gdk_window_set_back_pixmap: assertion `pixmap == NULL || gdk_drawable_get_depth (window) == gdk_drawable_get_depth (pixmap)' failed and as far as I see it, all (ok, maybe not) gtk applications have a problem with unreferencing a GObject (firefox-bin:24962): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed I really hope, I could help in some way
Closing this because it works for me, and has probably been fixed in a later version. If the problem persists with a fresh SVN checkout, please open a new bug in the new bugtracker: http://gtk-qt.ecs.soton.ac.uk/bugs.php Thanks!
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.