Debian User Forums

It finally happened again (manually suspending and resuming doesn't seem to work?!), and this is what was in the window where I ran "plasmashell --replace &": Model size of -2147483647 is less than 0 libkcups: Renew-Subscription last error: 0 successful-ok Model size of -2147483647 is ...

It has just happened again. Unfortunately, the journal is empty: cassiopeia:~# journalctl /usr/bin/plasmashell -- Journal begins at Sat 2022-05-21 11:24:01 CEST, ends at Fri 2022-06-24 16:00:10 CEST. -- -- No entries -- And because there is no more plasmashell running, I'm not sure how to apply the ...

Yes, I'll try that once I'm done with my current task. BTW, my plasmoid is still installed: cassiopeia ~ > ls .local/share/plasma/plasmoids/ pliff/ But where are widget instances registered? The file .config/plasma-org.kde.plasma.desktop-appletsrc contains pliff: [Containments][39][General] extraIte...

I've used my notebook extensively over the past two weeks, but so far everything is still working (while still using UUIDs). But this discussion is very handy to have in case something goes wrong again.

Thanks for that command plasmashell --replace & that does indeed restore the plasma desktop without losing my session. Unfortunately, I've just restarted plasma using that command, so because of that (I assume) the journal for /usr/bin/plasmashell is empty. I'll check next time it happens. As fo...

canci wrote: ↑2022-06-04 16:02 And you could have a look, since sometimes warning about Xorg stuff also appears in journalctl

I did post the journal, which includes the suspension and the resume.

fabien wrote: ↑2022-06-04 13:17 How do you know the UUID was invalid ?

You're right, that was just an assumption, since the machine waited and waited until the emergency shell came up.

Usually, there'd be a prompt for my LUKS password.

Yes, since I didn't remember the UUID, I just wrote "...", and yes, I assumed it's waiting for a partition.

I still don't understand why the system waited for an invalid UUID, but I then wanted to replace UUID references by devices, but the message remained.

fabien wrote: ↑2022-06-04 13:17 You are mistaken by the fact that the error message uses UUID to refer to the disk).

I'm not sure I understand. Are you saying that the UUID in the error message does not refer to a disk device? If so, what else could it be?

canci wrote: ↑2022-06-04 13:10

ralphb wrote: ↑2022-06-04 12:36 Unfortunately, .xsession-errors doesn't contain timestamps, so I don't know how far to go up.

But journalctl does.

Yes indeed. And?

Unfortunately, .xsession-errors doesn't contain timestamps, so I don't know how far to go up. But there are also entries like this: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 975, resource id: 25165837, major code: 2 (ChangeWindowAttributes), minor code: 0 kdeinit5: PID 247365 t...

Hmm, maybe the -b -1 was not quite right. It actually happened right now, so screw my overnight hypothesis. Here's the current journal Jun 04 14:19:29 cassiopeia kernel: microcode: CPU17: patch_level=0x08701013 Jun 04 14:19:29 cassiopeia kernel: ACPI: \_PR_.C00B: Found 2 idle states Jun 04 14:19:29 ...

You do not know why it happened and you are expecting that it will not happen again ? Prepare to be disappointed.

*sigh* I fully agree with you here! And I know which problem UUIDs are meant to solve, but so far, my experience has been the other way around.

I'm using the nvidia driver, as nouveau (I think) was freezing my machine occasionally. Here's the inxi output: Graphics: Device-1: NVIDIA TU116 [GeForce GTX 1660] driver: nvidia v: 460.91.03 Display: x11 server: X.Org 1.20.11 driver: loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa resolutio...

By "removing UUIDs" I meant replacing them with /dev/XXX. There were only two entries anyway. And yes, I meant update-initramfs -u -k all but omitted it. I also didn't use &&, but wanted to avoid having too many code blocks to improve legibility. But I finally decided to reinstall ...

Thanks for the suggestion! That seems to be the mapping from UUID to device, which I didn't know about, so I guess I could just add a new link for the missing UUID.

But in terms of eliminating the usage of all UUIDs, this probably doesn't help.

I've installed Debian 11 on my notebook, with one boot partition and an encrypted root partition. Everything was well. Overnight, my notebook wouldn't start anymore and displayed this message instead: cryptsetup: waiting for encrypted source device UUID=.... I don't have the slightest clue why this ...

I have a pretty new Debian 11 installation on my desktop computer. If I resume my computer from suspension, my plasma desktop has disappeared: no background image, no panel, no widgets, no switching virtual desktops with the mouse wheel, etc. All the windows remain, though, and even the keyboard sho...

Oh wait, I found it -- KDE's regional setting were set to de_DE, so that was a quick fix.

Last week I switched from Kubuntu to Debian, which was generally pretty straight-forward. But there is a locale problem I don't understand. On my system, I have both en_US and de_DE locales generated, but then set the en_US locale as active. For root, everything is fine: cassiopeia:~# locale LANG=en...