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 520027 - crash in System Log: Trying to see the System...
crash in System Log: Trying to see the System...
Status: RESOLVED DUPLICATE of bug 364106
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: 2008-03-03 05:11 UTC by Juan
Modified: 2008-08-25 10:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.17/2.18


Description Juan 2008-03-03 05:11:06 UTC 
Version: 2.18.1

What were you doing when the application crashed?
Trying to see the System log


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

System: Linux 2.6.23.15-80.fc7 #1 SMP Sun Feb 10 17:29:10 EST 2008 i686
X Vendor: The X.Org Foundation
X Vendor Release: 10300000
Selinux: Permissive
Accessibility: Disabled
GTK+ Theme: Clearlooks
Icon Theme: Fedora

Memory status: size: 64733184 vsize: 64733184 resident: 26529792 share: 22310912 rss: 26529792 rss_rlim: 4294967295
CPU usage: start_time: 1204520913 rtime: 12 utime: 7 stime: 5 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/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1208764704 (LWP 32566)]
(no debugging symbols found)
0x00110402 in __kernel_vsyscall ()

+ Trace 191114

Thread 1 (Thread -1208764704 (LWP 32566))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 ??
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 log_open
  • #5 log_open
  • #6 logview_add_logs_from_names
  • #7 main
  • #0 __kernel_vsyscall 






Comment 1


Cosimo Cecchi





          2008-08-25 10:51:19 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 364106 ***