Bug#763401: failure to start brings confusion between keyboard and chair

Am 30.09.2014 um 00:29 schrieb Michael Biebl: > So, bascially the issue here is, that for SysV/LSB services, systemd > uses RemainAfterExit=true > > Which means, the service is considered active, even though the main > process has exited. This is, because from the available metadata in the > LSB h

Bug#763401: failure to start brings confusion between keyboard and chair

So, bascially the issue here is, that for SysV/LSB services, systemd uses RemainAfterExit=true Which means, the service is considered active, even though the main process has exited. This is, because from the available metadata in the LSB header, systemd doesn't know if the service is supposed to

Processed: Re: Bug#761953: Acknowledgement (systemd: Hangup in shutdown process)

Processing control commands: > reassign -1 samba Bug #761953 [systemd] systemd: Hangup in shutdown process Bug reassigned from package 'systemd' to 'samba'. No longer marked as found in versions systemd/215-4. Ignoring request to alter fixed versions of bug #761953 to the same values previously s

Bug#761953: Acknowledgement (systemd: Hangup in shutdown process)

Control: reassign -1 samba Control: forcemerge 740942 -1 Control: affects 740942 systemd Am 18.09.2014 um 10:27 schrieb K.Ohta: > I resolved this hangup issue with below workarounds: > > 1. In /etc/fstab, was written undefined UUID of swap partition > (used older disk) entry. > So, systemd tr

Bug#761951: systemd: Did not start network in default

Am 17.09.2014 um 09:45 schrieb Kyuma Ohta: > Package: systemd > Version: 215-4 > Severity: normal > > Dear Maintainer, > > When update to version 215 from version 208, not starting network at default. > Networks are defined by /etc/network/interfaces, not NetworkManagedr. > Workaround is re-de

Processed: retitle 761951 to systemd: networking service not started due to dependency cycle

Processing commands for cont...@bugs.debian.org: > retitle 761951 systemd: networking service not started due to dependency cycle Bug #761951 [systemd] systemd: Did not start network in default Changed Bug title to 'systemd: networking service not started due to dependency cycle' from 'systemd: D

Processed: Re: Bug#763327: [systemd] FAILED to remount /

Processing control commands: > forcemerge 742048 -1 Bug #742048 [systemd] systemd-remount-fs.service fails for split-usr Bug #763327 [systemd] [systemd] FAILED to remount / Marked as found in versions systemd/204-7, systemd/215-3, and systemd/204-10. Bug #742048 [systemd] systemd-remount-fs.servic

Bug#763327: [systemd] FAILED to remount /

Control: forcemerge 742048 -1 Am 29.09.2014 um 16:21 schrieb Michael Biebl: > Am 29.09.2014 um 15:30 schrieb David Baron: >> # /usr was on /dev/sda5 during installation >> UUID=61df1af1-f443-4a9d-aa66-dd13abaa5f3b /usrext4defaults >> >> 0 2 > > Seeing that you have

Bug#763327: [systemd] FAILED to remount /

Am 29.09.2014 um 15:30 schrieb David Baron: > On Monday 29 September 2014 14:29:22 Michael Biebl wrote: >> Control: tags -1 moreinfo >> >> Am 29.09.2014 um 13:22 schrieb David Baron: >>> Package: systemd >>> Version: 215-5 >>> Severity: normal >>> >>> --- Please enter the report below this line. --

Bug#763327: [systemd] FAILED to remount /

On Monday 29 September 2014 14:29:22 Michael Biebl wrote: > Control: tags -1 moreinfo > > Am 29.09.2014 um 13:22 schrieb David Baron: > > Package: systemd > > Version: 215-5 > > Severity: normal > > > > --- Please enter the report below this line. --- > > Since recent upgrade to 215-5 (maybe prev

Processed: Re: Bug#763327: [systemd] FAILED to remount /

Processing control commands: > tags -1 moreinfo Bug #763327 [systemd] [systemd] FAILED to remount / Added tag(s) moreinfo. -- 763327: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763327 Debian Bug Tracking System Contact ow...@bugs.debian.org with problems __

Bug#763327: [systemd] FAILED to remount /

Control: tags -1 moreinfo Am 29.09.2014 um 13:22 schrieb David Baron: > Package: systemd > Version: 215-5 > Severity: normal > > --- Please enter the report below this line. --- > Since recent upgrade to 215-5 (maybe previous as well), get one or two FAILED > to remount / message at the very star

Bug#763330: loginctl show-seat does not show ActiveSession/Sessions anymore

Package: systemd Version: 215-5+b1 Severity: minor File: /bin/loginctl At some point, loginctl stopped printing relevant information such as current ActiveSession and Sessions in 'show-seat' (and I guess in other commands as well): $ loginctl show-seat seat0 -a Id=seat0

Bug#763327: [systemd] FAILED to remount /

Package: systemd Version: 215-5 Severity: normal --- Please enter the report below this line. --- Since recent upgrade to 215-5 (maybe previous as well), get one or two FAILED to remount / message at the very startup. At this point, boot leaves the silent mode, shows all the messages, proceeds w

Call for paper- International Conference on Economics, Energy, Environment and Agricultural Sciences

Dear Colleagues, *Call for papers* International Conference on Economics, Energy, Environment and Agricultural Sciences * (ICEEEAS)* *(**1-2 November, 2014**– Kuala Lumpur, Malaysia)* *Pearl International Hotel**, Kuala Lumpur, Malaysia* http://www.pakrdw.com/?ic=details&id=7 The aim o

Bug#762953: no network after emergency mode

On Sun, Sep 28, 2014 at 10:41:59AM +0200, Michael Biebl wrote: > Afaics you are using ifupdown, specifically allow-hotplug interfaces to > start the network. Probably yes. This is a new system installed with no Desktop Environment from Jessie's daily image, then apt-get upgraded to sid. I did not