hai everyone!! 
happens only in x11. whomst a thunk it, mate!
systemd[1767]: Starting Portal service (GTK/GNOME implementation)...
.xdg-desktop-po[2317]: cannot open display:
systemd[1767]: xdg-desktop-portal-gtk.service: Main process exited, code=exited, status=1/FAILURE
systemd[1767]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
systemd[1767]: Failed to start Portal service (GTK/GNOME implementation).
hehe… but there’s more!!! this one makes me chortle and giggle quite a wee bit, haha! (after a reboot)
systemd[1866]: Failed to start Portal service (GTK/GNOME implementation).
systemd[1866]: xdg-desktop-portal-gtk.service: Start request repeated too quickly.
systemd[1866]: xdg-desktop-portal-gtk.service: Failed with result 'exit-code'.
and it repeats ad nauseam.
is this a hoo hoo or a haa haa moment, guys, does anyone know? i cant not use xorg until i finish all my silly little x11 exclusive games… as soon as i do, x11 go byebye, mwahahaha!
ANYWAY!
no, unplugging and plugging it back again doesnt help. hmm, i really thought it would work this time though!
my $DISPLAY is :0 both in xorg and wl.
i also tried adding it thusly:
xdg.portal.extraPortals = [
pkgs.xdg-desktop-portal-gtk
];
unfortunately, to no avail…
and nope, i have absolutely nothing in xdg.portal.config (for now). is that a problem, not changing anything?
in x11 i have these portal services launched:
xdg-desktop-portal-gtk (epic fail)
xdg-desktop-portal (worky yay)
as mentioned, in wayland (hyprland) i caught them all:
xdg-desktop-portal-gtk
xdg-desktop-portal-hyprland
xdg-desktop-portal
in another wayland (niri) session:
xdg-desktop-portal-gnome
xdg-desktop-portal-gtk
xdg-desktop-portal
interesting… would you look at that! they all work (clarification: only in wayland!
of course, AS PER USUAL, i may have done something in my configuration.nix. oh, but what did i do last time…? I DONT REMEMBER! that’s the fun bit! im such a goof…
but i really dont know… a variable? perchance! i shall have a proper look at it all tomorrow, i suppose! 
EDIT: whoopsie doodles, i forgot to say hello… 
(sry it was 3 in the morning)
EDIT2: people on the internet say that it’s a certified “session error”, however, i have literally nothing that changes .xinitrc and the like? okay, MAYBE its this thing, but i had THAT (see below) for the last couple a months and everything was alright?
environment.etc."xdg/autostart/xrandr.desktop".text = ''
[Desktop Entry]
Type=Application
Name=xrandr
Exec=sh -c "xrandr --output eDP --off && xrandr --output DisplayPort-0 --mode 1280x1024 --rate 60.02 --primary"
NoDisplay=true
''; # config.ron! -- 1280x1024@60.02, 1024x768@60.00, 1280x1024@75.03, 1024x768@75.03
…which eventually starts After=graphical-session.target
nevermind how horrid it looks (but pls tell me if i can improve this somehow? do i actually put it into .xinitrc or something? services.xserver.displayManager.sessionCommands? i probably should… i dont need a “desktop entry”!), this DOES NOT break a session, right? SURELY…
but anyway… the oddities dont stop here. the very same script i am talking about? it doesnt start either!
sh[1956]: /run/current-system/sw/bin/sh: regel 1: xrandr: opdracht niet gevonden
systemd[1883]: app-xrandr@autostart.service: Main process exited, code=exited, status=127/n/a
systemd[1883]: app-xrandr@autostart.service: Failed with result 'exit-code'.
excuse me, EXCUSE ME, you cant find xrandr? let me help you find xrandr:
~ xrandr
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 16384 x 16384
eDP connected (normal left inverted right x axis y axis)
800x1280 60.00 +
800x600 60.00
640x480 60.00
256x160 58.79
DisplayPort-0 connected primary 1280x1024+0+0 (normal left inverted right x axis y axis) 376mm x 301mm
1280x1024 60.02*+ 75.02
1280x960 60.00
1280x800 59.91
1152x864 75.00
1280x720 60.00
1024x768 75.03 60.00
832x624 74.55
800x600 75.00 60.32
640x480 75.00 59.94
720x400 70.08
~
see? worky. services? no worky. otherwise my internal eDP monitor wouldnt have turned off…
oh, i just noticed. bwahaha, xorg thinks that im using a DP connection. that’s hilarious! i am using HDMI to connect to a DVI-d (passive adapter)! (wait, now that i think about it, i think wayland also thinks the same? is this… normal?)
WAIT A MINUTE. what. WHAT???
guys, when i use xrandr like this:
~ sh xrandr
/run/current-system/sw/bin/xrandr: /run/current-system/sw/bin/xrandr: kan binair bestand niet uitvoeren
but when i FIRST get into sh and THEN run xrandr:
sh-5.3$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 16384 x 16384
...
then it works??? whatever, i dont think it is even related! SORRY. just strange.
but anyway, i have a slight suspicion it could be one of those “just pin a version ya @#$%!” situations, is it? but i raelly dont wanna do this, i have no idea how to, and i know it takes quite a lot of scary and unknown lines of code (unknown to me, that is, i am a noob, btw…)
also, i tried using my backup of flake.lock (sorry i keep forgetting to mention i am using flakes, nixos/nixpkgs/nixos-unstable branch, but do i have to? isnt it the norm by now using something “experimental”?) and no, nothing’s changed… alas… defeated, shamefully so.