Am 30.06.2015 um 21:20 schrieb Michael Biebl:
> Am 30.06.2015 um 20:45 schrieb Klaus Ethgen:
>> Am Di den 30. Jun 2015 um 17:38 schrieb Michael Biebl:
>>> Am 30.06.2015 um 17:52 schrieb Klaus Ethgen:
>>>> # CONFIG_FHANDLE is not set
>>
>>> E.g. tha
Hi,
Am 30.06.2015 um 21:48 schrieb Meelis Roos:
>> Did older udev versions work?
>
> Yes.
>
> By dpkg.log, 215-18 was the previous version before 220-7 that broke.
> Unfortunatley, 215 does not seem to be available from Debian mirrors any
> more. 215-18 seems to be available from snapshot.debi
Am 30.06.2015 um 21:44 schrieb Klaus Ethgen:
> Am Di den 30. Jun 2015 um 20:20 schrieb Michael Biebl:
>>> New kernel with all pre requirements in kernel enabled and still
>>> unbootable.
>
>> CONFIG_UEVENT_HELPER=y
>
> I cannot find any note abo
Am 30.06.2015 um 10:04 schrieb Meelis Roos:
> Package: udev
> Version: 221-1
> Severity: critical
> Justification: breaks the whole system
>
> udev 220-7 broke sparc boot with strange messages about different
> options of udevadm not supported (--cleanup-db un recognized,
> --action=add not recogn
control: -1 user debian-sp...@lists.debian.org
control: -1 usertag sparc
control: -1 retitle "systemctl crashes, systemd setup fails on sparc"
Am 01.07.2015 um 11:08 schrieb Meelis Roos:
>>> I had trouble with udev 220-7 hanging on sparc boot with corrupted
>>> messages on serial console. Because
Control: found -1 220-7
(you said it is already broken in 220-7, so marking the bug accordingly)
Am 01.07.2015 um 14:11 schrieb Alberto:
> Package: systemd
> Version: 221-1
> Severity: normal
>
> Dear Maintainer,
>
> I have a machine with 2 nvidia graphic cards, configured as multiseat, with 2
Control: tags -1 upstream
Hi Stephen,
Am 02.07.2015 um 03:47 schrieb Stephen Powell:
> Package: udev
> Version: 220-7
> Severity: normal
>
> After upgrading udev from version 215-18 to version 220-7, I found that the
> symbolic links in the /dev/disk/by-uuid and /dev/disk/by-label directories
>
e in the
universe are pointed away from Earth?
commit 11dd7339838b9dfd16bcda2067b2a7b2c4948e2f
Author: Michael Biebl
Date: Tue Jun 30 19:14:28 2015 +0200
Move a few man pages into correct packages
diff --git a/debian/control b/debian/control
index a47bd30..345277f 100644
--- a/debian/cont
Control: forwarded -1 https://github.com/systemd/systemd/issues/476
Am 03.07.2015 um 00:08 schrieb Stephen Powell:
> Upstream bug number is 476.
> (https://github.com/systemd/systemd/issues/476)
>
Thanks, marking accordingly
--
Why is it that all of the instruments seeking intelligent life in
Control: forwarded -1 https://github.com/systemd/systemd/issues/451
Hi Jessie, hi Yaroslav!
Am 12.06.2015 um 17:21 schrieb Michael Biebl:
> Am 11.06.2015 um 20:44 schrieb Jessica Frazelle:
>>> Can you reboot,run
>>> ls -la /sys/class/drm
>>> suspend/resume and ru
Am 30.06.2015 um 22:53 schrieb Klaus Ethgen:
> Am Di den 30. Jun 2015 um 20:22 schrieb Michael Biebl:
>> Booting with udev.log-priority=debug udev.children-max=1 on the kernel
>> command line should give you a more verbose log. Please attach that.
>
> I did that. And it se
Am 04.07.2015 um 11:38 schrieb Daniel Pocock:
> Package: systemd
> Version: 215-17+deb8u1
> Severity: important
>
> This has been happening on a system that was upgraded from wheezy to jessie
>
> Sometimes systemd starts the network and then tries to start things that
> depend on the network (e.g
Am 04.07.2015 um 14:22 schrieb Daniel Pocock:
>
>
> On 04/07/15 13:58, Michael Biebl wrote:
>> Am 04.07.2015 um 11:38 schrieb Daniel Pocock:
>>> Package: systemd Version: 215-17+deb8u1 Severity: important
>>>
>>> This has been happening on a system t
Am 04.07.2015 um 15:35 schrieb Ritesh Raj Sarraf:
> Package: systemd
> Version: 220-7
> Severity: normal
>
>
> I have a .service defined for laptop-mode-tools
>
> rrs@chutzpah:~$ cat /lib/systemd/system/laptop-mode.service
> [Unit]
> Description=Laptop Mode Tools
>
> [Service]
> Type=oneshot
>
Control: reassign -1 laptop-mode-tools
Am 04.07.2015 um 15:44 schrieb Michael Biebl:
> Am 04.07.2015 um 15:35 schrieb Ritesh Raj Sarraf:
>> Package: systemd
>> Version: 220-7
>> Severity: normal
>>
>>
>> I have a .service defined for laptop-mode-tools
>&g
Am 04.07.2015 um 20:10 schrieb Ritesh Raj Sarraf:
> Control: reassign -1 systemd
>
>
> Hello Michael,
>
>
> Thank you for the quick reply. I'm reassigning it because I think I have
> some explanations that have made me conclude that it might be a systemd bug.
>
> But please feel free to reassi
Am 04.07.2015 um 19:08 schrieb Joshua:
> Package: udev
> Version: 215-17
> Severity: serious
> Justification: Policy 9.1
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>
> Noticed CDROM drive spinnin
Am 04.07.2015 um 20:31 schrieb Ritesh Raj Sarraf:
> On Saturday 04 July 2015 11:43 PM, Michael Biebl wrote:
>>>> But please feel free to reassign back, in case I'm wrong.
>>>>
>> It would help if you explained why this is supposed to be a bug in
>> s
Hi,
Am 04.07.2015 um 18:08 schrieb Daniel Pocock:
> On 04/07/15 14:29, Michael Biebl wrote:
>> (*) As a side note: you might want to consider enabling
>> systemd-timesyncd.service (and removing ntpdate). timesyncd is a
>> very lightweight NTP client.
>
>
> Wou
Am 04.07.2015 um 21:09 schrieb Joshua Hudson:
> Devices not created by kernel. Verified by stopping udev.
>
Sorry, what are you trying to say here? Please be more verbose.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature
Am 04.07.2015 um 21:41 schrieb Joshua Hudson:
> Update: problem disappeared after cold boot. Additional information
> gained from experiment:
>
> devtmpfs does not create /dev/sr? nodes on this system. udevd does once
> started.
No, as explained. udevd doesn't create the /dev/sr* device node.
T
Am 05.07.2015 um 14:16 schrieb Tino:
> Another systemd segfault.
> I still didn't find a workaround for this problem and the reboots every
> few days is getting quite annoying. :/ At least it looks like i am the
> only one with this problem.
Sorry for the inconvenience.
I think the best course of
Am 05.07.2015 um 15:30 schrieb Ritesh Raj Sarraf:
> On Sunday 05 July 2015 12:27 AM, Michael Biebl wrote:
>>> Other point I can see is that the invoking process is systemd.
>>
>> Well, sure, if a service start is triggered, the invoking process will
>> be sys
Am 06.07.2015 um 09:29 schrieb Ritesh Raj Sarraf:
> rrs@learner:~$ cat /lib/udev/lmt-udev
> #!/bin/sh -e
> # /usr is not guaranteed to be mounted when udev starts
>
> (
> if grep -w "systemd" /proc/1/conn; then
> systemctl --non-block reload laptop-mode
>
> elif [
Am 06.07.2015 um 09:58 schrieb Michael Biebl:
> The canonical way to check if systemd is the active PID 1 is a simple
> test for the existence of the /run/systemd/systemd directory [2]
> In shell this would be
> if [ -d /run/systemd/systemd ] ; then
> do stuff
> fi
Sorry fo
Control: forcemerge 764267 -1
Am 07.07.2015 um 02:45 schrieb 積丹尼 Dan Jacobson:
> Package: systemd
> Version: 221-1
> Severity: wishlist
> File: /bin/systemctl
>
> Can't anything bad be detected when given e.g.,
>
> # systemctl disable .servicez ; echo $?
> 0
You filed the same b
Am 07.07.2015 um 03:52 schrieb Michael Biebl:
> Am 07.07.2015 um 02:45 schrieb 積丹尼 Dan Jacobson:
>> Package: systemd
>> Version: 221-1
>> Severity: wishlist
>> File: /bin/systemctl
>>
>> Can't anything bad be detected when given e.g.,
>>
>&
Package: systemd
Version: 222-1
Severity: normal
With v222, the following files are installed in /usr/share/doc/systemd:
$ ls -al /usr/share/doc/systemd/
insgesamt 332
drwxr-xr-x.2 root root 4096 Jul 8 20:48 .
drwxr-xr-x. 3368 root root 131072 Jul 8 19:03 ..
-rw-r--r-- 1 root root 2
Am 09.07.2015 um 12:43 schrieb Vincent Lefevre:
> Package: systemd
> Version: 222-1
> Severity: normal
>
> The .journal files under /var/log/journal/*/ have an incorrect x bit
> for the group:
>
> -rw-r-x---+ 1 root root50331648 2015-07-09 12:25:09 system.journal
> -rw-r-x---+ 1 root
Am 09.07.2015 um 15:08 schrieb Vincent Lefevre:
> Control: forwarded -1 https://github.com/systemd/systemd/issues/534
>
> On 2015-07-09 13:37:58 +0200, Michael Biebl wrote:
>> Please consider filing this upstream.
>
> Done and set forwarded.
Thanks,
Michael
--
Why
Control: reassign -1 ifupdown
Am 09.07.2015 um 16:54 schrieb Vincent Lefevre:
> Package: systemd
> Version: 222-1
> Severity: important
>
> Note: the following applies when /etc/network/interfaces contains:
>
> allow-hotplug eth0
> iface eth0 inet dhcp
>
> which is the default.
>
> With ifupdo
Am 09.07.2015 um 18:57 schrieb Jochen Sprickerhof:
> Package: udev
> Version: 222-1
> Severity: normal
>
> Dear Maintainer,
>
> starting with 221-1, my computer doesn't power off anymore. Running
> swapoff -a or installing 220-7 makes it work again. I have a encrypted
> swap partition listed in t
Am 09.07.2015 um 19:47 schrieb Jochen Sprickerhof:
> * Michael Biebl [2015-07-09 19:28]:
>> udev is usually not responsible for turning off the swap file system.
>> Is the problem reproducible with systemd as init system?
>
> Works fine with systemd. Still, I only updated ud
Control: severity -1 serious
Am 09.07.2015 um 20:14 schrieb David Mohr:
> Package: gdm3
> Version: 3.14.2-1
> Severity: normal
>
> Dear Maintainer,
>
> the changelog reads:
> * Systemd has been fixed in v222 to no longer kill services on reload
> if BusName is set, so drop that part from 9
Am 10.07.2015 um 14:05 schrieb Bodo Eggert:
> Package: systemd
> Version: 215-17+deb8u1
> Severity: normal
>
> Dear Maintainer,
>
> when I boot my system, some of the NFS shares don't get mounted reliably.
>
> At first I blamed it on the RPC race condition, but since I applied the
> countermeasu
[keeping pkg-systemd into the loop here]
Am 10.07.2015 um 14:37 schrieb Michael Biebl:
> I suggest we follow up on this bug report.
>
> I'm not yet quite sure, if this is a gdm or systemd bug and whether the
> best course of action is to simply re-introduce the workaround patc
Control: severity -1 important
(downgrading severity as per your explanations)
Am 10.07.2015 um 16:41 schrieb Klaus Ethgen:
> Hello,
>
> Am Mo den 6. Jul 2015 um 20:26 schrieb Martin Pitt:
>> Klaus Ethgen [2015-07-05 1:34 +0100]:
>>> Well, it clearly shows that it probes some unexisting USB st
Am 10.07.2015 um 16:59 schrieb Martin Pitt:
> It's also not completely clear to me whether the hang already
> happens in initramfs or in the "real" system. In the former case, you
> need to call "update-initramfs -u" after each step (doing that can't
> hurt either way).
Klaus is using a custom ker
Am 10.07.2015 um 17:00 schrieb Klaus Ethgen:
> Am Fr den 10. Jul 2015 um 15:55 schrieb Michael Biebl:
>>> After SCSI detection it takes ~100 seconds to finish USB HID detection.
>>> That is ten times more than with udev 215-18. So the system is not
>>> unbootable an
Am 10.07.2015 um 18:38 schrieb Josh Triplett:
> On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote:
>> Control: severity -1 serious
>>
>> Am 09.07.2015 um 20:14 schrieb David Mohr:
>>> Package: gdm3
>>> Version: 3.14.2-1
>>> Sever
Am 10.07.2015 um 19:11 schrieb Josh Triplett:
> On Fri, Jul 10, 2015 at 06:46:18PM +0200, Michael Biebl wrote:
>> Am 10.07.2015 um 18:38 schrieb Josh Triplett:
>>> Note, though, that it doesn't help for systemd to be upgraded first.
>>> Even if running the new s
Am 10.07.2015 um 18:38 schrieb Josh Triplett:
> On Fri, Jul 10, 2015 at 02:37:49PM +0200, Michael Biebl wrote:
>> I'm not yet quite sure, if this is a gdm or systemd bug and whether the
>> best course of action is to simply re-introduce the workaround patch and
>> drop
Control: tags -1 + upstream
Am 12.07.2015 um 15:30 schrieb nfb:
> After a quick jump on the #tor IRC channel we concluded that this may
> be an issue on the systemd side, and after reading something around
> the web we tried to tweak the Hardening section of the unit file. And
> indeed we found tha
Hi,
Am 12.07.2015 um 23:41 schrieb nfb:
>> That said, this sounds like an upstream issue, so please report that at
>>
>> https://github.com/systemd/systemd/issues/
>>
>> and report bug with the bug number.
>
> Sorry, do i have to file an upstream bug referring to this bug number in its
> body, or
Control: forwarded -1 https://github.com/systemd/systemd/issues/567
Am 13.07.2015 um 01:04 schrieb nfb:
>> Once you file the bug upstream, reply to *this* bug report with the
>> upstream bug report number.
>> This way I can link the two bug reports and we can track the upstream
>> process automati
Control: tags -1 moreinfo
Am 07.04.2015 um 14:27 schrieb Eric Valette:
> Package: systemd
> Version: 219-6
> Severity: important
>
> Dear Maintainer,
>
>
> When upgrading to the latests version of systemd, I was asked if I wanted to
> keep my own modified version of /etc/systemd/logind.conf wer
Control: tags -1 moreinfo
On Sat, 30 May 2015 11:18:34 +0300 Shaman
wrote:
> Package: general
> Severity: important
>
> Dear Maintainer,
>
> After upgrade from Wheezy to Jessie PC hang on reboot and I get last message
> "Reached target shutdown".
Did you already run systemd in wheezy? Which ve
Version: 222-1
On Sat, 28 Sep 2013 02:17:00 +0200 Michael Biebl wrote:
> Package: systemd
> Version: 204-5
> Severity: important
>
> I've been investigating a dist-upgrade failure, where rsyslog fails to
> upgrade properly from its wheezy to jessie version.
> The p
Am 14.07.2015 um 16:11 schrieb Stefan Sauer:
> Package: systemd
> Version: 215-17+deb8u1
>
> When running systemd-bootchart it crashes at the end in attempt to produce
> the svg.
>
> Here is a transcript:
>
> Starting program: /lib/systemd/systemd-bootchart --rel -n 10
> [Thread debugging using
Control: forwarded -1 https://github.com/systemd/systemd/issues/583
Am 14.07.2015 um 16:32 schrieb Michael Biebl:
> Would be great if you can test the latest v222 from unstable and file
> this bug upstream if it's still reproducible with this version.
> From a cursory look, this doe
Am 14.07.2015 um 17:40 schrieb Stefan Sauer:
> Sorry if that is a silly question. Should I be able to install this version
> https://packages.debian.org/stretch/armel/systemd/download
> on a jessie system?
This will require other dependencies from unstable, so you'll have a mix
of unstable and sta
Am 15.07.2015 um 19:08 schrieb Martin Pitt:
> Cyril Brulebois [2015-07-15 18:03 +0200]:
>> Bottom line(s):
>> ---
>> I'll be testing 221-1 to make sure I reproduce the issue with a full
>> install, then 221-1 + two patches to make sure it goes away. If that
>> works fine, it might be a
Am 15.07.2015 um 20:15 schrieb Felipe Sateler:
> Jul 15 09:35:31 deb-dschepler dbus[836]: [system] Activating systemd
> to hand-off: service name='org.freedesktop.login1'
> unit='dbus-org.freedesktop.login1.service'
> Jul 15 09:35:33 deb-dschepler dbus[836]: [system] Failed to activate
> service 'o
Am 16.07.2015 um 10:05 schrieb Michael Cree:
> Source: systemd
> Version: 222-2
> Severity: important
> Justification: Fails to build from source but built in the past.
> Tag: patch
> User: debian-al...@lists.debian.org
> Usertags: alpha
>
> Systemd FTBFS on alpha due to missing syscalls. Build l
Hi Guus,
I was wondering if you are coming to Debconf this year. Martin and I
will be there and I think it would be a great opportunity to sit down
and discuss ifupdown, networkd and systemd and how we can integrate them
better.
Looking forward hearing back from you!
Regards,
Michael
--
Why is
Hi Felipe,
thanks for working on this!
Am 17.07.2015 um 19:17 schrieb Felipe Sateler:
> [tag]
> https://lintian.debian.org/tags/systemd-no-service-for-init-rcS-script.html
> , but there are some false positives in this list.
..
> dd-list of affected packages:
This list seems to be incomplete.
Control: tags -1 moreinfo unreproducible
Am 22.07.2015 um 12:14 schrieb Пронин Илья Сергеевич:
> Source: systemd
> Severity: normal
Which version of systemd is that?
>
> Dear Maintainer,
>
> When I shutdown/reboot with LXDE menu, it goes shutdown/reboot
> instantly. So every next boot time the
Hi
Am 22.07.2015 um 15:58 schrieb nfb:
> As i suspected there is no such issue on my main x86 laptop running
> the same distro and updated software. The only difference is the arm
> architecture and the custom kernel, as i noticed before.
Are you suspecting the arm architecture or the custom kern
Control: forcemerge 787480 -1
Hi Dimitri,
Am 23.07.2015 um 12:33 schrieb Dimitri John Ledkov:
> Package: systemd
> Severity: normal
> Version: 222-2
>
> Please add iptables-dev build-dependency and thus enable libiptc which
> in turn should enable systemd-networkd IPMasquarade support as well as
Am 22.07.2015 um 17:42 schrieb nfb:
>> Are you suspecting the arm architecture or the custom kernel to be the
>> culprit? Can you test the stock Debian kernel on arm?
>> Your custom kernel, does it have every option enabled as specified in
>> /usr/share/doc/systemd/README.gz
>
> Yes i suspect abou
Control: reassign -1 cups
Am 23.07.2015 um 11:20 schrieb Andreas Brogle:
> Solution:
>
> I've created a new default cupsd.conf file. That strange behavior no
> longer exists.
>
> Until 2 weeks ago there had been needed only that Listen entry:
> Listen /var/run/cups/cups.sock
>
> Now to work corr
Am 23.07.2015 um 13:21 schrieb Dimitri John Ledkov:
> If we in-vision that networkd is / will-be required on minimal
> systems, I would want to have an alternative build available of
> networkd & nspawn with firewall support enabled. (could be something
> like update-alternatives, or e.g. systemd-n
Control: tags -1 = upstream
Control: severity -1 normal
Hi!
Am 19.07.2015 um 18:54 schrieb Ritesh Raj Sarraf:
> Package: systemd
> Version: 222-2
> Severity: important
> File: /bin/machinectl
> Tags: patch
>
> I am evaluating moving from LXC to systemd-nspawn. During the course, I've
> run into
Am 23.07.2015 um 13:48 schrieb Michael Biebl:
>> I am evaluating moving from LXC to systemd-nspawn. During the course, I've
>> run into the following problem, which is known upstream, and claimed to be
>> fixed.
>>
>>
>> My hope was that the fix was par
Control: forwarded -1 https://github.com/systemd/systemd/issues/685
Am 23.07.2015 um 13:56 schrieb Ritesh Raj Sarraf:
> I've filed the bug upstream at:
> https://github.com/systemd/systemd/issues/685
Thanks, marking accordingly.
Regards,
Michael
--
Why is it that all of the instruments seeking
Am 23.07.2015 um 14:07 schrieb Julian Wollrath:
> Package: systemd
> Version: 222-2
> Severity: normal
>
> Dear Maintainer,
>
> I change my network device names via an .link definition in
> /etc/systemd/network/01-ethernet.link with the following content:
> [Match]
> MACAddress=xx:xx:xx:x
Am 23.07.2015 um 14:25 schrieb Julian Wollrath:
> diff --git a/debian/extra/initramfs-tools/hooks/udev
> b/debian/extra/initramfs-tools/hooks/udev index
> cfe5085ae079..d3d08aa48f93 100755 ---
> a/debian/extra/initramfs-tools/hooks/udev +++
> b/debian/extra/initramfs-tools/hooks/udev @@ -41,6 +41,
Am 23.07.2015 um 14:07 schrieb Julian Wollrath:
> Package: systemd
> Version: 222-2
> Severity: normal
>
> Dear Maintainer,
>
> I change my network device names via an .link definition in
> /etc/systemd/network/01-ethernet.link with the following content:
> [Match]
> MACAddress=xx:xx:xx:x
Control: merge 771675 -1
This turned out to be the same issue as #771675:
missing dbus in the container and missing pts/0 in /etc/securetty
Merging the two bug reports.
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.as
Am 23.07.2015 um 15:09 schrieb Felipe Sateler:
> On 23 July 2015 at 09:24, Michael Biebl wrote:
>>
>> The problem might be, that we don't know, which link files to copy.
>> We will need to check, if it's actually safe to copy all of
>> /etc/systemd/networ
Am 24.07.2015 um 06:50 schrieb Пронин Илья Сергеевич:
> Please help write shutdown log. Method described here doesn't work:
>
> https://wiki.freedesktop.org/www/Software/systemd/Debugging/#diagnosingshutdownproblems
>
> boot with the debug options:
>
> systemd.log_level=debug systemd.log_target=
Am 08.08.2007 um 02:08 schrieb Пронин Илья Сергеевич:
> [20471.606659] systemd-shutdown[1]: Sending SIGTERM to remaining processes...
> [20471.612886] systemd-journald[158]: Received SIGTERM from PID 1
> (systemd-shutdow).
> [20471.646553] systemd-shutdown[1]: Sending SIGKILL to remaining processe
Am 24.07.2015 um 13:49 schrieb Пронин Илья Сергеевич:
> Wrote config for my broken hwclock, thanks. But it has nothing to do
> with fs errors and bad fs superblocks.
>
> poweroff causes errors, not reboot. I attached logs for poweroff and
> then boot, for fresh fixed fs. Something goes wrong while
Am 24.07.2015 um 14:41 schrieb Пронин Илья Сергеевич:
> авг 08 04:01:14 shambler systemd-fsck[416]: /dev/sda6 contains a file
> system with errors, check forced. 1736 авг 08 04:01:14 shambler
> systemd-fsck[375]: /dev/sda8 contains a file system wit h errors,
> check forced. 1737 авг 08 04:
Am 24.07.2015 um 15:22 schrieb Пронин Илья Сергеевич:
> Well, thank you for patience!
>
> I have to switch to sysv-init or openrc. It does fsck at boot time and
> tells everything is clean.
>
> I insist that systemd is main suspect, but I could be wrong.
What I've seen so far indicates otherwis
Am 25.07.2015 um 23:45 schrieb Alban Browaeys:
> Package: systemd
> Version: 222-2
> Severity: normal
>
> Dear Maintainer,
>
> Building systemd from package source, on arm 32 bits, I get :
> configure.ac:1135: error: AM_COND_IF: no such condition "ARCH_IA32"
> /usr/share/aclocal-1.15/cond-if.m4:2
Hi Ben,
thanks for your quick reply.
Am 26.07.2015 um 02:55 schrieb Ben Pfaff:
> The wrapper in the autoconf2.13 package is supposed to automatically
> determine which version of Autoconf is necessary. I see a bug, however,
> which makes it fail to do that correctly with gummiboot. I can fix
>
Am 26.07.2015 um 03:30 schrieb Michael Biebl:
> With v222, a simple autoreconf works, a "intltoolize -f -c, autoreconf
> -f -i" fails.
>
> That should be sufficient if you want to reproduce the issue.
Actually, that's a red-herring.
That said, I can reproduce the p
Control: reassign -1 autoconf2.13
Am 26.07.2015 um 02:55 schrieb Ben Pfaff:
> On Sun, Jul 26, 2015 at 01:25:03AM +0200, Michael Biebl wrote:
>> Am 25.07.2015 um 23:45 schrieb Alban Browaeys:
>>> Package: systemd
>>> Version: 222-2
>>> Severity: normal
>&
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
Hello,
Am 30.07.2015 um 07:59 schrieb Clemens Haupt Hohentrenk:
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What led up to the situation?
>* What exactly did you do (or not do) that was effective (or
> ineffective)?
>* What was the outcom
Control: reassign -1 systemd-shim
Control: forcemerge 756247 -1
Am 30.07.2015 um 07:59 schrieb Clemens Haupt Hohentrenk:
> 9398 login: [ 223.579151] systemd-logind[4102]: Failed to start user
> service: Unknown unit: user@0.service
> ?
That's a duplicate of
https://bugs.debian.org/c
Am 31.07.2015 um 11:23 schrieb David Liontooth:
> root@cartago:~# just list ipmi
> ii freeipmi-bmc-watchdog 1.4.5-3
> amd64GNU implementation of the IPMI protocol - BMC watchdog
[..]
> At that moment, however, the machine just rebooted. /var
Control: tags -1 moreinfo
Am 31.07.2015 um 20:57 schrieb ael:
> Package: systemd
> Version: 221-1
> Severity: critical
> Justification: breaks the whole system
>
> I had to select the sysvinit option from the grub menu in order to
> achieve a boot. The standard menu entry got as far as (probably)
Control: severtiy -1 important
Control: tags -1 moreinfo
Am 03.08.2015 um 10:27 schrieb Jens Stavnstrup:
> Package: systemd
> Version: 215-17
> Severity: critical
> Justification: breaks the whole system
>
>
> Trying to install 220-7 and all subsequent releases.
> On 222-2 udev will not ins
Control: severity -1 normal
Control: tags -1 moreinfo unreproducible
Am 03.08.2015 um 18:30 schrieb Marcin Wolcendorf:
> Package: systemd
> Version: 222-2
> Severity: important
>
> Dear Maintainer,
>
> *** Reporter, please consider answering these questions, where appropriate ***
>
>* What
Control: notfound -1 215-17
Control: found -1 220-7
Am 04.08.2015 um 00:29 schrieb Jens Stavnstrup:
> Agree that the language was bad :(
>
> You filed this bug against version 215-17, yet you talk about 220-7.
>> Please clarify.
>>
>
> I have been unable to boot the machine with any version of s
Am 04.08.2015 um 13:35 schrieb ael:
> On Fri, Jul 31, 2015 at 11:11:54PM +0200, Michael Biebl wrote:
>> Am 31.07.2015 um 22:32 schrieb ael:
>>> Package: udev
>>> Version: 222-2
>>> Severity: normal
>>>
>>> Setting up udev (222-2) ...
>>&g
Am 04.08.2015 um 10:29 schrieb Jens Stavnstrup:
> Michael
>
> Tried to follow your instructions.
>
> - First removed the input group
> - Then tried to install 222-2 which failed, udev would not install (no
> error message)
> - Then tried to install 215-17 which did not succeed.
> - When booting a
Hi Brian,
Am 06.08.2015 um 10:17 schrieb Brian May:
> When closing the lid, system doesn't suspend, all I get is the following
> logged in auth.log:
>
> Aug 6 15:20:36 prune systemd-logind[571]: Lid closed.
> Aug 6 15:20:47 prune systemd-logind[571]: Lid opened.
>
> Occassionally the system do
Am 06.08.2015 um 12:28 schrieb Thomas Schmidt:
ug 06 10:43:50 9398 systemd[1]: ssh.service: Main process exited,
code=exited, status=255/n/a
> Aug 06 10:43:50 9398 systemd[1]: ssh.service: Unit entered failed state.
> Aug 06 10:43:50 9398 systemd[1]: ssh.service: Failed with result 'exit-code'.
> A
Am 06.08.2015 um 12:07 schrieb Brian May:
> On Thu, 6 Aug 2015 at 19:56 Brian May wrote:
>
>> Then again, maybe I was premature; I think I should do a reboot and redo
>> the following:
>>
>
> Really good theory, however after a reboot everything is fine:
>
> [brian:~] % for i in /sys/class/drm/
[please always CC the bug report]
Am 06.08.2015 um 14:58 schrieb q...@vienna.at:
> On Thu, Aug 06, 2015 at 01:25:59PM +0200, Michael Biebl wrote:
>> It looks like ssh service is restarted too often within a short period
>
> Perfectly true.
>
>> of time due to some exter
Am 06.08.2015 um 16:13 schrieb d...@mattli.us:
> Richard Mortimer writes:
>
>> So maybe the code is trying to use the wrong string as input to chdir
>> and hence failing.
>
> Is udev using the gold linker during build?
It is, indeed.
We had a hack in debian/rules for a while, to use ld.bfd on
Am 14.08.2015 um 19:15 schrieb Vladimir Kudrya:
> Package: udev
> Version: 224-1
> Severity: normal
>
> Dear Maintainer,
> After a switch to predictable interface naming, I am still using udev rule to
> name the interfaces conveniently. (This is still valid, but not in auto,
> right?)
>
> Whle c
Package: systemd
Version: 224-1
Severity: normal
File: /etc/X11/xinit/xinitrc.d/50-systemd-user.sh
On Debian, there is apparently no support for /etc/X11/xinit/xinitrc.d/.
So 50-systemd-user.sh is not run during X session startup.
If this is a Fedora specific directory, it might be worth filing th
Control: tags -1 - patch
Hi!
Am 15.12.2014 um 05:55 schrieb Jerad Simpson:
> Package: systemd
> Version: 215-7
> Severity: normal
> Tags: patch
>
> The following configuration causes boot to wait 1 minute and 30 seconds
> before starting an emergency root shell.
>
> /etc/crypttab:
> vg0-tmp_cry
Control: severity -1 important
Hi!
On Sat, 19 Jul 2014 23:20:58 +0200 Francesco Muzio
wrote:
> Package: kdm
> Version: 4:4.11.9-1
> Severity: minor
>
> Dear maintainers,
> My machine (updated debian testing) has only KDM as display manager, it
> starts without problem after upgrading/trasition
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 we can prepare and test the upload within time.
Michael
[1] http://anonscm.debian.org/
Hi
Am 21.08.2015 um 15:59 schrieb Marc Haber:
> I have systemd-networkd segfault when it works as a DHCP client for
> IPv4 on a banana pi. Googling has led me to
> https://bugs.archlinux.org/task/45855 and to
> https://github.com/systemd/systemd/issues/827, which contains a patch
> which was merge
601 - 700 of 2654 matches
Mail list logo
