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 427129 - crash in System Log: nothing. Just trying to ...
crash in System Log: nothing. Just trying to ...
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-04-07 01:45 UTC by cinod79
Modified: 2007-04-07 14:06 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description cinod79 2007-04-07 01:45:30 UTC
Version: 2.16.1

What were you doing when the application crashed?
nothing. Just trying to access the log


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

Memory status: size: 51372032 vsize: 0 resident: 51372032 share: 0 rss: 12070912 rss_rlim: 0
CPU usage: start_time: 1175910267 rtime: 0 utime: 35 stime: 0 cutime:33 cstime: 0 timeout: 2 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 -1209067328 (LWP 5355)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1209067328 (LWP 5355))

  • #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 palfrey 2007-04-07 09:57:05 UTC
Thanks for taking the time to report this bug.
Unfortunately, that stack trace is missing some elements that will help a lot
to solve the problem, so it will be hard for the developers to fix that crash.
Can you get us a stack trace with debugging symbols? Please see
http://live.gnome.org/GettingTraces for more information on how to do so.
Thanks in advance!
Comment 2 cinod79 2007-04-07 13:12:23 UTC
No problem, here is the stack trace with dbsyms

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

Memory status: size: 51367936 vsize: 0 resident: 51367936 share: 0 rss: 11907072 rss_rlim: 0
CPU usage: start_time: 1175951253 rtime: 0 utime: 32 stime: 0 cutime:30 cstime: 0 timeout: 2 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/gnome-system-log'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1208452928 (LWP 9308)]
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1208452928 (LWP 9308))

  • #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 string_get_date_string
    at logrtns.c line 136
  • #5 log_read_dates
    at logrtns.c line 253
  • #6 log_open
    at logrtns.c line 422
  • #7 logview_add_logs_from_names
    at logview.c line 251
  • #8 main
    at main.c line 179
  • #9 __libc_start_main
    from /lib/tls/i686/cmov/libc.so.6
  • #10 _start
  • #0 __kernel_vsyscall

Comment 3 palfrey 2007-04-07 14:06:13 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 364106 ***