no , it is much simpler, basically press super key or move the mouse to the mint logo🥸, then see the prefrences tab hover over it🤓, you should see "preferred application" once you click on it you will find it mr or ms @andrewta 🧐

did it work?

Thank you!

FS-UAE

Amiberry

Amiga Forever

Is it just alphabetical, and are you able to rename the printer/scanners?

Wobbly windows are fun! I also turned them off for stability. I should try them again sometime.

Adding additional DEs on Debian variants (Debian, Ubuntu, Mint) has always just plugged them in to my login page as a drop-down to choose between.

So I consider it pretty low risk. The main cost is disk space.

If the DE freezes up, a hard power button reboot will stop at the login page and allow choosing a different one, as long as the "automatic login" setting is turned off (and as long as I know I password).

Thank you for your reply, no I have not.

For clarification of the pop out video, I mean say you are playing a youtube video, firefox and its forks allow you to "pop-out" that video into a separate borderless always on top window. I use ublock origin for element blocking including advertising and other privacy related features.

I did think window manager extensions as I did play around with the obligatory wobbly windows and the like. But I prefer to have them turned off and have made sure they are all disabled. It was fun though.

A different DE was a consideration but I am a little nervous being new to linux of changing too much and getting myself into a situation where I do not have a GUI. I do have a means to do a system image so would probably wait until I have a recent backup and a system image before changing the DE. Ideally I'd like to fix whatever this issue is but I agree it would be a good diagnostic step.

Thank you for your help.

The issue where the window needs reloaded after some time does sound like software - specifically like a slow memory leak.

Plenty of us are using Cinnamon without that issue, but of course it could be you have some strange unlucky combination of hardware, patch version, etc.

I'm not sure b if the video thing is related. Pop-out videos come in many flavors, and most range from mildly anti-user to outright evil. So the video misbehaving could be down to the specific combination of site, site video digital rights management, how much spying they try to do while the video plays, how much of that spying Librewolf is set to block, and what day of the week it is (how fast your Internet connection is, that day, really).

Do you have any window manager extensions installed? (I know gnome has a whole extension ecosystem, but I'm but sure Cinnamon even supports Desktop extensions. If you don't remember adding anything, ignore this, it's a really long shot.)

You could try adding a second desktop environment (MATE is a popular enough 2nd choice) and see if the issues happen there, as well. You can switch desktop environments in a drop-down on the login page.

Have you changed the UI scaling at all?

Is this a laptop or desktop? If laptop, what brand/model and how new is it?

Just in case it's relevant, I had similar issues some years back on a new laptop, and it turned out some component in the laptop was newer than the kernel version that was included. A newer kernel (I think it was using HWE, or Hardware Enablement Kernel) sorted it out.

The drivers tool shows everything as OK. Also of note, I am using an AMD GPU so I am not dealing with any NVIDIA weirdness.

Have you launched the Drivers tool to see if it recommends anything?

One time I was having issues and I typed "drivers" into the Start menu, and it brought up a panel that recommended a driver update, which fixed some issues for me.

I don't know how that could happen aside from you unmounting it from /mnt and remounting it under /media. Your fstab is mounting it under /mnt at boot. Until you change the fstab, it will continue to be mounted under /mnt every time you reboot, and you will continue to have to access it manually before it is truly accessible to the system. /mnt is a special mountpoint for temporary, manually mounted drives, not system drives or system partitions.

You don't have to use /media, but since other, removable media will be mounted there, I find it practical to keep everything together. Just create the mountpoint folder in advance and set the ownership and permissions (you have to do all that as root), and then fstab will happily mount it there once you change that entry as well.

I also don't think you should use

auto nosuid,nodev,nofail,x-gvfs-show 0 0  

in fstab, but you should instead be using

ext4 errors=remount-ro 0 2  

Keep in mind, if you mess up fstab, the computer will no longer boot. Be sure to check it before rebooting with:

sudo findmnt --verify  

Example fstab:

UUID=4a7c4523-15a1-4552-b696-c0f510d57184 /media/schipelblort/4a7c4523-15a1-4552-b696-c0f510d57184		ext4	errors=remount-ro 0 2  

Example mountpoint:

/media/schipelblort/4a7c4523-15a1-4552-b696-c0f510d57184  

It needs to be owned by schipelblort and the permissions can be standard 755 or 750.

That's weird. When I dragged the folders over, they were mounted to /media. Hm. And it no longer worked to click on it since the folders were still pointing to /meda. Weird.

Well, everything is working now at least. I wonder if it's going to get pulled back to /mnt for some reason?

I would first change your mount point for the second drive so that it is mounted under

/media

and not

/mnt

Be sure to chown and chmod it accordingly. This in itself will resolve the issue with nemo not accessing links to the second drive until you first access it manually.

Then, if you really want to have your home folders recognized where they truly are, modify the user-dirs.dirs file to reflect the absolute paths to your home folders and reboot.

As with any system modifications, first make a backup!

alex@alex-MS-7C02:~/Desktop$ cat ~/.config/user-dirs.dirs  
# This file is written by xdg-user-dirs-update
# If you want to change or add directories, just edit the line you're
# interested in. All local changes will be retained on the next run.
# Format is XDG_xxx_DIR="$HOME/yyy", where yyy is a shell-escaped
# homedir-relative path, or XDG_xxx_DIR="/yyy", where /yyy is an
# absolute path. No other format is supported.
# 
XDG_DESKTOP_DIR="$HOME/Desktop"
XDG_DOWNLOAD_DIR="$HOME/Downloads"
XDG_TEMPLATES_DIR="$HOME/Templates"
XDG_PUBLICSHARE_DIR="$HOME/Public"
XDG_DOCUMENTS_DIR="$HOME/Documents"
XDG_MUSIC_DIR="$HOME/"
XDG_PICTURES_DIR="$HOME/Pictures"
XDG_VIDEOS_DIR="$HOME/Videos"

Ah, ok, I think what might be happening is because I just mirror the naming conventions of home on the second drive, maybe its getting confused?

So instead of going directory by directory, how can I just change the absolute location of home?

What does

cat ~/.config/user-dirs.dirs  

say?

ACPI errors are typically not important. Are you sure there are no other errors above or below your screenshot?

FWIW, you can use the following command to see what BIOS version you currently have, then check with the manufacturer to see what version is most up-to-date and install that. It may quiet down your dmesg/log output if nothing else.

Be warned, there is a certain risk to updating the BIOS. Things can go wrong or even create new problems, but in general it is advisable to keep the BIOS up-to-date. The command to determine what BIOS version you have installed is:

sudo dmidecode -s bios-version  

Also, you should try to boot with nothing unnecessary connected to the PC, to see if it behaves differently. A poorly initialized hardware device can cause any number of strange behavior. USB/Bluetooth devices are easily overlooked/forgotten/ignored as inconsequential, but can hang a system up. Also check the cable connections if it's a desktop PC.

On top of all that I would run fsck on your drive to make sure you aren't dealing with file corruption of some kind. This can be done during boot via the recovery console.

Reboot and hold the Shift key during boot. This will get you to the GRUB menu, even if it is not normally shown.

Select “Advanced options”

Select “Recovery mode” for the kernel version you are normally using.

In the recovery menu, select “fsck“

When prompted to remount the root filesystem, select “Yes“

When fsck completes, “Resume” will continue the boot process normally.

I hope this helps. If not, you may want to consider restoring from backup, assuming you have made a working backup via Timeshift or similar.

Barring that, you either need to dig much deeper into the logs and boot process, or simply reinstall the OS. Testing the hardware by booting a live USB session is also advisable - that can be done via the same USB image you probably used to install the OS to begin with. If the problem persists, then you know something has gone wrong with a hardware component.

Good luck, and keep us posted on your outcome.

ACPI ERROR

ACPI BIOS ERROR

Also; sry for the late

Because of short attention and lack of time to re-read and motivation to fix previous message because my brain is focused on next task in a short time to dedicate to Lemmy.

OP, FYI

You can still get to terminal by changing you tty session

compu9thinks jnplug Uoubdo am

How does anyone manage to fuck up writing that badly and somehow not notice? Do you not read what you write?

Since you have the terminal, either use it to browse your drive or drives to see which files are there and identify it. You may also install a nice file manager to do it graphically. Maybe it is just your graphical desktop that got any package uninstalled or has a fallback config or something. Or you installed an extra lightweight desktop without noticing or remembering. Deaktop or even session manager.

Yeah, I don’t think my SSD was that large.