← Back to team overview

kernel-packages team mailing list archive

[Bug 1312159] [NEW] ** (gksu:xxxx): CRITICAL **: fcntl error

 

Public bug reported:

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.

** Affects: linux (Ubuntu)
     Importance: Undecided
         Status: Incomplete

** Attachment added: "photo about the gksu error"
   https://bugs.launchpad.net/bugs/1312159/+attachment/4095371/+files/gksu_error.png

** Description changed:

- I chneged my system from 13.10 to 14.04 by clean install. I got
+ 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.
+ 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.

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1312159

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

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1312159/+subscriptions


Follow ups

References