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 440600 - crash in Panel: abrindo a seção depois d...
crash in Panel: abrindo a seção depois d...
Status: RESOLVED DUPLICATE of bug 432554
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-05-23 00:38 UTC by gwfonsaca
Modified: 2007-05-23 01:11 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18



Description gwfonsaca 2007-05-23 00:38:18 UTC
Version: 2.18.0

What were you doing when the application crashed?
abrindo a seção depois de trocar o tema do GDM


Distribution: Mandriva Linux release 2007.1 (Official) for i586
Gnome Release: 2.18.0 2007-03-15 (Mandriva)
BugBuddy Version: 2.18.0

System: Linux 2.6.17-13mdvlegacy #1 SMP Fri Mar 23 19:05:24 UTC 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 70200000
Selinux: No
Accessibility: Enabled
GTK+ Theme: Glossy
Icon Theme: OSX

Memory status: size: 53858304 vsize: 53858304 resident: 20213760 share: 12881920 rss: 20213760 rss_rlim: 4294967295
CPU usage: start_time: 1179869845 rtime: 103 utime: 92 stime: 11 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/i686/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1226651968 (LWP 14736)]
(no debugging symbols found)
0xbfffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1226651968 (LWP 14736))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/libpthread.so.0
  • #2 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 wnck_workspace_get_width
    from /usr/lib/libwnck-1.so.18
  • #5 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libwnck-1.so.18
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgobject-2.0.so.0
  • #8 g_closure_invoke
    from /usr/lib/libgobject-2.0.so.0
  • #9 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgobject-2.0.so.0
  • #10 g_signal_emit_valist
    from /usr/lib/libgobject-2.0.so.0
  • #11 g_signal_emit
    from /usr/lib/libgobject-2.0.so.0
  • #12 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #13 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #14 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgdk-x11-2.0.so.0
  • #15 gdk_window_process_all_updates
    from /usr/lib/libgdk-x11-2.0.so.0
  • #16 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #17 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libglib-2.0.so.0
  • #18 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #19 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libglib-2.0.so.0
  • #20 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #21 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #22 main
  • #0 __kernel_vsyscall


----------- .xsession-errors ---------------------
kxdocker: WARNING: loading xml...
kxdocker: WARNING: saving xml configuration to backup configuration...
kxdocker: WARNING: loading plugins...
XEPlugin_Sounds xeplugin_register()
kxdocker: WARNING: Plugins loaded:
kxdocker: WARNING: Going to background...
GTK Accessibility Module initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
/home/oracle/.MdkOnline/mdkonline should be set to TRUE: please use --force or -f option to launch applet at /usr/bin/mdkapplet line 242.
GTK Accessibility Module initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
GTK Accessibility Module initialized
Bonobo accessibility support initialized
--------------------------------------------------
Comment 1 Pedro Villavicencio 2007-05-23 01:11:06 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 432554 ***