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 404114 - crash in Archive Manager: Working within a gnome-t...
crash in Archive Manager: Working within a gnome-t...
Status: RESOLVED DUPLICATE of bug 363472
Product: file-roller
Classification: Applications
Component: general
2.16.x
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2007-02-03 23:15 UTC by rembert
Modified: 2007-02-04 13:58 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description rembert 2007-02-03 23:15:46 UTC
Version: 2.16.1

What were you doing when the application crashed?
Working within a gnome-terminal. I had some source file opened using vim and was scrolling downwards using the arrow-down key. Nothing more, nothing less.


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 81207296 vsize: 0 resident: 81207296 share: 0 rss: 17473536 rss_rlim: 0
CPU usage: start_time: 1170544249 rtime: 0 utime: 285 stime: 0 cutime:263 cstime: 0 timeout: 22 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/file-roller'

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224718672 (LWP 25830)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1224718672 (LWP 25830))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_file_info_get_is_folder
    from /usr/lib/libgtk-x11-2.0.so.0
  • #5 _gtk_file_chooser_default_new
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 gtk_tree_model_filter_convert_child_iter_to_iter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 gtk_tree_model_sort_convert_iter_to_child_iter
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 _gtk_marshal_VOID__BOXED_BOXED
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #13 gtk_tree_model_row_inserted
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 _gtk_file_system_model_get_info
    from /usr/lib/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__POINTER
    from /usr/lib/libgobject-2.0.so.0
  • #16 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #17 g_signal_chain_from_overridden
    from /usr/lib/libgobject-2.0.so.0
  • #18 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #19 g_signal_emit_by_name
    from /usr/lib/libgobject-2.0.so.0
  • #20 fs_module_create
    from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
  • #21 gnome_vfs_monitor_callback
    from /usr/lib/libgnomevfs-2.so.0
  • #22 g_source_is_destroyed
    from /usr/lib/libglib-2.0.so.0
  • #23 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #24 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #25 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #26 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #27 ??
  • #28 ??
  • #29 ??
  • #0 __kernel_vsyscall

Comment 1 rembert 2007-02-03 23:26:09 UTC
As the bugreporter didn't tell anything regarding the application that crashed, nor did the details provide enough details, I probably gave some wrong info.

Just after submitting the bug, a ZIP window closed unsuspectely while my gnome-terminal with vim stayed alive. The ZIP window had a dialog open to be used to expand some selected file.
Comment 2 palfrey 2007-02-04 13:58:40 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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