My quebes os got stuck after enter password. Desktop doesn't load

User Support General
1

My quebes os got stuck after enter password. Desktop doesn’t load

Hello, two days ago, the following problem occurred with my NotpadeNV41 laptop. In the morning, I was still able to work on it normally. I then shut it down normally. In the evening, I started the laptop to continue working. After entering the password, the loading process was fast until halfway through, then it became very slow. When the loading process was complete, the image froze and the desktop view wouldn’t load. Support hasn’t been able to help me so far, so I hope someone here can.

20250929_095202
20250929_0952021920×2560 230 KB

2

Maybe this issue is causing by one of the qubes that fail to autostart. Try to boot with qubes.skip_autostart:

1 Like
3

Thanks for the answer. I’m relatively new to using Qubes OS. How do I do this with the boot?

4

Hi Noelia - and welcome to the forum! :slight_smile:

When you have the GRUB Boot menu, hit e to edit the boot options and use the arrow keys to find the kernel-line and replace quiet with cubes.skip_autostart.

:slight_smile:

1 Like
5

I dont have GRUB

6

Oh - it wasn’t clear to me, how your system is configured/setup.

To help the next one, can you share a bit more details?

:slight_smile:

7

First thank you for your help. :pray::blush:What Details do you need?

8

I’m not familiar with the NotpadeNV41 – I just assumed that it would have GRUB as bootloader … but as always, “assumptions are the mother of all …” :wink:

So things like

  • it’s configured with XX …
  • it has YY disabled …

:slight_smile:

9

I don’t know where to find this information. I’m not that familiar with Qubes OS yet. I can only tell you what’s listed under System.info. FW_VER: Dasharo Nitroney -v2.4. Kernel linux 6.1.8-Nitrokey.

10

If you hit Esc key when at the part in your photo (after entering password and hitting enter), it should switch to the log and tell you where it is getting stuck. Take a photo

Is this your computer?

From your firmware version, it appears you might be using a nitrokey USB… do you have that plugged in during bootup ?

11

I think there might be a misunderstanding here? The link provided by @MellowPoison contains outdated screenshots. It should be all black and white by default, like this:

666×458 8.31 KB

But the instructions are correct. You get this before entering your passphrase.

12

Hello, thank you very much.
Yes, my nitrokey USB is connected. After entering the password, I pressed enter and then esc, and they received this information. See image.
Yes, the tablet looks the same, but it was purchased from nitrokey, and support couldn’t help me and referred me to the forum.

20251003_141056
20251003_1410561920×2560 465 KB

13

LVM event activation on device 253:0

If boot is stuck at this message, then try to repair your LVM from some Live Linux OS:

14

Thank you. I can’t do anything with your answer because I don’t know how it works. I’m not a programmer, and I’m still learning about Qubes OS. Can anyone help me do it step by step?

15

Try this:
Boot from some Live Linux OS.
Open a terminal.
Find your Qubes OS LUKS partition name using this command:

sudo blkid | grep LUKS

Example output:

$ sudo blkid | grep LUKS
/dev/nvme0n1p3: UUID="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" TYPE="crypto_LUKS" PARTUUID="xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx"

In this example output, your LUKS partition is /dev/nvme0n1p3.
Decrypt your LUKS partition:

sudo cryptsetup luksOpen /dev/nvme0n1p3 luks

Deactivate LVM volumes:

sudo  lvchange -an /dev/qubes_dom0/*

Repair the dom0 pool:

sudo lvconvert --repair /dev/mapper/qubes_dom0-pool00

Reboot into the Qubes OS.

16

Thank you. But how do i do this “Boot from some Live Linux OS.”
Do i have to open something from herein?

20251003_205114
20251003_2051141920×2560 300 KB

17
18

But I’m not familiar with Heads, maybe it won’t be that easy to decrypt the LUKS partition.
Maybe you can use the Heads Recovery Shell instead of booting from some Live Linux OS, but I’m not sure:

It’s better to ask this from Heads community:

19

It looks like there is something wrong with your lvm. As mellow suggests you could try repairing the LVM issue

You’d need to use another computer to create a bootable USB with something like Ubuntu or fedora on it and then run those commands. But I think this might be too difficult for you.

I would think that nova could be more helpful than referring you to the forum. Their link says they might help you with software issues (and charge you)

“If it appears that the malfunction is software related, we will advise you to contact the maker of the software. If we are able to help you, we reserve the right to charge for this”