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 106582 - gnome-panel crashes and won't restart after running file-roller from command line
gnome-panel crashes and won't restart after running file-roller from command ...
Status: RESOLVED DUPLICATE of bug 111147
Product: gnome-vfs
Classification: Deprecated
Component: Other
unspecified
Other other
: High critical
: ---
Assigned To: gnome-vfs maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2003-02-20 02:23 UTC by psahm
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.1/2.2


Description psahm 2003-02-20 02:24:24 UTC 
Package: gnome-panel
Severity: major
Version: GNOME2.2.0 2.2.0.1
os_details: Gnome.Org
Synopsis: gnome-panel crashes and won't restart after running file-roller from command line
Bugzilla-Product: gnome-panel
Bugzilla-Component: Panel
BugBuddy-GnomeVersion: 2.0 (2.2.0.1)
Description:
Description of Problem:
gnome-panel crashed and will not restart after running fiile-roller from
the command line. The stack trace shows the file that was created and
subsequently deleted.

Steps to reproduce the problem:
1.  from commnd prompt enter: file-roller -a <non-existent_file.tar.gz>
<file_list> (in my case it was "file-roller -a test.tar.gz ATT*" The
files were a bunch of jpegs.
2. panel will crash
3. kill X, re-login, gnome-panel crashes

Actual Results:


Expected Results:


How often does this happen?


Additional Information:



Debugging Information:

Backtrace was generated from '/home/psahm/garnome/bin/gnome-panel'

[New Thread 1024 (LWP 29219)]
0x420b4769 in wait4 () from /lib/i686/libc.so.6

+ Trace 34039

Thread 1 (Thread 1024 (LWP 29219))

  • #0 wait4
    from /lib/i686/libc.so.6
  • #1 __DTOR_END__
    from /lib/i686/libc.so.6
  • #2 waitpid
    from /lib/i686/libpthread.so.0
  • #3 libgnomeui_segv_handle
    at gnome-ui-init.c line 646
  • #4 pthread_sighandler
    from /lib/i686/libpthread.so.0
  • #5 <signal handler called>
  • #6 strlen
    from /lib/i686/libc.so.6
  • #7 FAMDebugLevel
    from /usr/lib/libfam.so.0
  • #8 FAMMonitorFile
    from /usr/lib/libfam.so.0
  • #9 do_monitor_add
    at file-method.c line 2200
  • #10 _gnome_vfs_monitor_do_add
    at gnome-vfs-monitor.c line 84
  • #11 gnome_vfs_monitor_add
    at gnome-vfs-ops.c line 764
  • #12 egg_recent_model_monitor_list
    at egg-recent-model.c line 628
  • #13 egg_recent_model_changed
    at egg-recent-model.c line 1631
  • #14 egg_recent_view_set_model
    at egg-recent-view.c line 67
  • #15 panel_recent_append_documents_menu
    at panel-recent.c line 173
  • #16 append_actions_menu
    at foobar-widget.c line 208
  • #17 foobar_widget_instance_init
    at foobar-widget.c line 756
  • #18 g_type_create_instance
    at gtype.c line 1419
  • #19 g_object_constructor
    at gobject.c line 827
  • #20 g_object_newv
    at gobject.c line 725
  • #21 g_object_new_valist
    at gobject.c line 764
  • #22 g_object_new
    at gobject.c line 618
  • #23 foobar_widget_new
    at foobar-widget.c line 898
  • #24 panel_load_panel_from_gconf
    at panel.c line 2441
  • #25 panel_load_panels_from_gconf
    at panel.c line 2588
  • #26 session_load
    at session.c line 348
  • #27 main
    at main.c line 201
  • #28 __libc_start_main
    from /lib/i686/libc.so.6
  • #0 wait4
    from /lib/i686/libc.so.6 




------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-02-19 21:24 -------

The original reporter (psahm@usadatanet.net) of this bug does not have an account here.
Reassigning to the exporter, unknown@bugzilla.gnome.org.
Reassigning to the default owner of the component, gnome-panel-maint@bugzilla.gnome.org.
Comment 1 Elijah Newren 2003-02-20 06:06:09 UTC 
Appears to be a unique stack trace, according to the
simple-dup-finder.  Setting version->2.2.x, marking priority->high &
severity->critical (it's a crasher), adding GNOMEVER2.2 and bugsquad
keywords, and marking as new.
Comment 2 Mark McLoughlin 2003-03-10 01:19:45 UTC 
looks like another FAM/gnome-vfs bug triggered by the recent files menu.
Comment 3 Christophe Fergeau 2003-06-28 20:56:59 UTC 

*** This bug has been marked as a duplicate of 111147 ***