Bug 451334 - presence of steam-libs-i386 breaks distro upgrade
Summary: presence of steam-libs-i386 breaks distro upgrade
Status: RESOLVED DUPLICATE of bug 451315
Alias: None
Product: neon
Classification: KDE Neon
Component: Packages User Edition (show other bugs)
Version: unspecified
Platform: Neon Linux
: NOR critical
Target Milestone: ---
Assignee: Neon Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-03-09 19:49 UTC by benjamin
Modified: 2022-03-23 04:17 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description benjamin 2022-03-09 19:49:13 UTC
SUMMARY
***
the fact that steam-libs-i386 is installed renders the installation unusable after a system upgrade
***


STEPS TO REPRODUCE
1. install steam-libs-i386
2. upgrade to latest version of kde neon via the system upgrade in discover
3. go through with the requested reboots (was 2 reboots for me)

OBSERVED RESULT
starting a x.org session results in immediate termination of the x server. the user gets presented with the graphical login again

EXPECTED RESULT
i expected auto login to just start my x server

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.24
(available in About System)
KDE Plasma Version: 5.24

ADDITIONAL INFORMATION
i upgraded from a 5.2x to 5.24. i have done so before without major trouble
only after i ran
sudo pkcon remove steam-libs-i386
and 
sudo pkcon -y update
was i able to start my x server again. 
a novice user would have been completely overwhelmed by the problem. thats why i marked it as critical
there was no hint to the user about what is the root of the problem
manually trying to start a xserver by tying
startx
in the terminal resulted in no error message and a advise to look at /var/log/x.org.1/somelog.file but there no /var/log/x.org* present. i was unable to find logfiles that could help me
the fact that the log file hint points in the wrong direction makes it even difficult for an advanced user to solve the problem
Comment 1 Nate Graham 2022-03-23 04:17:38 UTC

*** This bug has been marked as a duplicate of bug 451315 ***