Processing of kf6-kservice_6.0.0-1_amd64.changes
kf6-kservice_6.0.0-1_amd64.changes uploaded successfully to localhost along with the files: kf6-kservice_6.0.0-1.dsc kf6-kservice_6.0.0.orig.tar.xz kf6-kservice_6.0.0.orig.tar.xz.asc kf6-kservice_6.0.0-1.debian.tar.xz kf6-kservice_6.0.0-1_amd64.buildinfo libkf6service-bin-dbgsym_6.0.0-1_amd64.deb libkf6service-bin_6.0.0-1_amd64.deb libkf6service-data_6.0.0-1_all.deb libkf6service-dev_6.0.0-1_amd64.deb libkf6service-doc_6.0.0-1_all.deb libkf6service6-dbgsym_6.0.0-1_amd64.deb libkf6service6_6.0.0-1_amd64.deb Greetings, Your Debian queue daemon (running on host usper.debian.org)
kf6-kservice_6.0.0-1_amd64.changes is NEW
binary:libkf6service-bin is NEW. binary:libkf6service-data is NEW. binary:libkf6service-dev is NEW. binary:libkf6service-doc is NEW. binary:libkf6service6 is NEW. binary:libkf6service-bin is NEW. binary:libkf6service-data is NEW. binary:libkf6service-dev is NEW. binary:libkf6service-doc is NEW. binary:libkf6service6 is NEW. source:kf6-kservice is NEW. Your package has been put into the NEW queue, which requires manual action from the ftpteam to process. The upload was otherwise valid (it had a good OpenPGP signature and file hashes are valid), so please be patient. Packages are routinely processed through to the archive, and do feel free to browse the NEW queue[1]. If there is an issue with the upload, you will receive an email from a member of the ftpteam. If you have any questions, you may reply to this email. [1]: https://ftp-master.debian.org/new.html or https://ftp-master.debian.org/backports-new.html for *-backports pgp9c15xnso6I.pgp Description: PGP signature
Processed: Re: Bug#1068833: discover: A game installed via Discover doesn't start
Processing control commands: > reassign -1 plasma-discover 5.27.5-2 Bug #1068833 [discover] discover: A game installed via Discover doesn't start Bug reassigned from package 'discover' to 'plasma-discover'. No longer marked as found in versions discover/2.1.2-10. Ignoring request to alter fixed versions of bug #1068833 to the same values previously set Bug #1068833 [plasma-discover] discover: A game installed via Discover doesn't start Marked as found in versions plasma-discover/5.27.5-2. -- 1068833: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1068833 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Processed: block 1036884 with 1068078
Processing commands for cont...@bugs.debian.org: > block 1036884 with 1068078 Bug #1036884 [release.debian.org] transition: time64_t 1036884 was blocked by: 1065787 1068325 1067288 1065940 1067171 1055352 1067829 1068160 1067494 1067509 1055530 1066328 1067676 1066794 1066134 1067192 1067916 1065816 1067170 1068068 1067508 1067272 1065790 1065973 1066049 1065725 1067189 1067190 1067069 1067458 1067193 1068586 1067677 1068327 1067175 1062847 1067561 1036884 was not blocking any bugs. Added blocking bug(s) of 1036884: 1068078 > thanks Stopping processing here. Please contact me if you need assistance. -- 1036884: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1036884 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems
Bug#1068829: Disabling the autostart of KDE Connect and screenreader KAccessible
Package: kde-plasma-desktop Version: 5:142 These aren't needed for most users and are a privacy and security risk. In principle, it makes sense to only autostart things one actually needs to reduce the likelihood of crashes, the number of irrelevant log entries, the hardware resource consumption, and the attack surface (for example due to potential vulnerabilities in any of the software, especially if they constantly listen on some port). Many people are looking for ways to disable these autostarts and don't like that they're just enabled by default, see for example https://unix.stackexchange.com/questions/384306/why-does-kdeconnect-listen-on-port-1716-tcp-all-the-time-how-to-close-the-port and https://discuss.kde.org/t/how-to-disable-kde-connect/7686/3 (there two devs clarified that this is not a KDE issue but "a distribution issue" which is why I'm filing it here). I thought Debian was a distro with great regard for security and stability and that it considers privacy and actual user needs/practices. A major issue with these autostarts is that there is no proper way to disable them. See https://unix.stackexchange.com/questions/774190/how-to-permanently-disable-autostarting-of-applications-on-linux-debian These methods do not only require time and are inconvenient (it's not even clear which one to use), they also get reset when the packages get upgraded such as during a distro upgrade. KDE Connect constantly listens on some ports and according to the second link has been a known vector for a DOS attack. I think "Calendar Reminders", screenreader "Orca", and "geoclue-2.0" also should not autostart but this issue is only about wireless file/device sharing app KDE Connection and KDE Accessible. I don't think these autostarts were enabled to give people a reason to get educated on autostarts and autostart-prevention and to harden these two apps. If that's why they were automatically starting by default so far, then they should still be disabled now. If needed, the user could be asked if they want to have these autostart during initial installation. Rather than bundling security-reducing bloat autostarts, I suggest that if these are installed by default at all, they are not configured to autostart. The user can easily configure them to autostart if they actually want that in the "Autostart" settings.
