[Touch-packages] [Bug 1827253] Re: [apparmor] missing 'mr' on binary for usage on containers
MPs got reviewed and uploaded to D/B SRU queue -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to rsyslog in Ubuntu. https://bugs.launchpad.net/bugs/1827253 Title: [apparmor] missing 'mr' on binary for usage on containers Status in rsyslog package in Ubuntu: Fix Released Status in rsyslog source package in Bionic: Triaged Status in rsyslog source package in Disco: Triaged Bug description: [Impact] * rsyslog ships with a (Default disable) apparmor profile. * Security sensitive users are in general encouraged to enable such profiles but unfortunately due to slightly new behavior of the program the profile prevents its usage. * Allow the program to map/read its binary to get this working again [Test Case] 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog [Regression Potential] * This is just opening up the apparmor profile a bit. Therefore the only regression it could cause IMHO is a security issue. But then what it actually allows is reading (not writing!) its own binary which should be very safe. * Thinking further it came to my mind that package updates (independent to the change) might restart services and that means if there is any issue e.g. in a local config that worked but now fails (not by this change but in general) then the upgrade will not cause, but trigger this. This is a general regression risk for any upload, but in this case worth to mention as it is about log handling - which if broken - makes large scale systems hard to debug. [Other Info] * n/a --- Issue description: Enabling the rsyslog (disabled by default) Apparmor profile causes rsyslog to fail to start when running *inside a container*. Steps to reproduce: 1) Create a 'eoan' container called rs1 here: lxc launch ubuntu-daily:e rs1 2) Enter the container lxc shell rs1 3) Enable apparmor profile rm /etc/apparmor.d/disable/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog 4) notice rsyslog failed to start systemctl status rsyslog Workaround: echo ' /usr/sbin/rsyslogd mr,' >> /etc/apparmor.d/local/usr.sbin.rsyslogd apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.rsyslogd systemctl restart rsyslog Additional information: root@rs1:~# uname -a Linux rs1 4.15.0-48-generic #51-Ubuntu SMP Wed Apr 3 08:28:49 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux root@rs1:~# lsb_release -rd Description: Ubuntu Eoan EANIMAL (development branch) Release: 19.10 root@rs1:~# dpkg -l| grep -wE 'apparmor|rsyslog' ii apparmor 2.13.2-9ubuntu6 amd64user-space parser utility for AppArmor ii rsyslog 8.32.0-1ubuntu7 amd64reliable system and kernel logging daemon ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: rsyslog 8.32.0-1ubuntu7 ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18 Uname: Linux 4.15.0-48-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 Date: Wed May 1 17:36:29 2019 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: rsyslog UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1827253/+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 1843381] Re: Dell system takes a long time to connect network with external dock
Yes, since it will be the same result as udev failed to rename it, it doesn't matter. -- 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/1843381 Title: Dell system takes a long time to connect network with external dock Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: This is a bug reopen from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700 The original one caused systemd regressed. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651 This issue needs an alternative solution. Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+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 1847896] Re: Unable to shutdown or restart from log-in screen
** Tags added: fixed-in-243 fixed-upstream -- 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/1847896 Title: Unable to shutdown or restart from log-in screen Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: When selecting the shutdown icon from the log-in screen you are prompted with a dialog that allows you to either cancel, restart or shutdown. It has been noted that the restart and shutdown options no longer work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 13 09:08:23 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (148 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1556439] Re: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_se
Hello Anders, or anyone else affected, Accepted pulseaudio into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.4 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Tags removed: verification-done-bionic ** Tags added: verification-needed-bionic -- 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/1556439 Title: pulseaudio crashed with SIGABRT in pa_sink_input_assert_ref() from pa_sink_input_finish_move() from pa_sink_move_all_finish() from card_set_profile() from pa_card_set_profile Status in PulseAudio: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Cosmic: Fix Released Status in pulseaudio source package in Disco: Fix Released Status in pulseaudio source package in Eoan: Fix Released Bug description: [Impact] https://errors.ubuntu.com/problem/a83a007593c81501c4fbb4e9ac0f47e0b3880d17 This is one of the top pulseaudio crashes in Ubuntu 18.04 according to: https://errors.ubuntu.com/?release=Ubuntu%2018.04=pulseaudio=year [Test Case] No manual test case known. Just watch errors.ubuntu.com to check for recurrences. [Regression Potential] Low. The fix is already in PulseAudio 12 so has been used in Ubuntu 18.10 and later for a year so far. [Original Report] Changing between Logitech G933 digital and analog and Logitech G930 digital and analog ProblemType: Crash DistroRelease: Ubuntu 16.04 Package: pulseaudio 1:8.0-0ubuntu2 ProcVersionSignature: Ubuntu 4.4.0-12.28-generic 4.4.4 Uname: Linux 4.4.0-12-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_modeset wl nvidia ApportVersion: 2.20-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Sat Mar 12 17:20:34 2016 EcryptfsInUse: Yes ExecutablePath: /usr/bin/pulseaudio InstallationDate: Installed on 2016-02-22 (19 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) ProcCmdline: /usr/bin/pulseaudio --start --log-target=syslog ProcEnviron: PATH=(custom, no user) SHELL=/bin/bash LANG=sv_SE.UTF-8 LANGUAGE=sv XDG_RUNTIME_DIR= Signal: 6 SourcePackage: pulseaudio StacktraceTop: pa_sink_input_finish_move () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so pa_sink_move_all_finish () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/module-alsa-card.so pa_card_set_profile () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecore-8.0.so ?? () from /usr/lib/pulse-8.0/modules/libprotocol-native.so Title: pulseaudio crashed with SIGABRT in pa_sink_input_finish_move() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo dmi.bios.date: 09/30/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2001 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: X99-DELUXE dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2001:bd09/30/2015:svnASUS:pnAllSeries:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnX99-DELUXE:rvrRev1.xx:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: All Series dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1556439/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help :
[Touch-packages] [Bug 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports
Hello Hui, or anyone else affected, Accepted pulseaudio into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/pulseaudio/1:11.1-1ubuntu7.4 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: pulseaudio (Ubuntu Bionic) Status: Incomplete => Fix Committed ** Tags added: verification-needed-bionic -- 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/1834138 Title: PA: Don't restore the streams to sinks/sources with only unavailable ports Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio source package in Bionic: Fix Committed Status in pulseaudio source package in Disco: Fix Committed Status in pulseaudio source package in Eoan: Fix Released Bug description: SRU Document: [Impact] The Lenovo P520 machine has dual analogue codecs, so there are two sinks and two sources in the PA, one has the front headphone and front microphone, the other has the rear lineout, linein and rear microphone, and the rear microphone always shows up in the gnome- sound-setting, When we plug a microphone to front audio jack, there are two input devices: rear mic and front mic in the gnome-sound- setting, and suppose users select the the front mic to record sound via audio app like arecord, the front mic will be bond the arecord, after the front mic is unplugged, there is only one rear mic left in the gnome-sound-setting, but the binding will not be changed, the arecrod still bind to front mic, under this situation if users record sound via arecord, they will find they can't record any sound from any other input devices even they are listed in the gnome-sound-setting. This problem also happens to output devices too. [Test Case] After applying this patch, I did the same test: unplug the front mic, then use the arecord to record sound, the app can record sound from rear mic now. After I plug the front mic back, the arecord still record from front mic. Also did the similar test for output devices, it worked as expected too. [Regression Potential] Low, Just make a simple check when creating new streams (sink_input/source_output), If the restored device (sink/source) has ports and all ports are unavialble, it will not restore the binding, otherwise it will work as before. For the Bionic, This SRU also includes the fix of LP: #1556439, this fix is safe and is very low possible to introduce any regression too, because it just adds a sink-input/source-output state checking, if the sink-input/source-output is unlinking or unlinked, it is useless to move it to a new sink/source, furthermore it will trigger an assertion that make the pulseaudio crash, adding this check can fix this problem (LP: #1556439). [Other Info] No more info here To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834138/+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 945448] Re: add toolbar commands pane shrinks, disappears
Launchpad has imported 4 comments from the remote bug at https://bugs.documentfoundation.org/show_bug.cgi?id=46924. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2012-03-03T02:52:37+00:00 Satchit Bhogle wrote: Created attachment 57964 Screenshot of problem Problem description: See steps and attached image. Steps to reproduce: 1. Go to Tools > Customise > Toolbars, and click Add. 2. Move to a toolbar that does not have enough elements to fill the pane, e.g. Data. Now back to something that has, e.g. Application. 3. Keep switching between toolbars. 4. Watch the commands pane gradually shrink and then disappear. Current behavior: The pane shrinks for toolbars with fewer elements and then stays shrunk when going to a toolbar with more elements. Expected behavior: The pane remains the same size regardless. Platform (if different from the browser): Ubuntu 11.10 Oneiric stable 32-bit Browser: Mozilla/5.0 (X11; Ubuntu; Linux i686; rv:10.0.2) Gecko/20100101 Firefox/10.0.2 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/945448/comments/0 On 2012-03-03T06:32:21+00:00 Björn Michaelsen wrote: _NOT_ reproducable at upstream libreoffice-3-5 branch-off without Ubuntus default theme. reproducable with 1:3.5.0-1ubuntu4 with Ubuntus theme. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/945448/comments/1 On 2012-03-03T07:48:14+00:00 Björn Michaelsen wrote: Also not reproducable on upstream master (1cf3e446744ae679bc89b39dcbbcf6b4e9821f3a) without default Ubuntu theming on oneiric. Also not reproducable on 3.4.5 Ubuntu build on oneiric. This seems to be a regression between oneiric->precise in either Ubuntus theme or stack (gtk?) resolving here as not our bug. Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/945448/comments/2 On 2012-03-03T07:59:16+00:00 Björn Michaelsen wrote: Of course, it could well be that it is a bug in the libreoffice gtk-vcl plugin which only shows with recent versions of gtk. In that case, please reopen. @Fedora, SUSE user: Can you reproduce this with a very new gtk? The issie is visible here with gtk+-2.24.10-0ubuntu4 Reply at: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/945448/comments/3 ** Changed in: df-libreoffice Status: Unknown => Won't Fix ** Changed in: df-libreoffice Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/945448 Title: add toolbar commands pane shrinks, disappears Status in LibreOffice: Won't Fix Status in One Hundred Papercuts: Invalid Status in gtk+2.0 package in Ubuntu: New Status in libreoffice package in Ubuntu: Incomplete Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.0-1ubuntu3~oneiric1 Candidate: 1:3.5.0-1ubuntu3~oneiric1 Version table: *** 1:3.5.0-1ubuntu3~oneiric1 0 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.4-0ubuntu1 0 500 http://in.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 1:3.4.3-3ubuntu2 0 500 http://in.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages See attached image. Steps to reproduce: 1. Go to Tools > Customise > Toolbars, and click Add. 2. Move to a toolbar that does not have enough elements to fill the pane, e.g. Data. Now back to something that has, e.g. Application. 3. Keep switching between toolbars. 4. Watch the commands pane gradually shrink and then disappear. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/945448/+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 1848237] Re: amd64-only test running on i386
** Changed in: six (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1848237
Title:
amd64-only test running on i386
Status in python-pyeclib package in Ubuntu:
New
Status in six package in Ubuntu:
Invalid
Bug description:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {} architecture".format(sys.argv[1], arch))
else:
...
In eoan, at some point during the development cycle, the VM running i386
tests is actually on an amd64 kernel:
"""
...
-name adt-eoan-i386-python-pyeclib-20191014-091043 --image
adt/ubuntu-eoan-i386-server
...
Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/universe Sources [127 kB]
Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 Packages
[18.0 kB]
Get:7 http://ftpmaster.internal/ubuntu eoan-proposed/main i386 Packages [12.9
kB]
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test
will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/tests/encode-decode.py
isa_l_rs_vand
autopkgtest [09:22:26]: test command7: [---
Traceback (most recent call last):
File "debian/tests/encode-decode.py", line 15, in
ec = ECDriver(k=3, m=3, hd=3, ec_type=sys.argv[1])
File "/usr/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 212, in
__init__
validate=int(self.validate)
File "/usr/lib/python2.7/dist-packages/pyeclib/utils.py", line 73, in
create_instance
instance = object_class(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pyeclib/core.py", line 61, in
__init__
validate)
pyeclib.ec_iface.ECBackendInstanceNotAvailable: pyeclib_c_init ERROR: Backend
instance not found. Please inspect syslog for liberasurecode error report.
init: autopkgtest [09:22:26]: test command7: ---]
It's probably best to use "dpkg --architecture" for this check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyeclib/+bug/1848237/+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 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration
kalvdans -- they don't get it. Inflexibility for inflexibility's sake is the new goal. My proposed fix is very simple and safe, but because it allows flexibility it's not going to be accepted. Feel free to edit the broken script in the package to enable your setup to work properly. I've done this on several systems I administer and they are running as one would expect now. -- 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/1745463 Title: Disabling systemd-resolved breaks dhclient resolvconf integration Status in resolvconf package in Ubuntu: Expired Status in systemd package in Ubuntu: New Bug description: To reproduce, mask resolved: sudo systemctl mask systemd-resolved.service ...then disable network-manager for ifupdown interfaces: $cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile dns=default rc-manager=resolvconf [ifupdown] managed=false [device] wifi.scan-rand-mac-address=no ...and reboot. You'll note that resolvconf integration with dhclient is now broken. Interfaces listed in /etc/network/interfaces or /etc/network/interfaces.d/* will not provide DNS configuration in /etc/resolv.conf and /run/resolvconf/interfaces/. This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines "make_resolv_conf()" as a valid function for the BOUND case, but /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty now, eh?) even though resolved is masked. The file existence check in the beginning of /etc/dhcp/dhclient-enter- hooks.d/resolved should be more thorough, i.e. it should ensure that resolved is enabled, rather than simply look for the existence of /lib/systemd/systemd-resolved. This works for me: -if [ -x /lib/systemd/systemd-resolved ] ; then +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled systemd-resolved ; then Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement a similar check, looking for /run/resolvconf/enable-updates as a condition for meddling with DNS settings. If desired, I'll file a separate bug for that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+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 1848237] Re: amd64-only test running on i386
Currently testing this fix in bileto:
https://code.launchpad.net/~ahasenack/ubuntu/+source/python-pyeclib/+git
/python-pyeclib/+ref/eoan-dep8-fix-1848237
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1848237
Title:
amd64-only test running on i386
Status in python-pyeclib package in Ubuntu:
New
Status in six package in Ubuntu:
New
Bug description:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {} architecture".format(sys.argv[1], arch))
else:
...
In eoan, at some point during the development cycle, the VM running i386
tests is actually on an amd64 kernel:
"""
...
-name adt-eoan-i386-python-pyeclib-20191014-091043 --image
adt/ubuntu-eoan-i386-server
...
Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/universe Sources [127 kB]
Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 Packages
[18.0 kB]
Get:7 http://ftpmaster.internal/ubuntu eoan-proposed/main i386 Packages [12.9
kB]
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test
will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/tests/encode-decode.py
isa_l_rs_vand
autopkgtest [09:22:26]: test command7: [---
Traceback (most recent call last):
File "debian/tests/encode-decode.py", line 15, in
ec = ECDriver(k=3, m=3, hd=3, ec_type=sys.argv[1])
File "/usr/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 212, in
__init__
validate=int(self.validate)
File "/usr/lib/python2.7/dist-packages/pyeclib/utils.py", line 73, in
create_instance
instance = object_class(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pyeclib/core.py", line 61, in
__init__
validate)
pyeclib.ec_iface.ECBackendInstanceNotAvailable: pyeclib_c_init ERROR: Backend
instance not found. Please inspect syslog for liberasurecode error report.
init: autopkgtest [09:22:26]: test command7: ---]
It's probably best to use "dpkg --architecture" for this check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyeclib/+bug/1848237/+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 1843099] Re: Unattended upgrades does not work on shutdown
Thank you! I should've responded but your earlier explanation did make sense so I was thinking of just adjusting the value you mentioned and didn't respond. Still I believe the fix will be useful to many. Essentially we do quarterly patching, unless there's an urgent security need, so there often are a lot of packages to update. This is in a corporate environment. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1843099 Title: Unattended upgrades does not work on shutdown Status in unattended-upgrades package in Ubuntu: In Progress Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu * Ubuntu Xenial 16.04.6 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center * 1.1ubuntu1.18.04.7~16.04.3 3) What you expected to happen * Packages to be upgraded on reboot / shutdown. 4) What happened instead * The host just rebooted. Didn't perform upgrades. No useful output either until I enabled debug logging in the systemd unit file. I'm reporting a new bug but this is very similar to #1806487 and I'm actually wondering if it resurfaced somehow. We're running Ubuntu Xenial 16.04.6 which has 1.1ubuntu1.18.04.7~16.04.3 installed. I see that #1806487 was resolved with 1.1ubuntu1.18.04.7~16.04.2. However I'm seeing similar behavior. So far I've modified systemd to see if anything stands out. I do have an strace and then just debug mode. Unless needed, simply put, this is what a reboot with debug logging looks like (i.e. unattended-upgrades-shutdown.log): 2019-09-06 09:20:04,871 DEBUG - Waiting for signal to start operation 2019-09-06 09:20:43,996 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2019-09-06 09:20:43,996 DEBUG - Starting countdown of 25.0 minutes 2019-09-06 09:20:43,997 DEBUG - get_lock returned 7 2019-09-06 09:20:43,997 DEBUG - lock not taken I hope that helps, please let me know if you need anything else from me or if I can provide any more information. I've done this many times before, this is the first time it hasn't worked. When I patched around the end of May, all went well. My other variants worked, well mainly Trusty but that's EOL for public access. Bionic doesn't seem to have anything it needs to update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1843099/+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 1843099] Re: Unattended upgrades does not work on shutdown
The following fix should speed up u-u where originally it tried to adjust a lot of packages: https://github.com/mvo5/unattended-upgrades/pull/231 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1843099 Title: Unattended upgrades does not work on shutdown Status in unattended-upgrades package in Ubuntu: In Progress Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu * Ubuntu Xenial 16.04.6 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center * 1.1ubuntu1.18.04.7~16.04.3 3) What you expected to happen * Packages to be upgraded on reboot / shutdown. 4) What happened instead * The host just rebooted. Didn't perform upgrades. No useful output either until I enabled debug logging in the systemd unit file. I'm reporting a new bug but this is very similar to #1806487 and I'm actually wondering if it resurfaced somehow. We're running Ubuntu Xenial 16.04.6 which has 1.1ubuntu1.18.04.7~16.04.3 installed. I see that #1806487 was resolved with 1.1ubuntu1.18.04.7~16.04.2. However I'm seeing similar behavior. So far I've modified systemd to see if anything stands out. I do have an strace and then just debug mode. Unless needed, simply put, this is what a reboot with debug logging looks like (i.e. unattended-upgrades-shutdown.log): 2019-09-06 09:20:04,871 DEBUG - Waiting for signal to start operation 2019-09-06 09:20:43,996 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2019-09-06 09:20:43,996 DEBUG - Starting countdown of 25.0 minutes 2019-09-06 09:20:43,997 DEBUG - get_lock returned 7 2019-09-06 09:20:43,997 DEBUG - lock not taken I hope that helps, please let me know if you need anything else from me or if I can provide any more information. I've done this many times before, this is the first time it hasn't worked. When I patched around the end of May, all went well. My other variants worked, well mainly Trusty but that's EOL for public access. Bionic doesn't seem to have anything it needs to update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1843099/+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 1843099] Re: Unattended upgrades does not work on shutdown
** Changed in: unattended-upgrades (Ubuntu) Status: Invalid => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unattended-upgrades in Ubuntu. https://bugs.launchpad.net/bugs/1843099 Title: Unattended upgrades does not work on shutdown Status in unattended-upgrades package in Ubuntu: In Progress Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu * Ubuntu Xenial 16.04.6 LTS 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center * 1.1ubuntu1.18.04.7~16.04.3 3) What you expected to happen * Packages to be upgraded on reboot / shutdown. 4) What happened instead * The host just rebooted. Didn't perform upgrades. No useful output either until I enabled debug logging in the systemd unit file. I'm reporting a new bug but this is very similar to #1806487 and I'm actually wondering if it resurfaced somehow. We're running Ubuntu Xenial 16.04.6 which has 1.1ubuntu1.18.04.7~16.04.3 installed. I see that #1806487 was resolved with 1.1ubuntu1.18.04.7~16.04.2. However I'm seeing similar behavior. So far I've modified systemd to see if anything stands out. I do have an strace and then just debug mode. Unless needed, simply put, this is what a reboot with debug logging looks like (i.e. unattended-upgrades-shutdown.log): 2019-09-06 09:20:04,871 DEBUG - Waiting for signal to start operation 2019-09-06 09:20:43,996 WARNING - SIGTERM or SIGHUP received, stopping unattended-upgradesonly if it is running 2019-09-06 09:20:43,996 DEBUG - Starting countdown of 25.0 minutes 2019-09-06 09:20:43,997 DEBUG - get_lock returned 7 2019-09-06 09:20:43,997 DEBUG - lock not taken I hope that helps, please let me know if you need anything else from me or if I can provide any more information. I've done this many times before, this is the first time it hasn't worked. When I patched around the end of May, all went well. My other variants worked, well mainly Trusty but that's EOL for public access. Bionic doesn't seem to have anything it needs to update. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1843099/+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 1843381] Re: Dell system takes a long time to connect network with external dock
Ok, so just to clarify, the only issue here is the delay/failure for the system to finish bringing its networking up, right? The exact name of the second "duplicated mac" interface doesn't really matter? -- 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/1843381 Title: Dell system takes a long time to connect network with external dock Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: This is a bug reopen from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700 The original one caused systemd regressed. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651 This issue needs an alternative solution. Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/tree/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch?h=ubuntu-bionic To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1843381/+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 1316830] Re: /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak
Is incredible how this is still a thing in 2019 in Ubuntu 18.04 LTS... -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1316830 Title: /usr/lib/accountsservice/accounts-daemon :: memory and CPU time leak Status in accountsservice package in Ubuntu: Confirmed Bug description: netikras@netikras-netbook ~/received/accountsservice-0.6.20 $ cat /etc/lsb-release DISTRIB_ID=LinuxMint DISTRIB_RELEASE=16 DISTRIB_CODENAME=petra DISTRIB_DESCRIPTION="Linux Mint 16 Petra" uname -a Linux netikras-netbook 3.11.0-12-generic #19-Ubuntu SMP Wed Oct 9 16:12:00 UTC 2013 i686 i686 i686 GNU/Linux Nothing. Using my netbook as usual. Did not really notice when this started since earlier today did not feel any significant slowdowns. That's what happened: PID USER PR NI VIRT RES SHR S %CPU %MEMTIME+ COMMAND 13155 root 20 0 61424 25m 2948 R 99,6 1,3 1:06.01 accounts-daemon netikras@netikras-netbook /tmp $ while :; do ps aux | grep accounts|grep -v grep;echo; sleep 2; done root 13155 93.6 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon root 13155 92.7 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon root 13155 91.9 26.1 555660 519912 pts/0 Sl 01:11 3:15 /usr/lib/accountsservice/accounts-daemon accounts-daemon is using lots o CPU cycles and memory. Stats above are after restarting daemon for several times. Before this memory usage was >60%; CPU - 100%. In file attached you should be able to see there's a loop checking for something repeatedly. Not sure this is the cause though, but feels like it.. It's the first time I've noticed this problem, but I often leave my computer running unattended so I cannot tell if it's really the first time it happened. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1316830/+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 1631161] Re: Preferred output device is not remembered between logins
@Doug, you should probably open a new bug including details about your audio configuration, your ubuntu version/desktop and journal log -- 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/1631161 Title: Preferred output device is not remembered between logins Status in pulseaudio package in Ubuntu: Confirmed Bug description: Whenever I reboot anew, pulseaudio has forgotten the correct audio port which I have set using the kde pulseaudio tool. I use line out, but it defaults to headphones, which is incorrect for my current setup. I expect it to remember that I wanted line out every time. Once selected, everything runs fine for that session, but it doesn't get saved and defaults back to the wrong output every time. Guessing this is pulseaudio as it happens with the gnome tool also. Tested not working in 16.04, 16.10 and Mint 18 (packages from 16.04). Policy installed: 1:8.0-0ubuntu3 Cheers --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: kvd1577 F...m pulseaudio /dev/snd/pcmC0D0p: kvd1577 F...m pulseaudio /dev/snd/controlC0: kvd1577 F pulseaudio CurrentDesktop: KDE DistroRelease: Linux 18 InstallationDate: Installed on 2016-10-02 (5 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160904 NonfreeKernelModules: nvidia_uvm nvidia Package: pulseaudio 1:8.0-0ubuntu3 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Tags: sarah third-party-packages Uname: Linux 4.4.0-38-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/24/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5f dmi.board.name: GA-770T-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5f:bd09/24/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-770T-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770T-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-770T-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1631161/+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
Re: [Touch-packages] [Bug 1831736] Re: [MIR] lz4 by default
On Tue, Oct 15, 2019 at 09:30:48AM -, Dimitri John Ledkov wrote: > However 298.1MB is larger than old installs. Do you mean that 298.1MB is larger than what old installs will guarantee for a /boot partition? Which old releases in particular will be affected? Shouldn't this be called out in the release notes? For reference: $ df -h /boot Filesystem Size Used Avail Use% Mounted on /dev/sda5 280M 116M 145M 45% /boot $ With an Ubuntu 10.04.1 vintage install ;) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831736 Title: [MIR] lz4 by default Status in Release Upgrader: New Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in partman-auto package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) I booted grub2 and measured loading largish amount of files, ie. $ date; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; date To get a rough speed between 30 and 44 MB/s of loading these files off ext4 on nvme. With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o penalty is 0.18s whilst I gain over a second in faster decompression time. Overall a win. xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining 2.4s of decompression time, meaning overall worse than gzip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1831736/+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 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration
> I'm running a system without network-manager, without netplan, without > resolvconf. Only ifupdown and dhclient. I expect /etc/resolv.conf to be > updated by the logic in /sbin/dhclient-script where it (correctly, in my > system) assumes it is the only source of dns servers. I have reopened > the bug. I repeat myself: Flexibility for flexibility's sake is not a goal of Ubuntu. That you have disabled a base component of Ubuntu and the resulting system does not function as you expect is not a valid bug report against Ubuntu. If there are scenarios where it is not appropriate to run resolved, then we should absolutely evaluate those and determine how they should be supported in Ubuntu. However, they must be evaluated on their own merits, which means that the technical details must be presented for consideration. -- 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/1745463 Title: Disabling systemd-resolved breaks dhclient resolvconf integration Status in resolvconf package in Ubuntu: Expired Status in systemd package in Ubuntu: New Bug description: To reproduce, mask resolved: sudo systemctl mask systemd-resolved.service ...then disable network-manager for ifupdown interfaces: $cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile dns=default rc-manager=resolvconf [ifupdown] managed=false [device] wifi.scan-rand-mac-address=no ...and reboot. You'll note that resolvconf integration with dhclient is now broken. Interfaces listed in /etc/network/interfaces or /etc/network/interfaces.d/* will not provide DNS configuration in /etc/resolv.conf and /run/resolvconf/interfaces/. This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines "make_resolv_conf()" as a valid function for the BOUND case, but /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty now, eh?) even though resolved is masked. The file existence check in the beginning of /etc/dhcp/dhclient-enter- hooks.d/resolved should be more thorough, i.e. it should ensure that resolved is enabled, rather than simply look for the existence of /lib/systemd/systemd-resolved. This works for me: -if [ -x /lib/systemd/systemd-resolved ] ; then +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled systemd-resolved ; then Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement a similar check, looking for /run/resolvconf/enable-updates as a condition for meddling with DNS settings. If desired, I'll file a separate bug for that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+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 1848237] [NEW] amd64-only test running on i386
Public bug reported:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {} architecture".format(sys.argv[1], arch))
else:
...
In eoan, at some point during the development cycle, the VM running i386 tests
is actually on an amd64 kernel:
"""
...
-name adt-eoan-i386-python-pyeclib-20191014-091043 --image
adt/ubuntu-eoan-i386-server
...
Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/universe Sources [127 kB]
Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 Packages [18.0
kB]
Get:7 http://ftpmaster.internal/ubuntu eoan-proposed/main i386 Packages [12.9
kB]
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test
will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/tests/encode-decode.py
isa_l_rs_vand
autopkgtest [09:22:26]: test command7: [---
Traceback (most recent call last):
File "debian/tests/encode-decode.py", line 15, in
ec = ECDriver(k=3, m=3, hd=3, ec_type=sys.argv[1])
File "/usr/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 212, in
__init__
validate=int(self.validate)
File "/usr/lib/python2.7/dist-packages/pyeclib/utils.py", line 73, in
create_instance
instance = object_class(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pyeclib/core.py", line 61, in __init__
validate)
pyeclib.ec_iface.ECBackendInstanceNotAvailable: pyeclib_c_init ERROR: Backend
instance not found. Please inspect syslog for liberasurecode error report.
init: autopkgtest [09:22:26]: test command7: ---]
It's probably best to use "dpkg --architecture" for this check.
** Affects: python-pyeclib (Ubuntu)
Importance: Undecided
Status: New
** Affects: six (Ubuntu)
Importance: Undecided
Status: New
** Tags: update-excuse
** Also affects: six (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1848237
Title:
amd64-only test running on i386
Status in python-pyeclib package in Ubuntu:
New
Status in six package in Ubuntu:
New
Bug description:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {} architecture".format(sys.argv[1], arch))
else:
...
In eoan, at some point during the development cycle, the VM running i386
tests is actually on an amd64 kernel:
"""
...
-name adt-eoan-i386-python-pyeclib-20191014-091043 --image
adt/ubuntu-eoan-i386-server
...
Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/universe Sources [127 kB]
Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 Packages
[18.0 kB]
Get:7 http://ftpmaster.internal/ubuntu eoan-proposed/main i386 Packages [12.9
kB]
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test
will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/tests/encode-decode.py
isa_l_rs_vand
autopkgtest [09:22:26]: test command7: [---
Traceback (most recent call last):
File "debian/tests/encode-decode.py", line 15, in
ec = ECDriver(k=3, m=3, hd=3, ec_type=sys.argv[1])
File "/usr/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 212, in
__init__
validate=int(self.validate)
File "/usr/lib/python2.7/dist-packages/pyeclib/utils.py", line 73, in
create_instance
instance = object_class(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pyeclib/core.py", line 61, in
__init__
validate)
pyeclib.ec_iface.ECBackendInstanceNotAvailable: pyeclib_c_init ERROR: Backend
instance not found. Please inspect syslog for liberasurecode error report.
init: autopkgtest [09:22:26]: test command7: ---]
It's probably best to use "dpkg --architecture" for this check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyeclib/+bug/1848237/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1848237] Re: amd64-only test running on i386
Added six to the list of affected packages so that this bug will show up
in the excuses report as to why six isn't migrating.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to six in Ubuntu.
https://bugs.launchpad.net/bugs/1848237
Title:
amd64-only test running on i386
Status in python-pyeclib package in Ubuntu:
New
Status in six package in Ubuntu:
New
Bug description:
Some tests in d/t/control are not meant to be run on non-amd64 architectures.
The test script tries to detect this and skip them:
arch = platform.machine()
if sys.argv[1].startswith('isa_') and arch == 'x86_64':
print("Skipping {} test for {} architecture".format(sys.argv[1], arch))
else:
...
In eoan, at some point during the development cycle, the VM running i386
tests is actually on an amd64 kernel:
"""
...
-name adt-eoan-i386-python-pyeclib-20191014-091043 --image
adt/ubuntu-eoan-i386-server
...
Get:5 http://ftpmaster.internal/ubuntu eoan-proposed/universe Sources [127 kB]
Get:6 http://ftpmaster.internal/ubuntu eoan-proposed/main amd64 Packages
[18.0 kB]
Get:7 http://ftpmaster.internal/ubuntu eoan-proposed/main i386 Packages [12.9
kB]
...
linux-generic:amd64 is already the newest version (5.3.0.18.21).
...
utopkgtest [09:11:51]: testbed running kernel: Linux 5.3.0-18-generic
#19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019
autopkgtest [09:11:51]: testbed dpkg architecture: i386
"""
In such an environment, platform.machine() will return "x86_64", and the test
will be run, but fail:
autopkgtest [09:22:26]: test command7: python debian/tests/encode-decode.py
isa_l_rs_vand
autopkgtest [09:22:26]: test command7: [---
Traceback (most recent call last):
File "debian/tests/encode-decode.py", line 15, in
ec = ECDriver(k=3, m=3, hd=3, ec_type=sys.argv[1])
File "/usr/lib/python2.7/dist-packages/pyeclib/ec_iface.py", line 212, in
__init__
validate=int(self.validate)
File "/usr/lib/python2.7/dist-packages/pyeclib/utils.py", line 73, in
create_instance
instance = object_class(*args, **kwargs)
File "/usr/lib/python2.7/dist-packages/pyeclib/core.py", line 61, in
__init__
validate)
pyeclib.ec_iface.ECBackendInstanceNotAvailable: pyeclib_c_init ERROR: Backend
instance not found. Please inspect syslog for liberasurecode error report.
init: autopkgtest [09:22:26]: test command7: ---]
It's probably best to use "dpkg --architecture" for this check.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-pyeclib/+bug/1848237/+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 1745463] Re: Disabling systemd-resolved breaks dhclient resolvconf integration
I agree with the change @GeekSmith suggests as well. I'm running a system without network-manager, without netplan, without resolvconf. Only ifupdown and dhclient. I expect /etc/resolv.conf to be updated by the logic in /sbin/dhclient-script where it (correctly, in my system) assumes it is the only source of dns servers. I have reopened the bug. ** Changed in: systemd (Ubuntu) Status: Invalid => New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1745463 Title: Disabling systemd-resolved breaks dhclient resolvconf integration Status in resolvconf package in Ubuntu: Expired Status in systemd package in Ubuntu: New Bug description: To reproduce, mask resolved: sudo systemctl mask systemd-resolved.service ...then disable network-manager for ifupdown interfaces: $cat /etc/NetworkManager/NetworkManager.conf [main] plugins=ifupdown,keyfile dns=default rc-manager=resolvconf [ifupdown] managed=false [device] wifi.scan-rand-mac-address=no ...and reboot. You'll note that resolvconf integration with dhclient is now broken. Interfaces listed in /etc/network/interfaces or /etc/network/interfaces.d/* will not provide DNS configuration in /etc/resolv.conf and /run/resolvconf/interfaces/. This is because /etc/dhcp/dhclient-enter-hooks.d/resolvconf defines "make_resolv_conf()" as a valid function for the BOUND case, but /etc/dhcp/dhclient-enter-hooks.d/resolved undefines it (who's nasty now, eh?) even though resolved is masked. The file existence check in the beginning of /etc/dhcp/dhclient-enter- hooks.d/resolved should be more thorough, i.e. it should ensure that resolved is enabled, rather than simply look for the existence of /lib/systemd/systemd-resolved. This works for me: -if [ -x /lib/systemd/systemd-resolved ] ; then +if [ -x /lib/systemd/systemd-resolved ] && systemctl -q is-enabled systemd-resolved ; then Arguably, /etc/dhcp/dhclient-enter-hooks.d/resolvconf should implement a similar check, looking for /run/resolvconf/enable-updates as a condition for meddling with DNS settings. If desired, I'll file a separate bug for that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1745463/+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 945448] Re: add toolbar commands pane shrinks, disappears
** Bug watch added: Document Foundation Bugzilla #46924 https://bugs.documentfoundation.org/show_bug.cgi?id=46924 ** Changed in: df-libreoffice Importance: Medium => Unknown ** Changed in: df-libreoffice Status: Won't Fix => Unknown ** Changed in: df-libreoffice Remote watch: freedesktop.org Bugzilla #46924 => Document Foundation Bugzilla #46924 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+2.0 in Ubuntu. https://bugs.launchpad.net/bugs/945448 Title: add toolbar commands pane shrinks, disappears Status in LibreOffice: Unknown Status in One Hundred Papercuts: Invalid Status in gtk+2.0 package in Ubuntu: New Status in libreoffice package in Ubuntu: Incomplete Bug description: 1) lsb_release -rd Description: Ubuntu 11.10 Release: 11.10 2) apt-cache policy libreoffice-writer libreoffice-writer: Installed: 1:3.5.0-1ubuntu3~oneiric1 Candidate: 1:3.5.0-1ubuntu3~oneiric1 Version table: *** 1:3.5.0-1ubuntu3~oneiric1 0 500 http://ppa.launchpad.net/libreoffice/ppa/ubuntu/ oneiric/main i386 Packages 100 /var/lib/dpkg/status 1:3.4.4-0ubuntu1 0 500 http://in.archive.ubuntu.com/ubuntu/ oneiric-updates/main i386 Packages 1:3.4.3-3ubuntu2 0 500 http://in.archive.ubuntu.com/ubuntu/ oneiric/main i386 Packages See attached image. Steps to reproduce: 1. Go to Tools > Customise > Toolbars, and click Add. 2. Move to a toolbar that does not have enough elements to fill the pane, e.g. Data. Now back to something that has, e.g. Application. 3. Keep switching between toolbars. 4. Watch the commands pane gradually shrink and then disappear. To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/945448/+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 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
** Changed in: unity-control-center (Ubuntu) Status: Fix Released => In Progress -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: In Progress Status in unity-greeter package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned
This is likely a duplicate of https://bugs.launchpad.net/ubuntu/+source/dpkg/+bug/1828639. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mime-support in Ubuntu. https://bugs.launchpad.net/bugs/1825420 Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned Status in Ubuntu MATE: Invalid Status in bamf package in Ubuntu: Confirmed Status in dpkg package in Ubuntu: Confirmed Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Confirmed Status in mime-support package in Ubuntu: Confirmed Bug description: Steps to reproduce: 1. Have Ubuntu 18.10 installed 2. Install all updates to it 3. Switch to Main server 4. Launch update-manager 5. Confirm upgrading to 19.04 6. Wait for upgrade process to finish Expected results: * upgrade process ended without errors Actual results: * upgrade process ended with warning message: Could not install 'linux-image-5.0.0-13-generic' The upgrade will continue but the 'linux-image-5.0.0-13-generic' package may not be in a working state. Please consider submitting a bug report about it. triggers looping, abandoned Workaround: Run recommended `dpkg --configure -a` before actual reboot. System info: running VirtualBox guest with virtualbox-guest-x11 (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host. ProblemType: Package DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-13-generic 5.0.0-13.14 ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20 Uname: Linux 4.18.0-17-generic x86_64 ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mate 1542 F pulseaudio Date: Thu Apr 18 22:56:56 2019 ErrorMessage: triggers looping, abandoned InstallationDate: Installed on 2019-02-17 (60 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) IwConfig: lono wireless extensions. enp0s3no wireless extensions. Lsusb: Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: innotek GmbH VirtualBox ProcFB: 0 vboxdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1 PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1 RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2 RfKill: SourcePackage: linux StagingDrivers: vboxvideo Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) dmi.bios.date: 12/01/2006 dmi.bios.vendor: innotek GmbH dmi.bios.version: VirtualBox dmi.board.name: VirtualBox dmi.board.vendor: Oracle Corporation dmi.board.version: 1.2 dmi.chassis.type: 1 dmi.chassis.vendor: Oracle Corporation dmi.modalias: dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr: dmi.product.family: Virtual Machine dmi.product.name: VirtualBox dmi.product.version: 1.2 dmi.sys.vendor: innotek GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+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 1844422] Re: WPA3-SAE support
@Seb128 Alright, thank you for you guidance, I'll open a new bug for NM-Applet ** No longer affects: network-manager-applet (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/1844422 Title: WPA3-SAE support Status in gnome-shell package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. == Update 09-10-2019: So it has come to my attention that NetworkManager needs one additional commit backported from upstream to make WPA3-SAE work: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08 Without this latest commit connecting to WPA3-personal networks will still fail because of a lack of 802.11w support in the network-manager settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5
** Summary changed: - SRU: Update Python interpreter to 3.6.9 and 3.7.4 + SRU: Update Python interpreter to 3.6.9 and 3.7.5 ** Description changed: - Update Python interpreter to 3.6.9 and 3.7.4. As done with earlier + Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier subminor upstream releases. ** Also affects: python3-defaults (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: python3-stdlib-extensions (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: python3.6 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: python3.7 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: python3-stdlib-extensions (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: python3.6 (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: python3.7 (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: python3-defaults (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: python3-stdlib-extensions (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: python3.6 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: python3.7 (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier - subminor upstream releases. + subminor upstream releases (LP: #1822993). + + SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the + 3.6.9 release. + + python3-stdlib-extensions also updates the modules to the 3.6.9 release + for Python 3.6. + + Acceptance Criteria: The package builds, and the test suite doesn't show + regressions. The test suite passes in the autopkg tests. The new + packages don't cause regressions in a test rebuild of the main + component. + + TODO: update after test rebuild + http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html + http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html + + The test rebuilds are finished, and don't show any regressions for the + main component. + + Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. + Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python3-defaults in Ubuntu. https://bugs.launchpad.net/bugs/1835738 Title: SRU: Update Python interpreter to 3.6.9 and 3.7.5 Status in python3-defaults package in Ubuntu: New Status in python3-stdlib-extensions package in Ubuntu: New Status in python3.6 package in Ubuntu: New Status in python3.7 package in Ubuntu: New Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: New Status in python3.6 source package in Bionic: New Status in python3.7 source package in Bionic: New Status in python3-defaults source package in Disco: New Status in python3-stdlib-extensions source package in Disco: New Status in python3.6 source package in Disco: New Status in python3.7 source package in Disco: New Status in python3-defaults source package in Eoan: New Status in python3-stdlib-extensions source package in Eoan: New Status in python3.6 source package in Eoan: New Status in python3.7 source package in Eoan: New Bug description: Update Python interpreter to 3.6.9 and 3.7.5. As done with earlier subminor upstream releases (LP: #1822993). SRU: update Python 3.7 to the 3.7.5 release, update Python 3.6 to the 3.6.9 release. python3-stdlib-extensions also updates the modules to the 3.6.9 release for Python 3.6. Acceptance Criteria: The package builds, and the test suite doesn't show regressions. The test suite passes in the autopkg tests. The new packages don't cause regressions in a test rebuild of the main component. TODO: update after test rebuild http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-cosmic.html http://people.canonical.com/~doko/ftbfs-report/test-rebuild-20190404-gcc8-cosmic.html The test rebuilds are finished, and don't show any regressions for the main component. Regression Potential: Python 3.7 isn't used by default, so we don't have many default users. Regression Potential: Python 3.6 could see some regressions, although we are trying to minimize the risk by doing the test rebuild. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1835738/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net
[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon
** Changed in: unity-control-center (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-settings in Ubuntu. https://bugs.launchpad.net/bugs/1842324 Title: Port schemas from gnome-settings-daemon-common to com.canonical.unity .settings-daemon Status in indicator-session package in Ubuntu: Fix Released Status in ubuntu-settings package in Ubuntu: Fix Released Status in unity package in Ubuntu: Fix Released Status in unity-control-center package in Ubuntu: Fix Released Status in unity-greeter package in Ubuntu: Fix Released Status in unity-settings-daemon package in Ubuntu: Fix Released Bug description: Unity-settings-daemon still depends on gnome-settings-daemon schemas. It is undesired as it requires to modify code in all unity related components when upstream drops some gsettings schemas. gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an undesired way that it can't easily be reverted. Keyboard & mouse schemas are modified and unity-settings-daemon is crashing. So it's better unity uses it's own schema as suggested by Laney. We will of- course keep using settings migration (org.gnome.settings-daemon-> org.gnome.desktop) wherever possible. https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c https://gitlab.gnome.org/GNOME/gnome-settings- daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768 Since this is a huge task it can be achieved gradually. 1) Ubuntu 19.10 - Port media keys to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - u-s-d will still respects activation toggle in org.gnome.settings- daemon - everything else remains the same 2) Ubuntu 20.04 - Port rest of plugins to use com.canonical.unity.settings-daemon - u-s-d will still use org.gnome.settings-daemon name in dbus - Activation toggle key will now use com.canonical.unity.settings- daemon - Everything else will remain the same To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+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 1844422] Re: WPA3-SAE support
Ok, thanks, that's not a regression then if it was simply not working before. Better if you open a new bug report since the one described there has been fixed (WPA3 support landed and is working in Ubuntu's default desktop) -- 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/1844422 Title: WPA3-SAE support Status in gnome-shell package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: New Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. == Update 09-10-2019: So it has come to my attention that NetworkManager needs one additional commit backported from upstream to make WPA3-SAE work: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08 Without this latest commit connecting to WPA3-personal networks will still fail because of a lack of 802.11w support in the network-manager settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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 1844422] Re: WPA3-SAE support
It didn't work before, the password field being 'missing in action' is something that started when I enabled WPA3 on my AP/Router and has persisted. I think WPA3 in general doesn't fully work with NM-Applet as of yet. I am able to connect using WPA3 via via NMTUI, after which NM-Applet, for instance, shows Security as "None". -- 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/1844422 Title: WPA3-SAE support Status in gnome-shell package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: New Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. == Update 09-10-2019: So it has come to my attention that NetworkManager needs one additional commit backported from upstream to make WPA3-SAE work: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08 Without this latest commit connecting to WPA3-personal networks will still fail because of a lack of 802.11w support in the network-manager settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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 1843381] Re: Dell system takes a long time to connect network with external dock
I would like to explain the original intention of the design in the udev rule. Since it is not possible letting two NICs to have the same ifname, I tend to find a way to assign a persistent name that would not duplicate on a system for each usbnet. It is meant to break the current rule, so I was trying to reduce the number of potential victims. I found that people using NetworkManager, which identifies connections by UUID, won't be affected. Restrict the system vendor also helps to mitigate the impact. I admit unsetting the duplicated ifname does solve the original issue without regression in a real case. -- 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/1843381 Title: Dell system takes a long time to connect network with external dock Status in OEM Priority Project: New Status in systemd package in Ubuntu: New Bug description: This is a bug reopen from https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1837700 The original one caused systemd regressed. https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842651 This issue needs an alternative solution. Dell has a feature called MAC addrss passthrough[1] that would force usb ethernet adapters to be assigned with a predefined MAC address stored in BIOS or so. This feature has been landed to mainline kernel in driver r8152[2]. So whenever a r8152 managed device is plugged into Dell devices with MAC addrss passthrough enabled, this driver will set NIC MAC to a predefined one. And some Dell devices have already one built-in r8152 NIC port. On these devices, when a second r8152 NIC is plugged in, a Debian originated udev rules file 73-usb-net-by-mac.rules[3] will invoke udev built-in command `net_id` to give a persistent name, and that will be based on MAC address. However, since the system has already initialized the built-in r8152 NIC with that name, renaming the second interface with this name will always fail. While Debian still carries a patch called "Revert-udev-network-device- renaming-immediately-give.patch"[4] that tries to keep support of already deprecated "75-persistent-net-generator.rules" based interface renaming mechanism, this patch also propagated into Ubuntu[5]. This patch will retry renaming with a 90 seconds timeout when the error code is -EEXIST, so the uevent processing will always be blocked in the last ifrename step in the victim system. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: udev 237-3ubuntu10.24 [modified: lib/udev/rules.d/50-firmware.rules lib/udev/rules.d/50-udev-default.rules lib/udev/rules.d/73-special-net-names.rules lib/udev/rules.d/73-usb-net-by-mac.rules] ProcVersionSignature: Ubuntu 4.15.0-1043.48-oem 4.15.18 Uname: Linux 4.15.0-1043-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME CustomUdevRuleFiles: 70-snap.core.rules 95-oem-hotkey-osd.rules Date: Wed Jul 24 15:30:59 2019 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+beaver-jorah+X90 InstallationDate: Installed on 2019-07-03 (20 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 MachineType: Dell Inc. Latitude 7424 Rugged Extreme ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1043-oem.efi.signed root=UUID=5da90c85-3500-49a2-b989-71a604f9eec4 ro mem_sleep_default=deep quiet splash systemd.log_level=debug udev.log-priority=debug log_buf_len=8M vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0Y7FK3 dmi.board.vendor: Dell Inc. dmi.board.version: X03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd05/27/2019:svnDellInc.:pnLatitude7424RuggedExtreme:pvr:rvnDellInc.:rn0Y7FK3:rvrX03:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7424 Rugged Extreme dmi.sys.vendor: Dell Inc. [1]: https://www.dell.com/support/article/tw/zh/twdhs1/sln301147/what-is-mac-address-pass-through?lang=en [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/drivers/net/usb/r8152.c [3]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/extra/rules/73-usb-net-by-mac.rules [4]: https://salsa.debian.org/systemd-team/systemd/blob/master/debian/patches/debian/Revert-udev-network-device-renaming-immediately-give.patch [5]:
[Touch-packages] [Bug 1844422] Re: WPA3-SAE support
Did it work before? Or is that just that the new mode doesn't fully work with the applet UI (where it works in gnome-shell)? -- 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/1844422 Title: WPA3-SAE support Status in gnome-shell package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: New Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. == Update 09-10-2019: So it has come to my attention that NetworkManager needs one additional commit backported from upstream to make WPA3-SAE work: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08 Without this latest commit connecting to WPA3-personal networks will still fail because of a lack of 802.11w support in the network-manager settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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 1631161] Re: Preferred output device is not remembered between logins
It is not HDMI specific. I have a similar problem: every start up, output is selected on (usb) headphones, but actual audio comes out my motherboard line out. Volume control adjusts headphones, so apparently has no effect. I have to go change it to line out, then the volume control works. Should I create yet another duplicate? Or can someone familiar suggest the right bug to follow? Thanks. -- 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/1631161 Title: Preferred output device is not remembered between logins Status in pulseaudio package in Ubuntu: Confirmed Bug description: Whenever I reboot anew, pulseaudio has forgotten the correct audio port which I have set using the kde pulseaudio tool. I use line out, but it defaults to headphones, which is incorrect for my current setup. I expect it to remember that I wanted line out every time. Once selected, everything runs fine for that session, but it doesn't get saved and defaults back to the wrong output every time. Guessing this is pulseaudio as it happens with the gnome tool also. Tested not working in 16.04, 16.10 and Mint 18 (packages from 16.04). Policy installed: 1:8.0-0ubuntu3 Cheers --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: kvd1577 F...m pulseaudio /dev/snd/pcmC0D0p: kvd1577 F...m pulseaudio /dev/snd/controlC0: kvd1577 F pulseaudio CurrentDesktop: KDE DistroRelease: Linux 18 InstallationDate: Installed on 2016-10-02 (5 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160904 NonfreeKernelModules: nvidia_uvm nvidia Package: pulseaudio 1:8.0-0ubuntu3 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Tags: sarah third-party-packages Uname: Linux 4.4.0-38-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/24/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5f dmi.board.name: GA-770T-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5f:bd09/24/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-770T-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770T-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-770T-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1631161/+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 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss
Like several of the most recent posters above I've had a 9360 for a couple of years without any hiss problems. A few days ago I started getting a pretty bad hiss thru headphones. Tried various headphones - all have bad hiss. All are ok on other devices. Running 19.04. Something has changed. -- 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/1654448 Title: Dell XPS 13 9350/9360 headphone audio hiss Status in Dell Sputnik: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Won't Fix Status in pulseaudio package in Ubuntu: Confirmed Bug description: Pertaining to 16.04 on a dell XPS 13 9360 ii alsa-base 1.0.25+dfsg-0ubuntu5 Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic. When headphones are plugged in, there is a clearly audible hiss (white noise). This is present as soon as the headphones are plugged in, whether 'headphones' or 'headset' are selected from the pop-up box. Using alsamixer to debug the issue reveals that it is related to "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If this is changed to: 10.00, 10.00 (one notch up) the hiss disappears. 20.00, 20.00 cause a louder hiss and 30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. When the headphones are removed and plugged back in the Headphone Mic Boost setting returns to dB gain 0 and the problem also returns. This (problem and workaround) has been reported in the wild: https://news.ycombinator.com/item?id=13050843 and https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/ for example To manage notifications about this bug go to: https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+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 1631161] Re: Preferred output device is not remembered between logins
Discussed during the meeting, it's not a new issue and while it would be nice to see things improved that doesn't qualify as a release issue ** Tags removed: rls-ee-incoming ** Tags added: rls-ee-notfixing -- 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/1631161 Title: Preferred output device is not remembered between logins Status in pulseaudio package in Ubuntu: Confirmed Bug description: Whenever I reboot anew, pulseaudio has forgotten the correct audio port which I have set using the kde pulseaudio tool. I use line out, but it defaults to headphones, which is incorrect for my current setup. I expect it to remember that I wanted line out every time. Once selected, everything runs fine for that session, but it doesn't get saved and defaults back to the wrong output every time. Guessing this is pulseaudio as it happens with the gnome tool also. Tested not working in 16.04, 16.10 and Mint 18 (packages from 16.04). Policy installed: 1:8.0-0ubuntu3 Cheers --- ApportVersion: 2.20.1-0ubuntu2.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: kvd1577 F...m pulseaudio /dev/snd/pcmC0D0p: kvd1577 F...m pulseaudio /dev/snd/controlC0: kvd1577 F pulseaudio CurrentDesktop: KDE DistroRelease: Linux 18 InstallationDate: Installed on 2016-10-02 (5 days ago) InstallationMedia: Linux Mint 18 "Sarah" - Release amd64 20160904 NonfreeKernelModules: nvidia_uvm nvidia Package: pulseaudio 1:8.0-0ubuntu3 [origin: Ubuntu] PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 4.4.0-38.57-generic 4.4.19 Tags: sarah third-party-packages Uname: Linux 4.4.0-38-generic x86_64 UnreportableReason: This is not an official Linux package. Please remove any third party package and try again. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/24/2013 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5f dmi.board.name: GA-770T-USB3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5f:bd09/24/2013:svnGigabyteTechnologyCo.,Ltd.:pnGA-770T-USB3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-770T-USB3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-770T-USB3 dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1631161/+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
Daniel, could you keep an eye on this one and see if we can help upstream to fix it? ** Also affects: pulseaudio (Ubuntu Eoan) Importance: Medium Status: Triaged ** Changed in: pulseaudio (Ubuntu Eoan) Assignee: (unassigned) => Daniel van Vugt (vanvugt) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Eoan: Triaged Bug description: 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. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. 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
@Daniel, however, this creates "interesting" issues, like when you have a pulseaudio server on the network. Even if your laptop is connected before the user session, it will always switch to the server, even if you reverted on this decision at previous reboot. However what I describe above isn't a regression (contrary to this report). -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1847570 Title: PulseAudio automatically switches to HDMI sound output on login Status in PulseAudio: New Status in pulseaudio package in Ubuntu: Triaged Status in pulseaudio source package in Eoan: Triaged Bug description: 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. I would be good if it would remember this choice so that I have to do it only once. Or maybe (if that is technically possible) just output on both output devices by default - this would be even more user friendly for newbies who will have a hard time finding the right place to change this (or maybe have UI in the volume slider to select outputs if there are more than one? But anyway, my immediate concern is that it should just remember my choice :) Please let me know if I can provide more information. Happy to dig into code if needed but I will need some pointers. 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 1848202] Re: Use after free in gdbus leads to eds segfaults
** Changed in: glib Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1848202 Title: Use after free in gdbus leads to eds segfaults Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+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 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
** Tags removed: rls-ee-incoming ** Tags added: rls-ee-notfixing rls-ff-incoming -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mawk in Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` Status in bash-completion package in Ubuntu: Triaged Status in gawk package in Ubuntu: Invalid Status in mawk package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in Debian: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+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 1848202] Re: Use after free in gdbus leads to eds segfaults
glib 2.62 backport pending https://gitlab.gnome.org/GNOME/glib/merge_requests/1162 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1848202 Title: Use after free in gdbus leads to eds segfaults Status in GLib: Unknown Status in glib2.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+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 1848202] Re: Use after free in gdbus leads to eds segfaults
Upstream https://gitlab.gnome.org/GNOME/glib/issues/1896 ** Summary changed: - /usr/libexec/evolution-calendar-factory:11:malloc:pvl_newlist:icalcomponent_new_impl:icalcomponent_new:i_cal_component_new + Use after free in gdbus leads to eds segfaults ** Bug watch added: gitlab.gnome.org/GNOME/glib/issues #1896 https://gitlab.gnome.org/GNOME/glib/issues/1896 ** Package changed: evolution-data-server (Ubuntu) => glib2.0 (Ubuntu) ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => High ** Also affects: glib via https://gitlab.gnome.org/GNOME/glib/issues/1896 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1848202 Title: Use after free in gdbus leads to eds segfaults Status in GLib: Unknown Status in glib2.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+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 1848202] [NEW] Use after free in gdbus leads to eds segfaults
Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. ** Affects: glib Importance: Unknown Status: Unknown ** Affects: glib2.0 (Ubuntu) Importance: High Status: New ** Tags: eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1848202 Title: Use after free in gdbus leads to eds segfaults Status in GLib: Unknown Status in glib2.0 package in Ubuntu: New Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding evolution-data-server. This problem was most recently seen with package version 3.34.1-1, the problem page at https://errors.ubuntu.com/problem/b1f62616406e36e521fd1fb1d2be4ac2fe9a2cda contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1848202/+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 1848200] [NEW] gdb not stopping on breakpoint in a 32-bit program
Public bug reported:
After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not
stop on breakpoint when running a 32-bit application (on 64-bit Ubuntu).
This can be reproduced with a simple “hello world” program:
$ cat hello.c
#include
int main()
{
// printf() displays the string inside quotation
printf("Hello, World!");
return 0;
}
$ gcc -ggdb -m32 hello.c
$ gdb a.out
(gdb) b hello.c:5
Breakpoint 1 at 0x536: file hello.c, line 5.
(gdb) run
Starting program: /home/user/sandbox/a.out
warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.
--- (and not stopping nor outputting the text…) ---
It works well with a 64-bit build (leaving out the gcc’s -m32 option).
This problem has been already discussed on:
https://stackoverflow.com/questions/58225562/how-to-fix-hang-in-gdb-in-
ld-linux-so-2-when-running-a-32-bit-executable-on-a-64
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdb 8.1-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
Uname: Linux 4.15.0-65-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 15 14:37:37 2019
InstallationDate: Installed on 2015-12-08 (1407 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64
(20150805)
SourcePackage: gdb
UpgradeStatus: Upgraded to bionic on 2019-06-10 (127 days ago)
** Affects: gdb (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug bionic
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1848200
Title:
gdb not stopping on breakpoint in a 32-bit program
Status in gdb package in Ubuntu:
New
Bug description:
After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not
stop on breakpoint when running a 32-bit application (on 64-bit
Ubuntu). This can be reproduced with a simple “hello world” program:
$ cat hello.c
#include
int main()
{
// printf() displays the string inside quotation
printf("Hello, World!");
return 0;
}
$ gcc -ggdb -m32 hello.c
$ gdb a.out
(gdb) b hello.c:5
Breakpoint 1 at 0x536: file hello.c, line 5.
(gdb) run
Starting program: /home/user/sandbox/a.out
warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.
--- (and not stopping nor outputting the text…) ---
It works well with a 64-bit build (leaving out the gcc’s -m32 option).
This problem has been already discussed on:
https://stackoverflow.com/questions/58225562/how-to-fix-hang-in-gdb-
in-ld-linux-so-2-when-running-a-32-bit-executable-on-a-64
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gdb 8.1-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
Uname: Linux 4.15.0-65-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: XFCE
Date: Tue Oct 15 14:37:37 2019
InstallationDate: Installed on 2015-12-08 (1407 days ago)
InstallationMedia: Ubuntu-Server 14.04.3 LTS "Trusty Tahr" - Beta amd64
(20150805)
SourcePackage: gdb
UpgradeStatus: Upgraded to bionic on 2019-06-10 (127 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1848200/+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 1847896] Re: Unable to shutdown or restart from log-in screen
** Tags added: id-5da4c44b2f3bee7a637eb2b0 -- 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/1847896 Title: Unable to shutdown or restart from log-in screen Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: When selecting the shutdown icon from the log-in screen you are prompted with a dialog that allows you to either cancel, restart or shutdown. It has been noted that the restart and shutdown options no longer work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 13 09:08:23 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (148 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1647333] Re: adduser misses extrausers support for group management
*** This bug is a duplicate of bug 1840375 *** https://bugs.launchpad.net/bugs/1840375 Hmm, this feels like a duplicate of 1840375 ** Project changed: snappy => snapd ** This bug has been marked a duplicate of bug 1840375 groupdel doesn't support extrausers -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to shadow in Ubuntu. https://bugs.launchpad.net/bugs/1647333 Title: adduser misses extrausers support for group management Status in snapd: New Status in adduser package in Ubuntu: Confirmed Status in shadow package in Ubuntu: In Progress Bug description: trying to add a user to a group in /var/lib/extrausers by using the --extrausers option results in a "group not found" error despite adduser being supposed to be able to do this kind of modification. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1647333/+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 1840375] Re: groupdel doesn't support extrausers
NOTE: I just had a look at snapd code and we still have a reference to
this bug.
// TODO: groupdel doesn't currently support --extrausers, so
// don't try to clean up when it is specified (LP: #1840375)
I'm keeping the snapd task open
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to shadow in Ubuntu.
https://bugs.launchpad.net/bugs/1840375
Title:
groupdel doesn't support extrausers
Status in snapd:
Triaged
Status in shadow package in Ubuntu:
Fix Released
Status in shadow source package in Xenial:
Fix Committed
Status in shadow source package in Bionic:
Fix Committed
Status in shadow source package in Disco:
Fix Committed
Bug description:
snapd needs the ability to call 'groupdel --extrausers foo' to clean
up after itself, but --extrausers is currently unsupported.
[Impact]
On ubuntu-core systems we want to be able to manage "extrausers" in the same
way as regular users. This requires updates to the various
{user,group}{add,del} tools. Right now "groupdel" cannot handle extrausers.
This is an important feature for Ubuntu Core
[Test Case]
1. install the libnss-extrausers and configure it
2. run "groupadd --extrausers foo"
3 check /var/lib/extrausers/group for the new "foo" group
4. run "groupdel --extrausers foo"
5. check /var/lib/extrausers/group and ensure the "foo" group is removed
[Regression Potential]
* low: this adds a new (optional) option which is off by default
To manage notifications about this bug go to:
https://bugs.launchpad.net/snapd/+bug/1840375/+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 1842437] Re: Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem with udev
** Tags removed: sts-sponsor-slashd -- 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/1842437 Title: Xenial: libblkid: fix false-positive/misdetection of nilfs2 filesystem with udev Status in util-linux package in Ubuntu: Fix Released Status in util-linux source package in Xenial: Fix Committed Bug description: [Impact] * Users / systemd can fail to mount a filesystem by UUID (e.g., during boot, triggering emergency shell prompt) if the magic bytes for the nilfs filesystem are written to the right place in a partition of another filesystem, (for whatever reason or coincidence). * Note this can happen after the filesystem/mount is working correctly, so a change of behavior/problem can potentially be noticed when trying to mount the filesystem again, which can very well be the next time the system boots. * This happens because if udev blkid detects more than one filesystem, it does not print the UUID env vars required to create the /dev/disk/by-id symlinks and other things. * The fix enhances the check for valid nilfs superblock by specifically checking a value read from disk to be valid/ within a value range, which addresses this one occurrence and prevents a lot more. [Test Case] * Synthetic test case written for this problem on comment #6. [Regression Potential] * Low. The code is contained in the probe for the nilfs filesystem. * This just makes it be more restrictive about the possibly valid values for a few bytes read from disk (that now need to be within the acceptable range of valid values) so this only decreases false- positives, and cannot increase false-negatives of valid filesystems. [Original Description] The nilfs filesystem has a backup superblock at the end of the device. If the magic number is coincidentally found at the right position and the filesystem is on a partition/not-wholedisk device, the only check left is for checksum verification, which is explicitly ignored in 'udev built-in blkid'. This causes blkid to detect one actually valid filesystem with a superblock at the beginning of the device (e.g., ext4), and then an invalid nilfs2 filesystem due to a coincidental magic number at the end of the device. And this causes blkid to break out of the safeprobe routine (which expects a single filesystem to be detected), and not print the UUIDs, thus not creating /dev/disk/by-uuid/ links which prevent mounting the partition by-uuid at boot time, causing emergency shell/boot failures. This upstream fix resolved the problem by introducing a check for the 'bytes' paramenters in the superblock, which is read from disk, and turns out to have an out-of-range value. - 'liblkid: Add length check in probe_nilfs2 before crc32' https://git.kernel.org/pub/scm/utils/util-linux/util-linux.git/commit/?id=ac681a310c32319423297544833932f4d689a7a2 $ git describe --contains ac681a310c32319423297544833932f4d689a7a2 v2.29-rc1~172 Xenial, which is v2.27.1-based, is the only release that needs it. Bionic is v2.31.1, so all post-Xenial supported releases have it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1842437/+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 1845529] Re: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/`
** Summary changed: - bash completion in 19.10 shows `awk: line 18: function gensub never defined` on ``umount /dev/` + bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mawk in Ubuntu. https://bugs.launchpad.net/bugs/1845529 Title: bash completion shows `awk: line 18: function gensub never defined` on `umount /dev/` Status in bash-completion package in Ubuntu: Triaged Status in gawk package in Ubuntu: Invalid Status in mawk package in Ubuntu: Invalid Status in ubuntu-meta package in Ubuntu: Invalid Status in Debian: Confirmed Bug description: Steps to reproduce: 1. Install Ubuntu MATE 19.10 using minimal desktop option 2. Open terminal and enter `umount /dev/s` and then hit Expected result: * bash completion works as expected Actual results: * bash completion does not work : $ umount /dev/awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined $ umount /meawk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined awk: line 18: function gensub never defined ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bash-completion 1:2.9-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8 Uname: Linux 5.3.0-10-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Thu Sep 26 18:46:59 2019 Dependencies: InstallationDate: Installed on 2019-09-26 (0 days ago) InstallationMedia: Ubuntu-MATE 19.10 "Eoan Ermine" - Beta amd64 (20190926.1) PackageArchitecture: all SourcePackage: bash-completion UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bash-completion/+bug/1845529/+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 1848180] [NEW] LVM initrd fails to activate btrfs multidevice root
Public bug reported: I have two lvm volumes (/dev/mapper/raid-btrfs and /dev/mapper/fast- btrfs) in two different volume groups. I have created a btrfs (raid1) filesystem on top of them and that's my root filesystem. If i define it by UUID in the root= kernel argument, i just hit bug #1574333. Forcing my root to "/dev/mapper/fast-btrfs" by defining GRUB_DEVICE in /etc/default/grub works around that bug. The problem now is that initrd is only activating the device given as root= argument, leaving the other inactive; consequently the btrfs mount fails to find its second device and the system fails to boot giving up at initramfs prompt. Manually adding a line to activate also 2nd device at the bottom of /usr/share/initramfs-tools/scripts/local-top/lvm2 and rebuilding the initramfs works around this issue too, but i suppose my mods will be washed away by next package upgrade. Here is the result: > activate "$ROOT" > activate "$resume" > activate "/dev/mapper/raid-btrfs" Proposed solution: I understand this is an uncommon setup and correctly handling multidevice LVM roots is complicated, please just add a configuration option to manually define/append the list of volume groups to be activated at initrd time. ** Affects: lvm2 (Ubuntu) Importance: Undecided Status: New ** Description changed: I have two lvm volumes (/dev/mapper/raid-btrfs and /dev/mapper/fast- btrfs) in two different volume groups. I have created a btrfs (raid1) filesystem on top of them and that's my root filesystem. - If i define it bu UUID in the root= kernel argument, i just hit bug + If i define it by UUID in the root= kernel argument, i just hit bug #1574333. Forcing my root to "/dev/mapper/fast-btrfs" by defining GRUB_DEVICE in /etc/default/grub works around that bug. The problem now is that initrd is only activating the device given as root= argument, leaving the other inactive; consequently the btrfs mount fails to find its second device and the system fails to boot giving up at initramfs prompt. Manually adding a line to activate also 2nd device at the bottom of /usr/share/initramfs-tools/scripts/local-top/lvm2 and rebuilding the initramfs works around this issue too, but i suppose my mods will be washed away by next package upgrade. Here is the result: > activate "$ROOT" > activate "$resume" > activate "/dev/mapper/raid-btrfs" Proposed solution: I understand this is an uncommon setup and correctly handling multidevice LVM roots is complicated, please just add a configuration option to manually define/append the list of volume groups to be activated at initrd time. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lvm2 in Ubuntu. https://bugs.launchpad.net/bugs/1848180 Title: LVM initrd fails to activate btrfs multidevice root Status in lvm2 package in Ubuntu: New Bug description: I have two lvm volumes (/dev/mapper/raid-btrfs and /dev/mapper/fast- btrfs) in two different volume groups. I have created a btrfs (raid1) filesystem on top of them and that's my root filesystem. If i define it by UUID in the root= kernel argument, i just hit bug #1574333. Forcing my root to "/dev/mapper/fast-btrfs" by defining GRUB_DEVICE in /etc/default/grub works around that bug. The problem now is that initrd is only activating the device given as root= argument, leaving the other inactive; consequently the btrfs mount fails to find its second device and the system fails to boot giving up at initramfs prompt. Manually adding a line to activate also 2nd device at the bottom of /usr/share/initramfs-tools/scripts/local-top/lvm2 and rebuilding the initramfs works around this issue too, but i suppose my mods will be washed away by next package upgrade. Here is the result: > activate "$ROOT" > activate "$resume" > activate "/dev/mapper/raid-btrfs" Proposed solution: I understand this is an uncommon setup and correctly handling multidevice LVM roots is complicated, please just add a configuration option to manually define/append the list of volume groups to be activated at initrd time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1848180/+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 1831736] Re: [MIR] lz4 by default
** Branch linked: lp:~xnox/ubuntu-release-upgrader/eoan-kernel-sizes -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831736 Title: [MIR] lz4 by default Status in Release Upgrader: New Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in partman-auto package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) I booted grub2 and measured loading largish amount of files, ie. $ date; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; date To get a rough speed between 30 and 44 MB/s of loading these files off ext4 on nvme. With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o penalty is 0.18s whilst I gain over a second in faster decompression time. Overall a win. xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining 2.4s of decompression time, meaning overall worse than gzip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1831736/+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 1831736] Re: [MIR] lz4 by default
** Also affects: ubuntu-release-upgrader Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831736 Title: [MIR] lz4 by default Status in Release Upgrader: New Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in partman-auto package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) I booted grub2 and measured loading largish amount of files, ie. $ date; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; date To get a rough speed between 30 and 44 MB/s of loading these files off ext4 on nvme. With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o penalty is 0.18s whilst I gain over a second in faster decompression time. Overall a win. xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining 2.4s of decompression time, meaning overall worse than gzip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1831736/+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 1831736] Re: [MIR] lz4 by default
However 298.1MB is larger than old installs. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831736 Title: [MIR] lz4 by default Status in Release Upgrader: New Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in partman-auto package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) I booted grub2 and measured loading largish amount of files, ie. $ date; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; date To get a rough speed between 30 and 44 MB/s of loading these files off ext4 on nvme. With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o penalty is 0.18s whilst I gain over a second in faster decompression time. Overall a win. xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining 2.4s of decompression time, meaning overall worse than gzip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-upgrader/+bug/1831736/+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 1831736] Re: [MIR] lz4 by default
Sizing: $ sudo du -sh /boot/* | grep -e grub -e 5.3.0-18 231K/boot/config-5.3.0-18-generic 8.0M/boot/grub 81M /boot/initrd.img-5.3.0-18-generic 4.5M/boot/System.map-5.3.0-18-generic 11M /boot/vmlinuz-5.3.0-18-generic This is desktop system, amd64, with all microcodes, and linux-firmware, and signed grub. For three kernels that brings my system to (11+81+4.5+0.2)*3+8 = 298.1 MB Which is still within reasonable /boot sizing and need not to be bumped. However, there are potential disk space saving that could be made: * on securebooted systems /boot/grub contains 8MB of modules that cannot be loaded at runtime * config is informational only, and is not strictly needed at boot * System.map is not strictly needed for boot Which could save (4.5+0.2)*3+8=22.1 MB Subiquity creates /boot at 1GB. Ubiquity/partman-auto aims for (512 1024 768) All are still reasonable for up to 10 kernel versions. ** Changed in: partman-auto (Ubuntu) Status: Triaged => Invalid ** Changed in: ubuntu-release-upgrader (Ubuntu) Status: Triaged => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831736 Title: [MIR] lz4 by default Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in partman-auto package in Ubuntu: Invalid Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) I booted grub2 and measured loading largish amount of files, ie. $ date; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; date To get a rough speed between 30 and 44 MB/s of loading these files off ext4 on nvme. With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o penalty is 0.18s whilst I gain over a second in faster decompression time. Overall a win. xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining 2.4s of decompression time, meaning overall worse than gzip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831736/+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 1640180] Re: gnome-todo doesn't load CalDav task list from EDS
gnome-todo 3.28.1 - same problem. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1640180 Title: gnome-todo doesn't load CalDav task list from EDS Status in GNOME To Do: Confirmed Status in Ubuntu GNOME: New Status in evolution-data-server package in Ubuntu: Confirmed Status in gnome-todo package in Ubuntu: Triaged Bug description: Since the upgrade to Yakkety Gnome-TODO doesn't show my remote CalDav task list that were set through evolution. The list are still available in working in Evolution. I tried to set them up again but they didn't appear. I tried upgrading to version available in various gnome3-ppa (still 3.20.* though) and it didn't help. The bug seems to have been handled in Fedora : https://bugzilla.redhat.com/show_bug.cgi?format=multiple=1363848 and https://bodhi.fedoraproject.org/updates/FEDORA-2016-db729be3e1 (I found those while searching the web for a solution). To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-todo/+bug/1640180/+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 1831736] Re: [MIR] lz4 by default
Linux kernel compression was changed to lz4 with bugs https://bugs.launchpad.net/bugs/1840934 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to initramfs-tools in Ubuntu. https://bugs.launchpad.net/bugs/1831736 Title: [MIR] lz4 by default Status in initramfs-tools package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in live-build package in Ubuntu: Fix Released Status in livecd-rootfs package in Ubuntu: Fix Released Status in lz4 package in Ubuntu: Fix Released Status in partman-auto package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: Use `lz4 -9 -l` compression for initramfs by default as discussed on ubuntu-devel. This would also pull the lz4 package into main https://lists.ubuntu.com/archives/ubuntu-devel/2019-June/040726.html [Regression Potential] We are trying to optimize for total boot speed, but performing a micro-optimization upon time to create/unpack kernel/initrd is an insufficient benchmark for total boot speed. This is because it ignores time to load the kernel/initrd, and whether the firmware/bootloader were able to stream decompress it whilst loading it. I.e. it is argued that in the real world, subsecond decompression gains are irrelevant if UEFI firmware, tftp boot, etc. take a lot longer than that to read extra 10s of MBs of boot material. [TODO] Measure pure i/o load speed with stopwatch, to figure out MB/s speed of loading initrds/kernel off FAT32, EXT4, TFTP, HTTP. Re-evaluate if we should provide different compression mechanisms: - ie. gzip instead of lz4 for most cases (revert) - ie. xz for painful i/o cases (e.g. netboot) I booted grub2 and measured loading largish amount of files, ie. $ date; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; initrd (hd0,gpt5)/initrd.img; date To get a rough speed between 30 and 44 MB/s of loading these files off ext4 on nvme. With lz4 initrd taking 67M, and gzip initrd taking 59M, the grub i/o penalty is 0.18s whilst I gain over a second in faster decompression time. Overall a win. xz initrd is 36M meaning saving e.g. 0.8s of i/o time whilst gaining 2.4s of decompression time, meaning overall worse than gzip. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1831736/+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 1279060] Re: MIssing voicemail info for French provider Free
** Changed in: mobile-broadband-provider-info (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mobile-broadband-provider- info in Ubuntu. https://bugs.launchpad.net/bugs/1279060 Title: MIssing voicemail info for French provider Free Status in mobile-broadband-provider-info package in Ubuntu: Incomplete Bug description: I'm not sure if I just need to add 666 in the xml or if there are some wizardries to do, so I just open a bug for now. Provider is Free Mobile, country is France, and voicemail number is 666. Thanks :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mobile-broadband-provider-info/+bug/1279060/+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 1848070] Re: [System Product Name, Realtek Generic, Green Headphone Out, Front] fails after a while
It seems to work (running for 4 hours and no issue). -- 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/1848070 Title: [System Product Name, Realtek Generic, Green Headphone Out, Front] fails after a while Status in alsa-driver package in Ubuntu: New Bug description: After a while (after rebooting my computer), my sound output gets distorted. When listening to music containing voice, it sounds like voice is removed. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jul2408 F pulseaudio /dev/snd/controlC1: jul2408 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 14 18:37:11 2019 InstallationDate: Installed on 2019-04-04 (192 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Green Headphone Out, Front Symptom_PulseAudioLog: oct. 14 16:04:20 narwhal dbus-daemon[720]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.32' (uid=121 pid=1456 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined") Symptom_Type: Sound works for a while, then breaks Title: [System Product Name, Realtek Generic, Green Headphone Out, Front] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/07/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1002 dmi.board.asset.tag: Default string dmi.board.name: TUF Z390-PRO GAMING dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1002:bd11/07/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFZ390-PROGAMING:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: ASUS_MB_CNL dmi.product.version: System Version dmi.sys.vendor: System manufacturer modified.conffile..etc.modprobe.d.alsa-base.conf: [modified] mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-10-14T16:03:44.015994 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1848070/+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 1847896] Re: Unable to shutdown or restart from log-in screen
I've tested it as well (saw you asking yesterday and kicked a build but I didn't see you tested as well meanwhile), I can confirm it fixes the issue -- 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/1847896 Title: Unable to shutdown or restart from log-in screen Status in gnome-shell package in Ubuntu: Invalid Status in systemd package in Ubuntu: Triaged Bug description: When selecting the shutdown icon from the log-in screen you are prompted with a dialog that allows you to either cancel, restart or shutdown. It has been noted that the restart and shutdown options no longer work. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1-1ubuntu1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Sun Oct 13 09:08:23 2019 DisplayManager: gdm3 InstallationDate: Installed on 2019-05-17 (148 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190517) RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1847896/+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 1847980] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: disco -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1847980 Title: Lightdm is just a black screen when booting kernel 5.3.0-17-generic on an i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in xorg-server package in Ubuntu: New Bug description: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux-image-5.3.0-17 after upgraded to the development release Ubuntu Eoan Ermine (development branch). If i boot with linux-image-5.0.0-31-generic the Xorg works well. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 14 11:15:23 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.42 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.36 dmi.chassis.asset.tag: CZC64082W1 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: X3J10ET#ABZ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro nomodeset resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Tags: eoan ubuntu Uname: Linux 5.3.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/19/2019 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.42 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.36
[Touch-packages] [Bug 1847980] Re: [i915] Black screen when booting kernel 5.3.0-17-generic on an i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it
Oops, I missed the part where you said that booting works. Only the login screen is missing: Every time i boot with kernel 5.3 I can see the services loaded (I disable splash screen), the screen is black when requiring the user credentials. ** Package changed: xorg-server (Ubuntu) => lightdm (Ubuntu) ** Summary changed: - [i915] Black screen when booting kernel 5.3.0-17-generic on an i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it + Lightdm is just a black screen when booting kernel 5.3.0-17-generic on an i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it ** Also affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1847980 Title: Lightdm is just a black screen when booting kernel 5.3.0-17-generic on an i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it Status in lightdm package in Ubuntu: New Status in linux package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux-image-5.3.0-17 after upgraded to the development release Ubuntu Eoan Ermine (development branch). If i boot with linux-image-5.0.0-31-generic the Xorg works well. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 14 11:15:23 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.42 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.36 dmi.chassis.asset.tag: CZC64082W1 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: X3J10ET#ABZ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic
[Touch-packages] [Bug 1847980] [NEW] [i915] Black screen when booting kernel 5.3.0-17-generic on an i5-6500, but "nomodeset" or booting kernel 5.0.0 fixes it
You have been subscribed to a public bug: Xorg freeze at boot on Intel Corporation HD Graphics 530 with linux-image-5.3.0-17 after upgraded to the development release Ubuntu Eoan Ermine (development branch). If i boot with linux-image-5.0.0-31-generic the Xorg works well. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-31.33-generic 5.0.21 Uname: Linux 5.0.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE Date: Mon Oct 14 11:15:23 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GpuHangFrequency: Continuously GpuHangReproducibility: Yes, I can easily reproduce it GpuHangStarted: Immediately after installing this version of Ubuntu GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-31-generic root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/19/2019 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.42 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.36 dmi.chassis.asset.tag: CZC64082W1 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: X3J10ET#ABZ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: XFCE DistUpgraded: Fresh install DistroCodename: eoan DistroRelease: Ubuntu 19.10 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company HD Graphics 530 [103c:8054] Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 047d:2048 Kensington Orbit Trackball with Scroll Ring Bus 001 Device 002: ID 04d9:a0cd Holtek Semiconductor, Inc. USB Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP EliteDesk 800 G2 SFF Package: xorg-server (not installed) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-17-generic root=UUID=714cc192-0d1c-4899-b891-16e6e504c662 ro nomodeset resume=UUID=316a3e2d-ef98-4c31-8ba1-52e1cd0e8c05 ProcVersionSignature: Ubuntu 5.3.0-17.18-generic 5.3.1 Tags: eoan ubuntu Uname: Linux 5.3.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/19/2019 dmi.bios.vendor: HP dmi.bios.version: N01 Ver. 02.42 dmi.board.name: 8054 dmi.board.vendor: HP dmi.board.version: KBC Version 05.36 dmi.chassis.asset.tag: CZC64082W1 dmi.chassis.type: 4 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrN01Ver.02.42:bd08/19/2019:svnHP:pnHPEliteDesk800G2SFF:pvr:rvnHP:rn8054:rvrKBCVersion05.36:cvnHP:ct4:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP EliteDesk 800 G2 SFF dmi.product.sku: X3J10ET#ABZ dmi.sys.vendor: HP version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
[Touch-packages] [Bug 1844422] Re: WPA3-SAE support
So there's a bit more work to this than i stated yesterday: https://gitlab.gnome.org/GNOME/network-manager-applet/commits/master?utf8=%E2%9C%93=sae -- 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/1844422 Title: WPA3-SAE support Status in gnome-shell package in Ubuntu: Fix Released Status in network-manager package in Ubuntu: Fix Released Status in network-manager-applet package in Ubuntu: New Bug description: After some user feedback WPA3 support for NetworkManager has been finalized upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e1608030c6614d8dfd86122e9df81fdaad9453c9 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/84a86ce55f1e70cb32217d2c74242ff848db8cd7 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/merge_requests/276/diffs?commit_id=8d4497088fff562773b9c05260e810833bfc9c85 At this time NetworkManager will not associate with Wifi-networks using WPA3. Tested using Ubuntu Ubuntu Eoan Ermine [development branch] with NetworkManager 1.20.2-1ubuntu1 and WPA_Supplicant 2:2.9-1ubuntu1. It would be great if the aforementioned commits where backported to Eoan before release, so that Eoan based systems will associate with WiFi-networks using WPA3. == Update 09-10-2019: So it has come to my attention that NetworkManager needs one additional commit backported from upstream to make WPA3-SAE work: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/commit/e36c297fd8c6b1b57cd120739cc5ee8eab57aa08 Without this latest commit connecting to WPA3-personal networks will still fail because of a lack of 802.11w support in the network-manager settings. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1844422/+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 1847967] Re: oem kernel packages treated differently from generic kernel ones
** Changed in: oem-priority Importance: Undecided => High -- 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/1847967 Title: oem kernel packages treated differently from generic kernel ones Status in OEM Priority Project: New Status in apport package in Ubuntu: New Bug description: When `apport-bug linux` was executed on systems with linux-oem, linux- oem-osp1 kernels, many details are not included as generic linux kernel does. Alsa info, dmesg, lspci, lsusb, DMI, etc. are missing. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1847967/+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 1845617] Re: Bluetooth service stop working
** Package changed: linux (Ubuntu) => bluez (Ubuntu) -- 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/1845617 Title: Bluetooth service stop working Status in bluez package in Ubuntu: Incomplete Bug description: lsb_release -rd command Description: Ubuntu 19.04 Release: 19.04 ++ apt-cache policy bluetooth command bluetooth: Installato: 5.50-0ubuntu2 Candidato: 5.50-0ubuntu2 Tabella versione: *** 5.50-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu disco/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu disco/universe i386 Packages 100 /var/lib/dpkg/status ++ sudo service bluetooth status command bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: deactivating (final-sigterm) (Result: exit-code) since Fri 2019-09-27 10:44:37 CEST; 20min ago Docs: man:bluetoothd(8) Process: 3897 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=1/FAILURE) Main PID: 3897 (code=exited, status=1/FAILURE) Status: "Starting up" Tasks: 1 (limit: 4915) Memory: 3.9M CGroup: /system.slice/bluetooth.service └─1156 /usr/lib/bluetooth/bluetoothd set 27 11:00:53 hostname systemd[1]: Starting Bluetooth service... set 27 11:00:53 hostname bluetoothd[3897]: Bluetooth daemon 5.50 set 27 11:00:53 hostname bluetoothd[3897]: D-Bus setup failed: Name already in use set 27 11:00:53 hostname bluetoothd[3897]: Unable to get on D-Bus set 27 11:00:53 hostname systemd[1]: bluetooth.service: Main process exited, code=exited, status=1/FAILURE set 27 11:02:24 hostname systemd[1]: bluetooth.service: State 'stop-sigterm' timed out. Killing. set 27 11:02:24 hostname systemd[1]: bluetooth.service: Killing process 1156 (bluetoothd) with signal SIGKILL. set 27 11:03:54 hostname systemd[1]: bluetooth.service: Processes still around after SIGKILL. Ignoring. ++ cat /proc/version_signature command Ubuntu 5.0.0-29.31-generic 5.0.21 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1845617/+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 1845617] [NEW] Bluetooth service stop working
You have been subscribed to a public bug: lsb_release -rd command Description:Ubuntu 19.04 Release:19.04 ++ apt-cache policy bluetooth command bluetooth: Installato: 5.50-0ubuntu2 Candidato: 5.50-0ubuntu2 Tabella versione: *** 5.50-0ubuntu2 500 500 http://archive.ubuntu.com/ubuntu disco/universe amd64 Packages 500 http://archive.ubuntu.com/ubuntu disco/universe i386 Packages 100 /var/lib/dpkg/status ++ sudo service bluetooth status command bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: deactivating (final-sigterm) (Result: exit-code) since Fri 2019-09-27 10:44:37 CEST; 20min ago Docs: man:bluetoothd(8) Process: 3897 ExecStart=/usr/lib/bluetooth/bluetoothd (code=exited, status=1/FAILURE) Main PID: 3897 (code=exited, status=1/FAILURE) Status: "Starting up" Tasks: 1 (limit: 4915) Memory: 3.9M CGroup: /system.slice/bluetooth.service └─1156 /usr/lib/bluetooth/bluetoothd set 27 11:00:53 hostname systemd[1]: Starting Bluetooth service... set 27 11:00:53 hostname bluetoothd[3897]: Bluetooth daemon 5.50 set 27 11:00:53 hostname bluetoothd[3897]: D-Bus setup failed: Name already in use set 27 11:00:53 hostname bluetoothd[3897]: Unable to get on D-Bus set 27 11:00:53 hostname systemd[1]: bluetooth.service: Main process exited, code=exited, status=1/FAILURE set 27 11:02:24 hostname systemd[1]: bluetooth.service: State 'stop-sigterm' timed out. Killing. set 27 11:02:24 hostname systemd[1]: bluetooth.service: Killing process 1156 (bluetoothd) with signal SIGKILL. set 27 11:03:54 hostname systemd[1]: bluetooth.service: Processes still around after SIGKILL. Ignoring. ++ cat /proc/version_signature command Ubuntu 5.0.0-29.31-generic 5.0.21 ** Affects: bluez (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: bluetooth disco -- Bluetooth service stop working https://bugs.launchpad.net/bugs/1845617 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to bluez 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
