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 375012 - crash in System Log: Usando el visor de regis...
crash in System Log: Usando el visor de regis...
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
: 381535 404069 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2006-11-14 07:30 UTC by Mario Sanchez Prada
Modified: 2007-09-25 18:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Mario Sanchez Prada 2006-11-14 07:30:22 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Usando el visor de registros del sistema


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

Memory status: size: 65634304 vsize: 0 resident: 65634304 share: 0 rss: 17326080 rss_rlim: 0
CPU usage: start_time: 1163489240 rtime: 0 utime: 322 stime: 0 cutime:314 cstime: 0 timeout: 8 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".
[Thread debugging using libthread_db enabled]
[New Thread -1224836928 (LWP 5844)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 86292

Thread 1 (Thread -1224836928 (LWP 5844))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/tls/i686/cmov/libpthread.so.0
  • #2 libgnomeui_segv_handle
    at gnome-ui-init.c line 874
  • #3 <signal handler called>
  • #4 strrchr
    from /lib/tls/i686/cmov/libc.so.6
  • #5 ??
  • #6 ??
  • #0 __kernel_vsyscall 






Comment 1


palfrey





          2007-02-21 15:17:51 UTC
        



*** Bug 404069 has been marked as a duplicate of this bug. ***






Comment 2


palfrey





          2007-02-21 17:24:01 UTC
        



*** Bug 381535 has been marked as a duplicate of this bug. ***






Comment 3


Emmanuele Bassi (:ebassi)





          2007-09-25 18: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.


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