GNOME Bugzilla – Bug 311068
Mini-Commander Quit Unexpectedly
Last modified: 2007-04-10 14:34:54 UTC
Distribution: Debian testing/unstable Package: gnome-applets Severity: normal Version: GNOME2.10.2 0 Gnome-Distributor: Debian Synopsis: Mini-Commander Quit Unexpectedly Bugzilla-Product: gnome-applets Bugzilla-Component: mini-commander Bugzilla-Version: 0 BugBuddy-GnomeVersion: 2.0 (2.10.1) Description: Description of the crash: Click on history item, got error dialog However, the requested program was run as it should be Steps to reproduce the crash: 1. Click on history item ("gksu aegis-virus-scanner '/'") 2. 3. Expected Results: Prompt for root password, run virus scan How often does this happen? don't know Additional Information: Debugging Information: Backtrace was generated from '/usr/libexec/mini_commander_applet' Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (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) [Thread debugging using libthread_db enabled] [New Thread -1222254464 (LWP 9289)] 0xffffe410 in ?? ()
+ Trace 61896
Thread 1 (Thread -1222254464 (LWP 9289))
------- Bug moved to this database by unknown@gnome.bugs 2005-07-21 01:26 UTC ------- Unknown version 0 in product gnome-applets. Setting version to "unspecified". The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was superbiskit@cox.net.
Happens with 2.11.90 sometimes
*** Bug 311234 has been marked as a duplicate of this bug. ***
Created attachment 51050 [details] [review] .pa -- atch. Both of these bugs happen because their respective signal handlers destroy the treeview and then proceed to return FALSE (ie: telling glib to continue propagating the signal to the default handler of the just-destroyed treeview). We return TRUE instead to stop the signal from being handled further. I wonder, though, if GTK should maybe be doing this on its own... ?
*** Bug 311185 has been marked as a duplicate of this bug. ***
Created attachment 51053 [details] [review] re! By the principle of least force, I like this one better. Only cancel event proagation in the event that the widget is actually destroyed -- otherwise, continue as before.
Please ignore the preferences.c part. That belongs to bug #313359 :P
Seems sane. Make it so, Mr Lortie.
Fixed in HEAD.
*** Bug 315464 has been marked as a duplicate of this bug. ***
*** Bug 341940 has been marked as a duplicate of this bug. ***
*** Bug 419471 has been marked as a duplicate of this bug. ***