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 422866 - crash in System Log: Trying to close nautilus...
crash in System Log: Trying to close nautilus...
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-03-26 02:40 UTC by adude707
Modified: 2007-03-28 19:02 UTC
See Also:
GNOME target: ---
GNOME version: 2.15/2.16


Description adude707 2007-03-26 02:40:49 UTC 
Version: 2.16.1

What were you doing when the application crashed?
Trying to close nautilus.
Nautilus had not started properly when i clicked Home in the Places menu, and had started a thread (or 8 from my repeated clicking) in the background. The bugreporter opened when I killed the processes in a terminal window.


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

Memory status: size: 58552320 vsize: 0 resident: 58552320 share: 0 rss: 17272832 rss_rlim: 0
CPU usage: start_time: 1174876422 rtime: 0 utime: 239 stime: 0 cutime:227 cstime: 0 timeout: 12 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 -1224591168 (LWP 16896)]
(no debugging symbols found)
0xffffe410 in __kernel_vsyscall ()

+ Trace 122255

Thread 1 (Thread -1224591168 (LWP 16896))

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


Damien Durand





          2007-03-26 20:04:12 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 ***






Comment 2


adude707





          2007-03-28 19:02:19 UTC
        



I think i might have written the wrong description in the wrong bug window - i think two things might have crashed at the same time, or very close together.
Sorry for the confusion.