Bug#1063757:

Could you please also capture the value in /sys/devices/system/cpu/intel_pstate/turbo_pct when you reproduced the issue?

Bug#1063757:

In that case can you please modify the daemon's systemd unit to run the daemon with -vv in the ExecStart command then share the unit's journal output from a boot this occurs to better understand it?

Bug#1063757:

Can this still reproduce using power-profiles-daemon 0.21-1? It's available in unstable. If so, can you please check the value of "/sys/devices/system/cpu/intel_pstate/no_turbo" at the time of the problem? If the kernel doesn't advertise turbo support then power-profiles-daemon can't do

Bug#1064659: (no subject)

Thanks! But we can go a step farther.  We haven't needed it since switching to meson.  Will drop in the next upload. https://salsa.debian.org/efi-team/fwupd/-/commit/e57b1114f8c0299eb6e2b68e2a14ef3e2ff0f0d3

Bug#1027486: (no subject)

Can you still reproduce this with fwupd 1.9.15-2?  I believe it should be fixed now.

Bug#1062820: (no subject)

This will be fixed in the next upload by this change. https://salsa.debian.org/efi-team/fwupd/-/commit/08001e21ccbb71902429dc3096086b35114c822f

Bug#1062678: amd64-microcode: Package upstream's amdtee dir in amd64-microcode?

On 2/15/2024 12:39, Henrique de Moraes Holschuh wrote: While adding linux-firmware's amdtee/ directory to the Debian amd64-microcode package, I have noticed that the linux-firmware WHENCE file mentions a symbolic link that is not present in the git repository. The missing symlink is:

Bug#1062678: amd64-microcode: Package upstream's amdtee dir in amd64-microcode?

'amdtee' is the one thing right now, but soon (TM) the IPU/NPU binaries will go to linux-firmware.git and then where do those go? My (current) thinking is to have 2 categories: - AMD CPU related - AMD GPU/graphics related Current products only put the IPU/NPU in APU chips, but who is to stay;

Bug#1062678: amd64-microcode: Package upstream's amdtee dir in amd64-microcode?

mdtee' dir and was wondering what (best) to do with that, hence this bug. And I need to know what I should do about it on the backport branches and security update branches. I don't know/understand what you mean by this. Can you clarify? On Wed, 7 Feb 2024 18:38:30 -0600 Mario Limoncie

Bug#1062678: (no subject)

The firmware is only used on mobile APUs (which contain graphics). So if needing to pick an existing binary package instead of a new one I can see a stronger argument to bundle it with the graphics package.

Bug#1063161: Processed: Re: Bug#1063161: Add amd_pmf module

Yes, please set CONFIG_AMDTEE and CONFIG_AMD_PMF both. The firmware is optional, certain functions for amd-pmf will be non-functional without it.

Bug#1059606: (no subject)

It looks like it's still failing to build, but it's outside of fwupd code now. https://buildd.debian.org/status/fetch.php?pkg=fwupd=loong64=1.9.12-3=1706130974=0

Bug#974220: #974220 libreoffice-writer: Double paste in Writer

I just installed Debian 12 and bug still happens.

Bug#1059606: fwupd: add build support for loongarch64

This will be fixed by the next upload with this change: https://salsa.debian.org/efi-team/fwupd/-/commit/493293f60f78ed8c67d4839437765be140ebb25f Sent with Shortwave

Bug#1058701: RM: pm-utils; abandoned upstream

Package: ftp.debian.org Severity: normal X-Debbugs-Cc: mario.limoncie...@amd.com The pm-utils package hasn't had any activity in Debian since 2019. All bugs have been ignored. Upstream [1] has been dead since 2010. Modern userspace uses systemd to perform suspend/resume instead. [1]

Bug#1055694: klibc-utils: Patch to fix cp warning

Package: klibc-utils Version: 2.0.13-2 Followup-For: Bug #1055694 Dear Maintainer, I found a small typo in initramfs-tools klibc-utils script: # diff -ur klibc-utils /usr/share/initramfs-tools/hooks/klibc-utils --- klibc-utils 2023-12-07 10:35:52.738502916 +0100 +++

Bug#1010492: 

This is intentional behavior because some devices require AC to be plugged in to perform updates. It won't be changed for Debian, if you disagree with it you can raise a discussion upstream.

Bug#1055979: 

This should be fixed in 1.9.9, can you try it?

Bug#1040245: 

As you correctly pointed out this is unexpected and it definitely (used to) work properly. Can you add —verbose to the fwupd-refresh unit that causes this behavior? Maybe we'll get some more hints. Also if you raise this bug upstream (https://github.com/fwupd/fwupd

Bug#1056185: /usr/lib/python3/dist-packages/gidocgen/gir/ast.py: Debian specific multiarch detection fails when called outside of dpkg build

Package: gi-docgen Version: 2023.1+ds-4 Severity: normal File: /usr/lib/python3/dist-packages/gidocgen/gir/ast.py X-Debbugs-Cc: supe...@gmail.com When running gi-docgen outside of a package (such as a test build by hand) it will fail with the following: usr/bin/gi-docgen generate --quiet

Bug#1052993: (no subject)

Sorry; I missed this bug in the last upload. I've submitted your changes to the VCS for review and they should be part of the next version. https://github.com/fwupd/fwupd/pull/6378

Bug#1053856: (no subject)

The specific issue here is that there is a firmware binary in upstream linux-firwmare.git, also documented in WHENCE upstream but not installed in Debian's package.

Bug#1053764: radeon-amdgpu-firmware-is-required-for-drm-and-kms-on-r600-onward.patch unnecessary for amdgpu now

Package: linux Version: 6.5.0-1 Hi, The patch carried by the Debian kernel bugfix/all/radeon-amdgpu-firmware-is-required-for-drm-and-kms-on-r600-onward.patch isn't necessary specifically for amdgpu anymore with modern kernels. AMDGPU has been modified to check for the existence of firmware

Bug#1051294: This appears t

This appears to be a bug in libxmlb-dev, it's missing a dependency on libzstd-dev.

Bug#802539: closed by Julien Cristau (Re: Bug#802539: Please properly configure HTTPS in security.debian.org)

I filled this bug when I was a kid. In the time it took you to do anything about this, I became an adult. You suck.

Bug#934938: [cargo-docs] missing files

Hey, I might be able to help build deb packages. Because I've been learning rust for a few, this seems a good place to start contributing to Debian. May I know what's the bug's latest status and where should I start first? Thanks! -- https://www.linkedin.com/in/gonzalemario

Bug#1043582: New upstream version for pocketsphinx and Co

Am Sonntag, 13. August 2023, 17:33:42 CEST schrieb Samuel Thibault: > Hello, Good morning Samuel Thanks for your work and your quick reaction. > Mario Fux, le dim. 13 août 2023 11:49:37 +0200, a ecrit: > > Announcement of PocketSphinx 5.0.0: https://cmusphinx.github.io/2022/10/

Bug#1043582: New upstream version for pocketsphinx and Co

: https://cmusphinx.github.io/2022/10/ release/ Announcement of PocketSphinx 5.0.1: https://cmusphinx.github.io/2023/05/ release/ Thanks for your work on this package. Mario

Bug#1041752: fwupd: ships empty directory /lib/systemd/system-preset

On Sun, 23 Jul 2023 06:58:25 +0200 Helmut Grohne wrote: > Source: fwupd > Version: 1.9.3-1 > Severity: important > Tags: patch > > fwupd ships an empty directory /lib/systemd/system-preset. This > directory is prone to loss since we implemented the /usr-merge using > aliasing. Another package

Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)

Nevertheless: thx for your report your help through this thread. No problem. I am willing to try to do more, but right now I don't know how to do what has been suggested. Here is where to report Nouveau bugs: https://gitlab.freedesktop.org/drm/nouveau/-/issues/

Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)

[AMD Official Use Only - General] > -Original Message- > From: Nick Hastings > Sent: Thursday, June 1, 2023 7:02 PM > To: Karol Herbst > Cc: Limonciello, Mario ; Lyude Paul > ; Lukas Wunner ; Salvatore > Bonaccorso ; 1036...@bugs.debian.org; Rafael J. > Wys

Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)

[AMD Official Use Only - General] > -Original Message- > From: Karol Herbst > Sent: Thursday, June 1, 2023 12:19 PM > To: Limonciello, Mario > Cc: Nick Hastings ; Lyude Paul > ; Lukas Wunner ; Salvatore > Bonaccorso ; 1036...@bugs.debian.org; Rafael J. > Wys

Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)

[AMD Official Use Only - General] > -Original Message- > From: Karol Herbst > Sent: Thursday, June 1, 2023 11:33 AM > To: Limonciello, Mario > Cc: Nick Hastings ; Lyude Paul > ; Lukas Wunner ; Salvatore > Bonaccorso ; 1036...@bugs.debian.org; Rafael J. > Wys

Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)

+Lyude, Lukas, Karol On 5/31/2023 6:40 PM, Nick Hastings wrote: Hi, * Nick Hastings [230530 16:01]: * Mario Limonciello [230530 13:00]: As you're actually loading nouveau, can you please try nouveau.runpm=0 on the kernel command line? I'm not intentionally loading it. This machine also

Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)

On 5/29/23 18:01, Nick Hastings wrote: Hi, * Nick Hastings [230529 12:51]: * Mario Limonciello [230529 10:14]: On 5/28/23 19:56, Nick Hastings wrote: Hi, * Mario Limonciello [230528 21:44]: On 5/28/23 01:49, Salvatore Bonaccorso wrote: Hi Mario Nick Hastings reported in Debian

Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)

On 5/28/23 19:56, Nick Hastings wrote: Hi, * Mario Limonciello [230528 21:44]: On 5/28/23 01:49, Salvatore Bonaccorso wrote: Hi Mario Nick Hastings reported in Debian in https://bugs.debian.org/1036530 lockups from his system after updating from a 6.0 based version to 6.1.y. > #regz

Bug#1036530: Regression from "ACPI: OSI: Remove Linux-Dell-Video _OSI string"? (was: Re: Bug#1036530: linux-signed-amd64: Hard lock up of system)

On 5/28/23 01:49, Salvatore Bonaccorso wrote: Hi Mario Nick Hastings reported in Debian in https://bugs.debian.org/1036530 lockups from his system after updating from a 6.0 based version to 6.1.y. > #regzbot ^introduced 24867516f06d he bisected the issue and tracked it down to: On Sun, May

Bug#1035397: pm-utils is abandoned, should be removed from Debian

[Public] There was a comment on #852167 that there are no non-systemd tools, but that's simply not true. All you need for a suspend is echo mem | sudo tee /sys/power/state BTW - there's a reason that systemd refuses to include a lot of hooks and quirks. The scripts/quirks/etc that pm-utils

Bug#1035397: pm-utils is abandoned, should be removed from Debian

Package: pm-utils Severity: important X-Debbugs-Cc: mario.limoncie...@amd.com Dear Maintainer, pm-utils hasn't had any changed in 13 years upstream. It's been effectively replaced by systemd-sleep in all practical ways. It should be removed from the archive. -- System Information: Debian

Bug#1032706: [pkg-lxc-devel] Bug#1032706: lxc-snapshot cannot restore containers with loop storage backend

Hi Mathias, I submitted an issue on github: https://github.com/lxc/lxc/issues/4289 Step-by-step is explained there. Thank you, Mario On 3/11/23 17:59, Mathias Gibbens wrote: Hi Mario, I'm currently on travel with not-so-great network connectivity, so I haven't been able to reproduce

Bug#1032706: lxc-snapshot cannot restore containers with loop storage backend

Package: lxc Version: 1:5.0.2-1 Severity: grave Justification: causes data loss Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I tried to generate a snapshot with lxc-snapshot for a test container that is more

Bug#1008025:

[AMD Official Use Only - General] I believe this should be fixed in the latest version which drops the efi-cc and uses CC variable directly. Can you confirm it?

Bug#1023329:

[Public] FYI - the patch was originally targeted to ath-next (6.2), but because of the severity of this deadlock issue it's going to go to 6.1-rc with a CC to stable. [v6.1] wifi: ath11k: avoid deadlock during regulatory update in ath11k_regd_update() - Patchwork

Bug#1022187: upgrade-reports: Watching videos on the web doesn't work.

Package: upgrade-reports Severity: important X-Debbugs-Cc: mario_lu...@tiscali.it Hello everyone. As per object trying to watch videos on any site that publishes videos (youtube, twitch, etc., etc.) the same hangs and is not displayed. I tried with both Firefox and Chromium but the result is

Bug#1011511:

[Public] https://github.com/fwupd/fwupd/pull/5041 may help your problem, can you try that?

Bug#1016920: libopenscenegraph-dev: openscenegraph for Testing/Bookworm

Package: libopenscenegraph-dev Severity: normal X-Debbugs-Cc: mario_lu...@tiscali.it Dear Maintainer, Howdy. It seems to me that there is no package in Testing/Bookworm referring to openscenegraph, whether it is libraries, development libraries or the actual package. Am I wrong? Do you plan to

Bug#1010490:

It was validated to be fixed in 1.8.0, but the fix is present in 1.5.8 and later. Debian testing has 1.7.7, which picks up this fix. -- Mario Limonciello supe...@gmail.com

Bug#1005339: [Solved] This issue is not a Debian bullseye problem

[Solved] The issue is solved if the external monitor is connected natively to the laptop's displayport instead of using displaymanager-debian through a dock. -- Mario Natiello

Bug#1006390: Incorrect entry in SEE ALSO section of lintian(1)

to other versions in Bullseye, Bullseye-Backports and Testing. [1] https://manpages.debian.org/unstable/lintian/lintian.1.en.html#SEE_ALSO Best Regards, Mario

Bug#1005339: general: usbmouse+keyboard lag on closing the lid or issuing xrandr --output eDP-1 --off

is on, even if lid is closed Linux 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux Debian 11 bullseye -- Mario Natiello

Bug#1003575: portaudio19: Request for update of Portaudio to v19.7.0

reason for this request is that an up to date package would benefit scientific use cases provided by the octave-psychtoolbox-3 package in Debian, Ubuntu, and the NeuroDebian project which is part of Debian/Science. Many thanks and happy new year! Mario (the upstream maintainer of octave

Bug#1001908: manpages-de: manpage of "shutdown" not up-to-date

Hello, Am So., 26. Dez. 2021 um 01:43 Uhr schrieb Jesse Smith : > > On 2021-12-25 3:35 p.m., Mario Blättermann wrote: > > OK, it is in my favor to both keep existing man page translations > > alive (acknowledging the work of the previous translators) and > > integrate

Bug#1001908: manpages-de: manpage of "shutdown" not up-to-date

Hello all, Am Fr., 24. Dez. 2021 um 10:27 Uhr schrieb Helge Kreutzmann : > > Hello Mark, > On Fri, Dec 24, 2021 at 08:13:56AM +, Mark Hindley wrote: > > [Adding CC debian-init-divers...@chiark.greenend.org.uk] > > And adding Mario, manpages-l10n upstream maintainer

Bug#1000622: ser2net: Fails to start on boot since the serial port is not ready

Documentation=man:ser2net(8) After=network-online.target Wants=network-online.target [Service] EnvironmentFile=-/etc/default/ser2net ExecStart=/usr/sbin/ser2net -n -c $CONFFILE -P /run/ser2net.pid Type=exec Restart=on-failure [Install] WantedBy=multi-user.target ``` Thank you a lot!!! Best Regards, Mario

Bug#1000622: ser2net: Fails to start on boot since the serial port is not ready

Package: ser2net Version: 4.3.3-1 Severity: important X-Debbugs-Cc: mario@volterra.cloud Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Installed, before upgrade to Debian Bullseye it worked fine on buster

Bug#994250: simple-scan: Brightness and Contrast settings do not have any effect (CanoScan Lide 35)

Package: simple-scan Version: 3.38.1-1 Severity: normal Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? I often need b/w scans, but these are always too dark * What exactly did you do (or not do) that

Bug#993257: bind9: /etc/default/bind9 renamed in bullseye

Package: bind9 Version: 1:9.16.15-1 Severity: normal Tags: d-i Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? * What exactly did you do (or not do) that was effective (or ineffective)? * What was the

Bug#993160: xz-utils doesn't contain translated man pages

Package: xz-utils Version: 5.2.5-2 Hello, the upstream tarball contains some man pages translated into German. Please add them to the downstream package (this applies also to xzdec). To get the man pages installed, probably po4a is needed as a build requirement. Best Regards, Mario

Bug#974220: #974220 libreoffice-writer: Double paste in Writer

libc6 2.31-12 LibreOffice 7.0.4.2 00(Build:2) Best regards, Mario

Bug#988584: manpages-hu: Contains undistributable content - All rights reserved

Hello, Helge Kreutzmann schrieb am So., 16. Mai 2021, 12:27: > Package: manpages-hu > Version: 20010119-7 > Severity: serious > Justification: Policy 2.3 > X-Debbugs-Cc: Mario Blättermann > > Short: > man8/ssh.8 states: > .\" Copyright (c) 1

Bug#977043: fwupdmgr[1191] trap invalid opcode ip:4247d0 sp:bf98504c error:0 in fwupdmgr[423000+15000]

As an experiment, can you please try to disable the "cpu" plugin in /etc/fwupd/daemon.conf? Add to "BlacklistPlugins" list. > -Original Message- > From: Martin-Éric Racine > Sent: Wednesday, March 10, 2021 5:14 > To: Julien Cristau > Cc: 977...@bugs.debian.org; Bernhard Übelacker >

Bug#977043: fwupdmgr[1191] trap invalid opcode ip:4247d0 sp:bf98504c error:0 in fwupdmgr[423000+15000]

Martin-Éric Racine > Sent: Wednesday, March 10, 2021 10:25 > To: Limonciello, Mario > Cc: 977...@bugs.debian.org; Julien Cristau; Bernhard Übelacker > Subject: Re: Bug#977043: fwupdmgr[1191] trap invalid opcode ip:4247d0 > sp:bf98504c error:0 in fwupdmgr[423000+15000] > >

Bug#973715: RE: Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary

00:09 To: 973...@bugs.debian.org Subject: Bug#973715: RE: Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary Hi Mario, LOn Mon, 16 Nov 2020 16:01:34 + "Limonciello, Mario" wrote: > As @Steve McIntyre mentions, it's a manual process to kick

Bug#982059: manpages-de,psmisc: File conflict between psmisc and manpages-de: '/usr/share/man/de/man1/fuser.1.gz

Am Mi., 10. Feb. 2021 um 16:52 Uhr schrieb Helge Kreutzmann : > > Hello Mario, > On Wed, Feb 10, 2021 at 02:53:14PM +0100, Mario Blättermann wrote: > > to mention that Craig just released procps-ng-3.3.17 which also ships > > translated man pages. To avoid file conflicts,

Bug#982059: manpages-de,psmisc: File conflict between psmisc and manpages-de: '/usr/share/man/de/man1/fuser.1.gz

which now needs to be packaged to fix the file conflicts. Best Regards, Mario Am Di., 9. Feb. 2021 um 19:40 Uhr schrieb Helge Kreutzmann : > > Hello Craig, > thank you very much for your support. I was tired and frustrated > yesterday. > > On Mon, Feb 08, 2021 at 04:34:19PM

Bug#982059: manpages-de,psmisc: File conflict between psmisc and manpages-de: '/usr/share/man/de/man1/fuser.1.gz

talls psmisc-23.4, could it happen that manpages-de-4.2.0 will be deleted, without updating it to v4.9.1? Best Regards, Mario

Bug#982059: manpages-de,psmisc: File conflict between psmisc and manpages-de: '/usr/share/man/de/man1/fuser.1.gz

://salsa.debian.org/manpages-l10n-team/manpages-l10n/-/tags/v4.9.1 Best Regards, Mario Am So., 7. Feb. 2021 um 01:51 Uhr schrieb Craig Small : > > Yep, psmisc now ships with translated packages. So fuser.1 and friends are in > two places. > > So manpages-de has fuser, killall

Bug#980885: manpages-es-extra: Suitable for Bullseye?

benefits of. Best Regards, Mario

Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.

Limonciello, Mario > Cc: 943...@bugs.debian.org > Subject: RE: Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh > fwupd metadata and update motd. > > > [EXTERNAL EMAIL] > > Yes, I'm using sssd against FreeIPA. > > Tom > > > On 28 Janua

Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.

Are you by chance using NFS mounted directories? Or external entity for authentication such as LDAP or SSSD? > -Original Message- > From: Thomas Stewart > Sent: Wednesday, January 27, 2021 8:33 > To: Limonciello, Mario > Cc: 943...@bugs.debian.org > Subject: Re:

Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.

Can you check if fwupdmgr works as a standard user to talk to the daemon for you? > -Original Message- > From: Thomas Stewart > Sent: Wednesday, January 27, 2021 5:42 > To: 943...@bugs.debian.org > Subject: Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh > fwupd

Bug#980570: fwupd: obsolete-conffile /etc/fwupd/ata.conf

Thanks for the report. It's an oversight that it didn't get removed. Will have a future upload resolve it. > -Original Message- > From: Thorsten Glaser > Sent: Wednesday, January 20, 2021 12:25 > To: Debian Bug Tracking System > Subject: Bug#980570: fwupd: obsolete-conffile

Bug#943343: fwupd: fwupd-refresh.service failed to start Refresh fwupd metadata and update motd.

On Thu, 19 Mar 2020 15:02:13 +0100 Diederik de Haas wrote: > On donderdag 19 maart 2020 14:59:56 CET mario.limoncie...@dell.com wrote: > > Sorry - I see now that was from a while back. > > And also a different user (OP). After some upstream discussion, any remaining issues with 1.3.x this is

Bug#980049: fwupd: Should fwupd specify dbus as a dependency?

> -Original Message- > From: Lukas Pirl > Sent: Wednesday, January 13, 2021 13:51 > To: Limonciello, Mario > Cc: 980...@bugs.debian.org > Subject: Re: Bug#980049: fwupd: Should fwupd specify dbus as a dependency? > > Thanks for your quick reply, Mario. >

Bug#980049: fwupd: Should fwupd specify dbus as a dependency?

I don't think it's a true dependency. You can use fwupdtool without it. It's only needed for fwupdmgr. Perhaps a Recommends would be better? That being said I don't think it would solve it for you. Systemd has dbus as a Recommends and you still appear to not have it. > -Original

Bug#976639: flashrom does not support jlink_spi

> > On Tue, 2020-12-08 at 05:45 +, Limonciello, Mario wrote: > > I checked and meson.build is missing jlink support. So this needs to > > be fixed upstream to enable in the package. > > Thanks, I didn't know that there is a meson build option. I pushed

Bug#976639: flashrom does not support jlink_spi

I checked and meson.build is missing jlink support. So this needs to be fixed upstream to enable in the package.

Bug#944247: xen domU crashes under high i/o load if you use qcow2 images

iminating Xen from the equation? > -- -- Mit freundlichen Grüßen Mario Bregulla muneX Mobil: 0160 / 94 62 09 02 i...@munex.de www.munex.de UStNr: DE 149371863 Steuernummer: 31/020/33191

Bug#973715: fwupd-amd64-signed holding off fwupd update results in segfaulting binary

> -Original Message- > From: Matteo Settenvini On Behalf Of Matteo Settenvini > Sent: Saturday, November 14, 2020 7:35 > To: 973...@bugs.debian.org > Subject: Bug#973715: fwupd-amd64-signed holding off fwupd update results in > segfaulting binary > > The problem suddenly become worse.

Bug#974738: fwupd: FTBFS on various architectures

Yes, I'm aware. I fixed all but ppc64le in the upstream packaging. That one is under discussion. Will wait until that one is also fixed for next upload. Get Outlook for Android From: Salvatore Bonaccorso Sent: Saturday, November 14, 2020

Bug#973715: fwupd-amd64-signed: Uninstallable; not binNMU-friendly

> -Original Message- > From: Boyuan Yang > Sent: Tuesday, November 3, 2020 23:45 > To: Limonciello, Mario; 973...@bugs.debian.org > Subject: Re: Bug#973715: fwupd-amd64-signed: Uninstallable; not binNMU- > friendly > > > [EXTERNAL EMAIL] > > Hi,

Bug#973715: fwupd-amd64-signed: Uninstallable; not binNMU-friendly

> > On Wed, Nov 04, 2020 at 06:30:54PM +, Limonciello, Mario wrote: > >> 在 2020-11-03星期二的 22:21 +0000，Limonciello, Mario写道： > >> > > -Original Message- > >> > > From: Boyuan Yang > >> > > Sent: Tuesday, November 3, 2020 13:

Bug#973715: fwupd-amd64-signed: Uninstallable; not binNMU-friendly

> -Original Message- > From: Boyuan Yang > Sent: Tuesday, November 3, 2020 13:09 > To: sub...@bugs.debian.org > Subject: Bug#973715: fwupd-amd64-signed: Uninstallable; not binNMU-friendly > > Package: fwupd-amd64-signed > Severity: grave > Version: 1.4.6+2 > X-Debbugs-CC:

Bug#973267: Acknowledgement (libtss2-dev: pkgconfig file included with libtss2-dev has invalid path)

Submitted this to upstream project: https://github.com/tpm2-software/tpm2-tss/issues/1876

Bug#973267: libtss2-dev: pkgconfig file included with libtss2-dev has invalid path

Package: libtss2-dev Version: 3.0.0-1 Severity: normal X-Debbugs-Cc: mario.limoncie...@dell.com Dear Maintainer, The pkgconfig file included in libtss2-dev contains an invalid path: Name: tss2-esys Description: TPM2 Enhanced System API library. URL: https://github.com/tpm2-software/tpm2-tss

Bug#971238: Expose RPCNFSDOPTS in /etc/default/nfs-kernel-server

@@ -1,6 +1,10 @@ # Number of servers to start up RPCNFSDCOUNT=8 +# Options for rpc.nfsd +# To enable RDMA on the server, specify '--rdma' here +RPCNFSDOPTS="" + # Runtime priority of server (see nice(1)) RPCNFSDPRIORITY=0 -- AR Mario Lang Phone: +

Bug#970698: Please remove amd64 from NO_PMIX_ARCH

Package: openmpi Version: 4.0.5-4 Severity: important Right now, debian/rules has NO_PMIX_ARCH:= armel mipsel amd64 This looks like an oversight. I get an error about undefined symbol when launching an MPI job via SLURM. Removing amd64 from NO_PMIX_ARCH fixes this. -- AR Mario Lang

Bug#948336: selinux-policy-default: systemd-journal cannot access processes with 'signull' (RedHat Bug 1676923).

Hello, Today I installed a Debian Box with selinux enabled. I found that I'm affected by this bug. Is there any activity to solve this bug? The referenced Redhat Bug 1676923 is closed. Links: [1] https://bugzilla.redhat.com/show_bug.cgi?id=1676923 sincerely yours Mario Koppensteiner

Bug#970054: fwupd: Missing Depends (or Recommends) on udisks2 for UEFI update

Thanks for the report, and submitting the fix upstream! I agree, it should probably be a recommends and we should pull that patch in for safety. I'll include it in a 1.4.6-2 upload once we merge it upstream. Thanks! > -Original Message- > From: Jochen Sprickerhof > Sent: Thursday,

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

I would suggest a new issue linking to that one instead so it's not lost. > -Original Message- > From: Michel Le Bihan > Sent: Monday, July 27, 2020 1:01 PM > To: Limonciello, Mario; 963...@bugs.debian.org > Subject: Re: Bug#963475: libefivar1: "efibootmgr -

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

Limonciello, Mario; 963...@bugs.debian.org > Subject: Re: Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not > parse device path: Invalid argument" > > > [EXTERNAL EMAIL] > > It was efibootmgr and efivar master. > > Le lund

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

> -Original Message- > From: Michel Le Bihan > Sent: Sunday, July 26, 2020 2:58 PM > To: 963...@bugs.debian.org > Subject: Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not > parse device path: Invalid argument" > > > [EXTERNAL EMAIL] > > Hello, > > What's preventing the

Bug#963475: libefivar1: "efibootmgr -v" fails with "Could not parse device path: Invalid argument"

Was that just efibootmgr master? If possible, can you move up to *both* efivar master and efibootmgr master and try again? > -Original Message- > From: Michel Le Bihan > Sent: Monday, July 27, 2020 11:25 AM > To: Limonciello, Mario; 963...@bugs.debian.org > Subject:

Bug#956013: Fails to install

Well, alternatively we could disable the man pages which come from there and keep publishing the old manpages-fr-extra package again and again, with all the outdated stuff it contains. Doesn't make sense at all. Instead, let's go a step ahead and switch to up-to-date man pages. Best Regards, Mario

Bug#953565: ITP: libjcat -- JSON Catalog library

Package: wnpp Severity: wishlist Owner: Mario Limonciello * Package name: libjcat Version : 0.1.0 Upstream Author : Richard Hughes * URL : https://github.com/hughsie/libjcat * License : LGPL 2.1+ Programming Lang: C Description : JSON Catalog library

Bug#951589: flashrom: Update to version 1.2

Package: flashrom Severity: wishlist Tags: upstream Dear Maintainer, Can you please upgrade to the recently released version 1.2? This package now supports a library for other applications to compile against it. As part of upgrading to 1.2, can you please introduce new binary packages for that

Bug#950389: libc6 s390x preinstall script fails

Package: libc6 Version: 2.30-0ubuntu3 Severity: grave Justification: renders package unusable Dear Maintainer, I currently use multi arch with s390x on Debian testing in an amd64 container for continuous integration purposes for an upstream project, fwupd. In the last day or so the container

Bug#891410:

I think that upstream would be happy to switch to a "public" interface in the future. Would you mind suggesting something upstream with the relevant changes that make sense? On Mon, Jan 20, 2020 at 7:52 AM Guilhem Moulin wrote: > On Mon, 20 Jan 2020 at 07:12:37 -0600, Mario Limo

Bug#891410:

FYI, the newly released version 12 has initramfs support.

Bug#949069: "apt autoremove" doesn't remove an automatic package with 0 dependents

package: apt version: 1.8.2 I'm refiling this report since it was wrongly marked as resolved. to reproduce the problem, run these commands on a fresh Ubuntu or Debian installation: $ apt install postgresql-11 $ apt purge postgresql-11 $ apt autoremove a dependency named "postgresql-client-11"

  1   2   3   4   5   6   7   8   9   10   >