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 449110 - crash in Panel: Using file-roller-2.18.3...
crash in Panel: Using file-roller-2.18.3...
Status: RESOLVED DUPLICATE of bug 422966
Product: gnome-panel
Classification: Other
Component: general
2.18.x
Other All
: High critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-06-19 13:00 UTC by rossm
Modified: 2007-06-19 14:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description rossm 2007-06-19 13:00:52 UTC 
Version: 2.18.2

What were you doing when the application crashed?
Using file-roller-2.18.3 to extrac alunn-0.6.3.tar.gz to /home/$username/Desktop.
Pressed  "Extract" button.


Distribution: Unknown
Gnome Release: 2.18.2 2007-05-31 (Archlinux)
BugBuddy Version: 2.18.1

System: Linux 2.6.21-ARCH #1 SMP PREEMPT Mon Jun 11 23:47:51 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: gnome

Memory status: size: 60272640 vsize: 60272640 resident: 17080320 share: 12562432 rss: 17080320 rss_rlim: 4294967295
CPU usage: start_time: 1182216427 rtime: 555 utime: 469 stime: 86 cutime:0 cstime: 1 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

(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 -1224951088 (LWP 6010)]
(no debugging symbols found)
0xb7f1e410 in __kernel_vsyscall ()

+ Trace 142139

Thread 1 (Thread -1224951088 (LWP 6010))

  • #0 __kernel_vsyscall
  • #1 ??
    from /lib/libpthread.so.0
  • #2 libgnomeui_segv_handle
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_str_hash
    from /usr/lib/libglib-2.0.so.0
  • #5 g_hash_table_remove
    from /usr/lib/libglib-2.0.so.0
  • #6 remove_watch
    from /usr/lib/libgnome-menu.so.2
  • #7 inotify_data_pending
    from /usr/lib/libgnome-menu.so.2
  • #8 g_io_unix_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #9 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #10 g_main_context_iterate
    from /usr/lib/libglib-2.0.so.0
  • #11 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #12 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
** Message: drive = 0
** Message: volume = 0
--------------------------------------------------
Comment 1 Vincent Untz 2007-06-19 14:21:59 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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