GNOME Bugzilla – Bug 353503
crash after theme change [@gtk_style_realize] [@gtk_style_ref]
Last modified: 2009-09-05 12:01:36 UTC
Version: 2.15.91 What were you doing when the application crashed? Browsing the page http://www.ubuntuforums.org/showthread.php?t=243622 Distribution: Ubuntu 6.10 (edgy) Gnome Release: 2.15.92 2006-08-22 (Ubuntu) BugBuddy Version: 2.15.92 Memory status: size: 206921728 vsize: 0 resident: 206921728 share: 0 rss: 64475136 rss_rlim: 0 CPU usage: start_time: 1156917510 rtime: 0 utime: 4465 stime: 0 cutime:4227 cstime: 0 timeout: 238 it_real_value: 0 frequency: 0 Backtrace was generated from '/usr/bin/epiphany' (no debugging symbols found) Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1227667792 (LWP 4959)] [New Thread -1373996128 (LWP 5026)] [New Thread -1365603424 (LWP 5025)] [New Thread -1355953248 (LWP 4996)] [New Thread -1347560544 (LWP 4995)] [New Thread -1292559456 (LWP 4973)] [New Thread -1283310688 (LWP 4967)] 0xffffe410 in __kernel_vsyscall ()
+ Trace 71232
Thread 1 (Thread -1227667792 (LWP 4959))
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so.
hmm,
+ Trace 71242
I'm not sure but a NULL colormap could be the problem. Code in gtk is: gtk_style_realize ((GtkStyle *style, GdkColormap *colormap): ... style->colormap = g_object_ref (colormap); style->depth = gdk_colormap_get_visual (colormap)->depth; ...
Can you get a trace with debug symbols (at least glib, pango, gtk, and firefox -dbg packages installed) ? Looks similar but not identical to bug 353398...
Hi, I've installed the debug packages. But right now I can't reproduce the crash, and epiphany is a little unstable.
*** Bug 354928 has been marked as a duplicate of this bug. ***
last duplicate has a good trace
+ Trace 71878
*** Bug 354940 has been marked as a duplicate of this bug. ***
*** Bug 353398 has been marked as a duplicate of this bug. ***
*** Bug 351852 has been marked as a duplicate of this bug. ***
Created attachment 72417 [details] [review] possible fix
*** Bug 354982 has been marked as a duplicate of this bug. ***
*** Bug 355026 has been marked as a duplicate of this bug. ***
*** Bug 355331 has been marked as a duplicate of this bug. ***
*** Bug 355421 has been marked as a duplicate of this bug. ***
Excellent trace from bug 355421 !
+ Trace 72111
(In reply to comment #15) > Excellent trace from bug 355421 ! Thanks. ;) Kinda funny that I wasn't even running Epiphany when I got the crash. :D Anything I can do to help?
Were there any warnings on console before the crash? (Or in ~/.xsession-errors if you started epiphany from the menus/panel.)
*** Bug 355461 has been marked as a duplicate of this bug. ***
*** Bug 355561 has been marked as a duplicate of this bug. ***
*** Bug 356326 has been marked as a duplicate of this bug. ***
*** Bug 356490 has been marked as a duplicate of this bug. ***
*** Bug 356580 has been marked as a duplicate of this bug. ***
*** Bug 356558 has been marked as a duplicate of this bug. ***
*** Bug 357651 has been marked as a duplicate of this bug. ***
*** Bug 357875 has been marked as a duplicate of this bug. ***
*** Bug 354673 has been marked as a duplicate of this bug. ***
> chpe changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > Summary|crash in Epiphany Web |crash after theme change > |Browser: Browsing the page |[@gtk_style_realize] > |http:/... |[@gtk_style_ref] > Version|2.15.x |unspecified I'm not sure about anyone else, but I'm pretty sure I hadn't touched my GTK+ theme at all before seeing this bug. Unless I'm misunderstanding?
+ Trace 73348
This indicates an icon theme change. That could be triggered by a theme change, but also by a run of gtk-update-icon-cache (by installing a program or updating with apt-get), or by installing or uninstalling a theme engine, or by a crash of gnome-settings-daemon.
*** Bug 357924 has been marked as a duplicate of this bug. ***
*** Bug 358967 has been marked as a duplicate of this bug. ***
*** Bug 359385 has been marked as a duplicate of this bug. ***
confirming as per duplicates. :-)
*** Bug 361018 has been marked as a duplicate of this bug. ***
*** Bug 361022 has been marked as a duplicate of this bug. ***
*** Bug 361201 has been marked as a duplicate of this bug. ***
*** Bug 361496 has been marked as a duplicate of this bug. ***
*** Bug 362146 has been marked as a duplicate of this bug. ***
*** Bug 362731 has been marked as a duplicate of this bug. ***
*** Bug 362741 has been marked as a duplicate of this bug. ***
*** Bug 362748 has been marked as a duplicate of this bug. ***
any progress here? this should be fixed in gnome 2.16, this issue bites lots of users... :-/
*** Bug 363060 has been marked as a duplicate of this bug. ***
I haven't been able to find the cause (or even reproduce this). The trace from comment 15 is excellent but not enough; I need to know exactly which widget it is that's having its style reset at the moment of the crash. Everyone who gets this bug please try to produce a core file from the crash so we can examine it (don't attach it to the bug though, that would be useless. If you get one, come on irc.gnome.org #epiphany and we'll debug it remotely).
...which leads up to the question: how can a "normal", non-techie user get a core file? any FAQ or instructions available?
*** Bug 364043 has been marked as a duplicate of this bug. ***
*** Bug 364146 has been marked as a duplicate of this bug. ***
chpe: *ping* - how can a "normal", non-techie user get a core file? any FAQ or instructions available?
Once you have attached gdb to the crashed process according to the standard wiki instructions, type "generate-core-file filename". Or you can run epiphany after enabling core dumps ("ulimit -c unlimited").
*** Bug 365898 has been marked as a duplicate of this bug. ***
*** Bug 366016 has been marked as a duplicate of this bug. ***
*** Bug 365860 has been marked as a duplicate of this bug. ***
*** Bug 366232 has been marked as a duplicate of this bug. ***
*** Bug 366461 has been marked as a duplicate of this bug. ***
*** Bug 367832 has been marked as a duplicate of this bug. ***
*** Bug 368344 has been marked as a duplicate of this bug. ***
*** Bug 368783 has been marked as a duplicate of this bug. ***
*** Bug 370510 has been marked as a duplicate of this bug. ***
Dear bug reporters, can anybody please help the developers to fix this issue by attaching gdb to the crashed process according to http://live.gnome.org/GettingTraces/Details#line-134 ? After that, just type "generate-core-file filename" (where "filename" is the name of the file to generate) and post that file here? Thanks a lot in advance, your help is very appreciated! (20 duplicates in the last 30 days, 40 duplicates total => gnome 2.16.x target.)
*** Bug 371859 has been marked as a duplicate of this bug. ***
I found https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=210151 which I can reproduce in firefox and which gives a trace that seems to indicate to me that it is the same problem. Filed upstream as https://bugzilla.mozilla.org/show_bug.cgi?id=359870 .
*** Bug 373997 has been marked as a duplicate of this bug. ***
*** Bug 374119 has been marked as a duplicate of this bug. ***
*** Bug 376492 has been marked as a duplicate of this bug. ***
*** Bug 377146 has been marked as a duplicate of this bug. ***
*** Bug 377611 has been marked as a duplicate of this bug. ***
*** Bug 377994 has been marked as a duplicate of this bug. ***
*** Bug 379344 has been marked as a duplicate of this bug. ***
*** Bug 380209 has been marked as a duplicate of this bug. ***
*** Bug 380614 has been marked as a duplicate of this bug. ***
*** Bug 382162 has been marked as a duplicate of this bug. ***
100% reproducible steps for reproducing a similar backtrace to the ones mentioned in this bug under Ubuntu Edgy have been attached to https://bugs.launchpad.net/distros/ubuntu/+source/firefox/+bug/74576
(In reply to comment #71) > 100% reproducible steps for reproducing a similar backtrace to the ones > mentioned in this bug under Ubuntu Edgy have been attached to > https://bugs.launchpad.net/distros/ubuntu/+source/firefox/+bug/74576 Steps to reproduce: 1. Start firefox. 2. Go to http://fedoraproject.org/wiki/RenderingProject/aiglx#head-7c28114d7bfca3fd27da422f9bd36de8f8d41703 . 3. Click on the "Minimization" link. 4. After the video has played press the back button at the top of the window. 5. Start gnome-theme-manager . 6. Change the theme from Human to Industrial Tango. Expected results: Window decoration and widgets to change shape/colour across all open gtk programs. Actual results: Decoration and widgets change in all gtk programs bar firefox. Firefox crashes with a segfault and prints the following in ~/.xsession-errors: " ** Message: plugin_destroy totemBasicPlugin dtor [0x8824858] (Gecko:9018): Gdk-CRITICAL **: gdk_colormap_get_screen: assertion GDK_IS_COLORMAP (cmap)' failed (Gecko:9018): GLib-GObject-CRITICAL **: g_object_ref: assertion `G_IS_OBJECT (object)' failed (Gecko:9018): Gdk-CRITICAL **: gdk_colormap_get_visual: assertion GDK_IS_COLORMAP (colormap)' failed " How reproducible is the problem? It is reproducible 100% of the time. Version information: Ubuntu Edgy firefox 2.0+0dfsg-0ubuntu3 libgtk2.0-0 2.10.6-0ubuntu1
See comment 60, this is filed upstream.
*** Bug 384196 has been marked as a duplicate of this bug. ***
Andrew's steps crash epiphany too.
*** Bug 386234 has been marked as a duplicate of this bug. ***
*** Bug 386663 has been marked as a duplicate of this bug. ***
*** Bug 386046 has been marked as a duplicate of this bug. ***
*** Bug 390660 has been marked as a duplicate of this bug. ***
*** Bug 391487 has been marked as a duplicate of this bug. ***
*** Bug 391689 has been marked as a duplicate of this bug. ***
*** Bug 393056 has been marked as a duplicate of this bug. ***
*** Bug 393321 has been marked as a duplicate of this bug. ***
last duplicate is 2.17.4
*** Bug 393561 has been marked as a duplicate of this bug. ***
*** Bug 394639 has been marked as a duplicate of this bug. ***
*** Bug 395033 has been marked as a duplicate of this bug. ***
*** Bug 395254 has been marked as a duplicate of this bug. ***
*** Bug 395407 has been marked as a duplicate of this bug. ***
*** Bug 398279 has been marked as a duplicate of this bug. ***
*** Bug 398597 has been marked as a duplicate of this bug. ***
*** Bug 399687 has been marked as a duplicate of this bug. ***
*** Bug 399800 has been marked as a duplicate of this bug. ***
*** Bug 400604 has been marked as a duplicate of this bug. ***
*** Bug 400821 has been marked as a duplicate of this bug. ***
*** Bug 402692 has been marked as a duplicate of this bug. ***
*** Bug 402892 has been marked as a duplicate of this bug. ***
*** Bug 403480 has been marked as a duplicate of this bug. ***
*** Bug 403484 has been marked as a duplicate of this bug. ***
*** Bug 403727 has been marked as a duplicate of this bug. ***
*** Bug 404190 has been marked as a duplicate of this bug. ***
*** Bug 405395 has been marked as a duplicate of this bug. ***
*** Bug 405502 has been marked as a duplicate of this bug. ***
*** Bug 405891 has been marked as a duplicate of this bug. ***
*** Bug 406013 has been marked as a duplicate of this bug. ***
*** Bug 407047 has been marked as a duplicate of this bug. ***
*** Bug 407807 has been marked as a duplicate of this bug. ***
*** Bug 407849 has been marked as a duplicate of this bug. ***
*** Bug 408418 has been marked as a duplicate of this bug. ***
Just for reference, the widget that has a widget->window with NULL colourmap is a GtkSocket that has been destroyed.
*** Bug 413062 has been marked as a duplicate of this bug. ***
*** Bug 395264 has been marked as a duplicate of this bug. ***
*** Bug 413077 has been marked as a duplicate of this bug. ***
*** Bug 413331 has been marked as a duplicate of this bug. ***
*** Bug 415474 has been marked as a duplicate of this bug. ***
*** Bug 411908 has been marked as a duplicate of this bug. ***
*** Bug 411108 has been marked as a duplicate of this bug. ***
*** Bug 411570 has been marked as a duplicate of this bug. ***
*** Bug 415995 has been marked as a duplicate of this bug. ***
This should at least not occur anymore when using the totem plugin (>= 2.18.0), since totem was fixed in bug 415389. It still might occur with other plugins that use NPPVpluginKeepLibraryInMemory. At least this should be uncommon; google codesearch didn't find anything beside totem-plugin. I'll close this; the upstream bug is https://bugzilla.mozilla.org/show_bug.cgi?id=359870 .
*** Bug 417153 has been marked as a duplicate of this bug. ***
*** Bug 417588 has been marked as a duplicate of this bug. ***
*** Bug 418172 has been marked as a duplicate of this bug. ***
*** Bug 418248 has been marked as a duplicate of this bug. ***
*** Bug 419930 has been marked as a duplicate of this bug. ***
*** Bug 420450 has been marked as a duplicate of this bug. ***
*** Bug 421235 has been marked as a duplicate of this bug. ***
*** Bug 421617 has been marked as a duplicate of this bug. ***
*** Bug 422050 has been marked as a duplicate of this bug. ***
*** Bug 423068 has been marked as a duplicate of this bug. ***
*** Bug 423073 has been marked as a duplicate of this bug. ***
*** Bug 423457 has been marked as a duplicate of this bug. ***
*** Bug 420789 has been marked as a duplicate of this bug. ***
*** Bug 417723 has been marked as a duplicate of this bug. ***
*** Bug 417546 has been marked as a duplicate of this bug. ***
*** Bug 416073 has been marked as a duplicate of this bug. ***
*** Bug 414525 has been marked as a duplicate of this bug. ***
*** Bug 424294 has been marked as a duplicate of this bug. ***
*** Bug 425026 has been marked as a duplicate of this bug. ***
*** Bug 422167 has been marked as a duplicate of this bug. ***
*** Bug 427103 has been marked as a duplicate of this bug. ***
*** Bug 428991 has been marked as a duplicate of this bug. ***
*** Bug 429032 has been marked as a duplicate of this bug. ***
*** Bug 429146 has been marked as a duplicate of this bug. ***
*** Bug 429975 has been marked as a duplicate of this bug. ***
*** Bug 429357 has been marked as a duplicate of this bug. ***
*** Bug 429540 has been marked as a duplicate of this bug. ***
*** Bug 430267 has been marked as a duplicate of this bug. ***
*** Bug 430312 has been marked as a duplicate of this bug. ***
*** Bug 430135 has been marked as a duplicate of this bug. ***
*** Bug 431924 has been marked as a duplicate of this bug. ***
*** Bug 435710 has been marked as a duplicate of this bug. ***
*** Bug 436112 has been marked as a duplicate of this bug. ***
*** Bug 437054 has been marked as a duplicate of this bug. ***
*** Bug 438160 has been marked as a duplicate of this bug. ***
*** Bug 439541 has been marked as a duplicate of this bug. ***
*** Bug 439777 has been marked as a duplicate of this bug. ***
*** Bug 441753 has been marked as a duplicate of this bug. ***
*** Bug 445355 has been marked as a duplicate of this bug. ***
*** Bug 469059 has been marked as a duplicate of this bug. ***
*** Bug 478472 has been marked as a duplicate of this bug. ***
*** Bug 485907 has been marked as a duplicate of this bug. ***
*** Bug 489239 has been marked as a duplicate of this bug. ***
*** Bug 491412 has been marked as a duplicate of this bug. ***
removed from auto-reject list
*** Bug 500980 has been marked as a duplicate of this bug. ***
*** Bug 504044 has been marked as a duplicate of this bug. ***
Andre, why did you remove this from the auto-reject list?
reinout, because there hadn't been any rejected reports for weeks, and because we want to keep the number of auto-reject bugs manageable.
sorry for not posting figures when i removed it: 2007-07-10: 2 rejected bugs. 2007-11-18: still 2 rejected bugs. no reason to keep this one.
*** Bug 509878 has been marked as a duplicate of this bug. ***
*** Bug 523659 has been marked as a duplicate of this bug. ***
*** Bug 524233 has been marked as a duplicate of this bug. ***
*** Bug 531772 has been marked as a duplicate of this bug. ***
*** Bug 533655 has been marked as a duplicate of this bug. ***
*** Bug 534237 has been marked as a duplicate of this bug. ***
The mozilla bug says this is fixed in Firefox 3, but I just ran into it using xulrunner 1.9 beta 5.
Sam Morris: please reopen the mozilla bug then.
*** Bug 538522 has been marked as a duplicate of this bug. ***
There doesn't appear to be any way for mere mortals to reopen Mozilla bugs.
Upstream says this is a GTK+ bug, can someone please re-open and reassign it. https://bugzilla.mozilla.org/show_bug.cgi?id=359870#c24
The bug just does not happen anymore. No new duplicates for ages now. If you can still reproduce it, please provide a stacktrace and the exact versions of gtk+ and mozilla/xulrunner/forefox/whatever you are using.
It still happens to me, details on Mozilla's bugzilla. Hopefully someone there will work out WTF is going on.
Ah come on, posting them here too isn't that hard... ;-) "And I ran into this again with GTK+ 2.12.11. Oh, and xulrunner 1.9.0.1 this time. backtrace with gtk 2.12.11 and xulrunner 1.9.0.1: https://bugzilla.mozilla.org/attachment.cgi?id=333248 " Sam, do you use totem and is it used for displaying media content in firefox? which totem backend (xine, gstreamer)? which distro at all?
Totem eh... I'm using the Mozilla plug-in from version 2.22.2. GStreamer backend, on a Debian testing/unstable system.
what is "the Mozilla plug-in"? Something that totem ships? Which GStreamer version is installed, which totem version is installed?
It's a netscape browser plugin that totem ships: http://packages.debian.org/totem-mozilla from totem 2.22.2. Installed, I have: gstreamer 0.10.20 gst-plugins-good 0.10.8 gst-plugins-bad 0.10.7 gst-plugins-ugly 0.10.8 gst-plugins-base 0.10.19
*** Bug 551140 has been marked as a duplicate of this bug. ***
*** Bug 566478 has been marked as a duplicate of this bug. ***
*** Bug 571545 has been marked as a duplicate of this bug. ***
*** Bug 574606 has been marked as a duplicate of this bug. ***
*** Bug 575560 has been marked as a duplicate of this bug. ***
*** Bug 576209 has been marked as a duplicate of this bug. ***
*** Bug 576297 has been marked as a duplicate of this bug. ***
*** Bug 576258 has been marked as a duplicate of this bug. ***
*** Bug 589061 has been marked as a duplicate of this bug. ***
*** Bug 594207 has been marked as a duplicate of this bug. ***