Debian User Forums

I just went through all relevant bugs for "debian-installer" and didn't find anything related - if you'd like to look for yourself check it out here - https://bugs.debian.org/debian-installer edit: anything before bug #103500-ish is before Bookworm's release so that might narrow your searc...

...And with the LXQt ISO file, the graphical expert install as well as the text expert install did not ask me if I want the non-free firmware packages, they were installed automatically. I noticed the firmware=never parameter only worked with the netinst ISO file. I think this is worthy of a bug re...

aptitude is pretty good about offering more than one solution if more than one is available. Glad you got it sorted

libelf1 0.190-1+b1 isn't available in Trixie, at least not for amd64 - sure looks like this came from Unstable.

Looks like the thing to do would be to remove any packages installed from Unstable, remove Unstable from your sources.list, do an apt update and then reinstall Steam.

It's a security update - the CVE says versions < 1.105.1 are vulnerable. The package tracker says the package is in bullseye-backports, bookworm-backports, Trixie and Sid and does *not* appear to be in regular Bookworm. Strange.

https://security-tracker.debian.org/tra ... 2024-31208

This sure sounds like a hardware issue. Are you sure battery is charged and external power supply is working?

Aki wrote: ↑2024-04-23 16:15Therefore, it looks that "." in not allowed by default.

I stand corrected. Thanks, Aki

There is no debian-security or unstable-updates repository for Unstable. This is all you need in sources.list for Unstable: deb http://deb.debian.org/debian/ unstable main contrib non-free non-free-firmware # deb-src http://deb.debian.org/debian/ unstable main contrib non-free non-free-firmware I co...

What I see in the screenshot are all recommended packages and can be ignored or installed, whichever you prefer.

Usernames must conform to IEEE 1003.1-2001; legal characters are letters, digits, underscores, periods, at signs (@) and dashes but the username may not *start* with a dash.

There used to be an issue with systemd and periods in usernames but that has been resolved.

Hope this helps -

You know, I think we just discovered an aptitude thing that everybody should know - that sudo aptitude search ~o above tells you which packages aptitude is calling obsolete because they're not available in mapped repoitories. Check out mine - quite a few of these are manually installed debs wizard@w...

Moved to Off-Topic because this is not a Debian question.

nalterov wrote: ↑2024-04-22 16:03...Should I check them? How can I do it? I will try to see how now

You could useNote that's ~o, not -o. That'll give you a list of packages you have installed that are not currently available in repositories. I'd check those

Yeah, I've seen that on my machines also.

Do you have any non-Debian packages installed on the machine? Maybe something like that is causing issues.

I'm not sure what's going on there then - none of the four Sid installations I have here are doing this. It's clear you've got a package installed that apt doesn't like; one thing you can do is install aptitude and let it do its thing - aptitude will offer solutions that apt doesn't. It should ident...

Try apt full-upgrade and if the upgrade still doesn't look safe we'll need to look at non-Debian repositories you have enabled - they may be in /etc/apt/sources.list.d

But - if full-upgrade doesn't look safe don't upgrade!

Moved to Testing and Unstable.

...if I care about the outcome of the prior command I run the follow-on command separately. I'm sure you already know this stuff so this is more for our studio audience but the reason I use the double ampersand thing is that if program 1 crashes (or exits with a nonzero exit code) bash won't attemp...

I'm locking this thread. If you have an issue with the way this forum is moderated take it up privately with a forum admin.

@sunrat @donald @4D696B65 @dilberts_left_nut @Aki

Linuxgaming1824 wrote: ↑2024-04-21 17:49I think I've seen bad behaviour with the ampersands before where commands run into each other...

I find that hard to believe considering the purpose of the double ampersand. The double ampersand will not execute a second command unless the first command exited successfully.