*** This bug is a duplicate of bug 50971 ***
https://bugs.launchpad.net/bugs/50971
[Expired for kdebase (Ubuntu) because there has been no activity for 60
days.]
--
kdesu fails when invoked immediately after sudo from terminal
https://bugs.launchpad.net/bugs/72545
You received this bug notif
*** This bug is a duplicate of bug 50971 ***
Yes, 'sudo -k' and 'sudo -K' should (and do) also remove the problem, if
done on the right pseudo-terminal.
--
kdesu fails when invoked immediately after sudo from terminal
https://launchpad.net/bugs/72545
--
kubuntu-bugs mailing list
kubuntu-bugs@l
*** This bug is a duplicate of bug 50971 ***
Does sudo -k work as a workaround?
sudo apt-get update
sudo -k
kdesu kate /etc/apt/sources.list
--
kdesu fails when invoked immediately after sudo from terminal
https://launchpad.net/bugs/72545
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu
*** This bug is a duplicate of bug 50971 ***
About workarounds:
- Opening a new instance of Konsole (or two) occupying some new pts's should
normally help.
- Also, you can set the option "timestamp_timeout=0" in '/etc/sudoers', which
will force 'sudo' to always ask for the password. (This wouldn
*** This bug is a duplicate of bug 50971 ***
Marking this a dupe of 72545.
Now that we know where the problem actually is, we're more likely to be
able to fix this. (as opposed to it being random)
** This bug has been marked a duplicate of bug 50971
kdesu will not start apps
--
kdesu fail
That was a clear explanation of what was happening. Is there a
workaround for this? If so why shouldn't the workaround be made in the
default installation so that newbies are not put off? Also, why is it
that kdesu needs two instances of sudo?
--
kdesu fails when invoked immediately after sudo
I will concisely document here my reasoning.
In essence, 'kdesu' needs two instances of 'sudo', and each 'sudo' needs
a terminal (tty) or, in this case, a pseudo-terminal (pts). This is
because '/etc/sudoers' defines that we are using "tty_tickets", i.e.
that for each tty or pts we need to input t
A common typo. You mean bug #50971.
I believe your interpretation of what happens is correct. Incidentally,
I have been exploring this issue too, after my last comment, and meaning
to post here in essence the same explanation as yours. (I arrived at the
same conclusion based on observing what hap
This appears to be a duplicate of bug #50791. I have posted an
explanation attempt there which may or may not be correct.
--
kdesu fails when invoked immediately after sudo from terminal
https://launchpad.net/bugs/72545
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ub
I just experienced this, trying to launch an application (synaptic)
requiring kdesu after a number of commands involving sudo in a konsole.
All I got was the launch feedback, but no kdesu dialog. A 'sudo -K'
actually helped, oddly enough. And no, I don't currently have a way to
reproduce this.
--
I can't really tell how long it takes, often no more than a few minutes
if I had to guess. I use Edgy and the easiest way to reproduce this is
to do a 'sudo ...' in e.g. konsole, 'exit' and trying to run Adept as
soon as possible. Sometimes it's (seemingly) persistent and the only
thing that works
Jera, do you also have a long time between the kdesu dialogue opening.
For both of you, what happens when you type "exit" after you use sudo in
the konsole and try to open Adept. Does this problem persist? What kind
of systems are you both using? Do you have any ideas on ways to
reproduce these bug
I can confirm this problem, but it occurs at random. When I use sudo in
a console and immediately try to open Adept, it sometimes refuses to
show the kdesu dialog.
--
kdesu fails when invoked immediately after sudo from terminal
https://launchpad.net/bugs/72545
--
kubuntu-bugs mailing list
kubu
13 matches
Mail list logo
