Re: Plasma with Wayland: No ssh-agent started automatically?
Am Dienstag, 14. Februar 2023, 23:07:52 CET schrieb Martin Steigerwald: > Martin Steigerwald - 14.02.23, 22:27:16 CET: > > Do I really need to start ssh-agent by hand with Plasma (Wayland) > > session type? > > Never mind. I tried some weeks back and it seemed that there *was* a ssh-agent running, but some processes had SSH_AGENT.* set and some not. For reasons I did not investigate further, it seemed to depend on how child processes were spawned. > That is not the only issue. Kick off menu with scaling 150% spanning the > whole 1920x1080 laptop screen and artifacts while typing in Konsole are > other issues with Wayland. Multi screen setups, esp. with different scaling factors seem to have issues, too. And any scaling factor different from 100% led to blurring, even in text. > That still does not appear to be ready for me. > > Maybe some day. I have a recurring event "Test Wayland & KDE" every December ;-). Regards, Dietz signature.asc Description: This is a digitally signed message part.
Re: Plasma with Wayland: No ssh-agent started automatically?
Martin Steigerwald - 14.02.23, 22:27:16 CET: > Do I really need to start ssh-agent by hand with Plasma (Wayland) > session type? Never mind. That is not the only issue. Kick off menu with scaling 150% spanning the whole 1920x1080 laptop screen and artifacts while typing in Konsole are other issues with Wayland. That still does not appear to be ready for me. Maybe some day. Thanks, -- Martin
Plasma with Wayland: No ssh-agent started automatically?
Hi! I just switched the session type from Plasma (X11) to Plasma (Wayland). No ssh-agent is started automatically anymore. There is an older forum post about this: ssh-agent not started in Wayland https://forum.kde.org/viewtopic.php?t=153769 Do I really need to start ssh-agent by hand with Plasma (Wayland) session type? Thanks, -- Martin
Re: Runit with KDE Plasma: krunner current working directory /
Reinhard Karcher - 10.02.23, 15:20:49 CET: > I have a different system: Debian SID/Testing with usrmerge, systemd > and bash, and I see the expected behavior: cwd linked to /home/USER. > So I suspect, that it is not caused by KDE/QT. Just for the record: Sometimes the truth is not that digital. It appears to be that there is a relation with an upstream change that affects anything except Systemd. krunner starts applications with cwd "/" with init system other than systemd (openrc, runit, ...) https://bugs.kde.org/432975 Plasma appears to use different code paths for systemd and non systemd startup: https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ Will be looking with upstream and/or Debian's other init team whether a solution can be found or… apply a work-around. Best, Martin > Am Freitag, 10. Februar 2023, 14:39 schrieb Martin Steigerwald: > > Hi! > > > > This puzzled me for a long time and I have no idea where to report > > this: > > > > …proc# ls -ld $(pidof krunner)/cwd > > lrwxrwxrwx 1 USER USER 0 10. Feb 14:26 15116/cwd -> / > > …proc# ls -ld $(pidof plasmashell)/cwd > > lrwxrwxrwx 1 USER USER 0 10. Feb 14:27 9191/cwd -> /home/USER > > > > This is with /bin/sh pointing to Dash, the user shell is Z-Shell, > > but I have also seen this on systems where the user shell is Bash. > > No usrmerge. (I hope to avoid it as long as possible.) > > > > According to pstree krunner's parent process is runit which of > > course > > has current working directory pointing to /. > > > > Plasmashell instead is going like this > > > > ├─runsv(2066)─┬─sddm(2116)─┬ > > > > ─sddm-helper(8989)───startplasma-x11(8994)─┬─plasma_session(9056)─┬ > > > > I bet through SDDM its working directory is set to the actual home > > directory of the user. > > > > Is this a bug with runit? Is this an upstream bug? > > > > Any idea how to find the root cause for this and determine what > > needs to be fixed? > > > > I tried to work around this by doing "cd $HOME" in my zshrc. However > > this makes open new tabs in Konsole always start at $HOME even when > > I > > open them with a tab active which has a different cwd. Yeah, I got > > only do "cd $HOME" if current working directory is /, but I'd > > rather see this fixed. However, I do not even know where to report > > this issue. > > > > Any insight greatly appreciated. -- Martin
Re: Runit with KDE Plasma: krunner current working directory /
Reinhard Karcher - 10.02.23, 15:20:49 CET: > I have a different system: Debian SID/Testing with usrmerge, systemd > and bash, and I see the expected behavior: cwd linked to /home/USER. > So I suspect, that it is not caused by KDE/QT. Just for the record: Sometimes the truth is not that digital. It appears to be that there is a relation with an upstream change that affects anything except Systemd. krunner starts applications with cwd "/" with init system other than systemd (openrc, runit, ...) https://bugs.kde.org/432975 Plasma appears to use different code paths for systemd and non systemd startup: https://blog.davidedmundson.co.uk/blog/plasma-and-the-systemd-startup/ Will be looking with upstream and/or Debian's other init team whether a solution can be found or… apply a work-around. Best, Martin > Am Freitag, 10. Februar 2023, 14:39 schrieb Martin Steigerwald: > > Hi! > > > > This puzzled me for a long time and I have no idea where to report > > this: > > > > …proc# ls -ld $(pidof krunner)/cwd > > lrwxrwxrwx 1 USER USER 0 10. Feb 14:26 15116/cwd -> / > > …proc# ls -ld $(pidof plasmashell)/cwd > > lrwxrwxrwx 1 USER USER 0 10. Feb 14:27 9191/cwd -> /home/USER > > > > This is with /bin/sh pointing to Dash, the user shell is Z-Shell, > > but I have also seen this on systems where the user shell is Bash. > > No usrmerge. (I hope to avoid it as long as possible.) > > > > According to pstree krunner's parent process is runit which of > > course > > has current working directory pointing to /. > > > > Plasmashell instead is going like this > > > > ├─runsv(2066)─┬─sddm(2116)─┬ > > > > ─sddm-helper(8989)───startplasma-x11(8994)─┬─plasma_session(9056)─┬ > > > > I bet through SDDM its working directory is set to the actual home > > directory of the user. > > > > Is this a bug with runit? Is this an upstream bug? > > > > Any idea how to find the root cause for this and determine what > > needs to be fixed? > > > > I tried to work around this by doing "cd $HOME" in my zshrc. However > > this makes open new tabs in Konsole always start at $HOME even when > > I > > open them with a tab active which has a different cwd. Yeah, I got > > only do "cd $HOME" if current working directory is /, but I'd > > rather see this fixed. However, I do not even know where to report > > this issue. > > > > Any insight greatly appreciated. -- Martin
Bug#1031277: gcompris-qt: gcompris doesn't start - Your root item has to be a window
Package: gcompris-qt Version: 3.1-1 Severity: normal X-Debbugs-Cc: stefan.kr...@posteo.de Dear Maintainer, on a testing system, I'm not able to start gcompris. I get an error message "Your root item has to be a window" on the terminal. -- Stefan
kosmindoormap_22.12.2-2_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 14 Feb 2023 14:02:06 +0100 Source: kosmindoormap Architecture: source Version: 22.12.2-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Sandro Knauß Changes: kosmindoormap (22.12.2-2) unstable; urgency=medium . * Make failing tests not fail the build for unstable architectures. Checksums-Sha1: 1eab1d6b176d34442f87f3f0b354f01cca1c0070 2895 kosmindoormap_22.12.2-2.dsc 0e970a5150e64fc16bc348c8c3a3e7f98edc6948 25568 kosmindoormap_22.12.2-2.debian.tar.xz 94b73606fbda9dc580faa4304354e803fe708d3a 13701 kosmindoormap_22.12.2-2_source.buildinfo Checksums-Sha256: 2444a8d1900eb0c4e8f901c681befe8d1844016b8937e13979d7738f6ff908a9 2895 kosmindoormap_22.12.2-2.dsc 49f7a9be3733ddc6a0bb1d2de55f4b736c2eed03834ee9a04959743bca3ce7aa 25568 kosmindoormap_22.12.2-2.debian.tar.xz fb73f84843a031bf95daad128c57d0745090bea99de32106e3bc766a23dd3794 13701 kosmindoormap_22.12.2-2_source.buildinfo Files: f7803fafc620928a67269984eae7d810 2895 libs optional kosmindoormap_22.12.2-2.dsc 8cc2b69c26fe6d241ce5af6dce7d08f3 25568 libs optional kosmindoormap_22.12.2-2.debian.tar.xz be1af432cf0bd70b8bf4cb319b2559aa 13701 libs optional kosmindoormap_22.12.2-2_source.buildinfo -BEGIN PGP SIGNATURE- iQJFBAEBCgAvFiEEOewRoCAWtykmSRoG462wCFBgVjYFAmPrhmYRHGhlZmVlQGRl Ymlhbi5vcmcACgkQ462wCFBgVjartQ//ecx5nj9x+2T5fKePGOF49Wjh0qYxIh2Q qvBhoyiP3IVFVTUMgW99SD0n454WW/azsvuK/Sx9xKeGIyaBjOKLh1ponUPcNDFm N2bpH58tk45W3uaTlpo5Xbbj+p/u+Av/X/BKkur10/z7aE6ojVx9OwavtJBA/CV3 IRrIT1kwomm6BLTo52qXZnV/jzT64SrorsY1G4FlQXJVA271FehPhcyT8H6JY3aY 5+8e7z1qq0IU5CoYUhf3QFwxuTuv0XSYQ5fjylCy9VDCRokPjFxVK/WJ/oA3vpjJ 0jvG4urLD9LG1cCo5DUH/0AT3LgHt2OdWv4RlzGiHQSlif83ZBh7kkxi7KpcJ4TQ ULW12UasElk+m1LmvQrS6sukLD/iY2HGKececPoYRMhmA0XXNkEXpkgehw9Yih7Z fiPUU88eiUaoqoncj7Le6hqXv47pY87eDjrj+OnwEqhTUs7M4jWxdnelw4eNShDb /v1KOuXV/tSLRusSGDmDxxqnsmTHCWk2VjSibWcUl+772v+dSSmEXq8/1eh8Ao10 IcLKy9hWMGgGEyYgxmnx7TazL4yPNT9Ul6e3lEfdeIjbOPt294/AT+Qc3ZsxEhN6 GjMeUVvQ6fuOka4AQ+ao3pNOiAxuloEUu7FlIvx4B7G34AoF8qv8KgBkVYsV+nZV osNb6e6ubGU= =u/zm -END PGP SIGNATURE-
Processing of kosmindoormap_22.12.2-2_source.changes
kosmindoormap_22.12.2-2_source.changes uploaded successfully to localhost along with the files: kosmindoormap_22.12.2-2.dsc kosmindoormap_22.12.2-2.debian.tar.xz kosmindoormap_22.12.2-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
ksyntax-highlighting_5.103.0-2_source.changes ACCEPTED into unstable
Thank you for your contribution to Debian. Accepted: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Format: 1.8 Date: Tue, 14 Feb 2023 08:36:41 +0100 Source: ksyntax-highlighting Architecture: source Version: 5.103.0-2 Distribution: unstable Urgency: medium Maintainer: Debian Qt/KDE Maintainers Changed-By: Pino Toscano Changes: ksyntax-highlighting (5.103.0-2) unstable; urgency=medium . * Team upload. * Remove inactive Uploaders. * Modernize building: - add the dh-sequence-kf5 build dependency to use the kf5 addon automatically - add the dh-sequence-pkgkde-symbolshelper build dependency to use the pkgkde_symbolshelper automatically - drop the pkg-kde-tools build dependency, no more explicitly needed - drop all the manually specified addons and buildsystem for dh * Remove breaks/replaces for existing packages with versions older than oldstable. * Make sure to link with atomic on architectures that need it, i.e. armel m68k mipsel sh4. * Update symbols files from the logs of buildds. Checksums-Sha1: 6aa16b30d254975dfef84635ab88fb4923592766 3231 ksyntax-highlighting_5.103.0-2.dsc 851ea02139e9380f37f518c81295e83ec2bf0a44 21932 ksyntax-highlighting_5.103.0-2.debian.tar.xz 65de4b524af229d0d0fc108b58cff9dddc1eb5b5 12128 ksyntax-highlighting_5.103.0-2_source.buildinfo Checksums-Sha256: e9c13452d21c61603814fbf252be5a8f4baf96c69beb0d436906bd306f16332c 3231 ksyntax-highlighting_5.103.0-2.dsc 542e2e9e01c12bce1ccfeb0c9e494328c194e086b8bb61d9d25ae5b3aedf6f0b 21932 ksyntax-highlighting_5.103.0-2.debian.tar.xz 82d1b207d65010bfb667dd0f945e49a9cc624f7ac9142976524d25fe1725f5e8 12128 ksyntax-highlighting_5.103.0-2_source.buildinfo Files: 121474a951ed312115ddf535d228b156 3231 libs optional ksyntax-highlighting_5.103.0-2.dsc 4b63d8e4814363edd69cb476acdf799f 21932 libs optional ksyntax-highlighting_5.103.0-2.debian.tar.xz 9e292bf5caa67e4f0dcb2805608d8d70 12128 libs optional ksyntax-highlighting_5.103.0-2_source.buildinfo -BEGIN PGP SIGNATURE- iQIzBAEBCgAdFiEEXyqfuC+mweEHcAcHLRkciEOxP00FAmPrOi8ACgkQLRkciEOx P03wGw/+Kte+IAMist4Q/7O1AlGV2TfFlDvkiGVP3KRhXJ8u+2jdCJuoXtA/sbhO Us9RVq5FUz8M3NdFkypxwr+SgCMM36BaqobrBd5j7HuI45kc2iqaM6IVe1FqOBNE 5z3IqhbPyNbziFj9Bz3TaW9WJvdbpwWNi5UV8HHHgc3FP9WKUamwGwl8w2KJgQ6X yOTVVoBuCrkomzrY0AmqY3cE/tyCXIkPJgbihNr/M/VYUlghN5zm0/FVUB58Ez7u XMyIkuMWUjiNdQkLrtZlwQlWdUB9zPwvtCcNS54Ei6Kqqw3NIJBOkDDk3DbMAwzP PHEU36a9sKNynw9VQN5iCNCfnvPhrjSC7A+SJDsAWaCQmAV3TIslG2hYXmrsuihv p5vOrxYkhTM4zxBmvjGGN8tMUawVLYHY+pQxBViZLEl3DFJDZ9vRTGlGqF0ctyjC y4Q9tAv9ikLPEEg82xFHdtByo/BWOiVaxh/ouMENRIXqzuY9qHci8bUTGSyulk/Q hszP9AI+uCQfK9HBIjVOeVusdMPbKsaz67n2mzexK2xR5kCx7kbUIElwmPW+msqH UxO5N34Pa0AEOYxO78PD+uCej/X5dqc1j0SYWWU0yiYyL1Wn7qtd9wnfip4b5uNm QfySEJqZxFc0Mi0mxhNVqD7HWVadZb/mXV0KTlsm9wWT9UfUSAI= =J4+G -END PGP SIGNATURE-
Processing of ksyntax-highlighting_5.103.0-2_source.changes
ksyntax-highlighting_5.103.0-2_source.changes uploaded successfully to localhost along with the files: ksyntax-highlighting_5.103.0-2.dsc ksyntax-highlighting_5.103.0-2.debian.tar.xz ksyntax-highlighting_5.103.0-2_source.buildinfo Greetings, Your Debian queue daemon (running on host usper.debian.org)
