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 463026 - crash in System Log: Opening system log progr...
crash in System Log: Opening system log progr...
Status: RESOLVED DUPLICATE of bug 364106
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-08-03 08:08 UTC by ed
Modified: 2007-08-03 21:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description ed 2007-08-03 08:08:59 UTC 
Version: 2.16.0

What were you doing when the application crashed?
Opening system log program


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: 84058112 vsize: 0 resident: 84058112 share: 0 rss: 11804672 rss_rlim: 0
CPU usage: start_time: 1186128709 rtime: 0 utime: 7 stime: 0 cutime:1 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208682800 (LWP 2557)]
(no debugging symbols found)
0x00a8d402 in __kernel_vsyscall ()

+ Trace 152493

Thread 1 (Thread -1208682800 (LWP 2557))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/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 __libc_start_main
    from /lib/libc.so.6
  • #10 gtk_main_quit
  • #0 __kernel_vsyscall 






Comment 1


Iestyn Pryce





          2007-08-03 21:43:54 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.

Duplicate via Bug 366458

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