nextcloud / nextcloud/talk-desktop

Compose and Mod3 keys do not work

Open
#1,404 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug needs triage
Dominant language
JavaScript
Stars
525
Forks
85
Avg merge
8h 5m
Merged PRs (30d)
35

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are affected by the same issue.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Steps to reproduce

  1. Type a message, attempting to use the Compose key.
  2. Again, this time using Mod3 (usually AltGr).
Expected behaviour

I should be able to type accented characters etc. using these methods.

Actual behaviour

I can't type accented characters using these methods. There's nothing to show!

Diagnosis and logs

Diagnosis report ### Diagnosis report
Nextcloud Talk Desktop
Version v1.2.5
Built-in Talk version v21.1.2
Release channel stable
Operating system Linux 6.14.0-24-generic (#24~24.04.3-Ubuntu SMP PREEMPT_DYNAMIC Mon Jul 7 16:39:17 UTC 2)
Executable Path /app/lib/com.nextcloud.talk/Nextcloud Talk
Using Wayland ❌ no
Connected to -
Nextcloud version 31.0.7
Nextcloud Talk version 21.1.2
notifications app enabled ✅ yes
notify_push app enabled ❌ no
Application config
{
  "launchAtStartup": false,
  "theme": "default",
  "systemTitleBar": true,
  "monochromeTrayIcon": false,
  "zoomFactor": 1,
  "playSoundChat": "respect-dnd",
  "playSoundCall": "respect-dnd",
  "enableCallbox": "respect-dnd",
  "secondarySpeaker": false,
  "secondarySpeakerDevice": null,
  "trustedFingerprints": []
}
Client logs

Press:

  • 🪟 Windows: Ctrl+Shift+I
  • 🍎 macOS: Cmd+Option+C
  • 🐧Linux: Ctrl+Shift+I

Or use the context menu to open the developer tools, then go to the Console tab.

Insert error logs here.

I have no problem using Compose and AltGr in the web version of Talk.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the Compose and Mod3/AltGr behavior in the Linux desktop client and compare it with Talk in the web version. Review the client logs and the desktop input-handling entry points to determine where these key events are lost. Done means accented characters can be entered through both methods without breaking other keyboard input.

Written by the indexing model from the issue text.

Assessment

Tech stack
electron, javascript
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.