For everyone affected by this issue, can you please answer this question:
Did you reboot after the upgrade?
Is the problem reproducible after the reboot or only directly after the
upgrade?
signature.asc
Description: OpenPGP digital signature
On Thu, 3 Oct 2019 13:57:09 +0200 Michael Biebl wrote:
> Am 03.10.19 um 13:12 schrieb Alexandra N. Kossovsky:
> > Thank you for your patience.
> >
> > I've submitted the part of the issue which (by my opinion) is a clear
> > bug: https://github.com/systemd/systemd/issu
Hi Ben,
I'm bringing you into the loop here. Maybe you can help as kernel
maintainer (or know someone we could ask).
On Thu, 17 Oct 2019 11:26:05 +0200 Rado S wrote:
> =- Michael Biebl wrote on Wed 16.Oct'19 at 13:06:29 +0200 -=
>
> > >>> # cat /sys/class/backlight/intel
Am 10.11.19 um 17:48 schrieb Michael Biebl:
> Package: debhelper
> Version: 12.7.1
> Severity: normal
>
> Hi,
>
> I'm currently working on updating the debhelper compat level in systemd
> from 10 to 12:
>
> https://salsa.debian.org/systemd-team/systemd/com
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
Am 08.11.19 um 15:55 schrieb kwadronaut - debian:
> Event: time 1573224694.677054, type 4 (EV_MSC), code 4 (MSC_SCAN), value
> 1c
> Event: time 1573224694.677054, type 1 (EV_KEY), code 28 (KEY_ENTER),
> value 0
> Event: time 1573224694.677054, -- SYN_REPORT
> Event: time
Control: tags -1 + moreinfo
Am 08.11.19 um 12:59 schrieb ganomi:
> Package: systemd
> Version: 242-7
> Severity: normal
>
> Dear Maintainer,
>
> Environment:
> Thinkpad X1 Extreme gen2 with OLED.
>
> Troubleshooting:
> I am not able to find anything in logs. Can you perhaps let me know how I
Am 08.11.19 um 15:27 schrieb Jiri Kanicky:
> I am not sure whether this is being handled by systemd or kernel. Please
> change it to kernel is you think its kernel problem.
>
> I am trying to use pm-suspend to debug it, so i might provide more info,
> but so far I dont see any errors. The machine
Package: debhelper
Version: 12.7.1
Severity: normal
Hi,
I'm currently working on updating the debhelper compat level in systemd
from 10 to 12:
https://salsa.debian.org/systemd-team/systemd/commits/wip/compat-12
systemd ships several units files, which are currently enabled manually
in the
Am 10.11.19 um 17:48 schrieb Michael Biebl:
> Somehow I think it would the cleanest solution if tmpfiles handling was
> split into a separate helper, say dh_installtmpfile which can be called
> individually from dh_installsystemd.
> Technically this would make sense, as a tmpfile
Control: tag -1 + moreinfo
What do you get in the kernel log/journal if you press the
brightness up/brightness down key?
What happens if you run evtest (as root) and you press one of those keys?
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away
Am 21.11.19 um 09:10 schrieb Fred Boiteux:
> Hi,
>
> Please find the output of 'systemctl show squid.service' in 'info1'
> attached file,
> and the output of 'journalctl -alb' in 'info2' one.
>
> Thanks for your help,
> Fred.
>
> [I send this e-mail again, seems that my first
Am 21.11.19 um 09:35 schrieb Amit Agnani:
> Package: systemd
> Version: 241-7~deb10u2
>
> When attempting to decrypt LUKS-encrypted volumes under systemd (through
> dracut) during boot/init, I get the following failure message:
I don't really have any experience with systemd-cryptsetup-generator
Am 21.11.19 um 10:49 schrieb Michael Biebl:
> As you can see, the problem is, that you have a resolvconf hook which
> tries to start squid.service way too early during boot. It's not
> directly systemd which schedules the start of the service.
> Since those hook scripts are pr
Control: reassign -1 squid
Control: retitle -1 squid should use /run/squid.pid
Am 21.11.19 um 11:52 schrieb Fred Boiteux:
> Thanks Michael for your advices !
>
> Le 21/11/2019 à 11:27, Michael Biebl a écrit :
>> Am 21.11.19 um 10:49 schrieb Michael Biebl:
>>
>>&g
Am 21.11.19 um 12:22 schrieb Amit Agnani:
> Upstream seems to have a policy to only track bugs against the two most
> recent revisions of systemd, which are 243 and 242 at the moment of writing.
> See: https://github.com/systemd/systemd/blob/master/docs/CONTRIBUTING.md
>
> But if you insist, I
Control: forwarded -1 https://github.com/systemd/systemd/issues/14098
Am 21.11.19 um 14:01 schrieb Amit Agnani:
> Bug has been tested with systemd 242-8~bpo10+1 yielding the same error.
>
> An upstream bug has been filed at:
> https://github.com/systemd/systemd/issues/14098
Thanks Amit!
Marking
Am 04.12.19 um 14:28 schrieb Michael Biebl:
> Btw, if you move those headers, don't forget to add a Breaks/Replaces:
> libiptc-dev to libip4tc-dev. This seems to be missing currently.
A versioned Breaks/Replaces, obviously...
--
Why is it that all of the instruments seeking intelligen
Hi Arturo
Am 04.12.19 um 12:41 schrieb Arturo Borrero Gonzalez:
> Package: systemd
> Version: 243-8
> Severity: normal
>
> Hi there!
>
> The src:iptables debian package (v1.8.4-1) dropped the libiptc-dev and
> libiptc0
> binary packages. The content is included now in either libip4tc or
Am 04.12.19 um 13:59 schrieb Arturo Borrero Gonzalez:
>
>
> On 12/4/19 1:53 PM, Michael Biebl wrote:
>> Hi Arturo
>>
>> Am 04.12.19 um 12:41 schrieb Arturo Borrero Gonzalez:
>>> Package: systemd
>>> Version: 243-8
>>> Severity: normal
>
Am 04.12.19 um 13:53 schrieb Michael Biebl:
> Hi Arturo
>
> Am 04.12.19 um 12:41 schrieb Arturo Borrero Gonzalez:
>> Package: systemd
>> Version: 243-8
>> Severity: normal
>>
>> Hi there!
>>
>> The src:iptables debian package (v1.8.4-1) dropped
control: reassign -1 lvm2
Am 09.12.19 um 00:43 schrieb Vincent Lefevre:
> Package: udev
> Version: 244-3
> Severity: minor
>
> I get the following message in the journalctl output:
>
> Dec 09 00:10:17 zira systemd-udevd[477]: /lib/udev/rules.d/56-lvm.rules:40
> Invalid value for OPTIONS key,
device unit.
Among other things, this fixes StopWhenUnneeded=true being broken for
mount units. (Closes: #941758)
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=941758
https://salsa.debian.org/systemd-team/systemd/commit/e1be83ad48df9743cabc0c23c086f6f53e8eb46d
-- Michael Biebl Wed, 16
Am 14.10.19 um 23:13 schrieb Rado S:
> dell_backlight: Failed to write system 'brightness' attribute: No such device
> or address
Looks like a kernel or firmware/bios problem to me.
Since you didn't use reportbug there is no information about your used
kernel.
--
Why is it that all of the
Am 16.10.19 um 05:10 schrieb Rado S:
> =- Michael Biebl wrote on Tue 15.Oct'19 at 13:33:15 +0200 -=
>
>> I can get the current brightness via
>>> # cat /sys/class/backlight/intel_backlight/brightness
>>> 1500
>
> I get 79560.
>
>> and change
On 15.10.19 00:30, David Castillo wrote:
> Hi!
>
> I'm currently working on packaging an application which runs as a
> systemd service within a slice.
Is there a specific reason for using a dedicated slice?
What exactly is the use case here?
Is this a package shipped in Debian so we could have
On 15.10.19 03:03, Rado S wrote:
> =- Michael Biebl wrote on Mon 14.Oct'19 at 23:20:57 +0200 -=
>
>> Am 14.10.19 um 23:13 schrieb Rado S:
>>> dell_backlight: Failed to write system 'brightness' attribute: No such
>>> device or address
>>
>> Looks li
Am 25.10.19 um 01:10 schrieb Thomas Goirand:
> Hi Michael,
>
> Apparently, I haven't made myself clear, sorry for this.
Given what you wrote in the bug report, your intentions are/were indeed
not clear.
> Using plymouth is very much fine *IF* it worked, but it does only
> partially,
Control: tags -1 + moreinfo
Am 28.10.19 um 15:23 schrieb Vincent Lefevre:
> Package: systemd
> Version: 242-7
> Severity: important
> Tags: security
>
> systemd generates a directory name under /var/log/journal with
> the /etc/machine-id value, which is confidential according to
> the
Am 29.10.2019 um 08:21 schrieb Michael Biebl:
> Am 29.10.2019 um 02:25 schrieb Vincent Lefevre:
>
>> Note also that the same paragraph recommends to use a hash as a
>> stable unique identifier. But since this is meant to be stable
>> and unique, this would also allow t
Am 29.10.2019 um 02:25 schrieb Vincent Lefevre:
> Note also that the same paragraph recommends to use a hash as a
> stable unique identifier. But since this is meant to be stable
> and unique, this would also allow the machine to be tracked if
> such a hash is exposed on the network. So the
Am 17.10.19 um 15:19 schrieb Mathias Behrle:
> * Michael Biebl: " Re: Bug#942511: systemd: Excludes in tmpfiles.d do not
> work" (Thu, 17 Oct 2019 13:33:50 +0200):
>
> Hi Michael,
>
> thanks for your immediate response.
>
>> Am 17.10.19 um 13:09 schrieb
Control: severity -1 normal
Control: tags -1 moreinfo
Am 17.10.19 um 13:09 schrieb Mathias Behrle:
> Package: systemd
> Version: 242-7
> Severity: important
>
> Dear Maintainers,
>
> since considerable time I encounter the problem, that tmp
> files/directories created by vim are obviously
Am 17.10.19 um 13:33 schrieb Michael Biebl:
> Maybe this is a misunderstanding how x/X is supposed to work.
> "D /tmp 1777 root root -" is supposed to clean up /tmp during boot
> unconditionally. It is *not* using age based cleaning.
>
> This Debian specific change wa
Control: severity -1 normal
Control: retitle -1 udev aborts processing rules on failures
Am 19.11.19 um 02:18 schrieb Michael Biebl:
> Am 19.11.19 um 00:56 schrieb Klaumi Klingsporn:
>> That leaves me with the question: Why the hell on my
>> amd64-system (with i386 enabled onl
This is blocked by a bug in gnome-shell which dies when logind is restarted:
https://gitlab.gnome.org/GNOME/gnome-shell/issues/1881
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital
Am 19.11.19 um 00:56 schrieb Klaumi Klingsporn:
> That leaves me with the question: Why the hell on my
> amd64-system (with i386 enabled only as
> foreign-architecture) the i386 version of libinput-bin was
> installed?
I'm puzzled as well how so many users ended up with a non-native
Am 20.11.19 um 19:35 schrieb Yaroslav Halchenko:
>
> On Wed, 20 Nov 2019, Michael Biebl wrote:
>>> Problem statement:
>
>>> if laptop lid is closed after suspend is initiated (via keyboard
>>> shortcut), but before laptop actually is suspended, then upon re
Am 20.11.19 um 19:35 schrieb Yaroslav Halchenko:
>
> On Wed, 20 Nov 2019, Michael Biebl wrote:
>>> Problem statement:
>
>>> if laptop lid is closed after suspend is initiated (via keyboard
>>> shortcut), but before laptop actually is suspended, then upon re
Control: tags -1 + moreinfo
Am 20.11.19 um 16:05 schrieb Yaroslav Halchenko:
> Package: systemd
> Version: 243-7
> Severity: normal
>
> Problem statement:
>
> if laptop lid is closed after suspend is initiated (via keyboard
> shortcut), but before laptop actually is suspended, then upon
Control: forcemerge 941636 -1
basically a duplicate of #941636, so merging accordingly.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Am 27.11.19 um 17:42 schrieb Ansgar:
> On Wed, 2019-11-27 at 15:22 +, Graham Cobb wrote:
>>> I suspect there are some old binaries (from systemd-241) around for
>>> some reason.
>>
>> That does seem to be the case.
>
> Did you ever (a) install systemd yourself, or (b) tried to convert the
>
Am 27.11.19 um 19:06 schrieb Graham Cobb:
> On 27/11/2019 16:42, Ansgar wrote:
>> On Wed, 2019-11-27 at 15:22 +, Graham Cobb wrote:
I suspect there are some old binaries (from systemd-241) around for
some reason.
>>>
>>> That does seem to be the case.
>>
>> Did you ever (a) install
Am 30.11.19 um 17:56 schrieb Marc Lehmann:
> On Sat, Nov 30, 2019 at 04:14:55PM +0100, Michael Biebl
> wrote:
>> I assume there is no further interest to work collaboratively on this
>> from the bug reporters side, so closing the issue.
>
> Your assumption is
Control: tags -1 + moreinfo
Hi
On Mon, 10 Aug 2015 23:25:36 + "brian m. carlson"
wrote:
> On Sun, Aug 09, 2015 at 05:54:29PM +0200, Marco d'Itri wrote:
> > On Aug 08, "brian m. carlson" wrote:
> >
> > > Previously, my WiMAX device was named something like wmx0. Now, it
> > > appears
Control: reassign -1 iwd
Control: forcemerge 941652 -1
Control: affects -1 udev
Hi Nicolas
Am 04.11.19 um 10:38 schrieb Nicolas Évrard:
> Package: udev
> Version: 242-7
> Severity: normal
>
> Dear Maintainer,
>
> I recently updated my laptop and after a few I rebooted to use the new
> kernel
Am 14.11.19 um 11:50 schrieb Klaumi Klingsporn:
> So: As this bug makes desktop-systems where systemd generally uses the
> graphical.target
> as default.target totally unusable, I think thebug should be set to grave!
So far this seems to be an isolated issue, possibly hardware related or
Control: tags -1 + moreinfo
Am 14.11.19 um 13:22 schrieb Jan Sindelar:
> Package: systemd
> Version: 243-5
> Severity: critical
> Justification: breaks the whole system
>
> Dear Maintainer,
>
>* What led up to the situation?
> Installing latest systemd package using apt full-upgrade in
Am 27.11.19 um 11:47 schrieb westlake:
> Bugreport relayed to the dbus package, immediately closes bug with the
> following response,
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=945561
> ""
> Even if systemd --user was suitable for being started by a D-Bus service
> file
Control: tags -1 + moreinfo
Am 27.11.19 um 12:49 schrieb Graham Cobb:
> Package: systemd
> Version: 243-8
> Severity: important
>
> Dear Maintainer,
>
> I am upgrading my debian testing system but the upgrades fail as systemd
> cannot be configured.
>
> Output from dpkg --configure systemd:
>
Am 27.11.19 um 11:47 schrieb westlake:
> ^ "systemctl --user" is still used by many users and this user-context
> requires "org.freedesktop.systemd1.service"
No, systemctl requires the org.freedesktop.systemd1 D-Bus interface.
This D-Bus interface is provided by the systemd --user instance that
Please attach
journalctl -ub systemd-journald.service
signature.asc
Description: OpenPGP digital signature
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@alioth-lists.debian.net
Am 25.09.19 um 00:41 schrieb Jörg Sommer:
> Michael Biebl hat am Di 24. Sep, 21:50 (+0200) geschrieben:
>> Please attach
>> journalctl -ub systemd-journald.service
systemd-analyze log-level debug
systemctl restart systemd-journald
journalctl -alb
journalctl --verify
output
output of
systemd-analyze dump
systemctl list-jobs
as well, please.
It's odd that restarting journald pulls in a start of -.mount and
var.mount, as if this units were not active.
Have you rebooted after the upgrade to v243?
If not, can you reproduce the problem after a reboot?
signature.asc
Am 25.09.19 um 14:22 schrieb Jörg Sommer:
> Michael Biebl hat am Mi 25. Sep, 12:33 (+0200) geschrieben:
>> output of
>> systemd-analyze dump
>
> I've recorded a dump before and after restart.
Seems to be missing?
One thing I noticed is that you seem to have hit the
Am 07.10.19 um 10:29 schrieb Jonathan Dowland:
> On Sat, Oct 05, 2019 at 02:20:48AM +0200, Michael Biebl wrote:
>> Do you know about automount units?
>> They would be the perfect fit for your use case.
>
> From what I understand they behave like pre-systemd automounting, t
user pkg-systemd-maintain...@lists.alioth.debian.org
usertag 941758 + buster-backport
done
Am 07.10.19 um 12:52 schrieb Jonathan Dowland:
> Fair enough, thanks. Realistically I doubt I'll work on one and I'll
> wait instead for buster-backports. But I'll probably have a look to see
> if I can
On Fri, 13 Sep 2019 09:06:39 +0200 Harald Dunkel
wrote:
> Stay tuned, I had a busy week.
>
> But I am surprised that you rely on "non-Debian" software to
> reproduce the bug. Ain't the test case mentioned in
>
> https://github.com/systemd/systemd/commit/37ed15d7edaf59a1fc7c9e3552cd93a83f3814ef
Thanks for the additional information.
Your proposed change looks ok to me but I'd like an ACK from Martin on this.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
Am 03.10.19 um 10:44 schrieb Alexandra N. Kossovsky:
> I do not think systemd people will accept it as a bug.
> They have a new configuration key MACAddressPolicy, and it all works as
> expected. Or almost as expected.
>
Now I'm confused, either there is a bug or there isn't.
My point is, that
>> Hm, you probably need to blacklist
>> /lib/udev/rules.d/73-usb-net-by-mac.rules. You can do that by creating a
>> file /etc/udev/rules.d/73-usb-net-by-mac.rules pointing at /dev/null
>>
>> After that (and running update-initramfs -u), 70-wifi.link should become
>> active and you should be able
Am 04.10.19 um 22:57 schrieb Jonathan Dowland:
> Package: systemd
> Version: 241-7~deb10u1
> Severity: normal
>
> I have a mount unit as follows
>
> [Unit]
> Requires=systemd-cryptsetup@backup.service
> StopWhenUnneeded=true
>
> [Mount]
> What=/dev/phobos_backup/backup
>
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:
> - failed 'powerof
Seems like Conflicts= do not work reliably to ensure the
systemd-timesyncd.service is not started during boot.
See also the upstream bug report
https://github.com/systemd/systemd/issues/7104
We've re-added the Conditions to systemd-timesyncd.service.
#
Am 04.10.19 um 13:34 schrieb Rado S:
> =- Michael Biebl wrote on Thu 3.Oct'19 at 13:51:28 +0200 -=
>
>>> How to find more information on this failure?
>>
>> Do you get any shutdown messages from systemd when you shut down?
>
> No, the screen is black all
Am 04.10.19 um 13:34 schrieb Rado S:
>> Please also follow the hints in
>> /usr/share/doc/systemd/README.Debian.gz (Debugging boot/shutdown problems)
>>
>> See the section starting with "In situations where the debug shell is
>> not available,..."
>
> I've attached the so produced log-file.
>
>
Am 03.10.19 um 13:12 schrieb Alexandra N. Kossovsky:
> Thank you for your patience.
>
> I've submitted the part of the issue which (by my opinion) is a clear
> bug: https://github.com/systemd/systemd/issues/13712
>
Thanks Alexandra.
--
Why is it that all of the instruments seeking intelligent
Am 03.10.19 um 12:43 schrieb Alexandra N. Kossovsky:
> My point is, it is a major change in behaviour, and users should be
> notified via NEWS.Debian. The notification should include the
> instructions how to get the old behaviour.
Ok, it was not clear to me, whether you considered this new
Hi
Am 03.10.19 um 10:17 schrieb Benjamin Poirier:
> Package: udev
> Version: 243-2
> Severity: normal
>
> /lib/udev/rules.d/73-usb-net-by-mac.rules prevents the renaming of network
> interfaces from usb adapters using the systemd.link(5) mechanism.
>
> The latter is implemented using
Control: tags -1 + moreinfo
Am 26.09.19 um 23:28 schrieb Rado Q:
> I tried to get more clues using the advice here:
> http://freedesktop.org/wiki/Software/systemd/Debugging/
>
> systemd.debug-shell=1 systemd.log_level=debug systemd.log_target=kmsg
> log_buf_len=1M printk.devkmsg=on enforcing=0
Control: tags -1 - patch
Am 13.10.19 um 21:41 schrieb Jesse Smith:
> On 10/13/19 4:33 PM, Michael Biebl wrote:
>> Control: tags -1 + moreinfo
>> Will insserv fail if the version is too old, i.e. do we need a versioned
>> dependency (or rather versioned Breaks)?
>
Control: tags -1 + moreinfo
Am 12.10.19 um 15:56 schrieb Rado Q:
> Package: systemd
> Version: 241-7~deb10u1
>
> Dear Maintainer,
>* What led up to the situation?
> Installation of debian10.
>
>* What exactly did you do (or not do) that was effective (or ineffective)?
> Boot.
>
>*
Control: tags -1 + moreinfo unreproducible
Am 13.10.19 um 15:12 schrieb Corcodel Marian:
> Package: systemd
> Version: 232-25+deb9u12
> Severity: normal
>
> Hi, when try to enable global pulseaudio.socket missing subdir
> etc/systemd/user/socket.target.wants and need create manual.
> $systemctl
Control: tags -1 + moreinfo
On Sat, 28 Sep 2019 15:21:17 -0300 Jesse Smith
wrote:
> This has been addressed upstream in insserv by allowing the program to
> accept changes like this silently. All we need now is for update-rc.d to
> be updated to use the new behaviour (enabled with the -q flag)
Am 22.12.19 um 07:51 schrieb Paul Szabo:
> Package: systemd
> Version: 241-7~deb10u2
> Severity: normal
> Tags: patch
>
> Lately (since buster?) I observe that "After=network.target" is ineffective,
> maybe because dhcpcd runs asynchronously. I seem to get good results by
> creating a file
>
>
Control: severity -1 minor
Am 18.12.19 um 15:28 schrieb Dejan Muhamedagic:
> Package: systemd
> Version: 241-7~deb10u2
> Severity: important
>
> Dear Maintainer,
>
> Listing systemd units takes more than a second on a rather fast
> system:
>
> # time systemctl list-unit-files | wc
> 351
Control: reassign -1 ifupdown
Am 18.12.19 um 17:58 schrieb Joshua:
> Package: systemd
> Version: 241-7~deb10u2
> Severity: important
>
> Dear Maintainer,
>
> systemd gets stuck in boot waiting for eth0 to start.
>
> (Yes it is eth0. The assumptions in predictable network interface
> names
Am 05.12.19 um 09:55 schrieb Sven Joachim:
> Package: udev
> Version: 244-3
> Severity: important
>
> According to /usr/share/doc/udev/README.Debian.gz,
>
> ln -s /dev/null /etc/systemd/network/99-default.link
>
> should be sufficient to keep the kernel-provided network interface
> names.
Am 13.02.20 um 13:39 schrieb Michael Biebl:
> I guess you'd have to convince upstream that this is a good idea to add
> such a check.
The upstream bug tracker is at https://github.com/systemd/systemd/issues
signature.asc
Description: OpenPGP digital signature
Am 13.02.20 um 13:29 schrieb Trent W. Buck:
> Package: udev
> Version: 241-7~deb10u3
> Severity: wishlist
> File: /sbin/udevadm
>
> Packages like udisks2 run "udevadm trigger" in their postinsts.
> When building a Debian Live image, if /proc is mounted in the chroot, all is
> well.
> When
Am 13.02.20 um 14:03 schrieb Trent W. Buck:
> Michael Biebl wrote:
>> Am 13.02.20 um 13:29 schrieb Trent W. Buck:
>>> Packages like udisks2 run "udevadm trigger" in their postinsts.
>>> When building a Debian Live image, if /proc is mounted in the chroot
Am 09.02.20 um 02:24 schrieb Ryutaroh Matsumoto:
> Control: tags -1 + fixed - moreinfo
> Control: retitle -1 Fix found: systemd-sysusers hangs if nis is
> enabled in a systemd-nspawn container
>
> I found a solution (or a workaround).
>
> The problem is that
> (1) systemd-sysusers tries to use
Control: tags -1 + moreinfo unreproducible
Am 25.02.20 um 07:42 schrieb gulfstream:
> Package: systemd
> Version: 244.3-1
> Severity: normal
>
>
> Hi, the wired interface name maybe changed when root. Sometimes the wired
> interface's name is "enp0s31f6", sometimes it is "eth0". I think it
Am 26.02.2020 um 05:26 schrieb wg...@china.com:
> When the wired interface was be named enp0s31f6:
>
The journal logs as well please.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital
Am 26.02.20 um 12:42 schrieb wg...@china.com:
>
> some of contents kern.log is attached. Thank you!
>
A verbose debug log (journalctl -alb) please from a failed boot as
described in the wiki.
signature.asc
Description: OpenPGP digital signature
Control: reassign -1 laptop-mode-tools
Control: retitle -1 lmt breaks network interface renaming
Control: severity -1 serious
Am 26.02.20 um 16:01 schrieb wg...@china.com:
> As your recommendation, I removed the laptop-mode-tools, it seems that wired
> interface' name is correct for several
Am 26.02.20 um 14:40 schrieb wg...@china.com:
>
> The attachment file 111.txt is the ouput of command "journalctl -alb". Thank
> you!
Ok, thanks.
Here's the relevant part of the log:
2月 26 21:34:29 athena systemd-udevd[499]: eth0: Failed to rename
network interface 2 from 'eth0' to
Am 28.02.20 um 21:57 schrieb Kevin Locke:
> Package: systemd
> Version: 244.3-1
> Severity: normal
>
> Dear Maintainer,
>
> This morning my ThinkPad T430 failed to boot with the message:
>
> Error: The non-volatile variable storage is about full
> Press F1 to enter Setup.
>
> The cause
Am 03.03.20 um 11:16 schrieb Sergio Gelato:
> Package: udev
> Version: 241-7~deb10u3
>
> After upgrading a system from stretch to buster, the names of some network
> interfaces changed unexpectedly. Specifically:
>
> stretch# udevadm test-builtin net_id /sys/class/net/enp94s0f0
>
Am 28.02.20 um 10:00 schrieb Janusz S. Bień:
> On Fri, Feb 28 2020 at 9:25 +01, Michael Biebl wrote:
>> Am 28.02.20 um 08:17 schrieb Janusz S. Bień:
>>> Package: systemd
>>> Version: 241-7~deb10u3
>>> Severity: normal
>>>
>>> Dear Maintaine
Am 28.02.20 um 08:17 schrieb Janusz S. Bień:
> Package: systemd
> Version: 241-7~deb10u3
> Severity: normal
>
> Dear Maintainer,
>
> This is a fresh install of buster on a just bought HP 15-rb063nw
> (7SG28EA) laptop. Following the suggestions found in the Internet I
> tried adding to
Am 20.02.20 um 18:21 schrieb Tomas Barton:
> Package: systemd
> Version: 232-25+deb9u12
> Severity: important
>
> Dear Maintainer,
>
> I'm having problem with systemd-networkd.service that are likely linked
> to latest stretch patch 232-25+deb9u12.
Can you reproduce the problem with systemd
Am 13.02.20 um 14:03 schrieb Trent W. Buck:
> Michael Biebl wrote:
>> Am 13.02.20 um 13:29 schrieb Trent W. Buck:
>> I guess you'd have to convince upstream that this is a good idea to add
>> such a check.
>>
>> Once upstream has such a patch, we can cherry-pick i
Control: tags -1 moreinfo unreproducible
On Thu, 12 Dec 2019 19:05:09 +0100 chrysn wrote:
> Package: systemd
> Version: 244-3
> Severity: normal
> File: /usr/share/man/man5/logind.conf.5.gz
>
> The documentation about KillUserProcesses claims that processes will be
> left alive after user
Am 26.01.20 um 01:29 schrieb Michael Biebl:
> This works fine for me, so I can reproduce the issue with the given
can *not* reproduce ...
signature.asc
Description: OpenPGP digital signature
On Mon, 9 Sep 2019 09:10:39 +0200 Marc Haber
wrote:
> On Sat, Aug 10, 2019 at 12:37:04PM +0200, Marc Haber wrote:
> > Of course not, but no components that I have installed willingly. I'll roll
> > out
> > a monitoring job that runs more often than once daily so that the change
> > gets
> >
Control: tags -1 + moreinfo
On Mon, 9 Dec 2019 00:31:29 +0100 Vincent Lefevre
wrote:
> Package: udev
> Version: 244-3
> Severity: minor
>
> I've noticed the following error (in red) in the journalctl output:
>
> Dec 09 00:10:18 zira systemd-udevd[506]: event4: Failed to call EVIOCSKEYCODE
>
On Mon, 18 Mar 2019 08:32:32 +0100 Marc-Robin Wendt
wrote:
> Hello Michael,
>
> no, I'm using Intel driver and cards. i915 is loaded.
> Problem is not solved anyway. I helped myself in disabling automatic
> suspend at all and have to do it manually now.
>
Please attach the verbose debug log
Am 27.01.20 um 11:17 schrieb Vincent Lefevre:
> On 2020-01-26 01:48:06 +0100, Michael Biebl wrote:
>> Control: tags -1 + moreinfo
>>
>> On Mon, 9 Dec 2019 00:31:29 +0100 Vincent Lefevre
>> wrote:
>>> Package: udev
>>> Version: 244-3
>>> Se
like CacheDirectory and
+StateDirectory are properly chowned to the user specified in User= before
+launching the service. (Closes: #919231)
+
+ -- Michael Biebl Wed, 29 Jan 2020 19:07:53 +0100
+
systemd (241-7~deb10u2) buster; urgency=medium
* core: never propagate reload failure
701 - 800 of 1843 matches
Mail list logo
