[Touch-packages] [Bug 1853762] Re: Headphones stop working until pairing again
This may have something to do with another user already being logged in another Gnome Session. -- 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/1853762 Title: Headphones stop working until pairing again Status in bluez package in Ubuntu: New Status in gnome-control-center package in Ubuntu: New Bug description: I'm using Marshall MID ANC headphones with Ubuntu 19.10. Every now and then, I won't be able to use them without re-pairing first (like today - see logs). After re-pairing, everything works again for a while : I can switch off and on the headphones, reboot... Until it breaks again. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Nov 24 19:13:40 2019 InstallationDate: Installed on 2018-07-28 (483 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) 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:0a2b Intel Corp. Bus 001 Device 002: ID 0bda:58d2 Realtek Semiconductor Corp. USB2.0 HD UVC WebCam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX410UAK ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2019-10-18 (37 days ago) dmi.bios.date: 11/08/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX410UAK.308 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX410UAK 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.:bvrUX410UAK.308:bd11/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX410UAK dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. hciconfig: hci0:Type: Primary Bus: USB BD Address: 14:AB:C5:7E:41:26 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:319948 acl:71 sco:0 events:45583 errors:0 TX bytes:37324973 acl:43061 sco:0 commands:2478 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1853762/+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 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering
*** This bug is a duplicate of bug 1847524 *** https://bugs.launchpad.net/bugs/1847524 SOLVED: I found the fix for the gnome-tweak tool. In my case, it turns out the rapid flickering occurs when Animations is disabled in the GENERAL page of GNOME-tweak. Re-enabling Animations stopped the window flicker. There is another minor artifact -- the Close-Minimize-Maximize- Search icons disappear from the application bar when using "<" to return to the main menu. But they do reappear when further clicking on page links in the left menu. The page link menu and the page menus display separately now in independent windows -- and this was the initial behavior I remember before disabling Animations. -- 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/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering Status in gnome-tweaks package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+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 1850103] Re: gnome-tweak-tool window keeps flickering on cursor hovering
*** This bug is a duplicate of bug 1847524 *** https://bugs.launchpad.net/bugs/1847524 Additional information: The above rapid flickering on cursor hover in GNOME-tweak occurs even after: 1) Removing un...@hardpixel.eu (a window decoration multi-function extension) -- no effect 2) Disabling ALL gnome-shell-extensions and restarting -- no effect I don't think that this is a conflict between gnome-shell-extensions. I have restored both of the above, as they aren't causing additional problems. Ubuntu 19.10 5.3.0-26-generic x86_64 GNOME Shell 3.34.1 occurs under both Wayland AND X11 -- 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/1850103 Title: gnome-tweak-tool window keeps flickering on cursor hovering Status in gnome-tweaks package in Ubuntu: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Bug description: the gnome-tweak-tool window keeps flickering abnormally. this might be a bug as i have seen somebody else mention the issue somewhere in the internet. i do have the screencast of the phenomenon i can send it to you for the review of the problem i am facing. i am on ubuntu 19.10 system installed via bootable usb. before i had interrupted network upgrade of the system which was recovered via grub recovery mode. since i thought the flickering was due to all this, i fresh installed the system via bootable usb. still the problem is persistent and its abnormal irrespective of the animation button turned on or off. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-26 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: mutter PackageArchitecture: all ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Tags: wayland-session eoan Uname: Linux 5.3.0-19-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-tweaks/+bug/1850103/+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 1859390] Re: Blurred texts, icons and character typed on login screen after logout or switching user
** Summary changed: - Blurred texts, icons and character typed on login screen after logout + Blurred texts, icons and character typed on login screen after logout or switching user -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1859390 Title: Blurred texts, icons and character typed on login screen after logout or switching user Status in lightdm package in Ubuntu: New Bug description: I login to my account normally. But, when I click on "switch user" from app indicator, the clock in login screen will be completely blurred, impossible even to perceive it is a clock/time, except if I wait one minute so that the last number will update and it will show correctly (only the last number). If I press enter or click-up, I see the login form with the same problem: I can see that there are two users but they are completely indistinguishable and blurred. If I click on it, I can type my password but still blurred, even the chars I type are blurred. The app indicator icons are blurred too, but when I put the cursor over them, instantly they are fixed. PS: I have two enabled monitors and two users, but the second user is not logged in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: lightdm (not installed) ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Jan 13 00:13:45 2020 InstallationDate: Installed on 2019-12-31 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191230) SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1859390/+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 1841157] Re: have /usr/bin/oem-getlogs in apport to collect all in one logs
add_hooks_info works, however, there seems certain limitation and something out of current design scope. For example, check source_xorg.py, there is code flow like: if is_xorg_input_package(pkg): code a else: code b If I want to get log from code a and b, I need to use code like: report.add_hooks_info(None, srcpackage='xserver-xorg-input-evdev') report.add_hooks_info(None, srcpackage='xorg') It does not really work because, the pkg will be "Unknown" because the code get the source pkg from the report object, instead of srcpackage parameter. Even it works, other code the collect log will run twice, and the will make the code run longer. (Given we potentially want to add lots of packages, the duplicate log collected will increase.) -- 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/1841157 Title: have /usr/bin/oem-getlogs in apport to collect all in one logs Status in Apport: New Status in OEM Priority Project: In Progress Status in apport package in Ubuntu: Fix Released Bug description: plan to use command like $ sudo oem-getlogs to collect all logs that oem project could need. To manage notifications about this bug go to: https://bugs.launchpad.net/apport/+bug/1841157/+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 1609700] Re: username is not saved in openconnect connection dialog
** Changed in: fedora Status: Fix Released => Confirmed ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues #328 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/328 ** Bug watch added: gitlab.gnome.org/GNOME/gnome-shell/issues #2105 https://gitlab.gnome.org/GNOME/gnome-shell/issues/2105 -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Confirmed Bug description: Happening again on Eoan 19.10! Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1609700]
I don't think it's helpful to reopen bugs that were closed for years. The original issue was identified and confirmed to be fixed. It's unlikely that the new symptoms have the same cause as the original one. But even so, it would require information to understand the new symptoms better. Let's discuss this on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/328. -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Confirmed Bug description: Happening again on Eoan 19.10! Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1609700]
Now https://gitlab.gnome.org/GNOME/gnome-shell/issues/2105 -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Confirmed Bug description: Happening again on Eoan 19.10! Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1609700]
That build seems not to fix it. I tried to build locally to bisect, but can't seem to get the local build to work at all. May have to leave this to the NM maintainers. -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Confirmed Bug description: Happening again on Eoan 19.10! Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1609700]
Just wanted to mention that this 'bug/issue' is also present in the current Fedora 31 beta with the following packages: NetworkManager-openconnect-gnome-1.2.6-2.fc31.x86_64 NetworkManager-openconnect-1.2.6-2.fc31.x86_64 NetworkManager-1.20.4-1.fc31.x86_64 -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Confirmed Bug description: Happening again on Eoan 19.10! Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1609700]
This is happening to me with F30 with the latest updates as of date. NetworkManager-openconnect-1.2.6-2.fc30.x86_64 -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Confirmed Bug description: Happening again on Eoan 19.10! Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1609700]
This is happening to me with F31 and some Anyconnect VPNs NetworkManager-openconnect-gnome-1.2.6-2.fc31.x86_64 NetworkManager-openconnect-1.2.6-2.fc31.x86_64 NetworkManager-1.20.6-1.fc31.x86_64 My workaround: nmcli con mod VPNNAME vpn.secrets 'form:main:group_list=GROUPNAME','form:main:username=USERNAME','save_passwords=yes' -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Confirmed Bug description: Happening again on Eoan 19.10! Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1609700]
Please test the Fedora 30 build with that commit reverted, at https://koji.fedoraproject.org/koji/taskinfo?taskID=36857342 -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Confirmed Bug description: Happening again on Eoan 19.10! Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1609700]
I wonder if this regression is caused by https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=009f7560867e939 ? -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Confirmed Bug description: Happening again on Eoan 19.10! Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1609700]
According to https://bugs.launchpad.net/bugs/1609700 this bug has reoccurred in f30. -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Confirmed Bug description: Happening again on Eoan 19.10! Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1609700]
*** Bug 1705711 has been marked as a duplicate of this bug. *** -- 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/1609700 Title: username is not saved in openconnect connection dialog Status in network-manager package in Ubuntu: Fix Released Status in network-manager-openconnect package in Ubuntu: Fix Released Status in Fedora: Confirmed Bug description: Happening again on Eoan 19.10! Hi, I clicked on "save passwords" but only the password is filled in automatically when I open the connection dialog. The "Username" field is empty! This happens for a SSLVPN configuration. For another VPN config (don't know which type) everything is ok. openconnect: 7.06-2build2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609700/+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 1671606] Re: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1
*** This bug is a duplicate of bug 1688018 *** https://bugs.launchpad.net/bugs/1688018 This is scary thread for a relatively easy fix, for some reason dnsmasq and OpenVPN don't play well together, it's as simple as commenting out the "dns=dnsmasq" line in /etc/NetworkManager/NetworkManager.conf and then restarting network manager. -- 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/1671606 Title: DNS server from vpn connection is not being used after network-manager upgrade to 1.2.6-0ubuntu0.16.04.1 Status in network-manager package in Ubuntu: Confirmed Status in resolvconf package in Ubuntu: Invalid Bug description: I use my company's cisco vpn via network-manager in Ubuntu 16.04.2 LTS. After recent upgrade of network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 DNS resolution of VPN's server hostnames does not work. Roll back to version 1.2.2-0ubuntu0.16.04.4 solves the problem. Steps for reproducing: 1. upgrade network-manager:amd64 from version 1.2.2-0ubuntu0.16.04.4 to version 1.2.6-0ubuntu0.16.04.1 2. connect to VPN via network-manager applet 3. nslookop servername.internal --> ** server can't find servername.internal: NXDOMAIN 4. disconnect from VPN via network-manager applet 5. roll back network-manager via command: sudo apt-get install network-manager=1.2.2-0ubuntu0.16.04.4 6. restart network-manager via sudo service network-manager restart 7. connect to VPN via network-manager applet 8. nslookop servername.internal --> the server is resolved correctly ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.2.6-0ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44 Uname: Linux 4.4.0-66-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 CurrentDesktop: Unity Date: Thu Mar 9 19:49:55 2017 InstallationDate: Installed on 2015-10-05 (520 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true WimaxEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.2.6connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1671606/+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 1838838] Re: username is not saved in openconnect connection dialog
** Package changed: network-manager-openconnect (Ubuntu) => gnome-shell (Ubuntu) -- 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/1838838 Title: username is not saved in openconnect connection dialog Status in gnome-shell package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: Same issue as https://bugs.launchpad.net/ubuntu/+source/network- manager-openconnect/+bug/1609700 This was marked resolved. The report of its reappearance in Ubuntu 19.04 and 19.10 has not been acknowledged. This was working for me in 18.10, but a fresh install of 19.04 and 19.10 show that it is back. The password is saved when the option to save passwords is selected, but the username must be entered manually upon connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1838838/+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 1806232] Re: Graphical artifacts/glitches on Intel Atom x5 - Screen Tearing
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mesa (Ubuntu) Status: New => Confirmed -- 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/1806232 Title: Graphical artifacts/glitches on Intel Atom x5 - Screen Tearing Status in linux package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: There is screen tearing on the left side of the screen, and it's especially apparent when there's motion on the entire screen. This is happening on Ubuntu 18.10 on an Asus T102HA with an Atom x5 Cherry Trail. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Dec 2 00:59:01 2018 DistUpgraded: Fresh install DistroCodename: cosmic DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [8086:22b0] (rev 36) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1400] InstallationDate: Installed on 2018-12-02 (0 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) MachineType: ASUSTeK COMPUTER INC. T102HA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=6d4342e4-1f2b-42ea-850e-63e34c955cd3 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T102HA.204 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T102HA 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.:bvrT102HA.204:bd07/18/2016:svnASUSTeKCOMPUTERINC.:pnT102HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT102HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T102HA dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1806232/+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 1859483] [NEW] busybox udhcpd does not honour SIGTERM
Public bug reported: busybox 1.27.2, shipped with at least Ubuntu 18.04, has a bug where the udhcpd daemon does not react properly to SIGTERM. That bug if fixed in upstream busybox as of 1.29.0, commit 3293bc146985c56790033409facc0ad64a471084 . That patch should be back- ported to the busybox 1.27.2 - I believe it applies cleanly (it did when we hit this on our Yocto-based embedded systems). ** Affects: busybox (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to busybox in Ubuntu. https://bugs.launchpad.net/bugs/1859483 Title: busybox udhcpd does not honour SIGTERM Status in busybox package in Ubuntu: New Bug description: busybox 1.27.2, shipped with at least Ubuntu 18.04, has a bug where the udhcpd daemon does not react properly to SIGTERM. That bug if fixed in upstream busybox as of 1.29.0, commit 3293bc146985c56790033409facc0ad64a471084 . That patch should be back- ported to the busybox 1.27.2 - I believe it applies cleanly (it did when we hit this on our Yocto-based embedded systems). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/busybox/+bug/1859483/+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 1853935] Re: systemd-mount doesn't support lazyunmount / forceunmount
** Changed in: systemd (Ubuntu) Status: New => Fix Released -- 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/1853935 Title: systemd-mount doesn't support lazyunmount / forceunmount Status in systemd package in Ubuntu: Fix Released Bug description: systemd-mount doesn't support lazyunmount / forceunmount yet it should To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853935/+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 1859468] [NEW] dialog windows spanning across dual monitors poorly
Public bug reported: lsb_release -rd Description:Ubuntu 19.10 Release:19.10 apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status the dialog windows are spanning across my two monitors. 1 open dialog for saving file 2 window opens and spans across the two monitors 3 user buttons open/cancel/save are hidden in the UI. The task bar on the left side is covering/hiding the dialog window buttons desired behavior dialog windows fit INSIDE a single monitor UI please see the attached screenshots ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Mon Jan 13 15:41:37 2020 DistUpgraded: 2019-10-23 09:33:56,809 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family Integrated Graphics Controller [1043:84ca] InstallationDate: Installed on 2015-08-23 (1603 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=UUID=155c3c3c-daa6-414c-ac3d-0f8c492592c0 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to eoan on 2019-10-23 (82 days ago) dmi.bios.date: 07/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2501 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z77-V LX dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2501:bd07/21/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8Z77-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: 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 version.compiz: compiz 1:0.9.14.0+19.10.20190918-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Mon Aug 20 17:24:57 2018 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.4-0ubuntu0.7 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan ubuntu ** Attachment added: "Screenshot (1).png" https://bugs.launchpad.net/bugs/1859468/+attachment/5319789/+files/Screenshot%20%281%29.png -- 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/1859468 Title: dialog windows spanning across dual monitors poorly Status in xorg package in Ubuntu: New Bug description: lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 apt-cache policy xorg xorg: Installed: 1:7.7+19ubuntu12 Candidate: 1:7.7+19ubuntu12 Version table: *** 1:7.7+19ubuntu12 500 500 http://us.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status the dialog windows are spanning across my two monitors. 1 open dialog for saving file 2 window opens and spans across the two monitors 3 user buttons open/cancel/save are hidden in the UI. The task bar on the left side is covering/hiding the dialog window buttons desired behavior dialog windows fit INSIDE a single monitor UI please see the attached screenshots ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature:
[Touch-packages] [Bug 1848522] Re: Backport packages for 18.04.4 HWE stack
Hey Timo! How is this update looking? Is it looking good for the upcoming point release? 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/1848522 Title: Backport packages for 18.04.4 HWE stack Status in libclc package in Ubuntu: Invalid Status in libdrm package in Ubuntu: Invalid Status in llvm-toolchain-9 package in Ubuntu: Invalid Status in mesa package in Ubuntu: Invalid Status in xorg-server-hwe-18.04 package in Ubuntu: Invalid Status in libclc source package in Bionic: Fix Committed Status in libdrm source package in Bionic: Fix Committed Status in llvm-toolchain-9 source package in Bionic: Fix Committed Status in mesa source package in Bionic: Fix Committed Status in xorg-server-hwe-18.04 source package in Bionic: Fix Committed Bug description: [Impact] These are needed for 18.04.4 images. [Test case] Boot a daily image, see that it still has the necessary stack installed and working. Check upgrade from stock bionic. [Regression potential] libdrm: very minimal chance for regressions llvm-9: a new package, no regression potential on it's own libclc: more or less just adds support for new llvm mesa: a new major release, but we'll pull the final stable release of 19.2.x series, so there shouldn't be any regressions left at that point xserver: a new git snapshot (or maybe a point-release) xorg drivers: modest updates, mainly just new ati/amdgpu [Other info] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libclc/+bug/1848522/+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
not proper link wrote(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1856884) -- 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: Fix Released 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] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. 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 1853657] Re: librsvg 2.44.15 FTBFS in focal
** Changed in: librsvg (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1853657 Title: librsvg 2.44.15 FTBFS in focal Status in librsvg package in Ubuntu: Fix Released Bug description: focal currently has rustc 1.38 (1.38.0+dfsg0.2+llvm-0ubuntu1), and librsvg 2.44.15 fails to build from source with this version. It built fine with rustc 1.37 (although there was a unit test failure on ppc64el, which prevented it from leaving focal-proposed, see https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=942022). The upstream commit that addresses this is https://gitlab.gnome.org/GNOME/librsvg/commit/de26c4d8. I backported it and added another patch to update the vendored crates in the source tarball accordingly, and the build succeeds again, but unit tests consistently fail, on all architectures. The upstream commit message says « Although you should rather be using the 2.46 branch of librsvg as 2.44 is EOL », so we should probably update librsvg in debian to 2.46 indeed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1853657/+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
i take off earphones from the socket, my acoustics sounds correct(switch signal from earphones to acoustics) but when i take on my earphones to socket, acoustics sounds , but earphones don't. settings->sound, it chooses proper device(earphones), but it doesn't work proper(not switch signal from acoustics to earphones) it is my old bug description https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1847570 -- 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: Fix Released 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] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. 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 1859404] Re: binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on arm64
also hedgewars, ghc, and others are having the very same SIGILL -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1859404 Title: binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on arm64 Status in binutils package in Ubuntu: New Bug description: Retrying builds on bileto with the release only pocket enabled worked correctly. Still trying to figure out what can have regressed it (Debian doesn't show the issue, but probably it is affected on the same way, just his CPUs can understand the new instructions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1859404/+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 1644996] Re: logrotate config uses syslog group
Having journald in place, rsyslog is no longer strictly necessary, so I would suggest to stop assuming that rsyslog will be in installed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to logrotate in Ubuntu. https://bugs.launchpad.net/bugs/1644996 Title: logrotate config uses syslog group Status in logrotate package in Ubuntu: Fix Released Status in logrotate source package in Bionic: New Status in logrotate source package in Cosmic: New Bug description: The default logrotate config uses the "syslog" group. > # use the syslog group by default, since this is the owning group > # of /var/log/syslog. > su root syslog This is not correct anymore since 16.04, because: 1. "syslog" group doesn't exist on a stock Ubuntu 16.04 system, it only gets installed via rsyslog 2. The owning group is actually "adm". This results in logrotate terminating with the following error during cron.daily run: run-parts -v /etc/cron.daily run-parts: executing /etc/cron.daily/logrotate error: /etc/logrotate.conf:7 unknown group 'syslog' And can be fixed by changing syslog to adm group. This is not present when rsyslog is installed, but only because that package creates the syslog group. This is a common bug in lighter environments, like Docker, where syslog-ng is a common choice instead of rsyslog, like in this issue: https://github.com/phusion/baseimage-docker/issues/338 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logrotate/+bug/1644996/+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 1859404] Re: binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on arm64
golang-1.13 has a really similar issue # ../misc/cgo/testshared shared_test.go:72: executing go install -installsuffix=5577006791947779410 -buildmode=shared runtime sync/atomic failed exit status 2: # /tmp/go-build097387848/b009/libruntime,sync-atomic.so /<>/pkg/tool/linux_arm64/link: running gcc failed: exit status 1 collect2: fatal error: ld terminated with signal 4 [Illegal instruction], core dumped compilation terminated. FAILmisc/cgo/testshared 6.272s FAIL 2020/01/13 08:41:33 Failed: exit status 1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1859404 Title: binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on arm64 Status in binutils package in Ubuntu: New Bug description: Retrying builds on bileto with the release only pocket enabled worked correctly. Still trying to figure out what can have regressed it (Debian doesn't show the issue, but probably it is affected on the same way, just his CPUs can understand the new instructions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1859404/+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 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
** Changed in: linux (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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Fix Released Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)
Excellent news! The bluetooth dock battery status started working properly a couple of weeks ago. I can't be sure which update fixed the bug, but here is the latest system status:- ubuntu 19.10 eoan Desktop 5.3.0-26-generic x86_64 kernel Bluez-* 5.50-0ubuntu4 gnome-bluetooth 3.34.0-1 udev 242-7ubuntu3.2 libudev-1.0.0"amd64 1.233-1 The bug can finally be closed as fixed. Thanks very much everyone who contributed. Brian -- 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/1769075 Title: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later) Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d" reports always 0% as battery percentage of the bluetooth Logitech K810 keyboard. Which is a bit annoying since I get a KDE warning on the battery. Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery native-path: hid-34:88:5d:5e:0c:2f-battery model:Logitech K810 power supply: no updated: Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago) has history: yes has statistics: yes keyboard present: yes rechargeable:yes state: unknown warning-level: none percentage: 0% icon-name: 'battery-missing-symbolic' My guess is that the issue is in the bluetooth rather in the upowerd since the reporting in the /sys/devices shows battery level of 0 --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: bnv1714 F pulseaudio /dev/snd/pcmC0D0p: bnv1714 F...m pulseaudio /dev/snd/controlC0: bnv1714 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf InstallationDate: Installed on 2017-11-02 (185 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) IwConfig: lono wireless extensions. enp0s25 no wireless extensions. MachineType: Dell Inc. Precision Tower 5810 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago) UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/08/2017 dmi.bios.vendor: Dell Inc. dmi.bios.version: A19 dmi.board.name: 0K240Y dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 7 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr: dmi.product.name: Precision Tower 5810 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1769075/+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 autopkgtest issue got resolved on a retry -- 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: Fix Released 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] The behaviour is changed back to what it was before 19.10, some users might find it inconvenient and prefer the auto switch but the feedback we got shows it's unreliable and an annoying for the majority of our users so we will got back to default to safest behaviour. 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 1859404] [NEW] binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on arm64
Public bug reported: Retrying builds on bileto with the release only pocket enabled worked correctly. Still trying to figure out what can have regressed it (Debian doesn't show the issue, but probably it is affected on the same way, just his CPUs can understand the new instructions? ** Affects: binutils (Ubuntu) Importance: Undecided Assignee: Matthias Klose (doko) Status: New ** Tags: block-proposed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1859404 Title: binutils regressed llvm-toolchain-9 and llvm-toolchain-7 bootstrap on arm64 Status in binutils package in Ubuntu: New Bug description: Retrying builds on bileto with the release only pocket enabled worked correctly. Still trying to figure out what can have regressed it (Debian doesn't show the issue, but probably it is affected on the same way, just his CPUs can understand the new instructions? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1859404/+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
