I am still on Bullseye. I think I have tried Bookworm, but I ran into issues with SSH and Wayland IIRC. I don't know Gnome. Maybe it is better organized than KDE. I can't recall I ever did a successful upgrade after KDE3. On a side track. KDE is so crooked. One day my wife's PC would not show the desktop on the second screen The greeter was right, but after the desktop started the second monitor went "No Signal". When I logged in myself, I did have the second screen. So that must be a user profile error, right? Now she has her /home/mywife directory on the server. So I restored a backup of the previous day. Same thing. Restored the backup from a week ago. Same thing. Deleting the .KDE and .config directory. Same thing. Copied my own .KDE and .config. Same thing. Only deleting the complete home directory and starting from scratch brought back the second screen. And then restoring all her files, excluding anything that could have to do with a GUI.
Like I said a lot breaks when dist-upgrading. udev is one of them. Was that it?
I haven't seen this running Fedora. I've run KDE and Gnome without any problems.
I've been lax. They don't want to upgrade from Fedora 39 to Fedora 41. Time to download a full distro and load from the stone age I guess.
I've been lax. They don't want to upgrade from Fedora 39 to Fedora 41. Time to download a full distro and load from the stone age I guess.
That sounds frustrating. There was probably a simpler fix, but it sometimes requires a lot of patience and googling to figure out. The “scorched earth” approach is something I have resorted to in the past. Not so much anymore.
Nope, it wasn’t udev.
Another hint; technically, it wasn’t the fault of Debian, or Linux in general.
I have one more guess: the controversial systemd, but I don't know Linus' position on that, and I know Debian uses it.
Not Vbox or systemd.
It was, of course, Nvidia drivers! Very surprised nobody guessed. This has been a thorn in the sides of Linux users for decades now. Linus famously declared his opinion about Nvidia.
Normally DKMS takes care of building new modules, and it tried but failed to build Nvidia modules for the new kernel. I still had GUI access because the primary video on my laptop is the integrated Radeon graphics. I tried a few things and then finally did a “sudo apt purge nvidia*” to flush the toilet and start fresh. Despite this, and some more googling, the module builds continued to fail. I finally ignored the official advice and download the driver package from Nvidia and installed it. Modules built fine and it is working. When I upgrade my kernel again, it’ll probably break again, but it isn’t a show stopper. Also important to note that I am now running Debian “testing” so I have no right to complain. By the time 13 is released I bet this issue will be ironed out.
This didn’t take me an hour. There was also some issue with OpenWebUI. It wouldn’t start up anymore. I didn’t even bother troubleshooting it. Just flushed the toilet and re-installed. Probably something python-related. I chose to go with the docker install method this time.
It was, of course, Nvidia drivers! Very surprised nobody guessed. This has been a thorn in the sides of Linux users for decades now. Linus famously declared his opinion about Nvidia.
Normally DKMS takes care of building new modules, and it tried but failed to build Nvidia modules for the new kernel. I still had GUI access because the primary video on my laptop is the integrated Radeon graphics. I tried a few things and then finally did a “sudo apt purge nvidia*” to flush the toilet and start fresh. Despite this, and some more googling, the module builds continued to fail. I finally ignored the official advice and download the driver package from Nvidia and installed it. Modules built fine and it is working. When I upgrade my kernel again, it’ll probably break again, but it isn’t a show stopper. Also important to note that I am now running Debian “testing” so I have no right to complain. By the time 13 is released I bet this issue will be ironed out.
This didn’t take me an hour. There was also some issue with OpenWebUI. It wouldn’t start up anymore. I didn’t even bother troubleshooting it. Just flushed the toilet and re-installed. Probably something python-related. I chose to go with the docker install method this time.
I will move to Trixie in around 4 months.
Kernel 6.12 is a big one for audio, with preempt support for real-time processor attention.
I wouldn't have guessed that. I had an Nvidia card sometime in the late 90s to early 00s, running Slackware, Nvidia drivers weren't supplied with the distribution. I wouldn't have expected that Debian supplied Nvidia drivers, I thought they would be incompatible with their policies.
There are proprietary drivers available in the non-free repository. Debian is a lot more relaxed about this stuff these days.
There is also an open version of the Nvidia driver (finally) but it is still a bit wonky from what I have read. I have not tried it, so this is hearsay.
I have always been an AMD/ATI guy so I mostly avoided the Nvidia driver issue, but this laptop I am running has a secondary Nvidia 2050 GPU which, honestly, is worth the trouble of installing proprietary drivers.
There is also an open version of the Nvidia driver (finally) but it is still a bit wonky from what I have read. I have not tried it, so this is hearsay.
I have always been an AMD/ATI guy so I mostly avoided the Nvidia driver issue, but this laptop I am running has a secondary Nvidia 2050 GPU which, honestly, is worth the trouble of installing proprietary drivers.
Don't mix and match. I got bit by grub once.
WINE... last and only time I used that was back in '96. In a Sun Ultra Solaris machine.
Computers are cheap.
Get one for each OS.
Network them.
Now for those of us who use git on a daily basis... "Linus uses CVS at home"... I almost fell off my chair at work when someone sent me the link... We ALL almost fell of our chairs when the link made it through the office. BRILLIANT...
Last edited:
So, one for Debian, one for Fedora, one for Arch…
Or just actually make use of all your CPU power and RAM by utilizing virtualization. I have 4 servers on my network, 3 of them are virtual. I have 6 workstations, 5 of them are virtual.
I think I'm down to four Windows PCs, three Raspberries, One Ubuntu, two chromebooks, some Android..... as I said, computers are cheap nowadays.
I need to install a Git server at home to store all of my media and configuration files....
%git clone #Eh 0o0)() ljnlkl ))8ddd 808080 zzzzzzzzzzzzzzzttt............................ . . .... <HEAD>....
I need to install a Git server at home to store all of my media and configuration files....
%git clone #Eh 0o0)() ljnlkl ))8ddd 808080 zzzzzzzzzzzzzzzttt............................ . . .... <HEAD>....
Last edited:
I felt that... I use git and emacs.
A good gui client makes git much less painful. As does knowing what concepts/commands to know and which to ignore. And if you mess things up, use the reflog.
Sorry, I lost my <HEAD>
@jgf On Emacs.... I used to work with people, early AI researchers, PhDs, around 97, who used Emacs for everything. They'd log into Solaris, launch Emacs and use that as their document processor, email, editor, compiler, console, etc, etc... It requires a GUI. They never used the mouse, they were lighting quick with the keyboard commands.
I only use Git with the command line. git clone... my favorite, when you've lost your <HEAD>, you clone again, copy the new code over and continue...
@jgf On Emacs.... I used to work with people, early AI researchers, PhDs, around 97, who used Emacs for everything. They'd log into Solaris, launch Emacs and use that as their document processor, email, editor, compiler, console, etc, etc... It requires a GUI. They never used the mouse, they were lighting quick with the keyboard commands.
I only use Git with the command line. git clone... my favorite, when you've lost your <HEAD>, you clone again, copy the new code over and continue...
Last edited: