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 480462 - crash in System Log: dual booting with xp, vi...
crash in System Log: dual booting with xp, vi...
Status: RESOLVED DUPLICATE of bug 355887
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-09-26 04:41 UTC by gaston1
Modified: 2007-09-26 09:43 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description gaston1 2007-09-26 04:41:23 UTC 
Version: 2.16.1

What were you doing when the application crashed?
dual booting with xp, vista and ubunto 6.10


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

Memory status: size: 36737024 vsize: 0 resident: 36737024 share: 0 rss: 13557760 rss_rlim: 0
CPU usage: start_time: 1190781305 rtime: 0 utime: 641 stime: 0 cutime:621 cstime: 0 timeout: 20 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 -1224845120 (LWP 4716)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 165544

Thread 1 (Thread -1224845120 (LWP 4716))

  • #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 strrchr
    from /lib/tls/i686/cmov/libc.so.6
  • #5 ??
  • #6 ??
  • #0 __kernel_vsyscall 






Comment 1


Emmanuele Bassi (:ebassi)





          2007-09-26 09:43:04 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 355887 ***