Do i need to repair mint after a few hard shut-downs?

Brian Alex

Member
Joined
Feb 28, 2025
Messages
82
Reaction score
51
Credits
790
I can't remember what caused the need to do the hard shut-downs (just holding the power button in until it powers off) and I am in the process of learning all of the shortcuts and commands to attempt a proper shut-down if needed. I am noticing problems on my beloved Mint 22.3 such as today a sudden blue screen when I attempted to close a program. Yesterday it woke from sleep with no desktop icons. Also today I could not display the BlueTooth settings to connect my headphones. I'm encountering problems such as these and I feel like there must be a way to detect and repair any system file issues. I am researching this subject but some (all) of the posted solutions are slightly beyond my comfort zone. My question is; Is there an easy, newbie-level program to do this such as the equivalent of Windows DISM and SFC utilities? Thanks -BA

ps- I just realized that the HDMI connection to my TV might be an issue since I haven't yet learned how to set this up.
 


Did you keep a Timeshift snapshot of Mint 22.2, by any chance ?
 
Last edited:
as its Debian based distro, you may like to..

TRY from a terminal in order run
sudo dpkg configure -a
sudo apt update && apt
--fix-missing
sudo apt --fix-broken install
sudo apt upgrade
sudo apt autoremove
 
Last edited:
I have hard shutdown Linux quite a few times over the years on the desktop and also on servers, never caused an issue.
 
as its Debian based distro, you may like to..

just a note, Brian - you might like to edit that to reflect that all those commands require sudo?

Wiz
 
ps- I just realized that the HDMI connection to my TV might be an issue since I haven't yet learned how to set this up.

i use a tv via hdmi for my monitor, never had an issue - the only thing I did was to disable the audio component so it doesnt try to pipe audio to the tv's speakers - I have dedicated audio hardware for that. not sure how to do it in debian though as I use arch.

fsck can be used to check/repair a filesystem, but it can only run against an unmounted filesystem. I've never needed to use it on the systems that I have that run debian derivitives (mostly as I dont modify them often). my understanding is that you boot into recovery mode, then run it. I'm sure the debian gurus know much more than my limited understanding.
 
as its Debian based distro, you may like to..

TRY from a terminal in order run
sudo dpkg configure -a
sudo apt update && apt
--fix-missing
sudo apt --fix-broken install
sudo apt upgrade
sudo apt autoremove
Thank you.
I tried the first command and received the following:
"dpkg: error: need an action option

Type dpkg --help for help about installing and deinstalling packages [*];
Use 'apt' or 'aptitude' for user-friendly package management;
Type dpkg -Dhelp for a list of dpkg debug flag values;
Type dpkg --force-help for a list of forcing options;
Type dpkg-deb --help for help about manipulating *.deb files;

Options marked [*] produce a lot of output - pipe it through 'less' or 'more' ! "
 
Did you keep a Timeshift snapshot of Mint 22.2, by any chance ?
Yes, I have TS going back to Nov.'25. Good point. If I need to I'll restore using this utility. -BA
 
I have hard shutdown Linux quite a few times over the years on the desktop and also on servers, never caused an issue.
This gives me hope. Thanks.
 
did you put the space between configure and -a?
you can continue with the rest, but it is best to copy and paste to the terminal
 
Yesterday it woke from sleep with no desktop icons. Also today I could not display the BlueTooth settings to connect my headphones.
I would make use of one of your Timeshift snapshots, sooner rather than later, Brian

Mint 22.3 is a new release, and until some of these problems get sorted out at developer level, you may be giving yourself an unnecessarily hard time.

Mint 22.2 is very reliable and still has support until April 2029.
 
fsck can be used to check/repair a filesystem, but it can only run against an unmounted filesystem. I've never needed to use it on the systems that I have that run debian derivitives (mostly as I dont modify them often). my understanding is that you boot into recovery mode, then run it. I'm sure the debian gurus know much more than my limited understanding.
That is right, fsck only works with unmounted filesystems. The article I linked explains how to create a mark for the system to run fsck at next boot, before mounting all the filesystems.
 
You can also make a desktop launcher to do this job

Right click on desktop....select Create a new launcher here...see the screenshot below,

2026-01-23_09-26.png


Click on ok. Done.

A double click and your pc will shutdown.
 
You can also make a desktop launcher to do this job

Right click on desktop....select Create a new launcher here...see the screenshot below,

View attachment 29915

Click on ok. Done.

A double click and your pc will shutdown.
I tried this but I don't see what to double click. Of course I have ~100 desktop icons so maybe it is hiding. However the main thing is I have to do a hard shutdown when there is no cursor or keyboard response. If there is a cursor I just right click desktop and choose "open in terminal" and use the terminal to reboot. Sorry to be a time-sink newbie. I'll get this eventually. -BA
 
did you put the space between configure and -a?
you can continue with the rest, but it is best to copy and paste to the terminal
Yes sir. I copy and pasted.
I would make use of one of your Timeshift snapshots, sooner rather than later, Brian

Mint 22.3 is a new release, and until some of these problems get sorted out at developer level, you may be giving yourself an unnecessarily hard time.

Mint 22.2 is very reliable and still has support until April 2029.
If it gives me any more guff I will do this. I suppose I just select a TS date and click "restore" and follow the prompts. Hopefully it is not too involved. -BA
 
Instead of a hard shut down maybe try:

Code:
sudo shutdown -h now

Linux Mint 22.3 known issues:

Other ideas:-

* Roll back to an older kernel <or> perhaps think about installing LM 21 or 22.
It's still supported until April of 2027.

Missing icons is possibly a broken desktop extension and falure in extension upgrades.
A mis-configuration in the entire config that's related to the LM system as a whole...ie: the .config/ or the session or .xsession?.
See screenshot.

Also, what DE are you running? Gnome?
Code:
echo $DESKTOP_SESSION

Code:
OR>
echo $XDG_CURRENT_DESKTOP
 

Attachments

  • Config.png
    Config.png
    226.9 KB · Views: 45
Last edited:


Follow Linux.org

Members online


Top