On this page
When sound goes to the wrong place or a key types an unexpected symbol, the hardware may be working correctly. Ubuntu may have selected a different device or layout.
Change one control, test it, and keep the change only when the evidence improves.
Choose where sound comes out
Open Settings → Sound. Under output, select the device you want to hear: built-in speakers, headphones, a monitor, or a Bluetooth headset.
The device list reflects connected and recognized hardware. A monitor can appear as an audio output even when you expected laptop speakers.
Use the test control when available, or play familiar audio at a low volume. Confirm both the selected output and its volume.
If there is no sound:
- Check mute and volume.
- Confirm the correct output device.
- Check a physical headphone connection or monitor volume.
- Try another known-working audio source.
Do not raise every volume to maximum as the first test.
Choose the microphone input
Under input, select the intended microphone. Speak normally and watch the input-level meter.
A moving meter shows that Ubuntu receives some signal. It does not prove every application has microphone permission or selected the same source.
For a headset, output and input can appear as separate choices. Verify both.
Why the typed symbol can differ from the key
What you may see: pressing the key printed with @ produces another symbol, or punctuation appears in unexpected places.
Why this happens: a keyboard layout maps physical key positions to characters. Two English layouts, such as US and UK, can assign punctuation differently.
What to do next: open the keyboard or region/language settings and inspect Input Sources. Select the layout that matches the physical keyboard and language you intend to type.
Use the layout preview when offered. Test letters, numbers, @, quotes, slash, backslash, and other symbols you use often.
Work with more than one input source
People who type in several languages can add multiple input sources. Ubuntu shows the active source in the top bar when more than one is configured.
The documented default shortcut Super + Space switches to the next input source. Shortcuts can be customized, so inspect Keyboard settings if yours differs.
If unexpected characters begin after an accidental shortcut, check which input source is active before changing system files.
Adjust mouse behavior
In Mouse & Touchpad, pointer speed changes how far the pointer moves for the same physical motion. Test a small adjustment by selecting a few normal targets.
Primary-button choice supports left- or right-handed use. Changing it swaps which physical button performs the main selection, so record the previous setting before testing.
Some controls appear only when matching hardware is connected.
Adjust touchpad behavior
Available options can include:
- Pointer speed.
- Tap to Click.
- Natural Scrolling.
- Two-finger scrolling or edge scrolling.
- Disabling the touchpad while typing.
Natural Scrolling changes the direction the page moves relative to your fingers. Neither direction is universally correct. Choose the one that makes your movement predictable.
If tap-to-click changes unexpectedly, remember that the physical click may still work. Use it to return to Settings.
Keyboard and pointer accessibility
Accessibility settings can provide sticky keys, slow keys, bounce keys, an on-screen keyboard, pointer assistance, and other controls.
These are functional tools, not emergency-only settings. Test them when they match a real need, and keep a way to reverse the change if the input behavior surprises you.
Common mistakes
Changing the language when only the layout is wrong. Inspect Input Sources first.
Testing sound through the wrong application output. Confirm both the system device and any per-application selection.
Assuming Bluetooth audio is connected because it is paired. Paired and actively connected are different states.
Changing several pointer options together. Restore them, then adjust speed, scrolling, and tap behavior separately.
Thinking password typing failed because no characters appear. Terminal administrator prompts intentionally hide typed passwords; Path 1 explains this special case. Ordinary text fields should show their documented feedback.
Practice
Knowledge check
Diagnose the wrong keyboard character.
Every time a learner presses the printed @ key, a quote appears. What should they inspect
first, and which symbols would you ask them to test after the change?
What to learn next
Continue to Connect Ubuntu to Wi-Fi and Bluetooth to manage network and paired-device state without jumping to advanced driver commands.