Processed: fixed 876103 in 233-1

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> fixed 876103 233-1
Bug #876103 [systemd-container] systemd-nspawn: --read-only is broken
There is no source info for the package 'systemd-container' at version '233-1' 
with architecture ''
Unable to make a source version for version '233-1'
Marked as fixed in versions 233-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
876103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: reopening 876103

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> reopen 876103
Bug #876103 {Done: Michael Biebl } [systemd-container] 
systemd-nspawn: --read-only is broken
'reopen' may be inappropriate when a bug has been closed with a version;
all fixed versions will be cleared, and you may need to re-add them.
Bug reopened
No longer marked as fixed in versions 233-1.
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
876103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Processed: closing 876103

[Debian Bug Tracking System]

Processing commands for cont...@bugs.debian.org:

> close 876103
Bug #876103 [systemd-container] systemd-nspawn: --read-only is broken
Marked Bug as done
> thanks
Stopping processing here.

Please contact me if you need assistance.
-- 
876103: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=876103
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#886914: systemd: Kernel Panic on systemctl daemon-relaod, unit enable/disable when libvirt vms are running

[Michael Biebl]

On Thu, 11 Jan 2018 11:01:03 +0200 "Plamen K. Kosseff"
 wrote:
> Package: systemd
> Version: 236-2
> Severity: normal
> 
> Dear Maintainer,
> 
> 
> This is new debian buster install on HP z600 workstation (for hardware spec 
> see below).
> The issue has manifested first during normal "apt-get upgrade" over ssh the 
> system would free during processing systemd triggers.
> Upon local investigation there was Kernel panic - not synching: Attempted to 
> kill init exitcode=0x9. I'll try to attach picture of the full panic message.
> 
> After some more investigation it looks like the probelm is reproducible only 
> when there are libvirt VMs running.
> If I stop the VMs before systemctl daemon-reload, enable disable it works as 
> expected

Is this problem still reproducible?
Might this actually be a kernel/kvm bug triggered by the reload of libvirt?

CCing Guido, maybe he has an idea.

-- 
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
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#870301: systemd: Touchpad fix Dell Inspiron Mini 1012

[Michael Biebl]

On Tue, 30 Jan 2018 04:30:58 -0500 (EST) bw  wrote:

> I'll go back and read your earlier posts, and see what I need to do.  I 
> guess you are recommending that I upgrade systemd and use upstream bug 
> reporting instead of debian bugtracker?

Yes, please upgrade to v238, try to reproduce your (libinput) problem,
if it still exists, file a bug report upstream at
https://github.com/systemd/systemd/issues
and report back with the bug number.
-- 
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
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#884784: systemd-network segfaults

[Michael Biebl]

On Tue, 19 Dec 2017 19:50:49 +0200 =?utf-8?q?R=C3=A9mi_Denis-Courmont?=
 wrote:
> Package: systemd
> Version: 235-3
> Severity: critical
> Justification: breaks unrelated software
> 
> Dear Maintainer,
> 
> systemd-networkd from version 236-1 systematically segfaults at start-up.

Could you test with v238 please and report back with your results.

-- 
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
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#888955: marked as done (open-vm-tools.service 10.2.0 does not start on boot on jessie/stretch/etc)

[Debian Bug Tracking System]

Your message dated Sat, 17 Mar 2018 03:12:26 +0100
with message-id 
and subject line Re: Bug#888955: open-vm-tools.service 10.2.0 does not start on 
boot on jessie/stretch/etc
has caused the Debian Bug report #888955,
regarding open-vm-tools.service 10.2.0 does not start on boot on 
jessie/stretch/etc
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
888955: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=888955
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: open-vm-tools
Version: 2:10.2.0-2
Severity: important

Dear Maintainer,

here all systems on vSphere 6.0/6.5 fail to start open-vm-tools.service
on boot.
The only thing I see is:

# systemctl status open-vm-tools.service
● open-vm-tools.service - Service for virtual machines hosted on VMware
   Loaded: loaded (/lib/systemd/system/open-vm-tools.service; enabled)
   Active: failed (Result: resources)
 Docs: http://open-vm-tools.sourceforge.net/about.php

This happens on jessie and stretch:

Stretch:
Works: 2:10.1.5-5055683-4+deb9u1
Fails: 2:10.2.0-2~bpo9+1

Jessie:
Works: 2:9.4.6-1770165-8
Works: 2:10.1.5-5055683-4+deb9u1~bpo8+1
Fails: 2:10.2.0-2~bpo8+1 (jessie-bpo-sloppy)


-- System Information:
Debian Release: 9.3
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.9.0-5-amd64 (SMP w/2 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8),
LANGUAGE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages open-vm-tools depends on:
ii  iproute2    4.9.0-1+deb9u1
ii  libc6   2.24-11+deb9u1
ii  libdrm2 2.4.74-1
ii  libdumbnet1 1.12-7+b1
ii  libfuse2    2.9.7-1
ii  libgcc1 1:6.3.0-18
ii  libglib2.0-0    2.50.3-2
ii  libicu57    57.1-6+deb9u1
ii  libmspack0  0.5-1+deb9u1
ii  libssl1.1   1.1.0f-3+deb9u1
ii  libstdc++6  6.3.0-18
ii  libudev1    232-25+deb9u1
ii  libxml2 2.9.4+dfsg1-2.2+deb9u2
ii  libxmlsec1  1.2.23-0.1
ii  libxmlsec1-openssl  1.2.23-0.1
ii  libxslt1.1  1.1.29-2.1
ii  pciutils    1:3.5.2-1

Versions of packages open-vm-tools recommends:
ii  ethtool  1:4.8-1+b1
pn  fuse 
ii  lsb-release  9.20161125
pn  zerofree 

Versions of packages open-vm-tools suggests:
pn  cloud-init 
pn  open-vm-tools-desktop  

-- Configuration Files:
/etc/vmware-tools/tools.conf changed:


-- no debconf information

-- /* Mit freundlichem Gruß / With kind regards, Patrick Matthäi
GNU/Linux Debian Developer Blog: http://www.linux-dev.org/ E-Mail:
pmatth...@debian.org patr...@linux-dev.org */

-- 
/*
Mit freundlichem Gruß / With kind regards,
 Patrick Matthäi
 GNU/Linux Debian Developer

  Blog: http://www.linux-dev.org/
E-Mail: pmatth...@debian.org
patr...@linux-dev.org
*/

--- End Message ---
--- Begin Message ---
Version: 238-1

On Sat, 10 Mar 2018 09:29:46 +0100 Bernd Zeimetz  wrote:
> > Why does it need to run before cloud-init i.e. why does cloud-init need
> > open-vm-tools?
> 
> because cloud-init pulls the configuration it should apply from vmtoolsd.
> 
> But that is not the bug here and nothing that needs to be changed.
> 
> If you would finally read
> https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780
> 
> you would learn that there is a race condition that when PrivateTmp is
> being used the necessary mounts are not always available.
> 
> The workaround for now is After=local-fs.target - which will result in a
> dependency loop at some point, which is discussed in
> 
> https://bugs.launchpad.net/ubuntu/+source/open-vm-tools/+bug/1750780/comments/11
> 
> basically all information is in that bug. Please read it.

Actually this bug report it doesn't contain any actual information what
this supposed race condition in systemd should be. It's mostly
speculation on their part.
Anyway, they said they can no longer reproduce it anyway on bionic which
ships the same version as unstable, so let's close this 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
--- End Message ---
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892321: attempts to suspend failing after crash

[Michael Biebl]

On Thu, 8 Mar 2018 10:02:32 + Daniel Pocock  wrote:
> Package: systemd
> Version: 232-25+deb9u1
> Severity: important
> 
> 
> Laptop was connected to a Thunderbolt dock, lid closed, using desktop
> monitor and keyboard, everything connected through the dock.  It is a
> laptop with encrypted LVM and swap on LVM.
> 
> Laptop's thunderbolt cable was bumped very slightly without coming out
> completely and then pushed back in.  As the lid was down, it appears the
> laptop tried to suspend
> 
> It didn't really suspend though, it became frozen with a blank screen.
> 
> After a hard reboot, every subsequent attempt to close the lid or undock
> also failed, the screen would go blank and it wouldn't come back.
> 
> journalctl and /var/log/messages provided no clues.
> 
> Guessing it was a problem with the swap partition, tried the following:
> 
>  swapoff /dev/mapper/vg00--vg-swap_1
>  mkswap /dev/mapper/vg00--vg-swap_1
> mkswap: /dev/mapper/vg00--vg-swap_1: warning: wiping old swap signature.
> Setting up swapspace version 1, size = 23.8 GiB (25513947136 bytes)
> no label, UUID=
> swapon /dev/mapper/vg00--vg-swap_1
> 
> In this case, the swap partition is named in /etc/fstab, not the UUID. 
> For somebody with the UUID in fstab it would be necessary to update
> there too and also run update-initramfs
> 
> This is not hard for an experienced user to resolve but very annoying as
> you only discover you have a problem after the second attempt to sleep.
> 
> Can systemd or whatever else is involved in the suspend/sleep mechanism
> be improved to detect problems like this, give some kind of error to the
> user and maybe even help them automatically correct it?

It's unclear to me what exactly your specific problem is/how and how
systemd should detect that.

-- 
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
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#807041: logind: laptop unexpectedly auto-suspends after some time of inactivity

[George B.]

Package: systemd
Version: 238-2
Followup-For: Bug #807041

Actuall, having said that, I have found
https://github.com/systemd/systemd/issues/786 and my new laptop does
have Nvidia with closed source driver so this would explain it.

Will dig up my old laptop and test again with that...


George

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892989: weird chars found in dpkg output

[Michael Biebl]

Am 16.03.2018 um 08:45 schrieb Harald Dunkel:
> On 03/15/18 18:46, Michael Biebl wrote:
>>
>> With a UTF-8 locale (which you really should enable), systemctl will use
>> '→', for a non-UTF8 locale, systemctl will fall back to '->'
>>
>>
> 
> Sorry to say, but thats ridiculous. Shouldn't it work no matter
> what? Ain't that "if locale == xxx" just asking for troubles?

No, I don't think it's ridiculous at all to use Unicode in 2018. The
ASCII fallback is only to be super-nice to people still refusing to use
a UTF-8 locale.

https://github.com/systemd/systemd/blob/master/src/basic/locale-util.c#L370
-- 
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
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers

Bug#892989: weird chars found in dpkg output

[Harald Dunkel]

On 03/15/18 18:46, Michael Biebl wrote:


With a UTF-8 locale (which you really should enable), systemctl will use
'→', for a non-UTF8 locale, systemctl will fall back to '->'




Sorry to say, but thats ridiculous. Shouldn't it work no matter
what? Ain't that "if locale == xxx" just asking for troubles?

___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-systemd-maintainers