Public bug reported:
Got all the way through the downloads and installation and crashed at
the last second.
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:
The package information is not available on my copy of ubuntu because I
installed some extra software - python 3 upgrades etc.
The system options such as mouse functions should be in the kernel not an
application package. I believe the bug report was clear.
Also yes, a bug can be in more than one
Public bug reported:
Description:Ubuntu 20.04.1 LTS
Release:20.04
Probably the Kernel
What I expected: I expected the right mouse button to be the primary
What happened instead: The primary button was the left button even
though the mouse configuration showed it to be the right
A related issue was reported again in
https://github.com/igbinary/igbinary/issues/299 in PHP 7.4, Ubuntu 20.04
and igbinary 3.1.2, in the form of a reproducible segmentation fault for
ArrayObject.
There have been no changes to the igbinary v2 serialization format
itself - 3.1.6 and 3.1.2 should
Thanks, Colin. I intend to retest, with 20.10, but for now, with
deduplication disabled, things seem stable.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899249
Title:
OpenZFS writing stalls,
00400cc0 x26: d91c5600
[97679.052204] x25: 0001e843ee28 x24: 00001000
[97679.052207] x23: 000133996400 x22: 0001f554c810
[97679.052209] x21: 0001da0ca000 x20: 0001f5518b80
[97679.052212] x19: 0001da0ca000 x18:
[97679.052214] x17
And, after 18 hours+, I was able to archive a ZFS snapshot, using
BorgBackup, with the WBT settings, suggested, earlier:
tyson@ubuntu:~$ sudo zfs send Yaesu@Crucial-2TB-1951E22FA633 | borg create
--stats BorgStore::Yaesu@Crucial-2TB-1951E22FA633
Needs more time, in terms of long-running I/O, but changing the WBT
setting at least makes retrieving snapshots a little faster, with "zfs
list -t all".
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
All of the drives in the pool are SSDs (2x Crucial BX500 (2TB), 1x
SanDisk Ultra 3D (4TB), 1x Samsung 870 QVO (4TB), but obviously don't
perfectly-align, in terms of performance characteristics - but, I'll
test the WBT tuneable, to see if it makes a difference.
I'm also suspecting that some power
Set the WBT value to 0, for all of the devices, whilst another archive
run takes place. The last one ran for just over 20 hours, before hitting
the I/O problem.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm using 16GB of swap, on a ZVOL, in the pool, but I can also test with
swap, on the internal MicroSD card's EXT4 root partition, if it helps.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1899249
Here's a full "dmesg" log, if it helps:
tyson@ubuntu:~$ dmesg
[0.00] Booting Linux on physical CPU 0x00 [0x410fd083]
[0.00] Linux version 5.4.0-1018-raspi (buildd@bos02-arm64-052) (gcc
version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #20-Ubuntu SMP Sun Sep 6 05:11:16
Looks like I could archive about 1.3TB, of a 1.64TB snapshot, before
things started to go bad, again:
[110079.681102] INFO: task z_wr_iss_h:2171 blocked for more than 120 seconds.
[110079.688123] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
[110079.695167] "echo 0 >
Thanks.
I was able to archive, and delete 400GB of data, without problems,
earlier on, today, which reduced the "REFER" of my data set, a little -
however, it looks like I probably need to focus on archiving, and
removing some of the older snapshots, if I want to trim down the memory
utilisation
Unfortunately, I haven't got a storage device large enough, to contain
all of the data from the pool, and much of it cannot be recreated, or
restored, from another source, so I won't be able to nuke the pool, and
rebuild it.
--
You received this bug notification because you are a member of
Also receive this, when trying to archive a large directory:
[ 2055.147509] INFO: task z_wr_iss_h:2169 blocked for more than 120 seconds.
[ 2055.154450] Tainted: P C OE 5.4.0-1018-raspi #20-Ubuntu
[ 2055.161401] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
]
[12205.175609] zpl_iter_write+0xe4/0x150 [zfs]
[12205.175629] new_sync_write+0x100/0x1a8
[12205.175638] __vfs_write+0x74/0x90
[12205.175647] vfs_write+0xe4/0x1c8
[12205.175657] ksys_write+0x78/0x100
[12205.175666] __arm64_sys_write+0x24/0x30
[12205.175676] el0_svc_common.constprop.0+0x80/0x218
In the meantime, I'll see if I can temporarily disable ZPool-level
deduplication, and retry the backup run, again, on the Windows machine.
Whilst it's not the perfect long-term solution, I might look into using
offline deduplication, for older, infrequently-accessed data in the pool
(probably
It looks like writing snapshots, with "zfs snapshot" will sometimes
stall, even if other commands, like "zfs status" appear to work,
occasionally, too.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
_io_start+0x670/0x9f8 [zfs]
[10151.015765] zio_vdev_io_start+0xdc/0x2b8 [zfs]
[10151.015852] zio_nowait+0xd4/0x170 [zfs]
[10151.015939] vdev_queue_io+0x23c/0x258 [zfs]
[10151.016031] zio_vdev_io_start+0x94/0x2b8 [zfs]
[10151.016118] zio_nowait+0xd4/0x170 [zfs]
[10151.016205] vdev_mirror_io_start+0xa8
25496.768595] lookup_open+0x4ec/0x6a8
[25496.768604] do_last+0x260/0x8c0
[25496.768614] path_openat+0x84/0x258
[25496.768624] do_filp_open+0x84/0x108
[25496.768636] do_sys_open+0x180/0x2b0
[25496.768647] __arm64_sys_openat+0x2c/0x38
[25496.768657] el0_svc_common.constprop.0+0x80/0x218
[2549
Hi,
Is this the best place to report this, or should I put it on the Gnome
Bugzilla too?
Thank you very much for your time and I look forward to any assistance
you are willing to provide.
Sincerely,
Brandon Tyson
On 9/17/18, Alex ARNAUD wrote:
> Hello all,
>
> I'm able to
remains silent.
I use this option a lot especially when taking notes, as for me it's the
equivalent of how sighted users can look at what they've just written
and make any corrections.
Thank you very much for your time and I look forward to any fixes you
may be able to provide.
Sincerely,
Brand
ager -d results in this same sort of problem occuring.
> The expected result is that when running the installer, that the
> bootloader will install and the installation would succeed.
> Thank you very much for your time and I look forward to any fixes you may
> be able to provi
fixes you may be
able to provide.
Sincerely,
Brandon Tyson
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.3
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.389
It's fixed by upstream. Manjaro 17.1.6 Gnome is working as expected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1697701
Title:
Wacom tablet cannot Map to Monitor properly with dual/multiple
Public bug reported:
App won't let me log even after installing and uninstalling
** Affects: apache2 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
New test result today seems to be a intel P-state related problem.
I had reverted everything to their default state, with only the following
changes in TLP settings:
/etc/default/tlp
# Set Intel P-state
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
I did a few more tests. On my system, the combination of a realtime
(lowlatency) kernel and certain tlp settings fixed the random crash.
Although the side effect was the machine can get very hot because CPU
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
If you were testing on a laptop without a power supply connected, there
is an additional TLP settings change:
SCHED_POWERSAVE_ON_BAT=0
--
You received this bug notification because you are a member of
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
On my system:
1) the problem doesn't seem to be related to i915 firmware (which the archlinux
report I mentioned)
2) the problem seems to be triggered by a spike in CPU/GPU stress, it can be
triggered by
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
Here is the crach log and further discussion linked by the bug reporter on
archlinux:
https://github.com/nisenbeck/ct-server-2016-jessie/issues/1
** Attachment added: "intel_crash.txt"
*** This bug is a duplicate of bug 1554613 ***
https://bugs.launchpad.net/bugs/1554613
I have a machine with intel Skylake and it is suffering random reboot.
Although I'm not familiar with hardware side of things, please let me
know if there is anything I can help.
Meanwhile, the archlinux
Marked the affected package to mutter as described in
https://bugzilla.gnome.org/show_bug.cgi?id=782032
** Also affects: mutter (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There was a similar bug reported to Gnome with more technical
description: https://bugzilla.gnome.org/show_bug.cgi?id=782032
** Bug watch added: GNOME Bug Tracker #782032
https://bugzilla.gnome.org/show_bug.cgi?id=782032
--
You received this bug notification because you are a member of
Public bug reported:
In Ubuntu Gnome 17.04, Wacom tablet cannot be properly mapped using the
"Map to Monitor" dialogue provided by gnome-control-center's Wacom
panel. It's always mapped to the first monitor, and the ratio is
incorrect. Both Wayland and Xorg sessions are affected. It has never
Public bug reported:
attempted to install cups from
https://help.ubuntu.com/lts/serverguide/cups.html using the teminal and ran
into error message:
Errors were encountered while processing:
/var/cache/apt/archives/cups-daemon_2.1.3-4ubuntu0.2_amd64.deb
E: Sub-process /usr/bin/dpkg returned an
Public bug reported:
Ubuntu 16.04 is affected, probably every Ubuntu release with php 7.0.
Installations with php 5 should be unaffected, though igbinary releases
also contain performance improvements.
This should be upgraded to 2.0.0 (on PECL) or 2.0.1. The PHP function
signatures and
I always encounter this bug on every Ubuntu released after its
discovery. I have to use RSA key to SSH everyday and it annoys me to no
end.
Comment 9 helped me to workaround this bug though. That's a start! -_-
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
I dicovered that "sudo colormgr get-devices" listed my devices, while
"colormgr get-devices" does not. Is this a privilege issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514990
Title:
I upgraded to colord 1.2.12-1ubuntu1 from Xenial and this issue is
solved after that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514990
Title:
Primary screen not listed in Gnome color manager
I thoroughly tested the patches when the bug happened to me before. The
same kind of stuttering never happened again after the fix was released.
I suppose the newer reports are not related to this bug. Please
understand not all choppy audio has the same source.
You may troubleshoot over these
I can confirm this bug from Ubuntu Gnome 15.10, after all newest
packages installed. This did not happened in 14.04.x and 15.04.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514990
Title:
Primary
There is a terminal command:
colormgr get-devices
I wonder it list anything on 15.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1514990
Title:
Primary screen not listed in Gnome color manager
See Debian bug 787652 for a patch for this
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787652
** Bug watch added: Debian Bug tracker #787652
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=787652
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I was looking at the details before letting apport submit the bug and I
noticed that the stack trace I was just like the one submitted here
having no debug information available. So I ran 'sudo apt-get install
bluez-dbg libbluetooth3-dbg', rebooted and the problem went away... it's
a hiesenbug.
That's odd - the error had been annoying me every boot for months has
now gone, even after apt-get --purge bluez-dbg; reboot and then the
same for bluez-dbg. To be clear, the last time the error appeared was
at boot time before installing both bluez-dbg and libbluetooth3-dbg as
per comment #7.
I
Public bug reported:
The computer randomly locks up. I switched to nouveau because NVIDIA
tested driver caused artifacts with SLI enabled. But nouveau doesn't
seem to support SLI and locks up randomly. See attached screenshot
about DRM GPU lockup.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Public bug reported:
If SLI is enabled, there are many flickering artifacts and double images
(especially tooltips). Eventually, the desktop environment locks up
completely and the computer needs a forced manual reset. I needed to
disable SLI as soon as possible and restart in order to get out
Bug does not show up in screenshot which means ... ?
Bug is easy to reproduce. Use recommended NVIDIA driver with any two
NVIDIA cards in SLI and see bug right away.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Attachment added: Since bug doesn't show up in screenshot, I took a picture
of the monitor.
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1365102/+attachment/4194843/+files/20140903_183606_resized.jpg
--
You received this bug notification because you are a member of Ubuntu
Bugs,
** Description changed:
If SLI is enabled, there are many flickering artifacts and double images
- (especially tooltips). Eventually, the desktop environment locks up
- completely and the computer needs a forced manual reset. I needed to
- disable SLI as soon as possible and restart in order
** Also affects: xorg-server
Importance: Undecided
Status: New
** Project changed: xorg-server = nvidia-drivers-ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1365102
Title:
** Also affects: nvidia-graphics-drivers-310-updates (Ubuntu)
Importance: Undecided
Status: New
** Package changed: nvidia-graphics-drivers-310-updates (Ubuntu) =
nvidia-graphics-drivers (Ubuntu)
** Summary changed:
- Enabling SLI on NVIDIA tested drivers causes artifacts and freeze
@Andrejs
I'm using Trisquel 6.0 (Ubuntu 12.04 based) + Linux-libre 3.11.x / 3.12.0, it
works fine for me.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1136110
Title:
USB Audio Codec choppy
No regression saw here. I'm using Linux Libre kernel 3.10.1 X64.
I think it is a bad idea to connect an USB DAC through a HUB, though.
Even a mouse gets choppy from time to time in spite of being the only
thing on a HUB. The last time I did this I was still using Windows 7 and
it didn't work for
Today the revert landed on kernel v3.10-rc5.
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.10-rc5-saucy/
I've tested it and it worked. Finally I can use my DAC again. It had been half
an year since.
Thank you all guys! :)
--
You received this bug notification because you are a member of
Thank you for looking into this bug, Alan!
Thank you for building those kernels for us to test, Joseph!
And thank you Tim for testing the debug kernel because I couldn't risk breaking
my working machine at the moment.
:)
--
You received this bug notification because you are a member of Ubuntu
Hello Joseph,
The not-reverted debug kernel that you had just built fails to boot on my
system.
http://kernel.ubuntu.com/~jsalisbury/lp1136110/commit-not-reverted/
I don't know much about this, but the file size for the images are very
different to the reverted ones.
(reverted: 13M/30M)
It seems that Alan's asynchronous DAC is not the only one that worked
fine. My friend has an Arce MDAC2 which however is labeled
asynchronous, not affected by this bug. That DAC supports only two
sample rates: 44100Hz and 48000Hz at 16bit. I happen to know it use a BB
PCM1792 as its DAC chip, but
I took a look in the information of the commit that caused the regression:
https://patchwork.kernel.org/patch/2164101/
And I think there are some details to report:
1) So far as I know, the affected Asynchronous DACs are all USB 1.1
devices, and therefore low-speed (despite being labled as full
Sorry for overlooking part of the request in comment #71.
I have done an extra usbmon trace using the following kernel, which is not
affected by this bug:
$ uname -a
Linux tysontan-ThinkPad-X201-Tablet 3.5.0-25-generic #39-Ubuntu SMP Mon Feb 25
18:26:58 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Here is how I tested with usbmon trace:
1. Start PC with USB DAC is on.
2. Start 'cat' to trace USB.
3. Start Jack Audio Connection Kit Service (which ensures the audio stream is
bit exact, sample rate exact).
4. Start Clementine.
5. Play a song for a few second, stop.
6. Play another song for a
I have tested the following packages:
linux-headers-3.8.0-19-generic_3.8.0-19.29~lp1136110v1_amd64.deb
linux-headers-3.8.0-19_3.8.0-19.29~lp1136110v1_all.deb
linux-image-3.8.0-19-generic_3.8.0-19.29~lp1136110v1_amd64.deb
linux-image-extra-3.8.0-19-generic_3.8.0-19.29~lp1136110v1_amd64.deb
They
Alan Stern
I have done an usbmon trace using the following kernel
$uname -a
Linux tysontan-ThinkPad-X201-Tablet 3.5.0-28-generic #47-Ubuntu SMP Tue Apr 9
19:03:54 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
Using the mehtod described in the following URL:
I have also captured the USB device information of my test environment,
just in case it's going to be needed, using CLI command sudo lsusb -v .
Those information is saved as a text file and uploaded as the attachment
of this comment.
Hope the information I had collected can be useful. Thanks in
Joseph Salisbury
OK, thanks for helping us to build all those bisect kernels!
:)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1136110
Title:
USB Audio Codec choppy playback
To manage
I have tested the following commit:
78796ae17eacedcdcaaeb03ba73d2e532a4c8f83
filename:
linux-image-3.8.0-030800rc5-generic_3.8.0-030800rc5.201304101508_amd64.deb
This kernel is not affected by the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I have tested the following commit:
b09a61cc0bc2a7151f4ab652489e85253d5d0175
This kernel is not affected by the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1136110
Title:
USB Audio Codec
I tested the following commit:
3e619d04159be54b3daa0b7036b0ce9e067f4b5d
filename:
linux-image-3.8.0-030800rc5-generic_3.8.0-030800rc5.201304051428_amd64.deb
This commit is affected by the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I've tested the following commit:
f292e7f9fb0e4bec68bbd83443407d6bb7922d36
filename:
linux-image-3.8.0-030800rc5-generic_3.8.0-030800rc5.201304041308_amd64.deb
This commit works normally. Not affected by the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
##CLI COMMAND
grep device.buffering -B 10
##RETURNS
I: [pulseaudio] sink.c: device.bus_path = pci-:00:1a.0-usb-0:1.5.4:1.0
I: [pulseaudio] sink.c: sysfs.path =
/devices/pci:00/:00:1a.0/usb1/1-1/1-1.5/1-1.5.4/1-1.5.4:1.0/sound/card1
I: [pulseaudio] sink.c: udev.id =
Joseph Salisbury
I have just tested 3296944e29a048c06c5d724ef5c2c8c6e1297161,
This commit works normally without being affected by the bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1136110
I tested the following commit:
200e0d994d9d1919b28c87f1a5fb99a8e13b8a0f
filename:
linux-image-3.8.0-030800rc5-generic_3.8.0-030800rc5.201304031425_amd64.deb
This commit is affected by the bug.
P.S. Please move each of those packages into their own directory. As the
number of files increased, I
Joseph Salisbury
Thank you for building the test kernels! :)
On my setup, I can confirm the kernel of commit:
ff7c60c580d9722f820d85c9c58ca55ecc1ee7c4
is affected by the bug.
Jan
I think Joseph is trying to narrow down which modification to the newer kernels
that has actually caused the
Tim Richardson
In my case I have tested the AMD64 builds only. On the v3.8.x branch this bug
has appeared since v3.8.0-rc7, every AMD 64 kernel since that version is
affected, including v3.8.4 .
** Description changed:
1) The release of Ubuntu using
Ubuntu 12.10 AMD64.
Ubuntu 13.04
Tested with Linux kernel v3.8.5, problem remains.
Added Dragonfly USB DAC into the affected device list.
** Description changed:
1) The release of Ubuntu using
Ubuntu 12.10 AMD64.
Ubuntu 13.04 AMD64, daily build as new as 20130314.
2) The version of the package used
Tested with Linux kernel v3.9-rc4, problem remains.
** Description changed:
1) The release of Ubuntu using
Ubuntu 12.10 AMD64.
Ubuntu 13.04 AMD64, daily build as new as 20130314.
2) The version of the package used
linux-image-3.5.0-26-generic
Joseph Salisbury
I had tested v3.9-rc3 on 2013-03-21, it didn't fix the problem. (#22 comment)
v3.8.4, v 3.5.0.-27 did't fix the problem either.
The bug description have been constantly updated with new information I
discovered, too. Please have a look.
--
You received this bug notification
** Description changed:
1) The release of Ubuntu using
Ubuntu 12.10 AMD64.
Ubuntu 13.04 AMD64, daily build as new as 20130314.
2) The version of the package used
linux-image-3.5.0-26-generic
linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb
Joseph Salisbury
Yes, this bug didn't happen with v3.8.0-rc6 kernel, but it happened with every
new kernel release after that version. So far the newest version is v3.9-rc3
and it is also affected.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Tested on linux kernel 3.8.4, still not fixed.
Jan (ya-me)
From the change log of the recent Linux Kernel releases, It seems that the
developers are busy tinkering with the kernel to add new features to the USB
related modules. When those new features are fully implemented, hopefully they
Added:
Using CLI command grep device.buffering to get the buffer from the devices,
those affected kernels are reporting back a different number to the unaffected
devices. The choppy noise is very similar to the situation when buffer size is
not correctly set.
Added:
Affected Devices:
Arce
Jan (ya-me)
If you are affected by this issue, please help by selecting Yes, it affects
me by clicking the yellow pencil icon right side of the green text This bug
affects X people. Does this bug affect you?. It can be found somewhere below
the title. This will increase the heat of the bug and
Tested on linux kernel 3.9.0-rc3, still not fixed.
** Summary changed:
- USB Audio Codec jerky playback (crackling noise)
+ USB Audio Codec choppy playback
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Tested on linux kernel 3.8.3, still not working.
Tested on one more asynchronous USB DAC, and one other synchronous USB DAC,
reproduced exactly the same issue in the description.
** Description changed:
1) The release of Ubuntu using
Ubuntu 12.10 AMD64.
Ubuntu 13.04 AMD64, daily build as
USB Audio Streaming Controller on affected devices:
Texas Instrument TAS1020
http://www.ti.com/product/tas1020
** Description changed:
1) The release of Ubuntu using
Ubuntu 12.10 AMD64.
Ubuntu 13.04 AMD64, daily build as new as 20130314.
2) The version of the package used
Audio DAC on affected devices:
Texas Instruments PCM1742
http://www.ti.com/product/pcm1742
** Description changed:
1) The release of Ubuntu using
Ubuntu 12.10 AMD64.
Ubuntu 13.04 AMD64, daily build as new as 20130314.
2) The version of the package used
linux-image-3.5.0-26-generic
** Description changed:
1) The release of Ubuntu using
Ubuntu 12.10 AMD64.
Ubuntu 13.04 AMD64, daily build as new as 20130314.
2) The version of the package used
linux-image-3.5.0-26-generic
linux-image-3.5.7-03050706-generic_3.5.7-03050706.201302221435_amd64.deb
ALSA: usb-audio: fix invalid length check for RME and other UAC 2 devices
This commit might had caused some USB DAC to produce jerky audio output. All
kernel versions after linux kernel 3.5.0-26 won't work with my asychronous USB
DAC, my synchronous USB DAC works fine with the new version,
** Summary changed:
- Asynchronous USB DAC cracking sound in Linux kernel 3.5.0.26
+ Asynchronous USB DAC cracking sound in Linux kernel 3.5.0.26 and later
** Description changed:
1) The release of Ubuntu using
- Ubuntu 12.10 64-bit.
+ Ubuntu 12.10 AMD64.
+ Ubuntu 13.04 AMD64, daily build as
** Description changed:
1) The release of Ubuntu using
Ubuntu 12.10 AMD64.
Ubuntu 13.04 AMD64, daily build as of 20130314.
2) The version of the package used
linux-image-3.5.0-26-generic and later.
3) What you expected to happen
When using a USB DAC to play audio, the audio
I've finished the test on all available kernels. kernel-bug-exists-
upstream has been added to the tags, the bug description has also been
updated according to my test result. Good luck on fixing the bug!
** Description changed:
1) The release of Ubuntu using
Ubuntu 12.10 AMD64.
- Ubuntu
** Tags added: raring
** Tags added: audio usb
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1136110
Title:
USB Audio Codec jerky playback (crackling noise)
To manage notifications about this bug
** Tags added: kernel-bug usb-audio
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1136110
Title:
USB Audio Codec jerky playback (crackling noise)
To manage notifications about this bug go to:
I've singled out one modification that might be responsible for this
issue:
* ALSA: usb-audio: fix invalid length check for RME and other UAC 2
devices
- LP: #1119885
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
The fix might cause Asynchronous USB DAC to produce cracking sound in Linux
kernel 3.5.0.26.
#1136110
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1119885
Title:
Quantal update to 3.5.7.5
apport information
** Tags added: apport-collected package-from-proposed running-unity
third-party-packages
** Description changed:
1) The release of Ubuntu using
Ubuntu 12.10 64-bit.
2) The version of the package used
linux-image-3.5.0-26-generic
3) What you expected to happen
apport information
** Attachment added: BootDmesg.txt
https://bugs.launchpad.net/bugs/1136110/+attachment/3553685/+files/BootDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1136110
apport information
** Attachment added: CurrentDmesg.txt
https://bugs.launchpad.net/bugs/1136110/+attachment/3553686/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1136110
1 - 100 of 172 matches
Mail list logo
