[Touch-packages] [Bug 1856460] Re: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone doesn't work
*** This bug is a duplicate of bug 1850439 *** https://bugs.launchpad.net/bugs/1850439 This seems to be an issue with all the new ASUS zenbooks (or Asus laptops in general). I am going around marking duplicates so we can get more heat ** This bug has been marked a duplicate of bug 1850439 No sound on ASUS UX534FT -- 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/1856460 Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] Microphone doesn't work Status in alsa-driver package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a dual boot system with windows 10. In windows I don't find any problem but on Ubuntu the microphone doesn't seem to work or be recognized. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: pulseaudio 1:13.0-1ubuntu1 Uname: Linux 5.3.16-050316-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Dec 15 15:04:59 2019 InstallationDate: Installed on 2019-11-26 (19 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful Symptom_Card: Audio interno - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2260 F pulseaudio Symptom_Jack: Mic, Internal Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH failed Symptom_Type: No sound at all Title: [ZenBook UX334FL_UX334FL, Realtek ALC294, Mic, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL 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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nesar 2298 F pulseaudio /dev/snd/pcmC0D0p: nesar 2298 F...m pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-11-26 (20 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash Tags: eoan Uname: Linux 5.3.16-050316-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/16/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX334FL.302 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX334FL 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.:bvrUX334FL.302:bd10/16/2019:svnASUSTeKCOMPUTERINC.:pnZenBookUX334FL_UX334FL:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX334FL:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ZenBook dmi.product.name: ZenBook UX334FL_UX334FL dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1856460/+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 1858971] Re: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures
mysql-8.0 confused about it CURRENT_TEST: main.events_bugs mysqltest: At line 1036: Query 'CREATE EVENT e1 ON SCHEDULE AT '2020-01-01 00:00:00' DO SET @a = 1' succeeded, should have failed with error '1290' -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1858971 Title: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures Status in openssh package in Ubuntu: New Status in openssl package in Ubuntu: New Status in python2.7 package in Ubuntu: New Status in ruby-openssl package in Ubuntu: New Status in ruby2.5 package in Ubuntu: New Bug description: SECLEVEL=2 by default is causing ftbfs / autopkgtest failure openssl switched to SECLEVEL=2 by default Causes: SSL_CTX_use_certificate: ca md too weak in ruby2.5 ruby-openssl openssl uses tls1.2-min: test_ssl failing in python2.7 ERROR: test_protocol_sslv23 (test.test_ssl.ThreadedTests) Connecting to an SSLv23 server with various client options ERROR: test_protocol_tlsv1_1 (test.test_ssl.ThreadedTests) Connecting to a TLSv1.1 server with various client options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1858971/+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 1858971] Re: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures
Something odd is happening with openssh tests =/ 22:35:08.766049714 O: trace: certified host keys: host rsa-sha2-512 revoked cert 22:35:08.767645798 O: FAIL: ssh cert connect cert not yet valid succeeded unexpectedly 22:35:08.769149660 O: FAIL: ssh cert connect cert not yet valid succeeded unexpectedly ** Also affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1858971 Title: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures Status in openssh package in Ubuntu: New Status in openssl package in Ubuntu: New Status in python2.7 package in Ubuntu: New Status in ruby-openssl package in Ubuntu: New Status in ruby2.5 package in Ubuntu: New Bug description: SECLEVEL=2 by default is causing ftbfs / autopkgtest failure openssl switched to SECLEVEL=2 by default Causes: SSL_CTX_use_certificate: ca md too weak in ruby2.5 ruby-openssl openssl uses tls1.2-min: test_ssl failing in python2.7 ERROR: test_protocol_sslv23 (test.test_ssl.ThreadedTests) Connecting to an SSLv23 server with various client options ERROR: test_protocol_tlsv1_1 (test.test_ssl.ThreadedTests) Connecting to a TLSv1.1 server with various client options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1858971/+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 1858971] Re: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures
nodejs small keys Error: error:140AB18F:SSL routines:SSL_CTX_use_certificate:ee key too small -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1858971 Title: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures Status in openssh package in Ubuntu: New Status in openssl package in Ubuntu: New Status in python2.7 package in Ubuntu: New Status in ruby-openssl package in Ubuntu: New Status in ruby2.5 package in Ubuntu: New Bug description: SECLEVEL=2 by default is causing ftbfs / autopkgtest failure openssl switched to SECLEVEL=2 by default Causes: SSL_CTX_use_certificate: ca md too weak in ruby2.5 ruby-openssl openssl uses tls1.2-min: test_ssl failing in python2.7 ERROR: test_protocol_sslv23 (test.test_ssl.ThreadedTests) Connecting to an SSLv23 server with various client options ERROR: test_protocol_tlsv1_1 (test.test_ssl.ThreadedTests) Connecting to a TLSv1.1 server with various client options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1858971/+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 1858971] [NEW] SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures
Public bug reported: SECLEVEL=2 by default is causing ftbfs / autopkgtest failure openssl switched to SECLEVEL=2 by default Causes: SSL_CTX_use_certificate: ca md too weak in ruby2.5 ruby-openssl openssl uses tls1.2-min: test_ssl failing in python2.7 ERROR: test_protocol_sslv23 (test.test_ssl.ThreadedTests) Connecting to an SSLv23 server with various client options ERROR: test_protocol_tlsv1_1 (test.test_ssl.ThreadedTests) Connecting to a TLSv1.1 server with various client options. ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Affects: openssl (Ubuntu) Importance: Undecided Status: New ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Affects: ruby-openssl (Ubuntu) Importance: Undecided Status: New ** Affects: ruby2.5 (Ubuntu) Importance: Undecided Status: New ** Tags: tls1.2-min update-excuse ** Also affects: ruby2.5 (Ubuntu) Importance: Undecided Status: New ** Tags added: update-excuse ** Also affects: ruby-openssl (Ubuntu) Importance: Undecided Status: New ** Description changed: SECLEVEL=2 by default is causing ftbfs / autopkgtest failure openssl switched to SECLEVEL=2 by default Causes: SSL_CTX_use_certificate: ca md too weak in ruby2.5 ruby-openssl + + openssl uses tls1.2-min: + + test_ssl failing in python2.7 + ERROR: test_protocol_sslv23 (test.test_ssl.ThreadedTests) + Connecting to an SSLv23 server with various client options + ERROR: test_protocol_tlsv1_1 (test.test_ssl.ThreadedTests) + Connecting to a TLSv1.1 server with various client options. ** Tags added: tls1.2-min ** Also affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - SECLEVEL=2 by default is causing ftbfs / autopkgtest failure + SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1858971 Title: SECLEVEL=2 & tls1.2-min by default are causing ftbfs / autopkgtest failures Status in openssh package in Ubuntu: New Status in openssl package in Ubuntu: New Status in python2.7 package in Ubuntu: New Status in ruby-openssl package in Ubuntu: New Status in ruby2.5 package in Ubuntu: New Bug description: SECLEVEL=2 by default is causing ftbfs / autopkgtest failure openssl switched to SECLEVEL=2 by default Causes: SSL_CTX_use_certificate: ca md too weak in ruby2.5 ruby-openssl openssl uses tls1.2-min: test_ssl failing in python2.7 ERROR: test_protocol_sslv23 (test.test_ssl.ThreadedTests) Connecting to an SSLv23 server with various client options ERROR: test_protocol_tlsv1_1 (test.test_ssl.ThreadedTests) Connecting to a TLSv1.1 server with various client options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1858971/+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 1856501] Re: xgettext cannot deal with jsx self-closing tags
It's important because a lot of web-developers are using React[1] (*.jsx), but can't using gettext for localization. Testcase: xgettext --from-code=utf-8 --language=JavaScript filename.jsx Fix already done, see first message. [1] A JavaScript library for building user interfaces - https://reactjs.org/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1856501 Title: xgettext cannot deal with jsx self-closing tags Status in gettext package in Ubuntu: In Progress Bug description: Bug in xgettext: https://savannah.gnu.org/bugs/?56848 Fixed through https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=8f8b910322f5905045a8731df7aca5e601c9b082 Can you apply this patch? It really needed. ProblemType: Bug Architecture: x86_64 Date: Mon Dec 16 09:30:05 +07 2019 DistroRelease: Ubuntu 18.04 Package: gettext 0.19.8.1-6ubuntu0.3 PackageArchitecture: amd64 SourcePackage: gettext Uname: Linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1856501/+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
That armhf test failure doesn't seem to look related to this change. Can someone just retry a rebuild? -- 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 1847570] Autopkgtest regression report (pulseaudio/1:13.0-1ubuntu1.1)
All autopkgtests for the newly accepted pulseaudio (1:13.0-1ubuntu1.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: sphinxbase/0.8+5prealpha+1-7 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#pulseaudio [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- 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 1813112] Re: avahi-discover failed to display selected service details with UnicodeDecodeError
I have seen this in about 20 Lubuntu/Ubuntu 16.04 installations dist upgraded to 18.04 Also it works in some others.. I did NOT see this prior to avahi-daemon version 0.70 No idea what breaks it, however avahi-browse seams to work. Can it be something related with the support for "binary records" starting in 0.7x In a fresh 18.04 installation MDNS in general seams to be broken/disabled -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1813112 Title: avahi-discover failed to display selected service details with UnicodeDecodeError Status in avahi package in Ubuntu: Confirmed Bug description: ## Bug reproduce instruction (As this is a Unicode decode issue it might not be reproducible in all network environments) 1. Launch avahi-discover 2. Select certain service ## Expected behavior The service details properly rendered on the bottom pane ## Current behavior The service details remain "No service currently selected" with the following error traceback: ``` Found service 'Buo-ren-TS453A' of type '_qdiscover._tcp' in domain 'local' on 2.0. Service data for service 'Buo-ren-TS453A' of type '_qdiscover._tcp' in domain 'local' on 2.0: Host Buo-ren-TS453A.local (192.168.1.10), port 8080, TXT data: ['accessType=http,accessPort=8080,model=TS-X53II,displayModel=TS-453A,fwVer=4.3.4,fwBuildNum=20180830,serialNum=Q169I13903,myCloudNASName=LinBuoRenNAS,myCloudNASDomain=myqnapcloud.com,webAdmPort=0,webAdmSslPort=0,webPort=0,webSslPort=0'] Traceback (most recent call last): File "/usr/lib/python2.7/dist-packages/dbus/connection.py", line 604, in msg_reply_handler reply_handler(*message.get_args_list(**get_args_opts)) File "/usr/bin/avahi-discover", line 113, in service_resolved self.update_label(interface, protocol, name, stype, domain, host, aprotocol, address, port, avahi.txt_array_to_string_array(txt)) File "/usr/bin/avahi-discover", line 246, in update_label infos = infos % (stype, name, domain, self.siocgifname(interface), self.protoname(protocol), host, address, port, txts.strip()) UnicodeDecodeError: 'ascii' codec can't decode byte 0xe6 in position 6: ordinal not in range(128) ``` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1813112/+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
I moved it to NetworkManager because that's where the regression is. There's not a lot we can do about it in NetworkManager-openconnect. -- 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 network-manager package in Ubuntu: Confirmed Status in network-manager-openconnect 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/network-manager/+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 1838838] Re: username is not saved in openconnect connection dialog
** Also affects: network-manager-openconnect (Ubuntu) Importance: Undecided Status: New -- 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 network-manager package in Ubuntu: Confirmed Status in network-manager-openconnect 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/network-manager/+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 1838838] Re: username is not saved in openconnect connection dialog
** Tags added: eoan -- 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 network-manager package in Ubuntu: Confirmed Status in network-manager-openconnect 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/network-manager/+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 1838838] Re: username is not saved in openconnect connection dialog
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: network-manager-openconnect (Ubuntu) Status: New => Confirmed -- 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 network-manager package in Ubuntu: Confirmed Status in network-manager-openconnect 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/network-manager/+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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
This seems to have also fixed another issue where my sound would switch to HDMI sink from headphones when changing screen resolutions in XFCE: https://bugs.launchpad.net/ubuntu/+source/xfce4-settings/+bug/1858250 https://bugzilla.xfce.org/show_bug.cgi?id=16335 ** Bug watch added: Xfce Bugzilla #16335 https://bugzilla.xfce.org/show_bug.cgi?id=16335 -- 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 1858883] [NEW] date utility format unexpectedly changed after upgrade from bionic to focal
Public bug reported: After upgrading my Bionic system to Focal, I noticed a significant change in the output of the `date` utility. This could potentially cause regressions for those who are relying on a consistent date format when using `date` in shell scripts. EXPECTED BEHAVIOR = I expected to see the same date format that can be seen on Ubuntu releases (at least) from Trusty through Bionic: $ date -u Wed Jan 8 21:00:14 UTC 2020 ACTUAL BEHAVIOR === On Focal (and Eoan) the following date format is seen by default: $ date -u Wed 08 Jan 2020 09:00:14 PM UTC Note the differences in zero-padding, whitespace, placement of the year, and the extraneous "PM" (I had expected to see a 24-hour time). FURTHER DETAILS === This machine was originally on Bionic and has been upgraded to development releases between Bionic and Focal. $ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= ** Affects: coreutils (Ubuntu) Importance: Undecided Status: New ** Attachment added: "ubuntu-bug.txt" https://bugs.launchpad.net/bugs/1858883/+attachment/5318665/+files/ubuntu-bug.txt ** Description changed: After upgrading my Bionic system to Focal, I noticed a significant change in the output of the `date` utility. This could potentially cause regressions for those who are relying on a consistent date format when using `date` in shell scripts. - EXPECTED BEHAVIOR = - The date format seen below can be seen on Ubuntu releases from Trusty - through Bionic: + I expected to see the same date format that can be seen on Ubuntu + releases (at least) from Trusty through Bionic: $ date -u Wed Jan 8 21:00:14 UTC 2020 - ACTUAL BEHAVIOR === On Focal (and Eoan) the following date format is seen by default: $ date -u Wed 08 Jan 2020 09:00:14 PM UTC Note the differences in zero-padding, whitespace, placement of the year, and the extraneous "PM" (I had expected to see a 24-hour time). - FURTHER DETAILS === This machine was originally on Bionic and has been upgraded to development releases between Bionic and Focal. $ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to coreutils in Ubuntu. https://bugs.launchpad.net/bugs/1858883 Title: date utility format unexpectedly changed after upgrade from bionic to focal Status in coreutils package in Ubuntu: New Bug description: After upgrading my Bionic system to Focal, I noticed a significant change in the output of the `date` utility. This could potentially cause regressions for those who are relying on a consistent date format when using `date` in shell scripts. EXPECTED BEHAVIOR = I expected to see the same date format that can be seen on Ubuntu releases (at least) from Trusty through Bionic: $ date -u Wed Jan 8 21:00:14 UTC 2020 ACTUAL BEHAVIOR === On Focal (and Eoan) the following date format is seen by default: $ date -u Wed 08 Jan 2020 09:00:14 PM UTC Note the differences in zero-padding, whitespace, placement of the year, and the extraneous "PM" (I had expected to see a 24-hour time). FURTHER DETAILS === This machine was originally on Bionic and has been upgraded to development releases between Bionic and Focal. $ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC="en_US.UTF-8" LC_TIME="en_US.UTF-8" LC_COLLATE="en_US.UTF-8" LC_MONETARY="en_US.UTF-8" LC_MESSAGES="en_US.UTF-8" LC_PAPER="en_US.UTF-8" LC_NAME="en_US.UTF-8" LC_ADDRESS="en_US.UTF-8" LC_TELEPHONE="en_US.UTF-8" LC_MEASUREMENT="en_US.UTF-8" LC_IDENTIFICATION="en_US.UTF-8" LC_ALL= To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1858883/+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
After enabling proposed, did sudo apt install pulseaudio pulseaudio-module-bluetooth pulseaudio-utils to update only present packages related to pulseaudio Can confirm the issue is now fixed for me. -- 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 1851806] Re: 'module' object has no attribute 'O_PATH'
** Branch linked: lp:~tdaitx/ubuntu/focal/apport/lp-1851806-fix
--
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/1851806
Title:
'module' object has no attribute 'O_PATH'
Status in apport package in Ubuntu:
Confirmed
Bug description:
I encountered the following exception in python-apport while
encountering an exception `bup` which uses `python-apport`. I'm sure
that the exception lies in the responsibility of `python-apport` (the
`AttributeError` stacktrace is relevant):
```
Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in
update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
os.rename(self.tmpname, self.filename)
OSError: [Errno 13] Permission denied
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/bup/bup/helpers.py", line 916, in newhook
return oldhook(exctype, value, traceback)
File "/usr/lib/python2.7/dist-packages/apport_python_hook.py", line 109, in
apport_excepthook
pr.add_proc_info(extraenv=['PYTHONPATH', 'PYTHONHOME'])
File "/usr/lib/python2.7/dist-packages/apport/report.py", line 544, in
add_proc_info
proc_pid_fd = os.open('/proc/%s' % pid, os.O_RDONLY | os.O_PATH |
os.O_DIRECTORY)
AttributeError: 'module' object has no attribute 'O_PATH'
Original exception was:
Traceback (most recent call last):
File "/usr/lib/bup/cmd/bup-index", line 269, in
update_index(rp, excluded_paths, exclude_rxs, xdev_exceptions=xexcept)
File "/usr/lib/bup/cmd/bup-index", line 191, in update_index
mi.close()
File "/usr/lib/bup/bup/index.py", line 528, in close
os.rename(self.tmpname, self.filename)
OSError: [Errno 13] Permission denied
```
ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: python-apport 2.20.11-0ubuntu8.2
ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
Uname: Linux 5.3.0-19-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog: Error: [Errno 13] Keine Berechtigung: '/var/log/apport.log'
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov 8 10:43:02 2019
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2019-10-25 (13 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1851806/+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 also upgraded everything from the proposed repo and tested. This issue is fixed for me as well. I power cycled each monitor monitor (I have two.) in succession, and the output device selected remained the motherboard line out throughout. Line out was also selected at boot, where previously at each boot, it would reset to one of my monitors. I was previously using the workaround but reenabled switch-on-connect and switch-on-port-available (removed the hashtags commenting them out) prior to installing the new pulse audio packages. -- 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 1838838] Re: username is not saved in openconnect connection dialog
** Package changed: network-manager-openconnect (Ubuntu) => network- manager (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 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/network-manager/+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 1838838] [NEW] username is not saved in openconnect connection dialog
You have been subscribed to a public bug: 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. ** Affects: network-manager (Ubuntu) Importance: Undecided Status: Confirmed -- username is not saved in openconnect connection dialog https://bugs.launchpad.net/bugs/1838838 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. -- 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
Successfully tested on eoan. I enabled the proposed repository, upgraded everything (so including pulseaudio 13.0-1ubuntu1.1) then rebooted. The audio device is no longer switched to HDMI when the screen wake up after standby or when login-out and in. (note that the workaround from the description was not applied, so no possible confusion here) So this is all good from my point of view. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- 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 1856428] Re: Disable TLS1.0, TLS 1.1
** Changed in: openssl (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gnutls28 (Ubuntu) Status: New => In Progress ** Changed in: nss (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1856428 Title: Disable TLS1.0, TLS 1.1 Status in gnutls28 package in Ubuntu: In Progress Status in nss package in Ubuntu: Triaged Status in openssl package in Ubuntu: Fix Committed Bug description: Disable TLS 1.0, TLS1.1, DTLS1.0 As part of focal commitment, we shall disable obsolete protocols by default. Users can override this behaviour with a config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1856428/+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
If you are affected by this bug, please comment on the bug above. It has been open since August 2019. -- 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: Fix Released 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] Re: username is not saved in openconnect connection dialog
Sebastien Bacher - please see https://bugs.launchpad.net/ubuntu/+source /network-manager-openconnect/+bug/1838838 -- 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: Fix Released 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 1856428] Re: Disable TLS1.0, TLS 1.1
** Changed in: openssl (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1856428 Title: Disable TLS1.0, TLS 1.1 Status in gnutls28 package in Ubuntu: New Status in nss package in Ubuntu: New Status in openssl package in Ubuntu: In Progress Bug description: Disable TLS 1.0, TLS1.1, DTLS1.0 As part of focal commitment, we shall disable obsolete protocols by default. Users can override this behaviour with a config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1856428/+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
How do I update only pulseaudio? I get: $ sudo apt upgrade pulseaudio/eoan-proposed Reading package lists... Done Building dependency tree Reading state information... Done Selected version '1:13.0-1ubuntu1.1' (Ubuntu:19.10/eoan-proposed [amd64]) for 'pulseaudio' Selected version '1:13.0-1ubuntu1.1' (Ubuntu:19.10/eoan-proposed [amd64]) for 'libpulse0' because of 'pulseaudio' Calculating upgrade... Done Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: pulseaudio : Depends: libpulse0 (= 1:13.0-1ubuntu1.1) but 1:13.0-1ubuntu1 is to be installed pulseaudio-module-bluetooth : Depends: pulseaudio (= 1:13.0-1ubuntu1) E: Broken packages -- 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 1856428] Re: Disable TLS1.0, TLS 1.1
** Summary changed: - Disable TLS1.0, TLS 1.1, DTLS1.0 + Disable TLS1.0, TLS 1.1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to nss in Ubuntu. https://bugs.launchpad.net/bugs/1856428 Title: Disable TLS1.0, TLS 1.1 Status in gnutls28 package in Ubuntu: New Status in nss package in Ubuntu: New Status in openssl package in Ubuntu: New Bug description: Disable TLS 1.0, TLS1.1, DTLS1.0 As part of focal commitment, we shall disable obsolete protocols by default. Users can override this behaviour with a config file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnutls28/+bug/1856428/+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 1858092] Re: Network Manager not saving OpenVPN password
> Network Manager works with the ppa provided. thanks for verifying, uploaded to eoan. -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1858092] Re: Network Manager not saving OpenVPN password
@ddstreet Network Manager works with the ppa provided. Thanks -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1807138] Re: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected
Having the same issue on the same machine and would be extremely happy if there is any help or advances in this regard. -- 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/1807138 Title: [ALC256 - Razer Blade 15 2018] Headphones not automatically detected Status in alsa-driver package in Ubuntu: Confirmed Bug description: Running the command alsamixer allows me to manually increase the sound levels for the headset, and sound plays properly through them. This requires me to disable the auto-mute feature. I haven't rebooted my system yet to see if this is permanent. But the UI doesn't show the heaphones at all and only sends sound through the main speakers of the laptop. ➜ ~ lspci -nnk | grep -i -A7 audio 00:1f.3 Audio device [0403]: Intel Corporation Device [8086:a348] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel 00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a323] (rev 10) Subsystem: Razer USA Ltd. Device [1a58:2001] Kernel driver in use: i801_smbus Kernel modules: i2c_i801 ➜ ~ cat /proc/asound/card0/codec* | grep Codec Codec: Realtek ALC256 Codec: Intel Kabylake HDMI Using for example pavucontrol allows me to select the headphone, which are marked as unplugged, and I can play audio through them as long as I keep the application open. If I reboot or close pavucontrol, everything is back to the original state and only the speakers work. Additional Information: ➜ ~ lsb_release -rd Description: Ubuntu 18.04.1 LTS Release: 18.04 What I expect to happen: When I plug in my headphones, Ubuntu and the UI should see them and automatically redirect all sound through them. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: olivar 8320 F...m pulseaudio /dev/snd/controlC0: olivar 8320 F pulseaudio CurrentDesktop: X-Cinnamon Date: Thu Dec 6 13:02:14 2018 InstallationDate: Installed on 2018-11-21 (15 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_PulsePlaybackTest: PulseAudio playback test successful Symptom_Type: Only some of outputs are working Title: [HDA-Intel - HDA Intel PCH, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: Razer dmi.bios.version: 01.01 dmi.board.name: DANA_MB dmi.board.vendor: Razer dmi.chassis.type: 10 dmi.chassis.vendor: Razer dmi.modalias: dmi:bvnRazer:bvr01.01:bd08/31/2018:svnRazer:pnBlade:pvr1.04:rvnRazer:rnDANA_MB:rvr:cvnRazer:ct10:cvr: dmi.product.family: 1A582001 Razer Blade dmi.product.name: Blade dmi.product.version: 1.04 dmi.sys.vendor: Razer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1807138/+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 1778936] Re: please re-add Support-system-image-read-only-etc.patch
** Changed in: systemd (Ubuntu Focal) Importance: Critical => High ** Patch added: "debdiff for 20.04 with the proposed fix" https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+attachment/5318599/+files/systemd_244-3ubuntu2.debdiff -- 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/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Triaged Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Focal: Triaged Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of behaviour for the classic systems. * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. [Other Info] * original bug report The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+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
Hello Michael, or anyone else affected, Accepted pulseaudio into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:13.0-1ubuntu1.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Tags added: verification-needed verification-needed-eoan -- 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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login
** Description changed: [Impact] On my freshly installed eoan system I have two output devices: - HDMI/DisplayPort 2 - GK208 ... - Line Out - Family 17h ... When I login into the system pulseaudio always select the "wrong" one (HDMI) and I need to go to gnome-settings/Sound/Output Device and switch to "line out". This applies to every login/logout not just reboots. [Test Case] 0. Plug in a monitor that supports HDMI audio (one that appears in your Settings>Sound) 1. Log out and in again. Verify the default audio device in Settings is still speakers or headphones. Not the monitor's HDMI audio device. [Regression Potential] - Low. The fix proposed just reverts to the same code used in PulseAudio - 12 and earlier. It has also been released and verified on focal already. + 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 -- 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 1845046] Re: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected
I've sponsored the 18.04 and 19.10 SRUs now -- 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/1845046 Title: Bluetooth headphones default to low quality headset mode and fail to switch to A2DP when selected Status in bluez package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Invalid Status in bluez source package in Bionic: Fix Committed Status in bluez source package in Eoan: Fix Committed Status in bluez source package in Focal: Fix Released Bug description: [Impact] Whenever I turn on my headphones they'll connect to my computer but I'm able to hear the input audio from my microphone and low quality output audio. I have to disconnect the headphones in the bluetooth devices and reconnect for it to fix the problem. [Test Case] 0. Set up your Bluetooth headphones with Ubuntu. 1. Turn off the headphones. 2. Turn on the headphones. 3. In Settings>Sound verify they have reconnected in A2DP mode (stereo, high quality, no microphone support). [Regression Potential] Low. Only the headset code path is affected and the fix has already been released for some time in BlueZ 5.51 onward. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845046/+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 1858092] Re: Network Manager not saving OpenVPN password
@panfaust or @duarte-rocha, can you test with the n-m from this ppa https://launchpad.net/~ddstreet/+archive/ubuntu/lp1858092 -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1858799] Re: lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64
This might be caused by changes to busybox since this looks like it's testing liblxc-3.0.4. In any case, I believe that the following commit in the stable-3.0 tree would fix it: https://github.com/lxc/lxc/commit/3daa49d845b153dfb2012b61dba763cbc6e11374 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1858799 Title: lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64 Status in lxc package in Ubuntu: New Status in lxc source package in Bionic: New Bug description: On Bionic with linux-raspi2-5.3 arm64: PASS: lxc-tests: lxc-test-api-reboot (78s) PASS: lxc-tests: lxc-test-apparmor (1s) PASS: lxc-tests: lxc-test-apparmor-mount (52s) PASS: lxc-tests: lxc-test-attach (3s) PASS: lxc-tests: lxc-test-autostart (68s) PASS: lxc-tests: lxc-test-basic (0s) FAIL: lxc-tests: lxc-test-cgpath (1s) --- /usr/share/lxc/templates/lxc-busybox: 143: cannot create /var/lib/lxc/lxctest1/rootfs/: Is a directory cgpath.c:91 cgroup_get failed --- PASS: lxc-tests: lxc-test-checkpoint-restore (0s) PASS: lxc-tests: lxc-test-cloneconfig (8s) PASS: lxc-tests: lxc-test-clonetest (2s) PASS: lxc-tests: lxc-test-concurrent (7s) PASS: lxc-tests: lxc-test-config-jump-table (1s) PASS: lxc-tests: lxc-test-console (3s) PASS: lxc-tests: lxc-test-console-log (10s) PASS: lxc-tests: lxc-test-containertests (5s) PASS: lxc-tests: lxc-test-createtest (1s) PASS: lxc-tests: lxc-test-criu-check-feature (0s) PASS: lxc-tests: lxc-test-cve-2019-5736 (4s) PASS: lxc-tests: lxc-test-destroytest (4s) PASS: lxc-tests: lxc-test-device-add-remove (3s) PASS: lxc-tests: lxc-test-get_item (2s) PASS: lxc-tests: lxc-test-getkeys (0s) PASS: lxc-tests: lxc-test-list (0s) PASS: lxc-tests: lxc-test-locktests (3s) PASS: lxc-tests: lxc-test-lxc-attach (4s) PASS: lxc-tests: lxc-test-lxcpath (0s) PASS: lxc-tests: lxc-test-no-new-privs (66s) PASS: lxc-tests: lxc-test-parse-config-file (0s) PASS: lxc-tests: lxc-test-raw-clone (0s) PASS: lxc-tests: lxc-test-reboot (0s) PASS: lxc-tests: lxc-test-rootfs (2s) PASS: lxc-tests: lxc-test-saveconfig (1s) PASS: lxc-tests: lxc-test-share-ns (144s) PASS: lxc-tests: lxc-test-shortlived (9s) PASS: lxc-tests: lxc-test-shutdowntest (26s) PASS: lxc-tests: lxc-test-snapshot (2s) PASS: lxc-tests: lxc-test-startone (5s) IGNORED: lxc-tests: lxc-test-state-server PASS: lxc-tests: lxc-test-symlink (2s) PASS: lxc-tests: lxc-test-unpriv (29s) PASS: lxc-tests: lxc-test-utils (0s) Removing 'local diversion of /usr/bin/dirmngr to /usr/bin/dirmngr.orig' SUMMARY: pass=39, fail=1, ignored=1 autopkgtest [20:47:46]: test exercise: ---] autopkgtest [20:47:48]: test exercise: - - - - - - - - - - results - - - - - - - - - - exercise FAIL non-zero exit status 1 autopkgtest [20:47:49]: summary exercise FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1858799/+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 1856501] Re: xgettext cannot deal with jsx self-closing tags
Thank you for your bug report, Debian is working on a gettext version update which will include that fix It doesn't seem important enough to justify a SRU backport to Bionic though, could you give a bit more details of why you think it's important and maybe a testcase which can be used to verify the issue and the fix? ** Changed in: gettext (Ubuntu) Importance: Undecided => Low ** Changed in: gettext (Ubuntu) Status: New => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gettext in Ubuntu. https://bugs.launchpad.net/bugs/1856501 Title: xgettext cannot deal with jsx self-closing tags Status in gettext package in Ubuntu: In Progress Bug description: Bug in xgettext: https://savannah.gnu.org/bugs/?56848 Fixed through https://git.savannah.gnu.org/gitweb/?p=gettext.git;a=commitdiff;h=8f8b910322f5905045a8731df7aca5e601c9b082 Can you apply this patch? It really needed. ProblemType: Bug Architecture: x86_64 Date: Mon Dec 16 09:30:05 +07 2019 DistroRelease: Ubuntu 18.04 Package: gettext 0.19.8.1-6ubuntu0.3 PackageArchitecture: amd64 SourcePackage: gettext Uname: Linux 5.0.0-36-generic #39~18.04.1-Ubuntu SMP Tue Nov 12 11:09:50 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gettext/+bug/1856501/+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 1841058] Re: kernel version 4.4.0-1090-aws docker file system issue
*** This bug is a duplicate of bug 1851243 *** https://bugs.launchpad.net/bugs/1851243 ** This bug has been marked a duplicate of bug 1851243 overlayfs : broken access to r/w files -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to sed in Ubuntu. https://bugs.launchpad.net/bugs/1841058 Title: kernel version 4.4.0-1090-aws docker file system issue Status in linux-aws package in Ubuntu: New Status in sed package in Ubuntu: New Bug description: When using kernel version 4.4.0-1090-aws if you have running container and you do sed on some files then you cannot access them inside the container any more we use the nginx image and we can reproduce it everytime in the container we have chown and then sed commands on some nginx.conf files after the sed we are getting persmission denied inside the container even that we use root. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1841058/+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 1858801] [NEW] lxd ADT failure on Bionic with linux-raspi2-5.3 arm64
Public bug reported: On Bionic with linux-raspi2-5.3 arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/arm64/l/lxd/20191219_143544_26c78@/log.gz ** Affects: lxd (Ubuntu) Importance: Undecided Status: New ** Affects: lxd (Ubuntu Bionic) Importance: Undecided Status: New ** Package changed: lxc (Ubuntu) => lxd (Ubuntu) ** Also affects: lxd (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: + On Bionic with linux-raspi2-5.3 arm64: + https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/arm64/l/lxd/20191219_143544_26c78@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1858801 Title: lxd ADT failure on Bionic with linux-raspi2-5.3 arm64 Status in lxd package in Ubuntu: New Status in lxd source package in Bionic: New Bug description: On Bionic with linux-raspi2-5.3 arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/arm64/l/lxd/20191219_143544_26c78@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxd/+bug/1858801/+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 1858802] [NEW] libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device
Public bug reported: description/debdiffs to be provided. upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 ** Affects: util-linux (Ubuntu) Importance: Undecided Assignee: Mauricio Faria de Oliveira (mfo) Status: In Progress ** Changed in: util-linux (Ubuntu) Status: New => In Progress ** Changed in: util-linux (Ubuntu) Assignee: (unassigned) => Mauricio Faria de Oliveira (mfo) ** Summary changed: - libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache device + libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1858802 Title: libblkid: no bcache UUID due to ambivalent detection of bcache and xfs_external_log for regular xfs in bcache backing device Status in util-linux package in Ubuntu: In Progress Bug description: description/debdiffs to be provided. upstream commit: https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=d756af7d640c51ce8d1414607bd3f17eeecf2424 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1858802/+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 1858092] Re: Network Manager not saving OpenVPN password
** Changed in: network-manager Status: Unknown => Fix Released -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1858799] Re: lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64
Above log is from an Eoan run. Here is Bionic: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-bionic/bionic/arm64/l/lxc/20191219_142612_71881@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1858799 Title: lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64 Status in lxc package in Ubuntu: New Status in lxc source package in Bionic: New Bug description: On Bionic with linux-raspi2-5.3 arm64: PASS: lxc-tests: lxc-test-api-reboot (78s) PASS: lxc-tests: lxc-test-apparmor (1s) PASS: lxc-tests: lxc-test-apparmor-mount (52s) PASS: lxc-tests: lxc-test-attach (3s) PASS: lxc-tests: lxc-test-autostart (68s) PASS: lxc-tests: lxc-test-basic (0s) FAIL: lxc-tests: lxc-test-cgpath (1s) --- /usr/share/lxc/templates/lxc-busybox: 143: cannot create /var/lib/lxc/lxctest1/rootfs/: Is a directory cgpath.c:91 cgroup_get failed --- PASS: lxc-tests: lxc-test-checkpoint-restore (0s) PASS: lxc-tests: lxc-test-cloneconfig (8s) PASS: lxc-tests: lxc-test-clonetest (2s) PASS: lxc-tests: lxc-test-concurrent (7s) PASS: lxc-tests: lxc-test-config-jump-table (1s) PASS: lxc-tests: lxc-test-console (3s) PASS: lxc-tests: lxc-test-console-log (10s) PASS: lxc-tests: lxc-test-containertests (5s) PASS: lxc-tests: lxc-test-createtest (1s) PASS: lxc-tests: lxc-test-criu-check-feature (0s) PASS: lxc-tests: lxc-test-cve-2019-5736 (4s) PASS: lxc-tests: lxc-test-destroytest (4s) PASS: lxc-tests: lxc-test-device-add-remove (3s) PASS: lxc-tests: lxc-test-get_item (2s) PASS: lxc-tests: lxc-test-getkeys (0s) PASS: lxc-tests: lxc-test-list (0s) PASS: lxc-tests: lxc-test-locktests (3s) PASS: lxc-tests: lxc-test-lxc-attach (4s) PASS: lxc-tests: lxc-test-lxcpath (0s) PASS: lxc-tests: lxc-test-no-new-privs (66s) PASS: lxc-tests: lxc-test-parse-config-file (0s) PASS: lxc-tests: lxc-test-raw-clone (0s) PASS: lxc-tests: lxc-test-reboot (0s) PASS: lxc-tests: lxc-test-rootfs (2s) PASS: lxc-tests: lxc-test-saveconfig (1s) PASS: lxc-tests: lxc-test-share-ns (144s) PASS: lxc-tests: lxc-test-shortlived (9s) PASS: lxc-tests: lxc-test-shutdowntest (26s) PASS: lxc-tests: lxc-test-snapshot (2s) PASS: lxc-tests: lxc-test-startone (5s) IGNORED: lxc-tests: lxc-test-state-server PASS: lxc-tests: lxc-test-symlink (2s) PASS: lxc-tests: lxc-test-unpriv (29s) PASS: lxc-tests: lxc-test-utils (0s) Removing 'local diversion of /usr/bin/dirmngr to /usr/bin/dirmngr.orig' SUMMARY: pass=39, fail=1, ignored=1 autopkgtest [20:47:46]: test exercise: ---] autopkgtest [20:47:48]: test exercise: - - - - - - - - - - results - - - - - - - - - - exercise FAIL non-zero exit status 1 autopkgtest [20:47:49]: summary exercise FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1858799/+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 1858799] Re: lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-eoan/eoan/arm64/l/lxc/20191216_204800_eb922@/log.gz -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1858799 Title: lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64 Status in lxc package in Ubuntu: New Status in lxc source package in Bionic: New Bug description: On Bionic with linux-raspi2-5.3 arm64: PASS: lxc-tests: lxc-test-api-reboot (78s) PASS: lxc-tests: lxc-test-apparmor (1s) PASS: lxc-tests: lxc-test-apparmor-mount (52s) PASS: lxc-tests: lxc-test-attach (3s) PASS: lxc-tests: lxc-test-autostart (68s) PASS: lxc-tests: lxc-test-basic (0s) FAIL: lxc-tests: lxc-test-cgpath (1s) --- /usr/share/lxc/templates/lxc-busybox: 143: cannot create /var/lib/lxc/lxctest1/rootfs/: Is a directory cgpath.c:91 cgroup_get failed --- PASS: lxc-tests: lxc-test-checkpoint-restore (0s) PASS: lxc-tests: lxc-test-cloneconfig (8s) PASS: lxc-tests: lxc-test-clonetest (2s) PASS: lxc-tests: lxc-test-concurrent (7s) PASS: lxc-tests: lxc-test-config-jump-table (1s) PASS: lxc-tests: lxc-test-console (3s) PASS: lxc-tests: lxc-test-console-log (10s) PASS: lxc-tests: lxc-test-containertests (5s) PASS: lxc-tests: lxc-test-createtest (1s) PASS: lxc-tests: lxc-test-criu-check-feature (0s) PASS: lxc-tests: lxc-test-cve-2019-5736 (4s) PASS: lxc-tests: lxc-test-destroytest (4s) PASS: lxc-tests: lxc-test-device-add-remove (3s) PASS: lxc-tests: lxc-test-get_item (2s) PASS: lxc-tests: lxc-test-getkeys (0s) PASS: lxc-tests: lxc-test-list (0s) PASS: lxc-tests: lxc-test-locktests (3s) PASS: lxc-tests: lxc-test-lxc-attach (4s) PASS: lxc-tests: lxc-test-lxcpath (0s) PASS: lxc-tests: lxc-test-no-new-privs (66s) PASS: lxc-tests: lxc-test-parse-config-file (0s) PASS: lxc-tests: lxc-test-raw-clone (0s) PASS: lxc-tests: lxc-test-reboot (0s) PASS: lxc-tests: lxc-test-rootfs (2s) PASS: lxc-tests: lxc-test-saveconfig (1s) PASS: lxc-tests: lxc-test-share-ns (144s) PASS: lxc-tests: lxc-test-shortlived (9s) PASS: lxc-tests: lxc-test-shutdowntest (26s) PASS: lxc-tests: lxc-test-snapshot (2s) PASS: lxc-tests: lxc-test-startone (5s) IGNORED: lxc-tests: lxc-test-state-server PASS: lxc-tests: lxc-test-symlink (2s) PASS: lxc-tests: lxc-test-unpriv (29s) PASS: lxc-tests: lxc-test-utils (0s) Removing 'local diversion of /usr/bin/dirmngr to /usr/bin/dirmngr.orig' SUMMARY: pass=39, fail=1, ignored=1 autopkgtest [20:47:46]: test exercise: ---] autopkgtest [20:47:48]: test exercise: - - - - - - - - - - results - - - - - - - - - - exercise FAIL non-zero exit status 1 autopkgtest [20:47:49]: summary exercise FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1858799/+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 1858799] [NEW] lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64
Public bug reported: On Bionic with linux-raspi2-5.3 arm64: PASS: lxc-tests: lxc-test-api-reboot (78s) PASS: lxc-tests: lxc-test-apparmor (1s) PASS: lxc-tests: lxc-test-apparmor-mount (52s) PASS: lxc-tests: lxc-test-attach (3s) PASS: lxc-tests: lxc-test-autostart (68s) PASS: lxc-tests: lxc-test-basic (0s) FAIL: lxc-tests: lxc-test-cgpath (1s) --- /usr/share/lxc/templates/lxc-busybox: 143: cannot create /var/lib/lxc/lxctest1/rootfs/: Is a directory cgpath.c:91 cgroup_get failed --- PASS: lxc-tests: lxc-test-checkpoint-restore (0s) PASS: lxc-tests: lxc-test-cloneconfig (8s) PASS: lxc-tests: lxc-test-clonetest (2s) PASS: lxc-tests: lxc-test-concurrent (7s) PASS: lxc-tests: lxc-test-config-jump-table (1s) PASS: lxc-tests: lxc-test-console (3s) PASS: lxc-tests: lxc-test-console-log (10s) PASS: lxc-tests: lxc-test-containertests (5s) PASS: lxc-tests: lxc-test-createtest (1s) PASS: lxc-tests: lxc-test-criu-check-feature (0s) PASS: lxc-tests: lxc-test-cve-2019-5736 (4s) PASS: lxc-tests: lxc-test-destroytest (4s) PASS: lxc-tests: lxc-test-device-add-remove (3s) PASS: lxc-tests: lxc-test-get_item (2s) PASS: lxc-tests: lxc-test-getkeys (0s) PASS: lxc-tests: lxc-test-list (0s) PASS: lxc-tests: lxc-test-locktests (3s) PASS: lxc-tests: lxc-test-lxc-attach (4s) PASS: lxc-tests: lxc-test-lxcpath (0s) PASS: lxc-tests: lxc-test-no-new-privs (66s) PASS: lxc-tests: lxc-test-parse-config-file (0s) PASS: lxc-tests: lxc-test-raw-clone (0s) PASS: lxc-tests: lxc-test-reboot (0s) PASS: lxc-tests: lxc-test-rootfs (2s) PASS: lxc-tests: lxc-test-saveconfig (1s) PASS: lxc-tests: lxc-test-share-ns (144s) PASS: lxc-tests: lxc-test-shortlived (9s) PASS: lxc-tests: lxc-test-shutdowntest (26s) PASS: lxc-tests: lxc-test-snapshot (2s) PASS: lxc-tests: lxc-test-startone (5s) IGNORED: lxc-tests: lxc-test-state-server PASS: lxc-tests: lxc-test-symlink (2s) PASS: lxc-tests: lxc-test-unpriv (29s) PASS: lxc-tests: lxc-test-utils (0s) Removing 'local diversion of /usr/bin/dirmngr to /usr/bin/dirmngr.orig' SUMMARY: pass=39, fail=1, ignored=1 autopkgtest [20:47:46]: test exercise: ---] autopkgtest [20:47:48]: test exercise: - - - - - - - - - - results - - - - - - - - - - exercise FAIL non-zero exit status 1 autopkgtest [20:47:49]: summary exercise FAIL non-zero exit status 1 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Affects: lxc (Ubuntu Bionic) Importance: Undecided Status: New ** Package changed: glibc (Ubuntu) => lxc (Ubuntu) ** Also affects: lxc (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1858799 Title: lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64 Status in lxc package in Ubuntu: New Status in lxc source package in Bionic: New Bug description: On Bionic with linux-raspi2-5.3 arm64: PASS: lxc-tests: lxc-test-api-reboot (78s) PASS: lxc-tests: lxc-test-apparmor (1s) PASS: lxc-tests: lxc-test-apparmor-mount (52s) PASS: lxc-tests: lxc-test-attach (3s) PASS: lxc-tests: lxc-test-autostart (68s) PASS: lxc-tests: lxc-test-basic (0s) FAIL: lxc-tests: lxc-test-cgpath (1s) --- /usr/share/lxc/templates/lxc-busybox: 143: cannot create /var/lib/lxc/lxctest1/rootfs/: Is a directory cgpath.c:91 cgroup_get failed --- PASS: lxc-tests: lxc-test-checkpoint-restore (0s) PASS: lxc-tests: lxc-test-cloneconfig (8s) PASS: lxc-tests: lxc-test-clonetest (2s) PASS: lxc-tests: lxc-test-concurrent (7s) PASS: lxc-tests: lxc-test-config-jump-table (1s) PASS: lxc-tests: lxc-test-console (3s) PASS: lxc-tests: lxc-test-console-log (10s) PASS: lxc-tests: lxc-test-containertests (5s) PASS: lxc-tests: lxc-test-createtest (1s) PASS: lxc-tests: lxc-test-criu-check-feature (0s) PASS: lxc-tests: lxc-test-cve-2019-5736 (4s) PASS: lxc-tests: lxc-test-destroytest (4s) PASS: lxc-tests: lxc-test-device-add-remove (3s) PASS: lxc-tests: lxc-test-get_item (2s) PASS: lxc-tests: lxc-test-getkeys (0s) PASS: lxc-tests: lxc-test-list (0s) PASS: lxc-tests: lxc-test-locktests (3s) PASS: lxc-tests: lxc-test-lxc-attach (4s) PASS: lxc-tests: lxc-test-lxcpath (0s) PASS: lxc-tests: lxc-test-no-new-privs (66s) PASS: lxc-tests: lxc-test-parse-config-file (0s) PASS: lxc-tests: lxc-test-raw-clone (0s) PASS: lxc-tests: lxc-test-reboot (0s) PASS: lxc-tests: lxc-test-rootfs (2s) PASS: lxc-tests: lxc-test-saveconfig (1s) PASS: lxc-tests: lxc-test-share-ns (144s) PASS: lxc-tests: lxc-test-shortlived (9s) PASS: lxc-tests: lxc-test-shutdowntest (26s) PASS: lxc-tests: lxc-test-snapshot (2s) PASS: lxc-tests: lxc-test-startone (5s) IGNORED: lxc-tests: lxc-test-state-server PASS: lxc-tests: lxc-test-symlink (2s) PASS: lxc-tests: lxc-test-unpriv (29s) PASS: lxc-tests: lxc-test-utils (0s) Removing 'local dive
[Touch-packages] [Bug 1858799] [NEW] lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64
You have been subscribed to a public bug: On Bionic with linux-raspi2-5.3 arm64: PASS: lxc-tests: lxc-test-api-reboot (78s) PASS: lxc-tests: lxc-test-apparmor (1s) PASS: lxc-tests: lxc-test-apparmor-mount (52s) PASS: lxc-tests: lxc-test-attach (3s) PASS: lxc-tests: lxc-test-autostart (68s) PASS: lxc-tests: lxc-test-basic (0s) FAIL: lxc-tests: lxc-test-cgpath (1s) --- /usr/share/lxc/templates/lxc-busybox: 143: cannot create /var/lib/lxc/lxctest1/rootfs/: Is a directory cgpath.c:91 cgroup_get failed --- PASS: lxc-tests: lxc-test-checkpoint-restore (0s) PASS: lxc-tests: lxc-test-cloneconfig (8s) PASS: lxc-tests: lxc-test-clonetest (2s) PASS: lxc-tests: lxc-test-concurrent (7s) PASS: lxc-tests: lxc-test-config-jump-table (1s) PASS: lxc-tests: lxc-test-console (3s) PASS: lxc-tests: lxc-test-console-log (10s) PASS: lxc-tests: lxc-test-containertests (5s) PASS: lxc-tests: lxc-test-createtest (1s) PASS: lxc-tests: lxc-test-criu-check-feature (0s) PASS: lxc-tests: lxc-test-cve-2019-5736 (4s) PASS: lxc-tests: lxc-test-destroytest (4s) PASS: lxc-tests: lxc-test-device-add-remove (3s) PASS: lxc-tests: lxc-test-get_item (2s) PASS: lxc-tests: lxc-test-getkeys (0s) PASS: lxc-tests: lxc-test-list (0s) PASS: lxc-tests: lxc-test-locktests (3s) PASS: lxc-tests: lxc-test-lxc-attach (4s) PASS: lxc-tests: lxc-test-lxcpath (0s) PASS: lxc-tests: lxc-test-no-new-privs (66s) PASS: lxc-tests: lxc-test-parse-config-file (0s) PASS: lxc-tests: lxc-test-raw-clone (0s) PASS: lxc-tests: lxc-test-reboot (0s) PASS: lxc-tests: lxc-test-rootfs (2s) PASS: lxc-tests: lxc-test-saveconfig (1s) PASS: lxc-tests: lxc-test-share-ns (144s) PASS: lxc-tests: lxc-test-shortlived (9s) PASS: lxc-tests: lxc-test-shutdowntest (26s) PASS: lxc-tests: lxc-test-snapshot (2s) PASS: lxc-tests: lxc-test-startone (5s) IGNORED: lxc-tests: lxc-test-state-server PASS: lxc-tests: lxc-test-symlink (2s) PASS: lxc-tests: lxc-test-unpriv (29s) PASS: lxc-tests: lxc-test-utils (0s) Removing 'local diversion of /usr/bin/dirmngr to /usr/bin/dirmngr.orig' SUMMARY: pass=39, fail=1, ignored=1 autopkgtest [20:47:46]: test exercise: ---] autopkgtest [20:47:48]: test exercise: - - - - - - - - - - results - - - - - - - - - - exercise FAIL non-zero exit status 1 autopkgtest [20:47:49]: summary exercise FAIL non-zero exit status 1 ** Affects: lxc (Ubuntu) Importance: Undecided Status: New -- lxc ADT test failure on Bionic with linux-raspi2-5.3 arm64 https://bugs.launchpad.net/bugs/1858799 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. -- 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 1858092] Re: Network Manager not saving OpenVPN password
** Description changed: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] - This bug was introduced after version 1.18, so it needs fixing only in - Eoan and Focal. + This is needed only in eoan. + + The patch: + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 + is included in the 1.20.6 release: + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 + + focal-proposed currently has version 1.20.8, so this patch is already + included in focal. + + This bug was introduced after version 1.18.2: + https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 + + disco-updates has version 1.60.0, so this patch is not needed in disco + or earlier. [other info] original description: --- - Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit ** Changed in: network-manager (Ubuntu Focal) Status: In Progress => Fix Released -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+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 1858092] Re: Network Manager not saving OpenVPN password
** Description changed: + [impact] + + network-manager no longer correctly saves VPN passwords + + [test case] + + on a 19.10 (or later) system, configure a VPN with network-manager and + provide a password that it should save. On next connection, it will + prompt for a password again. + + [regression potential] + + as this adjusts how n-m handles connections with secrets/passwords, any + regression would likely cause secrets to fail to be stored for later + use, and/or failure to correctly use the secrets at all to setup the + connection. + + [scope] + + This bug was introduced after version 1.18, so it needs fixing only in + Eoan and Focal. + + [other info] + + original description: + --- + + Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit ** Also affects: network-manager (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Also affects: network-manager (Ubuntu Eoan) Importance: Undecided Status: New ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/issues #230 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230 ** Also affects: network-manager via https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230 Importance: Unknown Status: Unknown ** Changed in: network-manager (Ubuntu Eoan) Status: New => In Progress ** Changed in: network-manager (Ubuntu Focal) Status: Confirmed => In Progress ** Changed in: network-manager (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: network-manager (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: network-manager (Ubuntu Eoan) Assignee: (unassigned) => Jose Manuel Santamaria Lema (panfaust) ** Changed in: network-manager (Ubuntu Focal) Assignee: (unassigned) => Jose Manuel Santamaria Lema (panfaust) -- 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/1858092 Title: Network Manager not saving OpenVPN password Status in NetworkManager: Unknown Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Eoan: In Progress Status in network-manager source package in Focal: Fix Released Bug description: [impact] network-manager no longer correctly saves VPN passwords [test case] on a 19.10 (or later) system, configure a VPN with network-manager and provide a password that it should save. On next connection, it will prompt for a password again. [regression potential] as this adjusts how n-m handles connections with secrets/passwords, any regression would likely cause secrets to fail to be stored for later use, and/or failure to correctly use the secrets at all to setup the connection. [scope] This is needed only in eoan. The patch: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/cf557bf06f344bdbcd775dce35daa42335c645d7 is included in the 1.20.6 release: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_283402 focal-proposed currently has version 1.20.8, so this patch is already included in focal. This bug was introduced after version 1.18.2: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/230#note_235976 disco-updates has version 1.60.0, so this patch is not needed in disco or earlier. [other info] original description: --- Hi everyone, After upgrading to kubuntu 19.10 I can't save the VPN password using Store password for this user only. It seems the integration with the kwallet is failing somehow... The system logs seem to show that everything went ok, but the password is not saved: jan 02 11:40:40 NetworkManager[5530]: [1577965240.2166] audit: op="connection-update" uuid="4c05-911a-1d9161f05a19" name="ovpn" args="vpn.secrets" pid=14142 uid=1000 result="success" This also happens with a clean install. Operating System: Kubuntu 19.10 KDE Plasma Version: 5.16.5 KDE Frameworks Version: 5.62.0 Qt Version: 5.12.4 Kernel Version: 5.3.0-24-generic OS Type: 64-bit To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1858092/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post t
[Touch-packages] [Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: Fix Released ** Changed in: systemd (Ubuntu Focal) Status: Fix Released => Triaged ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Critical -- 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/1778936 Title: please re-add Support-system-image-read-only-etc.patch Status in systemd package in Ubuntu: Triaged Status in systemd source package in Bionic: Fix Released Status in systemd source package in Cosmic: Fix Released Status in systemd source package in Focal: Triaged Bug description: [Impact] * core18 systems fail to update hostname * this happens due to /etc/hostname actually being a symlink to a file under /etc/writable/, adjust hostnamed to take that into account when trying to update /etc/hostname [Test Case] * run a core18 system, check that dhcp acquire hostname is correctly updated in /etc/writable/hostname [Regression Potential] * This is cherrypick of code that has gone missing since xenial. * There is no change of behaviour for the classic systems. * Currently, core18 systems simply fail to update hostname/machine-info files, thus the worst case is that they will still fail to do so. [Other Info] * original bug report The 16.04 version of systemd had a patch to support the read-only etc. For core18 we will also need this change because core18 is still not on a fully writable etc. I will attach a debdiff against the current bionic version of systemd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+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
Don't comment on a close bug, if that's still a problem better to report a new bug (using ubuntu-bug so the system informations are included) -- 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: Fix Released 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 1797002] Re: Bluetooth audio skips while the settings dialog is open
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: pulseaudio (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: Bluetooth audio skips while the settings dialog is open Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1797002] Re: Bluetooth audio skips while the settings dialog is open
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bluez (Ubuntu) Status: New => Confirmed -- 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/1797002 Title: Bluetooth audio skips while the settings dialog is open Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1797002] Re: Bluetooth audio skips while the settings dialog is open
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-control-center (Ubuntu) Status: New => Confirmed -- 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/1797002 Title: Bluetooth audio skips while the settings dialog is open Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+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 1086783] Re: New PolicyKit 0.106 changes configuration file format
@Robert, I would start by getting the security team's input on using mozjs or duktape, if it's a no go from their side then we know what are our options. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to policykit-1 in Ubuntu. https://bugs.launchpad.net/bugs/1086783 Title: New PolicyKit 0.106 changes configuration file format Status in policykit-1 package in Ubuntu: Triaged Status in policykit-1 package in Debian: Fix Released Bug description: From the NEWS file: This is polkit 0.106. There's a major change in this release which is a switch from .pkla files (keyfile-format) to .rules files (JavaScript). We may want to hold off on the new version because it requires rewriting the configuration files, and adds a dependency on mozjs185, which will need a MIR (and getting a MIR may be problematic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1086783/+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
Please reopen the bug! ** Tags removed: trusty ** Tags added: eoan ** Description changed: + 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 ** Changed in: network-manager-openconnect (Ubuntu) Assignee: (unassigned) => Yannis Tsop (ogiannhs) -- 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: Fix Released 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
