seems like it is a bug within chrome. since no other window on my machine has this behavior and it just appeared after updating chrome..
found an open bug, too:
hope it gets fixed soon! ;)
sudo curl [options] -o <file> <url>
sudo rm <file>
echo <debline> | sudo tee <file>
sudo rm <file>
sudo apt install <package>
sudo apt purge --autoremove <package>
So yes, the opposite is really to simply remove the files that you created in addition to purging the package and any ...
This is ultimately a result of Windows using the drives to cache some data so that it can start up faster. It can be fixed by changing some settings in windows.
Start by opening cmd as admin and execute powercfg -H off to turn off the hibernate feature. Next navigate to the power options in the system management and deactivate fast startup as well as the ...
Well, this is a bit tricky.
The authentication methods for various services are controlled by files in /etc/pam.d/ directory. The pam-auth-update command will update the common-* files, which are @included by the service-specific files.
I'm more of a KDE guy myself, but Cinnamon is a GNOME derivative, so its initial login is probably handled by /etc/pam.d/...
dpkg -i attempts to process every package file, in the order specified on the command line. You used glob expansion (*), which usually means alphabetical order. But as you can see from these messages, the package dependencies mean they have to be installed in a specific order:
ca-certificates-mono pre-depends on mono-runtime-common (>= 5.20)
I am not really familiar with apt or dpkg. But, if they are similar to how rpm and yum operate, your problem is that you are missing a depndency. From your "failed" output:`dpkg: regarding .../ca-certificates-mono_220.127.116.11+dfsg-2_all.deb containing ca-certificates-mono, pre-dependency problem:
ca-certificates-mono pre-depends on mono-runtime-...
If you installed the package using sudo apt install signal-desktop as instructed at signal.org's download page, then there should be another (system-wide) desktop file at /usr/share/applications/signal-desktop.desktop.
If you right-click the Signal (env) menu item, does it offer any "properties" option or similar? That might tell you more about ...
@telcoM, you hit the nail on the head. Didn't even think to check if the installation was UEFI or not. Reinstalled it with the USB and saw that the first boot option wasn't it, so I changed it and voila. Didn't even have to put anything into grub, it just detected Windows 10 and automatically set a menu entry.