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 383430 - crash in System Log: looks like spy ware. com...
crash in System Log: looks like spy ware. com...
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: 2006-12-07 17:04 UTC by onezero
Modified: 2006-12-07 21:24 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description onezero 2006-12-07 17:04:39 UTC 
Version: 2.16.1

What were you doing when the application crashed?
looks like spy ware. competition for the mouse, just like some women.
Looks like something sitting in video memory grabbing mouse when gksudo runs. Great work on edgy!



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

Memory status: size: 37707776 vsize: 0 resident: 37707776 share: 0 rss: 15966208 rss_rlim: 0
CPU usage: start_time: 1165510869 rtime: 0 utime: 982 stime: 0 cutime:943 cstime: 0 timeout: 39 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 -1225505104 (LWP 4881)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 92356

Thread 1 (Thread -1225505104 (LWP 4881))

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


Bruno Boaventura





          2006-12-07 21:24:40 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 355887 ***