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 622986 - crash in Panel: I had just finished ente...
crash in Panel: I had just finished ente...
Status: RESOLVED DUPLICATE of bug 600280
Product: gnome-panel
Classification: Other
Component: general
2.28.x
Other All
: Normal critical
: ---
Assigned To: Panel Maintainers
Panel Maintainers
Depends on:
Blocks:
 
 
Reported: 2010-06-27 21:32 UTC by Tim Rice
Modified: 2010-06-28 04:04 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description Tim Rice 2010-06-27 21:32:38 UTC
Version: 2.28.0

What were you doing when the application crashed?
I had just finished entering my password at the log in screen. The icons
were displayed on the desktop although many were blank, when the
bug reporting tool popped up.


Distribution:                   Solaris Express Community Edition snv_130 X86
Gnome Release: 2.28.0 2009-12-06 (Sun Microsystems, Inc.)
BugBuddy Version: 2.28.0

X Vendor: Sun Microsystems, Inc., based on X.Org Foundation sources
X Vendor Release: 10703000
Selinux: No
Accessibility: Disabled
GTK+ Theme: SphereCrystal
Icon Theme: gnome
GTK+ Modules: canberra-gtk-module, gnomebreakpad

Memory status: size: 100814848 vsize: 100814848 resident: 19525632 share: 393216 rss: 19525632 rss_rlim: 0
CPU usage: start_time: 1277674027 rtime: 20 utime: 153962 stime: 46989 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 0

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

1848:	gnome-panel
 feef53a5 waitid   (0, 773, 8046850, 3)
 feea3e75 waitpid  (773, 804690c, 0, fe78b601) + 65
 fe78ba08 g_spawn_sync (0, 8215180, 0, 4, 0, 0) + 418
 fe78be1c g_spawn_command_line_sync (82553b0, 0, 0, 0, 8046a2c) + 5c
 fdb61e4f __1cNrun_bug_buddy6Fpkclp0_b_ (80e51a8, 738, 0, fdb61ff2) + f3
 fdb620d6 __1cMcheck_if_gdb6F_v_ (fef83000, fef83000, 8046ab4, feeefda5, b, 0) + 12e
 fdb61a94 __1cUbugbuddy_segv_handle6Fi_v_ (b, 0, 8046b68, fe332a00, fef83000, 8046b24) + 64
 feeefda5 __sighndlr (b, 0, 8046b68, fdb61a30) + 15
 feee2cff call_user_handler (b) + 2af
 feee2f2f sigacthandler (b, 0, 8046b68) + df
 --- called from signal handler with signal 11 (SIGSEGV) ---
 fed2256d gdk_window_impl_x11_get_colormap (8176760, 80f9838, 8046df8, fecd668c) + 5d
 fecd66b0 gdk_drawable_get_colormap (8176760, 80f8380, 8046e18, fecf8d04) + 3c
 fecf8d2f gdk_window_real_get_colormap (80fde90, 80f9838, 8046e38, fecd668c) + 43
 fecd66b0 gdk_drawable_get_colormap (80fde90, 0, 8046e88, fed1c339) + 3c
 fed1c3a6 _gdk_pixmap_new (80fde90, 1, 20, ffffffff, 1c) + 1c6
 fece5f0d gdk_pixmap_new (80fde90, 1, 20, ffffffff) + 39
 fecf9757 gdk_window_process_updates_internal (80fde90, fec65d74, 0, fecf98fd) + 27f
 fecf993f gdk_window_process_all_updates (fe7fd220, fe7fc458, 8046f88, 0, 0, fed5c8e4) + af
 fe8fde56 gtk_container_idle_sizer (0, fe7fc458, 8046f88, fecd2d18) + 5a
 fecd2d35 gdk_threads_dispatch (8187370, fe7fc458, 8046fb8, fe757514) + 49
 fe75752a g_idle_dispatch (81f7300, fecd2cec, 8187370, 8047010) + 22
 fe754eee g_main_context_dispatch (80fff90, 6e, 81f51f8, 14) + 262
 fe75559f g_main_context_iterate (80fff90, 1, 1, 80de800) + 483
 fe755bc9 g_main_loop_run (819cde0, 819cde0, 80470f8, fe97e832) + 1dd
 fe97e8db gtk_main (804711c, feffb804, 8047154, 8074b8d, 1, 8047160) + b7
 0807901e main     (1, 8047160, 8047168, 804711c) + 15a
 08074b8d _start   (1, 804728c, 0, 8047298, 80472d1, 8047302) + 7d


----------- .xsession-errors (54790 sec old) ---------------------
  - Arts::Synth_BUS_UPLINK
  - Arts::Synth_AMAN_PLAY
  - Arts::AudioManagerClient
  - Arts::MidiManager
  - OGGPlayObject
  - Arts::Synth_BUS_UPLINK
  - Arts::AudioManagerClient
  - Arts::Synth_AMAN_PLAY
warning: leaving MCOP Dispatcher and still 240 types alive.
KWrited - Listening on Device /dev/pts/0
startkde: Running shutdown scripts...
startkde: Done.
The application 'gnome-settings-daemon' lost its connection to the display :0.0;
most likely the X server was shut down or you killed/destroyed
the application.
--------------------------------------------------
Comment 1 Akhil Laddha 2010-06-28 04:04:32 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

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