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 362606 - crash in System Log: Open Gnome System Log fr...
crash in System Log: Open Gnome System Log fr...
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: 2006-10-16 13:35 UTC by sadothk
Modified: 2006-10-25 02:32 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description sadothk 2006-10-16 13:35:14 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Open Gnome System Log from the System -> Administration -> System Log Menu


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

Memory status: size: 34111488 vsize: 0 resident: 34111488 share: 0 rss: 11644928 rss_rlim: 0
CPU usage: start_time: 1161005567 rtime: 0 utime: 35 stime: 0 cutime:32 cstime: 0 timeout: 3 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 -1224988480 (LWP 5026)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 76607

Thread 1 (Thread -1224988480 (LWP 5026))

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


André Klapper





          2006-10-17 10:09:03 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


André Klapper





          2006-10-25 02:32:38 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?

Marking as duplicate of bug 364106 as bug 364106 provides a stacktrace with debug symbols.

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