14 Oct
2010
14 Oct
'10
12:10 a.m.
Jimmy Johnson wrote:
Ok, first of all we are talking about Debian and not
Ubuntu.
Trinity is using a 15min time out, the sudoers file used is the same
as what is in normal Debian system, I know I can change the sudoers
file and add ",timestamp_timeout=0" to set it to ask for a passwd each
time you need to be superuser, but like I said the sudoers file is the
same as Squeeze without Trinity.
So the question is what else can be causing this 15min timeout?
What ever it is I want it to die, I want it to behave like a normal
Debian system and not like a Ubuntu system.
Thanks,
I notice in the console, kde4 squeeze when I run "sudo synaptic and
enter the passwd" that I get the error: (synaptic:28768): Gtk-WARNING
**: cannot open display: :0.0
In, trinity squeeze when I run "sudo synaptic and enter the passwd"
synaptic opens.
In kde4, gksu in the console opens synaptic needing the passwd.
In trinity, gksu in the console opens synaptic without the passwd.
These are all clues, but, I'm too ignorant to know what is causing the
difference, probably something to do with sudo not timing out.
All I know is that someway-somehow I would like to get the Debian behavior.
I'm sure it's something simple in the Trinity way and the Debian way
that is causing all these permission differences, after all this is a
Debian system, not a Ubuntu system.
At the same time I would like to say that my trinity ubuntu 10.04 system
is great, I mostly use it while the squeeze system has these bugs.
The trinity 10.10 system has been doing some really weird things, like
logging out and back in to find all kinds of desktop settings have
changed, but I really would rather not get into that as the squeeze
install is more important to me.
--
Jimmy Johnson
Debian Squeeze - Trinity KDE 3.5.12 at sda12
Registered Linux User #380263