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 477984 - crash in System Log: i am fairly new to the u...
crash in System Log: i am fairly new to the u...
Status: RESOLVED DUPLICATE of bug 442846
Product: gnome-utils
Classification: Deprecated
Component: logview
2.18.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-09-18 09:30 UTC by macsima.krecie
Modified: 2007-09-25 18:49 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description macsima.krecie 2007-09-18 09:30:14 UTC 
Version: 2.18.0

What were you doing when the application crashed?
i am fairly new to the use of fedora / linux OS
i went to System - Options - Sessions - Session Options  and clicked the Save-the-current-session button, when this Bug Reporting Tool appeared on my screen and asked for this detail


Distribution: Fedora release 7 (Moonshine)
Gnome Release: 2.18.0 2007-03-23 (Red Hat, Inc)
BugBuddy Version: 2.18.0

System: Linux 2.6.20-2925.9.fc7xen #1 SMP Tue May 22 08:53:03 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: 43184128 vsize: 43184128 resident: 12378112 share: 8458240 rss: 12378112 rss_rlim: 4294967295
CPU usage: start_time: 1190099523 rtime: 90 utime: 84 stime: 6 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100

Backtrace was generated from '/usr/sbin/gnome-system-log'

(no debugging symbols found)
Using host libthread_db library "/lib/i686/nosegneg/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208727840 (LWP 24049)]
(no debugging symbols found)
0x00fea402 in __kernel_vsyscall ()

+ Trace 163708

Thread 1 (Thread -1208727840 (LWP 24049))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 gtk_main_quit
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 ??
  • #5 _gnome_marshal_BOOLEAN__INT_ENUM_BOOLEAN_ENUM_BOOLEAN
    from /usr/lib/libgnomeui-2.so.0
  • #6 g_closure_invoke
    from /lib/libgobject-2.0.so.0
  • #7 gtk_main_quit
    from /lib/libgobject-2.0.so.0
  • #8 g_signal_emit_valist
    from /lib/libgobject-2.0.so.0
  • #9 g_signal_emit
    from /lib/libgobject-2.0.so.0
  • #10 gtk_main_quit
    from /usr/lib/libgnomeui-2.so.0
  • #11 _SmcProcessMessage
    from /usr/lib/libSM.so.6
  • #12 IceProcessMessages
    from /usr/lib/libICE.so.6
  • #13 gtk_main_quit
    from /usr/lib/libgnomeui-2.so.0
  • #14 gtk_main_quit
    from /lib/libglib-2.0.so.0
  • #15 g_main_context_dispatch
    from /lib/libglib-2.0.so.0
  • #16 gtk_main_quit
    from /lib/libglib-2.0.so.0
  • #17 g_main_loop_run
    from /lib/libglib-2.0.so.0
  • #18 gtk_main
    from /usr/lib/libgtk-x11-2.0.so.0
  • #19 main
  • #0 __kernel_vsyscall 


----------- .xsession-errors (303 sec old) ---------------------
** (yelp:26873): WARNING **: failure: no device event controller found.
** (yelp:26873): WARNING **: failure: no device event controller found.
** (yelp:26873): WARNING **: failure: no device event controller found.
(yelp:26873): Yelp-WARNING **: beagled not running, using basic search support.
** (yelp:26873): WARNING **: failure: no device event controller found.
(yelp:26873): Bonobo-CRITICAL **: bonobo_object_corba_objref: assertion `BONOBO_IS_OBJECT (object)' failed
--------------------------------------------------
Comment 1 Emmanuele Bassi (:ebassi) 2007-09-25 18:49:17 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 442846 ***