[Bug 876449] Re: plymouth hanging after printing "Booting system without full network configuration"

[Thomas Schweikle]

> Please show the contents of /etc/network/interfaces.

This is quite straight forward (I've attached the file).

> Which of the bridges is the one that gets started?
vm0 only

> The bridges are assumed to be up at system startup.
vm0
vm1
vm2
vm8

> What do you mean here? Do you mean that other parts of
> your configuration assume they're available? That's entirely
> reasonable.

>> Maybe this is again related to parts of the networking setup using
>> /var/run/network, while others use /run/network.

> Not unless something broke on your upgrade and prevented
> /var/run from being migrated to a symlink to /run. If so, you
> probably have a broken shutdown sequence as described
> in bug #858122.

/run and /var/run where both directories. None of them was symlinked to
the other.

> I don't think this is likely to be the cause in any case, since
> ifupdown doesn't use /run to share data with other packages.

ifup was the command exausting the error message about /run not holding
directory /run/network. Which was correct: ifup mentions /run/network
checking if it is there, breaking if not.

Since there where various other issues, I decided to reinstall. This
solved some errors, but gave some new ones, while some old remained.
Badly enough most related to networking ... :-(

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to plymouth in Ubuntu.
https://bugs.launchpad.net/bugs/876449

Title:
  plymouth hanging after printing "Booting system without full network
  configuration"

Status in “plymouth” package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu boots, but never shows lightDM login screen. plymouth is showing "Booting system without full network configuration ...". lightDM login will never show. Looking at any of the consoles 1 to 6 you may log in, looking at the network various devices are not configured.
  Plymouth seems not to be active any more, lightDM occupies tty7.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: plymouth 0.8.2-2ubuntu28
  Uname: Linux 3.0.4 x86_64
  NonfreeKernelModules: openafs
  ApportVersion: 1.23-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 17 14:18:45 2011
  DefaultPlymouth: /lib/plymouth/themes/tps-ubuntu/tps-ubuntu.plymouth
  MachineType: Acer, inc. TravelMate 6292
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.4 root=UUID=e8a84ed2-696e-4c59-b2c6-0df091211846 ro crashkernel=384M-2G:64M,2G-:128M splash vt.handoff=7
  ProcEnviron:
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.4 root=UUID=e8a84ed2-696e-4c59-b2c6-0df091211846 ro crashkernel=384M-2G:64M,2G-:128M splash vt.handoff=7
  SourcePackage: plymouth
  TextPlymouth: /lib/plymouth/themes/text/text.plymouth
  UpgradeStatus: Upgraded to oneiric on 2011-10-17 (0 days ago)
  dmi.bios.date: 01/11/2008
  dmi.bios.vendor: Acer
  dmi.bios.version: S1.3502
  dmi.board.name: Victoria
  dmi.board.vendor: Acer, Inc.
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Acer, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: dmi:bvnAcer:bvrS1.3502:bd01/11/2008:svnAcer,inc.:pnTravelMate6292:pvrNotApplicable:rvnAcer,Inc.:rnVictoria:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A:
  dmi.product.name: TravelMate 6292
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Acer, inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/plymouth/+bug/876449/+subscriptions