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 430983 - crash in System Log: Hello, Nothing at all! ...
crash in System Log: Hello, Nothing at all! ...
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-04-18 11:56 UTC by b.sanin
Modified: 2007-04-18 20:46 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description b.sanin 2007-04-18 11:56:56 UTC
Version: 2.16.1

What were you doing when the application crashed?
Hello,

Nothing at all! My computer was just ideling.

Regards,


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

Memory status: size: 32460800 vsize: 0 resident: 32460800 share: 0 rss: 11980800 rss_rlim: 0
CPU usage: start_time: 1176846277 rtime: 0 utime: 232 stime: 0 cutime:216 cstime: 0 timeout: 16 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 -1225516864 (LWP 6088)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225516864 (LWP 6088))

  • #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 Damien Durand 2007-04-18 20:46:16 UTC
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.


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