On Tuesday, 31 May 2022 18:52:44 CET Diederik de Haas wrote:
> Now that 989153 and 989181 have been merged into this one and the bug is
> reopened, then the next question becomes: how to proceed.
Ping?
signature.asc
Description: This is a digitally signed message part.
Control: tag -1 moreinfo
On 5 Jul 2022 18:21:27 +0500 Alexandr Podgorniy wrote:
> I tried 5.18.0-2-amd64 kernel recently and noticed that it doesn't go to
> sleep when Bluetooth mouse connected. Otherwise it's fine. Not tried
> 5.18.5 yet.
FTR: 5.18.5 is 5.18.0-2 and if that didn't fix it, the
Control: tag -1 moreinfo
On woensdag 22 juni 2022 00:20:22 CET you wrote:
> Kernel 5.18.3 contains (at least) 2 patches related to dpaa2-eth.
> Kernel 5.18.5-1 (currently in Sid) does contain quite a few fixes vs 5.18.2,
> so it would be useful to verify if that fixes your issue. I don't know when
Control: retitle -1 Please add brcmfmac43456-sdio.* files as it's not just used
in RPi devices
On 10 Nov 2022 11:40:06 +0100 Diederik de Haas wrote:
> On Sat, 9 Apr 2022 17:52:00 -0500 Gunnar Wolf wrote:
> > Please note I'm currenlty shipping the required files in
>
On maandag 5 december 2022 19:29:46 CET Alexandr Podgorniy wrote:
> I don't know, but current 6.0.10-1 kernel works fine. Issue disappeared
> after few updates, 5.19 kernel worked fine as far as i remember.
Can you find out the lowest kernel version in which it was fixed?
Or would you rather just
Control: tag -1 moreinfo
On Saturday, 25 June 2022 05:33:01 CET Ian Turner wrote:
> On this kernel (linux-image-5.10.0-13-amd64 and previous) I experience
> occasional kworker kernel hangs with numerous other associated
> uninterruptable processes.
>
> * The issue is resolved in linux-image-5.16.
Control: found -1 5.15.5-2~bpo11+1
On Thursday, 30 June 2022 01:10:05 CET Douglas Silva wrote:
> I've tested 5.15.5-2~bpo11+1 and it's reproducible.
signature.asc
Description: This is a digitally signed message part.
On Sunday, 30 October 2022 09:34:25 CET Salvatore Bonaccorso wrote:
> > I can no longer reproduce this. Currently running Ubuntu 22.10 with
> > kernel 5.19.0-23-generic. C-states enabled in the BIOS.
>
> But what about Debian's kernels? Are you able to reproduce your issue
> still with most recent
On 3 Nov 2022 08:00:00 + Chris Knadle wrote:
> tags 1017780 + help
I've mentioned this bug in #debian-mentors (on OFTC), but it could help if
you'd join that channel and ask yourself so you can get direct feedback on
direct questions/issues you're encountering.
HTH,
Diederik
signature.a
On Tuesday, 6 December 2022 13:39:23 CET Diederik de Haas wrote:
> On 3 Nov 2022 08:00:00 + Chris Knadle wrote:
> > tags 1017780 + help
>
> I've mentioned this bug in #debian-mentors (on OFTC), but it could help if
> you'd join that channel and ask yourself so yo
On Tuesday, 6 December 2022 12:54:31 CET Olivier Mehani wrote:
> NFS would still be accessible as before (:
What's the version of NFS you're using?
signature.asc
Description: This is a digitally signed message part.
Control: found -1 5.10.149-2
On Tuesday, 6 December 2022 15:27:11 CET bob wrote:
> It still occurs with
> Linux AsusTUFgX570 5.10.0-19-amd64 #1 SMP Debian 5.10.149-2 (2022-10-21)
Thanks, updated bug accordingly.
It may be useful to keep testing new updates, also from backports, but I
suspect thi
Control: tag -1 moreinfo
On Monday, 1 August 2022 02:07:02 CET Linas Vepstas wrote:
> I just attempted a hand-build of kernel 5.18.15 and it exhibits exactly the
> same failure, the same stack traces.
Does the problem still occur with a recent 6.0 kernel?
There have recently also been uploads of
On Tue, 11 Apr 2017 23:28:41 +0100 Ben Hutchings wrote:
> Control: severity -1 important
> Control: severity 824442 important
>
> On Tue, 2017-04-11 at 23:20 +0200, Aurelien Jarno wrote:
> > On 2017-04-11 03:35, Ben Hutchings wrote:
> > > Control: tag -1 moreinfo
> > >
> > > On Mon, 10 Apr 2017
On Tuesday, 6 December 2022 23:10:32 CET Olivier Mehani wrote:
> >What's the version of NFS you're using?
>
> The clients are recent Linux hosts, and one Kodi 19.x. I don't specify a
> version in either their fstab or the server's exports.
Sorry, I meant the package version of the NFS server
sig
On Friday, 10 June 2022 14:16:00 CET Diederik de Haas wrote:
> If I understand the forwarded thread correctly, the reported symptoms went
> completely away by updating firmware files from
> https://github.com/RPi-Distro/ firmware-nonfree/tree/master/brcm on
> 2021-03-29.
> Those
Control: tag -1 moreinfo
Hi Hank,
On Tuesday, 13 September 2022 17:48:22 CET Hank Barta wrote:
> Package: src:linux
> Version: 5.19.6-1
>
>* What led up to the situation?
>
> Apparent inability to initialize/connect to the SD card H/W. This leads to
> the message below that is repeated abou
Control: tag -1 moreinfo
On Mon, 03 Sep 2012 14:24:47 -0700 Russ Allbery wrote:
> Ben Hutchings writes:
> > On Mon, Sep 03, 2012 at 12:21:06PM -0700, Russ Allbery wrote:
> > [...]
> >> linux-libc-dev maintainers, when upgrading to squeeze, there is
> >> currently nothing preventing linux-libc-de
On Wednesday, 7 December 2022 05:57:55 CET Christoph Anton Mitterer wrote:
> A patch has now been posted for dash at:
> https://lore.kernel.org/dash/y47zlpwkqy+ji...@gondor.apana.org.au/
> which is apparently scheduled to be merged into their git.
FTR: a v2 of that patch has been posted:
https://l
Hi Chris,
On Wednesday, 7 December 2022 10:13:00 CET Chris Knadle wrote:
> > So I'd suggest skipping 1.4 altogether and go straight for 1.5.
> > You _could_ now release a development snapshot (to Experimental?),
> > especially if the package needs to go through NEW and then the update to
> > the 1
Control: tag -1 -fixed-upstream
Control: tag -1 moreinfo
On 13 Feb 2019 01:14:36 + Chris Knadle wrote:
> retitle 921617 Mumble echo canceler leaks memory
> forwarded 921617 https://github.com/mumble-voip/mumble/issues/3379
> thanks
The forwarded issue was closed without a fix, so removing th
On Wednesday, 7 December 2022 10:13:00 CET Chris Knadle wrote:
> What I really need is a Debian source package that uses CMake to see an
> example of how to build a package. I'm looking at list of packages that
> reverse depend on cmake, maybe I can find a Debian source package that
> build-depends
On Thursday, 8 December 2022 09:39:40 CET Marco Moock wrote:
> Package: src:linux
> Version: 6.0.10-2
>
>My Logitech Inc. QuickCam Communicate STX USB Webcam 046d:08d7 can't
>use USB 2.0, although the manufacturer says it supports it.
Has it worked properly before with an older kernel? If
Control: tag -1 upstream
On Thursday, 8 December 2022 12:48:08 CET Marco Moock wrote:
> > Has it worked properly before with an older kernel? If so, which?
>
> No, it is a general problem.
Tagging the bug accordingly
On Thursday, 8 December 2022 09:39:40 CET Marco Moock wrote:
>My Logitech
Control: severity -1 important
Control: forwarded -1
https://lore.kernel.org/linux-scsi/y1jkuktjvyrow...@eldamar.lan/
Control: merge -1 1022126
On Monday, 31 October 2022 13:44:05 CET Taavi Ansper wrote:
> Yes we are using xen virtualization
Merging it with 1022126 then
signature.asc
Descriptio
Control: forwarded -1
https://lore.kernel.org/linux-scsi/y1jkuktjvyrow...@eldamar.lan/
Control: merge -1 1022126
On Thursday, 8 December 2022 15:27:49 CET Dröszler Gábor wrote:
> Package: src:linux
> Version: 5.10.149-2
> Severity: important
>
> Debian Bullseye not boot with XEN, linux-image-5.1
Control: tag -1 =upstream
signature.asc
Description: This is a digitally signed message part.
Control: tag -1 moreinfo
On Sunday, 3 July 2022 14:40:36 CET Jean-Marc LACROIX wrote:
> Package: linux-image-5.18.0-2-arm64
> Version: 5.18.5-1
>
> Please find in attached file success story (!) on recent boot for
> target rock64 (pine64) with 64 Go class10 MMC card with Debian 11.3
> Bu
Control: reassign -1 debbugs 2.6.0
On Sat, 10 Dec 2022 13:56:54 +0500 Akbarkhon Variskhanov
wrote:
> Package: bugs.debian.org
> Severity: minor
> Tags: newcomer patch
> X-Debbugs-Cc: akbarkhon.variskha...@gmail.com
signature.asc
Description: This is a digitally signed message part.
On Sunday, 11 December 2022 14:16:04 CET Bernhard wrote:
> igc :04:00.0 eno1: PCIe link lost, device now detached
https://lore.kernel.org/all/20221031170535.77be0...@kernel.org/ looks relevant
signature.asc
Description: This is a digitally signed message part.
Control: tag -1 -moreinfo
On Wednesday, 1 June 2022 01:27:32 CET Diederik de Haas wrote:
> What's the current status wrt this bug?
Just saw upstream commit 630dc25e43dacfb5af94cd41532e77c47ec1caff which should
become part of 6.1-rc9 and/or 6.1 and it would be interesting to know if tha
On Tuesday, 13 December 2022 15:40:04 CET Adi Kriegisch wrote:
> Source: linux
> Version: 5.10.158-1
>
> we just upgraded our xen test cluster's kernel to the latest kernel from
> s-p-u and noticed that network communication is broken. We do have a
> 'classic' setup with bridges in dom0. After upg
Control: found -1 6.0.12-1
On Thursday, 15 December 2022 10:09:27 CET Bernhard wrote:
> This bug still exist in Daily image from today (2022-12-15).
That's using the 6.0.0-6-armmp kernel.
signature.asc
Description: This is a digitally signed message part.
On Thursday, 15 December 2022 10:43:22 CET Adi Kriegisch wrote:
> after the discussion about the root cause of this issue on the linux-scsi
> mailing list[1] there was one simple patch submitted to this list[2] that
> just changes the logic of the selection of the dma mask: in case of a 64bit
> hos
On Thursday, 15 December 2022 11:47:11 CET Diederik de Haas wrote:
> On Thursday, 15 December 2022 10:43:22 CET Adi Kriegisch wrote:
> > after the discussion about the root cause of this issue on the linux-scsi
> > mailing list[1] there was one simple patch submitted to this list[2
On Saturday, 22 May 2021 00:46:55 CET Vagrant Cascadian wrote:
> Package: src:linux
> Version: 5.10.28-1
> File: /boot/vmlinuz-5.10.0-6-armmp-lpae
> Control: block 986767 by -1
>
> The ethernet bridge fails to work on 5.10.x (also tried 5.10.38-1),
> but works fine on 4.19.x from buster. (This was
found 1026174 linux/6.0.10-2
signature.asc
Description: This is a digitally signed message part.
Hi Jonas,
On Tuesday, 13 December 2022 10:55:18 CET Jonas Smedegaard wrote:
> perhaps I can point you to other examples as well
I'd love to have several examples to look at :-)
Especially if you know of one (or more) who write extensive commit messages
explaining the reasons/rational of their ch
On 13 Sep 2022 09:00:07 -0300 Antonio Terceiro wrote:
> Source: ruby-safe-yaml
> Version: 1.0.5-2
> Justification: FTBFS
> Usertags: ruby3.1
>
> We are about to start the ruby3.1 transition in unstable. While trying to
> rebuild ruby-safe-yaml with ruby3.1 enabled, the build failed.
>
> Relevant
Source: wlroots
Version: 0.16.0-2
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I just saw that upstream released wlroots 0.16.1 last week.
AFAICT it has some important fixes, so if the package could be upgraded
to that version, that would be appreciated.
Cheers,
Diederik
On Monday, 2 January 2023 07:03:10 CET Vagrant Cascadian wrote:
> Also wifi related, on first boot, there was no wifi device configured,
> and I did not happen to install anything that pulled in
> network-manager or something similar. I am not sure I even did an
> install using wifi before, so this
On 14 Apr 2022 15:45:26 -0700 Vagrant Cascadian wrote:
> On 2021-08-08, Sebastian Ramacher wrote:
> > On 2021-03-13 20:05:47 -0800, Vagrant Cascadian wrote:
> >> Source: ffmpeg
> >> Severity: normal
> >> Tags: patch
> >> User: reproducible-bui...@lists.alioth.debian.org
> >>
> >> The build path i
On Tuesday, 3 January 2023 19:06:41 CET Vagrant Cascadian wrote:
> Looks like some new source of non-determinism was added in 5.0.x, you
> can see bookworm (which does not test build paths) was reproducible
> until 5.0.x started getting tested in bookworm in June of 2022:
>
> https://tests.reprod
On Wednesday, 4 January 2023 16:39:33 CET Renato Gallo wrote:
> 5.10 should be EOL by now
Please refrain from comments like that.
It doesn't help at all and is also plain false.
signature.asc
Description: This is a digitally signed message part.
On Wednesday, 4 January 2023 15:38:32 CET Tim Düsterhus wrote:
> Unfortunately the setting `1` allows direct write access to the devices,
> whereas the previous and to my understanding the default setting of `-1`
> only allows read access, making this a safer option.
>
> It appears that aacraid's
On Tuesday, 3 January 2023 22:14:10 CET Santiago Vila wrote:
> --
> From this definition it follows that packages of required priority are not
> necessarily build essential, as it is possible for some them not to be
... for some *of* them ..
Package: aerc
Version: 0.13.0-1+b1
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Earlier today the release of version 0.14.0 was announced:
https://lists.sr.ht/~rjarry/aerc-announce/%3C20230104163910.PQQOJR7R3JWE%40ringo%3E
And hereby the request to update the aerc package i
Control: tag -1 upstream
Control: severity -1 normal
On Wed, 04 Jan 2023 12:04:52 +0100 xevilstar wrote:
> Package: linux-image-6.2.0-rc2
> Version: 6.2.0-rc2-1
>
> I am testing linux kernel 6.2-rc2
That is great, but you should report any issues you find to the relevant
upstream maintainers.
Package: fwupd
Version: 1.8.9-2
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
When I check the status of `fwupd.service` I see the (error?) message as
mentioned in the Subject.
It doesn't sound good, although I have no idea if this has any effect on
the workings of `fwupd`. I h
On Sun, 25 Dec 2022 12:49:27 +0100 Helge Deller wrote:
> Package: rrdtool
> Version: 1.7.2-4
> Tags: hppa, patch, ftbfs
> Severity: important
>
> The command "rrdtool list /some/dir/" fails on 32-bit arches at runtime
> if those are running on huge discs, e.g. see failing "list1" testcase
> on hp
On Thursday, 5 January 2023 22:16:15 CET Helge Deller wrote:
> But it seems to fail differently for you
> https://salsa.debian.org/diederik/rrdtool/-/jobs/3746600 :
>
> /builds/diederik/rrdtool/debian/output/source_dir/src/rrdtool list
> FAILED: (rc=1) list without parameters displays Usage
> FA
Control: tag -1 upstream patch
On Wed, 03 Mar 2021 16:16:49 + Matthias Klose wrote:
> Package: src:qpxtool
> Version: 0.8.1-1
> Usertags: ftbfs-gcc-11
>
> The package fails to build in a test rebuild on at least amd64 with
> gcc-11/g++-11, but succeeds to build with gcc-10/g++-10.
>
> [...]
Control: found -1 6.0.10-1
On Monday, 9 January 2023 13:20:08 CET Julian Groß wrote:
> when running Linux Kernel version 6.0.12 or 6.0.10, my system seemingly
> randomly freezes due to the filesystem being set to read-only due to an
> issue with my nvme controller.
> The issue does *not* appear o
Control: forwarded -1
https://lore.kernel.org/all/877f41ovlu@free-electrons.com/
Hi Ben,
On 07 Mar 2017 18:16:45 +0100 Gregory CLEMENT
wrote:
> On lun., févr. 20 2017, Ben Hutchings wrote:
> > On Mon, 2017-02-20 at 17:50 +0100, Thomas Petazzoni wrote:
> >> On Mon, 20 Feb 2017 16:40:25 +0
On Tue, 23 Nov 2021 07:58:32 +0100 Ard Biesheuvel wrote:
> I don't see a reason to revert the default upstream. The feature
> remains deprecated (and in the longer term, the EFI handover protocol
> may be deprecated and removed as well), so the earlier the bootloaders
> adapt, the better it is.
>
On Wednesday, 11 January 2023 08:33:29 CET Didier 'OdyX' Raboud wrote:
> Package: src:linux
> Version: 6.1.4-1
> Severity: serious
>
> Since booting 6.1.0-1, the 2nd DisplayPort output from my Lenovo Docking
> Station doesn't get any output.
Can you try the previous versions of the 6.1.x series w
Control: found -1 6.0~rc7-1~exp1
On Wednesday, 11 January 2023 15:04:30 CET Julian wrote:
> 6.0~rc7-1~exp1 is also broken.
>
> I will go through https://wiki.debian.org/DebianKernel/GitBisect and see
> what I can find. Thankfully the documentation is quite comprehensive.
That would be great, tha
On Wednesday, 11 January 2023 19:28:25 CET Julian Groß wrote:
> On Mon, 09 Jan 2023 14:09:30 +0100 Diederik de Haas
> wrote:
> > https://wiki.debian.org/DebianKernel/GitBisect describes a procedure
> > to find the exact commit which introduced the issue you reported, but it&#
Control: forwarded -1
http://lists.infradead.org/pipermail/linux-nvme/2023-January/037384.html
On Thursday, 12 January 2023 12:11:57 CET Julian wrote:
> The message to linux-nvme finally came through and the thread is here:
> http://lists.infradead.org/pipermail/linux-nvme/2023-January/037384.htm
On Thursday, 12 January 2023 12:03:24 CET Sjoerd Simons wrote:
> Fwiw there is a general regression with AMDGPU MST on linux 6.1; tracked
> upstream here:
> https://gitlab.freedesktop.org/drm/amd/-/issues/2171
Thanks! About an hour ago the suggested fix was to revert commit
4d07b0bc403403438d9cf
Hi Julian,
On Thursday, 12 January 2023 12:11:57 CET Julian wrote:
> The message to linux-nvme finally came through and the thread is here:
> http://lists.infradead.org/pipermail/linux-nvme/2023-January/037384.html
The following paragraph may not be ideally formulated:
"Currently, I am using git
Source: linux
Version: 6.1.4-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The DeviceTree files (*.dtb) as shipped with the Debian kernel have the
executable bit set, but there is absolutely no need for that.
Lintian rightfully complains about it (executable-not-elf-or-script
Package: firmware-brcm80211
Version: 20221012-1
Severity: normal
X-Debbugs-Cc: pkg-raspi-maintain...@lists.alioth.debian.org
With a freshly made RPi 3 Bookworm image (with [1]) I booted up my
RPi 3B+ and noticed the following error in `dmesg`:
[ 19.801109] brcmfmac mmc1:0001:1: firmware: failed
Package: bluez-firmware
Version: 1.2-7
Severity: normal
X-Debbugs-Cc: pkg-raspi-maintain...@lists.alioth.debian.org
With a freshly made RPi 3 Bookworm image (with [1]) I booted up my
RPi 3B+ and noticed the following error in `dmesg`:
[ 21.159415] bluetooth hci0: firmware: failed to load
brcm/
Control: tag -1 -moreinfo upstream
Control: found -1 20221012-1
On Friday, 11 November 2022 20:41:56 CET Rui Dinis wrote:
> After further testing with firmware-misc-nonfree 20220913-1 and
> firmware-misc-nonfree 20221012-1, the problem still persists the machine
> crashes after several minutes or
Package: mpv
Version: 0.34.1-1+b5
Severity: wishlist
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Upstream has just released v0.35.0 and it would be great if that could
be packaged for Debian.
TIA,
Diederik
- -- System Information:
Debian Release: bookworm/sid
APT prefers testing
APT p
Control: reopen -1
Control: found -1 1.1.1-2
On Mon, 19 Sep 2022 18:09:44 +0700 Arnaud Rebillout wrote:
> at the moment debos (and fakemachine) is broken in unstable:
And it's still broken, but now also in Testing
I installed debos, but without systemd-resolved:
root@prancing-pony:~# aptitude
user debian-rele...@lists.debian.org
usertag 900821 + bsp-2022-11-nl-tilburg
found 900821 5.10.70-1
fixed 900821 5.10.84-1
thanks
We have/had a BSP in Tilburg today and I went to work on this bug.
With success :-)
I first created a new Bullseye VM with virt-manager using the
debian-11.5.0-amd64-
Control: found -1 5.14.9-2 5.15.5-2
Control: fixed -1 5.15.15-2 5.16.11-1 5.18.16-1 6.0.3-1
On zaterdag 19 november 2022 21:22:46 CET Diederik de Haas wrote:
> found 900821 5.10.70-1
> fixed 900821 5.10.84-1
I continued testing with kernels from backports and updated metadata
accor
Control: found -1 5.14.9-2
Control: found -1 5.15.5-2
Control: fixed -1 5.15.15-2
Control: fixed -1 5.16.11-1
Control: fixed -1 5.18.16-1
Control: fixed -1 6.0.3-1
On zondag 20 november 2022 12:18:50 CET you wrote:
> Control: found -1 5.14.9-2 5.15.5-2
> Control: fixed -1 5.15.15-2 5.16.11-1 5.18
Control: notfound -1 4.9.88-1+deb9u1
Control: found -1 4.9.88-1
On zondag 20 november 2022 13:55:09 CET Salvatore Bonaccorso wrote:
> Seems the BSP was productive :).
Yeah, once I set up the VM and created the script, it was actually quite easy.
> If you have spare cycles, might you
> check if d
user debian-rele...@lists.debian.org
usertag 1020066 + bsp-2022-11-nl-tilburg
tag 1020066 + pending
thanks
On Sun, 18 Sep 2022 08:18:31 +0200 Lucas Nussbaum wrote:
> Source: tt-rss
> Version: 21~git20210204.b4cbc79+dfsg-1
> Severity: serious
> Justification: FTBFS
Merged "Relax libjs-prototype b
Control: found -1 4.9.88-1+deb9u1
Control: notfound -1 4.9.88-1
Hi Salvatore,
On zondag 20 november 2022 16:38:25 CET Salvatore Bonaccorso wrote:
> On Sun, Nov 20, 2022 at 04:26:45PM +0100, Diederik de Haas wrote:
> > Control: notfound -1 4.9.88-1+deb9u1
> > Control: found -1 4.
Control: reassign -1 src:tt-rss 21~git20210204.b4cbc79+dfsg-1
Control: tag -1 = bookworm ftbfs pending sid
Control: severity -1 serious
Control: merge -1 1020066
On 7 Sep 2022 01:15:32 +0100 Peter Michael Green wrote:
> Package: tt-rss
> Version: 21~git20210204.b4cbc79+dfsg-1
> Serverity: seri
Control: forcemerge -1 1020066
On woensdag 23 november 2022 18:39:05 CET you wrote:
> > merge -1 1020066
>
> Bug #1019296 [src:tt-rss] tt-rss - build-dependencies unsatisfiable
> Unable to merge bugs because:
signature.asc
Description: This is a digitally signed message part.
On dinsdag 29 november 2022 02:35:44 CET Moessbauer, Felix wrote:
> The reason is well documented in this link and this has already been
> fixed upstream in the 6.0.x branch.
In the upstream 6.0.4 release to be exact and part of Debian's 6.0.5-1 upload.
signature.asc
Description: This is a digita
Package: libc6
Version: 2.36-6
Severity: important
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Since upgrading to 2.36-6 I regularly, but not always, get network
resolution/connection failures, most visibly in Firefox, but the same
issue has also occured with qutebrowser and on different devi
acking System
Copies sent to:
Debian Bug Tracking System
Diederik de Haas
And also in KMail, I regularly get error message related to network
resolution, like "Could not connect to Sieve server".
Or sending this message: E-Mail Sending Failed:
"Failed to transport message.
Control: tag -1 moreinfo
On Saturday, 25 March 2023 15:27:52 CET Vivek K J wrote:
> I've been using a automount script (in /etc/fstab) to mount my
> windows NTFS partition in Debian Testing. But after updating to
> 6.1.0-6-amd64 the kernel doesn't boot and stucks at recovery mode. On
> commenting
Control: found -1 5.19~rc4-1~exp1
Control: forwarded -1
https://lore.kernel.org/bpf/20230118051443.78988-1-alexei.starovoi...@gmail.com/
On Saturday, 25 March 2023 16:00:47 CET Florian Lehner wrote:
> > Via https://snapshot.debian.org/binary/linux-image-amd64/ you can easily
> > test various kern
On Sunday, 26 March 2023 23:58:58 CEST Ken Milmore wrote:
> The upstream fix [1] to avoid the irksome error messages has been to replace
> a call to request_firmware() from the iwlwifi driver with
> firmware_request_nowarn() instead. This causes option flag FW_OPT_NO_WARN to
> be set inside the fir
On Monday, 27 March 2023 15:59:37 CEST Marcel Camijn wrote:
> We recently got new hardware with a new raid controller but noticed that the
> required module MPI3MR is not enabled. The latest uploaded kernel image has
> "#CONFIG_SCSI_MPI3MR is not set" in the config.
>
> The module seems to be incl
On Tuesday, 28 March 2023 00:21:59 CEST Ken Milmore wrote:
> > I don't know if it's also an upstream kernel issue or it's only caused by
> > Debian's patch, but AFAICT that patch needs to be revised to (at least)
> > account for the upstream change(s?) in firmware loading.
>
> AFAICT, it's just a
Control: reassign src:linux 6.1.15-1
On Wednesday, 29 March 2023 09:59:22 CEST Stefan K wrote:
> Package: linux-image-amd64
> Version: 6.1.15-1
Unstable has version 6.1.20-1, can you test whether the issue is present there
too?
signature.asc
Description: This is a digitally signed message part.
On Monday, 27 March 2023 17:35:25 CEST Diederik de Haas wrote:
> While looking into it, I did find some troubling aspects though.
> I noticed that in upstream's master branch there were quite some commits
> *after* 6.1 of which a reasonable amount has been backported to 6.1.
>
Control: reopen -1
On Tuesday, 21 March 2023 14:21:05 CEST Debian Bug Tracking System wrote:
> > In https://github.com/waydroid/waydroid/issues/811 I asked 'upstream'
> > for recommendations on which/how/what kernel modules to enable.
>
> In https://git.kernel.org/linus/9e18d0c82f0c07f2a41898d4ad
On Wednesday, 29 March 2023 22:59:13 CEST Diederik de Haas wrote:
> Control: reopen -1
>
> On Tuesday, 21 March 2023 14:21:05 CEST Debian Bug Tracking System wrote:
> > > In https://github.com/waydroid/waydroid/issues/811 I asked 'upstream'
> > > for rec
Control: found -1 6.1.20-1
> > Unstable has version 6.1.20-1, can you test whether the issue is present
> > there too?
> Yes, it still happens with 6.1.20-1..
Updating metadata accordingly
On Thursday, 30 March 2023 14:46:51 CEST Stefan K wrote:
> With Kernel 6.0.0-0.deb11.6-amd64 it works fine
On Friday, 31 March 2023 12:57:44 CEST Stefan K wrote:
> when I searching my error message I got a lot of hits..
> In arch it's solved:
> https://bugs.archlinux.org/task/76934
>
> the patch:
> https://gitlab.freedesktop.org/superm1/linux/-/commit/2145b4de3fea9908cda6be
> f0693a797cc7f4ddfc.patch
to the actual one which is para 4.2.2 and I have
attached a patch which reverts the referenced commit and that .patch file is
what you give as an argument to `bash debian/bin/test-patches`.
If you could try that to see if that indeed fixes the issue, that would be
very helpful.
HTH
>From 2e6223080905caf4c775680201700b2
Is it sufficient to apply the patch given by Diederik de Haas ?
I'm guessing you forgot to do the Preparation from 4.2.1
>Le 01/04/2023 à 15:28, Salvatore Bonaccorso a écrit :
>> Hi,
>>
>> On Sat, Apr 01, 2023 at 11:51:38AM +0200, Guy Durrieu wrote:
>>> Hello
On Saturday, 1 April 2023 17:44:21 CEST Guy Durrieu wrote:
> I am in trouble... I first did "Obtaining the kernel source", and at the
> end I got a /root/linux-source-6.1/ directory.
>
> Then I did "Rebuilding official Debian kernel packages" and
> "Preparation", and then I got among others a
> /
Control: tag -1 upstream
On Saturday, 1 April 2023 22:47:35 CEST Guy Durrieu wrote:
> I just finished to build the patched kernel.
Well done!
> After installing it, the system 6.1.0-7 boots again and run fine.
> Thus the source was well identified by Bjørn Mork.
This is great :-)
> I just had
On Sunday, 2 April 2023 00:24:26 CEST Diederik de Haas wrote:
> 2) The commit that Bjørn identified also contained a "Link:" tag:
> https://lore.kernel.org/r/20230105041059.39366-1-kvija...@amd.com
>
> The best thing to do is to respond to that thread and explain the issue y
On Saturday, 18 March 2023 23:10:39 CEST Diederik de Haas wrote:
On Monday, 3 April 2023 14:57:02 CEST Julien Cristau wrote:
> > Not sure why patchwork still shows v2 of the patch as v4 is available
> > here:
> > https://lore.kernel.org/all/20230308154244.722337-1-hdego...@redha
Hi Russ,
On Sat, 26 Nov 2022 08:47:59 -0800 Russ Allbery wrote:
> Russ Allbery writes:
> > Jean-Michel Vourgère writes:
>
> >> I'm using pod to generate man files in package rrdtool.
>
> >> I expected pod2man to generate the corect \: escape sequence, but it
> >> did not.
>
> [...]
>
> > Un
On Tuesday, 4 April 2023 13:11:16 CEST Julien Cristau wrote:
> On Mon, Apr 3, 2023 at 15:16:42 +0200, Diederik de Haas wrote:
> > On Saturday, 18 March 2023 23:10:39 CEST Diederik de Haas wrote:
> >
> > On Monday, 3 April 2023 14:57:02 CEST Julien Cristau wrote:
> >
On Wednesday, 5 April 2023 22:04:57 CEST Cyril Brulebois wrote:
> you should be able to activate os-prober via some configuration
> file under /etc (probably /etc/default/grub).
Correct, the setting is GRUB_DISABLE_OS_PROBER=false
/me wonders why that default changed ...
signature.asc
Descriptio
On Friday, 7 April 2023 23:15:03 CEST Debian Bug Tracking System wrote:
> > Comments:
> > 1. If the kernel installation requires the headers to function properly,
> > then they should probably be a package dependency.
>
> As said above, the kernel does need the headers installed.
Correction: the
UCZDCVcQAKCRDXblvOeH7b
buLOAP9yKZNz0+Vfk+Y186OcFVIpetwPWIr+XFEw8IVAFLs17QEA7OHU0vY4KWFs
1Wh7DR5LuMimmcbIQcKjxRz3Fdt/wQc=
=uIwT
-END PGP SIGNATURE-
>From 382c1e20b0809d5dd9dcba757e574b4bfbcca0dc Mon Sep 17 00:00:00 2001
From: Diederik de Haas
Date: Thu, 6 Apr 2023 18:10:12 +0200
Subject: [PATCH] u-boot
701 - 800 of 1765 matches
Mail list logo
