Hi -I am running OpenSuSE Leap 15.3 x64 on one of my systems, and it is failing to start the desktop at the end of booting up. All I get is an XMessage box on a black screen with the error message "startkde: Could not start kdeinit5. Check your installation." Looking in the messages log file I see this message -
messages:2022-06-04T13:45:32.942306-07:00 nova startplasma-x11[2747]: "/usr/lib64/libexec/kf5/start_kdeinit_wrapper" ("--kded", "+kcminit_startup") exited with code 127
I don't grok this message and Google shows lots of old complaints about this problem but nothing current or seemingly relevant. Can some kind guru(s) help me to get this poor computer run and show my KDE desktop? I did use zypper up to make sure my computer has all the latest updates, but that gave no joy solving this problem.
Thanks in advance, Marc
Marc Chamberlin composed on 2022-06-19 11:03 (UTC-0700):
Hi -I am running OpenSuSE Leap 15.3 x64 on one of my systems, and it is failing to start the desktop at the end of booting up. All I get is an XMessage box on a black screen with the error message "startkde: Could not start kdeinit5. Check your installation." Looking in the messages log file I see this message -
messages:2022-06-04T13:45:32.942306-07:00 nova startplasma-x11[2747]: "/usr/lib64/libexec/kf5/start_kdeinit_wrapper" ("--kded", "+kcminit_startup") exited with code 127
I don't grok this message and Google shows lots of old complaints about this problem but nothing current or seemingly relevant. Can some kind guru(s) help me to get this poor computer run and show my KDE desktop? I did use zypper up to make sure my computer has all the latest updates, but that gave no joy solving this problem.
Probably something failed to upgrade or install. Run
zypper ve
to confirm all dependencies are met.
On 6/19/22 11:30, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-19 11:03 (UTC-0700):
Hi -I am running OpenSuSE Leap 15.3 x64 on one of my systems, and it is failing to start the desktop at the end of booting up. All I get is an XMessage box on a black screen with the error message "startkde: Could not start kdeinit5. Check your installation." Looking in the messages log file I see this message - messages:2022-06-04T13:45:32.942306-07:00 nova startplasma-x11[2747]: "/usr/lib64/libexec/kf5/start_kdeinit_wrapper" ("--kded", "+kcminit_startup") exited with code 127 I don't grok this message and Google shows lots of old complaints about this problem but nothing current or seemingly relevant. Can some kind guru(s) help me to get this poor computer run and show my KDE desktop? I did use zypper up to make sure my computer has all the latest updates, but that gave no joy solving this problem.
Probably something failed to upgrade or install. Run
zypper ve
to confirm all dependencies are met.
Hi Felix, thanks for replying and yeah I am now working on my next problem! ;-) The output of the zypper ve command looks good...
nova:/var/log #zypper ve Loading repository data... Reading installed packages... Dependencies of all installed packages are satisfied.
Marc...
Marc Chamberlin composed on 2022-06-19 12:11 (UTC-0700):
Dependencies of all installed packages are satisfied.
Let's see output from
zypper lr -d | susepaste
On 6/19/22 12:21, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-19 12:11 (UTC-0700):
Dependencies of all installed packages are satisfied.
Let's see output from
zypper lr -d | susepaste
Here you go Felix, note I am using SSH to access this sick computer, hence that is probably the reason for the display error.
nova:/var/log #zypper lr -d | susepaste Pasted as: https://susepaste.org/48665208 https://paste.opensuse.org/48665208 Error: Can't open display: (null) Link is also in your clipboard.
HTHs Marc...
Marc Chamberlin composed on 2022-06-19 12:38 (UTC-0700):
Here you go Felix, note I am using SSH to access this sick computer, hence that is probably the reason for the display error.
nova:/var/log #zypper lr -d | susepaste Pasted as: https://susepaste.org/48665208 https://paste.opensuse.org/48665208 Error: Can't open display: (null) Link is also in your clipboard.
What happens when you try a normal boot now?
If Plasma won't start, try IceWM, or whatever other session type your login manager offers.
You should do some repo maintenance. You have a bunch of optional repos. Those pointing to 15.2 should be removed or switched to 15.3. Those you aren't sure you need, disable or remove.
Once that's done, let's see output of the following command:
zypper se -si | grep 'tem Pac' | grep -v plication
On 6/19/22 12:57, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-19 12:38 (UTC-0700):
Here you go Felix, note I am using SSH to access this sick computer, hence that is probably the reason for the display error.
nova:/var/log #zypper lr -d | susepaste Pasted as: https://susepaste.org/48665208 https://paste.opensuse.org/48665208 Error: Can't open display: (null) Link is also in your clipboard.
What happens when you try a normal boot now?
Felix - I still get the same error - startkde: Could not start kdeinit5. Check your installation.
If Plasma won't start, try IceWM, or whatever other session type your login manager offers.
Um, I am gonna need some help I think. The system was set up to automatically log me in, so I don't get the login manager screen. Without the GUI I don't know how to reset this.
You should do some repo maintenance. You have a bunch of optional repos. Those pointing to 15.2 should be removed or switched to 15.3. Those you aren't sure you need, disable or remove.
I disabled the Bacula 15.2 repo which does not have a 15.3 version available, and a few other not so important repos that I will need eventually.
Once that's done, let's see output of the following command:
zypper se -si | grep 'tem Pac' | grep -v plication
OK, here you go, kinda long and wraps every line, sorry!
nova:/home/marc #zypper se -si | grep 'tem Pac' | grep -v plication i+ | awesfx | package | 0.5.2-lp153.117.1 | x86_64 | (System Packages) i+ | bacula-client | package | 11.0.6-lp152.1.1 | x86_64 | (System Packages) i+ | bacula-common | package | 11.0.6-lp152.1.1 | x86_64 | (System Packages) i+ | bacula-console | package | 11.0.6-lp152.1.1 | x86_64 | (System Packages) i+ | clementine | package | 1.3.99.20210609-lp153.151.3 | x86_64 | (System Packages) i+ | curl | package | 7.83.1-lp153.324.1 | x86_64 | (System Packages) i+ | hw-probe | package | 1.5-lp152.6.1 | noarch | (System Packages) i+ | libbind9-160 | package | 9.11.2-lp152.13.6 | x86_64 | (System Packages) i+ | libcurl4 | package | 7.83.1-lp153.324.1 | x86_64 | (System Packages) i+ | libdns169 | package | 9.11.2-lp152.13.6 | x86_64 | (System Packages) i+ | libdvdcss2 | package | 1.4.2-lp153.2.1 | x86_64 | (System Packages) i+ | libgnutls30 | package | 3.7.6-lp153.72.9 | x86_64 | (System Packages) i+ | libhogweed6 | package | 3.7.3-lp153.27.1 | x86_64 | (System Packages) i+ | libirs160 | package | 9.11.2-lp152.13.6 | x86_64 | (System Packages) i+ | libisc166 | package | 9.11.2-lp152.13.6 | x86_64 | (System Packages) i+ | libisccc160 | package | 9.11.2-lp152.13.6 | x86_64 | (System Packages) i+ | libisccfg160 | package | 9.11.2-lp152.13.6 | x86_64 | (System Packages) i+ | liblwres160 | package | 9.11.2-lp152.13.6 | x86_64 | (System Packages) i+ | libnettle8 | package | 3.7.3-lp153.27.1 | x86_64 | (System Packages) i+ | libopenssl-1_1-devel | package | 1.1.1o-lp153.123.1 | x86_64 | (System Packages) i+ | libopenssl-devel | package | 1.1.1o-lp153.1.1 | noarch | (System Packages) i+ | libopenssl1_1 | package | 1.1.1o-lp153.123.1 | x86_64 | (System Packages) i+ | libply-boot-client4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 | x86_64 | (System Packages) i+ | libply-splash-core4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 | x86_64 | (System Packages) i+ | libply-splash-graphics4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 | x86_64 | (System Packages) i+ | libply4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 | x86_64 | (System Packages) i+ | libprojectM3 | package | 3.1.12-lp153.49.1 | x86_64 | (System Packages) i+ | libsuil-0-0 | package | 0.10.10-lp153.33.1 | x86_64 | (System Packages) i+ | libtasn1-6 | package | 4.18.0-lp153.18.3 | x86_64 | (System Packages) i+ | libtasn1-tools | package | 4.18.0-lp153.18.3 | x86_64 | (System Packages) i+ | libwireshark13 | package | 3.2.8-lp152.2.9.1 | x86_64 | (System Packages) i+ | libwiretap10 | package | 3.2.8-lp152.2.9.1 | x86_64 | (System Packages) i+ | libwsutil11 | package | 3.2.8-lp152.2.9.1 | x86_64 | (System Packages) i+ | libx264-160 | package | 0.160+git20200702.cde9a933-pm152.1.2 | x86_64 | (System Packages) i+ | libx265-192 | package | 3.4-pm152.1.2 | x86_64 | (System Packages) i+ | libyui-ncurses11 | package | 2.54.5-lp152.1.3 | x86_64 | (System Packages) i+ | libyui-qt-graph11 | package | 2.46.3-lp152.1.1 | x86_64 | (System Packages) i+ | libyui-qt11 | package | 2.52.4-lp152.1.1 | x86_64 | (System Packages) i+ | libyui11 | package | 3.9.3-lp152.1.3 | x86_64 | (System Packages) i+ | libzvbi0 | package | 0.2.35-lp153.52.1 | x86_64 | (System Packages) i+ | openssl | package | 1.1.1o-lp153.1.1 | noarch | (System Packages) i+ | openssl-1_1 | package | 1.1.1o-lp153.123.1 | x86_64 | (System Packages) i+ | patterns-desktop-multimedia_opt | package | 20170319-lp152.5.3 | x86_64 | (System Packages) i+ | perl-Class-Std-Fast | package | 0.0.8-lp153.4.1 | x86_64 | (System Packages) i+ | perl-Number-Bytes-Human | package | 0.11-lp153.5.1 | noarch | (System Packages) i+ | perl-SOAP-WSDL | package | 3.004-lp153.2.1 | x86_64 | (System Packages) i+ | perl-Sys-MemInfo | package | 0.99-lp153.5.1 | x86_64 | (System Packages) i+ | perl-Sys-Mmap | package | 0.20-lp153.3.1 | x86_64 | (System Packages) i+ | projectM | package | 3.1.12-lp153.49.1 | x86_64 | (System Packages) i+ | projectM-data | package | 3.1.12-lp153.49.1 | x86_64 | (System Packages) i+ | projectM-devel | package | 3.1.12-lp153.49.1 | x86_64 | (System Packages) i+ | python2-iniconfig | package | 1.1.1-lp152.2.3 | noarch | (System Packages) i | python3-zm_database_init | package | 3.3.3-lp153.5.1 | noarch | (System Packages) i+ | snapd | package | 2.56-lp153.1.1 | x86_64 | (System Packages) i+ | vorbis-tools | package | 1.4.2-lp153.273.2 | x86_64 | (System Packages) i+ | vorbis-tools-lang | package | 1.4.2-lp153.273.2 | noarch | (System Packages) i+ | ZoneMinder | package | 1.36.18-lp153.5.1 | x86_64 | (System Packages) i+ | zoom | package | 5.6.13632.0328_openSUSE-1 | x86_64 | (System Packages)
HTHs. Marc..
Marc Chamberlin composed on 2022-06-19 14:34 (UTC-0700):
Felix Miata wrote:
What happens when you try a normal boot now?
Felix - I still get the same error - startkde: Could not start kdeinit5. Check your installation.
If Plasma won't start, try IceWM, or whatever other session type your login manager offers.
Um, I am gonna need some help I think. The system was set up to automatically log me in, so I don't get the login manager screen. Without the GUI I don't know how to reset this.
I don't remember the official way to disable it when you cannot get into an X session, but if you rename your greeter's config file that should allow all the defaults, and let you start a session. Try /etc/sddm.conf or whatever /etc/sddm.cond.d/ contains, or the equivalents if using GDM or LightDM. YaST ought to be able to do it, but if not, you could try changing to a different DM:
update-alternatives --config default-displaymanager
Once that's done, let's see output of the following command:
zypper se -si | grep 'tem Pac' | grep -v plication
OK, here you go, kinda long and wraps every line, sorry!
In SeaMonkey Mail, which TB was forked from, and now supplies patches that SM Mail uses to continue, I am able to toggle line wrapping on/off in the current composition. Can't you add the Toggle Worg Wrap extension to TB?
I don't recognize anything amongst those oldies that should impact starting up a Plasma session. Let's work first on getting any X session to start, by disabling auto-login.
I cut your System Packages output down to manageable groups:
i+ | awesfx | package | 0.5.2-lp153.117.1 i+ | clementine | package | 1.3.99.20210609-lp153.151.3 i+ | curl | package | 7.83.1-lp153.324.1 i+ | libcurl4 | package | 7.83.1-lp153.324.1 i+ | libdvdcss2 | package | 1.4.2-lp153.2.1 i+ | libgnutls30 | package | 3.7.6-lp153.72.9 i+ | libhogweed6 | package | 3.7.3-lp153.27.1 i+ | libnettle8 | package | 3.7.3-lp153.27.1 i+ | libopenssl-1_1-devel | package | 1.1.1o-lp153.123.1 i+ | libopenssl-devel | package | 1.1.1o-lp153.1.1 i+ | libopenssl1_1 | package | 1.1.1o-lp153.123.1 i+ | libprojectM3 | package | 3.1.12-lp153.49.1 i+ | libsuil-0-0 | package | 0.10.10-lp153.33.1 i+ | libtasn1-6 | package | 4.18.0-lp153.18.3 i+ | libtasn1-tools | package | 4.18.0-lp153.18.3 i+ | libzvbi0 | package | 0.2.35-lp153.52.1 i+ | openssl | package | 1.1.1o-lp153.1.1 i+ | openssl-1_1 | package | 1.1.1o-lp153.123.1 i+ | perl-Class-Std-Fast | package | 0.0.8-lp153.4.1 i+ | perl-Number-Bytes-Human | package | 0.11-lp153.5.1 i+ | perl-SOAP-WSDL | package | 3.004-lp153.2.1 i+ | perl-Sys-MemInfo | package | 0.99-lp153.5.1 i+ | perl-Sys-Mmap | package | 0.20-lp153.3.1 i+ | projectM | package | 3.1.12-lp153.49.1 i+ | projectM-data | package | 3.1.12-lp153.49.1 i+ | projectM-devel | package | 3.1.12-lp153.49.1 i | python3-zm_database_init | package | 3.3.3-lp153.5.1 i+ | snapd | package | 2.56-lp153.1.1 i+ | vorbis-tools | package | 1.4.2-lp153.273.2 i+ | vorbis-tools-lang | package | 1.4.2-lp153.273.2 i+ | ZoneMinder | package | 1.36.18-lp153.5.1
i+ | bacula-client | package | 11.0.6-lp152.1.1 i+ | bacula-common | package | 11.0.6-lp152.1.1 i+ | bacula-console | package | 11.0.6-lp152.1.1 i+ | hw-probe | package | 1.5-lp152.6.1 i+ | libbind9-160 | package | 9.11.2-lp152.13.6 i+ | libdns169 | package | 9.11.2-lp152.13.6 i+ | libirs160 | package | 9.11.2-lp152.13.6 i+ | libisc166 | package | 9.11.2-lp152.13.6 i+ | libisccc160 | package | 9.11.2-lp152.13.6 i+ | libisccfg160 | package | 9.11.2-lp152.13.6 i+ | liblwres160 | package | 9.11.2-lp152.13.6 i+ | libply-boot-client4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 i+ | libply-splash-core4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 i+ | libply-splash-graphics4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 i+ | libply4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 i+ | libwireshark13 | package | 3.2.8-lp152.2.9.1 i+ | libwiretap10 | package | 3.2.8-lp152.2.9.1 i+ | libwsutil11 | package | 3.2.8-lp152.2.9.1 i+ | libyui-ncurses11 | package | 2.54.5-lp152.1.3 i+ | libyui-qt-graph11 | package | 2.46.3-lp152.1.1 i+ | libyui-qt11 | package | 2.52.4-lp152.1.1 i+ | libyui11 | package | 3.9.3-lp152.1.3 i+ | patterns-desktop-multimedia_opt| package | 20170319-lp152.5.3 i+ | python2-iniconfig | package | 1.1.1-lp152.2.3
Some of these I would have expected to be upgraded by a zypper dup, but the rest are from your optional repos.
* Felix Miata mrmazda@earthlink.net [06-19-22 19:03]:
Marc Chamberlin composed on 2022-06-19 14:34 (UTC-0700):
Felix Miata wrote:
What happens when you try a normal boot now?
Felix - I still get the same error - startkde: Could not start kdeinit5. Check your installation.
If Plasma won't start, try IceWM, or whatever other session type your login manager offers.
Um, I am gonna need some help I think. The system was set up to automatically log me in, so I don't get the login manager screen. Without the GUI I don't know how to reset this.
I don't remember the official way to disable it when you cannot get into an X session, but if you rename your greeter's config file that should allow all the defaults, and let you start a session. Try /etc/sddm.conf or whatever /etc/sddm.cond.d/ contains, or the equivalents if using GDM or LightDM. YaST ought to be able to do it, but if not, you could try changing to a different DM:
update-alternatives --config default-displaymanager
as root systemctl isolate multi-user
<ctrl><alt><f1>
log in as <your user name> startx /usr/bin/icewm-session-default -- :1
will open an iceWM session for you.
On 6/19/22 18:27, Patrick Shanahan wrote:
- Felix Miata mrmazda@earthlink.net [06-19-22 19:03]:
Marc Chamberlin composed on 2022-06-19 14:34 (UTC-0700):
Felix Miata wrote:
What happens when you try a normal boot now?
Felix - I still get the same error - startkde: Could not start kdeinit5. Check your installation.
If Plasma won't start, try IceWM, or whatever other session type your login manager offers.
Um, I am gonna need some help I think. The system was set up to automatically log me in, so I don't get the login manager screen. Without the GUI I don't know how to reset this.
I don't remember the official way to disable it when you cannot get into an X session, but if you rename your greeter's config file that should allow all the defaults, and let you start a session. Try /etc/sddm.conf or whatever /etc/sddm.cond.d/ contains, or the equivalents if using GDM or LightDM. YaST ought to be able to do it, but if not, you could try changing to a different DM:
update-alternatives --config default-displaymanager
as root systemctl isolate multi-user
<ctrl><alt><f1>
log in as <your user name> startx /usr/bin/icewm-session-default -- :1
will open an iceWM session for you.
Thanks Patrick, your magic incantations worked and I am able to bring up the iceWM session! Still no joy getting kdeinit5 working and (if I grok this correctly) starting up the SDDM session. Marc...
On 6/19/22 16:02, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-19 14:34 (UTC-0700):
Felix Miata wrote:
What happens when you try a normal boot now?
Felix - I still get the same error - startkde: Could not start kdeinit5. Check your installation.
If Plasma won't start, try IceWM, or whatever other session type your login manager offers.
Hello again Felix, and again thank you for your assistance. And thanks to Patrick's magic I was able to start the IceWM which seems to be working fine. The only hitch was that I use both Knockd and Fail2Ban to control remote access to this system, and both had stopped working also. Internet research lead me to discover that OpenSuSE 15.3 relatively recently switched the Firewalld from using iptables to nftables. Took me awhile to figure out how to get it back to working with iptables instead. Guess this will be another problem to solve later, getting both Knockd and Fail2Ban to work with nftables instead of iptables.
Um, I am gonna need some help I think. The system was set up to automatically log me in, so I don't get the login manager screen. Without the GUI I don't know how to reset this.
I don't remember the official way to disable it when you cannot get into an X session, but if you rename your greeter's config file that should allow all the defaults, and let you start a session. Try /etc/sddm.conf or whatever /etc/sddm.cond.d/ contains, or the equivalents if using GDM or LightDM. YaST ought to be able to do it, but if not, you could try changing to a different DM:
update-alternatives --config default-displaymanager
I found and changed the setting for automatic login in the KDE Systems Management utility, after getting the IceWM working. However it did not make a difference, unfortunately, I am still getting the kdeinit5 error message. Unfortunately the update-alternatives command does not offer me the choice of using IceWM as my default windows manager. SIGH! And I would prefer using SDDM since I already familiar with it and know how to use it.
Once that's done, let's see output of the following command: zypper se -si | grep 'tem Pac' | grep -v plication
OK, here you go, kinda long and wraps every line, sorry!
In SeaMonkey Mail, which TB was forked from, and now supplies patches that SM Mail uses to continue, I am able to toggle line wrapping on/off in the current composition. Can't you add the Toggle Worg Wrap extension to TB?
I don't recognize anything amongst those oldies that should impact starting up a Plasma session. Let's work first on getting any X session to start, by disabling auto-login.
I added the extension to Thunderbird and hopefully it will come in handy the next time you ask me to produce some output! 😁
I cut your System Packages output down to manageable groups:
i+ | awesfx | package | 0.5.2-lp153.117.1 i+ | clementine | package | 1.3.99.20210609-lp153.151.3 i+ | curl | package | 7.83.1-lp153.324.1 i+ | libcurl4 | package | 7.83.1-lp153.324.1 i+ | libdvdcss2 | package | 1.4.2-lp153.2.1 i+ | libgnutls30 | package | 3.7.6-lp153.72.9 i+ | libhogweed6 | package | 3.7.3-lp153.27.1 i+ | libnettle8 | package | 3.7.3-lp153.27.1 i+ | libopenssl-1_1-devel | package | 1.1.1o-lp153.123.1 i+ | libopenssl-devel | package | 1.1.1o-lp153.1.1 i+ | libopenssl1_1 | package | 1.1.1o-lp153.123.1 i+ | libprojectM3 | package | 3.1.12-lp153.49.1 i+ | libsuil-0-0 | package | 0.10.10-lp153.33.1 i+ | libtasn1-6 | package | 4.18.0-lp153.18.3 i+ | libtasn1-tools | package | 4.18.0-lp153.18.3 i+ | libzvbi0 | package | 0.2.35-lp153.52.1 i+ | openssl | package | 1.1.1o-lp153.1.1 i+ | openssl-1_1 | package | 1.1.1o-lp153.123.1 i+ | perl-Class-Std-Fast | package | 0.0.8-lp153.4.1 i+ | perl-Number-Bytes-Human | package | 0.11-lp153.5.1 i+ | perl-SOAP-WSDL | package | 3.004-lp153.2.1 i+ | perl-Sys-MemInfo | package | 0.99-lp153.5.1 i+ | perl-Sys-Mmap | package | 0.20-lp153.3.1 i+ | projectM | package | 3.1.12-lp153.49.1 i+ | projectM-data | package | 3.1.12-lp153.49.1 i+ | projectM-devel | package | 3.1.12-lp153.49.1 i | python3-zm_database_init | package | 3.3.3-lp153.5.1 i+ | snapd | package | 2.56-lp153.1.1 i+ | vorbis-tools | package | 1.4.2-lp153.273.2 i+ | vorbis-tools-lang | package | 1.4.2-lp153.273.2 i+ | ZoneMinder | package | 1.36.18-lp153.5.1 i+ | bacula-client | package | 11.0.6-lp152.1.1 i+ | bacula-common | package | 11.0.6-lp152.1.1 i+ | bacula-console | package | 11.0.6-lp152.1.1 i+ | hw-probe | package | 1.5-lp152.6.1 i+ | libbind9-160 | package | 9.11.2-lp152.13.6 i+ | libdns169 | package | 9.11.2-lp152.13.6 i+ | libirs160 | package | 9.11.2-lp152.13.6 i+ | libisc166 | package | 9.11.2-lp152.13.6 i+ | libisccc160 | package | 9.11.2-lp152.13.6 i+ | libisccfg160 | package | 9.11.2-lp152.13.6 i+ | liblwres160 | package | 9.11.2-lp152.13.6 i+ | libply-boot-client4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 i+ | libply-splash-core4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 i+ | libply-splash-graphics4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 i+ | libply4 | package | 0.9.4+git20190304.ed9f201-lp152.4.4 i+ | libwireshark13 | package | 3.2.8-lp152.2.9.1 i+ | libwiretap10 | package | 3.2.8-lp152.2.9.1 i+ | libwsutil11 | package | 3.2.8-lp152.2.9.1 i+ | libyui-ncurses11 | package | 2.54.5-lp152.1.3 i+ | libyui-qt-graph11 | package | 2.46.3-lp152.1.1 i+ | libyui-qt11 | package | 2.52.4-lp152.1.1 i+ | libyui11 | package | 3.9.3-lp152.1.3 i+ | patterns-desktop-multimedia_opt| package | 20170319-lp152.5.3 i+ | python2-iniconfig | package | 1.1.1-lp152.2.3
Some of these I would have expected to be upgraded by a zypper dup, but the rest are from your optional repos.
I am not sure if you are asking me to do a zypper dup on this system or not. The last time I just ran zypper up thinking that was probably safer. Still stuck but feeling more hopeful now that I see IceWM is working OK. I wonder if there is some kind of configuration error for SDDM but I haven't messed with it (don't know how) AFAIK.
Marc...
Marc Chamberlin composed on 2022-06-20 14:38 (UTC-0700):
Felix Miata wrote:
...
update-alternatives --config default-displaymanager
Unfortunately the update-alternatives command does not offer me the choice of using IceWM as my default windows manager.
# update-alternatives --config default-xsession.desktop
i+ | python2-iniconfig | package | 1.1.1-lp152.2.3
Some of these I would have expected to be upgraded by a zypper dup, but the rest are from your optional repos.
I am not sure if you are asking me to do a zypper dup on this system or not. The last time I just ran zypper up thinking that was probably safer. Still stuck but feeling more hopeful now that I see IceWM is working OK. I wonder if there is some kind of configuration error for SDDM but I haven't messed with it (don't know how) AFAIK.
For a 15.3 installation to be complete, it might be necessary to run zypper dup at least once. My confusion may be from spending time on 15.3 so long ago, and mostly working with 15.4 since before its beta release. I don't remember seeing you report whether this was a fresh installation, or an upgrade. If upgrade, once since its release announcement is required, I think. The idea is to ensure nothing from 15.2 is leftover, and everything you need has been installed without error.
Anyway, from a working freshly updated 15.3 with AMD graphics, running a Plasma session, I did what follows:
# ps -A | egrep 'dm|start|kde|plasma' 34 ? 00:00:00 kdevtmpfs 400 ? 00:00:00 dmeventd 696 ? 00:00:00 sdma0 697 ? 00:00:00 sdma1 1420 ? 00:00:00 tdm 1985 ? 00:00:00 tdm 2008 ? 00:00:00 startplasma-x11 2087 ? 00:00:00 start_kdeinit 2088 ? 00:00:00 kdeinit5 2104 ? 00:00:00 kded5 2146 ? 00:00:00 plasma_session 2158 ? 00:00:00 polkit-kde-auth 2160 ? 00:00:06 plasmashell 2187 ? 00:00:00 org_kde_powerde # which org_kde_powerdevil which: no org_kde_powerdevil in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin) # which org_kde_powerde which: no org_kde_powerde in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin) # which plasmashell /usr/bin/plasmashell # which polkit-kde-auth which: no polkit-kde-auth in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin) # which plasma-session which: no plasma-session in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin) # which kded5 /usr/bin/kded5 # which kdeinit5 /usr/bin/kdeinit5 # which start_kdeinit which: no start_kdeinit in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin) # which startplasma-x11 /usr/bin/startplasma-x11 # which kcminit_startup /usr/bin/kcminit_startup # ls -Gg /usr/lib64/libexec/org_kde_powerdevil -rwxr-xr-x 1 120008 Apr 23 2021 /usr/lib64/libexec/org_kde_powerdevil # ls -Gg /usr/lib64/libexec/polkit-kde-authentication-agent-1 -rwxr-xr-x 1 90208 Aug 26 2021 /usr/lib64/libexec/polkit-kde-authentication-agent-1 # ls -Gg /usr/share/xsessions/plasma5.desktop # just guessing here that it actually matters -rw-r--r-- 1 2529 Aug 27 2021 /usr/share/xsessions/plasma5.desktop # ls -Gg /usr/lib64/libexec/kf5/start_kdeinit* -rwxr-xr-x 1 10616 Aug 26 2021 /usr/lib64/libexec/kf5/start_kdeinit -rwxr-xr-x 1 6376 Aug 26 2021 /usr/lib64/libexec/kf5/start_kdeinit_wrapper # rpm -qf /usr/lib64/libexec/org_kde_powerdevil powerdevil5-5.18.5-bp153.1.36.x86_64 # rpm -qf /usr/bin/plasmashell plasma5-workspace-5.18.6-bp153.4.2.3.x86_64 # rpm -qf /usr/lib64/libexec/polkit-kde-authentication-agent-1 polkit-kde-agent-5-5.18.5-bp153.2.2.1.x86_64 # rpm -qf /usr/share/xsessions/plasma5.desktop plasma5-session-5.18.6-bp153.4.2.3.noarch # rpm -qf /usr/bin/kded5 kded-5.76.0-bp153.2.2.1.x86_64 # rpm -qf /usr/bin/kdeinit5 kinit-5.76.0-bp153.2.2.1.x86_64 # rpm -qf /usr/lib64/libexec/kf5/start_kdeinit kinit-5.76.0-bp153.2.2.1.x86_64 # rpm -qf /usr/lib64/libexec/kf5/start_kdeinit_wrapper kinit-5.76.0-bp153.2.2.1.x86_64 # rpm -qf /usr/bin/startplasma-x11 plasma5-workspace-5.18.6-bp153.4.2.3.x86_64 # rpm -qf /usr/bin/kcminit_startup plasma5-workspace-5.18.6-bp153.4.2.3.x86_64 #
One thing that might help is to force reinstallation of the above listed rpms, since it is obvious they are necessary parts of achieving a running Plasma session. It could be that there is some corruption involved somewhere to cause that not found error 127 that prevents startplasma-x11 from running.
Before getting back to package management, try from an IceWM session, or a vtty login, removing the content from ~/.cache. It's a longshot here, but it sometimes cleans up Plasma's act. Do you have an alternate user configured? Does Plasma fail to start for it too? If yes, not likely this has anything to do with user settings.
If force reinstalling the above packages is unhelpful, you could try removing the entirety of KDE/Plasma with zypper or yast, rebooting, then installing it. To do this in zypper, use the --clean-deps option, and choose several obvious basic packages to remove, such as plasma5-workspace-libs, plasma5-workspace, plasma5-session, libKF5Plasma5, plasma5-desktop, plasma-framework, kded, kde-user-manager.
Plasma on 15.3 can work: # inxi -GSaz --vs System: Kernel: 5.3.18-150300.59.71-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=<filter> noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 Desktop: KDE Plasma v: 5.18.6 tk: Qt v: 5.12.7 wm: kwin_x11 vt: 7 dm: TDM Distro: openSUSE Leap 15.3 Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu v: kernel alternate: radeon arch: GCN 2 process: GF/TSMC 16-28nm built: 2013-17 ports: active: DP-1,DVI-D-1,HDMI-A-1 empty: VGA-1 bus-ID: 00:01.0 chip-ID: 1002:1313 class-ID: 0300 Display: x11 server: X.Org v: 1.20.3 compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 2560x3540 s-dpi: 120 s-size: 541x749mm (21.30x29.49") s-diag: 924mm (36.38") Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: middle model: Dell P2012H serial: <filter> built: 2012 res: 1600x900 hz: 60 dpi: 92 gamma: 1.2 size: 443x249mm (17.44x9.8") diag: 508mm (20") ratio: 16:9 modes: max: 1600x900 min: 720x400 Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,bottom model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: primary,top model: NEC EA243WM serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 OpenGL: renderer: AMD KAVERI (DRM 3.39.0 5.3.18-150300.59.71-default LLVM 11.0.1) v: 4.6 Mesa 20.2.4 direct render: Yes # Pay no attention to the radeon.cik_support=0 amdgpu.cik_support=1 command line options. They're only for the particular (older) AMD generation I have.
On 6/20/22 23:30, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-20 14:38 (UTC-0700):
Felix Miata wrote:
...
update-alternatives --config default-displaymanager
Unfortunately the update-alternatives command does not offer me the choice of using IceWM as my default windows manager.
# update-alternatives --config default-xsession.desktop
Hi Felix, First a big thank you for taking the time to respond and trying to help me! This email must have taken you quite a bit of time and effort to compose it for me and I really appreciate it! I will intersperse my comments within your email in order to keep them in the proper context. Also I am sorry for the delay in responding myself, life got in the way and I have encountered a new puzzling problem regarding the firewall I think. More on that below.
You second version of the magic incantation for update-alternatives does allow me to select IceWM, thank you! I don't grok what the difference is between selecting a default display manager and selecting a default xsession desktop. It feels like having these two variants is an unnecessary complication, not intuitive, and doesn't provide a user friendly method/need for selecting the type of desktop environment wanted. Anywise this is not an issue that needs to be discussed, I will accept it and move on.
i+ | python2-iniconfig | package | 1.1.1-lp152.2.3
Some of these I would have expected to be upgraded by a zypper dup, but the rest are from your optional repos.
I am not sure if you are asking me to do a zypper dup on this system or not. The last time I just ran zypper up thinking that was probably safer. Still stuck but feeling more hopeful now that I see IceWM is working OK. I wonder if there is some kind of configuration error for SDDM but I haven't messed with it (don't know how) AFAIK.
For a 15.3 installation to be complete, it might be necessary to run zypper dup at least once. My confusion may be from spending time on 15.3 so long ago, and mostly working with 15.4 since before its beta release. I don't remember seeing you report whether this was a fresh installation, or an upgrade. If upgrade, once since its release announcement is required, I think. The idea is to ensure nothing from 15.2 is leftover, and everything you need has been installed without error.
My OpenSuSE 15.3 system has been up and running for quite awhile. My troubles seem to begin with some updates I notified about that needed to be installed.
I went ahead and ran a zypper dup --allow-vendor-change and that resulted in a bunch of packages being reinstalled using the SuSE vendor versions. This did not fix the problem I am having with starting kdeinit5, and it introduced a new but inconstant problem with firewalld. Most of the time, after rebooting this system I can no longer access services such as SSH, X11VNC, AUTOMOUNT/AUTOFS and KNOCKD although I can always access HTTP/HTTPS.
I did find and correct one issue that zypper dup caused, it switched firewalld from using iptables to using nftables. I switched it back to iptables because I am using both KNOCKD and FAIL2BAN which only work (afaik) with iptables. But that did not fix the other new issue, my inability to access services on this afflicted system from my laptop (or any other computer)
The funny thing is however, after a couple of my reboots I have been able to access all these services from my (remote) laptop all of the sudden and I have no idea why (next reboot and that ability reverted back to not being able to connect to ports that I had opened). When my ability to access these other services wasn't working, I did the CNTL-ALT-F1 trick to get to a shell login prompt (after I got the failed to start KDEINIT5 message) and logged to to the system. Then I checked what ports had a listening daemon connected to them using both -
|sudo lsof -i -P -n | grep LISTEN sudo netstat -tulpn | grep LISTEN|
nova:/home/marc #lsof -i -P -n | grep LISTEN systemd 1 root 37u IPv4 17481 0t0 TCP *:111 (LISTEN) systemd 1 root 39u IPv6 17485 0t0 TCP *:111 (LISTEN) rpcbind 1034 rpc 4u IPv4 17481 0t0 TCP *:111 (LISTEN) rpcbind 1034 rpc 6u IPv6 17485 0t0 TCP *:111 (LISTEN) cupsd 1109 root 7u IPv6 30165 0t0 TCP [::1]:631 (LISTEN) cupsd 1109 root 8u IPv4 30166 0t0 TCP 127.0.0.1:631 (LISTEN) boinc 2182 boinc 5u IPv4 46517 0t0 TCP 127.0.0.1:31416 (LISTEN) bacula-fd 2185 root 4u IPv4 38502 0t0 TCP *:9102 (LISTEN) rpc.mount 2186 root 8u IPv4 34313 0t0 TCP *:20048 (LISTEN) rpc.mount 2186 root 10u IPv6 34317 0t0 TCP *:20048 (LISTEN) rpc.statd 2193 statd 8u IPv4 33638 0t0 TCP *:47261 (LISTEN) rpc.statd 2193 statd 10u IPv6 33642 0t0 TCP *:54907 (LISTEN) java 2203 root 152u IPv6 47479 0t0 TCP 127.0.0.1:53566 (LISTEN) java 2203 root 195u IPv6 46943 0t0 TCP *:3052 (LISTEN) java 2203 root 200u IPv6 46945 0t0 TCP *:53568 (LISTEN) sshd 2236 root 3u IPv4 37397 0t0 TCP 192.168.10.20:622 (LISTEN) sshd 2236 root 4u IPv4 37400 0t0 TCP 192.168.10.20:22 (LISTEN) httpd-pre 2244 root 4u IPv6 35211 0t0 TCP *:80 (LISTEN) httpd-pre 2244 root 6u IPv6 35214 0t0 TCP *:443 (LISTEN) mysqld 2319 mysql 17u IPv4 37702 0t0 TCP 127.0.0.1:3306 (LISTEN) sendmail 2447 root 4u IPv4 35375 0t0 TCP 127.0.0.1:25 (LISTEN) clamd 2638 vscan 5u IPv4 48618 0t0 TCP 127.0.0.1:3310 (LISTEN) smbd 2993 root 45u IPv4 46506 0t0 TCP 10.10.10.1:445 (LISTEN) smbd 2993 root 46u IPv4 46507 0t0 TCP 10.10.10.1:139 (LISTEN) smbd 2993 root 47u IPv4 46508 0t0 TCP 192.168.10.20:445 (LISTEN) smbd 2993 root 48u IPv4 46509 0t0 TCP 192.168.10.20:139 (LISTEN) smbd 2993 root 49u IPv4 46510 0t0 TCP 127.0.0.1:445 (LISTEN) smbd 2993 root 50u IPv4 46511 0t0 TCP 127.0.0.1:139 (LISTEN) smbd 2993 root 51u IPv6 46512 0t0 TCP [::1]:445 (LISTEN) smbd 2993 root 52u IPv6 46513 0t0 TCP [::1]:139 (LISTEN) x11vnc 3032 root 8u IPv4 48628 0t0 TCP *:5900 (LISTEN) x11vnc 3032 root 9u IPv6 48629 0t0 TCP *:5900 (LISTEN) httpd-pre 7151 wwwrun 4u IPv6 35211 0t0 TCP *:80 (LISTEN) httpd-pre 7151 wwwrun 6u IPv6 35214 0t0 TCP *:443 (LISTEN) httpd-pre 7152 wwwrun 4u IPv6 35211 0t0 TCP *:80 (LISTEN) httpd-pre 7152 wwwrun 6u IPv6 35214 0t0 TCP *:443 (LISTEN) httpd-pre 7153 wwwrun 4u IPv6 35211 0t0 TCP *:80 (LISTEN) httpd-pre 7153 wwwrun 6u IPv6 35214 0t0 TCP *:443 (LISTEN) httpd-pre 7154 wwwrun 4u IPv6 35211 0t0 TCP *:80 (LISTEN) httpd-pre 7154 wwwrun 6u IPv6 35214 0t0 TCP *:443 (LISTEN) httpd-pre 7155 wwwrun 4u IPv6 35211 0t0 TCP *:80 (LISTEN) httpd-pre 7155 wwwrun 6u IPv6 35214 0t0 TCP *:443 (LISTEN) httpd-pre 7495 wwwrun 4u IPv6 35211 0t0 TCP *:80 (LISTEN) httpd-pre 7495 wwwrun 6u IPv6 35214 0t0 TCP *:443 (LISTEN) httpd-pre 14670 wwwrun 4u IPv6 35211 0t0 TCP *:80 (LISTEN) httpd-pre 14670 wwwrun 6u IPv6 35214 0t0 TCP *:443 (LISTEN)
and this did show me that there was a listening process for all the ports that I want open, for example, these would show me that the SSHD was listening on port 22. Next I check FIREWALLD using then command
nova:/home/marc #firewall-cmd --list-all --zone=internal internal (active) target: default icmp-block-inversion: no interfaces: eth0 sources: services: apache2 apache2-ssl bacula-client dhcpv6-client http https kdeconnect kdeconnect-kde mdns nfs nfs3 rpc-bind samba samba-client slp smtp smtp-submi ssion smtps ssh tigervnc vnc-server x11 ports: 5900-5910/tcp 3052/tcp 622/tcp 622/udp protocols: forward: no masquerade: no forward-ports: source-ports: icmp-blocks: rich rules:
to see what ports it had opened. So indeed taking SSHD as and example, port 22 is both open and has a listener. But when I actually try to use SSH and connect to port 22 on this system, from my laptop (also on the same internal 192.168.10.0/24 net) I get an error message telling me there is no route to this host. So I dunno what the problem could be. I have tried making the connection with and without
Anyway, from a working freshly updated 15.3 with AMD graphics, running a Plasma session, I did what follows:
# ps -A | egrep 'dm|start|kde|plasma' 34 ? 00:00:00 kdevtmpfs 400 ? 00:00:00 dmeventd 696 ? 00:00:00 sdma0 697 ? 00:00:00 sdma1 1420 ? 00:00:00 tdm 1985 ? 00:00:00 tdm 2008 ? 00:00:00 startplasma-x11 2087 ? 00:00:00 start_kdeinit 2088 ? 00:00:00 kdeinit5 2104 ? 00:00:00 kded5 2146 ? 00:00:00 plasma_session 2158 ? 00:00:00 polkit-kde-auth 2160 ? 00:00:06 plasmashell 2187 ? 00:00:00 org_kde_powerde # which org_kde_powerdevil which: no org_kde_powerdevil in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin) # which org_kde_powerde which: no org_kde_powerde in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin) # which plasmashell /usr/bin/plasmashell # which polkit-kde-auth which: no polkit-kde-auth in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin) # which plasma-session which: no plasma-session in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin) # which kded5 /usr/bin/kded5 # which kdeinit5 /usr/bin/kdeinit5 # which start_kdeinit which: no start_kdeinit in (/sbin:/usr/sbin:/usr/local/sbin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/X11R6/bin) # which startplasma-x11 /usr/bin/startplasma-x11 # which kcminit_startup /usr/bin/kcminit_startup # ls -Gg /usr/lib64/libexec/org_kde_powerdevil -rwxr-xr-x 1 120008 Apr 23 2021 /usr/lib64/libexec/org_kde_powerdevil # ls -Gg /usr/lib64/libexec/polkit-kde-authentication-agent-1 -rwxr-xr-x 1 90208 Aug 26 2021 /usr/lib64/libexec/polkit-kde-authentication-agent-1 # ls -Gg /usr/share/xsessions/plasma5.desktop # just guessing here that it actually matters -rw-r--r-- 1 2529 Aug 27 2021 /usr/share/xsessions/plasma5.desktop # ls -Gg /usr/lib64/libexec/kf5/start_kdeinit* -rwxr-xr-x 1 10616 Aug 26 2021 /usr/lib64/libexec/kf5/start_kdeinit -rwxr-xr-x 1 6376 Aug 26 2021 /usr/lib64/libexec/kf5/start_kdeinit_wrapper # rpm -qf /usr/lib64/libexec/org_kde_powerdevil powerdevil5-5.18.5-bp153.1.36.x86_64 # rpm -qf /usr/bin/plasmashell plasma5-workspace-5.18.6-bp153.4.2.3.x86_64 # rpm -qf /usr/lib64/libexec/polkit-kde-authentication-agent-1 polkit-kde-agent-5-5.18.5-bp153.2.2.1.x86_64 # rpm -qf /usr/share/xsessions/plasma5.desktop plasma5-session-5.18.6-bp153.4.2.3.noarch # rpm -qf /usr/bin/kded5 kded-5.76.0-bp153.2.2.1.x86_64 # rpm -qf /usr/bin/kdeinit5 kinit-5.76.0-bp153.2.2.1.x86_64 # rpm -qf /usr/lib64/libexec/kf5/start_kdeinit kinit-5.76.0-bp153.2.2.1.x86_64 # rpm -qf /usr/lib64/libexec/kf5/start_kdeinit_wrapper kinit-5.76.0-bp153.2.2.1.x86_64 # rpm -qf /usr/bin/startplasma-x11 plasma5-workspace-5.18.6-bp153.4.2.3.x86_64 # rpm -qf /usr/bin/kcminit_startup plasma5-workspace-5.18.6-bp153.4.2.3.x86_64 #
I ran all these commands and got exactly the same results.
One thing that might help is to force reinstallation of the above listed rpms, since it is obvious they are necessary parts of achieving a running Plasma session. It could be that there is some corruption involved somewhere to cause that not found error 127 that prevents startplasma-x11 from running.
I did this for all of the above listed packages using the command - zypper in -f <package name> There was no joy in resolving my issues.
Before getting back to package management, try from an IceWM session, or a vtty login, removing the content from ~/.cache. It's a longshot here, but it sometimes cleans up Plasma's act. Do you have an alternate user configured? Does Plasma fail to start for it too? If yes, not likely this has anything to do with user settings.
I removed everything in ~/.cache and again no joy. KDE/Plasma fails to give me a login screen at all so I cannot try using an alternate user.
If force reinstalling the above packages is unhelpful, you could try removing the entirety of KDE/Plasma with zypper or yast, rebooting, then installing it. To do this in zypper, use the --clean-deps option, and choose several obvious basic packages to remove, such as plasma5-workspace-libs, plasma5-workspace, plasma5-session, libKF5Plasma5, plasma5-desktop, plasma-framework, kded, kde-user-manager.
Well I don't know what is "obvious" ;-) but I used the command -
zypper remove --clean-deps <package name>
to remove each of the packages you suggested, then rebooted, and use the command -
zypper install <package name>
to reinstall all the packages you suggested. Again rebooted and (sigh) again no joy in getting kdeinit5 to start, and getting it to show a login screen and/or show the plasma desktop! I was able to connect via SSH so at least that may be working (# of tests is one so inductive proof does not apply)...
Marc...
Plasma on 15.3 can work: # inxi -GSaz --vs System: Kernel: 5.3.18-150300.59.71-default arch: x86_64 bits: 64 compiler: gcc v: 7.5.0 parameters: BOOT_IMAGE=/boot/vmlinuz root=LABEL=<filter> noresume ipv6.disable=1 net.ifnames=0 mitigations=auto consoleblank=0 radeon.cik_support=0 amdgpu.cik_support=1 Desktop: KDE Plasma v: 5.18.6 tk: Qt v: 5.12.7 wm: kwin_x11 vt: 7 dm: TDM Distro: openSUSE Leap 15.3 Graphics: Device-1: AMD Kaveri [Radeon R7 Graphics] vendor: ASRock driver: amdgpu v: kernel alternate: radeon arch: GCN 2 process: GF/TSMC 16-28nm built: 2013-17 ports: active: DP-1,DVI-D-1,HDMI-A-1 empty: VGA-1 bus-ID: 00:01.0 chip-ID: 1002:1313 class-ID: 0300 Display: x11 server: X.Org v: 1.20.3 compositor: kwin_x11 driver: X: loaded: amdgpu unloaded: fbdev,modesetting,vesa gpu: amdgpu display-ID: :0 screens: 1 Screen-1: 0 s-res: 2560x3540 s-dpi: 120 s-size: 541x749mm (21.30x29.49") s-diag: 924mm (36.38") Monitor-1: DVI-D-1 mapped: DVI-D-0 pos: middle model: Dell P2012H serial: <filter> built: 2012 res: 1600x900 hz: 60 dpi: 92 gamma: 1.2 size: 443x249mm (17.44x9.8") diag: 508mm (20") ratio: 16:9 modes: max: 1600x900 min: 720x400 Monitor-2: DP-1 mapped: DisplayPort-0 pos: primary,bottom model: Acer K272HUL serial: <filter> built: 2018 res: 2560x1440 hz: 60 dpi: 109 gamma: 1.2 size: 598x336mm (23.54x13.23") diag: 686mm (27") ratio: 16:9 modes: max: 2560x1440 min: 720x400 Monitor-3: HDMI-A-1 mapped: HDMI-A-0 pos: primary,top model: NEC EA243WM serial: <filter> built: 2011 res: 1920x1200 hz: 60 dpi: 94 gamma: 1.2 size: 519x324mm (20.43x12.76") diag: 612mm (24.1") ratio: 16:10 modes: max: 1920x1200 min: 640x480 OpenGL: renderer: AMD KAVERI (DRM 3.39.0 5.3.18-150300.59.71-default LLVM 11.0.1) v: 4.6 Mesa 20.2.4 direct render: Yes # Pay no attention to the radeon.cik_support=0 amdgpu.cik_support=1 command line options. They're only for the particular (older) AMD generation I have.
On 6/24/22 20:22, Marc Chamberlin wrote:
I was able to connect via SSH so at least that may be working (# of tests is one so inductive proof does not apply)...
Think I was too optimistic, second attempt to connect via SSH to my sick computer, after a reboot, failed. So something is wrong with the firewall still.
Going bug hunting on the firewall.... Marc..
Marc Chamberlin composed on 2022-06-24 20:22 (UTC-0700):
You second version of the magic incantation for update-alternatives does allow me to select IceWM, thank you! I don't grok what the difference is between selecting a default display manager and selecting a default xsession desktop. It feels like having these two variants is an unnecessary complication, not intuitive, and doesn't provide a user friendly method/need for selecting the type of desktop environment wanted. Anywise this is not an issue that needs to be discussed, I will accept it and move on.
...
I removed everything in ~/.cache and again no joy. KDE/Plasma fails to give me a login screen at all so I cannot try using an alternate user.
KDE/Plasma doesn't give anybody a login screen. That's the job of the installed and configured DM. Which DM you get is the result of:
update-alternatives --config default-displaymanager
You should rarely or never need to use this again, unless for troubleshooting, or you just want to switch from whatever you've been using.
It's on the login screen presented by the DM that a user-friendly choice among session types may be selected from a menu after logging out or booting, the same session types you see from using:
update-alternatives --config default-xsession.desktop
You should rarely or never need to use this again, unless for troubleshooting.
Once you've made your first selection of xsession type, the default will no longer be relevant, except to a new user, /or/, if you login on a vtty and use startx to try to open an X session.
It is necessary to open an X session as a different/new user to determine whether or not the kdeinit5 issue has anything to do with user settings. That choice should be made via the GUI login greeter, whether it's SDDM, LightDM, GDM, XDM or something else available when running update-alternatives --config default-displaymanager.
SDDM is the normal DM used with KDE installations. Did you try switching with update-alternatives --config default-displaymanager to something else (e.g. LightDM) to see if Plasma would start from it?
Do you get the same error if you boot with a 3 appended to the linu line at the Grub menu striking the E key, then login and try:
WINDOWMANAGER=startplasma-x11 startx
If no joy as normal user, what about as root user, or as virgin user?
I'm out of other ideas how to troubleshoot this, and those new network/firewall issues will need a new thread to draw people with experience troubleshooting those areas. If it was me at this point, I'd restore from a good backup, or more likely, do a fresh installation, and skip up to 15.4. You might give an upgrade to 15.4 a try rather than a fresh installation.
Given the relative lack of interest in this thread by other people, it's probably prudent to try elsewhere, either forums.opensuse.org, or KDE forums.
On 6/24/22 22:12, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-24 20:22 (UTC-0700):
You second version of the magic incantation for update-alternatives does allow me to select IceWM, thank you! I don't grok what the difference is between selecting a default display manager and selecting a default xsession desktop. It feels like having these two variants is an unnecessary complication, not intuitive, and doesn't provide a user friendly method/need for selecting the type of desktop environment wanted. Anywise this is not an issue that needs to be discussed, I will accept it and move on.
...
I removed everything in ~/.cache and again no joy. KDE/Plasma fails to give me a login screen at all so I cannot try using an alternate user.
KDE/Plasma doesn't give anybody a login screen. That's the job of the installed and configured DM. Which DM you get is the result of:
update-alternatives --config default-displaymanager
You should rarely or never need to use this again, unless for troubleshooting, or you just want to switch from whatever you've been using.
It's on the login screen presented by the DM that a user-friendly choice among session types may be selected from a menu after logging out or booting, the same session types you see from using:
update-alternatives --config default-xsession.desktop
You should rarely or never need to use this again, unless for troubleshooting.
Once you've made your first selection of xsession type, the default will no longer be relevant, except to a new user, /or/, if you login on a vtty and use startx to try to open an X session.
Hi again Felix, I am using SDDM -
nova:/home/marc #update-alternatives --config default-displaymanager There are 4 choices for the alternative default-displaymanager (providing /usr/lib/X11/displaymanagers/default-displaymanager).
Selection Path Priority Status ------------------------------------------------------------ * 0 /usr/lib/X11/displaymanagers/sddm 25 auto mode 1 /usr/lib/X11/displaymanagers/console 5 manual mode 2 /usr/lib/X11/displaymanagers/lightdm 15 manual mode 3 /usr/lib/X11/displaymanagers/sddm 25 manual mode 4 /usr/lib/X11/displaymanagers/xdm 10 manual mode
Press <enter> to keep the current choice[*], or type selection number:
It is necessary to open an X session as a different/new user to determine whether or not the kdeinit5 issue has anything to do with user settings. That choice should be made via the GUI login greeter, whether it's SDDM, LightDM, GDM, XDM or something else available when running update-alternatives --config default-displaymanager.
Trouble is, I am not getting far enough to see the GUI login greeter. As soon as all the start up messages finish, the screen goes black, the cursor arrow is shown, and then the xbox message pops up telling me that kdeinit5 failed to start. I can then do the CTRL-ALT-F1 trick to break out and get to a simple login prompt. I can then log in to a simple text base terminal and use text commands, but there is no GUI except for things like the ncurses version of YaST2.
SDDM is the normal DM used with KDE installations. Did you try switching with update-alternatives --config default-displaymanager to something else (e.g. LightDM) to see if Plasma would start from it?
Yes, I tried changing the DM to LightDM and others, and got the exact same error, kdeinit5 failed to start.
Do you get the same error if you boot with a 3 appended to the linu line at the Grub menu striking the E key, then login and try:marc
WINDOWMANAGER=startplasma-x11 startx
If no joy as normal user, what about as root user, or as virgin user?
No joy with this approach either Felix, but with a slightly different behavior with root and newuser. When I login with either I get a brief flash of the xbox message about kdeinit5 not starting, followed by a blank screen with a spinning circle for awhile, then back to the screen with the xbox message.
I'm out of other ideas how to troubleshoot this, and those new network/firewall issues will need a new thread to draw people with experience troubleshooting those areas. If it was me at this point, I'd restore from a good backup, or more likely, do a fresh installation, and skip up to 15.4. You might give an upgrade to 15.4 a try rather than a fresh installation.
Yeah I am beginning to think that installing 15.4, in a separate partition might be the better part of valor! That also will mean a lot of work but probably best.
Given the relative lack of interest in this thread by other people, it's probably prudent to try elsewhere, either forums.opensuse.org, or KDE forums.
OK, I hear you and understand... Marc...
On 26/06/2022 10:21, Marc Chamberlin wrote:
On 6/24/22 22:12, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-24 20:22 (UTC-0700):
You second version of the magic incantation for update-alternatives does allow me to select IceWM, thank you! I don't grok what the difference is between selecting a default display manager and selecting a default xsession desktop. It feels like having these two variants is an unnecessary complication, not intuitive, and doesn't provide a user friendly method/need for selecting the type of desktop environment wanted. Anywise this is not an issue that needs to be discussed, I will accept it and move on.
...
I removed everything in ~/.cache and again no joy. KDE/Plasma fails to give me a login screen at all so I cannot try using an alternate user.
KDE/Plasma doesn't give anybody a login screen. That's the job of the installed and configured DM. Which DM you get is the result of:
update-alternatives --config default-displaymanager
You should rarely or never need to use this again, unless for troubleshooting, or you just want to switch from whatever you've been using.
It's on the login screen presented by the DM that a user-friendly choice among session types may be selected from a menu after logging out or booting, the same session types you see from using:
update-alternatives --config default-xsession.desktop
You should rarely or never need to use this again, unless for troubleshooting.
Once you've made your first selection of xsession type, the default will no longer be relevant, except to a new user, /or/, if you login on a vtty and use startx to try to open an X session.
Hi again Felix, I am using SDDM -
nova:/home/marc #update-alternatives --config default-displaymanager There are 4 choices for the alternative default-displaymanager (providing /usr/lib/X11/displaymanagers/default-displaymanager).
Selection Path Priority Status
- 0 /usr/lib/X11/displaymanagers/sddm 25 auto mode
1 /usr/lib/X11/displaymanagers/console 5 manual mode 2 /usr/lib/X11/displaymanagers/lightdm 15 manual mode 3 /usr/lib/X11/displaymanagers/sddm 25 manual mode 4 /usr/lib/X11/displaymanagers/xdm 10 manual mode
Press <enter> to keep the current choice[*], or type selection number:
It is necessary to open an X session as a different/new user to determine whether or not the kdeinit5 issue has anything to do with user settings. That choice should be made via the GUI login greeter, whether it's SDDM, LightDM, GDM, XDM or something else available when running update-alternatives --config default-displaymanager.
Trouble is, I am not getting far enough to see the GUI login greeter. As soon as all the start up messages finish, the screen goes black, the cursor arrow is shown, and then the xbox message pops up telling me that kdeinit5 failed to start. I can then do the CTRL-ALT-F1 trick to break out and get to a simple login prompt. I can then log in to a simple text base terminal and use text commands, but there is no GUI except for things like the ncurses version of YaST2.
SDDM is the normal DM used with KDE installations. Did you try switching with update-alternatives --config default-displaymanager to something else (e.g. LightDM) to see if Plasma would start from it?
Yes, I tried changing the DM to LightDM and others, and got the exact same error, kdeinit5 failed to start.
Do you get the same error if you boot with a 3 appended to the linu line at the Grub menu striking the E key, then login and try:marc
WINDOWMANAGER=startplasma-x11 startx
If no joy as normal user, what about as root user, or as virgin user?
No joy with this approach either Felix, but with a slightly different behavior with root and newuser. When I login with either I get a brief flash of the xbox message about kdeinit5 not starting, followed by a blank screen with a spinning circle for awhile, then back to the screen with the xbox message.
I'm out of other ideas how to troubleshoot this, and those new network/firewall issues will need a new thread to draw people with experience troubleshooting those areas. If it was me at this point, I'd restore from a good backup, or more likely, do a fresh installation, and skip up to 15.4. You might give an upgrade to 15.4 a try rather than a fresh installation.
Yeah I am beginning to think that installing 15.4, in a separate partition might be the better part of valor! That also will mean a lot of work but probably best.
Given the relative lack of interest in this thread by other people, it's probably prudent to try elsewhere, either forums.opensuse.org, or KDE forums.
OK, I hear you and understand... Marc...
I did have this issue some time back, not sure if 15.1 or 15.2. It's a wile ago and can't really remember how it was resolved. Fairly sure I ended up with ICE working but not KDE. I have Nvidia graphics, so went back to nouveau to take the nvidia drivers out of the equation. I think I ended up removing X11 and all graphical components in the end and reinstalling with YAST but then I also think KDE would only load without plasma.
I can't remember how I got from non-plasma to a plasma desktop again, if I changed video drivers or some other thing. Like you I was trying just about everything under the sun and eventually it came right.
Marc Chamberlin composed on 2022-06-25 15:21 (UTC-0700):
It is necessary to open an X session as a different/new user to determine whether or not the kdeinit5 issue has anything to do with user settings. That choice should be made via the GUI login greeter, whether it's SDDM, LightDM, GDM, XDM or something else available when running update-alternatives --config default-displaymanager.
Trouble is, I am not getting far enough to see the GUI login greeter. As soon as all the start up messages finish, the screen goes black, the cursor arrow is shown, and then the xbox message pops up telling me that kdeinit5 failed to start. I can then do the CTRL-ALT-F1 trick to break out and get to a simple login prompt. I can then log in to a simple text base terminal and use text commands, but there is no GUI except for things like the ncurses version of YaST2.
IIRC, this is behavior from an automatic login session failing to start. IOW, SDDM is being bypassed, so that you cannot choose to login to any other session type.
SDDM is the normal DM used with KDE installations. Did you try switching with update-alternatives --config default-displaymanager to something else (e.g. LightDM) to see if Plasma would start from it?
Yes, I tried changing the DM to LightDM and others, and got the exact same error, kdeinit5 failed to start.
Until whatever triggers automatic login gets disabled, or whatever is wrong to prevent kdeinit5 from loading, you're going to be stuck with it. Renaming /etc/sddm.conf and/or any files in /etc/sddm.conf.d/ to not end in .conf might be all that's needed. Without them the upstream defaults should give you a GUI login greeter.
Do you get the same error if you boot with a 3 appended to the linu line at the Grub menu striking the E key, then login and try:marc
WINDOWMANAGER=startplasma-x11 startx
If no joy as normal user, what about as root user, or as virgin user?
No joy with this approach either Felix, but with a slightly different behavior with root and newuser. When I login with either I get a brief flash of the xbox message about kdeinit5 not starting, followed by a blank screen with a spinning circle for awhile, then back to the screen with the xbox message.
Try instead:
WINDOWMANAGER=/usr/bin/icewm startx
Once in an IceWM session you should be able to disable automatic login either using YaST, or possibly systemsettings5 (if it doesn't require kdeinit5 to run).
On boot to login prompt, you should be able to use text mode YaST to disable automatic login.
Please show output from:
ls -Gg /etc/X11/xorg.conf.d/ cat /etc/X11/*.conf cat /etc/X11/xorg.conf.d/50*conf
On 6/25/22 15:54, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-25 15:21 (UTC-0700):
It is necessary to open an X session as a different/new user to determine whether or not the kdeinit5 issue has anything to do with user settings. That choice should be made via the GUI login greeter, whether it's SDDM, LightDM, GDM, XDM or something else available when running update-alternatives --config default-displaymanager.
Trouble is, I am not getting far enough to see the GUI login greeter. As soon as all the start up messages finish, the screen goes black, the cursor arrow is shown, and then the xbox message pops up telling me that kdeinit5 failed to start. I can then do the CTRL-ALT-F1 trick to break out and get to a simple login prompt. I can then log in to a simple text base terminal and use text commands, but there is no GUI except for things like the ncurses version of YaST2.
IIRC, this is behavior from an automatic login session failing to start. IOW, SDDM is being bypassed, so that you cannot choose to login to any other session type.
SDDM is the normal DM used with KDE installations. Did you try switching with update-alternatives --config default-displaymanager to something else (e.g. LightDM) to see if Plasma would start from it?
Yes, I tried changing the DM to LightDM and others, and got the exact same error, kdeinit5 failed to start.
Until whatever triggers automatic login gets disabled, or whatever is wrong to prevent kdeinit5 from loading, you're going to be stuck with it. Renaming /etc/sddm.conf and/or any files in /etc/sddm.conf.d/ to not end in .conf might be all that's needed. Without them the upstream defaults should give you a GUI login greeter.
Do you get the same error if you boot with a 3 appended to the linu line at the Grub menu striking the E key, then login and try:marc WINDOWMANAGER=startplasma-x11 startx If no joy as normal user, what about as root user, or as virgin user?
No joy with this approach either Felix, but with a slightly different behavior with root and newuser. When I login with either I get a brief flash of the xbox message about kdeinit5 not starting, followed by a blank screen with a spinning circle for awhile, then back to the screen with the xbox message.
Try instead:
WINDOWMANAGER=/usr/bin/icewm startx
Once in an IceWM session you should be able to disable automatic login either using YaST, or possibly systemsettings5 (if it doesn't require kdeinit5 to run).
On boot to login prompt, you should be able to use text mode YaST to disable automatic login.
Hi Felix, Found it, the ability to enable/disable automatic logins is buried in YaST2 under Security and Users > User and Group Management > Expert Options > Login Settings. Rather difficult to remember that, since I don't use it very often. Anywise I turned off Auto Login and Passwordless Logins and am now seeing the login prompt screen after a reboot. When I enter my credentials the screen goes blank and after a few seconds the Xbox with them message about the kdeinit5 failure, is shown.
Please show output from:
ls -Gg /etc/X11/xorg.conf.d/ cat /etc/X11/*.conf cat /etc/X11/xorg.conf.d/50*conf
OK HTHs...
nova:/home/marc #ls -Gg /etc/X11/xorg.conf.d/ total 56 -rw-r--r-- 1 311 Aug 17 2020 00-keyboard.conf -rw-r--r-- 1 1099 May 4 2019 10-evdev.conf -rw-r--r-- 1 489 Apr 11 02:09 10-libvnc.conf -rw-r--r-- 1 1350 Mar 21 03:14 10-quirks.conf -rw-r--r-- 1 484 May 4 2019 11-evdev.conf -rw-r--r-- 1 975 May 4 2019 40-libinput.conf -rw-r--r-- 1 529 Jul 1 2011 50-device.conf -rw-r--r-- 1 199 May 4 2019 50-elotouch.conf -rw-r--r-- 1 264 Mar 21 03:14 50-extensions.conf -rw-r--r-- 1 527 Jul 1 2011 50-monitor.conf -rw-r--r-- 1 491 Jul 1 2011 50-screen.conf -rw-r--r-- 1 1913 Aug 27 2021 70-synaptics.conf -rw-r--r-- 1 115 Mar 5 2021 70-vmmouse.conf -rw-r--r-- 1 2747 Jan 28 2019 70-wacom.conf nova:/home/marc #cat /etc/X11/*.conf cat: '/etc/X11/*.conf': No such file or directory
nova:/home/marc #cat /etc/X11/xorg.conf.d/50*conf # Having multiple "Device" sections is known to be problematic. Make # sure you don't have in use another one laying around e.g. in another # xorg.conf.d file or even a generic xorg.conf file. More details can # be found in https://bugs.freedesktop.org/show_bug.cgi?id=32430. # #Section "Device" # Identifier "Default Device" # # #Driver "radeon" # # ## Required magic for radeon/radeonhd drivers; output name # ## (here: "DVI-0") can be figured out via 'xrandr -q' # #Option "monitor-DVI-0" "Default Monitor" # #EndSection Section "InputClass" MatchProduct "Elo TouchSystems CarrollTouch 4500U|Elo TouchSystems CarrollTouch 4000U" Identifier "Elotouch" Driver "evdev" Option "Mode" "Absolute" EndSection # Add extensions to be disabled. This may be needed as some # extra modules may add extensions which cause the maximum # number of extensions possible to be exceeded. # # SUSE Default: disable DGA.
Section "Extensions" Option "XFree86-DGA" "Disable" EndSection# Having multiple "Monitor" sections is known to be problematic. Make # sure you don't have in use another one laying around e.g. in another # xorg.conf.d file or even a generic xorg.conf file. More details can # be found in https://bugs.freedesktop.org/show_bug.cgi?id=32430. # #Section "Monitor" # Identifier "Default Monitor" # # ## If your monitor doesn't support DDC you may override the # ## defaults here # #HorizSync 28-85 # #VertRefresh 50-100 # # ## Add your mode lines here, use e.g the cvt tool # #EndSection # Having multiple "Screen" sections is known to be problematic. Make # sure you don't have in use another one laying around e.g. in another # xorg.conf.d file or even a generic xorg.conf file. More details can # be found in https://bugs.freedesktop.org/show_bug.cgi?id=32430. # #Section "Screen" # Identifier "Default Screen" # # Device "Default Device" # # ## Doesn't help for radeon/radeonhd drivers; use magic in # ## 50-device.conf instead # Monitor "Default Monitor" # #EndSection
Marc Chamberlin composed on 2022-06-26 00:22 (UTC-0700):
On 6/25/22 15:54, Felix Miata wrote:
Try instead:
WINDOWMANAGER=/usr/bin/icewm startx
Once in an IceWM session you should be able to disable automatic login either using YaST, or possibly systemsettings5 (if it doesn't require kdeinit5 to run).
On boot to login prompt, you should be able to use text mode YaST to disable automatic login.
Hi Felix, Found it, the ability to enable/disable automatic logins is buried in YaST2 under Security and Users > User and Group Management > Expert Options > Login Settings. Rather difficult to remember that, since I don't use it very often. Anywise I turned off Auto Login and Passwordless Logins and am now seeing the login prompt screen after a reboot. When I enter my credentials the screen goes blank and after a few seconds the Xbox with them message about the kdeinit5 failure, is shown.
Now it should be a simple matter to run IceWM or some other session besides Plasma via selection from the login greeter, either to your regular login, or a virgin alternate user.
At this point, it might be worth using update-alternatives to switch from SDDM to LightDM, in order to ensure the kdeinit5 problem is not some failure on the part of SDDM enabling auth for the Plasma session.
Please show output from:
ls -Gg /etc/X11/xorg.conf.d/ cat /etc/X11/*.conf cat /etc/X11/xorg.conf.d/50*conf
OK HTHs...
Everything there looks normal, no suggestion of a failure point I recognize. To be sure, you could temporarily rename /etc/X11/xorg.conf.d to something else, but that looks like a seriously slim slim slim possibility. What's in there is mostly oddball stuff for antique hardware, and lots of comments (e.g. all the 2011 files).
After all the changes and switching around of packages on my system, to make it more consistent with SuSE15.3, it is interesting that I am now seeing some error messages that weren't in the system logs when I first asked my question about why kdeinit5 was failing. I don't grok these error messages but will post them here.
2022-06-26T17:43:46.428657-07:00 nova dbus-daemon[2688]: Cannot setup inotify for '/var/lib/flatpak/exports/share/dbus-1/services'; error 'Permission denied' 2022-06-26T17:43:46.429073-07:00 nova dbus-daemon[2688]: [session uid=465 pid=2688] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus- bus.service' requested by ':1.1' (uid=465 pid=2675 comm="/usr/sbin/lightdm-gtk-greeter ") 2022-06-26T17:43:46.434081-07:00 nova systemd[2656]: Starting Accessibility services bus... 2022-06-26T17:43:46.503940-07:00 nova at-spi-bus-laun[2690]: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission denied 2022-06-26T17:43:46.505275-07:00 nova dbus-daemon[2688]: [session uid=465 pid=2688] Successfully activated service 'org.a11y.Bus' 2022-06-26T17:43:46.505344-07:00 nova systemd[2656]: Started Accessibility services bus. 2022-06-26T17:43:46.579316-07:00 nova dbus-daemon[2688]: [session uid=465 pid=2688] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-d aemon.service' requested by ':1.3' (uid=465 pid=2675 comm="/usr/sbin/lightdm-gtk-greeter ")
For the Permission denied messages, the problem is caused by the following missing directory - /var/lib/flatpak/exports/ I have no idea if this is serious and what to do about it, but it does seem relevant. There are a lot of variations on this theme -
2022-06-26T17:44:14.650219-07:00 nova systemd[2774]: Started D-Bus User Message Bus. 2022-06-26T17:44:14.665395-07:00 nova dbus-daemon[2793]: Cannot setup inotify for '/var/lib/flatpak/exports/share/dbus-1/services'; error 'Permission deni ed' 2022-06-26T17:44:16.663255-07:00 nova ksplashqml[2841]: QCoreApplication::arguments: Please instantiate the QApplication object first 2022-06-26T17:44:16.687200-07:00 nova startplasma-x11[2782]: "/usr/lib64/libexec/kf5/start_kdeinit_wrapper" ("--kded", "+kcminit_startup") exited with cod e 127 2022-06-26T17:44:17.063971-07:00 nova dbus-daemon[2793]: [session uid=1000 pid=2793] Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs- daemon.service' requested by ':1.4' (uid=1000 pid=2851 comm="ibus-daemon --xim -d ") 2
2022-06-26T17:44:17.617632-07:00 nova dbus-daemon[2793]: [session uid=1000 pid=2793] Activating via systemd: service name='org.a11y.Bus' unit='at-spi-dbus -bus.service' requested by ':1.12' (uid=1000 pid=2879 comm="/usr/lib64/ibus/ibus-x11 --kill-daemon ") 2022-06-26T17:44:17.618935-07:00 nova systemd[2774]: Starting Accessibility services bus... 2022-06-26T17:44:17.622225-07:00 nova at-spi-bus-laun[2893]: Unable to open /var/lib/flatpak/exports/share/dconf/profile/user: Permission denied 2022-06-26T17:44:17.623407-07:00 nova dbus-daemon[2793]: [session uid=1000 pid=2793] Successfully activated service 'org.a11y.Bus' 2022-06-26T17:44:17.623491-07:00 nova systemd[2774]: Started Accessibility services bus.
HTHs Marc...
On 2022-06-26 00:21, Marc Chamberlin wrote:
On 6/24/22 22:12, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-24 20:22 (UTC-0700):
It is necessary to open an X session as a different/new user to determine whether or not the kdeinit5 issue has anything to do with user settings. That choice should be made via the GUI login greeter, whether it's SDDM, LightDM, GDM, XDM or something else available when running update-alternatives --config default-displaymanager.
Trouble is, I am not getting far enough to see the GUI login greeter. As soon as all the start up messages finish, the screen goes black, the cursor arrow is shown, and then the xbox message pops up telling me that kdeinit5 failed to start. I can then do the CTRL-ALT-F1 trick to break out and get to a simple login prompt. I can then log in to a simple text base terminal and use text commands, but there is no GUI except for things like the ncurses version of YaST2.
Try ctrl-alt-backspace, twice.
...
On 19/06/2022 23.34, Marc Chamberlin wrote:
On 6/19/22 12:57, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-19 12:38 (UTC-0700):
...
You should do some repo maintenance. You have a bunch of optional repos. Those pointing to 15.2 should be removed or switched to 15.3. Those you aren't sure you need, disable or remove.
I disabled the Bacula 15.2 repo which does not have a 15.3 version available, and a few other not so important repos that I will need eventually.
Once that's done, let's see output of the following command:
zypper se -si | grep 'tem Pac' | grep -v plication
OK, here you go, kinda long and wraps every line, sorry!
nova:/home/marc #zypper se -si | grep 'tem Pac' | grep -v plication i+ | awesfx | package | 0.5.2-lp153.117.1 | x86_64 | (System Packages) i+ | bacula-client | package | 11.0.6-lp152.1.1 | x86_64 | (System Packages)
You have many 15.2 packages. You have to list them all and upgrade them all to 15.3.
This command will list them all:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE Leap 15.3|openSUSE_Leap_15.3|-lp153|SUSE Linux Enterprise 15" | less -S
Also, check your home partition is not full.
On 25/06/2022 17:39, Carlos E. R. wrote:
On 19/06/2022 23.34, Marc Chamberlin wrote:
On 6/19/22 12:57, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-19 12:38 (UTC-0700):
...
You should do some repo maintenance. You have a bunch of optional repos. Those pointing to 15.2 should be removed or switched to 15.3. Those you aren't sure you need, disable or remove.
I disabled the Bacula 15.2 repo which does not have a 15.3 version available, and a few other not so important repos that I will need eventually.
Once that's done, let's see output of the following command:
zypper se -si | grep 'tem Pac' | grep -v plication
OK, here you go, kinda long and wraps every line, sorry!
nova:/home/marc #zypper se -si | grep 'tem Pac' | grep -v plication i+ | awesfx | package | 0.5.2-lp153.117.1 | x86_64 | (System Packages) i+ | bacula-client | package | 11.0.6-lp152.1.1 | x86_64 | (System Packages)
You have many 15.2 packages. You have to list them all and upgrade them all to 15.3.
This command will list them all:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE Leap 15.3|openSUSE_Leap_15.3|-lp153|SUSE Linux Enterprise 15" | less -S
Also, check your home partition is not full.
Do the system logs show anything when your ssh login fails. Does running without the firewall make any difference.
On 6/24/22 23:07, Steve Edmonds wrote:
On 25/06/2022 17:39, Carlos E. R. wrote:
On 19/06/2022 23.34, Marc Chamberlin wrote:
On 6/19/22 12:57, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-19 12:38 (UTC-0700):
...
You should do some repo maintenance. You have a bunch of optional repos. Those pointing to 15.2 should be removed or switched to 15.3. Those you aren't sure you need, disable or remove.
I disabled the Bacula 15.2 repo which does not have a 15.3 version available, and a few other not so important repos that I will need eventually.
Once that's done, let's see output of the following command:
zypper se -si | grep 'tem Pac' | grep -v plication
OK, here you go, kinda long and wraps every line, sorry!
nova:/home/marc #zypper se -si | grep 'tem Pac' | grep -v plication i+ | awesfx | package | 0.5.2-lp153.117.1 | x86_64 | (System Packages) i+ | bacula-client | package | 11.0.6-lp152.1.1 | x86_64 | (System Packages)
You have many 15.2 packages. You have to list them all and upgrade them all to 15.3.
This command will list them all:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE Leap 15.3|openSUSE_Leap_15.3|-lp153|SUSE Linux Enterprise 15" | less -S
Also, check your home partition is not full.
Do the system logs show anything when your ssh login fails.
Hi Steve, and thanks for your thoughts/reply. I am going to change the name of this thread since my Firewall issues are separate from the kdeinit5 issues (I think...)
I don't see any messages in the log files that get generated when I attempt to SSH into my system and it fails. I am still looking around but no joy. .
Does running without the firewall make any difference.
Yes, stopping the firewalld service does allow me to then connect to services such as SSH and VNC. That indicates this is a firewall issue.
A couple of checks I made, while the firewalld service is running, are interesting in that they seem to show nothing is wrong -
firewall-cmd --list-all --zone=internal
internal (active) target: default icmp-block-inversion: no interfaces: eth0 sources: services: apache2 apache2-ssl bacula-client dhcpv6-client http https kdeconnect mdns nfs nfs3 rpc-bind samba samba-client slp smtp smtp-submission smtps ssh tigervnc vnc-server x11 ports: 5900-5910/tcp 3052/tcp protocols: forward: no masquerade: no forward-ports: source-ports: icmp-blocks: rich rules:
netstat -tulpn | grep LISTEN
tcp 0 0 0.0.0.0:5900 0.0.0.0:* LISTEN 3028/x11vnc tcp 0 0 127.0.0.1:3310 0.0.0.0:* LISTEN 2582/clamd tcp 0 0 0.0.0.0:9102 0.0.0.0:* LISTEN 2185/bacula-fd tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 1/systemd tcp 0 0 0.0.0.0:20048 0.0.0.0:* LISTEN 2218/rpc.mountd tcp 0 0 192.168.10.20:22 0.0.0.0:* LISTEN 2256/sshd: /usr/sbi tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 1103/cupsd tcp 0 0 127.0.0.1:31416 0.0.0.0:* LISTEN 2170/boinc tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2260/sendmail: acce tcp 0 0 127.0.0.1:445 0.0.0.0:* LISTEN 2812/smbd tcp 0 0 192.168.10.20:445 0.0.0.0:* LISTEN 2812/smbd tcp 0 0 10.10.10.1:445 0.0.0.0:* LISTEN 2812/smbd tcp 0 0 0.0.0.0:37729 0.0.0.0:* LISTEN - tcp 0 0 0.0.0.0:2049 0.0.0.0:* LISTEN - tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 2323/mysqld tcp 0 0 127.0.0.1:139 0.0.0.0:* LISTEN 2812/smbd tcp 0 0 192.168.10.20:139 0.0.0.0:* LISTEN 2812/smbd tcp 0 0 10.10.10.1:139 0.0.0.0:* LISTEN 2812/smbd tcp 0 0 0.0.0.0:35275 0.0.0.0:* LISTEN 2239/rpc.statd tcp6 0 0 :::5900 :::* LISTEN 3028/x11vnc tcp6 0 0 :::3052 :::* LISTEN 2228/java tcp6 0 0 :::111 :::* LISTEN 1/systemd tcp6 0 0 :::80 :::* LISTEN 2230/httpd-prefork tcp6 0 0 :::20048 :::* LISTEN 2218/rpc.mountd tcp6 0 0 ::1:631 :::* LISTEN 1103/cupsd tcp6 0 0 :::443 :::* LISTEN 2230/httpd-prefork tcp6 0 0 ::1:445 :::* LISTEN 2812/smbd tcp6 0 0 127.0.0.1:53566 :::* LISTEN 2228/java tcp6 0 0 :::53568 :::* LISTEN 2228/java tcp6 0 0 :::2049 :::* LISTEN - tcp6 0 0 :::38211 :::* LISTEN - tcp6 0 0 :::49195 :::* LISTEN 2239/rpc.statd tcp6 0 0 ::1:139 :::* LISTEN 2812/smbd
HTHs Marc..
On 6/24/22 22:39, Carlos E. R. wrote:
On 19/06/2022 23.34, Marc Chamberlin wrote:
On 6/19/22 12:57, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-19 12:38 (UTC-0700):
...
You should do some repo maintenance. You have a bunch of optional repos. Those pointing to 15.2 should be removed or switched to 15.3. Those you aren't sure you need, disable or remove.
I disabled the Bacula 15.2 repo which does not have a 15.3 version available, and a few other not so important repos that I will need eventually.
Once that's done, let's see output of the following command:
zypper se -si | grep 'tem Pac' | grep -v plication
OK, here you go, kinda long and wraps every line, sorry!
nova:/home/marc #zypper se -si | grep 'tem Pac' | grep -v plication i+ | awesfx | package | 0.5.2-lp153.117.1 | x86_64 | (System Packages) i+ | bacula-client | package | 11.0.6-lp152.1.1 | x86_64 | (System Packages)
You have many 15.2 packages. You have to list them all and upgrade them all to 15.3.
This command will list them all:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE Leap 15.3|openSUSE_Leap_15.3|-lp153|SUSE Linux Enterprise 15" | less -S
Thanks Carlos, that is quite the incantation for figuring out what packages from previous versions are hanging around! Much appreciate your taking the time to put that together for me. I used it to remove all the packages left from OpenSuSE15.2 and the following shows what is the output now from your magic. I dunno what to do about gpg-pubkey, YaST2 only shows it as being provided from openSUSE-release - openSUSE Leap 15.3and I don't think I want to remove that package. There are a couple other packages shown which I acquired from outside repositories and I do want to keep those.
Mon Aug 17 2020 Thu Mar 15 2018 gpg-pubkey 307e3d54-5aaa90a5 (none) (none)SuSE Package Signing Key build@suse.de == (none) (none) Mon Aug 17 2020 Mon May 05 2014 gpg-pubkey 3dbdc284-53674dd4 (none) (none)openSUSE Project Signing Key opensuse@opensuse.org == (none) (none) Wed Aug 26 2020 Wed Mar 09 2011 gpg-pubkey 6867f5be-4d77cecd (none) (none)Martin Schlander (cb400f) martin.schlander@gmail.com == (none) (none) Wed Aug 26 2020 Mon Sep 15 2014 gpg-pubkey 1abd1afb-54176598 (none) (none)PackMan Project (signing key) packman@links2linux.de == (none) (none) Sun Oct 04 2020 Mon Aug 05 2019 gpg-pubkey ba86df65-5d488f60 (none) (none)home:wmerriam OBS Project home:wmerriam@build.opensuse.org == (none) (none) Thu Nov 12 2020 Wed Feb 26 2020 gpg-pubkey 85eac349-5e56eb52 (none) (none)home:cristyde OBS Project home:cristyde@build.opensuse.org == (none) (none) Sun Dec 06 2020 Sat Oct 31 2020 gpg-pubkey ed340235-5f9d97fb (none) (none)system:snappy OBS Project system:snappy@build.opensuse.org == (none) (none) Tue Dec 29 2020 Sun Dec 27 2020 gpg-pubkey ee3d166a-5fe932a4 (none) (none)security OBS Project security@build.opensuse.org == (none) (none) Tue Jan 12 2021 Tue Jan 12 2021 gpg-pubkey 31542ea9-5ffdfcc4 (none) (none)home:Lord-Master OBS Project home:Lord-Master@build.opensuse.org == (none) (none) Sat Apr 03 2021 Sun Mar 28 2021 zoom 5.6.13632.0328_openSUSE-1 x86_64 Zoom Video Communications, Inc.Zoom Linux Team linux-dev@zoom.us == (none) (none) Tue Jul 06 2021 Fri Jun 18 2021 gpg-pubkey 3094d053-60cd79c0 (none) (none)home:simotek OBS Project home:simotek@build.opensuse.org == (none) (none) Sun Jan 02 2022 Sun Sep 05 2021 gpg-pubkey 8b662dfb-61347fd3 (none) (none)home:ecsos OBS Project home:ecsos@build.opensuse.org == (none) (none) Fri Feb 11 2022 Mon Sep 21 2020 gpg-pubkey 39db7c82-5f68629b (none) (none)SuSE Package Signing Key build@suse.de == (none) (none) Fri Feb 11 2022 Fri Nov 26 2021 gpg-pubkey 65176565-61a0ee8f (none) (none)openSUSE:Backports OBS Project openSUSE:Backports@build.opensuse.org == (none) (none) Mon Mar 28 2022 Thu Mar 10 2022 bacula-client 11.0.6-lp152.1.1 x86_64 obs://build.opensuse.org/home:cristyde (none) == home:cristyde / openSUSE_Leap_15.2 (none) Mon Mar 28 2022 Thu Mar 10 2022 bacula-common 11.0.6-lp152.1.1 x86_64 obs://build.opensuse.org/home:cristyde (none) == home:cristyde / openSUSE_Leap_15.2 (none) Mon Mar 28 2022 Thu Mar 10 2022 bacula-console 11.0.6-lp152.1.1 x86_64 obs://build.opensuse.org/home:cristyde (none) == home:cristyde / openSUSE_Leap_15.2 (none) Wed Mar 30 2022 Wed Mar 30 2022 gpg-pubkey f23c6aa3-624437f7 (none) (none)multimedia OBS Project multimedia@build.opensuse.org == (none) (none) Wed Mar 30 2022 Mon Jan 11 2021 gpg-pubkey 95e6d72b-5ffc6754 (none) (none)home:Monex OBS Project home:Monex@build.opensuse.org == (none) (none) Tue Apr 26 2022 Sat Apr 23 2022 gpg-pubkey 3a243fa3-6264ddf6 (none) (none)home:GNorth OBS Project home:GNorth@build.opensuse.org == (none) (none) Sat Jun 04 2022 Sun Jan 23 2022 gpg-pubkey d2722ae2-61ee5a68 (none) (none)home:michalsrb2 OBS Project home:michalsrb2@build.opensuse.org == (none) (none)
Also, check your home partition is not full.
No, my home partition is not full -
marc@nova:~> df Filesystem 1K-blocks Used Available Use% Mounted on devtmpfs 4096 0 4096 0% /dev tmpfs 8110664 0 8110664 0% /dev/shm tmpfs 3244268 10296 3233972 1% /run tmpfs 4096 0 4096 0% /sys/fs/cgroup /dev/sdb2 51343840 18536596 30169420 39% / /dev/sda3 596354848 15844272 580510576 3% /MediaCenter /dev/sda1 511996 31808 480188 7% /Windows_C /dev/sda2 113604604 43098040 70506564 38% /Windows_D /dev/sdc1 7751334644 88497620 7272120952 2% /MediaSecurity /dev/sdb4 205375464 19319916 175553404 10% /home /dev/sdb1 50311712 24293636 23432684 51% /SuSE15.1 /dev/sdb5 51343840 21629228 27076788 45% /srv /dev/sdb7 1055840692 114110340 888026880 12% /DataFiles /dev/sdb3 51343840 53284 48652732 1% /extraPartition tmpfs 1622132 52 1622080 1% /run/user/1000
And finally, still no joy getting my system to boot up, start SDDM, and launch my plasma/KDE desktop properly. Still won't start kdeinit5....
HTHs, Marc..
On 2022-06-25 23:36, Marc Chamberlin wrote:
On 6/24/22 22:39, Carlos E. R. wrote:
On 19/06/2022 23.34, Marc Chamberlin wrote:
On 6/19/22 12:57, Felix Miata wrote:
Marc Chamberlin composed on 2022-06-19 12:38 (UTC-0700):
...
nova:/home/marc #zypper se -si | grep 'tem Pac' | grep -v plication i+ | awesfx | package | 0.5.2-lp153.117.1 | x86_64 | (System Packages) i+ | bacula-client | package | 11.0.6-lp152.1.1 | x86_64 | (System Packages)
You have many 15.2 packages. You have to list them all and upgrade them all to 15.3.
This command will list them all:
rpm -q -a --queryformat "%{INSTALLTIME}\t%{INSTALLTIME:day} \ %{BUILDTIME:day} %-30{NAME}\t%15{VERSION}-%-7{RELEASE}\t%{arch} \ %25{VENDOR}%25{PACKAGER} == %{DISTRIBUTION} %{DISTTAG}\n" \ | sort | cut --fields="2-" | tee rpmlist \ | egrep -v "openSUSE Leap 15.3|openSUSE_Leap_15.3|-lp153|SUSE Linux Enterprise 15" | less -S
Thanks Carlos, that is quite the incantation for figuring out what packages from previous versions are hanging around! Much appreciate your taking the time to put that together for me.
LOL, no! I concocted that one long ago and wrote it out in my "howto" text file of recipes ;-D
I used it to remove all the packages left from OpenSuSE15.2 and the following shows what is the output now from your magic. I dunno what to do about gpg-pubkey,
Those are safe.
YaST2 only shows it as being provided from openSUSE-release - openSUSE Leap 15.3and I don't think I want to remove that package. There are a couple other packages shown which I acquired from outside repositories and I do want to keep those.
Try to find their current versions for 15.3
...
Also, check your home partition is not full.
No, my home partition is not full -
Well, it was a shot.
..
And finally, still no joy getting my system to boot up, start SDDM, and launch my plasma/KDE desktop properly. Still won't start kdeinit5....
Sigh.
-
Carlos E. R. -
Felix Miata -
Marc Chamberlin -
Patrick Shanahan -
Steve Edmonds