System hangs during boot at "Started configure plugged in printer"

Bug #1797628 reported by Michael Ehling
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

System: Lenovo T430s with HP OfficeJet Pro 8600 attached via usb hub

Followed general bug reporting instructions (including https://wiki.ubuntu.com/Bugs/FindRightPackage). This may be kernel related, not xorg.

What I tried: rebooting
What I expected: to see the login screen
What happened: booting hangs

Rebooted using 'E' option in grub to remove splash and quiet. Saw system hang at "Started configure plugged in printer"

When I unplug the USB hub (to which the printer is connected), I can reboot and login fine then reinsert USB hub.

After this "fix," I can reboot fine without unplugging anything. This bug appears to happen right after a system update (running Software Updater and there are kernel bits to update).

This is new behaviour; I had the same system setup running and booting fine under 18.04

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12
Uname: Linux 4.18.0-9-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.10-0ubuntu11
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Oct 12 15:48:22 2018
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21fb]
InstallationDate: Installed on 2018-10-02 (10 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180927)
MachineType: LENOVO 2356CU8
ProcEnviron:
 LANGUAGE=en_CA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=e307efee-e562-4d24-9632-4a97a84073ee ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/22/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: G7ET91WW (2.51 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2356CU8
dmi.board.vendor: LENOVO
dmi.board.version: Not Defined
dmi.chassis.asset.tag: 529944
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG7ET91WW(2.51):bd01/22/2013:svnLENOVO:pn2356CU8:pvrThinkPadT430s:rvnLENOVO:rn2356CU8:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T430s
dmi.product.name: 2356CU8
dmi.product.sku: LENOVO_MT_2356
dmi.product.version: ThinkPad T430s
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.13.1+18.10.20180930-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

Revision history for this message
Michael Ehling (0-mike-1) wrote :
description: updated
affects: xorg (Ubuntu) → linux (Ubuntu)
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc8

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Michael Ehling (0-mike-1) wrote :

This started happening after the distribution upgrade from Bionic 18.04 which I did in the first few days of October 2018. (Sorry for lack of specificity here.)

Tested the latest upstream kernel: 4.19rc8. Problem still exists. I set the take 'kernel-bug-exists-upstream.'

Set status to 'confirmed.'

Thanks!

tags: added: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Seems like it worked on older kernels. Can you find out which on works?

Revision history for this message
Michael Ehling (0-mike-1) wrote :

I would like to but I have a correction to report: this system never had 18.04 LTS (or any prior versions) on it. I had remembered upgrading a different machine to Cosmic at the same time as I had done a fresh install on this machine.

So we don't know if this problem existed in prior versions of the kernel.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.