Linux - Troubleshooting - Revision history

Tinker: /* Dealing with Cinnamon Crashes */

2021-11-12T19:10:09Z

Dealing with Cinnamon Crashes

Tinker at 19:05, 12 November 2021

2021-11-12T19:05:42Z

Tinker: /* Boot Problems */

2021-10-26T05:05:34Z

Boot Problems

Tinker: /* Boot Problems */

2021-10-19T17:07:02Z

Boot Problems

Tinker at 19:54, 10 August 2021

2021-08-10T19:54:36Z

Tinker at 18:35, 9 August 2021

2021-08-09T18:35:23Z

Tinker at 18:14, 7 July 2021

2021-07-07T18:14:55Z

Tinker at 01:11, 1 December 2020

2020-12-01T01:11:25Z

Tinker at 04:20, 1 July 2020

2020-07-01T04:20:19Z

Tinker: Created page with "= '''One of my Mint 19.1 machines seems to regularly refuse to acknowledge mouse clicks...''' = = Mint 19 Update Manager occasionally seems..."

2020-07-01T04:11:02Z

Created page with "= '''One of my Mint 19.1 machines seems to regularly refuse to acknowledge mouse clicks...''' = = Mint 19 Update Manager occasionally seems..."

New page

= '''One of my Mint 19.1 machines seems to regularly refuse to acknowledge mouse clicks...''' =

= Mint 19 Update Manager occasionally seems to have an issue where it cannot refresh the update list. =
Most likely, it is a repository problem that will resolve itself if you just wait a bit & try again.

= Mint is trying to eliminate Samba... =
* [https://forums.linuxmint.com/viewtopic.php?t=272334 [SOLVED]Mint 19 Network SAMBA shares not shownin File Manager]
* [https://forums.linuxmint.com/viewtopic.php?f=42&t=270442 Mint 19 and Samba File Sharing Changes]
* [https://forums.linuxmint.com/viewtopic.php?f=42&t=88146&start=0 HowTo: Samba Browsing Problems Checklist]
* [https://forums.linuxmint.com/viewtopic.php?f=42&t=192794?f=42&t=192794 Resetting Mint's Default umask to 002]

= [https://forums.linuxmint.com/viewtopic.php?t=282973#p1561928 Unable to launch "cinnamon-session-cinnamon"] =
<code>apt install mint-meta-cinnamon</code>

= "You have ''X'' broken package on your system! =
I was updating, upgrading Thunderbird from the Update Manager. I got a message:
"You have 1 broken package on your system!
Use the "Broken" filter to locate it."

What is that, how do I run it?
* <code>sudo apt-get install -f</code>

= I was removing unwanted software from my Linux Mint machine and went too far... =
* '''Unable to launch "cinnamon-session-cinnamon" X session "cinnamon-session-cinnamon" not found; Falling back to default session'''
* aaarrrggg...
* Open an SSH session to the machine
** <code>apt install mint-meta-cinnamon</code>
* aaahhh...   :)

← Older revision		Revision as of 19:10, 12 November 2021
Line 64:		Line 64:

	==Dealing with Cinnamon Crashes==		==Dealing with Cinnamon Crashes==
		+
		+	===Restarting Cinnamon from the command line===
		+
		+	If you can SSH into the machine (I most commonly have to deal with this on VMs...), you can often restart Cinnamon by:
		+
		+	* <code>cinnamon --replace --display=:0 &</code>
		+
		+	(This came from [https://forums.linuxmint.com/viewtopic.php?t=159772 a discussion on the Linux Mint forums])

← Older revision		Revision as of 19:05, 12 November 2021
Line 61:		Line 61:
	*<code>sudo service systemd-resolved restart</code>		*<code>sudo service systemd-resolved restart</code>

−	But not always... :(~~<br />~~	+	But not always... :(
		+
		+	==Dealing with Cinnamon Crashes==

@@ Line 4: / Line 4: @@
 This is most commonly caused by corruption of the filesystem (Either a bad shutdown or a failing drive...)
-Run the <code>fsck</code> command to repair the filesystem
+Run the <code>fsck</code> command to repair the filesystem ('''Note''': it might be a partition other than '''sda1''', you can do an <code>ls /dev/sd*</code> & see if there are more partitions...)
 *<code>fsck -y /dev/sda1</code>

@@ Line 1: / Line 1: @@
 ==Boot Problems==
-[https://prognotes.net/2018/04/linux-mint-initramfs-prompt-at-boot/ Mint fails to boot.  Lands in BusyBox with an '''(initramfs)''' prompt]
+===Mint fails to boot.  Lands in BusyBox with an '''(initramfs)''' prompt===
 =='''<span style="color:#c0392b">One of my Mint 19.1 machines seems to regularly refuse to acknowledge mouse clicks...</span>'''==

@@ Line 44: / Line 44: @@
 ==Mint 19.3 machine periodically fails to properly use my local DNS server==
-</div> </div>Dunno what's causing this, but a quick fix seems to be:
+</div>I'm thinking it's related to the machine it happens to being due for a complete rebuild...
 *<code>sudo service systemd-resolved restart</code>
 But not always...  :(<br />

@@ Line 1: / Line 1: @@
-== Boot Problems ==
+==Boot Problems==
 [https://prognotes.net/2018/04/linux-mint-initramfs-prompt-at-boot/ Mint fails to boot.  Lands in BusyBox with an '''(initramfs)''' prompt]
@@ Line 41: / Line 41: @@
 [https://forums.linuxmint.com/viewtopic.php?t=231342#p1225436 Re: Linux Mint 18 Remote Desktop (No Security types supported)]
-<div class="postbody"><div id="post_content1225436"><div class="content" style="margin-left: 40px">It wouldn't matter if the box you're coming from is Windows 7/8/10, MacOS, or Linux, or if you're running RealVNC, tightVNC, or Remmina--you'll have the same problem. The encryption used by Vino-server on Ubuntu/LM seems to be incompatible with that used by anything else and the result is no security type (0) instead of off/none (1) or normal (2). The only way to make it work is to diable its incompatible encyrption. One way is:<br /> <br /> '''gsettings set org.gnome.Vino require-encryption false'''<br /> <br /> Once you do that, you want to ensure VNC/5900+ is not open in your firewall (gufw). You can then tunnel VNC through ssh ([[Software - SSH|install OpenSSH Server]]) or use RDP (install xrdp) for security. However, if you do the latter, you'll find Vino also doesn't spawn on port 5910+ as xrdp expects. So you'll have to edit the xrdp config file and replace port=-1 with port=5900 to get it to work. You'll also have to have a logged in session running on the server for this VNC to work.<br /> <br /> Install xrdp on a Raspberry Pi and it just works.I have several running headless for various functions. sessman runs on 3350 and xrdp on 3389. Upon connection, Xvnc wakes up on 5910 for xrdp to link to.</div> <div class="signature" id="sig1225436" style="margin-left: 40px">Desktop: HP Z240 Quad-Core Xeon, 32GB RAM, 500GB SSD, Nvidia graphics, 27" monitor<br /> Laptop:::: HP Zbook Quad-Core i7,,,,, 32GB RAM, 500GB SSD, Nvidia graphics, 15" display<br /> OS Both: Linux Mint 18 Sarah Cinnamon, kernel 4.4.0-45.66</div> </div> </div>
+<div class="postbody"><div id="post_content1225436"><div class="content" style="margin-left: 40px">It wouldn't matter if the box you're coming from is Windows 7/8/10, MacOS, or Linux, or if you're running RealVNC, tightVNC, or Remmina--you'll have the same problem. The encryption used by Vino-server on Ubuntu/LM seems to be incompatible with that used by anything else and the result is no security type (0) instead of off/none (1) or normal (2). The only way to make it work is to diable its incompatible encyrption. One way is:<br /> <br /> '''gsettings set org.gnome.Vino require-encryption false'''<br /> <br /> Once you do that, you want to ensure VNC/5900+ is not open in your firewall (gufw). You can then tunnel VNC through ssh ([[Software - SSH|install OpenSSH Server]]) or use RDP (install xrdp) for security. However, if you do the latter, you'll find Vino also doesn't spawn on port 5910+ as xrdp expects. So you'll have to edit the xrdp config file and replace port=-1 with port=5900 to get it to work. You'll also have to have a logged in session running on the server for this VNC to work.<br /> <br /> Install xrdp on a Raspberry Pi and it just works.I have several running headless for various functions. sessman runs on 3350 and xrdp on 3389. Upon connection, Xvnc wakes up on 5910 for xrdp to link to.</div> <div class="signature" id="sig1225436" style="margin-left: 40px">Desktop: HP Z240 Quad-Core Xeon, 32GB RAM, 500GB SSD, Nvidia graphics, 27" monitor<br /> Laptop:::: HP Zbook Quad-Core i7,,,,, 32GB RAM, 500GB SSD, Nvidia graphics, 15" display<br /> OS Both: Linux Mint 18 Sarah Cinnamon, kernel 4.4.0-45.66</div>

@@ Line 1: / Line 1: @@
-= '''<span style="color:#c0392b">One of my Mint 19.1 machines seems to regularly refuse to acknowledge mouse clicks...</span>''' =
+== Boot Problems ==
-= Mint 19 Update Manager occasionally seems to have an issue where it cannot refresh the update list. =
+=='''<span style="color:#c0392b">One of my Mint 19.1 machines seems to regularly refuse to acknowledge mouse clicks...</span>'''==
 Most likely, it is a repository problem that will resolve itself if you just wait a bit & try again.
-= Mint is trying to eliminate Samba... =
+==Mint is trying to eliminate Samba...==
 * [https://forums.linuxmint.com/viewtopic.php?t=272334 [SOLVED]Mint 19 Network SAMBA shares not shownin File Manager]
-* [https://forums.linuxmint.com/viewtopic.php?f=42&t=270442 Mint 19 and Samba File Sharing Changes]
+*[https://forums.linuxmint.com/viewtopic.php?t=272334 [SOLVED]Mint 19 Network SAMBA shares not shownin File Manager]
-* [https://forums.linuxmint.com/viewtopic.php?f=42&t=88146&start=0 HowTo: Samba Browsing Problems Checklist]
+*[https://forums.linuxmint.com/viewtopic.php?f=42&t=270442 Mint 19 and Samba File Sharing Changes]
-* [https://forums.linuxmint.com/viewtopic.php?f=42&t=192794?f=42&t=192794 Resetting Mint's Default umask to 002]
+*[https://forums.linuxmint.com/viewtopic.php?f=42&t=88146&start=0 HowTo: Samba Browsing Problems Checklist]
-= [https://forums.linuxmint.com/viewtopic.php?t=282973#p1561928 Unable to launch "cinnamon-session-cinnamon"] =
+==[https://forums.linuxmint.com/viewtopic.php?t=282973#p1561928 Unable to launch "cinnamon-session-cinnamon"]==
 <code>apt install mint-meta-cinnamon</code>
-= "You have ''X'' broken package on your system! =
+=="You have ''X'' broken package on your system!==
 I was updating, upgrading Thunderbird from the Update Manager. I got a message:
   "You have 1 broken package on your system!
@@ Line 19: / Line 23: @@
 What is that, how do I run it?
 * <code>sudo apt-get install -f</code>
-= I was removing unwanted software from my Linux Mint machine and went too far... =
+==I was removing unwanted software from my Linux Mint machine and went too far...==
 * <span style="color:#c0392b">'''Unable to launch "cinnamon-session-cinnamon" X session "cinnamon-session-cinnamon" not found; Falling back to default session'''</span>
-* aaarrrggg...
+*<span style="color:#c0392b">'''Unable to launch "cinnamon-session-cinnamon" X session "cinnamon-session-cinnamon" not found; Falling back to default session'''</span>
-* Open an SSH session to the machine
+*aaarrrggg...
-** <code>apt install mint-meta-cinnamon</code>
+*Open an SSH session to the machine
-* aaahhh...&nbsp;&nbsp; :)
+**<code>apt install mint-meta-cinnamon</code>
-= RDP =
+==RDP==
 In order to access a machine through RDP, the user MUST have a valid '''.xsession''' file.

← Older revision		Revision as of 04:20, 1 July 2020
Line 27:		Line 27:
	** <code>apt install mint-meta-cinnamon</code>		** <code>apt install mint-meta-cinnamon</code>
	* aaahhh...   :)		* aaahhh...   :)
		+
		+	= RDP =
		+
		+	In order to access a machine through RDP, the user MUST have a valid '''.xsession''' file.
		+
		+	----
		+
		+	[https://forums.linuxmint.com/viewtopic.php?t=231342#p1225436 Re: Linux Mint 18 Remote Desktop (No Security types supported)]
		+	<div class="postbody"><div id="post_content1225436"><div class="content" style="margin-left: 40px">It wouldn't matter if the box you're coming from is Windows 7/8/10, MacOS, or Linux, or if you're running RealVNC, tightVNC, or Remmina--you'll have the same problem. The encryption used by Vino-server on Ubuntu/LM seems to be incompatible with that used by anything else and the result is no security type (0) instead of off/none (1) or normal (2). The only way to make it work is to diable its incompatible encyrption. One way is:<br /> <br /> '''gsettings set org.gnome.Vino require-encryption false'''<br /> <br /> Once you do that, you want to ensure VNC/5900+ is not open in your firewall (gufw). You can then tunnel VNC through ssh ([[Software - SSH\|install OpenSSH Server]]) or use RDP (install xrdp) for security. However, if you do the latter, you'll find Vino also doesn't spawn on port 5910+ as xrdp expects. So you'll have to edit the xrdp config file and replace port=-1 with port=5900 to get it to work. You'll also have to have a logged in session running on the server for this VNC to work.<br /> <br /> Install xrdp on a Raspberry Pi and it just works.I have several running headless for various functions. sessman runs on 3350 and xrdp on 3389. Upon connection, Xvnc wakes up on 5910 for xrdp to link to.</div> <div class="signature" id="sig1225436" style="margin-left: 40px">Desktop: HP Z240 Quad-Core Xeon, 32GB RAM, 500GB SSD, Nvidia graphics, 27" monitor<br /> Laptop:::: HP Zbook Quad-Core i7,,,,, 32GB RAM, 500GB SSD, Nvidia graphics, 15" display<br /> OS Both: Linux Mint 18 Sarah Cinnamon, kernel 4.4.0-45.66</div> </div> </div>