- Original Message -From: Michael Biebl Date:
Wednesday, October 21, 2015 4:30 pmSubject: Re: Bug#801844: [systemd] Sudden
Unbootable SystemTo: David Baron , 801...@bugs.debian.org>
Am 18.10.2015 um 11:02 schrieb David Baron:> > Spontaneously gave it a try
today and ... it > > booted su
Am 18.10.2015 um 11:02 schrieb David Baron:
> Spontaneously gave it a try today and ... it
> booted successfully!
>
> Did have an "invalid mount point" error up
> front but does not show on journalctl or
> dmesg.
>
Please provide full error messages in context. If necessary take a
screenshot.
Spontaneously gave it a try today and ... it
booted successfully!
Did have an "invalid mount point" error up
front but does not show on journalctl or
dmesg.
___
Pkg-systemd-maintainers mailing list
Pkg-systemd-maintainers@lists.alioth.debian.org
http:
On Thursday 15 October 2015 15:23:28 Michael Biebl wrote:
> Control: tags -1 + moreinfo
>
> Am 15.10.2015 um 10:23 schrieb David Baron:
> > Package: systemd
> > Version: 226-4
> > Severity: grave
> >
> > --- Please enter the report below this line. ---
> > Systemd is still 226-4, not upgraded, ha
Processing control commands:
> tags -1 + moreinfo
Bug #801844 [systemd] [systemd] Sudden Unbootable System
Added tag(s) moreinfo.
--
801844: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=801844
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
___
Control: tags -1 + moreinfo
Am 15.10.2015 um 10:23 schrieb David Baron:
> Package: systemd
> Version: 226-4
> Severity: grave
>
> --- Please enter the report below this line. ---
> Systemd is still 226-4, not upgraded, had been working up until my first boot
> morning of 14.10
> which booted OK
Package: systemd
Version: 226-4
Severity: grave
--- Please enter the report below this line. ---
Systemd is still 226-4, not upgraded, had been working up until my first boot
morning of 14.10
which booted OK.
Upgraded some KF5 Baloo packages to fix dorked KDE, rebooted, then bingo.
Boot stop
