startkde: Could not start kdeinit5. Check your installation.
Hello - I have a recalcitrant computer running OpenSuSE 15.3 that is refusing to start the KDE/Plasma desktop. After login I get a dialog box saying "startkde: Could not start kdeinit5. Check your installation." Despite the fact that the KDE/Plasma desktop won't start, I can SSH into the system and everything else (processes, services) I want running do start up OK. In the file /var/log/warn I do see a couple of messages that are of concern, one in particular -
2022-10-24T21:58:44.060159-07:00 nova ksplashqml[2832]: QCoreApplication::arguments: Please instantiate the QApplication object first 2022-10-24T21:58:44.121497-07:00 nova startplasma-x11[2751]: "/usr/lib64/libexec/kf5/start_kdeinit_wrapper" ("--kded", "+kcminit_startup") exited with code 127 The startplasma-x11 error is the one I think I should be most concerned about. Google tells me that an exit with code 127 means there is a missing or unreadable file. I checked to see if "/usr/lib64/libexec/kf5/start_kdeinit_wrapper" exists and it does.
nova:/usr/lib64/libexec/kf5 # ll /usr/lib64/libexec/kf5/start_kdeinit* -rwxr-xr-x 1 root root 10616 Aug 26 2021 /usr/lib64/libexec/kf5/start_kdeinit -rwxr-xr-x 1 root root 6376 Aug 26 2021 /usr/lib64/libexec/kf5/start_kdeinit_wrapper
nova:/ # find /usr -name kcminit_startup -print /usr/bin/kcminit_startup I also ran zypper up to make sure I had all the latest versions of software installed on this system, and I used YaST2 to find any package with files that had "kdeinit" in their provides or file lists and forced
start_kdeinit_wrapper is not a txt file so I am unable to inspect it any further. I also searched for a file called "kcminit_startup" and found it at those packages to be updated as well. That is about as far as my debugging skills can take me, any kind gurus around who can help me get this beast going? Thanks as always, in advance. Marc... -- *"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./)
Hello, In the Message; Subject : startkde: Could not start kdeinit5. Check your installation. Message-ID : <5044e87c-08ab-9bb0-f385-f6f4ebeefa7a@marcchamberlin.com> Date & Time: Mon, 24 Oct 2022 22:53:05 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: MC> Hello - I have a recalcitrant computer running OpenSuSE 15.3 MC> that is refusing to start the KDE/Plasma desktop. After login I MC> get a dialog box saying "startkde: Could not start MC> kdeinit5. Check your installation." [...] Maybe, this log file give you a clue; $ kdeniit5 > kde.log 2>&1 Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "The question of who holds the platform and whether the person or organisation holding it is trustworthy has serious and profound implications in these volatile times. Once trust is broken, it is extremely difficult to restore. It is necessary to diversify in advance." -- Financial Times --
On 10/24/22 23:21, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : startkde: Could not start kdeinit5. Check your installation. Message-ID : <5044e87c-08ab-9bb0-f385-f6f4ebeefa7a@marcchamberlin.com> Date & Time: Mon, 24 Oct 2022 22:53:05 -0700
[MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
MC> Hello - I have a recalcitrant computer running OpenSuSE 15.3 MC> that is refusing to start the KDE/Plasma desktop. After login I MC> get a dialog box saying "startkde: Could not start MC> kdeinit5. Check your installation." [...]
Maybe, this log file give you a clue;
$ kdeniit5 > kde.log 2>&1 Thanks Masaru Nomiya , here is what was produced, not sure what to do about it,
nova:/home/marc # kdeinit5 > kde.log 2>&1 nova:/home/marc # more kde.log kdeinit5: Aborting. $DISPLAY is not set.
Google hasn't been helpful yet, looking for this particular $DISPLAY error message. There are lots of different solutions depending on platform and type of underlying process/purpose involved, but I am still surfing and looking for clues/answers... One thing I tried, no joy, was to enable the sddm.service so that it is started automagically. If you got any good ideas on how to proceed, I sure would appreciate! Marc...
Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "The question of who holds the platform and whether the person or organisation holding it is trustworthy has serious and profound implications in these volatile times. Once trust is broken, it is extremely difficult to restore. It is necessary to diversify in advance."
-- Financial Times --
-- *"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./)
Hello, In the Message; Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <57f9c7f7-cb29-8902-46da-7c58fc624bfe@marcchamberlin.com> Date & Time: Tue, 25 Oct 2022 15:55:00 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: [...] MC> > nova:/home/marc # kdeinit5 > kde.log 2>&1 MC> > nova:/home/marc # more kde.log MC> > kdeinit5: Aborting. $DISPLAY is not set. [...] Ah, I see. Please write this in your .bashrc; export DISPLAY="${DISPLAY:-:0}" Then, you can log in KDE5. Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "A society bound by e-mail and mobile phones deprives us of the freedom to face ourselves and indulge our fantasies." -- Michael Crichton (Speech in Japan) --
On 10/25/22 18:10, Masaru Nomiya wrote:
Ah, I see.
Please write this in your .bashrc;
export DISPLAY="${DISPLAY:-:0}"
Then, you can log in KDE5.
Shouldn't this already be done in the xdg, or X11 setup somewhere? Seems like in the past it was, or maybe in sysconfig or profile.d? I know I don't have to set it on 15.4 and it has been configured correctly since install without having to set a user export of it. That will get you going Marc, but the big question -- Why is it needed? -- David C. Rankin, J.D.,P.E.
Hello, In the Message; Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <fed89f5f-4228-5df3-fd1c-7fb4993cf7dc@suddenlinkmail.com> Date & Time: Tue, 25 Oct 2022 20:27:52 -0500 [DCR] == "David C. Rankin" <drankinatty@suddenlinkmail.com> has written: MN> On 10/25/22 18:10, Masaru Nomiya wrote: MN> > Ah, I see. MN> > MN> > Please write this in your .bashrc; MN> > MN> > export DISPLAY="${DISPLAY:-:0}" MN> > MN> > Then, you can log in KDE5. DCR> Shouldn't this already be done in the xdg, or X11 setup DCR> somewhere? Seems like in the past it was, or maybe in sysconfig DCR> or profile.d? I know I don't have to set it on 15.4 and it has DCR> been configured correctly since install without having to set a DCR> user export of it. DCR> That will get you going Marc, but the big question -- Why is it DCR> needed? export DISPLAY="${DISPLAY:-:0}" is a well known workarond. That is, DISPLAY almost always have to be set when working across unix/linux-machines with X-applications. Therefore, DISPLAY is also referred to as the magic word. Could show the result of; # xdpyinfo | grep -A 3 display Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "She continues to deeply divide opinion, nearly a decade after her death in 2013, due to her policies of privatisation, breaking the power of trade unions, and selling off public housing." -- World Is One News --
On Wed, 26 Oct 2022 11:21:29 +0900, Masaru Nomiya <nomiya@galaxy.dti.ne.jp> wrote:
In the Message; Date & Time: Tue, 25 Oct 2022 20:27:52 -0500 [DCR] == "David C. Rankin" <drankinatty@suddenlinkmail.com> has written:
MN> On 10/25/22 18:10, Masaru Nomiya wrote: MN> > Please write this in your .bashrc; MN> > MN> > export DISPLAY="${DISPLAY:-:0}" MN> > MN> > Then, you can log in KDE5.
DCR> Shouldn't this already be done in the xdg, or X11 setup DCR> somewhere? Seems like in the past it was, or maybe in sysconfig DCR> or profile.d? I know I don't have to set it on 15.4 and it has DCR> been configured correctly since install without having to set a DCR> user export of it.
DCR> That will get you going Marc, but the big question -- Why is it DCR> needed?
export DISPLAY="${DISPLAY:-:0}"
is a well known workarond. That is, DISPLAY almost always have to be set when working across unix/linux-machines with X-applications. Therefore, DISPLAY is also referred to as the magic word.
Would there be any disadvantage to putting the export into .profile, rather than into .bashrc ? -- Robert Webb
Hello, In the Message; Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <728469938.138156.1666752693734@mail.yahoo.com> Date & Time: Wed, 26 Oct 2022 02:51:33 +0000 (UTC) [RW] == Robert Webb <webbdg@verizon.net> has written: RW> On Wed, 26 Oct 2022 11:21:29 +0900, Masaru Nomiya <nomiya@galaxy.dti.ne.jp> wrote: RW> > In the Message; RW> > Date & Time: Tue, 25 Oct 2022 20:27:52 -0500 RW> > [DCR] == "David C. Rankin" <drankinatty@suddenlinkmail.com> has written: RW> > RW> > MN> On 10/25/22 18:10, Masaru Nomiya wrote: RW> > MN> > Please write this in your .bashrc; RW> > MN> > RW> > MN> > export DISPLAY="${DISPLAY:-:0}" RW> > MN> > RW> > MN> > Then, you can log in KDE5. [...] RW> Would there be any disadvantage to putting the export into .profile, RW> rather than into .bashrc ? When you log in, the .profiles are recited first, so it's probably better to write in the .profile. In my environment, the login sound written in .profile often does not sound, so I have a habit of writing it in .bashrc. But I think I should write it in .bash_profile, which reads .bashrc, because I never start other shells. Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Tim Cook, the C.E.O. of Apple, said earlier this year that he would not let his nephew join social networks. Bill Gates banned cellphone until his children were teenagers, and Melinda Gates wrote that she wished they had waited even longer. Steve Jobs would not let his young children near iPads." -- The New York Times --
On 10/25/22 21:51, Robert Webb wrote:
Would there be any disadvantage to putting the export into .profile, rather than into .bashrc ?
No. .bash_profile is invoked for interactive login shells (when you type your username/pass to login either locally or remotely over ssh, etc..) while .bashrc is invoked for interactive non-login shells (konsole instances). Non-interactive, e.g. is when bash is invoked to run a script. You want DISPLAY set when you login, so it makes sense to go in profile, but openSUSE /etc/profile will source the system bash.bashrc and your $HOME/.bashrc as well. So exports in either profile or bashrc will work even though it's only needed on your actual login. I still recall DISPLAY being set somewhere in the displaymanager, xdm or X11 setup, but picking around, I can't locate it on 15.4 at the moment (there were changes to sysconfig and what you used displaymanager and windowmanager files for over the past couple of releases) So some up to date dev will have to fill in the blanks. -- David C. Rankin, J.D.,P.E.
Hello, In the Message; Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <5a5fc906-5b79-02ae-7242-44b12c0105f1@suddenlinkmail.com> Date & Time: Tue, 25 Oct 2022 22:42:07 -0500 [DCR] == "David C. Rankin" <drankinatty@suddenlinkmail.com> has written: DCR> On 10/25/22 21:51, Robert Webb wrote: MN> > Would there be any disadvantage to putting the export into .profile, MN> > rather than into .bashrc ? DCR> No. .bash_profile is invoked for interactive login shells (when DCR> you type your username/pass to login either locally or remotely DCR> over ssh, etc..) while .bashrc is invoked for interactive DCR> non-login shells (konsole instances). Non-interactive, e.g. is DCR> when bash is invoked to run a script. DCR> You want DISPLAY set when you login, so it makes sense to go in DCR> profile, but openSUSE /etc/profile will source the system DCR> bash.bashrc and your $HOME/.bashrc as well. So exports in either DCR> profile or bashrc will work even though it's only needed on your DCR> actual login. Thanks to you, I am aware that I am using it with uncertain knowledge. I knew that .bashrc was executed every time I started the terminal, but I learned for the first time that I should not write environment variable settings in .bashrc. So I moved the environment variable settings to .bash_profile. The loading order of the system to .bash_profice --> .profile --> .bashrc I see... DCR> I still recall DISPLAY being set somewhere in the DCR> displaymanager, xdm or X11 setup, but picking around, I can't DCR> locate it on 15.4 at the moment there were changes to sysconfig DCR> and what you used displaymanager and windowmanager files for over DCR> the past couple of releases) DCR> So some up to date dev will have to fill in the blanks. I don't remember that the DISPLAY environment variable was set, but rather, I have had many experiences of difficulty in building because it was not set. Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "It should never be said that it is OK to ignore the theoretical as long as it becomes a tool." -- T. Mori (The original is in Japanese) --
On 10/25/22 23:28, Andrei Borzenkov wrote:
On 26.10.2022 06:42, David C. Rankin wrote:
I still recall DISPLAY being set somewhere in the displaymanager, xdm or X11 setup,
I fail to find a single word about using displaymanager or GUI login in original post.
There are times, inquiring minds just want to know.... :) -- David C. Rankin, J.D.,P.E.
On 10/25/22 21:28, Andrei Borzenkov wrote:
On 26.10.2022 06:42, David C. Rankin wrote:
I still recall DISPLAY being set somewhere in the displaymanager, xdm or X11 setup,
I fail to find a single word about using displaymanager or GUI login in original post.
Sorry Andrei, if you are referring to my original post, I am not always sure what info needs to be included v.s. what info can be inferred from my questions. I think Yast2 -- alternatives will give you a more definitive answer than I can. There is much here that I do not yet grok about Linux, so I am on a steep learning curve.
Name │Current choice │Status │ │chardetect │/usr/bin/chardetect-3.6 │auto │ │ctags │/usr/bin/ctags-exuberant │auto │ │dbus-launch │/usr/bin/dbus-launch.x11 │auto │ │default-displaymanager │/usr/lib/X11/displaymanagers/sddm │manual │ │default-xsession.desktop│/usr/share/xsessions/plasma5.desktop│auto │ │easy_install │/usr/bin/easy_install-3.6 │auto │ │gtk-update-icon-cache │/usr/bin/gtk-update-icon-cache-3.0 │auto │ │mt │/usr/bin/gnumt │auto │ │rmt │/usr/bin/srmt │auto │ │
Regards and thanks for your question and request for clarification, Marc -- *"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./)
On 10/25/22 19:21, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <fed89f5f-4228-5df3-fd1c-7fb4993cf7dc@suddenlinkmail.com> Date & Time: Tue, 25 Oct 2022 20:27:52 -0500
[DCR] == "David C. Rankin" <drankinatty@suddenlinkmail.com> has written:
MN> On 10/25/22 18:10, Masaru Nomiya wrote: MN> > Ah, I see. MN> > MN> > Please write this in your .bashrc; MN> > MN> > export DISPLAY="${DISPLAY:-:0}" MN> > MN> > Then, you can log in KDE5.
DCR> Shouldn't this already be done in the xdg, or X11 setup DCR> somewhere? Seems like in the past it was, or maybe in sysconfig DCR> or profile.d? I know I don't have to set it on 15.4 and it has DCR> been configured correctly since install without having to set a DCR> user export of it.
DCR> That will get you going Marc, but the big question -- Why is it DCR> needed?
Unfortunately it didn't get me going David! Sigh....
export DISPLAY="${DISPLAY:-:0}"
is a well known workarond.
That is, DISPLAY almost always have to be set when working across unix/linux-machines with X-applications.
Therefore, DISPLAY is also referred to as the magic word.
Could show the result of;
# xdpyinfo | grep -A 3 display
Using SSH to connect into this system, and su to root this is what your incantation gave me -
nova:/home/marc # xdpyinfo | grep -A 3 display Invalid MIT-MAGIC-COOKIE-1 keyNo protocol specified xdpyinfo: unable to open display ":0".
Doesn't look good to my eyes, but love the "MAGIC-COOKIE" name! Marc...
Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "She continues to deeply divide opinion, nearly a decade after her death in 2013, due to her policies of privatisation, breaking the power of trade unions, and selling off public housing."
-- World Is One News --
-- *"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./)
Hello, In the Message; Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <503276af-5b87-6bcd-68e0-76b93abf047c@marcchamberlin.com> Date & Time: Tue, 25 Oct 2022 22:15:58 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: [...] MC> > In the Message; MC> > MC> > Subject : Re: startkde: Could not start kdeinit5. Check your installation. MC> > Message-ID : <fed89f5f-4228-5df3-fd1c-7fb4993cf7dc@suddenlinkmail.com> MC> > Date & Time: Tue, 25 Oct 2022 20:27:52 -0500 MC> > MC> > [DCR] == "David C. Rankin" <drankinatty@suddenlinkmail.com> has written: MC> > MC> > MN> On 10/25/22 18:10, Masaru Nomiya wrote: MC> > MN> > Ah, I see. MC> > MN> > MC> > MN> > Please write this in your .bashrc; MC> > MN> > MC> > MN> > export DISPLAY="${DISPLAY:-:0}" MC> > MN> > MC> > MN> > Then, you can log in KDE5. MC> > MC> > DCR> Shouldn't this already be done in the xdg, or X11 setup MC> > DCR> somewhere? Seems like in the past it was, or maybe in sysconfig MC> > DCR> or profile.d? I know I don't have to set it on 15.4 and it has MC> > DCR> been configured correctly since install without having to set a MC> > DCR> user export of it. MC> > MC> > DCR> That will get you going Marc, but the big question -- Why is it MC> > DCR> needed? MC> Unfortunately it didn't get me going David! Sigh.... MC> > export DISPLAY="${DISPLAY:-:0}" MC> > MC> > is a well known workarond. MC> > MC> > That is, DISPLAY almost always have to be set when working across MC> > unix/linux-machines with X-applications. MC> > MC> > Therefore, DISPLAY is also referred to as the magic word. MC> > MC> > Could show the result of; MC> > MC> > # xdpyinfo | grep -A 3 display MC> Using SSH to connect into this system, and su to root this is what your MC> incantation gave me - MC> > nova:/home/marc # xdpyinfo | grep -A 3 display MC> > Invalid MIT-MAGIC-COOKIE-1 keyNo protocol specified MC> > xdpyinfo: unable to open display ":0". [...] This means; # env | grep DISPLAY # In my case; 1. as an user $ env | grep DISPLAY $ DISPLAY=:0.0 2. as root # env | grep DISPLAY # DISPLAY=:0.0 I have a .bash_profile (previously, .bashrc) with export DISPLAY="${DISPLAY:-:0}" and just set it to ... Can I get the same result as this? $ env | grep DISPLAY $ DISPLAY=:0.0 where 0.0 is an environment-dependent number. Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
On 10/25/22 22:43, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <503276af-5b87-6bcd-68e0-76b93abf047c@marcchamberlin.com> Date & Time: Tue, 25 Oct 2022 22:15:58 -0700
[MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
[...] MC> > In the Message; MC> > MC> > Subject : Re: startkde: Could not start kdeinit5. Check your installation. MC> > Message-ID : <fed89f5f-4228-5df3-fd1c-7fb4993cf7dc@suddenlinkmail.com> MC> > Date & Time: Tue, 25 Oct 2022 20:27:52 -0500 MC> > MC> > [DCR] == "David C. Rankin" <drankinatty@suddenlinkmail.com> has written: MC> > MC> > MN> On 10/25/22 18:10, Masaru Nomiya wrote: MC> > MN> > Ah, I see. MC> > MN> > MC> > MN> > Please write this in your .bashrc; MC> > MN> > MC> > MN> > export DISPLAY="${DISPLAY:-:0}" MC> > MN> > MC> > MN> > Then, you can log in KDE5. MC> > MC> > DCR> Shouldn't this already be done in the xdg, or X11 setup MC> > DCR> somewhere? Seems like in the past it was, or maybe in sysconfig MC> > DCR> or profile.d? I know I don't have to set it on 15.4 and it has MC> > DCR> been configured correctly since install without having to set a MC> > DCR> user export of it. MC> > MC> > DCR> That will get you going Marc, but the big question -- Why is it MC> > DCR> needed?
MC> Unfortunately it didn't get me going David! Sigh....
MC> > export DISPLAY="${DISPLAY:-:0}" MC> > MC> > is a well known workarond. MC> > MC> > That is, DISPLAY almost always have to be set when working across MC> > unix/linux-machines with X-applications. MC> > MC> > Therefore, DISPLAY is also referred to as the magic word. MC> > MC> > Could show the result of; MC> > MC> > # xdpyinfo | grep -A 3 display MC> Using SSH to connect into this system, and su to root this is what your MC> incantation gave me - MC> > nova:/home/marc # xdpyinfo | grep -A 3 display MC> > Invalid MIT-MAGIC-COOKIE-1 keyNo protocol specified MC> > xdpyinfo: unable to open display ":0". [...]
This means;
# env | grep DISPLAY #
In my case;
1. as an user
$ env | grep DISPLAY $ DISPLAY=:0.0 as user marc I get -
marc@nova:~> env | grep DISPLAY DISPLAY=:0
2. as root
# env | grep DISPLAY # DISPLAY=:0.0 as root I get -
nova:/home/marc # env | grep DISPLAY DISPLAY=:0
I have a .bash_profile (previously, .bashrc) with
export DISPLAY="${DISPLAY:-:0}"
and just set it to ...
Can I get the same result as this?
$ env | grep DISPLAY $ DISPLAY=:0.0
where 0.0 is an environment-dependent number.
See above for the results for both root and user marc. The only difference I see (don't know if it is important) is that for you DISPLAY is :0.0 whereas DISPLAY for me is simply :0 I also tried changing the name of the .bashrc file, for user marc, to .bash_profile It didn't help or make a difference. Marc...
Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "Bill! You married with Computer. Not with Me!" "No..., with money."
-- *"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./)
Hello, In the Message; Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <261c8fc4-eb91-ac85-82d6-b91d765d946c@marcchamberlin.com> Date & Time: Tue, 25 Oct 2022 23:22:27 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: [...] MC> > I have a .bash_profile (previously, .bashrc) with MC> > MC> > export DISPLAY="${DISPLAY:-:0}" MC> > MC> > and just set it to ... MC> > MC> > Can I get the same result as this? MC> > MC> > $ env | grep DISPLAY MC> > $ DISPLAY=:0.0 MC> > MC> > where 0.0 is an environment-dependent number. MC> See above for the results for both root and user marc. The only difference I see MC> (don't know if it is important) is that for you DISPLAY is :0.0 whereas DISPLAY MC> for me is simply :0 MC> I also tried changing the name of the .bashrc file, for user marc, to MC> .bash_profile It didn't help or make a difference. Marc... What does this give you? $ xauth list|grep `uname -n` And, please show your .bash_profice. Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "The question of who holds the platform and whether the person or organisation holding it is trustworthy has serious and profound implications in these volatile times. Once trust is broken, it is extremely difficult to restore. It is necessary to diversify in advance." -- Financial Times --
On 10/25/22 23:54, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <261c8fc4-eb91-ac85-82d6-b91d765d946c@marcchamberlin.com> Date & Time: Tue, 25 Oct 2022 23:22:27 -0700
[MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
[...] MC> > I have a .bash_profile (previously, .bashrc) with MC> > MC> > export DISPLAY="${DISPLAY:-:0}" MC> > MC> > and just set it to ... MC> > MC> > Can I get the same result as this? MC> > MC> > $ env | grep DISPLAY MC> > $ DISPLAY=:0.0 MC> > MC> > where 0.0 is an environment-dependent number. MC> See above for the results for both root and user marc. The only difference I see MC> (don't know if it is important) is that for you DISPLAY is :0.0 whereas DISPLAY MC> for me is simply :0
MC> I also tried changing the name of the .bashrc file, for user marc, to MC> .bash_profile It didn't help or make a difference. Marc...
What does this give you?
$ xauth list|grep `uname -n` nova:/usr/lib64 # xauth list|grep `uname -n` nova/unix:0 MIT-MAGIC-COOKIE-1 754c1c8d9f9695ad5a8c381da997f2d1
And, please show your .bash_profice. OK, I have removed the comments for brevity -
nova:/home/marc # cat .bash_profile export EDITOR=/usr/bin/emacs export DISPLAY="${DISPLAY:-:0}" test -s ~/.alias && . ~/.alias || true HTHs and again thanks for taking the time to help me! Marc...
Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "The question of who holds the platform and whether the person or organisation holding it is trustworthy has serious and profound implications in these volatile times. Once trust is broken, it is extremely difficult to restore. It is necessary to diversify in advance."
-- Financial Times --
-- *"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./)
Hello, In the Message; Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <d98eb0cc-9760-8fd6-d805-d4dec1586f45@marcchamberlin.com> Date & Time: Wed, 26 Oct 2022 09:06:18 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: [...] MN> > What does this give you? MN> > MN> > $ xauth list|grep `uname -n` MC> nova:/usr/lib64 # xauth list|grep `uname -n` MC> nova/unix:0 MIT-MAGIC-COOKIE-1 754c1c8d9f9695ad5a8c381da997f2d1 Please execute as a user. MN> > And, please show your .bash_profice. MC> OK, I have removed the comments for brevity - MC> nova:/home/marc # cat .bash_profile MC> export EDITOR=/usr/bin/emacs MC> export DISPLAY="${DISPLAY:-:0}" MC> test -s ~/.alias && . ~/.alias || true Ah, you're using emacs, not vim. Regards. --- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "In the west, from the time of the Ancient Greeks to the modern day — from Plato in his cave to Aldous Huxley's Brave New World — the idea that reality has value, no matter how ugly or unpleasant it might be, has been accepted as an article of faith." -- J. Kelly "What Meta's VR advert tells us about life in the metaverse" --
On 10/26/22 16:46, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <d98eb0cc-9760-8fd6-d805-d4dec1586f45@marcchamberlin.com> Date & Time: Wed, 26 Oct 2022 09:06:18 -0700
[MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
[...] MN> > What does this give you? MN> > MN> > $ xauth list|grep `uname -n`
MC> nova:/usr/lib64 # xauth list|grep `uname -n` MC> nova/unix:0 MIT-MAGIC-COOKIE-1 754c1c8d9f9695ad5a8c381da997f2d1
Please execute as a user. Executing as a user gave me the same response -
marc@nova:~> xauth list|grep `uname -n` nova/unix:0 MIT-MAGIC-COOKIE-1 754c1c8d9f9695ad5a8c381da997f2d1
MN> > And, please show your .bash_profice.
MC> OK, I have removed the comments for brevity -
MC> nova:/home/marc # cat .bash_profile MC> export EDITOR=/usr/bin/emacs MC> export DISPLAY="${DISPLAY:-:0}" MC> test -s ~/.alias && . ~/.alias || true
Ah, you're using emacs, not vim. Yep, my fingers are emacs trained, have been for over 30 years now! LOL Only wish emacs would add some of the more modern paradigms for editing, such as copy/paste. But I have too many emacs macros, that I have created over the years, for me to give it up.
I am not sure why you pointed this out, why would the editor I use make a difference to why the KDE/Plasma desktop won't start? Thanks again Masaru Nomiya for your help, Marc...
Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "In the west, from the time of the Ancient Greeks to the modern day — from Plato in his cave to Aldous Huxley's Brave New World — the idea that reality has value, no matter how ugly or unpleasant it might be, has been accepted as an article of faith."
-- J. Kelly "What Meta's VR advert tells us about life in the metaverse" --
-- *"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./)
Hello, In the Message; Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <5362a0dc-8f16-6b3f-22f9-be50378de8ef@marcchamberlin.com> Date & Time: Wed, 26 Oct 2022 18:01:12 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: [...] MC>>> nova:/usr/lib64 # xauth list|grep `uname -n` MC>>> nova/unix:0 MIT-MAGIC-COOKIE-1 754c1c8d9f9695ad5a8c381da997f2d1 MN>> Please execute as a user. MN>> Executing as a user gave me the same response - MC> marc@nova:~> xauth list|grep `uname -n` MC> nova/unix:0 MIT-MAGIC-COOKIE-1 754c1c8d9f9695ad5a8c381da997f2d1 It's fine, it's the same. You can see what processes have the DISPLAY variable set by this; $ for file in /proc/[0-9]*; do grep -ao 'DISPLAY=[^[:cntrl:]]*' $file/environ 2>/dev/null && grep -ao '(.*)' $file/stat; done | sed 'N;s/\n/\t/' > DISPLAY.log 2>&1 Please show this DISPLAY.log. [...] MN>> Ah, you're using emacs, not vim. MC> Yep, my fingers are emacs trained, have been for over 30 years now! LOL Only MC> wish emacs would add some of the more modern paradigms for editing, such as MC> copy/paste. But I have too many emacs macros, that I have created over the MC> years, for me to give it up. More than 30 years is a long time. I started with emacs ported to OS/2 (I think it was named mule) . MC> I am not sure why you pointed this out, why would the editor I use make a MC> difference to why the KDE/Plasma desktop won't start? No, I just thought it was rare for people to specify Emacs as the EDITOR environment variable. Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "A bachelor’s degree still holds prestige as a ticket to the middle class, but its value has received increasing scrutiny. In the last several years, rising tuition and student loan debt have led more Americans to reconsider an investment in postsecondary education." -- Washington Post --
On 10/26/22 19:09, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <5362a0dc-8f16-6b3f-22f9-be50378de8ef@marcchamberlin.com> Date & Time: Wed, 26 Oct 2022 18:01:12 -0700
[MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
[...] MC>>> nova:/usr/lib64 # xauth list|grep `uname -n` MC>>> nova/unix:0 MIT-MAGIC-COOKIE-1 754c1c8d9f9695ad5a8c381da997f2d1
MN>> Please execute as a user. MN>> Executing as a user gave me the same response -
MC> marc@nova:~> xauth list|grep `uname -n` MC> nova/unix:0 MIT-MAGIC-COOKIE-1 754c1c8d9f9695ad5a8c381da997f2d1
It's fine, it's the same.
You can see what processes have the DISPLAY variable set by this;
$ for file in /proc/[0-9]*; do grep -ao 'DISPLAY=[^[:cntrl:]]*' $file/environ 2>/dev/null && grep -ao '(.*)' $file/stat; done | sed 'N;s/\n/\t/' > DISPLAY.log 2>&1
Please show this DISPLAY.log.
Wow, impressive incantation! Here you go....
marc@nova:~/tmp> for file in /proc/[0-9]*; do grep -ao 'DISPLAY=[^[:cntrl:]]*' $file/environ 2>/dev/null && grep -ao '(.*)' $file/stat; done | sed 'N;s/\n/\t/' > DISPLAY.log 2>&1 marc@nova:~/tmp> ll total 4 -rw-r--r-- 1 marc users 593 Oct 26 19:22 DISPLAY.log marc@nova:~/tmp> more DISPLAY.log DISPLAY=:0 (sed) DISPLAY=:0 (startplasma-x11) DISPLAY=:0 (dbus-daemon) DISPLAY=:0 (ibus-daemon) DISPLAY=:0 (gvfsd) DISPLAY=:0 (gvfsd-fuse) DISPLAY=:0 (ibus-dconf) DISPLAY=:0 (xmessage) DISPLAY=:0 (ibus-ui-gtk3) DISPLAY=:0 (ibus-extension-) DISPLAY=:0 (ibus-x11) DISPLAY=:0 (ibus-portal) DISPLAY=:0 (at-spi-bus-laun) DISPLAY=:0 (dbus-daemon) DISPLAY=:0 (at-spi2-registr) DISPLAY=:0 (xdg-desktop-por) DISPLAY=:0 (ibus-engine-sim) DISPLAY=:0 (xdg-document-po) DISPLAY=:0 (xdg-permission-) DISPLAY=:0 (dconf-service) DISPLAY=:0 (xdg-desktop-por) DISPLAY=:0 (pipewire) DISPLAY=:0 (pipewire-media-)
[...] MN>> Ah, you're using emacs, not vim.
MC> Yep, my fingers are emacs trained, have been for over 30 years now! LOL Only MC> wish emacs would add some of the more modern paradigms for editing, such as MC> copy/paste. But I have too many emacs macros, that I have created over the MC> years, for me to give it up.
More than 30 years is a long time. I started with emacs ported to OS/2 (I think it was named mule) .
MC> I am not sure why you pointed this out, why would the editor I use make a MC> difference to why the KDE/Plasma desktop won't start?
No, I just thought it was rare for people to specify Emacs as the EDITOR environment variable.
Ha Ha, yes we are a rare breed indeed! I well remember the Emacs v.s. Vi wars! Marc...
Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "A bachelor’s degree still holds prestige as a ticket to the middle class, but its value has received increasing scrutiny. In the last several years, rising tuition and student loan debt have led more Americans to reconsider an investment in postsecondary education."
-- Washington Post --
-- *"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./)
* Masaru Nomiya <nomiya@galaxy.dti.ne.jp> [10-26-22 22:11]:
Hello,
In the Message;
Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <5362a0dc-8f16-6b3f-22f9-be50378de8ef@marcchamberlin.com> Date & Time: Wed, 26 Oct 2022 18:01:12 -0700
[MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
[...] MC>>> nova:/usr/lib64 # xauth list|grep `uname -n` MC>>> nova/unix:0 MIT-MAGIC-COOKIE-1 754c1c8d9f9695ad5a8c381da997f2d1
MN>> Please execute as a user. MN>> Executing as a user gave me the same response -
MC> marc@nova:~> xauth list|grep `uname -n` MC> nova/unix:0 MIT-MAGIC-COOKIE-1 754c1c8d9f9695ad5a8c381da997f2d1
It's fine, it's the same.
You can see what processes have the DISPLAY variable set by this;
$ for file in /proc/[0-9]*; do grep -ao 'DISPLAY=[^[:cntrl:]]*' $file/environ 2>/dev/null && grep -ao '(.*)' $file/stat; done | sed 'N;s/\n/\t/' > DISPLAY.log 2>&1
Please show this DISPLAY.log.
[...] MN>> Ah, you're using emacs, not vim.
MC> Yep, my fingers are emacs trained, have been for over 30 years now! LOL Only MC> wish emacs would add some of the more modern paradigms for editing, such as MC> copy/paste. But I have too many emacs macros, that I have created over the MC> years, for me to give it up.
More than 30 years is a long time. I started with emacs ported to OS/2 (I think it was named mule) .
MC> I am not sure why you pointed this out, why would the editor I use make a MC> difference to why the KDE/Plasma desktop won't start?
No, I just thought it was rare for people to specify Emacs as the EDITOR environment variable.
Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "A bachelor’s degree still holds prestige as a ticket to the middle class, but its value has received increasing scrutiny. In the last several years, rising tuition and student loan debt have led more Americans to reconsider an investment in postsecondary education."
-- Washington Post --
why not just correct the problem identified by Andrei Borzenkov there are two different versions of libreadline installed ??? libreadline4 and libreadline7 according to marc's post on 26 Oct -- (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
On 10/26/22 19:41, Patrick Shanahan wrote:
why not just correct the problem identified by Andrei Borzenkov
there are two different versions of libreadline installed ??? libreadline4 and libreadline7 according to marc's post on 26 Oct
Hi Patrick, thanks for joining the party! And thanks for your thoughts... You raise an interesting question in my mind. I do not see any evidence that both libreadline4 and libreadline7 packages are installed on this system, just libreadline7. That raises the question, why is /usr/lib64/libexec/kf5/start_kdeinit_wrapper raising a fuss about /lib64/libreadline.so.4? That file just doesn't exist. Yast reports that there are packages for libreadline5 and libreadline6 but those packages are not installed. Yast doesn't even give a possibility to install a libreadline4 package. I don't grok what the error message even means, but it seems like a very unusual (and very bad) way to complain about a missing file!! for a quick reference here is what was reported in the xorg-session.log file -
nova:/home/marc/.local/share/sddm # more xorg-session.log /usr/lib64/libexec/kf5/start_kdeinit_wrapper: symbol lookup error: /lib64/libreadline.so.4: undefined symbol: null, version GLIBC_2.2.5
FWIW, start_kdeinit_wrapper is provided in the kinit ver 5.76.0 package. I reinstalled that package just to be certain I have an up to date version actually installed. but still no joy... Marc... -- *"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./)
Hello, In the Message; Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <20221027024122.GP13841@wahoo.no-ip.org> Date & Time: Wed, 26 Oct 2022 22:41:22 -0400 [PS] == Patrick Shanahan <paka@opensuse.org> has written: [...] PS> why not just correct the problem identified by Andrei Borzenkov PS> there are two different versions of libreadline installed ??? PS> libreadline4 and libreadline7 PS> according to marc's post on 26 Oct Different versions of libreadline can essentially co-exist. Also, libreadline does not seem to affect the DISPLAY environment. Of course, if he has libreadlines he doesn't want, he should remove them. Anyway, In the Message; Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <2a0852e4-c8d7-6bbe-53e2-d37d2a6e16de@marcchamberlin.com> Date & Time: Wed, 26 Oct 2022 19:40:39 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: [...] MN> > You can see what processes have the DISPLAY variable set by this; MN> > MN> > $ for file in /proc/[0-9]*; do grep -ao 'DISPLAY=[^[:cntrl:]]*' $file/environ 2>/dev/null && grep -ao '(.*)' $file/stat; done | sed 'N;s/\n/\t/' > DISPLAY.log 2>&1 MN> > MN> > Please show this DISPLAY.log. MC> Wow, impressive incantation! Here you go.... MC> marc@nova:~/tmp> for file in /proc/[0-9]*; do grep -ao 'DISPLAY=[^[:cntrl:]]*' MC> $file/environ 2>/dev/null && grep -ao '(.*)' $file/stat; done | sed MC> 'N;s/\n/\t/' > DISPLAY.log 2>&1 MC> marc@nova:~/tmp> ll MC> total 4 MC> -rw-r--r-- 1 marc users 593 Oct 26 19:22 DISPLAY.log MC> marc@nova:~/tmp> more DISPLAY.log MC> DISPLAY=:0 (sed) MC> DISPLAY=:0 (startplasma-x11) MC> DISPLAY=:0 (dbus-daemon) MC> DISPLAY=:0 (ibus-daemon) MC> DISPLAY=:0 (gvfsd) MC> DISPLAY=:0 (gvfsd-fuse) MC> DISPLAY=:0 (ibus-dconf) MC> DISPLAY=:0 (xmessage) MC> DISPLAY=:0 (ibus-ui-gtk3) MC> DISPLAY=:0 (ibus-extension-) MC> DISPLAY=:0 (ibus-x11) MC> DISPLAY=:0 (ibus-portal) MC> DISPLAY=:0 (at-spi-bus-laun) MC> DISPLAY=:0 (dbus-daemon) MC> DISPLAY=:0 (at-spi2-registr) MC> DISPLAY=:0 (xdg-desktop-por) MC> DISPLAY=:0 (ibus-engine-sim) MC> DISPLAY=:0 (xdg-document-po) MC> DISPLAY=:0 (xdg-permission-) MC> DISPLAY=:0 (dconf-service) MC> DISPLAY=:0 (xdg-desktop-por) MC> DISPLAY=:0 (pipewire) MC> DISPLAY=:0 (pipewire-media-) [...] KDE-related, in your case. That's it; DISPLAY=:0 (startplasma-x11) When I got into plasma5 desktop, I have the followings which are related with plasma5; DISPLAY=:0 (plasma_session) DISPLAY=:0 (start_kdeinit) DISPLAY=:0 (kded5) DISPLAY=:0 (kwin_x11) DISPLAY=:0 (kglobalaccel5) DISPLAY=:0 (ksmserver) DISPLAY=:0 (xsettingsd) DISPLAY=:0 (kscreen_backend) DISPLAY=:0 (kaccess) DISPLAY=:0 (org_kde_powerde) DISPLAY=:0 (plasmashell) DISPLAY=:0 (kalendarac) DISPLAY=:0 (kactivitymanage) DISPLAY=:0 (akonadi_control) DISPLAY=:0 (kmail) DISPLAY=:0 (akonadiserver) DISPLAY=:0 (akonadi_akonote) DISPLAY=:0 (akonadi_archive) DISPLAY=:0 (akonadi_birthda) DISPLAY=:0 (akonadi_contact) DISPLAY=:0 (akonadi_followu) DISPLAY=:0 (akonadi_ical_re) DISPLAY=:0 (akonadi_indexin) DISPLAY=:0 (akonadi_maildir) DISPLAY=:0 (akonadi_maildis) DISPLAY=:0 (akonadi_mailfil) DISPLAY=:0 (akonadi_mailmer) DISPLAY=:0 (akonadi_migrati) DISPLAY=:0 (akonadi_newmail) DISPLAY=:0 (akonadi_sendlat) DISPLAY=:0 (akonadi_unified) DISPLAY=:0 (kioslave5) DISPLAY=:0 (kioslave5) How about this way? As an user, 1. $ DISPLAY="${DISPLAY:-:0}"; export DISPLAY 2. $ xauth add $DISPLAY . hexkey Then, 3. echo $DISPLAY Regards. --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ " Today’s China is not the old China humiliated and bullied over 100 years ago. It is time for these people to wake up from their imperial dream." -- Hua Chunying’s Regular Press Conference on August 4, 2022 --
On 10/26/22 21:58, Masaru Nomiya wrote:
Hello,
In the Message;
Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <20221027024122.GP13841@wahoo.no-ip.org> Date & Time: Wed, 26 Oct 2022 22:41:22 -0400
[PS] == Patrick Shanahan <paka@opensuse.org> has written:
[...] PS> why not just correct the problem identified by Andrei Borzenkov
PS> there are two different versions of libreadline installed ??? PS> libreadline4 and libreadline7 PS> according to marc's post on 26 Oct
Different versions of libreadline can essentially co-exist. Also, libreadline does not seem to affect the DISPLAY environment.
Of course, if he has libreadlines he doesn't want, he should remove them.
Anyway,
In the Message;
Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <2a0852e4-c8d7-6bbe-53e2-d37d2a6e16de@marcchamberlin.com> Date & Time: Wed, 26 Oct 2022 19:40:39 -0700
[MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
[...] MN> > You can see what processes have the DISPLAY variable set by this; MN> > MN> > $ for file in /proc/[0-9]*; do grep -ao 'DISPLAY=[^[:cntrl:]]*' $file/environ 2>/dev/null && grep -ao '(.*)' $file/stat; done | sed 'N;s/\n/\t/' > DISPLAY.log 2>&1 MN> > MN> > Please show this DISPLAY.log.
MC> Wow, impressive incantation! Here you go....
MC> marc@nova:~/tmp> for file in /proc/[0-9]*; do grep -ao 'DISPLAY=[^[:cntrl:]]*' MC> $file/environ 2>/dev/null && grep -ao '(.*)' $file/stat; done | sed MC> 'N;s/\n/\t/' > DISPLAY.log 2>&1 MC> marc@nova:~/tmp> ll MC> total 4 MC> -rw-r--r-- 1 marc users 593 Oct 26 19:22 DISPLAY.log MC> marc@nova:~/tmp> more DISPLAY.log MC> DISPLAY=:0 (sed) MC> DISPLAY=:0 (startplasma-x11) MC> DISPLAY=:0 (dbus-daemon) MC> DISPLAY=:0 (ibus-daemon) MC> DISPLAY=:0 (gvfsd) MC> DISPLAY=:0 (gvfsd-fuse) MC> DISPLAY=:0 (ibus-dconf) MC> DISPLAY=:0 (xmessage) MC> DISPLAY=:0 (ibus-ui-gtk3) MC> DISPLAY=:0 (ibus-extension-) MC> DISPLAY=:0 (ibus-x11) MC> DISPLAY=:0 (ibus-portal) MC> DISPLAY=:0 (at-spi-bus-laun) MC> DISPLAY=:0 (dbus-daemon) MC> DISPLAY=:0 (at-spi2-registr) MC> DISPLAY=:0 (xdg-desktop-por) MC> DISPLAY=:0 (ibus-engine-sim) MC> DISPLAY=:0 (xdg-document-po) MC> DISPLAY=:0 (xdg-permission-) MC> DISPLAY=:0 (dconf-service) MC> DISPLAY=:0 (xdg-desktop-por) MC> DISPLAY=:0 (pipewire) MC> DISPLAY=:0 (pipewire-media-) [...]
KDE-related, in your case. That's it;
DISPLAY=:0 (startplasma-x11)
When I got into plasma5 desktop, I have the followings which are related with plasma5;
DISPLAY=:0 (plasma_session) DISPLAY=:0 (start_kdeinit) DISPLAY=:0 (kded5) DISPLAY=:0 (kwin_x11) DISPLAY=:0 (kglobalaccel5) DISPLAY=:0 (ksmserver) DISPLAY=:0 (xsettingsd) DISPLAY=:0 (kscreen_backend) DISPLAY=:0 (kaccess) DISPLAY=:0 (org_kde_powerde) DISPLAY=:0 (plasmashell) DISPLAY=:0 (kalendarac) DISPLAY=:0 (kactivitymanage) DISPLAY=:0 (akonadi_control) DISPLAY=:0 (kmail) DISPLAY=:0 (akonadiserver) DISPLAY=:0 (akonadi_akonote) DISPLAY=:0 (akonadi_archive) DISPLAY=:0 (akonadi_birthda) DISPLAY=:0 (akonadi_contact) DISPLAY=:0 (akonadi_followu) DISPLAY=:0 (akonadi_ical_re) DISPLAY=:0 (akonadi_indexin) DISPLAY=:0 (akonadi_maildir) DISPLAY=:0 (akonadi_maildis) DISPLAY=:0 (akonadi_mailfil) DISPLAY=:0 (akonadi_mailmer) DISPLAY=:0 (akonadi_migrati) DISPLAY=:0 (akonadi_newmail) DISPLAY=:0 (akonadi_sendlat) DISPLAY=:0 (akonadi_unified) DISPLAY=:0 (kioslave5) DISPLAY=:0 (kioslave5)
How about this way?
As an user,
1. $ DISPLAY="${DISPLAY:-:0}"; export DISPLAY
2. $ xauth add $DISPLAY . hexkey
Then,
3. echo $DISPLAY
OK, and here is what I saw -
marc@nova:~> DISPLAY="${DISPLAY:-:0}"; export DISPLAY marc@nova:~> xauth add $DISPLAY . hexkey xauth: (argv):1: key contains odd number of or non-hex characters marc@nova:~> echo $DISPLAY :0 HTHs Thank you again for your assistance! Marc...
Regards.
--- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ " Today’s China is not the old China humiliated and bullied over 100 years ago. It is time for these people to wake up from their imperial dream."
-- Hua Chunying’s Regular Press Conference on August 4, 2022 --
-- *"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./)
Hello, In the Message; Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <efdebcc9-11e6-6fea-d796-1771f6ffc9d0@marcchamberlin.com> Date & Time: Wed, 26 Oct 2022 22:24:41 -0700 [MC] == Marc Chamberlin <marc@marcchamberlin.com> has written: [...] MC> OK, and here is what I saw - MC> marc@nova:~> DISPLAY="${DISPLAY:-:0}"; export DISPLAY MC> marc@nova:~> xauth add $DISPLAY . hexkey MC> xauth: (argv):1: key contains odd number of or non-hex characters MC> marc@nova:~> echo $DISPLAY MC> :0 This is how you can log in to plasma5? --- ┏━━┓彡 野宮 賢 mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "The question of who holds the platform and whether the person or organisation holding it is trustworthy has serious and profound implications in these volatile times. Once trust is broken, it is extremely difficult to restore. It is necessary to diversify in advance." -- Financial Times --
Hello,
In the Message;
Subject : Re: startkde: Could not start kdeinit5. Check your installation. Message-ID : <57f9c7f7-cb29-8902-46da-7c58fc624bfe@marcchamberlin.com> Date & Time: Tue, 25 Oct 2022 15:55:00 -0700
[MC] == Marc Chamberlin <marc@marcchamberlin.com> has written:
[...] MC> > nova:/home/marc # kdeinit5 > kde.log 2>&1 MC> > nova:/home/marc # more kde.log MC> > kdeinit5: Aborting. $DISPLAY is not set. [...]
Ah, I see.
Please write this in your .bashrc;
export DISPLAY="${DISPLAY:-:0}"
Then, you can log in KDE5. Hi again Masaru Nomiya, I added the export line to my own user's .bashrc file (not to root's or any other account's home dir) but it didn't make any difference! Sure seemed like a good idea though, again
On 10/25/22 16:10, Masaru Nomiya wrote: thanks! Marc....
Regards.
--- ┏━━┓彡 Masaru Nomiya mail-to: nomiya @ galaxy.dti.ne.jp ┃＼／彡 ┗━━┛ "A society bound by e-mail and mobile phones deprives us of the freedom to face ourselves and indulge our fantasies."
-- Michael Crichton (Speech in Japan) --
-- *"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./)
On Tuesday 25 October 2022, Marc Chamberlin wrote:
Hello - I have a recalcitrant computer running OpenSuSE 15.3 that is refusing to start the KDE/Plasma desktop. After login I get a dialog box saying "startkde: Could not start kdeinit5. Check your installation." Despite the fact that the KDE/Plasma desktop won't start, I can SSH into the system and everything else (processes, services) I want running do start up OK. In the file /var/log/warn I do see a couple of messages that are of concern, one in particular - ...
The cause might be a broken config file for this particular user. Have you tried logging in as a different user or tried a freshly created user? If either of those suggestions work, it still might prove difficult to track down which file is broken, but perhaps take a closer look at any that have changed recently, for example: % find ~/.config ~/.local -newer a-file-that-predates-the-problem To find a file that predates the problem, you could use ls on the users home directory: % ls -lart It's possible some cluses may be logged to the journal, % journalctl --boot might help. I'm not sure if leap still logs to xorg-session, but it might we worth looking in the user's .local/share/sddm/xorg-session.log Often there is too much info in these files, but you never know. Hope this helps. Michael
On Tuesday 25 October 2022, Marc Chamberlin wrote:
Hello - I have a recalcitrant computer running OpenSuSE 15.3 that is refusing to start the KDE/Plasma desktop. After login I get a dialog box saying "startkde: Could not start kdeinit5. Check your installation." Despite the fact that the KDE/Plasma desktop won't start, I can SSH into the system and everything else (processes, services) I want running do start up OK. In the file /var/log/warn I do see a couple of messages that are of concern, one in particular - ... The cause might be a broken config file for this particular user. Have you tried logging in as a different user or tried a freshly created user? Hi Michael, and thanks for your thoughts. Yes I have tried creating a new user and logging in but no joy. I have also switch display managers but again to no joy.
If either of those suggestions work, it still might prove difficult to track down which file is broken, but perhaps take a closer look at any that have changed recently, for example:
% find ~/.config ~/.local -newer a-file-that-predates-the-problem
To find a file that predates the problem, you could use ls on the users home directory:
% ls -lart Since the same problem occurred with a new user and a new home
On 10/24/22 23:39, Michael Hamilton wrote: directory, I didn't pursue this route too far. I renamed my own .config and .local files then tried again. Didn't bring any joy either, same problem, KDE and Plasma won't start.
It's possible some cluses may be logged to the journal,
% journalctl --boot
Most of what I saw in the output looks OK to my untrained eyes, most looks like instrumentation statements, showing the progress of the start up period. Above my pay grade to grok it! But there were some statements that caught my eye and look suspicious. These are copy/pastes from the relevant sections of the journalctl command (nor do I grok any of this) -
Oct 25 12:26:35 nova systemd[1]: Found device WDC_WD7500AAKS-00RBA0 5. Oct 25 12:26:35 nova systemd[1]: Starting Resume from hibernation using device /dev/disk/by-uuid/e43a583a-8dbe-4643-a8aa-f3747e066d70... Oct 25 12:26:35 nova systemd-hibernate-resume[342]: Could not resume from '/dev/disk/by-uuid/e43a583a-8dbe-4643-a8aa-f3747e066d70' (8:5). Oct 25 12:26:35 nova systemd[1]: systemd-hibernate-resume@dev-disk-by\x2duuid-e43a583a\x2d8dbe\x2d4643\x2da8aa\x2df3747e066d70.service: Succeeded. Oct 25 12:26:35 nova systemd[1]: Finished Resume from hibernation using device /dev/disk/by-uuid/e43a583a-8dbe-4643-a8aa-f3747e066d70. Oct 25 12:26:35 nova systemd[1]: Reached target Local File Systems (Pre). Oct 25 12:26:35 nova systemd[1]: Reached target Local File Systems. Oct 25 12:26:35 nova systemd[1]: Starting Create Volatile Files and Directories... Oct 25 12:26:35 nova kernel: PM: Image not found (code -22) Oct 25 12:26:35 nova systemd[1]: Finished Create Volatile Files and Directories.
Oct 25 19:26:43 nova kernel: ACPI Warning: SystemIO range 0x0000000000001828-0x000000000000182F conflicts with OpRegion 0x0000000000001800-0x000000000000187F (\ PMIO) (20200925/utaddress-213) Oct 25 19:26:43 nova kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver Oct 25 19:26:43 nova kernel: ACPI Warning: SystemIO range 0x0000000000001C40-0x0000000000001C4F conflicts with OpRegion 0x0000000000001C00-0x0000000000001FFF (\ GPR) (20200925/utaddress-213) Oct 25 19:26:43 nova kernel: ACPI: If an ACPI driver is available for this device, you should use it instead of the native driver
Oct 25 19:26:43 nova udevadm[455]: systemd-udev-settle.service is deprecated. Please fix wickedd.service not to pull it in.
Oct 25 19:26:50 nova systemd[1]: Started Modem Manager. Oct 25 19:26:50 nova kernel: Generic FE-GE Realtek PHY r8169-700:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-700:00, irq=IGNORE) Oct 25 19:26:50 nova kernel: r8169 0000:07:00.0 eth1: Link is Down Oct 25 19:26:51 nova kernel: Generic FE-GE Realtek PHY r8169-800:00: attached PHY driver [Generic FE-GE Realtek PHY] (mii_bus:phy_addr=r8169-800:00, irq=IGNORE) Oct 25 19:26:51 nova kernel: r8169 0000:08:00.0 eth0: Link is Down Oct 25 19:26:51 nova avahi-daemon[1104]: Files changed, reloading. Oct 25 19:26:51 nova nscd[1152]: 1152 ignored inotify event for `/etc/resolv.conf` (file exists) Oct 25 19:26:51 nova nscd[1152]: 1152 ignored inotify event for `/etc/resolv.conf` (file exists) Oct 25 19:26:51 nova avahi-daemon[1104]: No service file found in /etc/avahi/services. Oct 25 19:26:53 nova ModemManager[1226]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:19.0': not supported by any plugin Oct 25 19:26:53 nova ModemManager[1226]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.4/0000:04:00.0': not supported by any plu gin Oct 25 19:26:53 nova ModemManager[1226]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/0000:06:03.0/0000:07:00.0' : not supported by any plugin Oct 25 19:26:53 nova ModemManager[1226]: <info> Couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.5/0000:05:00.0/0000:06:07.0/0000:08:00.0' : not supported by any plugin
Oct 25 19:27:16 nova plymouth[2367]: error: unexpectedly disconnected from boot status daemon
I have already started another thread asking about these messages that refer to flatpak. I have no idea how serious these are....
Oct 25 19:27:25 nova systemd[2465]: pam_unix(systemd-user:session): session opened for user newmarc by (uid=0) Oct 25 19:27:26 nova systemd[2465]: Failed to open "/var/lib/flatpak/exports/share/systemd/user", ignoring: Permission denied
Oct 25 19:27:27 nova dbus-daemon[2481]: Cannot setup inotify for '/var/lib/flatpak/exports/share/dbus-1/services'; error 'Permission denied' Oct 25 19:27:33 nova ksplashqml[2545]: QCoreApplication::arguments: Please instantiate the QApplication object first Oct 25 19:27:33 nova startplasma-x11[2473]: "/usr/lib64/libexec/kf5/start_kdeinit_wrapper" ("--kded", "+kcminit_startup") exited with code 127
There are lots of these "flatpak" error messages that refer to this particular file. It is the exports directory that is missing causing all these "flatpak" errors.
Oct 25 19:27:38 nova at-spi-bus-laun[2744]: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission denied
might help. I'm not sure if leap still logs to xorg-session, but it might w
e worth looking in the user's .local/share/sddm/xorg-session.log Often there is too much info in these files, but you never know. I only found this one (rather unhelpful, Google didn't find anything relevant either) line in the xorg-session.log file - nova:/home/marc/.local/share/sddm # more xorg-session.log /usr/lib64/libexec/kf5/start_kdeinit_wrapper: symbol lookup error: /lib64/libreadline.so.4: undefined symbol: null, version GLIBC_2.2.5
Hope this helps.
Me too! Thanks for your help and thoughts.... Marc....
Michael
-- *"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./)
On Wednesday 26 October 2022, Marc Chamberlin wrote:
On 10/24/22 23:39, Michael Hamilton wrote: ... might help. I'm not sure if leap still logs to xorg-session, but it might worth looking in the user's .local/share/sddm/xorg-session.log Often there is too much info in these files, but you never know. I only found this one (rather unhelpful, Google didn't find anything relevant either) line in the xorg-session.log file - nova:/home/marc/.local/share/sddm # more xorg-session.log /usr/lib64/libexec/kf5/start_kdeinit_wrapper: symbol lookup error: /lib64/libreadline.so.4: undefined symbol: null, version GLIBC_2.2.5
This looks interesting. On a normally linked executable, a missing symbol would cause the executable to fail to start. Missing symbol null is a bit weird though - I'd expect a proper symbol name. It could be that the glibc in in the load library path and start_kdeinit_wrapper are mismatched. I'm getting out of my depth in respect to Leap and modern Linux/glibc practice, perhaps someone with more of clue might comment. It may be that if more than one glibc is present, the right one might be able to be selected by setting the LD_LIBRARY_PATH. Michael
On Wed, Oct 26, 2022 at 7:38 AM Marc Chamberlin <marc@marcchamberlin.com> wrote: ...
I only found this one (rather unhelpful, Google didn't find anything relevant either) line in the xorg-session.log file -
nova:/home/marc/.local/share/sddm # more xorg-session.log /usr/lib64/libexec/kf5/start_kdeinit_wrapper: symbol lookup error: /lib64/libreadline.so.4: undefined symbol: null, version GLIBC_2.2.5
So this is the real reason. Show output of ls -l /lib64/libreadline* ls -l /usr/lib64/libreadline* rpm -qf /lib64/libreadline.so.4
On 10/25/22 23:46, Andrei Borzenkov wrote:
On Wed, Oct 26, 2022 at 7:38 AM Marc Chamberlin <marc@marcchamberlin.com> wrote: ...
I only found this one (rather unhelpful, Google didn't find anything relevant either) line in the xorg-session.log file -
nova:/home/marc/.local/share/sddm # more xorg-session.log /usr/lib64/libexec/kf5/start_kdeinit_wrapper: symbol lookup error: /lib64/libreadline.so.4: undefined symbol: null, version GLIBC_2.2.5 So this is the real reason. Show output of
ls -l /lib64/libreadline* nova:/home/marc # ls -l /lib64/libreadline* lrwxrwxrwx 1 root root 18 Aug 6 2021 /lib64/libreadline.so.7 -> libreadline.so.7.0 -rwxr-xr-x 1 root root 317432 Aug 6 2021 /lib64/libreadline.so.7.0
ls -l /usr/lib64/libreadline* nova:/home/marc # ls -l /usr/lib64/libreadline* ls: cannot access '/usr/lib64/libreadline*': No such file or directory Hmm, that looks suspicious?
rpm -qf /lib64/libreadline.so.4 nova:/home/marc # rpm -qf /lib64/libreadline.so.4 file /lib64/libreadline.so.4 is not owned by any package
Thanks for your assistance Andrei, not sure if these are the results you were expecting to see! Marc... -- *"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./)
On 10/26/22 10:44, Marc Chamberlin wrote:
rpm -qf /lib64/libreadline.so.4 nova:/home/marc # rpm -qf /lib64/libreadline.so.4 file /lib64/libreadline.so.4 is not owned by any package
Thanks for your assistance Andrei, not sure if these are the results you were expecting to see! Marc...
What that means is that you have a stray /lib64/libreadline.so.4 file on your system that isn't owned by any rpm known in the rpm database. I'd do a quick: $ mkdir -p $HOME/tmp $ sudo mv /lib64/libreadline.so.4 /home/marc/tmp $ sudo systemctl reboot If for some reason the graphics setup is searching /lib64 and picking up libreadline.so.4 instead of libreadline.so.7 and is looking for a symbol that doesn't exist in libreadline.so.4, I could see that screwing things up. The question is where in the heck did the stray libreadline.so.4 come from and why didn't it bite you before now? -- David C. Rankin, J.D.,P.E.
On 10/26/22 22:18, David C. Rankin wrote:
On 10/26/22 10:44, Marc Chamberlin wrote:
rpm -qf /lib64/libreadline.so.4 nova:/home/marc # rpm -qf /lib64/libreadline.so.4 file /lib64/libreadline.so.4 is not owned by any package
Thanks for your assistance Andrei, not sure if these are the results you were expecting to see! Marc...
What that means is that you have a stray /lib64/libreadline.so.4 file on your system that isn't owned by any rpm known in the rpm database.
I'd do a quick:
$ mkdir -p $HOME/tmp $ sudo mv /lib64/libreadline.so.4 /home/marc/tmp $ sudo systemctl reboot
If for some reason the graphics setup is searching /lib64 and picking up libreadline.so.4 instead of libreadline.so.7 and is looking for a symbol that doesn't exist in libreadline.so.4, I could see that screwing things up. Well well well! That seems to have fixed it! The KDE/Plasma desktop came up! What has me perplexed is that I had specifically done a cd /lib64 and then did an ls libreadline* and I only saw libreadline.so.7! There was no libreadline.so.4 in that directory. Interesting, and I have no explanation..
The question is where in the heck did the stray libreadline.so.4 come from and why didn't it bite you before now? Got me beat also! I keep some partitions like /home and /srv when I upgrade from one release to the next, but I don't keep or do anything special with /lib64 and it is not in it's own partition either. Here is a copy of what happened as I followed your instructions and my own small bit of investigation. I don't grok this and was a bit surprised -
marc@nova:~> mkdir -p $HOME/tmp marc@nova:~> sudo mv /lib64/libreadline.so.4 /home/marc/tmp [sudo] password for root: marc@nova:~> ls tmp ERROR: ld.so: object '/lib64/libreadline.so.4' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. libreadline.so.4 marc@nova:~> sudo systemctl reboot ERROR: ld.so: object '/lib64/libreadline.so.4' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object '/lib64/libreadline.so.4' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. marc@nova:~> Connection to nova.marcchamberlin.com closed by remote host. Connection to nova.marcchamberlin.com closed.
However something is still amiss, while the desktop did come up OK, every Konsole window starts up with this message repeated 3 times -
ERROR: ld.so: object '/lib64/libreadline.so.4' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
HTHs and thanks David for your assistance! Marc -- *"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./)
On Thu, Oct 27, 2022 at 9:12 AM Marc Chamberlin <marc@marcchamberlin.com> wrote:
However something is still amiss, while the desktop did come up OK, every Konsole window starts up with this message repeated 3 times -
ERROR: ld.so: object '/lib64/libreadline.so.4' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
Show full content of /etc/ld.so.preload
On 10/26/22 23:27, Andrei Borzenkov wrote:
On Thu, Oct 27, 2022 at 9:12 AM Marc Chamberlin <marc@marcchamberlin.com> wrote:
However something is still amiss, while the desktop did come up OK, every Konsole window starts up with this message repeated 3 times -
ERROR: ld.so: object '/lib64/libreadline.so.4' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. Show full content of /etc/ld.so.preload Hi Andrei - Well I will do the best I can but first I regret to say my SuSE15.3 system will not boot up at all. Fortunately I still have a SuSE15.1 system on this computer that does boot up fine. So I can boot it up and then look at files in the partition that contains SuSE15.3. Here is what I found -
nova:/etc # cd /SuSE15.3/etc/ld.so.conf.d/ nova:/SuSE15.3/etc/ld.so.conf.d # ls graphviz.conf nova:/SuSE15.3/etc/ld.so.conf.d # more graphviz.conf /usr/lib64/graphviz /usr/lib64/graphviz/sharp /usr/lib64/graphviz/java /usr/lib64/graphviz/perl /usr/lib64/graphviz/php /usr/lib64/graphviz/ocaml /usr/lib64/graphviz/python /usr/lib64/graphviz/lua /usr/lib64/graphviz/tcl /usr/lib64/graphviz/guile /usr/lib64/graphviz/ruby
As for my current status, David Rankin send me instructions to do -
$ sudo ldconfig
but I think I got that too late. While I had 15.3 up and running it notified me that I had some updates to install. So I thought why not and went ahead and let my system update. One of the updates was for the kernel and that requires a reboot. So I rebooted and now my system is seriously hung up. I get as far as selecting which OS I want to bring up, and if I select 15.3, the computer almost instantly hangs and freezes. I cannot even get the escape key to bring down the SuSE logo and show the progress as the various startup scripts and other things run. Nor does the file /var/log/boot.log contain any info, nothing was written to it. So I almost had 15.3 running but then things went sideways. I then had an idea to try, and that was to copy libreadline.so.4 back to /lib64 and try booting up with the intention that if I could again get the 15.3 system up and running (without the KDE/Plasma desktop) I could then SSH in to the system and run the ldconfig script that David Rankin told me to do. But still no joy, the system still hangs/freezes right after I select the 15.3 system to start up. So this is where things now stand. I will try, not very hopeful, to remove the libreadline.so.4 file from /lib64 again to see if that makes any difference. If so, will get back to you with the results... As always, thanks for your thoughts! Marc... -- *"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./)
On 10/28/22 00:22, Marc Chamberlin wrote:
I then had an idea to try, and that was to copy
libreadline.so.4
back to /lib64 and try booting up with the intention that if I could again get the 15.3 system up and running (without the KDE/Plasma desktop) I could then SSH in to the system and run the ldconfig script that David Rankin told me to do. But still no joy, the system still hangs/freezes right after I select the 15.3 system to start up. So this is where things now stand.
I will try, not very hopeful, to remove the libreadline.so.4 file from /lib64 again to see if that makes any difference. If so, will get back to you with the results...
As always, thanks for your thoughts! Marc...
Can you boot 15.1 and mount your 15.3 root under /mnt (or a subdirectory) and check the /lib/modules with ls -al to see what kernel(s) you have installed? Unless you disabled the multiversion setting for zypper, you should still have your last kernel installed. You can likely rebuild the startup files (initrd) though somebody else will have to chime in with the exact command for 15.3 (I'm pretty sure it used dracut also) With the luck you have had lately, don't go gambling.... -- David C. Rankin, J.D.,P.E.
On 10/27/22 23:53, David C. Rankin wrote:
On 10/28/22 00:22, Marc Chamberlin wrote:
I then had an idea to try, and that was to copy
libreadline.so.4
back to /lib64 and try booting up with the intention that if I could again get the 15.3 system up and running (without the KDE/Plasma desktop) I could then SSH in to the system and run the ldconfig script that David Rankin told me to do. But still no joy, the system still hangs/freezes right after I select the 15.3 system to start up. So this is where things now stand.
I will try, not very hopeful, to remove the libreadline.so.4 file from /lib64 again to see if that makes any difference. If so, will get back to you with the results...
As always, thanks for your thoughts! Marc...
Can you boot 15.1 and mount your 15.3 root under /mnt (or a subdirectory) and check the /lib/modules with ls -al to see what kernel(s) you have installed? Unless you disabled the multiversion setting for zypper, you should still have your last kernel installed. HA! Yes I was ahead of you on mounting 15.3, in my 15.1 world I have it mounted at /SuSE15.3. Here is what ls -al shows -
nova:~ # cd /SuSE15.3/lib/modules/ nova:/SuSE15.3/lib/modules # ls -al total 20 drwxr-xr-x 5 root root 4096 Oct 26 23:15 . drwxr-xr-x 8 root root 4096 Sep 15 20:11 .. drwxr-xr-x 4 root root 4096 Jun 23 17:48 5.3.18-150300.59.71-default drwxr-xr-x 4 root root 4096 Oct 23 18:29 5.3.18-150300.59.93-default drwxr-xr-x 4 root root 4096 Oct 26 23:16 5.3.18-150300.59.98-default
You can likely rebuild the startup files (initrd) though somebody else will have to chime in with the exact command for 15.3 (I'm pretty sure it used dracut also)
OK, any somebodies else around?
With the luck you have had lately, don't go gambling....
I agree! Won't do anything until I am told to do anything! Thanks again David... Marc... -- *"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./)
On 10/28/22 12:56, Marc Chamberlin wrote:
HA! Yes I was ahead of you on mounting 15.3, in my 15.1 world I have it mounted at /SuSE15.3. Here is what ls -al shows -
nova:~ # cd /SuSE15.3/lib/modules/ nova:/SuSE15.3/lib/modules # ls -al total 20 drwxr-xr-x 5 root root 4096 Oct 26 23:15 . drwxr-xr-x 8 root root 4096 Sep 15 20:11 .. drwxr-xr-x 4 root root 4096 Jun 23 17:48 5.3.18-150300.59.71-default drwxr-xr-x 4 root root 4096 Oct 23 18:29 5.3.18-150300.59.93-default drwxr-xr-x 4 root root 4096 Oct 26 23:16 5.3.18-150300.59.98-default
The good news is you have your updated kernel and the last two kernels you ran still installed. I'd see if Andrei has any additional advise on the ld.so.preload state. My guess is that you need to remove (comment out) /lib64/libreadline.so.4 in /etc/ld.so.preload to prevent it from being loaded globally. Likely cures the boot problem too. You can always give it a go, and if no luck, simply uncomment. -- David C. Rankin, J.D.,P.E.
Marc Chamberlin composed on 2022-10-28 10:56 (UTC-0700):
OK, any somebodies else around?
I searched for existence of /etc/ld.so.preload on Leap installations of versions 11.4, 12.1, 12.2, 12.3, 13.1, 13.2, 15.0, 15.1, 15.2, 15.3, 15.4, 15.5, plus TW and found it nowhere. Odds are pretty good it's not needed on most installations, and may be the cause of your trouble regardless which libreadline version it points to. -- 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 Fri, Oct 28, 2022 at 8:22 AM Marc Chamberlin <marc@marcchamberlin.com> wrote: ...
Show full content of /etc/ld.so.preload ... Here is what I found -
nova:/etc # cd /SuSE15.3/etc/ld.so.conf.d/ nova:/SuSE15.3/etc/ld.so.conf.d # ls graphviz.conf nova:/SuSE15.3/etc/ld.so.conf.d # more graphviz.conf /usr/lib64/graphviz /usr/lib64/graphviz/sharp /usr/lib64/graphviz/java /usr/lib64/graphviz/perl /usr/lib64/graphviz/php /usr/lib64/graphviz/ocaml /usr/lib64/graphviz/python /usr/lib64/graphviz/lua /usr/lib64/graphviz/tcl /usr/lib64/graphviz/guile /usr/lib64/graphviz/ruby
That is not what I requested. Preloading a library is a very exceptional use case and preloading a library globally needs a very good reason. And libreadline is not something that makes sense to preload in any case. I wonder if you have something like rootkit (which would also explain the "missing" file in ls output).
As for my current status, David Rankin send me instructions to do -
$ sudo ldconfig
It is not related to /etc/ld.so.preload at all.
On 10/28/22 01:59, Andrei Borzenkov wrote:
Show full content of /etc/ld.so.preload ... Here is what I found -
nova:/etc # cd /SuSE15.3/etc/ld.so.conf.d/ nova:/SuSE15.3/etc/ld.so.conf.d # ls graphviz.conf nova:/SuSE15.3/etc/ld.so.conf.d # more graphviz.conf /usr/lib64/graphviz /usr/lib64/graphviz/sharp /usr/lib64/graphviz/java /usr/lib64/graphviz/perl /usr/lib64/graphviz/php /usr/lib64/graphviz/ocaml /usr/lib64/graphviz/python /usr/lib64/graphviz/lua /usr/lib64/graphviz/tcl /usr/lib64/graphviz/guile /usr/lib64/graphviz/ruby That is not what I requested. Preloading a library is a very exceptional use case and preloading a library globally needs a very good reason. And libreadline is not something that makes sense to
On Fri, Oct 28, 2022 at 8:22 AM Marc Chamberlin <marc@marcchamberlin.com> wrote: ... preload in any case. I wonder if you have something like rootkit (which would also explain the "missing" file in ls output).
OH!! My bad! Dunno my brain must have slipped a cog somewhere! Anywise here is the output you requested, I think it is very interesting but dunno how it got set this way -
nova:/SuSE15.3/etc # cat ld.so.preload /lib64/libreadline.so.4
As for my current status, David Rankin send me instructions to do -
$ sudo ldconfig It is not related to /etc/ld.so.preload at all.
OK, thanks again for being patient with me and helping me get out of these weeds! Marc.... -- *"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./)
On 10/27/22 01:12, Marc Chamberlin wrote:
However something is still amiss, while the desktop did come up OK, every Konsole window starts up with this message repeated 3 times -
ERROR: ld.so: object '/lib64/libreadline.so.4' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
Sorry Marc, You get two copies, I forgot to send to the list. You need to run ldconfig to update the shared library cache. So, $ sudo ldconfig $ sudo systemctl reboot Should get rid of the /lib64/libreadline.so.4 entry. -- David C. Rankin, J.D.,P.E.
On Wed, 26 Oct 2022 23:12:12 -0700, Marc Chamberlin <marc@marcchamberlin.com> wrote:
On 10/26/22 22:18, David C. Rankin wrote:
On 10/26/22 10:44, Marc Chamberlin wrote:
rpm -qf /lib64/libreadline.so.4 nova:/home/marc # rpm -qf /lib64/libreadline.so.4 file /lib64/libreadline.so.4 is not owned by any package
Thanks for your assistance Andrei, not sure if these are the results you were expecting to see! Marc...
What that means is that you have a stray /lib64/libreadline.so.4 file on your system that isn't owned by any rpm known in the rpm database.
I'd do a quick:
$ mkdir -p $HOME/tmp $ sudo mv /lib64/libreadline.so.4 /home/marc/tmp $ sudo systemctl reboot
If for some reason the graphics setup is searching /lib64 and picking up libreadline.so.4 instead of libreadline.so.7 and is looking for a symbol that doesn't exist in libreadline.so.4, I could see that screwing things up. Well well well! That seems to have fixed it! The KDE/Plasma desktop came up! What has me perplexed is that I had specifically done a cd /lib64 and then did an ls libreadline* and I only saw libreadline.so.7! There was no libreadline.so.4 in that directory. Interesting, and I have no explanation..
The question is where in the heck did the stray libreadline.so.4 come from and why didn't it bite you before now? Got me beat also! I keep some partitions like /home and /srv when I upgrade from one release to the next, but I don't keep or do anything special with /lib64 and it is not in it's own partition either. Here is a copy of what happened as I followed your instructions and my own small bit of investigation. I don't grok this and was a bit surprised -
marc@nova:~> mkdir -p $HOME/tmp marc@nova:~> sudo mv /lib64/libreadline.so.4 /home/marc/tmp [sudo] password for root: marc@nova:~> ls tmp ERROR: ld.so: object '/lib64/libreadline.so.4' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. libreadline.so.4 marc@nova:~> sudo systemctl reboot ERROR: ld.so: object '/lib64/libreadline.so.4' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. ERROR: ld.so: object '/lib64/libreadline.so.4' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored. marc@nova:~> Connection to nova.marcchamberlin.com closed by remote host. Connection to nova.marcchamberlin.com closed.
However something is still amiss, while the desktop did come up OK, every Konsole window starts up with this message repeated 3 times -
ERROR: ld.so: object '/lib64/libreadline.so.4' from /etc/ld.so.preload cannot be preloaded (cannot open shared object file): ignored.
Since it didn't appear to be there in the first place, I would be tempted to move libreadline.so.4 "back" to /lib64 and see what happens, if you haven't changed anything else in the meantime. -- Robert Webb
On 10/27/22 14:54, Robert Webb wrote:
Since it didn't appear to be there in the first place, I would be tempted to move libreadline.so.4 "back" to /lib64 and see what happens, if you haven't changed anything else in the meantime.
That'd be "tap dancing on land mines". If some yast process or otherwise triggered ldconfig again, you would be back in the same boat. Bottom line, since libreadline.so.4 did not belong to any rpm on the system -- it should not be there. However it got there, it was the cause of KDE puking and falling over looking for a symbol that doesn't exist in that library. Reading the tea-leaves, the crux of the problem is KDE doesn't enforce a soname on libreadline selection and will apparently load the first one it finds in the shared object cache. If you put libreadline.so.4 back on the system, the same issue that started this tread can reoccur. -- David C. Rankin, J.D.,P.E.
On 27.10.2022 23:36, David C. Rankin wrote:
Reading the tea-leaves, the crux of the problem is KDE doesn't enforce a soname on libreadline selection and will apparently load the first one it finds in the shared object cache.
Do man ld.so and search for ld.so.preload before making this statement.
On 10/27/22 23:25, Andrei Borzenkov wrote:
On 27.10.2022 23:36, David C. Rankin wrote:
Reading the tea-leaves, the crux of the problem is KDE doesn't enforce a soname on libreadline selection and will apparently load the first one it finds in the shared object cache.
Do
man ld.so
and search for ld.so.preload before making this statement.
Okay, good read, god I miss the old a.out binaries -- not. So other than LD_LIBRARY_PATH being searched before ld.so.cache (I presume the frowned upon rpath isn't involved) and my use of "soname" instead of $ORIGIN, $LIB, and $PLATFORM (or the versions using curly braces around the names) and that the libraries specified by LD_PRELOAD are preloaded first -- what was I suppose to pickup that casts doubt KDE was trying to load the first version of libreadline it encountered and failing? -- David C. Rankin, J.D.,P.E.
On Fri, Oct 28, 2022 at 9:39 AM David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
the libraries specified by LD_PRELOAD are preloaded first
Libraries listed in /etc/ld.so.preload in this case.
On 10/28/22 03:53, Andrei Borzenkov wrote:
On Fri, Oct 28, 2022 at 9:39 AM David C. Rankin <drankinatty@suddenlinkmail.com> wrote:
the libraries specified by LD_PRELOAD are preloaded first
Libraries listed in /etc/ld.so.preload in this case.
That's fair, Have not looked at any code or KDE5/plasma config or what it contributes to ld.so.preload. Hopefully Marc gets the issue sorted. -- David C. Rankin, J.D.,P.E.
On 2022-10-25 07:53, Marc Chamberlin wrote:
Hello - I have a recalcitrant computer running OpenSuSE 15.3 that is refusing to start the KDE/Plasma desktop. After login I get a dialog box saying "startkde: Could not start kdeinit5. Check your installation."
Are you booting to a graphical system, then login there, or are you booting to a text system, and then run some command to get a graphical session? -- Cheers / Saludos, Carlos E. R. (from 15.3 x86_64 at Telcontar)
On 10/24/22 23:48, Carlos E. R. wrote:
On 2022-10-25 07:53, Marc Chamberlin wrote:
Hello - I have a recalcitrant computer running OpenSuSE 15.3 that is refusing to start the KDE/Plasma desktop. After login I get a dialog box saying "startkde: Could not start kdeinit5. Check your installation."
Are you booting to a graphical system, then login there, or are you booting to a text system, and then run some command to get a graphical session?
Hi Carlos, and thanks for your question. I am booting directly to a graphical system. I get to the login prompt from the display manager OK but after entering my credentials, which seems to be accepted OK, things then go into the weeds and the display hangs with a box displaying the warning/error message shown in the Subject line. Marc... -- *"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./)
participants (9)
-
Andrei Borzenkov -
Carlos E. R. -
David C. Rankin -
Felix Miata -
Marc Chamberlin -
Masaru Nomiya -
Michael Hamilton -
Patrick Shanahan -
Robert Webb