Bug 452880 – crash in Archive Manager: login the lumaqq downloa...

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 452880 - crash in Archive Manager: login the lumaqq downloa...


Summary:	crash in Archive Manager: login the lumaqq downloa...


Status:	RESOLVED INCOMPLETE

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:

Duplicates:	453662 455775 456991 478878 483148 487758 492364 497637 507405 509980 510288 (view as bug list)
Depends on:
Blocks:

Reported:	2007-07-01 16:10 UTC by pantaiti
Modified:	2008-11-15 17:10 UTC

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

Description pantaiti 2007-07-01 16:10:12 UTC

Version: 2.18.1

What were you doing when the application crashed?
login the lumaqq
download some software


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3194.fc7 #1 SMP Wed May 23 22:35:01 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 40927232 vsize: 40927232 resident: 13582336 share: 9990144 rss: 13582336 rss_rlim: 4294967295
CPU usage: start_time: 1183306114 rtime: 77 utime: 66 stime: 11 cutime:40 cstime: 10 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 -1208592672 (LWP 9224)]
(no debugging symbols found)
0x003c2402 in __kernel_vsyscall ()

+ Trace 145076

Thread 1 (Thread -1208592672 (LWP 9224))

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

Comment 1 Karsten Bräckelmann 2007-07-01 17:42:56 UTC

Thanks for taking the time to report this bug.

Unfortunately, that stack trace is not very useful in determining the cause of
the crash. Can you get us a stack trace with debugging symbols? Please install
some debugging packages and reproduce the crash, if possible.

Please see http://live.gnome.org/GettingTraces for more information on how to
do so and reopen this bug or simply report a new one.  Thanks!

Comment 2 palfrey 2007-07-04 13:05:53 UTC

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

Comment 3 Damien Durand 2007-07-11 10:10:13 UTC

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

Comment 4 Pedro Villavicencio 2007-07-15 19:01:43 UTC

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

Comment 5 pantaiti 2007-07-17 03:46:29 UTC

how can add comment here 
i recieved the letter,but still didn't know what should i do.

Comment 6 André Klapper 2007-10-29 22:40:59 UTC

pantaiti: the question that karsten asked in comment #1 here.

Comment 7 André Klapper 2007-10-29 22:41:04 UTC

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

Comment 8 André Klapper 2007-10-29 22:45:03 UTC

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

Comment 9 André Klapper 2007-10-29 22:45:05 UTC

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

Comment 10 Susana 2007-11-24 16:29:07 UTC

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

Comment 11 Bruno Boaventura 2008-01-18 23:18:20 UTC

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

Comment 12 Cosimo Cecchi 2008-03-06 09:42:16 UTC

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

Comment 13 Cosimo Cecchi 2008-05-04 23:26:43 UTC

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

Comment 14 Cosimo Cecchi 2008-05-04 23:33:05 UTC

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

Comment 15 André Klapper 2008-11-15 17:10:10 UTC

Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for.
Thanks!