Bug#1079477: plasma-mobile: FTBFS
Hi Marco, On Wed, 28 Aug 2024 18:51:23 +0200 Marco Mattiolo wrote: > Hi Patrick, > > thank you for the note. I'm answering to the shell's bug, but the > topic is similar for the other 5 bugs of the packages I'm > maintaining, as well. > > I'm quite inclined to let it broken and then fix it with the Plasma6 > upload to sid, if that will be possible in a reasonable amount of > time: without making promises, do you think it's going to be matter of > couple of weeks / a month / 2 months /... ? As a ballpark, plasma- > mobile has the same build-deps like plasma-desktop. We have 2 bugs left to fix and then we'd like to upload Plasma 6 to unstable. We also need to give users a heads-up and maintainers of reverse dependencies a final warning that stuff will break. We don't have an ETA, but it's likely a matter of 2-4 weeks. -- Med vänliga hälsningar Patrick Franz
Bug#1079483: spacebar: FTBFS
Source: spacebar Version: 23.01.0-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package currently build-depends on "kirigami-addons-dev". The version in unstable is Qt 5-based whereas a newer version in experimental is Qt 6-based and will stay Qt 6-only. Uploading said version to unstable would break all reverse dependencies. Therefore we created a new source package "kirigami-addons5" which is and will stay Qt 5-based. This package is already available in unstable. Unfortunately, by uploading kirigami-addons5 to unstable, we accidently broke kirigami-addons-dev and hence your package currently FTBFS. We are sorry for this. However, the fix for the build failure is quite trivial: Simply replace the "kirigami-addons-dev" build-dependency with "kirigami-addons5-dev". That will make your package build again. Again sorry for the inconvenience. -- Regards Patrick Franz
Bug#1079477: plasma-mobile: FTBFS
Source: plasma-mobile Version: 5.27.10-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package currently build-depends on "kirigami-addons-dev". The version in unstable is Qt 5-based whereas a newer version in experimental is Qt 6-based and will stay Qt 6-only. Uploading said version to unstable would break all reverse dependencies. Therefore we created a new source package "kirigami-addons5" which is and will stay Qt 5-based. This package is already available in unstable. Unfortunately, by uploading kirigami-addons5 to unstable, we accidently broke kirigami-addons-dev and hence your package currently FTBFS. We are sorry for this. However, the fix for the build failure is quite trivial: Simply replace the "kirigami-addons-dev" build-dependency with "kirigami-addons5-dev". That will make your package build again. Again sorry for the inconvenience. -- Regards Patrick Franz
Bug#1079480: qmlkonsole: FTBFS
Source: qmlkonsole Version: 23.08.3-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package currently build-depends on "kirigami-addons-dev". The version in unstable is Qt 5-based whereas a newer version in experimental is Qt 6-based and will stay Qt 6-only. Uploading said version to unstable would break all reverse dependencies. Therefore we created a new source package "kirigami-addons5" which is and will stay Qt 5-based. This package is already available in unstable. Unfortunately, by uploading kirigami-addons5 to unstable, we accidently broke kirigami-addons-dev and hence your package currently FTBFS. We are sorry for this. However, the fix for the build failure is quite trivial: Simply replace the "kirigami-addons-dev" build-dependency with "kirigami-addons5-dev". That will make your package build again. Again sorry for the inconvenience. -- Regards Patrick Franz
Bug#1079479: plasma-settings: FTBFS
Source: plasma-settings Version: 23.01.0-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package currently build-depends on "kirigami-addons-dev". The version in unstable is Qt 5-based whereas a newer version in experimental is Qt 6-based and will stay Qt 6-only. Uploading said version to unstable would break all reverse dependencies. Therefore we created a new source package "kirigami-addons5" which is and will stay Qt 5-based. This package is already available in unstable. Unfortunately, by uploading kirigami-addons5 to unstable, we accidently broke kirigami-addons-dev and hence your package currently FTBFS. We are sorry for this. However, the fix for the build failure is quite trivial: Simply replace the "kirigami-addons-dev" build-dependency with "kirigami-addons5-dev". That will make your package build again. Again sorry for the inconvenience. -- Regards Patrick Franz
Bug#1079478: plasma-phonebook: FTBFS
Source: plasma-phonebook Version: 23.01.0-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package currently build-depends on "kirigami-addons-dev". The version in unstable is Qt 5-based whereas a newer version in experimental is Qt 6-based and will stay Qt 6-only. Uploading said version to unstable would break all reverse dependencies. Therefore we created a new source package "kirigami-addons5" which is and will stay Qt 5-based. This package is already available in unstable. Unfortunately, by uploading kirigami-addons5 to unstable, we accidently broke kirigami-addons-dev and hence your package currently FTBFS. We are sorry for this. However, the fix for the build failure is quite trivial: Simply replace the "kirigami-addons-dev" build-dependency with "kirigami-addons5-dev". That will make your package build again. Again sorry for the inconvenience. -- Regards Patrick Franz
Bug#1079476: plasma-dialer: FTBFS
Source: plasma-dialer Version: 23.01.0-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package currently build-depends on "kirigami-addons-dev". The version in unstable is Qt 5-based whereas a newer version in experimental is Qt 6-based and will stay Qt 6-only. Uploading said version to unstable would break all reverse dependencies. Therefore we created a new source package "kirigami-addons5" which is and will stay Qt 5-based. This package is already available in unstable. Unfortunately, by uploading kirigami-addons5 to unstable, we accidently broke kirigami-addons-dev and hence your package currently FTBFS. We are sorry for this. However, the fix for the build failure is quite trivial: Simply replace the "kirigami-addons-dev" build-dependency with "kirigami-addons5-dev". That will make your package build again. Again sorry for the inconvenience. -- Regards Patrick Franz
Bug#1079472: krecorder: FTBFS
Source: krecorder Version: 23.08.3-2 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package currently build-depends on "kirigami-addons-dev". The version in unstable is Qt 5-based whereas a newer version in experimental is Qt 6-based and will stay Qt 6-only. Uploading said version to unstable would break all reverse dependencies. Therefore we created a new source package "kirigami-addons5" which is and will stay Qt 5-based. This package is already available in unstable. Unfortunately, by uploading kirigami-addons5 to unstable, we accidently broke kirigami-addons-dev and hence your package currently FTBFS. We are sorry for this. However, the fix for the build failure is quite trivial: Simply replace the "kirigami-addons-dev" build-dependency with "kirigami-addons5-dev". That will make your package build again. Again sorry for the inconvenience. -- Regards Patrick Franz
Bug#1079470: kasts: FTBFS
Source: kasts Version: 23.08.4-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package currently build-depends on "kirigami-addons-dev". The version in unstable is Qt 5-based whereas a newer version in experimental is Qt 6-based and will stay Qt 6-only. Uploading said version to unstable would break all reverse dependencies. Therefore we created a new source package "kirigami-addons5" which is and will stay Qt 5-based. This package is already available in unstable. Unfortunately, by uploading kirigami-addons5 to unstable, we accidently broke kirigami-addons-dev and hence your package currently FTBFS. We are sorry for this. However, the fix for the build failure is quite trivial: Simply replace the "kirigami-addons-dev" build-dependency with "kirigami-addons5-dev". That will make your package build again. Again sorry for the inconvenience. -- Regards Patrick Franz
Bug#1079471: kclock: FTBFS
Source: kclock Version: 23.08.0-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package currently build-depends on "kirigami-addons-dev". The version in unstable is Qt 5-based whereas a newer version in experimental is Qt 6-based and will stay Qt 6-only. Uploading said version to unstable would break all reverse dependencies. Therefore we created a new source package "kirigami-addons5" which is and will stay Qt 5-based. This package is already available in unstable. Unfortunately, by uploading kirigami-addons5 to unstable, we accidently broke kirigami-addons-dev and hence your package currently FTBFS. We are sorry for this. However, the fix for the build failure is quite trivial: Simply replace the "kirigami-addons-dev" build-dependency with "kirigami-addons5-dev". That will make your package build again. Again sorry for the inconvenience. -- Regards Patrick Franz
Bug#1079469: angelfish: FTBFS
Source: angelfish Version: 23.04.3-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package currently build-depends on "kirigami-addons-dev". The version in unstable is Qt 5-based whereas a newer version in experimental is Qt 6-based and will stay Qt 6-only. Uploading said version to unstable would break all reverse dependencies. Therefore we created a new source package "kirigami-addons5" which is and will stay Qt 5-based. This package is already available in unstable. Unfortunately, by uploading kirigami-addons5 to unstable, we accidently broke kirigami-addons-dev and hence your package currently FTBFS. We are sorry for this. However, the fix for the build failure is quite trivial: Simply replace the "kirigami-addons-dev" build-dependency with "kirigami-addons5-dev". That will make your package build again. Again sorry for the inconvenience. -- Regards Patrick Franz
Bug#1079468: alligator: FTBFS
Package: alligator Version: alligator Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package currently build-depends on "kirigami-addons-dev". The version in unstable is Qt 5-based whereas a newer version in experimental is Qt 6-based and will stay Qt 6-only. Uploading said version to unstable would break all reverse dependencies. Therefore we created a new source package "kirigami-addons5" which is and will stay Qt 5-based. This package is already available in unstable. Unfortunately, by uploading kirigami-addons5 to unstable, we accidently broke kirigami-addons-dev and hence your package currently FTBFS. We are sorry for this. However, the fix for the build failure is quite trivial: Simply replace the "kirigami-addons-dev" build-dependency with "kirigami-addons5-dev". That will make your package build again. Again sorry for the inconvenience. -- Regards Patrick Franz
Bug#1076729: libwayland: breaks plasma desktop start after last upgrade to version 1.23.0-1
Hi, On Wed, 24 Jul 2024 18:22:02 + Jaycee Santos wrote: > According to [1], rebuilding kwin fixes the issue. > Will the auto-kwayland transition[2] handle this? No, that transition is something else. -- Med vänliga hälsningar Patrick Franz
Bug#1074633: qt6-base: upgrading libqt6core6t64 removes qpdfview and wireshark instead of upgrading them
Hej Vincent, Am Mittwoch, 3. Juli 2024, 01:02:28 CEST schrieb Vincent Lefevre: [...] > In particular, "apt install libqt6core6t64" wants to remove > qt6-wayland, but if I try "apt install libqt6core6t64 qt6-wayland", > then the upgrade is fine. So there seems to be really something > wrong with the Qt package relationships. The dependencies of Qt are fine, you just ended up in an unfortunate situation that makes it look as if the dependencies in Qt are wrong. The upgrade from Qt 6.4 to 6.6 involves a number of Break+Replaces, but that doesn't mean anything is wrong. In your first example, you only wanted to upgrade libqt6core6t64. The thing here is that there are multiple solutions about what to do with the reverse dependencies. Some solutions remove a lot of them and install as little as possible, others replace a bunch of libs and remove fewer packages. You asked apt to upgrade libqt6core6t64 and that is exactly what apt did. The issue is that the proposed solution is correct, but it's just not your preferred one. In your second example, removing all those libraries without replacing them is not a viable option, because that would make wireshark uninstallable. Therefore, apt installs a number of libs to satisfy the dependencies of wireshark. So in both cases, apt proposes a solution that does exactly what you asked it for. In the first example, there are multiple solutions and apt happened to pick one that you don't want. Why it picked that one and not another one, I do not know. Maybe it found this solution quicker. But all that doesn't mean that the dependencies in Qt are wrong. In fact, all the libs that apt wants to remove are not compatible with libqt6core6t64 6.6.2 and therefore removing them is correct. I absolutely do not see that this is a problem with Qt's dependencies. It's just that apt gives you a correct solution that you don't like and hence have to adjust the upgrade command slightly. But nothing is wrong with Qt's dependencies. You can either close this bug or you can re-assign the bug to apt and turn it into a wishlist item suggesting that apt give you more than 1 solution in such cases. -- Med vänliga hälsningar Patrick Franz
Bug#1074633: qt6-base: upgrading libqt6core6t64 removes qpdfview and wireshark instead of upgrading them
Hi Vincent, this seems more a problem of apt than of Qt. For some reason, apt is not able to resolve the dependencies when you only want to upgrade libqt6core6t64, but is able to do so when you want to upgrade libqt6core6t64 and wireshark. To me, that means that the dependencies in Qt are correct (that it wants to replace some libqt6...t64 packages with non-t64 versions is the correct solution). Have you tried upgrading just libqt6core6t64 with aptitude ? I'm inclined to reassign this bug to apt as the dependencies can clearly be resolved and IMO this is down to the resolver. -- Med vänliga hälsningar Patrick Franz
debian-bugs-rc@lists.debian.org
Hi, On Tue, 2 Jul 2024 19:39:27 +0200 Marco Mattiolo wrote: > Hi Santiago, > > I'm the maintainer of plasma-mobile package in Debian, plus some of > the related apps. At the moment, the present bug keeps meta-plasma- > mobile metapackage out of trixie, thus letting the building of Mobian > plasma-mobile images to fail [1]. As I wrote in the previous message, > looking into buildd and reproducible-builds, I thought this to be > solved, but from your attachment I see I shouldn't have assumed. > > I'm not the maintainer of wacomtablet, so I'm not sure what to touch > if tests are still failing. I see in your attachment that the error > message is always the same as in the original report, then I'd try > e.g. [2] that I see is not implemented in d/rules for wacomtablet, > but maybe it's just better to wait for the new version of wacomtablet > (6.1.0-1 now in experimental) to be uploaded to sid and check how that > new version behaves. I don't have the resources to dig into why the tests are failing, but I could disable them for the time being if wacomtablet is a blocker for something right now. We will definitely revisit this once the new version in exp (now part of Plasma 6) can be compiled there. -- Med vänliga hälsningar Patrick Franz
Bug#1073480: zstdTargets.cmake: missing targets zstd::libzstd_shared, zstd::libzstd_static, zstd::libzstd
Hi, On Thu, 27 Jun 2024 11:01:44 +0900 yokota wrote: > Hello, > > I think this bug is not a libzstd's bug but qt6-base's bug. > > Please check this QTBUG. > > [#QTBUG-119469] Targets not yet defined: zstd::libzstd_static > > https://bugreports.qt.io/browse/QTBUG-119469 > > The QTBUG said this bug was fixed in Qt 6.7.2, so update Qt to 6.7.2 > will fixes the problem. > > Or, back port QTBUG-119469 fix from git commits. > https://code.qt.io/cgit/qt/qtbase.git/log/?qt=grep&q=QTBUG-119469 > > PS: > Arch Linux also have this bug. > > https://gitlab.archlinux.org/archlinux/packaging/packages/qt6-doc/-/ issues/1 Backporting these commits does not solve the issue for me. Maybe I am doing something wrong, but I still get the error in qt6-tools. If anybody else wants to take a crack a it, go ahead. Because I cannot spend any more time on this. Short of updating Qt to 6.7.2 or completely disabling zstd support in Qt, I'm kinda out of options. I cannot judge the consequence of removing zstd support and updating Qt will take several weeks at least. -- Med vänliga hälsningar Patrick Franz
Bug#1074264: marked as pending in kdecoration
Control: tag -1 pending Hello, Bug #1074264 in kdecoration reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/kde/kdecoration/-/commit/7732fcfd78ad10402ad8a60b302db7aac300e558 Add missing Breaks+Replaces for libkdecorations2-6 against libkdecorations2-5v5 (Closes: #1074264). (this message was generated automatically) -- Greetings https://bugs.debian.org/1074264
Bug#1074165: marked as pending in kscreenlocker
Control: tag -1 pending Hello, Bug #1074165 in kscreenlocker reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/kde/kscreenlocker/-/commit/162ac2ad16ae8167a59793dcf8921898788f846c Add missing Breaks+Replaces for libkscreenlocker6 against libkscreenlocker5 (Closes: #1074165). (this message was generated automatically) -- Greetings https://bugs.debian.org/1074165
Bug#1074227: goldencheetah: Unsatisfiable build-dependencies
Package: goldencheetah Version: 1:3.5-5 Severity: serious X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package has unsatisfiable build-dependencies, specifically libqt5widgets5 and libqt5concurrent5. These packages have been superseded by libqt5widgets5t64 and libqt5concurrent5t64 respectively. Build-depending on them is neither necessary nor recommended as the corresponding packages are pulled automatically by qtbase5-dev. -- Regards Patrick Franz
Bug#1074226: sonic-visualiser: FTBFS on armel/armhf
Package: sonic-visualiser Version: 4.5.2-2 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package FTBFS on armel/armhf is therefore stuck on unsatisfiable dependencies. See https://buildd.debian.org/status/fetch.php?pkg=sonic-visualiser&arch=armel&ver=4.5.2-2%2Bb3&stamp=1713251413&raw=0 and https://buildd.debian.org/status/fetch.php?pkg=sonic-visualiser&arch=armhf&ver=4.5.2-2%2Bb3&stamp=1713249425&raw=0 -- Regards Patrick Franz
Bug#1026957: (no subject)
Hi, I'm raising the severity to serious as the explicit dependency to libqt6core6 causes the package to have unsatisfiable dependencies. The package libqt6core6 has been superseded by libqt6core6t64. And as already mentioned, these explicit dependencies to the Qt libraries should not be needed. -- Med vänliga hälsningar Patrick Franz
Bug#1074221: morph-browser: FTBFS on mips64el
Package: morph-browser Version: 1.1.0+dfsg-2 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package fails to build on mips64el and can therefore not migrate to testing. See https://buildd.debian.org/status/fetch.php?pkg=morph-browser&arch=mips64el&ver=1.1.0%2Bdfsg-2&stamp=1716667926&raw=0 -- Regards Patrick Franz
Bug#1074219: eln: Build-Depends on unsatisfiable dependencies on armel/mips64el/ppc64el/s390x
Package: eln Version: 1.5.4-1 Severity: serious X-Debbugs-Cc: delta...@debian.org Dear Maintainer, your package build-depends on qt6-pdf-dev, qml6-module-qtwebengine-controlsdelegates and qml6-module-qtwebengine on armel/mips64el/ppc64el/s390x. However, these packages only exist on amd64/arm64/armhf/i386. This prevents the packages from being built on these architectures and thus from migrating to testing. -- Regards Patrick Franz
Bug#1074218: dogecoin: FTBFS because of symbol errors
Package: dogecoin Version: 1.14.7-1 Severity: serious Tags: ftbfs X-Debbugs-Cc: delta...@debian.org Dear Maintainer, the package FTBFS on amd64 due to symbol errors. See https://buildd.debian.org/status/fetch.php?pkg=dogecoin&arch=amd64&ver=1.14.7-1&stamp=1716846348&raw=0 -- Regards Patrick Franz
Bug#1074071: marked as pending in libkscreen
Control: tag -1 pending Hello, Bug #1074071 in libkscreen reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/kde/libkscreen/-/commit/db2b3255dd90db720fbb5512dc195394327ebf9e Add missing Breaks+Replaces for libkf6screen-bin against libkf5screen-bin (Closes: #1074071). (this message was generated automatically) -- Greetings https://bugs.debian.org/1074071
Bug#1073394: ktextaddons: FTBFS: unsatisfiable build-dependencies: libkf6archive-dev (>= 6.0.0~), libkf6configwidgets-dev (>= 6.0.0~), libkf6coreaddons-dev (>= 6.0.0~), libkf6i18n-dev (>= 6.0.0~), lib
Hi, the package was accidentally uploaded to unstable instead of experimental and therefore has unsatisfiable build-dependencies. This will be solved once the KDE Frameworks 6 are uploaded to unstable. But since ktextaddons currently does not have any reverse dependencies in Debian, I'll leave it at that. -- Med vänliga hälsningar Patrick Franz
Bug#998197: kdeconnectd: should not listen on all interfaces by default
Control: severity -1 important Hi Witold, On Tue, 07 May 2024 02:36:46 + Witold Baryluk wrote: [...] > Elevating severity, because it looks like I didn't even installed this > package (I did inspect all apt-get install invokations since system > creation), and it kdeconnect could only be installed due to some > suggests / recommends, not due to any dependency or direct request. How the package was installed on your system, I don't know, but as you suspect it was likely a recommendation of another package. Regarding the issue at hand: I can see why you consider this a problem. But unfortunately, there is no way of changing that behaviour, I suspect the behaviour might be intentional. People have requested this feature upstream (https:// bugs.kde.org/show_bug.cgi?id=432378) and even asked for ways to disable kdeconnectd (https://bugs.kde.org/show_bug.cgi?id=417615). The latter bug report could give you ideas how to achieve that. If this issue poses a serious problem for you, you can remove kdeconnect from your system. That might also give you a hint why it was installed in the first place. Upstream KDE actually recommends installing kdeconnect as part of the Plasma installation. Whether that recommendation fits the Debian's recommendation, is yet to be determined and we might have to see over the recommendation. However, I do disagree about the severity of this. I don't think that this issue warrants the removal of kdeconnect from Debian and hence, I'm lowering it to important. -- Med vänliga hälsningar Patrick Franz
Bug#1070254: ktp-text-ui FTBFS: undefined reference to `snappy::RawCompress(char const*, unsigned long, char*, unsigned long*)'
Hej, Am Donnerstag, 2. Mai 2024, 15:24:07 CEST schrieb Helmut Grohne: > Source: ktp-text-ui > Version: 22.12.3-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in > the past) > > ktp-text-ui fails to build from source in unstable on amd64. The [...] > | /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.15.10 /usr/bin/ld: > | /usr/lib/x86_64-linux-gnu/libQt5WebEngineCore.so.5.15.15: undefined > | reference to `snappy::RawCompress(char const*, unsigned long, > | char*, unsigned long*)' collect2: error: ld returned 1 exit status That looks like it's https://bugs.debian.org/cgi-bin/bugreport.cgi? bug=1070254 for which a fix has been uploaded. I guess trying to rebuild it tomorrow will fix this build error. -- Med vänliga hälsningar Patrick Franz
Bug#1067657: marked as pending in frameworkintegration
Control: tag -1 pending Hello, Bug #1067657 in frameworkintegration reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/kde/frameworkintegration/-/commit/04bff0539332af222a4b818c9caf0eab9f5f35c6 Depend on libqt5widgets5t64 instead of libqt5widgets5 (Closes: #1067657). (this message was generated automatically) -- Greetings https://bugs.debian.org/1067657
Bug#1000115: marked as pending in kjs
Control: tag -1 pending Hello, Bug #1000115 in kjs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/kde/kjs/-/commit/8feb0197184521eb7c6952af95d7abe5812f22e8 Port to PCRE2, thx to Yavor Doganov (Closes: #1000112, #1000115). (this message was generated automatically) -- Greetings https://bugs.debian.org/1000115
Bug#1000112: marked as pending in kjs
Control: tag -1 pending Hello, Bug #1000112 in kjs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/kde/kjs/-/commit/8feb0197184521eb7c6952af95d7abe5812f22e8 Port to PCRE2, thx to Yavor Doganov (Closes: #1000112, #1000115). (this message was generated automatically) -- Greetings https://bugs.debian.org/1000112
Bug#1061205: Please upgrade to llvm-toolchain-17
Hi, I have a patch that makes qt6-tools build with llvm-toolchain-17. However, qt6-tools in affected by the ongoing 64bit time_t transition and I don't want to interfere with that. I can upload the patch once qt6-tools has been uploaded to unstable for the transition. -- Med vänliga hälsningar Patrick Franz
Bug#1042018: qt6-declarative: FTBFS on hppa - Segmentation fault in /usr/lib/qt6/bin/qsb
severity -1 normal thanks Hi, since hppa is not an officially supported architecture, I'm downgrading the severity. Due to the lack of resources, it's unlikely we'll even investigate this. However, if you have a patch, I'm happy to apply it. -- Med vänliga hälsningar Patrick Franz
Bug#1035732: libkscreenlocker5: Endless loop when using PAM
Hi Andreas, On Mon, 8 May 2023 14:15:17 +0200 "Poenicke, Andreas (TKM)" wrote: > Package: libkscreenlocker5 > Version: 5.20.5-1 > Severity: critical > Tags: patch upstream > Justification: breaks the whole system [...] > Please include the short patch > https://invent.kde.org/plasma/kscreenlocker/-/commit/fca315cf72826f93eda7a026016b33818b9d1f39 > to kscreenlocker-5.20.5 in bullseye. Thanks for reporting this. I have applied the patch onto the version in bullseye and uploaded it here: https://people.debian.org/~deltaone/kscreenlocker/ Could be so kind and install it ? If you can confirm it fixes your issue, I'll prepare the upload for stable. -- Med vänliga hälsningar Patrick Franz
Bug#1032240: akonadi server fails to start since it cannot connect to mysql database
Hi, the issue is connected to MariaDB when upgrading after the shutdown was not clean, see https://bugs.debian.org/cgi-bin/bugreport.cgi? bug=1032047#40 We are trying to find a solution for this. -- Med vänliga hälsningar Patrick Franz
Bug#1027474: marked as pending in qbs
Control: tag -1 pending Hello, Bug #1027474 in qbs reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/qt/qbs/-/commit/94c6a1ac0a137fc74c39904c03f21b920ca5ee7e Update symbols from buildlogs (Closes: #1027474). (this message was generated automatically) -- Greetings https://bugs.debian.org/1027474
Bug#1000955: libkf5globalaccel-bin: /usr/bin/kglobalaccel5 eats up huge amount of CPU after suspend
Hi Filippo, I have noticed a similar behaviour. However, the behaviour has improved significantly (at least for me) and in recent versions of libkf5globalaccel-bin the CPU bursts after connecting e.g. a mouse with a USB connector are only relatively short (a couple of seconds maybe depending on your machine). Could you try to run a recent KDE stack with testing or unstable and see if the issue is still as bad ? For some people, the issue was apparently caused by ~/.Xmodmap. Can you check whether you have such a file ? Thank you. -- Med vänliga hälsningar Patrick Franz
Bug#1019712: marked as pending in zanshin
Control: tag -1 pending Hello, Bug #1019712 in zanshin reported by you has been fixed in the Git repository and is awaiting an upload. You can see the commit message below and you can check the diff of the fix at: https://salsa.debian.org/qt-kde-team/kde/zanshin/-/commit/318e97a7575956907c7f43e80178b12043686815 New upstream release (Closes: #1019712). (this message was generated automatically) -- Greetings https://bugs.debian.org/1019712
Bug#1017591: libkf5service5: missing symbols in library
control: severity -1 important Hi Oswald, On Thu, 18 Aug 2022 07:04:32 +0200 Oswald Buddenhagen wrote: > Package: libkf5service5 > Version: 5.97.0-1 > Severity: grave > Justification: renders package unusable > > /usr/bin/startplasma-x11: symbol lookup error: /usr/lib/x86_64-linux- gnu/libKF5Service.so.5: undefined symbol: _ZN8KSandbox9isFlatpakEv That looks like as if you're using an old version of libkf5coreaddons5 (5.95 or older). Have you compiled that on your own and loaded that one instead ? Can you please post the output of "ldd -r /usr/lib/x86_64-linux-gnu/ libKF5Service.so.5" ? -- Med vänliga hälsningar Patrick Franz
Bug#1014022: kalendar segfaults immediately on start
Control: severity -1 important Control: reassign -1 akonadi thanks Hi, I cannot reproduce this. When I start kalendar with a fresh user on a default installation, it starts as expected for me. Looking at the output, it seems like an akonadiserver issue rather than a kalendar issue, reassigning it therefore. -- Med vänliga hälsningar Patrick Franz
Bug#1002721: okular: segfaults when trying to open a signed PDF
Control: 1002721 severity important thanks Hi Pablo, can you point to a PDF document available on the web that causes Okular to segfault for you such that I can try to reproduce it ? -- Med vänliga hälsningar Patrick Franz
Bug#998205: plasma-desktop: unable to log into Plasma desktop
Hi Gary, KDE Plasma is currently broken in testing. Do you have a mixed Plasma, e.g. some packages from 5.21.5 and some from 5.23.0 ? If yes, then please see the following bug report: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996726 -- Med vänliga hälsningar Patrick Franz
Bug#996761: kwin-x11: KWin crashes and doesn't start
Hi, I assume you're using testing. Unfortunately, Plasma is broken in testing at the moment if you have upgraded libkdecorations2-5v5 to 5.23. Could you check that ? If this is the case, I wrote about a possible solution here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=996726#10 -- Med vänliga hälsningar Patrick Franz
Bug#993071: kmail: symbol lookup error: /lib/x86_64-linux-gnu/libKF5Libkleo.so.5: undefined symbol: _ZN5GpgME6UserID9SignatureltERKS1_
Hi Johannes, I cannot reproduce the issue on an up-to-date unstable. kmail starts as expected. Do you maybe still have an older version of some package running that causes the error ? -- Med vänliga hälsningar Patrick Franz
Bug#911067: chromium: Conflict with chrome-gnome-shell /etc/chromium
Hi On Mon, 15 Oct 2018 12:28:05 +0200 wrote: > Package: chromium > Version: 70.0.3538.54-1 > Severity: serious > Justification: Policy 10.7.4 > > dpkg: erreur de traitement de l'archive /var/cache/apt/archives/ chromium_70.0.3538.54-2_amd64.deb (--unpack) : > tentative de remplacement du répertoire « /etc/chromium » dans le paquet chrome-gnome-shell 10.1-1 avec un élément de type différent In my case, it conflicts with plasma-browser-integration, but I think it's the same error: dpkg: Fehler beim Bearbeiten des Archivs /var/cache/apt/archives/ chromium_70.0.3538.54-2_amd64.deb (--unpack): Versuch, Verzeichnis »/etc/chromium« in Paket plasma-browser- integration 5.13.5-1 mit Nichtverzeichnis zu überschreiben Essentially it says, that it tries to override /etc/chromium in the package plasma-browser-integration with a "non-directory". -- Med vänliga hälsningar Patrick Franz
