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 452432 - crash in Panel: I changed settings on im...
crash in Panel: I changed settings on im...
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-06-30 02:08 UTC by n-rooter
Modified: 2007-06-30 10:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description n-rooter 2007-06-30 02:08:03 UTC 
Version: 2.18.2

What were you doing when the application crashed?
I changed settings on im-chooser.
Then, i logouted on system.

When i logined on system, the issue occurred.


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 14:56:37 EDT 2007 x86_64
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Enforcing
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 286162944 vsize: 286162944 resident: 18255872 share: 14602240 rss: 18255872 rss_rlim: 18446744073709551615
CPU usage: start_time: 1183169129 rtime: 10 utime: 9 stime: 1 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 "/lib64/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 46912496376848 (LWP 3638)]
(no debugging symbols found)
0x0000003e2cc0d865 in waitpid () from /lib64/libpthread.so.0

+ Trace 144756

Thread 1 (Thread 46912496376848 (LWP 3638))

  • #0 waitpid
    from /lib64/libpthread.so.0
  • #1 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgnomeui-2.so.0
  • #2 <signal handler called>
  • #3 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #4 g_hash_table_foreach
    from /lib64/libglib-2.0.so.0
  • #5 gtk_rc_reset_styles
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #6 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #7 g_closure_invoke
    from /lib64/libgobject-2.0.so.0
  • #8 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #9 g_signal_emit_valist
    from /lib64/libgobject-2.0.so.0
  • #10 g_signal_emit
    from /lib64/libgobject-2.0.so.0
  • #11 g_cclosure_marshal_VOID__ENUM
    from /lib64/libgobject-2.0.so.0
  • #12 g_object_notify
    from /lib64/libgobject-2.0.so.0
  • #13 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #14 gtk_main_do_event
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #15 g_cclosure_marshal_VOID__ENUM
    from /usr/lib64/libgdk-x11-2.0.so.0
  • #16 g_main_context_dispatch
    from /lib64/libglib-2.0.so.0
  • #17 g_cclosure_marshal_VOID__ENUM
    from /lib64/libglib-2.0.so.0
  • #18 g_main_loop_run
    from /lib64/libglib-2.0.so.0
  • #19 gtk_main
    from /usr/lib64/libgtk-x11-2.0.so.0
  • #20 main
  • #0 waitpid
    from /lib64/libpthread.so.0 


----------- .xsession-errors ---------------------
Creating backend ...
Loading socket FrontEnd module ...
Starting SCIM as daemon ...
Launching a SCIM process with x11...
Loading socket Config module ...
Creating backend ...
Loading x11 FrontEnd module ...
(gnome-panel:3638): GLib-GObject-CRITICAL **: g_object_unref: assertion `G_IS_OBJECT (object)' failed
GTK Panel of SCIM 1.4.5
Starting SCIM as daemon ...
SCIM has been successfully launched.
Smart Common Input Method 1.4.5
--------------------------------------------------
Comment 1 Vincent Untz 2007-06-30 10:29:53 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 ***