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 557320 - crash in Archive Manager: Nothing
crash in Archive Manager: Nothing
Status: RESOLVED DUPLICATE of bug 448249
Product: file-roller
Classification: Applications
Component: general
2.22.x
Other All
: High critical
: ---
Assigned To: Paolo Bacchilega
file-roller-maint
Depends on:
Blocks:
 
 
Reported: 2008-10-21 21:23 UTC by gilles_vestens
Modified: 2008-10-27 15:14 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22


Description gilles_vestens 2008-10-21 21:23:01 UTC 
Version: 2.22.4

What were you doing when the application crashed?
Nothing


Distribution: Gentoo Base System release 2.0.0
Gnome Release: 2.22.3 2008-09-17 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.26-gentoo-r1 #1 PREEMPT Thu Sep 18 12:56:11 CEST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10500000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Tango-Blue-Materia

Memory status: size: 39792640 vsize: 39792640 resident: 16674816 share: 11460608 rss: 16674816 rss_rlim: 4294967295
CPU usage: start_time: 1224623778 rtime: 45 utime: 33 stime: 12 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/file-roller'

[Thread debugging using libthread_db enabled]
[New Thread 0xb6fb2aa0 (LWP 3054)]
0xb8095424 in __kernel_vsyscall ()

+ Trace 208507

Thread 1 (Thread 0xb6fb2aa0 (LWP 3054))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 IA__g_spawn_sync
    at gspawn.c line 374
  • #3 IA__g_spawn_command_line_sync
    at gspawn.c line 682
  • #4 run_bug_buddy
    at gnome-breakpad.cc line 213
  • #5 check_if_gdb
    at gnome-breakpad.cc line 283
  • #6 google_breakpad::ExceptionHandler::InternalWriteMinidump
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 226
  • #7 google_breakpad::ExceptionHandler::HandleException
    at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 197
  • #8 <signal handler called>
  • #9 set_sensitive
    at fr-window.c line 1964
  • #10 check_clipboard_cb
    at fr-window.c line 1990
  • #11 g_timeout_dispatch
    at gmain.c line 3446
  • #12 IA__g_main_context_dispatch
    at gmain.c line 2012
  • #13 g_main_context_iterate
    at gmain.c line 2645
  • #14 IA__g_main_loop_run
    at gmain.c line 2853
  • #15 IA__gtk_main
    at gtkmain.c line 1163
  • #16 main
    at main.c line 241
  • #0 __kernel_vsyscall 


----------- .xsession-errors (8 sec old) ---------------------
** (epiphany:2090): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (epiphany:2090): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
Fontconfig error: "/etc/fonts/conf.d/45-latin.conf", line 56: no element found
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x340001e (Archive Ma)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
** (epiphany:2090): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (epiphany:2090): CRITICAL **: dbus_g_proxy_connect_signal: assertion `DBUS_IS_G_PROXY (proxy)' failed
** (epiphany:2090): CRITICAL **: dbus_g_proxy_call: assertion `DBUS_IS_G_PROXY (proxy)' failed
Fontconfig error: "/etc/fonts/conf.d/45-latin.conf", line 56: no element found
Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x340001e (Archive Ma)
Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed.
--------------------------------------------------
Comment 1 André Klapper 2008-10-27 15:14:49 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 448249 ***