Failed to start Portal service #107
Comments
|
if you run /usr/libexec/xdg-desktop-portal on the commandline, does it start normally ? |
|
Sorry for not getting back to you earlier. I lost the means to reproduce this for a while. Here is the stack trace: and when I run To reproduce this, you can install this app: https://flathub.org/apps/details/org.gahshomar.Gahshomar Please let me know if you want more information. |
|
Could you please reopen this issue? |
|
Gentle reminder @matthiasclasen once an issue is closed, only the maintainers can re-open it. |
|
Sorry about that. It seems to work. |
|
@183amir can you please follow the instructions at https://wiki.gnome.org/Community/GettingInTouch/Bugzilla/GettingTraces to install debuginfo, so we can get a useful backtrace for the crash? The trace you posted is not useful because it does not contain debuginfo for any of the libraries in the crash. We probably only need one thread for this, but it should be a full trace showing member variables, so please take the trace using |
|
To get the debug info in archlinux, I have to rebuild the package but I am facing an error in compiling the package: Do you have any idea what could be the problem? |
|
I just fixed this problem (invalid xml) here: flatpak/flatpak@f28e8af |
|
Here is the stacktrace with xdg-desktop-portal symbols: |
|
Installing flatpak from this commit flatpak/flatpak@f28e8af and installing xdg-desktop-portal 1.1.1 does not result in any segmentation faults anymore. However running Gahshomar for the first time after login does hang the desktop until the desktop portal service is activated. From my experience nothing changed, the desktop still hangs for 15 seconds or so when I run the app. Now it happens the first time only. |
|
It takes around 25 seconds to activate and it hangs the desktop in that time. |
|
Is there any way that I can avoid activating xdg-desktop-portal when running Gahshomar? Here is the flatpak builder definition of Gahshomar: https://github.com/flathub/org.gahshomar.Gahshomar/blob/master/org.gahshomar.Gahshomar.json Gahshomar is a very simple app. It does not need any permission to run except for dconf to save its settings. It doesn't need internet access neither. |
|
Hello, Is there any news on this? I am still facing this issue in archlinux. |
|
Running Is there any way that I can avoid activating xdg-desktop-portal when running Gahshomar? |
|
The portal is expected to be running. Its an issue with the session setup that needs to be fixed, not worked around by avoiding the portal. |
|
Who is supposed to activate this service? I tried enabling it with systemd and I got this: which makes sense since it's a dbus service. |
|
I noticed that this happens only in my app (Gahshomar) and not using other flatpak apps (e.g. Fondo). If I kill |
|
Duplicate of # |
|
@HambaliArab duplicate of what? |
|
I am still having this issue by the way. I would really appreciate any help and feedback. |
|
@183amir I don't know if you're still having the issue but I have some information and hopefully a solution, as I experienced the same issue on Arch. After reviewing the logs and debug output for xdg-desktop-portal, I found that it was throwing an error about not being able to connect to pipewire which xdg-desktop-portal uses for some multimedia functions. I installed the version of pipewire from the git repo (pipewire-git in the AUR) and the error went away and my programs now launch without the delay. So, I don't think this is a flatpak/xdg-desktop-portal issue, I think it's a problem with pipewire that has apparently been fixed. Not a developer, but I hope this helps. |
|
Thank you for your comment. I tried it and I still get: and the desktop hangs. Now it hangs even when portal is already running. |
|
Running: |
|
I stumbled over this report, while searching for a solution to broken screen sharing on my Arch Linux machine. @horatiog your comment was the key to fixing this issue for me. I noticed, that there was a I hope this is useful for other Arch Linux user coming across this issue. |
|
I have tested this on Fedora and everything works there. On ArchLinux, please refer to #107 (comment) |
|
@harmathy I love you! the new pipewire configuration has solved 2 very annoying Issues for me:
Notes: There is no need to add I have been actively searching for a solution for more than a week thank you so much @harmathy !!! |
You're welcome 😄 |
Wow, I was searching and debugging for hours and this solved all the issues. |
Relevant for Arch: this did not work for me because the .pacnew file was using a format which isn't compatible with the current version. See flatpak/xdg-desktop-portal#570 (comment) for context. |
|
In my case, on a Debian Sid box, the |
|
@ivilata Simple, it worked for me too, thank you! |
As it currently stands, the arch wiki page on xinit asserts that you should be running all of the scripts in So you might consider adding the terminal if block from the template xinitrc into yours: |
Similar to #72 when I run a dbus-activated app (installed using flatpak) it takes forever to start. Looking at the logs I see that the portal fails to load:
the workaround mentioned in #72 solves the slownees issue too. This issue happens in a Gnome environment in both Arch Linux and a fresh install of Ubuntu 17.10.
The question is why my session is not setting this environment up for me? I am not using i3wm or anything. I am using vanilla Gnome 3.
Also, why does this happen only with portal? Any other non-flatpak that I launch using dbus starts instantly.
The text was updated successfully, but these errors were encountered: