[Desktop-packages] [Bug 1860940] [NEW] Cannot read /sys/devices/platform/hp-wmi/tablet
Public bug reported: # cat /sys/devices/platform/hp-wmi/tablet cat: /sys/devices/platform/hp-wmi/tablet: Invalid argument Ubuntu 18.04.3 LTS This is on a Hewlett-Packard x360 310 G2 convertible laptop. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Package changed: onboard (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1860940 Title: Cannot read /sys/devices/platform/hp-wmi/tablet Status in linux package in Ubuntu: Incomplete Bug description: # cat /sys/devices/platform/hp-wmi/tablet cat: /sys/devices/platform/hp-wmi/tablet: Invalid argument Ubuntu 18.04.3 LTS This is on a Hewlett-Packard x360 310 G2 convertible laptop. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860940/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1755987] Re: onboard onscreen keyboard lacks arrow keys, pg up/down delete etc
>From https://askubuntu.com/questions/1153506/how-do-i-enable-all-keys- on-the-touchscreen-keyboard : The GNOME On Screen Keyboard (OSK) is designed to generate keyboards from the Unicode Common Locale Data Repository data. The Unicode CLDR was never intended to limit the keys available, but that seems to be the path the GNOME developers are following. If a key isn't in the CLDR, there is no way to type it. So, that means, no Esc, no F1, no Control, etc. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1755987 Title: onboard onscreen keyboard lacks arrow keys, pg up/down delete etc Status in onboard package in Ubuntu: Confirmed Bug description: Onboard 1.4.1-2ubuntu1 Running ubuntu 18.04 Bionic Beaver development branch Onboard doesn't allow the user to use a termial or much of anything properly because basic keys like allows and pg up down delete home end etc are all not available. It would be good to look at hacker's keyboard, which is an open source Android app, which allows full use of a terminal, WITH EASE. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1755987/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718927] Re: No HDMI sound after suspend/resume
Update: The HDMI audio device is missing even after screen off (screensaver). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1718927 Title: No HDMI sound after suspend/resume Status in pulseaudio package in Ubuntu: Confirmed Bug description: When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works perfectly, but when I suspend computer and resume it there is no sound via HDMI in TV. However sound via built in speakers works fine. The only thing I can do to restore sound is to reboot the machine. Similar problem was discussed in following thread https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1718927] Re: No HDMI sound after suspend/resume
For me, after suspend/resume the HDMI audio device is missing from Sound Settings and pavucontrol. 'pacmd list-cards' still shows the device. None of the workarounds work here. This on Ubuntu 18.04.2 LTS 18.04 kernel 5.2.0-rc6-19.06.26.amdgpu.ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1718927 Title: No HDMI sound after suspend/resume Status in pulseaudio package in Ubuntu: Confirmed Bug description: When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works perfectly, but when I suspend computer and resume it there is no sound via HDMI in TV. However sound via built in speakers works fine. The only thing I can do to restore sound is to reboot the machine. Similar problem was discussed in following thread https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no solution. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1836418] [NEW] No HDMI audio device after resume, but pacmd list-cards sees it
Public bug reported: After suspend/resume, the HDMI audio device is missing from Sound Settings and pavucontrol. 'pacmd list-cards' still shows the device. This on Ubuntu 18.04.2 LTS 18.04 kernel 5.2.0-rc6-19.06.26.amdgpu.ubuntu ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Output of pacmd list-cards" https://bugs.launchpad.net/bugs/1836418/+attachment/5276828/+files/list-card.txt ** Summary changed: - No HDMI audio device after resume, but pacmd list-card sees it + No HDMI audio device after resume, but pacmd list-cards sees it ** Description changed: After suspend/resume, the HDMI audio device is missing from Sound Settings and pavucontrol. - 'pacmd list-card' still shows the device. - + 'pacmd list-cards' still shows the device. This on Ubuntu 18.04.2 LTS 18.04 kernel 5.2.0-rc6-19.06.26.amdgpu.ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1836418 Title: No HDMI audio device after resume, but pacmd list-cards sees it Status in pulseaudio package in Ubuntu: New Bug description: After suspend/resume, the HDMI audio device is missing from Sound Settings and pavucontrol. 'pacmd list-cards' still shows the device. This on Ubuntu 18.04.2 LTS 18.04 kernel 5.2.0-rc6-19.06.26.amdgpu.ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1836418/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1458947] Re: QinHeng Electronics CH345 MIDI adapter triggers error
In Xenial, the error message is still there, however the behavior has improved and only 1 MIDI out and 1 MIDI in ports are registered. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1458947 Title: QinHeng Electronics CH345 MIDI adapter triggers error Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Incomplete Bug description: Cheap oriental MIDI adapter starts up with the following error, but works as expected.* E: [pulseaudio] module.c: Failed to load module "module-alsa-card" (argument: "device_id="1" name="usb-1a86_USB2.0-MIDI-00-USB20MIDI" card_name="alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI" namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties="module-udev- detect.discovered=1""): initialization failed. The device: 1a86:752d QinHeng Electronics CH345 MIDI adapter Of course i'm not sure whether this is a PA problem or an ALSA or UDEV bug. Ubuntu 14.04.2 LTS Pulseaudio 1:4.0-0ubuntu11.1 * works almost as expected: there is one physical input and one output, but in ALSA one input and two outputs appear. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1458947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1454240] Re: touchscreen refuses calibration by xinput set-prop
--format=32 works as expected ** Changed in: xinput (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1454240 Title: touchscreen refuses calibration by xinput set-prop Status in xinput package in Ubuntu: Invalid Bug description: I had managed to calibrate my eGalax touchscreen (Hewlett-Packard Pavilion TX 1000 tablet pc) a while ago, then upgraded video drivers. Ran into a problem with the video drivers, and by the time I've ironed it out, the touchscreen started to refuse calibration. I have purged all extra PPAs but still no success. ` $ xinput set-prop --type=int --format=8 12 Evdev Axis Calibration 41 3961 100 3949 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 131 (XInputExtension) Minor opcode of failed request: 57 () Serial number of failed request: 19 Current serial number in output stream: 20 ` Calibration values set in /usr/share/X11/xorg.conf.d/99-calibration.conf do work. Ubuntu 14.04.2 LTS xserver-xorg-input-evdev: Installed: 1:2.8.2-1ubuntu2 Candidate: 1:2.8.2-1ubuntu2 Version table: *** 1:2.8.2-1ubuntu2 0 500 http://hu.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 12 14:39:37 2015 DistUpgraded: 2014-08-20 00:50:55,180 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-09 (487 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=c286a7df-7364-4dcd-83ab-7cd2b4f2b792 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to trusty on 2014-08-19 (265 days ago) dmi.bios.date: 04/18/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.20 dmi.board.name: 30BF dmi.board.vendor: Quanta dmi.board.version: 69.2E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.20:bd04/18/2008:svnHewlett-Packard:pn:pvrRev1:rvnQuanta:rn30BF:rvr69.2E:cvnQuanta:ct10:cvrN/A: dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 12 14:01:51 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DFP-0 xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1454240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1454240] Re: touchscreen refuses calibration by xinput set-prop
** Package changed: xserver-xorg-input-evdev (Ubuntu) = xinput (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xinput in Ubuntu. https://bugs.launchpad.net/bugs/1454240 Title: touchscreen refuses calibration by xinput set-prop Status in xinput package in Ubuntu: New Bug description: I had managed to calibrate my eGalax touchscreen (Hewlett-Packard Pavilion TX 1000 tablet pc) a while ago, then upgraded video drivers. Ran into a problem with the video drivers, and by the time I've ironed it out, the touchscreen started to refuse calibration. I have purged all extra PPAs but still no success. ` $ xinput set-prop --type=int --format=8 12 Evdev Axis Calibration 41 3961 100 3949 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 131 (XInputExtension) Minor opcode of failed request: 57 () Serial number of failed request: 19 Current serial number in output stream: 20 ` Calibration values set in /usr/share/X11/xorg.conf.d/99-calibration.conf do work. Ubuntu 14.04.2 LTS xserver-xorg-input-evdev: Installed: 1:2.8.2-1ubuntu2 Candidate: 1:2.8.2-1ubuntu2 Version table: *** 1:2.8.2-1ubuntu2 0 500 http://hu.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 12 14:39:37 2015 DistUpgraded: 2014-08-20 00:50:55,180 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-09 (487 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=c286a7df-7364-4dcd-83ab-7cd2b4f2b792 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to trusty on 2014-08-19 (265 days ago) dmi.bios.date: 04/18/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.20 dmi.board.name: 30BF dmi.board.vendor: Quanta dmi.board.version: 69.2E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.20:bd04/18/2008:svnHewlett-Packard:pn:pvrRev1:rvnQuanta:rn30BF:rvr69.2E:cvnQuanta:ct10:cvrN/A: dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 12 14:01:51 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DFP-0 xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: nvidia To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xinput/+bug/1454240/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1458947] Re: QinHeng Electronics CH345 MIDI adapter triggers error
** Attachment added: Output of alsa-info.sh https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1458947/+attachment/4405365/+files/alsa-info.sh.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1458947 Title: QinHeng Electronics CH345 MIDI adapter triggers error Status in pulseaudio package in Ubuntu: Incomplete Bug description: Cheap oriental MIDI adapter starts up with the following error, but works as expected.* E: [pulseaudio] module.c: Failed to load module module-alsa-card (argument: device_id=1 name=usb-1a86_USB2.0-MIDI-00-USB20MIDI card_name=alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties=module-udev- detect.discovered=1): initialization failed. The device: 1a86:752d QinHeng Electronics CH345 MIDI adapter Of course i'm not sure whether this is a PA problem or an ALSA or UDEV bug. Ubuntu 14.04.2 LTS Pulseaudio 1:4.0-0ubuntu11.1 * works almost as expected: there is one physical input and one output, but in ALSA one input and two outputs appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1458947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1458947] Re: QinHeng Electronics CH345 MIDI adapter triggers error
** Bug watch added: freedesktop.org Bugzilla #90678 https://bugs.freedesktop.org/show_bug.cgi?id=90678 ** Also affects: pulseaudio via https://bugs.freedesktop.org/show_bug.cgi?id=90678 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1458947 Title: QinHeng Electronics CH345 MIDI adapter triggers error Status in PulseAudio sound server: Unknown Status in pulseaudio package in Ubuntu: Incomplete Bug description: Cheap oriental MIDI adapter starts up with the following error, but works as expected.* E: [pulseaudio] module.c: Failed to load module module-alsa-card (argument: device_id=1 name=usb-1a86_USB2.0-MIDI-00-USB20MIDI card_name=alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties=module-udev- detect.discovered=1): initialization failed. The device: 1a86:752d QinHeng Electronics CH345 MIDI adapter Of course i'm not sure whether this is a PA problem or an ALSA or UDEV bug. Ubuntu 14.04.2 LTS Pulseaudio 1:4.0-0ubuntu11.1 * works almost as expected: there is one physical input and one output, but in ALSA one input and two outputs appear. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1458947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1458947] [NEW] QinHeng Electronics CH345 MIDI adapter triggers error
Public bug reported: Cheap oriental MIDI adapter starts up with the following error, but works as expected.* E: [pulseaudio] module.c: Failed to load module module-alsa-card (argument: device_id=1 name=usb-1a86_USB2.0-MIDI-00-USB20MIDI card_name=alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties=module-udev- detect.discovered=1): initialization failed. The device: 1a86:752d QinHeng Electronics CH345 MIDI adapter Of course i'm not sure whether this is a PA problem or an ALSA or UDEV bug. Ubuntu 14.04.2 LTS Pulseaudio 1:4.0-0ubuntu11.1 * works almost as expected: there is one physical input and one output, but in ALSA one input and two outputs appear. ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1458947 Title: QinHeng Electronics CH345 MIDI adapter triggers error Status in pulseaudio package in Ubuntu: New Bug description: Cheap oriental MIDI adapter starts up with the following error, but works as expected.* E: [pulseaudio] module.c: Failed to load module module-alsa-card (argument: device_id=1 name=usb-1a86_USB2.0-MIDI-00-USB20MIDI card_name=alsa_card.usb-1a86_USB2.0-MIDI-00-USB20MIDI namereg_fail=false tsched=yes fixed_latency_range=no ignore_dB=no deferred_volume=yes use_ucm=yes card_properties=module-udev- detect.discovered=1): initialization failed. The device: 1a86:752d QinHeng Electronics CH345 MIDI adapter Of course i'm not sure whether this is a PA problem or an ALSA or UDEV bug. Ubuntu 14.04.2 LTS Pulseaudio 1:4.0-0ubuntu11.1 * works almost as expected: there is one physical input and one output, but in ALSA one input and two outputs appear. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1458947/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1454240] Re: touchscreen refuses calibration
** Description changed: I had managed to calibrate my eGalax touchscreen (Hewlett-Packard Pavilion TX 1000 tablet pc) a while ago, then upgraded video drivers. Ran into a problem with the video drivers, and by the time I've ironed it out, the touchscreen started to refuse calibration. I have purged all extra PPAs but still no success. ` $ xinput set-prop --type=int --format=8 12 Evdev Axis Calibration 41 3961 100 3949 X Error of failed request: BadMatch (invalid parameter attributes) - Major opcode of failed request: 131 (XInputExtension) - Minor opcode of failed request: 57 () - Serial number of failed request: 19 - Current serial number in output stream: 20 + Major opcode of failed request: 131 (XInputExtension) + Minor opcode of failed request: 57 () + Serial number of failed request: 19 + Current serial number in output stream: 20 ` - Also, calibration values set in - /usr/share/X11/xorg.conf.d/99-calibration.conf don't work any more. + Calibration values set in /usr/share/X11/xorg.conf.d/99-calibration.conf + do work. Ubuntu 14.04.2 LTS xserver-xorg-input-evdev: - Installed: 1:2.8.2-1ubuntu2 - Candidate: 1:2.8.2-1ubuntu2 - Version table: - *** 1:2.8.2-1ubuntu2 0 - 500 http://hu.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 1:2.8.2-1ubuntu2 + Candidate: 1:2.8.2-1ubuntu2 + Version table: + *** 1:2.8.2-1ubuntu2 0 + 500 http://hu.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages + 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 12 14:39:37 2015 DistUpgraded: 2014-08-20 00:50:55,180 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-09 (487 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=c286a7df-7364-4dcd-83ab-7cd2b4f2b792 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to trusty on 2014-08-19 (265 days ago) dmi.bios.date: 04/18/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.20 dmi.board.name: 30BF dmi.board.vendor: Quanta dmi.board.version: 69.2E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.20:bd04/18/2008:svnHewlett-Packard:pn:pvrRev1:rvnQuanta:rn30BF:rvr69.2E:cvnQuanta:ct10:cvrN/A: dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 12 14:01:51 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DFP-0 xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: nvidia ** Summary changed: - touchscreen refuses calibration + touchscreen refuses calibration by xinput set-prop -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1454240 Title: touchscreen refuses calibration by xinput set-prop Status in xserver-xorg-input-evdev package in Ubuntu: New Bug description: I had managed to calibrate my eGalax touchscreen (Hewlett-Packard Pavilion TX 1000 tablet pc) a while ago, then upgraded video drivers. Ran into a problem with the video drivers, and by the time I've ironed it out, the touchscreen started to refuse calibration. I have purged all extra PPAs but still no success. ` $ xinput set-prop --type=int --format=8 12 Evdev Axis Calibration 41 3961 100 3949 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 131 (XInputExtension) Minor opcode of failed request: 57 ()
[Desktop-packages] [Bug 1454240] [NEW] touchscreen refuses calibration
Public bug reported: I had managed to calibrate my eGalax touchscreen (Hewlett-Packard Pavilion TX 1000 tablet pc) a while ago, then upgraded video drivers. Ran into a problem with the video drivers, and by the time I've ironed it out, the touchscreen started to refuse calibration. I have purged all extra PPAs but still no success. ` $ xinput set-prop --type=int --format=8 12 Evdev Axis Calibration 41 3961 100 3949 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 131 (XInputExtension) Minor opcode of failed request: 57 () Serial number of failed request: 19 Current serial number in output stream: 20 ` Also, calibration values set in /usr/share/X11/xorg.conf.d/99-calibration.conf don't work any more. Ubuntu 14.04.2 LTS xserver-xorg-input-evdev: Installed: 1:2.8.2-1ubuntu2 Candidate: 1:2.8.2-1ubuntu2 Version table: *** 1:2.8.2-1ubuntu2 0 500 http://hu.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-52.86-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 NonfreeKernelModules: wl nvidia ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 12 14:39:37 2015 DistUpgraded: 2014-08-20 00:50:55,180 DEBUG enabling apt cron job DistroCodename: trusty DistroVariant: ubuntu EcryptfsInUse: Yes InstallationDate: Installed on 2014-01-09 (487 days ago) InstallationMedia: Ubuntu 12.04.3 LTS Precise Pangolin - Release amd64 (20130820.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-52-generic root=UUID=c286a7df-7364-4dcd-83ab-7cd2b4f2b792 ro quiet splash vt.handoff=7 SourcePackage: xserver-xorg-input-evdev UpgradeStatus: Upgraded to trusty on 2014-08-19 (265 days ago) dmi.bios.date: 04/18/2008 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: F.20 dmi.board.name: 30BF dmi.board.vendor: Quanta dmi.board.version: 69.2E dmi.chassis.type: 10 dmi.chassis.vendor: Quanta dmi.chassis.version: N/A dmi.modalias: dmi:bvnHewlett-Packard:bvrF.20:bd04/18/2008:svnHewlett-Packard:pn:pvrRev1:rvnQuanta:rn30BF:rvr69.2E:cvnQuanta:ct10:cvrN/A: dmi.product.version: Rev 1 dmi.sys.vendor: Hewlett-Packard version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.4 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.4 version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1.6 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.10-1ubuntu2 xserver.bootTime: Tue May 12 14:01:51 2015 xserver.configfile: /etc/X11/xorg.conf xserver.errors: open /dev/dri/card0: No such file or directory xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DFP-0 xserver.version: 2:1.15.1-0ubuntu2.7 xserver.video_driver: nvidia ** Affects: xserver-xorg-input-evdev (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug possible-manual-nvidia-install trusty ubuntu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xserver-xorg-input-evdev in Ubuntu. https://bugs.launchpad.net/bugs/1454240 Title: touchscreen refuses calibration Status in xserver-xorg-input-evdev package in Ubuntu: New Bug description: I had managed to calibrate my eGalax touchscreen (Hewlett-Packard Pavilion TX 1000 tablet pc) a while ago, then upgraded video drivers. Ran into a problem with the video drivers, and by the time I've ironed it out, the touchscreen started to refuse calibration. I have purged all extra PPAs but still no success. ` $ xinput set-prop --type=int --format=8 12 Evdev Axis Calibration 41 3961 100 3949 X Error of failed request: BadMatch (invalid parameter attributes) Major opcode of failed request: 131 (XInputExtension) Minor opcode of failed request: 57 () Serial number of failed request: 19 Current serial number in output stream: 20 ` Also, calibration values set in /usr/share/X11/xorg.conf.d/99-calibration.conf don't work any more. Ubuntu 14.04.2 LTS xserver-xorg-input-evdev: Installed: 1:2.8.2-1ubuntu2 Candidate: 1:2.8.2-1ubuntu2 Version table: *** 1:2.8.2-1ubuntu2 0 500 http://hu.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2 ProcVersionSignature: Ubuntu
[Desktop-packages] [Bug 1390474] Re: Volume element PCM has 6 channels. That's too much! - PA doesn't support elements with more than two channels
** Bug watch added: freedesktop.org Bugzilla #84804 https://bugs.freedesktop.org/show_bug.cgi?id=84804 ** Also affects: pulseaudio via https://bugs.freedesktop.org/show_bug.cgi?id=84804 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1390474 Title: Volume element PCM has 6 channels. That's too much! - PA doesn't support elements with more than two channels Status in PulseAudio sound server: Unknown Status in pulseaudio package in Ubuntu: Confirmed Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1390474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390474] Re: Volume element PCM has 6 channels. That's too much! - PA doesn't support elements with more than two channels
According to comment 5 ** Changed in: pulseaudio (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1390474 Title: Volume element PCM has 6 channels. That's too much! - PA doesn't support elements with more than two channels Status in pulseaudio package in Ubuntu: Confirmed Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390474] Re: Volume element PCM has 6 channels. That's too much! - PA doesn't support elements with more than two channels
Thanks Raymond for the info. I would like to get this bug ironed out in Pulseaudio not only locally. Can we go on with triaging? Right the the bug is New. Could we eventually change to Conformed? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1390474 Title: Volume element PCM has 6 channels. That's too much! - PA doesn't support elements with more than two channels Status in pulseaudio package in Ubuntu: Incomplete Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390474] Re: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26
have you ask Arun how to revert his patch ? No, I am just an end user so I don't feel I shall ask someone to revert their patch. However... Arun? The patch was registered by Tanu Kaskinen and Colin Guthrie. I have forwarded this bug to them. Colin did not reply, Tanu's reply is above. https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/comments/5 I would appreciate if, in case you think that is the best solution for the moment, you proposed reverting the patch to the appropriate personnel. Thanks. Anyway, shall we triage this bug, shan't we? Otherwise it will just expire. ** Summary changed: - Volume element PCM has 6 channels. That's too much! with Terratec PHASE26 + Volume element PCM has 6 channels. That's too much! - PA doesn't support elements with more than two channels -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1390474 Title: Volume element PCM has 6 channels. That's too much! - PA doesn't support elements with more than two channels Status in pulseaudio package in Ubuntu: Incomplete Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390474] Re: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26
Please tell me what to send in order to triage this bug, thanks -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1390474 Title: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26 Status in pulseaudio package in Ubuntu: Incomplete Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390474] Re: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26
Is any sound card with multi channel volume control supported by pulseaudio? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1390474 Title: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26 Status in pulseaudio package in Ubuntu: New Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390474] Re: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26
this mean your usb audio have a 6 channel playbacck volume control similar to https://bugs.freedesktop.org/show_bug.cgi?id=84983#c5 Does this mean that bug #936539 (Freedesktop bug 84983 on Launchpad) involves all devices with more than 2 volume channels? In that case, shall I suggest to change the description of #936539 to something more general and mark this one as a duplicate? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1390474 Title: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26 Status in pulseaudio package in Ubuntu: New Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 519452] Re: Can't start a session in low-graphics mode
Same promlem here with 14.04. ** Changed in: nvidia-graphics-drivers (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers in Ubuntu. https://bugs.launchpad.net/bugs/519452 Title: Can't start a session in low-graphics mode Status in nvidia-graphics-drivers package in Ubuntu: Confirmed Bug description: When starting KDM without the necessary NVidia drivers, I get the message about Ubuntu running in low-graphics mode. I selected Run Ubuntu in low-graphics mode for just one session, and got a message Stand by one minute while the display restarts It just stays like that forever. If I click Ok, it restarts X and starts over. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers/+bug/519452/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] Fwd: [Bug 1390474] Re: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26
Kindly forwarding this bug, please express your thoughts on Launchpad. -- Forwarded message -- From: Raymond 1390...@bugs.launchpad.net Date: Sat, Nov 8, 2014 at 4:06 PM Subject: [Bug 1390474] Re: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26 To: muran...@gmail.com http://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/src/modules/alsa /alsa-mixer.c?id=527078523815587bfd021bc1d10782403e9b3e84 send email to the author of the patch -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1390474 Title: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26 Status in “pulseaudio” package in Ubuntu: New Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1390474 Title: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26 Status in “pulseaudio” package in Ubuntu: New Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1390474] [NEW] Volume element PCM has 6 channels. That's too much! with Terratec PHASE26
Public bug reported: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: output of pulseaudio - https://bugs.launchpad.net/bugs/1390474/+attachment/4255236/+files/phase26-pa.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1390474 Title: Volume element PCM has 6 channels. That's too much! with Terratec PHASE26 Status in “pulseaudio” package in Ubuntu: New Bug description: When connecting the Terratec PHASE26 in 16/48 mode (6 channels) I get the error Volume element PCM has 6 channels. That's too much! I can't handle that! and the card fails to show up in Sound Settings. Everything is fine with 24/48 mode (2 channels). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1390474/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller
BTW not only Gnome Settings but also `pactl list` has the same info. The right names are there too, however. alsa.card = 0 alsa.card_name = PHASE 88 Rack FW alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW (id:3, rev:1), GUID 000aac0300592827 a alsa.driver_name = snd_bebob device.bus_path = pci-:01:09.0 sysfs.path = /devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0 udev.id = firewire-0x000aac0300592827 device.bus = firewire device.vendor.name = Texas Instruments device.product.name = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] device.string = 0 device.description = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] module-udev-detect.discovered = 1 device.icon_name = audio-card-firewire profiles: input:10-channels: 10 Channels Input (priority 10, available: unknown) output:10-channels: 10 Channels Output (priority 1000, available: unknown) output:10-channels+input:10-channels: 10 Channels Output + 10 Channels Input (priority 1010, available: unknown) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1381475 Title: Firewire sound card registered by the name of the fw controller Status in “pulseaudio” package in Ubuntu: Triaged Bug description: I am testing the new snd-firewire ALSA module which is currently getting accepted into the kernel. I have noticed that while ALSA recognizes the correct name for the card, PulseAudio displays another, wrong name, which is apparently the name of the FireWire controller through which the sound card is connected. $ aplay -l List of PLAYBACK Hardware Devices card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 $ pacmd list-sinks Welcome to PulseAudio! Use help for usage information. 4 sink(s) available. [...] index: 2 name: alsa_output.firewire-0x000aac0300592827.10-channels driver: module-alsa-card.c flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9000 volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 8: 100% 9: 100% 0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB balance 0,00 base volume: 100% 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 5 sample spec: s16le 10ch 44100Hz channel map: front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1 used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 185,76 ms card: 3 alsa_card.firewire-0x000aac0300592827 module: 8 properties: alsa.resolution_bits = 16 device.api = alsa device.class = sound alsa.class = generic alsa.subclass = generic-mix alsa.name = PHASE 88 Rack FW PCM alsa.id = BeBoB alsa.subdevice = 0 alsa.subdevice_name = subdevice #0 alsa.device = 0 alsa.card = 0 alsa.card_name = PHASE 88 Rack FW alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW (id:3, rev:1), GUID 000aac0300592827 a alsa.driver_name = snd_bebob device.bus_path = pci-:01:09.0 sysfs.path = /devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0 udev.id = firewire-0x000aac0300592827 device.bus = firewire device.vendor.name = Texas Instruments device.product.name = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] device.string = hw:0 device.buffering.buffer_size = 163840 device.buffering.fragment_size = 81920 device.access_mode = mmap+timer device.profile.name = 10-channels device.profile.description = 10 Channels device.description = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] 10 Channels alsa.mixer_name = PHASE 88 Rack FW module-udev-detect.discovered = 1 device.icon_name = audio-card-firewire PulseAudio 1:4.0-0ubuntu11 To manage notifications about this bug go to:
[Desktop-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller
which name do you want when you plug and unplug the device ? Based on how other cards are named (see previous attachment Firewire sound card listed in Sound Settings) there sould be a short description of the output, followed by the short name of the card. For example: 10 Channels * PHASE 88 ** * Please note that the 10 output channels are, in this case, 8 Analog and 2 Digital (the same applies to Input channels). As far as I can see, normally the 8 Channels Analog Output and the Digital Output (S/PDIF) would be displayed as two separate options in Sound Settings - I guess this is beyond the scope of the current issue and I shall file a new bug. ** or PHASE 88 Rack FW -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1381475 Title: Firewire sound card registered by the name of the fw controller Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: I am testing the new snd-firewire ALSA module which is currently getting accepted into the kernel. I have noticed that while ALSA recognizes the correct name for the card, PulseAudio displays another, wrong name, which is apparently the name of the FireWire controller through which the sound card is connected. $ aplay -l List of PLAYBACK Hardware Devices card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 $ pacmd list-sinks Welcome to PulseAudio! Use help for usage information. 4 sink(s) available. [...] index: 2 name: alsa_output.firewire-0x000aac0300592827.10-channels driver: module-alsa-card.c flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9000 volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 8: 100% 9: 100% 0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB balance 0,00 base volume: 100% 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 5 sample spec: s16le 10ch 44100Hz channel map: front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1 used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 185,76 ms card: 3 alsa_card.firewire-0x000aac0300592827 module: 8 properties: alsa.resolution_bits = 16 device.api = alsa device.class = sound alsa.class = generic alsa.subclass = generic-mix alsa.name = PHASE 88 Rack FW PCM alsa.id = BeBoB alsa.subdevice = 0 alsa.subdevice_name = subdevice #0 alsa.device = 0 alsa.card = 0 alsa.card_name = PHASE 88 Rack FW alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW (id:3, rev:1), GUID 000aac0300592827 a alsa.driver_name = snd_bebob device.bus_path = pci-:01:09.0 sysfs.path = /devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0 udev.id = firewire-0x000aac0300592827 device.bus = firewire device.vendor.name = Texas Instruments device.product.name = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] device.string = hw:0 device.buffering.buffer_size = 163840 device.buffering.fragment_size = 81920 device.access_mode = mmap+timer device.profile.name = 10-channels device.profile.description = 10 Channels device.description = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] 10 Channels alsa.mixer_name = PHASE 88 Rack FW module-udev-detect.discovered = 1 device.icon_name = audio-card-firewire PulseAudio 1:4.0-0ubuntu11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1381475] [NEW] Firewire sound card registered by the name of the fw controller
Public bug reported: I am testing the new snd-firewire ALSA module which is currently getting accepted into the kernel. I have noticed that while ALSA recognizes the correct name for the card, PulseAudio displays another, wrong name, which is apparently the name of the FireWire controller through which the sound card is connected. $ aplay -l List of PLAYBACK Hardware Devices card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 $ pacmd list-sinks Welcome to PulseAudio! Use help for usage information. 4 sink(s) available. [...] index: 2 name: alsa_output.firewire-0x000aac0300592827.10-channels driver: module-alsa-card.c flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9000 volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 8: 100% 9: 100% 0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB balance 0,00 base volume: 100% 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 5 sample spec: s16le 10ch 44100Hz channel map: front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1 used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 185,76 ms card: 3 alsa_card.firewire-0x000aac0300592827 module: 8 properties: alsa.resolution_bits = 16 device.api = alsa device.class = sound alsa.class = generic alsa.subclass = generic-mix alsa.name = PHASE 88 Rack FW PCM alsa.id = BeBoB alsa.subdevice = 0 alsa.subdevice_name = subdevice #0 alsa.device = 0 alsa.card = 0 alsa.card_name = PHASE 88 Rack FW alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW (id:3, rev:1), GUID 000aac0300592827 a alsa.driver_name = snd_bebob device.bus_path = pci-:01:09.0 sysfs.path = /devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0 udev.id = firewire-0x000aac0300592827 device.bus = firewire device.vendor.name = Texas Instruments device.product.name = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] device.string = hw:0 device.buffering.buffer_size = 163840 device.buffering.fragment_size = 81920 device.access_mode = mmap+timer device.profile.name = 10-channels device.profile.description = 10 Channels device.description = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] 10 Channels alsa.mixer_name = PHASE 88 Rack FW module-udev-detect.discovered = 1 device.icon_name = audio-card-firewire PulseAudio 1:4.0-0ubuntu11 ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Attachment added: Firewire sound card listed in Sound Settings https://bugs.launchpad.net/bugs/1381475/+attachment/4236944/+files/73dda98c-53ad-11e4-9367-1fa6479efb60.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1381475 Title: Firewire sound card registered by the name of the fw controller Status in “pulseaudio” package in Ubuntu: New Bug description: I am testing the new snd-firewire ALSA module which is currently getting accepted into the kernel. I have noticed that while ALSA recognizes the correct name for the card, PulseAudio displays another, wrong name, which is apparently the name of the FireWire controller through which the sound card is connected. $ aplay -l List of PLAYBACK Hardware Devices card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 $ pacmd list-sinks Welcome to PulseAudio! Use help for usage information. 4 sink(s) available. [...] index: 2 name: alsa_output.firewire-0x000aac0300592827.10-channels driver: module-alsa-card.c flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9000 volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 8: 100% 9: 100% 0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB
[Desktop-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller
http://www.alsa- project.org/db/?f=8b6f81d43c2c1156c94deba796317d3c274dee3e -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1381475 Title: Firewire sound card registered by the name of the fw controller Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: I am testing the new snd-firewire ALSA module which is currently getting accepted into the kernel. I have noticed that while ALSA recognizes the correct name for the card, PulseAudio displays another, wrong name, which is apparently the name of the FireWire controller through which the sound card is connected. $ aplay -l List of PLAYBACK Hardware Devices card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 $ pacmd list-sinks Welcome to PulseAudio! Use help for usage information. 4 sink(s) available. [...] index: 2 name: alsa_output.firewire-0x000aac0300592827.10-channels driver: module-alsa-card.c flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9000 volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 8: 100% 9: 100% 0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB balance 0,00 base volume: 100% 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 5 sample spec: s16le 10ch 44100Hz channel map: front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1 used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 185,76 ms card: 3 alsa_card.firewire-0x000aac0300592827 module: 8 properties: alsa.resolution_bits = 16 device.api = alsa device.class = sound alsa.class = generic alsa.subclass = generic-mix alsa.name = PHASE 88 Rack FW PCM alsa.id = BeBoB alsa.subdevice = 0 alsa.subdevice_name = subdevice #0 alsa.device = 0 alsa.card = 0 alsa.card_name = PHASE 88 Rack FW alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW (id:3, rev:1), GUID 000aac0300592827 a alsa.driver_name = snd_bebob device.bus_path = pci-:01:09.0 sysfs.path = /devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0 udev.id = firewire-0x000aac0300592827 device.bus = firewire device.vendor.name = Texas Instruments device.product.name = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] device.string = hw:0 device.buffering.buffer_size = 163840 device.buffering.fragment_size = 81920 device.access_mode = mmap+timer device.profile.name = 10-channels device.profile.description = 10 Channels device.description = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] 10 Channels alsa.mixer_name = PHASE 88 Rack FW module-udev-detect.discovered = 1 device.icon_name = audio-card-firewire PulseAudio 1:4.0-0ubuntu11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller
** Attachment added: output of pulseaudio - --log-time=1 https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+attachment/4237185/+files/pulseverbose.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1381475 Title: Firewire sound card registered by the name of the fw controller Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: I am testing the new snd-firewire ALSA module which is currently getting accepted into the kernel. I have noticed that while ALSA recognizes the correct name for the card, PulseAudio displays another, wrong name, which is apparently the name of the FireWire controller through which the sound card is connected. $ aplay -l List of PLAYBACK Hardware Devices card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 $ pacmd list-sinks Welcome to PulseAudio! Use help for usage information. 4 sink(s) available. [...] index: 2 name: alsa_output.firewire-0x000aac0300592827.10-channels driver: module-alsa-card.c flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9000 volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 8: 100% 9: 100% 0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB balance 0,00 base volume: 100% 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 5 sample spec: s16le 10ch 44100Hz channel map: front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1 used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 185,76 ms card: 3 alsa_card.firewire-0x000aac0300592827 module: 8 properties: alsa.resolution_bits = 16 device.api = alsa device.class = sound alsa.class = generic alsa.subclass = generic-mix alsa.name = PHASE 88 Rack FW PCM alsa.id = BeBoB alsa.subdevice = 0 alsa.subdevice_name = subdevice #0 alsa.device = 0 alsa.card = 0 alsa.card_name = PHASE 88 Rack FW alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW (id:3, rev:1), GUID 000aac0300592827 a alsa.driver_name = snd_bebob device.bus_path = pci-:01:09.0 sysfs.path = /devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0 udev.id = firewire-0x000aac0300592827 device.bus = firewire device.vendor.name = Texas Instruments device.product.name = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] device.string = hw:0 device.buffering.buffer_size = 163840 device.buffering.fragment_size = 81920 device.access_mode = mmap+timer device.profile.name = 10-channels device.profile.description = 10 Channels device.description = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] 10 Channels alsa.mixer_name = PHASE 88 Rack FW module-udev-detect.discovered = 1 device.icon_name = audio-card-firewire PulseAudio 1:4.0-0ubuntu11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1381475] Re: Firewire sound card registered by the name of the fw controller
** Attachment added: output of pactl list https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+attachment/4237170/+files/pactl.list.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1381475 Title: Firewire sound card registered by the name of the fw controller Status in “pulseaudio” package in Ubuntu: Incomplete Bug description: I am testing the new snd-firewire ALSA module which is currently getting accepted into the kernel. I have noticed that while ALSA recognizes the correct name for the card, PulseAudio displays another, wrong name, which is apparently the name of the FireWire controller through which the sound card is connected. $ aplay -l List of PLAYBACK Hardware Devices card 0: FW [PHASE 88 Rack FW], device 0: BeBoB [PHASE 88 Rack FW PCM] Subdevices: 1/1 Subdevice #0: subdevice #0 $ pacmd list-sinks Welcome to PulseAudio! Use help for usage information. 4 sink(s) available. [...] index: 2 name: alsa_output.firewire-0x000aac0300592827.10-channels driver: module-alsa-card.c flags: HARDWARE DECIBEL_VOLUME LATENCY DYNAMIC_LATENCY state: SUSPENDED suspend cause: IDLE priority: 9000 volume: 0: 100% 1: 100% 2: 100% 3: 100% 4: 100% 5: 100% 6: 100% 7: 100% 8: 100% 9: 100% 0: 0,00 dB 1: 0,00 dB 2: 0,00 dB 3: 0,00 dB 4: 0,00 dB 5: 0,00 dB 6: 0,00 dB 7: 0,00 dB 8: 0,00 dB 9: 0,00 dB balance 0,00 base volume: 100% 0,00 dB volume steps: 65537 muted: no current latency: 0,00 ms max request: 0 KiB max rewind: 0 KiB monitor source: 5 sample spec: s16le 10ch 44100Hz channel map: front-left,front-right,rear-left,rear-right,front-center,lfe,side-left,side-right,aux0,aux1 used by: 0 linked by: 0 configured latency: 0,00 ms; range is 0,50 .. 185,76 ms card: 3 alsa_card.firewire-0x000aac0300592827 module: 8 properties: alsa.resolution_bits = 16 device.api = alsa device.class = sound alsa.class = generic alsa.subclass = generic-mix alsa.name = PHASE 88 Rack FW PCM alsa.id = BeBoB alsa.subdevice = 0 alsa.subdevice_name = subdevice #0 alsa.device = 0 alsa.card = 0 alsa.card_name = PHASE 88 Rack FW alsa.long_card_name = TerraTec Electronic Gmb PHASE 88 Rack FW (id:3, rev:1), GUID 000aac0300592827 a alsa.driver_name = snd_bebob device.bus_path = pci-:01:09.0 sysfs.path = /devices/pci:00/:00:09.0/:01:09.0/fw2/fw2.0/sound/card0 udev.id = firewire-0x000aac0300592827 device.bus = firewire device.vendor.name = Texas Instruments device.product.name = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] device.string = hw:0 device.buffering.buffer_size = 163840 device.buffering.fragment_size = 81920 device.access_mode = mmap+timer device.profile.name = 10-channels device.profile.description = 10 Channels device.description = TSB43AB22A IEEE-1394a-2000 Controller (PHY/Link) [iOHCI-Lynx] 10 Channels alsa.mixer_name = PHASE 88 Rack FW module-udev-detect.discovered = 1 device.icon_name = audio-card-firewire PulseAudio 1:4.0-0ubuntu11 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1381475/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 959616] Re: Permission denied errors when writing on any target drive
Inspired by Nick's tip I've renamed ~/.config/transmission/settings.json and ~/.config/transmission/dht.dat but kept resume and torrents folders intact. The error is gone. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/959616 Title: Permission denied errors when writing on any target drive Status in “transmission” package in Ubuntu: Confirmed Bug description: When opening a magnet link or a torrent file, I get the chance to specify where do I want the downloads to be put. However, no matter what disk or directory is chosen, after receiving around 4M (probably when it tries to write to disk for the first time) the download finishes with an error Error: Permission denied (intended_path_to_file). I have ensured that the user has write permission (touch intended_path works OK). I have tried to save on my home directory as well as to NTFS partitions, with the same results. I have also tried different torrents and magnets. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: transmission-gtk 2.50-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic 3.2.11 Uname: Linux 3.2.0-19-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.94.1-0ubuntu2 Architecture: amd64 Date: Mon Mar 19 19:54:37 2012 ExecutablePath: /usr/bin/transmission-gtk InstallationMedia: Ubuntu 12.04 LTS Precise Pangolin - Alpha amd64 (20120316) ProcEnviron: LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: transmission UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/transmission/+bug/959616/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1306363] Re: Session-Saver Plugin Missing from gedit-plugins
There is a newer version of the plugin at https://github.com/sphax3d/gedit-sessionsaver It doesn't seem stabile at the time of writing (current version needs to be patched according to Issue Tracker comments). -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1306363 Title: Session-Saver Plugin Missing from gedit-plugins Status in Gedit Developer Plugins: New Status in “gedit-plugins” package in Ubuntu: Confirmed Bug description: I open a lot of tabs in gedit, so saving each one of them is cumbersome if I need to reboot or want to continue a project the next day. The session-saver plugin addresses this need, but no longer seems to be included in the gedit-plugins package in Ubuntu 14.04. How can we get that added back? ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: gedit-plugins 3.10.1-1ubuntu2 ProcVersionSignature: Ubuntu 3.13.0-23.45-generic 3.13.8 Uname: Linux 3.13.0-23-generic x86_64 ApportVersion: 2.14.1-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 10 23:49:58 2014 InstallationDate: Installed on 2014-04-03 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140402) SourcePackage: gedit-plugins UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gdp/+bug/1306363/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1016291] Re: gimp-message outputs script-fu-Warning when it's not necessarily a warning
Thank you for the reply, Thomas. I'm attaching two test scripts. (None of them is perfect as I am not very good at Gimp scripts.) I made the tests with Gimp 2.8. First one (message-TEST-registered.scm) registers the script with script-fu so that it can be run from the Filters menu as Message Test. I recommend you run it with the following command: gimp -b '(script-fu-message-test)' The result is a popup titled Gimp Message, which is quite good, the icon however is a sad face. Alternatively, you can just start Gimp and run the script from the Filters menu: The result is an exclamation mark in the status bar, plus the message Hello World. The above results don't have the word Warning any more, but still have the icons that refer to a warning (sad face or exclamation mark). The second script (message-test-TEST-raw.scm) contains only a gimp-message command and will run immediately when Gimp is started. I recommend that you start Gimp from the command line with gimp. The result is a message on the console: script-fu-Warning: Hello World. My point is that any reference to a problem situation (sad face, exclamation mark, or the textWarning) is unnecessary and shall be replaced (maybe with an i for info icon, and respecively with the text script-fu-Message) as a gimp-message command does not necessarily indicate a warning. Thanks for taking a look! ** Attachment added: Gimp script to test the gimp-message command (registered version) https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1016291/+attachment/3850870/+files/message-TEST-registered.scm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1016291 Title: gimp-message outputs script-fu-Warning when it's not necessarily a warning Status in “gimp” package in Ubuntu: Incomplete Bug description: When I use the command 'gimp-message' in a Gimp script, the output is started withscript-fu-Warning:. I think there is no reason to assume that the message is an actual warning. This behavior may be misleading or frightening for some people, especially if they are not so experienced with the computer. Steps to reproduce: 1. Create an .scm file with the following content: (gimp-message test) 2. Run the newly created .scm file with Gimp. Actual result: - Console output reads: script-fu-Warning: test Expected result: - Console output reads: script-fu-Message: test (Gimp 2.6.11) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1016291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1016291] Re: gimp-message outputs script-fu-Warning when it's not necessarily a warning
The other script ** Attachment added: Gimp script to test the gimp-message command (raw version) https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1016291/+attachment/3850871/+files/message-test-TEST-raw.scm -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1016291 Title: gimp-message outputs script-fu-Warning when it's not necessarily a warning Status in “gimp” package in Ubuntu: Incomplete Bug description: When I use the command 'gimp-message' in a Gimp script, the output is started withscript-fu-Warning:. I think there is no reason to assume that the message is an actual warning. This behavior may be misleading or frightening for some people, especially if they are not so experienced with the computer. Steps to reproduce: 1. Create an .scm file with the following content: (gimp-message test) 2. Run the newly created .scm file with Gimp. Actual result: - Console output reads: script-fu-Warning: test Expected result: - Console output reads: script-fu-Message: test (Gimp 2.6.11) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1016291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1016291] [NEW] gimp-message outputs script-fu-Warning when it's not necessarily a warning
Public bug reported: When I use the command 'gimp-message' in a Gimp script, the output is started withscript-fu-Warning:. I think there is no reason to assume that the message is an actual warning. This behavior may be misleading or frightening for some people, especially if they are not so experienced with the computer. Steps to reproduce: 1. Create an .scm file with the following content: (gimp-message test) 2. Run the newly created .scm file with Gimp. Actual result: - Console output reads: script-fu-Warning: test Expected result: - Console output reads: script-fu-Message: test (Gimp 2.6.11) ** Affects: gimp (Ubuntu) Importance: Undecided Status: New ** Tags: console script-fu -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gimp in Ubuntu. https://bugs.launchpad.net/bugs/1016291 Title: gimp-message outputs script-fu-Warning when it's not necessarily a warning Status in “gimp” package in Ubuntu: New Bug description: When I use the command 'gimp-message' in a Gimp script, the output is started withscript-fu-Warning:. I think there is no reason to assume that the message is an actual warning. This behavior may be misleading or frightening for some people, especially if they are not so experienced with the computer. Steps to reproduce: 1. Create an .scm file with the following content: (gimp-message test) 2. Run the newly created .scm file with Gimp. Actual result: - Console output reads: script-fu-Warning: test Expected result: - Console output reads: script-fu-Message: test (Gimp 2.6.11) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gimp/+bug/1016291/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
