You are not logged in.

#26 2010-08-27 17:43:55

irishjava
Member
Registered: 2010-07-13
Posts: 5

Re: [Solved]gksudo problem

I'm using gksudo with Awesome WM and find it incredibly useful. I don't really want to use some big, bloated Gnome/DBUS system.
What I do is have different users for different development work that I might be doing, such as Flash, Java, Python, etc.
I've added to the awesome menu (and happy to share my code with others) some little links to a script which I've created called
runasanother.

Usage of this script is like so :

bin/runasanother flexuser /usr/bin/firefox

I could use sudo directly, and the script does make use of sudo. But what I find particularly useful is to just launch from the
Awesome Pop-up menu, then I don't have a proliferation of consoles.

Also I've set up a local AUR (forgive me if I use the wrong terminology here) customised the libgksu PKGBUILD, successfully built
and installed (using a patch from the gentoo bug system).

And it fixes it. It works now for me. Where is a good place to submit my PKGBUILD file?

Sorry, I'm a total noob to all this.

Offline

#27 2010-08-27 17:54:01

anonymous_user
Member
Registered: 2009-08-28
Posts: 3,059

Re: [Solved]gksudo problem

irishjava wrote:

It works now for me. Where is a good place to submit my PKGBUILD file?

Create an account and upload your PKGBUILD to the AUR?

http://wiki.archlinux.org/index.php/AUR_User_Guidelines

Offline

#28 2010-08-28 13:44:31

jackjackk
Member
Registered: 2010-07-21
Posts: 40

Re: [Solved]gksudo problem

I had the problem

sudo: sorry, a password is required to run sudo

with gksudo. Reinstalling the package libgksu seems to have fixed the problem in my case.

Last edited by jackjackk (2010-08-28 13:53:54)

Offline

#29 2010-08-28 13:50:57

anonymous_user
Member
Registered: 2009-08-28
Posts: 3,059

Re: [Solved]gksudo problem

Edit: nvm its not fixed.

Last edited by anonymous_user (2010-08-28 13:53:59)

Offline

#30 2010-08-28 15:53:34

jackjackk
Member
Registered: 2010-07-21
Posts: 40

Re: [Solved]gksudo problem

I rectify... gksudo works (in my case) ONLY soon after running

sudo pacman -S libgksu

and remaining in the same gnome-terminal: if I use gksudo in another gnome-terminal, the usual "sudo: sorry, a password is required to run sudo" problem comes up. This is very weird! Is anybody experiencing the same behaviour?!

The only uncommented lines in my /etc/sudoers are

root ALL=(ALL) ALL
jack ALL=(ALL) ALL

where jack is my username.

Last edited by jackjackk (2010-08-28 16:15:52)

Offline

#31 2010-08-28 16:31:51

bharani
Member
From: Karaikudi, India
Registered: 2009-07-12
Posts: 202

Re: [Solved]gksudo problem

I added

Defaults !tty_tickets

to my sudoers file .
It allows others terminal to  run  sudo without requring passwords.

Last edited by bharani (2010-08-28 16:32:57)


Tamil is my mother tongue.

Offline

#32 2010-08-28 18:09:11

jackjackk
Member
Registered: 2010-07-21
Posts: 40

Re: [Solved]gksudo problem

Thank bharani! It seems to really work now!

Offline

#33 2010-08-29 12:22:21

naguz
Member
Registered: 2008-11-05
Posts: 98

Re: [Solved]gksudo problem

Are eny one of those still having problems using the new sudoers file (sudoers.pacnew) provided provided after the update?

Offline

#34 2010-08-29 13:54:26

anonymous_user
Member
Registered: 2009-08-28
Posts: 3,059

Re: [Solved]gksudo problem

Yes I used the new sudoers file and gksudo still gives me the message. Heres is my sudoers btw:

## sudoers file.
##
## This file MUST be edited with the 'visudo' command as root.
## Failure to use 'visudo' may result in syntax or file permission errors
## that prevent sudo from running.
##
## See the sudoers man page for the details on how to write a sudoers file.
##

##
## Host alias specification
##
## Groups of machines. These may include host names (optionally with wildcards),
## IP addresses, network numbers or netgroups.
# Host_Alias    WEBSERVERS = www1, www2, www3

##
## User alias specification
##
## Groups of users.  These may consist of user names, uids, Unix groups,
## or netgroups.
# User_Alias    ADMINS = millert, dowdy, mikef

##
## Cmnd alias specification
##
## Groups of commands.  Often used to group related commands together.
# Cmnd_Alias    PROCESSES = /usr/bin/nice, /bin/kill, /usr/bin/renice, \
#                 /usr/bin/pkill, /usr/bin/top

##
## Defaults specification
##
## You may wish to keep some of the following environment variables
## when running commands via sudo.
##
## Locale settings
# Defaults env_keep += "LANG LANGUAGE LINGUAS LC_* _XKB_CHARSET"
##
## Run X applications through sudo; HOME is used to find the
## .Xauthority file.  Note that other programs use HOME to find   
## configuration files and this may lead to privilege escalation!
# Defaults env_keep += "HOME"
##
## X11 resource path settings
# Defaults env_keep += "XAPPLRESDIR XFILESEARCHPATH XUSERFILESEARCHPATH"
##
## Desktop path settings
# Defaults env_keep += "QTDIR KDEDIR"
##
## Allow sudo-run commands to inherit the callers' ConsoleKit session
# Defaults env_keep += "XDG_SESSION_COOKIE"
##
## Uncomment to enable special input methods.  Care should be taken as
## this may allow users to subvert the command being run via sudo.
# Defaults env_keep += "XMODIFIERS GTK_IM_MODULE QT_IM_MODULE QT_IM_SWITCHER"
##
## Uncomment to enable logging of a command's output, except for
## sudoreplay and reboot.  Use sudoreplay to play back logged sessions.
# Defaults log_output
# Defaults!/usr/bin/sudoreplay !log_output
# Defaults!/usr/local/bin/sudoreplay !log_output
# Defaults!/sbin/reboot !log_output

##
## Runas alias specification
##

##
## User privilege specification
##
root ALL=(ALL) ALL

## Uncomment to allow members of group wheel to execute any command
%wheel ALL=(ALL) ALL
%wheel ALL=(ALL) NOPASSWD: /sbin/shutdown

## Same thing without a password
# %wheel ALL=(ALL) NOPASSWD: ALL

## Uncomment to allow members of group sudo to execute any command
# %sudo    ALL=(ALL) ALL

## Uncomment to allow any user to run sudo if they know the password
## of the user they are running the command as (root by default).
# Defaults targetpw  # Ask for the password of the target user
# ALL ALL=(ALL) ALL  # WARNING: only use this together with 'Defaults targetpw'

## Read drop-in files from /etc/sudoers.d (the # here does not mean a comment)
#includedir /etc/sudoers.d

Offline

#35 2010-08-29 15:40:15

naguz
Member
Registered: 2008-11-05
Posts: 98

Re: [Solved]gksudo problem

I do now too. OO But I didn't right after replacing it. Strange.
irishjava: You should also file a bug report and linkt to the patch, so it can be fixed. AFAI can understan this is a bug.

Offline

#36 2010-08-30 20:52:43

Deadguy1
Member
From: IL, USA
Registered: 2009-09-08
Posts: 9

Re: [Solved]gksudo problem

jackjackk wrote:

I rectify... gksudo works (in my case) ONLY soon after running

sudo pacman -S libgksu

and remaining in the same gnome-terminal: if I use gksudo in another gnome-terminal, the usual "sudo: sorry, a password is required to run sudo" problem comes up. This is very weird! Is anybody experiencing the same behaviour?!

The only uncommented lines in my /etc/sudoers are

root ALL=(ALL) ALL
jack ALL=(ALL) ALL

where jack is my username.

same issue here.. I downgraded sudo to 1.7.3-1 for now as gksudo works fine with it..


Linux=Freedom

Offline

#37 2010-09-14 13:11:19

kgas
Member
From: Qatar
Registered: 2008-11-08
Posts: 718

Re: [Solved]gksudo problem

I thing the recent libgksu (libgksu 2.0.12-3) update solved this issue.

Offline

#38 2010-09-14 17:17:23

Deadguy1
Member
From: IL, USA
Registered: 2009-09-08
Posts: 9

Re: [Solved]gksudo problem

kgas wrote:

I thing the recent libgksu (libgksu 2.0.12-3) update solved this issue.

yes it does. thanks for the heads up.


Linux=Freedom

Offline

Board footer

Powered by FluxBB