tw, kernel-6.3.1-2.2 log-in, no gui
Whether I click the grub (for some reason unversioned) default entry or the alternative 6.3.1-2.2 kernel entry, the boot only gets as far as a log-in prompt, which would be just fine with me. But at this point I want to log in as root or as userMe, but how do I get from either of these logins to a running KDE/XCFCE desktop, or lightdm (for chosing DT and re log-in)? As root neither of these work: systemctl isolate graphical.target lightdm Starx probably would As userMe: startx does not work M prefred method would be to first log in as root and then start lightdm or other DM, or to log in as userMe and start X with desktop of choice.
* bent fender <ksusup@trixtar.org> [05-18-23 19:20]:
Whether I click the grub (for some reason unversioned) default entry or the alternative 6.3.1-2.2 kernel entry, the boot only gets as far as a log-in prompt, which would be just fine with me.
But at this point I want to log in as root or as userMe, but how do I get from either of these logins to a running KDE/XCFCE desktop, or lightdm (for chosing DT and re log-in)?
As root neither of these work: systemctl isolate graphical.target lightdm
Starx probably would
but is not desired (as it would solve) ???
As userMe:
startx does not work
M prefred method would be to first log in as root and then start lightdm or other DM, or to log in as userMe and start X with desktop of choice.
I use sddm and merely have to go to a tty in multi-user.target or graphical.target and "startx /usr/bin//usr/bin/icewm-session-default" and I am on tumbleweed and have no idea what you are on. and have been using it for many, many years nwo. from watching your previous posts, appears you are making something usually simple into a complicated xxxxx. why not just install and use the system in the manner normally perscribed? then slowly make wanted adjustments and proceed when successful. ie: start with a known rather than shotgun the barn door. -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
* Patrick Shanahan <paka@opensuse.org> [05-18-23 19:49]:
* bent fender <ksusup@trixtar.org> [05-18-23 19:20]:
Whether I click the grub (for some reason unversioned) default entry or the alternative 6.3.1-2.2 kernel entry, the boot only gets as far as a log-in prompt, which would be just fine with me.
But at this point I want to log in as root or as userMe, but
note that logging in as root is considered a security problem. why not log in a <user> and "su -" to root? -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Thu, 18 May 2023 19:52:31 -0400 Patrick Shanahan <paka@opensuse.org> :
* Patrick Shanahan <paka@opensuse.org> [05-18-23 19:49]:
* bent fender <ksusup@trixtar.org> [05-18-23 19:20]:
Whether I click the grub (for some reason unversioned) default entry or the alternative 6.3.1-2.2 kernel entry, the boot only gets as far as a log-in prompt, which would be just fine with me.
But at this point I want to log in as root or as userMe, but
note that logging in as root is considered a security problem.
Only I will decide waht is a security problem for me. As far as any distro or dev may be concerned it may be *suggested* as a security problem in the form of an ADVISORY. The actual prerogative is an administrative one meaning it belongs soleley to the user or system-admin and NO ONE ELSE. That said, as in my other reply, when I do see such a 'caution' or 'warning' ADVISORY *with which I concurr* then I do avoid the practice more often then not (startx as root for example).
why not log in a <user> and "su -" to root?
One of many reasons is that (lately) doing so can lead to situations where I as root am told "you cannot do this" which I find not only ridiculous and presumptuous but more importantly pathetically arrogant, questionable, and revolting.
Thu, 18 May 2023 19:48:26 -0400 Patrick Shanahan <paka@opensuse.org> :
* bent fender <ksusup@trixtar.org> [05-18-23 19:20]:
Whether I click the grub (for some reason unversioned) default entry or the alternative 6.3.1-2.2 kernel entry, the boot only gets as far as a log-in prompt, which would be just fine with me.
But at this point I want to log in as root or as userMe, but how do I get from either of these logins to a running KDE/XCFCE desktop, or lightdm (for chosing DT and re log-in)?
As root neither of these work: systemctl isolate graphical.target lightdm
Starx probably would
but is not desired (as it would solve) ???
It works, but is not *recommeneded* being a security risk so I seldom use it.
As user startx does not work
red pencil: it does work (did not the previous time I tried)
M prefred method would be to first log in as root and then start lightdm or other DM, or to log in as userMe and start X with desktop of choice.
I use sddm and merely have to go to a tty in multi-user.target or graphical.target and "startx /usr/bin//usr/bin/icewm-session-default"
that works for me too as root but it's not what I want seeing that it has been *suggested* as being a security risk. I would like to start a DM like lightDM with # lightDM as root at this point (after having logged in as root in this case by necessity) but am not successful.
and I am on tumbleweed and have no idea what you are on.
subject header "tw"
and have been using it for many, many years nwo.
same here
from watching your previous posts, appears you are making something usually simple into a complicated xxxxx. why not just install and use the system in the manner normally perscribed? then slowly make wanted adjustments and proceed when successful. ie: start with a known rather than shotgun the barn door.
I did start with a perfectly sane OLD Suse method which began with booting and then continued with logging-in, an then went on to starting the GUI system with startx (Slackware and some others still do it that way BTW). Suse have abandoned this over the years and I won't go into that discussion here, but I have found it increasingly difficult to do it my way i.e. as it was done before. And just to stay on topic, my postiong is about what I thought to be at least implicitly an IRREGULARITY in the form of not being able to start the GUI with the cited kernel. The other 2 kernels listed in the grub2 menu pose no such problem.
* bent fender <ksusup@trixtar.org> [05-18-23 21:44]:
Thu, 18 May 2023 19:48:26 -0400 Patrick Shanahan <paka@opensuse.org> :
* bent fender <ksusup@trixtar.org> [05-18-23 19:20]:
Whether I click the grub (for some reason unversioned) default entry or the alternative 6.3.1-2.2 kernel entry, the boot only gets as far as a log-in prompt, which would be just fine with me.
But at this point I want to log in as root or as userMe, but how do I get from either of these logins to a running KDE/XCFCE desktop, or lightdm (for chosing DT and re log-in)?
As root neither of these work: systemctl isolate graphical.target lightdm
Starx probably would
but is not desired (as it would solve) ???
It works, but is not *recommeneded* being a security risk so I seldom use it.
As user startx does not work
red pencil: it does work (did not the previous time I tried)
M prefred method would be to first log in as root and then start lightdm or other DM, or to log in as userMe and start X with desktop of choice.
I use sddm and merely have to go to a tty in multi-user.target or graphical.target and "startx /usr/bin//usr/bin/icewm-session-default"
that works for me too as root but it's not what I want seeing that it has been *suggested* as being a security risk.
I would like to start a DM like lightDM with
# lightDM
as root at this point (after having logged in as root in this case by necessity) but am not successful.
and I am on tumbleweed and have no idea what you are on.
subject header "tw"
and have been using it for many, many years nwo.
same here
from watching your previous posts, appears you are making something usually simple into a complicated xxxxx. why not just install and use the system in the manner normally perscribed? then slowly make wanted adjustments and proceed when successful. ie: start with a known rather than shotgun the barn door.
I did start with a perfectly sane OLD Suse method which began with booting and then continued with logging-in, an then went on to starting the GUI system with startx (Slackware and some others still do it that way BTW). Suse have abandoned this over the years and I won't go into that discussion here, but I have found it increasingly difficult to do it my way i.e. as it was done before.
And just to stay on topic, my postiong is about what I thought to be at least implicitly an IRREGULARITY in the form of not being able to start the GUI with the cited kernel. The other 2 kernels listed in the grub2 menu pose no such problem.
fwiw: I believe logging in as "root" is considered unsave and a possible security risk, not using "startx". of course using startx to log in as "root" would follow as being considered less secure. as you seem to have the answers, I will leave you to your preferred path(s). -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet oftc
Thu, 18 May 2023 22:55:23 -0400 Patrick Shanahan <paka@opensuse.org> :
fwiw: I believe logging in as "root" is considered unsave and a possible security risk, not using "startx".
of course using startx to log in as "root" would follow as being considered less secure.
When I first read about this (many years ago) it was about doing startx as root, no one at that time considered logging in as root unsafe, many devs still don't, but startig X as root did already raise eyebrows. When I informed one dear person in my family of what I had learned he told me "I log in as root and start X as root ALL THE TIME". I forget how long he had been doing so but he lived happily for many a year after that.
as you seem to have the answers, I will leave you to your preferred path(s).
If I did have all the answers I would not have posted this, trying to find out why I get neither a DM login dialog nor an ability to get a kde or xfce DT going 'as user' once I had booted the cited kernel.
On 2023-05-19 01:18, bent fender wrote:
Whether I click the grub (for some reason unversioned) default entry or the alternative 6.3.1-2.2 kernel entry, the boot only gets as far as a log-in prompt, which would be just fine with me.
Do you mean a graphical login, or a text mode login?
But at this point I want to log in as root or as userMe, but how do I get from either of these logins to a running KDE/XCFCE desktop, or lightdm (for chosing DT and re log-in)?
So you got a text login? Your next step would be to examine the logs to find out why graphical mode failed.
As root neither of these work: systemctl isolate graphical.target lightdm
Starx probably would
As userMe:
startx does not work
What does this mean exactly? You got an error, I assume. Exactly which? -- Cheers / Saludos, Carlos E. R. (from 15.4 x86_64 at Telcontar)
Fri, 19 May 2023 18:44:08 +0200 "Carlos E. R." <robin.listas@telefonica.net> :
On 2023-05-19 01:18, bent fender wrote:
Whether I click the grub (for some reason unversioned) default entry or the alternative 6.3.1-2.2 kernel entry, the boot only gets as far as a log-in prompt, which would be just fine with me.
Do you mean a graphical login, or a text mode login?
graphical login has no prompt
But at this point I want to log in as root or as userMe, but how do I get from either of these logins to a running KDE/XCFCE desktop, or lightdm (for chosing DT and re log-in)?
So you got a text login?
yes, and I can log in as root or as userMe
Your next step would be to examine the logs to find out why graphical mode failed.
I got annunciated that maybe /usr/bin/Xorg was not 'setuid'. So I went and did that setuid as I have mnany times in the past. The effort usually bears for a while before some sript resets it no setuid. Anyway, this time it didn't work at all.
startx does not work
What does this mean exactly? You got an error, I assume. Exactly which?
looks like nothing BUT errors: https://paste.opensuse.org/pastes/cff1b91c21be But, to return to the original suspects, it happens only with the last (cited) kernel, not with the other two.
bent fender composed on 2023-05-19 19:43 (UTC-0400):
looks like nothing BUT errors:
This appears to be standard, run-of-the-mill NVidia driver trouble, new TW kernel version released before NVidia's driver is ready to support it. -- Evolution as taught in public schools is, like religion, based on faith, not based on science. Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata
On Saturday 20 May 2023, Felix Miata wrote:
bent fender composed on 2023-05-19 19:43 (UTC-0400):
looks like nothing BUT errors:
This appears to be standard, run-of-the-mill NVidia driver trouble, new TW kernel version released before NVidia's driver is ready to support it.
Running Nvidia 525.116.04 (from the easy-way) with a GTX 1650 SUPER. No issues at all with TW 20230518 6.3.2-1-default (or any other releases I've run recently).
On Saturday 20 May 2023, Michael Hamilton wrote:
On Saturday 20 May 2023, Felix Miata wrote:
bent fender composed on 2023-05-19 19:43 (UTC-0400):
looks like nothing BUT errors:
This appears to be standard, run-of-the-mill NVidia driver trouble, new TW kernel version released before NVidia's driver is ready to support it.
Running Nvidia 525.116.04 (from the easy-way) with a GTX 1650 SUPER. No issues at all with TW 20230518 6.3.2-1-default (or any other releases I've run recently).
I also just updated a machine with a GTX 650 to TW 20230518 and Nvidia 470.182.03. No issues with gui logins either. You might try a reinstall of the the Nvidia driver in case the kernel module didn't get updated for some reason. Cheers, Michael
Sylpheed default reply addressing got me again, and I bothered Felix Miata with an unsolicited email instead of the list. My apologies Felix :-) Fri, 19 May 2023 20:20:55 -0400 Felix Miata <mrmazda@earthlink.net> :
bent fender composed on 2023-05-19 19:43 (UTC-0400):
looks like nothing BUT errors:
This appears to be standard, run-of-the-mill NVidia driver trouble, new TW kernel version released before NVidia's driver is ready to support it. -- Evolution as taught in public schools is, like religion, based on faith, not based on science.
Team OS/2 ** Reg. Linux User #211409 ** a11y rocks!
Felix Miata
Meanwhile the last upgrade took out the 6.1 and 6.2 kernels leaving me only two versions of 6.3 neither of which would go into GUI. So I started yast with a view to reinstall nvidia. With no such option I deleted nvidia and then tried to install it again. During that process which was very quick and involved no nvidia downlooad the box locked up. After a hard reset I can log in as usual with lightdm (I think it's lightdm).
Am 19.05.23 um 01:18 schrieb bent fender:
Whether I click the grub (for some reason unversioned) default entry or the alternative 6.3.1-2.2 kernel entry, the boot only gets as far as a log-in prompt, which would be just fine with me.
But at this point I want to log in as root or as userMe, but how do I get from either of these logins to a running KDE/XCFCE desktop, or lightdm (for chosing DT and re log-in)?
As root neither of these work: systemctl isolate graphical.target lightdm
Starx probably would
As userMe:
startx does not work
M prefred method would be to first log in as root and then start lightdm or other DM, or to log in as userMe and start X with desktop of choice. I do have this problem with a old nVidia card now and then after updating TW to a newer kernel (most of the time new 6.X versions). Often compilation of the nVidia modules fail during update (you can see that in console output).
You might find my corresponding post with subject "No Login, no Graphics after update to Tumbleweed 20230211-0" here. BR Pete
participants (6)
-
bent fender -
Carlos E. R. -
Felix Miata -
Michael Hamilton -
Patrick Shanahan -
Peter Maffter