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 485926 - crash in Panel: Trying to add WP_Tray to...
crash in Panel: Trying to add WP_Tray to...
Status: RESOLVED DUPLICATE of bug 452428
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-10-12 05:01 UTC by tenyousei
Modified: 2007-10-15 19:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description tenyousei 2007-10-12 05:01:09 UTC
Version: 2.18.3

What were you doing when the application crashed?
Trying to add WP_Tray to the Top Panel


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.9-91.fc7 #1 SMP Thu Sep 27 23:10:59 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Glider
Icon Theme: gnome

Memory status: size: 36769792 vsize: 36769792 resident: 18661376 share: 15294464 rss: 18661376 rss_rlim: 4294967295
CPU usage: start_time: 1192165148 rtime: 37 utime: 33 stime: 4 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 -1208887584 (LWP 4947)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

Thread 1 (Thread -1208887584 (LWP 4947))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libORBit-2.so.0
  • #11 CORBA_any__freekids
    from /usr/lib/libORBit-2.so.0
  • #12 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libORBit-2.so.0
  • #13 CORBA_exception_free
    from /usr/lib/libORBit-2.so.0
  • #14 CORBA_exception_set
    from /usr/lib/libORBit-2.so.0
  • #15 CORBA_exception_set_system
    from /usr/lib/libORBit-2.so.0
  • #16 ORBit_small_invoke_stub
    from /usr/lib/libORBit-2.so.0
  • #17 ORBit_small_invoke_stub_n
    from /usr/lib/libORBit-2.so.0
  • #18 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #19 Bonobo_Control_getProperties
    from /usr/lib/libbonobo-2.so.0
  • #20 bonobo_control_frame_get_control_property_bag
    from /usr/lib/libbonoboui-2.so.0
  • #21 ??
  • #22 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libbonobo-2.so.0
  • #23 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libbonobo-2.so.0
  • #24 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libORBit-2.so.0
  • #25 giop_invoke_async
    from /usr/lib/libORBit-2.so.0
  • #26 giop_connection_handle_input
    from /usr/lib/libORBit-2.so.0
  • #27 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libORBit-2.so.0
  • #28 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libORBit-2.so.0
  • #29 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #30 g_cclosure_marshal_VOID__ENUM
    from /lib/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #32 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 main
  • #0 __kernel_vsyscall


----------- .xsession-errors (3120 sec old) ---------------------
Win32 LoadLibrary failed to load: wmv9dmod.dll, /wmv9dmod.dll, /usr/lib/win32/wmv9dmod.dll, /usr/local/lib/win32/wmv9dmod.dll, /usr/lib/codecs/wmv9dmod.dll, /usr/local/lib/codecs/wmv9dmod.dll
Win32 LoadLibrary failed to load: wmv9dmod.dll, /wmv9dmod.dll, /usr/lib/win32/wmv9dmod.dll, /usr/local/lib/win32/wmv9dmod.dll, /usr/lib/codecs/wmv9dmod.dll, /usr/local/lib/codecs/wmv9dmod.dll
Win32 LoadLibrary failed to load: wmv9dmod.dll, /wmv9dmod.dll, /usr/lib/win32/wmv9dmod.dll, /usr/local/lib/win32/wmv9dmod.dll, /usr/lib/codecs/wmv9dmod.dll, /usr/local/lib/codecs/wmv9dmod.dll
Win32 LoadLibrary failed to load: wmv9dmod.dll, /wmv9dmod.dll, /usr/lib/win32/wmv9dmod.dll, /usr/local/lib/win32/wmv9dmod.dll, /usr/lib/codecs/wmv9dmod.dll, /usr/local/lib/codecs/wmv9dmod.dll
Win32 LoadLibrary failed to load: wma9dmod.dll, /wma9dmod.dll, /usr/lib/win32/wma9dmod.dll, /usr/local/lib/win32/wma9dmod.dll, /usr/lib/codecs/wma9dmod.dll, /usr/local/lib/codecs/wma9dmod.dll
[00000371] dmo decoder error: DecOpen failed
[00000371] dmo decoder error: DecOpen failed
[00000326] dmo decoder error: DecOpen failed
[00000326] dmo decoder error: DecOpen failed
[00000371] dmo decoder error: DecOpen failed
Win32 LoadLibrary failed to load: wmv9dmod.dll, /wmv9dmod.dll, /usr/lib/win32/wmv9dmod.dll, /usr/local/lib/win32/wmv9dmod.dll, /usr/lib/codecs/wmv9dmod.dll, /usr/local/lib/codecs/wmv9dmod.dll
Win32 LoadLibrary failed to load: wmv9dmod.dll, /wmv9dmod.dll, /usr/lib/win32/wmv9dmod.dll, /usr/local/lib/win32/wmv9dmod.dll, /usr/lib/codecs/wmv9dmod.dll, /usr/local/lib/codecs/wmv9dmod.dll
Win32 LoadLibrary failed to load: wma9dmod.dll, /wma9dmod.dll, /usr/lib/win32/wma9dmod.dll, /usr/local/lib/win32/wma9dmod.dll, /usr/lib/codecs/wma9dmod.dll, /usr/local/lib/codecs/wma9dmod.dll
Win32 LoadLibrary failed to load: wma9dmod.dll, /wma9dmod.dll, /usr/lib/win32/wma9dmod.dll, /usr/local/lib/win32/wma9dmod.dll, /usr/lib/codecs/wma9
...Too much output, ignoring rest...
--------------------------------------------------
Comment 1 Vincent Untz 2007-10-15 19:27:05 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 452428 ***