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 495193 - crash in Archive Manager: close the window!
crash in Archive Manager: close the window!
Status: RESOLVED DUPLICATE of bug 492364
Product: file-roller
Classification: Applications
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2007-11-09 04:45 UTC by chlm_ming
Modified: 2007-11-09 15:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description chlm_ming 2007-11-09 04:45:02 UTC
Version: 2.18.1

What were you doing when the application crashed?
close the window!


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: 60182528 vsize: 60182528 resident: 9097216 share: 4333568 rss: 9097216 rss_rlim: 4294967295
CPU usage: start_time: 1194583406 rtime: 37 utime: 31 stime: 6 cutime:36 cstime: 8 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 -1208178976 (LWP 3068)]
(no debugging symbols found)
0x00558402 in __kernel_vsyscall ()

Thread 1 (Thread -1208178976 (LWP 3068))

  • #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 (908 sec old) ---------------------
Launching a SCIM process with x11...
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/2556
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
/root/Download/realplay-10.0.6.776-linux-2.2-libc6-gcc32-i586.bin: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
/root/Download/realplay-10.0.6.776-linux-2.2-libc6-gcc32-i586.bin: error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory
Loading "installonlyn" plugin
Loading "installonlyn" plugin
--------------------------------------------------
Comment 1 palfrey 2007-11-09 15:32:10 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find

*** This bug has been marked as a duplicate of 492364 ***