GNOME Bugzilla – Bug 453419
Crash in Gnome-about 2.18.2 repeatedly after about 30 seconds (without touching a thing)
Last modified: 2007-07-04 07:19:15 UTC
Distribution: Debian lenny/sid Package: gnome-desktop Severity: critical Version: GNOME2.18.2 unspecified Gnome-Distributor: Debian Synopsis: Crash in Gnome-about 2.18.2 repeatedly after about 30 seconds (without touching a thing) Bugzilla-Product: gnome-desktop Bugzilla-Component: gnome-about Steps to reproduce the crash: 1. Start Gnome-about 2. Wait about 30 seconds Expected Results: After Brought to you By: and the first (random) name has faded away it crashes and starts the bug reporter. How often does this happen? Every time. Additional Information: Earlier bugs that have been reported (for version 2.16.1 on Ubuntu) http://bugzilla.gnome.org/show_bug.cgi?id=388423 http://bugzilla.gnome.org/show_bug.cgi?id=421169 were moved to pango. I disagree with this action and would prefer to see gnome-about removing the dependency to weird fonts from the component. It's ridiculously flashy/complex for an about box. The links also don't work for me and the version it displays is not even the version of Gnome (which you would sanely expect for an about box) but it's own version number! %-) Regards, Pete -- Backtrace was generated from '/usr/bin/gnome-about' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1224652480 (LWP 2859)] (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) 0xb7da2aee in __waitpid_nocancel () from /lib/libpthread.so.0
+ Trace 145489
Thread 1 (Thread -1224652480 (LWP 2859))
(In reply to comment #0) > Earlier bugs that have been reported (for version 2.16.1 on Ubuntu) > > http://bugzilla.gnome.org/show_bug.cgi?id=388423 > http://bugzilla.gnome.org/show_bug.cgi?id=421169 > > were moved to pango. I disagree with this action and would prefer to see > gnome-about removing the dependency to weird fonts from the component. It's > ridiculously flashy/complex for an about box. The links also don't work for me > and the version it displays is not even the version of Gnome (which you would > sanely expect for an about box) but it's own version number! %-) The crash is definitely a pango/cairo bug, there's nothing we can do about it (and we're not using any weird font). A redesign of gnome-about is planned, but we need people with time to turn it into reality. And it does display the GNOME version number, which is data coming from gnome-desktop. If the packages in sid are not all in sync, there's nothing we can do. *** This bug has been marked as a duplicate of 431990 ***
> A redesign of gnome-about is planned, but we need people with time to turn it > into reality. Ah ok, I understand. I'm afraid I don't have the time or skills to help you there. > And it does display the GNOME version number, which is data > coming from gnome-desktop. If the packages in sid are not all in sync, there's > nothing we can do. Ok fair enough, I'll see if I can help sort out the Debian side of things. I won't reopen this bug, I'll leave that up to you, but I find it strange that this bug gets tagged as STATUS: resolved as it obviously hasn't been yet, it's just been moved to the dependency that is causing the problem. Thanks for your help, Pete
(In reply to comment #2) > I won't reopen this bug, I'll leave that up to you, but I find it strange that > this bug gets tagged as STATUS: resolved as it obviously hasn't been yet, it's > just been moved to the dependency that is causing the problem. I don't understand: there's no bug in gnome-about for this crash: the bug is in cairo and has been reported there (and is fixed in 1.4.8).
(In reply to comment #3) > (In reply to comment #2) > > I won't reopen this bug, I'll leave that up to you, but I find it strange that > > this bug gets tagged as STATUS: resolved as it obviously hasn't been yet, it's > > just been moved to the dependency that is causing the problem. > > I don't understand: there's no bug in gnome-about for this crash: the bug is in > cairo and has been reported there (and is fixed in 1.4.8). In developer-speak there may be no bug in the gnome-about code, but in user-speak there certainly is a bug in the gnome-about application, due to there being one in one of it's dependencies. This isn't just being pedantic either, it has a practical use: when someone comes across the crash in gnome-about they should eventually end up at this page [http://bugzilla.gnome.org/buglist.cgi?product=gnome-desktop&bug_status=NEW&bug_status=REOPENED&bug_status=ASSIGNED&bug_status=UNCONFIRMED&component=gnome-about] to see if a critical bug report has already been made. The way these reports are being moved and tagged STATUS:resolved no-one will see them and they will once again take the time to file another, which to me is a waste of people's time and leads to the large numbers op duplicates seen here [http://bugzilla.gnome.org/show_bug.cgi?id=431990]. Anyway, glad to hear that a fix is on the way! :-)