Re: Developing KWin, starting nested KWin
I found this post nice for some inspirationDeveloping KWin Wayland – TheBlindCowproli.netOn May 8, 2024, at 6:31 PM, Gerion Entrup wrote:Hi,I'm interested in playing around with KWin's source code (especially with the built-in tiling feature). However, I find it kind of complicated to find a good workflow for development (I'm on a desktop with Plasma/KWin on Wayland).I tried to research what is possible and see this possibilities:- Replace the current running KWin. I'm pretty sure that this is not a good idea, especially, when I include buggy code that segfaults, etc.- Start a nested KWin. I saw this here [1] and it seems to work quite well. However, I need some kind of launcher. I tried krunner but it disappears and pressing the keybinding just opens the "real" krunner. A terminal emulator also works but opening new windows there is not quite comfortable.- Start KWin on another TTY. I did not try this but it seems quite complicated to change the whole context every time to test something.So, what is your workflow? Is it possible to start a whole Plasma session inside a nested KWin and how are keybindings captured there?Best,Gerion[1] https://community.kde.org/KWin/Wayland#Starting_a_nested_KWin signature.asc Description: Binary data
Developing KWin, starting nested KWin
Hi, I'm interested in playing around with KWin's source code (especially with the built-in tiling feature). However, I find it kind of complicated to find a good workflow for development (I'm on a desktop with Plasma/KWin on Wayland). I tried to research what is possible and see this possibilities: - Replace the current running KWin. I'm pretty sure that this is not a good idea, especially, when I include buggy code that segfaults, etc. - Start a nested KWin. I saw this here [1] and it seems to work quite well. However, I need some kind of launcher. I tried krunner but it disappears and pressing the keybinding just opens the "real" krunner. A terminal emulator also works but opening new windows there is not quite comfortable. - Start KWin on another TTY. I did not try this but it seems quite complicated to change the whole context every time to test something. So, what is your workflow? Is it possible to start a whole Plasma session inside a nested KWin and how are keybindings captured there? Best, Gerion [1] https://community.kde.org/KWin/Wayland#Starting_a_nested_KWin signature.asc Description: This is a digitally signed message part.
Re: KDE Gear projects with failing CI (master) (7 May 2024)
On Wed, May 8, 2024 at 10:03 AM Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for > multiple > reasons. > > > Bad news: 1 repository is still failing and 3 new ones started failing > > > tokodon - 3rd week > * https://invent.kde.org/network/tokodon/-/pipelines/682294 > * suse_tumbleweed_qt67 fails > This looks to be a broken test that is relying on the selenium-webdriver-at-spi scaffolding (that i've warned against previously) and crashing for reasons not quite known. It is unlikely you will see this on a developer system as the CI system compiles everything in Debug mode (which means asserts are enabled) while developer systems won't have them enabled (due to using RelWithDebInfo). Probably best to just disable that test. > > kdenlive - NEW > * https://invent.kde.org/multimedia/kdenlive/-/pipelines/682483 > * craft_windows_qt6_x86_64 fails to compile kdenlivesettingsdialog.cpp > > > dolphin - NEW > * https://invent.kde.org/system/dolphin/-/pipelines/682230 > * craft_windows_qt6_x86_64 fails without any discernible error > > > kdeconnect-kde - NEW > * https://invent.kde.org/network/kdeconnect-kde/-/pipelines/682282 > * craft_windows_qt6_x86_64 fails without any discernible error > > > Cheers, > Albert > Cheers, Ben
Re: KDE Gear projects with failing CI (release/24.05) (7 May 2024)
On Wed, May 8, 2024 at 7:19 PM Albert Astals Cid wrote: > Please work on fixing them, otherwise i will remove the failing CI jobs on > their 4th failing week, it is very important that CI is passing for > multiple > reasons. > > Bad news: 9 repositories have started failing and 1 is still failing > > > cantor - 3rd week > * https://invent.kde.org/education/cantor/-/pipelines/676922 > * suse_tumbleweed_qt515 and windows_qt515 tests fail > > > tokodon - NEW > * https://invent.kde.org/network/tokodon/-/pipelines/682468 > * craft android fails > Will be fixed by https://invent.kde.org/packaging/craft-blueprints-kde/-/merge_requests/833 > > > kimap - NEW > * https://invent.kde.org/pim/kimap/-/pipelines/682429 > * freebsd tests fail > Do we know what this test is trying to do and what hostname it is assuming is invalid? > > > kig - NEW > * https://invent.kde.org/education/kig/-/pipelines/682321 > * craft_macos_x86_64 fails to compile Qt5 > > > gwenview - NEW > * https://invent.kde.org/graphics/gwenview/-/pipelines/682335 > * flatpak fails to compile > The Flatpak job likely needs to depend on a more stable tarball > > > craft_windows_qt6_x86_64 broken in several repos: no easy to understand > error > * https://invent.kde.org/utilities/kate/-/pipelines/682305 > * https://invent.kde.org/system/dolphin/-/pipelines/682309 > * https://invent.kde.org/graphics/okular/-/pipelines/682346 > * https://invent.kde.org/utilities/filelight/-/pipelines/682349 > * https://invent.kde.org/network/neochat/-/pipelines/682465 All fixed by Ingo restarting the signer process. > > > > Cheers, > Albert > Cheers, Ben
Re: KDE Gear projects with failing CI (master) (7 May 2024)
On Mittwoch, 8. Mai 2024 00:03:34 CEST Albert Astals Cid wrote: > dolphin - NEW > * https://invent.kde.org/system/dolphin/-/pipelines/682230 > * craft_windows_qt6_x86_64 fails without any discernible error > > > kdeconnect-kde - NEW > * https://invent.kde.org/network/kdeconnect-kde/-/pipelines/682282 > * craft_windows_qt6_x86_64 fails without any discernible error In both cases the last line logged under 'Executing "step_script" stage of the job script' is ``` Signing with custom command ``` and the error is ``` ERROR: Job failed: script timeout context: context deadline exceeded ``` This means both jobs timed out while waiting for the signer. The usual reason for the timeout is that unfortunately the windows signer stopped working once more. Maybe because the VM rebooted. Improving this is on Ben's long to do list. Re-runs of both jobs have now succeeded (after I restarted the signing service). Regards, Ingo signature.asc Description: This is a digitally signed message part.
KDE Gear projects with failing CI (release/24.05) (7 May 2024)
Please work on fixing them, otherwise i will remove the failing CI jobs on their 4th failing week, it is very important that CI is passing for multiple reasons. Bad news: 9 repositories have started failing and 1 is still failing cantor - 3rd week * https://invent.kde.org/education/cantor/-/pipelines/676922 * suse_tumbleweed_qt515 and windows_qt515 tests fail tokodon - NEW * https://invent.kde.org/network/tokodon/-/pipelines/682468 * craft android fails kimap - NEW * https://invent.kde.org/pim/kimap/-/pipelines/682429 * freebsd tests fail kig - NEW * https://invent.kde.org/education/kig/-/pipelines/682321 * craft_macos_x86_64 fails to compile Qt5 gwenview - NEW * https://invent.kde.org/graphics/gwenview/-/pipelines/682335 * flatpak fails to compile craft_windows_qt6_x86_64 broken in several repos: no easy to understand error * https://invent.kde.org/utilities/kate/-/pipelines/682305 * https://invent.kde.org/system/dolphin/-/pipelines/682309 * https://invent.kde.org/graphics/okular/-/pipelines/682346 * https://invent.kde.org/utilities/filelight/-/pipelines/682349 * https://invent.kde.org/network/neochat/-/pipelines/682465 Cheers, Albert
