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 397140 - crash in System Log: When writing a large fil...
crash in System Log: When writing a large fil...
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-01-16 06:07 UTC by muralee_pillai
Modified: 2007-01-16 12:27 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16



Description muralee_pillai 2007-01-16 06:07:00 UTC
Version: 2.16.1

What were you doing when the application crashed?
When writing a large file (10G+) to /dev/hda1 (a SATA 250G seagate drive) ubuntu crashed. When I tried to recover and repeat the copy it crashed again. Following this, I booted into recovery mode and executed fsck.ext3 -ccvf /dev/sda1 - to check for physical errors on the disk - badblocks starts checking but about 1min in the PC reboots. Finally I have changed the the SATA cable on the drive and am currently testing.


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

Memory status: size: 35262464 vsize: 0 resident: 35262464 share: 0 rss: 16142336 rss_rlim: 0
CPU usage: start_time: 1168905339 rtime: 0 utime: 576 stime: 0 cutime:512 cstime: 0 timeout: 64 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 -1225394512 (LWP 5022)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

Thread 1 (Thread -1225394512 (LWP 5022))

  • #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 Susana 2007-01-16 12:27:31 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 355887 ***