Bug#1064478: wireless-regdb: install firmware files into /usr

-07-30 22:10:23.0 +0200 +++ wireless-regdb-2022.06.06/debian/changelog 2024-02-22 22:52:06.0 +0100 @@ -1,3 +1,10 @@ +wireless-regdb (2022.06.06-1.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Install firmware files into /usr. (Closes: #-1) + + -- Michael Biebl

Bug#1058937: /usr-move: Do we support upgrades without apt?

Am 21.12.23 um 11:50 schrieb Christoph Berg: Re: Helmut Grohne Is it ok to call upgrade scenarios failures that cannot be reproduced using apt unsupported until we no longer deal with aliasing? If the answer is yes here, we'll close #1058937 (Ben's libnfsidmap1 bug) with no action calling the s

Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory

Am 12.07.22 um 20:54 schrieb Salvatore Bonaccorso: personally i would prefer if we can do it a regular kernel-team upload, there were some other changes pending. Will ping Ben on IRC to ask. Otherwise I guess the NMU is fine. I've seen the upload. Thank you both! OpenPGP_signature Descript

Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory

Am 12.07.22 um 20:54 schrieb Salvatore Bonaccorso: Hi Michael, On Tue, Jul 12, 2022 at 05:57:41PM +0200, Michael Biebl wrote: On Sat, 9 Jul 2022 21:02:50 +0200 Salvatore Bonaccorso wrote: On Thu, Jul 07, 2022 at 01:37:53PM +0200, Michael Biebl wrote: It would thus be great to have the patch

Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory

On Sat, 9 Jul 2022 21:02:50 +0200 Salvatore Bonaccorso wrote: On Thu, Jul 07, 2022 at 01:37:53PM +0200, Michael Biebl wrote: > It would thus be great to have the patch in [2] applied and uploaded soon. I > can offer to NMU if available time is an issue. With that patch MR filled:

Bug#1014319: depmod: WARNING: could not open modules.builtin.modinfo at /var/tmp/mkinitramfs_vBlw4a/lib/modules/5.18.0-2-amd64: No such file or directory

Control: severity -1 important On Mon, 04 Jul 2022 15:01:13 +1000 Konomi Kitten wrote: Package: initramfs-tools Version: 0.141 Severity: minor X-Debbugs-Cc: konomikit...@gmail.com When update-initramfs runs I receive the following message: depmod: WARNING: could not open modules.builtin.mod

Re: systemd bogus(?) remounts since upgrade to 249.5-1

reassign 996876 src:linux retitle 996876 filesystem being remounted supports timestamps until 2038 thanks On Wed, 20 Oct 2021 08:51:44 +0200 10dmar10 <10dma...@gmail.com> wrote: Package: systemd Version: 249.5-1 Severity: normal Hi, I noticed since upgrade to systemd 249.5-1 on 2021-10-15 foll

Bug#1004347: Suggests no longer existing crda

Package: wireless-regdb Version: 2021.08.28-1 Severity: normal The wireless-regdb suggests crda, yet this package has been removed from the archive: https://tracker.debian.org/news/1295874/removed-414git201911129856751-1-from-unstable/ wireless-regdb should drop the Suggests accordingly. -- Sy

Re: Bug#990411: systemd: set kernel.unprivileged_bpf_disabled = 1

Control: reassign -1 src:linux Am 30.06.21 um 20:33 schrieb Tomas Pospisek: reassign 990411 linux-image-5.10.0-7-amd64 - Thanks Michael, reassigning as proposed. Though I'm wondering (and not finding) whether there would be a more general package to assign this ticket to (such as linux-i

Re: Bug#990411: systemd: set kernel.unprivileged_bpf_disabled = 1

Am 28.06.21 um 14:52 schrieb Tomas Pospisek: Package: systemd Version: 247.3-5 Severity: wishlist Tags: security X-Debbugs-Cc: Debian Security Team Hi, TLDR: $ sudo sysctl kernel.unprivileged_bpf_disabled kernel.unprivileged_bpf_disabled = 0 please disable unprivileged BPF by defau

Bug#983357: Netinst crashes xen domU when loading kernel

Hi Phillip Am 24.05.2021 um 06:19 schrieb Cyril Brulebois: trigger to cold plug all devices. Both scripts are set -e. The Xen Virtual Keyboard driver and at least one other driver have always failed to trigger due to having absurdly long modalias, but the error used to be ignored. The kernel

Bug#981302: mandos-client: fails to fexecve plugins due to missing /dev/fd symlink

On Sun, 31 Jan 2021 15:38:06 +0100 Michael Biebl wrote: > Control: tags -1 + patch > > I've submitted a MR for initramfs-tools at > > https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/42 > > It basically mimics what dracut does and sets up th

Bug#946791: io.weight cannot be enabled in recent Debian kernel package

Control: retitle -1 Please enable CONFIG_IOSCHED_BFQ=y On Thu, 26 Dec 2019 23:17:13 +0900 Ryutaroh Matsumoto wrote: > Source: linux > Followup-For: Bug #946791 > Control: tags -1 + patch > > Dear Maintainer, > > I reported that IOWeight config item in systemd has no effect > on recent Debian ke

Bug#981302: mandos-client: fails to fexecve plugins due to missing /dev/fd symlink

Control: tags -1 + patch I've submitted a MR for initramfs-tools at https://salsa.debian.org/kernel-team/initramfs-tools/-/merge_requests/42 It basically mimics what dracut does and sets up those symlinks right after mounting devtmpfs. I also unmerged 975018, which I intend to use for the d-i/u

Re: Bug#966822: systemd: user-runtime-dir service crashes the kernel under SELinux

Control: reassign -1 src:linux Control: found -1 5.7.10-1 Am 06.08.20 um 21:43 schrieb bauen1: > Hi, > > I've already reported this bug in the kernel audit system upstream, see > https://lore.kernel.org/linux-audit/20200723200041.7yinlklts47pz...@madcap2.tricolour.ca/T/#t > for details. > > A

Bug#954294: libseccomp-dev: API break: SCMP_SYS() is unsigned long (was Re: Bug#954294: systemd: FTBFS on x32 due to format string errors, need explicit casts)

Am 25.06.20 um 17:49 schrieb Thorsten Glaser: > Michael Biebl dixit: > >> Is this workaround permanent or will systemd FTBFS again in the future? > > I’ve just verified that the upstream-merged fix, appearing in > linux-libc-dev 5.7.6-1 in sid, fixes this permanently. >

Bug#954294: libseccomp-dev: API break: SCMP_SYS() is unsigned long (was Re: Bug#954294: systemd: FTBFS on x32 due to format string errors, need explicit casts)

Am 08.04.20 um 09:56 schrieb Michael Biebl: > If seccomp support on x32 is causing so much trouble, we can just as > well disable it in systemd for the time being by dropping libseccomp-dev > from Build-Depends ... on x32 only, of course. signature.asc Description: OpenPGP digital signature

Bug#954294: libseccomp-dev: API break: SCMP_SYS() is unsigned long (was Re: Bug#954294: systemd: FTBFS on x32 due to format string errors, need explicit casts)

Am 07.04.20 um 14:26 schrieb Thorsten Glaser: > retitle 954294 linux: __X32_SYSCALL_BIT being defined as UL constant breaks > userspace > reassign 954294 > found 954294 5.5.13-2 > thanks > > Dixi quod… > >>> -#define SCMP_SYS(x) (__SNR_##x) >>> +#define SCMP_SYS(x) ((int)__SN

Re: Bug#952729: systemd: poweroff and reboot don't work

Control: reassign -1 src:linux Control: found -1 4.19.98-1 Hi Janusz On Tue, 17 Mar 2020 07:28:50 +0100 jsb...@mimuw.edu.pl (Janusz S. =?utf-8?Q?Bie=C5=84?=) wrote: > On Thu, Mar 12 2020 at 21:14 +01, Michael Biebl wrote: > > Hi > > > > Am 12.03.20 um 19:07 schrieb Janusz

Re: Bug#944350: systemd: screen remains off after waking up from suspend

Control: reassign -1 src:linux Control: found -1 5.3.7-1 Am 08.11.19 um 16:18 schrieb Jiri Kanicky: > Hi Michael. > > Thanks a lot getting back to me and for your interest in this issue. > > I would like to confirm that when I resume from suspend the machine > seems to be running fine. I can SSH

Re: Bug#941239: systemd 241-7, poweroff+reboot stalls/freezes after "Reached target shutdown"

Control: reassign -1 linux-image-4.19.0-6-686 Am 05.10.19 um 12:26 schrieb Rado Q: > =- Michael Biebl wrote on Fri 4.Oct'19 at 14:53:45 +0200 -= > >> Could you also provide a log file from a failed/hanging shutdown? > > I've attached a log per: > - faile

Re: Bug#940171: udev mounts /dev with the noexec flag

Control: reassign -1 initramfs-tools 0.135 Am 13.09.19 um 11:54 schrieb Mikulas Patocka: > Package: udev > Version: 242-7 > Severity: normal > > Dear Maintainer, > > *** Reporter, please consider answering these questions, where appropriate *** > >* What led up to the situation? > > I use

Re: Bug#928125: losetup causes Dead systemd-udevd processes, blocks forever

ked kernel: > > 4.9.0-9-amd64 #1 SMP Debian 4.9.168-1 (2019-04-12) x86_64 > > Hmm. Just noticed GNU/Linux tag is missing too.. Thanks for checking, Reassigning to the linux package and bumping severity a bit. Seems like something that should be fixed in stable. > > >

Re: Bug#927173: Adding details

Control: reassign -1 linux-image-4.9.0-8-amd64 Am 19.04.19 um 02:17 schrieb Felipe Sateler: > > > On Thu, Apr 18, 2019 at 8:05 PM JB > wrote: > > My bad, I thought it was the case but I mixed up the numbers. > > Please find enclosed the details yo

Bug#890950: Bug#902416: Bug#890950: RE: Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

Hi Ben Am 10.03.19 um 23:17 schrieb Ben Hutchings: > I think it would make sense for systemd to only set the hibernation > device if it's not already set (i.e. if /sys/power/resume contains > "0:0\n"). I get $ cat /sys/power/resume 8:4 which part is responsible for setting that? -- Why is it t

Bug#890950: RE: Bug#902416: systemd: systemctl hibernate: unable to resume after upgrade

Hi Mario, On Fri, 6 Jul 2018 12:41:37 + wrote: > > -Original Message- > > From: Michael Biebl [mailto:bi...@debian.org] > > Sent: Friday, July 6, 2018 5:46 AM > > To: Joel Cross; 902...@bugs.debian.org; Limonciello, Mario > > Subject: Re: Bug#902416

Re: Bug#919107: udev : suspend-to-ram randomly fails

Control: reassign -1 linux-image-4.19.0-1-amd64 Am 12.01.19 um 21:14 schrieb Julien Aubin: > Le sam. 12 janv. 2019 à 21:07, Michael Biebl a écrit : >> >> Control: tags -1 + moreinfo >> On Sat, 12 Jan 2019 20:12:22 +0100 Julien Aubin >> wrote: >>> Package:

Re: Bug#912406: systemd: reboot/poweroff usually gets stuck

Control: reassign -1 linux-image-4.9.0-7-686-pae Control: retitle -1 ehci-pci.ko prevents shutdown Hi Am 23.11.18 um 04:12 schrieb Andrew Pavlomanolakos: > Hi Michael, > > I built a 4.9.137 kernel and added some trace code and found that the > issue occurs during device_shutdown() in the linux k

Re: Fixing Linux getrandom() in stable

Hi Russ Am 10.05.2018 um 19:22 schrieb Russ Allbery: > Michael Biebl writes: >> Am 10.05.2018 um 00:46 schrieb Ben Hutchings: > >>> One of the krb5 maintainers (Benjamin Kaduk) favours option 2b, and >>> also proposed that systemd could provide a wait-for-rng-

Re: Fixing Linux getrandom() in stable

Am 10.05.2018 um 00:46 schrieb Ben Hutchings: > 1. Add entropy to the kernel during boot; either: >a. Improve systemd-random-seed >b. Recommend use of haveged > 2. For each affected userland package, either: >a. Revert to using /dev/urandom >b. Tolerate a longer wait for getrandom(

Re: Bug#886156: systemd: crashes the system on reloading

Control: reassign -1 linux-image-4.14.0-2-amd6 Am 02.01.2018 um 19:09 schrieb Kjö Hansi Glaz: > Package: systemd > Version: 236-2 > Severity: normal > > Dear Maintainer, > > When I upgrade the system with apt, the system often becomes > unresponsive after reloading systemd. Please find below the

Bug#881834: systemd: lib/systemd/systemd-remount-fs fails with /dev/nfs in fstab

Am 24.11.2017 um 17:03 schrieb Duncan Hare: > Michael > > Thanks, if /dev/nfs is ignored, then omitting it from fstab should work. > > That also fails. The filesystem is mounted ro by the kernel, and the > system is unusable. Again, this is something for the maintainers of mount.nfs to figure ou

Re: Bug#881834: systemd: lib/systemd/systemd-remount-fs fails with /dev/nfs in fstab

Control: reassign -1 nfs-common Control: tags -1 + patch On Wed, 15 Nov 2017 20:30:27 +0100 Michael Biebl wrote: > Fwiw, it's really mount or rather mount.nfs (from nfs-common) which > fails here: > > Nov 12 16:19:59 raspberrypi systemd-remount-fs[123]: /bin/mount for / &

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

Am 27.06.2017 um 04:03 schrieb Russell Coker: > Now what can we do about /dev and /sys/fs/cgroup neither of which needs to be > 24G in size on a system with 48G of RAM? Should I open a new bug report > about > this? What exactly would that solve? Neither of those are writable by the user. Mi

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

Am 27.06.2017 um 02:08 schrieb Michael Biebl: > You can add a entry to /etc/fstab which specifies the desired amount of > RAM for /run. > systemd will remount /run with the size you set very early during boot. > I don't think a separate config option is necessary. Something

Bug#862013: initramfs-tools-core: /run tmpfs size hardcoded at 10% RAM, but 16.0 MiB free required in /run/systemd

On Sun, 07 May 2017 13:38:11 +0100 J M Cerqueira Esteves wrote: > Package: initramfs-tools-core > Version: 0.130 > Severity: important > > In a virtual machine with 160 MiB RAM, running a freshly installed Debian > stretch system (i686), Since wheezy, the minimum requiremensts are 256M of RAM:

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

Am 11.01.2017 um 18:55 schrieb Vincent Lefevre: > On 2017-01-11 18:36:30 +0100, Michael Biebl wrote: >> Am 11.01.2017 um 18:28 schrieb Michael Biebl: >>> Am 11.01.2017 um 18:25 schrieb Vincent Lefevre: >>>> On 2017-01-11 18:09:51 +0100, Michael Biebl wrote: >&g

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

Am 11.01.2017 um 19:12 schrieb Michael Biebl: > Am 11.01.2017 um 18:55 schrieb Vincent Lefevre: >> On 2017-01-11 18:36:30 +0100, Michael Biebl wrote: >>> Am 11.01.2017 um 18:28 schrieb Michael Biebl: >>>> Am 11.01.2017 um 18:25 schrieb Vincent Lefevre: >>>&

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

Am 11.01.2017 um 18:28 schrieb Michael Biebl: > Am 11.01.2017 um 18:25 schrieb Vincent Lefevre: >> On 2017-01-11 18:09:51 +0100, Michael Biebl wrote: >>> Am 11.01.2017 um 18:05 schrieb Michael Biebl: >>>> Why is this no normal shutdown? >> >> Services

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

Am 11.01.2017 um 18:25 schrieb Vincent Lefevre: > On 2017-01-11 18:09:51 +0100, Michael Biebl wrote: >> Am 11.01.2017 um 18:05 schrieb Michael Biebl: >>> Why is this no normal shutdown? > > Services are not stopped as usual. How do you conclude that? -- Why is it tha

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

Am 11.01.2017 um 18:05 schrieb Michael Biebl: > Am 11.01.2017 um 17:05 schrieb Vincent Lefevre: >> Control: clone -1 -2 >> Control: reassign -2 systemd 232-8 >> Control: retitle -2 systemd: power off without always a normal shutdown when >> resuming after suspend with

Bug#850059: linux-image-4.8.0-2-amd64: After suspend, the power button powers off the laptop instead of resuming

Am 11.01.2017 um 17:05 schrieb Vincent Lefevre: > Control: clone -1 -2 > Control: reassign -2 systemd 232-8 > Control: retitle -2 systemd: power off without always a normal shutdown when > resuming after suspend with the power button > Control: severity -2 grave > > as the lack of shutdown yields

Bug#847204: nfs-kernel-server: `systemctl status` incorrectly reports server "active" even if not started

On Tue, 6 Dec 2016 15:15:12 +0100 Riccardo Murri wrote: > > Package: nfs-kernel-server > Version: 1:1.2.8-9 > > The systemd service unit file for `nfs-kernel-server` incorrectly > reports the service status as "active" even when the NFS server is *not* > running (e.g., empty exports file). ..

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

Am 15.12.2016 um 16:05 schrieb Ben Hutchings: > On Thu, 2016-12-15 at 11:39 +0100, Michael Biebl wrote: >> Or we fix the 3 packages which are affected. > > 'Fix' them like you did in udev, which results in an error message at > boot? No thanks. No, I would not add

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

Am 15.12.2016 um 07:18 schrieb Ben Hutchings: > On Fri, 2016-12-09 at 17:50 +, Ben Hutchings wrote: >> On Wed, 23 Nov 2016 14:30:36 +0100 Michael Biebl wrote: > [...] >>> We would also have to make sure to use mount --move in >>> /usr/share/initramfs-tools

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

Am 25.11.2016 um 08:48 schrieb K.Ohta: > Dear Michael, > > On Fri, 25 Nov 2016 07:49:55 +0100 > Michael Biebl wrote: > >> How did you apply the patch? If you do it via "patch < $patch", you'll >> need to chmod +x hooks/mounts. The lintian warni

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

Am 25.11.2016 um 05:18 schrieb K.Ohta: > Dear Michel, > Sorry for very later. > I test your patch of initramfs-tools, but, don't mount /usr with auto at > entry of fstab. > > I tested below: > 1.debuild initramfs after applying that patch and install packages. >> W: initramfs-tools-core: script-

Bug#838887: please dont bomb out on nofail option

On Mon, 26 Sep 2016 07:02:01 +0200 Marc Haber wrote: > when I looked for the last time (a few months ago), fstab entries > parsed by initramfs-tools or in initramfs MUST NOT contain the > "nofail" option. This is kind of surprising since some other fstab > entries MUST contain the "nofail" option

Bug#838887: please dont bomb out on nofail option

On Mon, 26 Sep 2016 07:02:01 +0200 Marc Haber wrote: > Package: initramfs-tools > Severity: wishlist > > Hi, > > when I looked for the last time (a few months ago), fstab entries > parsed by initramfs-tools or in initramfs MUST NOT contain the > "nofail" option. This is kind of surprising since

Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

Am 23.11.2016 um 14:30 schrieb Michael Biebl: > I'm going to reassign this to initramfs-tools as it uses mount > implementations from either klibc-utils or busybox which are both > incomplete and as a result, fail to mount /usr. > > I decided against reassigning this to bus

Re: Bug#845302: systemd: 232-6:Failed to boot, makes kernel panic when starting /sbin/init.

Control: reassign -1 initramfs-tools 0.125 Am 23.11.2016 um 11:25 schrieb K.Ohta: > Not mounted /usr and made kernel panic still longer sleep. > > Then booting with "init=/bin/bash" , check dmesg (attached). > Below message was wrote when trying to mount /usr : >> [ 15.958645] EXT4-fs (sde3):

Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

Am 25.09.2016 um 18:58 schrieb Julien Cristau: > On Sun, Sep 25, 2016 at 17:06:56 +0200, Michael Biebl wrote: >> Does this affect 4.7.2-1 as well, i.e. the current version in testing? > > The current version in testing is 4.6.4-1. Indeed. Somehow I was fooled by https://packages.

Bug#838544: ext4: ext4_iget:4476: inode #8: comm mount: checksum invalid

On Thu, 22 Sep 2016 07:51:36 +0200 Stefan Fritsch wrote: > Package: src:linux > Version: 4.7.4-2 > Severity: grave > Justification: renders package unusable > > When booting with linux-image-4.7.0-1-amd64 4.7.4-2, one of my > filesystems fails to mount with: > > ext4_iget:4476: inode #8: comm mo

Bug#836282: Fails to uninstall if 3rd party modules are installed: rmdir: failed to remove '/lib/modules/4.7.0-1-amd64': Directory not empty

Package: src:linux Version: 4.7.2-1 Severity: normal I have some 3rd party modules compiled and installed (which don't use DKMS). When I try to uninstall the kernel package, I get Removing linux-image-4.7.0-1-amd64 (4.7.2-1) ... Purging configuration files for linux-image-4.7.0-1-amd64 (4.7.2-1)

Bug#796674: Please enable CONFIG_SCHEDSTATS

Am 20.07.2016 um 05:16 schrieb Ben Hutchings: > On Wed, 2016-07-20 at 05:00 +0200, Michael Biebl wrote: >> Am 20.07.2016 um 04:54 schrieb Ben Hutchings: >>> As of 4.6, there is an additional run-time switch for schedstats >>> (kernel parameter and sysctl) ... >

Bug#796674: Please enable CONFIG_SCHEDSTATS

Thanks for the update Am 20.07.2016 um 04:54 schrieb Ben Hutchings: > As of 4.6, there is an additional run-time switch for schedstats > (kernel parameter and sysctl) so enabling CONFIG_SCHEDSTATS has minimal > performance cost: > > https://git.kernel.org/linus/cb2517653fccaf9f9b4ae968c7ee005c1bb

Bug#828826: nfs-common: move of rpc_pipefs mountpoint to /run breaks blkmapd

Control: severity -1 serious On Tue, 28 Jun 2016 09:21:44 +0200 Christoph Hellwig wrote: > Package: nfs-common > Version: 1:1.2.8-9 > Severity: important > Tags: patch > > Dear Maintainer, > > commit ba649fa4 ("Migrate the rpc_pipefs mount out of /var/lib to /run, to > better support /var on NF

Bug#796674: Please enable CONFIG_SCHEDSTATS

Am 06.07.2016 um 01:39 schrieb Roger Shimizu: > On Sun, Jul 3, 2016 at 2:58 PM, Michael Biebl wrote: >> This topic came up today on #pkg-systemd (again). >> Do you have any concerns regarding enabling CONFIG_SCHEDSTATS and if > > see: https://bugs.debian.org/600935#10 >

Bug#796674: Please enable CONFIG_SCHEDSTATS

Hi kernel maintainers, On Sun, 23 Aug 2015 15:10:13 +0200 Michael Biebl wrote: > the current Debian Linux kernels have CONFIG_SCHEDSTATS disabled. > > The systemd package ships a tool named systemd-bootchart [1] which can > be used to collect different metrics like CPU and memo

Bug#829127: systemd: Please make sure /lib/systemd/systemd is not linked with something in /usr

Am 30.06.2016 um 21:37 schrieb Eric Valette: > On 30/06/2016 21:32, Felipe Sateler wrote: >> On 30 June 2016 at 15:20, Eric Valette wrote: >>> On 30/06/2016 21:18, Martin Pitt wrote: Control: reassing -1 libaudit1 Control: forcemerge 828991 -1 Hello Eric, >>> >>> This

Re: Bug#816106: Suspend Bug, Severity: High

s either a hardware or driver/kernel issue. Reassigning to the linux kernel. > On Saturday, February 27, 2016 11:08 AM, Michael Biebl > wrote: > > > Am 27.02.2016 um 15:51 schrieb john Lutz: >> >> Package: systemd-sysv >> Version: 225-1 >> >> Using a

Re: broken mount behaviour on jessie

Am 31.01.2016 um 22:31 schrieb Brian May: > Peter Palfrader writes: > >> o) you cannot unmount the tmp0 tree while the tmp1 tree is busy: >> >> } root@valiant:/mnt# (cd tmp1/dev/pts ; sleep 10 &) >> } root@valiant:/mnt# umount /mnt/tmp0/dev/pts >> } umount: /mnt/tmp0/dev/pts: target is busy >> }

Re: Bug#810748: systemd does not mount /usr in initramfs, breaking split /usr

Am 14.01.2016 um 00:04 schrieb Nis Martensen: > If I read the code correctly, than this patch is the culprit: > http://sources.debian.net/src/systemd/215-17%2Bdeb8u2/debian/patches/Skip-filesystem-check-if-already-done-by-the-initram.patch/?hl=29#L29 > > When systemd is run in the initramfs (which

Re: [pkg-cryptsetup-devel] Bug#783297: breaks initramfs if BUSYBOX=n

Am 25.12.2015 um 14:46 schrieb Jonas Meurer: > Am 26.04.2015 um 01:35 schrieb Michael Biebl: >> On Sat, 25 Apr 2015 16:22:13 +0200 Michael Biebl wrote: >>> if the cryptsetup package is installed, it also installed a >>> initramfs-tools hook. >>> >>>

Bug#802337: file conflict with firmware-linux-nonfree 0.44

Package: firmware-misc-nonfree Version: 20151018-1 Severity: serious another file conflict: Preparing to unpack .../firmware-misc-nonfree_20151018-1_all.deb ... Unpacking firmware-misc-nonfree (20151018-1) ... dpkg: error processing archive /var/cache/apt/archives/firmware-misc-nonfree_20151018-

Bug#802336: file conflict with firmware-linux-nonfree 0.44

Package: firmware-amd-graphics Version: 20151018-1 Severity: serious todays update tried to install firmware-amd-graphics which lead to Preparing to unpack .../firmware-amd-graphics_20151018-1_all.deb ... Unpacking firmware-amd-graphics (20151018-1) ... dpkg: error processing archive /var/cache/

Re: Bug#799031: systemd: Freeze radeon driver using amdkfd of kernel 4.2.0 vanilla.

Control: reassign -1 linux-image-4.2.0-trunk-amd64 Am 15.09.2015 um 07:18 schrieb Kyuma Ohta: > Package: systemd > Version: 226-1 > Severity: important > > Dear Maintainer, > > When update systemd 225 to 226, and booting from 4.2 vanilla, > freeze screen on loading radeon drm framebuffer driver.

Re: Bug#720081: Install file trigger for /usr/share/initramfs-tools

Am 30.08.2015 um 16:38 schrieb Ben Hutchings: > On Sun, 2015-08-30 at 16:23 +0200, Michael Biebl wrote: >> initramfs-tools has the same problem. Right now, individual packages >> update the initramfs by calling "update-initramfs -u" in their >> maintainer sc

Re: Bug#720081: Install file trigger for /usr/share/initramfs-tools

Control: retitle -1 Add support for dpkg triggers Control: block 739464 by -1 Am 21.08.2013 um 15:40 schrieb Thomas Lange: >>>>>> On Sun, 18 Aug 2013 13:04:18 +0200, Michael Biebl >>>>>> said: > > > That's why I suggest to install a dpkg f

Bug#796674: Please enable CONFIG_SCHEDSTATS

Source: linux Version: 4.1.5-1 Severity: wishlist Hi, the current Debian Linux kernels have CONFIG_SCHEDSTATS disabled. The systemd package ships a tool named systemd-bootchart [1] which can be used to collect different metrics like CPU and memory usage and dist utilization during boot and gener

Re: [PATCH] Disable kdbus support

Am 26.07.2015 um 16:15 schrieb Martin Pitt: > Hey Julian, > > Julian Wollrath [2015-07-26 16:02 +0200]: >> kdbus is not available on Debian. Hence, disable kdbus support to avoid >> unnecessary inclusion of code handling its existance. > > It won't do that. --disable-kdbus merely changes the defa

Bug#775542: auto-mount NFS shares on boot

[ bringing pkg-systemd-maintainers into the loop here ] Am 27.06.2015 um 20:14 schrieb Christian Seiler: > On 06/27/2015 08:02 PM, Jonas Meurer wrote: >> Am 27.06.2015 um 16:07 schrieb Christian Seiler: >>> Could you try to do the following: >>> >>> 1. create a directory /etc/systemd/system/remote

Bug#783410: Please add support for fsck.mode= parameters as known by systemd-fsck

Package: initramfs-tools Version: 0.120 Severity: important systemd-fsck [1] knows the following kernel command line parameters fsck.mode= One of "auto", "force", "skip". Controls the mode of operation. The default is "auto", and ensures that file system checks are done when the file system c

Re: breaks initramfs if BUSYBOX=n

On Sat, 25 Apr 2015 16:22:13 +0200 Michael Biebl wrote: > Package: cryptsetup > Version: 2:1.6.6-5 > Severity: grave > > Hi, > > if the cryptsetup package is installed, it also installed a > initramfs-tools hook. > > I use BUSYBOX=no in initramfs.conf, but the

Bug#783291: /bin/touch is missing if built with BUSYBOX=n

Control: tags -1 + patch Am 25.04.2015 um 14:21 schrieb Michael Biebl: > > Maybe it could replace the following line in > /usr/share/initramfs-tools/scripts/functions: > > touch $FSCK_STAMPFILE > > with > > :> $FSCK_STAMPFILE > > This will work, even wh

Bug#783291: /bin/touch is missing if built with BUSYBOX=n

Am 25.04.2015 um 15:51 schrieb Michael Biebl: > Am 25.04.2015 um 14:44 schrieb Michael Biebl: >> >> I just tried to boot a system where the initramfs had been built with >> BUSYBOX=n. This failed miserably and ended in a kernel panic. >> >> /init: exec:

Bug#783291: /bin/touch is missing if built with BUSYBOX=n

[Sorry, this was meant to go to bug #783291, not #783282] Am 25.04.2015 um 15:55 schrieb Michael Biebl: > Am 25.04.2015 um 14:21 schrieb Michael Biebl: >> I can reproduce the missing /bin/touch if I build the initramfs without >> busybox support. Can you check your /etc/

Bug#783291: /bin/touch is missing if built with BUSYBOX=n

Am 25.04.2015 um 14:44 schrieb Michael Biebl: > On Sat, 25 Apr 2015 14:21:04 +0200 Michael Biebl >> I can reproduce the missing /bin/touch if I build the initramfs without >> busybox support. Can you check your /etc/initramfs-tools/initramfs.conf >> if it contains BUSYB

Bug#783291: /bin/touch is missing if built with BUSYBOX=n

Am 25.04.2015 um 14:44 schrieb Michael Biebl: > I just tried to boot a system where the initramfs had been built with > BUSYBOX=n. This failed miserably and ended in a kernel panic. > > /init: exec: line 330: switch_root: not found > [attempted to kill init ...] > > > Lo

Bug#783291: /bin/touch is missing if built with BUSYBOX=n

On Sat, 25 Apr 2015 14:21:04 +0200 Michael Biebl > I can reproduce the missing /bin/touch if I build the initramfs without > busybox support. Can you check your /etc/initramfs-tools/initramfs.conf > if it contains BUSYBOX=n or if you have a snippet in > /etc/initramfs-tools/conf.d

Bug#783291: /bin/touch is missing if built with BUSYBOX=n

Package: initramfs-tools Version: 0.120 Severity: important Am 25.04.2015 um 04:58 schrieb Mike Kupfer: > Michael Biebl wrote: > >> Which initramfs-tools version do you have installed? > > ii initramfs-tool 0.120all generic modular initramfs generat >

Re: Bug#782390: udev: time between USB-stick connection and device notification takes up to a minute

Am 11.04.2015 um 15:17 schrieb Bernhard Übelacker: > Package: udev > Version: 215-14 > Severity: normal > > Dear Maintainer, > when I insert a specific USB-stick I see following symptoms: > - cpu usage rises (/lib/systemd/systemd-udevd, /usr/lib/udisks2/udisksd, > /usr/bin/plasma-desktop) > - it t

Re: Bug#780520: systemd-sysv: computer restarts after shutdown if connected to an external display)

Control: reassign -1 linux-image-3.16.0-4-amd64 Am 16.03.2015 um 10:16 schrieb har...@free.fr: >> For testing purposes, can you install the "sysvinit" package, >> run update-grub, then choose the sysvinit option in the grub advanced >> option on next reboot. > >> Does the problem happen under sys

Re: Bug#777440: systemd: Fails to hibernate the system

control: reassign -1 linux-image-3.16.0-4-amd64 Am 08.02.2015 um 18:54 schrieb Waxhead: > Michael Biebl wrote: >> control: tags -1 moreinfo >> >> Am 08.02.2015 um 10:24 schrieb Svein Engelsgjerd: >>> Package: systemd >>> Version: 215-10 >>

Re: Bug#776874: systemd: system auto-resumes when pcspkr module is loaded

control: reassign -1 linux-image-3.16.0-4-amd64 Am 02.02.2015 um 21:26 schrieb Ralf Auer: > yes, I get the same result when I manually echo "mem". > > Is there an easy way to re-assign this ticket to the kernel package, or > should I file another report and you close this one? I've reassigned th

Re: Bug#772624: dmesg output

Ben, any idea why this users mouse is not correctly detected during boot? Might this be a kernel problem? Martin, do you have a custom initramfs without hid-generic? If you don't have MODULES=most in /etc/initramfs-tools/initramfs.conf, could you rebuilt your initramfs with that option set? Am 0

Bug#751238: Reopen bug report for switching hwclock-set to use hctosys

Am 09.10.2014 um 00:54 schrieb Ben Hutchings: > If > not, then there is a double adjustment during boot. That got me thinking. I do have ntp enabled. After disabling the ntp service, my hwclock is no longer incorrectly set and I no longer get the fsck errors. Does ntp and hwclock --hctosys not p

Bug#751238: Reopen bug report for switching hwclock-set to use hctosys

Am 09.10.2014 um 00:54 schrieb Ben Hutchings: > On Thu, 2014-10-09 at 00:14 +0200, Michael Biebl wrote: >> Am 08.10.2014 um 23:20 schrieb Ben Hutchings: >>> With those exact same versions, I still see the system clock set >>> correctly! >> >> What

Bug#751238: Reopen bug report for switching hwclock-set to use hctosys

Am 08.10.2014 um 18:14 schrieb Michael Biebl: > Am 08.10.2014 um 23:20 schrieb Ben Hutchings: >> With those exact same versions, I still see the system clock set >> correctly! > > What's your timezone? Mine is Europe/Berlin. > On each reboot, my hwclock will be off

Bug#751238: Reopen bug report for switching hwclock-set to use hctosys

Am 08.10.2014 um 23:20 schrieb Ben Hutchings: > With those exact same versions, I still see the system clock set > correctly! What's your timezone? Mine is Europe/Berlin. On each reboot, my hwclock will be off by another -2 hours. So if it's 12:00 local time, after reboot, my hwclock will be set t

Bug#751238: Reopen bug report for switching hwclock-set to use hctosys

Hi Ben Am 07.10.2014 um 21:00 schrieb Ben Hutchings: > On Tue, 2014-10-07 at 20:21 +0200, Michael Biebl wrote: >> Fwiw, it was me, how experiences this issue. >> After the switch from systz to hctosys in /lib/udev/hwclock-set, my >> hardware clock is no longer properly set u

Bug#751238: Reopen bug report for switching hwclock-set to use hctosys

Am 07.10.2014 um 20:37 schrieb Aurelien Jarno: > On Tue, Oct 07, 2014 at 08:21:51PM +0200, Michael Biebl wrote: >> Fwiw, it was me, how experiences this issue. >> After the switch from systz to hctosys in /lib/udev/hwclock-set, my >> hardware clock is no longer prope

Bug#751238: Reopen bug report for switching hwclock-set to use hctosys

Am 07.10.2014 um 20:40 schrieb Michael Biebl: > Am 07.10.2014 um 20:37 schrieb Aurelien Jarno: >> I don't really see how it can happen, this file is not supposed to be >> run under systemd, due to the following code at the beginning: >> >> | if [ -e /run/system

Bug#751238: Reopen bug report for switching hwclock-set to use hctosys

Am 07.10.2014 um 19:14 schrieb Andreas Henriksson: > Control: reopen -1 > Control: found -1 2.25.1-4 > > Hello! > > I'm reopening this bug report regarding using --hctosys in the util-linux > hwclock-set script. The change was proposed for the benefit of arm > systems where RTC drivers are built

Bug#764285: kernel panic with fuse mounted partition (ntfs-3g) when using virtualbox

Package: src:linux Version: 3.16.3-2 Severity: important File: /boot/vmlinuz-3.16-2-amd64 I use virtualbox and store the virtualbox images on a ntfs-3g partition. Since the upgrade to 3.16, this regularly leads to a kernel crash when using virtualbox. The error message is something like this: Ok

Bug#763777: fsck: Superblock set in the future, fixing system clock

Am 02.10.2014 um 18:15 schrieb Michael Biebl: > After the upgrade from 0.116 to 0.117 I get this error message on every > boot for /, and as a result fsck is also run on every boot for /. Forgot to add the actual message: > fsck from util-linux 2.20.1 > Debian: Superblock last writ

Bug#763777: fsck: Superblock set in the future, fixing system clock

Package: initramfs-tools Version: 0.117 Severity: serious After the upgrade from 0.116 to 0.117 I get this error message on every boot for /, and as a result fsck is also run on every boot for /. Note, my hardware clock runs in local time and I use UTC=no in /etc/default/rcS resp. LOCAL in /etc/a

Bug#652459: Bug#697002: jessie: -R skips check of /etc and /usr in addition to /

Am 05.08.2014 09:20, schrieb Simon McVittie: > If any of the maintainers involved consider mounting /etc from the initramfs > to be controversial or problematic, special-casing /usr but not /etc > is sufficient to unblock > . > > (I persona

Re: Bug#753816: [systemd] Broken audio

Am 06.07.2014 10:39, schrieb Antonio Marcos López Alonso: > El 06/07/14 05:34, Ben Hutchings escribió: >> I think the usual workaround is to add 'index=1' to the snd-aloop line >> in /etc/modules. It is probably possible to do something more >> sophisticated in an ALSA configuration file. > > Ad

Re: Bug#753816: [systemd] Broken audio

Am 05.07.2014 18:38, schrieb Antonio Marcos López Alonso: > El 05/07/14 17:06, Michael Biebl escribió: >> Am 05.07.2014 17:56, schrieb Antonio Marcos López Alonso: >>> Just in case, have you noticed I'm using an ALSA-Jack loopback setting >>> for audio? >> U

  1   2   >