Re: Kde window rules dialogue
Hey, > >Does anyone else have issues getting the edit dialogue to come up in > >kde 5.19 works nicely for me (using sid). > Can't offer any direct help (v5.17 here, mostly) but given several of us > have been experiencing issues with parts of KDE over the past week or > so, breakage is, currently, to be expected, I think. > > There's been a lot of activity transitioning KDE recently. Things are > migrating, and not always in a fully synchronised way. Breakage can be > expected for a while, I think. Please keep in mind - we can control sid directly with a new upload. But packages moved to testing is controlled via britney and we cannot control the decisions directly. That's why testing is sometimes more broken than sid when big transitions are happening. Because we never upload only part of plasma/pim etc. sid is normally only broken for one or two days. But the automatic system takes several data sources to decide if a package is free to migrate to testing the biggest issue is, that britney does not know bundles and do only decisions package by package. That is the reason why those metadata flaws often only visible when packages migrate to testing. hefee signature.asc Description: This is a digitally signed message part.
Re: Upgrade partially some packages (Plasma 5.19. 5 - 3) on testing broke plasma.
On Tue, 10 Nov 2020 at 14:48, Brad Rogers wrote: > Impossible to achieve. There's simply far too much that can go wrong to > cover every single (corner) case there may be. Is there anything to learn from this experience that can help us in future? Controls are never perfect, and there's always a cost-benefit to be done on them. No sense spending an extra 5 hours in work to prevent a problem that occasionally causes 5 minutes in inconvenience, for example. But, again, this isn't that situation. I have an unbootable system which could stay that way for days. But we don't have to give up because we cannot prevent every corner case. Making sure that all the KF libraries are at the same version doesn't seem like a corner case to me, especially after upstream said that you cannot mix and match versions. > It also ignores the ingenuity of idiots and their ability to foul things > up. True. Controls only work when people follow them. That means they generally fail against deliberate attempts to defeat them. When that happens, you throw your hands up and say that the system is too broken to fix. But I don't think that applies here. I understand that there are some very smart and generally honest people who get the GPG keys to the Debian repos.
Re: Bug#974158: RM: kdecoration/4:5.19.5-3
On Wed, 11 Nov 2020 05:28:23 +0900 Norbert Preining wrote: Hello Norbert, >Due to autpkgtest speedup, kdecoration 4:5.19.5-3 migrated to testing >before kwin, and now in testing we have > kwin 5.17 > kdecoration 5.19 >which breaks kwin and thus all KDE sessions. Thanks for posting this, Norbert. I was seeing some pretty odd behaviour, and I was not alone. We now know what's in store. Again, thank you. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" It's not your heart, it's your bank I want to break It's Yer Money - Wonder Stuff pgpz233eaCdxQ.pgp Description: OpenPGP digital signature
Bug#974158: RM: kdecoration/4:5.19.5-3
Package: release.debian.org Severity: normal User: release.debian@packages.debian.org Usertags: rm X-Debbugs-Cc: debian-kde@lists.debian.org Dear release team, Due to autpkgtest speedup, kdecoration 4:5.19.5-3 migrated to testing before kwin, and now in testing we have kwin 5.17 kdecoration 5.19 which breaks kwin and thus all KDE sessions. A fixed kdecoration 4:5.19.5-4 is already in unstable, but until it migrates to testing it would be better to remove kdecoration 4:5.19.5-3 from testing to prevent further breakage for users. See #974019 #974112 and probably some more. Thanks and all the best Norbert -- System Information: Debian Release: bullseye/sid APT prefers unstable APT policy: (500, 'unstable'), (200, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 5.9.6 (SMP w/4 CPU threads) Kernel taint flags: TAINT_UNSIGNED_MODULE Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system)
Re: Kde window rules dialogue
On Tue, 10 Nov 2020 12:12:01 -0500 Joe McEntire wrote: Hello Joe, >Does anyone else have issues getting the edit dialogue to come up in >kde 5.19 Can't offer any direct help (v5.17 here, mostly) but given several of us have been experiencing issues with parts of KDE over the past week or so, breakage is, currently, to be expected, I think. There's been a lot of activity transitioning KDE recently. Things are migrating, and not always in a fully synchronised way. Breakage can be expected for a while, I think. On top of that, breakage is pretty much par for the course in sid and/or experimental. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Just stop and take a second U & Ur Hand - P!nk pgpkoOSQhAxbi.pgp Description: OpenPGP digital signature
Re: Upgrade partially some packages (Plasma 5.19. 5 - 3) on testing broke plasma.
On Tue, 10 Nov 2020 13:31:17 -0500 Borden Rhodes wrote: Hello Borden, >over 30 years of packaging to prevent unbootable operating system >errors from happening Impossible to achieve. There's simply far too much that can go wrong to cover every single (corner) case there may be. It also ignores the ingenuity of idiots and their ability to foul things up. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" You're all invited to a party, you don't even have to come Get The Funk Out - Extreme pgp4Iv9BZJzqe.pgp Description: OpenPGP digital signature
Kde window rules dialogue
Does anyone else have issues getting the edit dialogue to come up in kde 5.19 or higher? Basically if you go to system settings, then to window management, then window rules and add a new rule, then finally click the pencil icon to edit the rule, nothing happens. This is also true if you right click the titlebar of a window and then go to more actions, then configure special window setting or special application settings, nothing happens. I'm curious if this is a kde bug, that hopefully gets fixed before the Debian freeze, or if I'm simply missing a package or something. Thanks, Joe McEntire get...@live.com
Re: Upgrade partially some packages (Plasma 5.19. 5 - 3) on testing broke plasma.
On Mon, 9 Nov 2020 at 16:20, Lisandro Damián Nicanor Pérez Meyer wrote: > That also means you have great expectations from us :-D Are we being unreasonable assuming that we can turn our computers off and back on and have them still boot? > But let me assure you that if this kind of things happens is because > (as Norbert said) we are humans and this is a **huge** stack to work > on, it requires a lot of time and detail, so things might slip through > from time to time. That's fair, KDE is infuriatingly complex and the volunteers do this at their own expense with already stretched resources. Nevertheless, it's concerning to learn the amount of manual work involved. I sympathise with the extreme tedium this must entail. I also hoped that the Debian rulers would have evolved adequate controls over 30 years of packaging to prevent unbootable operating system errors from happening. Or, at least, if they do happen, have useful error messages to shorten the guesswork. It's very frustrating with no useful error messages to go on search engines and have to guess what the problem might be - only to be led down one dead end after another. In accountancy, we call the former "preventative controls" and the latter "corrective controls." The question then is what controls or automation can be added to the process to reduce the likelihood of these sorts of errors from happening in the future? > Wanna check? Be sure to start packaging and come > and join us! That's a bluff you know we won't call. It's analogous to saying "Run for office and fix the government if you don't like it." As much as I'd love to help, I don't have the resources or knowledge to begin assisting. As you acknowledged in your previous sentence, KDE "is a **huge** stack to work on, it requires a lot of time and detail" - how could us plebs possibly get up to speed in a reasonable time? Anyhow, is there a way to roll the repos back to 5.17 until 5.19 is fully ready or am I stuck with an unbootable operating system until 5.19 goes downstream?
Re: Smart location no longer smart
On Tue, 10 Nov 2020 18:31:18 +0100 "luca.pedrielli" wrote: Hello luca.pedrielli, >This time I can not confirm and Minimize/maximize/Close and RollUp are >working properly here. Okay, thanks again, Luca. Seems we have to play the waiting game after all. :-) -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" Life's short, don't make a mess of it No Time To Be 21 - The Adverts pgpR_O_pVNKHL.pgp Description: OpenPGP digital signature
Re: Smart location no longer smart
Il 10/11/20 18:10, Brad Rogers ha scritto: On Tue, 10 Nov 2020 17:08:55 +0100 "luca.pedrielli" wrote: Hello luca.pedrielli, add AllowKDEAppsToRememberWindowPositions=false in ~/.config/kdeglobals I'm seeing some undesirable side effects now; Close gadget now toggles maximised window. Maximize gadget minimizes window to taskbar. Minimize gadget does nothing. This time I can not confirm and Minimize/maximize/Close and RollUp are working properly here. How critical is position of AllowKDEAppsToRememberWindowPositions=false in kdeglobals? I've placed it in the section headed [General] Me too. At the end of [General] section. Not a big deal, as I can workaround the issues, but it'll take a day or two to get used to. Then I'll probably have to 'unlearn' the changes later. -- Saluti, Luca Pedrielli
Re: Smart location no longer smart
On Tue, 10 Nov 2020 17:08:55 +0100 "luca.pedrielli" wrote: Hello luca.pedrielli, >add AllowKDEAppsToRememberWindowPositions=false in ~/.config/kdeglobals I'm seeing some undesirable side effects now; Close gadget now toggles maximised window. Maximize gadget minimizes window to taskbar. Minimize gadget does nothing. How critical is position of AllowKDEAppsToRememberWindowPositions=false in kdeglobals? I've placed it in the section headed [General] Not a big deal, as I can workaround the issues, but it'll take a day or two to get used to. Then I'll probably have to 'unlearn' the changes later. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" This disease is catching Into The Valley - Skids pgpyIPIYkyloY.pgp Description: OpenPGP digital signature
Re: Smart location no longer smart
On Tue, 10 Nov 2020 17:08:55 +0100 "luca.pedrielli" wrote: Hello luca.pedrielli, >it's working here: Okay, thanks. Two mistakes on my part; Misreading/misunderstanding the article you cited and assuming I needed to wait for an update to KDE to (at least) v5.19. > logout/login Didn't do that - despite adding the requisite line to kdeglobals. All is now working as it should. Once again, many thanks for your help and guidance. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" They said we'd be artistically free, but that was on a bit of paper Complete Control - The Clash pgpjLmHcJEA7X.pgp Description: OpenPGP digital signature
Re: Smart location no longer smart
Il 10/11/20 16:56, Brad Rogers ha scritto:
On Tue, 10 Nov 2020 16:42:05 +0100
"luca.pedrielli" wrote:
Hello luca.pedrielli,
https://www.reddit.com/r/kde/comments/j96kmq/window_placement_settings_not_working/ga90m1h/
Nice find. Thanks again.
Just have to play the waiting game now.
{fx: taps foot impatiently}
it's working here:
add AllowKDEAppsToRememberWindowPositions=false in ~/.config/kdeglobals
/[General]/
/.../
/.../
/.../
/AllowKDEAppsToRememberWindowPositions=false//
/
and logout/login
--
Saluti, Luca Pedrielli
Re: Smart location no longer smart
On Tue, 10 Nov 2020 16:42:05 +0100
"luca.pedrielli" wrote:
Hello luca.pedrielli,
>https://www.reddit.com/r/kde/comments/j96kmq/window_placement_settings_not_working/ga90m1h/
Nice find. Thanks again.
Just have to play the waiting game now.
{fx: taps foot impatiently}
--
Regards _
/ ) "The blindingly obvious is
/ _)radnever immediately apparent"
Loaded like a freight train flyin' like an aeroplane
Nightrain - Guns 'N' Roses
pgpCsume0fTnd.pgp
Description: OpenPGP digital signature
Re: Smart location no longer smart
Il 10/11/20 15:35, Brad Rogers ha scritto: Hello, Using Debian testing, regularly updated (almost daily). I have KDE set to locate windows using the "Smart" option. For the last week or so, I've noticed that Dolphin (maybe others, but I've not noticed the same behaviour with other software) is now always located in the same place. IOW, when I open a second instance, it gets placed exactly over the top of the existing window. That is, 'smart' location seems to not work. I've looked in KDE & Dolphin settings, thinking I may well have set something incorrectly, but without luck. There seems to be no existing bug reports, further leading me to think the problem is local. I tried setting up a new user, and found that exhibited the same behaviour. Deleting dolphinrc didn't help. There are no special window or application rules for dolphin, so I'm at a loss. Anybody have any suggestions. Any help greatly appreciated. Thanks. https://www.reddit.com/r/kde/comments/j96kmq/window_placement_settings_not_working/ga90m1h/ -- Saluti, Luca Pedrielli
Re: Smart location no longer smart
On Tue, 10 Nov 2020 16:14:47 +0100 "luca.pedrielli" wrote: Hello luca.pedrielli, >I can confirm :( Okay. Not "Just me" then. >I tried with konsole and the behavieur is the same. Same here. I'd not noticed it with konsole before. I rarely have more than one konsole window open, however. In konsole, I prefer to use tabs. >Tried also with other Window placement (cascade, random, Under-mouse) >with no luck. I did the same. Also, without success. Thanks for your confirmation and reply. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" It's cool to know nothin' Never Miss A Beat - Kaiser Chiefs pgpIwHiQ0bwQA.pgp Description: OpenPGP digital signature
Re: Smart location no longer smart
Il 10/11/20 15:35, Brad Rogers ha scritto: Hello, Using Debian testing, regularly updated (almost daily). I have KDE set to locate windows using the "Smart" option. For the last week or so, I've noticed that Dolphin (maybe others, but I've not noticed the same behaviour with other software) is now always located in the same place. IOW, when I open a second instance, it gets placed exactly over the top of the existing window. That is, 'smart' location seems to not work. I've looked in KDE & Dolphin settings, thinking I may well have set something incorrectly, but without luck. There seems to be no existing bug reports, further leading me to think the problem is local. I tried setting up a new user, and found that exhibited the same behaviour. Deleting dolphinrc didn't help. There are no special window or application rules for dolphin, so I'm at a loss. Anybody have any suggestions. Any help greatly appreciated. Thanks. I can confirm :( I tried with konsole and the behavieur is the same. Tried also with other Window placement (cascade, random, Under-mouse) with no luck. -- Saluti, Luca Pedrielli
Smart location no longer smart
Hello, Using Debian testing, regularly updated (almost daily). I have KDE set to locate windows using the "Smart" option. For the last week or so, I've noticed that Dolphin (maybe others, but I've not noticed the same behaviour with other software) is now always located in the same place. IOW, when I open a second instance, it gets placed exactly over the top of the existing window. That is, 'smart' location seems to not work. I've looked in KDE & Dolphin settings, thinking I may well have set something incorrectly, but without luck. There seems to be no existing bug reports, further leading me to think the problem is local. I tried setting up a new user, and found that exhibited the same behaviour. Deleting dolphinrc didn't help. There are no special window or application rules for dolphin, so I'm at a loss. Anybody have any suggestions. Any help greatly appreciated. Thanks. -- Regards _ / ) "The blindingly obvious is / _)radnever immediately apparent" They said we'd be artistically free, but that was on a bit of paper Complete Control - The Clash pgpluF1JlQbJ3.pgp Description: OpenPGP digital signature
Re: Current status of KDE in Sid
Hi all, Am Dienstag, 10. November 2020, 00:29:14 CET schrieb Miguel A. Vallejo: > Hello Hector. > YES! > Your proposal worked like a charm! Everything was updated without any problem. > Thank you! ...just as a very gentle reminder of what I had a misconception about in the past and have since learnt: This is exactly what unstable/testing is all about: Sorting out these kinds of things - neither unstable nor testing are some sort of rolling release (as I was initially mistaking it for, at least in the case of testing). Huge thanks to the team for all the effort, and huge thanks for the daring to endeavour into testing new KDE packages! :-) Best, Christian -- signature.asc Description: This is a digitally signed message part.
