[Touch-packages] [Bug 1592721] Re: Don't write search domains to resolv.conf in the case of split DNS
Yes, please bring to 16.04 -- 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/1592721 Title: Don't write search domains to resolv.conf in the case of split DNS Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Xenial: Fix Released Bug description: [Impact] All VPN users meaning to use split-tunnelling in a situation where leaking DNS data to the internet about what might be behind their VPN is undesirable. [Test case] 1) connect to VPN 2) Use dig to request a name that should be on the VPN 3) Verify (kill -USR1 the dnsmasq binary from NM) that the request has only gone through the VPN nameservers (only its request number should have increased by one) 4) Use dig to request a name off-VPN, such as google.com. 5) Verify (kill -USR1 again) that the request has caused the non-VPN nameserver request number to increase, and that the VPN number has not increased. It is easier to verify this when there is as little traffic as possible on the system, to avoid spurious DNS requests which would make it harder to validate the counters. [Regression potential] This change modifies the way in which DNS nameservers and search domains are passed to dnsmasq, as such, if a VPN is configured in a non-standard way and intended to be used to resolve all network requests (which is typically not the case for split-tunnelling) or if the public network is intended to always resolve all requests while the VPN still provides search domains, one might observe incorrect behavior. Possible failure cases would include failure to resolve names correctly (resulting in NXDOMAIN or REFUSED from dnsmasq) or resolving to the incorrect values (if the wrong nameserver is used). --- Currently, NM will write all search domains to both any DNS-handling plugins running, and also to resolv.conf / resolvconf; in all cases. The issue is that doing so means that in the split-DNS case on VPNs, you might get a negative response from all nameservers, then a new request by glibc with the search tacked on, to nameservers again, which might cause DNS requests for "private" resources (say, on the VPN) to be sent to external, untrusted resolvers, or for DNS queries not meant for VPN nameservers to be sent through the VPN anyway. This is fixable in the case where we have a caching plugin running (such as dnsmasq). dnsmasq will already know about the search domains and use that to limit queries to the right nameservers when a VPN is running. Writing search domains to resolv.conf is unnecessary in this case. We should still write search domains if no caching gets done, as we then need to expect glibc to send requests as it otherwise would. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1592721/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right
Me too on Ubuntu 18.04.2 LTS. Dell XPS-13 laptop shipped with Ubuntu. I can't click "Yes, it affects me" on this page -- I keep getting a timeout error. Any idea how to fix the timeout error and add my name? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to console-setup in Ubuntu. https://bugs.launchpad.net/bugs/520546 Title: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right Status in console-setup package in Ubuntu: In Progress Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: Confirmed Status in console-setup source package in Bionic: New Status in linux source package in Bionic: New Status in xorg-server source package in Bionic: New Status in console-setup source package in Cosmic: New Status in linux source package in Cosmic: New Status in xorg-server source package in Cosmic: New Status in console-setup source package in Disco: In Progress Status in linux source package in Disco: Confirmed Status in xorg-server source package in Disco: Confirmed Status in console-setup source package in Eoan: New Status in linux source package in Eoan: New Status in xorg-server source package in Eoan: New Bug description: WORKAROUND: sudo kbd_mode -s ORIGINAL DESCRIPTION: I'm running Ubuntu Lucid development branch. Pressing alt-f2 switches the screen to the second virtual terminal. Alt-f3 does the same to the third and so on. I expected alt-f2 to open the run dialog. I'm pretty sure that my keyboard is not malfunctioning as I can use all my applications normally. (Pressing O and Ctrl-O do not have the same effect.) I'm not sure which package I should file this bug against. I'll happily do an apport-collect once I know. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1754693] Re: Xwayland crashed with SIGABRT in st_renderbuffer_delete()
I just ran updates on my 18.04 machine today also and can confirm Slack is working under Wayland Here is my Slack Snap Version: commands: - slack snap-id: JUJH91Ved74jd4ZgJCpzMBtYbPOzTlsD tracking: stable refreshed: 2018-03-30T18:45:51-04:00 installed: 3.1.1 (6) 98MB classic If someone can tell me how to print out the affected Wayland component version I can post that also. -- 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/1754693 Title: Xwayland crashed with SIGABRT in st_renderbuffer_delete() Status in mesa package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/01a80d2110a46f6b6d857ce814079646e695f4ca --- Steps to reproduce: Install 'slack' snap: sudo snap install slack --classic Run slack: slack Instacrash. ProblemType: Crash DistroRelease: Ubuntu 18.04 Package: xwayland 2:1.19.6-1ubuntu2 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CompizPlugins: [core,composite,opengl,decor,mousepoll,grid,vpswitch,compiztoolbox,imgpng,gnomecompat,regex,move,place,resize,snap,unitymtgrabhandles,wall,animation,session,expo,workarounds,fade,ezoom,scale,unityshell] CompositorRunning: None CurrentDesktop: GNOME Date: Fri Mar 9 10:31:06 2018 DistUpgraded: 2018-03-06 13:58:47,853 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu EcryptfsInUse: Yes ExecutablePath: /usr/bin/Xwayland ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1043:8534] MachineType: ASUS All Series ProcCmdline: /usr/bin/Xwayland :0 -rootless -terminate -accessx -core -listen 4 -listen 5 -displayfd 6 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic root=UUID=cd444f9d-672e-4d7b-aea8-657fff0ea1f4 ro quiet splash crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M nomdmonddf nomdmonisw crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M vt.handoff=1 Signal: 6 SourcePackage: xorg-server StacktraceTop: ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so ?? () from /usr/lib/x86_64-linux-gnu/dri/swrast_dri.so Title: Xwayland crashed with SIGABRT UpgradeStatus: Upgraded to bionic on 2018-03-06 (2 days ago) UserGroups: adm admin audio cdrom chroot-admin dialout dip egbuild fax floppy fuse libvirt libvirtd lpadmin lxd plugdev sambashare sudo tape video wireshark dmi.bios.date: 10/27/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2702 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-PRO 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.:bvr2702:bd10/27/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnZ97-PRO:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: ASUS MB dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc4-1ubuntu3 version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc4-1ubuntu3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-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: Mon Oct 16 18:18:18 2017 xser
[Touch-packages] [Bug 1725333] Re: do-release-upgrade broke WSL
Where is this fixed? do-release-upgrade still fails with the same error in WSL and breaks it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bash in Ubuntu. https://bugs.launchpad.net/bugs/1725333 Title: do-release-upgrade broke WSL Status in Gnu Bash: New Status in bash package in Ubuntu: New Bug description: I had Ubuntu 17.04 installed in WSL and decided to upgrade it to 17.10, so I had run do-release-upgrade, as I did before to upgrade to 17.04. Everything was fine before script started upgrading packages. It's started from bash updating, and somehow there is a problem revealed that locale files is missing, and locale-gen can't be run (because of bug in WSL). I've tried to install language-pack-en as was suggested, but problem haven't resolved, any attempt to update leads to this error. ProblemType: Package DistroRelease: Ubuntu 17.10 Package: bash 4.4-2ubuntu1.1 ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35 Uname: Linux 4.4.0-43-Microsoft x86_64 ApportVersion: 2.20.4-0ubuntu4.5 Architecture: amd64 Date: Fri Oct 20 18:03:30 2017 Dmesg: DpkgTerminalLog: Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped DuplicateSignature: package:bash:4.4-2ubuntu1.1 Preparing to unpack .../bash_4.4-5ubuntu1_amd64.deb ... preinst: ../sysdeps/unix/sysv/linux/spawni.c:368: __spawnix: Assertion `ec >= 0' failed. dpkg: error processing archive /var/cache/apt/archives/bash_4.4-5ubuntu1_amd64.deb (--unpack): subprocess new pre-installation script was killed by signal (Aborted), core dumped ErrorMessage: subprocess new pre-installation script was killed by signal (Aborted), core dumped RelatedPackageVersions: dpkg 1.18.10ubuntu2 apt 1.4.6~17.04.1 SourcePackage: bash Title: package bash 4.4-2ubuntu1.1 failed to install/upgrade: subprocess new pre-installation script was killed by signal (Aborted), core dumped UpgradeStatus: Upgraded to artful on 2017-10-20 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnubash/+bug/1725333/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
Dell XPS 7560 17.04 Gnome Headphone jack won't work at all until I suspend and wake, then I have no issues. Even the main speaker sometimes has issues now, but with alsactl restore and no headphones in, I can get them to 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in alsa-driver package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+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 1583801] Re: No sound via headphones (headset) when Ubuntu boots with them plugged in
Sorry, that's on a 9560, not 7650. ^ -- 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/1583801 Title: No sound via headphones (headset) when Ubuntu boots with them plugged in Status in alsa-driver package in Ubuntu: Confirmed Bug description: The bug is twofold, first when computer boots if the headset (headphones with built-in mic, one audio jack) is plugged in, then there is no sound (via headphones or otherwise). If you plug headphones out and back in, then it usually works as expected. The second scenario is the same, except that plugging out and back in again doesn't help. In that case, I just restart the laptop, then plug them back in again and it works. In all cases, microphone works. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8 Uname: Linux 4.4.0-22-generic x86_64 NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: crunch 3248 F pulseaudio CurrentDesktop: Unity Date: Thu May 19 22:13:20 2016 InstallationDate: Installed on 2016-05-07 (12 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) 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: crunch 3248 F pulseaudio Symptom_Jack: Black Headphone Out, Left Symptom_Type: No sound at all Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/07/2016 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.02.00 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: XPS 15 9550 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1583801/+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 1869107] [NEW] Error when installing scanner deb on 20.04
Public bug reported: Trying to install .deb for Brother ADS-2200 scanner. Worked previously in 18.04, 18.10, 19.04 and 19.10. If I double click on the .deb, Gnome Software attempts to install and fails with the following error: Failed to install file: not supported If I use apt to install the file manually I get the following error: sudo apt install ./brscanads2200ads2700w-0.1.15-1.amd64.deb Reading package lists... Error! E: Problem parsing Provides line of brscanads2200ads2700w:amd64=0.1.15-1 E: Error occurred while processing brscanads2200ads2700w (NewVersion2) E: Problem with MergeList /home/caleb/Downloads/brscanads2200ads2700w-0.1.15-1.amd64.deb E: The package lists or status file could not be parsed or opened. I installed using dpkg without any errors. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869107 Title: Error when installing scanner deb on 20.04 Status in apt package in Ubuntu: New Bug description: Trying to install .deb for Brother ADS-2200 scanner. Worked previously in 18.04, 18.10, 19.04 and 19.10. If I double click on the .deb, Gnome Software attempts to install and fails with the following error: Failed to install file: not supported If I use apt to install the file manually I get the following error: sudo apt install ./brscanads2200ads2700w-0.1.15-1.amd64.deb Reading package lists... Error! E: Problem parsing Provides line of brscanads2200ads2700w:amd64=0.1.15-1 E: Error occurred while processing brscanads2200ads2700w (NewVersion2) E: Problem with MergeList /home/caleb/Downloads/brscanads2200ads2700w-0.1.15-1.amd64.deb E: The package lists or status file could not be parsed or opened. I installed using dpkg without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869107/+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 1869107] Re: Error when installing scanner deb on 20.04
Okay, well I was wrong. dpkg or gdebi will successfully install the .deb, but the scanner doesn't actually work. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869107 Title: Error when installing scanner deb on 20.04 Status in apt package in Ubuntu: New Bug description: Trying to install .deb for Brother ADS-2200 scanner. Worked previously in 18.04, 18.10, 19.04 and 19.10. If I double click on the .deb, Gnome Software attempts to install and fails with the following error: Failed to install file: not supported If I use apt to install the file manually I get the following error: sudo apt install ./brscanads2200ads2700w-0.1.15-1.amd64.deb Reading package lists... Error! E: Problem parsing Provides line of brscanads2200ads2700w:amd64=0.1.15-1 E: Error occurred while processing brscanads2200ads2700w (NewVersion2) E: Problem with MergeList /home/caleb/Downloads/brscanads2200ads2700w-0.1.15-1.amd64.deb E: The package lists or status file could not be parsed or opened. I installed using dpkg without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869107/+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 1869789] [NEW] Crossover fails to install due to missing lib32nss-mdns
Public bug reported: Crossover depends on lib32nss-mdns which does not appear to be available in 20.04. ** Affects: apt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869789 Title: Crossover fails to install due to missing lib32nss-mdns Status in apt package in Ubuntu: New Bug description: Crossover depends on lib32nss-mdns which does not appear to be available in 20.04. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869789/+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 1869107] Re: Error when installing scanner deb on 20.04
Issue is resolved now and scanner works if you would like to close. Thanks! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1869107 Title: Error when installing scanner deb on 20.04 Status in apt package in Ubuntu: Fix Committed Bug description: Trying to install .deb for Brother ADS-2200 scanner. Worked previously in 18.04, 18.10, 19.04 and 19.10. If I double click on the .deb, Gnome Software attempts to install and fails with the following error: Failed to install file: not supported If I use apt to install the file manually I get the following error: sudo apt install ./brscanads2200ads2700w-0.1.15-1.amd64.deb Reading package lists... Error! E: Problem parsing Provides line of brscanads2200ads2700w:amd64=0.1.15-1 E: Error occurred while processing brscanads2200ads2700w (NewVersion2) E: Problem with MergeList /home/caleb/Downloads/brscanads2200ads2700w-0.1.15-1.amd64.deb E: The package lists or status file could not be parsed or opened. I installed using dpkg without any errors. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1869107/+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 1873104] [NEW] Defaults to USB audio after every reboot
Public bug reported: I manually set my audio output to the Line Out. Every reboot this settings is lost and the system defaults back to the USB output. I have several other distros to test - Ubuntu and its flavors are the only ones that have this problem. Something changed in 19.04 or 19.10 that broke this, and it continues to be an issue in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: caleb 1778 F pulseaudio /dev/snd/controlC3: caleb 1778 F pulseaudio /dev/snd/controlC1: caleb 1778 F pulseaudio /dev/snd/controlC0: caleb 1778 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 15 19:32:36 2020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.name: 8437 dmi.board.vendor: HP dmi.board.version: 1.3 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.30:bd09/06/2018:svnHP:pnOMENbyHPDesktopPC880-p1xx:pvr:rvnHP:rn8437:rvr1.3:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Omen dmi.product.name: OMEN by HP Desktop PC 880-p1xx dmi.product.sku: 2TB61AV dmi.sys.vendor: HP ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1873104 Title: Defaults to USB audio after every reboot Status in alsa-driver package in Ubuntu: New Bug description: I manually set my audio output to the Line Out. Every reboot this settings is lost and the system defaults back to the USB output. I have several other distros to test - Ubuntu and its flavors are the only ones that have this problem. Something changed in 19.04 or 19.10 that broke this, and it continues to be an issue in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: caleb 1778 F pulseaudio /dev/snd/controlC3: caleb 1778 F pulseaudio /dev/snd/controlC1: caleb 1778 F pulseaudio /dev/snd/controlC0: caleb 1778 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 15 19:32:36 2020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.name: 8437 dmi.board.vendor: HP dmi.board.version: 1.3 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.30:bd09/06/2018:svnHP:pnOMENbyHPDesktopPC880-p1xx:pvr:rvnHP:rn8437:rvr1.3:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Omen dmi.product.name: OMEN by HP Desktop PC 880-p1xx dmi.product.sku: 2TB61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1873104/+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 1873104] Re: Defaults to USB audio after every reboot
Yes, I know I can modify a file and turn off switch on connect. Working around it isn't a problem, I still think it is a bug. It needs to either differentiate between detection on boot and detection during a hotplug, or it needs different behavior depending on if you are on a laptop or desktop. I can see how this option is great for laptop users. It is extremely frustrating, though, on a desktop where USB devices like headsets tend to stay plugged in all the time. -- 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/1873104 Title: Defaults to USB audio after every reboot Status in alsa-driver package in Ubuntu: New Bug description: I manually set my audio output to the Line Out. Every reboot this settings is lost and the system defaults back to the USB output. I have several other distros to test - Ubuntu and its flavors are the only ones that have this problem. Something changed in 19.04 or 19.10 that broke this, and it continues to be an issue in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: caleb 1778 F pulseaudio /dev/snd/controlC3: caleb 1778 F pulseaudio /dev/snd/controlC1: caleb 1778 F pulseaudio /dev/snd/controlC0: caleb 1778 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 15 19:32:36 2020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.name: 8437 dmi.board.vendor: HP dmi.board.version: 1.3 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.30:bd09/06/2018:svnHP:pnOMENbyHPDesktopPC880-p1xx:pvr:rvnHP:rn8437:rvr1.3:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Omen dmi.product.name: OMEN by HP Desktop PC 880-p1xx dmi.product.sku: 2TB61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1873104/+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 1873104] Re: Defaults to USB audio after every reboot
I agree. I don't see this as an upstream issue because I have tried it on other distros - they worked as expected. USB hotplugging updates the audio device. However, a reboot simply restores whatever was last in use. For some reason, only on Ubuntu, it treats a reboot as plugging a new USB device. And this occurs on every flavor I tested - Ubuntu, Mate, Kubuntu and Xubuntu. In Kubuntu it can be slightly mitigated because you can set the default from the tray. -- 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/1873104 Title: Defaults to USB audio after every reboot Status in alsa-driver package in Ubuntu: Confirmed Bug description: I manually set my audio output to the Line Out. Every reboot this settings is lost and the system defaults back to the USB output. I have several other distros to test - Ubuntu and its flavors are the only ones that have this problem. Something changed in 19.04 or 19.10 that broke this, and it continues to be an issue in 20.04. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: caleb 1778 F pulseaudio /dev/snd/controlC3: caleb 1778 F pulseaudio /dev/snd/controlC1: caleb 1778 F pulseaudio /dev/snd/controlC0: caleb 1778 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Apr 15 19:32:36 2020 PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Title: USB sound card not detected UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/06/2018 dmi.bios.vendor: AMI dmi.bios.version: F.30 dmi.board.name: 8437 dmi.board.vendor: HP dmi.board.version: 1.3 dmi.chassis.type: 3 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnAMI:bvrF.30:bd09/06/2018:svnHP:pnOMENbyHPDesktopPC880-p1xx:pvr:rvnHP:rn8437:rvr1.3:cvnHP:ct3:cvr: dmi.product.family: 103C_53311M HP Omen dmi.product.name: OMEN by HP Desktop PC 880-p1xx dmi.product.sku: 2TB61AV dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1873104/+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 1414899] [NEW] whoopsie cannot be installed on upgrade to vivid (hard dependency on libwhoopsie0 0.2.39)
Public bug reported: The whoopsie and libwhoopsie0 packages' (0.2.44) versions match, but dpkg complains that whoopsie currently hard-depends on libwhoopsie0 0.2.39 (the version used in utopic). This breaks in-place upgrades. ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: mismatch version vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1414899 Title: whoopsie cannot be installed on upgrade to vivid (hard dependency on libwhoopsie0 0.2.39) Status in whoopsie package in Ubuntu: New Bug description: The whoopsie and libwhoopsie0 packages' (0.2.44) versions match, but dpkg complains that whoopsie currently hard-depends on libwhoopsie0 0.2.39 (the version used in utopic). This breaks in-place upgrades. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1414899/+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 1311124] Re: webbrowser-app does not recognize alternate keyboard layouts
This has nothing to do with the wpa package. wpa provides support for connecting to WPA- and WPA2-encrypted wireless networks. I have marked the webbrowser-app package instead. ** Also affects: webbrowser-app Importance: Undecided Status: New ** Changed in: webbrowser-app Status: New => Confirmed ** Changed in: wpa (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to wpa in Ubuntu. https://bugs.launchpad.net/bugs/1311124 Title: webbrowser-app does not recognize alternate keyboard layouts Status in Web Browser App: Confirmed Status in “wpa” package in Ubuntu: Invalid Bug description: Attempting to use the Dvorak keyboard layout in the webbrowser-app (and, by extension, all webapps) fails, with input reverting to QWERTY layout. $ lsb_release -rd Description: Ubuntu 14.04 LTS Release: 14.04 $ apt-cache policy webbrowser-app webbrowser-app: Installed: 0.23+14.04.20140416-0ubuntu1 Candidate: 0.23+14.04.20140416-0ubuntu1 Version table: *** 0.23+14.04.20140416-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty-updates/main amd64 Packages 100 /var/lib/dpkg/status 0.23+14.04.20140414-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ trusty/main amd64 Packages Expected behavior: webbrowser-app recognizes the layout chosen through the layout switcher Actual behavior: webbrowser-app recognizes QWERTY (the layout chosen during install), ignoring whatever is chosen through the layout switcher. To manage notifications about this bug go to: https://bugs.launchpad.net/webbrowser-app/+bug/1311124/+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 1342586] Re: [utopic] [proposed] cgmanager breaks lightdm login
Whoever marked this bug 'invalid' apparently did not test it on UEFI hardware. The same bug exists for systemd-shim, making graphical login impossible. ** Changed in: systemd-shim (Ubuntu) Status: Invalid => Confirmed -- 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/1342586 Title: [utopic] [proposed] cgmanager breaks lightdm login Status in “systemd” package in Ubuntu: Fix Released Status in “systemd-shim” package in Ubuntu: Confirmed Bug description: The latest 'proposed' systemd-shim 6.3-ubuntu1 package install cgmanager. As a result X is first killed and then its impossible to login again. This happen on Utopic i386 with unity-greeter, systemd-boot and a gtx 750 nvidia card. The bad experience: - trying to purge cgmanager also wants to remove a bunch of packages that will deeply break the system - X can be started but the login always fail - there is no way to open a terminal (ctrl+t) or (ctrl+alt+t) from X - even cant get a command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1342586/+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
