Many thanks Anders - I can now finally use gksu again!
However, while I think I understand the technical reasons for the way
things are, from a more holistic perspective I disagree that this bug
should be marked invalid for the following reasons:
- It requires _more_ steps to run programs as anot
$ xhost +LOCAL:
non-network local connections being added to access control list
Now you can gksu -u anotheruser program
You can add this command to your startup programs in gnome-session-
properties.
As for using the other users password for authentication is not correct
behaviour. When you su
Still there in Karmic:
warn...@washington:~$ lsb_release -c
Codename: karmic
warn...@washington:~$ gksu -u darrenw firefox
No protocol specifiedNo protocol specified
Error: cannot open display: :0.0
--
gksuexec doesn't work in dapper !
https://bugs.launchpad.net/bugs/47388
You received thi
I can confirm this bug in Ubuntu 9.04 (my first steps with Gnome after
several years of KDE).
=== works =
edu...@nb-ewulff:~$ gksudo -d nautilus
No ask_pass set, using default!
xauth: /tmp/libgksu-u3Ectl/.Xauthority
STARTUP_ID: gksudo/nautilus/16567-0-nb-ewulff_TIME10844278
cmd[0
Still there in 8.10 (I don't have 9.04, and am a little reluctant to
install it yet given that the status of this bug hasn't changed since
dapper - unless you think something has changed that might help, or
there's something I can try?)
(I entered the wrong password on the first attempt, but I've
I can't confirm this symptom in 9.04. Please set the status to:
1) New if reproducible in a supported or development Ubuntu version, or
2) Invalid if you cannot reproduce it in a supported or development Ubuntu
version.
** Changed in: gksu (Ubuntu)
Status: New => Incomplete
--
gksuexec d
I must have been happy inside. Should have said :( though.
--
gksuexec doesn't work in dapper !
https://bugs.launchpad.net/bugs/47388
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.co
Just tried intrepid (beta 1, updated as of 2008/10/08) - same result :)
--
gksuexec doesn't work in dapper !
https://bugs.launchpad.net/bugs/47388
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bugs@li
Still the same result in hardy final. I'll install intrepid in a VM and
let you know what happens.
--
gksuexec doesn't work in dapper !
https://bugs.launchpad.net/bugs/47388
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs
Does this still happen in the final version of hardy? And if so could
you also try in the latest alpha of intrepid?
--
gksuexec doesn't work in dapper !
https://bugs.launchpad.net/bugs/47388
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
sorry for this, I realise my response has absolutely nothing to do with
your problem, I must have written in the wrong tab...
sorry for this
--
gksuexec doesn't work in dapper !
https://bugs.launchpad.net/bugs/47388
You received this bug notification because you are a member of Ubuntu
Bugs, whic
I'm not actually running anything from an application. My use case is
that I have two accounts (one for work, one for personal use).
Occasionally, I'm in one session and want to run a program as my other
account.
It seems that the -u option neither works in gksu, or gksudo.
I'm now running Hardy
There is a difference between gksudo (graphical equivalent to sudo) and
gksu which will prompt for the password of the so called "root" user
(not superuser).
If an application uses gksu by mistake, you'll need to create a root
user, assign a password (sudo passwd root) and use that password of the
[Expired for gksu (Ubuntu) because there has been no activity for 60
days.]
--
gksuexec doesn't work in dapper !
https://bugs.launchpad.net/bugs/47388
You received this bug notification because you are a member of Ubuntu
Bugs, which is a direct subscriber.
--
ubuntu-bugs mailing list
ubuntu-bug
This bug has no assignee - just wondering if it's dropped off the radar,
as it still affects gutsy.
I'm affected by this bug too (though it's now gksu, no gksuexec) - let
me know if there's anything I can do to help debug things.
--
gksuexec doesn't work in dapper !
https://bugs.launchpad.net/bu
** Bug 48265 has been marked a duplicate of this bug
** Bug 59507 has been marked a duplicate of this bug
--
gksuexec doesn't work in dapper !
https://launchpad.net/bugs/47388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
That's not the way it used to work in Hoary and Breezy : if you wanted
to start a program as userB you had to enter userB password.
Note that when you are asked for a password it is written (translating) :
Please enter your password to start "application X" as userB.
--
gksuexec doesn't work in
As far as I understand gksuexec should accept only userA password, exactly like
sudo... Using userB password should not work.
So when you're logged in as UserA, you gksudoexec with userA password
and select userB. You need to have permissions for this of course...
This seems to work as expected,
Ok , tried to test it on edgy eft knot 2... gksuexec is't there anymore
:-(((
--
gksuexec doesn't work in dapper !
https://launchpad.net/bugs/47388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Ok, I made some more tests, this time on a 'clean' install of dapper (as a
guest OS with mware server).
userA is the first account and is sudoer.
userB is the second account and is NOT sudoer.
Login with userA : gksuexec -> id as userB and using userB password :
GNOME_SUDO_PASS
sudo : 1 inco
Thanks for taking care of this bug which is annoying me so much ;-)
I'll try to sum-up everything I can tell you about this bug so far :
- I DO NOT have an explicit root password, I always use sudo from my
main account (userA), which is the only sudoer in the system.
- This bug happened after an
Thanks for this additional information. I just tried to reproduce it and
was not able to.
To reproduced I ran "gksuexec" and selected userB and the "id" command.
The passwort dialog came up asking me for my password and after that
"id" showed the output for userB.
Do you have a explicit root pass
** Changed in: gksu (Ubuntu)
Assignee: Sebastian Heinlein => (unassigned)
--
gksuexec doesn't work in dapper !
https://launchpad.net/bugs/47388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
New comment regarding the last one... and it's getting even more
strange.
This behaviour is happening only when i'm using XGL/compiz, when I start
a 'normal' Gnome session, I'm still at case one : gksuexec isn't working
: no way to launch a program as another user (other than root)...
--
gksuexe
... not completely solved in fact.. ;-)
I cant launch another program as another user, but I need to use the
root password, not the other user's password.
Strange behaviour !!
--
gksuexec doesn't work in dapper !
https://launchpad.net/bugs/47388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ub
It seems that with the new kernel (2.6.15-25-686 ) this problem is now
solved (maybe another package was released with the kernel) ?
--
gksuexec doesn't work in dapper !
https://launchpad.net/bugs/47388
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman
26 matches
Mail list logo
