Same here. On Noble and quite happy to test the fix.
--
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/2085162
Title:
Bluetooth devices can't reconnect after reboot or sleep
S
Took me two days to track this one down! Still in 24.04. A better (I
believe) work-around than the one in the OP is this:
sudo install -D -m 0644 /dev/fd/0 "/etc/systemd/system/blk-
availability.service.d/stop-late.conf" <<<$'[Unit]\nBefore=local-
fs.target'
This dependency should be added to the
Why is this invalid? It is still a bug in Ubuntu. I have a bunch of
machines in this state which all now report a systemd state of Degraded.
Is there a way to fix this from the command-line? I only have ssh access
to these machines.
--
You received this bug notification because you are a member
Is it just a matter of enabling whoopsie.path?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apport in Ubuntu.
https://bugs.launchpad.net/bugs/1988870
Title:
apport-autoreport.service fails: whoopsie.path is not enabled
** Changed in: libvpx (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1993867
Title:
Telegram sometimes start endless use 100%
I just did remove all the wireguard connections and recreated them.
Actually I found out that as long as I keep counting up on the wgX,
everything works smooth. But whenever I reuse a wg, it messes it all up
and nm is dying.
--
You received this bug notification because you are a member of Ubuntu
Hello Danilo,
sorry for the late reply - yes, there are more than one connections with wg0.
But this should not be an issue as long as only one connection is enabled at a
time.
Yes, it's very likely that I was hit by this bug. Do you think it's a good idea
to remove all the wireguard-config-fil
actually, it doesn't matter if any dns setting is set or left empty =>
the message stays the same.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/2044014
Title:
ne
** Attachment added: "Bildschirmfoto vom 2023-11-21 19-48-26.png"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721830/+files/Bildschirmfoto%20vom%202023-11-21%2019-48-26.png
--
You received this bug notification because you are a member of Ubuntu
Touch s
** Attachment added: "unitlog.log.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721831/+files/unitlog.log.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to network-manager in Ub
** Attachment added: "Bildschirmfoto vom 2023-11-21 19-45-58.png"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721829/+files/Bildschirmfoto%20vom%202023-11-21%2019-45-58.png
--
You received this bug notification because you are a member of Ubuntu
Touch s
** Attachment added: "Bildschirmfoto vom 2023-11-21 19-46-12.png"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721828/+files/Bildschirmfoto%20vom%202023-11-21%2019-46-12.png
--
You received this bug notification because you are a member of Ubuntu
Touch s
** Attachment added: "Bildschirmfoto vom 2023-11-21 19-46-08.png"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721827/+files/Bildschirmfoto%20vom%202023-11-21%2019-46-08.png
--
You received this bug notification because you are a member of Ubuntu
Touch s
Hello Danilo,
yes I am aware of that; actually I can't tell from where this is set as
actually I did not set any dns configuration. Please see attached log and
screenshots.
Yes, a netplan file has been created. I just retracted all the sensible
information. Quotes and double quotes were set corr
(had to remove a lot of auto-uploaded files due to privacy)
relevant loglines from syslog attached.
** Attachment added: "syslog.log.txt"
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2044014/+attachment/5721253/+files/syslog.log.txt
--
You received this bug notification bec
Public bug reported:
when configuring a new wireguard connection both via nm-connection-editor and
the settings app, NetworkManager crashes and restarts, with the error message
"Message recipient disconnected from message bus without replying".
Currently, I'm unable to add wireguard connections
** Attachment added: "Screenshot_20230430_181759.png"
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1667133/+attachment/5669983/+files/Screenshot_20230430_181759.png
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xo
Yes, it is present in the latest release of Ubuntu 23.04.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1667133
Title:
touch is constantly jumping around (ghost touching)
S
Public bug reported:
We found a breaking change with
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1991761 when running
an application that relies on ogre 1.9 for rendering inside a Docker
container based on the ubuntu:jammy image.
We could confirm that the upgrade causing this was as follo
We found a breaking change with this when running an application that
relies on ogre 1.9 for rendering inside a Docker container based on the
ubuntu:jammy image.
We could confirm that the upgrade causing this was as follows, because
the issue goes away when downgrading versions:
[UPGRADE] libegl-
It seems like there is no more force-probe required for oem-6.1, works
fine out-of-the-box now.
When is the 22.2 mesa from ppa:canonical-x/x-staging going to be
released, currently using the linux-oem-6.1 kernel together with the
23.0 mesa from the Intel Arc package sources.
--
You received this
Is this not going to happen?
> kernel: oem-6.0 plus a bunch of backports from 6.1/drm-tip
--
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/1971712
Title:
Add support for Intel
The new firmware package works fine with the 6.0 kernel, it loads the GuC and
HuC Firmware, as seen below:
[4.691687] i915 :03:00.0: [drm] Finished loading DMC firmware
i915/dg2_dmc_ver2_06.bin (v2.6)
[4.702309] i915 :03:00.0: [drm] GuC firmware i915/dg2_guc_70.1.2.bin
version 70
Hi Timo,
Upgrading to Mesa 22.2 seems to resolve this issue. Using the packages
from the intel repository (https://dgpu-docs.intel.com/installation-
guides/ubuntu/ubuntu-jammy-arc.html) works as well.
Is it planned to release the updated mesa 22.2 packages to Ubuntu 22.04?
--
You received this
I've managed to reproduce this bug on an Arc A380 and Arc A770 GPU. I've
attached the requested lspci output for the A770.
Ubuntu 22.04 has already received a mesa update with backported patches
for DG2 support:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1971712
I haven't tried 22.10 yet
Looking forward to linux-oem-6.0 support. Got an A380 and A770 here for
testing purposes.
It seems like the current proposed build of the linux-oem-6.0 kernel
still has some issues in this regard.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, whi
Are there any plans for providing an i915 DKMS Module with DG2 Support
for oem-5.17?
--
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/1971712
Title:
Add support for Intel DG2
Public bug reported:
updating from server 20.04 to 22.04
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: systemd 249.11-0ubuntu3.6
ProcVersionSignature: Ubuntu 5.15.0-48.54~20.04.1-generic 5.15.53
Uname: Linux 5.15.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.24
Architecture: am
Ubuntu 20.04 is also affected by this bug in the same way.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gpgme1.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1977645
Title:
python3-gpg "1.16.0-unknown" version is incompara
Any idea when the fix for this will be published? We too use debootstrap
off a focal package archive that has updates merged in so new
installations don't have to immediately upgrade 100s of packages.
Currently installations fail because of this.
--
You received this bug notification because you
Here are logs from 3 separate type of boots (actually I had to reboot at
least 20 times, because I had a lot of crashes/hangs):
1) USB safemode boot (since the normal USB boot didn't work ~ 5 times)
2) USB normal boot (it worked, don't know why, but I'm not complaining)
3) normal installed boot (c
With the live USB stick, there are also Xorg issues. Even got a nice
crash rapport.
** Attachment added: "_usr_lib_xorg_Xorg.127.crash"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5593009/+files/_usr_lib_xorg_Xorg.127.crash
--
You received this bug notification be
Here's the vulkaninfo. I got lucky, since the entire GUI hung shortly
after (don't think it's related to running this specific command
though).
Reverted the Wayland (GDM) change, so it's stock behaviour. And yes, I
switched back to stock config and kernel.
Will try to USB live version shortly.
*
Sorry for the late reply.
tonight I installed the full ubuntu-desktop package (with a "clean" test
user) and experienced crashes/hangs and other weird behaviour with the
stock setup. When I disabled Wayland in GDM3, it got a little better,
until that had issues as well.
Note: I went from an 7+ ye
am currently using AwesomeWM ( https://awesomewm.org/ ) with LightDM.
- when I ran the vulkaninfo this time, I temporarily switched back to 'stock'
config (which is radeon, not amdgpu). So that might be correct. Should I switch
to amdgpu and run it again?
- between first post and now, I also swi
Noticed something quite weird when using the default kernel module
(radeon).
- when running glxgears, it starts running normally, but stalls quickly. If I
active movement (hightling a part of my terminal and moving the mouse around
simultaneously), it seems to skyrocket and run normally. Until I
** Attachment added: "lsmod.txt"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5592575/+files/lsmod.txt
--
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/b
** Attachment added: "glxinfo.txt"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5592573/+files/glxinfo.txt
--
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.n
** Attachment added: "vulkaninfo.txt"
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1975566/+attachment/5592574/+files/vulkaninfo.txt
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mesa in Ubuntu.
https://bugs.launc
Already tried out some different things:
- Tried the latest linux kernel
- Fiddled with amdgpu & radeon kernel module options
- Tried running the amdgpu kernel module instead of radeon
Had to SSH into the machine to do anything (usually the system locks
up).
Some error messages from the fiddling:
Public bug reported:
Recently I upgraded my machine and moved my GPU over from the old (Intel
something) to the new machine (AMD Ryzen 7 5700X, B550 motherboard). I
did a fresh Ubuntu install (server) and added packages to get my GUI
rolling (lightdm + awesomewm), just like before.
The graphics c
with timeout of "1sec" is
possible.
Regards
Sebastian
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to openldap in Ubuntu.
https://bugs.launchpad.net/bugs/1973137
Title:
ldap_do_free_request: Assertion `lr->l
Can confirm, but haven't figured out why it occurs sometimes, and
sometimes it doesn't. Definitely no indication of the problem on any UI,
Wifi seems to be connected, it's just no internet coming through. Wifi
on/off fixes it for just a few minutes, too. Very annoying problem, and
it is due to Ubun
I can confirm "killall speech-dispatcher" fixes the hdmi output noise while
reproducing any audio.
My setup:
https://linux-hardware.org/?probe=fd15b34806
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
h
0]: sssd_be:
../../../../libraries/libldap/request.c:970: ldap_do_free_request:
Assertion `lr->lr_refcnt == 1' failed.
If i configured SSSD to use directly our LDAP Server, its working.
Regards Sebastian
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/op
Seems to be fixed with linux-image-5.13.0-39-generic
** 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/
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: linux (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1960460
Titl
Public bug reported:
Fresh install using 20220202 Daily ISO with ZFS + Encryption selected
from the installer
The system ends up in busybox after entering the unlock key.
Here is a part of the logs captured from the screen, the complete log
can be found as an attachement:
find: /dev/zvol/: No s
Public bug reported:
When the Laptop is not connected to it's dock, the bluethooth headset
works.
As soon as it is connected to a Lenovo 40AY0090EU Dock, sound stops on
the headsets and plays via the display connected via DisplayPort.
The headset is still available in sound settings, but even if
** Changed in: libvpx (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/992924
Title:
package libvpx1 1.0.0-1 failed to insta
** Changed in: libvpx (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1366406
Title:
Virtualbox capture error webm(vp8)
St
** Changed in: libvpx (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1518933
Title:
Illegal instruction in vp9_quantize_b_ssse3(
** Changed in: libvpx (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libvpx in Ubuntu.
https://bugs.launchpad.net/bugs/1455780
Title:
the i386 and amb64 versions break each other
Public bug reported:
I have two 4K Monitors connected to a single DisplayPort 1.4 Output via
a DisplayPort 1.4 MST Hub working flawlessly under X.org.
I have enabled nvidia-drm.modeset=1 in the GRUB CMDLINE Settings and
switched to Wayland in the GDM Greeter.
But it seems like Wayland is unable
** Changed in: ffmpeg (Ubuntu)
Status: New => Invalid
--
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/1931045
Title:
FFMPEG silently falls back to software encoding on
** Changed in: vlc (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1374825
Title:
VDPAU does not work in libav on Utopic
Status
Is there a good reason for still using 16.04?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/357732
Title:
cups always prints with the default page size
Status in GS-GPL:
** Changed in: mpg123 (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mpg123 in Ubuntu.
https://bugs.launchpad.net/bugs/105586
Title:
mpg123 does not support large files
St
** Changed in: mpg123 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to mpg123 in Ubuntu.
https://bugs.launchpad.net/bugs/297080
Title:
mpg123 fails playing icecast streams
Status
*** This bug is a duplicate of bug 1572167 ***
https://bugs.launchpad.net/bugs/1572167
** This bug has been marked a duplicate of bug 1572167
package libavcodec-ffmpeg-extra56:amd64 7:2.7.6-0ubuntu0.15.10.1 failed to
install/upgrade: package is in a very bad inconsistent state; you should
*** This bug is a duplicate of bug 1572167 ***
https://bugs.launchpad.net/bugs/1572167
** This bug has been marked a duplicate of bug 1632268
package libmpg123-0:i386 1.22.4-1 failed to install/upgrade: package is in a
very bad inconsistent state; you should reinstall it before attempting
Public bug reported:
Upgraded to 21.04 (hirsute) and now the network card is unavailable
after suspend to RAM (sleep state S3). It worked flawlessly up until
20.10. My workaround for now is unloading and reloading the kernel
module, but that won't work for normal users, hence this report.
NIC in
As I said, the workaround worked. To help others looking for a solution
and finding this bug, I will show it here for my configuration:
1.) Open a terminal
2.) Call xrandr to see, how your desired device is called. In my case,
it's called "HDMI-1". If you have more than one, you may guess, but
ou
Public bug reported:
If come here over bug 1895301 "XrandR does not propose 3440x1440 21:9
resolution".
In bug 1895301 sombody wrote "We just need one person experiencing the bug to
open a bug with the relevant system details automatically attached." - so I did.
I have a similar problem with a
> i'm inclined to also mark this as wont-fix for bionic, unless there
are still people affected by this problem using bionic without some
other workaround.
What kind of workarounds for binoic does this refer to? I have not found
any reliable workarounds yet at least.
--
You received this bug not
Public bug reported:
This is a configuration bug that affects the hirsute-proposed version of
sudo. This bug causes sudo when re-configuring, to assign to an unused
user id that is neither the end user nor root. The result is that sudo
will refuse to run, returning an error message that is display
** Changed in: apt (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: software-center (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: ubuntu-translations
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubu
Sounds like a driver bug.
** Package changed: vlc (Ubuntu) => mesa (Ubuntu)
--
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/1912030
Title:
Crash unless ffmpeg direct renderin
I think I found the bug in the linux 5.4, but I have no idea whether or how to
submit a patch...
The handling of exfat changes completely in the following (but not LTS)
versions.
In the file drivers/staging/exfat/exfat_super.c, in lines 60-
static void exfat_time_fat2unix(struct timespec64 *ts,
The fix is quite offtopic, but for this special case it should be a solution:
the date of the pictures should be also preserved in the EXIF-Data. You can
read the exif-data of the files and set the timestamp from this data.
I used another tool under windows for this so far, but exiftool should do
I made some experiments to define the behaviour, the problem is, that 3
computers with installed ubuntu 20.04.1 LTS behave(d) differently
(installing fuse-exfat 1.3.0 stopped the described behaviour in two of
the computers, seems, that nautilus is able to bypass fuse-exfat in some
conditions).
I m
... sorry, I never worked with repositories...
may someone check this:
https://code.launchpad.net/~arter97/+archive/ubuntu/exfat-dev
exfat-dkms - 5.8~2arter97~ubuntu20.04.1 (maybe also in the other versions?)
in the file misc.c:
void exfat_get_entry_time(struct exfat_sb_info *sbi, struct timespe
ngle session on Nov 18 2020(!), here only the
files "Fuga.blend1, Materials.blend1, Mixereinstellungen.vmsms" affeced - I
have no idea, what the common feature may be.
sebastian@osamu:/media/4tbp/Eigene Videoprojekte/Fuga BWV 863$ ls -l
insgesamt 106752
-rwxr-xr-x 1 root root 1016
... I have to add: exfat-fuse and exfat-utils are in the "newest
version" 1.3.0-1 and the bug still exists!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu.
https://bugs.launchpad.net/bugs/1872504
Title:
For it hasn't been corrected in the regular updates, I also confirm that it's
still present on ubuntu 20.04, while using an external 4 TB hard drive. I'd
like to emphasize the importance of this bug, for it may lead to complications
and erroneous deletions if I used the drive for synchronizing f
Broken driver or invalid driver selection is nothing we can fix in vlc.
** Changed in: vlc (Ubuntu)
Status: New => Invalid
--
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
Public bug reported:
Presumably mouse and keyboard (both uhci/ehci connected) lose power when
system suspends (LEDs are off), and so they are unable to wake the
system up despite `cat /sys/bus/usb/devices/$bus-$port/power/wakeup`
returning `enabled` (by default)
Expected results:
The system wakes
Looks like the secondary problem is here is the same as
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1880305
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1872286
T
Unfortunately I have not experience or knowledge of Ubuntu packaging or
bug fixing processes, but is there anything I can do to help get this
fixed in bionic?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
** Package changed: vlc (Ubuntu) => mesa (Ubuntu)
** Changed in: mesa (Ubuntu)
Status: Incomplete => New
--
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/1889052
Title:
As suspected, this seems to be an issue with a driver.
** Package changed: vlc (Ubuntu) => mesa (Ubuntu)
--
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/1888558
Title:
VLC is
** Package changed: vlc (Ubuntu) => qtbase-opensource-src (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1882853
Title:
No video output if top of pr
Please provide a log of vlc -vvv.
** Changed in: vlc (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libav in Ubuntu.
https://bugs.launchpad.net/bugs/1374825
Title:
VDPAU doe
** Changed in: intel-media-driver (Ubuntu)
Status: New => Fix Released
** Changed in: intel-media-driver-non-free (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libva in Ubu
Fixed in 2.8.0-1
** Changed in: libva (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1879796
Title:
File descriptor leak in libv
** Changed in: libva-utils (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to libva in Ubuntu.
https://bugs.launchpad.net/bugs/1872000
Title:
2020'Q1 Intel new media release
Status
** Summary changed:
- Truncated audio frequency response on snd-aloop device
+ Truncated audio frequency response on snd-aloop device (resample-method =
speex-float-1)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaud
It also affects pulseaudio 11.1 which comes originally with bionic.
I found these two lines to trigger the bug on /etc/pulse/daemon.conf
default-sample-format = s24le
default-sample-rate = 48000
The default values works just fine.
--
You received this bug notification because you are a member
Here it is:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/915
** Bug watch added: gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues #915
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/915
--
You received this bug notification because you are a member of Ubu
** Summary changed:
- Truncated audio frequency response on monitor device
+ Truncated audio frequency response on snd-aloop device
--
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.
Public bug reported:
Hi. I've found something strange happening when I record the output of a
sound card through loopback device audio monitor.
If I load the snd-aloop module, then setup a player to play a chirp sound that
spans a sine wave between 10Hz and 22kHz through it, and then record the
Public bug reported:
During the Dist upgrade from 18.04 LTS to 20.04 LTS udev failed to
configure interrupting the upgrade.
dpkg complained that kvm already exist but it is not a system group.
>From what I saw my user was the only member of kvm group
I don't recall installing kvm manually but I
** Package changed: linux (Ubuntu) => powermgmt-base (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to powermgmt-base in Ubuntu.
https://bugs.launchpad.net/bugs/1878635
Title:
Intel Titan Ridge TB3 USB Controller pre
Thanks, removing timidity did help.
--
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/1879054
Title:
No sound after 20.04 update
Status in pulseaudio package in Ubuntu:
Public bug reported:
After update from 18.04 to 20.04 sound stopped working.
KDE does not display Xonar sound card at all.
$ aplay /usr/share/sounds/alsa/Front_Center.wav
does not make any sound
Alsamixer displays Xonar set at full volume but changing anything there
does not seem to have any eff
Public bug reported:
If I set the scaling of my two QHD monitors to 125%, they remain black
when saved.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
Uname: Linux 5.4.0-28-generic x86_64
NonfreeKernelModules: nv
Ok, this is interesting. I just downgraded to bionic (18.04) and now the
dongle is working! So something went wrong somewhere along the way but
the H/W is definitely good.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez
Ok, I tried again but changed the command with the version above to:
make SUBLEVEL=0 EXTRAVERSION=-46-generic modules_prepare
Now I get in dmesg:
[ 7851.540982] usb 10-1: new full-speed USB device number 4 using xhci_hcd
[ 7851.788016] usb 10-1: New USB device found, idVendor=0a12, idProduct=000
Here are the steps I followed (all on Eoan):
sudo apt install kernel-package linux-source flex bison libssl-dev libelf-dev
tar xf /usr/src/linux-source-5.3.0.tar.bz2
cd linux-source-5.3.0
make mrproper
cp /usr/lib/modules/5.3.0-46-generic/build/{.config,Module.symvers} .
make oldconfig
patch -p1 <
Gave it another try with linux-image-unsigned-5.7.0-999-generic on Eoan,
same behaviour.
--
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
1 - 100 of 370 matches
Mail list logo
