root nautilus file browser segfaults with "GLib-GIO-CRITICAL **: g_file_has_prefix: assertion `G_IS_FILE (file)' failed"

Bug #803728 reported by Doug McMahon
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
nautilus (Ubuntu)
New
Undecided
Unassigned

Bug Description

Any attempt to open nautilus as root fails, common message is
(nautilus:3298): DEBUG: Syncdaemon not running, waiting for it to start in NameOwnerChanged
Initializing nautilus-gdu extension

(nautilus:3298): GLib-GIO-CRITICAL **: g_file_has_prefix: assertion `G_IS_FILE (file)' failed

(nautilus:3298): GLib-GIO-CRITICAL **: g_file_has_prefix: assertion `G_IS_FILE (file)' failed

ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: nautilus 1:3.1.2-0ubuntu1
ProcVersionSignature: Ubuntu 3.0-2.3-generic 3.0.0-rc4
Uname: Linux 3.0-2-generic i686
Architecture: i386
Date: Wed Jun 29 23:57:25 2011
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha i386 (20110629)
ProcEnviron:
 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
Doug McMahon (mc3man) wrote :
summary: - root nautilus file browser segfaults with Syncdaemon not running,
- waiting for it to start in NameOwnerChanged
+ root nautilus file browser segfaults with "Syncdaemon not running,
+ waiting for it to start in NameOwnerChanged"
Doug McMahon (mc3man)
summary: - root nautilus file browser segfaults with "Syncdaemon not running,
- waiting for it to start in NameOwnerChanged"
+ root nautilus file browser segfaults with "GLib-GIO-CRITICAL **:
+ g_file_has_prefix: assertion `G_IS_FILE (file)' failed"
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.

If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.

Now open your file manager, navigate to your /var/crash directory and open the crash report you wish to submit.
If this fails you will have to open a terminal and file your report with 'ubuntu-bug /var/crash/_my_crash_report.crash' where _my_crash_report.crash is the crash you would like to report. If you get an error that you aren't allowed to access this report you will have to file it with 'sudo ubuntu-bug /var/crash/_my_crash_report.crash'.

I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.

Changed in nautilus (Ubuntu):
status: New → Invalid
Revision history for this message
Doug McMahon (mc3man) wrote :

This is 11.10 - and there is no crash report created though It does 'crash' (segfault

It maybe just a blip in the live cd's, this was on the one from 06/29, I can 100% say that gksu(do) nautilus will not work on that live cd or an install from it.
Have removed the install because of other add. issues, will try either today's or tomorrow's to see if any improvement or the same.

Revision history for this message
useResa (rdrijsen) wrote :

I followed the suggestions as made by Pedro Villavicencio in comment #2.
The submitted bug report can be found as bug #804330

Revision history for this message
Doug McMahon (mc3man) wrote :

Marking as a dupe of new bug I filed against deja-dup

Changed in nautilus (Ubuntu):
status: Invalid → New
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.