This bug is back again in Kubuntu 20.10. Should I start a new bug? I
can attach pactl output for both the good and bad states if it would
help. When is issue occurs, aplay -l shows the problem device and
killing PA fixes the problem.
--
You received this bug notification because you are a
This bug can be closed as the driver seems to have fixed itself after
recent updates. I was reporting this issue remotely for my 82 year old
father, so I am not exactly sure what he did to fix the problem.
--
You received this bug notification because you are a member of Desktop
Packages, which
Public bug reported:
When using HPLIP to install drivers for HP ENVY 5530 e-All-in-One
Printer, the software correctly detects and tries to install the printer
driver. However, launching the printer window using printer icon in
the system tray shows a printer with a red x and a message that
Boot issue fixed with latest release 19.04 candidate (16-04-19).
Closing report.
** Changed in: nvidia-graphics-drivers-340 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
Legacy laptop, Dell Vostro 1720, booted to black screen after fresh full
disk install. Using ctrl-alt-f2 to drop to a terminal and issuing
"startx" completed the boot process.
Installed NVidia 340 driver which crashed the current session and sent
me to an endless GUI
Sound is still working today with the 4.20.17 kernel. I will give it
another day before I draw any conclusions.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1822426
Title:
uname -a: Linux Imagined 4.20.17-042017-generic
NVIDIA Driver Version: 418.56
Resumed 3 times from sleep with the 4.20 kernel, so far sound is working
fine.
Sometimes the issues does not appear until the next day (warm vs cold
hw?), so I will report back tomorrow.
If sound works for next few
I still lost sound after setting "realtime-scheduling = no" in
/etc/pulse/daemon.conf.
Previous kernels have worked fine with this hw.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
Journal file when sound failed after resume.
** Attachment added: "journal.txt"
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1822426/+attachment/5252628/+files/journal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Not sure if recent updates have fixed the issue, but problem has not
appeared after several sleep and awake events. I will ensure to post
details and try the above edit if problem recurs.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
With 19.04, Intel Corporation 8 Series/C220 Series Chipset High
Definition Audio Controller intermittently is not enabled when resuming
from sleep. The HDMI sound device is enabled but that is not hooked up
on my system. New with 19.04, when sound works after resume, an icon
Confirming this fixes my bug also:
https://bugs.launchpad.net/ubuntu/+source/sddm/+bug/1762885.
Nice job Alberto!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-prime in Ubuntu.
https://bugs.launchpad.net/bugs/1764005
Title:
Network connected without double password prompt via Ubiquity and from
the live boot panel icon (rebooted to test both). All secure networks
were correctly marked as "secure".
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
** Package changed: plasma-pa (Ubuntu) => pulseaudio (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1716092
Title:
Enabling Auto switching streams on new active output
Public bug reported:
While testing OEM install, the live boot, vendor update boot, and boot
to end user setup worked fine. After entering credentials and
performing final user setup, the subsequent reboot resulted in a
terminal login prompt. After logging in at the prompt, startx was
required
15 matches
Mail list logo
