GNOME Bugzilla – Bug 584745
crash in File Manager: 1. Я открыл из терминал...
Last modified: 2010-04-10 14:08:13 UTC
Version: 2.26.2 What were you doing when the application crashed? 1. Я открыл из терминала "sudo nautilus" 2. Правил файл /etc/X11/xorg.conf через программу "тексовый редактор" 3. Сохранил файл. 4. Закрыл программу редактор. 5. Закрыл nautilus Distribution: Debian squeeze/sid Gnome Release: 2.26.1 2009-04-14 (Debian) BugBuddy Version: 2.26.0 System: Linux 2.6.26-2-amd64 #1 SMP Fri Mar 27 04:02:59 UTC 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10402000 Selinux: No Accessibility: Disabled GTK+ Theme: Clearlooks Icon Theme: Nuvola GTK+ Modules: gnomebreakpad Memory status: size: 419573760 vsize: 419573760 resident: 29564928 share: 19607552 rss: 29564928 rss_rlim: 18446744073709551615 CPU usage: start_time: 1244047574 rtime: 193 utime: 179 stime: 14 cutime:0 cstime: 2 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] [New Thread 0x7f78356a97f0 (LWP 5807)] [New Thread 0x7f781e54e950 (LWP 5875)] [New Thread 0x7f781ed4f950 (LWP 5829)] 0x00007f7830f2f31f in waitpid () from /lib/libpthread.so.0
+ Trace 215835
Thread 1 (Thread 0x7f78356a97f0 (LWP 5807))
Thanks for taking the time to report this bug. This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 584953 has been marked as a duplicate of this bug. ***
*** Bug 585502 has been marked as a duplicate of this bug. ***
*** Bug 585700 has been marked as a duplicate of this bug. ***
*** Bug 585950 has been marked as a duplicate of this bug. ***
*** Bug 586103 has been marked as a duplicate of this bug. ***
For what it's worth... I reported duplicated bug 585950 and the problem was gone after uninstalling the package "nautilus-actions".
I can confirm that the problem disappears when I remove the package "nautilus-actions" on Debian Squeeze
*** Bug 586423 has been marked as a duplicate of this bug. ***
*** Bug 586673 has been marked as a duplicate of this bug. ***
(In reply to comment #1) > Thanks for taking the time to report this bug. > This bug report isn't very useful because it doesn't describe the bug well. If > you have time and can still reproduce the bug, please read > http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to > reproduce this bug. > > Unfortunately, that stack trace is missing some elements that will help a lot > to solve the problem, so it will be hard for the developers to fix that crash. > Can you get us a stack trace with debugging symbols? Please see > http://live.gnome.org/GettingTraces for more information on how to do so and > reopen this bug or report a new one. Thanks in advance! > Excuse for my English the matter is that I only have started it to study. At institute now I study German. =) What i do: 1. I execute "sudo nautilus" from terminal. 2. Change directory to /etc/X11 3. Right click to icon of file /etc/X11/xorg.conf 3. Edit with gedit. 4. Save this file & close this. 5. I try to close nautilus, but he raised this exception. After i install last versions of: regex:(nautilus(-dbg)?) and: p5-vbnekit@pc-21:~$ sudo gdb nautilus [sudo] password for p5-vbnekit: GNU gdb 6.8-debian Copyright (C) 2008 Free Software Foundation, Inc. License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html> This is free software: you are free to change and redistribute it. There is NO WARRANTY, to the extent permitted by law. Type "show copying" and "show warranty" for details. This GDB was configured as "x86_64-linux-gnu"... (gdb) run Starting program: /usr/bin/nautilus [Thread debugging using libthread_db enabled] [New Thread 0x7ffd386b47f0 (LWP 4604)] [New Thread 0x7ffd24b9c950 (LWP 4614)] [New Thread 0x7ffd2439b950 (LWP 4615)] [New Thread 0x7ffd219cd950 (LWP 4623)] [Thread 0x7ffd24b9c950 (LWP 4614) exited] ** (nautilus:4604): WARNING **: Unable to add monitor: Действие не поддерживается --- Hash table keys for warning below: --> file:///root (nautilus:4604): Eel-WARNING **: "nautilus-metafile.c: metafiles" hash table still has 1 element at quit time (keys above) (nautilus:4604): Eel-WARNING **: "nautilus-directory.c: directories" hash table still has 1 element at quit time Program received signal SIGSEGV, Segmentation fault.
+ Trace 216174
Thread 4 (Thread 0x7ffd219cd950 (LWP 4623))
(gdb) quit The program is running. Exit anyway? (y or n) y ********************* I try to close nautilus, but he is cycled.
Sorry, but from that article I have not understood, how I can give you more information on a stack at the moment of this exception.
*** Bug 587342 has been marked as a duplicate of this bug. ***
(In reply to comment #12) > Sorry, but from that article I have not understood, how I can give you more > information on a stack at the moment of this exception. What is not clear in comment 1?
*** Bug 587725 has been marked as a duplicate of this bug. ***
*** Bug 588459 has been marked as a duplicate of this bug. ***
*** Bug 589613 has been marked as a duplicate of this bug. ***
*** Bug 589811 has been marked as a duplicate of this bug. ***
*** Bug 589885 has been marked as a duplicate of this bug. ***
This bug report isn't very useful because it doesn't describe the bug well. If you have time and can still reproduce the bug, please read http://bugzilla.gnome.org/bug-HOWTO.html and add a description of how to reproduce this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance!
*** Bug 593748 has been marked as a duplicate of this bug. ***
*** Bug 593807 has been marked as a duplicate of this bug. ***
*** Bug 594123 has been marked as a duplicate of this bug. ***
There's a similar report on Ubuntu here : https://bugs.edge.launchpad.net/ubuntu/+source/nautilus/+bug/404351 with Nautilus 2.27/28 I'm asking for backtrace + valgrind logs.
*** Bug 597986 has been marked as a duplicate of this bug. ***
*** Bug 598666 has been marked as a duplicate of this bug. ***
*** Bug 598642 has been marked as a duplicate of this bug. ***
As per the downstream report, this is OBSOLETE. Please reopen if it's still an issue.