On Wednesday 30 December 2015 19.59:42 Michele Calgaro wrote: (...)
Now I've got a small problem with superuser rights with some programs. Until now kpackage-trinity and Gostcrypt have shown this behaviour:
- if I start the program (from TDE), at some point it will ask for the
password. Neither the root password nor the user password work.
- if I modify the program "icon" by adding "tdesu" before the command,
the password is asked first, and the program works correctly.
(...)
Thierry
Hi Thierry, I tried to reproduce the problem on my system but I didn't see anything wrong. But maybe I was doing something different from you. Could you file a bug report with detail instructions on how to reproduce the post? Some screenshots would also be useful . Thanks Michele
OK, I once again forgot to link the pictures... :)
Hi Michele,
Not so easy... There's not much showing.
With kpackage, I get the same behaviour wether I start kpackage (from the TDE/kicker menu) or by right-clicking on the *.deb file and choosing "open with":
kpackage opens, I choose install, kpackage asks for the password (snapshot 1). Maybe a clue? It asks for the SUDO password - I have no sudo password. Neither the root nor the user password work. The dialog box disappears, then comes back, and so on.
If I modify the menu command in "tdesu kpackage", kpackage works (albeit I get a "tdeinit could not start tdesu" message...).
I tried starting kpackage from the command line but all I get is:
thierry@haswell:~$ kpackage TQSettings::sync: failed to open '/etc/tqt3/tqt_plugins_3.5rc.tmp' for writing TQLayout "unnamed" added to TQVBox "page", which already has a layout thierry@haswell:~$ ^C thierry@haswell:~$
No idea if this tells you something...
Gostcrypt shows a similar behaviour, but with no message at all. I can select the crypted partition, but when I want to mount it this requires the root password, which is not taken, so of course gostcrypt does not get the superuser rights (snapshot 2). tdesu gostcrypt works perfectly, so this is not really a problem.
I also need tdesu to start synaptic, but this is more to get a nice dialog box (otherwise some text window is used to ask for the root password.
Thank you,
Thierry
On Wednesday 30 December 2015 21:40:45 Thierry de Coulon wrote:
On Wednesday 30 December 2015 19.59:42 Michele Calgaro wrote: (...)
Now I've got a small problem with superuser rights with some programs. Until now kpackage-trinity and Gostcrypt have shown this behaviour:
- if I start the program (from TDE), at some point it will ask for the
password. Neither the root password nor the user password work.
- if I modify the program "icon" by adding "tdesu" before the command,
the password is asked first, and the program works correctly.
(...)
Thierry
Hi Thierry, I tried to reproduce the problem on my system but I didn't see anything wrong. But maybe I was doing something different from you. Could you file a bug report with detail instructions on how to reproduce the post? Some screenshots would also be useful . Thanks Michele
OK, I once again forgot to link the pictures... :)
Hi Michele,
Not so easy... There's not much showing.
With kpackage, I get the same behaviour wether I start kpackage (from the TDE/kicker menu) or by right-clicking on the *.deb file and choosing "open with":
kpackage opens, I choose install, kpackage asks for the password (snapshot 1). Maybe a clue? It asks for the SUDO password - I have no sudo password. Neither the root nor the user password work. The dialog box disappears, then comes back, and so on.
If I modify the menu command in "tdesu kpackage", kpackage works (albeit I get a "tdeinit could not start tdesu" message...).
I tried starting kpackage from the command line but all I get is:
thierry@haswell:~$ kpackage TQSettings::sync: failed to open '/etc/tqt3/tqt_plugins_3.5rc.tmp' for writing TQLayout "unnamed" added to TQVBox "page", which already has a layout thierry@haswell:~$ ^C thierry@haswell:~$
No idea if this tells you something...
Gostcrypt shows a similar behaviour, but with no message at all. I can select the crypted partition, but when I want to mount it this requires the root password, which is not taken, so of course gostcrypt does not get the superuser rights (snapshot 2). tdesu gostcrypt works perfectly, so this is not really a problem.
I also need tdesu to start synaptic, but this is more to get a nice dialog box (otherwise some text window is used to ask for the root password.
Thank you,
Thierry
Speaking as a Debian user, those screen-shots look like Ubuntu screen shots and I suspect that this is another attack of cross-over-itis.
Try :
Change to the directory in which you have placed the file: # dpkg -i kpackage-trinity_3.5.13.2-0debian7.0.0+0_amd64.deb (except that hopefully you have a Jessie one for Jessie and you will need to use that name) Aptitude install all missing dependencies. And if my guess is correct, all will be well.
Though mine installed automatically, which raises the question of why yours did not.
Lisi
Lisi Reisz wrote:
Speaking as a Debian user, those screen-shots look like Ubuntu screen shots and I suspect that this is another attack of cross-over-itis.
Lisi, I don't think so - he has a different theme.
Try :
Change to the directory in which you have placed the file: # dpkg -i kpackage-trinity_3.5.13.2-0debian7.0.0+0_amd64.deb (except that hopefully you have a Jessie one for Jessie and you will need to use that name) Aptitude install all missing dependencies. And if my guess is correct, all will be well.
Though mine installed automatically, which raises the question of why yours did not.
He has a specific question not related to the installation of packages but to the password prompt not accepting the password.
I've had this same annoying password queries but only with gnome programs - it still pops up from time to time. I think it was the wicd and I tried to trace it, but couldn't spent much time on it and dropped the investigation. Perhaps it is debian related. I've seen this also before TDE.
I'm sorry I can not help much.
regards
On Wednesday 30 December 2015 23.58:28 Lisi Reisz wrote:
Speaking as a Debian user, those screen-shots look like Ubuntu screen shots and I suspect that this is another attack of cross-over-itis.
Thanks Lisi for the idea, however the desease would have to be TDE-internal: this is a brand new install on a formated partition and the only repos added are deb-multimedia and TDE's.
Try :
Change to the directory in which you have placed the file: # dpkg -i kpackage-trinity_3.5.13.2-0debian7.0.0+0_amd64.deb (except that hopefully you have a Jessie one for Jessie and you will need to use that name) Aptitude install all missing dependencies. And if my guess is correct, all will be well.
I tried this. By the way, reading the header of TDE's Packages list, I read:
Origin: LP-PPA-trinity-trinity-r14.0.0 Label: Trinity Desktop Environment R14.0.0 Suite: jessie Version: 8.0 Codename: jessie Date: Mon, 23 Nov 2015 22:13:40 UTC Architectures: amd64 armel armhf i386 ppc64el Components: main Description: Ubuntu Jessie 8.0
Does that mean Ubuntu and Jessie share the same binary?
Anyway, I downloaded kpackage from the TDE repositories and installed it new - no change. So the origin of the problem is deeper.
Deloptes says he's seen this "before TDE", so I assume KDE 3, and with Gnome programs. I guess somehow these program makes a call for password using some "software" that is both "wrong" enough not to process the answer to the right place but "right" enough not to throw some usable error - but this is a very theoretical guess and I'm afraid I'm totaly unable to go scout the code to find what it could be.
As there are workarounds, I can live with this.
You say your install does not show that. How did you install Jessie (I mean what UI did you choose prior to installing TDE)? Maybe this could have an effect on the behaviour.
I installed with Gnome 3. Installing TDE removes some Gnome programs because of "incompatibilities", maybe the source of the problem is there?
Have a nice day,
Thierry
On Thursday 31 December 2015 12:10:23 am Thierry de Coulon wrote:
You say your install does not show that. How did you install Jessie (I mean what UI did you choose prior to installing TDE)? Maybe this could have an effect on the behaviour.
I installed with Gnome 3. Installing TDE removes some Gnome programs because of "incompatibilities", maybe the source of the problem is there?
I use Debian, I usually install the base+standard, then add TDE repo's to my sources list. Using Gnome3 could be a source of issues. If I need a desktop environment to add TDE I usually use just a window manager and xorg to access help on the interent.
On Thursday 31 of December 2015 10:10:23 Thierry de Coulon wrote:
I tried this. By the way, reading the header of TDE's Packages list, I read:
Origin: LP-PPA-trinity-trinity-r14.0.0 Label: Trinity Desktop Environment R14.0.0 Suite: jessie Version: 8.0 Codename: jessie Date: Mon, 23 Nov 2015 22:13:40 UTC Architectures: amd64 armel armhf i386 ppc64el Components: main Description: Ubuntu Jessie 8.0
Does that mean Ubuntu and Jessie share the same binary?
Official packages are built on 'QuickBuild', which is an implementation of the Ubuntu Launchpad. Therefore, all distributions are called 'Ubuntu', although it is a Debian or Raspbian.
On Thursday 31 December 2015 11.10:00 Slávek Banko wrote:
Official packages are built on 'QuickBuild', which is an implementation of the Ubuntu Launchpad. Therefore, all distributions are called 'Ubuntu', although it is a Debian or Raspbian.
-- Slávek
Thanks Slávek for enlightening me on this (I had never bothered to look what QuickBuild is...).
Thierry
Thierry de Coulon wrote:
Deloptes says he's seen this "before TDE", so I assume KDE 3, and with Gnome programs. I guess somehow these program makes a call for password using some "software" that is both "wrong" enough not to process the answer to the right place but "right" enough not to throw some usable error - but this is a very theoretical guess and I'm afraid I'm totaly unable to go scout the code to find what it could be.
I suspect it to be something dbus related, but usually when I get the issue it is when I'm no in the local lan, but somewhere on the road and want to configure the wicd to use some other wlan. The workaround is to cancel all the prompts.
Perhaps you could create a new user and login first to TDE with that user. Check the kwallet as well and if the user is in the sudo group (this because you mentioned something about ksu).
I have no issue with TDE apps. I would love to use network manager instead of wicd, but it turned out it is linked to systemd ...
regards
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512
On 12/30/2015 10:40 PM, Thierry de Coulon wrote:
On Wednesday 30 December 2015 19.59:42 Michele Calgaro wrote: (...)
Now I've got a small problem with superuser rights with some programs. Until now kpackage-trinity and Gostcrypt have shown this behaviour:
- if I start the program (from TDE), at some point it will ask for the password. Neither the root password nor
the user password work.
- if I modify the program "icon" by adding "tdesu" before the command, the password is asked first, and the
program works correctly.
(...)
Thierry
Hi Thierry, I tried to reproduce the problem on my system but I didn't see anything wrong. But maybe I was doing something different from you. Could you file a bug report with detail instructions on how to reproduce the post? Some screenshots would also be useful . Thanks Michele
OK, I once again forgot to link the pictures... :)
Hi Michele,
Not so easy... There's not much showing.
With kpackage, I get the same behaviour wether I start kpackage (from the TDE/kicker menu) or by right-clicking on the *.deb file and choosing "open with":
kpackage opens, I choose install, kpackage asks for the password (snapshot 1). Maybe a clue? It asks for the SUDO password - I have no sudo password. Neither the root nor the user password work. The dialog box disappears, then comes back, and so on.
If I modify the menu command in "tdesu kpackage", kpackage works (albeit I get a "tdeinit could not start tdesu" message...).
I tried starting kpackage from the command line but all I get is:
thierry@haswell:~$ kpackage TQSettings::sync: failed to open '/etc/tqt3/tqt_plugins_3.5rc.tmp' for writing TQLayout "unnamed" added to TQVBox "page", which already has a layout thierry@haswell:~$ ^C thierry@haswell:~$
No idea if this tells you something...
Gostcrypt shows a similar behaviour, but with no message at all. I can select the crypted partition, but when I want to mount it this requires the root password, which is not taken, so of course gostcrypt does not get the superuser rights (snapshot 2). tdesu gostcrypt works perfectly, so this is not really a problem.
I also need tdesu to start synaptic, but this is more to get a nice dialog box (otherwise some text window is used to ask for the root password.
Thank you,
Thierry
Hi Thierry, I tried the same operation on my system (Debian/Stretch) and did not have any problem, after typing the root password I could install a package and also remove it. Obviously there must be some differences somewhere, so I have file bug report 2570 so we don't forget about it.
Cheers and Happy New Year to all users. Michele
On Wednesday 30 December 2015 12:40:45 pm Thierry de Coulon wrote:
On Wednesday 30 December 2015 19.59:42 Michele Calgaro wrote: (...)
Now I've got a small problem with superuser rights with some programs. Until now kpackage-trinity and Gostcrypt have shown this behaviour:
- if I start the program (from TDE), at some point it will ask for the
password. Neither the root password nor the user password work.
- if I modify the program "icon" by adding "tdesu" before the command,
the password is asked first, and the program works correctly.
(...)
Thierry
Hi Thierry, I tried to reproduce the problem on my system but I didn't see anything wrong. But maybe I was doing something different from you. Could you file a bug report with detail instructions on how to reproduce the post? Some screenshots would also be useful . Thanks Michele
OK, I once again forgot to link the pictures... :)
Hi Michele,
Not so easy... There's not much showing.
With kpackage, I get the same behaviour wether I start kpackage (from the TDE/kicker menu) or by right-clicking on the *.deb file and choosing "open with":
kpackage opens, I choose install, kpackage asks for the password (snapshot 1). Maybe a clue? It asks for the SUDO password - I have no sudo password. Neither the root nor the user password work. The dialog box disappears, then comes back, and so on.
If I modify the menu command in "tdesu kpackage", kpackage works (albeit I get a "tdeinit could not start tdesu" message...).
I tried starting kpackage from the command line but all I get is:
thierry@haswell:~$ kpackage TQSettings::sync: failed to open '/etc/tqt3/tqt_plugins_3.5rc.tmp' for writing TQLayout "unnamed" added to TQVBox "page", which already has a layout thierry@haswell:~$ ^C thierry@haswell:~$
No idea if this tells you something...
Gostcrypt shows a similar behaviour, but with no message at all. I can select the crypted partition, but when I want to mount it this requires the root password, which is not taken, so of course gostcrypt does not get the superuser rights (snapshot 2). tdesu gostcrypt works perfectly, so this is not really a problem.
I also need tdesu to start synaptic, but this is more to get a nice dialog box (otherwise some text window is used to ask for the root password.
Thank you,
Thierry
tdesu is a graphical frontend to 'su', root privledges, afaik uses the root password, This os different that the 'sudo' related TDE stuff, sudo et al uses the users password.The user has to be in the sudo group to work. No separate sudo password.
Your second png shows tdesudo being installed, all the TDE sudo packages depend on 'sudo', should be installed I 'am thinking, add users to the 'sudo' group.
another way to manage sudo users is with 'visudo' as root.
I would be supspicious of Gnome stuff, is gksu installed?
On Thursday 31 December 2015 16.49:38 Greg Madden wrote:
Thierry
tdesu is a graphical frontend to 'su', root privledges, afaik uses the root password,
Yes, and it works that way. Launching any program with "tdesu <program name>" takes the root password and runs the program with root privileges.
This os different that the 'sudo' related TDE stuff, sudo et al uses the users password.The user has to be in the sudo group to work. No separate sudo password.
Your second png shows tdesudo being installed, all the TDE sudo packages depend on 'sudo', should be installed I 'am thinking, add users to the 'sudo' group.
tdesudo is _not_ installed (at least synaptic does not list it as installed)
I would be supspicious of Gnome stuff, is gksu installed?
No, not installed either.
another way to manage sudo users is with 'visudo' as root.
Adding my user to the sudo group (with kuser), the user password works in kpackage.
I think this is logical, as visudo shows:
# User privilege specification root ALL=(ALL:ALL) ALL
# Allow members of group sudo to execute any command %sudo ALL=(ALL:ALL) ALL
But what is not logical is that kpackage expects a sudo password when tdesudo is not installed. I thought not installing sudo meant using the root password. Debain was not installed with sudo, so why is it working?
Thierry
On Thursday 31 December 2015 16.49:38 Greg Madden wrote:
another way to manage sudo users is with 'visudo' as root. Greg
Visudo was the way to go, but this way:
- comment out the sudo line
- add Defaults targetpw ALL ALL=(ALL) ALL
This way it seems the programs tyke the root password.
Thierry
-
deloptes -
Greg Madden -
Lisi Reisz -
Michele Calgaro -
Slávek Banko -
Thierry de Coulon