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 446100 - crash in Panel: >>archlinux menüs bearbe...
crash in Panel: >>archlinux menüs bearbe...
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-10 18:21 UTC by wakeup
Modified: 2007-06-10 19:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description wakeup 2007-06-10 18:21:36 UTC 
Version: 2.18.2

What were you doing when the application crashed?
>>archlinux
menüs bearbeiten...


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 Fri May 25 18:51:33 CEST 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: tango-noir0-8.0

Memory status: size: 27447296 vsize: 27447296 resident: 16433152 share: 11501568 rss: 16433152 rss_rlim: 4294967295
CPU usage: start_time: 1181530558 rtime: 303 utime: 275 stime: 28 cutime:0 cstime: 0 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 -1224497472 (LWP 5701)]
(no debugging symbols found)
0xb7f90410 in __kernel_vsyscall ()

+ Trace 139840

Thread 1 (Thread -1224497472 (LWP 5701))

  • #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 (50 sec old) ---------------------
/etc/gdm/PreSession/Default: Registering your session with wtmp and utmp
/etc/gdm/PreSession/Default: running: /usr/bin/sessreg -a -w /var/log/wtmp -u /var/run/utmp -x "/var/lib/gdm/:0.Xservers" -h "" -l ":0" "user"
/etc/gdm/Xsession: Beginning session setup...
/etc/gdm/Xsession: Setup done, will execute: /usr/bin/ssh-agent -- /usr/bin/gnome-session
SESSION_MANAGER=local/lifebook:/tmp/.ICE-unix/5658
seahorse nautilus module initialized
Initializing gnome-mount extension
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-5303--1272693046-1181528972 --active --geometry 70x15+437+432 --working-directory /home/us
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-5303--1272693046-1181528972 --active --geometry 70x15+437+432 --working-directory /home/us
Saving session: gnome-terminal --window-with-profile-internal-id=Default --show-menubar --role=gnome-terminal-5303--1272693046-1181528972 --active --geometry 70x15+437+449 --working-directory /home/us
Fehler beim Anzeigen einer URL: Fehler beim Ausführen des mit diesem Speicherorts verknüpften Befehls der Vorgabeaktion.
--------------------------------------------------
Comment 1 Susana 2007-06-10 19:13:44 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 422966 ***