nextcloud
Desktop App does not shutdown on Fedora 41/42
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?
4. Click on the close button in the upper right corner
This isn't supposed to quit the app but minimize it to the system tray
I know there are some desktop environments that don't have the tray. Is it a case for you?
- Ref: https://github.com/nextcloud/talk-desktop/issues/983
(By the way: I came across this behaviour, because I haven't found a possibility to minimize the Talk window.)
Could you clarify what you mean?
It doesn't start again!
Known issue, was broken again somehow, but I forgot to create an issue for it...
Hi @ShGKme ,
thank you very much for your immediate reply. 👍👍👍 I really appriciate that. __ Well, in Gome 47 there is a tray. Especially I'm using the Dash to Panle addon. Please have a look:
But after clicking that 'close'-button Talk disappears from the desktop.
And I've seen the same behaviour when deactivating the Dash to Panel addon.
That might be related to Gnome itself.
I've seen some screenshots from the new Dash to Panel addon for Gome 48. For me it seems that there are some notification icons. Fedora 42 with Gnome 48 is scheduled for April, 22nd. Let's see. I will come back.
Next. In my opinion the 'close-button' is foremost a close button. From an average users perspective I wouldn't care about it, when Talk restarts properly. So I was looking for some kind of minimizing an application. If it works your way properly, there is no problem.
I'm going to wait for FC42/Gnome 48 and an updated version of Nextcloud Talk. Version 1.1.6 this morning does not do the trick. I will check it and come back.
BR SMF
Same thing occur in my installation of Fedora 41, i have to kill Talk via ps -aux | grep nextcloud
And then i can kill the process to startup the application again, also same issue occur with the latest version of Talk.
Hi @ShGKme,
last week I've done a fresh installation of Fedora 42 after removing the partition containing Fedora 41. And since then I've done the first updates to Fedora 42.
I've updated my Nextcloud backend to 31.0.4.
This morning I've uninstalled Nextcloud Talk Desktop and then installed Nextcloud 1.17 using the flatpak file from this repository.
Unfortunately the issue remains.
BR SMF
Diagnosis report
### Diagnosis report
| **Nextcloud Talk Desktop** | |
| ------------------------------: | ---------------------------------------------------------------------------------- |
| **Version** | v1.1.7 |
| **Built-in Talk version** | v21.0.3 |
| **Release channel** | stable |
| **Operating system** | Linux 6.14.2-300.fc42.x86_64 (#1 SMP PREEMPT_DYNAMIC Thu Apr 10 21:50:55 UTC 2025) |
| **Executable Path** | /app/lib/com.nextcloud.talk/Nextcloud Talk |
| **Using Wayland** | ✅ yes |
| ****Connected to**** | - |
| **Nextcloud server version** | 31.0.4 |
| **Nextcloud Talk version** | 21.0.3 |
| **`notifications` app enabled** | ✅ yes |
| **`notify_push` app enabled** | ✅ yes |
#### Application config
```json
{
"launchAtStartup": false,
"theme": "default",
"systemTitleBar": true,
"monochromeTrayIcon": false,
"zoomFactor": 1,
"playSoundChat": "respect-dnd",
"playSoundCall": "respect-dnd",
"enableCallbox": "respect-dnd",
"secondarySpeaker": false,
"secondarySpeakerDevice": null,
"trustedFingerprints": []
}
It was expected, if it doesn't work on 41 it should not likely working on 42. I'm still on 41 and will be there until i know that 42 is 100% stable before i upgrade (not in nextclouds case) as this is something they need to take a look at.
Like i said before the processes are not being killed and that's the problem, the only way to go around it is to find the pids for the process and manually kill them one by one.
Hi @ShGKme ,
I've been tweaking my Gnome Desktop a little bit.
After installing an addon called "Tray Icons: Reloaded" I got an app icon indicator in the Dash-To-Panel tray:
When left-clicking on that icon, the Talk-app shows up immediately. And after right-clicking on that icon I got a context menu with an Open- and a Quit- entry.
Unfortunately, the context menu appears somewhere in the middle of my screen.
Don't know if this is a Gnome problem.
BR
SMF
Hi @ShGKme,
I've updated this morning to Talk Desktop 1.1.8, after deinstalling Talk 1.1.7, updating the whole system and rebooting.
In my opinion it's partially solved.
After clicking the x-button the application minimizes and ps -Af | grep talk shows Talk still running.
Clicking on the app icon (red rectangle) I got this error report on the right side.
Clicking on the tray icon (green rectangle) the application shows up on the screen again. As far as I've tested with no problems.
Clicking right on the tray icon, the context menu still shows up somewhere in the middle of the screen.
BR SMF
There is no information in their release about a fix for Fedora, so we'll just have to wait a bit longer.
@mf-in-mun This problem wasn't supposed to be solved in v1.1.8. The issue isn't marked as closed, nor linked to the release.
We know about this problem with some Linux distributions and will fix it soon, before the next major Talk release.