Today's update dropped me into IceWM?!

English Applications
1

Laptop AMD Tumbleweed Gnome Wayland. I ran sudo zypper dup this morning, and after rebooting and entering my login password I got dropped into a desktop environment called IceWM. !! :astonished: Was not expecting that.

Screenshot ā†’ https://paste.opensuse.org/pastes/eac8542205d6

The update moved me from kernel 7.0.2 to 7.0.3.

I then rebooted into an earlier snapshot (thank goodness for Btrfs snapshots!)

Anyone know why an update would dump me into IceWM? Never seen this before.

2

@invalid_user_name you need to troll the logs and seeā€¦ journalctl -b -1 may have it. AMD and Wayland issueā€¦

2 Likes
3

Log file ā†’ https://paste.opensuse.org/pastes/315056624098

Anything interesting? What should I look for?

4

@invalid_user_name either add your user to the systemd-journal group or run the log as root user to see more info.

Do you get to the GDM login? If so did you check the cog on the bottom right to see if GNOME is a selection?

2 Likes
5

Could this weird IceWM thing be connected to the Dirty Frag vuln?

6

Log here ā†’ https://paste.opensuse.org/pastes/186c4ed90b0b

7

Yes, I was able to get to the usual login screen.

did you check the cog on the bottom right to see if GNOME is a selection?

Iā€™m still in 7.0.2 and there was no cog on the bottom right. On the bottom right is only the Accessibility icon. Let me know if you need to see a screenshot.

8

Please see which gnome-session is installed:

bruno@LT-B:~> zypper se -si gnome-session
Loading repository data...
Reading installed packages...

S  | Name          | Type    | Version  | Arch   | Repository
---+---------------+---------+----------+--------+-----------
i+ | gnome-session | package | 50.0-4.1 | x86_64 | repo-oss
bruno@LT-B:~>
1 Like
9

Sure, here it is:

advait@localhost:~> zypper se -si gnome-session
Loading repository data...
Reading installed packages...

S  | Name          | Type    | Version  | Arch   | Repository
---+---------------+---------+----------+--------+------------------
i+ | gnome-session | package | 50.0-3.1 | x86_64 | (System Packages)
advait@localhost:~>
10

Odd that the upgrade brought you to kernel 7.0.3 but not to gnome-session 50.0-4.1
Can you try zypper dup again and see if the updated session is in the list?

EDIT: or did you rollback meanwhile?

1 Like
11

Odd that the upgrade brought you to kernel 7.0.3 but not to gnome-session 50.0-4.1
Can you try zypper dup again and see if the updated session is in the list?

EDIT: or did you rollback meanwhile?

Correct, I had to do a rollback to 7.0.2 so I could do my work. Booting into 7.0.3 just takes me to the GDM login and then dumps me right into IceWM. My hunch is that if I could login into Gnome with 7.0.3, I would also be on Gnome 50.0.4.

12

Why am I getting dumped into IceWM? Is that bundled with Gnome?

13

@invalid_user_name still have some X11 stuff lurking? No icewm installed here on a recent install.

Run the screen command, login as root user (no sudo) and run zypper -vvv dup inspect the output for anything untoward and reboot.

1 Like
14

Prolly. Iā€™ve been on the same install for over 4 years.

15

What is the ā€œscreen commandā€?

16 
LT-B:~ # screen zypper -vvv dup
1 Like
17

ā€œLT-B:~ # screen zypper -vvv dupā€

Output is here ā†’ https://paste.opensuse.org/pastes/5d5b01137c5a

At the end, last line, I didnā€™t want to hit ā€œyā€ until I check with you.

What should I do next?

18

LT-B:~ # screen zypper -vvv dup

How is this command different from the usual zypper dup?

19

I see two important deviations from a ā€œstandardā€ install:

  • you have the Mesa packages from Packman
  • you have a bunch of packages from ecsos home repo.

Mesa from Packman should not be needed these days unless you have a (very) old AMD graphics.
home: packages are known to cause issues and your log shows that they are apparently causing conflicts and are not being upgraded for whatever reason (but they are not locked apparently).

Then maybe the Mesa upgrade caused the X server to restart and if you did the upgrade from the graphical session (in other words, not via CTRL+ALT+Fn) the upgrade possibly didnā€™t complete and left the system in a broken state.
BTW that is what the screen command is for, isolating the running process from the X session; but there are reports of even screen crashing upon an X restart.

So I would advise to:

  • switch back Mesa to the OSS version;
  • switch the home:ecsos packages to the OSS (or Packman if available) versions, or at least check what is preventing them from being upgraded;
  • performing the zypper dup in a Virtual Terminal (e.g. CTRL+ALT+F4).
1 Like
20

These are above my noob head but no problem. Iā€™ve got a Linux wizard friend who can help me.

Iā€™ll post back here when itā€™s all fixed and give the details.