[Touch-packages] [Bug 1916851] Re: module-echo-cancel fails on first run
I have this problem in 20.4.2 LTS as well not sure if op is still interested. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1916851 Title: module-echo-cancel fails on first run Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have the following in `.config/pulse/default.pa`: ``` .include /etc/pulse/default.pa load-module module-echo-cancel aec_method=webrtc aec_args="analog_gain_control=0 digital_gain_control=1" ``` After a reboot, there is no echo cancelled device. And then I run `systemctl --user restart pulseaudio` and the echo cancelled devices appear. That's a bit of a hassle. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shahar39906 F pulseaudio /dev/snd/controlC1: shahar39906 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 25 16:05:48 2021 InstallationDate: Installed on 2010-10-12 (3788 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-25 (122 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.1a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.1a:bd10/24/2018:br5.11:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA dmi.product.sku: Default string dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.system.pa: 2021-02-20T16:50:24.134862 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1916851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1938477] [NEW] Screen brightness changing randomly
Public bug reported: Hello guys! The brightness of the screen on my laptop (Dell 7573 with touch ips 1080 panel) slightly changes randomly when using the laptop builtin display. It feels the same as I changed the brightness one step using the keyboard keys. Here is a video: https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing I suffer with this problem since a long time ago. I think since ubuntu 19. I tried everything you can imagine, I will make a list of things I've tried. I had gave up trying to fix this already but in a beautiful sunny day suddenly the bug stopped happening. So I decided to report this bug now because this bug does NOT happen with only this version of the kernel: Linux 5.11.0-16-generic. So that can probably e useful to help discovering the bug reason. I am choosing this version on grub every time I reboot so the bug doesn't happen. If I boot on 5.11.0-25 the bug is back. List of things I've tried: - Changing i915 parameters like enable_psr to false and many others. - Upgrading BIOS version. - Installing windows and applying all the patches on dell's website and installing ubuntu again. - Disabling "dynamic backlight control" on BIOS. Some maybe useful info: - I've tried other distros like Fedora and PopOS and the same bug happens. - The bug does not happen when using live ubuntu from usb. - When you fresh install ubuntu (I've tried with 20.04, 20.10 and 21.04) the bug doesn't happen when you have just installed the os but it starts again after the first update. The same applies to the other distro's mentioned above. - When you disable i915 driver with modeset parameter, it does not happen. - The bug does NOT happen only with this kernel version 5.11.0-16-generic, BUT it starts happening again if I lock screen and login again. So I am never locking my screen and holding this kernel version for now. Thanks guys! ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Jul 29 20:54:14 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DkmsStatus: virtualbox, 6.1.18, 5.11.0-16-generic, x86_64: installed virtualbox, 6.1.18, 5.11.0-25-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 620 [1028:07ec] InstallationDate: Installed on 2021-07-25 (4 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: Dell Inc. Inspiron 7573 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=663d1a67-7acb-428f-a6c8-a9a259a5427c ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/06/2021 dmi.bios.release: 1.18 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.18.1 dmi.board.name: 023FRC dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.18.1:bd05/06/2021:br1.18:svnDellInc.:pnInspiron7573:pvr:rvnDellInc.:rn023FRC:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7573 dmi.product.sku: 07EC dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~21.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1938477 Title: Screen brightness changing randomly Status in xorg package in Ubuntu: New Bug description: Hello guys! The brightness of the screen on my laptop (Dell 7573 with touch ips 1080 panel) slightly changes randomly when using the laptop builtin display. It feels the same as I changed the brightness one step using the keyboard keys. Here is a video: https://drive.google.com/file/d/1XQLXKLWu2TlOoGP-p8eaUGZR78713ErH/view?usp=sharing I suffer with this problem since a long time ago. I think since ubuntu 19. I tried everything you can imagine, I will make a list of things
[Touch-packages] [Bug 1914075] Re: subiquity 20.04.2 fails to install hwe kernel offline
The packages (linux-generic-hwe-20.04 and friends) appear in the manifest for focal daily builds so I believe this is fixed now. http://cdimage.ubuntu.com/focal/daily-live/20210728/focal-desktop- amd64.manifest ** Changed in: ubuntu-meta (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1914075 Title: subiquity 20.04.2 fails to install hwe kernel offline Status in ubuntu-meta package in Ubuntu: Fix Released Bug description: subiquity 20.04.2 fails to install hwe kernel offline as hwe kernel is missing from the pool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1914075/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault
I recorded pcap and captured moment just before crash. It doesnt looks like there was any MDNS at all at this moment, only suspicious is many weird DNS requests. (spinesystems.solutions is my local domain set on pc). Not sure what generated them. Small snap of these: 02:16:36.658522 IP 127.0.0.1.39766 > 127.0.0.1.53: 17063+ A? roxquromlpczqgh.spinesystems.solutions. (56) 02:16:36.658626 IP 127.0.0.1.31846 > 127.0.0.53.53: 54480+ A? roxquromlpczqgh.spinesystems.solutions. (56) 02:16:36.659106 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56) 02:16:36.659603 IP 127.0.0.53.53 > 127.0.0.1.31846: 54480 NXDomain 0/0/0 (56) 02:16:36.659644 IP 127.0.0.1.53 > 127.0.0.1.54315: 17063 NXDomain 0/0/0 (56) 02:16:36.659660 IP 127.0.0.1.53 > 127.0.0.1.39766: 17063 NXDomain 0/0/0 (56) 02:16:36.660099 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56) 02:16:36.660603 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56) 02:16:36.661082 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56) 02:16:36.661513 IP 127.0.0.53.53 > 127.0.0.1.25474: 60255 NXDomain 0/0/1 (67) 02:16:36.661898 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56) 02:16:36.662282 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56) 02:16:36.662778 IP 127.0.0.53.53 > 127.0.0.1.6126: 42840 NXDomain 0/0/0 (56) 02:16:36.663188 IP 127.0.0.1.60869 > 127.0.0.1.53: 47647+ ? xjstkkuhaqclygt.spinesystems.solutions. (56) 02:16:36.663259 IP 127.0.0.1.32600 > 127.0.0.53.53: 10939+ ? xjstkkuhaqclygt.spinesystems.solutions. (56) 02:16:36.663449 IP 127.0.0.1.36798 > 127.0.0.1.53: 30847+ ? roxquromlpczqgh.spinesystems.solutions. (56) 02:16:36.663481 IP 127.0.0.1.15565 > 127.0.0.53.53: 54137+ ? roxquromlpczqgh.spinesystems.solutions. (56) 02:16:36.664474 IP 127.0.0.1.47179 > 127.0.0.1.53: 3316+ A? roxquromlpczqgh.spinesystems.solutions. (56) 02:16:36.664563 IP 127.0.0.1.40056 > 127.0.0.53.53: 55684+ A? roxquromlpczqgh.spinesystems.solutions. (56) 02:16:36.664969 IP 10.255.255.225.55743 > 10.255.255.1.53: 60614+ [1au] A? roxquromlpczqgh.spinesystems.solutions. (67) 02:16:36.665503 IP 10.255.255.1.53 > 10.255.255.225.55743: 60614 NXDomain 0/1/1 (140) 02:16:36.666994 IP 10.255.255.225.55743 > 10.255.255.1.53: 60614+ A? roxquromlpczqgh.spinesystems.solutions. (56) 02:16:36.667494 IP 10.255.255.1.53 > 10.255.255.225.55743: 60614 NXDomain 0/1/0 (129) Maybe because there is massive timeouts in query to nonexisting domain it triggers this bug like in original issue in systemd ( https://github.com/systemd/systemd/issues/18427 )? In my ISP also all port 53 requests are force-redirected to their DNS, so they might timeout sometimes, instead of NXDomain. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Bug description: [Impact] * systemd-resolved stops replying to clients on the local LAN. * logging segfault crashes in dmesg: [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] [836786.046524] Code: Bad RIP value. [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4] [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8 * The upload backports the upstream fix (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute. [Test Plan] * Setup /etc/systemd/resolved.conf: [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. * wait for ~24-48 hours and observe if any crash happens [Where problems could occur] * Any regression would likely cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [Other Info] * Reported upstream: https://github.com/systemd/systemd/issues/18427 * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832 === Original description === systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is
[Touch-packages] [Bug 1381713] Re: Support policy query interface for file
** Changed in: apparmor (Ubuntu) Assignee: Michael (pinky999) => (unassigned) ** Changed in: apparmor (Ubuntu RTM) Assignee: Michael (pinky999) => (unassigned) ** Changed in: media-hub (Ubuntu RTM) Assignee: Michael (pinky999) => (unassigned) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1381713 Title: Support policy query interface for file Status in AppArmor: Triaged Status in Thumbnailer: Fix Released Status in apparmor package in Ubuntu: Fix Committed Status in media-hub package in Ubuntu: Triaged Status in mediascanner2 package in Ubuntu: New Status in apparmor package in Ubuntu RTM: New Status in media-hub package in Ubuntu RTM: Triaged Bug description: This bug tracks the work needed to support querying if a label can access a file. This is particularly useful with trusted helpers where an application requests access to a file and the trusted helper does something with it. For example, on Ubuntu when an app wants to play a music file, it (eventually) goes through the media-hub service. The media-hub service should be able to query if the app's policy has access to the file. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1381713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1934221] Re: systemd-resolve segfault
Denys, what kind of MDNS traffic is flowing in your network? I'm not really able to reproduce the problem locally. Maybe I'm missing this special network packets? Have you already been able to find out what triggers the issue for you? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1934221 Title: systemd-resolve segfault Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Focal: New Status in systemd source package in Hirsute: New Status in systemd source package in Impish: Fix Released Bug description: [Impact] * systemd-resolved stops replying to clients on the local LAN. * logging segfault crashes in dmesg: [836786.046514] systemd-resolve[872009]: segfault at 399 ip 0399 sp 7ffd7959a6d8 error 14 in systemd-resolved[556398695000+9000] [836786.046524] Code: Bad RIP value. [840887.303994] traps: systemd-resolve[877019] general protection fault ip:55ba402e2594 sp:7ffe8cb6bbb0 error:0 in systemd-resolved[55ba402b5000+4] [844395.313421] systemd-resolve[878503]: segfault at 208 ip 5557a249f5fa sp 7ffe686f5a90 error 6 in systemd-resolved[5557a2472000+4] [844395.313431] Code: 48 85 c0 74 0e 48 8b 8d 00 01 00 00 48 89 88 00 01 00 00 48 8b 85 00 01 00 00 48 85 c0 0f 84 1d 01 00 00 48 8b 95 f8 00 00 00 <48> 89 90 f8 00 00 00 48 c7 85 00 01 00 00 00 00 00 00 48 c7 85 f8 * The upload backports the upstream fix (https://github.com/systemd/systemd/pull/18832) to Focal & Hirsute. [Test Plan] * Setup /etc/systemd/resolved.conf: [Resolve] DNS=46.182.19.48#dns2.digitalcourage.de 1.1.1.1#cloudflare-dns.com 9.9.9.9#dns.quad9.net DNSSEC=yes DNSOverTLS=opportunistic MulticastDNS=no LLMNR=no Cache=yes DNSStubListener=yes Domains=~. * wait for ~24-48 hours and observe if any crash happens [Where problems could occur] * Any regression would likely cause crashes in systemd-resolved, making it unresponsive to DNS network name requests to local applications. [Other Info] * Reported upstream: https://github.com/systemd/systemd/issues/18427 * Fixed upstream in v248: https://github.com/systemd/systemd/pull/18832 === Original description === systemd-resolve keep crashing and it is very annoying as sometimes it severely interrupt normal dns resolving. Last uploaded report is 2d9e7378-d89b-11eb-9e14-fa163ee63de6 Typical error in dmesg: systemd-resolve[1792202]: segfault at 564ff982f3e0 ip 564ff982f3e0 sp 7ffe2fd0b758 error 15 apport hints me that problem is related to mdns #3 0x7f3e903c2f11 in sd_event_dispatch () from /lib/systemd/libsystemd-shared-245.so It might be (or not) related that some hosts with mdns in my network have ipv6 enabled. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: systemd 245.4-4ubuntu3.7 ProcVersionSignature: Ubuntu 5.4.0-75.84-generic 5.4.119 Uname: Linux 5.4.0-75-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 1 08:22:51 2021 InstallationDate: Installed on 2018-12-05 (938 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-75-generic root=UUID=54b80d5c-3d61-4919-873f-0d308083e3b9 ro quiet splash vt.handoff=7 SourcePackage: systemd UpgradeStatus: Upgraded to focal on 2020-05-22 (405 days ago) dmi.bios.date: 05/12/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1205 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX X399-E GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1205:bd05/12/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXX399-EGAMING:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1934221/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1271839] Re: ibus-ui-gtk3 big memory leak
I also faced this issue on 20.04 My ibus-related packages: gir1.2-ibus-1.0:amd64 1.5.22-2ubuntu2.1 ibus 1.5.22-2ubuntu2.1 ibus-data 1.5.22-2ubuntu2.1 ibus-gtk:amd64 1.5.22-2ubuntu2.1 ibus-gtk3:amd64 1.5.22-2ubuntu2.1 ibus-table 1.9.25-1 libibus-1.0-5:amd64 1.5.22-2ubuntu2.1 libibus-1.0-dev:amd64 1.5.22-2ubuntu2.1 libusageenvironment1 2014.01.13-1 libusageenvironment3:amd64 2020.01.19-1build1 libusermetricsinput1:amd64 1.1.1+15.10.20150915-0ubuntu1 libusermetricsoutput1:amd64 1.1.1+15.10.20150915-0ubuntu1 libusrsctp1:amd64 0.9.3.0+20190901-1 libustr-1.0-1:amd64 1.0.4-6 python3-ibus-1.0 1.5.22-2ubuntu2.1 qtdeclarative5-usermetrics0.1 1.1.1+15.10.20150915-0ubuntu1 Core dumps of both processes: https://mega.nz/file/B4ABGIxY#0dWUVbGpuKK- FKuuIvwxZv_-wog8tII6Enj_QdmKnEw ** Attachment added: "2021_07_29_10-57-19.png" https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1271839/+attachment/5514623/+files/2021_07_29_10-57-19.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1271839 Title: ibus-ui-gtk3 big memory leak Status in ibus package in Ubuntu: Confirmed Bug description: ubuntu 13.10 64bit 2gb of memory leak Also seen on Ubuntu 14.04 64Bit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ibus/+bug/1271839/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1617564] Re: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is
'accounts-plugins' is no longer included in any currently supported release of Ubuntu. I'm closing this as 'Invalid' in order to tidy the outstanding list of '100 Papercuts' bug reports. ** Changed in: hundredpapercuts Status: Confirmed => Invalid ** Changed in: account-plugins (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to account-plugins in Ubuntu. https://bugs.launchpad.net/bugs/1617564 Title: [master] package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit- options.d/www.facebook.com.conf', which is also in package account- plugin-facebook 0.12+16.04.20160126-0ubuntu1 Status in One Hundred Papercuts: Invalid Status in account-plugins package in Ubuntu: Invalid Status in kaccounts-providers package in Ubuntu: Won't Fix Bug description: showing this error when installing kde environment in ubuntu 16.04. it say kaccounts niot installed. so i think it may cause some security issue ProblemType: Package DistroRelease: Ubuntu 16.04 Package: kaccounts-providers (not installed) ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15 Uname: Linux 4.4.0-34-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 Date: Sat Aug 27 18:11:18 2016 DuplicateSignature: package:kaccounts-providers:(not installed) Unpacking kde-config-telepathy-accounts (4:15.12.3-0ubuntu1) ... dpkg: error processing archive /var/cache/apt/archives/kde-config-telepathy-accounts_4%3a15.12.3-0ubuntu1_amd64.deb (--unpack): trying to overwrite '/usr/share/accounts/services/google-im.service', which is also in package account-plugin-google 0.12+16.04.20160126-0ubuntu1 ErrorMessage: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 InstallationDate: Installed on 2016-08-25 (1 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.12~ubuntu16.04.1 SourcePackage: kaccounts-providers Title: package kaccounts-providers (not installed) failed to install/upgrade: trying to overwrite '/etc/signon-ui/webkit-options.d/www.facebook.com.conf', which is also in package account-plugin-facebook 0.12+16.04.20160126-0ubuntu1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1617564/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1658374] Re: package libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/ch
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. This release of Ubuntu is no longer receiving maintenance updates. If this is still an issue using a maintained version of Ubuntu then please let us know otherwise this report can be left to expire in approximately 60 days time. ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: kmod (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to kmod in Ubuntu. https://bugs.launchpad.net/bugs/1658374 Title: package libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 Status in One Hundred Papercuts: Incomplete Status in kmod package in Ubuntu: Incomplete Bug description: where can i found this information ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 Date: Sat Jan 21 18:45:51 2017 Dependencies: gcc-6-base 6.0.1-0ubuntu1 libc6 2.23-0ubuntu5 libgcc1 1:6.0.1-0ubuntu1 DuplicateSignature: package:libkmod2:22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] Unpacking libkmod2:i386 (22-1ubuntu4) ... dpkg: error processing archive /var/cache/apt/archives/libkmod2_22-1ubuntu4_i386.deb (--unpack): trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 ErrorMessage: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 InstallationDate: Installed on 2014-05-04 (993 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) RelatedPackageVersions: dpkg 1.18.4ubuntu1.1 apt 1.2.18 SourcePackage: kmod Title: package libkmod2 22-1ubuntu4 [modified: usr/share/doc/libkmod2/changelog.Debian.gz] failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libkmod2/changelog.Debian.gz', which is different from other instances of package libkmod2:i386 UpgradeStatus: Upgraded to xenial on 2016-09-25 (118 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1658374/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1402135] Re: Adding function in unity scope tool to fine tune the scope template
'unity8' is no longer included in any currently supported release of
Ubuntu. I'm closing this as 'Invalid' in order to tidy up the
outstanding list of '100 Papercuts' bug reports.
** Changed in: hundredpapercuts
Importance: Undecided => Wishlist
** Changed in: hundredpapercuts
Status: New => Invalid
** Changed in: unity8 (Ubuntu)
Status: Triaged => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1402135
Title:
Adding function in unity scope tool to fine tune the scope template
Status in One Hundred Papercuts:
Invalid
Status in unity8 package in Ubuntu:
Invalid
Bug description:
Currently, unity scope tool is a good unity for developing scopes on
desktop. I am thinking to add one more function to make it more useful
to the developers. A graphic tool can be helpful to the design "what
you see is what you get".
Currently, a developer can tweak the template definition:
const static string WEATHER_TEMPLATE =
R"(
{
"schema-version": 1,
"template": {
"category-layout": "grid",
"card-layout": "horizontal",
"card-size": "small"
},
"components": {
"title": "title",
"art" : {
"field": "art"
},
"subtitle": "subtitle"
}
}
)";
If a developer does not know the "category-layout" options for "grid"
or "carousel" etc, it would be difficult for them to make the
adjustment. The developer has to find some documents for it. It would
be good to have a graphic tool to help to design the template like the
"design" for QML apps, or some similar tool in the android eclipse to
help to fine tune the LIST/GRID templates . Microsoft Windows phone
also has some similar designs like this.
Ideally, the "category-layout" can have a dropbox to select the
available layouts ("grid", "carousel", "vertical-journal" etc), "card-
layout" has options for "horizontal " or what options there. Some
dummy data can be filled to show how the scope looks like. Even
further, some of the pre-designed good looking templates are already
there for NEWS, MUSIC, VIDEO, WEATHER etc so developer can straightly
start to make use of the well-designed templates there. They may even
drag and drop/move to fine-tune the positions of the elements in the
graphic view.
In this case, a developer can easily customize the look and feel of
the scopes of their development very quickly.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/1402135/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1381713] Re: Support policy query interface for file
** Changed in: apparmor (Ubuntu) Assignee: (unassigned) => Michael (pinky999) ** Changed in: apparmor (Ubuntu RTM) Assignee: (unassigned) => Michael (pinky999) ** Changed in: media-hub (Ubuntu RTM) Assignee: (unassigned) => Michael (pinky999) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1381713 Title: Support policy query interface for file Status in AppArmor: Triaged Status in Thumbnailer: Fix Released Status in apparmor package in Ubuntu: Fix Committed Status in media-hub package in Ubuntu: Triaged Status in mediascanner2 package in Ubuntu: New Status in apparmor package in Ubuntu RTM: New Status in media-hub package in Ubuntu RTM: Triaged Bug description: This bug tracks the work needed to support querying if a label can access a file. This is particularly useful with trusted helpers where an application requests access to a file and the trusted helper does something with it. For example, on Ubuntu when an app wants to play a music file, it (eventually) goes through the media-hub service. The media-hub service should be able to query if the app's policy has access to the file. To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1381713/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1736259] Re: apport-gtk segfault
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: apport (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apport in Ubuntu. https://bugs.launchpad.net/bugs/1736259 Title: apport-gtk segfault Status in apport package in Ubuntu: Confirmed Bug description: [ 717.875242] apport-gtk[2587]: segfault at 0 ip 7f8ddd065659 sp 7ffd91d18bb0 error 4 in libgtk-3.so.0.2200.25[7f8ddcd7e000+6fd000] Please, assist - which log files could be useful? ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: apport 2.20.7-0ubuntu3.5 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CrashReports: 640:121:119:21471288:2017-12-01 00:21:07.463343417 +0200:2017-12-01 00:20:46.635068070 +0200:/var/crash/_usr_bin_gnome-shell.121.crash 640:0:119:6944675:2017-12-04 23:01:59.209724958 +0200:2017-12-04 23:01:54.621558919 +0200:/var/crash/_usr_share_apport_apport-gtk.0.crash 640:1000:119:7570257:2017-12-01 00:11:17.960471870 +0200:2017-12-01 00:11:17.964471907 +0200:/var/crash/_usr_bin_Xwayland.1000.crash 640:1000:119:41459720:2017-12-01 00:11:10.500402699 +0200:2017-12-01 00:12:47.737350953 +0200:/var/crash/_usr_bin_gnome-shell.1000.crash CurrentDesktop: ubuntu:GNOME Date: Mon Dec 4 23:12:31 2017 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-19 (15 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: apport UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1736259/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1414029] Re: HERE asks to download the Android app on first launch
'webbrowser-app' is no longer included in any currently supported release of Ubuntu. I'm closing this as 'Invalid' in order to tidy up the outstanding list of '100 Papercuts' bug reports. ** Changed in: hundredpapercuts Status: Confirmed => Invalid ** Changed in: webbrowser-app (Ubuntu) Status: Confirmed => Invalid ** Changed in: webbrowser-app (Ubuntu RTM) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to webbrowser-app in Ubuntu. https://bugs.launchpad.net/bugs/1414029 Title: HERE asks to download the Android app on first launch Status in One Hundred Papercuts: Invalid Status in webbrowser-app package in Ubuntu: Invalid Status in webbrowser-app package in Ubuntu RTM: Invalid Bug description: Prerequisites: HERE webapp has never been launched before Steps to reproduce: 1. Launch HERE 2. Accept location prompt 3. Dismiss prompts until you see the one asking to install the Android app Expected result: This prompt should never be shown since we're on Ubuntu Actual result: It is shown and could confuse users apart from being irrelevant ProblemType: Bug DistroRelease: Ubuntu RTM 14.09 Package: webapp-container 0.23+15.04.20141218~rtm-0ubuntu1 [origin: unknown] Uname: Linux 3.4.67 armv7l ApportVersion: 2.14.7-0ubuntu8 Architecture: armhf Date: Fri Jan 23 14:44:40 2015 InstallationDate: Installed on 2015-01-23 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20150123-030204) SourcePackage: webbrowser-app UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1414029/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1363049] Re: [version bump] Please include LVM2 version > 2.02.106
Further to comment #2 I'm belatedly closing the 100 Papercuts task as fixed. ** Changed in: hundredpapercuts Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1363049 Title: [version bump] Please include LVM2 version > 2.02.106 Status in One Hundred Papercuts: Fix Released Status in lvm2 package in Ubuntu: Fix Released Bug description: LVM2 introduced LVM Caching with 2.02.106 to allow backend cache (SSD) for other block storage (HDD). The packages are built in Debian Sid, and it would be good to also include this package in Ubuntu. https://packages.debian.org/sid/lvm2 http://metadata.ftp-master.debian.org/changelogs//main/l/lvm2/lvm2_2.02.109-1_changelog RHEL7 has this feature as a tech preview: https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/7.0_Release_Notes/chap-Red_Hat_Enterprise_Linux-7.0_Release_Notes-Storage.html Though Trusty's kernel version is too old to support LVM Cache, Utopic's 3.16 kernel should work out of the box. Support was added in 3.14. Benefit over bcache and dm-cache is that the caching LV can be added and removed without the need for reformatting the FS. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1363049/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1267067] Re: Postinstallation failed
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 14.04 (trusty) reached end-of-life on April 25,2019. I'm setting this bug to "Incomplete" as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: hicolor-icon-theme (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to hicolor-icon-theme in Ubuntu. https://bugs.launchpad.net/bugs/1267067 Title: Postinstallation failed Status in One Hundred Papercuts: Incomplete Status in hicolor-icon-theme package in Ubuntu: Incomplete Bug description: By upgrade trusty I got the error-message: Trigger für hicolor-icon-theme werden verarbeitet ... (gtk-update-icon-cache-3.0:5100): GdkPixbuf-WARNING **: Cannot open pixbuf loader module file '/usr/lib/x86_64-linux-gnu/gdk- pixbuf-2.0/2.10.0/loaders.cache': Datei oder Verzeichnis nicht gefunden This likely means that your installation is broken. Try running the command gdk-pixbuf-query-loaders > /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache to make things work again for the time being. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hicolor-icon-theme 0.13-1 ProcVersionSignature: Ubuntu 3.12.0-7.15-generic 3.12.4 Uname: Linux 3.12.0-7-generic x86_64 ApportVersion: 2.12.7-0ubuntu6 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jan 8 12:14:58 2014 Dependencies: InstallationDate: Installed on 2013-11-10 (58 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20131110) PackageArchitecture: all ProcEnviron: LANGUAGE=de_DE PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: hicolor-icon-theme UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1267067/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1328610] Re: ubuntu-sdk cannot create emulator device without depending on ubuntu-emulator (missing dependency)
'ubuntu-touch-meta' is no longer included in any currently supported release of Ubuntu. I'm closing this as 'Invalid' in order to tidy up the outstanding list of '100 Papercuts' bug reports. ** Changed in: hundredpapercuts Status: Confirmed => Invalid ** Changed in: ubuntu-touch-meta (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-touch-meta in Ubuntu. https://bugs.launchpad.net/bugs/1328610 Title: ubuntu-sdk cannot create emulator device without depending on ubuntu- emulator (missing dependency) Status in One Hundred Papercuts: Invalid Status in ubuntu-touch-meta package in Ubuntu: Invalid Bug description: Hi. Running daily 14.10 on a new machine I installed ubuntu-sdk and tried to add a emulator device. That failed (after prompting for my password) without any obvious traces. I checked that ubuntu-emulator package is not installed and installing it fixed the issue. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: ubuntu-sdk 1.145 ProcVersionSignature: Ubuntu 3.15.0-5.10-generic 3.15.0-rc8 Uname: Linux 3.15.0-5-generic x86_64 NonfreeKernelModules: fglrx ApportVersion: 2.14.3-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Jun 10 18:55:07 2014 InstallationDate: Installed on 2014-01-13 (148 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140112) SourcePackage: ubuntu-touch-meta UpgradeStatus: Upgraded to utopic on 2014-06-09 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1328610/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1571154] Re: No wifi in 16.04 because of permission issue not having systemd-network permission
We are sorry that we do not always have the capacity to review all reported bugs in a timely manner. Ubuntu 16.04 (xenial) reached end-of-life on April 29, 2021. I'm setting this bug to "Incomplete" as it's not seen any activity for some time. If this is still an issue when using a currently maintained release of Ubuntu then please let us know otherwise this bug report can be left to expire in approximately 60 days time. ** Changed in: hundredpapercuts Status: Confirmed => Incomplete ** Changed in: network-manager (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1571154 Title: No wifi in 16.04 because of permission issue not having systemd- network permission Status in One Hundred Papercuts: Incomplete Status in network-manager package in Ubuntu: Incomplete Bug description: After upgrading to 16.04, I had no access to wifi. It only worked as root. I fixed it by adding my user to the new "systemd-network" group. The existing users (or those in group netdev) should be automatically be added to "systemd-network" group during upgrade. To manage notifications about this bug go to: https://bugs.launchpad.net/hundredpapercuts/+bug/1571154/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1925434] Re: New bugfix release 21.0.3
Working with the version 21.0.3-0ubuntu0.2~20.04.1 for several days, on: Operating System: Kubuntu 20.04.2 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 Kernel Version: 5.4.0-80-generic OS Type: 64-bit Processors: 4 � AMD A8-6500T APU with Radeon(tm) HD Graphics Memory: 7.0 GiB of RAM Looks OK, marking as verified. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1925434 Title: New bugfix release 21.0.3 Status in mesa package in Ubuntu: Invalid Status in mesa source package in Focal: Fix Committed Status in mesa source package in Hirsute: Fix Committed Bug description: [Impact] This is the last point-release of the 21.0.x-series, we should put it in hirsute so latest bugfixes would get there, and in focal for 20.04.3 image. [Test case] Install the updates, test desktop use and some basic games etc on at least AMD and Intel hw. [Where things could go wrong] It's possible that some apps (like games) might regress on some hw, but there should not be a big risk for more wider bugs appearing in this update, since upstream and vendor (Intel) CI machinery have tested these. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1925434/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1698083] Re: Maximize vertically/horizontally doesn't work (in some apps)
** Tags removed: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1698083 Title: Maximize vertically/horizontally doesn't work (in some apps) Status in GTK+: Unknown Status in gnome-shell package in Ubuntu: Triaged Status in gtk+3.0 package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Triaged Bug description: Upstream: https://gitlab.gnome.org/GNOME/gtk/issues/539 In Gnome Tweak Tool you can configure vertical maximizing for: Windows > Titlebar Actions > Middle-Click However this feature seems to get ignored in Wayland sessions (it just maximizes fully instead). It only works correctly in Xorg Gnome sessions. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: gnome-shell 3.24.2-0ubuntu6 ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15 Uname: Linux 4.10.0-22-generic x86_64 ApportVersion: 2.20.5-0ubuntu4 Architecture: amd64 Date: Thu Jun 15 14:46:04 2017 DisplayManager: lightdm InstallationDate: Installed on 2017-05-03 (43 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1698083/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1303316] Re: Digital S/PDIF output is not present in 5.1 mode
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: pulseaudio (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1303316 Title: Digital S/PDIF output is not present in 5.1 mode Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have the sound connected through digital S / PDIF Sound works properly selecting stereo, but can not get it to work using 5.1 When I select stereo sound, appears on the tab below to phonon spdif output option. When I select Output 5.1, that option does not appear. I imagine the error will also occur selecting 7.1 Deputy screenshots. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: phonon 4:4.7.0really4.6.0-0ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-60.91-generic 3.2.55 Uname: Linux 3.2.0-60-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: amd64 Date: Sun Apr 6 13:12:42 2014 InstallationMedia: Kubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MarkForUpload: True ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: phonon UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1303316/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1903909] Re: Audio keeps on popping and "bitcrunching" (digital output) at semi-random constant intervals
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: pulseaudio (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1903909 Title: Audio keeps on popping and "bitcrunching" (digital output) at semi- random constant intervals Status in pulseaudio package in Ubuntu: Won't Fix Bug description: This is with both of my sound cards, no matter which one I choose, the digital audio output is either popping with loud snaps or "frequency- modulating" (sounds around the same like someone would've filtered everything into a very narrow bandwidth for a couple of seconds.) ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-29.31-generic 5.8.14 Uname: Linux 5.8.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Nov 11 22:21:38 2020 SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-11-11 (0 days ago) dmi.bios.date: 06/26/2012 dmi.bios.release: 0.0 dmi.bios.vendor: Intel Corp. dmi.bios.version: WBIBX10J.86A.0336.2012.0626.0141 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55WB dmi.board.vendor: Intel Corporation dmi.board.version: AAE64798-206 dmi.chassis.type: 2 dmi.ec.firmware.release: 0.0 dmi.modalias: dmi:bvnIntelCorp.:bvrWBIBX10J.86A.0336.2012.0626.0141:bd06/26/2012:br0.0:efr0.0:svn:pn:pvr:rvnIntelCorporation:rnDP55WB:rvrAAE64798-206:cvn:ct2:cvr: modified.conffile..etc.pulse.daemon.conf: [modified] modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.daemon.conf: 2020-11-11T22:18:21.176026 mtime.conffile..etc.pulse.default.pa: 2020-11-11T17:20:02.886116 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1903909/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1905185] Re: [ThinkPad T14s Gen 1 20UJ0014IX] Internal microphone randomly does not work
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: pulseaudio (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1905185 Title: [ThinkPad T14s Gen 1 20UJ0014IX] Internal microphone randomly does not work Status in pulseaudio package in Ubuntu: Won't Fix Bug description: good evening, I have a problem with internal microphone, sometimes it works and sometimes it doesn't, it happens randomly, just a restart my pc should be Ubuntu certified thanks ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: roxibar73 1518 F pulseaudio /dev/snd/controlC0: roxibar73 1518 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Nov 22 18:32:04 2020 InstallationDate: Installed on 2020-11-20 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_Card: HDA-Intel - HD-Audio Generic Symptom_Jack: Speaker, Internal Title: [20UJ0014IX, Realtek ALC257, Speaker, Internal] Pulseaudio fails to detect card UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/15/2020 dmi.bios.release: 1.25 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET56W(1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UJ0014IX dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.25 dmi.modalias: dmi:bvnLENOVO:bvrR1CET56W(1.25):bd09/15/2020:br1.25:efr1.25:svnLENOVO:pn20UJ0014IX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UJ0014IX:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UJ0014IX dmi.product.sku: LENOVO_MT_20UJ_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1905185/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916722] Re: Pulseaudio fails to start after reboot if home partition is encrypted
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1916722 Title: Pulseaudio fails to start after reboot if home partition is encrypted Status in pulseaudio package in Ubuntu: Won't Fix Bug description: It seems that with Ubuntu 20.10, Pulseaudio now tries to start as main user too early, before user logs in and the home partition is decrypted. Probably pulseaudio should not start as main user before login of this user. Starting pulseaudio manually after login works. grep 'pulseaudio' /var/log/syslog Feb 24 10:52:31 aziber systemd[1451]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. Feb 24 10:52:31 aziber dbus-daemon[972]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.30' (uid=123 pid=1497 comm="/usr/bin/pulseaudio --daemonize=no --log-target=jo" label="unconfined") Feb 24 10:52:38 aziber systemd[3631]: Not generating service for XDG autostart app-pulseaudio-autostart.service, startup phases are not supported. Feb 24 10:52:38 aziber pulseaudio[3690]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 1. Feb 24 10:52:38 aziber pulseaudio[3899]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 2. Feb 24 10:52:39 aziber pulseaudio[4128]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 3. Feb 24 10:52:39 aziber pulseaudio[4311]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 4. Feb 24 10:52:39 aziber pulseaudio[4493]: Failed to create secure directory (/home/anton/.config/pulse): No such file or directory Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process exited, code=exited, status=1/FAILURE Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart job, restart counter is at 5. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Start request repeated too quickly. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 'exit-code'. Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.socket: Failed with result 'service-start-limit-hit'. Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: Connection failure: Connection refused Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: pa_context_connect() failed: Connection refused Feb 24 10:52:42 aziber gnome-session[5663]: gnome-session-binary[5663]: WARNING: App 'pulseaudio.desktop' exited with code 1 Feb 24 10:52:42 aziber gnome-session-binary[5663]: WARNING: App 'pulseaudio.desktop' exited with code 1 Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed to add PIDs to scope's control group: No such process Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed with result
[Touch-packages] [Bug 1907114] Re: [Acer Swift 3 SF314-42] Audio popping at low volumes
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: alsa-lib (Ubuntu) Status: New => Won't Fix ** Changed in: pulseaudio (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1907114 Title: [Acer Swift 3 SF314-42] Audio popping at low volumes Status in alsa-lib package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: My AMD Renoir-powered machine has audio popping at low volumes and when sound stops briefly. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-31.33-generic 5.8.17 Uname: Linux 5.8.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC3: dustin15118 F pulseaudio /dev/snd/controlC1: dustin15118 F pulseaudio /dev/snd/controlC2: dustin15118 F pulseaudio /dev/snd/controlC0: dustin15118 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Dec 7 07:47:38 2020 InstallationDate: Installed on 2020-07-15 (144 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/08/2020 dmi.bios.release: 1.4 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Kona_RN dmi.board.vendor: RO dmi.board.version: V1.04 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.04 dmi.ec.firmware.release: 1.4 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.04:bd06/08/2020:br1.4:efr1.4:svnAcer:pnSwiftSF314-42:pvrV1.04:rvnRO:rnKona_RN:rvrV1.04:cvnAcer:ct10:cvrV1.04: dmi.product.family: Swift 3 dmi.product.name: Swift SF314-42 dmi.product.sku: dmi.product.version: V1.04 dmi.sys.vendor: Acer modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-11-04T18:16:16.625370 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1907114/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1909703] Re: sound garbled in 20.10 with intel hdmi audio
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: pulseaudio (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1909703 Title: sound garbled in 20.10 with intel hdmi audio Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I've been having ongoing issues with pulse and my nvidia video card doing hdmi audio, so I thought I'd try using my builtin intel HDMI port for audio instead. However, when I switch the HDMI cable to that port, and select it in pulse, all the audio sounds crackly and garbled, like it's trying to play twice as many samples per second as it should. given this is with open source drivers, this may be a kernel issue and not a pulse issue, but I'm not sure how to fully determine that. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-33.36-lowlatency 5.8.17 Uname: Linux 5.8.0-33-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon Date: Wed Dec 30 18:05:38 2020 InstallationDate: Installed on 2020-07-15 (168 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-24 (68 days ago) dmi.bios.date: 04/18/2018 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3503 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: GRYPHON Z97 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3503:bd04/18/2018:br4.6:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnGRYPHONZ97:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.sku: All dmi.product.version: System Version dmi.sys.vendor: ASUS modified.conffile..etc.pulse.default.pa: [modified] mtime.conffile..etc.pulse.default.pa: 2020-09-10T05:59:01.429804 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1909703/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1912052] Re: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset)
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1912052 Title: [Acer Spin 5 - SP513-54N] External headset microphone not working on Ubuntu 20.10 (not even wired, cable headset) Status in Linux: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Recently, external microphone has stopped working while using classic wired audio combo jack headset. Basics: 1) Headset's microphone works fine both in MS Windows on the same machine and on older Xubuntu on another machine. 2) Internal laptop mic works normally. 3) Yes, I have mic unmuted in settings. I've followed whole step1 from this troubleshoot guide: https://help.ubuntu.com/community/SoundTroubleshootingProcedure Did not help. There are more information with screenshots here: https://askubuntu.com/questions/1305942/external-headset-microphone- not-working-on-ubuntu-20-10-not-even-wired-cable-h: ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.1 ProcVersionSignature: Ubuntu 5.8.0-38.43-generic 5.8.18 Uname: Linux 5.8.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crysman2301 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 16 13:31:13 2021 InstallationDate: Installed on 2020-06-19 (210 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-12-08 (38 days ago) dmi.bios.date: 07/17/2020 dmi.bios.release: 1.5 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.05 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.05 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.05 dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.05:bd07/17/2020:br1.5:efr1.2:svnAcer:pnSpinSP513-54N:pvrV1.05:rvnIL:rnCaboom_IL:rvrV1.05:cvnAcer:ct31:cvrV1.05: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.05 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1912052/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1938144] Re: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange
Hello Athos, thanks for looking into this! This is reproducible without Ansible, that was just use-case that brought up the issue. I've further narrowed it down to the following setup: Server: /usr/sbin/sshd -d -p -f /dev/null -o GSSAPIKeyExchange=yes -o GSSAPIAuthentication=yes Client: ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@compute-test -v -p -o GSSAPIKeyExchange=yes -F /dev/null I think this should make it independent from my local config, right? Obviously there is also Kerberos involved, which I would call configured pretty standard in our environment, but I can have a look at that config as well, if this is desired. The problem will not arise when: - The client has no valid Kerberos-Key (unset KRB5CCNAME) - If any of the the GSSAPI* options is missing on client or server - If the order of "gssapi-with-mic,gssapi-keyex" is switched (!) ** Changed in: openssh (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1938144 Title: monitor_read: unpermitted request 48 on server while attempting GSSAPI key exchange Status in openssh package in Ubuntu: New Bug description: I'm using openssh 1:8.2p1-4ubuntu0.2 on Ubuntu 20.04.2 LTS (client and server) with the option "GSSAPIKeyExchange=yes", and this causes the connection to fail. The server has GSSAPI (Kerberos authentication) enabled, but is is only used for non-root users (root uses SSH keys). Client command: ssh -o PreferredAuthentications=gssapi-with-mic,gssapi-keyex root@server -v -p -o GSSAPIKeyExchange=yes Client log: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2, OpenSSL 1.1.1f 31 Mar 2020 debug1: Reading configuration data /home/user/.ssh/config debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: include /etc/ssh/ssh_config.d/*.conf matched no files debug1: /etc/ssh/ssh_config line 21: Applying options for * debug1: Connecting to compute-test [130.75.80.46] port . debug1: Connection established. debug1: identity file /home/rother/.ssh/id_rsa type 0 debug1: identity file /home/rother/.ssh/id_rsa-cert type -1 debug1: identity file /home/rother/.ssh/id_dsa type -1 debug1: identity file /home/rother/.ssh/id_dsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa type -1 debug1: identity file /home/rother/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk type -1 debug1: identity file /home/rother/.ssh/id_ecdsa_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519 type -1 debug1: identity file /home/rother/.ssh/id_ed25519-cert type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk type -1 debug1: identity file /home/rother/.ssh/id_ed25519_sk-cert type -1 debug1: identity file /home/rother/.ssh/id_xmss type -1 debug1: identity file /home/rother/.ssh/id_xmss-cert type -1 debug1: Local version string SSH-2.0-OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: Remote protocol version 2.0, remote software version OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 debug1: match: OpenSSH_8.2p1 Ubuntu-4ubuntu0.2 pat OpenSSH* compat 0x0400 debug1: Authenticating to server: as 'root' debug1: Offering GSSAPI proposal: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-group14-sha1-toWM5Slw5Ew8Mqkay+al2g==,gss-gex-sha1-eipGX3TCiQSrx573bT1o1Q==,gss-group14-sha1-eipGX3TCiQSrx573bT1o1Q== debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: algorithm: gss-gex-sha1-toWM5Slw5Ew8Mqkay+al2g== debug1: kex: host key algorithm: ecdsa-sha2-nistp256 debug1: kex: server->client cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: kex: client->server cipher: chacha20-poly1...@openssh.com MAC: compression: none debug1: Doing group exchange debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Received GSSAPI_COMPLETE debug1: Calling gss_init_sec_context debug1: Delegating credentials debug1: Rekey has happened - updating saved versions debug1: rekey out after 134217728 blocks debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: rekey in after 134217728 blocks debug1: Will attempt key: /home/rother/.ssh/id_rsa RSA SHA256:n/EY/cGjgd/r+7JpuqODxIotHHLsYptGXYx9GlKCWSM agent debug1: Will attempt key: /home/rother/.ssh/root_id_rsa RSA SHA256:yCLAID9FMILharHmDpCB8wW8eiA+iHa4oQKLODbbzKw agent debug1: Will attempt key: /home/user/.ssh/id_dsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa debug1: Will attempt key: /home/user/.ssh/id_ecdsa_sk debug1: Will attempt key: /home/user/.ssh/id_ed25519 debug1: Will attempt key: /home/user/.ssh/id_ed25519_sk debug1: Will attempt key: /home/user/.ssh/id_xmss debug1: SSH2_MSG_EXT_INFO received debug1: kex_input_ext_info:
[Touch-packages] [Bug 1838151] Re: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs).
** Tags removed: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1838151 Title: Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support (Bluetooth A2DP codecs). Status in PulseAudio: Fix Released Status in bluez package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Committed Status in Arch Linux: New Bug description: Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all other major platforms (Windows, MacOS, ChromeOS, Android, iOS). Modern Bluetooth headsets (such as the Bose QC series headphones, many others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As it currently stands, Ubuntu defaults to only supporting HSP headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time. The ChromiumOS team recently tackled this issue - https://bugs.chromium.org/p/chromium/issues/detail?id=843048 Their efforts may assist in bringing this to Ubuntu, however it appears that there are quite a lot of differences considering they have developed their own audio server solution etc. The Bluetooth Telephony Working Group published the HFP 1.6 spec in May 2011 - https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193 Patches have been proposed in the past for this issue to the kernel and PulseAudio: PulseAudio: https://patchwork.freedesktop.org/patch/245272/ Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html It appears that the Chromium OS team applied the same kernel patch: https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: pulseaudio 1:12.2-2ubuntu3 ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8 Uname: Linux 5.0.0-20-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jnappi 2777 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Jul 27 11:08:29 2019 EcryptfsInUse: Yes InstallationDate: Installed on 2017-11-04 (629 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago) dmi.bios.date: 06/07/2016 dmi.bios.vendor: LENOVO dmi.bios.version: R07ET67W (2.07 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FW000TUS dmi.board.vendor: LENOVO dmi.board.version: SDK0J40705 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T460p dmi.product.name: 20FW000TUS dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p dmi.product.version: ThinkPad T460p dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1838151/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1877194] Re: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot
** Tags removed: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1877194 Title: switch-on-connect mistakes startup for USB hotplug, so seemingly ignores the old default device on reboot Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Triaged Bug description: Similar to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 Only difference is that it does not reset to HDMI output, but to one of my USB-outputs. It does not respect the change I made after reboot. In short: 1. Boot system 2. "Analogue Output - RODE NT-USB" is selected by default. I want to use "Line Out - Built-in Audio", which I choose. 3. Reboot. 4 Output device is now back to "Analogue Output - RODE NT-USB". ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: marcus 1604 F pulseaudio /dev/snd/controlC0: marcus 1604 F pulseaudio /dev/snd/controlC1: marcus 1604 F pulseaudio /dev/snd/pcmC1D0c: marcus 1604 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 23:40:08 2020 InstallationDate: Installed on 2020-05-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/27/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3703 dmi.board.asset.tag: Default string dmi.board.name: MAXIMUS VIII HERO dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3703:bd12/27/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnMAXIMUSVIIIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1877194/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1916851] Re: module-echo-cancel fails on first run
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: pulseaudio (Ubuntu) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1916851 Title: module-echo-cancel fails on first run Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Won't Fix Bug description: I have the following in `.config/pulse/default.pa`: ``` .include /etc/pulse/default.pa load-module module-echo-cancel aec_method=webrtc aec_args="analog_gain_control=0 digital_gain_control=1" ``` After a reboot, there is no echo cancelled device. And then I run `systemctl --user restart pulseaudio` and the echo cancelled devices appear. That's a bit of a hassle. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-44.50-generic 5.8.18 Uname: Linux 5.8.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: shahar39906 F pulseaudio /dev/snd/controlC1: shahar39906 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Feb 25 16:05:48 2021 InstallationDate: Installed on 2010-10-12 (3788 days ago) InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) SourcePackage: pulseaudio UpgradeStatus: Upgraded to groovy on 2020-10-25 (122 days ago) dmi.bios.date: 10/24/2018 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.1a dmi.board.asset.tag: Default string dmi.board.name: X10SRA dmi.board.vendor: Supermicro dmi.board.version: 1.01 dmi.chassis.asset.tag: Default string dmi.chassis.type: 17 dmi.chassis.vendor: Supermicro dmi.chassis.version: 0123456789 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.1a:bd10/24/2018:br5.11:svnSupermicro:pnX10SRA:pvr0123456789:rvnSupermicro:rnX10SRA:rvr1.01:cvnSupermicro:ct17:cvr0123456789: dmi.product.family: Default string dmi.product.name: X10SRA dmi.product.sku: Default string dmi.product.version: 0123456789 dmi.sys.vendor: Supermicro modified.conffile..etc.pulse.system.pa: [modified] mtime.conffile..etc.pulse.system.pa: 2021-02-20T16:50:24.134862 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1916851/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1892377] Re: Please add LDAC support in pulseaudio-module-bluetooth
** Tags removed: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1892377 Title: Please add LDAC support in pulseaudio-module-bluetooth Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Committed Bug description: There is a project which enables these codecs in pulseaudio (by adding profiles for these): https://github.com/EHfive/pulseaudio-modules-bt For LDAC (codec) it uses libldac from the AOSP project: https://android.googlesource.com/platform/external/libldac There is a libldac dispatcher by the same author: https://github.com/EHfive/ldacBT It would be nice to have this functionality out-of-the-box in Ubuntu. This cannot be merged to PulseAudio upstream because the Android libldac library is under Apache License 2.0 which is incompatible with pulseaudio license LGPL 2.1: https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/36#note_160736 To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1892377/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1899962] Re: Wrong audio output device selected on Raspberry Pi Desktop
** Tags removed: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1899962 Title: Wrong audio output device selected on Raspberry Pi Desktop Status in pulseaudio package in Ubuntu: Incomplete Bug description: On each boot, an incorrect audio output device is selected, at least when HDMI audio output is in use (still need to test the TV/aux output; will update the bug when done). Specifically, the settings application lists "Multichannel Output - Built-in Audio" as the selected output device. However, for audio to play through the connected HDMI device, "Analog Output - Built-in Audio" must be selected instead. Unfortunately, this setting will be lost on subsequent boots. A workaround is to remove the following lines from /etc/pulse/default.pa: ### Use hot-plugged devices like Bluetooth or USB automatically (LP: #1702794) .ifexists module-switch-on-connect.so load-module module-switch-on-connect .endif However, removal of these lines will (as the comment suggests) result in hot-plugged USB devices *not* being automatically selected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1899962/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1881699] Re: No analog output
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1881699 Title: No analog output Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Won't Fix Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions --
[Touch-packages] [Bug 1900812] Re: pulseaudio crashed with SIGSEGV in pa_sink_move_streams_to_default_sink() from report_jack_state() from mixer_class_event() from hctl_elem_event_handler() from snd_h
** Tags added: fixed-in-13.99.3 fixed-upstream ** Changed in: pulseaudio (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1900812 Title: pulseaudio crashed with SIGSEGV in pa_sink_move_streams_to_default_sink() from report_jack_state() from mixer_class_event() from hctl_elem_event_handler() from snd_hctl_elem_throw_event() Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Groovy: Fix Released Bug description: * Impact There is a segfault issue started with the recent update * Test case We don't have specific steps to trigger the issue so test for regression and verify that reports stop on https://errors.ubuntu.com/problem/31c6bfaf0ac65939a763307ca3d3a4f27f38e9f0 * Regression potential The regression was created by a fix for gnome-control-center device selection issues, check that the settings still work correctly, allowing to change devices and showing the active one as selected To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1900812/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1921766] Re: Output device not remembered after connecting/disconnecting another
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: pulseaudio (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1921766 Title: Output device not remembered after connecting/disconnecting another Status in PulseAudio: Unknown Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Ubuntu 20.10 running pulseaudio version 13.99.2 is my daily driver for development work. I run it on a Lenovo X1 Carbon 8th Generation connected to dual monitors via a Lenovo dock. Both monitors are capable of outputting sound via HDMI. I use bluetooth headphones frequently with my Ubuntu 20.10 system, but I don't leave them on -- I turn them on and off as needed for Zoom calls. When I'm not on a call, however, I prefer to use my laptop's speakers for audio -- not my monitor speakers. Turning the bluetooth headphones on works fine, they connect and pulseaudio correctly identifies the new connection and switches to the headphones as the audio device. However, when I turn the headphones off, pulseaudio always selects an HDMI audio device as the sound device to use, not the internal speaker device that I was using prior to turning on the headphones. I must manually open Sound Settings and select the speaker device every time I turn my headphones off. My expectation is that the device I was using prior to connecting the headphones is remembered and switched back to by default after I disconnect my bluetooth headphones. I've tried using the pavucontrol app to disable the HDMI audio devices, but the hardware device disable settings are not granular enough to let me target the HDMI devices independently of the speaker device. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1921766/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1931799] Re: audio not working on Raspberry Pi 4
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: pulseaudio (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1931799 Title: audio not working on Raspberry Pi 4 Status in pulseaudio package in Ubuntu: Won't Fix Bug description: Pulseaudio stops working. After I use the command "systemctl --user restart pulseaudio.service" ,it's starting to work, but for a while. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: pulseaudio 1:13.99.2-1ubuntu2.3 ProcVersionSignature: Ubuntu 5.8.0-1026.29-raspi 5.8.18 Uname: Linux 5.8.0-1026-raspi aarch64 ApportVersion: 2.20.11-0ubuntu50.7 Architecture: arm64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: daniel 1396 F pulseaudio /dev/snd/pcmC1D0p: daniel 1396 F...m pulseaudio /dev/snd/controlC0: daniel 1396 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 13 14:24:39 2021 ImageMediaBuild: 20201022 SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1931799/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901272] Re: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: bluez (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: linux-raspi (Ubuntu) Status: Incomplete => Won't Fix ** Changed in: pi-bluetooth (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1901272 Title: Can't connect Bluetooth devices after reboot - Ubuntu 20.10 on Raspberry Pi 4 Status in bluez package in Ubuntu: Won't Fix Status in linux-raspi package in Ubuntu: Won't Fix Status in pi-bluetooth package in Ubuntu: Won't Fix Status in bluez source package in Groovy: Won't Fix Status in linux-raspi source package in Groovy: Won't Fix Status in pi-bluetooth source package in Groovy: Won't Fix Bug description: Raspberry pi 4 4Gb ram Ubuntu desktop 20.10 64 bit After reboot no Bluetooth devices connect, scanning Bluetooth devices works, results with same device name (duplicated and with not set up status). Sometimes after several reboots it works. If I use power off and cycle power then it works fine each time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901272/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1904638] Re: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing
Thank you for reporting this bug to Ubuntu. Ubuntu 20.10 (groovy) reached end-of-life on July 22, 2021. See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in. ** Changed in: bluez (Ubuntu) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1904638 Title: Xbox Series X|S controller doesn't work and Xbox icon still blinks after pairing Status in bluez package in Ubuntu: Won't Fix Status in linux package in Ubuntu: Won't Fix Bug description: I have Xbox Series X|S controller and the Xbox icon still blinks after the successful pairing. I'm using Ubuntu 20.10 updated with BlueZ latest release. I'm following this bug closely and I can provide any information you need and do any tests you want. mhalano@glados:~$ lsb_release -rd Description: Ubuntu 20.10 Release: 20.10 mhalano@glados:~$ apt policy bluez bluez: Installed: 5.55-0ubuntu1.1 Candidate: 5.55-0ubuntu1.1 Version table: *** 5.55-0ubuntu1.1 500 500 http://br.archive.ubuntu.com/ubuntu groovy-proposed/main amd64 Packages 100 /var/lib/dpkg/status 5.55-0ubuntu1 500 500 http://br.archive.ubuntu.com/ubuntu groovy/main amd64 Packages --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.2 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-10-23 (25 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. Inspiron 5590 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-30-generic root=UUID=1e3484bb-be3c-4f5d-be22-044d9df06a4a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-30.32-generic 5.8.17 Tags: groovy package-from-proposed Uname: Linux 5.8.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/13/2020 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0XRXN9 dmi.board.vendor: Dell Inc. dmi.board.version: A04 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd08/13/2020:br1.11:svnDellInc.:pnInspiron5590:pvr:rvnDellInc.:rn0XRXN9:rvrA04:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5590 dmi.product.sku: 0957 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:F6:D8:6A:A3:F0 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:5307486 acl:57516 sco:0 events:78636 errors:0 TX bytes:18701 acl:357 sco:0 commands:841 errors:0 mtime.conffile..etc.bluetooth.main.conf: 2020-11-04T10:53:00.842656 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1904638/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1893655] Re: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list
** Tags removed: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1893655 Title: Sony WH-1000XM3 headphones connect but don't appear in the audio devices list Status in bluez package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Bug description: When I switch on my Sony WH-1000XM3 headphones, they reconnect to my laptop at Bluetooth level, but don't appear as an audio device. I have to remove them in the Ubuntu Bluetooth settings, and then re-pair them, every time. This is rather inconvenient. This started happening after upgrading to Ubuntu 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.6.0-1021.21-oem 5.6.19 Uname: Linux 5.6.0-1021-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: Unity:Unity7:ubuntu Date: Mon Aug 31 14:48:53 2020 InstallationDate: Installed on 2020-07-14 (48 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20U9CTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1021-oem root=UUID=42d20f5a-04dd-4073-ac83-e07bd283a1d1 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2WET19W (1.09 ) dmi.board.asset.tag: Not Available dmi.board.name: 20U9CTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2WET19W(1.09):bd07/01/2020:svnLENOVO:pn20U9CTO1WW:pvrThinkPadX1CarbonGen8:rvnLENOVO:rn20U9CTO1WW:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon Gen 8 dmi.product.name: 20U9CTO1WW dmi.product.sku: LENOVO_MT_20U9_BU_Think_FM_ThinkPad X1 Carbon Gen 8 dmi.product.version: ThinkPad X1 Carbon Gen 8 dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: F8:AC:65:6D:04:AB ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1274806 acl:246 sco:0 events:180845 errors:0 TX bytes:152114364 acl:177469 sco:0 commands:3182 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1893655/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689443] Re: bluetoothd crashed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch
Zero crashes after 18.04 so consider it fixed. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689443 Title: bluetoothd crashed with SIGSEGV in g_io_channel_unref from control_connect_cb from connect_cb from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/60e9f362576651ff41d2c58e273c79aa15824ad8 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689443/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690016] Re: bluetoothd crashed with SIGSEGV in browse_request_cancel() from device_remove() from adapter_remove() adapter_cleanup() from main()
Zero crashes after 17.04 so consider it fixed. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1690016 Title: bluetoothd crashed with SIGSEGV in browse_request_cancel() from device_remove() from adapter_remove() adapter_cleanup() from main() Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/f9d11c19ddb6d26b14ea21262ce40ee4357fce3b contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1690016/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690020] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from __GI___libc_malloc() from sdp_service_search_attr_async() connect_watch()
** Tags removed: yakkety ** Tags added: focal -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1690020 Title: bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from __GI___libc_malloc() from sdp_service_search_attr_async() connect_watch() Status in bluez package in Ubuntu: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/e58fe35211e3d090e36521860675c32d63800f8e contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1690020/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1901115] Re: package bluez failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 [Failed to start Bluetooth service.
** Tags removed: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1901115 Title: package bluez failed to install/upgrade: installed bluez package post- installation script subprocess returned error exit status 1 [Failed to start Bluetooth service.] Status in bluez package in Ubuntu: Confirmed Bug description: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 ProblemType: Package DistroRelease: Ubuntu 20.10 Package: bluez 5.55-0ubuntu1 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Oct 23 07:08:46 2020 ErrorMessage: installed bluez package post-installation script subprocess returned error exit status 1 InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:5689 Realtek Semiconductor Corp. Integrated Webcam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Latitude 3180 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=8e6f60a5-d013-4d5d-83ed-df27737e1381 ro quiet splash vt.handoff=7 Python3Details: /usr/bin/python3.8, Python 3.8.6, python3-minimal, 3.8.6-0ubuntu1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.5ubuntu2 apt 2.1.10 SourcePackage: bluez Title: package bluez 5.55-0ubuntu1 failed to install/upgrade: installed bluez package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to groovy on 2020-10-23 (0 days ago) dmi.bios.date: 10/03/2019 dmi.bios.release: 1.10 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05YMV0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd10/03/2019:br1.10:svnDellInc.:pnLatitude3180:pvr:rvnDellInc.:rn05YMV0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 3180 dmi.product.sku: 07B2 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 74:70:FD:58:F6:73 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:2712 acl:0 sco:0 events:305 errors:0 TX bytes:50942 acl:0 sco:0 commands:305 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1901115/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1246981] Re: Bluetooth devices fail to re-connect after sleep.
** Tags removed: groovy -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1246981 Title: Bluetooth devices fail to re-connect after sleep. Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: This exact harware was working faultlessly in 13.04. Since re- installing at 13.10 the mouse consistently failes to reconnect after the device either hybernates or ever goes to screen saver sleep. I have to remove the dive and re-add it each time (which works well). There are other issues with the bluetooth stack as well in that I have not found any way to use bluetooth tethering to my mobile which again worked well and was easy to configure in 13.04 Peter. ProblemType: Bug DistroRelease: Ubuntu 13.10 Package: bluetooth 4.101-0ubuntu8b1 ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3 Uname: Linux 3.11.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.12.5-0ubuntu2.1 Architecture: amd64 Date: Fri Nov 1 16:44:37 2013 InstallationDate: Installed on 2013-10-19 (13 days ago) InstallationMedia: Kubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1) InterestingModules: bnep rfcomm btusb bluetooth MachineType: Dell Inc. Latitude E6530 MarkForUpload: True PackageArchitecture: all ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.11.0-12-generic root=UUID=8283de78-9264-42bf-a8b4-25643fa1475f ro quiet splash SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/13/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A09 dmi.board.name: 07Y85M dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA09:bd12/13/2012:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E6530 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: BR/EDR Bus: USB BD Address: 20:16:D8:9C:38:E5 ACL MTU: 1021:8 SCO MTU: 64:1 UP RUNNING PSCAN ISCAN RX bytes:1817731 acl:117432 sco:0 events:5271 errors:0 TX bytes:37955 acl:131 sco:0 commands:5096 errors:0 syslog: Nov 1 14:50:19 pnunn-Latitude-E6530 bluetoothd[1015]: Discovery session 0x7f6489f7b450 with :1.582 activated Nov 1 14:50:25 pnunn-Latitude-E6530 bluetoothd[1015]: Unknown command complete for opcode 37 Nov 1 14:50:28 pnunn-Latitude-E6530 bluetoothd[1015]: Stopping discovery Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211132] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0/bluetooth/hci0/hci0:11/input29 Nov 1 14:50:36 pnunn-Latitude-E6530 kernel: [60934.211646] hid-generic 0005:045E:0700.000C: input,hidraw3: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on 20:16:d8:9c:38:e5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1246981/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689445] Re: bluetoothd crashed with SIGSEGV in timeout_cb from timeout_callback from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch
Zero crashes after 17.10 so consider it fixed. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689445 Title: bluetoothd crashed with SIGSEGV in timeout_cb from timeout_callback from g_timeout_dispatch from g_main_dispatch from g_main_context_dispatch Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.43-0ubuntu1, the problem page at https://errors.ubuntu.com/problem/b959171c4183443c43f641033bf8efcdee964438 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689445/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1689447] Re: bluetoothd crashed with SIGSEGV in browse_request_cancel from device_remove from btd_adapter_remove_device from remove_device from process_message
Zero crashes after 17.04 so consider it fixed. ** Changed in: bluez (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1689447 Title: bluetoothd crashed with SIGSEGV in browse_request_cancel from device_remove from btd_adapter_remove_device from remove_device from process_message Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/656d6f19e98b8adc45e8c6f3218c6dcea039315a contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1689447/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690013] Re: bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from __libc_calloc() from __GI___open_memstream() from __GI___vsyslog_chk
Zero crashes after 17.10 so consider it fixed. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1690013 Title: bluetoothd crashed with SIGSEGV in malloc_consolidate() from _int_malloc() from __libc_calloc() from __GI___open_memstream() from __GI___vsyslog_chk Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/c3d5226fc780ef2d3f4fcdf956712dafacd0be74 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1690013/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1690015] Re: bluetoothd crashed with SIGSEGV in g_io_channel_unix_get_fd() from bnep_setup_conn_req() from bnep_conn_req_to() from g_timeout_dispatch() from g_main_dispatch()
Zero crashes after 17.10 so consider it fixed. ** Changed in: bluez (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1690015 Title: bluetoothd crashed with SIGSEGV in g_io_channel_unix_get_fd() from bnep_setup_conn_req() from bnep_conn_req_to() from g_timeout_dispatch() from g_main_dispatch() Status in bluez package in Ubuntu: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding bluez. This problem was most recently seen with package version 5.41-0ubuntu3, the problem page at https://errors.ubuntu.com/problem/9fdd7aa0054e4f182328dc241c4f874b3a2b038c contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1690015/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1920248] Re: Anker Soundcore Life Q10 microphone not working
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1920248 Title: Anker Soundcore Life Q10 microphone not working Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a ThinkPad E560 with ubuntu 20.04 and I'm trying to use my Soundcore Life Q10 with it, but the microphone doesn't work. I tried also to follow some answers here, but no one worked for me. I tried to use blueman, but I get Failed to change profile to headset_head_unit. I tried to install oFono, but I cannot compile phonesim due to some problem with dependencies version. I think that PulseAudio does not support HFP out of the box, and I found many other people that has this problem (see for example https://itectec.com/ubuntu/ubuntu-use-bluetooth-headset-with- microphone-hfp-in-ubuntu-18-04/) Is there any way to make my headset working? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1920248/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937988] Re: The image is distrorted while use iGPU rendering and output via AMD GPU
@Shengyao, I meant the -dri1. I think the -dri2 is backported from https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11877#. Let's discuss it on upstream thread. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1937988 Title: The image is distrorted while use iGPU rendering and output via AMD GPU Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: [Steps to reproduce] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgear Cmd> DRI_PRIME=1 glxgears -info [Expected result] The image is not distrorted while running the glxgears [Actual result] The image is distrorted while running the glxgears --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1891165] Re: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed
-- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gsettings-desktop-schemas in Ubuntu. https://bugs.launchpad.net/bugs/1891165 Title: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed Status in gsettings-desktop-schemas package in Ubuntu: New Bug description: I was about to upgrade ubuntu 18 to ubuntu 20, but it says “Your python3 install is corrupted. Please fix the '/usr/bin/python3'”, So i tried to run sudo ln -sf /usr/bin/python2.7 /usr/bin/python as suggested in https://askubuntu.com/questions/1185813/how-to-fix-ubuntu-19-04-cannot-upgrade-to-19-10-error-your-python3-install-is. But i got more errors The following packages have unmet dependencies: gsettings-desktop-schemas : Breaks: mutter (< 3.31.4) but 3.28.4-0ubuntu18.04.2 is to be installed libgirepository-1.0-1 : Breaks: python-gi (< 3.34.0-4~) but 3.26.1-2ubuntu1 is to be installed E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages. sudo ln -sf /usr/bin/python2.7 /usr/bin/python ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: mutter 3.28.4-0ubuntu18.04.2 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.16 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Aug 11 20:38:08 2020 InstallationDate: Installed on 2020-02-08 (184 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: mutter UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gsettings-desktop-schemas/+bug/1891165/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1937988] Re: The image is distrorted while use iGPU rendering and output via AMD GPU
@Jeremy, there is a new version of mesa the PPA in #3: mesa (20.2.6-0ubuntu0.20.04.1dri2) focal; urgency=medium) You means the -dri2 version of mesa still has the issue? if yes, could you pls paste a video or screenshot about that? many thanks. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1937988 Title: The image is distrorted while use iGPU rendering and output via AMD GPU Status in OEM Priority Project: In Progress Status in mesa package in Ubuntu: New Bug description: [Steps to reproduce] 1. Connect a monitor on the AMD GPU. 2. Power on the system and boot into OS. 3. Run below command to launch glxgear Cmd> DRI_PRIME=1 glxgears -info [Expected result] The image is not distrorted while running the glxgears [Actual result] The image is distrorted while running the glxgears --- Here is the upstream bug for tracking this issue. https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/11942?commit_id=505f815e5ead8c9872bbda4c1ff3aeaee7223d64 To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1937988/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
