cannot open nautilus with gksu

[grahammechanical]

apport reported that Nautilus failed and a report would be sent.

Apport is enabled by default in development versions. I doubt very much that Apport would send a report with out our agreement. We have to confirm that the crash should be reported and we usually get a warning that some of the logs may contain stuff like passwords. We have to accept this contain, only then, as I understand it does Apport login to Launchpad and give us the opportunity to report a bug.

Regards.

[pfeiffep]

I did agree - and I found /var/crash/_usr_bin_nautilus.0.crash which contained

Title: nautilus crashed with SIGABRT in g_assertion_message()
UpgradeStatus: No upgrade log present (probably fresh install)
_MarkForUpload: True

I did 'approve' the send, however it was dead ended - nothing launched in Launchpad.

[mc4man]

I did agree - and I found /var/crash/_usr_bin_nautilus.0.crash which contained

I did 'approve' the send, however it was dead ended - nothing launched in Launchpad.

One of the more useful things to do when using dev versions is to ck. the changelogs, in the case of latest apport -

apport (2.14.1-0ubuntu2) trusty; urgency=medium

* etc/apport/crashdb.conf: Disable Launchpad crash/kernel reports for
the final release. Only report to http://errors.ubuntu.com from now on.

[Cavsfan]

Everything working great here! Not even a warning in terminal with "gksu nautilus". System all up to date.
I'm impressed.

[QDR06VV9]

Here it is again after full updates.

 gksu gedit

** (gksu:26771): CRITICAL **: fcntl error

** (gksu:26771): WARNING **: Lock taken by pid: -1. Exiting.
me@me-Aspire-M3300:~$ gksu nautilus

** (gksu:26773): CRITICAL **: fcntl error

** (gksu:26773): WARNING **: Lock taken by pid: -1. Exiting.

So have we determined if this is a bug?

[Cavsfan]

Here it is again after full updates.

 gksu gedit

** (gksu:26771): CRITICAL **: fcntl error

** (gksu:26771): WARNING **: Lock taken by pid: -1. Exiting.
me@me-Aspire-M3300:~$ gksu nautilus

** (gksu:26773): CRITICAL **: fcntl error

** (gksu:26773): WARNING **: Lock taken by pid: -1. Exiting.

So have we determined if this is a bug?

I get no errors with either one:

cavsfan@cavsfan-MS-7529:~$ gksu nautilus
^C
cavsfan@cavsfan-MS-7529:~$ gksu gedit
cavsfan@cavsfan-MS-7529:~$

[QDR06VV9]

I get no errors with either one:

cavsfan@cavsfan-MS-7529:~$ gksu nautilus
^C
cavsfan@cavsfan-MS-7529:~$ gksu gedit
cavsfan@cavsfan-MS-7529:~$

This is going on two machines as of now acer 5750 Intel
And Acer tower M3300 Nvidia
Past couple of days I've been thinking it is hardware related!

[QDR06VV9]

So this is the strangest thing I have seen to date!
I took the hard drive out of the acer laptop and plugged it in to a Lenovo B-570
And it works correctly(gksu gedit or gksu nautilus). My question Why?
Have not tried the tower hard drive yet but I suspect the same results.

[QDR06VV9]

And then replaced the hard dive back to accer 5750 intell i3 Quad core,
Bear in mind this was the machine the install was done on.
And back to fail opening anything using the gksu command.
Have two other hardives(for this lappy) with other OS's installed that just sing perfectly.
Sounds Buggy to me.
I have seen this error "WARNING **: Lock taken by pid: -1 Exiting" Before but never using those gksu commands

[Cavsfan]

That is indeed ironic and strange! I remember the last time I used gksudo gedit before I seen this thread I got a bunch of warnings in terminal.

But no output whatsoever in terminal now. I'm not usually the one without problems.