Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

tray icon is missing on linux (flatpak) #1018

Open
Fuseteam opened this issue Jan 8, 2025 · 9 comments
Open

tray icon is missing on linux (flatpak) #1018

Fuseteam opened this issue Jan 8, 2025 · 9 comments
Labels

Comments

@Fuseteam
Copy link

Fuseteam commented Jan 8, 2025

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. install talk-desktop as a flatpak
  2. launch talk-desktop

Expected behaviour

There should be a tray icon in the notification area (forgot the name of the region they appear in)

Actual behaviour

no tray icon is seen

Diagnosis and logs

Diagnosis report

Diagnosis report

Nextcloud Talk Desktop
Version v1.0.1
Built-in Talk version v20.1.1
Operating system Linux 6.8.0-51-generic (#52-Ubuntu SMP PREEMPT_DYNAMIC Thu Dec 5 13:09:44 UTC 2024)
Executable Path /app/lib/com.nextcloud.talk/Nextcloud Talk
Using Wayland ✅ yes
Connected to -
Nextcloud server version 30.0.4
Nextcloud Talk version 20.1.1
notifications app enabled ✅ yes
notify_push app enabled ✅ yes

Application config

{
  "theme": "dark",
  "systemTitleBar": true,
  "monochromeTrayIcon": false,
  "zoomFactor": 1,
  "playSoundChat": "respect-dnd",
  "playSoundCall": "respect-dnd",
  "enableCallbox": "respect-dnd"
}
Client logs

no errors

@Fuseteam Fuseteam added 0. Needs triage bug Something isn't working labels Jan 8, 2025
@nickvergessen
Copy link
Member

Works fine here on Ubuntu 24.10, what are you using?

@Fuseteam
Copy link
Author

Fuseteam commented Jan 9, 2025

i'm ubuntu sway 24.04 while a colleague with the same issue is on bazzite (fedora silverblue) with the tray icons reloaded extension

@ShGKme
Copy link
Contributor

ShGKme commented Jan 9, 2025

@Fuseteam Do you also use tray-icons-reloaded?

Could you run Talk Desktop from terminal and check for any errors in the log?

@Fuseteam
Copy link
Author

@ShGKme i use sway, it seemed to work fine when i was using the preview via the zip package

when i run it from the terminal i get this:

[3:0110/103656.599773:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0110/103656.765036:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[3:0110/103656.765077:ERROR:bus.cc(407)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Vue Devtools extension is installed

@ShGKme
Copy link
Contributor

ShGKme commented Feb 4, 2025

@Fuseteam I'm not really familiar with Sway, but having many reports about problems with the tray icon in the sway repo, I'm not sure the problem is on our (or maybe flatpak) side...

But just in case, could you try to run:

flatpak override --talk-name=org.kde.StatusNotifierItem com.nextcloud.talk

If I'm not mistaking...

@github-project-automation github-project-automation bot moved this to 🧭 Planning evaluation (don't pick) in 💬 Talk team Feb 4, 2025
@ShGKme ShGKme added this to the 🪴 Next Release milestone Feb 4, 2025
@Fuseteam
Copy link
Author

Fuseteam commented Feb 4, 2025

that unfortunately does not seem to solve it.

I have now double checked and the latest zip version does have a tray icon, it appears to be specific to the flatpak

the difference in logs seems to indicate to me that some dbus connection is failing perhaps?

Image

@ShGKme
Copy link
Contributor

ShGKme commented Feb 4, 2025

@Fuseteam Thanks! One last thing, could you try this:

flatpak override --talk-name=org.freedesktop.StatusNotifier.Watcher com.nextcloud.talk

You can then reset everything by

flatpak override --reset com.nextcloud.talk

the difference in logs seems to indicate to me that some dbus connection is failing perhaps?

override --talk-name actually changes the Session Bus Policy for connection.

@Fuseteam
Copy link
Author

Fuseteam commented Feb 4, 2025

unfortunately no luck

@ShGKme
Copy link
Contributor

ShGKme commented Feb 4, 2025

Eh, thanks for the testing.

Then I'm out of ideas. Will try to install and test sway on my machine

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: 🧭 Planning evaluation (don't pick)
Development

No branches or pull requests

3 participants