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

[György Szokolai]

I chaneged my system from 13.10 to 14.04 by clean install. I got kerneloops on 14.04 beta 2 so I went back to 13.10.

To try to new kernel on 14.04 I installed it yesterday. After the clean install and run updates my first task was to modify the grub and fstab. I'm using for it the gksu gedit command. Now I got error message and gedit not opened. For example:

barricade@Barricade:~$ gksu gedit /etc/fstab

(gksu:4983): Gtk-WARNING **: Failed to set text from markup due to error parsing markup: Error on line 1 char 86: Element 'b' was closed, but the currently open element is 'big'

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

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

We talked about it on hungarian ubuntu forum and got same message from gksu other user too. I tryed to purge and reinstall the gksu but it not solved the problem. The sudo nano /etc/fstab and sudo gedit /etc/fstab commands working well.

I tryed reinstall all system but the gksu problem is occured again.
---
ApportVersion: 2.14.1-0ubuntu3
Architecture: amd64
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
InstallationDate: Installed on 2014-04-23 (0 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
Package: linux (not installed)
Tags: trusty
Uname: Linux 3.15.0-031500rc2-generic x86_64
UnreportableReason: The running kernel is not an Ubuntu kernel
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 1312159

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[György Szokolai (gyszokol)]

apport information

[György Szokolai (gyszokol)]

Hi Brad,

thank you for your help! Running of apport-collect 1312159 is done.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.15 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.15-rc2-trusty/

[György Szokolai (gyszokol)]

I've been using the latest kernel because I got kerneloops by original kernel. I got propsed to trying the 3.15rc2 kernel for possible solution (it is a second day without freezing, hopefully - it was my first bug report). Other users can use the original kernel. This problem is not kernel related I think, is it?

[Launchpad Janitor (janitor)]

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

[Mathias Burén (mathias-buren)]

ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
DistroRelease: Ubuntu 12.04
MarkForUpload: True
Package: gksu 2.0.2-6ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 SHELL=/bin/bash
Tags: precise
Uname: Linux 3.15.0-997-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout lpadmin plugdev sambashare sudo

[Mathias Burén (mathias-buren)]

apport information

[Mathias Burén (mathias-buren)]

ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
DistroRelease: Ubuntu 12.04
MarkForUpload: True
Package: gksu 2.0.2-6ubuntu1
PackageArchitecture: amd64
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 SHELL=/bin/bash
Tags: precise
Uname: Linux 3.14.0-997-lowlatency x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dialout lpadmin plugdev sambashare sudo

[Mathias Burén (mathias-buren)]

apport information

[Mathias Burén (mathias-buren)]

I have attached a report from 3.14.0-997-lowlatency where gksu works, and from 3.15.0-997-lowlatency where gksu doesn work.

[penalvch (penalvch)]

Mathias Burén, please do not apport-collect to another person's report. Instead, so your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[penalvch (penalvch)]

György Szokolai, did this problem not occur in a release prior to Trusty?

[György Szokolai (gyszokol)]

gksu is worked well on 13.10. It is a new problem by 14.04

[galen (galen-technomage)]

I currently testing ubuntu 14.10 and I have this problem only with the kernel 3.15 ( testing or R.C(*) releases )

There is no problem with the kernel 3.13 or 3.14.

[penalvch (penalvch)]

galen, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

[penalvch (penalvch)]

György Szokolai, in your Saucy install could you please test the latest Trusty kernel via https://launchpad.net/~ubuntu-security/+archive/ppa/+build/5972522 and advise on the results?

[Doug McMahon (mc3man)]

Not sure why this is still "incomplete"?
In any event can be seen on any current 14.10 install (currently 3.15.0-1-generic #5-Ubuntu SMP

What 'works' is to remove ~/.gksu.lock, then gksudo <anything> will work *once*, after that will again fail unless mentioned file is removed.

Similar bug - Bug 1321704

[Doug McMahon (mc3man)]

Also note that gdebi will be similary affected, not adding due to this reports incomplete state

[Doug McMahon (mc3man)]

Final note: this is somehow related to "grab mode" of Screen Grabbing. If it's disabled then gksu works as expected

[Cavsfan (cavsfan)]

gksu is completely broken and this bug is incomplete and medium security? That is odd.

[Cavsfan (cavsfan)]

I meant medium importance.

[Doug McMahon (mc3man)]

It's been claimed to have been fixed with the 3.15-rc6 kernel
If so may be from this commit
http://www.spinics.net/lists/linux-fsdevel/msg75089.html

[György Szokolai (gyszokol)]

Sorry guys I can't help anymoe in this case becaus I cwitched to Manjaro and now Debian. Manjaro was work well till last update when I got x.org freeze same as on Ubuntu 14.04. I have ATI Radeon HD 3650 512...

[penalvch (penalvch)]

György Szokolai, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/gksu/+bug/1312159/comments/26 regarding you are not using Ubuntu. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[ubername (ubername)]

I am also unable to run gksu command in ubuntu using main repository kernels. If I delete ~/gksu.lock before each gksu command I can use whatever I need admin privileges for.

[penalvch (penalvch)]

ubername, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs