Seems to affect me in a persistent live system running Ubuntu Desktop
Lunar daily iso file in Dell Precision M4800
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gjs in Ubuntu.
https://bugs.launchpad.net/bugs/1796649
Title:
@ Jeremy Bicha,
Is "Won't fix" for Onboard in Wayland still the policy, or is there some
development?
What about the current (in Ubuntu 22.04.1 LTS) screen keyboard that we
get via gnome-control-center? Is it still based on Caribou? Are there
features from Onboard in it? (It looks like Caribou
I tested the current daily Ubuntu Desktop Focal iso file (with a
persistent live system), and fractional scaling works with a 4k monitor,
where is used to fail. So I see a big improvement :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Your observation is correct and I have seen it too. RAM is bigger and
processes are buffering in RAM more aggressively in recent computers
with recent versions of linux operating systems. Be aware that also
Windows uses this feature and for that reason you must 'remove the USB
drive safely' or
So I will move the focus to the following bug report (here at
Launchpad),
'GParted does not work in GNOME on Wayland'
https://bugs.launchpad.net/ubuntu-gnome/+bug/1652282
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in
After running the following command
xhost +si:localuser:root
sudo -H gparted
and
pkexec gparted
work, but
gksudo gparted
is still not working.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server in Ubuntu.
** Description changed:
This bug appears, when I try to run GUI application programs with
elevated permissions using sudo -H and gksudo in an installed Ubuntu
Artful system on Wayland.
I discovered it while testing mkusb: version 12 alias mkusb-dus works
because the GUI is running as
tester@tester-SATELLITE-PRO-C850-19W:~$ apt-cache policy xwayland
xwayland:
Installed: 2:1.19.3-1ubuntu2
Candidate: 2:1.19.3-1ubuntu2
Version table:
*** 2:1.19.3-1ubuntu2 500
500 http://se.archive.ubuntu.com/ubuntu artful/main amd64 Packages
100 /var/lib/dpkg/status
--
Public bug reported:
This bug appears, when I try to run GUI application programs with
elevated permissions using sudo -H and gksudo in an installed Ubuntu
Artful system on Wayland.
I discovered it while testing mkusb: version 12 alias mkusb-dus works
because the GUI is running as the regular
bump
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1571255
Title:
gnome-disks truncates a huge image when restoring to a drive from xz-
compressed image file
Status in
This bug seems to affect Lubuntu Zesty alpha 2. It affects all Lubuntu
test cases.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1656399
Title:
Unable to unlock session after
This bug seems to affect Lubuntu Alternate too, according to the test
case
'Alternate Install (Encryption) in Lubuntu Alternate i386 in Zesty
Daily'
http://iso.qa.ubuntu.com/qatracker/milestones/371/builds/141408/testcases/1439/results
--
You received this bug notification because you are a
It works for me with the Lubuntu amd86 Yakkety release candidate in my
computer too.
Maybe the problem depends on the hardware for example the graphics chip,
or maybe there is a time-out limit, so that slow computers will not show
the graphical bells and whistles.
--
You received this bug
This bug does not affect the Lubuntu i386 Yakkety release candidate in
my computer,
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
I'll check the corresponding amd64 version ...
--
You received this bug notification because you are a member of Desktop
Packages, which
This bug is valid directly after installation of Lubuntu i386 beta 2
(dated 2016 09 21), but after update & upgrade (2016-09-23 15:17:21 UTC
) it is squashed, so in the next released daily version gnome-software
should work.
--
You received this bug notification because you are a member of
added 'Yakkety' to the previous post: Lubuntu Yakkety i386 beta 2 (beta
testing)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1606238
Title:
gnome-software won't open
*** This bug is a duplicate of bug 1616400 ***
https://bugs.launchpad.net/bugs/1616400
> Actually it went away with the fix of the master bug of the networking
for beta 1.
That's great :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is
*** This bug is a duplicate of bug 1616400 ***
https://bugs.launchpad.net/bugs/1616400
Hi Brendan,
Is this really a a duplicate of bug #1616400? I guess you can check, if
the bug has been squashed. If it is still alive, it is a separate bug.
I suspect it is still alive, but you wrote the
I agree with peerus (comment #139). I suspect that this bug is related
to another program package, but I do not know enough to be able to
suggest which package.
I have problems with graphics with a non-intel graphics chip. It turns
pale (almost completely greyed out), and after switching to
It might be the same bug, but I'm not sure. It is strange, that it only
affects systems made from Lubuntu Xenial Alternate, not from Lubuntu
Xenial desktop.
So I created the bug report
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-
intel/+bug/1572640
Maybe it will be considered a
Public bug reported:
When installed from the *Lubuntu alternate* ISO files, the default
systems are affected by this bug:
After time-out the screensaver kicks in and the user is locked out. At
the unlock screen the cursor is visible, but after unlock the cursor is
invisible. This bug does not
I have this issue or very similar in two laptops, a Toshiba and a Lenovo
http://www.toshiba.se/laptops/satellite-pro/c850/satellite-pro-c850-19w/
https://shop.lenovo.com/ISS_Static/ww/wci/products/us/laptop/thinkpad/x-series
/x131e-intel/X131e-Datasheet-Intel.pdf
when running systems installed
** Description changed:
This bug affects Lubuntu Xenial i386 but not amd64.
gnome-disks works when restoring from a 300 MB image compressed with xz.
But it fails when trying to 'restore' from a 12 GB image compressed with
- xz. This extraction works with mkusb, which uses dd under the
This bug affects Lubuntu Xenial i386 but not amd64.
** Description changed:
+ This bug affects Lubuntu Xenial i386 but not amd64.
+
gnome-disks works when restoring from a 300 MB image compressed with xz.
But it fails when trying to 'restore' from a 12 GB image compressed with
xz. This
** Description changed:
gnome-disks works when restoring from a 300 MB image compressed with xz.
But it fails when trying to 'restore' from a 12 GB image compressed with
xz. This extraction works with mkusb, which uses dd under the hood. The
process is described at
Public bug reported:
gnome-disks works when restoring from a 300 MB image compressed with xz.
But it fails when trying to 'restore' from a 12 GB image compressed with
xz. This extraction works with mkusb, which uses dd under the hood. The
process is described at
Second workaround: gnome-disks works if wiping the whole device (in the
format menu) before creating the partition and file system. But this is
very slow.
It is enough to wipe the first megabyte (actually mibibyte 1024x1024
bytes) which takes less than 1 second compared to 6-16 minutes to wipe
Marc D. wrote, 'The user still needs to be in the admin group.' I did
not realize this. It keeps the least responsible people away from using
it, so maybe this is enough :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Workarounds: gparted and mkusb manage to do what gnome-disks cannot do
(I have tested in the same system).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/1547340
Title:
*** This bug is a duplicate of bug 1547340 ***
https://bugs.launchpad.net/bugs/1547340
(Yes, it seems to be the same bug, now that the other bug is public.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in
*** This bug is a duplicate of bug 1547340 ***
https://bugs.launchpad.net/bugs/1547340
It is not possible for me to view other people's private bugs, so I
cannot determine if the duplicate status is right or wrong!
-o-
Anyway, gparted and mkusb manage to do what gnome-disks cannot do (I
Public bug reported:
This is an automatically prompted bug, but it is related to bug
#1549603, usb-creator-gtk.
ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gnome-disk-utility 3.18.3.1-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-17.33-generic 4.4.6
Uname: Linux 4.4.0-17-generic i686
I have updated/upgraded a few times (during 4 days), and the problem
persists, when I use the proprietary nvidia 304 driver (but things work
with the free nouveau driver).
Today I tried nvidia-current --> 304
and also nvidia-current-updates (which was worse, I had to hard reboot,
when trying to
I removed the nvidia 304.131 driver from my installed system. After
rebooting I'm prompted for a new bug directly at log in. It seems to
affect xorg-server, but the free desktop graphics driver (nouveau) seems
to work with my nvidia Geforce GT 430 card.
I tried mkusb twice (making persistent live
I installed mkusb into a clean current Lubuntu Xenial i386 live system.
It seems to work well - also the zenity windows. The differences
compared my installed system are
- Live versus Installed
- free versus nvidia proprietary driver (version 304.131)
- clean versus contains several packages and
** Attachment added: "console-dialogue_including-errors.txt"
https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1562607/+attachment/4614068/+files/console-dialogue_including-errors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
** Attachment added: "console-dialogue_including-errors.txt"
https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1562607/+attachment/4614069/+files/console-dialogue_including-errors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
Public bug reported:
Bug #1562591 continues here:
After today's update/dist-upgrade zenity windows are flaky. Sometimes
they are empty, and the next attempt they work again. Finally I
rebooted, and then I was prompted to write this bug report.
I made a second update/dist-upgrade before trying
** Attachment added: "update_dist-upgrade.txt"
https://bugs.launchpad.net/ubuntu/+source/zenity/+bug/1562607/+attachment/4614070/+files/update_dist-upgrade.txt
** Attachment removed: "console-dialogue_including-errors.txt"
I hope it is still possible to build the alsa driver into a whole kernel
?!
Would it be an alternative that I install the same distro as you are
using, and that you compile kernels with the properties that you want me
to test. and upload its files for me to download and install?
Then I can run
I can continue to try helping to improve the driver for the Aureal card
(although there are no symptoms in this computer now). But as I said
before - I need a lot of help, this task is far beyond what I have been
doing before.
*An alternative is that you upload kernels that I can test*
If you
utils/setup-alsa-kernel -c ../../sound
worked without complaints :-)
Please tell me *the whole command line* that should end like that!
--with-debug=full
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
Reply from Tiwai:
The build with alsa-driver external tree is no longer supported.
You need to build the kernel module directly.
Takashi
-o-
And as usual - I need detailed help.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
'Usually the reason fail to compile are those patch in acore directory
are out dated and you need to report to alsa-devel mailng list
https://git.kernel.org/cgit/linux/kernel/git/tiwai/alsa-driver-
build.git/tree/alsa/acore?h=build'
Can you see anything wrong, or should I report to the
I think the subdirectories are correct, but still, something is missing.
alias l='ls -l --group-directories-first'
[100] olle@xenial32 ~/tiwai/alsa-driver-build/alsa $ l
totalt 324
drwxrwxr-x 5 olle olle 4096 mar 16 11:23 acore
drwxrwxr-x 27 olle olle 4096 mar 16 11:50 alsa-kernel
Since March 15 (during two full days and part of a third day) I am no
longer spammed by prompts to report kernel oops like I used to be at
login after reboot and shutdown + cold boot. There has been no
notification of a kernel oops at all. I have rebooted and still no such
prompts. I have also
I installed those 3 packages and ran gitcompile:
$ ./gitcompile --enable-dynamic-minors --with-oss=no --with-cards=au8820
,hda-intel --with-sequencer=yes --with-debug=full
See the whole output in the attached file.
It worked better, but there are still errors.
make[2]: Går till katalogen
olle@xenial32 ~/tiwai/alsa-driver-build/alsa $ ./gitcompile
--enable-dynamic-minors --with-oss=no --with-cards=au8820,hda-intel
--with-sequencer=yes make: Inget behöver göras för ”all-deps”.
./gitcompile: rad 59: aclocal: kommandot finns inte
[1] olle@xenial32 ~/tiwai/alsa-driver-build/alsa $
Following comment #71 caused the following error:
olle@xenial32 ~/linux $ cd ..
olle@xenial32 ~ $ mkdir tiwai; cd tiwai
olle@xenial32 ~/tiwai $ git clone git://github.com/tiwai/alsa-driver-build.git
Klonar till "alsa-driver-build"...
remote: Counting objects: 159995, done.
remote: Total 159995
I don't understand the talk about another computer in the link from
comment #71. Does it apply for me?
And the directory structure does not match the instructions. I'm lost
again.
Trying to follow comment #112 caused the following error:
olle@xenial32 ~/linux $ cd ~/tiwai/alsa-driver-build/
Edit: Has some change already *trickled* down? :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1551041
Title:
snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384,
I upgraded to a new kernel
$ uname -a
Linux xenial32 4.4.0-12-generic #28-Ubuntu SMP Wed Mar 9 00:33:13 UTC 2016 i686
i686 i686 GNU/Linux
and I am no longer spammed by prompts to report kernel oops. I rebooted
and still no such prompts.
- The sound is working as usual. Has some change already
Is this part of the instruction
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
wrong alias only a template? In that case, should it be
git clone
git://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git/commit/sound/core?id=48d882978eb0a15547093b4542a82b5c22548041
I need detailed instructions as terminal window command lines
I think the only way I can manage this task is that I get detailed
instructions as terminal window command lines (or a shellscript file).
Otherwise I will be lost. You know how to do things, and you give
instructions on a high level,
Is this part of the instruction
git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
wrong alias only a template? In that case, should it be
git://git.kernel.org/cgit/linux/kernel/git/tiwai/sound.git
or something else?
--
You received this bug notification because you
I installed Lubuntu 15.10 and tried according to the same method
https://wiki.ubuntu.com/Kernel/KernelBisection#Testing_a_newly_released_patch_from_upstream
but it did not work at all.
This is impossible for me. I do not understand the instructions. It is
not cherry-picking, it is sour grapes
Or should I try in another version of Ubuntu, for example 14.04.1 LTS?
But then I won't get those spammed messages anyway.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1551041
OK. A small step forward. It seems that I have compiled, but there are
errors:
--
scripts/extract-cert.c:21:25: fatal error: openssl/bio.h: Filen eller katalogen
finns inte
compilation terminated.
scripts/sign-file.c:23:30: fatal error: openssl/opensslv.h: Filen eller
katalogen finns inte
--
Looking more at the git command line, it seems the problem is a separate
'patch' command.
--
git config --global user.email "y...@example.com" && git config --global
user.name "Your Name" && cd $HOME && git clone
git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git && patch
>> patching file /home/olle/linux/drivers/acpi/video.c
>> Hunk #1 FAILED at 432.
>> 1 out of 1 hunk FAILED -- saving rejects to file
>> /home/olle/linux/drivers/acpi/video.c.rej
>
> See the file name here: you must be patching a totally different file.
> Or it's about a different patch.
>
> If
The file /home/olle/linux/drivers/acpi/video.c is missing.
- Is it because of the failed git command?
- Or does the git command fail because it was missing when the file
should have been there (put there by previous git commands)?
- Must I install source code before running the git command? How
I tried in the system which is suffering from this bug (Lubuntu Xenial
with the kernel
Linux xenial32 4.4.0-11-generic #26-Ubuntu SMP Sat Mar 5 14:22:05 UTC
2016 i686
and I failed with the git command. I replied directly to tiwai, and post
a copy here.
*Maybe you can see what is wrong*
-
I understand that tiwai's first fix only removes the symptoms, not the
original problem. I thought that I can live with that.
The problem is that I do not understand how to implement tiwai's second
fix, and he says that he doesn't know how to do it in Ubuntu. Now you
say I have to do it at the
'Sound.git is unstable and not gauarnteed to compile at any time
The safest way is to compile debug kernel/driver at stable ubuntu release'
Do you mean that I should install a system of Ubuntu 14.04.1 LTS or
Ubuntu 14.04.4 LTS, *dedicated for this task*, and use that for
compiling souund.git?
Do you suggest that I try to build the alsa driver with debug now?
Maybe I should I make a dedicated system alongside the system I am using
for general testing.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
$ dmesg | grep -i "au88"
[ 12.425799] snd_au8820 :01:04.0: init started
[ 13.157353] snd_au8820 :01:04.0: init done.
[ 13.192583] gameport gameport0: AU88x0 Gameport is
pci:01:04.0/gameport0, speed 1087kHz
[ 2357.843401] snd_au8820 :01:04.0: BUG: , pos = 16385, buffer
'Do the number of BUG messsges in system log still 2 frames larger than
buffer size'
I don't understand how to do this or check this. Please explain!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
'Can you change
periods from 4 to 16
and period_size from 1024 to 256
post the output of pcm_avail.c'
Done. See the attached file.
** Attachment added: "pcm_avail_periods-16_periodsize-256.out"
fixed typing error: please *tell* me what to do
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1551041
Title:
snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384,
Raymond, do you need anything from me now? In that case, please me what
to do?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1551041
Title:
snd_au8820 :01:04.0: BUG: , pos =
'Can you post the output of pcm_avail.c when using rate 44100 Hz instead
of 48000Hz?
print the time at the same time to check whether the ptr is monotically
increasing as expected rate'
I attach a file with the specified rate. I don't know/remember C well
enough, so I need your help to print the
Yes, I understand.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1551041
Title:
snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384,
period size = 1024
Status in
Raymond,
I can re-phrase the question like this:
Do you want to fix the alsa-driver to eliminate the problem with the
pointer? In that case I am willing to help testing it :-)
Otherwise I can wait for the fix, where the string 'BUG' is replaced
with 'XRUN'
- "BUG:
I have been away from the keyboard for a few hours. It is nice weather,
so nice outdoors here today :-)
Would you say it is meaningful to build a new alsa driver (even if it is
means installing many packages?
If that is the case, should I do it in a separate system (to avoid
damaging the current
I ran pcm_avail after changing to device #1
/* const char* device = "hw:0"; */
const char* device = "hw:1";
and re-compiling.
I redirected the error output to the attached file.
** Attachment added: "pcm_avail.out"
So using the ALSA tools, it is possible to have a better control of the
audio, it provides a more advanced mixer. Maybe that is why it is also
more difficult to learn :-)
-o-
I will scan the previous few comments and try to perform some tasks,
that I might have overlooked. Please remind me, if
I don't understand how to use comment #60.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1551041
Title:
snd_au8820 :01:04.0: BUG: , pos = 16386, buffer size = 16384,
Den 2016-03-11 kl. 02:22, skrev Raymond:
> There will be volume slider(hardware per stream volume control) for each
> application if the application use hw instead of pulse
>
> pavucontrol provide sofware per stream volume control
>
Both would be OK for me. But I have learned to use pavucontrol.
Raymond,
The committer, Takashi Iwai, decided to help us. Can you use this patch
(and help me test it) :-)
Nio
-
OK, I see why this bogus report reappears again. The message tag was
reverted back after some commit for correctness.
Now I rephrased the text again so that it won't hit some
I have written directly to the author and committer, but also made a
comment in their old bug report.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1305480/comments/13
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver
Thank you very much for investigating this issue, Raymond :-)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1551041
Title:
snd_au8820 :01:04.0: BUG: , pos = 16386, buffer
I see: 'The kerneloops-daemon scans dmesg for common crash signatures,
among which is 'BUG:'. The message emitted by the PCM library is really
a warning, so the most expedient thing to do seems to be to change the
string.'
Yes, this might be the problem :-)
Can you help getting rid of it (how to
No, I changed it according to your tips and could compile without
complaints.
/* #include */
#include
$ l
totalt 24
-rwxrwxr-x 1 olle olle39 mar 10 15:06 maker
-rwxrwxr-x 1 olle olle 13240 mar 10 16:02 pcm_avail
-rw-rw-r-- 1 olle olle 3703 mar 10 16:02 pcm_avail.c
olle@xenial32
'Are you the kernel oops is related to au8820 since it just flooding the
system log with BUGS message but no seg fault or dump
it is strange that your bug report did not have pulselist or pulseaudio
log'
No I'm not sure at all. It says 'snd_au8820' in the automatically
created bug report, but I
It should be there:
sudo apt-get install libasound2-dev
Läser paketlistor… Färdig
Bygger beroendeträd
Läser tillståndsinformation… Färdig
libasound2-dev is already the newest version (1.1.0-0ubuntu1).
Följande paket har installerats automatiskt och är inte längre nödvändiga:
It complains:
pcm_avail.c:5:23: fatal error: asoundlib.h: no such file
I guess I need some library?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1551041
Title:
snd_au8820
'You have to recompile alsa driver by adding
if (current_ptr > runtime->buffer_size)
current_ptr = runtime->buffer_size;'
--
'http://mailman.alsa-project.org/pipermail/alsa-devel/2014-September/081501.html
you can try Alexander's pcm_avail.c and post the output using your
au8820
It is
I added the output for the command with sudo to get the capabilities:
$ sudo lspci - |grep -A16 Multimedia
01:04.0 Multimedia audio controller: Aureal Semiconductor Vortex 1 (rev 02)
Subsystem: Voyetra Technologies Montego
Physical Slot: 1
Control: I/O+ Mem+ BusMaster+
I have not rebooted after my previous comments (and the test with
aplay).
Now I can give you better feedback :-)
olle@xenial32 ~ $ dmesg|wc -c
64123
olle@xenial32 ~ $ dmesg|grep -i au88
[ 12.021036] snd_au8820 :01:04.0: init started
[ 12.777390] snd_au8820 :01:04.0: init done.
[
I see. Will you upload a compiled version of it for testing?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1551041
Title:
snd_au8820 :01:04.0: BUG: , pos = 16386, buffer
Please bear with me. It was long ago that I was programming compiled
languages. And it was application programs simulating physical
processes. I was never near the kernel of any operating system.
I think you have to explain in a very detailed way, you you want me to
do things from source code ;-)
No output to /var/log/dmesg
I am listening to a broadcasting track at the same time. A minute after
this aplay test was finished, I had an new prompt to file a bug report
about a kernel oops. But there is still nothing in /var/log/dmesg
--
$ while true; do aplay -D hw:CARD=au8820
Please tell me which log file I should look into (the file name of it)!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1551041
Title:
snd_au8820 :01:04.0: BUG: , pos = 16386,
Directly at login after reboot I had many prompts to send a bug report
about kernel oops. I tried to count them. think this report is
responding to the 26th prompt to send a bug report, and a few seconds
later there was one more prompt to send a bug report.
The above event created the bug report
Correction:
2. The newer Trusty system with the 3.13.0-79-generic kernel
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1551041
Title:
snd_au8820 :01:04.0: BUG: , pos =
'How often do the message appear in system log? (BUG 16.04 or XRUN
before 14.04)
it mean the value return is larger than buffer size or the interrupt is
not handled properly'
Please tell me which log file I should look into, and which string to
look for! Maybe I can use grep.
--
'You can use hwmixvolume to change the playback volume of each
application which use hw device of au8820'
I use pavucontrol, and yes, I can change the playback volume also of
each individual channel (left and right).
Do you want me to test something else?
--
You received this bug notification
Last night I shut down the computer. This morning, when I cold booted it
and logged in, I was spammed with around ten prompts to file bug reports
about kernel oops (at once, not after starting any application program).
But still the audio works like it should (playing video and running your
test
aplay ./test/test0/'hello world.wav'
and
speaker-test -c2 -t wav
work correctly (through the Aureal device) without your explicit
specification.
'Front left' 'Front right' ... is put out from the correct loudspeakers
:-)
They work without 'complaints'.
But it seems that when I have the
There is a damaged onboard audio device. There is also an audio device
built into the graphics card, but I don't use hdmi.
This is the reason why I use the old Aureal Vortex 1 card (au 8820).
Could the damaged onboard audio device cause some confusion?
--
You received this bug notification
1 - 100 of 163 matches
Mail list logo
