Troubleshooting issues - Revision history

BTackt: this page is still terrible

2026-03-20T18:14:27Z

this page is still terrible

BTackt: Undo revision 3436 by BTackt

2025-05-22T22:12:16Z

Undo revision 3436 by BTackt

← Older revision		Revision as of 22:12, 22 May 2025
Line 18:		Line 18:
	=== Plover does not recognize my USB keyboard or steno machine ===		=== Plover does not recognize my USB keyboard or steno machine ===

	{{Info\|Initially, Plover is set up to use your computer keyboard as a steno machine. If you have a steno machine, you’ll need to configure Plover to look for your machine. See the [[~~Supported Hardware~~\|Supported Hardware page]] for configuration instructions specific to your machine.}}		{{Info\|text=Initially, Plover is set up to use your computer keyboard as a steno machine. If you have a steno machine, you’ll need to configure Plover to look for your machine. See the [[Supported_Hardware \|Supported Hardware page]] for configuration instructions specific to your machine.}}
	If you know your machine has been configured correctly, and Plover doesn’t recognize your keyboard or steno machine:		If you know your machine has been configured correctly, and Plover doesn’t recognize your keyboard or steno machine:

Line 25:		Line 25:
	#* If it states the machine is disconnected, press the Reconnect button (this is to the right of “connected” or “disconnected” message).		#* If it states the machine is disconnected, press the Reconnect button (this is to the right of “connected” or “disconnected” message).
	# If Plover still doesn’t recognize your machine, try closing and relaunching Plover.<span id="strokes-no-longer-appear-when-using-keyboard"></span>		# If Plover still doesn’t recognize your machine, try closing and relaunching Plover.<span id="strokes-no-longer-appear-when-using-keyboard"></span>

	=== Strokes no longer appear when using keyboard ===		=== Strokes no longer appear when using keyboard ===

BTackt: /* Plover does not recognize my USB keyboard or steno machine */

2025-05-22T22:09:01Z

Plover does not recognize my USB keyboard or steno machine

← Older revision		Revision as of 22:09, 22 May 2025
Line 18:		Line 18:
	=== Plover does not recognize my USB keyboard or steno machine ===		=== Plover does not recognize my USB keyboard or steno machine ===

	{{Info\|~~text=~~Initially, Plover is set up to use your computer keyboard as a steno machine. If you have a steno machine, you’ll need to configure Plover to look for your machine. See the [[~~Supported_Hardware~~ \|Supported Hardware page]] for configuration instructions specific to your machine.}}		{{Info\|Initially, Plover is set up to use your computer keyboard as a steno machine. If you have a steno machine, you’ll need to configure Plover to look for your machine. See the [[Supported Hardware\|Supported Hardware page]] for configuration instructions specific to your machine.}}
	If you know your machine has been configured correctly, and Plover doesn’t recognize your keyboard or steno machine:		If you know your machine has been configured correctly, and Plover doesn’t recognize your keyboard or steno machine:

Line 25:		Line 25:
	#* If it states the machine is disconnected, press the Reconnect button (this is to the right of “connected” or “disconnected” message).		#* If it states the machine is disconnected, press the Reconnect button (this is to the right of “connected” or “disconnected” message).
	# If Plover still doesn’t recognize your machine, try closing and relaunching Plover.<span id="strokes-no-longer-appear-when-using-keyboard"></span>		# If Plover still doesn’t recognize your machine, try closing and relaunching Plover.<span id="strokes-no-longer-appear-when-using-keyboard"></span>

	=== Strokes no longer appear when using keyboard ===		=== Strokes no longer appear when using keyboard ===

Aerick: Aerick moved page Troubleshooting Issues to Troubleshooting issues: Sentence case

2024-08-17T03:50:36Z

Aerick moved page Troubleshooting Issues to Troubleshooting issues: Sentence case

← Older revision		Revision as of 03:50, 17 August 2024
(No difference)

Aerick: /* Linux */

2024-06-26T21:57:20Z

Linux

← Older revision		Revision as of 21:57, 26 June 2024
Line 115:		Line 115:
	macOS has a feature where holding down a key brings up an accent menu. This can sometimes drop keys when typing quickly, such as <code>TO/FPLT</code> producing <code>t.</code> instead of <code>to.</code> To disable this, follow the instructions in this article: [https://www.tekrevue.com/tip/how-to-disable-the-character-accent-menu-in-os-x-mountain-lion/ “How to Disable the Character Accent Menu in OS X Mountain Lion”].<span id="linux"></span>		macOS has a feature where holding down a key brings up an accent menu. This can sometimes drop keys when typing quickly, such as <code>TO/FPLT</code> producing <code>t.</code> instead of <code>to.</code> To disable this, follow the instructions in this article: [https://www.tekrevue.com/tip/how-to-disable-the-character-accent-menu-in-os-x-mountain-lion/ “How to Disable the Character Accent Menu in OS X Mountain Lion”].<span id="linux"></span>
	== Linux ==		== Linux ==

			=== Permission denied with Gemini PR or TX Bolt ===
			''See: [[Installation Guide#Allow Access to Serial Ports\|allow access to serial ports]].''

	=== Missing or jumbled output ===		=== Missing or jumbled output ===
	IBus does not handle the very fast simulated key presses of Plover. This can result in dropped or transposed letters (<code>HAT</code> becomes <code>AHT</code> or <code>AT</code>). The solution is to go open Plover's configuration dialog, navigate to the <code>Output</code> tab, and increase the <code>Key press delay</code>.		IBus does not handle the very fast simulated key presses of Plover. This can result in dropped or transposed letters (<code>HAT</code> becomes <code>AHT</code> or <code>AT</code>). The solution is to go open Plover's configuration dialog, navigate to the <code>Output</code> tab, and increase the <code>Key press delay</code>.

Aerick: /* add Xwayland error */

2024-06-26T01:34:52Z

add Xwayland error

← Older revision		Revision as of 01:34, 26 June 2024
Line 124:		Line 124:
	=== Delayed/slow output when using gnome-shell and the keyboard machine ===		=== Delayed/slow output when using gnome-shell and the keyboard machine ===
	It’s a gnome-shell [https://github.com/openstenoproject/plover/issues/1030 bug], unfortunately there’s no known workaround.		It’s a gnome-shell [https://github.com/openstenoproject/plover/issues/1030 bug], unfortunately there’s no known workaround.

			=== No authorization protocol error ===
			If the following error occurs while trying to run Plover, your system is using Xwayland. See the wiki page on [[Wayland#Plover on Xwayland\|Wayland]] for a fix.
			[[File:Xwayland error.png\|alt=Xwayland error that pops up when trying to run Plover\|center\|thumb\|This error occurs on some systems running Wayland.]]

	=== Plover not working on Wayland ===		=== Plover not working on Wayland ===
	Plover does not officially support Wayland. This is an issue with Wayland not having adequate tools to cover emulated keyboard input. However, there are a few workarounds that use other methods of keyboard emulation with varying degrees of success.		Plover does not officially support Wayland. See the wiki page on [[Wayland]] for workarounds and alternatives to Plover.

	~~The [https://github.com/LilleAila/plover-uinput plover-uinput] plugin should work across all Wayland setups (including GNOME and KDE plasma), but relies on iBus for unicode characters~~. See the ~~Wiki~~ page on ~~the~~ [[~~plover-uinput~~]] ~~plugin~~ for ~~more details~~.

Aerick: /* Plover not working on Wayland */

2024-06-23T23:08:04Z

Plover not working on Wayland

← Older revision		Revision as of 23:08, 23 June 2024
Line 128:		Line 128:
	Plover does not officially support Wayland. This is an issue with Wayland not having adequate tools to cover emulated keyboard input. However, there are a few workarounds that use other methods of keyboard emulation with varying degrees of success.		Plover does not officially support Wayland. This is an issue with Wayland not having adequate tools to cover emulated keyboard input. However, there are a few workarounds that use other methods of keyboard emulation with varying degrees of success.

	The [https://github.com/LilleAila/plover-uinput plover-uinput] plugin should work across all Wayland setups (including GNOME and KDE plasma), but relies on iBus for unicode characters. ~~Also see~~ [[~~Plugins#Manually Installing Plugins\|manually installing plugins~~]] for ~~help installing this plugin as this is not in the plugins manager~~.		The [https://github.com/LilleAila/plover-uinput plover-uinput] plugin should work across all Wayland setups (including GNOME and KDE plasma), but relies on iBus for unicode characters. See the Wiki page on the [[plover-uinput]] plugin for more details.

Aerick: /* No output despite keys showing up in the paper tape */

2024-06-23T19:52:54Z

No output despite keys showing up in the paper tape

← Older revision		Revision as of 19:52, 23 June 2024
Line 102:		Line 102:
	# Enable Plover's output.		# Enable Plover's output.
	# Open the paper tape and press some keys.		# Open the paper tape and press some keys.
	#* If nothing shows up, you will first need to ~~[[Supported Hardware#Setting Up a Hobbyist Machine With Plover\|~~set up your machine]].		#* If nothing shows up, you will first need to set up your machine.
	#* If you see letters showing in the paper tape, follow the rest of these instructions.		#* If you see letters showing in the paper tape, follow the rest of these instructions.
	# Open <code>System Settings > Privacy & Security > Accessibility</code>.		# Open <code>System Settings > Privacy & Security > Accessibility</code>.

Aerick: /* Plugins not showing in the plugins manager: fix link */

2024-06-23T17:15:00Z

Plugins not showing in the plugins manager: fix link

← Older revision		Revision as of 17:15, 23 June 2024
Line 44:		Line 44:
	===Plugins not showing in the plugins manager===		===Plugins not showing in the plugins manager===

	Installing plugins that aren't in the plugins manager is a greater security risk, and is therefore not recommended. If you still want to proceed with this, follow the instructions for [[Plugins#Manually ~~installing plugins~~\|manually Installing Plugins]].		Installing plugins that aren't in the plugins manager is a greater security risk, and is therefore not recommended. If you still want to proceed with this, follow the instructions for [[Plugins#Manually Installing Plugins\|manually Installing Plugins]].

	== Dictionary issues ==		== Dictionary issues ==

Aerick: /* Plover not working on Wayland */

2024-06-16T01:08:52Z

Plover not working on Wayland

← Older revision		Revision as of 01:08, 16 June 2024
Line 126:		Line 126:

	=== Plover not working on Wayland ===		=== Plover not working on Wayland ===
	This is an issue with Wayland not having adequate tools to cover emulated keyboard input. However, there are a few workarounds that use other methods of keyboard emulation with varying degrees of success.		Plover does not officially support Wayland. This is an issue with Wayland not having adequate tools to cover emulated keyboard input. However, there are a few workarounds that use other methods of keyboard emulation with varying degrees of success.

	The [https://github.com/LilleAila/plover-uinput plover-uinput] plugin should work across all Wayland setups (including GNOME and KDE plasma), but relies on iBus for unicode characters. Also see [[Plugins#Manually Installing Plugins\|manually installing plugins]] for help installing this plugin as this is not in the plugins manager.		The [https://github.com/LilleAila/plover-uinput plover-uinput] plugin should work across all Wayland setups (including GNOME and KDE plasma), but relies on iBus for unicode characters. Also see [[Plugins#Manually Installing Plugins\|manually installing plugins]] for help installing this plugin as this is not in the plugins manager.