[Touch-packages] [Bug 1835738] Re: SRU: Update Python interpreter to 3.6.9 and 3.7.5
given back tests, the one remaining failing test virtualbox/6.0.14-dfsg-1 (amd64) doesn't look like it is Python specific. -- 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: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: Fix Released Status in python3.6 source package in Bionic: Fix Committed Status in python3.7 source package in Bionic: Fix Committed Status in python3-defaults source package in Disco: New Status in python3-stdlib-extensions source package in Disco: Fix Released 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: Fix Released Status in python3.7 source package in Eoan: Fix Committed 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. https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-tst-bionic.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 Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853378] Re: 2500u random freeze during usage
** Summary changed: - Xorg freeze + 2500u random freeze during usage ** Summary changed: - 2500u random freeze during usage + ryzen 2500u random freeze during usage ** Summary changed: - ryzen 2500u random freeze during usage + ryzen 2500u random Xorg freeze -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1853378 Title: ryzen 2500u random Xorg freeze Status in xorg package in Ubuntu: New Bug description: Currently using a Dell Inspiron 3835 with a ryzen 2500u with 8gb of ram on a pcie nvme ssd. PC randomly freezes at times. This actually occurs on asus x505za also running 2500u. I checked the log files and there was this error. [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654 [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process gnome-shell pid 10648 thread gnome-shel:cs0 pid 10654 I think it may be a problem with gnome since I was running lubuntu before and there's no hang whatsoever when using that. Ubuntu 18.04.3 LTS Release 18.04 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 Uname: Linux 5.3.12-050312-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 21 07:04:57 2019 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu GpuHangFrequency: Several times a week GpuHangReproducibility: Seems to happen randomly GpuHangStarted: Since a couple weeks or more GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Raven Ridge [Radeon Vega Series / Radeon Vega Mobile Series] [1002:15dd] (rev c4) (prog-if 00 [VGA controller]) Subsystem: Dell Vega [Radeon Vega 8 Mobile] [1028:08d7] InstallationDate: Installed on 2019-11-19 (1 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Dell Inc. Inspiron 3585 ProcEnviron: LANGUAGE=en_PH:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_PH.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.12-050312-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash idle=nomwait iommu=soft pci=nomsi vt.handoff=1 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/29/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.4.0 dmi.board.asset.tag: not specified dmi.board.name: 0TY9XW dmi.board.vendor: Dell Inc. dmi.board.version: X01 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 1.4.0 dmi.modalias: dmi:bvnDellInc.:bvr1.4.0:bd05/29/2019:svnDellInc.:pnInspiron3585:pvr1.4.0:rvnDellInc.:rn0TY9XW:rvrX01:cvnDellInc.:ct10:cvr1.4.0: dmi.product.family: Inspiron dmi.product.name: Inspiron 3585 dmi.product.sku: 08D7 dmi.product.version: 1.4.0 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.100+git1911150630.a39c34~oibaf~b version.libgl1-mesa-dri: libgl1-mesa-dri 20.0~git1911201930.bcfc9c~oibaf~b version.libgl1-mesa-glx: libgl1-mesa-glx 20.0~git1911201930.bcfc9c~oibaf~b version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1853378/+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 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications
I have the same problem with audacious, on UbuntuStudio 18.04 -- 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/1808710 Title: !xcb_xlib_threads_sequence_lost error with GTK2 applications Status in gtk+2.0 package in Ubuntu: Confirmed Bug description: GTK2 applications randomly crash or freeze with error like: [xcb] Unknown sequence number while processing queue [xcb] Most likely this is a multi-threaded client and XInitThreads has not been called [xcb] Aborting, sorry about that. : ../../src/xcb_io.c:263: poll_for_event: Assertion `!xcb_xlib_threads_sequence_lost' failed. where is the name of the executable, e.g. audacious, soffice.bin, etc. RELATED BUGS LibreOffice: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1801161 PCManFM: https://bugs.launchpad.net/ubuntu/+source/pcmanfm/+bug/1782984 Audacious: https://redmine.audacious-media-player.org/issues/798 FreeCAD: https://bugs.launchpad.net/ubuntu/+source/freecad/+bug/1754084 ClawsMail: https://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=4203 OTHER APPLICATIONS SpaceFM, Pidgin, GPicView and GIMP appear to have similar problems. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1841006] Re: gdb reports a segfault in ld-linux.so.3 on armhf
I finally got around to reporting this upstream as https://sourceware.org/bugzilla/show_bug.cgi?id=25215 ** Bug watch added: Sourceware.org Bugzilla #25215 https://sourceware.org/bugzilla/show_bug.cgi?id=25215 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to binutils in Ubuntu. https://bugs.launchpad.net/bugs/1841006 Title: gdb reports a segfault in ld-linux.so.3 on armhf Status in binutils package in Ubuntu: New Bug description: In an eoan armhf container on a disco arm64 vm: root@helped-oyster:~# gdb /bin/true GNU gdb (Ubuntu 8.3-0ubuntu1) 8.3 ... (gdb) r Starting program: /usr/bin/true Program received signal SIGSEGV, Segmentation fault. 0xf7fc8ee0 in ?? () from /lib/ld-linux-armhf.so.3 It happens in a disco container too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1841006/+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 1853525] [NEW] no python 2.7.17 in LTS version
I am sorry you have an issue with python on Ubuntu. By policy, Ubuntu does not blindly upgrade toolchains to point releases in an LTS release, but we go through extensive validation with rebuild and autopkgtests across all of our supported 6 architectures, which is usually in excess of upstream testing. See https://wiki.ubuntu.com/StableReleaseUpdates Note your bug report suggests that you are using out of date package. rc1 is not the latest version of python2.7 in bionic. It has been updated to final release, and has had security updates since. Can you please verify you are using 2.7.15-4ubuntu4~18.04.2 ? What particular issue are you having? Can you provide a minimized reproducer? Traceback? Segfault / coredump? If we have those details about the issue you are experiencing we can work towards resolving it with regression testcase, patch and eventual release of an SRU. I understand you feel frustrated, but please take some time to explain in detail the issue you are experiencing. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1853525 Title: no python 2.7.17 in LTS version Status in python2.7 package in Ubuntu: New Bug description: Python 2.7 in 18.04 that is LTS version is in 2.7.15 RC1 version this version broke my scripts and get me segmentation fault each time I trying to do something. IN LTS version always LATEST python 2.7 should be supported which is 2.7.17. so why I have .15 and in RC1 version. Who is maintainer of this package that sleeps so long. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1853525/+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 1850932] Autopkgtest regression report (glib2.0/2.62.2-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.2-2~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: indicator-session/17.3.20+19.10.20190921-0ubuntu1 (arm64) sbd/1.4.0-18-g5e3283c-1ubuntu1 (i386) cairo/unknown (armhf) netplan.io/0.98-0ubuntu1 (ppc64el) apport/2.20.11-0ubuntu8.2 (amd64) snapd-glib/unknown (armhf) firefox/70.0.1+build1-0ubuntu0.19.10.1 (armhf) bumblebee/unknown (armhf) glib2.0/2.62.2-2~ubuntu19.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850932 Title: [SRU] Backport 2.62.2-2 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.2-2 from focal. The main purpose of this backport (as opposed to -1) is to fix bug #1844853. But there are several other changes. There are many cherry-picks to improve the testsuite's reliability. At the time of upload they weren't in the stable branch, but now they almost all are. These commits can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The two that are not are: commit 2b1e706b2f0007982f4fe6a70734d4490e4093a3 Author: Simon McVittie Date: Tue Oct 29 16:27:53 2019 + gdbus-server-auth test: Create temporary directory for Unix socket This avoids failure to listen on the given address on non-Linux Unix kernels, where abstract sockets do not exist and so unix:tmpdir is equivalent to unix:dir. To avoid bugs like this one recurring, run most of these tests using the unix:dir address type, where Linux is equivalent to other Unix kernels; just do one unix:tmpdir test, to check that we still interoperate with libdbus when using abstract sockets on Linux. Resolves: GNOME/glib#1920 Fixes: 9f962ebe "Add a test for GDBusServer authentication" Signed-off-by: Simon McVittie commit 9f962ebeac1d67223579ad0d261c4c8215f7c427 Author: Simon McVittie Date: Fri Oct 11 19:02:55 2019 +0100 Add a test for GDBusServer authentication In particular, if libbdus is available, we test interoperability with a libdbus client: see GNOME/glib#1831. Because that issue describes a race condition, we do each test repeatedly to try to hit the failing case. Signed-off-by: Simon McVittie which are both testsuite fixes. There are some additional non-upstream changes: * d/p/debian/mimeapps-test-Mark-as-flaky.patch: Drop patch, hopefully no longer needed with #941550 fixed * d/p/debian/taptestrunner-Stop-looking-like-an-executable-script.patch: Make taptestrunner non-executable to avoid a Lintian warning the former is again a testsuite fix. The latter is a fix to the test runner, which is relevant for the installed tests (run via autopkgtest) but not otherwise. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. [ Regression potential ] all test fixes> Build failures or autopkgtest failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+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 1844853] Autopkgtest regression report (glib2.0/2.62.2-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.2-2~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: indicator-session/17.3.20+19.10.20190921-0ubuntu1 (arm64) sbd/1.4.0-18-g5e3283c-1ubuntu1 (i386) cairo/unknown (armhf) netplan.io/0.98-0ubuntu1 (ppc64el) apport/2.20.11-0ubuntu8.2 (amd64) snapd-glib/unknown (armhf) firefox/70.0.1+build1-0ubuntu0.19.10.1 (armhf) bumblebee/unknown (armhf) glib2.0/2.62.2-2~ubuntu19.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in GLib: Fix Released Status in ibus: Fix Released Status in glib2.0 package in Ubuntu: Fix Committed Status in ibus package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: In Progress Status in glib2.0 source package in Bionic: Fix Committed Status in glib2.0 source package in Disco: In Progress Status in glib2.0 source package in Eoan: Fix Committed Status in glib2.0 source package in Focal: Fix Committed Status in ibus source package in Focal: Fix Released Status in glib2.0 package in Debian: Fix Released Bug description: [Impact] IBus was broken for Qt applications as a regression due to the fix of CVE-2019-14822. As a result the IBus patch was disabled temporarily, which fixed IBus from a usability POV. The real fix has been made in glib2.0, and the updates in -proposed will allow the IBus patch to be re-enabled. [Test Case] * On a standard Ubuntu {eoan,disco,bionic,xenial} installation - Upgrade the glib2.0 packages from {eoan,disco,bionic,xenial}-proposed - Upgrade the ibus packages from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa - Install some IBus input method, e.g. ibus-libpinyin - Install some Qt application, e.g. Kate * Relogin (maybe reboot) * Add the input method to the input sources * Open the Qt app and try to input something using the IBus IM => Find that the transliteration works as expected [Regression Potential] The applicable patches origin from glib upstream: https://gitlab.gnome.org/GNOME/glib/merge_requests/1176 Consequently the changes have been reviewed by the glib maintainer, but also tested by the IBus maintainer, by me (gunnarhj), and - of course - the author Simon McVittie. The changes have been in Debian unstable since 2019-10-30. [Original description] Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1844853/+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] Autopkgtest regression report (glib2.0/2.62.2-2~ubuntu19.10.1)
All autopkgtests for the newly accepted glib2.0 (2.62.2-2~ubuntu19.10.1) for eoan have finished running. The following regressions have been reported in tests triggered by the package: indicator-session/17.3.20+19.10.20190921-0ubuntu1 (arm64) sbd/1.4.0-18-g5e3283c-1ubuntu1 (i386) cairo/unknown (armhf) netplan.io/0.98-0ubuntu1 (ppc64el) apport/2.20.11-0ubuntu8.2 (amd64) snapd-glib/unknown (armhf) firefox/70.0.1+build1-0ubuntu0.19.10.1 (armhf) bumblebee/unknown (armhf) glib2.0/2.62.2-2~ubuntu19.10.1 (i386) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ 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/. [ Fix ] This bug was fixed upstream in 2.62.2 (see the links below). That update is being issues to eoan. [ QA ] Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test that this bug is fixed. Nevertheless, to verify this bug please give the desktop a good workout. Ideally install the SRU and use your machine as you would normally for a variety of tasks. Make sure there are no regressions. [ Regression potential ] 1) The changes involve mutexes and stuff, which is error prone. 2) It's GLib, a core library, so any bad regressions will be really serious for the desktop as a whole. 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 1853525] Re: no python 2.7.17 in LTS version
Thank you for taking the time to report this issue and helping to make Ubuntu better. Python 2 is very near EOL & thus Debian & Ubuntu have been working to remove it as much as possible; ie. getting packages that use python ported to use python3 instead, with only security fixes the exception. Please refer https://wiki.ubuntu.com/Python/Python36Transition or https://wiki.ubuntu.com/Python or https://pythonclock.org/ -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1853525 Title: no python 2.7.17 in LTS version Status in python2.7 package in Ubuntu: New Bug description: Python 2.7 in 18.04 that is LTS version is in 2.7.15 RC1 version this version broke my scripts and get me segmentation fault each time I trying to do something. IN LTS version always LATEST python 2.7 should be supported which is 2.7.17. so why I have .15 and in RC1 version. Who is maintainer of this package that sleeps so long. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1853525/+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 1844853] Autopkgtest regression report (glib2.0/2.56.4-0ubuntu0.18.04.5)
All autopkgtests for the newly accepted glib2.0 (2.56.4-0ubuntu0.18.04.5) for bionic have finished running. The following regressions have been reported in tests triggered by the package: gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64) cairo/unknown (armhf) firefox/70.0.1+build1-0ubuntu0.18.04.1 (armhf) pinentry/1.1.0-1 (amd64) policykit-1/unknown (armhf) systemd/237-3ubuntu10.31 (s390x) cmake-extras/1.3+17.04.20170310-1ubuntu4 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#glib2.0 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in GLib: Fix Released Status in ibus: Fix Released Status in glib2.0 package in Ubuntu: Fix Committed Status in ibus package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: In Progress Status in glib2.0 source package in Bionic: Fix Committed Status in glib2.0 source package in Disco: In Progress Status in glib2.0 source package in Eoan: Fix Committed Status in glib2.0 source package in Focal: Fix Committed Status in ibus source package in Focal: Fix Released Status in glib2.0 package in Debian: Fix Released Bug description: [Impact] IBus was broken for Qt applications as a regression due to the fix of CVE-2019-14822. As a result the IBus patch was disabled temporarily, which fixed IBus from a usability POV. The real fix has been made in glib2.0, and the updates in -proposed will allow the IBus patch to be re-enabled. [Test Case] * On a standard Ubuntu {eoan,disco,bionic,xenial} installation - Upgrade the glib2.0 packages from {eoan,disco,bionic,xenial}-proposed - Upgrade the ibus packages from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa - Install some IBus input method, e.g. ibus-libpinyin - Install some Qt application, e.g. Kate * Relogin (maybe reboot) * Add the input method to the input sources * Open the Qt app and try to input something using the IBus IM => Find that the transliteration works as expected [Regression Potential] The applicable patches origin from glib upstream: https://gitlab.gnome.org/GNOME/glib/merge_requests/1176 Consequently the changes have been reviewed by the glib maintainer, but also tested by the IBus maintainer, by me (gunnarhj), and - of course - the author Simon McVittie. The changes have been in Debian unstable since 2019-10-30. [Original description] Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1844853/+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 1853525] [NEW] no python 2.7.17 in LTS version
Public bug reported: Python 2.7 in 18.04 that is LTS version is in 2.7.15 RC1 version this version broke my scripts and get me segmentation fault each time I trying to do something. IN LTS version always LATEST python 2.7 should be supported which is 2.7.17. so why I have .15 and in RC1 version. Who is maintainer of this package that sleeps so long. ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New ** Package changed: hdf5 (Ubuntu) => python2.7 (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. https://bugs.launchpad.net/bugs/1853525 Title: no python 2.7.17 in LTS version Status in python2.7 package in Ubuntu: New Bug description: Python 2.7 in 18.04 that is LTS version is in 2.7.15 RC1 version this version broke my scripts and get me segmentation fault each time I trying to do something. IN LTS version always LATEST python 2.7 should be supported which is 2.7.17. so why I have .15 and in RC1 version. Who is maintainer of this package that sleeps so long. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python2.7/+bug/1853525/+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 1853525] [NEW] no python 2.7.17 in LTS version
You have been subscribed to a public bug: Python 2.7 in 18.04 that is LTS version is in 2.7.15 RC1 version this version broke my scripts and get me segmentation fault each time I trying to do something. IN LTS version always LATEST python 2.7 should be supported which is 2.7.17. so why I have .15 and in RC1 version. Who is maintainer of this package that sleeps so long. ** Affects: python2.7 (Ubuntu) Importance: Undecided Status: New -- no python 2.7.17 in LTS version https://bugs.launchpad.net/bugs/1853525 You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python2.7 in Ubuntu. -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1835738] Autopkgtest regression report (python3.7/3.7.5-2~19.10)
All autopkgtests for the newly accepted python3.7 (3.7.5-2~19.10) for eoan have finished running. The following regressions have been reported in tests triggered by the package: libreoffice/1:6.3.3-0ubuntu0.19.10.1 (s390x) virtualbox/6.0.14-dfsg-1 (amd64) ros-ros-comm/1.14.3+ds1-5build2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/eoan/update_excuses.html#python3.7 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: Fix Released Status in python3.7 package in Ubuntu: Fix Released Status in python3-defaults source package in Bionic: New Status in python3-stdlib-extensions source package in Bionic: Fix Released Status in python3.6 source package in Bionic: Fix Committed Status in python3.7 source package in Bionic: Fix Committed Status in python3-defaults source package in Disco: New Status in python3-stdlib-extensions source package in Disco: Fix Released 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: Fix Released Status in python3.7 source package in Eoan: Fix Committed 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. https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-bionic.html https://people.canonical.com/~doko/ftbfs-report/test-rebuild-20191018-release-tst-bionic.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 Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1853516] [NEW] package libprocps6:amd64 2:3.3.12-3ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting con
Public bug reported: I was trying to install vscode and the command crashes. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libprocps6:amd64 2:3.3.12-3ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Nov 22 02:11:02 2019 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-13 (465 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.6ubuntu0.1 SourcePackage: procps Title: package libprocps6:amd64 2:3.3.12-3ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: procps (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to procps in Ubuntu. https://bugs.launchpad.net/bugs/1853516 Title: package libprocps6:amd64 2:3.3.12-3ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration Status in procps package in Ubuntu: New Bug description: I was trying to install vscode and the command crashes. ProblemType: Package DistroRelease: Ubuntu 18.04 Package: libprocps6:amd64 2:3.3.12-3ubuntu1.1 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Fri Nov 22 02:11:02 2019 ErrorMessage: package is in a very bad inconsistent state; you should reinstall it before attempting configuration InstallationDate: Installed on 2018-08-13 (465 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3ubuntu1 PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 2.7.15~rc1-1 RelatedPackageVersions: dpkg 1.19.0.5ubuntu2.3 apt 1.6.6ubuntu0.1 SourcePackage: procps Title: package libprocps6:amd64 2:3.3.12-3ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/procps/+bug/1853516/+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 1846821] Re: Qt print dialog has wrong default page size
Łukasz, thank you very much for accepting the package into bionic- proposed. I confirm that the updated binary package libqt5printsupport5 fixes the problem. I also updated other libqt5* packages available in bionic-proposed, and did not notice any obvious regressions. However, I would like to voice my differing opinion on the importance of this bug. While this is perhaps not a high-impact bug in the meaning that it does not impact system stability or security, it is nonetheless one of the "infuriating little bugs" that significantly degrade user experience. For the user who does not remember to dig into prefs to change paper size before every print job, the bug results in the necessity of printing everything twice, as the first copy (A4 on Letter) has top and bottom lines clipped and missing, rendering the printout unusable. This bug, coupled with similar ones and the general instability of KDE desktop, makes Kubuntu 18.04 unsuitable as a desktop OS for everyday use, in my opinion. Because of that I am very grateful that this bug is getting fixed. ** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1846821 Title: Qt print dialog has wrong default page size Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Committed Bug description: Please backport Qt patch 213677 to qtbase-opensource-src https://codereview.qt-project.org/c/qt/qtbase/+/213677 [Impact] In Qt5 applications, print dialog (Printer Properties) always defaults to A4 paper size, even when Letter is set as a default in all system and KDE preferences. After changing manually, Letter-size pages print correctly, but the setting does not stick. This impacts users of Qt applications who print things and live in countries where ISO 216 is not default, most notably the United States. [Test Case] 1) Use system settings (KDE preferences, gnome-control-center or system-config-printer) to set the printer size to Letter. 2) Open any Qt application (e.g. KWrite or Falkon). 3) Open a print dialog. 4) Behavior expected: Print dialog would default to Letter paper size and not A4. [Regression Potential] Two possibilities for regressions that I can imagine are: - crashes because something is not defined; - wrong default paper size (A4 wanted but CUPS returns something else). [Additional Information] The issue also affects other print settings, e.g. margins, though the aforementioned patch does not deal with these. A similar issue regarding the duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, but other print settings continue to cause problems. Software versions: lsb_release: Ubuntu 18.04.3 LTS libqt5core5a: 5.9.5+dfsg-0ubuntu2.3 Kernel: 5.0.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
I thought we were going to some effort to reduce the number of systems where resolveconf was going to be used, or even remove it from the distro entirely. Thanks -- 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/1853164 Title: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error Status in systemd package in Ubuntu: Triaged Status in systemd source package in Focal: Triaged Bug description: The functionality exists to allow users to revert to the traditional ifupdown package for network configuration. Alongside this, systemd's often-buggy resolver can be disabled. However, there's a logic error in the systemd- supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system from populating /etc/resolv.conf properly when systemd-resolved is disabled. The issue is here: if [ -x /lib/systemd/systemd-resolved ] ; then Instead of checking to see if the systemd-resolved service is enabled or active, which would be the correct behaviour, this checks for the existence of a binary, assuming that if it exists it's supposed to be used. I've not tested this in the absence of resolvconf, but if systemd-resolved isn't enabled, it's difficult to imagine this code wanting to run. I've tested this with resolvconf and ifupdown driving dhclient, and it corrects the behaviour that was broken with the introduction of systemd-resolved. I'm attaching a patch, and am also including it here for easy access: *** resolved.broken 2019-11-19 15:01:28.785588838 + --- resolved2019-11-19 15:08:06.519430073 + *** *** 14,20 # (D) = master script downs interface # (-) = master script does nothing with this ! if [ -x /lib/systemd/systemd-resolved ] ; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in --- 14,21 # (D) = master script downs interface # (-) = master script does nothing with this ! systemctl is-active systemd-resolved > /dev/null 2>&1 ! if [ $? -eq 0 ]; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+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 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
Interesting. But the code is still incorrect, with my patch correcting it, so I guess we'll see how it goes. I can either fix it locally or go elsewhere, but I'm hoping it's simply fixed in the distribution. Thanks for the pointer. -- 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/1853164 Title: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error Status in systemd package in Ubuntu: Triaged Status in systemd source package in Focal: Triaged Bug description: The functionality exists to allow users to revert to the traditional ifupdown package for network configuration. Alongside this, systemd's often-buggy resolver can be disabled. However, there's a logic error in the systemd- supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system from populating /etc/resolv.conf properly when systemd-resolved is disabled. The issue is here: if [ -x /lib/systemd/systemd-resolved ] ; then Instead of checking to see if the systemd-resolved service is enabled or active, which would be the correct behaviour, this checks for the existence of a binary, assuming that if it exists it's supposed to be used. I've not tested this in the absence of resolvconf, but if systemd-resolved isn't enabled, it's difficult to imagine this code wanting to run. I've tested this with resolvconf and ifupdown driving dhclient, and it corrects the behaviour that was broken with the introduction of systemd-resolved. I'm attaching a patch, and am also including it here for easy access: *** resolved.broken 2019-11-19 15:01:28.785588838 + --- resolved2019-11-19 15:08:06.519430073 + *** *** 14,20 # (D) = master script downs interface # (-) = master script does nothing with this ! if [ -x /lib/systemd/systemd-resolved ] ; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in --- 14,21 # (D) = master script downs interface # (-) = master script does nothing with this ! systemctl is-active systemd-resolved > /dev/null 2>&1 ! if [ $? -eq 0 ]; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+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 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
I think this is a dup of bug 1745463, which might not be the answer you were hoping for. -- 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/1853164 Title: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error Status in systemd package in Ubuntu: Triaged Status in systemd source package in Focal: Triaged Bug description: The functionality exists to allow users to revert to the traditional ifupdown package for network configuration. Alongside this, systemd's often-buggy resolver can be disabled. However, there's a logic error in the systemd- supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system from populating /etc/resolv.conf properly when systemd-resolved is disabled. The issue is here: if [ -x /lib/systemd/systemd-resolved ] ; then Instead of checking to see if the systemd-resolved service is enabled or active, which would be the correct behaviour, this checks for the existence of a binary, assuming that if it exists it's supposed to be used. I've not tested this in the absence of resolvconf, but if systemd-resolved isn't enabled, it's difficult to imagine this code wanting to run. I've tested this with resolvconf and ifupdown driving dhclient, and it corrects the behaviour that was broken with the introduction of systemd-resolved. I'm attaching a patch, and am also including it here for easy access: *** resolved.broken 2019-11-19 15:01:28.785588838 + --- resolved2019-11-19 15:08:06.519430073 + *** *** 14,20 # (D) = master script downs interface # (-) = master script does nothing with this ! if [ -x /lib/systemd/systemd-resolved ] ; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in --- 14,21 # (D) = master script downs interface # (-) = master script does nothing with this ! systemctl is-active systemd-resolved > /dev/null 2>&1 ! if [ $? -eq 0 ]; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+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 1853164] Re: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error
** Also affects: systemd (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: systemd (Ubuntu Focal) Status: New => Triaged ** Changed in: systemd (Ubuntu Focal) Importance: Undecided => Low -- 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/1853164 Title: systemd: /etc/dhcp/dhclient-enter-hooks.d/resolved error Status in systemd package in Ubuntu: Triaged Status in systemd source package in Focal: Triaged Bug description: The functionality exists to allow users to revert to the traditional ifupdown package for network configuration. Alongside this, systemd's often-buggy resolver can be disabled. However, there's a logic error in the systemd- supplied /etc/dhcp/dhclient-enter-hooks.d/resolved that prevents the system from populating /etc/resolv.conf properly when systemd-resolved is disabled. The issue is here: if [ -x /lib/systemd/systemd-resolved ] ; then Instead of checking to see if the systemd-resolved service is enabled or active, which would be the correct behaviour, this checks for the existence of a binary, assuming that if it exists it's supposed to be used. I've not tested this in the absence of resolvconf, but if systemd-resolved isn't enabled, it's difficult to imagine this code wanting to run. I've tested this with resolvconf and ifupdown driving dhclient, and it corrects the behaviour that was broken with the introduction of systemd-resolved. I'm attaching a patch, and am also including it here for easy access: *** resolved.broken 2019-11-19 15:01:28.785588838 + --- resolved2019-11-19 15:08:06.519430073 + *** *** 14,20 # (D) = master script downs interface # (-) = master script does nothing with this ! if [ -x /lib/systemd/systemd-resolved ] ; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in --- 14,21 # (D) = master script downs interface # (-) = master script does nothing with this ! systemctl is-active systemd-resolved > /dev/null 2>&1 ! if [ $? -eq 0 ]; then # For safety, first undefine the nasty default make_resolv_conf() make_resolv_conf() { : ; } case "$reason" in To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1853164/+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 1846821] Autopkgtest regression report (qtbase-opensource-src/5.9.5+dfsg-0ubuntu2.4)
All autopkgtests for the newly accepted qtbase-opensource-src (5.9.5+dfsg-0ubuntu2.4) for bionic have finished running. The following regressions have been reported in tests triggered by the package: kcoreaddons/unknown (armhf) killbots/unknown (armhf) kfind/unknown (armhf) libkf5mailimporter/unknown (armhf) kcrash/5.44.0-0ubuntu1 (armhf) khtml/5.44.0-0ubuntu1 (armhf) pinentry/1.1.0-1 (amd64) ksystemlog/4:17.12.3-0ubuntu1 (armhf) kdepim-runtime/4:17.12.3-0ubuntu2 (armhf) kf5-messagelib/4:17.12.3-0ubuntu3 (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/bionic/update_excuses.html#qtbase-opensource-src [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1846821 Title: Qt print dialog has wrong default page size Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Committed Bug description: Please backport Qt patch 213677 to qtbase-opensource-src https://codereview.qt-project.org/c/qt/qtbase/+/213677 [Impact] In Qt5 applications, print dialog (Printer Properties) always defaults to A4 paper size, even when Letter is set as a default in all system and KDE preferences. After changing manually, Letter-size pages print correctly, but the setting does not stick. This impacts users of Qt applications who print things and live in countries where ISO 216 is not default, most notably the United States. [Test Case] 1) Use system settings (KDE preferences, gnome-control-center or system-config-printer) to set the printer size to Letter. 2) Open any Qt application (e.g. KWrite or Falkon). 3) Open a print dialog. 4) Behavior expected: Print dialog would default to Letter paper size and not A4. [Regression Potential] Two possibilities for regressions that I can imagine are: - crashes because something is not defined; - wrong default paper size (A4 wanted but CUPS returns something else). [Additional Information] The issue also affects other print settings, e.g. margins, though the aforementioned patch does not deal with these. A similar issue regarding the duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, but other print settings continue to cause problems. Software versions: lsb_release: Ubuntu 18.04.3 LTS libqt5core5a: 5.9.5+dfsg-0ubuntu2.3 Kernel: 5.0.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1724919] Re: Bluetooth headphones only use A2DP when connected manually
For those with Sony headphones, and who are affected by this annoying bug, the attached "headphones" Perl script is a partial workaround. You'll need to edit it for the bluetooth address of your headphones. Run it after switching your headphones on and they connect, and it sets A2DP. ** Attachment added: "headphones" https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+attachment/5306921/+files/headphones -- 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/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1724919] Re: Bluetooth headphones only use A2DP when connected manually
Can this please be re-opened? Daniel van Vugt marked it as "won't fix" in comment #14 due to Ubuntu 17.10 being end of life, but numerous people are still encountering the problem with more recent versions. I'm encountering it on Ubuntu 19.10 and a new Sony WH-1000XM3. If this bug can't be re-opened, should we create a new bug for more recent versions of Ubuntu? -- 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/1724919 Title: Bluetooth headphones only use A2DP when connected manually Status in alsa-driver package in Ubuntu: Won't Fix Bug description: Issue with Sony MDR-1ABT Bluetooth headphones: Once paired, the headphones will be connected automatically whenever they are switched on. However when connected this way, only the HSP/HFP profile will work and trying to change to A2DP in sound settings does nothing. If the headphones are then manually disconnected and reconnected from Bluetooth settings, they will initially use HSP/HFP but then selecting A2DP in sound settings will successfully make them use A2DP. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.7-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neil 1443 F pulseaudio /dev/snd/pcmC0D0c: neil 1443 F...m pulseaudio /dev/snd/controlC0: neil 1443 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Oct 19 19:12:59 2017 InstallationDate: Installed on 2017-10-19 (0 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: MDR-1ABT Symptom_Type: None of the above Title: [MDR-1ABT, playback] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F5 dmi.board.asset.tag: Default string dmi.board.name: Z270N-WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF5:bd07/06/2017:svnGigabyteTechnologyCo.,Ltd.:pnZ270N-WIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ270N-WIFI-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: Z270N-WIFI dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1724919/+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 1853466] [NEW] I have installed the xserver-xorg-video-intel package but cannot detect monitor
Public bug reported: The monitor U2414H is not detected by Ubuntu, the graphics card displayed in settings is llvmpipe (LLVM 8.0, 256 bits). I believe it should be "Intel Iris Plus Graphics", which is what shows up in Windows Device Manager (my device is set up to dual boot). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 21 15:03:21 2019 DistUpgraded: SystemError: E:Setting in Stop via TCSAFLUSH for stdin failed! - tcsetattr (5: Input/output error), W:Operation was interrupted before it could finish DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8042, 4.15.0-70-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-70-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08b0] InstallationDate: Installed on 2019-11-15 (6 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-70-generic root=UUID=4540fdd6-b986-43c5-99ec-e2baa34ca219 ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg UpgradeStatus: Upgraded to bionic on 2019-11-19 (2 days ago) dmi.bios.date: 09/17/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.13 dmi.board.name: 06CDVY dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 31 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.13:bd09/17/2019:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 7390 2-in-1 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 xserver.bootTime: Thu Nov 21 15:01:07 2019 xserver.configfile: default xserver.errors: open /dev/dri/card0: No such file or directory open /dev/dri/card0: No such file or directory Screen 0 deleted because of no matching config section. AIGLX: reverting to software rendering xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.19.6-1ubuntu4.3 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ubuntu -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to xorg in Ubuntu. https://bugs.launchpad.net/bugs/1853466 Title: I have installed the xserver-xorg-video-intel package but cannot detect monitor Status in xorg package in Ubuntu: New Bug description: The monitor U2414H is not detected by Ubuntu, the graphics card displayed in settings is llvmpipe (LLVM 8.0, 256 bits). I believe it should be "Intel Iris Plus Graphics", which is what shows up in Windows Device Manager (my device is set up to dual boot). ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-70.79-generic 4.15.18 Uname: Linux 4.15.0-70-generic x86_64 NonfreeKernelModules: wl .tmp.unity_support_test.1: ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Thu Nov 21 15:03:21 2019 DistUpgraded: SystemError: E:Setting in Stop via TCSAFLUSH for stdin failed! - tcsetattr (5: Input/output error), W:Operation was interrupted before it could finish DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: backport-iwlwifi, 8042, 4.15.0-70-generic, x86_64: installed bcmwl, 6.30.223.271+bdcom, 4.15.0-70-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Device [8086:8a52] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:08b0] InstallationDate: Installed on 2019-11-15 (6 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: Dell Inc. XPS 13 7390 2-in-1 ProcKer
[Touch-packages] [Bug 1848202] Re: Use after free in gdbus leads to eds segfaults
This bug was fixed in the package glib2.0 - 2.63.1-2 --- glib2.0 (2.63.1-2) experimental; urgency=medium * d/p/Revert-glocalfileinfo-Only-return-file-mode-not-type-as-U.patch: Revert "glocalfileinfo: Only return file mode, not type, as UNIX_MODE attribute" This reverts commit bfdc5fc4fc84ef8518d2d1a328c8482cf5a38e98. This commit changes the semantics of the `unix::mode` attribute, which some things (the one we've noticed is ostree) rely on. * d/p/test_copy_preserve_mode-Adjust-for-revert-semantics.patch: test_copy_preserve_mode: Adjust for revert semantics. Now we're returning the file type again, we need to mask it out to compare with the mode. -- Iain Lane Mon, 18 Nov 2019 13:59:35 + ** Changed in: glib2.0 (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ 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/. [ Fix ] This bug was fixed upstream in 2.62.2 (see the links below). That update is being issues to eoan. [ QA ] Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test that this bug is fixed. Nevertheless, to verify this bug please give the desktop a good workout. Ideally install the SRU and use your machine as you would normally for a variety of tasks. Make sure there are no regressions. [ Regression potential ] 1) The changes involve mutexes and stuff, which is error prone. 2) It's GLib, a core library, so any bad regressions will be really serious for the desktop as a whole. 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
Bug #1844853 was explicitly verified (comment #15). Didn't observe any unexpected behavior due to the glib2.0 upgrade. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: In Progress Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ 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/. [ Fix ] This bug was fixed upstream in 2.62.2 (see the links below). That update is being issues to eoan. [ QA ] Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test that this bug is fixed. Nevertheless, to verify this bug please give the desktop a good workout. Ideally install the SRU and use your machine as you would normally for a variety of tasks. Make sure there are no regressions. [ Regression potential ] 1) The changes involve mutexes and stuff, which is error prone. 2) It's GLib, a core library, so any bad regressions will be really serious for the desktop as a whole. 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 1850932] Re: [SRU] Backport 2.62.2-2
Bug #1844853 was explicitly verified (comment #15). Didn't observe any unexpected behavior due to the glib2.0 upgrade. ** Tags removed: verification-needed verification-needed-eoan ** Tags added: verification-done verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850932 Title: [SRU] Backport 2.62.2-2 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.2-2 from focal. The main purpose of this backport (as opposed to -1) is to fix bug #1844853. But there are several other changes. There are many cherry-picks to improve the testsuite's reliability. At the time of upload they weren't in the stable branch, but now they almost all are. These commits can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The two that are not are: commit 2b1e706b2f0007982f4fe6a70734d4490e4093a3 Author: Simon McVittie Date: Tue Oct 29 16:27:53 2019 + gdbus-server-auth test: Create temporary directory for Unix socket This avoids failure to listen on the given address on non-Linux Unix kernels, where abstract sockets do not exist and so unix:tmpdir is equivalent to unix:dir. To avoid bugs like this one recurring, run most of these tests using the unix:dir address type, where Linux is equivalent to other Unix kernels; just do one unix:tmpdir test, to check that we still interoperate with libdbus when using abstract sockets on Linux. Resolves: GNOME/glib#1920 Fixes: 9f962ebe "Add a test for GDBusServer authentication" Signed-off-by: Simon McVittie commit 9f962ebeac1d67223579ad0d261c4c8215f7c427 Author: Simon McVittie Date: Fri Oct 11 19:02:55 2019 +0100 Add a test for GDBusServer authentication In particular, if libbdus is available, we test interoperability with a libdbus client: see GNOME/glib#1831. Because that issue describes a race condition, we do each test repeatedly to try to hit the failing case. Signed-off-by: Simon McVittie which are both testsuite fixes. There are some additional non-upstream changes: * d/p/debian/mimeapps-test-Mark-as-flaky.patch: Drop patch, hopefully no longer needed with #941550 fixed * d/p/debian/taptestrunner-Stop-looking-like-an-executable-script.patch: Make taptestrunner non-executable to avoid a Lintian warning the former is again a testsuite fix. The latter is a fix to the test runner, which is relevant for the installed tests (run via autopkgtest) but not otherwise. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. [ Regression potential ] all test fixes> Build failures or autopkgtest failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+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 1844853] Re: IBus no longer works in Qt applications after upgrade
I verified the test case using - version 2.62.2-2~ubuntu19.10.1 of libglib2.0-{0,bin,data} from eoan-proposed - version 1.5.21-1~exp2ubuntu2.1 of the ibus packages from ppa:ubuntu-security-proposed/ppa Could successfully input Bangla characters in Kate using ibus-avro. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in GLib: Fix Released Status in ibus: Fix Released Status in glib2.0 package in Ubuntu: Fix Committed Status in ibus package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: In Progress Status in glib2.0 source package in Bionic: Fix Committed Status in glib2.0 source package in Disco: In Progress Status in glib2.0 source package in Eoan: Fix Committed Status in glib2.0 source package in Focal: Fix Committed Status in ibus source package in Focal: Fix Released Status in glib2.0 package in Debian: Fix Released Bug description: [Impact] IBus was broken for Qt applications as a regression due to the fix of CVE-2019-14822. As a result the IBus patch was disabled temporarily, which fixed IBus from a usability POV. The real fix has been made in glib2.0, and the updates in -proposed will allow the IBus patch to be re-enabled. [Test Case] * On a standard Ubuntu {eoan,disco,bionic,xenial} installation - Upgrade the glib2.0 packages from {eoan,disco,bionic,xenial}-proposed - Upgrade the ibus packages from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa - Install some IBus input method, e.g. ibus-libpinyin - Install some Qt application, e.g. Kate * Relogin (maybe reboot) * Add the input method to the input sources * Open the Qt app and try to input something using the IBus IM => Find that the transliteration works as expected [Regression Potential] The applicable patches origin from glib upstream: https://gitlab.gnome.org/GNOME/glib/merge_requests/1176 Consequently the changes have been reviewed by the glib maintainer, but also tested by the IBus maintainer, by me (gunnarhj), and - of course - the author Simon McVittie. The changes have been in Debian unstable since 2019-10-30. [Original description] Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1844853/+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 1844853] Re: IBus no longer works in Qt applications after upgrade
Hello Adam, or anyone else affected, Accepted glib2.0 into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.56.4-0ubuntu0.18.04.5 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: glib2.0 (Ubuntu Bionic) Status: In Progress => 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 ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in GLib: Fix Released Status in ibus: Fix Released Status in glib2.0 package in Ubuntu: Fix Committed Status in ibus package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: In Progress Status in glib2.0 source package in Bionic: Fix Committed Status in glib2.0 source package in Disco: In Progress Status in glib2.0 source package in Eoan: Fix Committed Status in glib2.0 source package in Focal: Fix Committed Status in ibus source package in Focal: Fix Released Status in glib2.0 package in Debian: Fix Released Bug description: [Impact] IBus was broken for Qt applications as a regression due to the fix of CVE-2019-14822. As a result the IBus patch was disabled temporarily, which fixed IBus from a usability POV. The real fix has been made in glib2.0, and the updates in -proposed will allow the IBus patch to be re-enabled. [Test Case] * On a standard Ubuntu {eoan,disco,bionic,xenial} installation - Upgrade the glib2.0 packages from {eoan,disco,bionic,xenial}-proposed - Upgrade the ibus packages from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa - Install some IBus input method, e.g. ibus-libpinyin - Install some Qt application, e.g. Kate * Relogin (maybe reboot) * Add the input method to the input sources * Open the Qt app and try to input something using the IBus IM => Find that the transliteration works as expected [Regression Potential] The applicable patches origin from glib upstream: https://gitlab.gnome.org/GNOME/glib/merge_requests/1176 Consequently the changes have been reviewed by the glib maintainer, but also tested by the IBus maintainer, by me (gunnarhj), and - of course - the author Simon McVittie. The changes have been in Debian unstable since 2019-10-30. [Original description] Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (probably f
[Touch-packages] [Bug 1853440] [NEW] Volume either 0 or 100% on Lenovo X1 Carbon G7
Public bug reported: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 ** Affects: alsa-driver (Ubuntu) Importance: Undecided Status: New ** Attachment added: "alsa-info" https://bugs.launchpad.net/bugs/1853440/+attachment/5306861/+files/alsa-info.txt.90cJ4Z1Jmz -- 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/1853440 Title: Volume either 0 or 100% on Lenovo X1 Carbon G7 Status in alsa-driver package in Ubuntu: New Bug description: Volume increasing or decreasing doesn't work. I can only toggle sound on (= 100%) and off (= 0%). What I found out is that the Master channel seems to have no effect for volume adjustments, but the PCM channel does. If the sound is muted, PCM is set to 0 and therefore the sound is toggled off, but when I increase the sound a bit, PCM jumps straight to 100, causing the speakers to be very load. I have attached alsa-info output. System environment: Pop!_OS 19.10 Release: 19.10 Alsa-Version: alsa-base: 1.0.25 Sound Card: HDA-Intel Codec: Realtek ALC285 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1853440/+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 1853439] [NEW] xubuntu 18.04.3 rt5651 sound problem
Public bug reported: no sound ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Thu Nov 21 13:27:58 2019 InstallationDate: Installed on 2019-11-20 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=tr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC ** Affects: pulseaudio (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 pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1853439 Title: xubuntu 18.04.3 rt5651 sound problem Status in pulseaudio package in Ubuntu: New Bug description: no sound ! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.2 ProcVersionSignature: Ubuntu 5.0.0-36.39~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC1', '/dev/snd/pcmC1D2p', '/dev/snd/pcmC1D1p', '/dev/snd/pcmC1D0p', '/dev/snd/controlC0', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE Date: Thu Nov 21 13:27:58 2019 InstallationDate: Installed on 2019-11-20 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LANGUAGE=tr PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=tr_TR.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/06/2017 dmi.bios.version: LC-BI-14-Y116CR210-424-B dmi.board.asset.tag: Default string dmi.board.name: Cherry Trail CR dmi.board.vendor: AMI Corporation dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.version: Default string dmi.modalias: dmi:bvn:bvrLC-BI-14-Y116CR210-424-B:bd12/06/2017:svnI-LifeDigitalTechnologiesLLC:pnZEDAIRTES:pvrDefaultstring:rvnAMICorporation:rnCherryTrailCR:rvrDefaultstring:cvn:ct10:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: ZED AIR TES dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: I-Life Digital Technologies LLC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1853439/+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 1846821] Re: Qt print dialog has wrong default page size
Normally, as this is not really a high-impact bug, I would be a bit reluctant to accept it as an SRU. Since every SRU introduces risks, especially if it's in a big core package like qtbase. But since I see there's activity here (and testers available) + the patch is rather straightforward, then oh well, why not give it a chance. ** Changed in: qtbase-opensource-src (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1846821 Title: Qt print dialog has wrong default page size Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Committed Bug description: Please backport Qt patch 213677 to qtbase-opensource-src https://codereview.qt-project.org/c/qt/qtbase/+/213677 [Impact] In Qt5 applications, print dialog (Printer Properties) always defaults to A4 paper size, even when Letter is set as a default in all system and KDE preferences. After changing manually, Letter-size pages print correctly, but the setting does not stick. This impacts users of Qt applications who print things and live in countries where ISO 216 is not default, most notably the United States. [Test Case] 1) Use system settings (KDE preferences, gnome-control-center or system-config-printer) to set the printer size to Letter. 2) Open any Qt application (e.g. KWrite or Falkon). 3) Open a print dialog. 4) Behavior expected: Print dialog would default to Letter paper size and not A4. [Regression Potential] Two possibilities for regressions that I can imagine are: - crashes because something is not defined; - wrong default paper size (A4 wanted but CUPS returns something else). [Additional Information] The issue also affects other print settings, e.g. margins, though the aforementioned patch does not deal with these. A similar issue regarding the duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, but other print settings continue to cause problems. Software versions: lsb_release: Ubuntu 18.04.3 LTS libqt5core5a: 5.9.5+dfsg-0ubuntu2.3 Kernel: 5.0.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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 1846821] Please test proposed package
Hello Maciej, or anyone else affected, Accepted qtbase-opensource-src into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source /qtbase-opensource-src/5.9.5+dfsg-0ubuntu2.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. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to qtbase-opensource-src in Ubuntu. https://bugs.launchpad.net/bugs/1846821 Title: Qt print dialog has wrong default page size Status in qtbase-opensource-src package in Ubuntu: Fix Released Status in qtbase-opensource-src source package in Bionic: Fix Committed Bug description: Please backport Qt patch 213677 to qtbase-opensource-src https://codereview.qt-project.org/c/qt/qtbase/+/213677 [Impact] In Qt5 applications, print dialog (Printer Properties) always defaults to A4 paper size, even when Letter is set as a default in all system and KDE preferences. After changing manually, Letter-size pages print correctly, but the setting does not stick. This impacts users of Qt applications who print things and live in countries where ISO 216 is not default, most notably the United States. [Test Case] 1) Use system settings (KDE preferences, gnome-control-center or system-config-printer) to set the printer size to Letter. 2) Open any Qt application (e.g. KWrite or Falkon). 3) Open a print dialog. 4) Behavior expected: Print dialog would default to Letter paper size and not A4. [Regression Potential] Two possibilities for regressions that I can imagine are: - crashes because something is not defined; - wrong default paper size (A4 wanted but CUPS returns something else). [Additional Information] The issue also affects other print settings, e.g. margins, though the aforementioned patch does not deal with these. A similar issue regarding the duplex setting was reported as Launchpad bug 1776173, and subsequently fixed, but other print settings continue to cause problems. Software versions: lsb_release: Ubuntu 18.04.3 LTS libqt5core5a: 5.9.5+dfsg-0ubuntu2.3 Kernel: 5.0.0-25-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1846821/+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
Hello errors.ubuntu.com, or anyone else affected, Accepted glib2.0 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.62.2-2~ubuntu19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, 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: glib2.0 (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to 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: In Progress Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ 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/. [ Fix ] This bug was fixed upstream in 2.62.2 (see the links below). That update is being issues to eoan. [ QA ] Under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME, we don't need to explicitly test that this bug is fixed. Nevertheless, to verify this bug please give the desktop a good workout. Ideally install the SRU and use your machine as you would normally for a variety of tasks. Make sure there are no regressions. [ Regression potential ] 1) The changes involve mutexes and stuff, which is error prone. 2) It's GLib, a core library, so any bad regressions will be really serious for the desktop as a whole. 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 1844853] Re: IBus no longer works in Qt applications after upgrade
Hello Adam, or anyone else affected, Accepted glib2.0 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.62.2-2~ubuntu19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, 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: glib2.0 (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ibus in Ubuntu. https://bugs.launchpad.net/bugs/1844853 Title: IBus no longer works in Qt applications after upgrade Status in GLib: Fix Released Status in ibus: Fix Released Status in glib2.0 package in Ubuntu: Fix Committed Status in ibus package in Ubuntu: Fix Released Status in glib2.0 source package in Xenial: In Progress Status in glib2.0 source package in Bionic: In Progress Status in glib2.0 source package in Disco: In Progress Status in glib2.0 source package in Eoan: Fix Committed Status in glib2.0 source package in Focal: Fix Committed Status in ibus source package in Focal: Fix Released Status in glib2.0 package in Debian: Fix Released Bug description: [Impact] IBus was broken for Qt applications as a regression due to the fix of CVE-2019-14822. As a result the IBus patch was disabled temporarily, which fixed IBus from a usability POV. The real fix has been made in glib2.0, and the updates in -proposed will allow the IBus patch to be re-enabled. [Test Case] * On a standard Ubuntu {eoan,disco,bionic,xenial} installation - Upgrade the glib2.0 packages from {eoan,disco,bionic,xenial}-proposed - Upgrade the ibus packages from https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa - Install some IBus input method, e.g. ibus-libpinyin - Install some Qt application, e.g. Kate * Relogin (maybe reboot) * Add the input method to the input sources * Open the Qt app and try to input something using the IBus IM => Find that the transliteration works as expected [Regression Potential] The applicable patches origin from glib upstream: https://gitlab.gnome.org/GNOME/glib/merge_requests/1176 Consequently the changes have been reviewed by the glib maintainer, but also tested by the IBus maintainer, by me (gunnarhj), and - of course - the author Simon McVittie. The changes have been in Debian unstable since 2019-10-30. [Original description] Kubuntu Release 18.04.3 LTS Expected behavior: ibus continues working as before after applying security update 1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5. Observed behavior: ibus is not usable anymore in Qt applications. After updating ibus and the related packages ibus-gtk, ibus-gtk3, libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using shift-space no longer changes the selected input method and even when i switch to the mozc input method in a gtk application, i can not use it in any Qt applications. When starting qtconfig in a terminal, I also get the following message: Bus::open: Connect ibus failed! IBusInputContext::createInputContext: no connection to ibus-daemon This bug was not present in version 1.5.17-3ubuntu5 and I also confirmed that downgrading the packages to version 1.5.17-3ubuntu4 restores ibus functionality in Qt applications. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ibus 1.5.17-3ubuntu5.1 ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: KDE Date: Sat Sep 21 07:58:56 2019 InstallationDate: Installed on 2019-06-28 (84 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: ibus UpgradeStatus: No upgrade log present (proba
[Touch-packages] [Bug 1850932] Re: [SRU] Backport 2.62.2-2
Hello Iain, or anyone else affected, Accepted glib2.0 into eoan-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/glib2.0/2.62.2-2~ubuntu19.10.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-eoan to verification-done-eoan. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-eoan. In either case, 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: glib2.0 (Ubuntu Eoan) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-eoan -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1850932 Title: [SRU] Backport 2.62.2-2 Status in glib2.0 package in Ubuntu: Fix Released Status in glib2.0 source package in Eoan: Fix Committed Bug description: [ Description ] I'm creating this bug report to have a place to describe the proposed backport of glib2.0 2.62.2-2 from focal. The main purpose of this backport (as opposed to -1) is to fix bug #1844853. But there are several other changes. There are many cherry-picks to improve the testsuite's reliability. At the time of upload they weren't in the stable branch, but now they almost all are. These commits can be considered to be tested under https://wiki.ubuntu.com/StableReleaseUpdates/GNOME The two that are not are: commit 2b1e706b2f0007982f4fe6a70734d4490e4093a3 Author: Simon McVittie Date: Tue Oct 29 16:27:53 2019 + gdbus-server-auth test: Create temporary directory for Unix socket This avoids failure to listen on the given address on non-Linux Unix kernels, where abstract sockets do not exist and so unix:tmpdir is equivalent to unix:dir. To avoid bugs like this one recurring, run most of these tests using the unix:dir address type, where Linux is equivalent to other Unix kernels; just do one unix:tmpdir test, to check that we still interoperate with libdbus when using abstract sockets on Linux. Resolves: GNOME/glib#1920 Fixes: 9f962ebe "Add a test for GDBusServer authentication" Signed-off-by: Simon McVittie commit 9f962ebeac1d67223579ad0d261c4c8215f7c427 Author: Simon McVittie Date: Fri Oct 11 19:02:55 2019 +0100 Add a test for GDBusServer authentication In particular, if libbdus is available, we test interoperability with a libdbus client: see GNOME/glib#1831. Because that issue describes a race condition, we do each test repeatedly to try to hit the failing case. Signed-off-by: Simon McVittie which are both testsuite fixes. There are some additional non-upstream changes: * d/p/debian/mimeapps-test-Mark-as-flaky.patch: Drop patch, hopefully no longer needed with #941550 fixed * d/p/debian/taptestrunner-Stop-looking-like-an-executable-script.patch: Make taptestrunner non-executable to avoid a Lintian warning the former is again a testsuite fix. The latter is a fix to the test runner, which is relevant for the installed tests (run via autopkgtest) but not otherwise. [ QA ] The testsuite fixes will verify themselves during the build and autopkgtest. [ Regression potential ] all test fixes> Build failures or autopkgtest failures. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1850932/+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