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 480853 - crash in System Log: Nothing in particular, I...
crash in System Log: Nothing in particular, I...
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-27 07:50 UTC by r.kurowski5
Modified: 2007-09-27 09:33 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description r.kurowski5 2007-09-27 07:50:51 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Nothing in particular, I just opened page of Polish IPN catalog,when that happend.  > http://katalog.bip.ipn.gov.pl/ <


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

Memory status: size: 38039552 vsize: 0 resident: 38039552 share: 0 rss: 15888384 rss_rlim: 0
CPU usage: start_time: 1190878631 rtime: 0 utime: 543 stime: 0 cutime:532 cstime: 0 timeout: 11 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 -1224881984 (LWP 5194)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 165841

Thread 1 (Thread -1224881984 (LWP 5194))

  • #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-27 09:33:27 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 ***