** Description changed: Binary package hint: nautilus This morning I noticed that nautilus on my laptop crashes when trying to access any remote file share, or the "Computer" destination or the wastebasket. This is repeatable every time, and it must have been caused by a recent update, since it was all working fine three days ago. I can still connect perfectly well to the network with ssh and so on. Nautilus opens and navigates my home folders fine; also the file system. Steps to repeat: Attempt to open "computer" or "Network" from the standard gnome places menu alternatively Attempt to open "Wastebasket" from with Nautilus Expected result: they open Actual result: Nautilus crashes with enclosed failure. What would be very helpful, while this bug is being chased, is if someone could tell me how to access the list of recent updates to the system, so I can try reverting. ProblemType: Crash Architecture: i386 DistroRelease: Ubuntu 9.04 ExecutablePath: /usr/bin/nautilus Package: nautilus 1:2.26.2-0ubuntu2 ProcCmdline: nautilus --no-desktop computer: ProcEnviron: LANGUAGE=en_GB:en LANG=en_GB.UTF-8 SHELL=/bin/zsh Signal: 11 SourcePackage: nautilus StacktraceTop: g_slice_alloc () from /usr/lib/libglib-2.0.so.0 g_error_new_valist () from /usr/lib/libglib-2.0.so.0 g_set_error () from /usr/lib/libglib-2.0.so.0 g_key_file_get_value () from /usr/lib/libglib-2.0.so.0 g_key_file_get_string () from /usr/lib/libglib-2.0.so.0 Title: nautilus crashed with SIGSEGV in g_slice_alloc() Uname: Linux 2.6.28-15-generic i686 UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev pulse pulse-access pulse-rt sambashare scanner ssh users vboxusers + SegvAnalysis: + Segfault happened at: 0xb797487b <g_slice_alloc+267>: mov (%edx),%eax + PC (0xb797487b) ok + source "(%edx)" (0x656d614e) not located in a known VMA region (needed readable region)! + destination "%eax" ok + SegvReason: reading unknown VMA
-- nautilus crashed with SIGSEGV in g_slice_alloc() when connecting to computer:/// https://bugs.launchpad.net/bugs/424202 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
