Am 08.01.19 um 13:37 schrieb Dmitry Bogatov:
>
> control: tags -1 +moreinfo
>
> Seems old discussion did not ended in solution. Let us try again.
>
> Dear udev maintainers, did anything changed? Are there still problems
> running /etc/init.d/udev from runlevel 1 (when udev daemon was killed)
>
Am 08.01.19 um 14:38 schrieb fakefur:
> hi again
>
> sorry i did not reassign it to udev - the kernel people did
My question was targeted at Ben Hutchings, our kernel maintainer.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
en - i have to unload usbhid to get the touchscreen disabled,
> which of course disables usb mice but i'm using bluetooth for now so i
> can live with this
>
> hth
> :)
>
> On Tue, 2019-01-08 at 12:58 +0100, Michael Biebl wrote:
>> On Fri, 04 Jan 2019 10:19
On Mon, 7 Jan 2019 12:27:10 -0800 Isaac Gelado wrote:
> I am having this very same issue. If I run
>
> udevadm trigger --type=subsystems --action=add
> udevadm trigger --type=devices --action=add
>
> in the initramdfs shell, it does nothing at all. However, if I run
>
> udevadm trigger
Am 04.01.19 um 21:49 schrieb Patrick Häcker:
> I think the state to see the problem is quite reproducible: First install
> systemd 239 and afterwards install systemd 240, i.e. I can recreate whatever
> state you need.
It is indeed reproducible easily, which is why I raised this upstream
Am 08.01.19 um 17:38 schrieb Michael Biebl:
> Am 08.01.19 um 16:43 schrieb Isaac Gelado:
>> Adding sleep 1 does not work. I also check that the -v flag is only
>> needed in one of the calls to udevadm.
>
> Urgh, this is getting really weird.
> -v should not affect
Am 08.01.19 um 18:11 schrieb Isaac Gelado:
> As a side hint that might be helpful. I had two kernels 4.18 and 4.19
> in my system. This problem started when I first boot 4.19, while I was
> able to boot 4.18 without problems. At some point I decided to do an
> `update-initramfs -k all -u` and the
Am 04.01.19 um 12:22 schrieb Michael Biebl:
> For completeness sake, can you also post the output of
> stat /var/lib/systemd/timesync/clock
Make that
stat /var/lib/private/systemd/timesync/clock
(I missed that you already deleted /var/lib/systemd/timesync/)
--
Why is it th
Am 04.01.19 um 11:48 schrieb Patrick Häcker:
> Hello,
>
>> Can you post the output of
>> ls -ld /var/lib/systemd/timesync
>> ls -la /var/lib/private/systemd/
>
> root@mmm /h/pat# ls -ld /var/lib/systemd/timesync
> lrwxrwxrwx 1 root root 27 Jan 3 2018 /var/lib/systemd/timesync -> ../
>
Hello,
systemd-timesyncd.service in previous releases used DynamicUser=true.
This will create a symlink /var/lib/systemd/timesync pointing at
../private/systemd/timesync and make sure it is properly owned by
systemd-timesync:systemd-timesync
This was reverted upstream in
Am 04.01.19 um 10:23 schrieb Michael Biebl:
> Hello,
>
> systemd-timesyncd.service in previous releases used DynamicUser=true.
> This will create a symlink /var/lib/systemd/timesync pointing at
> ../private/systemd/timesync and make sure it is properly owned by
> systemd-timesyn
Am 27.12.18 um 23:09 schrieb Ben Caradoc-Davies:
> And I am also please to report that the two-minute wait on shutdown seen
> here after upgrade to 240-1 and also after upgrade to 240-2 occurs only
> on the first shutdown after upgrade:
>
Am 28.12.18 um 01:41 schrieb Ricardo Peliquero:
> Thank you Michael,
>
> I've just updated from 239-15 to 240-2; but, unfortunately, none of the
> problems were solved.
>
Too bad, this sounded like it could be the same issue as #917124 :-/
Unfortunately I'm a bit at a loss atm.
I wonder if this
Am 02.01.19 um 10:11 schrieb Pali Rohár:
> On Friday 28 December 2018 21:36:03 Michael Biebl wrote:
>> What also needs to be considered is, that quite a few packages already
>> build-depend on udev.
>> By splitting out udev.pc, we might break those packages.
>
> Hm
Hi Gregor
Am 03.01.19 um 20:45 schrieb gregor herrmann:
> Following the next suggestion in the upstream ticket, I've now added
>
> udevadm trigger --type=subsystems --action=add
>
> (on top of the b261494 patch, not sure if this is needed) to the init
> script; and lo and behold, all seems
Control: forcemerge -1 918841
Am 11.01.19 um 17:20 schrieb shirish शिरीष:
> It is very much possible that you may be working on it, in any case,
> look forward to the fixes.
Already filed in the bug tracker (as RC).
Merging with duplicate
--
Why is it that all of the instruments seeking
Am 12.01.19 um 01:02 schrieb Axel Beckert:
> Control: reopen -1
> Control: found -1 240-3
> *sigh* I'm sorry to say, but it just happened again with udev 240-3
> and kernel 4.20-1~exp1.
Would be good to know, if it also happens with 239-15 or if it's caused
by some other update.
Tbh, udevd or
Please also tar up /etc/udev/rules.d and /lib/udev/rules.d and attach it
to the bug report.
--
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
Control: tags -1 + moreinfo
On Sat, 12 Jan 2019 20:12:22 +0100 Julien Aubin
wrote:
> Package: udev
> Version: 240-2
> Severity: normal
>
> Dear Maintainer,
>
> After upgrading from Stretch to Buster I noticed that my computer had
> problems suspending to RAM, basically it fails randomly. It was
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:
Am 13.01.19 um 10:46 schrieb intrigeri:
> Hi!
>
> In Tails we're shipping systemd/stretch-backports. We will freeze our
> code base (and the APT repositories we use) on Jan 18 for our next
> major release, so in the current state of things we would ship
> 239-12~bpo9+1, which is vulnerable to
Control: forwarded -1 https://github.com/systemd/systemd/issues/11416
Thanks,
forwarded this issue upstream.
I replaced the backtrace with one where libudev1-dbgsym and udev1-dbgsym
is installed [1]
Regards,
Michael
[1] https://wiki.debian.org/HowToGetABacktrace
--
Why is it that all of the
On Wed, 9 Jan 2019 15:05:38 +0100 Trek wrote:
> if dpkg will not be updated with the new sd-notify interface, I think
> it would be better to rollback the #791944 patch: the system will not
> shutdown correctly with cryptsetup, but at least it can boot (with and
> without cryptsetup)
Can you
Am 28.12.18 um 15:49 schrieb Pali Rohár:
> On Friday 28 December 2018 15:32:45 Michael Biebl wrote:
>> Control: severity -1 wishlist
>>
>> Am 28.12.18 um 15:11 schrieb Pali Rohár:
>>> Package: udev
>>> Version: 240-2
>>>
>>> Currently pkg
Am 28.12.18 um 09:40 schrieb Rafał Olejnik:
> lvm2-activation-generator: lvmconfig failed
>
> lvm2-activation-generator: Activation generator failed.
Those error messages are unrelated to this particular issue. They are
caused by the latest lvm2 update.
See
What also needs to be considered is, that quite a few packages already
build-depend on udev.
By splitting out udev.pc, we might break those packages.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Am 28.12.18 um 07:04 schrieb Ben Hutchings:
> And if you downgrade udev and libudev1 to version 239-15, that will
> trigger an update of the 4.19 initramfs (only) and you should then be
> able to boot with Linux 4.19.
Or upgrade to udev 240-2, which should fix this issue.
signature.asc
Control: tags -1 moreinfo unreproducible
Am 09.01.19 um 11:16 schrieb Axel Beckert:
> Hi,
>
> Axel Beckert wrote:
>> I have no idea why this is happening, but several packages use "udevadm
>> control --reload-rules" in their postinst (e.g. fuse) and if that's run,
>> all process except init are
Am 09.01.19 um 07:32 schrieb Axel Beckert:
> Package: udev
> Version: 240-2
Is this specific to version 240-2?
Could you try downgrading udev to either 239-15 or 240-1 and report back
with the results.
Thanks,
Michael
--
Why is it that all of the instruments seeking intelligent life in the
Control: tags -1 + moreinfo
Am 09.01.19 um 19:26 schrieb Adrian Almenar:
> Package: systemd
> Version: 240-2
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>* What exactly
On Wed, 09 Jan 2019 21:08:51 +0100 Salvatore Bonaccorso
wrote:
> Source: systemd
> Version: 204-1
> Severity: grave
> Tags: security upstream
> Justification: user security hole
> Control: found -1 232-25+deb9u6
> Control: found -1 240-2
>
> Hi,
>
> The following vulnerability was published for
Am 09.01.19 um 22:45 schrieb Michael Biebl:
> Should CVE-2018-16864, CVE-2018-16865 and CVE-2018-16866 be handled
> separately, i.e. do you plan to file separate bug reports?
Hm, for some reason I only received #918848 just now.
So that part of my question is moot.
Regards,
Michael
-
forcemerge 908796 917247 917185
thanks
I'm now convinced this is just another incarnation of
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908796
Sorry for not thinking about this earlier.
The only difference seems to be, that with v240 it has become more
likely that this race condition is
On Fri, 04 Jan 2019 10:19:06 +0100 fakefur wrote:
> makes no difference
> i cannot disable the touchscreen
>
By "cannot disable the touchscreen", I assume you mean that the
hid_multitouch kernel module is loaded?
What's the output of
# lsmod | grep hid_multitouch
# grep hid_multitouch
On Tue, 18 Dec 2018 12:20:06 +0100 Michael Biebl wrote:
> Am 18.12.2018 um 12:09 schrieb Raphael Manfredi:
> > Quoting Michael Biebl:
> > : What happens if you boot into emergency mode (add emergency to the
> > : kernel command line)?
> > : This will start a very
Am 08.01.19 um 12:53 schrieb Vincent Lefevre:
> On 2019-01-06 12:30:04 +, Jakub Sokołowski wrote:
>> On Sun, 6 Jan 2019 08:33:09 +0100 ludszuweit1
>> wrote:
>>> Is it possible, that dev 240-2 have problems to boot with m2 connected
>>> SSDs?
>>
>> I don't use m2(though I do have it). I'm
Am 09.09.18 um 16:56 schrieb Felipe Sateler:
> We have had this reaction a number of times. Shipping systemd.pc in a
> separate package comes to mind. Perhaps we have a number of such "extra"
> files that could be bundled into this extra package?
You mean, introducing a systemd-dev package? Hm...
On Sun, 11 Mar 2018 19:48:30 +0100 Marc Haber
wrote:
> found #869995 232-25+deb9u1
> found #869995 232-25+deb9u2
> tags #869995 patch stretch
> thanks
>
> Hi,
>
> I have missed that this bug was actually closed for good. I can confirm
> that the issue is fixed in sid and buster, but is is still
Am 13.09.18 um 11:11 schrieb kochtopf:
>> MemoryDenyWriteExecute=yes
>
> Commenting this fixed the issue. Thank you very much for helping me out.
> This issue can be closed. NOTE: The same needed to be done for
> systemd-logind.service and systemd-journald.service too!
Ah, that rings a bell. Do
Am 13.09.18 um 23:22 schrieb Chris Lamb:
> Nice work. Is this…
>
>
> https://salsa.debian.org/systemd-team/systemd/commit/2e03e24734ef51cd47e1dd0ded3a701bbc936cbf
Those are the changes from
https://github.com/systemd/systemd/pull/10067
which drop the usage of the hard-coded
Am 13.09.18 um 09:51 schrieb Chris Lamb:
> Hi Vagrant,
>
>> Is it plausible to strip the embedded build directory information out of
>> the test binaries with the binaries shipped in the package
Just curious: which tool would you use for such a case?
> But why not hardcode said path to
Am 12.09.18 um 15:25 schrieb kochtopf:
> Sep 12 15:19:05 pi2 systemd-journald[93]: Journal stopped
> -- Logs begin at Wed 2018-09-12 15:06:28 CEST, end at Wed 2018-09-12
> 15:19:05 CEST. --
> -- No entries --
> ● systemd-udevd.service - udev Kernel Device Manager
> Loaded: loaded
Am 12.09.18 um 14:41 schrieb kochtopf:
>> I guess this should be version 239-8?
>
> Yes
>
>> Can you include the output of
>> journalctl -alb
>> journalctl -u systemd-udevd.service
>> systemctl status systemd-udevd.service
>
> I'm still on rsyslog. I don't use journalctl yet.
Just include the
control: tags 916880 + fixed-upstream patch
control: fixed 916880 234-1
(updated the meta-data)
Hi,
thanks for the detailed bug report.
Am 19.12.18 um 19:57 schrieb PODURY, SHARMILA:
> commit 5b3cc0c86aeddd4615e7e28e79aa89e5b77a6507
> Author: Yusuke Nojima
> Date: Sun Apr 30 02:37:53 2017
On Mon, 19 Feb 2018 11:25:56 +0100 Michael Biebl wrote:
> Am 12.02.2018 um 18:02 schrieb Calum Mackay:
> > Package: systemd
> > Version: 237-2
> > Severity: normal
> >
> > Dear Maintainer,
> >
> > The -g/--grep option was recently added to the ma
Am 03.04.19 um 01:58 schrieb Christoph Anton Mitterer:
> On Wed, 2019-04-03 at 00:15 +0200, Michael Biebl wrote:
>> Feel free to submit additions/corrections/updates to the release-
>> notes,
>> if you think those changes are not satisfactory.
>
> I think it's good s
Am 26.03.19 um 16:01 schrieb Celelibi:
> Note that some hunks apply with an offset. But nontheless, it applies
> and work.
Thanks for testing the patch. Very much appreciated.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
iesChanged` signal.
This reproduces <https://github.com/systemd/systemd/issues/11944> and
also the earlier <https://github.com/systemd/systemd/issues/9672>.
[ Michael Biebl ]
* Disable fallback DNS servers in resolved (Closes: #923081)
* cgtop: Fix processing of controllers
Hi,
so far the bug reports all mention that this is specific to AMD hardware.
Does the affected system have an AMD CPU/graphics card?
--
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 03.04.19 um 18:08 schrieb Felipe Sateler:
> Looks like sysvinit-core needs XB-Important: yes to prevent such easy
> removal.
I though about this too, but on the other hand with "init" we actually
allow users to switch between sysvinit and systemd and adding
XB-Important: yes to sysvinit-core
On Wed, 27 Feb 2019 10:33:48 -0300 Felipe Sateler
wrote:
> Control: found -1 241-5
> Control: tags -1 confirmed upstream
> Control: forwarded -1 https://github.com/systemd/systemd/issues/11842
>
> I was able to reproduce the issue, and forwarded this upstream.
Seems like something which we
Am 03.04.19 um 20:34 schrieb Felipe Sateler:
> On Wed, Apr 3, 2019 at 1:23 PM Michael Biebl <mailto:bi...@debian.org>> wrote:
> I have no idea how common that is, so maybe an alternative could be to
> move the libpam-systemd Recommends from systemd to systemd-sys
Am 28.03.19 um 11:08 schrieb wf...@niif.hu:
> Felipe Sateler writes:
>
>> I'm not opposed to a backport, and I don't think there are many
>> problems with attempting it. However, I do not have time to prepare
>> and test such a backport. Help welcome.
>
> I can do the busy-work of backporting,
On Wed, 13 Mar 2019 01:10:09 -0500 Bob Tracy wrote:
> On Tue, Mar 12, 2019 at 12:37:27PM +0100, Michael Biebl wrote:
> > I can't really trawl through the complete config file.
> > What I noticed from the journal are errors like this
> >
> > Feb 14 04:12:20 smirkin syst
Am 30.03.19 um 18:11 schrieb Iiro Laiho:
> Package: systemd
> Version: 232-25+deb9u9
> Severity: important
> Tags: l10n
>
> Dear Maintainer,
>
> When I set the system keymap using the "localectl" command, the
> application of the new layout to the virtual consoles is delayed. The
> delay seems
https://ftp-master.debian.org/backports-new.html
> Am 31.03.2019 um 16:31 schrieb wf...@niif.hu:
>
> Michael Biebl writes:
>
>> Personally I prefer to revert the compat bumps when doing backports for
>> stretch (like in [1]) as I like to to keep the impact on the sta
Control: tags -1 moreinfo
Am 07.04.19 um 18:51 schrieb Andy Ruddock:
> Package: systemd
> Severity: critical
>
> I'm running Windows 10 (Home edition - up to date) on the desktop, with
> Virtualbox (v6.0.4).
> I've used both the netinst CD & the testing DVD (downloaded today -
> 07/Apr/2019) to
Hi
Am 07.04.19 um 19:29 schrieb Eythan Weg:
> Hi,
>
> I hope this is the right place to seek help for my difficulty.
>
> I have been a way for sometime with my desktop shutdown, and upon my
> return had some trouble that I misdiagnosed and along the way I have
> upgraded systemd, lightdm, dbus
On Thu, 28 Feb 2019 12:06:10 + Dmitry Bogatov
wrote:
>
> control: reassign -1 udev
>
> [2019-02-27 08:00] shirish शिरीष
> > > Seems there is no /etc/init.d/mountkernfs.sh on your system.
> > >
> > > Since your init system is systemd, I question, why do you need insserv
> > > in first
On Mon, 25 Feb 2019 14:29:42 + Toni Mueller wrote:
>
>
> reopen 923081
> thanks
>
>
> Hi Andreas,
>
> On Mon, Feb 25, 2019 at 09:25:48AM +0100, Andreas Henriksson wrote:
> > (Not sure why you think Cloudflare is a problem but Google is not, but
> > oh well.)
>
> well, I think you
On Wed, 23 Jan 2019 14:54:48 -0800 Josh Triplett
wrote:
> On Wed, Jan 23, 2019 at 07:52:24PM -0300, Felipe Sateler wrote:
> > On Wed, Jan 23, 2019 at 4:15 PM Josh Triplett wrote:
> > > Package: systemd
> > > Severity: normal
> > >
> > > I installed using the Buster Alpha 4 installer, and for
I might be missing something obvious here, but why is the service
started after installation if it's not configured?
And if the package insist on this behaviour, why does it not use the
existing dh_installinit --error-handler mechanism to explicitly define
the behaviour it wants?
I'm not
Control: severity -1 wishlist
On Wed, 16 Jan 2019 12:44:28 -0600 "Karl O. Pinc" wrote:
> Package: systemd
> Version: 232-25+deb9u8
> Severity: normal
>
> Hi,
>
> systemd security updates to stable
> systemd (232-25+deb9u8) stretch-security; urgency=high
> systemd (232-25+deb9u7)
On Fri, 08 Feb 2019 22:24:24 + Qaz W wrote:
> Package: udev
> Version: 232-25+deb9u8
> Severity: normal
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
> Tried to implement a keyboard remapping
Hi dato,
On Mon, 21 Jan 2019 16:34:43 -0300 Dato wrote:
> $ sudo ls -ld /run/log/journal{,/ef...}
> drwxr-xr-x 3 root root 60 Jan 21 16:24 /run/log/journal
> drwxr-x--- 2 root root 60 Jan 21 16:24 /run/log/journal/ef...
>
> It would be great to see group ownership and ACLs fixed
Control: reassign -1 mysql-server-5.7
Hi Robie
On Fri, 8 Feb 2019 10:57:10 + Robie Basak
wrote:
> Hi,
>
> Could this be the issue described here:
> https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1600164 ?
>
> Apart from that, I don't know of anyone else affected by this, so I
>
Control: tags -1 + moreinfo
Hi
On Wed, 20 Feb 2019 14:20:19 -0800 Szabolcs Fruhwald
wrote:
> We experienced the same issue. After debugging it with gdb, found the
> culprit and created a fix / PR on systemd github repo:
> https://github.com/systemd/systemd/pull/11775
Hm, interesting.
I see
Control: reassign -1 lxc
On Wed, 16 Jan 2019 09:52:47 +0100 Matthijs Kooijman
wrote:
> severity 919259 normal
> found 919259 232-25
> retitle 919259 Reexecuting fails in containers without CAP_SYS_ADMIN
> thanks
>
> Hey Michael,
>
> > My suggestion would be to roll back to 232-25+deb9u1 and
Control: tags -1 + moreinfo
On Sat, 19 Jan 2019 09:15:37 +0100 Nicolas Patrois
wrote:
> Package: systemd
> Version: 240-4
> Severity: normal
>
> Dear Maintainer,
>
> Since systemd’s last upgrade, I can’t suspend with the XF86Sleep key.
> systemd seems a bit broken:
>
> # systemctl --failed
>
Control: tags -1 + moreinfo
On Sat, 19 Jan 2019 17:11:17 -0600 Bob Tracy wrote:
> Package: systemd
> Version: 240-4
> Severity: important
>
> Dear Maintainer,
>
> Sometime between December 2017 and late 2018 (the time period between when my
> most recent backups were made and when I had
Control: tags -1 + moreinfo
Hi
On Sun, 03 Feb 2019 13:59:02 -0600 william l-k
wrote:
> Package: systemd
> Version: 240-4
> Severity: important
>
> Dear Maintainer,
>
> For a while now my system would hang on reboot with waiting for stop job
> message. The wait is set to 2 min and I'm sure I
Am 28.02.19 um 14:08 schrieb Michael Biebl:
>> Since initramfs-maintainer says, that initramfs-tools do not invoke
>> insserv, another guess is udev/init-system-helpers. Reassigning for
>> udev.
>
> Dmitry, since you reassigned this to udev without further explanation,
Control: tags -1 + wontfix
Am 02.03.19 um 00:27 schrieb Thorsten Glaser:
> reopen 923559
> thanks
>
> Debian Bug Tracking System dixit:
>
>> If this explanation is unsatisfactory and you have not received a
>> better one in a separate message then p
Control: tags -1 + moreinfo
[snip]
I don't understand what this bug report is supposed to be about.
Is it about sshd.service using RestartPreventExitStatus=255 (in which
case you should file the bug report against the openssh-server) package.
Or is it about your drop-in snippets not being
Am 01.03.19 um 08:59 schrieb Andrew Roberts:
> Package: systemd
> Version: 232-25+deb9u
>
> On Debian 9 stretch with the latest updates systemd no longer restarts
> sshd due to changes to the sshd.service unit file.
>
> The line:
>
> RestartPreventExitStatus=255 has been added to the master
Am 02.03.19 um 09:28 schrieb Michael Biebl:
> http://bugs.debian.org/778913 contains more information why it
> was added to ssh.service. Short version: sshd will return with an exit
> code of 255 when your config file contains errors. Repeatedly restarting
> sshd in that case is no
Am 06.03.19 um 10:07 schrieb Mark Hindley:
> On Tue, Mar 05, 2019 at 09:11:28PM +0100, Michael Biebl wrote:
>>>> This has the potential for some interesting breakage, like the real
>>>> systemd being installed and used together with libelogind0.
>>>> We
Am 06.03.19 um 13:17 schrieb Dan Poltawski:
> We are seeing this bug on the jessie ( systemd 215-17+deb8u10) and it's
> extremely serious, leading to systemd-journald eventually consuming all
> memory on the system. Is there a fix for jessie incoming?
jessie is oldstable and no longer
Hi Stephane
Am 06.03.19 um 18:28 schrieb Stephane Chazelas:
> Package: systemd
> Version: 241-1
> Severity: normal
> Tags: patch upstream
>
> Dear Maintainer,
>
> At work, users (in LDAP) have home directories set as
> /export/./home/username. The /./ is used for instance by vsftpd
> to
To rule out the obvious, can you paste the output of
apt-cache policy dbus-user-session dbus-x11
(you want dbus-user-session if you are using systemd --user)
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Control: forwarded -1 https://github.com/systemd/systemd/pull/11912
Am 06.03.19 um 23:29 schrieb Stephane Chazelas:
> 2019-03-06 19:25:33 +0100, Michael Biebl:
> [...]
>> Please consider forwarding it to upstream at
>> https://github.com/systemd/systemd as pull request
>&
Am 05.03.19 um 12:43 schrieb Michael Biebl:
> Am 03.03.19 um 23:27 schrieb Thorsten Glaser:
>> Could you please, at least, forward the attached patch upstream,
>> if you’re not willing to maintain it downstream?
>
> Sure. To do that, can you please provide a git fo
Am 03.03.19 um 23:27 schrieb Thorsten Glaser:
> Could you please, at least, forward the attached patch upstream,
> if you’re not willing to maintain it downstream?
Sure. To do that, can you please provide a git formatted patch against
the upstream sources.
You probably want to add a bit more
Am 05.03.19 um 15:34 schrieb Mark Hindley:
>
> reassign -1 elogind
> retitle -1 Make libelogind0 ABI compatible with libsystemd0
> tags -1 + pending
> thanks
>
> On Wed, Feb 27, 2019 at 05:12:50PM +, Mark Hindley wrote:
>> We are currently liasing with elogind upstream who are making
Am 05.03.19 um 18:17 schrieb Mark Hindley:
> On Tue, Mar 05, 2019 at 05:58:30PM +0100, Michael Biebl wrote:
>> Am 05.03.19 um 15:34 schrieb Mark Hindley:
>>>
>>> reassign -1 elogind
>>> retitle -1 Make libelogind0 ABI compatible with libsystemd0
>>> tag
Control: reassign -1 insserv
On Thu, 28 Feb 2019 19:13:31 -0300 Felipe Sateler
wrote:
> On Thu, Feb 28, 2019 at 6:50 PM Michael Biebl wrote:
> >
> > Am 28.02.19 um 14:08 schrieb Michael Biebl:
> >
> > >> Since initramfs-maintainer says, that initramfs-tools do n
Am 05.03.19 um 22:40 schrieb Trek:
> On Tue, 5 Mar 2019 09:46:53 +0100
> Andreas Henriksson wrote:
>
>> You likely also want to include in your patch a debian/control
>> change that makes udev depend on a new enough dpkg which has the
>> new flags you're making use of.
>
> right, a new patch is
Hi
Am 14.03.19 um 15:16 schrieb Johan Wassberg:
> Package: systemd
> Version: 232-25+deb9u9
> Severity: important
>
> Dear Maintainer,
> this issue is a bit outside my confort zone but I still want to try to
> report this bug.
>
> It is probably the same as Launchpad#1800836[0] and according to
On Sun, 17 Mar 2019 10:53:57 +0200 Vincas Dargis wrote:
> I just tested on GNOME Sid, also cannot access smartphone via MTP:
>
> Mar 17 10:52:41 debian-sid-gnome gvfsd[1241]: error returned by
> libusb_claim_interface() = -6LIBMTP
> PANIC: Unable to initialize device
> Mar 17 10:52:42
On Mon, 18 Jun 2018 09:09:49 +0200 Michael Biebl wrote:
> Control: tags -1 + moreinfo
>
> On Sat, 21 Nov 2015 00:10:59 -0500 Brian Minton wrote:
> > Package: systemd
> > Version: 228-2
> > Severity: normal
> >
> > -BEGIN PGP SIGNED MESSAGE-
&g
Control: tags -1 + moreinfo
Hi Matvey,
sorry for not getting back to you earlier.
Can you still reproduce the issue on an up-to-date buster system with
systemd v241?
On Tue, 4 Aug 2015 05:50:55 -0400 Matvey Soloviev
wrote:
> Package: systemd
> Version: 222-2
> Severity: normal
>
> Dear
Control: tags -1 + moreinfo
On Fri, 02 Oct 2015 21:01:07 +0200 =?utf-8?q?J=C3=BCrgen_Bausa?=
wrote:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
>
> Dear Maintainer,
>
> I am running jessie on a laptop with wlan (Networkmanager) and want to use
> autofs to mount nfs shares,
Control: reassign -1 open-iscsi
On Sat, 11 Jun 2016 05:35:52 +0200 Klaus Pieper wrote:
> Package: systemd
> Version: 230-2
> Severity: normal
>
> Dear Maintainer,
>
> * installed on iscsi target with the beta installer which worked perfectly.
> Could boot up without any further configuration.
Control: tags -1 + moreinfo
On Sun, 18 Oct 2015 14:52:12 +0300 Aryeh Leib Taurog
wrote:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
>
> Dear Maintainer,
>
> I just recently upgraded from wheezy to jessie. The /home partition
> is LUKS encrypted.
>
> Shutdown always takes
Control: tags -1 + moreinfo
On Sun, 3 Mar 2019 22:57:29 + (UTC) Pierre Ynard
wrote:
> reassign 813176 systemd
> thanks
>
> This line is, or was, part of the systemd-fsckd source code:
>
>
On Tue, 24 Jul 2018 22:02:11 +0200 Michael Biebl wrote:
> Am 24.07.2018 um 21:33 schrieb Francesco Poli:
> > On Tue, 24 Jul 2018 01:46:51 +0200 Michael Biebl wrote:
> >
> >> Am 23.07.2018 um 19:53 schrieb Francesco Poli:
> > [...]
> >>> I am aga
Am 10.03.19 um 17:36 schrieb Harlan Lieberman-Berg:
> On Sun, Mar 10, 2019 at 12:29 PM Michael Biebl wrote:
>> Can you provide the output of
>> systemctl status certbot.timer
>> journalctl -u certbot.timer
>
> The output of `systemctl show certbot.timer` is at
> h
Am 10.03.19 um 17:05 schrieb Harlan Lieberman-Berg:
> Hello pkg-systemd!
>
> There's a strange bug being reported in the stable-updated version of
> certbot about the systemd timer that I'm having trouble reproducing or
> understanding how it could happen.
>
> According to the users reporting
Control: severity -1 serious
Let's bump this to serious. I think you should consider making another
stable upload for this.
As users have pointed out, systems which aren't rebooted regularly are
otherwise up for a nasty experience.
You might consider asking the security team to distribute the
Am 10.03.19 um 16:55 schrieb Michael Biebl:
> I'd like to make a stable upload for systemd, fixing 5 separate issues.
> Two of them have a CVE.
...
> The fix for CVE-2018-15686/#912005 is the most invasive one. I based it
> partially on what was uploaded to old-stable by the deb
301 - 400 of 1844 matches
Mail list logo
