Bug 478878 – 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 478878 - 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-09-21 08:46 UTC by ronald.schmieder
Modified:	2007-10-29 22:45 UTC

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

Description ronald.schmieder 2007-09-21 08:46:00 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.4-65.fc7PAE #1 SMP Tue Aug 21 22:17:33 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 39522304 vsize: 39522304 resident: 21823488 share: 16826368 rss: 21823488 rss_rlim: 4294967295
CPU usage: start_time: 1190364171 rtime: 82 utime: 73 stime: 9 cutime:151 cstime: 15 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 -1208432928 (LWP 3324)]
(no debugging symbols found)
0x00110410 in __kernel_vsyscall ()

+ Trace 164342

Thread 1 (Thread -1208432928 (LWP 3324))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 ??
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 ??
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 ??
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 ??
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 ??
from /lib/libglib-2.0.so.0
#26 g_main_context_dispatch
from /lib/libglib-2.0.so.0
#27 ??
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



----------- .xsession-errors (42 sec old) ---------------------
(evolution:2913): evolution-mail-WARNING **: Failed to refresh folders: Ordner existiert nicht
(evolution:2913): evolution-mail-WARNING **: Failed to refresh folders: Ordner existiert nicht
(evolution:2913): evolution-mail-WARNING **: Failed to refresh folders: Ordner existiert nicht
/media/ctsw0705/start.htm: line 1: syntax error near unexpected token `<'
/media/ctsw0705/start.htm: line 1: `<HTML><HEAD>
'
/media/ctsw0705/start.htm: line 1: syntax error near unexpected token `<'
/media/ctsw0705/start.htm: line 1: `<HTML><HEAD>
'
(evolution:2913): evolution-mail-WARNING **: Failed to refresh folders: Ordner existiert nicht
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
(evolution:2913): evolution-mail-WARNING **: Failed to refresh folders: Ordner existiert nicht
--------------------------------------------------

Comment 1 André Klapper 2007-10-29 22:45:03 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 ***