Bug#1063161:

On Thursday, 23 May 2024 17:33:47 CEST Vincent Blut wrote: > We are just lacking a configuration symbol. Diederik, starting with > linux 6.8 AMD PMF requires TEE. Do you want me to send a MR? Sure. Bit surprised it wouldn't be automatically selected though. signature.asc Description: This is a

Bug#966570: RFP: libamf -- Advanced Media Framework (AMF) SDK

On 30 Jul 2020 16:00:44 -0400 Louis-Philippe Véronneau wrote: > I'm happy to help or sponsor work for this, but I'm not confident I > understand the codebase enough to be packaging this myself. There has been a reply to this, but it didn't directly To/CC you, so I'm replying to make sure

Bug#1071666: ffmpeg: autopkgtest failure with ffmpeg 7.0

e8fc104e1da07335935 Mon Sep 17 00:00:00 2001 From: Diederik de Haas Date: Thu, 23 May 2024 12:08:28 +0200 Subject: [PATCH] d/tests: Update list_formats for extra output column in ffmpeg 7.0 The ``ffmpeg -formats`` command got an extra output column. ``ffmpeg -formats`` output header for ffmpeg 6.

Bug#1071662: chromium: Wrapper script does not correctly pass arguments to Chromium

Package: chromium Version: 125.0.6422.76-1~deb12u1 Severity: normal Dear Maintainer, When running 125.0.6422.76-1~deb12u1, when passing arguments to the chromium wrapper script included in the Debian package, not all arguments are passed correctly to the Chromium binary. This happens

Bug#1071258: linux-image-6.1.0-21-amd64: Mouse, trackpad, keyboard behave inconsistently

On Thursday, 23 May 2024 09:59:52 CEST Eduardo Casais wrote: > 4) Determining whether the bug was introduced by the passage from kernel > 5.10.0 to 6.1.0, or whether it was an error introduced between releases > of image 6.1.0-*. > > Attempted resolution: > > I looked at the image versions

Bug#1071559: linux-headers-6.8.9-amd64: error creating r8125 module with dkms

Control: reassign -1 r8125-dkms On Tuesday, 21 May 2024 10:41:54 CEST Pierpaolo Toniolo wrote: > Was installing the linux-image-6.8.9-amd64 and it's fellow linux- > headers-6.8.9-headers. > At modules creation with dkms I got an error building module r8125 (package > r8125-dkms) Which is a

Bug#1071501: linux-image-6.1.0-21-arm64: Linux NFS client hangs in nfs4_lookup_revalidate

On Monday, 20 May 2024 21:07:49 CEST Salvatore Bonaccorso wrote: > - I did read you cannot trigger with 5.15. If you build 6.1.90 from > upstream without Debian patches I assume you can trigger the issue > likewise? If so could you bisect the changes introducing the issue? If the test with

Bug#1071522: ITP: paping -- Test network connection between two hosts

Package: wnpp Severity: wishlist Owner: Rony Joao de Sousa X-Debbugs-Cc: debian-de...@lists.debian.org * Package name: paping Version : 1.6.0 Upstream Contact: Mike Lovell * URL : https://github.com/ronyjdesousa/paping * License : MIT Programming Lang: C

Bug#1071516: ITP: libhash-wrap-perl -- Perl module that provides a simple way to create object-oriented interfaces to hash references

Package: wnpp Owner: Lincoln Yuji , Luiza Soezima , Sabrina Araujo Severity: wishlist X-Debbugs-CC: debian-de...@lists.debian.org, debian-p...@lists.debian.org * Package name: libhash-wrap-perl Version : 1.03 Upstream Author : Diab Jerius * URL : https

Bug#1071184: Kernel 6.6 and 6.7 route-leak between VRF and default leads to Time to live exceeded

On Friday, 17 May 2024 15:08:17 CEST Development EasyNet wrote: > I will try. Meanwhile I was troubleshooting this issue for some time and > I notice a change in FRRouting between 9.1 and 10.0. > Before 10.0 FRRouting was installing the routes in kernel using the > destination interface of the

Bug#1071184: Kernel 6.6 and 6.7 route-leak between VRF and default leads to Time to live exceeded

Control: tag -1 moreinfo On 15 May 2024 16:08:27 +0200 Development EasyNet wrote: > Package: linux-image > Version: 6.6.15-2 and 6.7.12-1 > > I'm facing for some time a strange behavior of the route-leak. It happen > on both IPv4 and IPv6. > Configuration used: Debian Trixie, Kernel 6.7.12

Bug#1071263: linux-image-6.8.9-amd64: Vulkan applications crash on computers using amdgpu

Control: forwarded -1 https://gitlab.freedesktop.org/drm/amd/-/issues/3343 signature.asc Description: This is a digitally signed message part.

Bug#1069077: rockpro64: multiple kernel oops and frequent boot failures

On Friday, 17 May 2024 03:36:35 CEST Forest wrote: > A git bisect reveals it to be fixed by this commit: > > https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id= > f7a59018953910032231c0a019208c4b0a4a8bc3 > > maple_tree: make mas_erase() more robust > > > > mas_erase()

Bug#1071015: RFS: color-picker/1.0.3-3 -- Powerful screen color picker based on Qt

ast upload: color-picker (1.0.3-3) unstable; urgency=medium . * debian/control: bumped Standards-Version to 4.7.0. * debian/copyright: Updated dates. * debian/patches/01-segfaults.patch: - Created. Thanks to Sudip Mukherjee (Closes: #1060003) Regards, -- Hugo Torres de Lima

Bug#1070907: python-stdnum: please drop the suggests on SimpleSoap

On Sat, 2024-05-11 at 14:26 +0200, Alexandre Detiste wrote: > Please drop the suggests on python3-pysimplesoap; > this package would soon be dropped from Debian > altogheter. The next upload will drop the suggest (which already was a fallback for zeep). Thanks, -- -- arthur -

Bug#1070713: how-can-i-help: undefined local variable or method autorm_header_done

Control: severity -1 grave On 07 May 2024 19:35:30 +0200 Nicolas Noirbent wrote: > Package: how-can-i-help > Version: 18 > Severity: important > Tags: patch > > Running how-can-i-help outputs nothing past the initial banner, due to an > undefined variable: Which makes the package unusable, so

Bug#1070367: linux-image-6.7.12-amd64: No WiFi

Control: merge -1 1070353 On Saturday, 4 May 2024 16:56:10 CEST Kurt Meyer wrote: > Package: src:linux > Version: 6.7.12-1 > Severity: important > > * What led up to the situation? > > Booting with the linux-image-6.7.12-amd64 kernel results in Wi-Fi not > working and Wi-Fi isn't even an option

Bug#1053995: Info received (ITP: fastfetch -- like neofetch, but much faster because written in C)

Hello, On Wed, Nov 15, 2023 at 02:12:00AM +, Li Carter wrote: > Friendly ping > As discussed on https://github.com/fastfetch-cli/fastfetch/issues/533#issuecomment-2094282467 I will be taking this bug to work on it. > > 2023年10月16日 14:39，Debian Bug Tracking System 写道： > > > > Thank you

Bug#1068082: bullseye-pu: package intel-microcode/3.20240312.1~deb11u1

On Mon, Apr 22, 2024, at 13:58, Jonathan Wiltshire wrote: > Control: tag -1 confirmed > > On Sat, Mar 30, 2024 at 07:50:45AM -0300, Henrique de Moraes Holschuh wrote: >> As requested by the security team, I would like to bring the microcode >> update level for Intel p

Bug#1069870: linux-image-6.7.7-686-pae: please enable i915 mtl_* firmware

Control: reassign -1 src:firmware-nonfree 20230625-2 On Friday, 26 April 2024 07:36:16 CEST Martin-Éric Racine wrote: > Package: src:linux > Version: 6.7.7-1 > Severity: normal > > W: Possible missing firmware /lib/firmware/i915/mtl_gsc_1.bin for module > i915 W: Possible missing firmware

Bug#1068365: FTBFS on mips64el in lsfd/mkfds-multiplexing-pselect6 test et al

Control: forwarded -1 https://github.com/util-linux/util-linux/issues/2867 https://lore.kernel.org/all/20240328-mips_save_syscall-v1-1-9e1d62d69...@flygoat.com/ On Thursday, 25 April 2024 22:10:12 CEST Chris Hofstaedtler wrote: > reassign 1068365 src:linux > affects 1068365 src:util-linux >

Bug#1069301: linux-image-6.1.0-20-amd64: bluetooth causes kernel BUG - list_del corruption, (address)->prev is LIST_POISON2

Control: tag -1 -moreinfo +upstream Control: forwarded -1 https://lore.kernel.org/linux-bluetooth/CADRbXaDqx6S+7tzdDPPEpRu9eDLrHQkqoWTTGfKJSRxY=ht...@mail.gmail.com/ On Monday, 22 April 2024 10:32:00 CEST Jeremy Lainé wrote: > Over the weekend I reported the issue to the linux-bluetooth mailing

Bug#1069082: linux-image-6.1.0-20-amd64: USB ethernet AX88179 device name eth0

patch and build a kernel. https://kernel-team.pages.debian.net/kernel-handbook/ch-common-tasks.html#id-1.6.6.4 describes a procedure with which you can apply (the attached) patches HTH>From 21f7e476d0afe832f6656b917b976c6efe6b24f3 Mon Sep 17 00:00:00 2001 From: Diederik de Haas Date: Tue, 16

Bug#1069077: es8316 driver causes kernel oops / panic on rockpro64

the 6.7 kernel work properly again, we likely have found the culprit for the kernel oops/panic. Can you first try the Testing (6.6.15) kernel and if that works try applying the attached patches to the 6.7 kernel?>From 407672343a738ede6f5e955e3afa57d16b37f4e6 Mon Sep 17 00:00:00 2001 From: Died

Bug#1066398: xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1Init'

Control: forcemerge -1 1065184 On Saturday, 13 April 2024 16:32:04 CEST Andreas Metzler wrote: > > If you agree, please merge these two bugs. > > FTR: Bug #1065184 is already fixed in git. > > FWIW I can cobnfirm that xwayland builds successfully if libtirpc-dev is > installed. Thanks, then I'm

Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

On Wednesday, 10 April 2024 15:32:02 CEST Cyril Brulebois wrote: > Cyril Brulebois (2024-04-10): > > Salvatore Bonaccorso (2024-04-10): > > > On Tue, Apr 09, 2024 at 03:33:09PM +0200, Diederik de Haas wrote: > > > > Does the problem go away if you rever

Bug#1068675: linux-image-6.1.0-19-amd64: loss of SMART information: Device is in SLEEP mode, exit(2)

Hi Cyril, On Tuesday, 9 April 2024 01:06:43 CEST Cyril Brulebois wrote: > Upgrading from linux-image-6.1.0-18-amd64 to linux-image-6.1.0-19-amd64 > leads to losing some SMART information, at least as queried by munin (in > Debian 12) when it comes to sensors. Does the problem go away if you

Bug#1068701: TypeError: cannot use a string pattern on a bytes-like object

Package: duplicity Version: 0.8.22-1+b3 Severity: normal X-Debbugs-Cc: timon.degr...@hypernode.com Dear Maintainer, * What led up to the situation? We create write offsite backups to s3 with duply/duplicity. We run duplicity with the following params (from duply):

Bug#1068631: linux-image-6.6.15-amd64: Using monitor refreshrate above 120Hz i get random black screen for a few seconds at certain actions

Control: forcemerge -1 1054889 On Monday, 8 April 2024 10:44:12 CEST dada007 wrote: > I had an earlier report with this bug No need to have 2 bugs for the same problem, thus merging signature.asc Description: This is a digitally signed message part.

Bug#1057850: libnss-db: Uses db5.3, no replacement in sight

ood a time as any other to stop shipping libnss-db. Users can probably use any other NSS module that can use some form of database backend. After a while I intend to file an RM bug, too. Chris -- Paulo Henrique de Lima Santana (phls) Belo Horizonte - Brasil Debian Developer Site: http://phls.com

Bug#1068249: linux-image-6.1.0-18-amd64: ax201 iwlwifi driver creates millions of 'Unhandled alg: 0x33f0707' messages

ts). > > (3) Instead I will try first to use debian testing on a different NUC, but > this will take some time. > > 2. April 2024 20:28, "Diederik de Haas" schrieb: > > On Tuesday, 2 April 2024 19:54:41 CEST J. Pfennig wrote: > >> Package: src:linux > >>

Bug#1068084: bookworm-pu: package intel-microcode/3.20240312.1~deb12u1

Uploaded. On Mon, Apr 1, 2024, at 08:48, Jonathan Wiltshire wrote: > Control: tag -1 confirmed > > On Sat, Mar 30, 2024 at 07:47:05AM -0300, Henrique de Moraes Holschuh wrote: >> As requested by the security team, I would like to bring the microcode >> update level

Bug#1068249: linux-image-6.1.0-18-amd64: ax201 iwlwifi driver creates millions of 'Unhandled alg: 0x33f0707' messages

On Tuesday, 2 April 2024 19:54:41 CEST J. Pfennig wrote: > Package: src:linux > Version: 6.1.76-1 > Severity: important > Tags: upstream I am/was inclined to remove that tag, but the problem is likely caused by firmware which is too old for the 'backported' patches that upstream applied. > The

Bug#1068084: bookworm-pu: package intel-microcode/3.20240312.1~deb12u1

+++ b/debian/changelog @@ -1,3 +1,91 @@ +intel-microcode (3.20240312.1~deb12u1) bookworm; urgency=medium + + * Build for bookworm (no changes) + + -- Henrique de Moraes Holschuh Sat, 30 Mar 2024 07:01:52 -0300 + +intel-microcode (3.20240312.1) unstable; urgency=medium + + * New upstream micro

Bug#1068083: bullseye-pu: package intel-microcode/3.20240312.1~deb11u1

+++ b/debian/changelog @@ -1,3 +1,92 @@ +intel-microcode (3.20240312.1~deb11u1) bullseye; urgency=medium + + * Backport to Debian Bullseye + * debian/control: revert non-free-firmware change + + -- Henrique de Moraes Holschuh Sat, 30 Mar 2024 07:06:46 -0300 + +intel-microcode (3.20240312.1) unsta

Bug#1068082: bullseye-pu: package intel-microcode/3.20240312.1~deb11u1

angelog index fa702cb..317fad2 100644 --- a/debian/changelog +++ b/debian/changelog @@ -1,3 +1,92 @@ +intel-microcode (3.20240312.1~deb11u1) bullseye; urgency=medium + + * Backport to Debian Bullseye + * debian/control: revert non-free-firmware change + + -- Henrique de Moraes Holschuh Sat, 30 Ma

Bug#1054249: (no subject)

Can this solution be brought too bookworm, either through stable-updates (preferably) or otherwise backports? The current package is not useable.

Bug#1063591: (no subject)

retitle 1063591 RFP: anew -- Tool for adding new lines to files, skipping duplicates (program) noowner 1063591 The anew project isn't very active at the moment. There are open bug issues on GitHub that haven't been addressed. For this reason, I won't proceed with the effort to package anew for

Bug#1063591: (no subject)

retitle 1063591 RFP: anew -- Tool for adding new lines to files, skipping duplicates (program) noowner 1063591

Bug#1003091: xwayland: Xwayland uses glamor and shows black screens

I think this issued can be closed. In fact it is a really sad story. Problems occurred at i915 classic. Xwayland upstream didnot want to remove the activation of ES 2.0, which totally was not working. But they also did not want to approve merge-requests, which solve the problems. Then Debian was

Bug#1065184: xwayland: missing build-dep on libtirpc-dev

Hi, I saw that this issue was fixed in git, but there hasn't been an upload with that yet. It seems it's blocking the armhf build of wlroots and therefor its migration, so could you upload a version with that fix? Cheers, Diederik PS: On Salsa 'upstream-unstable' is set as default branch,

Bug#1003091: xwayland: Xwayland uses glamor and shows black screens

Hi, On 21 Jan 2022 19:49:55 +0100 Gert van de Kraats wrote: > I reported the bug upstream for Xwayland: > > https://gitlab.freedesktop.org/xorg/xserver/-/issues/1288 > > It will be fixed. Could you update this bug with its status? I got the impression that it is fixed ups

Bug#1066398: xwayland: FTBFS: ./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/./obj-x86_64-linux-gnu/meson-private/tmpz22kr2qg/testfile.c:17:(.text+0x9): undefined reference to `SHA1Init'

Hi, On Wed, 13 Mar 2024 13:06:09 +0100 Lucas Nussbaum wrote: > Source: xwayland > Version: 2:23.2.4-1 > Severity: serious > Justification: FTBFS > Tags: trixie sid ftbfs > > During a rebuild of all packages in sid, your package failed to build > on amd64. > > > Relevant part (hopefully): > >

Bug#1067194: ITP: ansible-creator -- fastest way to generate all your ansible content

Package: wnpp Severity: wishlist Owner: Guilherme de Paula Xavier Segundo X-Debbugs-Cc: debian-de...@lists.debian.org, guilherme@gmail.com * Package name: ansible-creator Version : 24.2.0 Upstream Contact: Ansible by Red Hat * URL : https://github.com/ansible

Bug#1064617: update password selection advice

On Tuesday, 19 March 2024 12:08:53 CET Holger Wansing wrote: > Apparently we have reached something like a consensus on this topic, > should we merge this then? > > > > Any objections? LGTM :-) possibly `s/rms/debra/` with

Bug#1065611: Additional support for SolidRun HoneyComb

On Tuesday, 19 March 2024 11:52:29 CET Josua Mayer wrote: > May I ask if you are analyzing dts manually, or whether you are aware > of an automatic tool? Analyses is done by a MUCH improved scripts based upon what I came up with a while ago:

Bug#1066829: ITP: assetfinder -- Find domains and subdomains related to a given domain

e. May I humbly suggest "dns-assetfinder" ? It might be a very good idea to talk to upstream first. -- Henrique de Moraes Holschuh

Bug#1065611: Additional support for SolidRun HoneyComb

ECC support should already work with the Stable 6.1 kernel (or newer). > > Am 07.03.24 um 13:34 schrieb Diederik de Haas: > >> On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote: > >> > >>> LX2160 SoC early silicon revisions have a pci-e generation 4 &g

Bug#1055016: override: tasksel-data:admin/optional

On Sunday, 29 October 2023 12:54:13 CET Cyril Brulebois wrote: > Daniel Lewart (2023-10-29): > > Package: ftp.debian.org > > Severity: normal > > User: ftp.debian@packages.debian.org > > Usertags: override > > X-Debbugs-Cc: task...@packages.debian.org, debian-b...@lists.debian.org, > >

Bug#1066060: libpam-modules: pam_lastlog.so missing

Package: libpam-modules Version: 1.5.3-6 Severity: normal I noticed the following line in my logs: login[2449]: PAM unable to dlopen(pam_lastlog.so): /usr/lib/security/pam_lastlog.so: cannot open shared object file: No such file or directory I looked in the deb files from snapshot.debian.org,

Bug#1064617: Passwords should not be changed frequently

On Friday, 8 March 2024 19:58:56 CET Philip Hands wrote: > IMO Having the 'password/passphrase' throughout makes it awkward to > read, and actually we've got one place where it still just says > password, and fixing that would make it slightly worse IMO. > > How about dropping the passphrase

Bug#1065611: Additional support for SolidRun HoneyComb

Hi Josua, On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote: > LX2160 SoC early silicon revisions have a pci-e generation 4 controller. > It requires a different driver from newer gen-3 silicon. > > This affects the SolidRun Honeycomb Workstation which > is otherwise fully supported in

Bug#1061116: linux-image-6.1.0-17-arm64: please enable support for lx2160a pcie gen4 controller on early silicon

Control: clone -1 -2 Control: retitle -2 Additional support for SolidRun HoneyComb On Thursday, 18 January 2024 17:40:38 CET Josua Mayer wrote: > LX2160 SoC early silicon revisions have a pci-e generation 4 controller. > It requires a different driver from newer gen-3 silicon. > > This affects

Bug#1032623: fixed in qa.debian.org

On Wednesday, 6 March 2024 16:26:40 CET Christoph Berg wrote: > Re: Diederik de Haas > > > The pre-filter which was 1GB and was recently further reduced to 500MB is > > still in place AFAICT. So it seems to me that this bug would be fixed > > when the size limitation is re

Bug#1032623: fixed in qa.debian.org

On Wednesday, 6 March 2024 15:13:20 CET Christoph Berg wrote: > Hello, > > Bug #1032623 in qa.debian.org reported by you has been fixed in the Git > repository. You can see the commit message below and you can check the diff > of the fix at: > >

Bug#1064617: Passwords should not be changed frequently

On Wednesday, 6 March 2024 13:19:04 CET Justin B Rye wrote: > Maybe instead of saying "use the system's initial user account to > become root" it should say "allow the system's initial user account > to gain administrative privileges"? I'm not sure. Oh, and we might > even want to mention the

Bug#1064617: Passwords should not be changed frequently

On Tuesday, 5 March 2024 19:28:25 CET Cyril Brulebois wrote: > Philip Hands (2024-03-05): > > Cool, in that case I'll fix those two things and then use the result > > for the MR[1], and if the openQA test runs look OK, will merge that. > > Only skimmed over it, but that looks sensible, thanks

Bug#1064617: Passwords should not be changed frequently

On Monday, 4 March 2024 22:30:57 CET Holger Wansing wrote: > > https://wiki.debian.org/Passwords doesn't exist (yet), but it's an easy to > > remember URL and we'd have all the space we need to give proper advise? > > Would need to check if that fits in the relevant screens (I want to avoid >

Bug#1060254: mumble: please make the build reproducible

On zondag 11 februari 2024 14:43:49 CET you wrote: > I went ahead and send your patch upstream and that got accepted. > So I'm attaching a/your patch with all the DEP-3 headers set. There's now a new release/tag v1.5.613 which includes this fix :) signature.asc Description: This is a digitally

Bug#1064617: Passwords should not be changed frequently

On Monday, 4 March 2024 10:43:59 CET Holger Wansing wrote: > >Regarding the password advice, I ended up concluding that it's pretty > >unlikely that anything we say at this point will have any effect on > >people's behaviour, but then I'm probably just an old cynic. Also, I > >failed when trying

Bug#1065404: virt-manager: Cannot load AooArmor profile

Package: virt-manager Version: 1:4.1.0-3 Severity: normal Dear Maintainer, I moved the `/var/lib/libvirt/images` directory to a new disk at `/libvirt/images` and created a symlink from the former to the later. The 3 VM disk images were working at the old location but at the new location I get

Bug#1065247: new lighttpd serves mangled file names

Glenn Strauss wrote: > This will be fixed in the next version of lighttpd, and I'll probably > submit a patch to Debian sooner. That would be awesome!!! Thanks, Erik -- -- Erik de Castro Lopo http://www.mega-nerd.com/

Bug#1065247: new lighttpd serves mangled file names

Hi, I have included the config at the bottom of this email. The files are being served from an ext4 filesystem. I have noticed something odd though. I created a directory which when served by lighttpd in Firefox looks like: Index of /test/ ../ - Directory This is just

Bug#1065247: new lighttpd serves mangled file names

Erik de Castro Lopo wrote: > Hi, > > I have included the config at the bottom of this email. > > The files are being served from an ext4 filesystem. > > I have noticed something odd though. I created a directory which when > served by lighttpd in Firefox looks like: I

Bug#1064617: Passwords should not be changed frequently

On Saturday, 2 March 2024 21:07:34 CET Philip Hands wrote: > I don't actually care very much whether we encourage sudo use. A person who I consider very knowledgeable deliberately went for sudo and disabled the root account for security reasons. It was an image provided by him that I ended up

Bug#1065247: new lighttpd servers mangled file names

uot;, ".pl", ".fcgi" ) compress.cache-dir = "/var/cache/lighttpd/compress/" compress.filetype = ( "application/javascript", "text/css", "text/html", "text/plain" ) include_shell "/usr/share/lighttpd/create-mime.conf.pl" include_shell "/usr/share/lighttpd/include-conf-enabled.pl" -- no debconf information -- -- Erik de Castro Lopo http://www.mega-nerd.com/

Bug#1064617: Passwords should not be changed frequently

Hi, On Friday, 1 March 2024 20:46:49 CET Holger Wansing wrote: > Philip Hands wrote (Fri, 01 Mar 2024 06:46:27 +0100): > > If you want to make a constructive contribution, how about suggesting a > > wording that reflects the advice that you think would be most useful to > > the people that

Bug#1064617: Passwords should not be changed frequently

Hi Philip, On Friday, 1 March 2024 06:46:27 CET Philip Hands wrote: > Having helped people to install Linux for ~30 years, I'd say that it's > the norm for people to be almost incapable of coming up with a decent > password if they were not expecting the question. I fully agree that most people

Bug#1064617: Passwords should not be changed frequently

On Thursday, 29 February 2024 23:13:55 CET Holger Wansing wrote: > > in which I'm recommending setting no password for root, which then gives > > the initial user 'sudo' membership[1]. > > What about the "Allow login as root?" question (only shown in expert mode), > which is asked directly before

Bug#1064879: systemd: User sessions started from system scope have no journal.

Biebl Sent: Tuesday, February 27, 2024 12:11:12 PM To: 1064...@bugs.debian.org; Timon de Groot Subject: Re: systemd: User sessions started from system scope have no journal. Control: tags -1 + moreinfo unreproducible On Tue, 27 Feb 2024 09:18:02 +0100 Timon de Groot wrote: > Package: syst

Bug#1061701: nss-pam-ldapd: install PAM and NSS modules into /usr

On Sun, 2024-01-28 at 20:44 +0100, Michael Biebl wrote: > We want to finalize the /usr-merge via DEP17 by moving all files to > /usr. nss-pam-ldapd installs files into /lib; these should be moved > into the respective canonical locations in /usr/. > > Please find a patch attached. It has been

Bug#1064579: new git url for non-free firmware

Control: tag -1 moreinfo On Saturday, 24 February 2024 14:16:53 CET Harald Dunkel wrote: > Package: firmware-iwlwifi > Version: 20230625-2 > > The source URL mentioned in the copyright file doesn't work anymore. Which URL do you mean?

Bug#1035880: radeon: radeon driver only partial support of pipelines

Control: reassign -1 src:linux 5.10.178-1 On Wednesday, 10 May 2023 15:41:44 CET Christian Kiss wrote: > Package: firmware-amd-graphics > Version: 20210315-3 > > kernel.log reports that radeon: 1 quad pipes, 2 z pipes initialized. > the gpu an rv530 has atleast double to 4 of these each. > >

Bug#988335: RTL8125B Failure of key exchange and association

Control: tag -1 moreinfo On Mon, 10 May 2021 18:13:43 + static wrote: > Package: firmware-realtek > Version: 20210315-2 > > I am trying to install from scratch firmware-edu-bullseye-DI-rc1-amd64- > BD-1.iso (also tried on debian-bullseye-DI-rc1-amd64-DVD-1.iso but interface > is not

Bug#949436: firmware-iwlwifi: Got an HT rate (flags:0x88/mcs:15) for a non data frame

Control: tag -1 moreinfo On 20 Jan 2020 22:32:26 +0100 Patrice Duroux wrote: > Package: firmware-iwlwifi > Version: 20190717-2 > > I am reporting this «exception» here without being sure this is the right > package or if it has been already reported (not easy to check). > > [ 48.335755]

Bug#949161: firmware-ti-connectivity: please include TIInit_10.6.15.bts

On Fri, 17 Jan 2020 17:24:14 +0200 Sicelo wrote: > Package: firmware-ti-connectivity > Version: 20190717-2 > > Please include TIInit_10.6.15.bts [1], which is needed for bluetooth on > the Motorola Droid 4 and similar boards. Similar files are already part > of the debian package, and the

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

Control: retitle -1 firmware-iwlwifi: Please update to version 20230804 On Sunday, 11 February 2024 18:56:23 CET Diederik de Haas wrote: > It could/might be there would be some improvement somewhere with newer > firmware, but as long as things keep working that is fine. > Consequen

Bug#1062817: firmware-amd-graphics: Invalid UVD handle causes the graphics driver to crash

Control: tag -1 moreinfo On Saturday, 3 February 2024 17:33:32 CET Aly Ghobashy wrote: > Package: firmware-amd-graphics > Version: 20230210-5 > >* What led up to the situation? > opening a video file with VLC >* What exactly did you do > video file to open normally. >

Bug#1061321: firmware-nonfree: Important changes coming up with upstream version 20230919

On maandag 22 januari 2024 15:42:48 CET you wrote: > I'm currently working on an update for upstream version 20230919, based > upon MR86 (Release 20230804) [1], which itself is based upon MR85 > (Update to 20230625) [2] and I'm running into some major issues: > > 1) Salsa's CI now always fails as

Bug#1056056: linux-image-6.1.0-13-amd64: After a 'warm' reboot the disk is missing (not detected by the bios) on a HP t640

On Tuesday, 20 February 2024 09:22:06 CET Ben Mesman | Spark Narrowcasting wrote: > mmc: sdhci-pci-o2micro: Fix a warm reboot issue that disk can't be > detected by BIOS > ... > Link: > https://lore.kernel.org/r/20240203102908.4683-1-fredaibayhubt...@126.com > > I'm still waiting for the

Bug#1062798: src:mumble: fails to migrate to testing for too long: autopkgtest failure

On Sat, 3 Feb 2024 11:52:03 +0100 Paul Gevers wrote: > Source: mumble > Version: 1.3.4-4 > Severity: serious > Control: close -1 1.5.517-1 > Tags: sid trixie > User: release.debian@packages.debian.org > Usertags: out-of-sync > > Dear maintainer(s), > > The Release Team considers packages

Bug#1064033: ITP: asn -- network OSINT CLI ASN, RPKI, BGP, Geo, Recon, Trace

Package: wnpp Severity: wishlist Owner: "Marcos Rodrigues de Carvalho (aka oday)" X-Debbugs-Cc: debian-de...@lists.debian.org, marcosrcarvalh...@gmail.com * Package name: asn Version : 0.75.3 Upstream Contact: Adriano nitefood * URL : https://github.com/ni

Bug#1063916: RFP: freenginx -- a fork of nginx maintained by Maxim Dounin and the development community

to even guess which one would make sense to stick to)... There are other potential issues as well, it is best to wait a couple months at the very least. -- Henrique de Moraes Holschuh

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

On Thu, Feb 15, 2024, at 15:45, Mario Limonciello wrote: > 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 >> men

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

bin Is the amd_pmf driver functional without that symlink ? -- Henrique de Moraes Holschuh

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

On Tue, Feb 13, 2024, at 17:04, Diederik de Haas wrote: > I'll add the `amdtee` dir to `Files-Excluded` in firmware-nonfree and > Henrique > can add those files to the amd64-microcode package. Agreed. For now, let's have amd64-microcode package to be the "SoC-and-CPU-rel

Bug#1063370: vulkan-tools: Fails to build from source.

Control: tag -1 upstream fixed-upstream On Tue, 06 Feb 2024 13:45:14 -0800 Elizabeth Loss-Cutler-Hull wrote: > Package: vulkan-tools > Version: 1.3.268.0+dfsg1-1 > Severity: serious > Tags: ftbfs > Justification: fails to build from source (but built successfully in the past) > > In file

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

On Tuesday, 13 February 2024 17:59:55 CET Mario Limonciello wrote: > > I think it's important to facilitate people having f.e. the following > > combos: > > - Intel CPU with AMD GPU > > - AMD CPU with Nvidia GPU > > - AMD CPU with AMD GPU (discrete or integrated) > > > > Preferably without

Bug#1063845: unbound: Package 1.19.1 to fix CVE-2023-50387 and CVE-2023-50868

Source: unbound Version: 1.18.0-2 Severity: important Tags: security X-Debbugs-Cc: Debian Security Team -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Today 2 remote exploitable High Severity CVE's were published and unbound has released version 1.19.1 to fix those. Relevant links:

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

On Monday, 12 February 2024 21:25:35 CET Mario Limonciello wrote: > > My logic was that this is about AMD TEE (Trusted Execution Environment), > > which I *assumed* is part of/tied to the CPU. This thought is based on > > that on ARM platforms, you also have a TEE and that is part of the CPU > >

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

On Monday, 12 February 2024 19:38:12 CET Henrique de Moraes Holschuh wrote: > On Fri, Feb 2, 2024, at 13:50, Diederik de Haas wrote: > > This is about "AMD Platform Management Framework TA", which seems to be > > about AMD CPU features. The first (and

Bug#1063789: RFS: anew/0.2-1 -- Tool for adding new lines to files, skipping duplicates (program)

w upstream release. Regards, Marcos Rodrigues de Carvalho (aka oday)

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

On Fri, Feb 2, 2024, at 13:50, Diederik de Haas wrote: > This is about "AMD Platform Management Framework TA", which seems to be > about AMD CPU features. The first (and only) commit message has this: > > ``` > amd_pmf: Add initial PMF TA for Smart PC Solution Builder

Bug#1060706: linux-image-6.1.0-17-amd64: intel i225 NIC loses PCIe link, network becomes unusable)

Control: forwarded -1 https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0...@its-lehmann.de/ On Monday, 12 February 2024 12:56:45 CET Arno Lehmann wrote: > Reported upstream, see > > https://lore.kernel.org/netdev/3179622f-7090-4a57-98ba-9042809a0d2a@its-lehm > ann.de/T/#u

Bug#1063660: the amdgpu module is missing from the kernel

100, Diederik de Haas пишет: > > Control: tag -1 moreinfo > > > > On Saturday, 10 February 2024 17:41:43 CET Nikolay Sabelnikov wrote: > > > Package: linux-image-amd64 > > > Version: 6.1.76-1 > > > > > > > update-initramfs: Generating /boot/in

Bug#1063660: the amdgpu module is missing from the kernel

Control: tag -1 moreinfo On Saturday, 10 February 2024 17:41:43 CET Nikolay Sabelnikov wrote: > Package: linux-image-amd64 > Version: 6.1.76-1 > > > update-initramfs: Generating /boot/initrd.img-6.1.0-18-amd64 > > W: Possible missing firmware /lib/firmware/amdgpu/ip_discovery.bin for > > module

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

Control: reassign -1 firmware-iwlwifi 20230625-2 Control: retitle -1 firmware-iwlwifi: Please update to version 20230919 On Sunday, 11 February 2024 16:34:16 CET Miguel Angel Rojas wrote: > > While 'annoying', this is expected behavior. It tries to load the newest > > (-83) > Yes, this is the

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

Hi Miguel, On Sunday, 11 February 2024 16:03:20 CET Miguel A. Rojas wrote: > I forgot to include you the dmesg as promised: > > [2.235947] iwlwifi :00:14.3: enabling device ( -> 0002) > [2.237778] iwlwifi :00:14.3: Detected crf-id 0x1300504, cnv-id > 0x80401 wfpm id

Bug#1062703: firmware-realtek: Direct firmware load for rtl_nic/rtl8125b-2.fw failed with error -2

On Sunday, 11 February 2024 11:11:53 CET Miguel Angel Rojas wrote: > My bad. Let me explain again. Taking into account the firmware errors: > >- Realtek messages are fixed now. There are no actions to be done here. Good. >- iwlwifi: If you are still working on a new version containing

Bug#1063711: mumble: autopkgtest fixes (fixes #1062798)

/XblvOeH7bbgUCZcjZDQAKCRDXblvOeH7b bg4bAQDunBxsV2mW/2MBftkaGikwal4ohr8UDB6q+f8clwHCyQD/WUyTgCg7W7E/ 6+IgJ7KLVdDVyVNaOogSyRQNDluUmAY= =u+Ks -END PGP SIGNATURE- >From ca324636bd152a418f5f7a60c166a4ea30d4e37b Mon Sep 17 00:00:00 2001 From: Diederik de Haas Date: Mon, 6 Mar 2023 11:56:30 +0100 Subj

  1   2   3   4   5   6   7   8   9   10   >