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 441392 - crash in System Log: Attempting to run the lo...
crash in System Log: Attempting to run the lo...
Status: RESOLVED DUPLICATE of bug 364106
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-26 11:30 UTC by Evan Jenkins
Modified: 2007-05-26 13:20 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description Evan Jenkins 2007-05-26 11:30:00 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Attempting to run the log viewer from the menu.


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

Memory status: size: 34078720 vsize: 0 resident: 34078720 share: 0 rss: 13144064 rss_rlim: 0
CPU usage: start_time: 1180157303 rtime: 0 utime: 50 stime: 0 cutime:46 cstime: 0 timeout: 4 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 -1225221952 (LWP 7580)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 136135

Thread 1 (Thread -1225221952 (LWP 7580))

  • #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 ??
  • #5 ??
  • #6 ??
  • #7 ??
  • #8 g_free
    from /usr/lib/libglib-2.0.so.0
  • #9 ??
  • #10 ??
  • #11 ??
  • #12 ??
  • #13 ??
  • #14 ??
  • #0 __kernel_vsyscall 






Comment 1


Pedro Villavicencio





          2007-05-26 13:20:07 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 ***