-
-
Notifications
You must be signed in to change notification settings - Fork 14.1k
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
nixosTests.gnome3-flashback: init #71212
Conversation
Perhaps I should move the session tests into a subdir
I might also want to hold off merging right away, the test script could be more flashback specific and check if those components are ok. |
8ac8a81
to
116abc0
Compare
@GrahamcOfBorg eval |
|
||
services.xserver.enable = true; | ||
|
||
services.xserver.displayManager.gdm.enable = false; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you add a comment why this is done? I do not think git blame
will carry to the original file
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, it seems in the gnome3-xorg
test, and in the past gnome3 module enabled gdm and then it got removed and this got added. And I've copied it here.
Actual issue with why we don't test with gdm is #66443.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, link there should be enough.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
GDM doesn't have any way to specify a default session, and I'm guessing it will happily launch wayland sessions even though GDM itself runs X11. Think I switched the test to LightDM when adding wayland support since I didn't manage to get it launch the correct session.
We'd probably have to do something with AccountsService to get it working.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Huh, that's weird, GDM X11 does indeed launch an X11 session, never mind me.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I wasn't sure why I was seeing error: unable to open display ":0.0"
when using xwininfo
. Only thing I thought of was it using wayland? But it was explicitly disabled.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@hedning You're actually correct, setting xserver default
will have no effects on gdm.
So we do need to set it with accountsservice over dbus.
Ok, so the feature to use different wm with gnome-flashback doesn't work as expected. So for example, with i3, it doesn't work without i3 installed because it needs its desktop file to launch required components. And even if I do this, none of the flashback components are visible (or maybe I just don't understand i3). And with xmonad there's no desktop file so it shows the "fail whale" requesting you to logout. (and gnome-flashback components are tiled) I don't really get why things have to be done in this way, can't you just do @jtojnar Has this ever worked? |
I am pretty sure it worked. We are creating the desktop file here: https://github.com/NixOS/nixpkgs/pull/53695/files#diff-eccb87703abad3f98a3c3e5c15584083R110-R125 |
Weird... I'll look closer, perhaps it has something to do with systemd sessions. |
The idea of #39871 was we would get rid of the old xserver module and just use DMs with session files. |
This reverts commit 60aedad. Using tests from NixOS#71212 I am now unable to reproduce there being issues with starting the default metacity flashback session without this.
Ok, so testing with
^ that happens and we get the |
Going to quote what I told @jtojnar in a pm on IRC
So I'm thinking because we see the message
it considers |
These are terminal tests identical to the gnome3-xorg test for various gnome flashback configurations.
0e89379
to
43d38ac
Compare
@jtojnar I disabled the other tests and just made the metacity one available. We should get to reporting the issues with those sessions to gnome-session eventually. (hopefully before 20.03). |
@GrahamcOfBorg test gnome3-flashback.metacity |
@@ -0,0 +1,98 @@ | |||
# GNOME Flashback Terminal tests for various custom sessions. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Terminal?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, they pretty much test if a terminal shows up.
Btw, I've pretty much rewritten this entirely locally. Though there's issues with the python testing driver and other ports preventing me from re-PRing it.
Thank you for your contributions.
|
yep, it's stale. I have a branch with it rewritten, just haven't gotten to PR'ing. |
Motivation for this change
Fixes #70561.
Test script is identical to the ancient one we have for gnome3-xorg, but at least by having this we'll catch things like #71210, and just testing the session is convenient on GitHub.
Has #71210 because you can't actually test the tests without it.
(please merge that first).
Things done
Haven't tested the tests yet 😄, as I have to run all three of them.
sandbox
innix.conf
on non-NixOS)nix-shell -p nix-review --run "nix-review wip"
./result/bin/
)nix path-info -S
before and after)