"usb_id: unable to access" - boot experience

Bug #440424 reported by Adam Michael Roach
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

1) When booting, I get this message first:

Grub loading.

2) Then I get the following messages:

(see attachment) There is more, but I didn't catch it fast enough

3) Then I get a sound as if I am getting into the login screen, even though I have it set to autologin.

4) The desktop loading sound comes on, and as my desktop is loading I see the brown xsplash wallpaper and not my own wallpaper for the first few secs, until my desktop is fully loaded, then it switches to the wallpaper I have set it to.

Although it is quite fast, overall it is a very akward boot experience.

ProblemType: Bug
Architecture: amd64
Date: Fri Oct 2 02:40:32 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: xsplash 0.8.1-0ubuntu2
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
SourcePackage: xsplash
Uname: Linux 2.6.31-11-generic x86_64

Revision history for this message
Adam Michael Roach (adammichaelroach) wrote :
affects: ubuntu → xsplash (Ubuntu)
Revision history for this message
Cody Russell (bratsche) wrote :

I don't know if this is a bug, but it's unrelated to xsplash.

Changed in xsplash (Ubuntu):
assignee: nobody → Cody Russell (bratsche)
affects: xsplash (Ubuntu) → upstart (Ubuntu)
Changed in upstart (Ubuntu):
assignee: Cody Russell (bratsche) → Scott James Remnant (scott)
Changed in upstart (Ubuntu):
assignee: Scott James Remnant (scott) → nobody
Revision history for this message
Robbie Williamson (robbiew) wrote :

2) The first set about sdb are from the kernel and we are looking at silencing those. Our alternative is to mask with usplash, but we'd rather not. The second set are from system daemon startups and can be fixed by following the solution here:
https://bugs.launchpad.net/ubuntu/+bug/438335/comments/13
We are looking at how to permanently address this issue by release as well.

3) This is fixed in the latest gdm. Do a
# sudo apt-get update
# sudo apt-get upgrade
Check to see if "gdm" is one of the packages being updated. If it is not, please post your level of gdm to this bug by running:
> dpkg -l gdm

4) This is a much harder situation to debug. I suggest installing "bootchart" and then reboot *TWICE*. The first reboot will be slow because sreadahead is profiling your boot. Attach the /var/log/bootchart/*-2.png file to this bug for analysis

Changed in upstart (Ubuntu):
status: New → Confirmed
affects: upstart (Ubuntu) → linux (Ubuntu)
Revision history for this message
Adam Michael Roach (adammichaelroach) wrote :

3) Is fixed for me

4) After updates is no longer doing that, it now goes straight to my wallpaper.

Revision history for this message
Jacopo Moronato (jmoronat) wrote :

My messages (see attachment)

summary: - Unexpected boot experience
+ "usb_id: unable to access" - boot experience
Changed in linux (Ubuntu):
status: Confirmed → Triaged
importance: Undecided → Medium
Revision history for this message
getaceres (getaceres) wrote :

I get the same message and I don't see any splash while booting but only text on screen until KDM starts. I have a NVidia card so it may be related to the nvidia drivers.

Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Triaged a while ago but has not had any updated comments for quite some time. Please let us know if this issue remains in the current Ubuntu release, http://www.ubuntu.com/getubuntu/download . If the issue remains, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Revision history for this message
Brad Figg (brad-figg) wrote : Unsupported series, setting status to "Won't Fix".

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: Triaged → Won't Fix
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.