nextcloud / nextcloud/talk-desktop
Desktop App does not shutdown on Fedora 41/42
Nobody has claimed this yet.
- 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
- Download and install the flatpak from this repo
- Connect for the first time to your Nextcloud backend
- Use that client
- Click on the close button in the upper right corner
- Try to restart the Talk app
Expected behaviour
After closing the Talk app, I'm expecting that the app starts again
(By the way: I came across this behaviour, because I haven't found a possibility to minimize the Talk window.)
Actual behaviour
It doesn't start again!
Diagnosis and logs
Diagnosis report
After closing the Talk app, I've opend a terminal window and run the following command:
ps -Af | grep nextcloud
I got the following output:
sebasti+ 6403 6402 0 14:26 ? 00:00:01 /app/lib/com.nextcloud.talk/Nextcloud Talk
sebasti+ 6410 6403 0 14:26 ? 00:00:00 /app/lib/com.nextcloud.talk/Nextcloud Talk --type=zygote --no-zygote-sandbox
sebasti+ 6417 4165 0 14:26 ? 00:00:00 /usr/bin/bwrap --args 42 -- /app/bin/zypak-helper child - /app/lib/com.nextcloud.talk/Nextcloud Talk --type=zygote
sebasti+ 6429 6401 0 14:26 ? 00:00:00 /usr/bin/bwrap --args 42 -- /app/bin/zypak-helper child - /app/lib/com.nextcloud.talk/Nextcloud Talk --type=zygote
sebasti+ 6430 6429 0 14:26 ? 00:00:00 /app/lib/com.nextcloud.talk/Nextcloud Talk --type=zygote
sebasti+ 6459 6410 0 14:26 ? 00:00:00 /app/lib/com.nextcloud.talk/Nextcloud Talk --type=gpu-process --enable-crash-reporter=e63da94f-83e0-4fb6-968c-f5a3c9edcd6e,no_channel --user-data-dir=/home/sebastian/.var/app/com.nextcloud.talk/config/Nextcloud Talk --gpu-preferences=UAAAAAAAAAAgAAAEAAAAAAAAAAAAAAAAAABgAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAQAAABAAAAAAAAAAEAAAAAAAAAAIAAAAAAAAAAgAAAAAAAAA --shared-files --field-trial-handle=3,i,14657440142378056940,6583332761794992626,262144 --disable-features=SpareRendererForSitePerProcess --variations-seed-version
sebasti+ 6466 6403 0 14:26 ? 00:00:00 /app/lib/com.nextcloud.talk/Nextcloud Talk --type=utility --utility-sub-type=network.mojom.NetworkService --lang=de --service-sandbox-type=none --enable-crash-reporter=e63da94f-83e0-4fb6-968c-f5a3c9edcd6e,no_channel --user-data-dir=/home/sebastian/.var/app/com.nextcloud.talk/config/Nextcloud Talk --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,14657440142378056940,6583332761794992626,262144 --disable-features=SpareRendererForSitePerProcess --variations-seed-version
sebasti+ 6539 6430 0 14:26 ? 00:00:03 /app/lib/com.nextcloud.talk/Nextcloud Talk --type=renderer --enable-crash-reporter=e63da94f-83e0-4fb6-968c-f5a3c9edcd6e,no_channel --user-data-dir=/home/sebastian/.var/app/com.nextcloud.talk/config/Nextcloud Talk --app-path=/app/lib/com.nextcloud.talk/resources/app.asar --enable-sandbox --lang=de --num-raster-threads=4 --enable-main-frame-before-activation --renderer-client-id=5 --time-ticks-at-unix-epoch=-1744287256857647 --launch-time-ticks=717279243 --shared-files=v8_context_snapshot_data:100 --field-trial-handle=3,i,14657440142378056940,6583332761794992626,262144 --disable-features=SpareRendererForSitePerProcess --variations-seed-version
sebasti+ 10116 2292 0 14:45 ? 00:00:00 /usr/bin/nextcloud --background
sebasti+ 12419 4560 0 14:55 pts/0 00:00:00 grep --color=auto nextcloud
It seems that there are a couple of related processes still running.
Then I send a kill to the first process:
kill 6403
The process 6403 and the subsequent proccesses has gone.
After that I can start again the application without problems so far.
Diagnosis report
OS Fedora FC 41, updated this morning
| Nextcloud Talk Desktop | |
|---|---|
| Version | v1.1.5 |
| Built-in Talk version | v21.0.0 |
| Release channel | stable |
| Operating system | Linux 6.13.9-200.fc41.x86_64 (#1 SMP PREEMPT_DYNAMIC Sat Mar 29 01:29:31 UTC 2025) |
| Executable Path | /app/lib/com.nextcloud.talk/Nextcloud Talk |
| Using Wayland | ✅ yes |
| Connected to | - |
| Nextcloud server version | 31.0.2 |
| Nextcloud Talk version | 21.0.1 |
notifications app enabled |
✅ yes |
notify_push app enabled |
✅ yes |
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
}
It can be found in the About window (open from the menu or via F1 and click on "Copy report" button).
Client logs
Press Ctrl+Shift+I (Cmd+Option+C on macOS) or use the context menu to open the developer tools, then go to the Console tab.
Which error logs?
Can I find error logs somewhere else?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the shutdown and restart failure using the Flatpak on Fedora 41 or 42, then inspect the remaining Nextcloud Talk and Electron processes shown by ps -Af | grep nextcloud. Use the provided diagnosis and client-log sections to investigate the close behavior. Done means closing the app terminates its related processes and allows it to start again normally.
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