nautilus crashed with SIGABRT in g_assertion_message()

Bug #1275946 reported by Bibek on 2014-02-03
22
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Medium
Unassigned

Bug Description

crashed while trying to use gksudo nautilus

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: nautilus 1:3.10.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-6.23-generic 3.13.0
Uname: Linux 3.13.0-6-generic x86_64
ApportVersion: 2.13.2-0ubuntu2
Architecture: amd64
Date: Mon Feb 3 15:48:04 2014
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2014-02-03 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140203)
ProcCmdline: nautilus
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 LANGUAGE=en_US
 SHELL=/bin/bash
Signal: 6
SourcePackage: nautilus
StacktraceTop:
 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 g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

Bibek (justwagle) wrote :
Bibek (justwagle) on 2014-02-06
information type: Private → Public Security
Bibek (justwagle) on 2014-02-06
information type: Public Security → Public
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in nautilus (Ubuntu):
status: New → Confirmed

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

tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Changed in nautilus (Ubuntu):
importance: Undecided → Medium
Sebastien Bacher (seb128) wrote :

The bug is quite old and the code changed since, also there has been no new report of that specific problem nor activity for some years so assuming it has been resolved and closing the ticket. If you still get issues in newer versions feel free to open a new report though.

Changed in nautilus (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers