Control: found -1 215-17
Control: severity -1 important
Control: retitle -1 compat dev packages need strictly versioned dep
Am 31.07.2015 um 23:36 schrieb Benjamin Jacobs:
> To add to the matter, libsystemd-journal-dev version 222 can currently
> be co-installed with the libsystemd-dev version 223
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
Hi Jon,
Am 10.08.2015 um 15:15 schrieb Jon DeVree:
> As far as the shutdown problem is concerned, just putting udevd's pid
> into /run/sendsigs.omit.d/udevd fixes the problem without causing any
> new ones.
>
> Thats probably a good fix for debian rather than trying to patch udevd
> itself.
Tha
Hi Helmut,
since we made the changes at debconf to improve
cross-building/bootstrapping in systemd, I get the following failure
when trying to run mk-build-deps -i (from the devscripts package):
> dh_gencontrol
> dpkg-gencontrol: warning: can't parse dependency python3:native
> dpkg-gencontrol: e
Am 24.08.2015 um 08:21 schrieb Johannes Schauer:
> Hi all,
>
> Quoting Helmut Grohne (2015-08-24 07:32:16)
>> If I remember correctly, dpkg-gencontrol reduces architecture and
>> profile restrictions, so these work by chance.
>
>
>> It is not clear how to implement :native for mk-build-deps, bec
Am 25.08.2015 um 18:41 schrieb Luca Bruno:
> I've tried this patch and looks like adding another bug to me. Please
> confirm what I'm experiencing. It's true, it does not remove cgroups
> created by systemd, but then it doesn't cleanup cgroups that systemd
> created either.
>
> Example:
>
> 1) s
Hi
Am 26.08.2015 um 00:52 schrieb Faidon Liambotis:
> Hey,
>
> On Tue, Jun 16, 2015 at 06:21:20PM +0300, Faidon Liambotis wrote:
>> Any news about this? Can I help in any way?
>
> Are there any objections/holdups here? It'd be great if this made it to
> 8.2, the deadline for which is this weeken
Am 26.08.2015 um 01:49 schrieb Michael Biebl:
> Hi
>
> Am 26.08.2015 um 00:52 schrieb Faidon Liambotis:
>> Hey,
>>
>> On Tue, Jun 16, 2015 at 06:21:20PM +0300, Faidon Liambotis wrote:
>>> Any news about this? Can I help in any way?
>>
>> Are the
Am 27.08.2015 um 10:28 schrieb Martin Pitt:
> unmerge 756202
> reopen 786393
> reopen 618862
> thanks
>
> Meh, #756202 is something entirely different than #786393 and #618862.
Yes and no.
At least the bug report in [1] has
cryptswap UUID=x-xxx---xdc3 sda4_crypt
luks,keysc
Hi Jakub,
Am 27.08.2015 um 12:09 schrieb Jakub Wilk:
> Package: systemd
> Version: 224-2
> User: debian...@lists.debian.org
> Usertags: adequate obsolete-conffile
>
> The package left obsolete conffile after upgrade:
> /etc/dbus-1/system.d/org.freedesktop.machine1.conf
This is due to the package
Am 27.08.2015 um 14:52 schrieb Felipe Sateler:
> On 27 August 2015 at 07:48, Michael Biebl wrote:
>> Hi Jakub,
>>
>> Am 27.08.2015 um 12:09 schrieb Jakub Wilk:
>>> Package: systemd
>>> Version: 224-2
>>> User: debian...@lists.debian.org
>>>
Am 26.08.2015 um 00:52 schrieb Faidon Liambotis:
> Hey,
>
> On Tue, Jun 16, 2015 at 06:21:20PM +0300, Faidon Liambotis wrote:
>> Any news about this? Can I help in any way?
>
> Are there any objections/holdups here? It'd be great if this made it to
> 8.2, the deadline for which is this weekend AI
Am 16.06.2015 um 17:21 schrieb Faidon Liambotis:
> Hi,
>
> Any news about this? Can I help in any way?
>
> Thanks,
> Faidon
>
> On Fri, May 29, 2015 at 05:41:24PM +0300, Faidon Liambotis wrote:
>> On Mon, Apr 06, 2015 at 08:50:58PM +0100, Ben Hutchings wrote:
>>> It looks the same as this proble
Control: tags -1 + moreinfo
Am 28.08.2015 um 21:51 schrieb westlake:
> Package: systemd
> Version: 215-17+deb8u1
> Severity: normal
>
> network shares auto-disconnect themselves after a certain amount of time
> -- this happens after a couple of hours but it occurs at least twice a
> day.. not sur
Am 28.08.2015 um 21:41 schrieb Stephen Dowdy:
> I've not built debian source package stuff before, and wasn't quickly able
> to determine how to even do it on the systemd-215 download,
> so prebuilt packages for amd64 would help greatly.
>
> I'm also not entirely sure if this is happening in the i
Hi Stephen,
Am 29.08.2015 um 01:49 schrieb Stephen Dowdy:
> On Fri, Aug 28, 2015 at 4:52 PM, Stephen Dowdy wrote:
>
>> The system DOES boot successfully, after a long pause (as expected)...
>> but it DOES boot. I am going to reboot a few more times with this setup
>> (test1) to make sure it's
ease udev event timeout to 180s. Some kernel modules, like
mptsas, can take longer then 30s to load so udevd kills the (hanging)
worker responsible for loading the module. Increase timeout from 30s to
180s to workaround this issue. Thanks Faidon Liambotis.
(Closes: #787191)
-- Michael
Control: tags -1 + pending
Am 29.08.2015 um 02:51 schrieb Stephen Dowdy:
> I don't see much therein that looks interesting/revealing, but i certainly
> can not reboot the system in this state to get further logging, since we'll
> be back at the original issue with a locked-up system. So, let me
Am 29.08.2015 um 16:50 schrieb intrig...@debian.org:
> Package: systemd
> Version: 224-2
> Severity: normal
>
> Hi,
>
> I've got a sid system that has /boot on a removable storage device, so
> its fstab contains:
>
> /dev/disk/by-uuid/18f3e795-3fd6-4dea-8b14-cee2251dc276/boot ext2
Hi Paul,
Am 30.08.2015 um 10:38 schrieb Paul Wise:
> Package: udev
> Version: 224-1
> Severity: normal
> File: /lib/systemd/systemd-udevd
>
> I had a random crash (SIGABRT) in systemd-udevd:
[..]
thanks for your bug report. On a first glance it doesn't look like a
distro/downstream specific iss
Am 29.08.2015 um 17:59 schrieb intrigeri:
> Michael Biebl wrote (29 Aug 2015 15:50:40 GMT) :
>> Could you attach the output of systemd-analyze dump
>
> Yes and no => send privately.
I see that you have a boot.automount unit. I wonder where this unit is
coming from. I vaguely
Control: tags -1 moreinfo
Hi Nicolas,
Am 26.06.2015 um 16:18 schrieb Nicolas Patrois:
> Package: systemd
> Version: 220-7
> Severity: important
>
> Dear Maintainer,
>
> Since this morning upgrade, systemd crashes. Reinstalling systemd or
> restarting systemd shows this kind of lines.
>
> Here
control: user -1 debian-sp...@lists.debian.org
control: usertag -1 sparc
control: tags -1 + help
On Tue, 30 Jun 2015 11:04:20 +0300 Meelis Roos wrote:
> Package: udev
> Version: 221-1
> Severity: critical
> Justification: breaks the whole system
>
> udev 220-7 broke sparc boot with strange messa
Am 06.08.2015 um 02:05 schrieb Jon:
> Package: udev
> Version: 224-1
> Severity: important
>
> Dear Maintainer,
>
> The udev_queue_get_udev_is_active() API call of libudev is used by
> things like device-mapper to determine if it should wait for udev to settle
> after doing various operations. Th
Am 21.08.2015 um 09:09 schrieb Michael Biebl:
> Hi,
>
> we currently have one commit in our jessie branch [1] and the jessie
> point release 8.2 is about one month away.
> Do you have have other fixes which you'd like to see go into 8.2?
>
> If so, please speak up so w
Am 28.06.2014 um 11:54 schrieb Thomas Lange:
>>>>>> On Sat, 28 Jun 2014 03:15:32 +0200, Michael Biebl
>>>>>> said:
>
> > does dracut provide any dpkg trigger which we could use in systemd to
> > force an update of the ini
Control: reassign -1 powerdevil
On Mon, 15 Sep 2014 14:21:41 +0200 Didier Raboud wrote:
> Package: systemd
> Version: 208-8
> Severity: important
> File: /usr/share/polkit-1/actions/org.freedesktop.login1.policy
>
> Hi,
>
> as discussed today on IRC with sjoerd, here's my use-case: I routinely
Am 30.08.2015 um 16:33 schrieb nicolas.patr...@gmail.com:
> Le 30/08/2015 15:24:22, Michael Biebl a écrit :
>
>> Control: tags -1 moreinfo
>
>> The log messages you showed show problems with "systemd-analyze" and
>> "systemd-delta". I don't im
Hi Andy,
Am 29.08.2015 um 02:46 schrieb Andy Valencia:
> ---
>> I do not think that there is anything else that udev can do, since the
>> check is done in udev.preinst.
>
> I hope you might consider talking to the apt folks. At least under a
> dist-upgrade it seems like this failure
Am 01.09.2015 um 19:38 schrieb Felipe Sateler:
> On 1 September 2015 at 14:05, Anton Zinoviev wrote:
>> On Thu, Aug 27, 2015 at 03:18:17PM -0300, Felipe Sateler wrote:
>>>
>>> Does console-setup actually need to be run before user services are
>>> started? My guess is that it only needs to run bef
Control: tags -1 + upstream
Hi Ben,
Am 02.09.2015 um 14:13 schrieb Ben Harris:
> Package: systemd
> Version: 224-1
> Severity: minor
> Tags: upstream
>
> Dear Maintainer,
>
> os-release(5) includes this description of the "CPE_NAME" parameter:
>
>CPE_NAME=
>A CPE name for t
Control: tags -1 + confirmed upstream
Control: forwarded -1 https://github.com/systemd/systemd/issues/1120
Hi
Am 02.09.2015 um 13:09 schrieb Jos van Wolput:
> Package: systemd
> Version: 225-1
> Severity: normal
>
> Dear Maintainer,
>
> After upgrading systemd from v.224-2 to 225-1 shutdown at
Source: systemd
Version: 225-1
Severity: wishlist
Currently systemd uses the default set of hardening build flags as
returned by dpkg-buildflags
We should consider enabling more then the default set of build flags.
This will likely mean a performance hit which shouldn't be a major issue
though, [
Control: forwarded -1 https://github.com/systemd/systemd/issues/45
Control: tags -1 upstream
Hi
Am 02.09.2015 um 23:38 schrieb Sven Hartge:
> The subject really says everything. I have extended getty@tty1.service
> to disable the screen clearing:
>
> -> /etc/systemd/system/getty@tty1.service.d/
Package: xserver-xorg-core
Version: 2:1.17.2-2
Severity: serious
I installed gdm3 from experimental which brought xserver-xorg-core from
experimental along with it.
This version has support for logind enabled, which apparently is
required to run gdm successfully.
There is one particular issue tho
Am 08.09.2015 um 02:33 schrieb Javier Ayres:
> Package: systemd
> Version: 225-1
> Severity: normal
>
> I have a NFS share configured in my /etc/fstab as follows:
>
> 192.168.1.4:/mnt/samsung /mnt/D3 nfs
> auto,nofail,timeo=25,users,_netdev,bg,comment=x-gvfs-show 0 0
>
> The drive
Am 08.09.2015 um 16:54 schrieb Javier Ayres:
> Hi, I'm connecting via wifi and using NetworkManager. This is
> NetworkManager's configuration file for this particular network:
>
> [connection]
> id=natalia
> uuid=c0a08844-145f-4c9d-8528-2163efcfba50
> type=802-11-wireless
> timestamp=1396749922
>
Control: severity -1 important
Am 08.09.2015 um 02:33 schrieb Javier Ayres:
> Package: systemd
> Version: 225-1
> Severity: normal
>
> I have a NFS share configured in my /etc/fstab as follows:
>
> 192.168.1.4:/mnt/samsung /mnt/D3 nfs
> auto,nofail,timeo=25,users,_netdev,bg,comment
Am 08.09.2015 um 19:18 schrieb Felipe Sateler:
> Hi Ritesh,
>
> On 4 September 2015 at 04:18, Ritesh Raj Sarraf wrote:
>> Package: systemd
>> Version: 225-1
>> Followup-For: Bug #792882
>>
>> Please find attached the journalctl -M log.
>
> It looks like the gettys in both containers cannot start
Am 09.09.2015 um 05:09 schrieb Javier Ayres:
> I edited the wpa_supplicant service as you suggested but the issue is still
> present.
Hm, right. The issue here is, that you are using NetworkManager.service
to bring up your (wireless) interface. Unfortunately we can't bring up
NetworkManager.servi
Am 09.09.2015 um 20:49 schrieb martin f krafft:
> Package: systemd
> Version: 225-1
> Severity: wishlist
> File: /bin/systemd-ask-password
>
> The file being in /bin suggests that users can use it. However,
> writing a service unit just now using User= to start a process as
> non-root exposed that
control: forwarded -1 https://github.com/systemd/systemd/issues/1231
Hi Julian,
thanks for your bug report.
I can confirm the problem with v226 as well.
Forwarded upstream as this not a downstream specific issue.
Regards,
Michael
--
Why is it that all of the instruments seeking intelligent lif
Am 10.09.2015 um 16:19 schrieb Javier Ayres:
> Trying to manually unmount the drive with the network down blocks (with CPU
> at 100%) indefinitely, or so it appears. I waited 40 minutes and then
> canceled it because I had to go.
This is probably a problem on its own.
> Can't the service which mo
Am 10.09.2015 um 16:50 schrieb Michael Biebl:
> Am 10.09.2015 um 16:19 schrieb Javier Ayres:
>> Can't the service which mounts/unmounts NFS (not sure which one that is) be
>> put after NetworkManager?
>
> I guess you mean *before*. But well, as I tried to explain, cur
Hi!
Am 10.09.2015 um 15:43 schrieb Dhionel Díaz:
> El 09/09/15 a las 21:26, Felipe Sateler escribió:
>> On 9 September 2015 at 20:46, Dhionel Díaz wrote:
>>> As an alternative, ¿do you think it would be appropriate to include a
>>> sd_notify call in xorp_rtrmgr main process and then use Type=not
Control: reassign 790556 binutils
Control: reassign -1 binutils
Control: forcemerge -1 790556
Control: retitle -1 LTO and gold linker broken on sparc
Am 08.09.2015 um 17:25 schrieb Artyom Tarasenko:
> On Sun, Aug 30, 2015 at 3:29 PM, Michael Biebl wrote:
>> control: user -1
On Mon, 17 Nov 2014 13:14:49 +0100 intrigeri wrote:
> Hi,
>
> Michael Biebl wrote (03 Jul 2014 21:07:36 GMT) :
> > Am 03.07.2014 20:57, schrieb Michal Suchanek:
> >> Also candidate for big fat release note.
>
> > Nod. I guess the recommendation here is to simpl
On Mon, 31 Mar 2014 20:24:28 +0200 Ralf Jung wrote:
> Hi,
>
> > Hm, true. Completely missed that bit.
> > Somehow systemctl enable|disable only outputs the symlinks
> > created|created by Alias= but not WantedBy=
> >
> > I guess this more accurately describes the bug, right?
>
> Correct.
Looki
Am 14.09.2015 um 14:53 schrieb Michael Biebl:
> Hi Russell,
>
> thanks for contacting us!
>
> Am 14.09.2015 um 14:46 schrieb Felipe Sateler:
>> I could not find what the fedora people are doing, but they likely
>> already faced this problem, it is probably worth checki
Hi Russell,
thanks for contacting us!
Am 14.09.2015 um 14:46 schrieb Felipe Sateler:
> I could not find what the fedora people are doing, but they likely
> already faced this problem, it is probably worth checking what they
> did.
A quick grep in a fedora f22 vm shows this:
> # grep relabel -R
How exactly did you start the containers?
Does it work, if you copy them to /var/lib/machines/ and
start them via
systemctl start systemd-nspawn@.service ?
At least this works for me.
signature.asc
Description: OpenPGP digital signature
___
Pkg-system
Am 15.09.2015 um 08:26 schrieb Martin Pitt:
> Package: udev
> Severity: grave
> Version: 226-1
>
> When upgrading a QEMU VM from 225 to 226, the "eth0" network interface
> (virtio) changes to "ens3".
>
> This is due to https://github.com/systemd/systemd/pull/1119 . While
> this is generally a goo
Control: tags -1 moreinfo
Am 17.09.2015 um 09:37 schrieb fin4478 fin4478:
> Package: systemd
> Version: 226-2
>
> Please do this:
> https://github.com/systemd/systemd/commit/e04658277d531763a5cbbb6e212041a35e0d9ff4
Sorry, it's unclear what you are trying to say here.
What are we supposed to do w
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.
Am 20.09.2015 um 13:59 schrieb Andreas Beckmann:
> Package: kdbus-dkms
> Version: 0.20150824t110616.0c05fbd-1
> Severity: serious
> User: debian...@lists.debian.org
> Usertags: piuparts
>
> Hi,
>
> kdbus-dkms fails to install since it cannot build a module
> for the current sid kernel. This is a
Fwiw, I mentioned similar concerns as Josh when I discussed this topic
with Martin but I also see where Martin is coming from.
The missing hook/extension mechanism in networkd is something which is
an issue.
Am 20.09.2015 um 15:54 schrieb Martin Pitt:
>> Hardly a zillion packages; here's a comple
Am 20.09.2015 um 15:54 schrieb Martin Pitt:
>>> The hooks are run asynchronously and don't block networkd.
>> >
>> > Interesting; as far as I know, that's a change compared to how other as
>> > far as I know those hooks are normally run synchronously by other
>> > software.
> What do you mean by "
Am 20.09.2015 um 16:37 schrieb Martin Pitt:
> Hello Matthias,
>
> Matthias Urlichs [2015-09-20 9:22 +0200]:
>> Some packages depend on or recommend e.g. "rsyslogd | system-log-daemon".
>> systemd provides a log daemon (the journal) and already intercepts all
>> syslog requests, so IMHO adding a "
Am 20.09.2015 um 17:23 schrieb Martin Pitt:
> This sounds a bit heavy to me, but indeed the only way how to do this
> cleanly.
Or at some point we enable persistent logging in the systemd package
itself. Dunno yet.
But this also interacts with systemd-journal-remote, as
> installing this will cu
Am 20.09.2015 um 17:09 schrieb Michael Biebl:
> Am 20.09.2015 um 16:37 schrieb Martin Pitt:
>> Hello Matthias,
>>
>> Matthias Urlichs [2015-09-20 9:22 +0200]:
>>> Some packages depend on or recommend e.g. "rsyslogd | system-log-daemon".
>>> system
Am 21.09.2015 um 01:59 schrieb Antonio Terceiro:
> On Sun, 20 Sep 2015 20:41:26 -0300 Antonio Terceiro
> wrote:
>> I am experiencing exactly the same with the latest systemd on unstable;
>> `systemctl suspend` works, but closing the lid does not suspend (at all).
>
> after rebooting with systemd
Am 21.09.2015 um 02:43 schrieb Michael Biebl:
> See
> https://github.com/systemd/systemd/blob/master/src/login/logind-button.c#L269
> and
> https://github.com/systemd/systemd/blob/master/src/login/logind-core.c#L453
>
> Either the the drm subsystem reports an external displa
Am 21.09.2015 um 19:16 schrieb Ritesh Raj Sarraf:
> Package: kdbus-dkms
> Version: 0.20150824t110616.0c05fbd-1
> Severity: normal
>
> Thanks for packaging kdbus. I'm assuming that you are willing to take
> bug reports. If not so, please let me know.
>
>
>>From what I've read so far, my understan
Am 22.09.2015 um 10:14 schrieb Ritesh Raj Sarraf:
> On Tue, 2015-09-22 at 00:53 +0200, Michael Biebl wrote:
>> Do you have dbus-user-session installed?
>> If not, please install it an re-test.
>
> Hello Michael,
>
> Installing dbus-user-session did not help. I still ge
Am 23.09.2015 um 18:08 schrieb Allen Webb:
> On Fri, 14 Aug 2015 10:13:25 +0200 Axel Ludszuweit
> wrote:
> > Dear maintainer,
> >
> > I also think there is is a timeout problem.
> > I Use lvm2 with md software raid based on ext3.
> > Systemd file system checks at boot-up on small partitions
Am 23.09.2015 um 13:19 schrieb Ansgar Burchardt:
> Josh Triplett writes:
>> I'd actually suggest *two* tiny packages: a systemd-journal-persistent
>> package that ships /var/log/journal and provides/conflicts
>> system-log-daemon, and a systemd-journal-transient package that
>> pointedly doesn't s
Am 24.09.2015 um 17:46 schrieb hannu@pp.inet.fi:
> This works for me:
>
> copy /lib/systemd/system/systemd-fsckd.service to /etc/systemd/system
>
> edit /etc/systemd/system/systemd-fsckd.service, add TimeoutStartSec under
> [Service]
>
> [Service]
> TimeoutStartSec=60min
Hm, good point. We
Control: forwareded -1 https://github.com/systemd/systemd/issues/1378
I suspect this is the same as this upstream bug, thus marking accordingly.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP di
Am 27.09.2015 um 16:40 schrieb Ritesh Raj Sarraf:
> On Tue, 2015-09-22 at 14:56 +0200, Michael Biebl wrote:
>>> Hello Michael,
>>>
>>> Installing dbus-user-session did not help. I still get the same
>> error
>>> messages.
>>
>> I assume y
Control: tags -1 + moreinfo
Am 27.09.2015 um 19:17 schrieb Harald Dunkel:
> Package: udev
> Version: 215-17+deb8u2
>
> If I try to boot my USB stick image in kvm, then it gets
> stuck with a message
>
> fb: switching to bochsdrmfb from simple
> or
> fb: switching to cirrusdrmfb from
Hi
Am 24.06.2015 um 16:25 schrieb A Mennucc:
> Package: systemd
> Version: 215-17+deb8u1
> Severity: normal
>
> Dear Mantainer,
>
> systemd is logging a lot of error messages as in the attached log
See
http://lists.freedesktop.org/archives/systemd-devel/2015-September/034356.html
Can you repr
Am 29.09.2015 um 13:33 schrieb Michael Biebl:
> Hi
>
> Am 24.06.2015 um 16:25 schrieb A Mennucc:
>> Package: systemd
>> Version: 215-17+deb8u1
>> Severity: normal
>>
>> Dear Mantainer,
>>
>> systemd is logging a lot of error
Am 31.08.2015 um 08:12 schrieb Paul Wise:
> On Sun, 2015-08-30 at 13:44 +0200, Michael Biebl wrote:
>
>> thanks for your bug report. On a first glance it doesn't look like a
>> distro/downstream specific issue, so would be great if you can file
>> that upstream
Am 30.09.2015 um 13:19 schrieb Ferenc Wágner:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
>
> Hi,
>
> On stock jessie systems sys-kernel-config.mount is not functional,
> because /sys/kernel/config does not exist before the configfs module
> is loaded, thus ConditionPathExists
Am 30.09.2015 um 13:19 schrieb Ferenc Wágner:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: normal
>
> Hi,
>
> On stock jessie systems sys-kernel-config.mount is not functional,
> because /sys/kernel/config does not exist before the configfs module
> is loaded, thus ConditionPathExists
control: tags -1 + moreinfo
Am 30.09.2015 um 14:58 schrieb ael:
> Package: systemd
> Version: 226-3
> Severity: important
>
> On two of my machines, I have been unable to boot with systemd for some
> time. Using the sysvinit fallback (init=/lib/sysvinit/init) does
> allow full boot.
>
> On this
Am 30.09.2015 um 15:09 schrieb Michael Biebl:
> control: tags -1 + moreinfo
>
> Am 30.09.2015 um 14:58 schrieb ael:
>> Package: systemd
>> Version: 226-3
>> Severity: important
>>
>> On two of my machines, I have been unable to boot with systemd for some
>
Control: tags -1 + moreinfo
Am 26.09.2015 um 18:08 schrieb James Bottomley:
> Package: systemd
> Version: 226-3
> Severity: normal
>
> rebooting the current system often causes listed init system failures.
> in addition to failing to start spamd (listed under separate bug).
> Systemd thinks units
Am 30.09.2015 um 16:04 schrieb Ferenc Wagner:
> Michael Biebl writes:
>
>> Why are your using a .service file to load the dlm module?
>
> Sorry for being confusing by eliding too much. The dlm service starts
> the DLM control daemon, and also loads the dlm kernel modu
Am 30.09.2015 um 16:09 schrieb Michael Biebl:
> See the upstream bug report you referenced:
> Either the module should be compiled in, or software requiring it should
> make sure to load the module itself, ideally by shipping a
> modules-load.d snippet.
My recommendation would be, tha
Hi Russel,
Am 29.09.2015 um 07:43 schrieb Russell Coker:
> Package: systemd
> Version: 215-17+deb8u2
> Severity: minor
>
> The following lines from the output of dmesg show that systemd (init_t) is
> leaking socket file handle 7748 when spawning kmod. It should either close
> the
> file handl
Am 30.09.2015 um 16:36 schrieb Ferenc Wagner:
> Michael Biebl writes:
>
>> Am 30.09.2015 um 16:04 schrieb Ferenc Wagner:
>>
>>> Michael Biebl writes:
>>>
>>>> Why are your using a .service file to load the dlm module?
>>>
>>&g
Hi,
Am 30.09.2015 um 16:58 schrieb Ferenc Wagner:
> Michael Biebl writes:
>
>> Have you asked dlm upstream, why they do it this way? Maybe they
>> simply don't know about modules-load.d? I would in any case try to get
>> this change upstream.
>
> Looking at
Control: tags -1 + moreinfo
On Thu, 16 Jul 2015 23:59:33 +0200 Hans wrote:
> Hi all,
>
> there is another hint, I dioscovered in my kernel logs.
>
> -
> Jul 16 21:51:55 localhost kernel: [ 1277.742162] atl1c :01:00.0: version
> 1.0.1.1-NAPI
> Jul 16 21:51:55 localhost kernel: [
Control: forcemerge 797382 776460
Control: forwarded 776460 https://github.com/systemd/systemd/issues/1353
Control: systemd-journald crashed with SIGABRT -- killed by 1 min watchdog
timeout on longer kernel lockups
Am 30.09.2015 um 13:57 schrieb Michael Biebl:
> Am 31.08.2015 um 08:12 schr
On Sun, 18 Jan 2015 11:07:40 +1100 Russell Coker
wrote:
> Package: systemd
> Version: 215-9
> Severity: normal
>
>
> type=AVC msg=audit(1421538903.417:232): avc: denied { use } for pid=23546
> comm="kded4" path="/run/systemd/inhibit/1.ref" dev="tmpfs" ino=91124
> scontext=rjc:user_r:user_t:
On Mon, 24 Nov 2014 09:23:22 +0100 Didier Roche wrote:
> Le 22/11/2014 21:28, Andrei POPESCU a écrit :
> >
> > 2b. Each display manager must add a Conflicts=[all other DMs]
>
> You don't really need to maintain a long list of Conflicts (which will
> never be kept up to date). I suggested last we
Control: reassign -1 cryptsetup
Am 10.07.2015 um 07:23 schrieb Jochen Sprickerhof:
> I've debugged a little more and actually it's not only enough to do a
> swapoff -a, but you need also a cryptsetup close /dev/mapper/swap0
> (sorry for forgetting it initiallly).
> The shutdown hangs in the do_clo
control: tags -1 + moreinfo
Am 01.10.2015 um 13:19 schrieb marek sowinski:
> Package: systemd
> Version: 226-3
> Severity: important
>
> Dear Maintainer,
>
>* What led up to the situation?
> when restarting, stopping or starting mysql it takes 10 minutes to complete
> the action
>* What
Am 05.10.2015 um 01:48 schrieb James Bottomley:
> On Sun, 2015-10-04 at 23:06 +, Debian Bug Tracking System wrote:
>> Well, this is apparently an apache configuration problem, causing the
>> service to return a non-zero exit code.
>>
>> Once you fix that, the service should not be marked as fai
Am 05.10.2015 um 10:41 schrieb Michael Biebl:
> Am 05.10.2015 um 01:48 schrieb James Bottomley:
>> On Sun, 2015-10-04 at 23:06 +, Debian Bug Tracking System wrote:
>>> Well, this is apparently an apache configuration problem, causing the
>>> service to return a non-z
Am 05.10.2015 um 11:15 schrieb Martin Pitt:
> Hello,
>
> Giuseppe Bilotta [2014-09-16 20:15 +0200]:
>> My fstab includes the line
>>
>> labrador:/oneforall /oneforall nfs auto,exec 0 0
>>
>> and the nfs share is automatically mounted when a network interface that
>> can resol
Am 05.10.2015 um 12:07 schrieb Michael Biebl:
> The ifup@.service unit file has DefaultDependencies=no and *no*
> Conflicts=shutdown.target, which means it should *not* be stopped on
> shutdown. This was done this way for exactly the reason you mention.
Originally I designed it tha
Am 05.10.2015 um 11:15 schrieb Martin Pitt:
> Or we just declare that we don't support manual stops, and you are
> supposed to run "sudo ifdown ethX" to stop an interface. This is also
> reasonable as we consider ifup@.service more like an internal helper
> unit, not an user-visible/actionable one.
Am 05.10.2015 um 12:26 schrieb Raphaël Halimi:
> Package: systemd
> Version: 226-4
>
> Hi,
>
> About persistent logging, README.Debian claims :
>
> "systemd will add an ACL for read permissions for users in the "adm" group."
>
> This is not working: after creating /var/log/journal with the "ins
Am 05.10.2015 um 13:08 schrieb Raphaël Halimi:
> Le 05/10/2015 12:30, Michael Biebl a écrit :
>> But the subdirectories of /var/log/journal have the correct ACL set, right?
>
> Yes, you're right, I just noticed it; but using journalctl as a user
> won't display system
Am 05.10.2015 um 13:12 schrieb Michael Biebl:
> Am 05.10.2015 um 13:08 schrieb Raphaël Halimi:
>> Le 05/10/2015 12:30, Michael Biebl a écrit :
>>> But the subdirectories of /var/log/journal have the correct ACL set, right?
>>
>> Yes, you're right, I just noticed
Am 05.10.2015 um 13:21 schrieb Michael Biebl:
> I wonder if we should fix the documentation to tell people to run
> systemd-tmpfiles /usr/lib/tmpfiles/systemd.conf immediately after
> enabling persistent journal.
We might also consider re-adding
https://anonscm.debian.org/cgit/pk
Am 05.10.2015 um 13:57 schrieb Raphaël Halimi:
> Le 05/10/2015 13:21, Michael Biebl a écrit :
>> Apparently the files were created before the ACLs have been set for
>> /var/log/journal/3deacfa10d0c169adfdeb36c50522bd6
>> so the journal files that were created did not inh
Am 05.10.2015 um 17:35 schrieb Felipe Sateler:
> On 5 October 2015 at 12:20, Michael Biebl wrote:
>> But, when using Storage=persistent, journald will create the directory
>> /var/log/journal/ itself. So this won't help in that case, unless
>> systemd-journald re-ad
701 - 800 of 2654 matches
Mail list logo
