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 452763 - crash in System Log: a
crash in System Log: a
Status: RESOLVED DUPLICATE of bug 366458
Product: gnome-utils
Classification: Deprecated
Component: logview
2.16.x
Other All
: High critical
: ---
Assigned To: gnome-utils Maintainers
gnome-utils Maintainers
Depends on:
Blocks:
 
 
Reported: 2007-07-01 08:33 UTC by bskang
Modified: 2007-07-07 12:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description bskang 2007-07-01 08:33:33 UTC 
Version: 2.16.0

What were you doing when the application crashed?
a


Distribution: Fedora Core release 6 (Zod)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 107036672 vsize: 0 resident: 107036672 share: 0 rss: 24907776 rss_rlim: 0
CPU usage: start_time: 1183325653 rtime: 0 utime: 20 stime: 0 cutime:14 cstime: 0 timeout: 6 it_real_value: 0 frequency: 0

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 -1208559392 (LWP 11734)]
(no debugging symbols found)
0x00a77402 in __kernel_vsyscall ()

+ Trace 145017

Thread 1 (Thread -1208559392 (LWP 11734))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/i686/nosegneg/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 gtk_main_quit
  • #5 gtk_main_quit
  • #6 gtk_main_quit
  • #7 gtk_main_quit
  • #8 gtk_main_quit
  • #9 gtk_main_quit
  • #10 __libc_start_main
    from /lib/i686/nosegneg/libc.so.6
  • #11 gtk_main_quit
  • #0 __kernel_vsyscall 






Comment 1


Teppo Turtiainen





          2007-07-07 12:02:25 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 366458 ***