Need help with a laptop that will only run Plasma/Wayland
I have an ASUS laptop that normally is running in a remote location. The trouble is, is that it will only start up the Plasma/Wayland desktop and I need it to bring up the Plasma/X11 desktop instead. (I use x11vnc for remote desktop access purposes, and x11vnc won't talk with Wayland AFAIK, and yes I must run both the x11vnc server as well as clients on the laptop) The laptop is running under OpenSuSE 15.5 x64 with the KDE desktop manager. When I try to use the Plasma/X11 desktop, after a reboot I reach the KDE login screen OK. If I choose to log in with the Plasma/X11 desktop, after entering my login name and password, the screen just goes blank for a moment, then cycles back and re-brings up the login/password screen again. Apparently the Plasma/X11 version of the desktop is not accepting my login credentials for some reason. However, if I choose to brings up the Plasma/Wayland desktop, my login credentials work just fine and the desktop comes up OK. I have no idea how to go about debugging and solving this problem, log files seem unhelpful with nothing much amiss, and DuckDuckGo internet searching ain't bringing no joy either. I would rather not apply a single case workaround either, I like to keep all my systems I support, as consistent as possible. Anyone up for helping me to get this beast of a laptop to behave itself. As always, my thanks and appreciation are offered in advance. Marc... --
On 8/11/24 2:49 PM, Marc Chamberlin via openSUSE Users wrote:
I have no idea how to go about debugging and solving this problem, log files seem unhelpful with nothing much amiss, and DuckDuckGo internet searching ain't bringing no joy either. I would rather not apply a single case workaround either, I like to keep all my systems I support, as consistent as possible. Anyone up for helping me to get this beast of a laptop to behave itself. As always, my thanks and appreciation are offered in advance.
Marc...
That's one I would open a bug report on including your .xsession-errors file. There isn't a reason that Plasma shouldn't run under X as well as wayland. -- David C. Rankin, J.D.,P.E.
On 8/11/24 13:34, David C. Rankin wrote:
On 8/11/24 2:49 PM, Marc Chamberlin via openSUSE Users wrote:
I have no idea how to go about debugging and solving this problem, log files seem unhelpful with nothing much amiss, and DuckDuckGo internet searching ain't bringing no joy either. I would rather not apply a single case workaround either, I like to keep all my systems I support, as consistent as possible. Anyone up for helping me to get this beast of a laptop to behave itself. As always, my thanks and appreciation are offered in advance.
Marc...
That's one I would open a bug report on including your .xsession-errors file. There isn't a reason that Plasma shouldn't run under X as well as wayland.
Thanks David, bug reported - Bug 1229061 Hopefully it will get resolved soon. Marc....
Hello, In the Message; Subject : Need help with a laptop that will only run Plasma/Wayland Message-ID : <2a2f055a-ff66-4868-97c9-d193736476de@marcchamberlin.com> Date & Time: Sun, 11 Aug 2024 12:49:03 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: MC> I have an ASUS laptop that normally is running in a remote MC> location. The trouble is, is that it will only start up the MC> Plasma/Wayland desktop and I need it to bring up the Plasma/X11 MC> desktop instead. [...] You've got a dependency issue. Please execute this; $ startplasma-x11 > plasma.log 2>&1 This plasma.log will give you a clue to the solution. Alternatively, here is another solution. 1. start YaST2 2. Select "Software Management" 3. Select "View", then "KDE Plasma 6 Desktop Base" 4. Select "Dependencies" item on the Menu bar 5. Execure "Check Now", then 6. Press the "Accept" button in the lower right corner. After this, try to log in to Plasama/X11. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Japan was the future but it's stuck in the past" -- Rupert Wingfield-Hayes (BBC) --
On 8/11/24 18:39, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Need help with a laptop that will only run Plasma/Wayland Message-ID :<2a2f055a-ff66-4868-97c9-d193736476de@marcchamberlin.com> Date & Time: Sun, 11 Aug 2024 12:49:03 -0700
[MC] == Marc Chamberlin via openSUSE Users<users@lists.opensuse.org> has written:
MC> I have an ASUS laptop that normally is running in a remote MC> location. The trouble is, is that it will only start up the MC> Plasma/Wayland desktop and I need it to bring up the Plasma/X11 MC> desktop instead. [...]
You've got a dependency issue.
Please execute this;
$ startplasma-x11 > plasma.log 2>&1
This plasma.log will give you a clue to the solution.
Naw no joy! I ran this under the plasma/wayland desktop (which is the only one I can bring up) and all it said was
marc@marcslaptop:~/Documents> startplasma-x11 > plasma.log 2>&1 marc@marcslaptop:~/Documents> more plasma.log Plasma seems to be already running on this display.
Alternatively, here is another solution.
1. start YaST2
2. Select "Software Management"
3. Select "View", then "KDE Plasma 6 Desktop Base"
I am guessing that you meant to select "View" -> "Patterns" -> "KDE Plasma 6 Desktop Base" I don't have that particular pattern so chose "KDE Plasma 5 Desktop Base" instead. (Note the difference is Plasma 5, which I have, and not Plasma 6, which you suggested but isn't an option for me.
4. Select "Dependencies" item on the Menu bar
5. Execure "Check Now", then
And this reported - "All package dependencies are OK."
6. Press the "Accept" button in the lower right corner.
Nothing happened, just simply exits the Software Management window.
After this, try to log in to Plasama/X11.
Still can't, so still no joy! Thanks Masaru for your time and suggestions, got any more? ;-) Marc..
Best Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Japan was the future but it's stuck in the past"
-- Rupert Wingfield-Hayes (BBC) --
-- "The Truth is out there" - Spooky _ _ . . . . . . _ _ . _ _ _ _ . . . . _ . . . . _ _ . _ _ _ . . . . _ _ . _ . . _ . _ _ _ _ . _ . _ . _ . _ . Computers: the final frontier. These are the voyages of the user Marc. His mission: to explore strange new hardware. To seek out new software and new applications. To boldly go where no Marc has gone before! (This email is digitally signed and the OpenPGP electronic signature is added as an attachment. If you know how, you can use my public key to prove this email indeed came from me and has not been modified in transit. My public key, which can be used for sending encrypted email to me also, can be found at - https://keys.openpgp.org/search?q=marc@marcchamberlin.com or just ask me for it and I will send it to you as an attachment. If you don't understand all this geek speak, no worries, just ignore this explanation and ignore the OpenPGP signature key attached to this email (it will look like gibberish if you open it) and/or ask me to explain it further if you like.)
got any more? Use update-alternatives to switch default-displaymanager from SDDM to XDM, and default-xsession.desktop to plasma6, if it isn't already. I don't think XDM can start any Wayland sessions directly. Normally, XDM is only used to start one of
Marc Chamberlin composed on 2024-08-12 14:34 (UTC-0700): the familiar DMs: SDDM, GDM, LightDM, etc. -- 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 08-12-2024 07:07PM, Felix Miata wrote:
Marc Chamberlin composed on 2024-08-12 14:34 (UTC-0700):
got any more? Use update-alternatives to switch default-displaymanager from SDDM to XDM, and default-xsession.desktop to plasma6, if it isn't already. I don't think XDM can start any Wayland sessions directly. Normally, XDM is only used to start one of the familiar DMs: SDDM, GDM, LightDM, etc. You mean Desktop Environment? > XDM is used to boot an X.org based desktop environment.[2] It can control a display directly or indirectly in order to start an X session and supports remote login.[3] XDM is initialized on system startup.[4]
It can be editing through the use of a configuration file, modules, or scripts.[5][6] The configratuion file is usually found in /usr/lib/X11/xdm/xdm-config.[7]
-pj composed on 2024-08-17 20:28 (UTC-0500):
Felix Miata wrote:
Marc Chamberlin composed on 2024-08-12 14:34 (UTC-0700):
got any more?
Use update-alternatives to switch default-displaymanager from SDDM to XDM, and default-xsession.desktop to plasma6, if it isn't already. I don't think XDM can start any Wayland sessions directly. Normally, XDM is only used to start one of the familiar DMs: SDDM, GDM, LightDM, etc.
You mean Desktop Environment? > XDM is used to boot an X.org based desktop environment.[2] It can control a display directly or indirectly in order to start an X session and supports remote login.[3] XDM is initialized on system startup.[4]
It can be editing through the use of a configuration file, modules, or scripts.[5][6] The configratuion file is usually found in /usr/lib/X11/xdm/xdm-config.[7]
I don't understand what you're getting at, especially those number suffixes. XDM is a DM (display manager: see also: GDM, KDM3, LightDM, SDDM, TDM, etc.) that is capable of starting either a WM (Window Manager: twm, xfwm4, openbox, fluxbox, etc.) or a DE (Desktop Environment: Gnome, Plasma, XFCE, Cinnamon, Mate, etc.) /OR/ another display manager (GDM, KDM3, LightDM, SDDM, TDM, etc.) *SUSE, unlike other most (all?) other distros, provides XDM as both the latter, a DM launcher (for GDM, KDM, LightDM, SDDM, TDM) /AND/ directly, to accept login, then launch whatever WM or DE is defined as default (no frills), as here: # inxi -S System: Host: fi965 Kernel: 6.9.9-1-default arch: x86_64 bits: 64 Console: pty pts/1 Distro: openSUSE Tumbleweed-Slowroll 20240803 # update-alternatives --config default-displaymanager There are 2 choices for the alternative default-displaymanager (providing /usr/lib/X11/displaymanagers/default-displaymanager). Selection Path Priority Status ------------------------------------------------------------ 0 /usr/lib/X11/displaymanagers/xdm 10 auto mode 1 /usr/lib/X11/displaymanagers/console 5 manual mode * 2 /usr/lib/X11/displaymanagers/xdm 10 manual mode # Most installations don't have so few, e.g.: # inxi -S System: Host: 00srv Kernel: 5.14.21-150500.55.68-default arch: x86_64 bits: 64 Console: pty pts/9 Distro: openSUSE Leap 15.5 # update-alternatives --config default-displaymanager There are 3 choices for the alternative default-displaymanager (providing /usr/lib/X11/displaymanagers/default-displaymanager). Selection Path Priority Status ------------------------------------------------------------ 0 /usr/lib/X11/displaymanagers/kdm3 15 auto mode 1 /usr/lib/X11/displaymanagers/console 5 manual mode * 2 /usr/lib/X11/displaymanagers/kdm3 15 manual mode 3 /usr/lib/X11/displaymanagers/xdm 10 manual mode # -- 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 08-17-2024 09:26PM, Felix Miata wrote:
-pj composed on 2024-08-17 20:28 (UTC-0500):
Felix Miata wrote:
Marc Chamberlin composed on 2024-08-12 14:34 (UTC-0700):
got any more?
Use update-alternatives to switch default-displaymanager from SDDM to XDM, and default-xsession.desktop to plasma6, if it isn't already. I don't think XDM can start any Wayland sessions directly. Normally, XDM is only used to start one of the familiar DMs: SDDM, GDM, LightDM, etc.
I was thinking that "Normally" XDM is used to start a WM or DE *not* DM. My brief experiences with XDM using i686 TW: XDM defaults/ed to starting DE "directly, to accept login" which is plasma6 on that machine.
You mean Desktop Environment? > XDM is used to boot an X.org based desktop environment.[2] It can control a display directly or indirectly in order to start an X session and supports remote login.[3] XDM is initialized on system startup.[4]
It can be editing through the use of a configuration file, modules, or scripts.[5][6] The configratuion file is usually found in /usr/lib/X11/xdm/xdm-config.[7]
I don't understand what you're getting at, especially those number suffixes.
Apologies I sent a snippet from wiki just for quick reference to your thought. Was thinking of SDDM hijack TTY1 and TTY3. It looks like you have explained more clearly below also.
XDM is a DM (display manager: see also: GDM, KDM3, LightDM, SDDM, TDM, etc.)
that is capable of starting either a WM (Window Manager: twm, xfwm4, openbox, fluxbox, etc.) or a DE (Desktop Environment: Gnome, Plasma, XFCE, Cinnamon, Mate, etc.) /OR/ another display manager (GDM, KDM3, LightDM, SDDM, TDM, etc.)
*SUSE, unlike other most (all?) other distros, provides XDM as both the latter,
I was not aware of this.
a DM launcher (for GDM, KDM, LightDM, SDDM, TDM)
/AND/
directly, to accept login, then launch whatever WM or DE is defined as default (no frills), as here:
# inxi -S System: Host: fi965 Kernel: 6.9.9-1-default arch: x86_64 bits: 64 Console: pty pts/1 Distro: openSUSE Tumbleweed-Slowroll 20240803 # update-alternatives --config default-displaymanager There are 2 choices for the alternative default-displaymanager (providing /usr/lib/X11/displaymanagers/default-displaymanager).
Selection Path Priority Status ------------------------------------------------------------ 0 /usr/lib/X11/displaymanagers/xdm 10 auto mode 1 /usr/lib/X11/displaymanagers/console 5 manual mode * 2 /usr/lib/X11/displaymanagers/xdm 10 manual mode #
Most installations don't have so few, e.g.: # inxi -S System: Host: 00srv Kernel: 5.14.21-150500.55.68-default arch: x86_64 bits: 64 Console: pty pts/9 Distro: openSUSE Leap 15.5 # update-alternatives --config default-displaymanager There are 3 choices for the alternative default-displaymanager (providing /usr/lib/X11/displaymanagers/default-displaymanager).
Selection Path Priority Status ------------------------------------------------------------ 0 /usr/lib/X11/displaymanagers/kdm3 15 auto mode 1 /usr/lib/X11/displaymanagers/console 5 manual mode * 2 /usr/lib/X11/displaymanagers/kdm3 15 manual mode 3 /usr/lib/X11/displaymanagers/xdm 10 manual mode #
My mistake, thanks for showing this so clearly.
Felix Miata composed on 2024-08-12 20:07 (UTC-0400):
Marc Chamberlin composed on 2024-08-12 14:34 (UTC-0700):
got any more?
Use update-alternatives to switch default-displaymanager from SDDM to XDM, and default-xsession.desktop to plasma6, if it isn't already. I don't think XDM can start any Wayland sessions directly. Normally, XDM is only used to start one of the familiar DMs: SDDM, GDM, LightDM, etc.
I saw no response to this except from pj. It's intended as a troubleshooting procedure, not permanent. -- 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
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <3bec6b3c-3875-c482-2f21-7f1dd8ed2ae1@earthlink.net> Date & Time: Mon, 19 Aug 2024 13:43:20 -0400 [FM] == Felix Miata <mrmazda@earthlink.net> has written: FM> Felix Miata composed on 2024-08-12 20:07 (UTC-0400): FM> > Marc Chamberlin composed on 2024-08-12 14:34 (UTC-0700): FM> >> got any more? FM> > Use update-alternatives to switch default-displaymanager from SDDM to XDM, and FM> > default-xsession.desktop to plasma6, if it isn't already. I don't think XDM can FM> > start any Wayland sessions directly. Normally, XDM is only used to start one of FM> > the familiar DMs: SDDM, GDM, LightDM, etc. FM> I saw no response to this except from pj. It's intended as a troubleshooting FM> procedure, not permanent. I think it is a good report. It would be perfect if a little more was written about the process by which WM or DE's desktop file in /usr/share/xsessions and /usr/share/wayland is callled, and the startup command in Exec= in the desktop file to start up DE, I think. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <a8e0af9e-d532-4ca6-9c1a-f51c3a508416@marcchamberlin.com> Date & Time: Mon, 12 Aug 2024 14:34:58 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: [...] MN> > You've got a dependency issue. MN> > MN> > Please execute this; MN> > MN> > $ startplasma-x11 > plasma.log 2>&1 MN> > MN> > This plasma.log will give you a clue to the solution. MC> Naw no joy! I ran this under the plasma/wayland desktop (which is MC> the only one I can bring up) and all it said was MC> marc@marcslaptop:~/Documents> startplasma-x11 > plasma.log 2>&1 MC> marc@marcslaptop:~/Documents> more plasma.log Plasma seems to be already MC> running on this display. This can be done in a virtual console, which is the usual way; At the login screen; 1. Ctrl+Alt+F1 key 2. Log in as root 3. Execute # init 3 4. Ctrl+Alt+F2 key 5. Log in as root, again 6. Exucute $ startplasma-x11 > /tmp/plasama.log 2>&1 Then, check the plasma.log. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices ― and change is hard." -- Employers don’t practice what they preach on skills-based hiring --
On 8/12/24 19:56, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID :<a8e0af9e-d532-4ca6-9c1a-f51c3a508416@marcchamberlin.com> Date & Time: Mon, 12 Aug 2024 14:34:58 -0700
[MC] == Marc Chamberlin via openSUSE Users<users@lists.opensuse.org> has written:
[...] MN> > You've got a dependency issue. MN> > MN> > Please execute this; MN> > MN> > $ startplasma-x11 > plasma.log 2>&1 MN> > MN> > This plasma.log will give you a clue to the solution.
MC> Naw no joy! I ran this under the plasma/wayland desktop (which is MC> the only one I can bring up) and all it said was
MC> marc@marcslaptop:~/Documents> startplasma-x11 > plasma.log 2>&1 MC> marc@marcslaptop:~/Documents> more plasma.log Plasma seems to be already MC> running on this display.
This can be done in a virtual console, which is the usual way;
At the login screen;
1. Ctrl+Alt+F1 key
2. Log in as root
3. Execute
# init 3
4. Ctrl+Alt+F2 key
5. Log in as root, again
6. Exucute
$ startplasma-x11 > /tmp/plasama.log 2>&1
Then, check the plasma.log.
Not sure if this is helpful or not, but this is what was captured in the plasma.log - marc@marcslaptop:~> cat /tmp/plasma.log $DISPLAY is not set or cannot connect to the X server. and sure enough the $DISPLAY variable is not set. I suspect it should be set to either :0 or 0:0 but I am not sure where or who it should be set for (if I need to edit some startup shell script, or simply to do an export under root and/or myself) I tried fooling around with setting the DISPLAY environment variable but didn't succeed in getting startplasma-x11 to run.. Marc...
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <65f84cc4-6c95-44ce-a981-82bb27ddcee1@marcchamberlin.com> Date & Time: Wed, 14 Aug 2024 12:13:43 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: [...] MN> > MN> > This can be done in a virtual console, which is the usual way; MN> > MN> > At the login screen; MN> > MN> > 1. Ctrl+Alt+F1 key MN> > MN> > 2. Log in as root MN> > MN> > 3. Execute MN> > MN> > # init 3 MN> > MN> > 4. Ctrl+Alt+F2 key MN> > MN> > 5. Log in as root, again MN> > MN> > 6. Exucute MN> > MN> > $ startplasma-x11 > /tmp/plasama.log 2>&1 MN> > MN> > Then, check the plasma.log. MC> Not sure if this is helpful or not, but this is what was captured in the MC> plasma.log - marc@marcslaptop:~> cat /tmp/plasma.log MC> $DISPLAY is not set or cannot connect to the X server. [...] Please set this in your ~/.bashrc export DISPLAY="${DISPLAY:-:0}" This is a important setting. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Japan was the future but it's stuck in the past" -- Rupert Wingfield-Hayes (BBC) --
On 8/14/24 19:18, Masaru Nomiya wrote:
Please set this in your ~/.bashrc
export DISPLAY="${DISPLAY:-:0}"
This is a important setting.
Hi Masaru Nomiya, just got the laptop back to try out your incantation, sorry for the delay. Actually that made things worse, after putting it in my .bashrc file (at the end) I could no longer bring up either the Wayland nor the X11 desktop. After entering my login credentials both desktops simply keep returning to the login screen and prompting me to again put in my login credentials. I had to login as root, using Wayland to change my .bashrc file back, and even there I encountered difficulties using editors like emacs, xemacs, kate etc. Anything that tried to launch a new window failed. So I resorted to using ed, probably could have used vi if I knew how to but my fingers are trained on emacs. Marc...
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <6a6e3f5f-c7c2-4d62-91d3-d3c8f696f868@marcchamberlin.com> Date & Time: Fri, 16 Aug 2024 10:59:51 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: MC> On 8/14/24 19:18, Masaru Nomiya wrote: MN> > Please set this in your ~/.bashrc MN> > export DISPLAY="${DISPLAY:-:0}" MN> > This is a important setting. MC> Hi Masaru Nomiya, just got the laptop back to try out your incantation, sorry MC> for the delay. Actually that made things worse, after putting it MC> in my .bashrc file (at the end) I could no longer bring up either MC> the Wayland nor the X11 desktop. After entering my login MC> credentials both desktops simply keep returning to the login MC> screen and prompting me to again put in my login credentials. MC> I had to login as root, using Wayland to change my .bashrc file MC> back, and even there I encountered difficulties using editors MC> like emacs, xemacs, kate etc. Anything that tried to launch a new MC> window failed. So I resorted to using ed, probably could have MC> used vi if I knew how to but my fingers are trained on emacs. I was curious about Wayland. As I have never used Wayland. BTW, I strongly advise you to install other DE's such as twm, etc. because of these possible problems. I have installed xfce and Gnome for build checking. And, I also recommend that you master the use of vim. I'm also an Emacs user, but I use vim for terminal processing. The startup is, vim .bashrc To enter edit mode, shift+i After editing, press Esc, then type ":" and wq to save your edits, or q to not save them, and press enter. Anyway, first of all, have't you left a misconfigured config (= Xorg.conf or vesa.conf), have you? I'm curious about your email regarding 2 displys..... If not, please show the log file obtained as follows; 1. Ctrl+Alt+F1 2. login as root 3. execute # init 3 4. Ctrl+Alt+F2 5. login as user (NOT as root) 6. write in ~/.bash_profile with vim export DISPLAY="${DISPLAY:-:0}" 7. execute $ startplasma-x11 > log 2>&1 Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --
On 2024-08-17 12:50, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <6a6e3f5f-c7c2-4d62-91d3-d3c8f696f868@marcchamberlin.com> Date & Time: Fri, 16 Aug 2024 10:59:51 -0700
[MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written:
...
And, I also recommend that you master the use of vim. I'm also an Emacs user, but I use vim for terminal processing.
The startup is,
vim .bashrc
Then you could both instead try "jmacs", which is joe in emacs mode. It is installed by default. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hi, I changed from Fedora to openSUSE due to an error on LUKS during boot. I could boot using an older kernel but couldn't figure out what the issue was/hadn't had the patience. Now it happened on openSUSE, but not even older kernels works. I have no visible option to revert to an older snapshot. Since on openSUSE the root password is set up I'm able to investigate more. Let me start with basic stuff first: how can I mount a LUKS device on dracut's initramfs? No cryptsetup exists??
On 2024-08-17 17:26, lst7cqtfws--- via openSUSE Users wrote: Don't do this. You did a "thread hijack". You took a post of mine, subject "Re: Need help with a laptop that will only run Plasma/Wayland", hit reply to it, then erased the content and the subject, and wrote your own. And it shows. Your post is inserted in the middle of an existing thread. Instead, please create a _new_ post to the mail list.
Hi, I changed from Fedora to openSUSE due to an error on LUKS during boot. I could boot using an older kernel but couldn't figure out what the issue was/hadn't had the patience.
Now it happened on openSUSE, but not even older kernels works. I have no visible option to revert to an older snapshot.
Since on openSUSE the root password is set up I'm able to investigate more.
Are you talking of a root password, or of a LUKS password? Because the root password can be replaced. The LUKS password lost, forget all hope.
Let me start with basic stuff first: how can I mount a LUKS device on dracut's initramfs? No cryptsetup exists??
-- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Weird. I may have done a forward so I could keep the ML address handy but never a reply all. Anyway, reinstalled. Thanks anyway! On Sat, Aug 17, 2024 at 7:07 PM Carlos E. R. <robin.listas@telefonica.net> wrote:
On 2024-08-17 17:26, lst7cqtfws--- via openSUSE Users wrote:
Don't do this.
You did a "thread hijack".
You took a post of mine, subject "Re: Need help with a laptop that will only run Plasma/Wayland", hit reply to it, then erased the content and the subject, and wrote your own.
And it shows. Your post is inserted in the middle of an existing thread.
Instead, please create a _new_ post to the mail list.
Hi, I changed from Fedora to openSUSE due to an error on LUKS during boot. I could boot using an older kernel but couldn't figure out what the issue was/hadn't had the patience.
Now it happened on openSUSE, but not even older kernels works. I have no visible option to revert to an older snapshot.
Since on openSUSE the root password is set up I'm able to investigate more.
Are you talking of a root password, or of a LUKS password?
Because the root password can be replaced. The LUKS password lost, forget all hope.
Let me start with basic stuff first: how can I mount a LUKS device on dracut's initramfs? No cryptsetup exists??
-- Cheers / Saludos,
Carlos E. R. (from 15.5 x86_64 at Telcontar)
On 8/17/24 05:14, Carlos E. R. wrote:
On 2024-08-17 12:50, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <6a6e3f5f-c7c2-4d62-91d3-d3c8f696f868@marcchamberlin.com> Date & Time: Fri, 16 Aug 2024 10:59:51 -0700
[MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written:
...
And, I also recommend that you master the use of vim. I'm also an Emacs user, but I use vim for terminal processing.
The startup is,
vim .bashrc
Then you could both instead try "jmacs", which is joe in emacs mode. It is installed by default. OOOH! I LIKE IT!!! Thanks for the tip, I won't forget it! Marc...
On 2024-08-17 23:38, Marc Chamberlin via openSUSE Users wrote:
On 8/17/24 05:14, Carlos E. R. wrote:
On 2024-08-17 12:50, Masaru Nomiya wrote:
Then you could both instead try "jmacs", which is joe in emacs mode. It is installed by default.
OOOH! I LIKE IT!!! Thanks for the tip, I won't forget it! Marc...
It is also included in the rescue partition of the installation DVD. Unfortunately, they don't install the symlinks to joe, last time I looked: jstar → joe jmacs → joe Depending on what name you use to call the program, the interface changes and emulates a different editor. There is no jvi, though 😛 -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <f849f461-a910-4c8b-b63e-2f2d40eb7c25@telefonica.net> Date & Time: Sat, 17 Aug 2024 14:14:45 +0200 [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: MN> > And, I also recommend that you master the use of vim. I'm also an MN> > Emacs user, but I use vim for terminal processing. MN> > The startup is, MN> > vim .bashrc CER> Then you could both instead try "jmacs", which is joe in emacs CER> mode. It is installed by default. Thanks. But as far as Marc is concerned, he can use emacs with no problem. I like emacs, but it's heavy, so I often use vim because it is very light. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices ― and change is hard." -- Employers don’t practice what they preach on skills-based hiring --
On 2024-08-18 02:23, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <f849f461-a910-4c8b-b63e-2f2d40eb7c25@telefonica.net> Date & Time: Sat, 17 Aug 2024 14:14:45 +0200
[CER] == "Carlos E. R." <robin.listas@telefonica.net> has written:
MN> > And, I also recommend that you master the use of vim. I'm also an MN> > Emacs user, but I use vim for terminal processing.
MN> > The startup is,
MN> > vim .bashrc
CER> Then you could both instead try "jmacs", which is joe in emacs CER> mode. It is installed by default.
Thanks.
But as far as Marc is concerned, he can use emacs with no problem.
I like emacs, but it's heavy, so I often use vim because it is very light.
The thing is, if you are used to the emacs interface, jmacs is a very light editor that emulates emacs and works in a terminal or in text mode. It is also included in the rescue partition of the installation DVD. So it should be easy for you to use in emergencies. -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <b1fadfe8-8830-4911-9f58-5521af2099e2@telefonica.net> Date & Time: Sun, 18 Aug 2024 03:40:21 +0200 [CER] == "Carlos E. R." <robin.listas@telefonica.net> has written: It's already 3 a.m! [...] MN> > I like emacs, but it's heavy, so I often use vim because it is very MN> > light. CER> The thing is, if you are used to the emacs interface, jmacs is a CER> very light editor that emulates emacs and works in a terminal or CER> in text mode. It is also included in the rescue partition of the CER> installation DVD. I was checking because you said. It sure is light. Thanks for the good info. CER> So it should be easy for you to use in emergencies. Bingo! I learned vim in a hurry when I had to start in resucue mode and edit the fstab. (^^;; Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Japan was the future but it's stuck in the past" -- Rupert Wingfield-Hayes (BBC) --
On 2024-08-18 04:19, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <b1fadfe8-8830-4911-9f58-5521af2099e2@telefonica.net> Date & Time: Sun, 18 Aug 2024 03:40:21 +0200
[CER] == "Carlos E. R." <robin.listas@telefonica.net> has written:
It's already 3 a.m!
O:-) I just had a look before going to bed and powering off.
[...] MN> > I like emacs, but it's heavy, so I often use vim because it is very MN> > light.
CER> The thing is, if you are used to the emacs interface, jmacs is a CER> very light editor that emulates emacs and works in a terminal or CER> in text mode. It is also included in the rescue partition of the CER> installation DVD.
I was checking because you said. It sure is light.
Thanks for the good info.
CER> So it should be easy for you to use in emergencies.
Bingo!
I learned vim in a hurry when I had to start in resucue mode and edit the fstab. (^^;;
Yes, same here. I learned minimal vi commands for emergencies. But years ago we convinced the SUSE people to include "joe" in the rescue system, same as "vi". The first time I used "vi" I had to kill the remote terminal I was using to access the Linux machine at the office. I did not know how to exit, there was no help or anything. Emacs was more friendly. Just a bit. :-) -- Cheers / Saludos, Carlos E. R. (from 15.5 x86_64 at Telcontar)
And, I also recommend that you master the use of vim. I second this. It's not that difficult, and you don't really need to be an expert with it. Just fire off google search and enter "vi cheat sheet". You'll be presented with a plethora of articles to read or pdf's to print. Then play around with it in a c/konsole.
Dunno if it's still true, but back in the old days of SUNOS (pre-Solaris) if forced into a command prompt, after failed boot, vi was about the only tool available to fix things (the copy for root was statically linked at compile time so it didn't require any outside help). Saved my bacon more than a few times.
On Sat, 17 Aug 2024 07:47:14 -0800 Bill Swisher wrote: 8< - - - - - snipped - - - - - >8
Dunno if it's still true, but back in the old days of SUNOS (pre-Solaris) if forced into a command prompt, after failed boot, vi was about the only tool available to fix things (the copy for root was statically linked at compile time so it didn't require any outside help). Saved my bacon more than a few times.
It is SO funny (and a bit strange) to read this here since 4.1.x was my "daily driver" until Linux (1.x) caught my eye. :) I miss those days. Thanks for this memory! Carl
On 8/17/24 5:50 AM, Masaru Nomiya wrote:
BTW, I strongly advise you to install other DE's such as twm, etc. because of these possible problems. I have installed xfce and Gnome for build checking.
kde3 + fluxbox - can't go wrong :) (and of course twm from the minimal X install) Back in the day, I used to try every desktop suse offered. Even the weird ones from blackbox to e-16 to sawfish, etc.. back before desktops to 100s of MB (or even GB) and they didn't try and take over your entire system (the smaller ones still don't, gnome and plasma are other cases altogether) -- David C. Rankin, J.D.,P.E.
On 8/12/24 19:56, Masaru Nomiya wrote:
Hello,
In the Message;
This can be done in a virtual console, which is the usual way;
At the login screen;
1. Ctrl+Alt+F1 key OK
2. Log in as root OK
3. Execute
# init 3 OK but took over a minute to complete
4. Ctrl+Alt+F2 key OK
5. Log in as root, again OK
6. Exucute
$ startplasma-x11 > /tmp/plasama.log 2>&1 OK
Then, check the plasma.log.
marcslaptop:~> cat /tmp/plasma.log $DISPLAY is not set or cannot connect to the X server. Again no joy, I tried this with and without setting export DISPLAY="${DISPLAY:-:0}" in my /home/marc/.bashrc file and it made no difference. I also noted that /root does not have a .bashrc file, should I create one for root logins? Thanks again for your time, thoughts, and help. Marc..
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <1c528155-e046-4088-9b69-7ec15fbab00e@marcchamberlin.com> Date & Time: Sat, 17 Aug 2024 15:40:14 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: MC> On 8/12/24 19:56, Masaru Nomiya wrote: [...] Mn> > Then, check the plasma.log. [...] MN > # init 3 MC> OK buut took over a minute to complete This is strange! [...] MN> Then, check the plasma.log. MC> marcslaptop:~> cat /tmp/plasma.log MC> $DISPLAY is not set or cannot connect to the X server. [...] The message seems to be looking for a virtual display....? Please show the results of; 1. $ ls -l /etc/X11/xorg.conf.d/ 2. $ ls -l /usr/share/X11/xorg.conf.d/ Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --
On 8/17/24 17:49, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID :<1c528155-e046-4088-9b69-7ec15fbab00e@marcchamberlin.com> Date & Time: Sat, 17 Aug 2024 15:40:14 -0700
[MC] == Marc Chamberlin via openSUSE Users<users@lists.opensuse.org> has written:
MC> On 8/12/24 19:56, Masaru Nomiya wrote: [...] Mn> > Then, check the plasma.log.
[...] MN > # init 3
MC> OK buut took over a minute to complete
This is strange!
[...] MN> Then, check the plasma.log.
MC> marcslaptop:~> cat /tmp/plasma.log MC> $DISPLAY is not set or cannot connect to the X server. [...]
The message seems to be looking for a virtual display....?
Please show the results of;
1. $ ls -l /etc/X11/xorg.conf.d/ marc@marcslaptop:~> ls -l /etc/X11/xorg.conf.d/ total 16 -rw-r--r-- 1 root root 311 Apr 14 22:25 00-keyboard.conf -rw-r--r-- 1 root root 529 Apr 14 22:25 50-device.conf -rw-r--r-- 1 root root 527 Apr 14 22:25 50-monitor.conf -rw-r--r-- 1 root root 491 Apr 14 22:25 50-screen.conf
2. $ ls -l /usr/share/X11/xorg.conf.d/
marc@marcslaptop:~> ls -l /usr/share/X11/xorg.conf.d/ total 40 -rw-r--r-- 1 root root 1099 Nov 26 2022 10-evdev.conf -rw-r--r-- 1 root root 489 May 17 2023 10-libvnc.conf -rw-r--r-- 1 root root 1350 Apr 11 02:20 10-quirks.conf -rw-r--r-- 1 root root 484 Nov 26 2022 11-evdev.conf -rw-r--r-- 1 root root 1459 Nov 26 2022 40-libinput.conf -rw-r--r-- 1 root root 199 Nov 26 2022 50-elotouch.conf -rw-r--r-- 1 root root 264 Apr 11 02:20 50-extensions.conf -rw-r--r-- 1 root root 1913 May 22 2023 70-synaptics.conf -rw-r--r-- 1 root root 115 May 22 2023 70-vmmouse.conf -rw-r--r-- 1 root root 3465 May 3 2023 70-wacom.conf HTHs, thanks Marc...
Best Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. "
-- Microsoft overhauls cyber strategy to finally embrace security by default --
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <bae54939-f7bc-4151-ac8e-9c4a115d5ed0@marcchamberlin.com> Date & Time: Sun, 18 Aug 2024 10:28:37 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: [...] MC> > Please show the results of; MC> > MC> > 1. $ ls -l /etc/X11/xorg.conf.d/ marc@marcslaptop:~> ls -l /etc/X11/xorg.conf.d/ MC> total 16 MC> -rw-r--r-- 1 root root 311 Apr 14 22:25 00-keyboard.conf MC> -rw-r--r-- 1 root root 529 Apr 14 22:25 50-device.conf MC> -rw-r--r-- 1 root root 527 Apr 14 22:25 50-monitor.conf MC> -rw-r--r-- 1 root root 491 Apr 14 22:25 50-screen.conf MC> > MC> > 2. $ ls -l /usr/share/X11/xorg.conf.d/ marc@marcslaptop:~> ls -l /usr/share/X11/xorg.conf.d/ MC> total 40 MC> -rw-r--r-- 1 root root 1099 Nov 26 2022 10-evdev.conf MC> -rw-r--r-- 1 root root 489 May 17 2023 10-libvnc.conf MC> -rw-r--r-- 1 root root 1350 Apr 11 02:20 10-quirks.conf MC> -rw-r--r-- 1 root root 484 Nov 26 2022 11-evdev.conf MC> -rw-r--r-- 1 root root 1459 Nov 26 2022 40-libinput.conf MC> -rw-r--r-- 1 root root 199 Nov 26 2022 50-elotouch.conf MC> -rw-r--r-- 1 root root 264 Apr 11 02:20 50-extensions.conf MC> -rw-r--r-- 1 root root 1913 May 22 2023 70-synaptics.conf MC> -rw-r--r-- 1 root root 115 May 22 2023 70-vmmouse.conf MC> -rw-r--r-- 1 root root 3465 May 3 2023 70-wacom.conf [...] Thanks. Isn't this what your problem is? https://askubuntu.com/questions/190194/how-can-i-view-an-x-window-from-a-rem... Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Japan was the future but it's stuck in the past" -- Rupert Wingfield-Hayes (BBC) --
On 8/18/24 18:32, Masaru Nomiya wrote:
Isn't this what your problem is?
https://askubuntu.com/questions/190194/how-can-i-view-an-x-window-from-a-rem...
Best Regards.
Still no joy! I tried the following incantation in my .bashrc file under /home/marc - export DISPLAY=local:0.0 and was unable to bring up any desktop manager (I tried all 4 that were offered at the login prompt) Just keeps rejecting my login credentials and cycling back to the login prompt. Marc...
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <10a97ff4-e3c7-4dad-aac7-1610648ba01e@marcchamberlin.com> Date & Time: Mon, 19 Aug 2024 09:35:23 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: MN> > Isn't this what your problem is? MN> > https://askubuntu.com/questions/190194/how-can-i-view-an-x-window-from-a-rem... MC> Still no joy! I tried the following incantation in my .bashrc file under MC> /home/marc - MC> export DISPLAY=local:0.0 ? Is this what the ip address displays in your environment? $ echo $local Anyway, this is all I can think of; export DISPLAY=$(ip address | grep “4” | head -1 | awk '{print $NF}' | awk 'sub(/\r$/,"")'):0 Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --
On 8/19/24 17:58, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID :<10a97ff4-e3c7-4dad-aac7-1610648ba01e@marcchamberlin.com> Date & Time: Mon, 19 Aug 2024 09:35:23 -0700
[MC] == Marc Chamberlin via openSUSE Users<users@lists.opensuse.org> has written:
MN> > Isn't this what your problem is?
MN> >https://askubuntu.com/questions/190194/how-can-i-view-an-x-window-from-a-rem...
MC> Still no joy! I tried the following incantation in my .bashrc file under MC> /home/marc -
MC> export DISPLAY=local:0.0
?
Is this what the ip address displays in your environment? Hmm I am not quite sure what you are asking me to do here, but will take a guess. This is what the command - ip address shows -
marc@marcslaptop:~> ip address 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000 link/ether 38:d5:47:31:54:0fbrd ff:ff:ff:ff:ff:ff altname enp3s0 inet 192.168.10.10/24 brd 192.168.10.255 scope global eth0 valid_lft forever preferred_lft forever 3: wlan0: <BROADCAST,MULTICAST> mtu 1500 qdisc noop state DOWN group default qlen 1000 link/ether e4:a7:a0:46:83:e0brd ff:ff:ff:ff:ff:ff altname wlp2s0
$ echo $local
Anyway, this is all I can think of;
export DISPLAY=$(ip address | grep “4” | head -1 | awk '{print $NF}' | awk 'sub(/\r$/,"")'):0 This incantation doesn't seem to work, and produces a null string. I
and this does not show anything - marc@marcslaptop:~> echo $local marc@marcslaptop:~> tried to break this command down and execute it in partial commands broken at each pipe. I found one error, the quotes around the 4 are wrong, I think. So I changed it and tried this partial command - marc@marcslaptop:~> ip address | grep "4" link/ether 38:d5:47:31:54:0f brd ff:ff:ff:ff:ff:ff inet 192.168.10.10/24brd 192.168.10.255 scope global eth0 link/ether e4:a7:a0:46:83:e0 brd ff:ff:ff:ff:ff:ff Note the change in the quotes around the grep "4" subcommand. But I have a feeling this is not what you wanted either. I took another guess and tried this - marc@marcslaptop:~> ip address | grep "net" inet127.0.0.1/8 scope host lo inet6 ::1/128 scope host inet192.168.10.10/24 brd 192.168.10.255 scope global eth0 Seems promising, so - marc@marcslaptop:~> ip address | grep "net" | head -1 inet 127.0.0.1/8 scope host lo Again, seems promising, though I am totally guessing what your incantation was trying to accomplish. So trying the next step - marc@marcslaptop:~> ip address | grep "net" | head -1 | awk '{print $NF}' lo Now I am outside of my comfort zone, I am not a user of awk so this is out of my league! Taking this to the last step produces a null string - marc@marcslaptop:~> ip address | grep "net" | head -1 | awk '{print $NF}' | awk 'sub(/\r$/,"")' marc@marcslaptop:~> and at this point I give up! Appears to me the incantation using my modifications also fails, so will turn this back to you! Thanks again and please keep in mind that I am struggling to be helpful. Probably not much, LOL... Marc
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <ad85133e-c59c-4d07-9207-8c076c83dc98@marcchamberlin.com> Date & Time: Tue, 20 Aug 2024 00:50:27 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: [...] MN> > Anyway, this is all I can think of; MN> > export DISPLAY=$(ip address | grep “4” | head -1 | awk '{print $NF}' | awk 'sub(/\r$/,"")'):0 MC> This incantation doesn't seem to work, and produces a null string. I tried to MC> break this command down and execute it in partial commands broken at each MC> pipe. I found one error, the quotes around the 4 are wrong, I think. So I MC> changed it and tried this partial command - marc@marcslaptop:~> ip address | grep "4" MC> link/ether 38:d5:47:31:54:0f brd ff:ff:ff:ff:ff:ff MC> inet 192.168.10.10/24brd 192.168.10.255 scope global eth0 MC> link/ether e4:a7:a0:46:83:e0 brd ff:ff:ff:ff:ff:ff [..] marc@marcslaptop:~> ip address | grep "net" | head -1 | awk '{print $NF}' MC> lo MC> Now I am outside of my comfort zone, I am not a user of awk so this is out of my MC> league! Taking this to the last step produces a null string - marc@marcslaptop:~> ip address | grep "net" | head -1 | awk '{print $NF}' | awk MC> 'sub(/\r$/,"")' MC> marc@marcslaptop:~> I'm Tumbleweed, but like this; $ export DISPLAY=$(ip address | grep “4” | head -1 | awk '{print $NF}' | awk 'sub(/\r$/,"")'):0 $ echo $DISPLAY :0 $ export DISPLAY= $ echo $DISPLAY then, $ export DISPLAY=$(ip address | grep “net” | head -1 | awk '{print $NF}' | awk 'sub(/\r$/,"")'):0 $ echo $DISPALY :0 I think the problem is around the X server? What the result of; 1. $ ps -ef | grep Xorg and 2. $ ls -l /tmp/.X11-unix Test 2 might return nil though.... Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --
On 8/20/24 19:27, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID :<ad85133e-c59c-4d07-9207-8c076c83dc98@marcchamberlin.com> Date & Time: Tue, 20 Aug 2024 00:50:27 -0700
[MC] == Marc Chamberlin via openSUSE Users<users@lists.opensuse.org> has written:
[...] MN> > Anyway, this is all I can think of;
MN> > export DISPLAY=$(ip address | grep “4” | head -1 | awk '{print $NF}' | awk 'sub(/\r$/,"")'):0
MC> This incantation doesn't seem to work, and produces a null string. I tried to MC> break this command down and execute it in partial commands broken at each MC> pipe. I found one error, the quotes around the 4 are wrong, I think. So I MC> changed it and tried this partial command -
marc@marcslaptop:~> ip address | grep "4" MC> link/ether 38:d5:47:31:54:0f brd ff:ff:ff:ff:ff:ff MC> inet 192.168.10.10/24brd 192.168.10.255 scope global eth0 MC> link/ether e4:a7:a0:46:83:e0 brd ff:ff:ff:ff:ff:ff [..] marc@marcslaptop:~> ip address | grep "net" | head -1 | awk '{print $NF}' MC> lo
MC> Now I am outside of my comfort zone, I am not a user of awk so this is out of my MC> league! Taking this to the last step produces a null string -
marc@marcslaptop:~> ip address | grep "net" | head -1 | awk '{print $NF}' | awk MC> 'sub(/\r$/,"")' MC> marc@marcslaptop:~>
I'm Tumbleweed, but like this;
$ export DISPLAY=$(ip address | grep “4” | head -1 | awk '{print $NF}' | awk 'sub(/\r$/,"")'):0
$ echo $DISPLAY :0 OK, same here - marc@marcslaptop:~> export DISPLAY=$(ip address | grep “4” | head -1 | awk '{print $NF}' | awk 'sub(/\r$/,"")'):0 marc@marcslaptop:~> echo $DISPLAY :0
$ export DISPLAY= $ echo $DISPLAY
then,
$ export DISPLAY=$(ip address | grep “net” | head -1 | awk '{print $NF}' | awk 'sub(/\r$/,"")'):0
$ echo $DISPALY :0
Ditto - marc@marcslaptop:~> export DISPLAY=$(ip address | grep “net” | head -1 | awk '{print $NF}' | awk 'sub(/\r$/,"")'):0 marc@marcslaptop:~> echo $DISPLAY :0
I think the problem is around the X server?
What the result of;
1. $ ps -ef | grep Xorg marc@marcslaptop:~> ps -ef | grep Xorg marc 23325 29033 0 21:59 pts/2 00:00:00 grep --color=auto Xorg
Do you expect a process to be running with Xorg as part of it's name? None of my other systems, either 15.4 or 15.5 have such a process.
and
2. $ ls -l /tmp/.X11-unix
marc@marcslaptop:~> ls -l /tmp/.X11-unix total 0 srwxrwxrwx 1 root root 0 Aug 19 09:28 X0 srwxr-xr-x 1 marc users 0 Aug 19 09:28 X1
Test 2 might return nil though....
No, Test 2 did return something, but I don't grok what it means... Thanks so much for staying with me and trying to help, I really do appreciate it! Marc...
On 8/21/24 11:54, David C. Rankin wrote:
On 8/21/24 12:58 PM, Marc Chamberlin via openSUSE Users wrote:
marc@marcslaptop:~> ls -l /tmp/.X11-unix total 0 srwxrwxrwx 1 root root 0 Aug 19 09:28 X0 srwxr-xr-x 1 marc users 0 Aug 19 09:28 X1
This looks strange. Why both?
Wild wild wild guess, could it be because the laptop is located about 40 miles away from my home and I am using SSH to access it? Marc...
On 8/21/24 2:38 PM, Marc Chamberlin via openSUSE Users wrote:
Wild wild wild guess, could it be because the laptop is located about 40 miles away from my home and I am using SSH to access it? Marc...
This is where the synapses in my brain break down from age. I can't recall if remote X (like tightvnc) starts a separate X session. I just can't recall. But, I suspect that is likely it. For some reason I thought it would start an X session if needed, otherwise reuse the current... I'll have to setup a test across the LAN to confirm, but that would be to an Arch box so there may be some config differences. The only other suse box I have to boot is running SUSE 9.0 (presuming it still boots after a long slumber in the corner....) -- David C. Rankin, J.D.,P.E.
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <55b86ea6-3c88-4f44-9231-2b8465d27430@marcchamberlin.com> Date & Time: Wed, 21 Aug 2024 10:58:17 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: [...] MC> marc@marcslaptop:~> ps -ef | grep Xorg MC> marc 23325 29033 0 21:59 pts/2 00:00:00 grep --color=auto Xorg MC> Do you expect a process to be running with Xorg as part of it's MC> name? None of my other systems, either 15.4 or 15.5 have such a MC> process. X Window System not running. .....? Please show the results of; $ cat /var/log/Xorg.0.log | grep -A 30 EE Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices — and change is hard." -- Employers don’t practice what they preach on skills-based hiring --
On 8/21/24 3:51 PM, Masaru Nomiya wrote:
Please show the results of;
$ cat /var/log/Xorg.0.log | grep -A 30 EE
According to the output of:
marc@marcslaptop:~> ls -l /tmp/.X11-unix total 0 srwxrwxrwx 1 root root 0 Aug 19 09:28 X0 srwxr-xr-x 1 marc users 0 Aug 19 09:28 X1
You may also want to try: $ cat /var/log/Xorg.1.log | grep -A 30 EE -- David C. Rankin, J.D.,P.E.
On 8/21/24 15:02, David C. Rankin wrote:
On 8/21/24 3:51 PM, Masaru Nomiya wrote:
Please show the results of;
$ cat /var/log/Xorg.0.log | grep -A 30 EE
According to the output of:
marc@marcslaptop:~> ls -l /tmp/.X11-unix total 0 srwxrwxrwx 1 root root 0 Aug 19 09:28 X0 srwxr-xr-x 1 marc users 0 Aug 19 09:28 X1
You may also want to try:
$ cat /var/log/Xorg.1.log | grep -A 30 EE
Thanks David for your suggestion, but no joy because there is no log file named /var/log/Xorg.1.log Only /var/log/Xorg.0.log Marc
On 8/21/24 13:51, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID :<55b86ea6-3c88-4f44-9231-2b8465d27430@marcchamberlin.com> Date & Time: Wed, 21 Aug 2024 10:58:17 -0700
[MC] == Marc Chamberlin via openSUSE Users<users@lists.opensuse.org> has written:
[...] MC> marc@marcslaptop:~> ps -ef | grep Xorg MC> marc 23325 29033 0 21:59 pts/2 00:00:00 grep --color=auto Xorg
MC> Do you expect a process to be running with Xorg as part of it's MC> name? None of my other systems, either 15.4 or 15.5 have such a MC> process.
X Window System not running. .....?
Please show the results of;
$ cat /var/log/Xorg.0.log | grep -A 30 EE Hmmm looks like there is an error about nv_drv.so but I don't know how to solve it yet...
marcslaptop:/var/log #cat /var/log/Xorg.0.log | grep -A 30 EE [ 335.761] Current Operating System: Linux marcslaptop 5.14.21-150500.55.52-default #1 SMP PREEMPT_DYNAMIC Tue Mar 5 16:53:41 UT C 2024 (a62851f) x86_64 [ 335.761] Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.52-default root=UUID=d0d25271-f3de-436d-9ed1-51648650 f18b splash=silent resume=/dev/disk/by-uuid/e71b7ac4-c002-47da-b903-42eaedee6a78 quiet mitigations=auto [ 335.761] [ 335.761] Current version of pixman: 0.40.0 [ 335.761] Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. [ 335.761] Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. [ 335.761] (==) Log file: "/var/log/Xorg.0.log", Time: Mon Aug 19 09:28:31 2024 [ 335.761] (==) Using config directory: "/etc/X11/xorg.conf.d" [ 335.761] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [ 335.762] (==) No Layout section. Using the first Screen section. [ 335.762] (==) No screen section available. Using defaults. [ 335.762] (**) |-->Screen "Default Screen Section" (0) [ 335.762] (**) | |-->Monitor "<default monitor>" [ 335.763] (==) No monitor specified for screen "Default Screen Section". Using a default monitor configuration. [ 335.763] (==) Automatically adding devices [ 335.763] (==) Automatically enabling devices [ 335.763] (==) Automatically adding GPU devices [ 335.763] (==) Automatically binding GPU devices [ 335.763] (==) Max clients allowed: 512, resource mask: 0xfffff [ 335.763] (WW) The directory "/usr/share/fonts/misc/sgi" does not exist. [ 335.763] Entry deleted from font path. [ 335.763] (==) FontPath set to: /usr/share/fonts/misc:unscaled, /usr/share/fonts/Type1/, /usr/share/fonts/100dpi:unscaled, /usr/share/fonts/75dpi:unscaled, /usr/share/fonts/ghostscript/, /usr/share/fonts/cyrillic:unscaled, /usr/share/fonts/truetype/, built-ins [ 335.763] (==) ModulePath set to "/usr/lib64/xorg/modules" [ 335.763] (WW) Ignoring unrecognized extension "XFree86-DGA" [ 335.763] (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. [ 335.763] (II) Loader magic: 0x55e483d95de0 -- [ 336.619] (EE) Failed to load /usr/lib64/xorg/modules/drivers/nv_drv.so: /usr/lib64/xorg/modules/drivers/nv_drv.so: undefined s ymbol: fbdevHWSave [ 336.619] (EE) Failed to load module "nv" (loader failed, 0) [ 336.619] (II) LoadModule: "modesetting" [ 336.619] (II) Loading /usr/lib64/xorg/modules/drivers/modesetting_drv.so [ 336.619] (II) Module modesetting: vendor="X.Org Foundation" [ 336.619] compiled for 1.21.1.4, module version = 1.21.1 [ 336.619] Module class: X.Org Video Driver [ 336.619] ABI class: X.Org Video Driver, version 25.2 [ 336.619] (II) LoadModule: "fbdev" [ 336.619] (II) Loading /usr/lib64/xorg/modules/drivers/fbdev_drv.so [ 336.619] (II) Module fbdev: vendor="X.Org Foundation" [ 336.619] compiled for 1.21.1.4, module version = 0.5.0 [ 336.619] Module class: X.Org Video Driver [ 336.619] ABI class: X.Org Video Driver, version 25.2 [ 336.619] (II) LoadModule: "vesa" [ 336.620] (II) Loading /usr/lib64/xorg/modules/drivers/vesa_drv.so [ 336.620] (II) Module vesa: vendor="X.Org Foundation" [ 336.620] compiled for 1.21.1.4, module version = 2.6.0 [ 336.620] Module class: X.Org Video Driver [ 336.620] ABI class: X.Org Video Driver, version 25.2 [ 336.620] (II) NVIDIA dlloader X Driver 550.100 Thu Jun 27 18:17:43 UTC 2024 [ 336.620] (II) NVIDIA Unified Driver for all Supported NVIDIA GPUs [ 336.620] (II) NOUVEAU driver [ 336.620] (II) NOUVEAU driver for NVIDIA chipset families : [ 336.620] RIVA TNT (NV04) [ 336.620] RIVA TNT2 (NV05) [ 336.620] GeForce 256 (NV10) [ 336.620] GeForce 2 (NV11, NV15) [ 336.620] GeForce 4MX (NV17, NV18) [ 336.620] GeForce 3 (NV20) [ 336.620] GeForce 4Ti (NV25, NV28) [ 336.620] GeForce FX (NV3x) -- [ 338.433] (II) Initializing extension MIT-SCREEN-SAVER [ 338.433] (II) Initializing extension DOUBLE-BUFFER [ 338.434] (II) Initializing extension RECORD [ 338.434] (II) Initializing extension DPMS [ 338.434] (II) Initializing extension Present [ 338.434] (II) Initializing extension DRI3 [ 338.434] (II) Initializing extension X-Resource [ 338.434] (II) Initializing extension XVideo [ 338.434] (II) Initializing extension XVideo-MotionCompensation [ 338.434] (II) Initializing extension GLX [ 338.434] (II) Initializing extension GLX [ 338.435] (II) Indirect GLX disabled. [ 338.435] (II) GLX: Another vendor is already registered for screen 0 [ 338.435] (II) Initializing extension XFree86-VidModeExtension [ 338.435] (II) Initializing extension XFree86-DGA [ 338.435] (II) Initializing extension XFree86-DRI [ 338.435] (II) Initializing extension DRI2 [ 338.435] (II) Initializing extension NV-GLX [ 338.435] (II) Initializing extension NV-CONTROL [ 338.435] (II) Initializing extension XINERAMA [ 338.564] (II) config/udev: Adding input device Power Button (/dev/input/event3) [ 338.565] (**) Power Button: Applying InputClass "evdev keyboard catchall" [ 338.565] (**) Power Button: Applying InputClass "libinput keyboard catchall" [ 338.565] (**) Power Button: Applying InputClass "system-keyboard" [ 338.565] (II) LoadModule: "libinput" [ 338.565] (II) Loading /usr/lib64/xorg/modules/input/libinput_drv.so [ 338.566] (II) Module libinput: vendor="X.Org Foundation" [ 338.566] compiled for 1.21.1.4, module version = 1.2.1 [ 338.566] Module class: X.Org XInput Driver [ 338.566] ABI class: X.Org XInput driver, version 24.4 [ 338.566] (II) Using input driver 'libinput' for 'Power Button'
Best Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "To hire for skills, firms will need to implement robust and intentional changes in their hiring practices — and change is hard."
-- Employers don’t practice what they preach on skills-based hiring --
Marc Chamberlin composed on 2024-08-21 22:06 (UTC-0700): ...
[ 336.619] (EE) Failed to load /usr/lib64/xorg/modules/drivers/nv_drv.so: /usr/lib64/xorg/modules/drivers/nv_drv.so: undefined s ymbol: fbdevHWSave [ 336.619] (EE) Failed to load module "nv" (loader failed, 0)
If your NVidia GPU is more than two decades old, possibly there might be hope to make it functional if kernel modesetting is disabled. Even if it managed to load, the possibility it won't subsequently unload is near zilch. Note the names contained in the description: # zypper info xf86-video-nv ... Information for package xf86-video-nv: ... Summary : NVIDIA video driver for the Xorg X server Description : nv is an Xorg driver for NVIDIA video cards. The driver supports 2D acceleration and provides support for the following framebuffer depths: 8, 15, 16 (except Riva128) and 24. All visual types are supported for depth 8, TrueColor and DirectColor visuals are supported for the other depths with the exception of the Riva128 which only supports TrueColor in the higher depths. Xorg tries to load every display driver conceptually possible to use with an available GPU. It determines which that succeeded to load has highest priority, keeps it loaded, and unloads the rest. -- 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
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <c52cdc75-652f-4178-bdf2-eca84f9c5f77@marcchamberlin.com> Date & Time: Wed, 21 Aug 2024 22:06:35 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: MC> On 8/21/24 13:51, Masaru Nomiya wrote: [...] MN> > X Window System not running. .....? MN> > Please show the results of; MN> > $ cat /var/log/Xorg.0.log | grep -A 30 EE MC> Hmmm looks like there is an error about nv_drv.so but I don't know MChow to solve it yet... MC> marcslaptop:/var/log #cat /var/log/Xorg.0.log | grep -A 30 EE [...] MC> [ 336.619] (EE) Failed to load /usr/lib64/xorg/modules/drivers/nv_drv.so: MC> /usr/lib64/xorg/modules/drivers/nv_drv.so: undefined s MC> ymbol: fbdevHWSave [...] I finally figured it out. It was all because the X Window System was not running. If you don't use neuveau, the following result serves for Felix; $ inxi -Ga But Felix, you'd better go to bed. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Microsoft is overhauling its cybersecurity strategy, called the Secure Future Initiative, to incorporate key security features into its core set of technology platforms and cloud services. " -- Microsoft overhauls cyber strategy to finally embrace security by default --
Masaru Nomiya composed on 2024-08-22 17:56 (UTC+0900):
If you don't use neuveau, the following result serves for Felix;
$ inxi -Ga
Actually no. S is also desired to include kernel version & cmdline options. Adding additionally z redacts possibly sensitive data. Adding also --vs notifies the version and date of inxi release, helpful in interpreting since data provided has changed over time, and Leap rarely gets its inxi version incremented. Another option holds back even more, --za. Thus: inxi -GSaz --vs --za is ideal for most FOSS graphics troubleshooting, not just "not" nouveau.
But Felix, you'd better go to bed.
I did that, but 90m later, I was back up with an urge to finish something started earlier. While doing that, your post arrived. I'm hoping to get back to sleep before sunup. :p -- 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
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <4c8daf1c-505b-c1bb-31b5-e79bfd29793c@earthlink.net> Date & Time: Thu, 22 Aug 2024 05:56:41 -0400 [FM] == Felix Miata <mrmazda@earthlink.net> has written: FM> Masaru Nomiya composed on 2024-08-22 17:56 (UTC+0900): MN> > If you don't use neuveau, the following result serves for Felix; MN> > $ inxi -Ga FM> Actually no. S is also desired to include kernel version & FM> cmdline options. Adding additionally z redacts possibly sensitive FM> data. Adding also --vs notifies the version and date of inxi FM> release, helpful in interpreting since data provided has changed FM> over time, and Leap rarely gets its inxi version FM> incremented. Another option holds back even more, --za. Thus: FM> inxi -GSaz --vs --za FM> is ideal for most FOSS graphics troubleshooting, not just "not" nouveau. Thanks. But I wonder... Isn't Marc using a patched and built driver? I mean, with that symbolic error, it shouldn't have been built? MN> > But Felix, you'd better go to bed. FM> I did that, but 90m later, I was back up with an urge to finish FM> something started earlier. While doing that, your post FM> arrived. I'm hoping to get back to sleep before sunup. :p Have a good sleep! I'm going to bed soon. v(^O^) Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "When you are young, if you stay up often too late, you will pay for it when you get older." -- An Universal Saying --
On 8/22/24 02:56, Felix Miata wrote:
Actually no. S is also desired to include kernel version & cmdline options. Adding additionally z redacts possibly sensitive data. Adding also --vs notifies the version and date of inxi release, helpful in interpreting since data provided has changed over time, and Leap rarely gets its inxi version incremented. Another option holds back even more, --za. Thus:
inxi -GSaz --vs --za
Thanks guys, If I grok correctly I think you are asking me to run this command on my laptop. So here is the results - marcslaptop:/etc/default #inxi -GSaz --vs --za inxi 3.3.23-00 (2022-10-31) System: Kernel:5.14.21-150500.55.52-default arch:x86_64 bits:64 compiler:gcc v:7.5.0 parameters:BOOT_IMAGE=/boot/vmlinuz-5.14.21-150500.55.52-default root=UUID=<filter> splash=silent resume=/dev/disk/by-uuid/e71b7ac4-c002-47da-b903-42eaedee6a78 quiet mitigations=auto Console:pty pts/2 DM:SDDM Distro:openSUSE Leap 15.5 Graphics: Device-1:NVIDIA GP104BM [GeForce GTX 1070 Mobile] vendor:ASUSTeK driver:nvidia v:550.100 alternate:nouveau,nvidia_drm non-free:520.xx+ status:current (as of 2022-10) arch:Pascal code:GP10x process:TSMC 16nm built:2016-21 pcie:gen:1 speed:2.5 GT/s lanes:16 link-max: gen:3 speed:8 GT/s ports:active:none off:eDP-1 empty:DP-1,DP-2,HDMI-A-1 bus-ID:01:00.0 chip-ID:10de:1be1 class-ID:0300 Device-2:Realtek USB2.0 HD UVC WebCam type:USB driver:uvcvideo bus-ID:1-4:3 chip-ID:0bda:57fa class-ID:0e02 serial:<filter> Display:x11 server:X.org v:1.21.1.4 with:Xwayland v:22.1.5 compositor:kwin_wayland driver:X:loaded:nvidia unloaded:fbdev,modesetting,nouveau,vesa failed:nv gpu:nvidia,nvidia-nvswitch tty:165x30 Monitor-1:eDP-1 model:LG Display 0x04e8 built:2015 res:1920x1080 dpi:128 gamma:1.2 size:382x215mm (15.04x8.46") diag:438mm (17.3") ratio:16:9 modes:1920x1080 API:OpenGL Message:GL data unavailable in console for root. HTHs, Marc...
Hello, In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <71799b19-3d93-4202-a2fb-d106ec1efa08@marcchamberlin.com> Date & Time: Thu, 22 Aug 2024 10:05:04 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: [...] MC> marcslaptop:/etc/default #inxi -GSaz --vs --za [...] MC> Device-1:NVIDIA GP104BM [GeForce GTX 1070 Mobile] vendor:ASUSTeK MC> driver:nvidia v:550.100 [...] You can only use the 470 driver, not 550.100. If someone know how to deal with this problem, please advise him. Best Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Japan was the future but it's stuck in the past" -- Rupert Wingfield-Hayes (BBC) --
On 8/22/24 8:22 PM, Masaru Nomiya wrote:
You can only use the 470 driver, not 550.100.
If someone know how to deal with this problem, please advise him.
I'd start with either Yast or zypper or just: # rpm -qa | grep 'nvidia' if that gives a concise list of the nvidia driver rpms you have installed, then just: # zypper rm < <(rpm -qa | grep 'nvidia') Then install the G05 driver. If you are on tumbleweed and need drivers patched for the 6.10 kernel, use the drivers in: https://download.opensuse.org/repositories/home:/drankinatty:/branches:/home... (the buildservice files creating the driver are at) https://build.opensuse.org/package/show/home:drankinatty:branches:home:ligur... Add a temporary repository, e.g. # zypper ar -k https://download.opensuse.org/repositories/home:/drankinatty:/branches:/home... nvidiatmp Then install with zypper or yast selecting the files from the nvidiatmp repository. You should be able to do it with: # zypper in --allow-vendor-change --oldpackage nvidia-gfxG05-kmp-default-470.256.02_k6.10.5_1-8.4.x86_64.rpm which should pull in the other packages. If not, just install all package from that repo. It has Leap 15.4 - Tumbleweed. -- David C. Rankin, J.D.,P.E.
Hello, I'm writing this just in case there are a lot of people watching. In the Message; Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID : <10a97ff4-e3c7-4dad-aac7-1610648ba01e@marcchamberlin.com> Date & Time: Mon, 19 Aug 2024 09:35:23 -0700 [MC] == Marc Chamberlin via openSUSE Users <users@lists.opensuse.org> has written: [...] MC> and was unable to bring up any desktop manager (I tried all 4 MC> that were offered at the login prompt) Just keeps rejecting my MC> login credentials and cycling back to the login prompt. Every DM runs startplasma-x11. In other words, changing DMs does not make any sense. Your problem is with the startplasma-x11 run. Best Regards & Good Night. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Japan was the future but it's stuck in the past" -- Rupert Wingfield-Hayes (BBC) --
On 8/20/24 03:24, Masaru Nomiya wrote:
Hello,
I'm writing this just in case there are a lot of people watching.
In the Message;
Subject : Re: Need help with a laptop that will only run Plasma/Wayland Message-ID :<10a97ff4-e3c7-4dad-aac7-1610648ba01e@marcchamberlin.com> Date & Time: Mon, 19 Aug 2024 09:35:23 -0700
[MC] == Marc Chamberlin via openSUSE Users<users@lists.opensuse.org> has written:
[...] MC> and was unable to bring up any desktop manager (I tried all 4 MC> that were offered at the login prompt) Just keeps rejecting my MC> login credentials and cycling back to the login prompt.
Every DM runs startplasma-x11. In other words, changing DMs does not make any sense. Interesting! I learn a thing or two every day! Thanks Masaru Nomiya! Marc... Your problem is with the startplasma-x11 run. I believe you! So if we can just figure out how to get startplasma-x11 to behave itself....
Best Regards & Good Night.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ lake.dti.ne.jp ┃＼／彡 ┗━━┛ "Japan was the future but it's stuck in the past"
-- Rupert Wingfield-Hayes (BBC) --
participants (9)
-
-pj -
Bill Swisher -
Carl Hartung -
Carlos E. R. -
David C. Rankin -
Felix Miata -
lst7cqtfws＠ol1y.com -
Marc Chamberlin -
Masaru Nomiya