Latest Slo Roll upgrades won't log in to GUI?

English Install/Boot/Login
1

Folks:

Can’t seem to get my foot off the banana peel in my various SUSE distros . . . today, ran a large 898 package upgrade in my new Slo Roll install . . . .

On cold boot into new kernel it took a minute to get to GUI log in, then entering password, screen goes black for a second then back to log in window. I tried the three pattern options, IceWeasel and the two GNOME options, same problem.

I rebooted, thinking I had to switch to another OS, but then tried to use the previous kernel . . . and, slowly, I was able to log into GUI.

There were a number of firmware packages, and there were a number of “nvidia” packages installed, even though I’m running nouveau . . . I just followed the zypper’s suggestions . . . ???

This is the '12 Mac Pro desktop unit that I have running as multi-boot. Seems like something in newer kernel or packages is not working?? I recently had similar issues in Leap or TW . . . one of them was solved by installing “sddm-qt6” . . . but I recall in another thread recently posted where somebody said, “Slo Roll isn’t able to use qt6.” ?? So many problems lately I’ve lost track.

Any way to get this latest round of Slo Roll packages to log into GUI??

2

Yes. The problem has continued, even after a newer kernel upgrade, the log in password is either “not accepted” or after typing password the password box is empty. Multiple attempts to log into GUI failed.

Thinking that this problem is similar to the problem I had in TW a few weeks back, slow log in, I tried to install “sddm-qt6” . . . this time that install was not selected for update-alternatives, so I had to manually select sddm, and on reboot system went to a TTY log in. I then tried XDM, which must have been installed with the system. That brought a basic window to enter the log in data . . . that brought an “Oops, something went wrong, please log out.” Had to get to a TTY to reboot the system.

Then I recalled mrmazda’s suggestion to another poster having similar issues to “use lightdm,” so I installed lightdm via the TTY and set it as default. On restart the system again went to TTY . . . .

I then restarted to the grub menu and picked advanced options and picked the 6.5.9-1 kernel that had worked for a couple weeks before this latest news of fresh disaster. The GPU spun up quite vigorously and then a basic SUSE wallpaper loaded and I entered the password . . . and we got into the GUI. However apps weren’t launching (this is the same stuff that happened in TW with the slow log in a few weeks back, now over in Slo Roll) . . . so I reset the displaymanager to sddm . . . and restarted, back to older kernel and again with the GPU spinning up, but password was accepted and GUI seems a bit better at launching apps . . . .

Seems like some issue with the 6.5.9-3 kernel which is not accepting passwords in displaymanager . . . but does OK in TTY . . . . What would the proper package to file a bug report against?? Slo Roll?? kernel?? displaymanager??

3

@non_space Did or have you checked what the default boot is multi-user or graphical?

systemctl get-default
4

Do you have a non default shell as your login shell, like fish for instance? I had a similar problem once and it was caused by my user shell not being bash.

5

Malcolm:

Thanks for stopping by . . . today is TW day so I won’t have time to boot back to Slo Roll to check that out. Generally everything is “default” and Slo Roll was running “OK” until one of the recent kernel upgrades . . . .

Yesterday was Deb Sid day and everything booted and ran fine . . . . Back in SUSE-land and this morning TW returned to booting to ER . . . but, as root?? A series of errors showed up in the dmesg and when I tried to run a “zypper ref” it said, “Zypper not recognized, you can run ‘apt install zypper’ to install it.” So it was some kind of “hybrid” combo of TW & ubuntu???

I power buttoned out of it and on cold boot selected “advanced options” and picked the lowest kernel in a list of about 6 . . . and boom, “Bob’s yr uncle” I have a working TW GUI. Now running a zypper dup to see if that “remedies” the problem. I just keep going from one banana peel to the next.

@throttlemeister:

All basically bone stock as installed by installer and/or zypper. No time to mess with non-stock items these days . . . so many problems just getting a basic system going, etc.

6 
sudo systemctl get-default

graphical.target

Problem with latest kernel in SloRoll booting to TTY continues. Rebooting into “advanced options” and selecting the older 6.5.9-1 kernel does get into GUI, but GPU spins up to get the job done???

7

Running like clockwork here:

# inxi -S
System:
  Host: ab85m Kernel: 6.5.9-1-default arch: x86_64 bits: 64 Desktop: KDE
    v: 3.5.10 Distro: openSUSE Tumbleweed-Slowroll 20231003
# parted -l | grep EFI
 1      1049kB  337MB   336MB   fat32           TG1P01 EFI System (ESP) T253X 2295  boot, esp
# tree /boot/efi
/boot/efi
|-- EFI
|   |-- BOOT
|   |   |-- BOOTX64.EFI
|   |   `-- mt74x64.efi
|   `-- opensusetw
|       `-- grubx64.efi
|-- mt74x64.efi # memtest86 7.4
`-- mt83x64.efi # memtest86 8.3
4 directories, 5 files
# ls -gG /boot/gru*
ls: cannot access '/boot/gru*': No such file or directory
# wc -l /disks/stw/boot/grub2/custom.cfg
124 /disks/stw/boot/grub2/custom.cfg
# grep -A4 roll /disks/stw/boot/grub2/custom.cfg
menuentry "openSUSE Slowroll defkernel 3" {
        search --no-floppy --set=root --hint-efi=hd0,gpt19 --label tg1p19sslo
        linux   /boot/vmlinuz root=LABEL=tg1p19sslo noresume ipv6.disable=1 net.ifnames=0 consoleblank=0 mitigations=off
        initrd  /boot/initrd
}
# ls -gG /disks/stw/boot/grub2
-rwxr-xr-x 1  7203 Sep 24 00:55 custom.cfg
drwxr-xr-x 2  4096 Jun 21  2018 fonts
-rw------- 1 41877 Oct 14 00:22 grub.cfg
-rw-r--r-- 1  1024 Jun 21  2018 grubenv
drwxr-xr-x 2  4096 Oct 14 00:22 locale
drwxr-xr-x 2 20480 Oct 14 00:22 x86_64-efi
# lsb | egrep 's1|st|edo|deb|ubu|int|slo|mga|f3'
|-sda7  ext4   tg1p07stw
|-sda8  ext4   tg1p08s154
|-sda9  ext4   tg1p09deb12
|-sda10 ext4   tg1p10mga9
|-sda11 ext4   tg1p11ubu22
|-sda12 ext4   tg1p12s153
|-sda13 ext4   tg1p13deb13
|-sda14 ext4   tg1p14f38
|-sda15 ext4   tg1p15mint
|-sda16 ext4   tg1p16s156
|-sda17 ext4   tg1p17deb11
|-sda18 ext4   tg1p18mga8
|-sda19 ext4   tg1p19sslo       3.6G    48% /
|-sda20 ext4   tg1p20ubu20
|-sda21 ext4   tg1p21s155
`-sda23 ext4   tg1p23f39
#
8

Well, that is one clue, the “6.5.9-1” kernel also boots for me, but right now had to use “advanced options” to deselect 6.5.9-3 kernel and pick the 6.5.9-1 kernel.

This problem with booting to TTY in both my Leap 15.6 AND my SloRoll editions with 6.5.9-3 kernel is happening . . . . And with the newer kernel the Leap install is not reviving from suspend either . . . .

I believe that my TW install boots with top kernel listed in grub . . . i.e., no need for “advanced options” to get in. I’ll have to check later to see which kernel that is running. It would be interesting if it was running 6.5.9-3.

sudo inxi -S
[sudo] password for root: 
System:
  Host: n00-MacPro.home Kernel: 6.5.9-1-default arch: x86_64 bits: 64
    Console: pty pts/1 Distro: openSUSE Tumbleweed-Slowroll 20231003

Slo@n00-MacPro:~> sudo parted -l | grep EFI
 1      20.5kB  210MB   210MB   fat32           EFI System Partition  boot, esp
 1      20.5kB  210MB   210MB   fat32           EFI System Partition     boot, esp
 1      20.5kB  210MB   210MB   fat32           EFI System Partition  boot, esp
Slo@n00-MacPro:~> sudo tree /boot/efi
/boot/efi
└── EFI
    ├── BOOT
    │   └── BOOTX64.EFI
    ├── leap15.6
    │   ├── boot.csv
    │   ├── grub.cfg
    │   ├── grub.efi
    │   ├── grubx64.efi
    │   ├── MokManager.efi
    │   └── shim.efi
    ├── opensuse
    │   ├── boot.csv
    │   ├── grub.cfg
    │   ├── grub.efi
    │   ├── grubx64.efi
    │   ├── MokManager.efi
    │   └── shim.efi
    └── tumbleweed
        └── grubx64.efi

6 directories, 14 files
Slo@n00-MacPro:~> sudo ls -gG /disks/stw/boot/grub2
ls: cannot access '/disks/stw/boot/grub2': No such file or directory

Grub has been removed from SloRoll and moved back over to TW for master control of grub. It was also removed from Leap, so not sure why it is showing those files.

9 
# inxi -S --vs
inxi 3.3.31-00 (2023-11-02)
System:
  Host: ab85m Kernel: 6.5.9-1-default arch: x86_64 bits: 64 Console: pty pts/4
    Distro: openSUSE Tumbleweed-Slowroll 20231003
# uname -r
6.5.9-1-default
# zypsei nel-def
il | kernel-default | package | 5.14.21-150500.55.19.1 | x86_64 | (System Packages)
il | kernel-default | package | 6.4.12-1.13            | x86_64 | (System Packages)
il | kernel-default | package | 6.5.9-1.3              | x86_64 | (System Packages)
#

zypper zup doesn’t install my TW/SR kernels. rpm does, from my LAN server. If and when I choose to install a kernel in SR, it comes from that cache. I choose which. In SR, I’ve been installing latest, 6.5.9-1.3 from TW, not SR latest, which is 6.5.9-1.2.

That it would. Last I checked, more than 12 hours ago, there was no 6.5.9-3 in standard TW or SR repos.

IME, Mac firmware does a poor job of handling FOSS booting, and needs be given the simplest configuration possible in order to be reasonably dependable. That simplicity, as shown in my previous thread reply, includes having only one ESP partition for it to find.

Do you mount your TW’s / filesystem to /disks/stw/? If not, why would you expect to find anything there? My prior thread post was intended to show both inclusions, and exclusions.

I don’t “remove” Grub very often. How was yours removed? I don’t recall whether or not removing Grub packages includes [no|some|all] files a particular installation put there. If you want them removed, you may need to do it yourself, including stripping them from NVRAM using efibootmgr with -b and -B options.

1 Like
10

As mentioned by Felix: You sure about the version numbers? 6.5.9-3 does not even exist yet in official repos…
Slowroll is at kernel-default-6.5.9-1.2 and Tumbleweed at kernel-default-6.5.9-1.3

11

I must be a “special” person . . . just rebooted from Slo Roll back to “advanced options” and it shows me 4 choices, two kernels with their respective “recovery” mode . . . top/auto load is the “6.5.9-3-default” option . . . picking that choice goes to the TTY. I took shots with my phone of the grub list and the TTY window, clearly showing the “6.5.9-3” . . . .

I don’t have time to mess with how and when the kernels get upgraded, whatever zypper runs is what I click “y” to . . . .

I’m in TW right now, and it is booting the 6.5.9-1 kernel that does work . . . . I’ve always been a little ahead of my time . . . I guess zypper just knows that about me . . . cutting edge dysfunction . . . doesn’t work, nobody gets it, etc.

12

Ok, now the new version get shown as kernel-default-6.5.9-3 in Slowroll…

13

Found the issue with Slowroll why it no longer boots.

The latest zypper dup pulls in kernel-default-base-6.5.9-3.10.1.7 additional to kernel-default-6.5.9-1.2 . This leads to a system which no longer boots into graphical session. This base package is also the reason why 6.5.9-3 is shown in grub menu (but as mentioned above this kernel version does not exist yet).

When you drop to the console/TTY, simply login as root and issue an zypper rm kernel-default-base. This will remove the not matching base package and you will be able to boot into a graphical session again with the latest available Slowroll kernel-default-6.5.9-1.2

1 Like
14

Great to know, but how did you determine he had kernel-default-base on his system?

# zypper se -s kernel-default  | grep -Ev 'extra|opt|live|debug|devel|srcp|openSUSE-20' | grep -E 'x86|noarch'| so                                                                   rt
 l | kernel-default-base            | package    | 6.5.4-1.1.28.13        | x86_64 | OSS
 l | kernel-default-base            | package    | 6.5.9-3.10.1.7         | x86_64 | Update
 l | kernel-default-base-rebuild    | package    | 6.5.4-1.1.28.13        | x86_64 | OSS
 l | kernel-default-base-rebuild    | package    | 6.5.9-3.10.1.7         | x86_64 | Update
 l | kernel-default-vdso            | package    | 6.5.4-1.1              | x86_64 | OSS
 l | kernel-default-vdso            | package    | 6.5.9-1.2              | x86_64 | Update
il | kernel-default                 | package    | 5.14.21-150500.55.19.1 | x86_64 | (System Packages)
il | kernel-default                 | package    | 6.4.12-1.13            | x86_64 | (System Packages)
il | kernel-default                 | package    | 6.5.9-1.3              | x86_64 | (System Packages)
vl | kernel-default                 | package    | 6.5.4-1.1              | x86_64 | OSS
vl | kernel-default                 | package    | 6.5.9-1.2              | x86_64 | Update
# zypper rl kernel-de*
1 lock has been successfully removed.
# zypper -v dup -d
... Run 'zypper locks -s' to see the complete list of locked items.

The following NEW package is going to be installed:
  kernel-default  6.5.9-1.2

The following package is going to be REMOVED:
  kernel-default  6.5.9-1.3

The following package requires a system reboot:
  kernel-default  6.5.9-1.2

1 new package to install, 1 to remove.
Overall download size: 161.4 MiB. Already cached: 0 B. Download only.

    Note: System reboot required.
Continue? [y/n/v/...? shows all options] (y):

I see nothing to indicate kernel-default-base would have been installed, or in this thread that it had.

15

Because i was able to reproduce the issue on a Slowroll installation?!
Please read again my previous post and you will maybe understand. The latest zypper dup on Slowroll pulls in falsely kernel-default-base which will lead to a system that drops to TTY on next reboot.

To recreate this problem, you need a untinkered Slowroll system without prior kernel locks or nonsense like that…

16

I’m getting this at the login screen after “dup” to latest snap of tumbleweed. If I login wih a gnome session it works. Logs me in to the GNOME WM. If I use KDE x11 or Wayland. Screen just goes black and back to the same screen with error message.

osscreenshot
osscreenshot2044×1530 212 KB

17

This thread is about Slowroll and another failure…

18

You are way off-topic for this thread. Please start a new thread with a title appropriate for your problem.

19

Problem something like Tumbleweed is just faster but with the same problems as Slowroll … just faster to get them.

Yeah, I get it. It’s just a joke.

1 Like
20

The difference between Slowroll and Tumbleweed kernels is evident and seems to explain why on Slowroll the base package gets pulled in…
On Tumbleweed the kernel-default and base package have the same version number. On Slowroll the base backage has a significantly higher version number…on Slowroll also x86_64 and i586 versions differ…

Slowroll:

slow@slowroll:~> zypper se -s kernel-default
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name                           | Type       | Version         | Arch   | Repository
---+--------------------------------+------------+-----------------+--------+-----------
i+ | kernel-default                 | Paket      | 6.5.9-1.2       | x86_64 | update
v  | kernel-default                 | Paket      | 6.5.9-3.1       | i586   | update
v  | kernel-default                 | Paket      | 6.5.4-1.1       | x86_64 | base-oss
   | kernel-default                 | Quellpaket | 6.5.9-3.1       | noarch | update
   | kernel-default                 | Quellpaket | 6.5.9-1.2       | noarch | update
   | kernel-default-base            | Paket      | 6.5.9-3.10.1.7  | x86_64 | update
   | kernel-default-base            | Paket      | 6.5.4-1.1.28.13 | x86_64 | base-oss
   | kernel-default-base            | Quellpaket | 6.5.9-3.10.1.7  | noarch | update
   | kernel-default-base-rebuild    | Paket      | 6.5.9-3.10.1.7  | x86_64 | update
   | kernel-default-base-rebuild    | Paket      | 6.5.4-1.1.28.13 | x86_64 | base-oss
   | kernel-default-debuginfo       | Paket      | 6.5.9-1.2       | x86_64 | update
   | kernel-default-debuginfo       | Paket      | 6.5.9-3.1       | i586   | update
   | kernel-default-debugsource     | Paket      | 6.5.9-1.2       | x86_64 | update
   | kernel-default-debugsource     | Paket      | 6.5.9-3.1       | i586   | update
   | kernel-default-devel           | Paket      | 6.5.9-1.2       | x86_64 | update
   | kernel-default-devel           | Paket      | 6.5.9-3.1       | i586   | update
   | kernel-default-devel           | Paket      | 6.5.4-1.1       | x86_64 | base-oss
   | kernel-default-devel-debuginfo | Paket      | 6.5.9-1.2       | x86_64 | update
   | kernel-default-vdso            | Paket      | 6.5.9-1.2       | x86_64 | update
   | kernel-default-vdso            | Paket      | 6.5.9-3.1       | i586   | update
   | kernel-default-vdso            | Paket      | 6.5.4-1.1       | x86_64 | base-oss
   | kernel-default-vdso-debuginfo  | Paket      | 6.5.9-1.2       | x86_64 | update
   | kernel-default-vdso-debuginfo  | Paket      | 6.5.9-3.1       | i586   | update
slow@slowroll:~>

Tumbleweed:

ich@laptop:~> zypper se -s kernel-default
Repository-Daten werden geladen...
Installierte Pakete werden gelesen...

S  | Name                        | Type  | Version        | Arch   | Repository
---+-----------------------------+-------+----------------+--------+-----------------------
i+ | kernel-default              | Paket | 6.5.8-1.1      | x86_64 | (Systempakete)
i+ | kernel-default              | Paket | 6.5.6-1.1      | x86_64 | (Systempakete)
i+ | kernel-default              | Paket | 6.5.9-1.3      | x86_64 | Haupt-Repository (OSS)
   | kernel-default-base         | Paket | 6.5.9-1.3.29.1 | x86_64 | Haupt-Repository (OSS)
   | kernel-default-base-rebuild | Paket | 6.5.9-1.3.29.1 | x86_64 | Haupt-Repository (OSS)
   | kernel-default-devel        | Paket | 6.5.9-1.3      | x86_64 | Haupt-Repository (OSS)
   | kernel-default-vdso         | Paket | 6.5.9-1.3      | x86_64 | Haupt-Repository (OSS)
ich@laptop:~>