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 97451 - Crashes when changing Gnome2 development application font preferences
Crashes when changing Gnome2 development application font preferences
Status: RESOLVED FIXED
Product: gtk+
Classification: Platform
Component: Widget: Other
2.1.x
Other Linux
: Low normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks: 99281
 
 
Reported: 2002-11-02 00:30 UTC by Simon Wong
Modified: 2011-02-04 16:11 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
test case for crash (485 bytes, patch)
2002-11-18 23:27 UTC, Bastien Nocera
none Details | Review

Description Simon Wong 2002-11-02 00:29:16 UTC
Package: acme
Severity: normal
Version: 1.99.9
Synopsis: Crashes when changing Gnome application font preferences
Bugzilla-Product: acme
Bugzilla-Component: general
BugBuddy-GnomeVersion: 2.0 (2.1.1)

Description:
Description of Problem:

When I change the "application font" in the font preferences app/dialog
acme crashes straight afterwards.

Steps to reproduce the problem:
1. acme running
2. choose Applications>Desktop Preferences>Font
3. change the Application Font to anything.

Actual Results:

Font changes in other applications.

Acme crashes.

Expected Results:

No crash!

How often does this happen?

Each time.

Additional Information:

Built with Garnome 0.18.3.



Debugging Information:

Backtrace was generated from '/usr/local/garnome-0.18.3/bin/acme'

[New Thread 1024 (LWP 2003)]
0x40860609 in wait4 () from /lib/libc.so.6

Thread 1 (Thread 1024 (LWP 2003))

  • #0 wait4
    from /lib/libc.so.6
  • #1 __check_rhosts_file
    from /lib/libc.so.6
  • #2 waitpid
    from /lib/libpthread.so.0
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 646
  • #4 sigaction
    from /lib/libc.so.6
  • #5 g_log
    at gmessages.c line 526
  • #6 ??
  • #7 ??
  • #0 wait4
    from /lib/libc.so.6

-- 
**************
* Simon Wong *
**************




------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-11-01 19:29 -------

Reassigning to the default owner of the component, hadess@hadess.net.

Comment 1 Bastien Nocera 2002-11-02 22:30:53 UTC
I could reproduce it with Gtk+ 2.1.1.
This looks like a bug in Gtk+.

Reassigning.
Comment 2 Owen Taylor 2002-11-05 00:34:48 UTC
Hadess - there is no useful backtrace or further information here;
"install ACME" is not really an acceptable reproduction mechanism.
Since other apps don't crash, without further information, I'd
have to guess it is an ACME bug.

Comment 3 Simon Wong 2002-11-05 01:09:32 UTC
Okay - I noticed the backtrace looked pretty lame but I'm no guru and
it's what BugBuddy gave me.

I'm rebuilding my Gnome2 Development stuff from Garnome 0.18.3 again
so will try again and deliver some better information.

Thanks.
Comment 4 Owen Taylor 2002-11-06 20:09:19 UTC
Without accurate backtrace or non-ACME reproduction, there
is really nothing we can do from the GTK+ end.
Comment 5 Bastien Nocera 2002-11-06 20:28:32 UTC
When changing the font, or the theme:

  • #0 kill
    from /lib/libc.so.6
  • #1 pthread_kill
    from /lib/libpthread.so.0
  • #2 raise
    from /lib/libpthread.so.0
  • #3 g_logv
    at gmessages.c line 503
  • #4 g_log
    at gmessages.c line 526
  • #5 gtk_main_do_event
    at gtkmain.c line 1550
  • #6 gdk_event_dispatch
    at gdkevents-x11.c line 1880
  • #7 g_main_dispatch
    at gmain.c line 1617
  • #8 g_main_context_dispatch
    at gmain.c line 2161
  • #9 g_main_context_iterate
    at gmain.c line 2242
  • #10 g_main_loop_run
    at gmain.c line 2462
  • #11 gtk_main
    at gtkmain.c line 1107
  • #12 main
    at acme.c line 935
  • #13 __libc_start_main
    from /lib/libc.so.6

I'll be trying to create a short test case later on.
Comment 6 Owen Taylor 2002-11-06 21:09:40 UTC
Stack trace doesn't say anything to me but "something scribbled
all over memory" and everything is all messed up.
Comment 7 Owen Taylor 2002-11-06 23:16:31 UTC
Unless we get a better test case, it is going to have to
be debugged by someone who runs acme.
Comment 8 Jeff Waugh 2002-11-15 22:48:32 UTC
Just to throw in my experiences with it - acme seems to crash on GTK+
theme change and font change. Happens with and without crack
optimisations (GARNOME defaults to just a sane -O2, though).
Comment 9 Bastien Nocera 2002-11-18 23:27:57 UTC
Created attachment 12383 [details] [review]
test case for crash
Comment 10 Bastien Nocera 2002-11-18 23:30:36 UTC
Owen, this is a pretty grave problem, if I want acme to be in the 2.2
release. Can you adjust severity and all and tell me what I should
expect ?
Comment 11 Luis Villa 2002-11-22 14:59:11 UTC
Reopening, as the ball is back in Owen's court, AFAICS.
Comment 12 Owen Taylor 2002-11-22 15:30:45 UTC
I guess I expect that if you can reproduce the problem, you
can debug it...  there is nothing I can really say beyond
that; it could be a GTK+ bug, it could be an ACME bug ...
there really is no information in this report that would
allow me do determine the question. (Except that it oly
happens for ACME)
Comment 13 Bastien Nocera 2002-11-22 15:38:54 UTC
Owen, I attached a test case to this bug, with code that works fine
with gtk+ 2.0 and doesn't with gtk+ 2.1.

I'm afraid it's the same bug that's hitting the panel transparency
stuff. That would make at least 2 of us.
Comment 14 Owen Taylor 2002-11-22 16:03:05 UTC
Sorry, missed the test case.

I'll fix up the problem; not very hard. (Just move the
the GDK_SETTINGS check before the check for not having
an event widget) Though it's pretty clearly a "don't do 
that then!" problem. Use an event filter. Clearly 
redirecting events from the root window to another widget
has a good potential to confuse GTK+.

I don't know what the "panel transparency stuff" does;
I hope it doesn't do that.

Comment 15 Bastien Nocera 2002-11-22 16:15:58 UTC
Sorry, it's black magic that used to work in gtk+ 2.0.x, and I guess
I've become too used to warnings from gtk+ when I'm doing something
wrong :)
Comment 16 Bastien Nocera 2002-11-22 16:16:47 UTC
Sorry for the spam
Comment 17 Bastien Nocera 2002-12-10 00:50:25 UTC
I fixed the bug properly in acme already. A warning rather than a crash for the other (potential) apps would still be good though.
Comment 18 Simon Wong 2002-12-11 05:58:33 UTC
I'm closing this as it's no longer happening in ACME 1.99.10 - thanks!
Comment 19 Owen Taylor 2002-12-11 13:18:10 UTC
There was an couple line GTK+ code change I could make in
case other programs were doing something similar;
reopening.
Comment 20 Owen Taylor 2002-12-12 23:09:06 UTC
Thu Dec 12 18:02:34 2002  Owen Taylor  <otaylor@redhat.com>

        * gtk/gtkmain.c (gtk_main_do_event): Intercept events
        of type GDK_SETTING before we check to see if there
        was an event widget or not. (#97451, Simon Wong,
        Bastien Nocera)