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 453143 - crash in Panel: just after logging in
crash in Panel: just after logging in
Status: RESOLVED DUPLICATE of bug 446183
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-07-02 15:49 UTC by aaskarov
Modified: 2007-07-02 15:50 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description aaskarov 2007-07-02 15:49:18 UTC 
Version: 2.18.2

What were you doing when the application crashed?
just after logging in


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.2 2007-05-28 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.21-1.3228.fc7 #1 SMP Tue Jun 12 15:37:31 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 42778624 vsize: 42778624 resident: 24375296 share: 21123072 rss: 24375296 rss_rlim: 4294967295
CPU usage: start_time: 1183391332 rtime: 36 utime: 32 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 -1208576288 (LWP 3774)]
(no debugging symbols found)
0x00226402 in __kernel_vsyscall ()

+ Trace 145281

Thread 1 (Thread -1208576288 (LWP 3774))

  • #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 g_slist_remove_all
    from /lib/libglib-2.0.so.0
  • #5 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #6 g_hash_table_foreach
    from /lib/libglib-2.0.so.0
  • #7 gtk_rc_reset_styles
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 g_cclosure_marshal_VOID__PARAM
    from /lib/libgobject-2.0.so.0
  • #10 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #11 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #12 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #13 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #14 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #15 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #16 g_cclosure_marshal_VOID__ENUM
    from /lib/libgobject-2.0.so.0
  • #17 g_object_notify
    from /lib/libgobject-2.0.so.0
  • #18 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 gtk_main_do_event
    from /usr/lib/libgtk-x11-2.0.so.0
  • #20 g_cclosure_marshal_VOID__ENUM
    from /usr/lib/libgdk-x11-2.0.so.0
  • #21 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #22 g_cclosure_marshal_VOID__ENUM
    from /lib/libglib-2.0.so.0
  • #23 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #24 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #25 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
localuser:aaskarov being added to access control list
SESSION_MANAGER=local/csmisc85.cs.chalmers.se:/tmp/.ICE-unix/3657
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
** Message: Could not connect to power manager: Could not get owner of name 'org.gnome.PowerManager': no such name
(gnome-panel:3774): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Vincent Untz 2007-07-02 15:50:01 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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