Bug 451123 – crash in Panel:

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 451123 - crash in Panel:


Summary:	crash in Panel:


Status:	RESOLVED DUPLICATE of bug 422966

Product:	gnome-panel
Classification:	Other
Component:	general
Version:	2.18.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	Panel Maintainers
QA Contact:	Panel Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2007-06-26 03:19 UTC by pencilo.mmotl
Modified:	2007-06-26 09:41 UTC

See Also:
GNOME target:	---
GNOME version:	2.17/2.18

Description pencilo.mmotl 2007-06-26 03:19:00 UTC

Version: 2.18.1

What were you doing when the application crashed?



Distribution: Gentoo Base System release 1.12.9
Gnome Release: 2.18.1 2007-06-25 (Gentoo)
BugBuddy Version: 2.18.1

System: Linux 2.6.20-gentoo-r8 #1 SMP Mon Jun 25 16:24:10 MDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 70000000
Selinux: No
Accessibility: Disabled
GTK+ Theme: MurrinaNightOrange
Icon Theme: Mist

Memory status: size: 163135488 vsize: 163135488 resident: 21471232 share: 15454208 rss: 21471232 rss_rlim: 18446744073709551615
CPU usage: start_time: 1182827828 rtime: 63 utime: 58 stime: 5 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 47422818548704 (LWP 8775)]
0x00002b217a1a8ad5 in waitpid () from /lib/libpthread.so.0

+ Trace 143745

Thread 1 (Thread 47422818548704 (LWP 8775))

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



----------- .xsession-errors ---------------------
(beryl-manager:8784): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(heliodor:8861): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(heliodor:8853): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(gnome-panel:8775): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(gnome-panel:8775): Gtk-WARNING **: gtk_widget_size_allocate(): attempt to allocate widget with width -5 and height 24
(nautilus:8781): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(gnome-terminal:8924): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
(bug-buddy:9035): Gtk-WARNING **: Unable to locate theme engine in module_path: "murrine",
--------------------------------------------------

Comment 1 Vincent Untz 2007-06-26 09:41:27 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 ***