Ubuntu
nautilus package

Nautilus restart fails

Bug #945878 reported by peterzay
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Nautilus
Unknown
Low
nautilus (Ubuntu)
Triaged
Low
Unassigned

Bug Description

The following restart command

nautilus -q && nautilus

fails as per attached terminal session.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: nautilus 1:3.3.90-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-17.27-generic-pae 3.2.6
Uname: Linux 3.2.0-17-generic-pae i686
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Sat Mar 3 16:37:14 2012
EcryptfsInUse: Yes
GsettingsChanges: org.gnome.nautilus.window-state geometry '800x550+79+38'
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120228.1)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: nautilus
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
peterzay (peterzay) wrote :
Lamine Manel (geekette86)
Changed in nautilus (Ubuntu):
status: New → Incomplete
status: Incomplete → Confirmed
status: Confirmed → Incomplete
Revision history for this message
peterzay (peterzay) wrote :

Scott,

Could you please provide any assistance that Lamine may require.

Thanks.

Revision history for this message
Scott Kitterman (kitterman) wrote :

I'm really not the right person for that. I just wanted to make sure the right bug got filled.

peterzay (peterzay)
Changed in nautilus (Ubuntu):
status: Incomplete → New
Revision history for this message
Vadim Rutkovsky (roignac) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Unfortunately, we cannot work on this bug because your description didn't include enough information. You may find it helpful to read "How to report bugs effectively" http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at http://wiki.ubuntu.com/DebuggingProcedures

At a minimum, we need:
1. the specific steps or actions you took that caused you to encounter the problem,
2. the behavior you expected, and
3. the behavior you actually encountered (in as much detail as possible).
Thanks!

Changed in nautilus (Ubuntu):
status: New → Incomplete
Revision history for this message
peterzay (peterzay) wrote :

Please refer to Bug #862609 comments starting at #32.

Changed in nautilus (Ubuntu):
status: Incomplete → New
Revision history for this message
Vadim Rutkovsky (roignac) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a valgrind log following the instructions at https://wiki.ubuntu.com/Valgrind and attach the file to the bug report. This will greatly help us in tracking down your problem.

Changed in nautilus (Ubuntu):
status: New → Incomplete
Revision history for this message
peterzay (peterzay) wrote :

You will find attached the requested valgrind log.

Changed in nautilus (Ubuntu):
status: Incomplete → New
Revision history for this message
Vadim Rutkovsky (roignac) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at https://bugzilla.gnome.org/show_bug.cgi?id=671435

Changed in nautilus (Ubuntu):
status: New → Confirmed
Sebastien Bacher (seb128)
Changed in nautilus (Ubuntu):
importance: Undecided → Low
status: Confirmed → Triaged
Bug Watch Updater (bug-watch-updater)
Changed in nautilus:
importance: Unknown → Low
status: Unknown → New
Bug Watch Updater (bug-watch-updater)
Changed in nautilus:
status: New → Unknown
Revision history for this message
Hibou57 (Yannick Duchêne) (yannick-duchene) wrote :

By the way, in prior versions of Ubuntu, a simple “nautilus -q” was enough to make Nautilus restart. Since Ubuntu 12.04, if one just do “nautilus -q” as before, then the desktop disappears, and that's probably why the OP wants “nautilus -q && nautilus”.

Trying to restart Nautilus the way he wants, I get this error:

    Could not register the application: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus).

Whether I do it from a console or from a script, the result is the same.

I use to do it with pre‑12.04 Ubuntu versions, from script, to update the environment after some refreshing (update-mime-database, update-menus and the like).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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