Bug 349945 – crash on 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 349945 - crash on Archive Manager


Summary:	crash on Archive Manager


Status:	RESOLVED INCOMPLETE

Product:	gtk+
Classification:	Platform
Component:	.General
Version:	2.10.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gtk-bugs
QA Contact:	gtk-bugs

URL:
Whiteboard:

Duplicates:	360594 363671 370477 371489 372540 376019 376323 378569 379012 380068 380239 380770 386384 389721 390860 399089 401983 403371 411847 412434 415710 419880 428206 445041 473483 477678 (view as bug list)
Depends on:
Blocks:

Reported:	2006-08-04 14:46 UTC by eivind.dahl
Modified:	2008-10-11 21:32 UTC

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

Description eivind.dahl 2006-08-04 14:46:47 UTC

What were you doing when the application crashed?
Opening a file in a .zip-archive, and/or extracting an .avi


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.15.90 2006-07-24 (Ubuntu)
BugBuddy Version: 2.15.90

Memory status: size: 96149504 vsize: 0 resident: 96149504 share: 0 rss: 14356480 rss_rlim: 0
CPU usage: start_time: 1154702573 rtime: 0 utime: 214 stime: 0 cutime:164 cstime: 0 timeout: 50 it_real_value: 0 frequency: 60

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 -1224538448 (LWP 18705)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 69975

Thread 1 (Thread -1224538448 (LWP 18705))

#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 gdk_drag_motion
from /usr/lib/libgdk-x11-2.0.so.0
#5 gtk_drag_set_icon_pixmap
from /usr/lib/libgtk-x11-2.0.so.0
#6 g_source_is_destroyed
from /usr/lib/libglib-2.0.so.0
#7 g_main_context_dispatch
from /usr/lib/libglib-2.0.so.0
#8 g_main_context_check
from /usr/lib/libglib-2.0.so.0
#9 g_main_loop_run
from /usr/lib/libglib-2.0.so.0
#10 gtk_main
from /usr/lib/libgtk-x11-2.0.so.0
#11 ??
#12 ??
#13 ??
#0 __kernel_vsyscall

Comment 1 Sebastien Bacher 2006-10-21 12:36:26 UTC

Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so. Thanks in advance!

Comment 2 Sebastien Bacher 2006-10-21 12:36:26 UTC

*** Bug 360594 has been marked as a duplicate of this bug. ***

Comment 3 Sebastien Bacher 2006-10-21 12:36:29 UTC

*** Bug 363671 has been marked as a duplicate of this bug. ***

Comment 4 André Klapper 2006-11-04 13:04:41 UTC

*** Bug 370477 has been marked as a duplicate of this bug. ***

Comment 5 Susana 2006-11-06 17:34:48 UTC

*** Bug 371489 has been marked as a duplicate of this bug. ***

Comment 6 eivind.dahl 2006-11-06 23:26:11 UTC

I'm afraid I reinstalled the system shortly after this bug as Edgy still was unstable. I've got Edgy now, but not this problem if I'm not mistaken. What this means is that I cannot get the traces I'm afraid.

Comment 7 clyde 2006-11-08 17:28:38 UTC

If I can help anyone with some informations, then pls feel free to write me a mail, in a english that I can understand ;) I am not the crack on linux but if there is anything I can do for solving this problem with informations from my mashine give me a mail and say what would you like.
This error appears 1 time where I delivered this report to bugzilla, ever since I dont have the problem anymore.

clyde

Comment 8 Karsten Bräckelmann 2006-11-08 20:44:19 UTC

*** Bug 372540 has been marked as a duplicate of this bug. ***

Comment 9 André Klapper 2006-11-17 15:34:46 UTC

*** Bug 376323 has been marked as a duplicate of this bug. ***

Comment 10 Susana 2006-11-23 20:53:38 UTC

*** Bug 378569 has been marked as a duplicate of this bug. ***

Comment 11 Jens Granseuer 2006-11-25 15:02:16 UTC

*** Bug 379012 has been marked as a duplicate of this bug. ***

Comment 12 Jens Granseuer 2006-11-25 15:03:03 UTC

*** Bug 376019 has been marked as a duplicate of this bug. ***

Comment 13 André Klapper 2006-11-28 16:05:14 UTC

*** Bug 380068 has been marked as a duplicate of this bug. ***

Comment 14 Susana 2006-11-28 21:47:05 UTC

*** Bug 380239 has been marked as a duplicate of this bug. ***

Comment 15 ebbywiselyn 2006-11-30 08:18:40 UTC

*** Bug 380770 has been marked as a duplicate of this bug. ***

Comment 16 Susana 2006-12-16 09:54:49 UTC

*** Bug 386384 has been marked as a duplicate of this bug. ***

Comment 17 Damien Durand 2006-12-26 16:17:28 UTC

*** Bug 389721 has been marked as a duplicate of this bug. ***

Comment 18 Jens Granseuer 2006-12-30 10:48:19 UTC

*** Bug 390860 has been marked as a duplicate of this bug. ***

Comment 19 palfrey 2007-01-22 13:41:20 UTC

*** Bug 399089 has been marked as a duplicate of this bug. ***

Comment 20 Mariano Suárez-Alvarez 2007-01-29 09:24:48 UTC

*** Bug 401983 has been marked as a duplicate of this bug. ***

Comment 21 palfrey 2007-02-02 15:53:50 UTC

*** Bug 403371 has been marked as a duplicate of this bug. ***

Comment 22 André Klapper 2007-02-24 14:50:44 UTC

(bug 385943, bug 399551, bug 401574, bug 402862, bug 411383 could be duplicates.)

Dear reporters,
could you please help fixing this by installing some debugging packages [1], start the application as normal, and try to reproduce the crash, if possible?

Once bug-buddy pops up, you can find the stacktrace in the 'Details', now containing way more information. Please copy that stacktrace and paste it as a comment here.

Thanks in advance for helping to get this fixed!

[1] Please install debug packages for glib2 and gtk2.
  Ubuntu 6.10: libglib2.0-0-dbg, libgtk2.0-0-dbg
  Fedora Core 6 or OpenSuSE 10.2: glib2-debuginfo, gtk2-debuginfo

More details can be found here: http://live.gnome.org/GettingTraces

Comment 23 Susana 2007-02-25 13:15:33 UTC

*** Bug 411847 has been marked as a duplicate of this bug. ***

Comment 24 Susana 2007-02-27 12:56:50 UTC

*** Bug 412434 has been marked as a duplicate of this bug. ***

Comment 25 Pedro Villavicencio 2007-03-07 14:27:35 UTC

*** Bug 415710 has been marked as a duplicate of this bug. ***

Comment 26 Pedro Villavicencio 2007-03-18 21:13:20 UTC

*** Bug 419880 has been marked as a duplicate of this bug. ***

Comment 27 palfrey 2007-04-10 17:55:09 UTC

*** Bug 428206 has been marked as a duplicate of this bug. ***

Comment 28 André Klapper 2007-06-22 14:13:37 UTC

*** Bug 445041 has been marked as a duplicate of this bug. ***

Comment 29 Cosimo Cecchi 2007-09-11 09:30:20 UTC

*** Bug 473483 has been marked as a duplicate of this bug. ***

Comment 30 André Klapper 2008-01-03 03:05:19 UTC

*** Bug 477678 has been marked as a duplicate of this bug. ***

Comment 31 André Klapper 2008-10-11 21:32:12 UTC

No new duplicates for a long time. Closing as INCOMPLETE.