Bug 487758 – crash in Archive Manager:

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 487758 - crash in Archive Manager:


Summary:	crash in Archive Manager:


Status:	RESOLVED DUPLICATE of bug 452880

Product:	file-roller
Classification:	Applications
Component:	general
Version:	2.18.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-10-18 03:43 UTC by richyoung
Modified:	2007-10-29 22:41 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description richyoung 2007-10-18 03:43:02 UTC

Version: 2.18.4

What were you doing when the application crashed?



Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 20:47:39 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 300003328 vsize: 300003328 resident: 28184576 share: 19832832 rss: 28184576 rss_rlim: 18446744073709551615
CPU usage: start_time: 1192678660 rtime: 34 utime: 28 stime: 6 cutime:9 cstime: 14 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496484816 (LWP 3555)]
(no debugging symbols found)
0x0000003ab000d945 in waitpid () from /lib64/libpthread.so.0

+ Trace 171030

Thread 1 (Thread 46912496484816 (LWP 3555))

#0 waitpid
from /lib64/libpthread.so.0
#1 g_cclosure_marshal_VOID__BOOLEAN
from /usr/lib64/libgnomeui-2.so.0
#2 <signal handler called>
#3 g_type_check_instance_cast
from /lib64/libgobject-2.0.so.0
#4 ??
#5 ??
#6 window_update_file_list
#7 ??
#8 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#9 g_cclosure_marshal_VOID__BOOLEAN
from /lib64/libgobject-2.0.so.0
#10 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#11 g_signal_emit
from /lib64/libgobject-2.0.so.0
#12 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#13 g_cclosure_marshal_VOID__BOOLEAN
from /lib64/libgobject-2.0.so.0
#14 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#15 g_signal_emit
from /lib64/libgobject-2.0.so.0
#16 g_closure_invoke
from /lib64/libgobject-2.0.so.0
#17 g_cclosure_marshal_VOID__BOOLEAN
from /lib64/libgobject-2.0.so.0
#18 g_signal_emit_valist
from /lib64/libgobject-2.0.so.0
#19 g_signal_emit
from /lib64/libgobject-2.0.so.0
#20 ??
#21 g_cclosure_marshal_VOID__BOOLEAN
from /lib64/libglib-2.0.so.0
#22 g_main_context_dispatch
from /lib64/libglib-2.0.so.0
#23 g_cclosure_marshal_VOID__BOOLEAN
from /lib64/libglib-2.0.so.0
#24 g_main_loop_run
from /lib64/libglib-2.0.so.0
#25 gtk_main
from /usr/lib64/libgtk-x11-2.0.so.0
#26 main
#0 waitpid
from /lib64/libpthread.so.0



----------- .xsession-errors (99393 sec old) ---------------------
  Resource id:  0x1421787
X Error: BadPixmap (invalid Pixmap parameter) 4
  Major opcode:  54
  Minor opcode:  0
  Resource id:  0x1421788
X Error: BadMatch (invalid parameter attributes) 8
  Major opcode:  160
  Minor opcode:  6
  Resource id:  0x1421788
X Error: BadWindow (invalid Window parameter) 3
  Major opcode:  19
  Minor opcode:  0
  Resource id:  0x3c00016
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2007-10-29 22:41:04 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 452880 ***