Please refer to my report in upstream:
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755326
Title:
Periodic glitch in sound
Please refer to my report in upstream:
http://mailman.alsa-project.org/pipermail/alsa-devel/2016-May/107715.html
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1755326
Title:
Periodic glitch in sound
: pulseaudio (Ubuntu)
Status: Triaged => Fix Released
** Changed in: pulseaudio (Ubuntu)
Assignee: (unassigned) => Takashi Sakamoto (mocchi)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Changed in: libffado (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170949
Title:
AudioFirePre8, MIDI data from hardware port is invalid when MIDI
play
Public bug reported:
The snd_seq_free_event() has been no meaning since 2000. See this commit:
New light-weight event handling
http://git.alsa-project.org/?p=alsa-lib.git;a=commitdiff;h=a7f3ff4a4f3531c98a7875d9789b49a0dc56ab36
Currently snd_seq_event_input() give a pointer to a cell of inner-buff
Hi David,
> The ID_MODEL_FROM_DATABASE is probably set (for the firewire controller) by
> udev/systemd,
> see the "hwdb" directory of systemd sources.
Exactly. I've already realized it and it require discussion between
ALSA, PulseAudio and systemd about which part of userspace has these
informat
FYI, a part of my work is already included in Linux 3.16 or later. In
this bug, the reporter uses my breeding-edge in github.com, thus you may
have an idea that this is due to out-of-tree kernel modules. But you can
actually see the same issue on Ubuntu utopic.
http://packages.ubuntu.com/utopic/am
Hi,
I'm an authour of this kernel module (snd-bebob), I think you already
know.
I'll explain about the naming rule for ALSA FireWire drivers.
struct snd_ctl_card_info.driver[16]
=> BeBoB/Fireworks/OXFW/Dice/Digi00x etc...
struct snd_ctl_card_info.name[32]
=> 'model name' from config ROM,
Hi,
I'm an upstream developer. I applied solutions for this issue at
r2451/2452.
http://subversion.ffado.org/changeset/2451
http://subversion.ffado.org/changeset/2452
Would you test current upstream?
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
Hi,
I'm an upstream developer. I applied a solution for this issue at r2451 and
r2452.
http://subversion.ffado.org/changeset/2451
http://subversion.ffado.org/changeset/2452
Would you please test the latest sources?
Thanks
--
You received this bug notification because you are a member of Ubunt
** Attachment added: "result_96000_2.log"
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649078/+files/result_96000_2.log
** Description changed:
I confirm this bug with my AudioFirePre8.
I generate this bug in the way below:
1.Prepare reliable MIDI capt
** Attachment added: "result_96000_1.log"
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649077/+files/result_96000_1.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs
** Attachment added: "result_88200.log"
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649076/+files/result_88200.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/117
** Attachment added: "result_48000.log"
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649075/+files/result_48000.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/117
** Attachment added: "result_44100.log"
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649074/+files/result_44100.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/117
Public bug reported:
I confirm this bug with my AudioFirePre8.
I generate this bug in the way below:
1.Prepare reliable MIDI capture device. I utilize E-MU 0404 USB with
snd-usb-audio.ko (ALSA).
2.Connect hardware MIDI-out of AudioFirePre8 and hardware MIDI-in port of E-MU
0404 USB
3.Prepare re
** Attachment added: "control.mid"
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649073/+files/control.mid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170949
Titl
** Attachment added: "connection.png"
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649072/+files/connection.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1170949
Public bug reported:
I tested "v4l2loopback-dkms", "ndiswrapper-dkms" package and my personal
DKMS package. The build process always failed.
== for v4l2loopback ==
$ sudo dkms build -m v4l2loopback -v 0.6.1
Kernel preparation unnecessary for this kernel. Skipping...
Building module:
cleaning b
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1022196
Title:
glibc detected *** lmms: double free or corruption (!prev)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubunt
Public bug reported:
I can see this under both i686/amd64
How to reproduce:
1. run lmms in terminal
2. shutdown lmms
3. then we can see below
*** glibc detected *** lmms: double free or corruption (!prev):
0x02906af0 ***
=== Backtrace: =
/lib/x86_64-linux-gnu/libc.so.6(+0x7e
22 Mar 2012 this package is updated and its configugration seems to be changed
according to its concept.
https://launchpad.net/ubuntu/precise/+source/linux-lowlatency/3.2.0-20.28
I should have commited this bug into linux-lowlatency package instead of this.
https://bugs.launchpad.net/ubuntu/+sour
Public bug reported:
How to reproduce this bug:
$ sudo apt-get install linux-image-3.2.0-18-generic-pae
linux-image-3.2.0-18-lowlatency-pae
$ diff /boot/config-3.2.0-18*
3c3
< # Linux/i386 3.2.0-18-generic-pae Kernel Configuration
---
> # Linux/i386 3.2.0-18-lowlatency-pae Kernel Configuration
7
Oh, unlinked...
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/832137
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778887
Title:
Compile error with "@CONFIG_SND_KERNELSRC@/include/linux
You can refer to my in-depth report about this at # 832137.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778887
Title:
Compile error with "@CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No
such
** Summary changed:
- [Oneiric] Need upgrading package from revision 1995 to fix jackd shutdown
problem
+ [Oneiric] Need to upgrade package with revision 1995 to fix jackd shutdown
problem
** Description changed:
How to reproduce:
1. run jackd with qjackctl or gladish
2. stop jackd
3.
Public bug reported:
How to reproduce:
1. run jackd with qjackctl or gladish
2. stop jackd
3. you can see jackd still exists in top or ps command
4. especially gladish can't open the other session
The current package is generated from revision 1985. This still causes
shutdown problem of jackd com
Maarten,
Yes. You're right. The two files are generated by running configure script from
templates which you mentioned.
This week I review the patch and find the bug. It's in
distinguish_kernel_makefile_and_source_dirs.patch in line 45 to 55.
+echo "\$(warning KBUILD_SRC=\$(KBUILD_SRC))" > "$di
Works well. Great!!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/835166
Title:
[Oneiric] Could not launch gladish with segmentation fault.
To manage notifications about this bug go to:
https://bug
** Description changed:
You can see this bug by:
1. $ sudo apr-get install gnome-color-manager icc-profiles;
+ (Optionally installing krita-data.)
2. $ gcm-viewer;
3. Select an icc color profile and click a tab named as "CIE1931".
4. You can never see the garmut.
I cannot find some
Public bug reported:
You can see this bug by:
1. $ sudo apr-get install gnome-color-manager icc-profiles;
(Optionally installing krita-data.)
2. $ gcm-viewer;
3. Select an icc color profile and click a tab named as "CIE1931".
4. You can never see the garmut.
I cannot find some specific informatio
** Attachment added: "coredump"
https://bugs.launchpad.net/ubuntu/+source/ladish/+bug/835166/+attachment/2320755/+files/coredump
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/835166
Title:
[Onei
Public bug reported:
I cannot launch gladish with Bug #835166 but in my terminal I can see a
line which mean try to start something related to a2jmidid.
$ gladish;
Loading glade from /usr/share/ladish/gladish.ui
JACK appeared
JACK started
a2j_proxy_is_started: a2j::is_started() failed.
...
I did
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/835168
Title:
[Oneiric] gladish needs dependency on a2jmidid.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/la
** Summary changed:
- [Oneiric] Could not launch with segmentation fault.
+ [Oneiric] Could not launch gladish with segmentation fault.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/835166
Title:
[
Public bug reported:
You can see this bug by:
1. launch jackd2
2. run "gladish"
3. Segmentation fault
$ gladish;
Loading glade from /usr/share/ladish/gladish.ui
JACK appeared
JACK started
Initial studio appear
refresh_internal() called
refresh_internal() called
canvas::clear()
canvas::client_appe
** Description changed:
This source cannot be used with module-assistant
because this source includes some bugs causes compiling error.
You can see this error in the process below.
1. $ sudo apt-get install module-assistant;
2. $ sudo module-assistant prepare;
3. $ sudo module-assis
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/832137
Title:
Need to fix bugs causes compiling error. One is related to Open Sound
System Emuration. The other is caused by modification when creating
Public bug reported:
This source cannot be used with module-assistant
because this source includes some bugs causes compiling error.
You can see this error in the process below.
1. $ sudo apt-get install module-assistant;
2. $ sudo module-assistant prepare;
3. $ sudo module-assistant update;
4. $
** Description changed:
I realized the current package from Ubuntu repository cannot deal with
firewire or v4l-capable devices because of a lack of dependency to
- libmjpegtools-dev. Then the build firm omit this function in its
+ libmjpegtools-dev. Then the build farm omit this function in it
** Summary changed:
- Need dependency into libmjpegtools-dev for enabling live firewire and
v4l-capable devices.
+ Need dependency on libmjpegtools-dev for enabling live firewire and
v4l-capable devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
On build logs of Natty and Oneiric, We can see a line "checking for
UNICAP... no".
i386, Natty
https://launchpadlibrarian.net/65067303/buildlog_ubuntu-natty-i386.lives_1.4.1-1ubuntu1_BUILDING.txt.gz
amd64, Natty
https://launchpadlibrarian.net/65068397/buildlog_ubuntu-natty-amd64.lives_1.4.1-1ubun
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/821791
Title:
Need dependency on libunicap2-dev for enabling live v4l-capable
devices.
To manage notifications about this bug go to:
https://bugs.laun
Public bug reported:
I realized the current package from Ubuntu repository cannot deal with
v4l-capable devices because of a lack of dependency to libunicap2-dev.
Then the build farm omit this function in its building process.
It's pretty sad that LiVES lost its live function in Ubuntu so I want
** Summary changed:
- For enabling live firewire and v4l-capable devices, need dependency into
libmjpegtools-dev.
+ Need dependency into libmjpegtools-dev for enabling live firewire and
v4l-capable devices.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
On build logs of Natty and Oneiric, We can see a line "checking for
MJPEGTOOLS... no".
i386, Natty
https://launchpadlibrarian.net/65067303/buildlog_ubuntu-natty-i386.lives_1.4.1-1ubuntu1_BUILDING.txt.gz
amd64, Natty
https://launchpadlibrarian.net/65068397/buildlog_ubuntu-natty-amd64.lives_1.4.1-1
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/820993
Title:
For enabling live firewire and v4l-capable devices, need dependency
into libmjpegtools-dev.
To manage notifications about this bug go to
Public bug reported:
I realized the current package from Ubuntu repository cannot deal with
firewire or v4l-capable devices because of a lack of dependency to
libmjpegtools-dev. Then the build firm omit this function in its
building process.
It's pretty sad that LiVES lost its live function in Ub
** Attachment added: "03_attach_events"
https://bugs.launchpad.net/ubuntu/+source/monobristol/+bug/820276/+attachment/2251490/+files/03_attach_events
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/8
** Patch added: "03_attach_events"
https://bugs.launchpad.net/bugs/820276/+attachment/2251463/+files/03_attach_events
** Patch removed: "03_attach_events"
https://bugs.launchpad.net/ubuntu/+source/monobristol/+bug/820276/+attachment/2251463/+files/03_attach_events
--
You received this bu
Public bug reported:
Moog Voyager Blue Ice, Prophet-52, Pro-1, YAMAHA DX cannot be called
from monoBristol. GUI has buttons for them but these buttons are not
attached with its event handler. My patch is just to add event handlers
to them.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: mo
Stefan,
Now I use 11.04 and get enough work.
Thanks,
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/649542
Title:
New firewire stack makes more FFADO XRUNs than old firewire stack.
To manage notifi
I would like to build ALSA 1.0.24.
I'm a member of Japanese LoCo and active to support users for sound
system in Japanese forum. This time a user post HDMI sound trouble and I
want to suggest to update ALSA kernel module to him or her. At first I
have a plan to utilize module-assistant script and
** Attachment added: "in case of VL Gothic"
https://bugs.launchpad.net/ubuntu/+bug/779194/+attachment/2122837/+files/VLGothic.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/779194
Title:
fixe
This bug also appears in the other Japanese monospace true type font. I
tested VL Gothic in "ttf-vlgothic" package. (See attached screenshot)
Each of full-width letters don't have the same width as half-width.
The Japanese glyphs of Takao and VL Gothic are not derived from the same
source. So thi
** Attachment added: "log for run make"
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/778887/+attachment/2117807/+files/make.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778887
T
** Attachment added: "configuration log with no options"
https://bugs.launchpad.net/bugs/778887/+attachment/2117797/+files/configure.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/778887
Title:
Public bug reported:
Natty's kernel is linux 2.6.38 and it includes ALSA 1.0.23 stuff. But
the latest version of ALSA is 1.0.24. We can get the latest ALSA kernel
module source by installing alsa-source package but get compile error
below,
In file included from /usr/src/modules/alsa-driver/includ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/776077
Title:
Rosegarden should have the dependency with awesfx.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mail
Public bug reported:
Binary package hint: rosegarden
Rosegarden can load sound font data into the sound device of
SoundBlaster then it utilize asfxload script which is included in
awesfx package. But there are no dependency to the package.
It's good for users that awesfx is installed with roseg
Hi,
Today I test the final test for Ubuntu Studio.
http://iso.qa.ubuntu.com/qatracker/build/ubuntustudio/all
And I faced the same problem...
Regards
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/769
I disabled the floppy controller at BIOS then the process proceeded as I
described above.
The bug #739774 you mentioned said it's fixed in the beginning of this
month but what I tested is a release candidate for Ubuntu Studio. I
think it should be fixed but I faced it.
Regards
--
You received t
Public bug reported:
Binary package hint: debian-installer
Hi,
CPU: Intel Core-i7 960
Motherboard: GA-X58-UD5 (X58 Express Chipset)
What happend:
I installed Ubuntu Studio 11.04, release candidate as of 2011-04-23.
http://iso.qa.ubuntu.com/qatracker/test/5606
And the installation process did
Thanks,
> The ubuntustudio-controls is under development, and a new version will
hopefully be available in the near future.
That's great. I'm looking forward to the next release!
https://wiki.ubuntu.com/UbuntuStudio/ControlsRedesign
--
You received this bug notification because you are a membe
This bug reports my kernel is -lowlatency from Alessio Igor Bogani's PPA
but I notice the lack of old firewire stack is the same in -generic
kernel.
Regards
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/703199
Title:
The role of UbuntuStudio Control may end in Natty.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/ma
Public bug reported:
Binary package hint: ubuntustudio-controls
I tested Ubuntu Studio Natty Alpha.
I understand the aim of this utility is,
0. Install /etc/udev/rules.d/60-raw1394.rules
1. To generate /dev/raw1394 device node, insert a line in /etc/modules.
2. To make the device node accessible
Now works fine in my maverick. Thanks and have a good year!
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/688847
Title:
[patch] startBristol process directly use sound device.
--
ubuntu-bugs maili
I tested it from maverick proposed and get unexpected behaviour. Then i
review my patch and found my mistake to the patch...
In advanced mode, the value in "adriver" item should be valuated but in
my patch "easyariver" is still valuated (at 21st line in previous
patch). This is due to my miss-oper
** Attachment added: "With this patch, we can see bristol process as ALSA
plug-in [bristol] in gnome-sound."
https://bugs.launchpad.net/ubuntu/+source/monobristol/+bug/688847/+attachment/1762382/+files/Screenshot.png
--
You received this bug notification because you are a member of Ubuntu
B
** Patch added: "Add "-audiodev default" option to "-audio alsa" option"
https://bugs.launchpad.net/bugs/688847/+attachment/1762380/+files/03_audiodev.patch
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
Public bug reported:
Binary package hint: monobristol
I think monobristol should open startBristol process with "-audiodev
default" option.
Current version of startBristol directly opens sound device (hw(0,0))
without this option, not via PulseAudio. With "-audiodev default"
option, startbristol
** Patch added: "diff patch for fix the command parameter"
https://bugs.launchpad.net/bugs/660627/+attachment/1692794/+files/02_fix-parameter.diff
** Description changed:
Binary package hint: monobristol
- In MainWindow.cs, this code is used to start bristrol process with some
paramet
Public bug reported:
Binary package hint: monobristol
In MainWindow.cs, this code is used to start bristrol process with some
parameters. In this case, one of parameter is "mini".
System.Diagnostics.Process.Start ("startBristol "+param+" -mini");
Then I got this error message below.
gvfs-open:
How is to use the PulseAudio's emuration module for Open Sound System?
Let you execute this.
$ padsp gtick
There is the same module in ALSA. You can use it by installing "alsa-oss"
package.
Then execute this.
$ aoss gtick
--
/dev/dsp on Ubuntu Studio is not enabled read/write for all, so GTick
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/649583/+attachment/1647359/+files/Dependencies.txt
** Description changed:
In Marveric Beta, I can connect to my MOTU 828 Mk2 with old firewire
stack (raw1394, ohci1394, ieee1394) and I got the sucess to work it with
Public bug reported:
In Marveric Beta, I can connect to my MOTU 828 Mk2 with old firewire
stack (raw1394, ohci1394, ieee1394) and I got the sucess to work it with
jackd2. But the sound is the worst. It's like buzzing and often nothing.
In Lucid, I can get better sound with this device. I know thi
*** This bug is a duplicate of bug 649542 ***
https://bugs.launchpad.net/bugs/649542
** This bug has been marked a duplicate of bug 649542
New firewire stack makes more FFADO XRUNs than old firewire stack.
* You can subscribe to bug 649542 by following this link:
https://bugs.launchpad.ne
** Attachment added: "Log for ffado-diag with old kernel stack"
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/649542/+attachment/1647191/+files/ffado-diag_old.log
--
New firewire stack makes more FFADO XRUNs than old firewire stack.
https://bugs.launchpad.net/bugs/649542
You receiv
** Attachment added: "Log for jackd with old kernel stack"
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/649542/+attachment/1647190/+files/qjackctl_log-old.log
--
New firewire stack makes more FFADO XRUNs than old firewire stack.
https://bugs.launchpad.net/bugs/649542
You received
** Attachment added: "Log for ffado-diag with new kernel stack"
https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/649542/+attachment/1647189/+files/ffado-diag_new.log
--
New firewire stack makes more FFADO XRUNs than old firewire stack.
https://bugs.launchpad.net/bugs/649542
You receiv
** Attachment added: "Log for jackd"
https://bugs.launchpad.net/bugs/649542/+attachment/1647187/+files/qjackctl_log-new.log
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/649542/+attachment/1647188/+files/Dependencies.txt
--
New firewire stack makes more FFADO X
Public bug reported:
I have a firewire audio device, M-Audio Firewire Solo. It works fine in
Lucid but not so good in Marveric because of much FFADO XRUNs in jackd2.
My IEEE 1394 chipset is below,
FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04)
$ dpkg -l | grep ffado
ii
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/644130/+attachment/1616838/+files/Dependencies.txt
** Attachment added: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/644130/+attachment/1616839/+files/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
https://
Public bug reported:
Binary package hint: jackd2
Ubuntu Studio 10.10 (i686)
I use M-Audio Firewire Solo and I get hashed sound with much XRUN.
The device works good in Lucid, jackd1 and ffado but worse in Marveric even if
I install jackd1 instead of jackd2.
The message from qjackctl below,
15
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/636159/+attachment/1572889/+files/Dependencies.txt
** Attachment added: "ProcMaps.txt"
https://bugs.launchpad.net/bugs/636159/+attachment/1572890/+files/ProcMaps.txt
** Attachment added: "ProcStatus.txt"
https://
Public bug reported:
Binary package hint: qsampler
$ qsampler
(2615) KSharedDataCache::Private::mapSharedMemory: Opening cache
"/var/tmp/kdecache-mocchi/icon-cache.kcache" page size is 4096
(2615) KSharedDataCache::Private::mapSharedMemory: Attached to cache,
determining if it must be initializ
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/50499843/Dependencies.txt
--
the wrong order of arguments in progress_callback function of plymouth script
https://bugs.launchpad.net/bugs/595599
You received this bug notification because you are a member of Ubuntu
Bugs, w
Public bug reported:
Binary package hint: ubuntustudio-look
http://www.freedesktop.org/wiki/Software/Plymouth/Scripts
Based on this document and ubuntu-logo plymouth theme, the order of
arguments in progress_callback function are progress at first and
secondly duration (time). But it's duration
The position in Option sub section is "Every persons is different". I use 1680
* 1050 so such a big number.
After installing xserver-xorg-input-wizardpen, we should get better number by
executing wizardpen-calibrate.
--
Waltop Tablet works but it indicates the absolute point only holding the bu
This tablet works fine if I installed xserver-xorg-input-wizardpen via
Martin Owen's PPA and modify /usr/lib/X11/xorg.conf.d/70-wizardpen.conf
as below.
Section "InputClass"
Identifier "wizardpen"
MatchIsTablet "on"
MatchDevicePath "/dev/input/event*"
Option "TopX" "100"
Option "Top
** Description changed:
Description: Ubuntu lucid (development branch)
Release: 10.04
lsusb
- Bus 004 Device 003: ID 172f:0031 Waltop International Corp.
+ Bus 004 Device 003: ID 172f:0031 Waltop International Corp.
By the update at Apr. 23, 2010, the Waltop tablet works. It' a gre
I reported this bug yesterday. Should I report it here?
Waltop Tablet works but it indicates the absolute point only holding the buttons
https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/569294
This tablet is rebranded and some company produces it at other name such
as G-Pen F610 fr
** Summary changed:
- Waltop Tablet works but it indicates the point holding the buttons
+ Waltop Tablet works but it indicates the absolute point only holding the
buttons
** Description changed:
+ Description: Ubuntu lucid (development branch)
+ Release: 10.04
+
lsusb
- Bus 004 Device 003:
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/45142712/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/45142713/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/45142714/Dependencies.txt
** A
Public bug reported:
lsusb
Bus 004 Device 003: ID 172f:0031 Waltop International Corp.
By the update at Apr. 23, 2010, the Waltop tablet works. It' a great
step against the Bug #392825 "WALTOP tablets not supported anymore"!
But it's not good. Just after the tablet plugged in, it works fine. Th
With reference to the threads on Ubuntu Community Forum, much people
with Ubuntu uses the same device.
http://ubuntuforums.org/showthread.php?t=1443829 Waltop tablet stop work in
Lucid
http://ubuntuforums.org/showthread.php?t=1261407 Tablet Buttons don't work
(Genius GPEN F610)
http://ubuntuf
At first, sudo modprobe wacom.ko
Next, connect the tablet device
Then, the log of Xorg is below,
(II) config/udev: Adding input device WALTOP International Corp. Slim Tablet
(/dev/input/mouse1)
(II) No input driver/identifier specified (ignoring)
(II) config/udev: Adding input device WALTOP Inter
** Attachment added: "BootDmesg.txt"
http://launchpadlibrarian.net/44611406/BootDmesg.txt
** Attachment added: "CurrentDmesg.txt"
http://launchpadlibrarian.net/44611407/CurrentDmesg.txt
** Attachment added: "Dependencies.txt"
http://launchpadlibrarian.net/44611408/Dependencies.txt
** A
Public bug reported:
1) Description: Ubuntu lucid (development branch)
Release:10.04
2) xserver-xorg-input-wacom:
Installed: 1:0.10.5-0ubuntu2
Candidate: 1:0.10.5-0ubuntu2
Version table:
*** 1:0.10.5-0ubuntu2 0
500 http://jp.archive.ubuntu.com/ubuntu/ lucid/main Packag
100 matches
Mail list logo
