Maybe it still appears in /var/lib/dpkg/status? If it is, try deleting the entry from there.
I use openmediavault for my home NAS, it does all the heavy lifting for you with a nice GUI so you don't have to config everything yourself. I'd recommend checking it if you don't have a lot of experience with RAID setups or don't want to do manually.
Just please remember that RAID is not a backup solution, it's a redundancy solution. If you have data corruption on one side, it can copy itself to the other mirror and then you're screwed. If your media is important, keep a proper separate backup.
I noticed the newest kernel package is named "linux-image-6.8.0-76060800daily20240311-generic".
Why is it named daily? Does it mean we will be getting more frequent kernel updates? Or just some daily build that someone forgot to change its name?
Turns out it was a problem with the Steam client itself, I think it's because the steam:i386 package isn't used anymore and it's now steam-installer, but something with the steam update didn't run correctly. After purging all the old steam packages and reinstalling from Pop Shop it started running again.
I ran apt upgrade on my laptop today after not using it for a couple of weeks, the main thing was upgrade of NVIDIA driver to 545.29.06, but there was also some change on one of the steam-lib packages (I'm using the Steam deb version, not flatpak). Ever since upgrading, Steam crashes on start.
I tried searching for recently reported issues with the Steam Linux client but can't find anything. Is this a known issue? Any suggestions on what I can check/do?
=-=-=
Here's the segfault from syslog, I have a bunch of core files but don't know if I can get anything useful from them.
Dec 6 17:13:30 computer steam.desktop[5200]: steam.sh[5200]: Running Steam on pop 22.04 64-bit Dec 6 17:13:30 computer steam.desktop[5200]: steam.sh[5200]: STEAM_RUNTIME is enabled automatically Dec 6 17:13:30 computer steam.desktop[5321]: setup.sh[5321]: Steam runtime environment up-to-date! Dec 6 17:13:31 computer steam.desktop[5200]: steam.sh[5200]: Steam client's requirements are satisfied Dec 6 17:13:31 computer steam.desktop[5392]: 12/06 17:13:31 Init: Installing breakpad exception handler for appid(steam)/version(1701289036)/tid(5392) Dec 6 17:13:33 computer steam.desktop[5392]: /home/user/.themes/Sweet-Dark-v40/gtk-2.0/main.rc:727: error: unexpected identifier 'direction', expected character '}' Dec 6 17:13:33 computer steam.desktop[5392]: /home/user/.themes/Sweet-Dark-v40/gtk-2.0/apps/chrome.rc:50: error: invalid string constant "button", expected valid string constant Dec 6 17:13:33 computer steam.desktop[5392]: /home/user/.themes/Sweet-Dark-v40/gtk-2.0/apps/xfce.rc:79: error: invalid string constant "entry", expected valid string constant Dec 6 17:13:33 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: Uploading dump (out-of-process) Dec 6 17:13:33 computer steam.desktop[5404]: /tmp/dumps/crash_20231206171333_5.dmp Dec 6 17:13:33 computer crash_20231206171333_5.dmp[5404]: Uploading dump (out-of-process)#012/tmp/dumps/crash_20231206171333_5.dmp Dec 6 17:13:33 computer kernel: [ 72.142532] show_signal_msg: 19 callbacks suppressed Dec 6 17:13:33 computer kernel: [ 72.142534] steam[5392]: segfault at 0 ip 00000000f7ab5045 sp 00000000fffb3e8c error 4 in libc.so.6[f7a20000+182000] likely on CPU 4 (core 4, socket 0) Dec 6 17:13:33 computer kernel: [ 72.142544] Code: 40 38 ca 0f 84 4d 01 00 00 80 f9 00 0f 84 71 01 00 00 40 4f 75 14 8a 08 38 ca 0f 84 36 01 00 00 80 f9 00 0f 84 5a 01 00 00 40 <8b> 08 bd ff fe fe fe bf ff fe fe fe 01 cd 31 cd 01 cf 8d 40 04 0f Dec 6 17:13:33 computer steam.desktop[5200]: /home/user/.local/share/Steam/steam.sh: line 798: 5392 Segmentation fault (core dumped) "$STEAMROOT/$STEAMEXEPATH" "$@" Dec 6 17:13:35 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: Finished uploading minidump (out-of-process): success = yes Dec 6 17:13:35 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: response: CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206 Dec 6 17:13:35 computer steam.desktop[5404]: crash_20231206171333_5.dmp[5404]: file ''/tmp/dumps/crash_20231206171333_5.dmp'', upload yes: ''CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206'' Dec 6 17:13:35 computer crash_20231206171333_5.dmp[5404]: Finished uploading minidump (out-of-process): success = yes Dec 6 17:13:35 computer crash_20231206171333_5.dmp[5404]: response: CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206 Dec 6 17:13:35 computer crash_20231206171333_5.dmp[5404]: file ''/tmp/dumps/crash_20231206171333_5.dmp'', upload yes: ''CrashID=bp-11a3ce92-de87-49ca-8b7c-7e1622231206'' Dec 6 17:13:35 computer systemd[3855]: app-gnome-steam-5200.scope: Consumed 1.187s CPU time.
Yeah, some vendors do this, I think the .exe basically unpacks the .bin file then calls some API or something to push it from Windows while it's running. Probably done for the sake of more casual users who don't know/want to mess with the actual BIOS UI.
Just to add to that, you also have the option of using Flatpak, which already comes installed by default in Pop OS and integrated into Pop Shop. With Flatpak you can usually get a more recent version of the app, but the downside is larger install size.
Worth a try. I should probably switch back to X11 anyway since Slack screen sharing is broken on Wayland for quite some time and it doesn't look like they're gonna fix it.
I have a Dell Precision laptop with an nvidia GPU, today for the second time I've experienced a freeze while updating drivers. This also happened to me the last time a driver update was published. The display just froze and I couldn't do anything, though it seemed it was just the display dying because I had some Youtube video playing at the time and the audio kept running. Tried to switch to another TTY and that froze too before I could login. I just left it alone for a few mintues, hoping it's still running the upgrade in the background, then forced a cold boot and the laptop came up normally. I didn't look for any logs or traces so don't really have more info.
I'm running Wayland, not sure if it's relevant/related.
Wondering if this is a known issue or if other people seen it. If it is known, anything I should do to avoid it?
Thank you for releasing the Mesa 23.1 update. I was hoping you'll get to it for some time.
Did you check if the recovery partition was recognised and mounted? Maybe some voodoo made it fail to mount, but it worked after a reboot.
If you're using the default bluetooth connection from settings, maybe try installing blueman instead.
Oh yeah, Time Commando. Had the demo as a kid and I played it so much, thought it was the best game ever. The demo was just some parts of the prehistoric and roman levels, I think. Then years later I suddenly remembered it and picked it up on sale from GOG, and oh boy, did this game age badly. The cutting edge graphics for its time are just plain ugly today, and the gameplay is boring. My advice to you is stick to your memories but don't bother with the actual game.
I have the wireguard configs imported with nmcli and use WireGuard Indicator to turn it on/off.
Probably the Quest for Glory series for me. Played them so many times that I can just pick up any one them with any character and get sucked right back in to the game. I've had an itch lately to do a full playthrough of all 5 games after not touching them for a long time but I have little free time and too much backlog...