[EN] System partialy start after upgrade

[sotnik]

Hello
With the last upgrade the system will not start. I get a black screen. I have to startx to get the desktop.
What is the possible problem?
Thank you

[devil]

To try to find an answer to that, we need to know your desktop environment. If it is KDE Plasma, check if sddm is installed.

[hsp]

downgrade  udisks2,  libudisks2-0 and all installed  libblockdev-*

...

[hendrikL]

udisks2 could be the reason,

Downgrading it should help,

https://snapshot.debian.org/package/udisks2/2.9.4-4/#udisks2_2.9.4-4

https://snapshot.debian.org/package/libblockdev/2.28-2/

check the logfile

/var/log/apt$ sudo cat history.log


but best is, do not upgrade your system till that is fixed

[hsp]

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1040793

...

[graviton]

I have the same problem, plasma practically no longer usable.

graviton

[graviton]

udisks2 could be the reason,

Downgrading it should help,

Do you have to set the debian.list to testing for the downgrade, or is there an easier way?

[hendrikL]

Do you have to set the debian.list to testing for the downgrade, or is there an easier way?

No, debian has something like a Time Machine called snapshots. See the links above.

You need to download all the needed files from there, You can find them, the needed files, in /var/log(apt/history.log.
In my case, it was:

libblockdev-part3, libblockdev-swap3, libblockdev-fs3, libnvme1:amd64 (1.5-1, automatic), libblockdev-loop3:amd64 (3.0.1-1, automatic), libblockdev3:amd64 (3.0.1-1, automatic), libblockdev-utils3:amd64 (3.0.1-1, automatic), libblockdev-nvme3:amd64 (3.0.1-1, automatic), libblockdev-crypto3:amd64 (3.0.1-1, automatic) udisks2-0 and libudisks2-0

Remove all that "amd64 automatic version number stuff", and you have your needed packages, download them from snapshots.debian.org.

[hendrikL]

To install the downloaded package, use apt!

Like, as root: "apt install ./your.downloaded.package.deb"

[graviton]

To install the downloaded package, use apt!

Like, as root: "apt install ./your.downloaded.package.deb"

Thanks, I've downgraded to the previous version number with apt (apt-cache policy udisks2 etc.), which temporarily solved the problem.

[sotnik]

Sorry I didn't notice the answers and I opened a new question in https://forum.siduction.org/index.php?topic=9056.0 which can be ignored

I use xfce (default installation) and I downgraded usedk2, as suggested, but the problem remains.
It load the lightdm and not the siduction (I installed  lightdm to overcome the problem. See above link)

At the moment my question is, how I can restore the default siduction display manager

[hendrikL]

As a workaround, you can install libblockdev-mdraid3!

Code: [Select]

sudo apt install libblockdev-mdraid3
From the bugreport

The crash is definitely not expected.

libblockdev-{crypto3,mdraid3,nvme3} are currently optional (Recommends
or Suggests).
It appears though, if they are missing udisks2 is crashing. So for a
short-term fix, you can manually install those packages.

Will have to check, whether to make those plugins hard dependencies or
if a different solution can be found.

[hschn]

fixed with
udisks=2.10.0-3

[DeepDayze]

Now it looks like mdadm now is required even if not used as libblockdev-mdraid3 is now a dependency for udisks2.