Bug#1031489: OpenSUSE Leap 15.4 + 340.108 + Qt 6.2.2 = ALL QT WORKING GOOD

OpenSUSE Leap 15.4 + 340.108 + Qt 6.2.2 = ALL QT WORKING GOOD https://i.imgur.com/u5WOQD0.png So its Debian issue?

Bug#1000209: Bug #1000209

Hello, I'd a look into this bug this evening and it looks like the problem was related to update-rc.d (provided by #DEBHELPER#) which is called after "invoke-rc.d timidity stop" which stops the service. It means systemd was not able to find the relevant service to stop at this moment in

Bug#1013594: insubstantial: FTBFS: Caused by: : java.lang.VerifyError: Expecting a stackmap frame at branch target 33

The laf-widget library that's part of this package generates some Java bytecode directly: . Since Java 11, additional metadata (the "stackmap

Bug#1013594: marked as done (insubstantial: FTBFS: Caused by: : java.lang.VerifyError: Expecting a stackmap frame at branch target 33)

Your message dated Fri, 03 Mar 2023 23:19:17 + with message-id and subject line Bug#1013594: fixed in insubstantial 7.3+dfsg3-5.1 has caused the Debian Bug report #1013594, regarding insubstantial: FTBFS: Caused by: : java.lang.VerifyError: Expecting a stackmap frame at branch target 33 to

Processed: severity of 1030205 is grave

Processing commands for cont...@bugs.debian.org: > severity 1030205 grave Bug #1030205 [scilab] scilab: Could not find Java package '/usr/share/java/batik-all-1.14.jar' Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. --

Processed: Bug#1031794 marked as pending in socklog

Processing control commands: > tag -1 pending Bug #1031794 [src:socklog] socklog: fails to extract source package: dpkg-source: error: pathname 'socklog-2.1.0+repack/debian/service/socklog-unix/log/supervise' points outside source root (to '/run/runit/supervise/socklog-unix.log') Added tag(s)

Bug#1031794: marked as pending in socklog

Control: tag -1 pending Hello, Bug #1031794 in socklog 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:

Bug#1023284: marked as done (libevent: FTBFS with glibc 2.36)

Your message dated Fri, 03 Mar 2023 21:49:23 + with message-id and subject line Bug#1023284: fixed in libevent 2.1.12-stable-8 has caused the Debian Bug report #1023284, regarding libevent: FTBFS with glibc 2.36 to be marked as done. This means that you claim that the problem has been dealt

Processed: Re: grub: grub-probe doesn't detect that file is on cryptfs on new installation

Processing control commands: > tag -1 upstream fixed-upstream patch Bug #1028301 [grub-common] grub: grub-probe doesn't detect that file is on cryptfs on new installation Added tag(s) patch, fixed-upstream, and upstream. -- 1028301: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1028301

Bug#1028301: grub: grub-probe doesn't detect that file is on cryptfs on new installation

Control: tag -1 upstream fixed-upstream patch On Mon, 09 Jan 2023 12:12:19 +0100 Laurent Bigonville wrote: > Package: grub-common > Version: 2.06-7 > Severity: serious > File: /usr/sbin/grub-probe > > Hello, > > On a newly installed laptop, it seems that grub-probe is not able to > detect that

Processed: Re: Bug#1032259: conky: High CPU usage

Processing control commands: > severity -1 important Bug #1032259 [src:conky] High CPU and memory usage Severity set to 'important' from 'serious' -- 1032259: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1032259 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1032259: conky: High CPU usage

Control: severity -1 important On Fri, Mar 3, 2023 at 5:48 AM Antoine Le Gonidec wrote: > > I think I can confirm that the high Xorg memory usage is due to this update, > I am now sitting at 3.30GB after a dozen hours. > > To make really sure of the cause, I am going to revert to the 1.17 build

Bug#1030284: [Pkg-javascript-devel] Bug#1030284: nodejs: [arm64] RangeError: Maximum call stack size exceeded

Hi, On Wed, Mar 01, 2023 at 02:41:05PM +0100, Jérémy Lal wrote: > For now I'm unlucky with the porterbox, because /var/run/schroot > disappeared yesterday. I can confirm that the issue isn't reproducible with V8_DEFAULT_STACK_SIZE_KB set to 984. Built and tested on a Macbook M1.

Bug#1026204: tar FTBFS on armel, armhf, i386, hppa, powerpc and sparc64

Hi, Is the issue that with older glibc versions, it was silently casted to a 32 bit value, but now that glibc supports 64 bit, it knows it can't represent it, and gives an error? Maybe for bookworm, we should just ignore the test error? Kurt

Bug#1003044: python3-dateutil: python_dateutil get_zonefile_instance functionality is broken (no zoneinfo found)

> This bug is about the warning, not about the fact that the bundled zoninfo > database is missing. not exactly even if these APIs are deprecated upstream, i think breaking them on purpose (by removing the bundled timezone file) is uncalled for. Either we reintroduce the timezone file (that may

Bug#1026508: ca-certificates: FTBFS: TypeError: argument 'data': 'bytearray' object cannot be converted to 'PyBytes'

Hi, Are you waiting for something before uploading this fix? Kurt

Bug#1023284: libevent: FTBFS with glibc 2.36

Hello, The patch was submitted upstream for their feedback [1], and was finally agreed. So I will upload a new package very soon then. /Nicolas [1] https://github.com/libevent/libevent/issues/1393#issuecomment-1453924054

Processed: tagging 1003044

Processing commands for cont...@bugs.debian.org: > tags 1003044 + patch Bug #1003044 [python3-dateutil] internal 'getzoneinfofile_stream' method emits a warning message Added tag(s) patch. > thanks Stopping processing here. Please contact me if you need assistance. -- 1003044:

Bug#1003044: python3-dateutil: python_dateutil get_zonefile_instance functionality is broken (no zoneinfo found)

 [I picked up this bug as part of a Debian bugsquashing sprint together with my colleagues.]  Since there's been some back-and-forth in this thread, let me first summarize the status. - The following will print an ugly warning: In [1]: from dateutil import zoneinfo In [2]:

Bug#1014329: marked as done (anbox: Not working after removing ashmem module)

Your message dated Fri, 03 Mar 2023 19:22:28 + with message-id and subject line Bug#1032304: Removed package(s) from unstable has caused the Debian Bug report #1014329, regarding anbox: Not working after removing ashmem module to be marked as done. This means that you claim that the problem

Bug#1023284: libevent: FTBFS with glibc 2.36

Hi, It seems a fix for this is sitting git, but hasn't been uploaded. Is there a reason it's not been uploaded yet? Kurt

Processed: severity of 987355 is grave

Processing commands for cont...@bugs.debian.org: > severity 987355 grave Bug #987355 [phpldapadmin] CVE-2020-35132 Severity set to 'grave' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 987355:

Bug#1031812: marked as done (crystal missing several dependencies)

Your message dated Fri, 03 Mar 2023 18:34:08 + with message-id and subject line Bug#1031812: fixed in crystal 1.6.0+dfsg-3 has caused the Debian Bug report #1031812, regarding crystal missing several dependencies to be marked as done. This means that you claim that the problem has been dealt

Processed: bug 1023284 is forwarded to https://github.com/libevent/libevent/issues/1393

Processing commands for cont...@bugs.debian.org: > forwarded 1023284 https://github.com/libevent/libevent/issues/1393 Bug #1023284 [src:libevent] libevent: FTBFS with glibc 2.36 Set Bug forwarded-to-address to 'https://github.com/libevent/libevent/issues/1393'. > thanks Stopping processing here.

Bug#1029010: llvm-toolchain-15: autopkgtest regression

On Fri, 03 Mar 2023 at 17:41:22 +0100, Sylvestre Ledru wrote: > Le 16/01/2023 à 16:44, Adrian Bunk a écrit : > > /usr/include/wasm32-wasi/c++/v1/__type_traits/is_array.h:40:22: error: > > reference to unresolved using declaration > > template struct _LIBCPP_TEMPLATE_VIS > > is_array<_Tp[_Np]> >

Bug#1022742: marked as done (multipath-tools: CVE-2022-41973 CVE-2022-41974)

Your message dated Fri, 03 Mar 2023 17:02:40 + with message-id and subject line Bug#1022742: fixed in multipath-tools 0.8.5-2+deb11u1 has caused the Debian Bug report #1022742, regarding multipath-tools: CVE-2022-41973 CVE-2022-41974 to be marked as done. This means that you claim that the

Bug#1029010: llvm-toolchain-15: autopkgtest regression

Hello Sorry, I missed this issue. Faidon, does it ring a bell ? Thanks Sylvestre Le 16/01/2023 à 16:44, Adrian Bunk a écrit : Source: llvm-toolchain-15 Version: 1:15.0.7-1 Severity: serious https://ci.debian.net/data/autopkgtest/testing/amd64/l/llvm-toolchain-15/30436521/log.gz ... In

Bug#1032316: llvm-toolchain-15: is this version intended for Debian 12 'bookworm'?

Source: llvm-toolchain-15 Version: 1:15.0.7-1 Severity: serious Justification: blocking RC bug fixes in Mesa from migrating X-Debbugs-Cc: debian-rele...@lists.debian.org llvm-toolchain-15/1:15.0.7-1 was uploaded several weeks ago, shortly after the transition freeze, but has not migrated to

Processed (with 1 error): Re: Bug#1031364: e2fsprogs: generates filesystems that grub-install doesn't recognize

Processing commands for cont...@bugs.debian.org: > tags 1031364 + upstream,forwarded,patch Unknown tag/s: forwarded. Recognized are: patch wontfix moreinfo unreproducible help security upstream pending confirmed ipv6 lfs d-i l10n newcomer a11y ftbfs fixed-upstream fixed fixed-in-experimental

Bug#1031364: e2fsprogs: generates filesystems that grub-install doesn't recognize

tags 1031364 + upstream,forwarded,patch thanks I have reported this bug to the upstream author as issue #69: https://gitlab.com/larswirzenius/vmdb2/-/issues/69 And proposed a simplistic patch as merge request #106: https://gitlab.com/larswirzenius/vmdb2/-/merge_requests/106 Just for

Bug#1032198: marked as done (wapiti fails to start with Python 3.11)

Your message dated Fri, 03 Mar 2023 15:06:56 + with message-id and subject line Bug#1032198: fixed in wapiti 3.0.4+dfsg-2 has caused the Debian Bug report #1032198, regarding wapiti fails to start with Python 3.11 to be marked as done. This means that you claim that the problem has been

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

Package: libgnome-desktop-4-2 Followup-For: Bug #1029821 X-Debbugs-Cc: gunna...@debian.org On Fri, 3 Mar 2023 15:10:30 +0100, Gunnar wrote: > On 2023-03-03 13:21, James Addison wrote: > > I also noticed that some of gnome-desktop's default locale-to-input-source > > mappings provide multiple

Bug#1030298: marked as done (pyopencl: FTBFS on i386: = 1 failed, 304 passed, 7 skipped, 1 deselected, 2 xfailed, 31 warnings in 736.25s (0:12:16) =)

Your message dated Fri, 03 Mar 2023 14:49:57 + with message-id and subject line Bug#1030298: fixed in pyopencl 2022.3.1-2.1 has caused the Debian Bug report #1030298, regarding pyopencl: FTBFS on i386: = 1 failed, 304 passed, 7 skipped, 1 deselected, 2 xfailed, 31 warnings in 736.25s

Bug#1032166: timeline data not shown in browser (from local install)

Hello, I have done some tests and I think that the issue is related to CORS policy of the browsers. If I install debian-timeline and I do: chromium --allow-file-access-from-files file:///usr/share/debian-timeline/index.html & I cannot see the events, but if I press F12 I can see them. So I

Bug#1031794: socklog: fails to extract source package: dpkg-source: error: pathname 'socklog-2.1.0+repack/debian/service/socklog-unix/log/supervise' points outside source root (to '/run/runit/supervis

On Wed, Feb 22, 2023 at 10:17:23PM +0100, Sven Joachim wrote: > On 2023-02-22 21:45 +0100, Lucas Nussbaum wrote: > > > Source: socklog > > Version: 2.1.0+repack-4 > > Severity: serious > > > > dpkg-source: info: extracting socklog in socklog-2.1.0+repack > > dpkg-source: info: unpacking

Bug#982794: firefox-esr: illegal instruction in libxul.so on armhf

Hi, On Sun, Feb 14, 2021 at 02:12:17PM +, Vincent Arkesteijn wrote: > Firefox is killed with SIGILL shortly after startup: > $ firefox-esr -safe-mode > Illegal instruction > $ This is due to the fact that some armhf CPUs do not have support for NEON instructions. skia used to detect such

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

On 2023-03-03 13:21, James Addison wrote: I also noticed that some of gnome-desktop's default locale-to-input-source mappings provide multiple entries, delimited by the '+' character: https://gitlab.gnome.org/GNOME/gnome-desktop/-/blob/43.2/libgnome-desktop/default-input-sources.h#L31 That's

Bug#1031763: marked as done (python3-motor asyncio broken with python3.11)

Your message dated Fri, 03 Mar 2023 13:48:59 + with message-id and subject line Bug#1031763: fixed in python-motor 2.3.0-3 has caused the Debian Bug report #1031763, regarding python3-motor asyncio broken with python3.11 to be marked as done. This means that you claim that the problem has

Processed: your mail

Processing commands for cont...@bugs.debian.org: > severity 1032259 serious Bug #1032259 [src:conky] High CPU and memory usage Severity set to 'serious' from 'important' > thanks Stopping processing here. Please contact me if you need assistance. -- 1032259:

Bug#1032041: marked as done (FTBFS: error: ‘size_t’ does not name a type)

Your message dated Fri, 03 Mar 2023 13:34:07 + with message-id and subject line Bug#1032041: fixed in arm-compute-library 20.08+dfsg-6 has caused the Debian Bug report #1032041, regarding FTBFS: error: ‘size_t’ does not name a type to be marked as done. This means that you claim that the

Processed: Bug#1031763 marked as pending in python-motor

Processing control commands: > tag -1 pending Bug #1031763 [python3-motor] python3-motor asyncio broken with python3.11 Added tag(s) pending. -- 1031763: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1031763 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems

Bug#1031763: marked as pending in python-motor

Control: tag -1 pending Hello, Bug #1031763 in python-motor 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:

Bug#1032310: marked as done (zcfan should "Conflicts: thinkfan")

Your message dated Fri, 03 Mar 2023 13:26:41 + with message-id and subject line Bug#1032310: fixed in thinkfan 1.3.1-4 has caused the Debian Bug report #1032310, regarding zcfan should "Conflicts: thinkfan" to be marked as done. This means that you claim that the problem has been dealt with.

Bug#1032255: pulseaudio: sound keeps dying (on Tiger Lake)

Package: pulseaudio Followup-For: Bug #1032255 Control: retitle -1 pulseaudio: application restart required to restore sound Control: severity -1 normal Control: tags -1 moreinfo Hi Dave, Are there any clues (error messages, service start/stops, or things like that) in the affected system's

Processed: Re: pulseaudio: sound keeps dying (on Tiger Lake)

Processing control commands: > retitle -1 pulseaudio: application restart required to restore sound Bug #1032255 [pulseaudio] pulseaudio: sound keeps dying (on Tiger Lake) Changed Bug title to 'pulseaudio: application restart required to restore sound' from 'pulseaudio: sound keeps dying (on

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

X-Debbugs-CC: s...@debian.org, z...@debian.org, ken...@xdump.org, yy.y.ja...@gmail.com, iwama...@debian.org, debian-i...@lists.debian.org, debian-japan...@lists.debian.org, m...@packages.debian.org, ibus-an...@packages.debian.org On 2023-03-03 12:52, James Addison wrote: If it's true that

Processed: reassign 1032310 to thinkfan

Processing commands for cont...@bugs.debian.org: > reassign 1032310 thinkfan Bug #1032310 [zcfan] zcfan should "Conflicts: thinkfan" Bug reassigned from package 'zcfan' to 'thinkfan'. Ignoring request to alter found versions of bug #1032310 to the same values previously set Ignoring request to

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

Package: libgnome-desktop-4-2 Followup-For: Bug #1029821 I also noticed that some of gnome-desktop's default locale-to-input-source mappings provide multiple entries, delimited by the '+' character:

Processed: cloning 1017980

Processing commands for cont...@bugs.debian.org: > clone 1017980 -1 Bug #1017980 [zcfan] zcfan should "Conflicts: thinkfan" Bug 1017980 cloned as bug 1032310 > thanks Stopping processing here. Please contact me if you need assistance. -- 1017980:

Processed: severity of 1017980 is grave

Processing commands for cont...@bugs.debian.org: > severity 1017980 grave Bug #1017980 [zcfan] zcfan should "Conflicts: thinkfan" Severity set to 'grave' from 'normal' > thanks Stopping processing here. Please contact me if you need assistance. -- 1017980:

Bug#1029821: change gnome-desktop's default choice of Japanese input methods for Debian

Package: libgnome-desktop-4-2 Followup-For: Bug #1029821 (comment to bug-thread only) If it's true that the cause is that 'tasksel' and 'gnome-initial-setup' are mismatched, then we could apply a fix in either one. Given that we have an existing patch available for 'gnome-initial-desktop', I've

Processed: bug 1032177 is forwarded to https://github.com/wolfcw/libfaketime/issues/418

Processing commands for cont...@bugs.debian.org: > forwarded 1032177 https://github.com/wolfcw/libfaketime/issues/418 Bug #1032177 [faketime] faketime doesn't fake time (on i386) Set Bug forwarded-to-address to 'https://github.com/wolfcw/libfaketime/issues/418'. > thanks Stopping processing

Bug#1018023: Update on this bug?

Hi, On 14/02/2023 18:36, Jose Antonio Jimenez Madrid wrote: I will test this patch and let you to know whether the bug is fixed. Any joy? We're approaching the time that eterm is going to be autoremoved from bookworm... Thanks, Matthew

Bug#1032300: odoo-14: Not functional with pypdf2 2.x

Package: odoo-14 Version: 14.0.0+dfsg.4-1 Severity: grave odoo 14.x is not compatible with pypdf2 2.x, and the server cannot be started: ModuleNotFoundError: No module named 'PyPDF2.utils' -- System Information: Debian Release: bookworm/sid APT prefers stable-security APT policy: (500,

Bug#1032048: marked as done (d3-dsv-tools: Dangling symlinks in /usr/bin/)

Your message dated Fri, 03 Mar 2023 08:23:24 + with message-id and subject line Bug#1032048: fixed in node-d3-dsv 1.1.1-9 has caused the Debian Bug report #1032048, regarding d3-dsv-tools: Dangling symlinks in /usr/bin/ to be marked as done. This means that you claim that the problem has

Bug#1027215: Bug#1026539: How much do we lose if we remove theano (+keras, deepnano, invesalius)?

On 03/03/2023 06:00, Andreas Tille wrote: Ahh, so aesara is not really a "fork" but a "rename"? The original is abandoned (no new development since 2017, and now mostly unmaintained, which is probably why it has this kind of bug). Aesara is a continuation by a new upstream (possibly one