[Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice
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 with Firewire and snd-dice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1755326] Re: Periodic glitch in sound with Firewire and snd-dice
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 with Firewire and snd-dice To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1755326/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381475] Re: Firewire sound card registered by the name of the fw controller
This is partly fixed at upstream of PulseAudio. And a new package has already released for Ubuntu 16.04. In detail, please refer to this commit. https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/modules/udev-util.c?id=3ac73598c67cb59a318c8baaf33fe97eed1e0b3e Thanks. ** Changed in: 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.net/bugs/1381475 Title: Firewire sound card registered by the name of the fw controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170949] Re: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** 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 playback runs at 88.2 and 96.0 kHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1395718] [NEW] snd_seq_free_event() is used in ALSAMidiDriver::read() but it's obsoleted.
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-buffer. This buffer is kept by snd_seq_open() and released by snd_seq_close(). The size of this buffer is retrieved by snd_seq_get_input_buffer_size() and changed by snd_seq_set_output_buffer_size(). ** Affects: amsynth (Ubuntu) Importance: Undecided Status: New ** Patch added: 0001-Remove-snd_seq_free_event-because-it-s-obsoleted-lon.patch https://bugs.launchpad.net/bugs/1395718/+attachment/4266687/+files/0001-Remove-snd_seq_free_event-because-it-s-obsoleted-lon.patch -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1395718 Title: snd_seq_free_event() is used in ALSAMidiDriver::read() but it's obsoleted. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/amsynth/+bug/1395718/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381475] Re: Firewire sound card registered by the name of the fw controller
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 information for FireWire sound devices. This requires a batch of time so I made it pending. Currently I would like to concentrate on my work for ALSA kernel-land. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381475 Title: Firewire sound card registered by the name of the fw controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381475] Re: Firewire sound card registered by the name of the fw controller
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, see below
struct snd_ctl_card_info.longname[80]
= a joined string of 'vendor name', 'model name', bus speed etc...
Sometimes truncated.
struct snd_ctl_card_info.mixername[80]
= not important because these modules basically has no control elements
struct snd_ctl_card_info.components[128]
= not filled
The 'config ROM' is defined in IEEE 1212 and IEEE 1394. Generally, each
device on IEEE 1394 bus have its information in the same register
defined in these specifications. In the information, vendor and model
name is included and the kernel modules refers to them.
You can see actual examples of the information in config ROM in ffado page:
http://subversion.ffado.org/wiki/AvcModels
For example,
http://subversion.ffado.org/wiki/AvcModels/TerratecPhase88
{{{
Config ROM
Current Node Id:0
GUID: 0x000aac0300d99287
Vendor Name:TerraTec Electronic GmbH
Model Name: PHASE 88 Rack FW
...
}}}
Well, I reccomend you to use struct snd_ctl_card_info.name[32] for shown
name. It can be retrieved by snd_ctl_card_info_get_name().
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1381475
Title:
Firewire sound card registered by the name of the fw controller
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1381475] Re: Firewire sound card registered by the name of the fw controller
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/amd64/linux-image-extra-3.16.0-23-generic/filelist (You can see /lib/modules/3.16.0-23-generic/kernel/sound/firewire/bebob/snd-bebob.ko in this list.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1381475 Title: Firewire sound card registered by the name of the fw controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 619752] Re: Ubuntu couldn output sound through the Presonus Firebox
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 Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/619752 Title: Ubuntu couldn output sound through the Presonus Firebox To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/619752/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1097308] Re: Echo Audiofire 12 not working on Ubuntu 12.10
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 is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1097308 Title: Echo Audiofire 12 not working on Ubuntu 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1097308/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** 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 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170949] [NEW] AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
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 reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) ** Affects: libffado (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jackd libffado quantal ** Attachment added: connection.png https://bugs.launchpad.net/bugs/1170949/+attachment/3649069/+files/connection.png ** Attachment removed: connection.png https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+attachment/3649069/+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 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** 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 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** 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/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** 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/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** 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/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** 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/1170949 Title: AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1170949] Re: MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz
** 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 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 reliable MIDI playback and capture software. I utilize kmidimon for playback and amidi for capture. - Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. - amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. + Using kmidimon and a2j togather, software MIDI playback port is connected to jackd's MIDI subsystem. + amidi can directly listen to hardware MIDI-in port of EMU 0404 USB with ALSA's MIDI subsystem. 4.Run jackd with Firewire backend at 88.2 or 96.0kHz and connect necessary ports. - See connection.png. + See connection.png. 5.Playback MIDI events to AudioFirePre8 and capture it from E-MU 0404 USB. - I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. - The captured data is converted to text data, result_.log. + I use control.mid as playback MIDI data. It includes control change events of 00 control in channel 1. + The captured data is converted to text data, result_.log. 6.Compare playback and capture MIDI bytes. When MIDI playback runs at 44.1 and 48.0 kHz, the capture data is the same as the playback but they are different at 88.2 and 96.0kHz. And at 88.2 and 96kHz, the capture data varies in each playback. + + This bug also appear in current upstream, svn revision 2299. ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: libffado2 2.0.99+svn2019-1ubuntu4 ProcVersionSignature: Ubuntu 3.5.0-28.47-generic 3.5.7.9 Uname: Linux 3.5.0-28-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.6.1-0ubuntu10 Architecture: amd64 Date: Sat Apr 20 23:01:31 2013 InstallationDate: Installed on 2011-12-18 (489 days ago) InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Release amd64 (20111011) MarkForUpload: True SourcePackage: libffado UpgradeStatus: Upgraded to quantal on 2012-11-11 (160 days ago) ** Summary changed: - MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz + AudioFirePre8, MIDI data from hardware port is invalid when MIDI playback runs at 88.2 and 96.0 kHz -- 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 playback runs at 88.2 and 96.0 kHz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/1170949/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1159450] [NEW] Almost DKMS packages fails to be built with Makefile: No such file or directory
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 build area(bad exit status: 2) make KERNELRELEASE=3.8.0-12-lowlatency -C /lib/modules/3.8.0-12-lowlatency/build M=/var/lib/dkms/v4l2loopback/0.6.1/build(bad exit status: 2) Traceback (most recent call last): File /usr/share/apport/package-hooks/dkms_packages.py, line 22, in module import apport ImportError: No module named apport Error! Bad return status for module build on kernel: 3.8.0-12-lowlatency (i686) Consult /var/lib/dkms/v4l2loopback/0.6.1/build/make.log for more information. $ cat /var/lib/dkms/v4l2loopback/0.6.1/build/make.log DKMS make.log for v4l2loopback-0.6.1 for kernel 3.8.0-12-lowlatency (i686) Mon Mar 25 00:49:05 JST 2013 make: Entering directory `/usr/src/linux-headers-3.8.0-12-lowlatency' make: Makefile: No such file or directory make: *** No rule to make target `Makefile'. Stop. make: Leaving directory `/usr/src/linux-headers-3.8.0-12-lowlatency' == for ndiswrapper == $ sudo dkms build -m ndiswrapper -v 1.58~rc1 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) make KERNELRELEASE=3.8.0-12-lowlatency KVERS=3.8.0-12-lowlatency(bad exit status: 2) Traceback (most recent call last): File /usr/share/apport/package-hooks/dkms_packages.py, line 22, in module import apport ImportError: No module named apport Error! Bad return status for module build on kernel: 3.8.0-12-lowlatency (i686) Consult /var/lib/dkms/ndiswrapper/1.58~rc1/build/make.log for more information. $ cat /var/lib/dkms/ndiswrapper/1.58~rc1/build/make.log DKMS make.log for ndiswrapper-1.58~rc1 for kernel 3.8.0-12-lowlatency (i686) Mon Mar 25 00:54:27 JST 2013 make -C /usr/src/linux-headers-3.8.0-12-lowlatency M=/var/lib/dkms/ndiswrapper/1.58~rc1/build make[1]: Entering directory `/usr/src/linux-headers-3.8.0-12-lowlatency' make[1]: Makefile: No such file or directory make[1]: *** No rule to make target `Makefile'. Stop. make[1]: Leaving directory `/usr/src/linux-headers-3.8.0-12-lowlatency' make: *** [modules] Error 2 My personal DKMS package also miss Makefile after entering /usr/src /linux-headers-3.8.0-12-lowlatency. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-lowlatency 3.8.0.12.5 ProcVersionSignature: Ubuntu 3.8.0-12.8-lowlatency 3.8.2 Uname: Linux 3.8.0-12-lowlatency i686 ApportVersion: 2.9.2-0ubuntu2 Architecture: i386 Date: Mon Mar 25 00:43:24 2013 InstallationDate: Installed on 2012-03-01 (387 days ago) InstallationMedia: Ubuntu-Studio 12.04 Precise Pangolin - Beta i386 (20120228.1) MarkForUpload: True SourcePackage: linux-meta-lowlatency UpgradeStatus: Upgraded to raring on 2013-03-17 (7 days ago) ** Affects: linux-meta-lowlatency (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug dkms i386 linux-lowlatency raring ** Description changed: 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 build area(bad exit status: 2) make KERNELRELEASE=3.8.0-12-lowlatency -C /lib/modules/3.8.0-12-lowlatency/build M=/var/lib/dkms/v4l2loopback/0.6.1/build(bad exit status: 2) Traceback (most recent call last): - File /usr/share/apport/package-hooks/dkms_packages.py, line 22, in module - import apport + File /usr/share/apport/package-hooks/dkms_packages.py, line 22, in module + import apport ImportError: No module named apport Error! Bad return status for module build on kernel: 3.8.0-12-lowlatency (i686) Consult /var/lib/dkms/v4l2loopback/0.6.1/build/make.log for more information. - $ cat /var/lib/dkms/v4l2loopback/0.6.1/ - build/make.log + $ cat /var/lib/dkms/v4l2loopback/0.6.1/build/make.log DKMS make.log for v4l2loopback-0.6.1 for kernel 3.8.0-12-lowlatency (i686) Mon Mar 25 00:49:05 JST 2013 make: Entering directory `/usr/src/linux-headers-3.8.0-12-lowlatency' make: Makefile: No such file or directory make: *** No rule to make target `Makefile'. Stop. make: Leaving directory `/usr/src/linux-headers-3.8.0-12-lowlatency' == for ndiswrapper == $ sudo dkms build -m ndiswrapper -v 1.58~rc1 Kernel preparation unnecessary for this kernel. Skipping... Building module: cleaning build area(bad exit status: 2) make KERNELRELEASE=3.8.0-12-lowlatency KVERS=3.8.0-12-lowlatency(bad exit status: 2) Traceback (most recent call last): - File /usr/share/apport/package-hooks/dkms_packages.py, line 22, in module - import apport + File
[Bug 1022196] Re: glibc detected *** lmms: double free or corruption (!prev)
-- 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/ubuntu/+source/lmms/+bug/1022196/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1022196] [NEW] glibc detected *** lmms: double free or corruption (!prev)
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(+0x7e626)[0x7fe7c4181626] /usr/lib/lmms/ladspa/caps.so(_fini+0x48)[0x7fe775c1faf8] /lib64/ld-linux-x86-64.so.2(+0xf92d)[0x7fe7c7de692d] /lib/x86_64-linux-gnu/libc.so.6(+0x3b921)[0x7fe7c413e921] /lib/x86_64-linux-gnu/libc.so.6(+0x3b9a5)[0x7fe7c413e9a5] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf4)[0x7fe7c4124774] lmms[0x47d1a1] === Memory map: 0040-005ab000 r-xp 08:01 1079973 /usr/bin/lmms 007aa000-007c3000 r--p 001aa000 08:01 1079973 /usr/bin/lmms 007c3000-007c6000 rw-p 001c3000 08:01 1079973 /usr/bin/lmms 007c6000-007d1000 rw-p 00:00 0 024a8000-08732000 rw-p 00:00 0 [heap] 7fe76400-7fe764021000 rw-p 00:00 0 7fe764021000-7fe76800 ---p 00:00 0 7fe76800-7fe768021000 rw-p 00:00 0 7fe768021000-7fe76c00 ---p 00:00 0 7fe76c00-7fe76c021000 rw-p 00:00 0 7fe76c021000-7fe77000 ---p 00:00 0 7fe771b6e000-7fe771b6f000 ---p 00:00 0 7fe771b6f000-7fe77236f000 rw-p 00:00 0 7fe77236f000-7fe772373000 r-xp 08:01 11814 /usr/lib/lmms/ladspa/vynil_1905.so 7fe772373000-7fe772572000 ---p 4000 08:01 11814 /usr/lib/lmms/ladspa/vynil_1905.so 7fe772572000-7fe772573000 r--p 3000 08:01 11814 /usr/lib/lmms/ladspa/vynil_1905.so 7fe772573000-7fe772574000 rw-p 4000 08:01 11814 /usr/lib/lmms/ladspa/vynil_1905.so 7fe772574000-7fe772576000 r-xp 08:01 11808 /usr/lib/lmms/ladspa/tap_vibrato.so 7fe772576000-7fe772775000 ---p 2000 08:01 11808 /usr/lib/lmms/ladspa/tap_vibrato.so 7fe772775000-7fe772776000 r--p 1000 08:01 11808 /usr/lib/lmms/ladspa/tap_vibrato.so 7fe772776000-7fe772777000 rw-p 2000 08:01 11808 /usr/lib/lmms/ladspa/tap_vibrato.so 7fe772777000-7fe772778000 rw-p 00:00 0 7fe772778000-7fe77277b000 r-xp 08:01 11823 /usr/lib/lmms/ladspa/tap_tubewarmth.so 7fe77277b000-7fe77297a000 ---p 3000 08:01 11823 /usr/lib/lmms/ladspa/tap_tubewarmth.so 7fe77297a000-7fe77297b000 r--p 2000 08:01 11823 /usr/lib/lmms/ladspa/tap_tubewarmth.so 7fe77297b000-7fe77297c000 rw-p 3000 08:01 11823 /usr/lib/lmms/ladspa/tap_tubewarmth.so 7fe77297c000-7fe77297e000 r-xp 08:01 11804 /usr/lib/lmms/ladspa/tap_tremolo.so 7fe77297e000-7fe772b7d000 ---p 2000 08:01 11804 /usr/lib/lmms/ladspa/tap_tremolo.so 7fe772b7d000-7fe772b7e000 r--p 1000 08:01 11804 /usr/lib/lmms/ladspa/tap_tremolo.so 7fe772b7e000-7fe772b7f000 rw-p 2000 08:01 11804 /usr/lib/lmms/ladspa/tap_tremolo.so 7fe772b7f000-7fe772b8 rw-p 00:00 0 7fe772b8-7fe772b83000 r-xp 08:01 11805 /usr/lib/lmms/ladspa/tap_sigmoid.so 7fe772b83000-7fe772d82000 ---p 3000 08:01 11805 /usr/lib/lmms/ladspa/tap_sigmoid.so 7fe772d82000-7fe772d83000 r--p 2000 08:01 11805 /usr/lib/lmms/ladspa/tap_sigmoid.so 7fe772d83000-7fe772d84000 rw-p 3000 08:01 11805 /usr/lib/lmms/ladspa/tap_sigmoid.so 7fe772d84000-7fe772d88000 r-xp 08:01 11802 /usr/lib/lmms/ladspa/tap_rotspeak.so 7fe772d88000-7fe772f88000 ---p 4000 08:01 11802 /usr/lib/lmms/ladspa/tap_rotspeak.so 7fe772f88000-7fe772f89000 r--p 4000 08:01 11802 /usr/lib/lmms/ladspa/tap_rotspeak.so 7fe772f89000-7fe772f8a000 rw-p 5000 08:01 11802 /usr/lib/lmms/ladspa/tap_rotspeak.so 7fe772f8a000-7fe772f8b000 rw-p 00:00 0 7fe772f8b000-7fe772f8f000 r-xp 08:01 11827 /usr/lib/lmms/ladspa/tap_reverb.so 7fe772f8f000-7fe77318e000 ---p 4000 08:01 11827 /usr/lib/lmms/ladspa/tap_reverb.so 7fe77318e000-7fe77318f000 r--p 3000 08:01 11827 /usr/lib/lmms/ladspa/tap_reverb.so 7fe77318f000-7fe773194000 rw-p 4000 08:01 11827 /usr/lib/lmms/ladspa/tap_reverb.so 7fe773194000-7fe773196000 r-xp 08:01 11815 /usr/lib/lmms/ladspa/tap_reflector.so 7fe773196000-7fe773396000 ---p 2000 08:01 11815 /usr/lib/lmms/ladspa/tap_reflector.so 7fe773396000-7fe773397000 r--p 2000 08:01 11815
[Bug 958673] Re: the kernel configuration is almost the same as generic kernel
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/+source/linux-lowlatency Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/958673 Title: the kernel configuration is almost the same as generic kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lowlatency/+bug/958673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 958673] [NEW] the kernel configuration is almost the same as generic kernel
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 77c77 CONFIG_VERSION_SIGNATURE=Ubuntu 3.2.0-18.29-generic-pae 3.2.9 --- CONFIG_VERSION_SIGNATURE=Ubuntu 3.2.0-18.26-lowlatency-pae 3.2.9 5833d5832 CONFIG_APPLE_GMUX=m As far as I know, lowlatency kernel is an aggressively configured kernel for multimedia performance but there seems to be no differences between generic and lowlatency kernel to refer to each configuration files under /boot. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: linux-lowlatency (not installed) ProcVersionSignature: Ubuntu 3.2.0-18.26-lowlatency-pae 3.2.9 Uname: Linux 3.2.0-18-lowlatency-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Mon Mar 19 02:03:40 2012 InstallationMedia: Ubuntu-Studio 12.04 Precise Pangolin - Beta i386 (20120228.1) ProcEnviron: LANGUAGE=ja:en TERM=xterm LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: linux-meta-lowlatency UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-meta-lowlatency (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lowlatency precise -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/958673 Title: the kernel configuration is almost the same as generic kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-lowlatency/+bug/958673/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778887] Re: Compile error with @CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No such file or directory.
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 file or directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/778887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778887] Re: Compile error with @CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No such file or directory.
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/pci_ids.h: No such file or directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/778887/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855438] [NEW] [Oneiric] Need upgrading package from revision 1995 to fix jackd shutdown problem
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 compiled with dbus. This bug was reported ticket 306 and it seemed to be fixed in revision 1985. http://subversion.ffado.org/ticket/306 But in this week, a guy post a patch related to this. His patch is not directly applied but it's a cue to reconsider the bug. http://sourceforge.net/mailarchive/forum.php?thread_name=4E7992BB.1000505%40monom.orgforum_name=ffado-devel Now this seems to be fixed in revision 1995. http://subversion.ffado.org/changeset/1995 I'm also realized there is a problem to shudown jackd which we can utilize from released package. I personnaly generated package from revision 1995 and confirmed this bug seems to be fixed. If possible, I hope you to upgrade package with revision 1995. Regards ** Affects: libffado (Ubuntu) Importance: Undecided Status: New ** Tags: ffado firewire gladish jackd libffado qjackctl -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855438 Title: [Oneiric] Need upgrading package from revision 1995 to fix jackd shutdown problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/855438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 855438] Re: [Oneiric] Need to upgrade package with revision 1995 to fix jackd shutdown problem
** 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. 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 + The current package is generated with revision 1985. This still causes shutdown problem of jackd compiled with dbus. This bug was reported ticket 306 and it seemed to be fixed in revision 1985. http://subversion.ffado.org/ticket/306 But in this week, a guy post a patch related to this. His patch is not directly applied but it's a cue to reconsider the bug. http://sourceforge.net/mailarchive/forum.php?thread_name=4E7992BB.1000505%40monom.orgforum_name=ffado-devel Now this seems to be fixed in revision 1995. http://subversion.ffado.org/changeset/1995 I'm also realized there is a problem to shudown jackd which we can utilize from released package. I personnaly generated package from revision 1995 and confirmed this bug seems to be fixed. If possible, I hope you to upgrade package with revision 1995. Regards -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/855438 Title: [Oneiric] Need to upgrade package with revision 1995 to fix jackd shutdown problem To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/855438/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835166] Re: [Oneiric] Could not launch gladish with segmentation fault.
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://bugs.launchpad.net/ladish/+bug/835166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 832137] Re: Need to fix bugs causes compiling error. One is related to Open Sound System Emuration. The other is caused by patches.
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)) $dir/Makefile +kernelsrc=$(make -C $CONFIG_SND_KERNELDIR M=$dir 21 /dev/null | \ + sed -n s#^$dir/Makefile:.*: KBUILD_SRC=\(.*\)\$#\1#; T; p; q) +rm -rf $dir +if test -z $kernelsrc; then + AC_MSG_RESULT(failed) + exit 1 +else + CONFIG_SND_KERNELSRC=$kernelsrc + AC_MSG_RESULT($kernelsrc) +fi With configure script generated by autoconf, we fail to set $CONFIG_SND_KERNELSRC into $kernelsrc in Ubuntu environment. I cannot generate fix patch with my poor skills... I hope this may help you. -- 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 patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/832137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835166] Re: [Oneiric] Could not launch with segmentation fault.
** 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: [Oneiric] Could not launch gladish with segmentation fault. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ladish/+bug/835166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835166] [NEW] [Oneiric] Could not launch gladish with segmentation fault.
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_appeared(1, Hardware Capture) canvas::port_appeared(1, 1, capture_1) canvas::port_appeared(1, 2, capture_2) canvas::client_appeared(2, Hardware Playback) canvas::port_appeared(2, 3, playback_1) canvas::port_appeared(2, 4, playback_2) canvas::client_appeared(3, PulseAudio JACK Sink) canvas::port_appeared(3, 5, front-left) canvas::port_appeared(3, 6, front-right) canvas::client_appeared(4, PulseAudio JACK Source) canvas::port_appeared(4, 7, front-left) canvas::port_appeared(4, 8, front-right) canvas::ports_connected(3, 5, 2, 3) canvas::ports_connected(3, 6, 2, 4) canvas::ports_connected(1, 1, 4, 7) canvas::ports_connected(1, 2, 4, 8) canvas_cls::on_realize Segmentation fault (core dumped) $ dmesg; [ 1523.843288] gladish[3488]: segfault at 24 ip 08056440 sp bf849888 error 4 in gladish[8048000+34000] [ 1825.174143] gladish[3927]: segfault at 4 ip 080677d3 sp bf929560 error 4 in gladish[8048000+34000] I have a time to report more infomation if you teach how to get it... Regards ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gladish 0.3-7 ProcVersionSignature: Ubuntu 3.0.0-9.14~ppa1-lowlatency 3.0.3 Uname: Linux 3.0.0-9-lowlatency i686 Architecture: i386 Date: Sat Aug 27 09:44:04 2011 InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Alpha i386 (20110716) ProcEnviron: PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: ladish UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ladish (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric -- 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://bugs.launchpad.net/ubuntu/+source/ladish/+bug/835166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835168] [NEW] [Oneiric] gladish needs dependency on a2jmidid.
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 didn't get the same line after installing a2jmidid package so It seems that gladish need dependency on a2jmidid package. Regards ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: gladish 0.3-7 ProcVersionSignature: Ubuntu 3.0.0-9.14~ppa1-lowlatency 3.0.3 Uname: Linux 3.0.0-9-lowlatency i686 Architecture: i386 Date: Sat Aug 27 09:55:31 2011 InstallationMedia: Ubuntu-Studio 11.10 Oneiric Ocelot - Alpha i386 (20110716) ProcEnviron: PATH=(custom, no user) LANG=C SHELL=/bin/bash SourcePackage: ladish UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ladish (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 oneiric -- 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/ladish/+bug/835168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835168] Re: [Oneiric] gladish needs dependency on a2jmidid.
-- 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/ladish/+bug/835168/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835166] Re: [Oneiric] Could not launch gladish with segmentation fault.
** 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: [Oneiric] Could not launch gladish with segmentation fault. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ladish/+bug/835166/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 835195] [NEW] [Oneiric] 2D gamut display is not shown in gcm-viewer.
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 information about this in my terminal. $ gcm-viewer -v 11:14:07Verbose debugging enabled (on console 1) 11:14:07no input profile, assume sRGB 11:14:07no output profile, assume sRGB 11:14:07no input profile, assume sRGB 11:14:07no output profile, assume sRGB 11:14:07Setting xid 14914340 11:14:07failed to get parent window 11:14:07updating profile list 11:14:07add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07add /usr/share/color/icc/colord/x11-colors.icc to profiles list 11:14:07add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07add /usr/share/color/icc/FOGRA30L.ti3 to profiles list 11:14:07add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07add /usr/share/color/icc/FOGRA40L.ti3 to profiles list 11:14:07add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07add /usr/share/color/icc/TR006.ti3 to profiles list 11:14:07add /usr/share/color/icc/LCMSLABI.ICM to profiles list 11:14:07add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07add /usr/share/color/icc/TR005.ti3 to profiles list 11:14:07add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07add /usr/share/color/icc/TR003.ti3 to profiles list 11:14:07add /usr/share/color/icc/TR002.ti3 to profiles list 11:14:07add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07add /usr/share/color/icc/FOGRA28L.ti3 to profiles list 11:14:07add /usr/share/color/icc/FOGRA29L.ti3 to profiles list 11:14:08add /usr/share/color/icc/FOGRA39L.ti3 to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/colord/x11-colors.icc to profiles list 11:14:08add /usr/share/color/icc/PSO_LWC_Improved_eci.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/ISOcoated_v2_eci.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/colord/x11-colors.icc to profiles list 11:14:08add /usr/share/color/icc/PSO_Coated_300_NPscreen_ISO12647_eci.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/PSO_LWC_Standard_eci.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/PSO_Uncoated_NPscreen_ISO12647_eci.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/ISOcoated_v2_300_eci.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/PSO_Uncoated_ISO12647_eci.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/ISO22028-2_ROMM-RGB.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/ISOuncoatedyellowish.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/sRGB_IEC61966-2-1_black_scaled.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/eciRGB_v2.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/PSO_SNP_Paper_eci.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/PSO_MFC_Paper_eci.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/PSO_Coated_NPscreen_ISO12647_eci.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/sRGB_v4_ICC_preference.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08add /usr/share/color/icc/SC_paper_eci.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/sRGB_IEC61966-2-1_no_black_scaling.icc.dpkg-new to profiles list 11:14:08add /usr/share/color/icc/CineLogCurve.icc to profiles list
[Bug 835195] Re: [Oneiric] 2D gamut display is not shown in gcm-viewer.
** 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 specific information about this in my terminal. $ gcm-viewer -v 11:14:07 Verbose debugging enabled (on console 1) 11:14:07 no input profile, assume sRGB 11:14:07 no output profile, assume sRGB 11:14:07 no input profile, assume sRGB 11:14:07 no output profile, assume sRGB 11:14:07 Setting xid 14914340 11:14:07 failed to get parent window 11:14:07 updating profile list 11:14:07 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07 add /usr/share/color/icc/colord/x11-colors.icc to profiles list 11:14:07 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07 add /usr/share/color/icc/FOGRA30L.ti3 to profiles list 11:14:07 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07 add /usr/share/color/icc/FOGRA40L.ti3 to profiles list 11:14:07 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07 add /usr/share/color/icc/TR006.ti3 to profiles list 11:14:07 add /usr/share/color/icc/LCMSLABI.ICM to profiles list 11:14:07 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07 add /usr/share/color/icc/TR005.ti3 to profiles list 11:14:07 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07 add /usr/share/color/icc/TR003.ti3 to profiles list 11:14:07 add /usr/share/color/icc/TR002.ti3 to profiles list 11:14:07 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:07 add /usr/share/color/icc/FOGRA28L.ti3 to profiles list 11:14:07 add /usr/share/color/icc/FOGRA29L.ti3 to profiles list 11:14:08 add /usr/share/color/icc/FOGRA39L.ti3 to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/colord/x11-colors.icc to profiles list 11:14:08 add /usr/share/color/icc/PSO_LWC_Improved_eci.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/ISOcoated_v2_eci.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/colord/x11-colors.icc to profiles list 11:14:08 add /usr/share/color/icc/PSO_Coated_300_NPscreen_ISO12647_eci.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/PSO_LWC_Standard_eci.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/PSO_Uncoated_NPscreen_ISO12647_eci.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/ISOcoated_v2_300_eci.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/PSO_Uncoated_ISO12647_eci.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/ISO22028-2_ROMM-RGB.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/ISOuncoatedyellowish.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/sRGB_IEC61966-2-1_black_scaled.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/eciRGB_v2.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/PSO_SNP_Paper_eci.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/PSO_MFC_Paper_eci.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/PSO_Coated_NPscreen_ISO12647_eci.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/sRGB_v4_ICC_preference.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/CineLogCurve.icc to profiles list 11:14:08 add /usr/share/color/icc/SC_paper_eci.icc.dpkg-new to profiles list 11:14:08 add /usr/share/color/icc/sRGB_IEC61966-2-1_no_black_scaling.icc.dpkg-new to profiles list 11:14:08 add
[Bug 832137] Re: Need to fix bugs causes compiling error. One is related to Open Sound System Emuration. The other is caused by modification when creating package.
** 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-assistant update; - 4. $ sudo a-i alsa; + 4. $ sudo module-assistant auto-install alsa; 5. failed. The bugs in this source are classified two parts below. 1. Open Sound System Emulation issue 2. troubles by modification when creating package - 1. Open Sound System Emulation issue Ubuntu's generic kernel has no options related to Open Sound System. You can see the kernel configuration in /boot/config-2.6.38-11-generic if you use 2.6.38-11-generic kernel. $ cat /boot/config-2.6.38-11-generic; # CONFIG_SOUND_OSS_CORE is not set # CONFIG_SND_MIXER_OSS is not set # CONFIG_SND_PCM_OSS is not set # CONFIG_SND_SEQUENCER_OSS is not set So Open Sound System Emuration should be disabled in ALSA, too. But as a default, this source enable it. As a result, even if we are success to compile the source and install them, then modprobe reject to call them with errors. For example: $ dmesg; [3.015889] snd: Unknown symbol unregister_sound_special (err 0) [3.016859] snd: Unknown symbol register_sound_special_device (err 0) [3.019419] snd_timer: Unknown symbol snd_info_register (err 0) [3.019473] snd_timer: Unknown symbol snd_info_create_module_entry (err 0) [3.019556] snd_timer: Unknown symbol snd_info_free_entry (err 0) [3.019697] snd_timer: Unknown symbol __snd_printk (err 0) [3.019750] snd_timer: Unknown symbol snd_iprintf (err 0) [3.019827] snd_timer: Unknown symbol snd_ecards_limit (err 0) [3.019908] snd_timer: Unknown symbol snd_oss_info_register (err 0) [3.019961] snd_timer: Unknown symbol snd_unregister_device (err 0) [3.020049] snd_timer: Unknown symbol snd_device_new (err 0) [3.022230] snd_timer: Unknown symbol snd_register_device_for_dev (err 0) To avoid this, it's good to enable --with-oss=no option in configure script or put some equivalent codes into configure script. The latter is good to use this with module-assistant. - 2. troubles by modification when creating package I generated diff between this source and original ALSA source and realized two modification. 2-1. half-finished replacement of macros In this source, @CONFIG_SND_KERNELSRC@ is rewrited as @CONFIG_SND_KERNELDIR@ but it's half-finished. Two files still include @CONFIG_SND_KERNELSRC@ and this causes error because @CONFIG_SND_KERNELSRC@ is not extracted. Files: /include/linux/pci_ids_compat.h /include/linux/i2c_id.h To avoid this, it's good to modify the lines in these two files of this source. (I've already reported this but it was expired Compile error with @CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No such file or directory. https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/778887) - 2-2. Some files are removed because of debian packaging policy. Some files related to five modules are removed. But as a default, they are compile target although missing makefile. modules: - - cs46xx - - cs46xx-new-dep - - maestro3 - - ymfpci - - korg1212 + - cs46xx + - cs46xx-new-dep + - maestro3 + - ymfpci + - korg1212 To solve this, it's to good to exclude these modules by configure option or disable some codes related to them in configure script. The latter is good to use this source with module-assistant. - This source makes no sence and currently we need to use the original alsa source. I hope you to put high priority to this bug and release modified package as soon as possible. Regards ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-source 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42~ppa2-lowlatency 2.6.38.2 Uname: Linux 2.6.38-8-lowlatency i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: - List of CAPTURE Hardware Devices - card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] -Subdevices: 2/2 -Subdevice #0: subdevice #0 -Subdevice #1: subdevice #1 + List of CAPTURE Hardware Devices + card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] + Subdevices: 2/2 + Subdevice #0: subdevice #0 + Subdevice #1: subdevice #1 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: mocchi 1625 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: mocchi 1625 F pulseaudio Card0.Amixer.info: - Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 44' -Mixer name : 'Analog Devices AD1984' -Components : 'HDA:11d41984,17aa20d6,00100400' -Controls : 31 -Simple ctrls : 19 + Card hw:0
[Bug 832137] [NEW] Need to fix bugs causes compiling error. One is related to Open Sound System Emuration. The other is caused by modification when creating package.
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. $ sudo a-i alsa; 5. failed. The bugs in this source are classified two parts below. 1. Open Sound System Emulation issue 2. troubles by modification when creating package 1. Open Sound System Emulation issue Ubuntu's generic kernel has no options related to Open Sound System. You can see the kernel configuration in /boot/config-2.6.38-11-generic if you use 2.6.38-11-generic kernel. $ cat /boot/config-2.6.38-11-generic; # CONFIG_SOUND_OSS_CORE is not set # CONFIG_SND_MIXER_OSS is not set # CONFIG_SND_PCM_OSS is not set # CONFIG_SND_SEQUENCER_OSS is not set So Open Sound System Emuration should be disabled in ALSA, too. But as a default, this source enable it. As a result, even if we are success to compile the source and install them, then modprobe reject to call them with errors. For example: $ dmesg; [3.015889] snd: Unknown symbol unregister_sound_special (err 0) [3.016859] snd: Unknown symbol register_sound_special_device (err 0) [3.019419] snd_timer: Unknown symbol snd_info_register (err 0) [3.019473] snd_timer: Unknown symbol snd_info_create_module_entry (err 0) [3.019556] snd_timer: Unknown symbol snd_info_free_entry (err 0) [3.019697] snd_timer: Unknown symbol __snd_printk (err 0) [3.019750] snd_timer: Unknown symbol snd_iprintf (err 0) [3.019827] snd_timer: Unknown symbol snd_ecards_limit (err 0) [3.019908] snd_timer: Unknown symbol snd_oss_info_register (err 0) [3.019961] snd_timer: Unknown symbol snd_unregister_device (err 0) [3.020049] snd_timer: Unknown symbol snd_device_new (err 0) [3.022230] snd_timer: Unknown symbol snd_register_device_for_dev (err 0) To avoid this, it's good to enable --with-oss=no option in configure script or put some equivalent codes into configure script. The latter is good to use this with module-assistant. 2. troubles by modification when creating package I generated diff between this source and original ALSA source and realized two modification. 2-1. half-finished replacement of macros In this source, @CONFIG_SND_KERNELSRC@ is rewrited as @CONFIG_SND_KERNELDIR@ but it's half-finished. Two files still include @CONFIG_SND_KERNELSRC@ and this causes error because @CONFIG_SND_KERNELSRC@ is not extracted. Files: /include/linux/pci_ids_compat.h /include/linux/i2c_id.h To avoid this, it's good to modify the lines in these two files of this source. (I've already reported this but it was expired Compile error with @CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No such file or directory. https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/778887) 2-2. Some files are removed because of debian packaging policy. Some files related to five modules are removed. But as a default, they are compile target although missing makefile. modules: - cs46xx - cs46xx-new-dep - maestro3 - ymfpci - korg1212 To solve this, it's to good to exclude these modules by configure option or disable some codes related to them in configure script. The latter is good to use this source with module-assistant. This source makes no sence and currently we need to use the original alsa source. I hope you to put high priority to this bug and release modified package as soon as possible. Regards ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-source 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42~ppa2-lowlatency 2.6.38.2 Uname: Linux 2.6.38-8-lowlatency i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mocchi 1625 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 44' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20d6,00100400' Controls : 31 Simple ctrls : 19 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7MHT25WW-1.03' Mixer name : 'ThinkPad EC 7MHT25WW-1.03' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] CurrentDmesg: [ 34.525939] e1000e :00:19.0: eth0: 10/100 speed: disabling TSO [ 34.526147] ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready [ 38.614492] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro,commit=0 [ 38.706488] EXT4-fs (sda2): re-mounted. Opts: commit=0 [
[Bug 832137] Re: Need to fix bugs causes compiling error. One is related to Open Sound System Emuration. The other is caused by modification when creating package.
-- 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 package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/832137/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820993] Re: Need dependency on libmjpegtools-dev for enabling live firewire and v4l-capable devices.
** 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 its building process. It's pretty sad that LiVES lost its live function in Ubuntu so I want you to make it enable. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: lives 1.4.1-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42~ppa2-lowlatency 2.6.38.2 Uname: Linux 2.6.38-8-lowlatency x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Aug 5 00:46:23 2011 InstallationMedia: Ubuntu-Studio 11.04 Natty Narwhal - Release amd64 (20110426.1) ProcEnviron: - LANGUAGE=ja:en - LANG=ja_JP.UTF-8 - SHELL=/bin/bash + LANGUAGE=ja:en + LANG=ja_JP.UTF-8 + SHELL=/bin/bash SourcePackage: lives UpgradeStatus: No upgrade log present (probably fresh install) -- 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: Need dependency on libmjpegtools-dev for enabling live firewire and v4l-capable devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lives/+bug/820993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820993] Re: Need dependency into libmjpegtools-dev for enabling live firewire and v4l-capable devices.
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/820993 Title: Need dependency into libmjpegtools-dev for enabling live firewire and v4l-capable devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lives/+bug/820993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 821791] [NEW] Need dependency on libunicap2-dev for enabling live v4l-capable devices.
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 you to make it enable. (This bug report looks similar to my previou one, Bug #820993, but I notice that LiVES has two distinguishable ways to enable v4l-capable devices.) ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: lives 1.4.1-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42~ppa2-lowlatency 2.6.38.2 Uname: Linux 2.6.38-8-lowlatency x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Sat Aug 6 12:52:19 2011 InstallationMedia: Ubuntu-Studio 11.04 Natty Narwhal - Release amd64 (20110426.1) ProcEnviron: LANGUAGE=ja:en LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: lives UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lives (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- 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.launchpad.net/ubuntu/+source/lives/+bug/821791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 821791] Re: Need dependency into libunicap2-dev for enabling live v4l-capable devices.
-- 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.launchpad.net/ubuntu/+source/lives/+bug/821791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 821791] Re: Need dependency into libunicap2-dev for enabling live v4l-capable devices.
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-1ubuntu1_BUILDING.txt.gz i386, Oneiric https://launchpadlibrarian.net/76104267/buildlog_ubuntu-oneiric-i386.lives_1.4.5-1_BUILDING.txt.gz amd64, Oneiric https://launchpadlibrarian.net/76128984/buildlog_ubuntu-oneiric-amd64.lives_1.4.5-1_BUILDING.txt.gz Let's see debian/control Source: lives Section: video Priority: optional Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Uploaders: Alessio Treglia ales...@debian.org, Harry Rickards hricka...@l33tmyst.com Standards-Version: 3.9.2 Build-Depends: debhelper (= 7.0.50~), autotools-dev (= 20100122.1~), libdirectfb-dev[!hurd-i386], libaa1-dev, libgtk2.0-dev (= 2.16), bison, libjack-dev, libsdl1.2-dev, xutils-dev, autoconf, automake, libtool, gettext, libtheora-dev[!sparc64], frei0r-plugins-dev [!kfreebsd-any !hurd-i386 !arm !avr32 !sparc64], libogg-dev, libdv4-dev[!hurd-i386], libraw1394-dev [linux-any], libavc1394-dev [linux-any], liboil0.3-dev, libasound2-dev [linux-any], libpulse-dev, libvorbis-dev, libv4l-dev [linux-any], libdirac-dev[!m68k], python-all (= 2.6.6-3~) DM-Upload-Allowed: yes X-Python-Version: = 2.5 Homepage: http://lives.sourceforge.net/ Vcs-Git: git://git.debian.org/git/pkg-multimedia/lives.git Vcs-Browser: http://git.debian.org/?p=pkg-multimedia/lives.git We need a line libunicap2-dev in Build-Depends field. ** Summary changed: - Need dependency into libunicap2-dev for enabling live v4l-capable devices. + Need dependency on libunicap2-dev for enabling live v4l-capable devices. -- 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.launchpad.net/ubuntu/+source/lives/+bug/821791/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820993] Re: Need dependency on libmjpegtools-dev for enabling live firewire and v4l-capable devices.
** 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 subscribed to Ubuntu. https://bugs.launchpad.net/bugs/820993 Title: Need dependency on libmjpegtools-dev for enabling live firewire and v4l-capable devices. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lives/+bug/820993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820993] [NEW] For enabling live firewire and v4l-capable devices, need dependency into libmjpegtools-dev.
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 Ubuntu so I want you to make it enable. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: lives 1.4.1-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42~ppa2-lowlatency 2.6.38.2 Uname: Linux 2.6.38-8-lowlatency x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Fri Aug 5 00:46:23 2011 InstallationMedia: Ubuntu-Studio 11.04 Natty Narwhal - Release amd64 (20110426.1) ProcEnviron: LANGUAGE=ja:en LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: lives UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lives (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug libmjpegtools-dev lives natty -- 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: https://bugs.launchpad.net/ubuntu/+source/lives/+bug/820993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820993] Re: For enabling live firewire and v4l-capable devices, need dependency into libmjpegtools-dev.
-- 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: https://bugs.launchpad.net/ubuntu/+source/lives/+bug/820993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820993] Re: For enabling live firewire and v4l-capable devices, need dependency into libmjpegtools-dev.
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-1ubuntu1_BUILDING.txt.gz i386, Oneiric https://launchpadlibrarian.net/76104267/buildlog_ubuntu-oneiric-i386.lives_1.4.5-1_BUILDING.txt.gz amd64, Oneiric https://launchpadlibrarian.net/76128984/buildlog_ubuntu-oneiric-amd64.lives_1.4.5-1_BUILDING.txt.gz Let's see debian/control Source: lives Section: video Priority: optional Maintainer: Debian Multimedia Maintainers pkg-multimedia-maintain...@lists.alioth.debian.org Uploaders: Alessio Treglia ales...@debian.org, Harry Rickards hricka...@l33tmyst.com Standards-Version: 3.9.2 Build-Depends: debhelper (= 7.0.50~), autotools-dev (= 20100122.1~), libdirectfb-dev[!hurd-i386], libaa1-dev, libgtk2.0-dev (= 2.16), bison, libjack-dev, libsdl1.2-dev, xutils-dev, autoconf, automake, libtool, gettext, libtheora-dev[!sparc64], frei0r-plugins-dev [!kfreebsd-any !hurd-i386 !arm !avr32 !sparc64], libogg-dev, libdv4-dev[!hurd-i386], libraw1394-dev [linux-any], libavc1394-dev [linux-any], liboil0.3-dev, libasound2-dev [linux-any], libpulse-dev, libvorbis-dev, libv4l-dev [linux-any], libdirac-dev[!m68k], python-all (= 2.6.6-3~) DM-Upload-Allowed: yes X-Python-Version: = 2.5 Homepage: http://lives.sourceforge.net/ Vcs-Git: git://git.debian.org/git/pkg-multimedia/lives.git Vcs-Browser: http://git.debian.org/?p=pkg-multimedia/lives.git We need a line libmjpegtools-dev in Build-Depends field. -- 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: https://bugs.launchpad.net/ubuntu/+source/lives/+bug/820993/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820276] [NEW] [patch] four synthesizers cannot be called.
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: monobristol 0.60.3-1 ProcVersionSignature: Ubuntu 2.6.38-8.42~ppa2-lowlatency 2.6.38.2 Uname: Linux 2.6.38-8-lowlatency x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Wed Aug 3 19:06:20 2011 InstallationMedia: Ubuntu-Studio 11.04 Natty Narwhal - Release amd64 (20110426.1) PackageArchitecture: all ProcEnviron: LANGUAGE=ja:en LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: monobristol UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: monobristol (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/820276 Title: [patch] four synthesizers cannot be called. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monobristol/+bug/820276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820276] Re: [patch] four synthesizers cannot be called.
** 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 bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/820276 Title: [patch] four synthesizers cannot be called. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monobristol/+bug/820276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 820276] Re: [patch] four synthesizers cannot be called.
** 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/820276 Title: [patch] four synthesizers cannot be called. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/monobristol/+bug/820276/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649542] Re: New firewire stack makes more FFADO XRUNs than old firewire stack.
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 notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libffado/+bug/649542/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778887] Re: Compile error with @CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No such file or directory.
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 install ALSA kernel module 1.0.24 as a maintainable package. But I failed to do this with the reported bug. This bug causes fail to build in module-assistant script. I'm very welcome to your work in Ubuntu Audio Dev team but this PPA serves Daily Build. In my opinion, daily build includes some bugs and should be used by the users who can find solutions by their own effort when facing bugs. Of cource, I hope to be such a user but all of members in my LoCo is not such users. So I'm hesitate to introduce your packages to all users. I think It a good way to use the same source then I need build-able alsa- source package. I say again that I'm very welcome to your work for daily build. But what I want is to keep both ways of utilizing daily build and utilize the same source, for good solutions. Best Regards -- 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 file or directory. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779194] Re: fixed-width japanese renders differently from other GTK/QT apps
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 this bug is not related to which font is applied but related to the backends of displaying process. -- 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: fixed-width japanese renders differently from other GTK/QT apps -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 779194] Re: fixed-width japanese renders differently from other GTK/QT apps
** 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: fixed-width japanese renders differently from other GTK/QT apps -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778887] [NEW] Compile error with @CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No such file or directory.
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/include/linux/config.h:4:0, from /usr/src/modules/alsa-driver/include/alsa-autoconf.h:9, from /usr/src/modules/alsa-driver/acore/memory_wrapper.c:1: /usr/src/modules/alsa-driver/include/generated/autoconf.h:4600:0: warning: CONFIG_SND_HDA_INPUT_BEEP_MODE redefined ./include/generated/autoconf.h:2385:0: note: this is the location of the previous definition In file included from /usr/src/modules/alsa-driver/include/linux/config.h:4:0, from /usr/src/modules/alsa-driver/include/alsa-autoconf.h:9, from /usr/src/modules/alsa-driver/acore/memalloc.inc:1, from /usr/src/modules/alsa-driver/acore/memalloc.c:1: /usr/src/modules/alsa-driver/include/generated/autoconf.h:4600:0: warning: CONFIG_SND_HDA_INPUT_BEEP_MODE redefined ./include/generated/autoconf.h:2385:0: note: this is the location of the previous definition In file included from include/linux/pci.h:58:0, from /usr/src/modules/alsa-driver/acore/memalloc.inc:13, from /usr/src/modules/alsa-driver/acore/memalloc.c:1: /usr/src/modules/alsa-driver/include/linux/pci_ids.h:2:58: fatal error: @CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No such file or directory compilation terminated. make[3]: *** [/usr/src/modules/alsa-driver/acore/memalloc.o] Error 1 make[2]: *** [/usr/src/modules/alsa-driver/acore] Error 2 make[1]: *** [_module_/usr/src/modules/alsa-driver] Error 2 make: *** [compile] Error 2 This bus is related to module-assistant package. I hope to fix this bug and to be able to generate the latest ALSA kernel module package by utilizing module-assistant. Regards ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: alsa-source 1.0.24+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4 Uname: Linux 2.6.38-9-generic i686 AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23. Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog] Subdevices: 2/2 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mocchi 1719 F pulseaudio Card0.Amixer.info: Card hw:0 'Intel'/'HDA Intel at 0xfe02 irq 44' Mixer name : 'Analog Devices AD1984' Components : 'HDA:11d41984,17aa20d6,00100400' Controls : 31 Simple ctrls : 19 Card29.Amixer.info: Card hw:29 'ThinkPadEC'/'ThinkPad Console Audio Control at EC reg 0x30, fw 7MHT25WW-1.03' Mixer name : 'ThinkPad EC 7MHT25WW-1.03' Components : '' Controls : 1 Simple ctrls : 1 Card29.Amixer.values: Simple mixer control 'Console',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Date: Sat May 7 15:31:05 2011 InstallationMedia: Ubuntu-Studio 11.04 Natty Narwhal - Alpha i386 (20110112) PackageArchitecture: all ProcEnviron: LANGUAGE=ja_JP:ja:en_GB:en LANG=ja_JP.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/09/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETC1WW (2.21 ) dmi.board.name: 7675A63 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7NETC1WW(2.21):bd10/09/2009:svnLENOVO:pn7675A63:pvrThinkPadX61:rvnLENOVO:rn7675A63:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7675A63 dmi.product.version: ThinkPad X61 dmi.sys.vendor: LENOVO ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: alsa-source apport-bug i386 modulle-assistant natty -- 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 file or directory. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778887] Re: Compile error with @CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No such file or directory.
** 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: Compile error with @CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No such file or directory. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 778887] Re: Compile error with @CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No such file or directory.
** 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 Title: Compile error with @CONFIG_SND_KERNELSRC@/include/linux/pci_ids.h: No such file or directory. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776077] [NEW] Rosegarden should have the dependency with awesfx.
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 rosegarden. Regards ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: rosegarden 1:10.10-1 ProcVersionSignature: Ubuntu 2.6.38-8.42~ppa2-lowlatency 2.6.38.2 Uname: Linux 2.6.38-8-lowlatency x86_64 NonfreeKernelModules: nvidia Architecture: amd64 Date: Tue May 3 12:11:48 2011 InstallationMedia: Ubuntu-Studio 11.04 Natty Narwhal - Release amd64 (20110423) ProcEnviron: LANGUAGE=ja:en LANG=ja_JP.utf8 SHELL=/bin/bash SourcePackage: rosegarden UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: rosegarden (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty -- 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/mailman/listinfo/ubuntu-bugs
[Bug 776077] Re: Rosegarden should have the dependency with awesfx.
-- 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/mailman/listinfo/ubuntu-bugs
[Bug 769704] Re: Install doesn't proceed because of I/O error for floppy disk drive
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/769704 Title: Install doesn't proceed because of I/O error for floppy disk drive -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769704] Re: Install doesn't proceed because of I/O error for floppy disk drive
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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769704 Title: Install doesn't proceed because of I/O error for floppy disk drive -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 769704] [NEW] Install doesn't proceed because of I/O error for floppy disk drive
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 didn't proceed because of floppy disk drive issue. What I did: I enabled floppy disk drive in Bios function but don't use the drive, do not connect the drive. I ran installer and the installer was not proceeded just after DHCP detection. Then I move to text console to push F4 key. The text concole report end_request: I/O error, dev fd0, sector 0. I guess this is an issue of floppy disk drive. I reboot my system and went to bios section and change the setting to disable floppy disk drive. Then the installer proceeded. What I expected: I can install Ubuntu till maverick the same settings to enable floppy disk drive and without connecting it to my system. The installer should run as the same circumstanses. Error messages: end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 2 EXT3-fs (fd0): error: unable to read superblock end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 2 EXT2-fs (fd0): error: unable to read superblock end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 EXT4-fs (fd0): error: unable to read superblock attempt to access beyond end of device fd0: rw=0, want=66, limit=8 isofs_fill_super: bread failed, dev=fr0, iso_blknum=16, block=32 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 FAT (fd0): error: unable to read superblock end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 FAT (fd0): error: unable to read superblock end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 2 EXT3-fs (fd0): error: unable to read superblock end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 2 EXT2-fs (fd0): error: unable to read superblock end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 EXT4-fs (fd0): error: unable to read superblock attempt to access beyond end of device fd0: rw=0, want=66, limit=8 isofs_fill_super: bread failed, dev=fr0, iso_blknum=16, block=32 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 end_request: I/O error, dev fd0, sector 0 FAT (fd0): error: unable to read superblock EXT3-fs (sda1): error couldn't mount because of unsupported optional features (240) EXT2-fs (sda1): error couldn't mount because of unsupported optional features (240) EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: EXT3-fs (sda1): error couldn't mount because of unsupported optional features (240) EXT2-fs (sda1): error couldn't mount because of unsupported optional features (240) EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: Regards ** Affects: debian-installer (Ubuntu) Importance: Undecided Status: New ** Tags: iso-testing -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/769704 Title: Install doesn't proceed because of I/O error for floppy disk drive -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 703199] Re: The role of UbuntuStudio Control may end in Natty.
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 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/mailman/listinfo/ubuntu-bugs
[Bug 703199] [NEW] The role of UbuntuStudio Control may end in Natty.
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 for audio group, insert a line in /etc/udev/rules.d/60-raw1394.rules. 3. To enable memlock for audio group, insert a line in /etc/security/limits.conf. 4. To set nice value for audio group, insert a line in /etc/security/limits.conf. This settings allows the users in audio group to use firewire sound device with jackd and jackd can run more efficiently. Here, Natty uses kernel 2.6.37 and this kernel does not include old firewire stack such as ohci1394, ieee1394, raw1394 and so on. The new firewire stack called as Juju are included. But UbuntuStudio Controls still expect the existence of old firewire stack. And after lucid, in my memory, it's reccomended that the limits.conf settings should be in files under /etc/security/limits.d. In Natty, new firewire stack use /dev/fw* as its device node and libffado2 package install some configuration for these nodes in /etc/udev/60-ffado.rules. So we can use firewire sound device without ubuntustudio-controls's settings. And the nice value settings and memlock settings are optional. So I think the role of this software may end in Natty. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: ubuntustudio-controls 0.4.7build1 ProcVersionSignature: Ubuntu 2.6.37-12.26~ppa3-lowlatency 2.6.37 Uname: Linux 2.6.37-12-lowlatency i686 Architecture: i386 Date: Sat Jan 15 15:09:57 2011 InstallationMedia: Ubuntu-Studio 11.04 Natty Narwhal - Alpha i386 (20110112) PackageArchitecture: all ProcEnviron: LANGUAGE=ja_JP:ja:en_GB:en LANG=ja_JP.UTF-8 LC_MESSAGES=ja_JP.utf8 SHELL=/bin/bash SourcePackage: ubuntustudio-controls ** Affects: ubuntustudio-controls (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty -- 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/mailman/listinfo/ubuntu-bugs
[Bug 703199] Re: The role of UbuntuStudio Control may end in Natty.
-- 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/mailman/listinfo/ubuntu-bugs
[Bug 703199] Re: The role of UbuntuStudio Control may end in Natty.
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/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/mailman/listinfo/ubuntu-bugs
[Bug 688847] Re: [patch] startBristol process directly use sound device.
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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688847] Re: [patch] startBristol process directly use sound device.
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-operation to create the patch, maybe subtle copy mistake... I'm sorry for package mentainers to take more time just before your vacation... ** Patch added: Modified patch for audiodev issue https://bugs.launchpad.net/ubuntu/+source/monobristol/+bug/688847/+attachment/1771438/+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.net/bugs/688847 Title: [patch] startBristol process directly use sound device. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688847] [NEW] [patch] startBristol process directly use sound device.
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 opens default pcm device of ALSA. It's PulseAudio. Then we can see bristol pcm output in gnome-sound window. This is due to ALSA plugin of PulseAudio. In my opinion, application's direct access to sound device is not good. If one application directly use the sound device, the other application cannot use it and there is no possibility to mix sounds from different appications. To solve this issue, I attach 03_audiodev.patch. Thanks to include my patch #660627 and It's my glad if you include this audiodev patch to distributed package. Regards. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: monobristol 0.60.1-2~maverick1 ProcVersionSignature: Ubuntu 2.6.35-24.42-generic 2.6.35.8 Uname: Linux 2.6.35-24-generic i686 Architecture: i386 Date: Sat Dec 11 10:00:21 2010 InstallationMedia: Ubuntu-Studio 10.10 Maverick Meerkat - Beta i386 (20100902.1) PackageArchitecture: all ProcEnviron: LANGUAGE=ja_JP:ja:en LANG=ja_JP.utf8 SHELL=/bin/bash SourcePackage: monobristol ** Affects: monobristol (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug bristol i386 maverick monobristol startbristol -- 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 mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688847] Re: [patch] startBristol process directly use sound device.
** 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.net/bugs/688847 Title: [patch] startBristol process directly use sound device. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 688847] Re: [patch] startBristol process directly use sound device.
** 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 Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/688847 Title: [patch] startBristol process directly use sound device. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660627] [NEW] wrong parameter to open startBristol process [patch]
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: file:///home/mocchi/test/hoge/startBristol%20-alsa- alsa%20-mini: error opening location: Error stating file '/home/mocchi/test/hoge/startBristol -alsa-alsa -mini': No such file or directory To refer to this developer document, the sigle parameter show the file path, not path with parameters. http://msdn.microsoft.com/en-us/library/53ezey2s%28v=VS.80%29.aspx There is a need to give two parameters to start method, not one parameter. http://msdn.microsoft.com/en-us/library/h6ak8zt5%28v=VS.80%29.aspx So I change the code below. Here I define startBristol as /usr/lib/startBristol in advance. System.Diagnostics.Process.Start (startBristol, param+ -mini); Then I got no error. Would you include this bug fix? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: monobristol 0.60.1-1 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Fri Oct 15 01:02:21 2010 InstallationMedia: Ubuntu-Studio 10.10 Maverick Meerkat - Beta i386 (20100902.1) PackageArchitecture: all ProcEnviron: LANGUAGE=ja_JP:ja:en LANG=ja_JP.utf8 SHELL=/bin/bash SourcePackage: monobristol ** Affects: monobristol (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 maverick monobristol -- wrong parameter to open startBristol process [patch] https://bugs.launchpad.net/bugs/660627 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 660627] Re: wrong parameter to open startBristol process [patch]
** 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 parameters. In this case, one of parameter is mini. + 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: file:///home/mocchi/test/hoge/startBristol%20-alsa-alsa%20-mini: error opening location: Error stating file '/home/mocchi/test/hoge/startBristol -alsa-alsa -mini': No such file or directory - To refer to this developer document, the sigle parameter show the file path, not path with parameters. + gvfs-open: file:///home/mocchi/test/hoge/startBristol%20-alsa- + alsa%20-mini: error opening location: Error stating file + '/home/mocchi/test/hoge/startBristol -alsa-alsa -mini': No such file or + directory + + To refer to this developer document, the sigle parameter show the file + path, not path with parameters. + http://msdn.microsoft.com/en-us/library/53ezey2s%28v=VS.80%29.aspx - There is a need to give two parameters to start method, not one parameter. + There is a need to give two parameters to start method, not one + parameter. + http://msdn.microsoft.com/en-us/library/h6ak8zt5%28v=VS.80%29.aspx - So I change the code below. Here I define startBristol as /usr/lib/startBristol in advance. + So I change the code below. Here I define startBristol as + /usr/lib/startBristol in advance. + System.Diagnostics.Process.Start (startBristol, param+ -mini); Then I got no error. Would you include this bug fix? ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: monobristol 0.60.1-1 ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Fri Oct 15 01:02:21 2010 InstallationMedia: Ubuntu-Studio 10.10 Maverick Meerkat - Beta i386 (20100902.1) PackageArchitecture: all ProcEnviron: - LANGUAGE=ja_JP:ja:en - LANG=ja_JP.utf8 - SHELL=/bin/bash + LANGUAGE=ja_JP:ja:en + LANG=ja_JP.utf8 + SHELL=/bin/bash SourcePackage: monobristol -- wrong parameter to open startBristol process [patch] https://bugs.launchpad.net/bugs/660627 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 623615] Re: /dev/dsp on Ubuntu Studio is not enabled read/write for all, so GTick does not work
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 does not work https://bugs.launchpad.net/bugs/623615 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649583] [NEW] MOTU 828 Mk2 works but the sound is noisy, like buzzing.
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 this is a result of developer's great work of reverse engineering. I hope this device works good in marveric. IEEE13994 chipset $ lspci FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) $ ffado-test ListDevices --- FFADO test and diagnostic utility Part of the FFADO project -- www.ffado.org Version: 2.999.0- (C) 2008, Daniel Wagner, Pieter Palmers This program comes with ABSOLUTELY NO WARRANTY. --- === 1394 PORT 0 === Node id GUID VendorId ModelId Vendor - Model 0 0x0001f201480f 0x01F2 0x00101800- 1 0x001d72ff883f4aff 0x1D72 0x Linux - ohci1394 - no message buffer overruns $ ffado-diag FFADO diagnostic utility 2.999.0- (C) 2008 Pieter Palmers === CHECK === Base system... kernel version 2.6.35-22-generic FIXME: implement test for RT kernel RT patched... False old 1394 stack present True old 1394 stack loaded. True old 1394 stack active. True new 1394 stack present True new 1394 stack loaded. False new 1394 stack active. False /dev/raw1394 node present. True /dev/raw1394 permissions.. True Prerequisites (dynamic at run-time)... gcc ... gcc (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5 g++ ... g++ (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5 PyQt4 (by pyuic4) . sh: pyuic4: not found jackd . no message buffer overruns path /usr/bin/jackd flags ... -ljack libraw1394 2.0.5 flags ... -lraw1394 libavc1394 Package libavc1394 was not found in the pkg-config search path. Perhaps you should add the directory containing `libavc1394.pc' to the PKG_CONFIG_PATH environment variable No package 'libavc1394' found flags ... Package libavc1394 was not found in the pkg-config search path. Perhaps you should add the directory containing `libavc1394.pc' to the PKG_CONFIG_PATH environment variable No package 'libavc1394' found libiec61883 ... Package libiec61883 was not found in the pkg-config search path. Perhaps you should add the directory containing `libiec61883.pc' to the PKG_CONFIG_PATH environment variable No package 'libiec61883' found flags ... Package libiec61883 was not found in the pkg-config search path. Perhaps you should add the directory containing `libiec61883.pc' to the PKG_CONFIG_PATH environment variable No package 'libiec61883' found libxml++-2.6 .. Package libxml++-2.6 was not found in the pkg-config search path. Perhaps you should add the directory containing `libxml++-2.6.pc' to the PKG_CONFIG_PATH environment variable No package 'libxml++-2.6' found flags ... Package libxml++-2.6 was not found in the pkg-config search path. Perhaps you should add the directory containing `libxml++-2.6.pc' to the PKG_CONFIG_PATH environment variable No package 'libxml++-2.6' found dbus-1 1.4.0 flags ... -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -L/lib -ldbus-1 -lpthread -lrt Prerequisites (static at compile-time)... gcc ... gcc (Ubuntu/Linaro 4.4.4-8ubuntu1) 4.4.5 20100728 (prerelease) g++ ... g++ (Ubuntu/Linaro 4.4.4-8ubuntu1) 4.4.5 20100728 (prerelease) PyQt4 (by pyuic4) . Python User Interface Compiler 4.7.4 for Qt version 4.7.0 jackd . sh: jackd: not found path flags ... Package jack was not found in the pkg-config search path. libraw1394 2.0.5 flags ... -lraw1394 libavc1394 Package libavc1394 was not found in the pkg-config search path. flags ... Package libavc1394 was not found in the pkg-config search path. libiec61883 ... 1.2.0 flags ... -liec61883 -lraw1394 libxml++-2.6 .. 2.30.0 flags ... -pthread -I/usr/include/libxml++-2.6 -I/usr/lib/libxml++-2.6/include -I/usr/include/libxml2 -I/usr/include/glibmm-2.4 -I/usr/lib/glibmm-2.4/include -I/usr/include/sigc++-2.0 -I/usr/lib/sigc++-2.0/include -I/usr/include/glib-2.0 -I/usr/lib/glib-2.0/include -pthread -lxml++-2.6 -lxml2 -lglibmm-2.4 -lgobject-2.0 -lsigc-2.0 -lgthread-2.0 -lrt -lglib-2.0 dbus-1 1.2.24 flags ... -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include -L/lib -ldbus-1 -lpthread -lrt Hardware... Host controllers: 05:00.1 FireWire (IEEE 1394) [0c00]: Ricoh Co Ltd R5C832 IEEE 1394 Controller [1180:0832] (rev 04) (prog-if 10 [OHCI]) Subsystem: Lenovo Device [17aa:20c7]
[Bug 649583] Re: MOTU 828 Mk2 works but the sound is noisy, like buzzing.
** 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 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 this is a result of developer's great work of reverse engineering. I hope this device works good in marveric. + + IEEE13994 chipset + $ lspci + FireWire (IEEE 1394): Ricoh Co Ltd R5C832 IEEE 1394 Controller (rev 04) $ ffado-test ListDevices --- FFADO test and diagnostic utility Part of the FFADO project -- www.ffado.org Version: 2.999.0- (C) 2008, Daniel Wagner, Pieter Palmers This program comes with ABSOLUTELY NO WARRANTY. --- === 1394 PORT 0 === - Node id GUID VendorId ModelId Vendor - Model -0 0x0001f201480f 0x01F2 0x00101800- -1 0x001d72ff883f4aff 0x1D72 0x Linux - ohci1394 - + Node id GUID VendorId ModelId Vendor - Model + 0 0x0001f201480f 0x01F2 0x00101800- + 1 0x001d72ff883f4aff 0x1D72 0x Linux - ohci1394 - no message buffer overruns - $ ffado-diag FFADO diagnostic utility 2.999.0- (C) 2008 Pieter Palmers - === CHECK === - Base system... - kernel version 2.6.35-22-generic + Base system... + kernel version 2.6.35-22-generic FIXME: implement test for RT kernel -RT patched... False - old 1394 stack present True - old 1394 stack loaded. True - old 1394 stack active. True - new 1394 stack present True - new 1394 stack loaded. False - new 1394 stack active. False - /dev/raw1394 node present. True - /dev/raw1394 permissions.. True - Prerequisites (dynamic at run-time)... -gcc ... gcc (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5 -g++ ... g++ (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5 -PyQt4 (by pyuic4) . sh: pyuic4: not found -jackd . no message buffer overruns - path /usr/bin/jackd - flags ... -ljack -libraw1394 2.0.5 - flags ... -lraw1394 -libavc1394 Package libavc1394 was not found in the pkg-config search path. + RT patched... False + old 1394 stack present True + old 1394 stack loaded. True + old 1394 stack active. True + new 1394 stack present True + new 1394 stack loaded. False + new 1394 stack active. False + /dev/raw1394 node present. True + /dev/raw1394 permissions.. True + Prerequisites (dynamic at run-time)... + gcc ... gcc (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5 + g++ ... g++ (Ubuntu/Linaro 4.4.4-14ubuntu5) 4.4.5 + PyQt4 (by pyuic4) . sh: pyuic4: not found + jackd . no message buffer overruns + path /usr/bin/jackd + flags ... -ljack + libraw1394 2.0.5 + flags ... -lraw1394 + libavc1394 Package libavc1394 was not found in the pkg-config search path. Perhaps you should add the directory containing `libavc1394.pc' to the PKG_CONFIG_PATH environment variable No package 'libavc1394' found - flags ... Package libavc1394 was not found in the pkg-config search path. + flags ... Package libavc1394 was not found in the pkg-config search path. Perhaps you should add the directory containing `libavc1394.pc' to the PKG_CONFIG_PATH environment variable No package 'libavc1394' found -libiec61883 ... Package libiec61883 was not found in the pkg-config search path. + libiec61883 ... Package libiec61883 was not found in the pkg-config search path. Perhaps you should add the directory containing `libiec61883.pc' to the PKG_CONFIG_PATH environment variable No package 'libiec61883' found - flags ... Package libiec61883 was not found in the pkg-config search path. + flags ... Package libiec61883 was not found in the pkg-config search path. Perhaps you should add the directory containing `libiec61883.pc' to the PKG_CONFIG_PATH environment variable No package 'libiec61883' found -libxml++-2.6 .. Package libxml++-2.6 was not found in the pkg-config search path. + libxml++-2.6 .. Package libxml++-2.6 was not found in the pkg-config search path. Perhaps you should add the directory containing `libxml++-2.6.pc' to the PKG_CONFIG_PATH environment variable No package 'libxml++-2.6' found - flags ... Package libxml++-2.6 was not found in the pkg-config search path. +
[Bug 649542] [NEW] New firewire stack makes more FFADO XRUNs than old firewire stack.
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 ffado-dbus-server 2.0.1+svn1856-1ubuntu1 FFADO D-Bus server ii ffado-mixer-qt42.0.1+svn1856-1ubuntu1 FFADO D-Bus mixer applets (QT4) ii ffado-tools 2.0.1+svn1856-1ubuntu1 FFADO debugging and firmware tools ii libffado2 2.0.1+svn1856-1ubuntu1 FFADO API At first, the kernel modules for this device is New Firewire Stack (so-called by FFADO developer), firewire_ohci, firewire_core and crc_itu_t. Then I get much FFADO XRuns, Secondly I use Old Firewire Stack, ohci1394, raw1394, ieee1394 with the commands of rmmod and modprobe, these modules are standard in Lucid. Then I got a few FFADO XRUNs. In both ways, I play the same music in the same sequencer. In detail, please refer to the logs of ffado-diag and jackd -v I'LL attach. The _old means the old firewire stack and the _new means new one. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: libffado2 2.0.1+svn1856-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4 Uname: Linux 2.6.35-22-generic i686 Architecture: i386 Date: Tue Sep 28 13:22:50 2010 InstallationMedia: Ubuntu-Studio 10.10 Maverick Meerkat - Beta i386 (20100902.1) ProcEnviron: LANG=ja_JP.utf8 SHELL=/bin/bash SourcePackage: libffado ** Affects: libffado (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug audio ffado firewire i386 jackd maverick sound -- New firewire stack makes more FFADO XRUNs than old firewire stack. https://bugs.launchpad.net/bugs/649542 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649542] Re: New firewire stack makes more FFADO XRUNs than old firewire stack.
** 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 XRUNs than old firewire stack. https://bugs.launchpad.net/bugs/649542 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649542] Re: New firewire stack makes more FFADO XRUNs than old firewire stack.
** 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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649542] Re: New firewire stack makes more FFADO XRUNs than old firewire stack.
** 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 this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 649542] Re: New firewire stack makes more FFADO XRUNs than old firewire stack.
** 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 received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644130] Re: JackAudioDriver::ProcessAsync: read error, skip cycle with firewire driver
*** 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.net/ubuntu/+source/libffado/+bug/649542/+subscribe -- JackAudioDriver::ProcessAsync: read error, skip cycle with firewire driver https://bugs.launchpad.net/bugs/644130 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 644130] [NEW] JackAudioDriver::ProcessAsync: read error, skip cycle with firewire driver
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:22:50.917 Patchbay deactivated. 15:22:50.926 Statistics reset. 15:22:50.987 JACK is starting... 15:22:50.987 /usr/bin/jackd -r -dfirewire -r48000 -p256 -n2 Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started Cannot connect to server socket err = No such file or directory Cannot connect to server socket jack server is not running or cannot be started Cannot create thread 1 Operation not permitted 15:22:51.053 ALSA connection graph change. 15:22:51.054 JACK was started with PID=1790. Cannot create thread 1 Operation not permitted jackdmp 1.9.6 Copyright 2001-2005 Paul Davis and others. Copyright 2004-2010 Grame. jackdmp comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK server starting in non-realtime mode Cannot lock down memory area (Cannot allocate memory) Cannot create thread 1 Operation not permitted ERROR: messagebuffer not initialized: 00052193720: (ffado.cpp)[ 92] ffado_streaming_init: libffado 2.999.0- built Aug 11 2010 00:12:04 15:22:51.219 ALSA connection change. 15:22:51.246 ALSA connection graph change. 15:22:56.972 Server configuration saved to /home/mocchi/.jackdrc. 15:22:56.972 Statistics reset. 15:22:56.980 Client activated. 15:22:56.985 JACK connection change. 15:22:56.991 JACK connection graph change. Cannot lock down memory area (Cannot allocate memory) 15:22:57.778 XRUN callback (1). JackAudioDriver::ProcessAsync: read error, skip cycle JackPosixMutex::Unlock res = 1 15:22:58.998 XRUN callback (2). JackAudioDriver::ProcessAsync: read error, skip cycle JackPosixMutex::Unlock res = 1 (Repeat these messages above) (Here I click the stop button of qjackctl) jack main caught signal 15 *** glibc detected *** /usr/bin/jackd: double free or corruption (!prev): 0x08efde20 *** === Backtrace: = /lib/libc.so.6(+0x6c501)[0x289501] /lib/libc.so.6(+0x6dd70)[0x28ad70] /lib/libc.so.6(cfree+0x6d)[0x28de5d] /usr/lib/libraw1394.so.11(fw_destroy_handle+0x82)[0x4b24a2] /usr/lib/libraw1394.so.11(raw1394_destroy_handle+0x53)[0x4b12c3] /usr/lib/libffado.so.2(_ZN17IsoHandlerManager10IsoHandler7disableEv+0x1f6)[0x106e294] /usr/lib/libffado.so.2(_ZN17IsoHandlerManager10IsoHandler11updateStateEv+0x146)[0x106e59c] /usr/lib/libffado.so.2(_ZN17IsoHandlerManager7IsoTask21updateShadowMapHelperEv+0x123)[0x1067551] /usr/lib/libffado.so.2(_ZN17IsoHandlerManager7IsoTask7ExecuteEv+0x159)[0x10678c9] /usr/lib/libffado.so.2(_ZN4Util11PosixThread13ThreadHandlerEPv+0x18c)[0x1096fd0] /lib/libpthread.so.0(+0x5cc9)[0x8a8cc9] /lib/libc.so.6(clone+0x5e)[0x2ed6ae] === Memory map: 00113000-00114000 r-xp 08:01 1063062/usr/lib/libX11-xcb.so.1.0.0 00114000-00115000 r--p 08:01 1063062/usr/lib/libX11-xcb.so.1.0.0 00115000-00116000 rw-p 1000 08:01 1063062/usr/lib/libX11-xcb.so.1.0.0 00116000-0012b000 r-xp 08:01 1062988/usr/lib/libICE.so.6.3.0 0012b000-0012c000 r--p 00014000 08:01 1062988/usr/lib/libICE.so.6.3.0 0012c000-0012d000 rw-p 00015000 08:01 1062988/usr/lib/libICE.so.6.3.0 0012d000-0012f000 rw-p 00:00 0 0012f000-00132000 r-xp 08:01 919421 /lib/libuuid.so.1.3.0 00132000-00133000 r--p 2000 08:01 919421 /lib/libuuid.so.1.3.0 00133000-00134000 rw-p 3000 08:01 919421 /lib/libuuid.so.1.3.0 00134000-00138000 r-xp 08:01 1062876/usr/lib/libXdmcp.so.6.0.0 00138000-00139000 r--p 3000 08:01 1062876/usr/lib/libXdmcp.so.6.0.0 00139000-0013a000 rw-p 4000 08:01 1062876/usr/lib/libXdmcp.so.6.0.0 0013a000-00141000 r-xp 08:01 923803 /lib/libwrap.so.0.7.6 00141000-00142000 r--p 6000 08:01 923803 /lib/libwrap.so.0.7.6 00142000-00143000 rw-p 7000 08:01 923803 /lib/libwrap.so.0.7.6 00143000-0014c000 r-xp 08:01 1200395/usr/lib/jack/jack_firewire.so 0014c000-0014d000 r--p 8000 08:01 1200395/usr/lib/jack/jack_firewire.so 0014d000-0014e000 rw-p 9000 08:01 1200395/usr/lib/jack/jack_firewire.so 0014e000-00151000 r-xp 08:01 1051955 /usr/lib/libgthread-2.0.so.0.2515.0 00151000-00152000 r--p 3000 08:01 1051955 /usr/lib/libgthread-2.0.so.0.2515.0 00152000-00153000 rw-p 4000 08:01 1051955 /usr/lib/libgthread-2.0.so.0.2515.0 00154000-00157000 r-xp 08:01 1063705/usr/lib/libxcb-atom.so.1.0.0 00157000-00158000 r--p 2000 08:01 1063705/usr/lib/libxcb-atom.so.1.0.0 00158000-00159000 rw-p 3000 08:01 1063705/usr/lib/libxcb-atom.so.1.0.0 00159000-0016c000 r-xp 08:01 924247 /lib/libnsl-2.12.1.so
[Bug 644130] Re: JackAudioDriver::ProcessAsync: read error, skip cycle with firewire driver
** 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://bugs.launchpad.net/bugs/644130/+attachment/1616840/+files/ProcStatus.txt -- JackAudioDriver::ProcessAsync: read error, skip cycle with firewire driver https://bugs.launchpad.net/bugs/644130 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 636159] [NEW] Qsampler crashed by segmentation fault
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 initialized (2615) KSharedDataCache::Private::mapSharedMemory: Cache fully initialized -- attached to memory mapping (2615) KSharedDataCache::Private::mapSharedMemory: 5378048 bytes available out of 10485760 Segmentation fault (core dumped) $ dmesg [ 1081.886592] qsampler[2615]: segfault at 2b0 ip 7f3a741ed648 sp 7fff688a14d0 error 4 in libQtGui.so.4.7.0[7f3a73aeb000+a9e000] I build liblinuxsampler and linuxsampler by my own from its official website. $ dpkg -l | grep sampler ii gigedit 0.2.0-1~exp1 instrument editor for Gigasampler files ii libgig6 3.3.0-1 library for loading and modifying Gigasampler and DLS files ii liblinuxsampler 1.0.0-1ubuntu1 realtime audio sampler (base library) ii linuxsampler 1.0.0-1ubuntu1 realtime audio sampler ii qsampler 0.2.2-2 LinuxSampler GUI frontend based on the Qt toolkit Current version of qt4 is 4.7.0~rc1-1ubuntu2. ProblemType: Bug DistroRelease: Ubuntu 10.10 Package: qsampler 0.2.2-2 ProcVersionSignature: Ubuntu 2.6.35-20.29-generic 2.6.35.4 Uname: Linux 2.6.35-20-generic x86_64 Architecture: amd64 Date: Sun Sep 12 12:56:43 2010 ExecutablePath: /usr/bin/qsampler InstallationMedia: Ubuntu-Studio 10.04 Lucid Lynx - Alpha amd64 (20100322) ProcEnviron: SHELL=/bin/bash LANG=ja_JP.utf8 SourcePackage: qsampler ** Affects: qsampler (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug maverick -- Qsampler crashed by segmentation fault https://bugs.launchpad.net/bugs/636159 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 636159] Re: Qsampler crashed by segmentation fault
** 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://bugs.launchpad.net/bugs/636159/+attachment/1572891/+files/ProcStatus.txt ** Attachment added: XsessionErrors.txt https://bugs.launchpad.net/bugs/636159/+attachment/1572892/+files/XsessionErrors.txt -- Qsampler crashed by segmentation fault https://bugs.launchpad.net/bugs/636159 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595599] [NEW] the wrong order of arguments in progress_callback function of plymouth script
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 (time) at first and progress
secondly in ubuntustudio-logo.script.
I change these arguments on lucid and marveric, but the plymouth splash
does not work good. It looks too short to show the splash between it
appears and GDM appears. I change this function below but it's not good.
fun progress_callback (progress, duration)
{
if (Plymouth.GetMode () == boot || unknown)
{
if (progress 1)
{
progress_bar.image = progress_bar.original_image.Scale
(progress_bar.original_image.GetWidth (progress_bar.original_image) * progress,
progress_bar.original_image.GetHeight ());
}
else
{
progress_bar.image = progress_bar.original_image.Scale
(progress_bar.original_image.GetWidth (progress_bar.original_image),
progress_bar.original_image.GetHeight ());
}
}
else
{
if (progress 1)
{
progress_bar.image = progress_bar.original_image.Scale
(progress_bar.original_image.GetWidth (progress_bar.original_image) * (1 -
progress), progress_bar.original_image.GetHeight ());
}
else
{
progress_bar.image = progress_bar.original_image.Scale (0,
progress_bar.original_image.GetHeight ());
}
}
progress_bar.sprite.SetImage (progress_bar.image);
return;
}
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: plymouth-theme-ubuntustudio 0.38.3
ProcVersionSignature: Ubuntu 2.6.32-23.37-preempt 2.6.32.15+drm33.5
Uname: Linux 2.6.32-23-preempt x86_64
Architecture: amd64
Date: Fri Jun 18 01:54:58 2010
InstallationMedia: Ubuntu-Studio 10.04 Lucid Lynx - Alpha amd64 (20100322)
PackageArchitecture: all
ProcEnviron:
LANG=ja_JP.utf8
SHELL=/bin/bash
SourcePackage: ubuntustudio-look
** Affects: ubuntustudio-look (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug lucid
--
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, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 595599] Re: the wrong order of arguments in progress_callback function of plymouth script
** 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, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569294] Re: Waltop Tablet works but it indicates the absolute point only holding the buttons
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 TopY 120 Option BottomX 9920 Option BottomY 6200 Driver wizardpen EndSection I wonder why it doesn't work good if I uninstall xserver-xorg-input-waltop. I hope xserver-xorg-input-wacom includes the support for this waltop tablet. And for other guys, would you please report the result of applying this tips? Regards -- Waltop Tablet works but it indicates the absolute point only holding the buttons https://bugs.launchpad.net/bugs/569294 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569294] Re: Waltop Tablet works but it indicates the absolute point only holding the buttons
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 buttons https://bugs.launchpad.net/bugs/569294 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 392825] Re: WALTOP tablets not supported anymore
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 from Genius, KYE Systems Corp., Slim Tablet 12.1 inch USb Tablet from Aiptek, Inc., PTB-ST12 from Princeton Tech., etc etc. -- WALTOP tablets not supported anymore https://bugs.launchpad.net/bugs/392825 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569294] Re: 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: 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 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. The - cursor moves to the absolute point where the pen located on the tablet - pad + I hope my Waltop pen tablet works fine. (Slim Tablet 12.1 inch, + http://www.waltop.com.tw/productDetail.asp?id=21). This tablet is + rebranded and some company produces other name such as G-Pen F610 from + Genius, KYE Systems Corp., Slim Tablet 12.1 inch USb Tablet from Aiptek, + Inc., PTB-ST12 from Princeton Tech. + + But it's not good on lucid. Just after the tablet plugged in, it works + fine. The cursor moves to the absolute point where the pen located on + the tablet pad But once pushing some button, the pointer doesn't move on the display when moving the tablet pen. Then I push some button of the tablet pen, the pointer is shown at the absolute point of the tablet pad. Then the cursor moves only holding the button of the tablet pen. xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ ... ⎜ ↳ WALTOP International Corp. Slim Tablet id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ... Xorg.0.log (II) config/udev: Adding input device WALTOP International Corp. Slim Tablet (/dev/input/mouse2) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device WALTOP International Corp. Slim Tablet (/dev/input/event9) (**) WALTOP International Corp. Slim Tablet: Applying InputClass evdev pointer catchall (**) WALTOP International Corp. Slim Tablet: Applying InputClass evdev tablet catchall (**) WALTOP International Corp. Slim Tablet: always reports core events (**) WALTOP International Corp. Slim Tablet: Device: /dev/input/event9 (II) WALTOP International Corp. Slim Tablet: Found 9 mouse buttons (II) WALTOP International Corp. Slim Tablet: Found scroll wheel(s) (II) WALTOP International Corp. Slim Tablet: Found relative axes (II) WALTOP International Corp. Slim Tablet: Found x and y relative axes (II) WALTOP International Corp. Slim Tablet: Found absolute axes (II) WALTOP International Corp. Slim Tablet: Found x and y absolute axes (II) WALTOP International Corp. Slim Tablet: Found absolute tablet. (II) WALTOP International Corp. Slim Tablet: Configuring as tablet (**) WALTOP International Corp. Slim Tablet: YAxisMapping: buttons 4 and 5 (**) WALTOP International Corp. Slim Tablet: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device WALTOP International Corp. Slim Tablet (type: TABLET) (WW) WALTOP International Corp. Slim Tablet: touchpads, tablets and touchscreens ignore relative axes. (II) WALTOP International Corp. Slim Tablet: initialized for absolute axes. kern.log Apr 24 12:39:11 7675A63 kernel: [ 641.609180] usb 4-1: new full speed USB device using uhci_hcd and address 2 Apr 24 12:39:11 7675A63 kernel: [ 641.772453] usb 4-1: configuration #1 chosen from 1 choice Apr 24 12:39:11 7675A63 kernel: [ 641.892819] usbcore: registered new interface driver hiddev Apr 24 12:39:11 7675A63 kernel: [ 641.901314] input: WALTOP International Corp. Slim Tablet as /devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.0/input/input9 Apr 24 12:39:11 7675A63 kernel: [ 641.901456] generic-usb 0003:172F:0031.0001: input,hidraw0: USB HID v1.10 Mouse [WALTOP International Corp. Slim Tablet] on usb-:00:1a.1-1/input0 Apr 24 12:39:11 7675A63 kernel: [ 641.901490] usbcore: registered new interface driver usbhid Apr 24 12:39:11 7675A63 kernel: [ 641.901500] usbhid: v2.6:USB HID core driver syslog Apr 24 12:39:11 7675A63 kernel: [ 641.609180] usb 4-1: new full speed USB device using uhci_hcd and address 2 Apr 24 12:39:11 7675A63 kernel: [ 641.772453] usb 4-1: configuration #1 chosen from 1 choice Apr 24 12:39:11 7675A63 kernel: [ 641.892819] usbcore: registered new interface driver hiddev Apr 24 12:39:11 7675A63 kernel: [ 641.901314] input: WALTOP International Corp. Slim Tablet as /devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.0/input/input9 Apr 24 12:39:11 7675A63 kernel: [ 641.901456] generic-usb 0003:172F:0031.0001: input,hidraw0: USB HID v1.10 Mouse [WALTOP International Corp. Slim Tablet] on usb-:00:1a.1-1/input0 Apr 24 12:39:11 7675A63 kernel: [ 641.901490] usbcore: registered new interface driver usbhid Apr 24 12:39:11 7675A63 kernel: [ 641.901500] usbhid: v2.6:USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 10.04 Package:
[Bug 569294] [NEW] Waltop Tablet works but it indicates the absolute point only holding the buttons
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. The cursor moves to the absolute point where the pen located on the tablet pad But once pushing some button, the pointer doesn't move on the display when moving the tablet pen. Then I push some button of the tablet pen, the pointer is shown at the absolute point of the tablet pad. Then the cursor moves only holding the button of the tablet pen. xinput --list ⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ ... ⎜ ↳ WALTOP International Corp. Slim Tabletid=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ... Xorg.0.log (II) config/udev: Adding input device WALTOP International Corp. Slim Tablet (/dev/input/mouse2) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device WALTOP International Corp. Slim Tablet (/dev/input/event9) (**) WALTOP International Corp. Slim Tablet: Applying InputClass evdev pointer catchall (**) WALTOP International Corp. Slim Tablet: Applying InputClass evdev tablet catchall (**) WALTOP International Corp. Slim Tablet: always reports core events (**) WALTOP International Corp. Slim Tablet: Device: /dev/input/event9 (II) WALTOP International Corp. Slim Tablet: Found 9 mouse buttons (II) WALTOP International Corp. Slim Tablet: Found scroll wheel(s) (II) WALTOP International Corp. Slim Tablet: Found relative axes (II) WALTOP International Corp. Slim Tablet: Found x and y relative axes (II) WALTOP International Corp. Slim Tablet: Found absolute axes (II) WALTOP International Corp. Slim Tablet: Found x and y absolute axes (II) WALTOP International Corp. Slim Tablet: Found absolute tablet. (II) WALTOP International Corp. Slim Tablet: Configuring as tablet (**) WALTOP International Corp. Slim Tablet: YAxisMapping: buttons 4 and 5 (**) WALTOP International Corp. Slim Tablet: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device WALTOP International Corp. Slim Tablet (type: TABLET) (WW) WALTOP International Corp. Slim Tablet: touchpads, tablets and touchscreens ignore relative axes. (II) WALTOP International Corp. Slim Tablet: initialized for absolute axes. kern.log Apr 24 12:39:11 7675A63 kernel: [ 641.609180] usb 4-1: new full speed USB device using uhci_hcd and address 2 Apr 24 12:39:11 7675A63 kernel: [ 641.772453] usb 4-1: configuration #1 chosen from 1 choice Apr 24 12:39:11 7675A63 kernel: [ 641.892819] usbcore: registered new interface driver hiddev Apr 24 12:39:11 7675A63 kernel: [ 641.901314] input: WALTOP International Corp. Slim Tablet as /devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.0/input/input9 Apr 24 12:39:11 7675A63 kernel: [ 641.901456] generic-usb 0003:172F:0031.0001: input,hidraw0: USB HID v1.10 Mouse [WALTOP International Corp. Slim Tablet] on usb-:00:1a.1-1/input0 Apr 24 12:39:11 7675A63 kernel: [ 641.901490] usbcore: registered new interface driver usbhid Apr 24 12:39:11 7675A63 kernel: [ 641.901500] usbhid: v2.6:USB HID core driver syslog Apr 24 12:39:11 7675A63 kernel: [ 641.609180] usb 4-1: new full speed USB device using uhci_hcd and address 2 Apr 24 12:39:11 7675A63 kernel: [ 641.772453] usb 4-1: configuration #1 chosen from 1 choice Apr 24 12:39:11 7675A63 kernel: [ 641.892819] usbcore: registered new interface driver hiddev Apr 24 12:39:11 7675A63 kernel: [ 641.901314] input: WALTOP International Corp. Slim Tablet as /devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.0/input/input9 Apr 24 12:39:11 7675A63 kernel: [ 641.901456] generic-usb 0003:172F:0031.0001: input,hidraw0: USB HID v1.10 Mouse [WALTOP International Corp. Slim Tablet] on usb-:00:1a.1-1/input0 Apr 24 12:39:11 7675A63 kernel: [ 641.901490] usbcore: registered new interface driver usbhid Apr 24 12:39:11 7675A63 kernel: [ 641.901500] usbhid: v2.6:USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-input-wacom 1:0.10.5-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-preempt 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-preempt x86_64 Architecture: amd64 Date: Sat Apr 24 13:13:51 2010 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu-Studio 10.04 Lucid Lynx - Alpha amd64 (20100322) MachineType: LENOVO 7675A63 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-preempt root=UUID=1c334b52-a73f-4fea-8fb6-f31810378c15 ro quiet splash ProcEnviron: LANG=ja_JP.utf8 SHELL=/bin/bash SourcePackage: xf86-input-wacom dmi.bios.date: 10/09/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETC1WW (2.21 ) dmi.board.name: 7675A63
[Bug 569294] Re: Waltop Tablet works but it indicates the point holding the buttons
** 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 ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/45142715/GdmLog.txt ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/45142716/GdmLog1.txt ** Attachment added: GdmLog2.txt http://launchpadlibrarian.net/45142718/GdmLog2.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/45142719/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/45142720/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/45142721/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/45142722/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/45142724/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/45142725/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/45142726/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/45142727/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/45142728/UdevLog.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/45142729/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/45142730/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/45142731/Xrandr.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/45142732/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/45142733/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/45142734/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/45142735/xkbcomp.txt -- Waltop Tablet works but it indicates the absolute point only holding the buttons https://bugs.launchpad.net/bugs/569294 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 569294] Re: Waltop Tablet works but it indicates the absolute point only holding the buttons
** 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: 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 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. The cursor moves to the absolute point where the pen located on the tablet pad But once pushing some button, the pointer doesn't move on the display when moving the tablet pen. Then I push some button of the tablet pen, the pointer is shown at the absolute point of the tablet pad. Then the cursor moves only holding the button of the tablet pen. xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ ... ⎜ ↳ WALTOP International Corp. Slim Tablet id=13 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ... Xorg.0.log (II) config/udev: Adding input device WALTOP International Corp. Slim Tablet (/dev/input/mouse2) (II) No input driver/identifier specified (ignoring) (II) config/udev: Adding input device WALTOP International Corp. Slim Tablet (/dev/input/event9) (**) WALTOP International Corp. Slim Tablet: Applying InputClass evdev pointer catchall (**) WALTOP International Corp. Slim Tablet: Applying InputClass evdev tablet catchall (**) WALTOP International Corp. Slim Tablet: always reports core events (**) WALTOP International Corp. Slim Tablet: Device: /dev/input/event9 (II) WALTOP International Corp. Slim Tablet: Found 9 mouse buttons (II) WALTOP International Corp. Slim Tablet: Found scroll wheel(s) (II) WALTOP International Corp. Slim Tablet: Found relative axes (II) WALTOP International Corp. Slim Tablet: Found x and y relative axes (II) WALTOP International Corp. Slim Tablet: Found absolute axes (II) WALTOP International Corp. Slim Tablet: Found x and y absolute axes (II) WALTOP International Corp. Slim Tablet: Found absolute tablet. (II) WALTOP International Corp. Slim Tablet: Configuring as tablet (**) WALTOP International Corp. Slim Tablet: YAxisMapping: buttons 4 and 5 (**) WALTOP International Corp. Slim Tablet: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200 (II) XINPUT: Adding extended input device WALTOP International Corp. Slim Tablet (type: TABLET) (WW) WALTOP International Corp. Slim Tablet: touchpads, tablets and touchscreens ignore relative axes. (II) WALTOP International Corp. Slim Tablet: initialized for absolute axes. kern.log Apr 24 12:39:11 7675A63 kernel: [ 641.609180] usb 4-1: new full speed USB device using uhci_hcd and address 2 Apr 24 12:39:11 7675A63 kernel: [ 641.772453] usb 4-1: configuration #1 chosen from 1 choice Apr 24 12:39:11 7675A63 kernel: [ 641.892819] usbcore: registered new interface driver hiddev Apr 24 12:39:11 7675A63 kernel: [ 641.901314] input: WALTOP International Corp. Slim Tablet as /devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.0/input/input9 Apr 24 12:39:11 7675A63 kernel: [ 641.901456] generic-usb 0003:172F:0031.0001: input,hidraw0: USB HID v1.10 Mouse [WALTOP International Corp. Slim Tablet] on usb-:00:1a.1-1/input0 Apr 24 12:39:11 7675A63 kernel: [ 641.901490] usbcore: registered new interface driver usbhid Apr 24 12:39:11 7675A63 kernel: [ 641.901500] usbhid: v2.6:USB HID core driver syslog Apr 24 12:39:11 7675A63 kernel: [ 641.609180] usb 4-1: new full speed USB device using uhci_hcd and address 2 Apr 24 12:39:11 7675A63 kernel: [ 641.772453] usb 4-1: configuration #1 chosen from 1 choice Apr 24 12:39:11 7675A63 kernel: [ 641.892819] usbcore: registered new interface driver hiddev Apr 24 12:39:11 7675A63 kernel: [ 641.901314] input: WALTOP International Corp. Slim Tablet as /devices/pci:00/:00:1a.1/usb4/4-1/4-1:1.0/input/input9 Apr 24 12:39:11 7675A63 kernel: [ 641.901456] generic-usb 0003:172F:0031.0001: input,hidraw0: USB HID v1.10 Mouse [WALTOP International Corp. Slim Tablet] on usb-:00:1a.1-1/input0 Apr 24 12:39:11 7675A63 kernel: [ 641.901490] usbcore: registered new interface driver usbhid Apr 24 12:39:11 7675A63 kernel: [ 641.901500] usbhid: v2.6:USB HID core driver ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-input-wacom 1:0.10.5-0ubuntu4 ProcVersionSignature: Ubuntu 2.6.32-21.32-preempt 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-preempt x86_64 Architecture: amd64 Date: Sat Apr 24 13:13:51 2010 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu-Studio 10.04 Lucid Lynx -
[Bug 565502] [NEW] Waltop tablet doesn't work on lucid
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 Packages 100 /var/lib/dpkg/status 3) I expected my Waltop pen tablet works fine. (Slim Tablet 12.1 inch, http://www.waltop.com.tw/productDetail.asp?id=21) This tablet is rebranded and some company produces other name such as G-Pen F610 from Genius, KYE Systems Corp., Slim Tablet 12.1 inch USb Tablet from Aiptek, Inc., PTB-ST12 from Princeton Tech. 4) The pointer dosn't move even if I draw on tablet. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: xserver-xorg-input-wacom 1:0.10.5-0ubuntu2 ProcVersionSignature: Ubuntu 2.6.32-21.32-preempt 2.6.32.11+drm33.2 Uname: Linux 2.6.32-21-preempt x86_64 Architecture: amd64 Date: Sun Apr 18 02:39:04 2010 DkmsStatus: Error: [Errno 2] No such file or directory InstallationMedia: Ubuntu-Studio 10.04 Lucid Lynx - Alpha amd64 (20100322) MachineType: LENOVO 7675A63 PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-preempt root=UUID=1c334b52-a73f-4fea-8fb6-f31810378c15 ro quiet splash ProcEnviron: LANG=ja_JP.utf8 SHELL=/bin/bash SourcePackage: xf86-input-wacom dmi.bios.date: 10/09/2009 dmi.bios.vendor: LENOVO dmi.bios.version: 7NETC1WW (2.21 ) dmi.board.name: 7675A63 dmi.board.vendor: LENOVO dmi.board.version: Not Available dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvr7NETC1WW(2.21):bd10/09/2009:svnLENOVO:pn7675A63:pvrThinkPadX61:rvnLENOVO:rn7675A63:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.name: 7675A63 dmi.product.version: ThinkPad X61 dmi.sys.vendor: LENOVO glxinfo: Error: [Errno 2] No such file or directory system: distro: Ubuntu codename: lucid architecture: x86_64 kernel: 2.6.32-21-preempt ** Affects: xf86-input-wacom (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- Waltop tablet doesn't work on lucid https://bugs.launchpad.net/bugs/565502 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 565502] Re: Waltop tablet doesn't work on lucid
** 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 ** Attachment added: GdmLog.txt http://launchpadlibrarian.net/44611409/GdmLog.txt ** Attachment added: GdmLog1.txt http://launchpadlibrarian.net/44611410/GdmLog1.txt ** Attachment added: GdmLog2.txt http://launchpadlibrarian.net/44611411/GdmLog2.txt ** Attachment added: Lspci.txt http://launchpadlibrarian.net/44611412/Lspci.txt ** Attachment added: Lsusb.txt http://launchpadlibrarian.net/44611413/Lsusb.txt ** Attachment added: PciDisplay.txt http://launchpadlibrarian.net/44611414/PciDisplay.txt ** Attachment added: ProcCpuinfo.txt http://launchpadlibrarian.net/44611415/ProcCpuinfo.txt ** Attachment added: ProcInterrupts.txt http://launchpadlibrarian.net/44611416/ProcInterrupts.txt ** Attachment added: ProcModules.txt http://launchpadlibrarian.net/44611417/ProcModules.txt ** Attachment added: RelatedPackageVersions.txt http://launchpadlibrarian.net/44611418/RelatedPackageVersions.txt ** Attachment added: UdevDb.txt http://launchpadlibrarian.net/44611419/UdevDb.txt ** Attachment added: UdevLog.txt http://launchpadlibrarian.net/44611420/UdevLog.txt ** Attachment added: XorgLog.txt http://launchpadlibrarian.net/44611421/XorgLog.txt ** Attachment added: XorgLogOld.txt http://launchpadlibrarian.net/44611422/XorgLogOld.txt ** Attachment added: Xrandr.txt http://launchpadlibrarian.net/44611423/Xrandr.txt ** Attachment added: monitors.xml.txt http://launchpadlibrarian.net/44611424/monitors.xml.txt ** Attachment added: setxkbmap.txt http://launchpadlibrarian.net/44611425/setxkbmap.txt ** Attachment added: xdpyinfo.txt http://launchpadlibrarian.net/44611426/xdpyinfo.txt ** Attachment added: xkbcomp.txt http://launchpadlibrarian.net/44611427/xkbcomp.txt -- Waltop tablet doesn't work on lucid https://bugs.launchpad.net/bugs/565502 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 565502] Re: Waltop tablet doesn't work on lucid
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 International Corp. Slim Tablet (/dev/input/event5) (**) WALTOP International Corp. Slim Tablet: Applying InputClass evdev pointer catchall (**) WALTOP International Corp. Slim Tablet: Applying InputClass evdev tablet catchall (**) WALTOP International Corp. Slim Tablet: Applying InputClass Wacom class (**) Option Device /dev/input/event5 (II) WALTOP International Corp. Slim Tablet: type not specified, assuming 'stylus'. (II) WALTOP International Corp. Slim Tablet: other types will be automatically added. (**) WALTOP International Corp. Slim Tablet: always reports core events (II) WALTOP International Corp. Slim Tablet: hotplugging dependent devices. (**) Option Device /dev/input/event5 (**) WALTOP International Corp. Slim Tablet eraser: always reports core events (II) XINPUT: Adding extended input device WALTOP International Corp. Slim Tablet eraser (type: ERASER) (--) WALTOP International Corp. Slim Tablet eraser: using pressure threshold of 61 for button 1 (--) WALTOP International Corp. Slim Tablet eraser: Wacom Unknown USB tablet speed=38400 maxX=1 maxY=6250 maxZ=1023 resX=1016 resY=1016 tilt=enabled (--) WALTOP International Corp. Slim Tablet eraser: top X=0 top Y=0 bottom X=1 bottom Y=6250 resol X=1016 resol Y=1016 (II) WALTOP International Corp. Slim Tablet: hotplugging completed. (II) XINPUT: Adding extended input device WALTOP International Corp. Slim Tablet (type: STYLUS) (--) WALTOP International Corp. Slim Tablet: top X=0 top Y=0 bottom X=1 bottom Y=6250 resol X=1016 resol Y=1016 /dev/input/mouse1 and /dev/input/event5 is related. Third, try [sudo xxd /dev/input/event5] and [sudo xxd /dev/input/mouse1] but no output. Forth, try [sudo xxd /dev/hidraw0] and I can get dump data below, 000: 0010 109e 1176 0d00 1010 9e11 760d .vv. 010: 0010 109c 1176 0d00 1010 9c11 ...v 020: 760d 0010 1094 1178 0d00 1010 vx.. 030: 9511 790d 0010 1097 1179 0d00 ..yy ... -- Waltop tablet doesn't work on lucid https://bugs.launchpad.net/bugs/565502 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 565502] Re: Waltop tablet doesn't work on lucid
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://ubuntuforums.org/showthread.php?t=1326789 Still can't get waltop/medion graphics tablet to work, can't build drivers in karmic http://ubuntuforums.org/showthread.php?t=1431664 Genius G-Pen F610 Pen Buttons Not Working http://ubuntuforums.org/showthread.php?t=1315438 karmic AIPTEK 14000u Media Tablet http://ubuntuforums.org/showthread.php?t=1300818 How is Support for Non-Wacom Tablets http://ubuntuforums.org/showthread.php?t=1432171 g-pen f610 tablet http://ubuntuforums.org/showthread.php?t=1384899 WALTOP International Corp. Slim Tablet not working... http://ubuntuforums.org/showthread.php?t=1354123 Waltop Slim Tablet - Buttons don't work http://ubuntuforums.org/showthread.php?t=1349735 Gpen F610 installation issue And this report disappointed much people including me. https://bugs.launchpad.net/ubuntu/+source/xf86-input-wacom/+bug/392825 Bug #392825 WALTOP tablets not supported anymore I hope xserver-xorg-input-wacom makes it possible to use this device on ubuntu!! Regards -- Waltop tablet doesn't work on lucid https://bugs.launchpad.net/bugs/565502 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
