Starts momentarily then closes #160
Comments
|
Looks like a D-Bus problem. There's a panic happening when Gtk4 tries to initialize the application. It connects to the Flatpak D-Bus proxy, but then suddenly its connection gets closed and that causes a panic. I'm about 99% sure this is not a bug in Trayscale. It might be a bug in the Flatpak package, but it seems more likely that there's something weird going on with D-Bus on your system. |
|
I am seeing the same issue, Fedora 40, Trayscale 0.13.4. I noticed this error some time after testing Wayland, but I am unable to confirm if this is caused by this. I have tested many changes with Flatseal around permissions, but I did not succeed. When running with flatpak run dev.deedles.Trayscale, I can see the following error after a while (Trayscale closes at 18:15:55, about 5 minutes after starting): |
|
In my specific issue, it seems it is now working by enabling 'D-Bus session bus' in Flatseal, which I did not try before. It seems I no longer get the first 'systray error' that I was originally getting: (followed by a crash) With session-bus: So with this configuration change, it seem it is resolved for me for now. As the same error appears in the original report from @MudDev, it could be worth checking if this helps. Should this be enabled in the flatpak by default? |
|
That systray error is caused by that, but that's not a fatal error. I get that on my machine, too, but without a crash. In fact, the code that produces that error in the if err != nil {
log.Printf("systray error: failed to request name: %s\n", err)
// it's not critical error: continue
}I don't think the problem is systray-related. It seems more likely that it's related to Gtk4's application system which registers with D-Bus when it starts. That not working would definitely cause it to fail to start, whereas if the systray icon didn't work it should just not have a systray icon.
No, probably not. I had permissions like that originally and the Flathub people requested that they be reduced before they allowed it to be published on there. |
|
I didn't make any changes, but it just started working today. Maybe it just needed a long weekend 😄 Nice find @bkazoo and thanks for sharing your solution, I hope this helps other people that are running into this issue. |
|
+1 i also have this error. it happens after a few minutes. i also use ubuntu 24.04 with the flatpak version |
|
When i do and it seems to not crash anymore |
|
Exactly the same issue running on, Ubuntu 24.04.1 LTS x86_64 |
|
@issinoho, you should also be able to override the permissions for the flatpak. I recommend Flatseal for dealing with that kind of thing. I'd really like to figure out what exactly is failing here rather than having to open it up to full session bus access. Could you try running it without |
|
Ok, here we go... Then lots of repeating information, and finally the exit. |
|
Can you try running the following and letting me know if it works, please? Make sure that if you've made any changes with Flatseal that you undo them before you run it. |
|
Crashed very quickly... |
This worked for me, using FlatSeal to give it 'socket=session-bus' makes the crashing stop for now. |
|
Just to add another data point: |
|
That's a weird one. If enabling that lets it do something that then persists through uninstallations, that could certainly explain why I've had so much trouble reproducing this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
After upgrading my ubuntu from 22 to 24, I am getting this error with trayscale, it was working great before, and now it's broken.
I tried to uninstall and install the flatpack again but not joy.
Here is the error when I try to launch it:
The text was updated successfully, but these errors were encountered: