In the absence of kdesu, or tdesu, how do you run eg KWrite or Konqueror as root in 14 on Debian? Even gksu seems still to be missing this time.
Lisi
On 07/26/2015 03:54 PM, Lisi Reisz wrote:
In the absence of kdesu, or tdesu, how do you run eg KWrite or Konqueror as root in 14 on Debian? Even gksu seems still to be missing this time.
Main menu / System / SuperUser, you should have both kwrite and konqueror.
To make other run-as-root menu items, make the item in Menu Editor, check "Run as a different user", and put root for the Username.
On Monday 27 July 2015 00:03:11 Dan Youngquist wrote:
On 07/26/2015 03:54 PM, Lisi Reisz wrote:
In the absence of kdesu, or tdesu, how do you run eg KWrite or Konqueror as root in 14 on Debian? Even gksu seems still to be missing this time.
Main menu / System / SuperUser, you should have both kwrite and konqueror.
To make other run-as-root menu items, make the item in Menu Editor, check "Run as a different user", and put root for the Username.
Thanks, Dan. I'll try it.
Lisi
On Monday 27 July 2015 00:03:11 Dan Youngquist wrote:
On 07/26/2015 03:54 PM, Lisi Reisz wrote:
In the absence of kdesu, or tdesu, how do you run eg KWrite or Konqueror as root in 14 on Debian? Even gksu seems still to be missing this time.
Main menu / System / SuperUser, you should have both kwrite and konqueror.
Unfortunately Konqueror and Konsole. :-( Konsole is easy anyway - launch as normal user and su to root. Buty I miss my beloved KWrite. :-(
To make other run-as-root menu items, make the item in Menu Editor, check "Run as a different user", and put root for the Username.
Still haven't tried this.
Lisi
Lisi Reisz composed on 2015-07-29 23:22 (UTC+0100):
Dan Youngquist wrote:
Lisi Reisz wrote:
In the absence of kdesu, or tdesu, how do you run eg KWrite or Konqueror as root in 14 on Debian? Even gksu seems still to be missing this time.
Main menu / System / SuperUser, you should have both kwrite and konqueror.
Unfortunately Konqueror and Konsole. :-(
What's wrong with getting where you need to go via Konsole?
Konsole is easy anyway - launch as normal user and su to root.
Even easier than that .....
Buty I miss my beloved KWrite. :-(
To make other run-as-root menu items, make the item in Menu Editor, check "Run as a different user", and put root for the Username.
Still haven't tried this.
How often due you find it necesary to edit as root? Is there some problem using a readily available but more generic editor instead of KWrite for such tasks?
..... http://fm.no-ip.com/SS/KDE/tde14KonsoleSessionMenu.png http://fm.no-ip.com/SS/KDE/tde14KonsoleSessionMenu.png
Are these Konsole session menu options missing on Jessie? MCEdit is how most system configuration maintenance gets done on all my installations. And of course, MC is one of the oldest and most feature packed file managers available. http://www.softpanorama.org/OFM/Paradigm/
On Thursday 30 July 2015 01:02:13 Felix Miata wrote:
Lisi Reisz composed on 2015-07-29 23:22 (UTC+0100):
Dan Youngquist wrote:
Lisi Reisz wrote:
In the absence of kdesu, or tdesu, how do you run eg KWrite or Konqueror as root in 14 on Debian? Even gksu seems still to be missing this time.
Main menu / System / SuperUser, you should have both kwrite and konqueror.
Unfortunately Konqueror and Konsole. :-(
What's wrong with getting where you need to go via Konsole?
I can't get there. I run Debian.
Konsole is easy anyway - launch as normal user and su to root.
Even easier than that .....
Buty I miss my beloved KWrite. :-(
To make other run-as-root menu items, make the item in Menu Editor, check "Run as a different user", and put root for the Username.
Still haven't tried this.
How often due you find it necesary to edit as root? Is there some problem using a readily available but more generic editor instead of KWrite for such tasks?
Not often. But when I do I find KWrite much the best for me. I don't have ot run TDE. I could run KDE44 or Gnome or LXDE. I don't have ot run KWrite. In fact, at the moment I can't run KWrite as root, but I want to run KWrite. And yes, there is a problem - I can't see anything else as well. But even if there weren't, why shouldn't I try to run it just because I want to?
I shall continue to try to use those facilities of TDE that I have particularly valued over the years. If I can't, I can't. One day I may even be forced to choose between KDE4 and Windows.
...
http://fm.no-ip.com/SS/KDE/tde14KonsoleSessionMenu.png http://fm.no-ip.com/SS/KDE/tde14KonsoleSessionMenu.png
Are these Konsole session menu options missing on Jessie? MCEdit is how most system configuration maintenance gets done on all my installations. And of course, MC is one of the oldest and most feature packed file managers available. http://www.softpanorama.org/OFM/Paradigm/
Sorry, I can't see what you are getting at here. But no, Konsole doesn't offer me mc. Probably because I haven't got mc installed.
Lisi
Am Donnerstag, 30. Juli 2015 schrieb Lisi Reisz:
On Thursday 30 July 2015 01:02:13 Felix Miata wrote:
Lisi Reisz composed on 2015-07-29 23:22 (UTC+0100):
Dan Youngquist wrote:
Lisi Reisz wrote:
In the absence of kdesu, or tdesu, how do you run eg KWrite or Konqueror as root in 14 on Debian? Even gksu seems still to be missing this time.
Main menu / System / SuperUser, you should have both kwrite and konqueror.
Unfortunately Konqueror and Konsole. :-(
What's wrong with getting where you need to go via Konsole?
I can't get there. I run Debian.
Konsole is easy anyway - launch as normal user and su to root.
Even easier than that .....
Buty I miss my beloved KWrite. :-(
To make other run-as-root menu items, make the item in Menu Editor, check "Run as a different user", and put root for the Username.
Still haven't tried this.
How often due you find it necesary to edit as root? Is there some problem using a readily available but more generic editor instead of KWrite for such tasks?
Not often. But when I do I find KWrite much the best for me. I don't have ot run TDE. I could run KDE44 or Gnome or LXDE. I don't have ot run KWrite. In fact, at the moment I can't run KWrite as root, but I want to run KWrite. And yes, there is a problem - I can't see anything else as well. But even if there weren't, why shouldn't I try to run it just because I want to?
I shall continue to try to use those facilities of TDE that I have particularly valued over the years. If I can't, I can't. One day I may even be forced to choose between KDE4 and Windows.
...
http://fm.no-ip.com/SS/KDE/tde14KonsoleSessionMenu.png http://fm.no-ip.com/SS/KDE/tde14KonsoleSessionMenu.png
Are these Konsole session menu options missing on Jessie? MCEdit is how most system configuration maintenance gets done on all my installations. And of course, MC is one of the oldest and most feature packed file managers available. http://www.softpanorama.org/OFM/Paradigm/
Sorry, I can't see what you are getting at here. But no, Konsole doesn't offer me mc. Probably because I haven't got mc installed.
Lisi
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi Lisi!
Press <alt>+<F2> and enter: tdesu kwrite
Nik
HI, Nik,
On Thursday 30 July 2015 09:18:26 Dr. Nikolaus Klepp wrote:
Press <alt>+<F2> and enter: tdesu kwrite
That is what doesn't work in R14. :-( It is what, mutatis mutandis, I have done for years, and what I shall file a wish bug to be able to do again/still. It is. or rather, sadly, was, great!
Lisi
Am Donnerstag, 30. Juli 2015 schrieb Lisi Reisz:
HI, Nik,
On Thursday 30 July 2015 09:18:26 Dr. Nikolaus Klepp wrote:
Press <alt>+<F2> and enter: tdesu kwrite
That is what doesn't work in R14. :-( It is what, mutatis mutandis, I have done for years, and what I shall file a wish bug to be able to do again/still. It is. or rather, sadly, was, great!
Lisi
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Hi Lisi!
It works here on R14.0.1 and tdesu is installed by tdebase-trinity-bin so I assume it's installed on your computer. But if /opt/trinity/bin is not in your path that command will fail more or less silently. Could you please open konsole, there enter:
/opt/trinity/bin/tdesu /opt/trinity/bin/kwrite
and post the output from the console? BTY, on my computer it takes about 15 seconds for kwrite to open.
Nik
Hi, Nik :-)
On Thursday 30 July 2015 10:22:00 Dr. Nikolaus Klepp wrote:
It works here on R14.0.1 and tdesu is installed by tdebase-trinity-bin so I assume it's installed on your computer. But if /opt/trinity/bin is not in your path that command will fail more or less silently. Could you please open konsole, there enter:
/opt/trinity/bin/tdesu /opt/trinity/bin/kwrite
and post the output from the console? BTY, on my computer it takes about 15 seconds for kwrite to open.
It ran KWrite as root, and in less than 15 seconds. No other output.
You would appear to have cracked it, Nik. I just have to sort out my paths.
Thank you. :-))
Lisi
On Thursday 30 July 2015 10:45:39 Lisi Reisz wrote:
Hi, Nik :-)
On Thursday 30 July 2015 10:22:00 Dr. Nikolaus Klepp wrote:
It works here on R14.0.1 and tdesu is installed by tdebase-trinity-bin so I assume it's installed on your computer. But if /opt/trinity/bin is not in your path that command will fail more or less silently. Could you please open konsole, there enter:
/opt/trinity/bin/tdesu /opt/trinity/bin/kwrite
and post the output from the console? BTY, on my computer it takes about 15 seconds for kwrite to open.
It ran KWrite as root, and in less than 15 seconds. No other output.
You would appear to have cracked it, Nik. I just have to sort out my paths.
/opt/trinity/bin is in my $PATH. :-(
Where next?
(It did occur to me as I ran between computers that it must be, because KWrite launches fine as $USER.)
Lisi
Am Donnerstag, 30. Juli 2015 schrieb Lisi Reisz:
On Thursday 30 July 2015 10:45:39 Lisi Reisz wrote:
Hi, Nik :-)
On Thursday 30 July 2015 10:22:00 Dr. Nikolaus Klepp wrote:
It works here on R14.0.1 and tdesu is installed by tdebase-trinity-bin so I assume it's installed on your computer. But if /opt/trinity/bin is not in your path that command will fail more or less silently. Could you please open konsole, there enter:
/opt/trinity/bin/tdesu /opt/trinity/bin/kwrite
and post the output from the console? BTY, on my computer it takes about 15 seconds for kwrite to open.
It ran KWrite as root, and in less than 15 seconds. No other output.
You would appear to have cracked it, Nik. I just have to sort out my paths.
/opt/trinity/bin is in my $PATH. :-(
Where next?
(It did occur to me as I ran between computers that it must be, because KWrite launches fine as $USER.)
Lisi
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Please start konsole, type: $ tdesu kwrite
What is the output that line and the next command prompt "$ "?
Nik
On Thursday 30 July 2015 11:36:40 Dr. Nikolaus Klepp wrote:
Am Donnerstag, 30. Juli 2015 schrieb Lisi Reisz:
On Thursday 30 July 2015 10:45:39 Lisi Reisz wrote:
Hi, Nik :-)
On Thursday 30 July 2015 10:22:00 Dr. Nikolaus Klepp wrote:
It works here on R14.0.1 and tdesu is installed by tdebase-trinity-bin so I assume it's installed on your computer. But if /opt/trinity/bin is not in your path that command will fail more or less silently. Could you please open konsole, there enter:
/opt/trinity/bin/tdesu /opt/trinity/bin/kwrite
and post the output from the console? BTY, on my computer it takes about 15 seconds for kwrite to open.
It ran KWrite as root, and in less than 15 seconds. No other output.
You would appear to have cracked it, Nik. I just have to sort out my paths.
/opt/trinity/bin is in my $PATH. :-(
Where next?
(It did occur to me as I ran between computers that it must be, because KWrite launches fine as $USER.)
Lisi
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Please start konsole, type: $ tdesu kwrite
What is the output that line and the next command prompt "$ "?
No output. It ran perfectly. So I thought: If it can run from konsole, why not from launcher? So I tried again in launcher. And tdesu now runs perfectly. Well, with all three of teh applications I want it to run with, and I don't care about anyhting else!!
So you, Alexandre and Dan have cracked it, it now woprks, and I haven't got a clue what I did that worked. :-/
But thank you all very much.
Lisi
On Thu, 30 Jul 2015 11:02:02 +0100 Lisi Reisz lisi.reisz@gmail.com wrote:
On Thursday 30 July 2015 10:45:39 Lisi Reisz wrote:
Hi, Nik :-)
On Thursday 30 July 2015 10:22:00 Dr. Nikolaus Klepp wrote:
It works here on R14.0.1 and tdesu is installed by tdebase-trinity-bin so I assume it's installed on your computer. But if /opt/trinity/bin is not in your path that command will fail more or less silently. Could you please open konsole, there enter:
/opt/trinity/bin/tdesu /opt/trinity/bin/kwrite
and post the output from the console? BTY, on my computer it takes about 15 seconds for kwrite to open.
It ran KWrite as root, and in less than 15 seconds. No other output.
You would appear to have cracked it, Nik. I just have to sort out my paths.
/opt/trinity/bin is in my $PATH. :-(
Where next?
(It did occur to me as I ran between computers that it must be, because KWrite launches fine as $USER.)
Maybe you've got a rogue nonfunctional tdesu installed somewhere earlier in your $PATH?
E. Liddell
On Thursday 30 July 2015 11:42:09 E. Liddell wrote:
On Thu, 30 Jul 2015 11:02:02 +0100
Lisi Reisz lisi.reisz@gmail.com wrote:
On Thursday 30 July 2015 10:45:39 Lisi Reisz wrote:
Hi, Nik :-)
On Thursday 30 July 2015 10:22:00 Dr. Nikolaus Klepp wrote:
It works here on R14.0.1 and tdesu is installed by tdebase-trinity-bin so I assume it's installed on your computer. But if /opt/trinity/bin is not in your path that command will fail more or less silently. Could you please open konsole, there enter:
/opt/trinity/bin/tdesu /opt/trinity/bin/kwrite
and post the output from the console? BTY, on my computer it takes about 15 seconds for kwrite to open.
It ran KWrite as root, and in less than 15 seconds. No other output.
You would appear to have cracked it, Nik. I just have to sort out my paths.
/opt/trinity/bin is in my $PATH. :-(
Where next?
(It did occur to me as I ran between computers that it must be, because KWrite launches fine as $USER.)
Maybe you've got a rogue nonfunctional tdesu installed somewhere earlier in your $PATH?
It now looks as though the real one was not functioning, and has somehow been stirred into functioning. Unless this is right, and all the stirring around has moved the real one up the pecking order?
Anything I can do to find out? If there is a rogue one floating around, I should perhaps get rid of it.
I am baffled but delighted. I do love this list!!
Lisi
Lisi Reisz composed on 2015-07-30 08:58 (UTC+0100):
Felix Miata wrote:
Lisi Reisz composed on 2015-07-29 23:22 (UTC+0100):
Dan Youngquist wrote:
Lisi Reisz wrote:
In the absence of kdesu, or tdesu, how do you run eg KWrite or Konqueror as root in 14 on Debian? Even gksu seems still to be missing this time.
Main menu / System / SuperUser, you should have both kwrite and konqueror.
Unfortunately Konqueror and Konsole. :-(
What's wrong with getting where you need to go via Konsole?
I can't get there. I run Debian.
I don't understand. I thought you were running Jessie. ;-) What does running Debian have to do with whatever your objection with Konq and/or Konsole is?
How often due you find it necesary to edit as root? Is there some problem using a readily available but more generic editor instead of KWrite for such tasks?
Not often. But when I do I find KWrite much the best for me. I don't have ot run TDE. I could run KDE44 or Gnome or LXDE. I don't have ot run KWrite. In fact, at the moment I can't run KWrite as root, but I want to run KWrite. And yes, there is a problem - I can't see anything else as well. But even if there weren't, why shouldn't I try to run it just because I want to?
I wasn't suggesting giving up your preferences, only offering workarounds for the period until such time as your expectations can be met.
I shall continue to try to use those facilities of TDE that I have particularly valued over the years. If I can't, I can't. One day I may even be forced to choose between KDE4 and Windows.
We don't want that, especially Win10, with its expanded intrusion on privacy. ;-)
...
http://fm.no-ip.com/SS/KDE/tde14KonsoleSessionMenu.png http://fm.no-ip.com/SS/KDE/tde14KonsoleSessionMenu.png
Are these Konsole session menu options missing on Jessie? MCEdit is how most system configuration maintenance gets done on all my installations. And of course, MC is one of the oldest and most feature packed file managers available. http://www.softpanorama.org/OFM/Paradigm/
Sorry, I can't see what you are getting at here. But no, Konsole doesn't offer me mc. Probably because I haven't got mc installed.
Is the root shell option missing from your Konsole menu too?
I find it inexplicable that default installs cant be bothered to include this unequaled tool. :-(
On Thursday 30 July 2015 09:32:48 Felix Miata wrote:
Lisi Reisz composed on 2015-07-30 08:58 (UTC+0100):
Felix Miata wrote:
Lisi Reisz composed on 2015-07-29 23:22 (UTC+0100):
Dan Youngquist wrote:
Lisi Reisz wrote:
In the absence of kdesu, or tdesu, how do you run eg KWrite or Konqueror as root in 14 on Debian? Even gksu seems still to be missing this time.
Main menu / System / SuperUser, you should have both kwrite and konqueror.
Unfortunately Konqueror and Konsole. :-(
What's wrong with getting where you need to go via Konsole?
I can't get there. I run Debian.
I don't understand. I thought you were running Jessie. ;-) What does running Debian have to do with whatever your objection with Konq and/or Konsole is?
Debian, by default, will not run a GUI as root. So if oyu try to run a GUI application from the root Konsole you get:
root@Tux-II:/home/lisi# kwrite Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed root@Tux-II:/home/lisi#
How often due you find it necesary to edit as root? Is there some problem using a readily available but more generic editor instead of KWrite for such tasks?
Not often. But when I do I find KWrite much the best for me. I don't have ot run TDE. I could run KDE44 or Gnome or LXDE. I don't have ot run KWrite. In fact, at the moment I can't run KWrite as root, but I want to run KWrite. And yes, there is a problem - I can't see anything else as well. But even if there weren't, why shouldn't I try to run it just because I want to?
I wasn't suggesting giving up your preferences, only offering workarounds for the period until such time as your expectations can be met.
I use nano. I just don't like it anyhting like as much.
I shall continue to try to use those facilities of TDE that I have particularly valued over the years. If I can't, I can't. One day I may even be forced to choose between KDE4 and Windows.
We don't want that, especially Win10, with its expanded intrusion on privacy. ;-)
...
http://fm.no-ip.com/SS/KDE/tde14KonsoleSessionMenu.png http://fm.no-ip.com/SS/KDE/tde14KonsoleSessionMenu.png
Are these Konsole session menu options missing on Jessie? MCEdit is how most system configuration maintenance gets done on all my installations. And of course, MC is one of the oldest and most feature packed file managers available. http://www.softpanorama.org/OFM/Paradigm/
Sorry, I can't see what you are getting at here. But no, Konsole doesn't offer me mc. Probably because I haven't got mc installed.
Is the root shell option missing from your Konsole menu too?
Of course not.
I find it inexplicable that default installs cant be bothered to include this unequaled tool. :-(
Debian has decided not to allow GUI root log-ins. It is not a case of "not being bothered", and there is nothing wrong with Konsole (which is supplied by TDE, not Debian). mc is missing only because I have not got mc installed. You didn't ask about the rest of the menu.
In R14 <tdesu konsole> doesn't work either, but is easier to work round.
Lisi
On Thursday 30 July 2015 04:57:53 am Lisi Reisz wrote: (snip)
What's wrong with getting where you need to go via Konsole?
I can't get there. I run Debian.
I don't understand. I thought you were running Jessie. ;-) What does running Debian have to do with whatever your objection with Konq and/or Konsole is?
Debian, by default, will not run a GUI as root. So if oyu try to run a GUI application from the root Konsole you get:
root@Tux-II:/home/lisi# kwrite Session management error: Authentication Rejected, reason : None of the authentication protocols specified are supported and host-based authentication failed root@Tux-II:/home/lisi#
I am currently playing with Debian on another box. This has become a source of some frustration to me, as I'm used to being able to work as root when I want to, GUI and all!
(snip)
Sorry, I can't see what you are getting at here. But no, Konsole doesn't offer me mc. Probably because I haven't got mc installed.
It's often one of the first things that I add after an installation. :-)
(snip)
Debian has decided not to allow GUI root log-ins. It is not a case of "not being bothered", and there is nothing wrong with Konsole (which is supplied by TDE, not Debian).
I don't know where this is defined, but if I find it I'm surely going to change it!
As of this point in time, I find that if I log in as root in a text console, ignoring the GUI login for the moment, then I can "startx" and it will get me there. But there's no obvious way to choose what desktop I want, so even though I have several installed (TDE is coming soon! :-) I'm stuck in Xfce.
Anybody know how to fix either of these things?
Roy J. Tellason, Sr. composed on 2015-08-12 10:05 (UTC-0400):
Lisi Reisz wrote:
Debian has decided not to allow GUI root log-ins. It is not a case of
I'm not so sure whether it has anything to do with Debian, but rather the default tdm config file specifies safer when there are alternatives available.
"not being bothered", and there is nothing wrong with Konsole (which is supplied by TDE, not Debian).
I don't know where this is defined, but if I find it I'm surely going to change it!
root@myhost# whoami root root@myhost:~# ps -A | egrep 'mc|onsole' 1152 ? 00:00:01 konsole 1167 pts/2 00:00:00 mc root@myhost:~# uname -a Linux myhost 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux root@gmyhost:~# grep PRETTY /etc/os-release PRETTY_NAME="Debian GNU/Linux 8 (jessie)" root@myhost:~# egrep 'root|wRoot' /etc/trinity/tdm/tdmrc AllowRootLogin=true SelectedUsers=root,...
As of this point in time, I find that if I log in as root in a text console, ignoring the GUI login for the moment, then I can "startx" and it will get me there. But there's no obvious way to choose what desktop I want, so even though I have several installed (TDE is coming soon! :-) I'm stuck in Xfce.
Anybody know how to fix either of these things?
Man startx.
Simply startx works here with TDE as the already selected/default session. startx /opt/trinity/bin/starttde also works here, but it disregards my xrandr display startup commands in /etc/X11/*.
On Wednesday 12 August 2015 16:49:56 Felix Miata wrote:
Debian has decided not to allow GUI root log-ins. It is not a case of
I'm not so sure whether it has anything to do with Debian, but rather the default tdm config file specifies safer when there are alternatives available.
Well, I have always understood from other Debian users that it does, I have used several different DEs with Debian, all with the same set-up, and it does not apply to all other distros whichever DE you use. I have not had a GUI root log-in since I abandoned a brief spell with OpenSuse many years ago.
I have always installed Debian with root enabled. This may make a difference.
Lisi
On Wednesday 12 August 2015 01:45:08 pm Lisi Reisz wrote:
On Wednesday 12 August 2015 16:49:56 Felix Miata wrote:
Debian has decided not to allow GUI root log-ins. It is not a case of
I'm not so sure whether it has anything to do with Debian, but rather the default tdm config file specifies safer when there are alternatives available.
Well, I have always understood from other Debian users that it does, I have used several different DEs with Debian, all with the same set-up, and it does not apply to all other distros whichever DE you use. I have not had a GUI root log-in since I abandoned a brief spell with OpenSuse many years ago.
I have always installed Debian with root enabled. This may make a difference.
I don't remember ever being offered that option when I installed. Nor a few other things that I was used to, like being able to configure my network as opposed to the installation just using DHCP because it found DHCP on the network. :-(
Where is this option available? Or was I supposed to install with some specific invocation that I missed?
On Wednesday 12 August 2015 19:16:22 Roy J. Tellason, Sr. wrote:
I don't remember ever being offered that option when I installed. Nor a few other things that I was used to, like being able to configure my network as opposed to the installation just using DHCP because it found DHCP on the network. :-(
Where is this option available? Or was I supposed to install with some specific invocation that I missed?
It is a question asked during the install.
As far as I can remember, having a root log-in is default, but you are offered the chance to refuse. But I have only installed Jessie twice, so may be misremebering it, because that is certainly what happens in Wheezy. But I certainly had no problem installing with root.
How, with what, and with what .iso, did you install?
Lisi
On Wednesday 12 August 2015 05:56:09 pm Lisi Reisz wrote:
On Wednesday 12 August 2015 19:16:22 Roy J. Tellason, Sr. wrote:
I don't remember ever being offered that option when I installed. Nor a few other things that I was used to, like being able to configure my network as opposed to the installation just using DHCP because it found DHCP on the network. :-(
Where is this option available? Or was I supposed to install with some specific invocation that I missed?
It is a question asked during the install.
As far as I can remember, having a root log-in is default, but you are offered the chance to refuse. But I have only installed Jessie twice, so may be misremebering it, because that is certainly what happens in Wheezy. But I certainly had no problem installing with root.
It may be that it asked me if I wanted a root login to be created during the install process, is that what you're talking about?
How, with what, and with what .iso, did you install?
The DVD I used is in the drive at the moment, I was looking over some doc files. It's the first one you can download for the 8.1 release.
I'd downloaded 7.0 a while back (hard to believe that it's been a couple of years already!) and tried to install that one on my workbench computer, which was not successful. That machine has Slackware, Ubuntu, and a couple of others on it that I was taking a look at. Then I downloaded 8.0 more recently, and tried to install on this workstation on my desk, but I ran into some issue or other, I can't recall just what offhand. Thankfully I had also downloaded a "live" DVD and booting into that one and using the install option there worked.
I managed to trash my first install pretty good, and had to re-install. The second one also went fine, and I then proceeded to install a number of software packages that I want to get to know and to use. One of the first was mc, I'm just used to using it. :-) Also some CAD packages and assorted other technical stuff. So I'm at the point where I'd really rather not have to go through all that again.
I selected several desktop environments so I could evaluate them and see what they were like, figuring that I'd add TDE to the mix. I just haven't gotten around to that yet.
I'm used to booting into a textmode console on my machines, and doing "startx" to get a GUI going. The default here seems to be to boot into the GUI, and I don't recall being offered a choice about that, either. I know how to go in and fiddle with inittab, but now I'm reading that this setup uses something else entirely, so I've gotta figure that one out too. I'm also used to being able to log in as root, and use a GUI as that user, and that hasn't worked out as well as I'd hoped either. At this point I can select a number of different desktop environments with the GUI login screen as a regular user, but logging into a text console as root and then doing startx I am stuck with Xfce, which I find limiting. The darn games don't even seem to work!
I do have my network shares mounted, which is strange because I see a failure indicated during the boot process, yet they're all there.
TDE is pretty high up on my list, as I'm used to KDE 3.x, which is what I'm using now on this laptop, with Slackware 12.1 under the hood. Can you tell I'm not usually in any big hurry to upgrade? :-)
Roy J. Tellason, Sr. composed on 2015-08-12 20:17 (UTC-0400):
I'm used to booting into a textmode console on my machines, and doing "startx" to get a GUI going. The default here seems to be to boot into the GUI, and I don't recall being offered a choice about that, either. I know how to go in and fiddle with inittab, but now I'm reading that this setup uses something else entirely, so I've gotta figure that one out too. I'm also used to being able to log in as root, and use a GUI as that user, and that hasn't worked out as well as I'd hoped either. At this point I can select a number of different desktop environments with the GUI login screen as a regular user,
The user-friendly distros' installers all default to providing a GUI login manager. Main exceptions I expect would be Gentoo and Slackware.
The old way of getting started without any GUI login manager for most distros (Debian and its derivatives excepted) was through inittab setting something other than 5 the default runlevel line. In distros that replaced sysvinit with systemd (e.g. Jessie) the new default configuration for GUI login manager is found thus:
# systemctl get-default
which will output
graphical.target
To by default stop init prior to X startup, do
# systemctl set-default multi-user.default
However, as with sysvinit, as with all rpm distros with which I am familiar, all the above can be disregarded, and yet not have X automatically start, simply by including a 2 or a 3 on the kernel's cmdline in the bootloader stanza you use. Debian and its derivatives (e.g. *buntu) using sysvinit differed from rpm distros by including X autostart in runlevel 2 and not defining any additional startups in runlevels 3-5.
but logging into a text console as root and then doing startx I am stuck with Xfce, which I find limiting.
When I've found myself up against failure of cmdline arguments to startx to get the WM session I want, I start the GUI login manager (usually KDM3 or TDM) and login selecting some other WM, which in some situations became the new default used by startx after login manager shutdown.
In openSUSE, changing the system level default WM session defined for the login manager has up to now at least been via /etc/sysconfig/windowmanager. Other distros control it someplace I never seem to be able to locate. I know at some point in time, user-level control could be via ~/.dmrc specifying something other than "default" from among the content of usr/share/xsessions. I think user-level selection may be something alternatively available via ~/.xinitrc, but I don't recall ever trying without tripping over other problems.
On Wednesday 12 August 2015 10:05:22 pm Felix Miata wrote:
Roy J. Tellason, Sr. composed on 2015-08-12 20:17 (UTC-0400):
I'm used to booting into a textmode console on my machines, and doing "startx" to get a GUI going. The default here seems to be to boot into the GUI, and I don't recall being offered a choice about that, either. I know how to go in and fiddle with inittab, but now I'm reading that this setup uses something else entirely, so I've gotta figure that one out too. I'm also used to being able to log in as root, and use a GUI as that user, and that hasn't worked out as well as I'd hoped either. At this point I can select a number of different desktop environments with the GUI login screen as a regular user,
The user-friendly distros' installers all default to providing a GUI login manager. Main exceptions I expect would be Gentoo and Slackware.
I've never looked at Gentoo, basically because from what I've read it appears that it would be *way* more time-consuming. In terms of other choices, I picked Debian since an awful lot of what else was out there was derived from it. Now I'm not so sure of my choice. I *did* feel that it was a good idea to get acquainted with some distro that used a package manager, so Debian seemed the logical choice.
The old way of getting started without any GUI login manager for most distros (Debian and its derivatives excepted) was through inittab setting something other than 5 the default runlevel line. In distros that replaced sysvinit with systemd (e.g. Jessie) the new default configuration for GUI login manager is found thus:
# systemctl get-default
Wow. Typing systemctl by itself sure brings up a lot of stuff... :-)
I guess I need to get acquainted with this bit of software now, as opposed to simply going in and editing a text config file in /etc like I'm used to doing. Lots of complications there...
which will output
graphical.target
It did.
To by default stop init prior to X startup, do
# systemctl set-default multi-user.default
I'll try that just before I'm ready to reboot the system next. Mostly I just leave it running...
However, as with sysvinit, as with all rpm distros with which I am familiar, all the above can be disregarded, and yet not have X automatically start, simply by including a 2 or a 3 on the kernel's cmdline in the bootloader stanza you use. Debian and its derivatives (e.g. *buntu) using sysvinit differed from rpm distros by including X autostart in runlevel 2 and not defining any additional startups in runlevels 3-5.
The bootloader is another issue. I'm used to LILO, not GRUB. So I have more to learn here, too.
but logging into a text console as root and then doing startx I am stuck with Xfce, which I find limiting.
When I've found myself up against failure of cmdline arguments to startx to get the WM session I want, I start the GUI login manager (usually KDM3 or TDM) and login selecting some other WM, which in some situations became the new default used by startx after login manager shutdown.
That's the part I'm not clear on at the moment, how I select which WM gets active when I startx...
In openSUSE, changing the system level default WM session defined for the login manager has up to now at least been via /etc/sysconfig/windowmanager.
That file doesn't seem to exist here. There's a /etc/sysctl.d directory, and a /etc/systemd directory, a lot of stuff to sort through.
Other distros control it someplace I never seem to be able to locate.
That's one of the things that drives me nuts with regard to this stuff. Lots and lots of complications, and it's not apparent to me why they changed things to be that way, what the advantage is.
I know at some point in time, user-level control could be via ~/.dmrc specifying something other than "default" from among the content of usr/share/xsessions. I think user-level selection may be something alternatively available via ~/.xinitrc, but I don't recall ever trying without tripping over other problems.
Yup!
Try looking at
man systemd.directives
which seems to refer mostly to a whole LOT of other man pages...! Almost 5000 lines worth, "contains 1621 entries in 14 sections, referring to 177 individual manual pages". Wow.
So at this point I need to resolve getting it to boot the way I want it to, being able to select which WM I want, finding out why my printer won't duplex when it does from this laptop, and installing TDE when they get around to that new release. Among other things...
Roy J. Tellason, Sr. composed on 2015-08-13 11:58 (UTC-0400):
I've never looked at Gentoo, basically because from what I've read it appears that it would be *way* more time-consuming. In terms of other
It is more time consuming, waiting for compiles for every package installed. But, you learn things you'd not likely ever learn otherwise, and the result is you have more control and knowledge of your system, and a lot less installed software that you'll never use.
choices, I picked Debian since an awful lot of what else was out there was derived from it. Now I'm not so sure of my choice. I *did* feel that
Debian's LTS nature can be a compelling reason for choosing it.
it was a good idea to get acquainted with some distro that used a package manager, so Debian seemed the logical choice.
My favorite package manager was the youngest around until Fedora 22 was released, when Yum was replaced by DNF, making DNF the newest. I find openSUSE's Zypper and YaST2 combination unbeatable in terms of power, ease of use and friendliness. Zypper is cmdline only. YaST2 has ncurses and GUI modes. Both use the same RPM foundation and databases, so they can freely be switched between, just not both run at the same time. Their package locking system is simple and easy to use yet as powerful as anyone could hope for.
...
To by default stop init prior to X startup, do
# systemctl set-default multi-user.default
I'll try that just before I'm ready to reboot the system next. Mostly I just leave it running...
It doesn't matter when. AFAICT, default.target has no effect on anything already running.
However, as with sysvinit, as with all rpm distros with which I am familiar, all the above can be disregarded, and yet not have X automatically start, simply by including a 2 or a 3 on the kernel's cmdline in the bootloader stanza you use. Debian and its derivatives (e.g. *buntu) using sysvinit differed from rpm distros by including X autostart in runlevel 2 and not defining any additional startups in runlevels 3-5.
The bootloader is another issue. I'm used to LILO, not GRUB. So I have more to learn here, too.
Note that there is both the original Grub, now typically called Grub Legacy, and Grub2, which some distros call Grub while others call it Grub2. The newer is significantly different, much more powerful, and much tougher to deal with manually if manually is your pleasure for configuration management. Grub Legacy doesn't support EFI, can be tricky or impossible to use with storage capacity >2TB, but doesn't cry the sky is falling when you wish to install it to a partition instead of MBR, nor complain when a vga= is on cmdline. Grub is my primary bootloader on every one of my many systems, always on a primary partition, never the MBR. Grub2 here is only ever installed to Debian or its derivatives, and not used to actually boot except when wanting to select a prior kernel version to boot.
...
In openSUSE, changing the system level default WM session defined for the login manager has up to now at least been via /etc/sysconfig/windowmanager.
That file doesn't seem to exist here. There's a /etc/sysctl.d directory, and a /etc/systemd directory, a lot of stuff to sort through.
I don't think very many distros use /etc/sysconfig/ any more, if they ever did. I do think on openSUSE it's used mostly or entirely by YaST2.
Other distros control it someplace I never seem to be able to locate.
That's one of the things that drives me nuts with regard to this stuff. Lots and lots of complications, and it's not apparent to me why they changed things to be that way, what the advantage is.
It seems distros are more and more catching on that /etc/ is where sysadmin deviation from default configs belong while defaults belong in /usr/ along with the software. ...
On Thursday 13 August 2015 01:17:34 Roy J. Tellason, Sr. wrote:
On Wednesday 12 August 2015 05:56:09 pm Lisi Reisz wrote:
On Wednesday 12 August 2015 19:16:22 Roy J. Tellason, Sr. wrote:
I don't remember ever being offered that option when I installed. Nor a few other things that I was used to, like being able to configure my network as opposed to the installation just using DHCP because it found DHCP on the network. :-(
Where is this option available? Or was I supposed to install with some specific invocation that I missed?
It is a question asked during the install.
As far as I can remember, having a root log-in is default, but you are offered the chance to refuse. But I have only installed Jessie twice, so may be misremebering it, because that is certainly what happens in Wheezy. But I certainly had no problem installing with root.
It may be that it asked me if I wanted a root login to be created during the install process, is that what you're talking about?
How, with what, and with what .iso, did you install?
The DVD I used is in the drive at the moment, I was looking over some doc files. It's the first one you can download for the 8.1 release.
I'd downloaded 7.0 a while back (hard to believe that it's been a couple of years already!) and tried to install that one on my workbench computer, which was not successful. That machine has Slackware, Ubuntu, and a couple of others on it that I was taking a look at. Then I downloaded 8.0 more recently, and tried to install on this workstation on my desk, but I ran into some issue or other, I can't recall just what offhand. Thankfully I had also downloaded a "live" DVD and booting into that one and using the install option there worked.
I managed to trash my first install pretty good, and had to re-install. The second one also went fine, and I then proceeded to install a number of software packages that I want to get to know and to use. One of the first was mc, I'm just used to using it. :-) Also some CAD packages and assorted other technical stuff. So I'm at the point where I'd really rather not have to go through all that again.
I selected several desktop environments so I could evaluate them and see what they were like, figuring that I'd add TDE to the mix. I just haven't gotten around to that yet.
I'm used to booting into a textmode console on my machines, and doing "startx" to get a GUI going. The default here seems to be to boot into the GUI, and I don't recall being offered a choice about that, either. I know how to go in and fiddle with inittab, but now I'm reading that this setup uses something else entirely,
Welcome, or otherwise, to the world of systemd.
so I've gotta figure that one out too. I'm also used to being able to log in as root, and use a GUI as that user, and that hasn't worked out as well as I'd hoped either. At this point I can select a number of different desktop environments with the GUI login screen as a regular user, but logging into a text console as root and then doing startx I am stuck with Xfce, which I find limiting.
I would expect you to be able to just uninstall the dm (gdm3? kdm?), boot into the command line, log-in as whomsoever you wish, and startx. ISTR that you can put the GUI you want to boot into from startx in an x conf file (.xsession? probably not). I did this once, but it was ages ago and my memory is fading.
The darn games don't even seem to work!
I do have my network shares mounted, which is strange because I see a failure indicated during the boot process, yet they're all there.
TDE is pretty high up on my list, as I'm used to KDE 3.x, which is what I'm using now on this laptop, with Slackware 12.1 under the hood. Can you tell I'm not usually in any big hurry to upgrade? :-)
If you are a KDE3-aholic you'll love TDE.
FWIW, all those seem minor and soluble to me.
Lisi
Lisi Reisz composed on 2015-08-14 00:49 (UTC+0100):
I would expect you to be able to just uninstall the dm (gdm3? kdm?), boot into the command line, log-in as whomsoever you wish, and startx. ISTR that you can put the GUI you want to boot into from startx in an x conf file (.xsession? probably not). I did this once, but it was ages ago and my memory is fading.
In Jessie it here appears that to make TDM the default DM all that's required is to include the following as the only content in /etc/X11/default-display-manager:
/opt/trinity/bin/tdm
Roy J. Tellason, Sr. composed on 2015-08-12 14:16 (UTC-0400):
Lisi Reisz wrote:
I have always installed Debian with root enabled. This may make a difference.
I don't remember ever being offered that option when I installed. Nor a few other things that I was used to, like being able to configure my network as opposed to the installation just using DHCP because it found DHCP on the network. :-(
Where is this option available? Or was I supposed to install with some specific invocation that I missed?
I don't know those answers, but I have 97%+ fixed IP installations regardless of distro here, and nearly always installations are via HTTP. This is from the installer's syslog from the Jessie installation I referred to upthread:
Jul 11 03:02:18 kernel: [ 0.000000] Command line: expert net.ifnames=0 ipv6.disable=1 netcfg/disable_dhcp=true netcfg/get_hostname=myhost hw-detect/start_pcmcia=false tasks=standard base-installer/install-recommends=false nosplash splash=0 DEBIAN_FRONTEND=gtk vga=788
Unless I edited it on the fly, which I do not remember now a month later, that cmdline resulted from a Grub (Legacy) stanza I created after reading Debian network installation instructions. Key to avoiding DHCP at the outset is the inclusion of netcfg/disable_dhcp=true while tasks=standard and base-installer/install-recommends=false are about preventing litter from other desktops' deps on a system intended to have TDE as its only DM.
AFAIR, I created zero ordinary users until quite some time after installation was over and I had rebooted several times.
On Wednesday 12 August 2015 07:13:39 pm Felix Miata wrote:
Roy J. Tellason, Sr. composed on 2015-08-12 14:16 (UTC-0400):
Lisi Reisz wrote:
I have always installed Debian with root enabled. This may make a difference.
I don't remember ever being offered that option when I installed. Nor a few other things that I was used to, like being able to configure my network as opposed to the installation just using DHCP because it found DHCP on the network. :-(
Where is this option available? Or was I supposed to install with some specific invocation that I missed?
I don't know those answers, but I have 97%+ fixed IP installations regardless of distro here, and nearly always installations are via HTTP. This is from the installer's syslog from the Jessie installation I referred to upthread:
Jul 11 03:02:18 kernel: [ 0.000000] Command line: expert net.ifnames=0 ipv6.disable=1 netcfg/disable_dhcp=true netcfg/get_hostname=myhost hw-detect/start_pcmcia=false tasks=standard base-installer/install-recommends=false nosplash splash=0 DEBIAN_FRONTEND=gtk vga=788
Unless I edited it on the fly, which I do not remember now a month later, that cmdline resulted from a Grub (Legacy) stanza I created after reading Debian network installation instructions. Key to avoiding DHCP at the outset is the inclusion of netcfg/disable_dhcp=true while tasks=standard and base-installer/install-recommends=false are about preventing litter from other desktops' deps on a system intended to have TDE as its only DM.
Well, I haven't decided that it'll be the *only* DM at this point, but odds are that I'll probably end up using it a good bit more than others, which I'm finding limiting.
AFAIR, I created zero ordinary users until quite some time after installation was over and I had rebooted several times.
I guess I didn't know what to expect when I installed it. With me being used to Slackware, I guess I was hoping that the installation software would prompt me for some of the choices, when it turned out it didn't. And I've seen since then a bit about how to make some of those choices with command-line arguments to the installer and similar, but I didn't know that those would be necessary.
Back to reading the fine manual, I guess. :-)
On Wednesday 12 August 2015 11:49:56 am Felix Miata wrote:
Roy J. Tellason, Sr. composed on 2015-08-12 10:05 (UTC-0400):
Lisi Reisz wrote:
Debian has decided not to allow GUI root log-ins. It is not a case of
I'm not so sure whether it has anything to do with Debian, but rather the default tdm config file specifies safer when there are alternatives available.
It does indeed seem to be Debian doing it, since I've not gotten as far as getting TDM installed here...
"not being bothered", and there is nothing wrong with Konsole (which is supplied by TDE, not Debian).
I don't know where this is defined, but if I find it I'm surely going to change it!
Referring to the system's default behavior here.
root@myhost# whoami root root@myhost:~# ps -A | egrep 'mc|onsole' 1152 ? 00:00:01 konsole 1167 pts/2 00:00:00 mc root@myhost:~# uname -a Linux myhost 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt11-1 (2015-05-24) x86_64 GNU/Linux root@gmyhost:~# grep PRETTY /etc/os-release PRETTY_NAME="Debian GNU/Linux 8 (jessie)"
Not a problem for me as I've logged in as root in a text console, and also have mc installed.
root@myhost:~# egrep 'root|wRoot' /etc/trinity/tdm/tdmrc AllowRootLogin=true SelectedUsers=root,...
No /etc/trinity here (yet?). And I can find nothing of the sort in any other config file that I've looked at. I've got mc open on two of the four desktops, and am poking around in assorted config files, but this stuff is so convoluted I'm having some trouble sorting it all out.
As of this point in time, I find that if I log in as root in a text console, ignoring the GUI login for the moment, then I can "startx" and it will get me there. But there's no obvious way to choose what desktop I want, so even though I have several installed (TDE is coming soon! :-) I'm stuck in Xfce.
Anybody know how to fix either of these things?
Man startx.
A front end to xinit, it says.
I'm sure that the info I'm looking for has to be documented *somewhere*, but I haven't found it yet... :-(
Simply startx works here with TDE as the already selected/default session. startx /opt/trinity/bin/starttde also works here, but it disregards my xrandr display startup commands in /etc/X11/*.
On Wednesday 12 August 2015 19:14:51 Roy J. Tellason, Sr. wrote:
I'm sure that the info I'm looking for has to be documented *somewhere*, but I haven't found it yet... :-(
Any of this any good? I haven't had a chance to check it yet. https://www.google.co.uk/search?q=change+debian+default+to+beable+to+login+a...
Lisi
On Wednesday 12 August 2015 05:51:41 pm Lisi Reisz wrote:
On Wednesday 12 August 2015 19:14:51 Roy J. Tellason, Sr. wrote:
I'm sure that the info I'm looking for has to be documented *somewhere*, but I haven't found it yet... :-(
Any of this any good? I haven't had a chance to check it yet. https://www.google.co.uk/search?q=change+debian+default+to+beable+to+login+a...
I looked over some of that and a lot of it is for different systems (even though Debian is contained in the search term) and a lot of it is pretty dated. I'd even seen some of it before. :-)
What I'm partway through is plowing through all of the doc files that are on the machine. Seems to me that the specifics about some aspects of the way things are set up should be in there somewhere...
On Wed, 12 Aug 2015 14:14:51 -0400 "Roy J. Tellason, Sr." rtellason@gmail.com wrote:
On Wednesday 12 August 2015 11:49:56 am Felix Miata wrote:
Roy J. Tellason, Sr. composed on 2015-08-12 10:05 (UTC-0400):
Lisi Reisz wrote:
As of this point in time, I find that if I log in as root in a text console, ignoring the GUI login for the moment, then I can "startx" and it will get me there. But there's no obvious way to choose what desktop I want, so even though I have several installed (TDE is coming soon! :-) I'm stuck in Xfce.
Anybody know how to fix either of these things?
Man startx.
A front end to xinit, it says.
I'm sure that the info I'm looking for has to be documented *somewhere*, but I haven't found it yet... :-(
Try creating a ~/.xinitrc for root with "exec starttde" inside (or try starttde's full path). I don't know if the system will pick up your xrandr settings with that setup, though, since that's never been a concern for me (and I use a completely different distro anyway).
E. Liddell
On Thu, 13 Aug 2015, E. Liddell wrote:
Try creating a ~/.xinitrc for root with "exec starttde" inside (or try starttde's full path). I don't know if the system will pick up your xrandr settings with that setup, though, since that's never been a concern for me (and I use a completely different distro anyway).
can't the xandr stuff be put in .profile for root?
f.
From: lisi.reisz@gmail.com To: trinity-users@lists.pearsoncomputing.net Date: Sun, 26 Jul 2015 23:54:30 +0100 Subject: [trinity-users] Running GUI programs as root in 14
In the absence of kdesu, or tdesu, how do you run eg KWrite or Konqueror as root in 14 on Debian? Even gksu seems still to be missing this time.
Lisi
Hi Lisi,
I'm not on a Debian setup right now, but depending of the distro, one of the following command should work in Konsole: On PCLinuxOS (if I remember well it works this way on Deb too): su (type your password) (type the name of the app you want to launch as root) exit (to quit super-user mode) On Ubuntu: sudo ((type the name of the app you want to launch) (type your password)
It is not the same command on every distro, but it is most of the time combinations of su and sudo.
Anyway you should be able to find easily a package with a name similar to tdesu or tdesudo in Synaptic (my preferred one) or any package manager app. Or sometimes the name of the app has changed to trinity-(the name of the app).
Hope it helps! -Alexandre
Thanks, Alexandre for the reply.
On Monday 27 July 2015 00:06:39 Alexandre wrote:
From: lisi.reisz@gmail.com To: trinity-users@lists.pearsoncomputing.net Date: Sun, 26 Jul 2015 23:54:30 +0100 Subject: [trinity-users] Running GUI programs as root in 14
In the absence of kdesu, or tdesu, how do you run eg KWrite or Konqueror as root in 14 on Debian? Even gksu seems still to be missing this time.
I'm not on a Debian setup right now, but depending of the distro, one of the following command should work in Konsole: On PCLinuxOS (if I remember well it works this way on Deb too): su (type your password) (type the name of the app you want to launch as root)
And in Debian it won't launch because you are root and it is a GUI program. :-( It will complain about lack of access to X.
exit (to quit super-user mode) On Ubuntu: sudo ((type the name of the app you want to launch) (type your password)
It is not the same command on every distro, but it is most of the time combinations of su and sudo.
Anyway you should be able to find easily a package with a name similar to tdesu or tdesudo in Synaptic (my preferred one) or any package manager app. Or sometimes the name of the app has changed to trinity-(the name of the app).
Ah! I'll look for that.
I have been in the habit of alt-F2 -> kdesu kwrite -> password -> Kwrite launches.
Hope it helps!
I'll look for tdesu via aptitude. Thanks.
Lisi
On Monday 27 July 2015 00:06:39 Alexandre wrote:
Anyway you should be able to find easily a package with a name similar to tdesu or tdesudo in Synaptic (my preferred one) or any package manager app. Or sometimes the name of the app has changed to trinity-(the name of the app).
No tdesu. But tdesudo and gksu are both there. So I installed gksu.
But it didn't work. I.e., <gksu kwrite. in the launcher produced a request for the root password - but entering the root password had no effect. Nothing at all happened, and a check with ps showed that nothing had been launched. I tried all three of the programs I normally want to use this way, and nada. :-(
So I purged gksu.
17 packets installed, one was removed. So now |I have 16 orphaned packages to remove. :-( Wne I have looked it up.
Lisi
No tdesu. But tdesudo and gksu are both there. So I installed gksu.
But it didn't work. I.e., <gksu kwrite. in the launcher produced a request for the root password - but entering the root password had no effect. Nothing at all happened, and a check with ps showed that nothing had been launched. I tried all three of the programs I normally want to use this way, and nada. :-(
So I purged gksu.
17 packets installed, one was removed. So now |I have 16 orphaned packages to remove. :-( Wne I have looked it up.
Lisi
All of what you are writing here are just adding to the reasons why I don't like Debian at all. At least Ubuntu adds some firmware pre-installed on top of Debian and remove some disagreeable aspects of it. PCLinuxOS is so much better!
As soon as TDE R14.0.1 will be out, I'll build the new release of my remaster. This time it will have less clutter and a smaller ISO size.
Have a great day! -Alexandre
On Wednesday 29 July 2015 23:33:40 Alexandre wrote:
No tdesu. But tdesudo and gksu are both there. So I installed gksu.
But it didn't work. I.e., <gksu kwrite. in the launcher produced a request for the root password - but entering the root password had no effect. Nothing at all happened, and a check with ps showed that nothing had been launched. I tried all three of the programs I normally want to use this way, and nada. :-(
So I purged gksu.
17 packets installed, one was removed. So now |I have 16 orphaned packages to remove. :-( Wne I have looked it up.
Lisi
All of what you are writing here are just adding to the reasons why I don't like Debian at all. At least Ubuntu adds some firmware pre-installed on top of Debian and remove some disagreeable aspects of it. PCLinuxOS is so much better!
We all have our likes and dislikes - but what here is specific to Debian? gksu is desktop specific surely. And what has firmware to do with this????
As soon as TDE R14.0.1 will be out, I'll build the new release of my remaster. This time it will have less clutter and a smaller ISO size.
Great. :-)) It is bit big to be a useful Live CD on older hardware at the nmoment. I know - I have just tried to use it.
Have a great day!
:-) I'm about to go to bed - it is way past my bedtime. ;-)
Lisi
-Alexandre
On 07/29/2015 03:28 PM, Lisi Reisz wrote:
17 packets installed, one was removed. So now |I have 16 orphaned packages to remove. :-(
'apt-get autoremove' will make quick work of that.
On 07/29/2015 03:33 PM, Alexandre wrote:
PCLinuxOS is so much better!
Maybe, but it's run by an authoritarian dictator who for a long time refused to allow Trinity to even be discussed on the forum while ridiculing anyone so Luddite that they wanted to use it, among other things. I used to use PCLOS, but got tired of forced obsolescence and having to reinstall all my systems just because he thought I should. I see now they've gone to a rolling release, which might solve that problem, but I no longer trust him with such control over my systems, so I'll probably stay away anyway.
Date: Wed, 29 Jul 2015 15:52:25 -0700 From: dan@homestead-products.com To: trinity-users@lists.pearsoncomputing.net Subject: Re: [trinity-users] Running GUI programs as root in 14
On 07/29/2015 03:28 PM, Lisi Reisz wrote:
17 packets installed, one was removed. So now |I have 16 orphaned packages to remove. :-(
'apt-get autoremove' will make quick work of that.
On 07/29/2015 03:33 PM, Alexandre wrote:
PCLinuxOS is so much better!
Maybe, but it's run by an authoritarian dictator who for a long time refused to allow Trinity to even be discussed on the forum while ridiculing anyone so Luddite that they wanted to use it, among other things. I used to use PCLOS, but got tired of forced obsolescence and having to reinstall all my systems just because he thought I should. I see now they've gone to a rolling release, which might solve that problem, but I no longer trust him with such control over my systems, so I'll probably stay away anyway.
--
Mageia is good too if you don't like Texstar. But now he accepts (more) the existence of TDE and it is rolling-release since at least the 5 last years.
-Alexandre
On Wednesday 29 July 2015 23:52:25 Dan Youngquist wrote:
On 07/29/2015 03:28 PM, Lisi Reisz wrote:
17 packets installed, one was removed. So now |I have 16 orphaned packages to remove. :-(
'apt-get autoremove' will make quick work of that.
I knew that there was a command! The problem is just my memory. :-( Hence my saying I would just have to look it up! Thank you.
(That is a disadvantage of the command line Alexandre - you actually have to know the command. But the advantages, when you do, are legion, so that it is well worth it IMHO.)
Thank for all your help Dan and Alexandre.
You will not be surprised to know, Dan, that the addition to the menu went swimmingly - I was pleasantly surprised that I actually managed to do it right. Thank you so much for that. I really must explore the menu some time.
Now to file a) a bug - gksu and b) a wish-bug - tdesu.
After I've had some sleep.
Goodnight, Lisi
On Wed, Jul 29, 2015 at 6:28 PM, Lisi Reisz lisi.reisz@gmail.com wrote:
On Monday 27 July 2015 00:06:39 Alexandre wrote:
Anyway you should be able to find easily a package with a name similar to tdesu or tdesudo in Synaptic (my preferred one) or any package manager
app.
Or sometimes the name of the app has changed to trinity-(the name of the app).
No tdesu. But tdesudo and gksu are both there. So I installed gksu.
But it didn't work. I.e., <gksu kwrite. in the launcher produced a request for the root password - but entering the root password had no effect.
I think you use your own password (and your user has to be in /etc/sudoers).
On Thursday 30 July 2015 15:06:56 Leonard T Harris wrote:
On Wed, Jul 29, 2015 at 6:28 PM, Lisi Reisz lisi.reisz@gmail.com wrote:
On Monday 27 July 2015 00:06:39 Alexandre wrote:
Anyway you should be able to find easily a package with a name similar to tdesu or tdesudo in Synaptic (my preferred one) or any package manager
app.
Or sometimes the name of the app has changed to trinity-(the name of the app).
No tdesu. But tdesudo and gksu are both there. So I installed gksu.
But it didn't work. I.e., <gksu kwrite. in the launcher produced a request for the root password - but entering the root password had no effect.
I think you use your own password (and your user has to be in /etc/sudoers).
That is supposed to be gksudo - or was last time I was reduced to using it. But that would certainly explain it. Anyhow, it is resolved. I can use tdesu now (root). tdesudo also exists, of course, but that would mean setting up sudo and sudoers.
Thanks for the reply.
Lisi
-
Alexandre -
Dan Youngquist -
Dr. Nikolaus Klepp -
E. Liddell -
Felix Miata -
Felmon Davis -
Leonard T Harris -
Lisi Reisz -
Roy J. Tellason, Sr.