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 311068 - Mini-Commander Quit Unexpectedly
Mini-Commander Quit Unexpectedly
Status: RESOLVED FIXED
Product: gnome-applets
Classification: Other
Component: mini-commander
2.11.x
Other other
: High critical
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
: 311185 311234 315464 341940 419471 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2005-07-21 01:26 UTC by superbiskit
Modified: 2007-04-10 14:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Attachments
.pa -- atch. (994 bytes, patch)
2005-08-21 04:17 UTC, Allison Karlitskaya (desrt)
none Details | Review
re! (1.85 KB, patch)
2005-08-21 05:27 UTC, Allison Karlitskaya (desrt)
committed Details | Review

Description superbiskit 2005-07-21 01:26:45 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 ?? ()

Thread 1 (Thread -1222254464 (LWP 9289))

  • #0 ??
  • #1 ??
  • #2 ??
  • #3 ??
  • #4 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #5 libgnomeui_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #6 <signal handler called>
  • #7 IA__gtk_window_group_add_window
    at gtkwindow.c line 6775
  • #8 gtk_tree_view_ensure_interactive_directory
    at gtktreeview.c line 8951
  • #9 gtk_tree_view_key_press
    at gtktreeview.c line 4381
  • #10 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #11 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #13 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #14 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #15 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #16 gtk_widget_event_internal
    at gtkwidget.c line 3631
  • #17 IA__gtk_window_propagate_key_event
    at gtkwindow.c line 4429
  • #18 gtk_window_key_press_event
    at gtkwindow.c line 4459
  • #19 _gtk_marshal_BOOLEAN__BOXED
    at gtkmarshalers.c line 83
  • #20 g_cclosure_new_swap
    from /usr/lib/libgobject-2.0.so.0
  • #21 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #22 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #23 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #24 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #25 gtk_widget_event_internal
    at gtkwidget.c line 3631
  • #26 IA__gtk_propagate_event
    at gtkmain.c line 2130
  • #27 IA__gtk_main_do_event
    at gtkmain.c line 1394
  • #28 gdk_event_dispatch
    at gdkevents-x11.c line 2259
  • #29 g_main_depth
    from /usr/lib/libglib-2.0.so.0
  • #30 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #31 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #32 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #33 bonobo_main
    from /usr/lib/libbonobo-2.so.0
  • #34 bonobo_generic_factory_main_timeout
    from /usr/lib/libbonobo-2.so.0
  • #35 bonobo_generic_factory_main
    from /usr/lib/libbonobo-2.so.0
  • #36 panel_applet_factory_main_closure
    from /usr/lib/libpanel-applet-2.so.0
  • #37 panel_applet_factory_main
    from /usr/lib/libpanel-applet-2.so.0
  • #38 main
  • #0 ??




------- 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.

Comment 1 Sebastien Bacher 2005-08-07 21:39:50 UTC
Happens with 2.11.90 sometimes
Comment 2 Allison Karlitskaya (desrt) 2005-08-21 04:13:34 UTC
*** Bug 311234 has been marked as a duplicate of this bug. ***
Comment 3 Allison Karlitskaya (desrt) 2005-08-21 04:17:28 UTC
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... ?
Comment 4 Allison Karlitskaya (desrt) 2005-08-21 04:20:25 UTC
*** Bug 311185 has been marked as a duplicate of this bug. ***
Comment 5 Allison Karlitskaya (desrt) 2005-08-21 05:27:37 UTC
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.
Comment 6 Allison Karlitskaya (desrt) 2005-08-21 05:28:37 UTC
Please ignore the preferences.c part.  That belongs to bug #313359 :P
Comment 7 Danielle Madeley 2005-08-21 11:53:18 UTC
Seems sane. Make it so, Mr Lortie.
Comment 8 Allison Karlitskaya (desrt) 2005-08-21 15:28:46 UTC
Fixed in HEAD.
Comment 9 Allison Karlitskaya (desrt) 2005-09-07 16:03:14 UTC
*** Bug 315464 has been marked as a duplicate of this bug. ***
Comment 10 Fabio Bonelli 2006-05-16 09:13:37 UTC
*** Bug 341940 has been marked as a duplicate of this bug. ***
Comment 11 Kjartan Maraas 2007-04-10 14:34:54 UTC
*** Bug 419471 has been marked as a duplicate of this bug. ***