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 404572 - crash in System Log: browsing xorg.o.log
crash in System Log: browsing xorg.o.log
Status: RESOLVED DUPLICATE of bug 369170
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-02-05 12:35 UTC by info
Modified: 2007-02-05 21:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description info 2007-02-05 12:35:44 UTC 
Version: 2.16.1

What were you doing when the application crashed?
browsing xorg.o.log


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

Memory status: size: 63623168 vsize: 0 resident: 63623168 share: 0 rss: 14905344 rss_rlim: 0
CPU usage: start_time: 1170678719 rtime: 0 utime: 475 stime: 0 cutime:465 cstime: 0 timeout: 10 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 -1224832832 (LWP 15101)]
0xffffe410 in __kernel_vsyscall ()

+ Trace 108145

Thread 1 (Thread -1224832832 (LWP 15101))

  • #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 free
    from /lib/tls/i686/cmov/libc.so.6
  • #5 g_free
    from /usr/lib/libglib-2.0.so.0
  • #6 gtk_tree_path_free
    from /usr/lib/libgtk-x11-2.0.so.0
  • #7 ??
  • #8 ??
  • #9 ??
  • #10 ??
  • #11 gtk_tree_model_get
    from /usr/lib/libgtk-x11-2.0.so.0
  • #12 ??
  • #13 ??
  • #14 ??
  • #15 ??
  • #0 __kernel_vsyscall 






Comment 1


Bruno Boaventura





          2007-02-05 21:43:17 UTC
        



Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but the maintainers need more information to fix the bug. Could you please answer the questions in the other report in order to help the developers?


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