LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   SUSE / openSUSE (https://www.linuxquestions.org/questions/suse-opensuse-60/)
-   -   Screen locker broken when upgrading Leap 42.3 to Leap 15.0 (https://www.linuxquestions.org/questions/suse-opensuse-60/screen-locker-broken-when-upgrading-leap-42-3-to-leap-15-0-a-4175631483/)

Crb999 06-08-2018 01:00 AM

Screen locker broken when upgrading Leap 42.3 to Leap 15.0
 
Hi,
I downloaded 15 made an iso and set about installing leap 15

I have reached a point where, on a black screen, I'm told:
===================
The screen locker is broken and unlocking is not possible anymore.

In order to unlock, switch to a virtual terminal (eg Ctrl + Alt + F2),
Login and execute the command
loginctl unlock-sessions
Afterwards, switch back to the running session (eg Ctrl + Alt + F7)
===================

I can switch but there is half a cursor on the left of the screen and nothing I type is entered on the screen.

I tried to login as root with psswd anyway, but there is no response, leaving me only to switch back to the 'sessions locked ' message.

Any suggestions would be much appreciated

Regards

Chris

Keruskerfuerst 06-14-2018 11:54 PM

I recommend installing Leap 15.0 freshly. (Not doing an upgrade)

Crb999 06-15-2018 10:33 AM

Thanks Keruskerfuerst, I love to do that but how can I do it without damaging the data on my disks. How can I contrain the install to only deal with the boot sector etc?

Keruskerfuerst 06-17-2018 12:00 AM

The disk should be partitioned with a separate home partition.

Crb999 06-17-2018 12:21 PM

The disk has been running 42.3 for quite a long time and I do not want the partitions that already exist, altered in any way. Nor would I want the data on the users area touched at all.

How would I do that?

ondoho 06-17-2018 11:29 PM

Quote:

Originally Posted by Crb999 (Post 5868617)
The disk has been running 42.3 for quite a long time and I do not want the partitions that already exist, altered in any way. Nor would I want the data on the users area touched at all.

well then just leave it as it is, and install the new suse version on a complete different partition, or even hard drive, and from then on access the data on the old partition(s) as data only, not actually booting into it.

this is the only literal solution to the condititons you layed out there.

Keruskerfuerst 06-18-2018 01:13 AM

Quote:

The disk has been running 42.3 for quite a long time and I do not want the partitions that already exist, altered in any way. Nor would I want the data on the users area touched at all.
If you do an upgrade, then the data on the partitions are changed.


All times are GMT -5. The time now is 02:28 AM.