[Touch-packages] [Bug 1857552] Re: [81NX, Realtek ALC285, Speaker, Internal] No sound at all
Sorry, not sure did the headphones work on the ubuntu-side, now they do not work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1857552 Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: In dual boot machine (lenove S740 laptop) sound is fine on windows side. Headphones work on linux side, but there is no sound at all from speakers on the ubuntu 19.10 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: hu-mka 1574 F pulseaudio hu-mka 5552 F alsamixer CurrentDesktop: ubuntu:GNOME Date: Wed Dec 25 20:14:17 2019 InstallationDate: Installed on 2019-12-22 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1126 F pulseaudio hu-mka 1574 F pulseaudio hu-mka 5552 F alsamixer Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [81NX, Realtek ALC285, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/15/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BKCN20WW(V1.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S740-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBKCN20WW(V1.02):bd07/15/2019:svnLENOVO:pn81NX:pvrLenovoYogaS740-15IRH:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct31:cvrLenovoYogaS740-15IRH: dmi.product.family: Yoga S740-15IRH dmi.product.name: 81NX dmi.product.sku: LENOVO_MT_81NX_BU_idea_FM_Yoga S740-15IRH dmi.product.version: Lenovo Yoga S740-15IRH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857552/+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 1510098] Re: /etc/network/interfaces ipv6 static gateway not set
** Changed in: ifupdown (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1510098 Title: /etc/network/interfaces ipv6 static gateway not set Status in ifupdown package in Ubuntu: Confirmed Status in ifupdown package in Debian: Confirmed Bug description: After installing 15.10 ipv6 gateway not set on start up. In 15.04 it worked fine andrej@nikel:~$ cat /etc/network/interfaces auto lo enp4s0 iface lo inet loopback iface enp4s0 inet manual iface enp4s0 inet6 static address :200:8221::--- netmask 64 gateway 198:20- andrej@nikel:~$ ip -6 route ---0:8221::/64 dev enp4s0 proto kernel metric 256 mtu 1500 pref medium fe80::/64 dev enp4s0 proto kernel metric 256 mtu 1500 pref medium fe80::/64 dev lxcbr0 proto kernel metric 256 pref medium fe80::/64 dev docker0 proto kernel metric 256 pref medium 3: enp4s0: mtu 9000 qdisc pfifo_fast state UP group default qlen 1000 link/ether --7:98 brd ff:ff:ff:ff:ff:ff inet 10.0.4.1/8 brd 10.255.255.255 scope global enp4s0 valid_lft forever preferred_lft forever inet6 200:8221::--/64 scope global valid_lft forever preferred_lft forever inet6 -15:17ff:fe9e:b798/64 scope global mngtmpaddr dynamic valid_lft 83024sec preferred_lft 11024sec inet6 fe80::215:17ff:fe9e:b798/64 scope link valid_lft forever preferred_lft forever andrej@nikel:~$ cat /etc/sysctl.conf net.ipv4.conf.default.rp_filter= 1 net.ipv4.conf.all.rp_filter= 1 net.ipv4.tcp_syncookies= 1 net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 net.ipv6.conf.enp4s0.use_tempaddr = 2 andrej@nikel:/proc/sys/net/ipv6/conf/enp4s0$ for i in *; do echo -n "$i: " ; cat $i ; done accept_dad: 1 accept_ra: 0 accept_ra_defrtr: 1 accept_ra_from_local: 0 accept_ra_mtu: 1 accept_ra_pinfo: 1 accept_ra_rt_info_max_plen: 0 accept_ra_rtr_pref: 1 accept_redirects: 1 accept_source_route: 0 autoconf: 0 dad_transmits: 1 disable_ipv6: 0 force_mld_version: 0 force_tllao: 0 forwarding: 0 hop_limit: 64 max_addresses: 16 max_desync_factor: 600 mc_forwarding: 0 mldv1_unsolicited_report_interval: 1 mldv2_unsolicited_report_interval: 1000 mtu: 1500 ndisc_notify: 0 proxy_ndp: 0 regen_max_retry: 3 router_probe_interval: 60 router_solicitation_delay: 1 router_solicitation_interval: 4 router_solicitations: 3 cat: stable_secret: Permission denied stable_secret: suppress_frag_ndisc: 1 temp_prefered_lft: 86400 temp_valid_lft: 604800 use_tempaddr: 2 Maybe related: https://bugs.launchpad.net/ubuntu/+source/miredo/+bug/1510047 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ifupdown 0.7.54ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 26 14:41:55 2015 JournalErrors: No journal files were found. -- No entries -- SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1510098/+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 1510098] Re: /etc/network/interfaces ipv6 static gateway not set
This is still valid on all Ubuntu versions when ifupdown is used, and an RA exists on the network - there is a race in assigning the default gateway. See the associated Debian bug for additional details. ** Bug watch added: Debian Bug tracker #805445 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805445 ** Also affects: ifupdown (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805445 Importance: Unknown Status: Unknown ** Changed in: ifupdown (Ubuntu) Status: Invalid => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ifupdown in Ubuntu. https://bugs.launchpad.net/bugs/1510098 Title: /etc/network/interfaces ipv6 static gateway not set Status in ifupdown package in Ubuntu: Confirmed Status in ifupdown package in Debian: Unknown Bug description: After installing 15.10 ipv6 gateway not set on start up. In 15.04 it worked fine andrej@nikel:~$ cat /etc/network/interfaces auto lo enp4s0 iface lo inet loopback iface enp4s0 inet manual iface enp4s0 inet6 static address :200:8221::--- netmask 64 gateway 198:20- andrej@nikel:~$ ip -6 route ---0:8221::/64 dev enp4s0 proto kernel metric 256 mtu 1500 pref medium fe80::/64 dev enp4s0 proto kernel metric 256 mtu 1500 pref medium fe80::/64 dev lxcbr0 proto kernel metric 256 pref medium fe80::/64 dev docker0 proto kernel metric 256 pref medium 3: enp4s0: mtu 9000 qdisc pfifo_fast state UP group default qlen 1000 link/ether --7:98 brd ff:ff:ff:ff:ff:ff inet 10.0.4.1/8 brd 10.255.255.255 scope global enp4s0 valid_lft forever preferred_lft forever inet6 200:8221::--/64 scope global valid_lft forever preferred_lft forever inet6 -15:17ff:fe9e:b798/64 scope global mngtmpaddr dynamic valid_lft 83024sec preferred_lft 11024sec inet6 fe80::215:17ff:fe9e:b798/64 scope link valid_lft forever preferred_lft forever andrej@nikel:~$ cat /etc/sysctl.conf net.ipv4.conf.default.rp_filter= 1 net.ipv4.conf.all.rp_filter= 1 net.ipv4.tcp_syncookies= 1 net.ipv6.conf.all.use_tempaddr = 2 net.ipv6.conf.default.use_tempaddr = 2 net.ipv6.conf.enp4s0.use_tempaddr = 2 andrej@nikel:/proc/sys/net/ipv6/conf/enp4s0$ for i in *; do echo -n "$i: " ; cat $i ; done accept_dad: 1 accept_ra: 0 accept_ra_defrtr: 1 accept_ra_from_local: 0 accept_ra_mtu: 1 accept_ra_pinfo: 1 accept_ra_rt_info_max_plen: 0 accept_ra_rtr_pref: 1 accept_redirects: 1 accept_source_route: 0 autoconf: 0 dad_transmits: 1 disable_ipv6: 0 force_mld_version: 0 force_tllao: 0 forwarding: 0 hop_limit: 64 max_addresses: 16 max_desync_factor: 600 mc_forwarding: 0 mldv1_unsolicited_report_interval: 1 mldv2_unsolicited_report_interval: 1000 mtu: 1500 ndisc_notify: 0 proxy_ndp: 0 regen_max_retry: 3 router_probe_interval: 60 router_solicitation_delay: 1 router_solicitation_interval: 4 router_solicitations: 3 cat: stable_secret: Permission denied stable_secret: suppress_frag_ndisc: 1 temp_prefered_lft: 86400 temp_valid_lft: 604800 use_tempaddr: 2 Maybe related: https://bugs.launchpad.net/ubuntu/+source/miredo/+bug/1510047 ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ifupdown 0.7.54ubuntu1 ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3 Uname: Linux 4.2.0-16-generic x86_64 ApportVersion: 2.19.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 26 14:41:55 2015 JournalErrors: No journal files were found. -- No entries -- SourcePackage: ifupdown UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1510098/+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 1857652] [NEW] Loud background hiss when using headphones (XPS 13 9350)
Public bug reported: Whenever I play audio, I head a loud hiss from my headphones. The hiss stops after a few seconds if I pause the audio, but starts again when I start it. The hiss goes away if I open 'alsamixer' and increase 'Headphone Mic Boost', but I'm not sure if this is expected behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: qasim 850 F pulseaudio /dev/snd/pcmC0D0p: qasim 850 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 26 16:33:21 2019 InstallationDate: Installed on 2019-12-21 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd01/22/2019:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.product.sku: 0704 dmi.sys.vendor: Dell Inc. ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1857652 Title: Loud background hiss when using headphones (XPS 13 9350) Status in alsa-driver package in Ubuntu: New Bug description: Whenever I play audio, I head a loud hiss from my headphones. The hiss stops after a few seconds if I pause the audio, but starts again when I start it. The hiss goes away if I open 'alsamixer' and increase 'Headphone Mic Boost', but I'm not sure if this is expected behaviour. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: qasim 850 F pulseaudio /dev/snd/pcmC0D0p: qasim 850 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 26 16:33:21 2019 InstallationDate: Installed on 2019-12-21 (5 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/fish SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Front Symptom_Type: High background noise, or volume is too low Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] Background noise or low volume UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/22/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.1 dmi.board.name: 07TYC2 dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.1:bd01/22/2019:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn07TYC2:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: NULL dmi.product.name: XPS 13 9350 dmi.product.sku: 0704 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1857652/+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 1766503] Re: ibus-* randomly use high CPU
same issue in 19.10 / 5.3.0-24-generic , opening system monitor does fix it, wierd. -- 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/1766503 Title: ibus-* randomly use high CPU Status in The Ubuntu Power Consumption Project: Confirmed Status in ibus package in Ubuntu: Confirmed Bug description: ibus-* randomly use high CPU in Ubuntu 18.04 In fact, I think it's now using more CPU overall than the shell itself is to redraw a 4K screen: PID USER PR NIVIRTRESSHR S %CPU %MEM TIME+ COMMAND 3308 dan 20 0 4009804 192676 84804 R 45.7 2.4 1:13.65 gnome-shell 3352 dan 20 0 384364 26796 20552 S 13.9 0.3 0:22.81 ibus-x11 3372 dan 20 0 217944 10620 7764 S 10.9 0.1 0:16.20 ibus-engin+ 3350 dan 20 0 293828 10384 7516 R 10.6 0.1 0:16.54 ibus-dconf 3346 dan 20 0 374572 11944 8268 S 10.3 0.1 0:15.93 ibus-daemon ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu4 ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17 Uname: Linux 4.15.0-19-generic x86_64 ApportVersion: 2.20.9-0ubuntu6 Architecture: amd64 Date: Tue Apr 24 15:29:07 2018 InstallationDate: Installed on 2017-12-12 (133 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled
** Changed in: systemd Status: Unknown => New -- 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/1857639 Title: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled Status in systemd: New Status in systemd package in Ubuntu: New Bug description: I'm running Ubuntu 19.10 I'm on latest version available from repositories, systemd 242 I'm expecting upstream DNS server capabilities being detected correctly and DNSSEC to keep working. Alternatively I'd expect a method of disabling capability checks instead of DNSSEC. Currently instead resolved misdetect features suddenly, stops resolving all together (fails closed, which is somewhat good). Capability reset is a very temporary fix. A suggested fix could be (ordered based on how nice of a solution it is): a. The capability detection is fixed (https://github.com/systemd/systemd/issues/9384) b. Force-disabling capability detection exists (this is what I also requested here: https://github.com/systemd/systemd/issues/14435) c. Patch Ubuntu version not to allow such a foot gun, update documentation (this is theoretically what Ubuntu could do meanwhile) d. Remove DNSSEC from resolved To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1857639/+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 1848476] Re: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1848476 Title: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all Status in alsa-driver package in Ubuntu: Confirmed Bug description: Ubuntu 18.04.3 LTS The sound works until I plug the headphones and then it never works again, even without them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 Uname: Linux 5.3.6-050306-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniela2692 F pulseaudio /dev/snd/pcmC0D0c: daniela2692 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 17 11:03:37 2019 InstallationDate: Installed on 2019-09-18 (28 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gdm1426 F pulseaudio daniela2692 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [ZenBook UX534FT_UX534FT, Realtek ALC294, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/10/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX534FT.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX534FT dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX534FT.204:bd06/10/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX534FT_UX534FT:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX534FT:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX534FT_UX534FT dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1848476/+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 1857639] Re: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled
** Description changed: I'm running Ubuntu 19.10 I'm on latest version available from repositories, systemd 242 I'm expecting upstream DNS server capabilities being detected correctly and DNSSEC to keep working. Alternatively I'd expect a method of disabling capability checks instead of DNSSEC. Currently instead resolved misdetect features suddenly, stops resolving all together (fails closed, which is somewhat good). Capability reset is a very temporary fix. + + A suggested fix could be (ordered based on how nice of a solution it + is): + + a. The capability detection is fixed + (https://github.com/systemd/systemd/issues/9384) + + b. Force-disabling capability detection exists + (https://github.com/systemd/systemd/issues/14435) + + c. Patch Ubuntu version not to allow such a foot gun, update + documentation + + d. Remove DNSSEC from resolved ** Description changed: I'm running Ubuntu 19.10 I'm on latest version available from repositories, systemd 242 I'm expecting upstream DNS server capabilities being detected correctly and DNSSEC to keep working. Alternatively I'd expect a method of disabling capability checks instead of DNSSEC. Currently instead resolved misdetect features suddenly, stops resolving all together (fails closed, which is somewhat good). Capability reset is a very temporary fix. A suggested fix could be (ordered based on how nice of a solution it is): a. The capability detection is fixed (https://github.com/systemd/systemd/issues/9384) - b. Force-disabling capability detection exists - (https://github.com/systemd/systemd/issues/14435) + b. Force-disabling capability detection exists (this is what I also + requested here: https://github.com/systemd/systemd/issues/14435) c. Patch Ubuntu version not to allow such a foot gun, update - documentation + documentation (this is theoretically what Ubuntu could do meanwhile) d. Remove DNSSEC from resolved -- 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/1857639 Title: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I'm running Ubuntu 19.10 I'm on latest version available from repositories, systemd 242 I'm expecting upstream DNS server capabilities being detected correctly and DNSSEC to keep working. Alternatively I'd expect a method of disabling capability checks instead of DNSSEC. Currently instead resolved misdetect features suddenly, stops resolving all together (fails closed, which is somewhat good). Capability reset is a very temporary fix. A suggested fix could be (ordered based on how nice of a solution it is): a. The capability detection is fixed (https://github.com/systemd/systemd/issues/9384) b. Force-disabling capability detection exists (this is what I also requested here: https://github.com/systemd/systemd/issues/14435) c. Patch Ubuntu version not to allow such a foot gun, update documentation (this is theoretically what Ubuntu could do meanwhile) d. Remove DNSSEC from resolved To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1857639/+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 1857639] [NEW] DNS server capability detection is broken and has critical consequences when DNSSEC is enabled
Public bug reported: I'm running Ubuntu 19.10 I'm on latest version available from repositories, systemd 242 I'm expecting upstream DNS server capabilities being detected correctly and DNSSEC to keep working. Alternatively I'd expect a method of disabling capability checks instead of DNSSEC. Currently instead resolved misdetect features suddenly, stops resolving all together (fails closed, which is somewhat good). Capability reset is a very temporary fix. ** Affects: systemd Importance: Unknown Status: Unknown ** Affects: systemd (Ubuntu) Importance: Undecided Status: New ** Bug watch added: github.com/systemd/systemd/issues #14435 https://github.com/systemd/systemd/issues/14435 ** Also affects: systemd via https://github.com/systemd/systemd/issues/14435 Importance: Unknown Status: Unknown -- 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/1857639 Title: DNS server capability detection is broken and has critical consequences when DNSSEC is enabled Status in systemd: Unknown Status in systemd package in Ubuntu: New Bug description: I'm running Ubuntu 19.10 I'm on latest version available from repositories, systemd 242 I'm expecting upstream DNS server capabilities being detected correctly and DNSSEC to keep working. Alternatively I'd expect a method of disabling capability checks instead of DNSSEC. Currently instead resolved misdetect features suddenly, stops resolving all together (fails closed, which is somewhat good). Capability reset is a very temporary fix. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1857639/+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 1727470] Re: [RFE] Automatically update the Ubuntu version strings in python-apt
The example from #7 looks good to me! :-) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1727470 Title: [RFE] Automatically update the Ubuntu version strings in python-apt Status in Ubuntu Translations: Triaged Status in python-apt package in Ubuntu: Triaged Bug description: Every time there is a new Ubuntu release, some strings need to be manually translated although the only thing that is changing is the Ubuntu version and code name. Please, consider updating these strings automatically based on a translated template. It would help many translators. These strings are: Ubuntu xx.yy 'Code Name' Cdrom with Ubuntu xx.yy 'Code Name' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/1727470/+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 1857631] [NEW] disconnect error upon search engine
Public bug reported: random occurance sometimes 1st login, or 2nd login ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Dec 26 12:05:36 2019 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1240 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (366 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Tue Dec 25 08:33:58 2018 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputLogitech Logitech USB Speaker KEYBOARD, id 8 inputLogitech USB-PS/2 Optical Mouse MOUSE, id 9 inputDell Dell USB Keyboard KEYBOARD, id 10 xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.18.4-0ubuntu0.8 xserver.video_driver: radeon ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic 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/1857631 Title: disconnect error upon search engine Status in xorg package in Ubuntu: New Bug description: random occurance sometimes 1st login, or 2nd login ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None Date: Thu Dec 26 12:05:36 2019 DistUpgraded: 2018-12-25 11:16:26,692 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] RV610 [Radeon HD 2400 PRO] [1002:94c3] (prog-if 00 [VGA controller]) Subsystem: Dell Radeon HD 2400 Pro [1028:0302] InstallationDate: Installed on 2016-08-03 (1240 days ago) InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) MachineType: Dell Inc. Dell XPS420 ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=UUID=e737e1ac-8869-44b7-a03f-477223f8 ro drm.debug=0xe plymouth:debug SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2018-12-25 (366 days ago) dmi.bios.date: 03/27/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A04 dmi.board.name: 0TP406 dmi.board.vendor: Dell Inc. dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA04:bd03/27/2008:svnDellInc.:pnDellXPS420:pvr:rvnDellInc.:rn0TP406:rvr:cvnDellInc.:ct7:cvr: dmi.product.name: Dell XPS420 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
[Touch-packages] [Bug 1823076] Re: System wakes up immediately after suspend if Bluetooth is still enabled
I am having this issue also. Turning off bluetooth with bluez (Bluetooth Manager) applet icon and manually stopping bluetooth service the suspend works. Otherwise I have seen suspends but usually just wakes up in a few seconds. Lenovo P53 with Ubuntu 19.10 and kernel 5.3.0-24-generic -- 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/1823076 Title: System wakes up immediately after suspend if Bluetooth is still enabled Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: After replacing my USB mouse with a BT mouse, I noticed my machine would no longer suspend without immediately waking up. i.e. I suspend and see the light go into the slow fade in and out for one cycle and then goes solid and the display wakes up again. If I disable BT (via blueman applet) suspend works fine. I've fixed this by shutting down the BT service before suspend, and starting it back up on wake, as indicated here: https://askubuntu.com/questions/797590/ubuntu-wakes-up-immediately- after-suspend Perhaps this script should be included in blueZ as suspend issues seem very hard to debug and the immediate wake after suspend could be caused many any number of things. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluez 5.48-0ubuntu3.1 [modified: lib/systemd/system/bluetooth.service] ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18 Uname: Linux 4.15.0-46-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: XFCE Date: Wed Apr 3 13:16:14 2019 InstallationDate: Installed on 2019-02-09 (53 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Intel(R) Client Systems NUC8i3BEH ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic root=UUID=9c982b36-8142-4719-810a-e06f81cab223 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/15/2018 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0051.2018.1015.1513 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-304 dmi.chassis.type: 3 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0051.2018.1015.1513:bd10/15/2018:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-303:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-304:cvnIntelCorporation:ct3:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.version: J72753-303 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:BB:60:50:92:5D ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1912660 acl:106009 sco:0 events:337 errors:0 TX bytes:12331 acl:74 sco:0 commands:204 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1823076/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
This fix will fix this issue also? https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1334329 -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] Low. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
The fix is only for the HDMI output? The same issue is with displayport :( -- 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/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Eoan: Fix Committed Status in pulseaudio source package in Focal: Fix Released Bug description: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] Low. The fix proposed just reverts to the same code used in PulseAudio 12 and earlier. It has also been released and verified on focal already. [Workaround] Comment out: load-module module-switch-on-port-available load-module module-switch-on-connect from /etc/pulse/default.pa To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1847570/+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
