nautilus crashed when clicking on bookmark

Bug #1168383 reported by Richard Ayotte
236
This bug affects 53 people
Affects Status Importance Assigned to Milestone
Ubuntu GNOME
Confirmed
Medium
Unassigned

Bug Description

Clicking on any Nautilus bookmark causes it to crash. sftp://, ftp:// and x-nautilus-desktop:/// all have the same result.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.8.0-0ubuntu1~raring [origin: LP-PPA-gnome3-team-gnome3]
ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
Uname: Linux 3.8.0-17-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.9.2-0ubuntu8
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 12 08:04:46 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:
 b'org.gnome.nautilus.window-state' b'geometry' b"'967x843+473+165'"
 b'org.gnome.nautilus.window-state' b'sidebar-width' b'312'
 b'org.gnome.nautilus.window-state' b'start-with-sidebar' b'false'
InstallationDate: Installed on 2011-02-26 (776 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007.1)
MarkForUpload: True
ProcCmdline: /usr/bin/nautilus --no-default-window
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANG=en_US.utf8
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? ()
Title: nautilus crashed with SIGABRT in raise()
UpgradeStatus: Upgraded to raring on 2013-04-11 (0 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev sambashare vboxusers

Revision history for this message
Richard Ayotte (rich-ayotte) wrote :
information type: Private → Public
Tim Lunn (darkxst)
summary: - nautilus crashed with SIGABRT in raise()
+ nautilus crashed when clicking on bookmark
Tim Lunn (darkxst)
Changed in ubuntu-gnome:
status: New → Confirmed
importance: Undecided → Low
Tim Lunn (darkxst)
Changed in ubuntu-gnome:
importance: Low → Medium
Revision history for this message
Ubuntu GNOME (ug-bot) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()

Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Stacktrace.txt
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : ThreadStacktrace.txt
Changed in ubuntu-gnome:
status: Confirmed → Invalid
Revision history for this message
Ubuntu GNOME (ug-bot) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

gnome-keyring version 3.7.92-0ubuntu1~raring1 required, but 3.8.2-0ubuntu3~raring1 is available
libgail-3-0 version 3.7.12-1ubuntu1~build1 required, but 3.8.2-3ubuntu4~raring1 is available
nautilus version 1:3.8.0-0ubuntu1~raring required, but 1:3.8.2-0ubuntu1~ubuntu13.04.1 is available
gnome-desktop3-data version 3.8.0.1-0ubuntu1~raring1 required, but 3.8.3-0ubuntu1~ubuntu13.04.1 is available
libgtk-3-0 version 3.7.12-1ubuntu1~build1 required, but 3.8.2-3ubuntu4~raring1 is available
libp11-kit-gnome-keyring version 3.7.92-0ubuntu1~raring1 required, but 3.8.2-0ubuntu3~raring1 is available
libgnome-desktop-3-7 version 3.8.0.1-0ubuntu1~raring1 required, but 3.8.3-0ubuntu1~ubuntu13.04.1 is available
libgcr-3-1 version 3.8.0-1~ubuntu13.04.1 required, but 3.8.2-3~ubuntu13.04.1 is available
outdated debug symbol package for libgcr-3-1: package version 3.8.2-3~ubuntu13.04.1 dbgsym version 3.6.2-0ubuntu2
libgcr-3-common version 3.8.0-1~ubuntu13.04.1 required, but 3.8.2-3~ubuntu13.04.1 is available
libsoup-gnome2.4-1 version 2.42.0-1~raring1 required, but 2.42.2-3~raring1 is available
libnautilus-extension1a version 1:3.8.0-0ubuntu1~raring required, but 1:3.8.2-0ubuntu1~ubuntu13.04.1 is available
libgtk-3-common version 3.7.12-1ubuntu1~build1 required, but 3.8.2-3ubuntu4~raring1 is available
gcr version 3.8.0-1~ubuntu13.04.1 required, but 3.8.2-3~ubuntu13.04.1 is available
libgck-1-0 version 3.8.0-1~ubuntu13.04.1 required, but 3.8.2-3~ubuntu13.04.1 is available
libpam-gnome-keyring version 3.7.92-0ubuntu1~raring1 required, but 3.8.2-0ubuntu3~raring1 is available
nautilus-data version 1:3.8.0-0ubuntu1~raring required, but 1:3.8.2-0ubuntu1~ubuntu13.04.1 is available
libsoup2.4-1 version 2.42.0-1~raring1 required, but 2.42.2-3~raring1 is available
libgtk-3-bin version 3.7.12-1ubuntu1~build1 required, but 3.8.2-3ubuntu4~raring1 is available

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Revision history for this message
Richard Ayotte (rich-ayotte) wrote :

> Please upgrade your system to the latest package versions. If you still
> encounter the crash, please file a new report.

I'm running 13.10 and clicking on a bookmark still causes nautilus to crash.

The bot wants me to file a new report? That's ridiculous. This report was filled seven months ago and since then 72 people have confirmed it and 35 duplicates have been filled. How is one more duplicate filling going to help? At least by keeping this one open, we can preserve history and not clog the system with more bug reports. More bug reports isn't going to stop nautilus from crashing.

Revision history for this message
Ronald Poulin (rrpoulin) wrote : Re: [Bug 1168383] Re: nautilus crashed when clicking on bookmark

I got sick of Gnome and the dev team's responsiveness. I moved on to
another distro and un-subscribed for the other dozen bugs I found. Wheh!

On Sat, Nov 16, 2013 at 5:45 AM, Richard Ayotte <email address hidden>wrote:

> > Please upgrade your system to the latest package versions. If you still
> > encounter the crash, please file a new report.
>
> I'm running 13.10 and clicking on a bookmark still causes nautilus to
> crash.
>
> The bot wants me to file a new report? That's ridiculous. This report
> was filled seven months ago and since then 72 people have confirmed it
> and 35 duplicates have been filled. How is one more duplicate filling
> going to help? At least by keeping this one open, we can preserve
> history and not clog the system with more bug reports. More bug reports
> isn't going to stop nautilus from crashing.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1192239).
> https://bugs.launchpad.net/bugs/1168383
>
> Title:
> nautilus crashed when clicking on bookmark
>
> Status in Ubuntu GNOME:
> Invalid
>
> Bug description:
> Clicking on any Nautilus bookmark causes it to crash. sftp://, ftp://
> and x-nautilus-desktop:/// all have the same result.
>
> ProblemType: Crash
> DistroRelease: Ubuntu 13.04
> Package: nautilus 1:3.8.0-0ubuntu1~raring [origin:
> LP-PPA-gnome3-team-gnome3]
> ProcVersionSignature: Ubuntu 3.8.0-17.27-generic 3.8.6
> Uname: Linux 3.8.0-17-generic x86_64
> NonfreeKernelModules: nvidia
> ApportVersion: 2.9.2-0ubuntu8
> Architecture: amd64
> CrashCounter: 1
> Date: Fri Apr 12 08:04:46 2013
> ExecutablePath: /usr/bin/nautilus
> GsettingsChanges:
> b'org.gnome.nautilus.window-state' b'geometry' b"'967x843+473+165'"
> b'org.gnome.nautilus.window-state' b'sidebar-width' b'312'
> b'org.gnome.nautilus.window-state' b'start-with-sidebar' b'false'
> InstallationDate: Installed on 2011-02-26 (776 days ago)
> InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64
> (20101007.1)
> MarkForUpload: True
> ProcCmdline: /usr/bin/nautilus --no-default-window
> ProcEnviron:
> SHELL=/bin/bash
> PATH=(custom, no user)
> LANG=en_US.utf8
> Signal: 6
> SourcePackage: nautilus
> StacktraceTop:
> raise () from /lib/x86_64-linux-gnu/libc.so.6
> abort () from /lib/x86_64-linux-gnu/libc.so.6
> g_assertion_message () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> g_assertion_message_expr () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
> ?? ()
> Title: nautilus crashed with SIGABRT in raise()
> UpgradeStatus: Upgraded to raring on 2013-04-11 (0 days ago)
> UserGroups: adm admin cdrom dialout libvirtd lpadmin mythtv plugdev
> sambashare vboxusers
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu-gnome/+bug/1168383/+subscriptions
>

Barneedhar (barneedhar)
Changed in ubuntu-gnome:
status: Invalid → Confirmed
Tim Lunn (darkxst)
Changed in ubuntu-gnome:
milestone: none → trusty
Tim Lunn (darkxst)
Changed in ubuntu-gnome:
milestone: trusty → trusty.1
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.