Bug#1069495: wacomtablet: FTBFS on armhf: dh_auto_test: error: cd obj-arm-linux-gnueabihf
Hi Patrick, I do not want to put too much burden on the Qt/KDE team. I've seen in the past weeks Qt6, then KF6 and now Plasma6 steadily being packaged and uploaded into experimental, making it easier and easier for me to test the plasma-mobile_6.x packaging. I know it's a big effort, so big thank you for that! When you estimate it being matter of one month or less, I definitely prefer to have Mobian plasma-mobile weekly images' building to fail for a few weeks more (users still have the pre-time64-migration images available, then they can upgrade from there) and let you continue with Plasma6 packaging, in order to get plasma-mobile_6.x available sooner for Mobian users. Kind regards Marco Il 02/07/24 22:48, Patrick Franz ha scritto: 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.
Bug#1069495: wacomtablet: FTBFS on armhf: dh_auto_test: error: cd obj-arm-linux-gnueabihf && make -j4 test ARGS\+=--verbose ARGS\+=-j4 returned exit code 2
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. Kind regards Marco [1] https://salsa.debian.org/Mobian-team/mobian-recipes/-/jobs/5907189/raw [2] https://superuser.com/questions/1694496/qt5s-qpa-can-not-connect-to-my-display Il 01/07/24 17:45, Santiago Vila ha scritto: retitle 1069495 wacomtablet: FTBFS: failing tests thanks [ Please always Cc: the bug submitter, the BTS does not forward messages sent to the bug address to the bug submitter by default ]. El 28/6/24 a las 19:26, Marco Mattiolo escribió: that looks more an issue with Qt (and xorg?). Is this still failing to build for you or shall we close this? I can reproduce this on m6a.large and r6a.large instances from AWS, but randomly. (See attach). The test which fails is not always the same. If you need an instance to reproduce this, please contact me privately. Thanks.
Bug#1069495: wacomtablet: FTBFS on armhf: dh_auto_test: error: cd obj-arm-linux-gnueabihf && make -j4 test ARGS\+=--verbose ARGS\+=-j4 returned exit code 2
Hi, this bug seems not to have been seen in the reproducible-builds [1] or in the buildd [2] projects. The FTBFS is related to a failing test 9: qt.qpa.xcb: could not connect to display :99 9: qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. 9: This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. 9: 9: Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. 9: 9/22 Test #9: Test.Common.PropertySet ..Subprocess aborted***Exception: 0.02 sec qt.qpa.xcb: could not connect to display :99 qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found. This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem. Available platform plugins are: eglfs, linuxfb, minimal, minimalegl, offscreen, vnc, xcb. that looks more an issue with Qt (and xorg?). Is this still failing to build for you or shall we close this? Thank you Marco [1]https://tests.reproducible-builds.org/debian/history/armhf/wacomtablet.html [2]https://buildd.debian.org/status/fetch.php?pkg=wacomtablet=armhf=3.2.0-5%2Bb1=1711193918=0
Bug#1042967: nheko crashes on first launch in arm64 (librem 5)
Hi, as I've just reported in the upstream issue, I've tested there's an upstream commit fixing this issue. Please note (mainly for Hubert): the commit does not apply cleanly on top of 0.11.3 due to other upstream changes to CMakeLists.txt, then you will have to rework the patch a bit. Kind regards Marco
Bug#1034310: Upstream issue
Hi Rainer, I'm not Digikam's maintainer, then maybe not the help you were looking for. But I noticed your bug report looks same as an issue reported upstream [1] on a different platform: if those issues are really the same, then it's not Debian-specific bug. I would suggest following developer's indication in the linked bug report, both trying a newer version and collecting backtrace. In the end, all of that will be useful for developers to find out what is going wrong and for Debian maintainers to cherry-pick a fix into stable release. Kind regards Marco [1] https://bugs.kde.org/show_bug.cgi?id=466170
Bug#1033212: Fwd: plasma-mobile fails to start on PP after kwin's commit eef9bd5c with "libkwinglutils: Shaders are not supported"
Prepared the patch to be included in order to fix this [1] and built patched kwin myself to confirm this solves the issue. Marco [1] https://salsa.debian.org/qt-kde-team/kde/kwin/-/merge_requests/6
Bug#1031379: kaffeine: does not work
Hi, I am not the package maintainer, but this bug report is almost useless. What's the issue? Is kaffeine not starting? Is it crashing? Or is just not showing what you expect? Which kind of DVB device are you using? Have you checked the device to work with other apps? Before flagging this bug report as "grave" (i.e. unusable app), have you checked if kaffeine is able to play local media? Imo, this is more "important" severity... Kind regards Marco
Bug#1026159: okular: Bogus memory allocation size error - some pages not displayed
Hi, I am not the package's maintainer and maybe I am not so much into the topic, but this bug report is barely understandable: what is being reported? Is this package failing to build from source? How is it being built? What's the error message? Or is this about okular failing to display some pages of a specific PDF document? On which okular version? Does this deserve a serious severity? If you are facing two issues, please file two separate bug reports... Kind regards Marco
Bug#764322: Looks like it's not done
Hi, I'm dist-upgrading in jessie: # apt-get dist-upgrade Lettura elenco dei pacchetti... Fatto Generazione albero delle dipendenze Lettura informazioni sullo stato... Fatto Calcolo dell'aggiornamento... Eseguito I seguenti pacchetti NUOVI saranno installati: libjpeg9 I seguenti pacchetti saranno aggiornati: libjpeg-progs 1 aggiornati, 1 installati, 0 da rimuovere e 0 non aggiornati. È necessario scaricare 0 B/204 kB di archivi. Dopo quest'operazione, verranno occupati 460 kB di spazio su disco. Continuare? [S/n] Lettura dei changelog... Fatto Selezionato il pacchetto libjpeg9:amd64 non precedentemente selezionato. (Lettura del database... 201773 file e directory attualmente installati.) Preparativi per estrarre .../libjpeg9_1%3a9a-2_amd64.deb... Estrazione di libjpeg9:amd64 (1:9a-2)... Preparativi per estrarre .../libjpeg-progs_1%3a9a-2_amd64.deb... Estrazione di libjpeg-progs (1:9a-2) su (1:1.3.1-3)... dpkg: errore nell'elaborare l'archivio /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb (--unpack): tentata sovrascrittura di /usr/share/man/man1/djpeg.1.gz presente anche nel pacchetto libjpeg-turbo-progs 1:1.3.1-3 Elaborazione dei trigger per man-db (2.7.0.2-1)... Si sono verificati degli errori nell'elaborazione: /var/cache/apt/archives/libjpeg-progs_1%3a9a-2_amd64.deb E: Sub-process /usr/bin/dpkg returned an error code (1) -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#611794: Thank you
The live-build 2.0.12-2 version in unstable repos fixed this for me. Thank you -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
