[Bug 1901043] Re: No sound in ubiquity-dm with nomodeset
William Wilson
1901043 at bugs.launchpad.net
Thu Feb 25 15:56:03 UTC 2021
The verification passed for focal. The following steps were taken for
verification:
1)boot to safe graphics mode
a) observe that no startup sound is played
b) `watch -n 1 'systemctl status sound.target'`
1) wait for sound.target to become active
2) observe that no startup sound is played after
sound.target becomes active
2) download source for ubiquity version 20.04.15.11
a) copy the changed files gtk_ui.py and misc.py
to a flash drive
3) reboot to safe graphics mode
a) add `break=init` to the kernel command line
b) in the initramfs, copy gtk_ui.py and misc.py from the
flash drive to the root/ file system
c) exit initramfs and allow boot to continue
d) once the boot process has finished, observe
that no startup sound is immediately played
e) `cat /proc/cmdline` to ensure that `nomodeset`
is on the kernel command line
f) `watch -n 1 'systemctl status sound.target'`
1) the startup sound is played when sound.target
becomes active. Success!
** Tags removed: verification-needed verification-needed-focal
** Tags added: verification-done verification-done-focal
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to ubiquity in Ubuntu.
https://bugs.launchpad.net/bugs/1901043
Title:
No sound in ubiquity-dm with nomodeset
Status in Release Notes for Ubuntu:
Fix Released
Status in ubiquity package in Ubuntu:
Fix Released
Status in ubiquity source package in Focal:
Fix Committed
Status in ubiquity source package in Groovy:
Won't Fix
Bug description:
[Impact]
* When booting to "Safe Graphics" mode the system startup sound would
sometimes not be played
* This is an accessibility issue as the system startup sound is meant to
indicate that Ubiquity is ready
[Test Case]
* Boot an installer image to Safe Graphics mode and listen for the
sound
* You can optionally use `systemctl status sound.target` to monitor when the
sound should be played. This should occur shortly after sound.target becomes
active
[Where problems could occur]
* If sound.target never comes up, the system ready sound will not be played.
This could be caused by a missing or broken sound card
[Other Info]
* It is expected behavior that the sound target may take longer to become active
when nomodeset is on the kernel command line. This is because nomodeset prevents
the kernel from pre-loading audio drivers.
* This problem seems to be more prevalent with Intel sound cards
[Original Description]
Ubuntu Groovy Desktop
There is no sound in ubiquity-dm with nomodeset (safe graphics mode)
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: ubiquity 20.10.13
ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14
Uname: Linux 5.8.0-25-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu50
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.455
CurrentDesktop: ubuntu:GNOME
Date: Thu Oct 22 15:20:00 2020
InstallCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/ubuntu.seed maybe-ubiquity quiet splash ---
LiveMediaBuild: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ubiquity
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1901043/+subscriptions
More information about the foundations-bugs
mailing list