Failing to start xdg-desktop-portal-gnome after logging on Gnome #206630
Labels
0.kind: bug
Something is broken
Comments
|
This issue has been mentioned on NixOS Discourse. There might be relevant details there: |
|
Could you try looking at systemd journal before the “Starting Portal service (GNOME implementation)...” line? Hopefully, there will be some hint about what is starting it. In my case |
|
Here the output of |
|
Looks like nextcloud-client is starting it: Perhaps this is too soon: |
|
This issue has been mentioned on NixOS Discourse. There might be relevant details there: |
|
I think you are correct, @jtojnar. Disabling Nextcloud xdg-desktop-portal-gnome starts correctly. |
|
This issue has been mentioned on NixOS Discourse. There might be relevant details there: |
|
Exactly the same thing happens on my system, but the offending service in my case was opensnitch-ui, which also starts too early and causes xdg-desktop-portal to fail. |
|
I filed a bug report over at home-manager, but it seems it's not that the services are starting early, but the graphical session is started even before starting the DE. nix-community/home-manager#3628 (comment)
|
|
For anyone looking for a workaround for fixing {
services.nextcloud-client.enable = true;
systemd.user.services.nextcloud-client = {
Unit = {
After = pkgs.lib.mkForce "graphical-session.target";
};
};
} |
|
I was having a similar issue, but in my case, rather than being a timing issue as has been suggested in the home-manager bug, it was a case of missing variables in the systemd user environment. For me the symptom was; when starting a number of applications. For me, those applications did eventually start, I assume after some timeout expires, but the delay was considerable. I seem to have resolved my issue by including extra variables via; Note, it's possible to confirm the variables able to systemd user units with; systemctl --user show-environmentThis works for me, as of nixpkgs 89d5998 with nixos and home-manager as a nixos module, with |
|
For this this only was a problem after upgrading from 22.11 to 23.05. Using work around in #206630 (comment) fixed the problem for me using X/i3. But still trying to find a solution on my wayland/sway box: |
|
Hmmm. The work around to run: While not particularly great, it does at least seem to solve the immediate problem for me for now. |
This worked for me, I've been having this issue using sway with gnome installed. |
|
This issue has been mentioned on NixOS Discourse. There might be relevant details there: https://discourse.nixos.org/t/nextcloud-client-does-not-auto-start-in-gnome3/46492/7 |
|
As of more recent nixos this is no longer an issue for me, and I no longer need to mask xdg-desktop-portal-gnome. Curiously, on my box where I use sway, the xdg-desktop-portal-gnome service doesn't start until I manually start it, but even then it isn't causing any notable problems with applications such as Firefox, |
Nebucatnetzer
added a commit
to Nebucatnetzer/nixos
that referenced
this issue
Jun 10, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
I’m using NixOS Unstable with Gnome (Wayland) and NVidia proprietary driver. In my config I have enabled xdg-portal and since I use Gnome the xdg-portal used is the gnome one (xdg-desktop-portal-gnome). But when I log into Gnome Systemd tries to start xdg-desktop-portal-gnome but it fails with this error:
If I restart the xdg-desktop-portal-gnome:
systemctl restart --user xdg-desktop-portal-gnome.serviceIt starts correctly:
The problem is Firefox and other apps are taking a lot of time to start the first time. If I restart xdg-desktop-portal-gnome before start firefox the first time, it starts quickly.
Steps To Reproduce
Steps to reproduce the behavior:
xdg.portal.enable = true;Expected behavior
xdg-desktop-portal-gnomestart after loggin on gnome.Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers
@NixOS/gnome
Metadata
Please run
nix-shell -p nix-info --run "nix-info -m"and paste the result.The text was updated successfully, but these errors were encountered: