Bug 368351 – crash in System Log: plugin usb harddisk

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 368351 - crash in System Log: plugin usb harddisk


Summary:	crash in System Log: plugin usb harddisk


Status:	RESOLVED DUPLICATE of bug 364106

Product:	gnome-utils
Classification:	Deprecated
Component:	logview
Version:	2.16.x
Hardware:	Other All

Importance:	High critical
Target Milestone:	---
Assigned To:	gnome-utils Maintainers
QA Contact:	gnome-utils Maintainers

URL:
Whiteboard:

Depends on:
Blocks:

Reported:	2006-10-31 15:39 UTC by tarkus.nnkh
Modified:	2006-10-31 16:39 UTC

See Also:
GNOME target:	---
GNOME version:	2.15/2.16

Description tarkus.nnkh 2006-10-31 15:39:31 UTC

Version: 2.16.1

What were you doing when the application crashed?
plugin usb harddisk


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

Memory status: size: 30412800 vsize: 0 resident: 30412800 share: 0 rss: 11698176 rss_rlim: 0
CPU usage: start_time: 1162309111 rtime: 0 utime: 58 stime: 0 cutime:53 cstime: 0 timeout: 5 it_real_value: 0 frequency: 2

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 -1225168704 (LWP 5798)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 81017

Thread 1 (Thread -1225168704 (LWP 5798))

#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-31 16:39:08 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?


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