[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
** Attachment added: "CoreDump.gz" http://launchpadlibrarian.net/49801699/CoreDump.gz ** Attachment added: "Dependencies.txt" http://launchpadlibrarian.net/49801700/Dependencies.txt ** Attachment added: "Disassembly.txt" http://launchpadlibrarian.net/49801701/Disassembly.txt ** Attachment added: "ProcMaps.txt" http://launchpadlibrarian.net/49801702/ProcMaps.txt ** Attachment added: "ProcStatus.txt" http://launchpadlibrarian.net/49801703/ProcStatus.txt ** Attachment added: "Registers.txt" http://launchpadlibrarian.net/49801704/Registers.txt ** Attachment added: "Stacktrace.txt" http://launchpadlibrarian.net/49801705/Stacktrace.txt ** Attachment added: "ThreadStacktrace.txt" http://launchpadlibrarian.net/49801706/ThreadStacktrace.txt ** Attachment added: "XsessionErrors.txt" http://launchpadlibrarian.net/49801707/XsessionErrors.txt ** Attachment added: "usr_lib_nautilus.txt" http://launchpadlibrarian.net/49801708/usr_lib_nautilus.txt ** Visibility changed to: Public -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
Thanks for your bug report. Please try to obtain a backtrace http://wiki.ubuntu.com/DebuggingProgramCrash and attach the file to the bug report. This will greatly help us in tracking down your problem. ** Attachment removed: "CoreDump.gz" http://launchpadlibrarian.net/49801699/CoreDump.gz ** Changed in: nautilus (Ubuntu) Importance: Undecided => Medium ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
Thanks Pedro. I followed the step-by-step procedure at the HTTP adress You quoted. I'm not expert, I don't know if I did the right job. Please, see the new attached TXT file. Please, let me know if this is enough for the debugging activity. Ciao from Italy CM ** Attachment added: "gdb generated logfile (TXT)" http://launchpadlibrarian.net/49825119/gdb-nautilus.txt ** Changed in: nautilus (Ubuntu) Status: Incomplete => New -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
backtrace is empty, could you please try again? thanks. ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
Many thanks. When I ran "list-dbgsym-packages.sh" I got these errors: warning: the debug information found in "/usr/lib/debug//lib/libuuid.so.1.3.0" does not match "/lib/libuuid.so.1" (CRC mismatch). warning: the debug information found in "/usr/lib/debug/lib/libuuid.so.1.3.0" does not match "/lib/libuuid.so.1" (CRC mismatch). Then I installed 126 missing "-dbgsym" and "-dbg" packages. After this, I repeated the gdb session. See the new attached TXT logfile. Ciao CM ** Attachment added: "GDB session log file (TXT)" http://launchpadlibrarian.net/49931628/nautilus-crash.txt ** Changed in: nautilus (Ubuntu) Status: Incomplete => New -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
the stacktrace has still nothing useful for some reason, could you try to get a valgrind log? -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
Il 08/06/2010 14:10, Sebastien Bacher ha scritto: > the stacktrace has still nothing useful for some reason, could you try > to get a valgrind log? > > Thanks. But I'm not able to do this. How to use valgrind? I read the manpage in my computer but I cannot understand how to load and inspect the coredump file generated by nautilus while crashing. Ciao CM -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
do you still work on the dump you got or can you get the crash by following some step on your box? valgrind is useful if you can get the issue again otherwise you can't use it on the gdb dump you got -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
Thanks for Your help. The problem (crash) happened at first time during normal desktop operations. Then it happened again just once during last 3 days. I read "valgrind" man page. I suppose that valgrind should launch the application in order to trace it, shouldn't it? It this is correct, I should run nautilus from the shell, encapsulating it into valgrind. Well, I'm really not able to do so: I have no idea how to run nautilus, because it usually start from the desktop environment ... Please, could You tell me how to do this? Ciao CM -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
you can use gconf-editor and edit your session in /desktop/gnome/session to not start nautilus for example, or edit the desktop entry /usr/share/applications/nautilus.desktop and rename it for example -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
Thank you for Your reply. Here You find my "/usr/share/applications/nautilus.desktop" file: [Desktop Entry] Name=File Manager Exec=nautilus Icon=system-file-manager Terminal=false Type=Application StartupNotify=true NoDisplay=true OnlyShowIn=GNOME; X-GNOME-Bugzilla-Bugzilla=GNOME X-GNOME-Bugzilla-Product=nautilus X-GNOME-Bugzilla-Component=general X-GNOME-Bugzilla-Version=2.30.1 #X-GNOME-Autostart-Phase=Desktop X-GNOME-Autostart-Notify=true X-GNOME-AutoRestart=true X-GNOME-Provides=filemanager X-Ubuntu-Gettext-Domain=nautilus How should I modify it in order to run valgrind? Many thanks. CM -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
you can move it on the side so it's not started with the session and then run it manually with valgrind -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
Thank You for Your help. I run nautilus from "inside" valgrind. The system became so sloow that it was actually not usable. I spent minutes to open a folder, then minutes to navigate to a sub-folder. Actually I'm not able to reproduce the real crash situation in this way. Before closing, valgrind itself crashed or something related to valgrind crashed, generating the file /var/crash/_usr_lib_valgrind_memcheck- amd64-linux.1000.crash So I don't know how to go on with this issue. Ciao CM -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
Today nautilus crashed again. This time, the crash happened again while deleting a folder. However, the first crash happened when deleting a folder from a removable media (USB mass storage device), today the crash happened while deleting a folder from the local filesystem. I tried to reproduce the bug, but this won't happen when I try to deleted folders nor files. It just happened some now and then. So I have not already understood the exact circumstances upon which the bug appears. I tried again to run nautilus from inside valgrind, but again the system is not usable, because the overhead is too much: is there any valgrind option to make it faster? Furthermore, the apport automatic bug system claimed that it was not possible to report the bug, because "libgail18, libgtk2.0-0" are not up- to-date. Then I run "sudo apt-get update ; sudo apt-get upgrade" but no download happened, because the packages are marked as up-to-date. So? Anyway, I decided to run nautilus from inside GDB for some days, because this won't show a great overhead and the system runs well. I hope to detect again the bug. See the attached TXT file for debug info. Thank You. Ciao. CM ** Attachment added: "txt outbput from GDB - nautilus crash" http://launchpadlibrarian.net/50441324/crash.txt ** Changed in: nautilus (Ubuntu) Status: Incomplete => New -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
Back again to You. Lucky enough I got another crash running from inside GDB. Se attached TXT file. Now there is 2 news: 1) gdb detected the location of the fault: Program received signal SIGSEGV, Segmentation fault. nautilus_file_peek_display_name (file=0x0) at nautilus-file.c:3734 3734nautilus-file.c: Nessun file o directory. in nautilus-file.c 2) I reproduced the bug this way: a) created a folder containing many files about 165 MBtyes b) use seahorse to tar-gzip-crypt the whole folder c) delete the folder d) delete the tgzip file e) delete the gpg file Between steps c) and d) the crash happened. Now I remember that this happen in the same way during the previous 2 crashes. Thanks to You in advance for Your help. Ciao CM ** Attachment added: "txt outbput from GDB - nautilus crash (2)" http://launchpadlibrarian.net/50442616/crash-2.txt -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 590650] Re: nautilus crashed with SIGSEGV in g_closure_invoke()
*** This bug is a duplicate of bug 518891 *** https://bugs.launchpad.net/bugs/518891 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. ** Changed in: nautilus (Ubuntu) Status: New => Invalid ** This bug has been marked a duplicate of bug 518891 nautilus crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID() -- nautilus crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/590650 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to nautilus in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
