Bug 560175 – crash in Panel: Changed the GTK theme.

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 560175 - crash in Panel: Changed the GTK theme.


Summary:	crash in Panel: Changed the GTK theme.


Status:	RESOLVED DUPLICATE of bug 364396

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

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

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2008-11-10 16:12 UTC by admin
Modified:	2008-11-10 16:32 UTC

See Also:
GNOME target:	---
GNOME version:	2.21/2.22

Description admin 2008-11-10 16:12:08 UTC

Version: 2.22.2

What were you doing when the application crashed?
Changed the GTK theme.


Distribution: Gentoo Base System release 1.12.11.1
Gnome Release: 2.22.3 2008-08-29 (Gentoo)
BugBuddy Version: 2.22.0

System: Linux 2.6.27-gentoo #2 SMP Wed Oct 22 00:57:43 CEST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Unity
Icon Theme: SnowIsh-1.0_PNG

Memory status: size: 79380480 vsize: 79380480 resident: 40079360 share: 18804736 rss: 40079360 rss_rlim: 4294967295
CPU usage: start_time: 1226269240 rtime: 1318 utime: 1136 stime: 182 cutime:0 cstime: 3 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/bin/gnome-panel'

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb5f18700 (LWP 13063)]
0xb7fe0424 in __kernel_vsyscall ()

+ Trace 209584

Thread 1 (Thread 0xb5f18700 (LWP 13063))

#0 __kernel_vsyscall
#1 __waitpid_nocancel
from /lib/libpthread.so.0
#2 IA__g_spawn_sync
at gspawn.c line 374
#3 IA__g_spawn_command_line_sync
at gspawn.c line 682
#4 run_bug_buddy
at gnome-breakpad.cc line 213
#5 check_if_gdb
at gnome-breakpad.cc line 283
#6 google_breakpad::ExceptionHandler::InternalWriteMinidump
at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 226
#7 google_breakpad::ExceptionHandler::HandleException
at ../google-breakpad/src/client/linux/handler/exception_handler.cc line 197
#8 <signal handler called>
#9 ??
#10 gdk_event_apply_filters
at gdkevents-x11.c line 345
#11 gdk_event_translate
at gdkevents-x11.c line 896
#12 _gdk_events_queue
at gdkevents-x11.c line 2285
#13 gdk_event_dispatch
at gdkevents-x11.c line 2345
#14 IA__g_main_context_dispatch
at gmain.c line 2012
#15 g_main_context_iterate
at gmain.c line 2645
#16 IA__g_main_loop_run
at gmain.c line 2853
#17 IA__gtk_main
at gtkmain.c line 1163
#18 main
at main.c line 95
#0 __kernel_vsyscall



----------- .xsession-errors (24414 sec old) ---------------------
Öffne Videofilter: [scale]
VDec: Verwende BGR 15-bit als Ausgabefarbraum (Nummer 2).
Film-Aspekt ist undefiniert - keine Vorskalierung durchgeführt.
SwScaler: reducing / aligning filtersize 1 -> 4
SwScaler: reducing / aligning filtersize 1 -> 4
SwScaler: reducing / aligning filtersize 1 -> 1
SwScaler: reducing / aligning filtersize 9 -> 8
[swscaler @ 0x89ae620]BICUBIC scaler, from rgb555 to yuv420p using MMX2
[swscaler @ 0x89ae620]using 4-tap MMX scaler for horizontal luminance scaling
[swscaler @ 0x89ae620]using 4-tap MMX scaler for horizontal chrominance scaling
[swscaler @ 0x89ae620]using 1-tap MMX "scaler" for vertical scaling (YV12 like)
[swscaler @ 0x89ae620]800x600 -> 800x600
VO: [xv] 800x600 => 800x600 Planar YV12 
A:   0.0 V:   0.0 A-V:  0.048 ct:  0.000   1/  1 ??% ??% ??,?% 0 0              A:   0.1 V:   0.5 A-V: -0.364 ct:  0.000   2/  2 ??% ??% ??,?% 0 0              A:   0.2 V:   0.5 A-V: -0.278 ct:  0.0
...Too much output, ignoring rest...
--------------------------------------------------

Comment 1 André Klapper 2008-11-10 16:32:28 UTC


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