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 449956 - crash in Panel: editing the menu as the ...
crash in Panel: editing the menu as the ...
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-22 05:28 UTC by ubuntu
Modified: 2007-06-22 10:53 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description ubuntu 2007-06-22 05:28:37 UTC 
Version: 2.18.2

What were you doing when the application crashed?
editing the menu as the terminal option wasn't showing


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: 28803072 vsize: 28803072 resident: 17702912 share: 11386880 rss: 17702912 rss_rlim: 4294967295
CPU usage: start_time: 1182453046 rtime: 453 utime: 400 stime: 53 cutime:0 cstime: 2 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 -1224484144 (LWP 5522)]
(no debugging symbols found)
0xb7f8f410 in __kernel_vsyscall ()

+ Trace 142814

Thread 1 (Thread -1224484144 (LWP 5522))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    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

(gnome-terminal:5794): GnomeUI-WARNING **: While connecting to session manager:
Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed.
Failed to load plugin (/usr/lib/audacious/Output/libjackout.so): libjack.so.0: cannot open shared object file: No such file or directory
Failed to load plugin (/usr/lib/audacious/General/liblirc.so): liblirc_client.so.0: cannot open shared object file: No such file or directory
Failed to load plugin (/usr/lib/audacious/Visualization/librovascope.so): libSDL-1.2.so.0: cannot open shared object file: No such file or directory
Failed to load plugin (/usr/lib/audacious/Visualization/libprojectm.so): libSDL-1.2.so.0: cannot open shared object file: No such file or directory
Failed to load plugin (/usr/lib/audacious/Visualization/libparanormal.so): libSDL-1.2.so.0: cannot open shared object file: No such file or directory
warning: .dynamic section for "/usr/lib/libglade-2.0.so.0" is not at the expected address (wrong library or version mismatch?)
--------------------------------------------------
Comment 1 André Klapper 2007-06-22 10:53:49 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.

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