Re: jessie: help debugging NFS shares not mounted at boot, double mounts with mount -a, and @reboot cronjobs

Disabling ifplugd didnt change the situation, and there are still missing mount points On Tue, Feb 9, 2016 at 9:21 PM, Michael Biebl wrote: > Am 09.02.2016 um 22:11 schrieb Sandro Tosi: >>> Another idea: maybe it's related to name resolution. How is that >>> configured? Does it

Re: jessie: help debugging NFS shares not mounted at boot, double mounts with mount -a, and @reboot cronjobs

Am 10.02.2016 um 18:37 schrieb Sandro Tosi: > Disabling ifplugd didnt change the situation, and there are still missing > mount points > > On Tue, Feb 9, 2016 at 9:21 PM, Michael Biebl wrote: >> Am 09.02.2016 um 22:11 schrieb Sandro Tosi: Another idea: maybe it's related

systemd 228-6 MIGRATED to testing

FYI: The status of the systemd source package in Debian's testing distribution has changed. Previous version: 228-4 Current version: 228-6 -- This email is automatically generated once a day. As the installation of new packages into testing happens multiple times a day you will receive

Bug#814365: Xorg.0.log in question

[  4033.331] (II) UnloadModule: "evdev" [  4033.331] (II) systemd-logind: releasing fd for 13:78 [  4033.331] (EE) systemd-logind: failed to release device: Connection is closed [  4033.331] (II) evdev: Power Button: Close   keeps on happening, until    [  4033.331] (II) systemd-logind:

Re: broken mount behaviour on jessie

On Feb 10, 2016 19:34, Brian May wrote: > > Brian May writes: > > I have a patched 1.6.10-2 for sid and jessie, amd64 and i386 at > > https://linuxpenguins.xyz/debian/pool/main/s/schroot/ > > > > Haven't had a chance to test it extensively yet, but so far

Bug#814324: systemd-networkd: networkd setup doesn't seem to work in non-systemd use cases

Control: reassign -1 virutalbox On Wed, 2016-02-10 at 17:40 +0530, Ritesh Raj Sarraf wrote: > On Wed, 2016-02-10 at 17:28 +0530, Ritesh Raj Sarraf wrote: > > I hope I have been able to explain the problem. Or in other words, > > how > > do I achieve a bridge interface status like the following

Processed: Re: systemd-networkd: networkd setup doesn't seem to work in non-systemd use cases

Processing control commands: > reassign -1 virutalbox Bug #814324 [systemd] systemd-networkd: networkd setup doesn't seem to work in non-systemd use cases Bug reassigned from package 'systemd' to 'virutalbox'. Warning: Unknown package 'virutalbox' Warning: Unknown package 'virutalbox' No longer

Bug#814324: systemd-networkd: networkd setup doesn't seem to work in non-systemd use cases

On Wed, 2016-02-10 at 17:28 +0530, Ritesh Raj Sarraf wrote: > I hope I have been able to explain the problem. Or in other words, > how > do I achieve a bridge interface status like the following under > systemd-networkd ? > > 4: sysbr0: mtu 1500 qdisc noqueue >

Re: broken mount behaviour on jessie

Brian May writes: > I have a patched 1.6.10-2 for sid and jessie, amd64 and i386 at > https://linuxpenguins.xyz/debian/pool/main/s/schroot/ > > Haven't had a chance to test it extensively yet, but so far seems to > work. Still getting unexpected mount errors; don't have time to

Processed: Re: Bug#814365: Xorg.0.log in question

Processing control commands: > severity -1 normal Bug #814365 [systemd] systemd: X vanishes, User thrown to tty1 to a login prompt, programs from X session continue to run Severity set to 'normal' from 'critical' > reassign -1 xserver-xorg-core Bug #814365 [systemd] systemd: X vanishes, User

Bug#814365: Xorg.0.log in question

Control: severity -1 normal Control: reassign -1 xserver-xorg-core Am 10.02.2016 um 22:09 schrieb Send Me: > [ 4033.331] (II) UnloadModule: "evdev" > [ 4033.331] (II) systemd-logind: releasing fd for 13:78 > [ 4033.331] (EE) systemd-logind: failed to release device: Connection is > closed > [

Bug#814240: systemd triggers break upgrades within unstable

Hi Guillem, could you have a look at this bug report, please? Somehow this looks like an issue in dpkg, if it triggers a package which is in an inconsistent state. But maybe we just made a mistake in our use of triggers in systemd: