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 474672 - crash in Panel: this is probably not a b...
crash in Panel: this is probably not a b...
Status: RESOLVED DUPLICATE of bug 452428
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-09-07 21:28 UTC by glistshere
Modified: 2007-09-09 11:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description glistshere 2007-09-07 21:28:40 UTC 
Version: 2.18.3

What were you doing when the application crashed?
this is probably not a bug -- most likely some bully from internet crashed the computer as I was using a chat client -- this probably most possible as I disabled SELinux in order to get wireless to run with FD7.  Will re-enable SELinux and try wireless again, but in the case it is not some outsider, and is some bug (which happened the other day) I am forwarding this report.


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.3 2007-07-02 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.22.4-65.fc7 #1 SMP Tue Aug 21 22:36:56 EDT 2007 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: No
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 39505920 vsize: 39505920 resident: 19132416 share: 16220160 rss: 19132416 rss_rlim: 4294967295
CPU usage: start_time: 1189199735 rtime: 68 utime: 57 stime: 11 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 -1208346912 (LWP 19253)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 161192

Thread 1 (Thread -1208346912 (LWP 19253))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 __kernel_vsyscall
  • #5 raise
    from /lib/libc.so.6
  • #6 abort
    from /lib/libc.so.6
  • #7 g_logv
    from /lib/libglib-2.0.so.0
  • #8 g_log
    from /lib/libglib-2.0.so.0
  • #9 g_assert_warning
    from /lib/libglib-2.0.so.0
  • #10 ??
    from /usr/lib/libORBit-2.so.0
  • #11 CORBA_any__freekids
    from /usr/lib/libORBit-2.so.0
  • #12 ??
    from /usr/lib/libORBit-2.so.0
  • #13 CORBA_exception_free
    from /usr/lib/libORBit-2.so.0
  • #14 CORBA_exception_set
    from /usr/lib/libORBit-2.so.0
  • #15 CORBA_exception_set_system
    from /usr/lib/libORBit-2.so.0
  • #16 ORBit_small_invoke_stub
    from /usr/lib/libORBit-2.so.0
  • #17 ORBit_small_invoke_stub_n
    from /usr/lib/libORBit-2.so.0
  • #18 ORBit_c_stub_invoke
    from /usr/lib/libORBit-2.so.0
  • #19 Bonobo_Control_getProperties
    from /usr/lib/libbonobo-2.so.0
  • #20 bonobo_control_frame_get_control_property_bag
    from /usr/lib/libbonoboui-2.so.0
  • #21 ??
  • #22 ??
    from /usr/lib/libbonobo-2.so.0
  • #23 ??
    from /usr/lib/libbonobo-2.so.0
  • #24 ??
    from /usr/lib/libORBit-2.so.0
  • #25 giop_invoke_async
    from /usr/lib/libORBit-2.so.0
  • #26 giop_connection_handle_input
    from /usr/lib/libORBit-2.so.0
  • #27 ??
    from /usr/lib/libORBit-2.so.0
  • #28 ??
    from /usr/lib/libORBit-2.so.0
  • #29 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #30 ??
    from /lib/libglib-2.0.so.0
  • #31 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #32 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #33 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors ---------------------
localuser:m being added to access control list
SESSION_MANAGER=local/localhost.localdomain:/tmp/.ICE-unix/19136
Unable to connect to yum-updatesd.  Please ensure that the yum-updatesd 
package is installed and that the service is running.
could not attach to desktop process
** ERROR **: file orbit-object.c: line 159 (do_unref): assertion failed: (robj->refs < ORBIT_REFCOUNT_MAX && robj->refs > 0)
aborting...
--------------------------------------------------
Comment 1 Vincent Untz 2007-09-09 11:02:24 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.


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