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 453603 - crash in Panel: 부팅을 하고 바로 이 에러가 뜨네 this ...
crash in Panel: 부팅을 하고 바로 이 에러가 뜨네 this ...
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-04 06:58 UTC by kyungmanshin
Modified: 2007-07-04 08:39 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description kyungmanshin 2007-07-04 06:58:35 UTC 
Version: 2.18.2

What were you doing when the application crashed?
부팅을 하고 바로 이 에러가 뜨네
this error was happened when i booting


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: 55013376 vsize: 55013376 resident: 25214976 share: 21889024 rss: 25214976 rss_rlim: 4294967295
CPU usage: start_time: 1183564471 rtime: 118 utime: 41 stime: 77 cutime:0 cstime: 1 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 -1208965408 (LWP 2447)]
(no debugging symbols found)
0x00fbe402 in __kernel_vsyscall ()

+ Trace 145641

Thread 1 (Thread -1208965408 (LWP 2447))

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


----------- .xsession-errors (9 sec old) ---------------------
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
SESSION_MANAGER=local/refh136.sec.samsung.co.kr:/tmp/.ICE-unix/2340
** 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
** (nautilus:2448): WARNING **: Didn't get any signs from mapping-daemon
(nautilus:2448): libgnomevfs-WARNING **: module '/usr/lib/gnome-vfs-2.0/modules/libmapping.so' returned a NULL handle
(gnome-panel:2447): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Vincent Untz 2007-07-04 08:39:12 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 ***