Using sudo to run nautilus with root permission to change the owner of a folder causes a crash

Bug #1163237 reported by Haakon_Løtveit
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

I ran a window of nautilus using sudo, to get root permissions.
Then I tried to change the owner of a folder. (It was really an hdd mounted in that folder if that matters.)

I set the owner to "Haakon" in the gui, and nautilus crashed.
Reopening nautilus to fix this resulted in more crashing, with the same error: "User \"Haakon\" does not exist".
My real username would be "haakon", and when going back and setting it manually using chown, nautilus happily accepted it, and stopped choking on that folder.

(Does nautilus convert properly between upper and lower case?)

From apt-cache policy nautilus:
nautilus:
  Installert: 1:3.6.3-0ubuntu13
  Kandidat: 1:3.6.3-0ubuntu13
  Versjonstabell:
 *** 1:3.6.3-0ubuntu13 0
        500 http://no.archive.ubuntu.com/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status

From lsb_release:
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: nautilus 1:3.6.3-0ubuntu13
ProcVersionSignature: Ubuntu 3.8.0-14.24-generic 3.8.4
Uname: Linux 3.8.0-14-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Tue Apr 2 11:12:54 2013
ExecutablePath: /usr/bin/nautilus
GsettingsChanges:

InstallationDate: Installed on 2013-04-01 (0 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130326)
MarkForUpload: True
ProcCmdline: nautilus
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=nb_NO.UTF-8
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 SHELL=/bin/bash
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: No upgrade log present (probably fresh install)
UserGroups:

Revision history for this message
Haakon_Løtveit (haakon-lotveit) wrote :
information type: Private → Public
Revision history for this message
Apport retracing service (apport) wrote :

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

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
tags: added: apport-failed-retrace
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nautilus (Ubuntu):
status: New → Confirmed
Revision history for this message
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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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