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 403675 - crash in System Log: Tried to open the system...
crash in System Log: Tried to open the system...
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-02-02 18:33 UTC by gmunholand
Modified: 2007-02-02 20:21 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description gmunholand 2007-02-02 18:33:22 UTC
Version: 2.16.1

What were you doing when the application crashed?
Tried to open the system log viewer.  When the window opened it was grey with only a menu bar.  Almost simultaneously the Bug Reproting tool(bug Buddy) dialog opened.  Send the bug report and close Bug Buddy and the log viewer window closes also.  The log viewer is crashing on startup.


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

Memory status: size: 39567360 vsize: 0 resident: 39567360 share: 0 rss: 13324288 rss_rlim: 0
CPU usage: start_time: 1170441161 rtime: 0 utime: 23 stime: 0 cutime:22 cstime: 0 timeout: 1 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 -1225353024 (LWP 5938)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225353024 (LWP 5938))

  • #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 ??
  • #15 ??
  • #16 ??
  • #0 __kernel_vsyscall

Comment 1 Bruno Boaventura 2007-02-02 20:21:18 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 ***