Bug 433880 – crash in Archive Manager: Standing up and then set...

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 433880 - crash in Archive Manager: Standing up and then set...


Summary:	crash in Archive Manager: Standing up and then set...


Status:	RESOLVED DUPLICATE of bug 373226

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:	2007-04-27 14:35 UTC by dsabo5
Modified:	2007-05-05 16:59 UTC

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

Description dsabo5 2007-04-27 14:35:56 UTC

Version: 2.16.1

What were you doing when the application crashed?
Standing up and then setting down at my computer table.


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

Memory status: size: 192987136 vsize: 192987136 resident: 22073344 share: 14282752 rss: 22073344 rss_rlim: -1
CPU usage: start_time: 1177676252 rtime: 569 utime: 536 stime: 33 cutime:1201 cstime: 79 timeout: 0 it_real_value: 0 frequency: 100

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

(no debugging symbols found)
Using host libthread_db library "/lib/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 47541385397952 (LWP 8664)]
(no debugging symbols found)
0x00002b3d1349feef in waitpid () from /lib/libpthread.so.0

+ Trace 130907

Thread 1 (Thread 47541385397952 (LWP 8664))

#0 waitpid
from /lib/libpthread.so.0
#1 gnome_gtk_module_info_get
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 raise
from /lib/libc.so.6
#4 abort
from /lib/libc.so.6
#5 g_logv
from /usr/lib64/libglib-2.0.so.0
#6 g_log
from /usr/lib64/libglib-2.0.so.0
#7 g_assert_warning
from /usr/lib64/libglib-2.0.so.0
#8 fs_module_create
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#9 g_object_unref
from /usr/lib64/libgobject-2.0.so.0
#10 fs_module_init
from /usr/lib/gtk-2.0/2.10.0/filesystems/libgnome-vfs.so
#11 gnome_vfs_connect_to_server
from /usr/lib64/libgnomevfs-2.so.0
#12 g_main_context_dispatch
from /usr/lib64/libglib-2.0.so.0
#13 g_main_context_check
from /usr/lib64/libglib-2.0.so.0
#14 g_main_loop_run
from /usr/lib64/libglib-2.0.so.0
#15 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#16 ??
#17 __libc_start_main
from /lib/libc.so.6
#18 ??
#19 ??
#20 ??
#0 waitpid
from /lib/libpthread.so.0

Comment 1 Pedro Villavicencio 2007-05-05 16:59:22 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 373226 ***