OpenSUSE Tumbleweed KDE not loading

English Applications
#1

Hi folks,

After python package installation on openSUSE Tumbleweed GUI stop working.
After the system reboot an unusual login GUI ask me for authentication.Even providing the right ones,
I got the error:** “Failed to start section”.**

With CTRL + ALT + F1 I’m able to access the terminal with the same credentials mentioned above.
The *CLI *work just fine. However the output for commands such as dolphin . is zsh: command not found: dolphin.
That’s the output for the command

inxi -G --display:

Graphics: 
 Device-1: Advanced Micro Devices [AMD/ATI] Picasso driver: amdgpu v:
 kernel             Display: x11 server: X.Org 1.20.8 driver: amdgpu, ati unloaded: fbdev,modesetting,vesa
             Message: No advanced graphics data found on this system.

screenfetch output:

OS: openSUSE 2020 05 15
Kernel: x86_64 Linux 5.6.12-1-
defaultUptime: 39m
Packages: 2602
Shell: zsh 5.8
Disk: 967G / 1.2T (80%)
CPU: AMD Ryzen 5 3500U with Radeon Vega Mobile Gfx @ 8x 2.1GHz
GPU:
RAM: 802MiB / 5846 MiB

Things I already tried
zypper update, refresh, dup
zypper in xf86-video-intel
zypper fresh install
zypper in purge-kernels
sudo passwd: new one

#2

Hi, welcome,

  1. On TW you should use ‘zypper dup’ ( no up, refresh happens automagically with dup )
    the intel video driver is of no use, you have an AMD + Radeon
    the other commands are neither to be expected to have some effect here.

Are you on btrfs? If so, run


sudo snapper list

and remember the last snapshot number before installing the python packages.
then


sudo snapper rollback ####

where #### is that last snapshotnumber

Also, show


zypper lr -d
#3

Hi Knurpht, I apologize for the delay and really appreciate your answer.
Thanks for your clarification.

As you can see I’m a newbie on Linux world and more precisely on openSUSE TW one.

Well, yes I’m on btrfs.

Here is the output for:



sudo snapper list:

      |-----+--------+-------+---------------------------------+------+---------+-----------------------+--------------|
|---|
|


|  0  | single |       |                                 | root |         | current               |              |
|---|---|---|---|---|---|---|---|
|


|519  | single |       | Sat 16 May 2020 10:25:43 PM -03 | root | number  | rollback backup of #1 | important=yes|
|---|---|---|---|---|---|---|---|
|


|521  | single |       | Sat 16 May 2020 10:28:40 PM -03 | root | number  | first root filesystem | important=yes|
|---|---|---|---|---|---|---|---|
|


|522* | single |       | Sat 16 May 2020 10:28:40 PM -03 | root |         | first root filesystem |              |
|---|---|---|---|---|---|---|---|
|


|523  | pre    |       | Sat 16 May 2020 11:59:51 PM -03 | root | number  | zypp(zypper)          | important=yes|
|---|---|---|---|---|---|---|---|
|


|524  | post   |   523 | Sun 17 May 2020 12:02:55 AM -03 | root | number  |                       | important=yes|
|---|---|---|---|---|---|---|---|
|


|527  | single |       | Sun 17 May 2020 02:16:31 PM -03 | root |         |                       |              |
|---|---|---|---|---|---|---|---|
|


|532  | pre    |       | Wed 20 May 2020 09:49:53 AM -03 | root | number  | zypp(zypper)          | important=no |
|---|---|---|---|---|---|---|---|
|


533  | post   |   532 | Wed 20 May 2020 10:09:38 AM -03 | root | number  |                       | important=no |# | Type   | Pre # | Date                            | User | Cleanup | Description           | Userdata     |
|---|---|---|---|---|---|---|---|
|

All the dates here are from the week that the issue happens. I’ve already blindly and unsuccessfully tried the rollback alternative.
I’m not sure if I messed the things up, but I have never saved snapshots file system before, so those dates make sense.

That said, simply does not make sense **rollback **to the last dated snapshot :frowning:

the output for



zypper lr -d|#  | Alias                                | Name                           | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                                                               | Service
|---|---|---|---|---|---|---|---|---|
|
|


|---+--------------------------------------+--------------------------------+---------+-----------+---------+----------+--------+---------------------------------------------------------------------------------------------------+--------|
|---|
|


| 1 | Google-Chrome                        | Google-Chrome                  | Yes     | (r ) Yes  | No      |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                                               | |
|---|---|---|---|---|---|---|---|---|---|
|


| 2 | KDE-Applications                     | KDE-Applications               | Yes     | (r ) Yes  | No      |   75     | rpm-md | https://download.opensuse.org/repositories/KDE:/Applications/KDE_Frameworks5_openSUSE_Tumbleweed/ | |
|---|---|---|---|---|---|---|---|---|---|
|


| 3 | KDE-Frameworks                       | KDE-Frameworks                 | Yes     | (r ) Yes  | No      |   75     | rpm-md | https://download.opensuse.org/repositories/KDE:/Frameworks5/openSUSE_Factory/                     | |
|---|---|---|---|---|---|---|---|---|---|
|


| 4 | KDE-Qt5                              | KDE-Qt5                        | Yes     | (r ) Yes  | No      |   75     | rpm-md | https://download.opensuse.org/repositories/KDE:/Qt5/openSUSE_Factory/                             | |
|---|---|---|---|---|---|---|---|---|---|
|


| 5 | adobe                                | adobe                          | Yes     | ( p) Yes  | Yes     |   99     | rpm-md | http://linuxdownload.adobe.com/linux/x86_64/                                                      | |
|---|---|---|---|---|---|---|---|---|---|
|


| 6 | code                                 | Visual Studio Code             | Yes     | (r ) Yes  | No      |   99     | rpm-md | https://packages.microsoft.com/yumrepos/vscode                                                    | |
|---|---|---|---|---|---|---|---|---|---|
|


| 7 | dvd                                  | dvd                            | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://opensuse-guide.org/repo/13.2/                                                              | |
|---|---|---|---|---|---|---|---|---|---|
|


| 8 | google-chrome                        | google-chrome                  | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64                                               | |
|---|---|---|---|---|---|---|---|---|---|
|


| 9 | http-download.opensuse.org-092ce705  | openSUSE:Factory               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/openSUSE:/Factory/snapshot/                             | |
|---|---|---|---|---|---|---|---|---|---|
|


|10 | http-download.opensuse.org-1e10a4bc  | openSUSE:Tumbleweed            | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/openSUSE:/Tumbleweed/standard/                          | |
|---|---|---|---|---|---|---|---|---|---|
|


|11 | http-download.opensuse.org-2cbd93c7  | devel:languages:haskell:lts:13 | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/devel:/languages:/haskell:/lts:/13/openSUSE_Leap_15.1/  | |
|---|---|---|---|---|---|---|---|---|---|
|


|12 | http-download.opensuse.org-84ca802d  | home:cabelo                    | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/home:/cabelo/openSUSE_Tumbleweed/                       | |
|---|---|---|---|---|---|---|---|---|---|
|


|13 | http-download.opensuse.org-957423dc  | server:database                | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/server:/database/openSUSE_Tumbleweed/                   | |
|---|---|---|---|---|---|---|---|---|---|
|


|14 | http-download.opensuse.org-a8779bfe  | system:packagemanager          | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/system:/packagemanager/openSUSE_Tumbleweed/             | |
|---|---|---|---|---|---|---|---|---|---|
|


|15 | http-download.opensuse.org-b888aba0  | home:darthzen:arduino          | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/repositories/home:/darthzen:/arduino/openSUSE_Tumbleweed/            | |
|---|---|---|---|---|---|---|---|---|---|
|


|16 | openSUSE-20190907-0                  | openSUSE-20190907-0            | No      | ----      | ----    |   99     | rpm-md | hd:/?device=/dev/disk/by-id/usb-Kingston_DataTraveler_3.0_80C5F260FAC2E311686F1AD8-0:0-part2      | |
|---|---|---|---|---|---|---|---|---|---|
|


|17 | packman                              | packman                        | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://ftp.gwdg.de/pub/linux/packman/suse/openSUSE_13.2/                                          | |
|---|---|---|---|---|---|---|---|---|---|
|


|18 | packman.inode.at-openSUSE_Tumbleweed | Packman Repository             | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://packman.inode.at/suse/openSUSE_Tumbleweed/                                                 | |
|---|---|---|---|---|---|---|---|---|---|
|


|19 | repo-debug                           | openSUSE-Tumbleweed-Debug      | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/tumbleweed/repo/oss/                                           | |
|---|---|---|---|---|---|---|---|---|---|
|


|20 | repo-non-oss                         | openSUSE-Tumbleweed-Non-Oss    | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/                                             | |
|---|---|---|---|---|---|---|---|---|---|
|


|21 | repo-oss                             | openSUSE-Tumbleweed-Oss        | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/                                                 | |
|---|---|---|---|---|---|---|---|---|---|
|


|22 | repo-source                          | openSUSE-Tumbleweed-Source     | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/tumbleweed/repo/oss/                                          | |
|---|---|---|---|---|---|---|---|---|---|
|


|23 | repo-update                          | openSUSE-Tumbleweed-Update     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/update/tumbleweed/                                                   | |
|---|---|---|---|---|---|---|---|---|---|
|


24 | snappy                               |  snappy                         | Yes     | (r ) Yes  | Yes     |   99      | rpm-md |  https://download.opensuse.org/repositories/system:/snappy/openSUSE_Leap_15.0                       | |sudo zypper lr -d|
|---|
|

Any thoughts?

~ Best wishes.

#4

Your attempts to salvage the system created additional snapshots, which forced the older, working snapshots to be cleaned up by snapper. I suppose snapshots #519,521 are only broken copies from #1. Next time, remember to find a working snapshot before attempting the rollback, by booting from a read-only snapshot from the grub menu.

You added repositories that would cause to break the system, that’s for sure.

  • repo-*: that’s the default repositories for tumbleweed, mainly repo-oss and repo-update, and if you want non-OSS software then the repo-non-oss as well.
  • 3 KDE/Qt repositories: tumbleweed has quite fresh versions of these packages already, unless you develop for that, remove them.
  • 2 google chrome repos: remove at least 1 of them.
  • 4 repos mention a version (13.2, 15.0, 15.1), it means it’s for Leap, not Tumbleweed. Get rid of them: packman’s, snappy, dvd, haskell.
  • Remove the installation media repository: openSUSE-20190907-0
  • http-download.*: remove all of them
  • adobe repo returns 404
  • VS code it’s fine to keep

Now run

zypper dup --allow-vendor-change

Hopefully it would bring back stable version of packages.

Reboot and see if the desktop is back.

Next run

zypper pa --orphaned

This is a list of installed packages that can’t receive updates, because the origin repository is gone. zypper rm packages you don’t need.

As for the other repositories, follow the procedure for packman and others, always picking the tumbleweed version, and never adding a “Factory” repository.

Good luck.

#5

Thoughts: Having these home: and KDE/QT repos are the cause. TW already has the latest tested KDE/Plasma and QT versions. Remove those KDE related repos, run


sudo zypper dup --allow-vendor-change

and my bet is KDE will start again.

#6

Hi guys, thanks for your hints.
The problem persists, but now I have a better understands of TW.

I’ve removed all the mentioned packages.
Here is the output for:



sudo lr -d

      |--+---------------+-----------------------------+---------+-----------+---------+----------+--------+----------------------------------------------------------+--------|
|---|
|


|1 | code          | Visual Studio Code          | Yes     | (r ) Yes  | No      |   99     | rpm-md | https://packages.microsoft.com/yumrepos/vscode           ||
|---|---|---|---|---|---|---|---|---|---|
|


|2 | google-chrome | google-chrome               | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://dl.google.com/linux/chrome/rpm/stable/x86_64      ||
|---|---|---|---|---|---|---|---|---|---|
|


|3 | repo-debug    | openSUSE-Tumbleweed-Debug   | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/debug/tumbleweed/repo/oss/  ||
|---|---|---|---|---|---|---|---|---|---|
|


|4 | repo-non-oss  | openSUSE-Tumbleweed-Non-Oss | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/non-oss/    ||
|---|---|---|---|---|---|---|---|---|---|
|


|5 | repo-oss      | openSUSE-Tumbleweed-Oss     | Yes     | (r ) Yes  | Yes     |   99     | rpm-md | http://download.opensuse.org/tumbleweed/repo/oss/        ||
|---|---|---|---|---|---|---|---|---|---|
|


|6 | repo-source   | openSUSE-Tumbleweed-Source  | No      | ----      | ----    |   99     | NONE   | http://download.opensuse.org/source/tumbleweed/repo/oss/ ||
|---|---|---|---|---|---|---|---|---|---|
|


7 | repo-update   |  openSUSE-Tumbleweed-Update  | Yes     | (r ) Yes  | Yes     |   99     |  rpm-md | http://download.opensuse.org/update/tumbleweed/          | |# | Alias         | Name                        | Enabled | GPG Check | Refresh | Priority | Type   | URI                                                      | Service|
|---|---|---|---|---|---|---|---|---|---|
|

awerlang, here is the output for



zypper pa --orphaned


      |Reading installed packages...|
|---|
|


|S  | Repository | Name                              | Version                   | Arch|
|---|---|---|---|---|
|


|---+------------+-----------------------------------+---------------------------+-------|
|---|
|


|i+ | @System    | adobe-release-x86_64              | 1.0-1                     | noarch|
|---|---|---|---|---|
|


|i+ | @System    | alien                             | 8.88-2.25                 | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | flash-player                      | 32.0.0.363-1.1            | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | flash-player-gnome                | 32.0.0.363-1.1            | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | flash-player-ppapi                | 32.0.0.371-release        | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | flash-plugin                      | 32.0.0.371-release        | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | gstreamer-plugins-ugly-orig-addon | 1.16.2-6.11               | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | intellij-idea-community-edition   | 2017.3-9.7                | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libdca0                           | 0.0.7-1.1                 | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libdvdcss2                        | 1.2.13-5.1                | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libfaad2                          | 2.9.1-1.3                 | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libfdk-aac1                       | 0.1.5-1.1                 | x86_64|
|---|---|---|---|---|
|


|i  | @System    | libicu66                          | 66.1-1.1                  | x86_64|
|---|---|---|---|---|
|


|i  | @System    | libicu66-ledata                   | 66.1-1.1                  | noarch|
|---|---|---|---|---|
|


|i+ | @System    | libopencore-amrnb0                | 0.1.5-1.42                | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libopencore-amrwb0                | 0.1.5-1.42                | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | librtmp1                          | 2.4.20151223.fa8646d-1.44 | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libvo-amrwbenc0                   | 0.1.3-1.30                | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libx264-148                       | 0.148svn20161219-5.1      | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libx264-155                       | 0.155svn20190201-3.2      | x86_64|
|---|---|---|---|---|
|


|i  | @System    | libx264-157                       | 0.157svn20191217-1.1      | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libx265-102                       | 2.2-1.1                   | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libx265-176                       | 3.1.2-1.3                 | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libx265-179                       | 3.2.1-3.10                | x86_64|
|---|---|---|---|---|
|


|i  | @System    | libx265-188                       | 3.3-1.3                   | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | libxvidcore4                      | 1.3.5-2.22                | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | mtpfs                             | 1.1-3.64                  | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | ocenaudio                         | 3.7.9-1.opensuse          | x86_64|
|---|---|---|---|---|
|


|i+ | @System    | openSUSE-release-dvd              | 20190907-247.1            | x86_64|
|---|---|---|---|---|
|


i+ | @System    | snapd                             | 2.44.5-lp150.1.1          | x86_64|Loading repository data...|
|---|
|
#7

For you both, after sudo zypper dup --allow-vendor-change
the following message is displayed:

there are running programs which still use files from libraries deleted or updated by recent upgrades. They should be restarted to benefit from the
latest updates. Run ‘zypper ps -s’ to list these programs.

The output for



sudo zypper ps -s
      ||
|---|
|


|PID  | PPID | UID  | User       | Command             | Service|
|---|---|---|---|---|---|
|


|-----+------+------+------------+---------------------+-----------------|
|---|
|


|1    | 0    | 0    | root       | systemd             ||
|---|---|---|---|---|---|
|


|535  | 1    | 0    | root       | systemd-journald    | systemd-journald|
|---|---|---|---|---|---|
|


|549  | 1    | 0    | root       | systemd-udevd       | systemd-udevd|
|---|---|---|---|---|---|
|


|1335 | 1    | 498  | avahi      | avahi-daemon        | avahi-daemon|
|---|---|---|---|---|---|
|


|1337 | 1    | 499  | messagebus | dbus-daemon         | dbus|
|---|---|---|---|---|---|
|


|1351 | 1    | 473  | polkitd    | polkitd             | polkit|
|---|---|---|---|---|---|
|


|1355 | 1    | 0    | root       | smartd              | smartd|
|---|---|---|---|---|---|
|


|1363 | 1    | 469  | nscd       | nscd                | nscd|
|---|---|---|---|---|---|
|


|1503 | 1    | 0    | root       | bluetoothd          | bluetooth|
|---|---|---|---|---|---|
|


|1504 | 1    | 0    | root       | systemd-logind      | systemd-logind|
|---|---|---|---|---|---|
|


|1505 | 1    | 0    | root       | ModemManager        | ModemManager|
|---|---|---|---|---|---|
|


|1506 | 1    | 0    | root       | python3.8           | firewalld|
|---|---|---|---|---|---|
|


|1514 | 1    | 0    | root       | NetworkManager      | NetworkManager|
|---|---|---|---|---|---|
|


|1530 | 1    | 0    | root       | cupsd               | cups|
|---|---|---|---|---|---|
|


|1531 | 1    | 0    | root       | dockerd             | docker|
|---|---|---|---|---|---|
|


|1763 | 1    | 0    | root       | wpa_supplicant      | wpa_supplicant|
|---|---|---|---|---|---|
|


|2054 | 1    | 0    | root       | login               ||
|---|---|---|---|---|---|
|


|2099 | 1    | 0    | root       | accounts-daemon     | accounts-daemon|
|---|---|---|---|---|---|
|


|2104 | 2094 | 0    | root       | Xorg                | display-manager|
|---|---|---|---|---|---|
|


|2128 | 2094 | 0    | root       | lightdm             ||
|---|---|---|---|---|---|
|


|2139 | 1    | 460  | lightdm    | systemd             ||
|---|---|---|---|---|---|
|


|2140 | 2139 | 460  | lightdm    | systemd             ||
|---|---|---|---|---|---|
|


|2148 | 2128 | 460  | lightdm    | lightdm-gtk-greeter ||
|---|---|---|---|---|---|
|


|2165 | 2139 | 460  | lightdm    | dbus-daemon         ||
|---|---|---|---|---|---|
|


|2171 | 2166 | 460  | lightdm    | dbus-daemon         ||
|---|---|---|---|---|---|
|


|2192 | 2094 | 0    | root       | lightdm             | display-manager|
|---|---|---|---|---|---|
|


|2195 | 2139 | 460  | lightdm    | at-spi2-registryd   ||
|---|---|---|---|---|---|
|


|2214 | 1    | 1000 | drawbridge | systemd             ||
|---|---|---|---|---|---|
|


|2216 | 2214 | 1000 | drawbridge | systemd             ||
|---|---|---|---|---|---|
|


||
|---|
|


|You may wish to restart these processes.|
|---|
|


|See 'man zypper' for information about the meaning of values in the above table.|
|---|
|


||
|---|
|


|Core libraries or services have been updated.|
|---|
|


Reboot is required to ensure that your system benefits from these updates.|The following running processes use deleted files:|
|---|
|

I’ll keep investigating and whenever I get results, I update the thread as well.

Regards.

#8

Reboot and you should be ok

#9

I’ve reboot and the warnings gone.

But the original problem persists.

"Failed to start section!"
The KDE theme I’m used to use still not back.

Tuff times bois, tuff times!

#10

This can give more insight into the login manager:


journalctl -b -u display-manager.service

It should contain mention of sddm, although it seems that the error message is more associated to LightDM (“Failed to start session!”). Resolution involved forcing re-installation of the desktop.

The ‘KDE theme’ you mention is the login screen? It might be LightDM instead of SDDM.

#11

Here is the output for



journalctl -b -u display-manager.service

||[0;1;38;5;185mJournal file /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/system@0005a27d97888a97-6ad15c9186514b65.journal~ is truncated, ignoring file.[0m|
|---|---|
||-- Logs begin at Thu 2020-04-02 20:33:27 -03, end at Fri 2020-05-29 23:34:04 -03. --|
||May 29 23:22:07 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.|
||May 29 23:22:08 localhost systemd[1]: Starting X Display Manager...|
||May 29 23:22:08 localhost display-manager[1573]: /etc/vconsole.conf available|
||May 29 23:22:08 localhost display-manager[1573]: KEYMAP: us|
||May 29 23:22:08 localhost display-manager[1573]: Command: localectl set-keymap us|
||May 29 23:22:08 localhost display-manager[1573]: I: Using systemd /usr/share/systemd/kbd-model-map mapping|
||May 29 23:22:09 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.|
||May 29 23:22:09 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.|
||May 29 23:22:10 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.|
||May 29 23:22:11 localhost.localdomain lightdm[2087]: g_file_test: assertion 'filename != NULL' failed|
||May 29 23:22:12 localhost.localdomain display-manager[1535]: Starting service lightdm..done|
||May 29 23:22:12 localhost.localdomain systemd[1]: Started X Display Manager.|
||May 29 23:22:21 localhost.localdomain lightdm[2185]: gkr-pam: unable to locate daemon control file|
||May 29 23:22:21 localhost.localdomain lightdm[2185]: gkr-pam: stashed password to try later in open session 
[FONT=-apple-system]
|


[/FONT]

The ‘KDE theme’ you mention is the login screen?

Yes, is that what I meant.

#12

I also ran


sudo journalctl --verify

and the output was quite annoying. Maybe it can provide insights as well.


PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2625b1686be-fad6ffd20b120e84.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2668cf67eab-d599df1bcdfba086.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a269b9ed2a95-247951ff347f168e.journal~
0;1;31m604f48: Invalid entry item (8/29 offset: 0000000m
0;1;31m604f48: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a27d97eec150-54ac79c96f46e6b3.journal~:604f48 (of 8388608 bytes, 75%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a27d97eec150-54ac79c96f46e6b3.journal~ (Bad message)0m
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a28e70a2580b-73bf6a8b84b6285c.journal~
0;1;31m73be20: Invalid entry item (26/29 offset: 0000000m
0;1;31m73be20: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2a78f12e0e5-073465d2f4b5f083.journal~:73be20 (of 8388608 bytes, 90%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2a78f12e0e5-073465d2f4b5f083.journal~ (Bad message)0m
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2b83749b7bc-d0ba08d2fc046ea9.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2b97de1d5f4-88032fcde7b396f5.journal~
0;1;31m9ecff8: Invalid object0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2e11218926d-d2c59cbdc1b9ce5a.journal~:9ecff8 (of 16777216 bytes, 62%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a2e11218926d-d2c59cbdc1b9ce5a.journal~ (Bad message)0m
0;1;31m897e78: Invalid entry item (21/29 offset: 0000000m
0;1;31m897e78: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3049d7ff67a-6ade40188f9916f4.journal~:897e78 (of 16777216 bytes, 53%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3049d7ff67a-6ade40188f9916f4.journal~ (Bad message)0m
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a322b2bb0821-9044943040f64b85.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a32cad0d4691-0082c3a18921e316.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a33e804b1b15-d7f370a0e68e3636.journal~
0;1;31m5f8df0: Invalid entry item (29/33 offset: 0000000m
0;1;31m5f8df0: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a343e4aa378b-895fffdc4c279432.journal~:5f8df0 (of 8388608 bytes, 74%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a343e4aa378b-895fffdc4c279432.journal~ (Bad message)0m
0;1;31m88afa8: Invalid hash (3fa7a96d26c13a73 vs. dcd0ed7ae0c07ef90m
0;1;31m88afa8: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3550823a3c2-e0511232b7324ea5.journal~:88afa8 (of 16777216 bytes, 53%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3550823a3c2-e0511232b7324ea5.journal~ (Bad message)0m
0;1;31m462fb8: Invalid hash (87a522932156435a vs. f0c87223d498e8660m
0;1;31m462fb8: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3568a6df9e2-06188e8bdd11c384.journal~:462fb8 (of 8388608 bytes, 54%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3568a6df9e2-06188e8bdd11c384.journal~ (Bad message)0m
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3a5dda97d11-e63bbe18343cc14a.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3a7945e1236-357eff059724d31d.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3ae8ce770fe-2295c1e617b37ec2.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3cfa9b68696-95818a736427d689.journal~
0;1;31m46aef8: Invalid entry item (13/29 offset: 0000000m
0;1;31m46aef8: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3d0971a56d5-b102932b6239cf24.journal~:46aef8 (of 8388608 bytes, 55%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3d0971a56d5-b102932b6239cf24.journal~ (Bad message)0m
0;1;31m574000: Invalid object0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3e1a13334bd-de6a99e213f8fe33.journal~:574000 (of 8388608 bytes, 68%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3e1a13334bd-de6a99e213f8fe33.journal~ (Bad message)0m
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3e88294f3f1-a560b8b90f3d5bee.journal~
0;1;31m5bef10: Invalid entry item (11/32 offset: 0000000m
0;1;31m5bef10: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3f5a385f591-16a93acfadf499e9.journal~:5bef10 (of 8388608 bytes, 71%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3f5a385f591-16a93acfadf499e9.journal~ (Bad message)0m
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3f74e1cd40d-d89071f0c5e5f54c.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a3f836679175-a10f425bc55d2dfa.journal~
0;1;31m625ea0: Invalid entry item (18/32 offset: 0000000m
0;1;31m625ea0: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a40a85beef25-ba0aa46fddb3f59f.journal~:625ea0 (of 8388608 bytes, 76%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a40a85beef25-ba0aa46fddb3f59f.journal~ (Bad message)0m
0;1;31m1af0e30: Invalid entry item (25/29 offset: 0000000m
0;1;31m1af0e30: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a44be59abc44-b1516c61a2868f92.journal~:1af0e30 (of 33554432 bytes, 84%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a44be59abc44-b1516c61a2868f92.journal~ (Bad message)0m
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a44eca91330e-e1ac6148ec8ddc90.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4502da0a728-bcbc3054c03583d8.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4512ae5f52b-4824b1310f099f3e.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4585a13bdb2-3151b206ae51583e.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4b4b8997392-6e50b9218c881ae9.journal~
0;1;31m405e00: Invalid entry item (28/29 offset: 0000000m
0;1;31m405e00: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4b578d853bf-ab2d4254a09b441b.journal~:405e00 (of 8388608 bytes, 50%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4b578d853bf-ab2d4254a09b441b.journal~ (Bad message)0m
0;1;31m97df40: Invalid entry item (8/29 offset: 0000000m
0;1;31m97df40: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4d1fba28572-85784d2af900199e.journal~:97df40 (of 16777216 bytes, 59%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4d1fba28572-85784d2af900199e.journal~ (Bad message)0m
0;1;31m68be60: Invalid entry item (22/29 offset: 0000000m
0;1;31m68be60: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4e7142806e4-9e5560eb5e4600a5.journal~:68be60 (of 8388608 bytes, 81%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4e7142806e4-9e5560eb5e4600a5.journal~ (Bad message)0m
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a4fafd806876-c3bec826dfab5662.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a501fffdde39-d6633dfe912aacc4.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a504baaf2c39-57b836ea86a53f9e.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a511d1f6c0a2-a18bb65eafd553c0.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a52b7a5a7a5e-26ff5b9a37004f37.journal~
0;1;38;5;185m5c4ff0: Unused data (entry_offset==0)0m
0;1;31m5c4ff0: Invalid hash (00000000 vs. def73f721dd8bb680m
0;1;31m5c4ff0: Invalid object contents: Bad message0m
0;1;31mFile corruption detected at /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a539e80bdf9b-0eaa616aa4e6c7e3.journal~:5c4ff0 (of 8388608 bytes, 72%).0m
0;1;38;5;185mFAIL: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a539e80bdf9b-0eaa616aa4e6c7e3.journal~ (Bad message)0m
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a53d44d7f0c4-2e6062508f2957e6.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a541c74801a2-4b7ddbc7921a271c.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a5a4500bb7a7-a040e0b6e9eee295.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0005a5cdca30139d-da03f4fb4bb23066.journal~
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0ac1294d6c314f0583bd6f221332e055-00000000000006b5-0005a5cdca2fc1a9.journal
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000@0ac1294d6c314f0583bd6f221332e055-0000000000003057-0005a61356cf7c06.journal
PASS: /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/user-1000.journal
#13

Here is the output for


sudo journalctl -b -u display-manager.service



                e[0;1;38;5;185mJournal file /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/system@0005a27d97888a97-6ad15c9186514b65.journal~ is truncated, ignoring file.e[0m                      
|          |
|---|
||-- Logs begin at Thu 2020-04-02 20:33:27 -03, end at Fri 2020-05-29 23:34:04 -03. --|
||May 29 23:22:07 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.|
||May 29 23:22:08 localhost systemd[1]: Starting X Display Manager...|
||May 29 23:22:08 localhost display-manager[1573]: /etc/vconsole.conf available|
||May 29 23:22:08 localhost display-manager[1573]: KEYMAP: us|
||May 29 23:22:08 localhost display-manager[1573]: Command: localectl set-keymap us|
||May 29 23:22:08 localhost display-manager[1573]: I: Using systemd /usr/share/systemd/kbd-model-map mapping|
||May 29 23:22:09 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.|
||May 29 23:22:09 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.|
||May 29 23:22:10 localhost systemd[1]: /usr/lib/systemd/system/display-manager.service:12: PIDFile= references a path below legacy directory /var/run/, updating /var/run/displaymanager.pid → /run/displaymanager.pid; please update the unit file accordingly.|
||May 29 23:22:11 localhost.localdomain lightdm[2087]: g_file_test: assertion 'filename != NULL' failed|
||May 29 23:22:12 localhost.localdomain display-manager[1535]: Starting service lightdm..done|
||May 29 23:22:12 localhost.localdomain systemd[1]: Started X Display Manager.|
||May 29 23:22:21 localhost.localdomain lightdm[2185]: gkr-pam: unable to locate daemon control file|
||May 29 23:22:21 localhost.localdomain lightdm[2185]: gkr-pam: stashed password to try later in open session|



|e0;1;38;5;185mJournal file /var/log/journal/7ab3ea39a1994e3dbfce7f7324ebfdd1/system@0005a27d97888a97-6ad15c9186514b65.journal~ is truncated, ignoring file.e0m|
|---|

The ‘KDE theme’ you mention is the login screen?

Yes.

#14

Somehow SDDM got replaced by LightDM. Re-enable it:

sudo systemctl --force enable sddm.service
#15

Uow, how did you realize it? (based on the info I provided)

Probably I blindly agreed to it during that python installation.

Your suggestion didn’t work, somehow sddm doesn’t exist.
Here is the output for the command :


sudo systemctl --force enable sddm.service
Failed to enable unit: Unit file sddm.service does not exist.

Funny because the system says the opposite:


whereis sddm
sddm: /usr/share/sddm

I also tried to reinstall (restore) sddm and the theme I was using based on this thread with


sudo apt-get install --reinstall sddm-theme-maldives

But no provider was found.

Overall I removed lightDM


sudo apt-get purge lighdm

But SDDM not “automatically replaced it” (I still can’t login as before)

Now and I’m trying to redefine SDDM as my default display-manager.
This is the output for


systemctl status display-manager

      |     Loaded: loaded (/usr/lib/systemd/system/display-manager.service; enabled; vendor preset: enabled)|
|---|
|


|     Active: active (running) since Sat 2020-05-30 18:12:35 -03; 1h 34min ago|
|---|
|


|   Main PID: 2085 (xdm)|
|---|
|


|      Tasks: 20 (limit: 4915)|
|---|
|


|     Memory: 192.6M|
|---|
|


|     CGroup: /system.slice/display-manager.service|
|---|
|


|             ├─2085 /usr/bin/xdm|
|---|
|


|             ├─2087 /usr/bin/X -nolisten tcp -br vt7 -keeptty -auth /var/lib/xdm/authdir/authfiles/A:0-lTLaBR|
|---|
|


|             └─2121 /usr/bin/xconsole -notify -nostdin -verbose -exitOnFail|
|---|
|


||
|---|
|


|May 30 18:12:35 localhost.localdomain root[2049]: /etc/init.d/xdm: No changes for /etc/X11/xdm/xdm-config|
|---|
|


|May 30 18:12:35 localhost.localdomain display-manager[1533]: Starting service xdm..done|
|---|
|


|May 30 18:12:35 localhost.localdomain systemd[1]: Started X Display Manager.|
|---|
|


|May 30 18:13:02 localhost.localdomain xdm[2108]: gkr-pam: unable to locate daemon control file|
|---|
|


|May 30 18:13:02 localhost.localdomain xdm[2108]: gkr-pam: stashed password to try later in open session|
|---|
|


|May 30 18:13:02 localhost.localdomain xdm[2108]: pam_unix(xdm:auth): authentication failure; logname= uid=0 euid=0 tty=:0 ruser= rhost=  user=drawbridge|
|---|
|


|May 30 18:13:04 localhost.localdomain xdm[2108]: LOGIN FAILURE ON :0, drawbridge|
|---|
|


|May 30 18:13:17 localhost.localdomain xdm[2108]: gkr-pam: unable to locate daemon control file|
|---|
|


|May 30 18:13:17 localhost.localdomain xdm[2108]: gkr-pam: stashed password to try later in open session|
|---|
|


May 30 18:13:17 localhost.localdomain xdm[2108]: pam_unix(xdm:session): session opened for user drawbridge(uid=1000) by (uid=0)|display-manager.service - X Display Manager|
|---|
|
  • gkr-pam: unable to locate daemon control file (this error is reported constantly in log verifications)
  • LOGIN FAILURE ON :0, drawbridge (Apparently in somewhere is defined that [drawbridge, my user] can’t succeed at the login)

I hope it can provide more informinsights.
Thank you so much for all your support so far.

#16

[ERRATUM] I still unable to login through SDDM display manager.

Since ligthDM is gone now,** “Failed to start section” **is no longer the issue here.

The login screen now is an openSUSE default one, and I’m able to successfully login as well.
After succeeding at login, I only have a small CLI widow and no (fancy)GUI at all.

I’m also able to open vscode, firefox, and other applications through CLI commands.

We’re about to make it happen.

o//

#17

“Today is a happy day.”
Me.

Hey folks, the problem was solved!

I just had to force install SDDM with zypper:


sudo zypper in -f sddm

and so I did with my Desktop Environment:


sudo zypper in -t pattern kde kde_plasma 

and then

sudo zypper install plasma5-session

Everything is working as before (AFAIK).

I appreciate all efforts in this thread.
When I introduced the problem (2-3 weeks ago) I was a complete Linux newbie, now I still as before just slightly less like.

Thank you all folks.