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 426682 - crash in System Log:
crash in System Log:
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-04-05 17:26 UTC by adrian
Modified: 2007-04-09 21:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description adrian 2007-04-05 17:26:17 UTC 
Version: 2.16.0

What were you doing when the application crashed?



Distribution: Red Hat Enterprise Linux Client release 5 (Tikanga)
Gnome Release: 2.16.0 2006-09-04 (Red Hat, Inc)
BugBuddy Version: 2.16.0

Memory status: size: 53420032 vsize: 0 resident: 53420032 share: 0 rss: 14958592 rss_rlim: 0
CPU usage: start_time: 1175793970 rtime: 0 utime: 12 stime: 0 cutime:7 cstime: 0 timeout: 5 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 -1209018144 (LWP 31255)]
(no debugging symbols found)
0x00c87402 in __kernel_vsyscall ()

+ Trace 125296

Thread 1 (Thread -1209018144 (LWP 31255))

  • #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


Susana





          2007-04-09 21:43:02 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 366458 ***