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 440138 - crash in System Log: nothing in particular, i...
crash in System Log: nothing in particular, i...
Status: RESOLVED DUPLICATE of bug 355887
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-05-21 10:06 UTC by barthek
Modified: 2007-05-21 16:55 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description barthek 2007-05-21 10:06:47 UTC 
Version: 2.16.1

What were you doing when the application crashed?
nothing in particular, it has been opened on a logfile for the last tens of hours


Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 56700928 vsize: 0 resident: 56700928 share: 0 rss: 15720448 rss_rlim: 0
CPU usage: start_time: 1173973903 rtime: 0 utime: 2568 stime: 0 cutime:2518 cstime: 0 timeout: 50 it_real_value: 0 frequency: 0

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

(no debugging symbols found)
Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread -1224775488 (LWP 15814)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 135308

Thread 1 (Thread -1224775488 (LWP 15814))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 gnome_gtk_module_info_get
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 strrchr
    from /lib/tls/i686/cmov/libc.so.6
  • #5 ??
  • #6 ??
  • #0 __kernel_vsyscall 






Comment 1


Susana





          2007-05-21 16:55:48 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 355887 ***