-
-
Notifications
You must be signed in to change notification settings - Fork 14.6k
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
kdePackages: Plasma 6.1.5 -> 6.2 #341487
kdePackages: Plasma 6.1.5 -> 6.2 #341487
Conversation
Result of 69 packages marked as broken and skipped:
12 packages failed to build:
1782 packages built:
|
343e6fe
to
7f042c7
Compare
Result of 69 packages marked as broken and skipped:
1 package failed to build:
1804 packages built:
The failing libsForGt5.pix has the following error:
|
@@ -249,10 +249,11 @@ in { | |||
|
|||
xdg.portal.enable = true; | |||
xdg.portal.extraPortals = [ | |||
kdePackages.kwallet | |||
kdePackages.xdg-desktop-portal-kde | |||
pkgs.xdg-desktop-portal-gtk |
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.
pkgs.xdg-desktop-portal-gtk | |
(pkgs.xdg-desktop-portal-gtk.override { buildPortalsInGnome = false; }) |
I've done this locally to remove some gnome dependencies. I think all the functionality still works as before.
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.
This no longer exists. See #345979
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.
So Plasma 6 now always needs to depend on half the gnome backend libraries?
Do we really need to increase closure size every other month?
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.
Even if this option wasn't removed, setting it would make the gtk portal useless as buildPortalsInGnome was disabling the settings portal.
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.
Yes someone on Matrix was hitting issues with not having this portal, and specifically the settings portal, just a week or so ago, which is why this was added for Plasma in the first place. Upstream recommends including it.
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.
@mjm it was 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.
Wasn't not having to depend on components of a DE you don't use the whole point of xdg-desktop-portal existing in the first place?
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.
No, it exists because flatpak people are afraid of same connection use in DE D-Bus APIs
c85fe89
to
5f05440
Compare
👋🏼 |
That's not particularly helpful. Do you have a log file or anything? Are you sure the issue is with Plasma and not, like, the rest of the staging merge? |
So far I know what I observed: sddm shows up, I enter my password, press enter, the input field and buttons deactivate and nothing else happens. Repeats after reboot. I'll give it another shot in some minutes when I get to my primary monitor that doesn't do weird stuff 🤞🏼 |
|
And of course it worked this time, when I wanted to reproduce it. 😞 I'm so sorry for the noise. Please ignore me until I hit the next issue 🙈 |
I've been having this happen as well and have a hunch it's related to session restore. I have luck sometimes with switching to TTY 1 then back to TTY 7 to get the graphical session to actually show up for some reason. |
It just happened here again, after I had to force reboot my machine. Nothing worked and when I was about to give up and switch back to 6.1... I have 2 monitors, one large secondary on my desktop, one primary projector. They usually run mutually exclusive. I've got the stuck login on the secondary screen. Powering up the projector (it's the only screen working in bios/grub) I've got a second login screen, not stuck. That one somehow worked fine... Afterall, this is probably not a nix-related issue and I should open a proper bug ticket in the plasma project. |
Much longer loading of kde plasma 6.2 compared to 6.1 |
Fixed in 6.2.1.1 |
Description of changes
staging-next because of plasma-wayland-protocols updates
https://kde.org/announcements/plasma/6/6.2.0/
Things done
nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.