** Tags added: hwe-bluetooth
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1873718
Title:
CSR8510 based BTA-402 Bluetooth device cannot be started
Status in bluez package
Sounds like this might be a kernel bug, or a hardware problem. I am
skeptical of CSR Bluetooth dongles since they seem to be consistently
unreliable, at least on Linux.
Please try a newer (or older) kernel version and tell us if that makes
any difference:
Please explain in more detail what kind of problem you are having.
** Package changed: xorg (Ubuntu) => ubuntu
** Changed in: ubuntu
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in
Public bug reported:
In the GUI, I can go to the Bluetooth settings and it shows BT to be
off. I turn on the little switch at the top but nothing else changes. If
I navigate away from this page and then back, the switch is off again.
If I try to reset the device on the command line I get:
Public bug reported:
Relatar erro na execução Linux
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-96.97-generic 4.15.18
Uname: Linux 4.15.0-96-generic x86_64
.tmp.unity_support_test.0:
ApportVersion: 2.20.9-0ubuntu7.14
** Changed in: pulseaudio (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1873630
Title:
[pulseaudio] alsa-ucm.c: Assertion
Note that we don't recommend use of nvidia-drm.modeset=1 for most users
because it still results in some bugs:
https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-drm.modeset
And I'm not sure that's even a complete list. So you should be aware of
what you're getting into.
--
You
And yes nvidia-drm.modeset=1 will give you back the missing boot
animation, but that discussion should stay in bug 1868240.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
worsk great. thanks. anyway, this should be fixed automaticaly :/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mir in Ubuntu.
https://bugs.launchpad.net/bugs/1808060
Title:
libmirclient causes multiarch SDL2 headers to
I agree. I don't see this as an upstream issue because I have tried it
on other distros - they worked as expected. USB hotplugging updates the
audio device. However, a reboot simply restores whatever was last in
use. For some reason, only on Ubuntu, it treats a reboot as plugging a
new USB device.
As mentioned in comment #37 the internal mic works well with Ubuntu
20.04 live mode. I haven't tried installing Ubuntu 20.04 though, as some
report the mic doesn't work once installed.
I wish I knew more and had the time to understand the difference (beyond
kernel) between Ubuntu 20.04 live mode
Sorry to post so much - I wish I could consolidate or edit all these
posts. The next day I came back and it didn't work in Zoom. I tried a
bunch of things listed on the following web page, starting with simplest
first, from
https://support.system76.com/articles/audio/
until finally I did
sudo
This is the most heated bug on this site. Can someone please get this
fixed?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1553685
Title:
Lenovo Y700-17ISK subwoofer
This failure appears to be coming from the gnome debconf frontend, which
for some reason is crashing in the upgrade environment between 18.04 and
20.04.
** Package changed: pam (Ubuntu) => libgtk3-perl (Ubuntu)
** Changed in: libgtk3-perl (Ubuntu)
Status: Incomplete => New
** Tags added:
This is a bug in 20.04 as well. I have no Release file, this is a
private, unsigned repository, only Packages.xz. On first run, apt update
first works. On the second run apt update issues a HTTP GET with an If-
Modified-Since header:
GET /deb/Packages.xz HTTP/1.1
Host: XXX
Cache-Control:
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: apt (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apt in Ubuntu.
@Rajat Pandita: awesome, thanks for sharing!
I came here to report that I too was experiencing this bug: GTX 1060,
up-to-date Focal Fossa beta, NVidia 440 driver series, 5.4.0-24 kernel.
Couldn't log in.
Removing `splash` from grub's kernel parameters solved the issue, but
adding
Great, thanks for testing, closing the bug!
** Changed in: pulseaudio (Ubuntu)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
I had a problem with a *missing* internal microphone today (well, I spotted it
today - probably been like this for ages...).
Note that this was PulseAudio saying that there were no input devices.
The problem (as I eventually spotted) was that I'd set the Profile to be
Analgue Stereo Output
to
"
i added w to
owner @{HOME}/.{,cache/}fontconfig/** mrl,
"
:
cboltz said in apparmor irc channel:
I'd recommend _not_ to allow writing to ~/.cache/fontconfig/ because apps could
in theory poison that cache
actually we recently (intentionally) removed write permissions in
abstractions/fonts
I don't think gdebi has been included in the install media.
** Package changed: ubuntu => gdebi (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdebi in Ubuntu.
https://bugs.launchpad.net/bugs/1873658
Title:
Deb
You have been subscribed to a public bug:
When you download a DEB file within 20.04 Ubuntu Beta and you double
click it the file is opened by the archive manager. I would expect the
installer to open the file just like in previous versions of Ubuntu.
** Affects: gdebi (Ubuntu)
Importance:
I’ve had the same problem during installation Ubuntu 20.04 Beta and last
daily release.
I’m not sure if it’s necessary but my PC spec is Intel i9
9900k/RTX2080Ti.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to
After doing some research I'm quite sure that this bug was introduced by [1] in
the 5.4.29 mainline kernel and the 5.4.0-22.26 ubuntu kernel.
The bug was already fixed by [2] in the 5.4.32 mainline kernel. At least that's
the case on my machine [3] and Heiner Kallweit also pointed in this
Did a Fresh Install today, and Selected the option to automatically install
proprietary drivers, Something changed and my Installation Failed, I got a
message saying that there was already a bug for that, I followed along and
updated my situation in that bug report, because why not, It is just
** Package changed: ubuntu => ncurses (Ubuntu)
** Changed in: ncurses (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ncurses in Ubuntu.
https://bugs.launchpad.net/bugs/1872896
You have been subscribed to a public bug:
This happens on a 20.04 LTS (Focal Fossa) beta system, specifically, the
xubuntu-20.04-beta-desktop-amd64.iso as downloaded on Apr 14.
When sshing into the 20.04 system, from the previous LTS (18.04),
entering/exiting insert mode in vi emits what looks
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: lightdm (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
This bug was fixed in the package adduser - 3.118ubuntu2
---
adduser (3.118ubuntu2) focal; urgency=medium
* Add support for ZFS home directories:
- Home directories are created as ZFS dataset if zsysctl is installed. If
the command is not installed or fails, the user will
Sebastien, I can confirm that the updated package fixes the problem.
Thanks for your work!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to evolution-data-server in
Ubuntu.
https://bugs.launchpad.net/bugs/1871019
Title:
It's half fixed, but NOT for my bug posting (I am on Ubuntu 18.04 and
compilation for it is MISSING)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1867188
Title:
Mesa
I ran the software updater and noticed that it installed a new
pulseaudio:
pulseaudio:
Installed: 1:13.99.1-1ubuntu3
Candidate: 1:13.99.1-1ubuntu3
After rebooting the system, I'm running this version.
You will be happy to learn that pulseaudio doesn't crash with this
version, and it shows
I ran the software updater and noticed that it installed a new
pulseaudio:
pulseaudio:
Installed: 1:13.99.1-1ubuntu3
Candidate: 1:13.99.1-1ubuntu3
After rebooting the system, I'm running this version.
You will be happy to learn that pulseaudio doesn't crash with this
version, and it shows
This bug was fixed in the package gtk+3.0 - 3.24.18-1ubuntu1
---
gtk+3.0 (3.24.18-1ubuntu1) focal; urgency=medium
* Update to the current stable version (based on Debian) (lp:
#1873038)
-- Sebastien Bacher Thu, 16 Apr 2020 11:23:10
+0200
** Changed in: gtk+3.0 (Ubuntu)
I also experienced this bug. I was running Ubuntu 18.04, and I upgraded
to Ubuntu 20.20 yesterday by running `update-manager -d` on the command-
line, which launched the GUI. During the upgrade itself, I was shown a
dialog displaying an error relating to pam.
I've attached apt-term.log (for me)
OK, that's bug #1873630.
We don't actually know that this current crasher bug is correctly solved
by the above patch, since pulseaudio is not yet working. Perhaps the
new bug was there all along, but perhaps it was introduced by this patch
being an incomplete fix.
--
You received this bug
Public bug reported:
I have a Gigabyte motherboard that gives pulseaudio fits in Ubuntu 20.04
beta. (It worked fine in 18.04.4 LTS.) It produced pulseaudio crashes
with bug #1870833 until a proposed fix was brought in from upstream:
Public bug reported:
Auditd was working on my system (Ubuntu 18.04LTS, kernel
4.15.0-1065-aws) until recently. But after splitting off /var into a new
filesystem it fails to launch.
running '/sbin/auditd -f' as root indicates a problem writing the pid file (no
file exists even when it says one
When I exit software-properties-gtk, suspend/resume my computer and log-
in back, I have the expected popup on the top-left of the screen. I
cannot exit this popup, neither by pressing the Cancel button, and
neither by entering my password and pressing the authenticate button.
I need to log off
When I start software-properties-gtk from a terminal and click on one of
the mentioned checkbox, I get this error output:
ERROR:root:Authentication canceled, changes have not been saved
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is
** Summary changed:
- Autorotation works but is backwards
+ [WinBook TW102] Autorotation works but is backwards
** Package changed: xorg (Ubuntu) => linux (Ubuntu)
** Also affects: iio-sensor-proxy (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification
** Tags added: a2dp a2dp-skip
** Tags removed: cosmic
** Tags added: bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1810636
Title:
[Qualcomm Atheros QCA6174]
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pulseaudio (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
** Summary changed:
- Suspect QCA6174 btcoex | Ubuntu 18 Bluetooth Audio Skip/Stutter/Delay WiFi
bandwidth conflict Dell XPS 9570 [Pending PulseAudio testing]
+ [Qualcomm Atheros QCA6174] Bluetooth audio choppiness
** Also affects: pulseaudio (Ubuntu)
Importance: Undecided
Status: New
*** This bug is a duplicate of bug 1810636 ***
https://bugs.launchpad.net/bugs/1810636
Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1810636, so it is being marked as such. Please
*** This bug is a duplicate of bug 1810636 ***
https://bugs.launchpad.net/bugs/1810636
It appears the same issue with the same Bluetooth chip as yours was
being discussed in:
https://forum.manjaro.org/t/enabling-bluetooth-coexistence-on-ath10k-
atheros-qca6174/81121
** Summary changed:
-
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1853374
and then change the status of the bug to 'Confirmed'.
If, due to the
Comment #13 appears to be a new bug. Please open a new bug for that by
running:
ubuntu-bug pulseaudio
and mentioning:
Apr 18 01:13:10 shh pulseaudio[1443]: E: [pulseaudio] alsa-ucm.c: Assertion
'jack' failed at modules/alsa/alsa-ucm.c:2158, function
device_add_hw_mute_jack(). Aborting.
48 matches
Mail list logo
