Bug 363200 – crash in Archive Manager: I opened 20 file-roller'...

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 363200 - crash in Archive Manager: I opened 20 file-roller'...


Summary:	crash in Archive Manager: I opened 20 file-roller'...


Status:	RESOLVED DUPLICATE of bug 349697

Product:	file-roller
Classification:	Applications
Component:	general
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Paolo Bacchilega
QA Contact:	file-roller-maint

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-18 17:47 UTC by Sander Thijsen
Modified:	2006-10-18 21:07 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description Sander Thijsen 2006-10-18 17:47:06 UTC

Version: 2.16.1

What were you doing when the application crashed?
I opened 20 file-roller's at one time (accidentally).


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

Memory status: size: 49618944 vsize: 0 resident: 49618944 share: 0 rss: 20492288 rss_rlim: 0
CPU usage: start_time: 1161193407 rtime: 0 utime: 260 stime: 0 cutime:240 cstime: 0 timeout: 20 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 -1225685328 (LWP 23621)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 77015

Thread 1 (Thread -1225685328 (LWP 23621))

#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_menu_shell_insert
from /usr/lib/libgtk-x11-2.0.so.0
#5 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#6 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#7 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#8 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#9 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#10 _gtk_menu_is_empty
from /usr/lib/libgtk-x11-2.0.so.0
#11 gtk_ui_manager_get_ui
from /usr/lib/libgtk-x11-2.0.so.0
#12 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#13 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#14 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#15 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#16 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#17 ??
#18 ??
#19 ??
#0 __kernel_vsyscall

Comment 1 Karsten Bräckelmann 2006-10-18 21:07:01 UTC

Thanks for taking the time to report this bug.

This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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