[Touch-packages] [Bug 1733334] Re: ATK doesn't list all children for GtkNotebook when tab contains more than label
** Changed in: gtk Status: Unknown => Confirmed ** Changed in: gtk Importance: Unknown => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/174 Title: ATK doesn't list all children for GtkNotebook when tab contains more than label Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When gtknotebook have got a tab page that contains something more than label we can't access those elements in accerciser. For example create a GtkNotebook and put a Bo that contains label and an image into the tab page, then observe the hierarchy in the accercisser. Those elements won't be show and what's worse if the image is used to close the tab, there will be no way to do this. more info can be found here: https://bugzilla.gnome.org/show_bug.cgi?id=790496 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/174/+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 1753043] [NEW] package apt-utils 1.2.25 failed to install/upgrade: package apt-utils is already installed and configured
Public bug reported: This bug was reported during the time of update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apt-utils 1.2.25 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Sat Mar 3 11:42:06 2018 DuplicateSignature: package:apt-utils:1.2.25 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package libapt-inst2.0:amd64 (--configure): package libapt-inst2.0:amd64 is already installed and configured ErrorMessage: package apt-utils is already installed and configured InstallationDate: Installed on 2018-01-31 (30 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: apt Title: package apt-utils 1.2.25 failed to install/upgrade: package apt-utils is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: apt (Ubuntu) Importance: Undecided Status: New ** Tags: already-installed amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1753043 Title: package apt-utils 1.2.25 failed to install/upgrade: package apt-utils is already installed and configured Status in apt package in Ubuntu: New Bug description: This bug was reported during the time of update. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: apt-utils 1.2.25 ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.1-0ubuntu2.15 AptdaemonVersion: 1.1.1+bzr982-0ubuntu14 Architecture: amd64 Date: Sat Mar 3 11:42:06 2018 DuplicateSignature: package:apt-utils:1.2.25 Processing triggers for dbus (1.10.6-1ubuntu3.3) ... dpkg: error processing package libapt-inst2.0:amd64 (--configure): package libapt-inst2.0:amd64 is already installed and configured ErrorMessage: package apt-utils is already installed and configured InstallationDate: Installed on 2018-01-31 (30 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: apt Title: package apt-utils 1.2.25 failed to install/upgrade: package apt-utils is already installed and configured UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1753043/+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 1743750] Re: [18.04 FEAT] Add support for CPACF enhancements to openssl
This bug was fixed in the package openssl - 1.1.0g-2ubuntu2 --- openssl (1.1.0g-2ubuntu2) bionic; urgency=medium * s390x: Add support for CPACF enhancements to openssl, for IBM z14. LP: #1743750 -- Dimitri John Ledkov Tue, 27 Feb 2018 13:01:19 + ** Changed in: openssl (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1743750 Title: [18.04 FEAT] Add support for CPACF enhancements to openssl Status in Ubuntu on IBM z Systems: Fix Committed Status in openssl package in Ubuntu: Fix Released Status in openssl1.0 package in Ubuntu: Fix Released Bug description: Add support for CPACF enhancements to openssl Support new CPACF instructions to accelerate the GCM mode of operation as available with IBM z14 and later hardware This feature implements the instruction support in openssl ! A prereq within IBMCA is already available with ibmca 1.4.0. Already requested for 17.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1743750/+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 1753042] [NEW] package python3-apt 1.1.0~beta1ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: don't install properly ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-apt 1.1.0~beta1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Feb 28 23:52:31 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-08-16 (199 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: python-apt Title: package python3-apt 1.1.0~beta1ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: python-apt (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check third-party-packages xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to python-apt in Ubuntu. https://bugs.launchpad.net/bugs/1753042 Title: package python3-apt 1.1.0~beta1ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 Status in python-apt package in Ubuntu: New Bug description: don't install properly ProblemType: Package DistroRelease: Ubuntu 16.04 Package: python3-apt 1.1.0~beta1ubuntu0.16.04.1 ProcVersionSignature: Ubuntu 4.4.0-116.140-generic 4.4.98 Uname: Linux 4.4.0-116-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Wed Feb 28 23:52:31 2018 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2017-08-16 (199 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: python-apt Title: package python3-apt 1.1.0~beta1ubuntu0.16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1753042/+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 1736618] Re: debconf: Switch GNOME frontend to gtk3
** Changed in: debconf Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to debconf in Ubuntu. https://bugs.launchpad.net/bugs/1736618 Title: debconf: Switch GNOME frontend to gtk3 Status in Debconf: Fix Released Status in debconf package in Ubuntu: Fix Released Bug description: Please switch debconf's GNOME backend to gtk3. debconf's GNOME backend is one of the last 3 things to pull gtk2 in to a default Ubuntu 18.04 install (without extra input methods). The other two are Firefox and Thunderbird which have fixes in progress. To manage notifications about this bug go to: https://bugs.launchpad.net/debconf/+bug/1736618/+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 1718931] Re: No VPN autoconnect
** Changed in: network-manager Status: Unknown => Confirmed ** Changed in: network-manager Importance: Unknown => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1718931 Title: No VPN autoconnect Status in NetworkManager: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: When setting up VPN to auto connect with wifi (done through nm- connection-editor) the wifi never manages to connect. However if I unselect the auto connect option while it is attempting a reconnection then it manages to connect to both (wifi and VPN). Doing the connection manually also poses no issues ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: network-manager 1.8.2-1ubuntu8 ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1 Uname: Linux 4.13.0-11-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Sep 22 13:15:55 2017 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2017-09-09 (12 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908) IpRoute: default via 192.168.0.1 dev wlp6s0 proto static metric 600 169.254.0.0/16 dev wlp6s0 scope link metric 1000 192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 metric 600 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp6s0 wifi connected /org/freedesktop/NetworkManager/Devices/2 VM5055940 85b8f881-7ed9-477a-9c39-9afb5a40bda9 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.8.2connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/network-manager/+bug/1718931/+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 1752578] Re: Evolution 3.27/3.28 transition
** Changed in: evolution-data-server (Ubuntu) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to evolution-data-server in Ubuntu. https://bugs.launchpad.net/bugs/1752578 Title: Evolution 3.27/3.28 transition Status in evolution package in Ubuntu: New Status in evolution-data-server package in Ubuntu: Fix Committed Status in evolution-ews package in Ubuntu: New Bug description: The Ubuntu Desktop Team would like to update evolution-data-server, evolution, and evolution-ews to 3.27.91 in preparation for evolution 3.28 (expected release March 12). Evolution bumped its sonames so we'll need a transition. Trackers = https://people.canonical.com/~ubuntu-archive/transitions/html/evolution-data-server.html https://release.debian.org/transitions/html/auto-evolution-data- server.html Successfully staged at https://launchpad.net/~jbicha/+archive/ubuntu/tempeds/+packages Justification = This transition was ready two weeks ago, but we wanted to do one major GNOME transition at a time. libgweather transition went smoothly. gnome-desktop3 got entangled with some other incomplete transitions (in particular, mesa/libglvnd). A Qt transition and a kdepim transition the week of 18.04 Feature Freeze made it impossible for those transitions to clear before Feature Freeze. We could have uploaded evolution now to avoid paperwork, but it feels like it would be smoother to be a bit more patient and do this soon after Feature Freeze. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1752578/+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 1672120] Re: package click-apparmor 0.3.17 failed to install/upgrade: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました
I use 17.10 now. And, I don't see this error messages. I think this problem is solved. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to click-apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1672120 Title: package click-apparmor 0.3.17 failed to install/upgrade: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました Status in click-apparmor package in Ubuntu: Incomplete Bug description: I login my account ProblemType: Package DistroRelease: Ubuntu 16.10 Package: click-apparmor 0.3.17 ProcVersionSignature: Ubuntu 4.8.0-41.44-generic 4.8.17 Uname: Linux 4.8.0-41-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Sun Mar 12 14:02:19 2017 ErrorMessage: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました InstallationDate: Installed on 2016-07-17 (237 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64(20160426.1) RelatedPackageVersions: dpkg 1.18.10ubuntu1 apt 1.3.4 SourcePackage: click-apparmor Title: package click-apparmor 0.3.17 failed to install/upgrade: サブプロセス インストール済みの pre-removal スクリプト はエラー終了ステータス 1 を返しました UpgradeStatus: Upgraded to yakkety on 2016-10-14 (148 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/click-apparmor/+bug/1672120/+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 1037411] Re: [regression][DRI] SubBuffer rendering is much slower in compiz 0.9.8.0 than it was in 0.9.7
** Changed in: mesa Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1037411 Title: [regression][DRI] SubBuffer rendering is much slower in compiz 0.9.8.0 than it was in 0.9.7 Status in Compiz: Fix Released Status in Mesa: Won't Fix Status in compiz package in Ubuntu: Fix Released Status in mesa package in Ubuntu: Triaged Status in compiz source package in Precise: Invalid Status in mesa source package in Precise: Invalid Status in compiz source package in Quantal: Fix Released Status in mesa source package in Quantal: Won't Fix Bug description: (This is no longer the primary performance regression bug for compiz 0.9.8.0. Look at bug 1024304 instead) TEST CASE: 1. CCSM > OpenGL > framebuffer_object = OFF vertex_buffer_object = OFF always_swap_buffers = OFF 2. Run graphics benchmarks. Expected: Similar results to compiz 0.9.7 Observed: Much lower results than compiz 0.9.7 ORIGINAL DESCRIPTION: Comparing graphics performance in a two-monitor configuration, I find the gles2 branch is 25-40% slower than trunk. This would not normally be surprising, however the slowdown REMAINS even when I turn off the new rendering features in the gles2 branch: framebuffer_object, vertex_buffer_object, always_swap_buffers So both branches should be using the same code path. But gles2 is still dramatically slower than trunk using two monitors. The good news is that this bug only affects benchmark results and seemingly a little lag. The physical frame rate achieved with two monitors still seems to be higher using the gles2 branch, meaning it drops from 60Hz to 30Hz much less often than trunk does. NOTE 1: This regression was allowed in compiz 0.9.8.0 because it is generally only visible in benchmark results. Meanwhile, physical compiz rendering performance (as reported by the compiz Benchmark plugin) is higher in compiz 0.9.8.0 than previous versions, in most cases. NOTE 2: If you're just worried about fullscreen game performance, then you don't need to wait for this bug to be resolved. You can get optimal graphics performance with unredirect mode. But see bug 980663 first. To manage notifications about this bug go to: https://bugs.launchpad.net/compiz/+bug/1037411/+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 1519778] Re: Single click opening of selected items in file-selector is confusing
** Changed in: gtk Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1519778 Title: Single click opening of selected items in file-selector is confusing Status in GTK+: Fix Released Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: Since the GNOME 3.18 upgrade I keep opening files by error in the gedit file-selector. It took me a while to understand, what's going on why sometime single click acts like double click it seems to be due to this change https://git.gnome.org/browse/gtk%2B/commit/?id=fb0a13b7 "file chooser: Allow activating without double-click Interpret a unmodified primary click on the selection like a double click. This makes it possible to activate a file or open a folder without using double-click." That has several issues: - the behaviour seems inconsistant, it's not easy to understand what's going on as an user (I first though my mouse buttons was having issues) - if you double click on a selected directory to browse it, it opens it with the first click then open an item directly in the directory, which is not what you want (seems https://bugzilla.gnome.org/show_bug.cgi?id=757950 was meant to address that but it doesn't here) - if you select an item, switch to another windows and click back on the file-selector to focus it and manage to hit the selected item then it's opened... I'm unsure what the issue the change was trying to address, if that's about touch devices maybe the behaviour shouldn't impact pointer devices? To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1519778/+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 1752472] Re: [ffe] Implement an Ubuntu Single Sign-on Provider
** Changed in: gnome-online-accounts Status: Unknown => Confirmed ** Changed in: gnome-online-accounts Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1752472 Title: [ffe] Implement an Ubuntu Single Sign-on Provider Status in gnome-online-accounts: Confirmed Status in gnome-online-accounts package in Ubuntu: New Bug description: Add an Ubuntu Single Sing-On provider in gnome-online-accounts. We plan to use this inside: 1) gnome-software 2) software-properties To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1752472/+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 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
Fixed for me. Thank you for your hard work!! -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 Status in libglvnd package in Ubuntu: Fix Released Status in mesa-demos package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Bug description: I just updated bionic and suddenly: * No 'Ubuntu on Wayland' login option. * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe (software rendering) WORKAROUND: sudo apt remove libegl1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Feb 24 13:59:46 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-12 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+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 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
This should be fixed now (or as soon as you get the pending updates). ** Changed in: libglvnd (Ubuntu) Status: Confirmed => Fix Released ** Changed in: mesa-demos (Ubuntu) Status: Confirmed => Invalid ** Changed in: mir (Ubuntu) Status: Confirmed => Invalid ** Changed in: mutter (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 Status in libglvnd package in Ubuntu: Fix Released Status in mesa-demos package in Ubuntu: Invalid Status in mir package in Ubuntu: Invalid Status in mutter package in Ubuntu: Invalid Bug description: I just updated bionic and suddenly: * No 'Ubuntu on Wayland' login option. * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe (software rendering) WORKAROUND: sudo apt remove libegl1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Feb 24 13:59:46 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-12 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+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 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
Nicolás, yes, we're waiting on libglvnd which is waiting on nvidia- graphics-driver-390 to be straightened out. Even though it's late Friday, it's being worked on now. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 Status in libglvnd package in Ubuntu: Confirmed Status in mesa-demos package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I just updated bionic and suddenly: * No 'Ubuntu on Wayland' login option. * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe (software rendering) WORKAROUND: sudo apt remove libegl1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Feb 24 13:59:46 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-12 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+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 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
Adding -proposed to sources works. Sent via the BlackBerry Hub for Android Original Message From: nicocarb...@gmail.com Sent: March 2, 2018 10:50 PM To: sla...@naprave.net Reply-to: 1751...@bugs.launchpad.net Subject: [Bug 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 I just got the whole mesa stack updated, including libgl1-mesa-glx (ver 18.0.0~rc4-1ubuntu3) and I still don't have gl acceleration, only llvm pipe. Are there any other packages on hold? -- You received this bug notification because you are subscribed to a duplicate bug report (1752343). https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 Status in libglvnd package in Ubuntu: Confirmed Status in mesa-demos package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I just updated bionic and suddenly: * No 'Ubuntu on Wayland' login option. * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe (software rendering) WORKAROUND: sudo apt remove libegl1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Feb 24 13:59:46 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-12 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+subscriptions -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 Status in libglvnd package in Ubuntu: Confirmed Status in mesa-demos package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I just updated bionic and suddenly: * No 'Ubuntu on Wayland' login option. * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe (software rendering) WORKAROUND: sudo apt remove libegl1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Feb 24 13:59:46 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-12 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+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 1752844] Re: Line drawing bug in applications using opengl 1
Tested 17.3.3, no success. The artifacts appeared after the #1735594 fix, so they may be specific to i965. My computer graphics indicate "Mobile Intel® GM45 Express Chipset". I found that the game titanion looks as expected when the window is resized to 960x720 or greater. Inspecting the source I found the game adjusts the line width at window resize while the other games keep it at 1 or 2, so I believe the driver is drawing the lines thinner than it should. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752844 Title: Line drawing bug in applications using opengl 1 Status in mesa package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04.3, as from the update fixing https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594, the line rendering in applications using Opengl 1 is incorrect. Blender and various games by Kenta Cho (tumiki-figthers, torus- trooper, parsec47, titanion) are affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752844/+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 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
I just got the whole mesa stack updated, including libgl1-mesa-glx (ver 18.0.0~rc4-1ubuntu3) and I still don't have gl acceleration, only llvm pipe. Are there any other packages on hold? -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 Status in libglvnd package in Ubuntu: Confirmed Status in mesa-demos package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I just updated bionic and suddenly: * No 'Ubuntu on Wayland' login option. * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe (software rendering) WORKAROUND: sudo apt remove libegl1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Feb 24 13:59:46 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-12 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+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 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)
That looks good. My only comment now is, I see you've switched cgmanager from Suggests: to Depends:...is that *really* needed to fix a memleak here? i.e., if you uninstall cgmanager and re-run your memleak tests, does mem still leak? While changing it to a Depends: isn't impossible, I'd prefer to do that only if there is a specific reason to do so that can't be easily fixed some other way. -- 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/1750013 Title: systemd-logind: memory leaks on session's connections (trusty-only) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: Below the SRU request form. Please refer to the Original Description to a more comprehensive explanation of the problem observed. [Impact] * systemd-logind tool is leaking memory at each session connected. The issues happens in systemd from Trusty (14.04) only. * Three issues observed: - systemd-logind is leaking entire sessions, i.e, the sessions are not feeed after they're closed. In order to fix that, we proactively add the sessions to systemd garbage collector (gc) when they are closed. Also, part of the fix is to make cgmanager package a dependency. Refer to comment #1 to a more thorough explanation of the issue and the fix. - a small memory leak was observed in the session creation logic of systemd-logind. The fix for that is the addition of an appropriate free() call. Refer to comment #2 to more details on the issue and fix. - another small memory leak was observed in the cgmanager glue code of systemd-logind - this code is only present in this specific Ubuntu release of the package, due to necessary compatibility layer with upstart init system. The fix is to properly call free() in 2 functions. Refer to comment #3 to a deep exposition of the issue and the fix. [Test Case] * The basic test-case is to run the following loop from a remote machine: while true; do ssh "whoami"; done * It's possible to watch the increase in memory consumption from "systemd-logind" process in the target machine. One can use the "ps uax" command to verify the RSS of the process, or count its anonymous pages from /proc//smaps. [Regression Potential] * Since the fixes are small and not intrusive, the potential for regressions are low. More regression considerations on comments #1, #2 and #3 for each fix. * A potential small regressson is performance-wise, since now we add sessions to garbage collector proactively. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+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 1651278] Re: systemd-sysv-generator does not fully translate facilities to targets
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1651278 Title: systemd-sysv-generator does not fully translate facilities to targets Status in systemd: Fix Released Status in systemd package in Ubuntu: Confirmed Bug description: See the bug raised here: https://github.com/systemd/systemd/issues/4762 and fixed upstream here: https://github.com/systemd/systemd/commit/e932f5407ef5ad05d25d7dfefa4cda0fe81cc346 In short, given a sysv-init script with valid LSB headers, one of which defines Required-Start: $foo and given that a foo.target target exists and is enabled, I would expect to see After=foo.target in the generated unit. In practice (on all versions of systemd prior to the unreleased v233) no other facilities beyond the pre-defined facilities ($network, $local_fs, etc) will be used in generating the systemd wrapper for the old sysv init script. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1651278/+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 1718568] Re: dhclient-script fails to wait for link-local address
> Is there no other more reliable way to reproduce the case that's being fixed here sure yes, here's what i did; first, setup: -create VMs for the releases (T/X/A), managed by virsh (e.g. with uvt-kvm or whatever) -add a second interface to each of them, e.g.: $ virsh attach-interface lp1718568-artful network default --model virtio --persistent -set up another server/vm/container/whatever, connected to the same network as the test VM second interfaces, and install and configure isc- dhcp-server (or dnsmasq or whatever dhcpv6 server) on that to serve out dhcpv6 now on each release VM: -check the virsh interface you'll be using, e.g.: $ virsh domiflist lp1718568-artful Interface Type Source Model MAC --- vnet3 networkdefaultvirtio 52:54:00:3f:b9:ad vnet0 networkdefaultvirtio 52:54:00:bf:16:8a confirm which matches the test interface in the VM using mac; in my case it's vnet0. now, bring its link state down using virsh: $ virsh domif-setlink lp1718568-artful vnet0 down and ssh into the test VM (on its first, still working, default interface - or use virt-viewer or whatever) and test dhclient -6, making sure to first verify the test interface is down (i.e. that it doesn't already have a link-local addr): ubuntu@lp1718568-artful:~$ sudo ip a show ens7 3: ens7: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 52:54:00:bf:16:8a brd ff:ff:ff:ff:ff:ff ubuntu@lp1718568-artful:~$ sudo dhclient -v -6 ens7 Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ no link-local IPv6 address for ens7 If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. as expected (for this bug), that fails immediately. now, upgrade to the test version in my ppa https://launchpad.net/~ddstreet/+archive/ubuntu/lp1718568 ubuntu@lp1718568-artful:~$ dpkg -l | grep isc-dhcp ii isc-dhcp-client 4.3.5-3ubuntu2.2+hf1718568v20180302b1amd64DHCP client for automatically obtaining an IP address ii isc-dhcp-common 4.3.5-3ubuntu2.2+hf1718568v20180302b1amd64common manpages relevant to all of the isc-dhcp packages again, make sure the interface is down (no link-local addr) and try the new dhclient: ubuntu@lp1718568-artful:~$ sudo ip l set down dev ens7 ubuntu@lp1718568-artful:~$ sudo ip a show ens7 3: ens7: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 52:54:00:bf:16:8a brd ff:ff:ff:ff:ff:ff ubuntu@lp1718568-artful:~$ sudo dhclient -v -6 ens7 Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ now, instead of immediately exiting with error, it waits - this is where it's waiting for the interface to get a 'tentative' link-local address, and then complete dad to switch to normal link-local so dhcpv6 can begin. After only a few seconds (dhclient-script.linux defaults to 60 attempts, with 0.1 second delays between, so ~6 seconds of waiting) it will give up and exit as before: no link-local IPv6 address for ens7 If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging.. exiting. Ok, we verified the patch does force dhclient to wait for the link-local addr (even without any tentative addr); now bring the interface back down and re-test, but this time immediately switch back to the host and use virsh to bring the link state back up (before dhclient times out): ubuntu@lp1718568-artful:~$ sudo ip l set down dev ens7 ubuntu@lp1718568-artful:~$ sudo ip a show ens7 3: ens7: mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000 link/ether 52:54:00:bf:16:8a brd ff:ff:ff:ff:ff:ff ubuntu@lp1718568-artful:~$ sudo dhclient -v -6 ens7 Internet Systems Consortium DHCP Client 4.3.5 Copyright 2004-2016 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ now quickly in the host: $ virsh domif-setlink lp1718568-artful vnet0 up Device updated successfully and back in the test VM: Listening on Socket/ens7 Sending on Socket/ens7 PRC: Soliciting for leases (INIT). XMT: Forming Solicit, 0 ms elapsed. XMT: X-- IA_NA 00:bf:16:8a XMT: | X-- Request renew in +3600 XMT:
[Touch-packages] [Bug 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS
*** This bug is a duplicate of bug 1683383 *** https://bugs.launchpad.net/bugs/1683383 ** This bug has been marked a duplicate of bug 1683383 Keyboard layout change on hotkeys press instead of release and do not work well with shortcuts (reopen) -- 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/1720364 Title: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS Status in MATE Desktop: New Status in ubuntu-mate: New Status in X.Org X server: Confirmed Status in marco package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Status in xorg-hwe-16.04 package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: marco 1.18.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Fri Sep 29 16:18:02 2017 InstallationDate: Installed on 2017-08-26 (33 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: marco UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1720364/+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 1752971] [NEW] lightdm don't started
Public bug reported: can not download system does not start lgtdm I have to start with the startx command from the console ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.25.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 2 21:57:29 2018 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic third-party-packages -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lightdm in Ubuntu. https://bugs.launchpad.net/bugs/1752971 Title: lightdm don't started Status in lightdm package in Ubuntu: New Bug description: can not download system does not start lgtdm I have to start with the startx command from the console ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: lightdm 1.25.2-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: XFCE Date: Fri Mar 2 21:57:29 2018 SourcePackage: lightdm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1752971/+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 1085976] Re: Documentation has "FIXME" items that are unfixed
** Changed in: gtk Status: Unknown => Confirmed ** Changed in: gtk Importance: Unknown => Medium -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1085976 Title: Documentation has "FIXME" items that are unfixed Status in GTK+: Confirmed Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk+3.0 package in Debian: Confirmed Bug description: The Ubuntu package libgtk-3-doc supplies the items of interest... In the directory /usr/share/doc/libgtk-3-doc/gtk3 there are 3 files that contain FIXME content In that directory: # grep FIXME * GtkApplication.html:FIXME: MISSING XINCLUDE CONTENT GtkBuilder.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html: FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT # I am just starting with GTK+ and Glade, so having this instead of the first code sample in the gtk-getting-started page is a show-stopper. I suggest it's as urgent as documentation bugs get. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgtk-3-doc 3.4.2-0ubuntu0.5 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 Date: Mon Dec 3 05:59:17 2012 Dependencies: InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True PackageArchitecture: all SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1085976/+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 1747744] Re: [regression] Video playback in totem is corrupted in X11
This bug was fixed in the package mesa - 18.0.0~rc4-1ubuntu3 --- mesa (18.0.0~rc4-1ubuntu3) bionic; urgency=medium * dont-enable-10bpc-by-default.diff: Replace the drirc hack, just flip the default to not enable 10bpc configs by default for gallium drivers. (LP: #1752123) -- Timo Aaltonen Wed, 28 Feb 2018 19:34:58 +0200 ** Changed in: mesa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1747744 Title: [regression] Video playback in totem is corrupted in X11 Status in Mesa: Fix Released Status in mesa package in Ubuntu: Fix Released Status in totem package in Ubuntu: Confirmed Bug description: WORKAROUND (1): Install these two together: https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu2/+build/13697262/+files/libgl1-mesa-glx_17.2.4-0ubuntu2_amd64.deb https://launchpad.net/ubuntu/+source/mesa/17.2.4-0ubuntu2/+build/13697262/+files/libglapi-mesa_17.2.4-0ubuntu2_amd64.deb WORKAROUND (2): sudo apt remove gstreamer1.0-vaapi WORKAROUND (3): Log in to "Ubuntu on Wayland" instead of "Ubuntu". --- Test case Log inti xorg session Install gstreamer1.0-vaapi plugin Play a supported video (- h.264/avc in .mp4, .mkv or .mov would suffice Expected: hardware decoded playback What happens: totally corrupted screen, see screenshots Does work ok in a wayland session $ vainfo libva info: VA-API version 1.0.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so libva info: Found init function __vaDriverInit_1_0 libva info: va_openDriver() returns 0 vainfo: VA-API version: 1.0 (libva 2.0.0) vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0 vainfo: Supported profile and entrypoints VAProfileMPEG2Simple: VAEntrypointVLD VAProfileMPEG2Simple: VAEntrypointEncSlice VAProfileMPEG2Main : VAEntrypointVLD VAProfileMPEG2Main : VAEntrypointEncSlice VAProfileH264ConstrainedBaseline: VAEntrypointVLD VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice VAProfileH264Main : VAEntrypointVLD VAProfileH264Main : VAEntrypointEncSlice VAProfileH264High : VAEntrypointVLD VAProfileH264High : VAEntrypointEncSlice VAProfileH264MultiviewHigh : VAEntrypointVLD VAProfileH264MultiviewHigh : VAEntrypointEncSlice VAProfileH264StereoHigh : VAEntrypointVLD VAProfileH264StereoHigh : VAEntrypointEncSlice VAProfileVC1Simple : VAEntrypointVLD VAProfileVC1Main: VAEntrypointVLD VAProfileVC1Advanced: VAEntrypointVLD VAProfileNone : VAEntrypointVideoProc VAProfileJPEGBaseline : VAEntrypointVLD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.8-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Feb 6 14:43:57 2018 InstallationDate: Installed on 2018-02-06 (0 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gstreamer-vaapi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mesa/+bug/1747744/+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 1743750] Re: [18.04 FEAT] Add support for CPACF enhancements to openssl
This bug was fixed in the package openssl1.0 - 1.0.2n-1ubuntu4 --- openssl1.0 (1.0.2n-1ubuntu4) bionic; urgency=medium * s390x: Add support for CPACF enhancements to openssl, for IBM z14. LP: #1743750 -- Dimitri John Ledkov Wed, 28 Feb 2018 14:52:10 + ** Changed in: openssl1.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssl in Ubuntu. https://bugs.launchpad.net/bugs/1743750 Title: [18.04 FEAT] Add support for CPACF enhancements to openssl Status in Ubuntu on IBM z Systems: Fix Committed Status in openssl package in Ubuntu: Fix Committed Status in openssl1.0 package in Ubuntu: Fix Released Bug description: Add support for CPACF enhancements to openssl Support new CPACF instructions to accelerate the GCM mode of operation as available with IBM z14 and later hardware This feature implements the instruction support in openssl ! A prereq within IBMCA is already available with ibmca 1.4.0. Already requested for 17.10. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1743750/+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 1752123] Re: Force 8bit RGB config
This bug was fixed in the package mesa - 18.0.0~rc4-1ubuntu3 --- mesa (18.0.0~rc4-1ubuntu3) bionic; urgency=medium * dont-enable-10bpc-by-default.diff: Replace the drirc hack, just flip the default to not enable 10bpc configs by default for gallium drivers. (LP: #1752123) -- Timo Aaltonen Wed, 28 Feb 2018 19:34:58 +0200 ** Changed in: mesa (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752123 Title: Force 8bit RGB config Status in cogl package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Fix Released Status in mutter package in Ubuntu: Triaged Bug description: New mesa supports 10bit RGB configs, and this causes issues with cogl/mutter which get a random EGLConfig that breaks some autopkgtests. To fix this this merge request is needed for mutter https://gitlab.gnome.org/GNOME/mutter/merge_requests/36 and a similar one for cogl. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cogl/+bug/1752123/+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 1693038] Re: needs to support restart on Lubuntu and Xubuntu
** Branch linked: lp:~brian-murray/software-properties/more-restart -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1693038 Title: needs to support restart on Lubuntu and Xubuntu Status in software-properties package in Ubuntu: Triaged Bug description: The fix for bug 1241210 only works in gnome-session based sessions. Let's make sure that the driver restart button works on Xubuntu and Lubuntu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1693038/+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 1751667] Re: classic snap does not run on live session
This is now merged in 2.32. Please see https://forum.snapcraft.io/t /confined-snaps-dont-work-on-live-images-due-to-apparmor-path- mapping/3767/9 if you want to check it out for yourself. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apparmor in Ubuntu. https://bugs.launchpad.net/bugs/1751667 Title: classic snap does not run on live session Status in apparmor package in Ubuntu: Invalid Status in snapd package in Ubuntu: In Progress Bug description: I'm testing Ubuntu Budgie's classic snap called "ubuntu-budgie- welcome" which is available in the beta channel. Ubuntu Budgie 18.04 daily ISO 25/02/2018 The snap works just fine on a normal install. However this classic snap fails on the Ubuntu Budgie live session. As snaps become more prevalent - snaps - including classic snaps should work on live sessions. For Ubuntu Budgie, the classic snap is very important because it presents the user vital info about the distro and instructions on how to install. Copying the .desktop launcher from the menu I see the following issue in a terminal: ubuntu-budgie@ubuntu-budgie:~$ env BAMF_DESKTOP_FILE_HINT=/var/lib/snapd/desktop/applications/ubuntu-budgie-welcome_budgie-welcome.desktop /snap/bin/ubuntu-budgie-welcome.budgie-welcome %U snap-confine has elevated permissions and is not confined but should be. Refusing to continue to avoid permission escalation attacks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: snapd 2.31.1+18.04 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CasperVersion: 1.388 CurrentDesktop: Budgie:GNOME Date: Sun Feb 25 23:28:38 2018 LiveMediaBuild: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180225) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: snapd UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1751667/+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 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)
** Patch added: "debdiff v2" https://bugs.launchpad.net/ubuntu/artful/+source/systemd/+bug/1750013/+attachment/5067376/+files/lp1750013-trusty_v2.debdiff -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1750013 Title: systemd-logind: memory leaks on session's connections (trusty-only) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: Below the SRU request form. Please refer to the Original Description to a more comprehensive explanation of the problem observed. [Impact] * systemd-logind tool is leaking memory at each session connected. The issues happens in systemd from Trusty (14.04) only. * Three issues observed: - systemd-logind is leaking entire sessions, i.e, the sessions are not feeed after they're closed. In order to fix that, we proactively add the sessions to systemd garbage collector (gc) when they are closed. Also, part of the fix is to make cgmanager package a dependency. Refer to comment #1 to a more thorough explanation of the issue and the fix. - a small memory leak was observed in the session creation logic of systemd-logind. The fix for that is the addition of an appropriate free() call. Refer to comment #2 to more details on the issue and fix. - another small memory leak was observed in the cgmanager glue code of systemd-logind - this code is only present in this specific Ubuntu release of the package, due to necessary compatibility layer with upstart init system. The fix is to properly call free() in 2 functions. Refer to comment #3 to a deep exposition of the issue and the fix. [Test Case] * The basic test-case is to run the following loop from a remote machine: while true; do ssh "whoami"; done * It's possible to watch the increase in memory consumption from "systemd-logind" process in the target machine. One can use the "ps uax" command to verify the RSS of the process, or count its anonymous pages from /proc//smaps. [Regression Potential] * Since the fixes are small and not intrusive, the potential for regressions are low. More regression considerations on comments #1, #2 and #3 for each fix. * A potential small regressson is performance-wise, since now we add sessions to garbage collector proactively. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+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 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)
Dan, please let me know if the debdiff v2 above addresses your concern and if it's properly following your suggestion. I tested the modification and it's working fine. Thanks, Guilherme -- 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/1750013 Title: systemd-logind: memory leaks on session's connections (trusty-only) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: Below the SRU request form. Please refer to the Original Description to a more comprehensive explanation of the problem observed. [Impact] * systemd-logind tool is leaking memory at each session connected. The issues happens in systemd from Trusty (14.04) only. * Three issues observed: - systemd-logind is leaking entire sessions, i.e, the sessions are not feeed after they're closed. In order to fix that, we proactively add the sessions to systemd garbage collector (gc) when they are closed. Also, part of the fix is to make cgmanager package a dependency. Refer to comment #1 to a more thorough explanation of the issue and the fix. - a small memory leak was observed in the session creation logic of systemd-logind. The fix for that is the addition of an appropriate free() call. Refer to comment #2 to more details on the issue and fix. - another small memory leak was observed in the cgmanager glue code of systemd-logind - this code is only present in this specific Ubuntu release of the package, due to necessary compatibility layer with upstart init system. The fix is to properly call free() in 2 functions. Refer to comment #3 to a deep exposition of the issue and the fix. [Test Case] * The basic test-case is to run the following loop from a remote machine: while true; do ssh "whoami"; done * It's possible to watch the increase in memory consumption from "systemd-logind" process in the target machine. One can use the "ps uax" command to verify the RSS of the process, or count its anonymous pages from /proc//smaps. [Regression Potential] * Since the fixes are small and not intrusive, the potential for regressions are low. More regression considerations on comments #1, #2 and #3 for each fix. * A potential small regressson is performance-wise, since now we add sessions to garbage collector proactively. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+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 1651278] Re: systemd-sysv-generator does not fully translate facilities to targets
** Bug watch added: github.com/systemd/systemd/issues #4762 https://github.com/systemd/systemd/issues/4762 ** Also affects: systemd via https://github.com/systemd/systemd/issues/4762 Importance: Unknown Status: Unknown -- 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/1651278 Title: systemd-sysv-generator does not fully translate facilities to targets Status in systemd: Unknown Status in systemd package in Ubuntu: Confirmed Bug description: See the bug raised here: https://github.com/systemd/systemd/issues/4762 and fixed upstream here: https://github.com/systemd/systemd/commit/e932f5407ef5ad05d25d7dfefa4cda0fe81cc346 In short, given a sysv-init script with valid LSB headers, one of which defines Required-Start: $foo and given that a foo.target target exists and is enabled, I would expect to see After=foo.target in the generated unit. In practice (on all versions of systemd prior to the unreleased v233) no other facilities beyond the pre-defined facilities ($network, $local_fs, etc) will be used in generating the systemd wrapper for the old sysv init script. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1651278/+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 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS
** Changed in: xorg (Debian) Status: Unknown => New -- 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/1720364 Title: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS Status in MATE Desktop: New Status in ubuntu-mate: New Status in X.Org X server: Confirmed Status in marco package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Status in xorg-hwe-16.04 package in Ubuntu: Confirmed Status in xorg package in Debian: New Bug description: Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: marco 1.18.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Fri Sep 29 16:18:02 2017 InstallationDate: Installed on 2017-08-26 (33 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: marco UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1720364/+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 1085976] Re: Documentation has "FIXME" items that are unfixed
** Changed in: gtk+3.0 (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1085976 Title: Documentation has "FIXME" items that are unfixed Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Confirmed Status in gtk+3.0 package in Debian: Confirmed Bug description: The Ubuntu package libgtk-3-doc supplies the items of interest... In the directory /usr/share/doc/libgtk-3-doc/gtk3 there are 3 files that contain FIXME content In that directory: # grep FIXME * GtkApplication.html:FIXME: MISSING XINCLUDE CONTENT GtkBuilder.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html: FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT gtk-getting-started.html:FIXME: MISSING XINCLUDE CONTENT # I am just starting with GTK+ and Glade, so having this instead of the first code sample in the gtk-getting-started page is a show-stopper. I suggest it's as urgent as documentation bugs get. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: libgtk-3-doc 3.4.2-0ubuntu0.5 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic-pae 3.2.28 Uname: Linux 3.2.0-31-generic-pae i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu15 Architecture: i386 Date: Mon Dec 3 05:59:17 2012 Dependencies: InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 (20120817.3) MarkForUpload: True PackageArchitecture: all SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1085976/+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 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration
*** This bug is a duplicate of bug 1751414 *** https://bugs.launchpad.net/bugs/1751414 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: xorg (Ubuntu) Status: New => Confirmed -- 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/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration Status in xorg package in Ubuntu: Confirmed Bug description: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to llvmpipe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 3 00:58:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-02 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302) MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3V-A dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D3V-A dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752938/+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 972077] Re: apt repository disk format has race conditions
Hi. Just to re-iterate what Robie said. If you are seeing hashsum mismatch errors on 16.04 or later, something is wrong. That could be: a.) you have a proxy in your way, and the proxy cached a bad download. Apt is recognizing this and not installing it. That is working as designed. Note, that http proxies can be transparent (ie, no explicit configuration from you). Your ISP could be providing a proxy service that is simply broken. b.) You're using a mirror that does not support 'by-hash'. c.) there could be an error in the official ubuntu publishers. If they updated the Release file before content that it referenced was complete then that would cause apt to correctly identify the invalid data. So, what should you do? First, rule out the most likely problem... the proxy. If you have an explicitly configured proxy, then unconfigure it. You can probably verify there is a proxy in your path via: wget -q -S http://archive.ubuntu.com/ubuntu/dists/xenial/Release -O/dev/null If you see 'X-Cache' in the output, then there is a proxy between you and archive.ubuntu.com. If you are seeing this issue on Ubuntu 14.04, then that is not easily fixed. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/972077 Title: apt repository disk format has race conditions Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+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 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
it's better to enable -proposed and install libgl1-mesa-glx after apt update (and not do full dist-upgrade to avoid unrelated updates)... not sure if just that is enough, might need some other packages too the packages should migrate "soon", now that all the blockers have been sorted out -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 Status in libglvnd package in Ubuntu: Confirmed Status in mesa-demos package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I just updated bionic and suddenly: * No 'Ubuntu on Wayland' login option. * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe (software rendering) WORKAROUND: sudo apt remove libegl1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Feb 24 13:59:46 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-12 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+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 1648183] Re: Crackling and popping sound when using headphones
Chris (#38) - try to put your computer to sleep and wake up while listening to something. Issue still persists, but once you plug out and plug in your headset - it returns back to normal volume as expected. -- 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/1648183 Title: Crackling and popping sound when using headphones Status in alsa-driver package in Ubuntu: Confirmed Status in alsa-driver package in Arch Linux: New Bug description: Laptop is HP Pavilion - 15-au118tx. The laptop has B and O play and the output from speakers are just fine, when using headphones there is some kind of crackling and popping sound in both ears but prominently in the left ear. The issue happens only when the sound is played, if i reduce the PCM way low using alsamixer, the effect is minimized but the volume is also reduced. Increasing the volume in the panel increases the PCM as well. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6 Uname: Linux 4.8.0-30-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia ApportVersion: 2.20.3-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: antony 1719 F pulseaudio CurrentDesktop: Unity Date: Wed Dec 7 23:30:05 2016 InstallationDate: Installed on 2016-11-20 (17 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Headphone Out, Left Symptom_Type: Digital clip or distortion, or "overdriven" sound Title: [HP Pavilion Notebook, Realtek ALC295, Black Headphone Out, Left] Sound is distorted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2016 dmi.bios.vendor: Insyde dmi.bios.version: F.14 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8216 dmi.board.vendor: HP dmi.board.version: 83.13 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.14:bd07/19/2016:svnHP:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHP:rn8216:rvr83.13:cvnHP:ct10:cvrChassisVersion: dmi.product.name: HP Pavilion Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2016-12-07T23:12:52.939689 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1648183/+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 1752343] Re: Problem with DRI2 and GLX - bionic 18.04
*** This bug is a duplicate of bug 1751414 *** https://bugs.launchpad.net/bugs/1751414 ** This bug has been marked a duplicate of bug 1751414 [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752343 Title: Problem with DRI2 and GLX - bionic 18.04 Status in mesa package in Ubuntu: Invalid Bug description: I have encountered the problem described below, after some recent updates in my Kubuntu. After asking on "Answers" I was requested to open a bug, so I'm doing it. My problem was, that kwin stopped to show graphical effects. I'm using a laptop with Intel graphics - HD5500 After some log file search I've found, that probably the cause is shown in Xorg.0.log: Xorg.0.log:[ 7073.803] (II) AIGLX: Screen 0 is not DRI2 capable Xorg.0.log:[ 7073.803] (EE) AIGLX: reverting to software rendering After some googling, I have found article below, explaining possible root cause. I have used a solution proposed there, and after installing libegl-mesa0_18.0.0~rc4-1_amd64.deb and libgbm1_18.0.0~rc4-1_amd64.deb my problem disappeared. Link below describes details: https://bugs.freedesktop.org/show_bug.cgi?id=104928 Here is some output from my OS diag tools: lshw -C display *-display description: VGA compatible controller product: HD Graphics 5500 vendor: Intel Corporation physical id: 2 bus info: pci@:00:02.0 version: 09 width: 64 bits clock: 33MHz capabilities: msi pm vga_controller bus_master cap_list rom configuration: driver=i915 latency=0 resources: irq:47 memory:c000-c0ff memory:b000-bfff ioport:4000(size=64) memory:c-d lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu Bionic Beaver (development branch) Release: 18.04 Codename: bionic uname -a Linux hostname 4.15.0-10-generic #11-Ubuntu SMP Tue Feb 13 18:23:35 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux sudo dmidecode -t 1 # dmidecode 3.1 Getting SMBIOS data from sysfs. SMBIOS 2.7 present. Handle 0x0001, DMI type 1, 27 bytes System Information Manufacturer: FUJITSU Product Name: LIFEBOOK A555 Version: Serial Number: YM3M035369 UUID: CF0F380B-2089-E511-8681-742B62ED267C Wake-up Type: Power Switch SKU Number: Family: LIFEBOOK-FTS Best Regards, Marek To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752343/+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 1752938] Re: Upgrading Ubuntu 18.04 disables GPU hardware acceleration
*** This bug is a duplicate of bug 1751414 *** https://bugs.launchpad.net/bugs/1751414 ** This bug has been marked a duplicate of bug 1751414 [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 -- 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/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration Status in xorg package in Ubuntu: New Bug description: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to llvmpipe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 3 00:58:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-02 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302) MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3V-A dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D3V-A dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1752938/+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 1752953] [NEW] RM: obsolete product
Public bug reported: libhybris was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:libhybris No reverse dependencies found $ reverse-depends -b src:libhybris No reverse dependencies found ** Affects: libhybris (Ubuntu) Importance: Undecided Status: Triaged ** Tags: u8rm ** Changed in: libhybris (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libhybris in Ubuntu. https://bugs.launchpad.net/bugs/1752953 Title: RM: obsolete product Status in libhybris package in Ubuntu: Triaged Bug description: libhybris was a component of Ubuntu Phone which is no longer developed. Please remove this package from the Ubuntu Archive. $ reverse-depends src:libhybris No reverse dependencies found $ reverse-depends -b src:libhybris No reverse dependencies found To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libhybris/+bug/1752953/+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 1752928] [NEW] [FFe] GNOME 3.28
On Fri, Mar 02, 2018 at 04:54:51PM -, Launchpad Bug Tracker wrote: > You have been subscribed to a public bug by Jeremy Bicha (jbicha): > > Feature Freeze Justification > > Evolution was delayed to not intertangle transitions. > gnome-shell was released late upstream. > gnome-control-center & gnome-shell were waiting for a subject matter expert > to return from holiday. > Shotwell got overlooked but plans to release at the same time as GNOME. > > GNOME prefers us to not mix and match components from different versions > as much as possible. > > GNOME 3.28.0 release is just over a week away > > > Affected Packages > - > evolution transition LP: #1752578 > gnome-control-center and gnome-settings-daemon LP: #1750174 > gnome-shell and mutter LP: #1751070 > > gnome-session > shotwell > > gnome-games, retro-gtk & libmanette (libmanette released yesterday with > updated library name, waiting on new retro-gtk release expected any day) The desktop team wants GNOME 3.28 in 18.04, so +1, let's get it done as soon as we can though. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1752928 Title: [FFe] GNOME 3.28 Status in ubuntu-meta package in Ubuntu: New Bug description: Feature Freeze Justification Evolution was delayed to not intertangle transitions. gnome-shell was released late upstream. gnome-control-center & gnome-shell were waiting for a subject matter expert to return from holiday. Shotwell got overlooked but plans to release at the same time as GNOME. GNOME prefers us to not mix and match components from different versions as much as possible. GNOME 3.28.0 release is just over a week away Affected Packages - evolution transition LP: #1752578 gnome-control-center and gnome-settings-daemon LP: #1750174 gnome-shell and mutter LP: #1751070 gnome-session shotwell gnome-games, retro-gtk & libmanette (libmanette released yesterday with updated library name, waiting on new retro-gtk release expected any day) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1752928/+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 1742946] Re: "gio monitor" does not work
** Changed in: glib Status: Unknown => Fix Released ** Changed in: glib Importance: Unknown => Medium -- 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/1742946 Title: "gio monitor" does not work Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Bug description: # ls -l /etc/adduser.conf -rw-r--r-- 1 root root 2981 Mar 11 2012 /etc/adduser.conf # gio monitor file:///etc/adduser.conf gio: No locations given Usage: gio monitor [OPTION…] [LOCATION...] Monitor files or directories for changes. Options: -d, --dir=LOCATIONMonitor a directory (default: depends on type) -f, --file=LOCATION Monitor a file (default: depends on type) -D, --direct=LOCATION Monitor a file directly (notices changes made via hardlinks) -s, --silent=LOCATION Monitors a file directly, but doesn’t report changes -n, --no-movesReport moves and renames as simple deleted/created events -m, --mounts Watch for mount events ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libglib2.0-bin 2.54.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Fri Jan 12 14:29:42 2018 InstallationDate: Installed on 2012-03-12 (2131 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120311) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/tcsh SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1742946/+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 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
I tried removing the package from recovery mode as root, it would not remove libegl1. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 Status in libglvnd package in Ubuntu: Confirmed Status in mesa-demos package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I just updated bionic and suddenly: * No 'Ubuntu on Wayland' login option. * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe (software rendering) WORKAROUND: sudo apt remove libegl1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Feb 24 13:59:46 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-12 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+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 1752722] Re: systemd 237 reports incorrect state when drop-in present
upstream fix: https://github.com/systemd/systemd/pull/8330 ** Changed in: systemd (Ubuntu) Status: Confirmed => Triaged ** Changed in: systemd (Ubuntu) Importance: Undecided => High ** Also affects: systemd (Ubuntu Bionic) Importance: High Status: Triaged -- 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/1752722 Title: systemd 237 reports incorrect state when drop-in present Status in systemd: Fix Released Status in systemd package in Ubuntu: Triaged Status in systemd source package in Bionic: Triaged Bug description: Raised this upstream: https://github.com/systemd/systemd/issues/8328 In short, in systemd 237 as it ships with Bionic, if a unit has a drop-in present but has been masked, systemctl is-enabled and systemctl list-unit-files report incorrect state, showing the units as enabled rather than masked. This works as-expected in systemd 229 under Xenial. I have not tested under systemd 234 in artful so I cannot say for sure exactly when this was introduced, but will spin up a quick test to see if this also exists under systemd 234. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1752722/+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 1752722] Re: systemd 237 reports incorrect state when drop-in present
** Changed in: systemd Status: Unknown => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1752722 Title: systemd 237 reports incorrect state when drop-in present Status in systemd: Fix Released Status in systemd package in Ubuntu: Triaged Status in systemd source package in Bionic: Triaged Bug description: Raised this upstream: https://github.com/systemd/systemd/issues/8328 In short, in systemd 237 as it ships with Bionic, if a unit has a drop-in present but has been masked, systemctl is-enabled and systemctl list-unit-files report incorrect state, showing the units as enabled rather than masked. This works as-expected in systemd 229 under Xenial. I have not tested under systemd 234 in artful so I cannot say for sure exactly when this was introduced, but will spin up a quick test to see if this also exists under systemd 234. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1752722/+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 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)
Dan, really well-observed! Thanks for the suggestion, it makes total sense. I'll update the approach: instead of using session_remove_fifo() to add the session on GC, I'll use the DBus handler itself. After testing, I'll submit a debdiff_v2 here. Thanks, Guilherme -- 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/1750013 Title: systemd-logind: memory leaks on session's connections (trusty-only) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: Below the SRU request form. Please refer to the Original Description to a more comprehensive explanation of the problem observed. [Impact] * systemd-logind tool is leaking memory at each session connected. The issues happens in systemd from Trusty (14.04) only. * Three issues observed: - systemd-logind is leaking entire sessions, i.e, the sessions are not feeed after they're closed. In order to fix that, we proactively add the sessions to systemd garbage collector (gc) when they are closed. Also, part of the fix is to make cgmanager package a dependency. Refer to comment #1 to a more thorough explanation of the issue and the fix. - a small memory leak was observed in the session creation logic of systemd-logind. The fix for that is the addition of an appropriate free() call. Refer to comment #2 to more details on the issue and fix. - another small memory leak was observed in the cgmanager glue code of systemd-logind - this code is only present in this specific Ubuntu release of the package, due to necessary compatibility layer with upstart init system. The fix is to properly call free() in 2 functions. Refer to comment #3 to a deep exposition of the issue and the fix. [Test Case] * The basic test-case is to run the following loop from a remote machine: while true; do ssh "whoami"; done * It's possible to watch the increase in memory consumption from "systemd-logind" process in the target machine. One can use the "ps uax" command to verify the RSS of the process, or count its anonymous pages from /proc//smaps. [Regression Potential] * Since the fixes are small and not intrusive, the potential for regressions are low. More regression considerations on comments #1, #2 and #3 for each fix. * A potential small regressson is performance-wise, since now we add sessions to garbage collector proactively. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+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 1752722] Re: systemd 237 reports incorrect state when drop-in present
** Bug watch added: github.com/systemd/systemd/issues #8328 https://github.com/systemd/systemd/issues/8328 ** Also affects: systemd via https://github.com/systemd/systemd/issues/8328 Importance: Unknown Status: Unknown -- 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/1752722 Title: systemd 237 reports incorrect state when drop-in present Status in systemd: Fix Released Status in systemd package in Ubuntu: Triaged Status in systemd source package in Bionic: Triaged Bug description: Raised this upstream: https://github.com/systemd/systemd/issues/8328 In short, in systemd 237 as it ships with Bionic, if a unit has a drop-in present but has been masked, systemctl is-enabled and systemctl list-unit-files report incorrect state, showing the units as enabled rather than masked. This works as-expected in systemd 229 under Xenial. I have not tested under systemd 234 in artful so I cannot say for sure exactly when this was introduced, but will spin up a quick test to see if this also exists under systemd 234. To manage notifications about this bug go to: https://bugs.launchpad.net/systemd/+bug/1752722/+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 1752722] Re: systemd 237 reports incorrect state when drop-in present
It looks like this was fixed upstream and it would be fantastic if this could make it into Bionic before anything is frozen. -- 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/1752722 Title: systemd 237 reports incorrect state when drop-in present Status in systemd package in Ubuntu: Confirmed Bug description: Raised this upstream: https://github.com/systemd/systemd/issues/8328 In short, in systemd 237 as it ships with Bionic, if a unit has a drop-in present but has been masked, systemctl is-enabled and systemctl list-unit-files report incorrect state, showing the units as enabled rather than masked. This works as-expected in systemd 229 under Xenial. I have not tested under systemd 234 in artful so I cannot say for sure exactly when this was introduced, but will spin up a quick test to see if this also exists under systemd 234. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1752722/+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 1752705] Re: When run from systemd-nspawn, installation of mysql-server fails because postinst fails to shut down server
Thanks for pointing out the changes to server start/stop, Robie. Adding the `--as-pid2` parameter to `systemd-nspawn` allows it to work. ** Changed in: mysql-5.7 (Ubuntu) Status: New => Invalid ** Changed in: systemd (Ubuntu) Status: New => Invalid -- 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/1752705 Title: When run from systemd-nspawn, installation of mysql-server fails because postinst fails to shut down server Status in mysql-5.7 package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Bug description: Creating a fresh Bionic directory with `debootstrap` and then attempting to install `mysql-server` inside a `systemd-nspawn` container fails with the following message: Setting up mysql-server-5.7 (5.7.21-1ubuntu1) ... invoke-rc.d: could not determine current runlevel * Stopping MySQL database server mysqld [ OK ] update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) Error: Unable to shut down server with process id 532 dpkg: error processing package mysql-server-5.7 (--configure): installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 Steps to reproduce: 1. debootstrap bionic testmysql 2. rm testmysql/etc/resolv.conf 2. systemd-nspawn -D testmyql --bind /etc/resolv.conf /bin/bash -c 'apt update && apt install mysql-server' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1752705/+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 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)
> when SSH ends, for example, a Release event is sent
> through dbus and systemd-logind captures it, in the function
> manager_message_handler().
>
> From there, the function session_remove_fifo() is called. That point is our
> "bootstrap"
> to add the closing session on gc
ok i see that path, dbus Release -> remove fifo, however i don't think
it's appropriate to put the add_to_gc into remove_fifo; because,
remove_fifo is also called from session_free()..consider this code:
session_remove_fifo(s);
free(s->state_file);
free(s);
}
so...that call to session_remove_fifo() previously only removed the
fifo. but with your patch, it's also adding 's' back onto the gc
queue...but then immediately freeing s!!! When the gc queue is
processed, this code:
while ((session = m->session_gc_queue)) {
LIST_REMOVE(Session, gc_queue, m->session_gc_queue, session);
session->in_gc_queue = false;
will dereference 's' ('session' in the gc handler), accessing freed
memory.
Since you're trying to use the dbus Release notification to add the
session to the gc, wouldn't it be better to simply update the dbus
Release handler to remove the fifo *and* add the session to the gc, from
there? not modify the remove_fifo function?
--
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/1750013
Title:
systemd-logind: memory leaks on session's connections (trusty-only)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Trusty:
In Progress
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Artful:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Bug description:
Below the SRU request form. Please refer to the Original Description
to a more comprehensive explanation of the problem observed.
[Impact]
* systemd-logind tool is leaking memory at each session connected. The
issues happens in systemd from Trusty (14.04) only.
* Three issues observed:
- systemd-logind is leaking entire sessions, i.e, the sessions are not
feeed after they're closed. In order to fix that, we proactively add
the sessions to systemd garbage collector (gc) when they are closed.
Also, part of the fix is to make cgmanager package a dependency. Refer
to comment #1 to a more thorough explanation of the issue and the fix.
- a small memory leak was observed in the session creation logic of
systemd-logind. The fix for that is the addition of an appropriate
free() call. Refer to comment #2 to more details on the issue and fix.
- another small memory leak was observed in the cgmanager glue code of
systemd-logind - this code is only present in this specific Ubuntu
release of the package, due to necessary compatibility layer with
upstart init system. The fix is to properly call free() in 2
functions. Refer to comment #3 to a deep exposition of the issue and
the fix.
[Test Case]
* The basic test-case is to run the following loop from a remote machine:
while true; do ssh "whoami"; done
* It's possible to watch the increase in memory consumption from
"systemd-logind" process in the target machine. One can use the
"ps uax" command to verify the RSS of the process, or count its
anonymous pages from /proc//smaps.
[Regression Potential]
* Since the fixes are small and not intrusive, the potential for
regressions are low. More regression considerations on comments #1, #2
and #3 for each fix.
* A potential small regressson is performance-wise, since now we add
sessions to garbage collector proactively.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+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 1752938] [NEW] Upgrading Ubuntu 18.04 disables GPU hardware acceleration
Public bug reported: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to llvmpipe. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu5 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: XFCE Date: Sat Mar 3 00:58:35 2018 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Baffin [Polaris11] [1002:67ff] (rev cf) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Baffin [Radeon RX 560] [1043:04be] InstallationDate: Installed on 2018-03-02 (0 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180302) MachineType: Gigabyte Technology Co., Ltd. B85M-D3V-A ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed root=UUID=d2dcc7eb-84ca-4102-9ae1-239de26d113c ro quiet splash vt.handoff=1 Renderer: Software SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/12/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F2 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-D3V-A dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF2:bd02/12/2015:svnGigabyteTechnologyCo.,Ltd.:pnB85M-D3V-A:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnB85M-D3V-A:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: B85M-D3V-A dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.90-1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.3.3-0ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 17.3.3-0ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 ** Affects: xorg (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic reproducible single-occurrence 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/1752938 Title: Upgrading Ubuntu 18.04 disables GPU hardware acceleration Status in xorg package in Ubuntu: New Bug description: I don't know which package causes this problem. The thing is ugrading Ubuntu 18.04 disables my GPU hardware acceleration. glxinfo_before_upgrade OpenGL vendor string: X.Org OpenGL renderer string: Radeon RX 560 Series (POLARIS11 / DRM 3.23.0 / 4.15.0-10-generic, LLVM 5.0.1) OpenGL core profile version string: 4.5 (Core Profile) Mesa 17.3.3 glxinfo_after_upgrade OpenGL vendor string: VMware, Inc. OpenGL renderer string: llvmpipe (LLVM 5.0, 256 bits) OpenGL core profile version string: 3.3 (Core Profile) Mesa 17.3.3 This problem is reproducible. Steps to reproduce: 1. Install Ubuntu 18.04 daily live. I've tried Kubuntu 18.04 Feb 26's daily live(the installer in Mar 1 crashes which prevents me from installing it) and Xubuntu 18.04 Mar 2's daily live. Ubuntu is utilizing my GPU in live cd session and after the fresh install Ubuntu is also utilizing my GPU. 2. Reboot into the newly installed system, do a dist-upgrade and reboot again. Opengl renderer falls back to
[Touch-packages] [Bug 1522675] Re: Warning messages about unsandboxed downloads
bdmurray@clean-xenial-amd64:~$ apt-cache policy update-notifier update-notifier: Installed: 3.168.1 Candidate: 3.168.7 Version table: 3.168.7 500 500 http://192.168.10.7/ubuntu xenial-updates/main amd64 Packages 500 http://192.168.10.7/ubuntu xenial-security/main amd64 Packages *** 3.168.1 100 100 /var/lib/dpkg/status 3.168 500 500 http://192.168.10.7/ubuntu xenial/main amd64 Packages bdmurray@clean-xenial-amd64:~$ sudo apt install flashplugin-installer Reading package lists... Done Building dependency tree Reading state information... Done The following additional packages will be installed: libpango1.0-0 libpangox-1.0-0 Suggested packages: x-ttcidfont-conf ttf-mscorefonts-installer ttf-bitstream-vera | ttf-dejavu ttf-xfree86-nonfree xfs The following NEW packages will be installed: flashplugin-installer libpango1.0-0 libpangox-1.0-0 0 upgraded, 3 newly installed, 0 to remove and 556 not upgraded. Need to get 6,798 B/51.9 kB of archives. After this operation, 445 kB of additional disk space will be used. Do you want to continue? [Y/n] y ... flashplugin-installer: downloading http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20180206.1.orig.tar.gz Get:1 http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20180206.1.orig.tar.gz [30.5 MB] Fetched 30.5 MB in 5s (5,929 kB/s) W: Can't drop privileges for downloading as file '/var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20180206.1.orig.tar.gz' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) Installing from local file /var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20180206.1.orig.tar.gz With the version from -proposed: Setting up update-notifier-common (3.168.8) ... flashplugin-installer: processing... flashplugin-installer: downloading http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20180206.1.orig.tar.gz Get:1 http://archive.canonical.com/pool/partner/a/adobe-flashplugin/adobe-flashplugin_20180206.1.orig.tar.gz [30.5 MB] Fetched 30.5 MB in 8s (3,434 kB/s) Installing from local file /var/lib/update-notifier/package-data-downloads/partial/adobe-flashplugin_20180206.1.orig.tar.gz Flash Plugin installed. Setting up libcairo-perl (1.106-1build1) ... ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: New Status in synaptic source package in Xenial: New Status in update-notifier source package in Xenial: Fix Committed Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is a cosmetic issue. The warning message is just that— a warning. Though the message comes up, there is no problem with the install/upgrade happening like normal. That said, feel free to ignore it. It will get fixed, but it's nowhere near as urgent as bugs that actually result in the wrong behavior rather than just a simple extra message. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r
Re: [Touch-packages] [Bug 1752472] Re: [ffe] Implement an Ubuntu Single Sign-on Provider
On Fri, Mar 02, 2018 at 07:51:58AM -, Sebastien Bacher wrote: > The provider has been discussed with upstream and they are fine on the > idea, Marco did a first code review and upstream said they would review > it as well this week. Please make sure to follow up on the comments upstream and get this merged, but OK with me to upload. -- Iain Lane [ i...@orangesquash.org.uk ] Debian Developer [ la...@debian.org ] Ubuntu Developer [ la...@ubuntu.com ] -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/1752472 Title: [ffe] Implement an Ubuntu Single Sign-on Provider Status in gnome-online-accounts: Unknown Status in gnome-online-accounts package in Ubuntu: New Bug description: Add an Ubuntu Single Sing-On provider in gnome-online-accounts. We plan to use this inside: 1) gnome-software 2) software-properties To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-online-accounts/+bug/1752472/+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 1752928] [NEW] [FFe] GNOME 3.28
Public bug reported: Feature Freeze Justification Evolution was delayed to not intertangle transitions. gnome-shell was released late upstream. gnome-control-center & gnome-shell were waiting for a subject matter expert to return from holiday. Shotwell got overlooked but plans to release at the same time as GNOME. GNOME prefers us to not mix and match components from different versions as much as possible. GNOME 3.28.0 release is just over a week away Affected Packages - evolution transition LP: #1752578 gnome-control-center and gnome-settings-daemon LP: #1750174 gnome-shell and mutter LP: #1751070 gnome-session shotwell gnome-games, retro-gtk & libmanette (libmanette released yesterday with updated library name, waiting on new retro-gtk release expected any day) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1752928 Title: [FFe] GNOME 3.28 Status in ubuntu-meta package in Ubuntu: New Bug description: Feature Freeze Justification Evolution was delayed to not intertangle transitions. gnome-shell was released late upstream. gnome-control-center & gnome-shell were waiting for a subject matter expert to return from holiday. Shotwell got overlooked but plans to release at the same time as GNOME. GNOME prefers us to not mix and match components from different versions as much as possible. GNOME 3.28.0 release is just over a week away Affected Packages - evolution transition LP: #1752578 gnome-control-center and gnome-settings-daemon LP: #1750174 gnome-shell and mutter LP: #1751070 gnome-session shotwell gnome-games, retro-gtk & libmanette (libmanette released yesterday with updated library name, waiting on new retro-gtk release expected any day) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1752928/+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 1522675] Re: Warning messages about unsandboxed downloads
Hopes someone will do the change too for synaptic, which display that error only the first upgrade is done. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: New Status in synaptic source package in Xenial: New Status in update-notifier source package in Xenial: Fix Committed Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is a cosmetic issue. The warning message is just that— a warning. Though the message comes up, there is no problem with the install/upgrade happening like normal. That said, feel free to ignore it. It will get fixed, but it's nowhere near as urgent as bugs that actually result in the wrong behavior rather than just a simple extra message. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1682695] Re: System stops recognizing correct screen resolution
I can't tell if it's still valid because my monitor stopped working and had to be replaced within a month afterward, and the problem hasn't happened since. -- 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/1682695 Title: System stops recognizing correct screen resolution Status in xorg package in Ubuntu: Incomplete Bug description: Up to last night, I was using my system just fine, with my 1280x1024 monitor. Today, the system boots up with all the text and icons much larger, and Settings -> Displays now informs me that my monitor is only 1024x768 and won't permit me to change it back to the correct setting. I haven't changed anything, hardware or software. How do I make it work correctly again? ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: xorg 1:7.7+13ubuntu4 ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17 Uname: Linux 4.8.0-46-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Apr 13 19:07:58 2017 DistUpgraded: Fresh install DistroCodename: yakkety DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G98 [GeForce 8400 GS Rev. 2] [1043:8321] InstallationDate: Installed on 2017-03-26 (18 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) MachineType: MSI MS-7865 ProcEnviron: LANGUAGE=en_US PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-46-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.0 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: AM1I (MS-7865) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.0:bd02/21/2014:svnMSI:pnMS-7865:pvr2.0:rvnMSI:rnAM1I(MS-7865):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.name: MS-7865 dmi.product.version: 2.0 dmi.sys.vendor: MSI version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.70-1 version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.6-0ubuntu0.16.10.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.6-0ubuntu0.16.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2 xserver.bootTime: Thu Apr 13 19:04:54 2017 xserver.configfile: default xserver.devices: inputPower Button KEYBOARD, id 6 inputPower Button KEYBOARD, id 7 inputHID 04f3:0103KEYBOARD, id 8 inputHID 04f3:0103KEYBOARD, id 9 inputUSB Optical MouseMOUSE, id 10 xserver.errors: Failed to load module "nvidia" (module does not exist, 0) Failed to load module "nvidia" (module does not exist, 0) xserver.logfile: /var/log/Xorg.0.log xserver.outputs: Output DVI-I-1 VGA-1 xserver.version: 2:1.18.4-1ubuntu6 xserver.video_driver: nouveau To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682695/+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 1522675] Re: Warning messages about unsandboxed downloads
Installed update-notifier 3.168.8 from xenial-proposed. I do not get any "W: Can't drop privileges for downloading" during execution of $ sudo apt-get install --reinstall flashplugin-installer ttf- mscorefonts-installer But aptitude is still complains when getting changelogs from terminal `aptitude changelog apt` or interactively by (see bug https://bugs.launchpad.net/bugs/1752907 ). Thank you! If others know other ways to test, please do it. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: New Status in synaptic source package in Xenial: New Status in update-notifier source package in Xenial: Fix Committed Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is a cosmetic issue. The warning message is just that— a warning. Though the message comes up, there is no problem with the install/upgrade happening like normal. That said, feel free to ignore it. It will get fixed, but it's nowhere near as urgent as bugs that actually result in the wrong behavior rather than just a simple extra message. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1749261] Re: Add amd64/i386 retpoline support
having here gcc-4.8 (Ubuntu 4.8.5-2ubuntu1-~14.04.01) 4.8.5 and it does not honor either of the above listed switches but returns an error. sounds a bit like a regression to me, a vanished feature. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1749261 Title: Add amd64/i386 retpoline support Status in gcc-4.8 package in Ubuntu: Confirmed Status in gcc-4.8 source package in Trusty: Fix Released Bug description: To mitigate Spectre Variant 2, gcc needs to have retpoline support (-mindirect-branch and -mfunction-return arguments on amd64 and i386). Packages with this will go into the proposed pockets but need to be published in the -security pockets for their respective releases. Patches for gcc-4.8 were pulled from H.J. Lu's backport branch to 4.9, available at https://github.com/hjl-tools/gcc/tree/hjl/indirect/gcc- 4_9-branch/master . Upstream GCC does not seem to be applying patches to anything older than the gcc-6-branch. H.J. Lu is the author of the upstream retpoline commits as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1749261/+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 1661205] Re: avahi daemon repeatedly crashes on boot
*** This bug is a duplicate of bug 1638345 *** https://bugs.launchpad.net/bugs/1638345 ** This bug has been marked a duplicate of bug 1638345 avahi-daemon crashes multiple times an hour -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661205 Title: avahi daemon repeatedly crashes on boot Status in avahi package in Ubuntu: Incomplete Bug description: causes "System program problem detected" to pop-up repeatedly and randomly. "Report problem..." does nothing. Used to just crash once per boot, and allow reports. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 2 10:43:04 2017 InstallationDate: Installed on 2016-10-31 (93 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661205/+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 1742946] Re: "gio monitor" does not work
Thank you for your bug report, indeed that's an upstream bug which was fixed after .1 but before .3. The fix is in the current bionic version The corresponding upstream bug is https://bugzilla.gnome.org/show_bug.cgi?id=790093 ** Bug watch added: GNOME Bug Tracker #790093 https://bugzilla.gnome.org/show_bug.cgi?id=790093 ** Changed in: glib2.0 (Ubuntu) Status: Confirmed => Fix Released ** Also affects: glib via https://bugzilla.gnome.org/show_bug.cgi?id=790093 Importance: Unknown Status: Unknown -- 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/1742946 Title: "gio monitor" does not work Status in GLib: Unknown Status in glib2.0 package in Ubuntu: Fix Released Bug description: # ls -l /etc/adduser.conf -rw-r--r-- 1 root root 2981 Mar 11 2012 /etc/adduser.conf # gio monitor file:///etc/adduser.conf gio: No locations given Usage: gio monitor [OPTION…] [LOCATION...] Monitor files or directories for changes. Options: -d, --dir=LOCATIONMonitor a directory (default: depends on type) -f, --file=LOCATION Monitor a file (default: depends on type) -D, --direct=LOCATION Monitor a file directly (notices changes made via hardlinks) -s, --silent=LOCATION Monitors a file directly, but doesn’t report changes -n, --no-movesReport moves and renames as simple deleted/created events -m, --mounts Watch for mount events ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libglib2.0-bin 2.54.1-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-21.24-generic 4.13.13 Uname: Linux 4.13.0-21-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 Date: Fri Jan 12 14:29:42 2018 InstallationDate: Installed on 2012-03-12 (2131 days ago) InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120311) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/usr/bin/tcsh SourcePackage: glib2.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1742946/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler!
probably related to bug #1749261 -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler! Status in gcc: New Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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 xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1750937/+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 1749261] Re: Add amd64/i386 retpoline support
referenced by bug #1750937 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1749261 Title: Add amd64/i386 retpoline support Status in gcc-4.8 package in Ubuntu: Confirmed Status in gcc-4.8 source package in Trusty: Fix Released Bug description: To mitigate Spectre Variant 2, gcc needs to have retpoline support (-mindirect-branch and -mfunction-return arguments on amd64 and i386). Packages with this will go into the proposed pockets but need to be published in the -security pockets for their respective releases. Patches for gcc-4.8 were pulled from H.J. Lu's backport branch to 4.9, available at https://github.com/hjl-tools/gcc/tree/hjl/indirect/gcc- 4_9-branch/master . Upstream GCC does not seem to be applying patches to anything older than the gcc-6-branch. H.J. Lu is the author of the upstream retpoline commits as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1749261/+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 1661205] Re: avahi daemon repeatedly crashes on boot
I am not the reporter but can confirm that it still affects 16.04 LTS. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to avahi in Ubuntu. https://bugs.launchpad.net/bugs/1661205 Title: avahi daemon repeatedly crashes on boot Status in avahi package in Ubuntu: Incomplete Bug description: causes "System program problem detected" to pop-up repeatedly and randomly. "Report problem..." does nothing. Used to just crash once per boot, and allow reports. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: avahi-daemon 0.6.32-1ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11 Uname: Linux 4.8.0-34-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 CurrentDesktop: Unity Date: Thu Feb 2 10:43:04 2017 InstallationDate: Installed on 2016-10-31 (93 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: avahi UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1661205/+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 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)
Dan, thanks for looking at the patch and for your question! I tried to explain this a bit in comment #1, not too much detailed though: "[...]closing session should be somehow added to gc [...] and then (the gc) performs the clean-up. To include a session in gc, the function session_add_to_gc_queue() should be called. [...] (this) patch proactively puts a session in gc on session_remove_fifo(). This function is always called in the event of Release a session - when the ssh ends, for example. [...]" Being a bit more specific: when SSH ends, for example, a Release event is sent through dbus and systemd-logind captures it, in the function manager_message_handler(). >From there, the function session_remove_fifo() is called. That point is our >"bootstrap" to add the closing session on gc, our first addition there. But unfortunately due to an unpredictable timing of cgroup become empty for that session, the gc might fail to remove the session right in that moment. So, we need to re-add the closing session to gc from...within the gc! In my experiments, 2 or 3 re-additions are enough to get the session removed. It wouldn't be necessary to do these 2 steps above IF the cgroup empty notification was working fine. In that case, after the cgroup for the closing session become empty, a notification handler would be triggered in the systemd-logind and that handler would add the session to gc, and then gc would clean it up. But, since in Trusty we have upstart as our init system (and systemd is highly patched to co-exist in this fashion) and cgroup empty notifications were broken in systemd (until a complete refactor of cgroup handling in systemd), our approach here is the less expensive one. In summary, the above 2 steps [adding the session to gc in session_remove_fifo() and re-adding it from within gc] are the most important parts of this patch - without them we leak entire sessions and eventually the logind process gets OOM'ed. Thanks, Guilherme -- 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/1750013 Title: systemd-logind: memory leaks on session's connections (trusty-only) Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Trusty: In Progress Status in systemd source package in Xenial: Fix Released Status in systemd source package in Artful: Fix Released Status in systemd source package in Bionic: Fix Released Bug description: Below the SRU request form. Please refer to the Original Description to a more comprehensive explanation of the problem observed. [Impact] * systemd-logind tool is leaking memory at each session connected. The issues happens in systemd from Trusty (14.04) only. * Three issues observed: - systemd-logind is leaking entire sessions, i.e, the sessions are not feeed after they're closed. In order to fix that, we proactively add the sessions to systemd garbage collector (gc) when they are closed. Also, part of the fix is to make cgmanager package a dependency. Refer to comment #1 to a more thorough explanation of the issue and the fix. - a small memory leak was observed in the session creation logic of systemd-logind. The fix for that is the addition of an appropriate free() call. Refer to comment #2 to more details on the issue and fix. - another small memory leak was observed in the cgmanager glue code of systemd-logind - this code is only present in this specific Ubuntu release of the package, due to necessary compatibility layer with upstart init system. The fix is to properly call free() in 2 functions. Refer to comment #3 to a deep exposition of the issue and the fix. [Test Case] * The basic test-case is to run the following loop from a remote machine: while true; do ssh "whoami"; done * It's possible to watch the increase in memory consumption from "systemd-logind" process in the target machine. One can use the "ps uax" command to verify the RSS of the process, or count its anonymous pages from /proc//smaps. [Regression Potential] * Since the fixes are small and not intrusive, the potential for regressions are low. More regression considerations on comments #1, #2 and #3 for each fix. * A potential small regressson is performance-wise, since now we add sessions to garbage collector proactively. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+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 1749261] Re: Add amd64/i386 retpoline support
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gcc-4.8 (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gcc-4.8 in Ubuntu. https://bugs.launchpad.net/bugs/1749261 Title: Add amd64/i386 retpoline support Status in gcc-4.8 package in Ubuntu: Confirmed Status in gcc-4.8 source package in Trusty: Fix Released Bug description: To mitigate Spectre Variant 2, gcc needs to have retpoline support (-mindirect-branch and -mfunction-return arguments on amd64 and i386). Packages with this will go into the proposed pockets but need to be published in the -security pockets for their respective releases. Patches for gcc-4.8 were pulled from H.J. Lu's backport branch to 4.9, available at https://github.com/hjl-tools/gcc/tree/hjl/indirect/gcc- 4_9-branch/master . Upstream GCC does not seem to be applying patches to anything older than the gcc-6-branch. H.J. Lu is the author of the upstream retpoline commits as well. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1749261/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
switching to "beta" version of gcc (Ubuntu 7.3.0-5ubuntu1~14.04.york0) 7.3.0 and rebuilding the kernel modules in question for 4.4.0-116 seemingly did the job. is this really what you wanted from a good amount of the end users by publishing those kernel? ** Summary changed: - 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) + 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler! ** Also affects: gcc Importance: Undecided Status: New -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) by an insufficient compiler! Status in gcc: New Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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 xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/gcc/+bug/1750937/+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.la
[Touch-packages] [Bug 1302546] Re: gtk drawing area - missing or incorrect expose or draw event
** Changed in: gtk+3.0 (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1302546 Title: gtk drawing area - missing or incorrect expose or draw event Status in GTK+: Fix Released Status in LiVES: Confirmed Status in gtk+3.0 package in Ubuntu: Fix Released Bug description: Application is Fotoxx 14.04. A GTK notebook is used with tabs containing drawing areas inside scrolled windows. The program works on Ubuntu 13.10 and earlier (GTK 3.8) and fails on Ubuntu 14.04 beta (as of April 4) (GTK 3.10). When the notebook tab is changed the new tab's drawing area is not updated (Fotoxx gallery page). Some prior data is present and the rest is background color only. Clicking elsewhere and then clicking the window title bar (unfocus and refocus the app) causes the tab to update correctly. Removing the default "double buffered" attribute from the drawing area widget after it is created makes everything work correctly on Ubuntu 14.04. However on earlier Ubuntu releases the background is not updated and is filled with data from the previous tab. This seems to be a problem with missing "draw" events or events with incorrect update regions. I have verified that draw events are not sent when the tab is switched but are sent when the window acquires focus. The GTK bug tracking system seems to have related bugs but I cannot be sure (too much technical jargon for my knowledge of GTK internals). I did not file a report there because the expected knowledge of internals is missing. The bug may be fixed in GTK 3.12. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: libgtk-3-0 3.10.7-0ubuntu5 ProcVersionSignature: Ubuntu 3.13.0-22.44-generic 3.13.8 Uname: Linux 3.13.0-22-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Fri Apr 4 13:28:59 2014 InstallationDate: Installed on 2014-03-28 (7 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Beta amd64 (20140326) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/1302546/+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 1168978] Re: Evince crashes consistently, reading 50+ pages into specific PDF document
That's fixed in the current version ** Changed in: cairo (Ubuntu) Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to cairo in Ubuntu. https://bugs.launchpad.net/bugs/1168978 Title: Evince crashes consistently, reading 50+ pages into specific PDF document Status in cairo: Fix Released Status in cairo package in Ubuntu: Fix Released Bug description: 1) lsb_release -rd Description: Ubuntu Vivid Vervet (development branch) Release: 15.04 2) apt-cache policy evince libcairo2 libpoppler[0-9]evince: Installed: 3.14.1-0ubuntu1 Candidate: 3.14.1-0ubuntu1 Version table: *** 3.14.1-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status libcairo2: Installed: 1.13.0~20140204-0ubuntu1 Candidate: 1.13.0~20140204-0ubuntu1 Version table: *** 1.13.0~20140204-0ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status libpoppler47: Installed: 0.28.1-1ubuntu1 Candidate: 0.28.1-1ubuntu1 Version table: *** 0.28.1-1ubuntu1 0 500 http://us.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3) What is expected to happen via https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1168978/+attachment/3644236/+files/ICE1712-1.pdf is the entire document is viewable, as it is in Adobe Reader. 4) What happens instead is it consistently crashes after reading past page 61. WORKRAROUND: Use Firefox's built-in PDF viewer. Upstreamed to Evince who advised Cairo issue: https://bugzilla.gnome.org/show_bug.cgi?id=741945 https://bugs.freedesktop.org/show_bug.cgi?id=92517 https://bugs.freedesktop.org/show_bug.cgi?id=85141 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: evince 3.6.1-1ubuntu3 ProcVersionSignature: Ubuntu 3.8.0-18.12-lowlatency 3.8.6 Uname: Linux 3.8.0-18-lowlatency i686 ApportVersion: 2.9.2-0ubuntu8 Architecture: i386 Date: Sun Apr 14 14:46:27 2013 InstallationDate: Installed on 2013-03-21 (24 days ago) InstallationMedia: Ubuntu-Studio 13.04 "Raring Ringtail" - Alpha i386 (20130321) KernLog: MarkForUpload: True SourcePackage: evince UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/cairo/+bug/1168978/+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 1716255] Re: nautilus crash opening directory with a spefic svg
the issue seems to be fixed in current version, it segfault in 16.04 but not using the 17.10 librsvg. The fix could be a candidate maybe for a stable update to xenial, in which case the bug can be nominated for the corresponding serie ** Also affects: librsvg via https://bugzilla.gnome.org/show_bug.cgi?id=789873 Importance: Unknown Status: Unknown ** Changed in: librsvg (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1716255 Title: nautilus crash opening directory with a spefic svg Status in librsvg: Unknown Status in librsvg package in Ubuntu: Fix Released Bug description: when I open a folder which contains the attached SVG-File, nautilus crashes. also gthumb crashes, if i try to open the file with gthumb and also firefox crashes, if i try to attach this file and navigate to the folder containing this file... the file was initially created with inkscape and i tried to remove as much as possible from the svg-xml-markup so that the problem is still reproducable. i think it has something todo with the thumbnail-generation for the SVG ? lsb_release -rd Description: Ubuntu 16.04.3 LTS Release: 16.04 apt-cache policy nautilus nautilus: Installiert: 1:3.18.4.is.3.14.3-0ubuntu6 apt-cache policy gthumb gthumb: Installiert: 3:3.4.3-1 nautilus --version GNOME nautilus 3.14.3 gthumb --version gthumb 3.4.3, Copyright © 2001-2010 Free Software Foundation, Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/1716255/+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 1733334] Re: ATK doesn't list all children for GtkNotebook when tab contains more than label
** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk+3.0 (Ubuntu) Status: New => Triaged ** Bug watch added: GNOME Bug Tracker #790496 https://bugzilla.gnome.org/show_bug.cgi?id=790496 ** Also affects: gtk via https://bugzilla.gnome.org/show_bug.cgi?id=790496 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/174 Title: ATK doesn't list all children for GtkNotebook when tab contains more than label Status in GTK+: Unknown Status in gtk+3.0 package in Ubuntu: Triaged Bug description: When gtknotebook have got a tab page that contains something more than label we can't access those elements in accerciser. For example create a GtkNotebook and put a Bo that contains label and an image into the tab page, then observe the hierarchy in the accercisser. Those elements won't be show and what's worse if the image is used to close the tab, there will be no way to do this. more info can be found here: https://bugzilla.gnome.org/show_bug.cgi?id=790496 To manage notifications about this bug go to: https://bugs.launchpad.net/gtk/+bug/174/+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 460925] Re: Kernel log message corruption due to incomplete /proc separation
** Changed in: lxc (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/460925 Title: Kernel log message corruption due to incomplete /proc separation Status in linux package in Ubuntu: Fix Committed Status in lxc package in Ubuntu: Fix Released Bug description: Binary package hint: lxc When using LXC (linux containers), /proc/kmsg can be read in guest systems in their filtered view of /proc. This special file should never be present in guest systems, and if created within a guest system, it should be effectively using /dev/null as it's source. The effect of this bug ranges from simply annoying to potentially a security issue in that kernel messages are allowed to be destroyed and never fully logged on the host system, which could be used to cover evidence of some sort of attack on the system. I'm adding the kernel team as well, as this could be an issue inside the kernel. I'm not sure if /proc filtration happens there or in the context of the lxc userland utilities. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/460925/+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 1752705] Re: When run from systemd-nspawn, installation of mysql-server fails because postinst fails to shut down server
It behaves differently (the installation succeeds) if you install mysql- server from a bash prompt inside the container. Running the installation as a parameter to `systemd-nspawn` will fail. I have tested this on a 16.04.3 system and an 18.04 system. I just noticed something especially weird: if I add `dpkg --configure -a` to the end of the `systemd-nspawn` command, then the `apt install` command will reliably finish. Prepare a base container to be used for the tests: 1. debootstrap bionic bionic 2. rm bionic/etc/resolv.conf This will always fail: sudo rm -rf testmysql && sudo cp -a bionic testmysql && sudo systemd-nspawn -D testmysql bash -c 'apt update && apt install mysql-server' This will always succeed: sudo rm -rf testmysql && sudo cp -a bionic testmysql && sudo systemd-nspawn -D testmysql bash -c 'apt update && apt install mysql-server; dpkg --configure -a' -- 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/1752705 Title: When run from systemd-nspawn, installation of mysql-server fails because postinst fails to shut down server Status in mysql-5.7 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Creating a fresh Bionic directory with `debootstrap` and then attempting to install `mysql-server` inside a `systemd-nspawn` container fails with the following message: Setting up mysql-server-5.7 (5.7.21-1ubuntu1) ... invoke-rc.d: could not determine current runlevel * Stopping MySQL database server mysqld [ OK ] update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) Error: Unable to shut down server with process id 532 dpkg: error processing package mysql-server-5.7 (--configure): installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 Steps to reproduce: 1. debootstrap bionic testmysql 2. rm testmysql/etc/resolv.conf 2. systemd-nspawn -D testmyql --bind /etc/resolv.conf /bin/bash -c 'apt update && apt install mysql-server' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1752705/+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 1752705] Re: When run from systemd-nspawn, installation of mysql-server fails because postinst fails to shut down server
It also succeeds if I replace `dpkg --configure -a` with `ls`: rm -rf testmysql && cp -a bionic testmysql && systemd-nspawn -D testmysql bash -c 'apt update && apt install mysql-server; ls' -- 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/1752705 Title: When run from systemd-nspawn, installation of mysql-server fails because postinst fails to shut down server Status in mysql-5.7 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Creating a fresh Bionic directory with `debootstrap` and then attempting to install `mysql-server` inside a `systemd-nspawn` container fails with the following message: Setting up mysql-server-5.7 (5.7.21-1ubuntu1) ... invoke-rc.d: could not determine current runlevel * Stopping MySQL database server mysqld [ OK ] update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) Error: Unable to shut down server with process id 532 dpkg: error processing package mysql-server-5.7 (--configure): installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 Steps to reproduce: 1. debootstrap bionic testmysql 2. rm testmysql/etc/resolv.conf 2. systemd-nspawn -D testmyql --bind /etc/resolv.conf /bin/bash -c 'apt update && apt install mysql-server' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1752705/+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 1752705] Re: installation of mysql-server fails because postinst fails to shut down server
We did change how mysql-server-5.7.postinst handles internal server start and stop in Bionic in order to fix bug 1592669. ** Summary changed: - installation of mysql-server fails because postinst fails to shut down server + When run from systemd-nspawn, installation of mysql-server fails because postinst fails to shut down server -- 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/1752705 Title: When run from systemd-nspawn, installation of mysql-server fails because postinst fails to shut down server Status in mysql-5.7 package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Creating a fresh Bionic directory with `debootstrap` and then attempting to install `mysql-server` inside a `systemd-nspawn` container fails with the following message: Setting up mysql-server-5.7 (5.7.21-1ubuntu1) ... invoke-rc.d: could not determine current runlevel * Stopping MySQL database server mysqld [ OK ] update-alternatives: using /etc/mysql/mysql.cnf to provide /etc/mysql/my.cnf (my.cnf) in auto mode Renaming removed key_buffer and myisam-recover options (if present) Error: Unable to shut down server with process id 532 dpkg: error processing package mysql-server-5.7 (--configure): installed mysql-server-5.7 package post-installation script subprocess returned error exit status 1 Steps to reproduce: 1. debootstrap bionic testmysql 2. rm testmysql/etc/resolv.conf 2. systemd-nspawn -D testmyql --bind /etc/resolv.conf /bin/bash -c 'apt update && apt install mysql-server' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.7/+bug/1752705/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
are you thinking of something like this? https://launchpad.net/~jonathonf/+archive/ubuntu/gcc-7.3 -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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 xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+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 1751414] Re: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1
> sudo apt remove libegl1 This cascaded to what turned out to be the entirety of ubuntu-desktop for me. I would advise caution here, it can be a pain to get back. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mir in Ubuntu. https://bugs.launchpad.net/bugs/1751414 Title: [regression] Missing Wayland login option and missing GL acceleration, after installing libegl1 Status in libglvnd package in Ubuntu: Confirmed Status in mesa-demos package in Ubuntu: Confirmed Status in mir package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: I just updated bionic and suddenly: * No 'Ubuntu on Wayland' login option. * The 'Ubuntu' login option is very slow -- glxinfo reports LLVMpipe (software rendering) WORKAROUND: sudo apt remove libegl1 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-shell 3.26.2-0ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 Date: Sat Feb 24 13:59:46 2018 DisplayManager: gdm3 InstallationDate: Installed on 2017-12-12 (73 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211) SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libglvnd/+bug/1751414/+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 1750937] Re: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04)
are you sure it has arrived with _some_ gcc version already. publications indicate its very experimental still and i can not see any of the typical switches beeing honored by the gcc versions on my machine. (and i was able to switch them forth and back using "update- alternatives") needless to say that even after a few attempts a call to "modinfo" does not at all report the "retpoline" option for the dkms built nvidia kernel modules (using -384 on top of 4.4.0-116). https://www.phoronix.com/scan.php?page=news_item&px=GCC-7-Gets-Retpolines https://www.phoronix.com/scan.php?page=article&item=gcc8-mindirect-thunk&num=1 can you please be more specific with the compiler versions you are using? please give exact versions. thank you. -- 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/1750937 Title: 4.4.0-116 Kernel update on 2/21 breaks Nvidia drivers (on 14.04 and 16.04) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-384 package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Bug description: Running fine with nvidia-384 until this kernel update came along. When booted into the new kernel, got super low resolution and nvidia- settings was missing most of its functionality - could not change resolution. Rebooted into 4.4.0-112 kernel and all was well. The root cause of the problem has been found to be installing the -116 kernel without a sufficiently updated version of gcc. In my case, my system received the gcc update AFTER the kernel update. Uninstalling the -116 kernel and reinstalling it with the updated version of gcc solved the problem for me. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: xorg 1:7.7+1ubuntu8.1 ProcVersionSignature: Ubuntu 4.4.0-112.135~14.04.1-generic 4.4.98 Uname: Linux 4.4.0-112-generic x86_64 NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 384.111 Tue Dec 19 23:51:45 PST 2017 GCC version: gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) ApportVersion: 2.14.1-0ubuntu3.27 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 21 19:23:39 2018 DistUpgraded: Fresh install DistroCodename: trusty DistroVariant: ubuntu DkmsStatus: bbswitch, 0.7, 4.4.0-112-generic, x86_64: installed bbswitch, 0.7, 4.4.0-116-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-112-generic, x86_64: installed nvidia-384, 384.111, 4.4.0-116-generic, x86_64: installed GraphicsCard: NVIDIA Corporation Device [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: eVga.com. Corp. Device [3842:6253] InstallationDate: Installed on 2015-03-03 (1086 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) MachineType: ASUSTeK COMPUTER INC. M11AD ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-112-generic root=UUID=5a88d2a1-0a24-415b-adc2-28435b13248a ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/15/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 0302 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M11AD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0302:bd08/15/2013:svnASUSTeKCOMPUTERINC.:pnM11AD:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnM11AD:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.name: M11AD dmi.product.version: System Version dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri N/A version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A 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 xserver.bootTime: Wed Feb 21 18:48:14 2018 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.18.3-1ubuntu2.3~trusty4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1750937/+subscriptions -- Mail
[Touch-packages] [Bug 972077] Re: apt repository disk format has race conditions
affects me too -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/972077 Title: apt repository disk format has race conditions Status in APT: Fix Released Status in apt package in Ubuntu: Fix Released Bug description: Apt archives are accessed over HTTP; this has resulted in a cluster of bugs (reported here, and upstream) about problems behind intercepting caches, problems with squid etc. There are 3 interlocking issues: A - mirror networks may be out of sync with each other (e.g. a file named on one mirror may no longer exist, or may not yet exist, on another mirror) B - updating files on a single mirror is not atomic - and even small windows of inconsistency will, given enough clients, cause headaches. C - caches exacerbate race conditions - when one happens, until the cached data expires, all clients of the cache will suffer from the race Solving this requires one of several things: - file system transactions - an archive format that requires only weakly ordered updates to the files at particular urls with the assumption that only one file may be observed to change at a time (because a lookup of file A, then B, may get a cache miss on A and a cache hit on B, so even if all clients strictly go A, then B, updates may still see old files when paths are reused). - super robust clients that repeatedly retry with progressively less cache friendly headers until they have a consistent view. (This is very tricky to do). It may be possible to do a tweak to the apt repository format though, which would allow publishing a race-free format in parallel with the existing layout, while clients migrate. To be safe against issue (A) the mirror network would need some care around handling of dns round- robin mirrors [to minimise the situation where referenced data is not available], but this should be doable - or alternatively clients doing 'apt-get update' may need to be willing to retry to accommodate round- robin skew. What would such an archive format look like? It would have only one well known file name (InRelease), which would be internally signed. Rather than signing e.g. Packages.gz, it would sign a uniquely named packages and sources file - e.g. Packages-$HASH.gz or Packages-$serialno.gz. Backwards compatibility is achieved by using the same filenames for deb's and the like. We need to keep writing Packages.gz though, and Releases, until we no longer worry about old apt clients. We can optimise disk space a little by making Packages.gz a symlink to a Packages-$HASH.gz (and so on for Sources..), but it may be simpler and less prone to unexpected behaviour to keep using regular files. tl;dr * Unique file names for all unique file content with one exception * InRelease, a self-signed file that provides hashes and names the index files (Packages, Sources, Translations etc) * Coexists with existing archive layout Related bugs: * bug 804252: Please support InRelease files * bug 1430011: support apt by-hash mirrors To manage notifications about this bug go to: https://bugs.launchpad.net/apt/+bug/972077/+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 1750013] Re: systemd-logind: memory leaks on session's connections (trusty-only)
This does not look right to me:
@@ -951,6 +952,7 @@
free(s->fifo_path);
s->fifo_path = NULL;
}
+session_add_to_gc_queue(s);
}
int session_check_gc(Session *s, bool drop_not_started) {
that puts the session on the manager's gc queue, however this function
(session_remove_fifo) is called from session_free(), which is called from the
manager's gc queue handler...can you explain why this is needed here?
The other parts of the patch look good, 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/1750013
Title:
systemd-logind: memory leaks on session's connections (trusty-only)
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Trusty:
In Progress
Status in systemd source package in Xenial:
Fix Released
Status in systemd source package in Artful:
Fix Released
Status in systemd source package in Bionic:
Fix Released
Bug description:
Below the SRU request form. Please refer to the Original Description
to a more comprehensive explanation of the problem observed.
[Impact]
* systemd-logind tool is leaking memory at each session connected. The
issues happens in systemd from Trusty (14.04) only.
* Three issues observed:
- systemd-logind is leaking entire sessions, i.e, the sessions are not
feeed after they're closed. In order to fix that, we proactively add
the sessions to systemd garbage collector (gc) when they are closed.
Also, part of the fix is to make cgmanager package a dependency. Refer
to comment #1 to a more thorough explanation of the issue and the fix.
- a small memory leak was observed in the session creation logic of
systemd-logind. The fix for that is the addition of an appropriate
free() call. Refer to comment #2 to more details on the issue and fix.
- another small memory leak was observed in the cgmanager glue code of
systemd-logind - this code is only present in this specific Ubuntu
release of the package, due to necessary compatibility layer with
upstart init system. The fix is to properly call free() in 2
functions. Refer to comment #3 to a deep exposition of the issue and
the fix.
[Test Case]
* The basic test-case is to run the following loop from a remote machine:
while true; do ssh "whoami"; done
* It's possible to watch the increase in memory consumption from
"systemd-logind" process in the target machine. One can use the
"ps uax" command to verify the RSS of the process, or count its
anonymous pages from /proc//smaps.
[Regression Potential]
* Since the fixes are small and not intrusive, the potential for
regressions are low. More regression considerations on comments #1, #2
and #3 for each fix.
* A potential small regressson is performance-wise, since now we add
sessions to garbage collector proactively.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1750013/+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 1751797] Re: dns resolution only works for domains in 'search'.
** Changed in: systemd (Ubuntu) Importance: Undecided => Critical -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1751797 Title: dns resolution only works for domains in 'search'. Status in systemd package in Ubuntu: Confirmed Bug description: After reboot, dns was broken. This is a very simple Network Manager managed interface that has dhcp. $ nmcli device show enp0s25 | pastebinit http://paste.ubuntu.com/p/sMVTdrMBxJ/ I've attached systemd-resolve --status output. In order to file the bug I just modified /etc/resolv.conf to put the dns server in directly. Other information, it seems like it just will only look for dns under my search domains from the dhcp server: $ systemd-resolve home.mosers.us home.mosers.us: 23.28.108.176 -- Information acquired via protocol DNS in 1.5ms. -- Data is authenticated: no $ systemd-resolve google.com google.com: resolve call failed: No appropriate name servers or networks for name found ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: systemd 237-3ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 NonfreeKernelModules: zfs zunicode zavl zcommon znvpair ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Feb 26 09:35:32 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2015-07-23 (949 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic root=UUID=f897b32a-eacf-4191-9717-844918947069 ro quiet splash vt.handoff=1 SourcePackage: systemd UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.vendor: Intel Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1751797/+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 1522675] Re: Warning messages about unsandboxed downloads
Hello dino99, or anyone else affected, Accepted update-notifier into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/update- notifier/3.168.8 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-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. 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! ** Changed in: update-notifier (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to apt in Ubuntu. https://bugs.launchpad.net/bugs/1522675 Title: Warning messages about unsandboxed downloads Status in apt package in Ubuntu: Fix Released Status in aptitude package in Ubuntu: Fix Released Status in synaptic package in Ubuntu: Triaged Status in update-notifier package in Ubuntu: Fix Released Status in aptitude source package in Xenial: New Status in synaptic source package in Xenial: New Status in update-notifier source package in Xenial: Fix Committed Status in apt package in Debian: Fix Released Status in aptitude package in Debian: Fix Released Status in synaptic package in Debian: New Bug description: READ ME FIRST = This is a cosmetic issue. The warning message is just that— a warning. Though the message comes up, there is no problem with the install/upgrade happening like normal. That said, feel free to ignore it. It will get fixed, but it's nowhere near as urgent as bugs that actually result in the wrong behavior rather than just a simple extra message. update-notifier SRU --- [Impact] Cosmetic. Warnings when installing packages using update-notifier downloading stuff [Test case] Install flashplugin-installer with apt and check that the output does not contain a message like this: W: Can't drop privileges for downloading as file '...' couldn't be accessed by user '_apt' [Regression Potential] It just chowns /var/lib/update-notifier/package-data- downloads/partial/ to _apt:root, there should not be any regression. Original report --- Recently we got new versions for synaptic 0.82+build1 & apt 1.1.3, but now get that error when installing/upgrading some packages: Setting up libc6-dbg:amd64 (2.21-0ubuntu5) ... Processing triggers for libc-bin (2.21-0ubuntu5) ... W: Can't drop privileges for downloading as file '/root/.synaptic/tmp//tmp_cl' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) From nautilus, i'm seeing a /root/ folder locked (x on its icon) and the folder is empty (no /.synaptic/ sub-folder or file), so the above error. oem@u64:~$ ls -l .synaptic total 4 -rw-rw-r-- 1 oem oem 0 Aug 25 11:19 options -rw-rw-r-- 1 oem oem 236 Aug 25 11:19 synaptic.conf oem@u64:~$ ls -l /var/lib/apt/lists/ -rw-r- 1 root root0 Sep 20 06:36 lock drwx-- 2 _apt root16384 Sep 24 15:25 partial .. oem@u64:~$ sudo ls -l /var/lib/update-notifier/package-data-downloads/ . drwxr-xr-x 2 _apt root 4096 Sep 22 23:33 partial ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: synaptic 0.82+build1 ProcVersionSignature: Ubuntu 4.3.0-1.10-generic 4.3.0 Uname: Linux 4.3.0-1-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 CurrentDesktop: GNOME Date: Fri Dec 4 05:23:25 2015 SourcePackage: synaptic UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1522675/+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 1676977] Re: Login prompt never presented with ldap login and ldapi set with a name.
I'll try to get 17.04 up somewhere and test that as well. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1676977 Title: Login prompt never presented with ldap login and ldapi set with a name. Status in accountsservice package in Ubuntu: New Status in libpam-ldap package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I have a ldap login configuration that has worked with several Ubuntu versions. Unfortunately it doesn't work with 16.10. If I left my ldapi setting using a name as I used to, the login prompt never appears. If I change the ldapi setting to the IP of the authentication server, the login works perfectly. The authentication server name resolution works fine on 16.10 (after login) and on previous version even during login. It seems to me my problem is related to some ordering issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libpam-ldap 184-8.7ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-44.47-generic 4.8.17 Uname: Linux 4.8.0-44-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Tue Mar 28 14:33:27 2017 InstallationDate: Installed on 2017-03-27 (1 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: libpam-ldap UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1676977/+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 1676977] Re: Login prompt never presented with ldap login and ldapi set with a name.
The ldapi:/// worked just fine, as did ldap:// with an IP or a name. And I don't have an entry in /etc/hosts for the ldap server, I'm really using DNS. Reboot works just fine, login prompt, and I can login at the console (and via ssh) with an ldap user. I'm sorry but I will need the files I requested in comment #16. Here are mine: ubuntu@04-57:~$ cat /etc/ldap.conf | grep -vE "^(#|$)" base dc=example,dc=com uri ldap://xenial-slapd-server.lxd ldap_version 3 pam_password exop ubuntu@04-57:~$ cat /etc/ldap/ldap.conf | grep -vE "^(#|$)" URIldap://xenial-slapd.server.lxd BASE dc=example,dc=com TLS_CACERT /etc/ssl/certs/ca-certificates.crt I used these ldif files to minimally populate the ldap server: ubuntu@04-57:~$ cat base.ldif usergroup.ldif dn: ou=People,dc=example,dc=com ou: People objectClass: organizationalUnit dn: ou=Group,dc=example,dc=com ou: Group objectClass: organizationalUnit dn: uid=testuser1,ou=People,dc=example,dc=com uid: testuser1 objectClass: inetOrgPerson objectClass: posixAccount cn: testuser1 sn: testuser1 givenName: testuser1 mail: testus...@example.com userPassword: testuser1secret uidNumber: 10001 gidNumber: 10001 loginShell: /bin/bash homeDirectory: /home/testuser1 dn: cn=testuser1,ou=Group,dc=example,dc=com cn: testuser1 objectClass: posixGroup gidNumber: 10001 memberUid: testuser1 dn: cn=ldapusers,ou=Group,dc=example,dc=com cn: ldapusers objectClass: posixGroup gidNumber: 10100 memberUid: testuser1 ** Attachment added: "ldaplogin.png" https://bugs.launchpad.net/ubuntu/+source/libpam-ldap/+bug/1676977/+attachment/5067121/+files/ldaplogin.png -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1676977 Title: Login prompt never presented with ldap login and ldapi set with a name. Status in accountsservice package in Ubuntu: New Status in libpam-ldap package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: I have a ldap login configuration that has worked with several Ubuntu versions. Unfortunately it doesn't work with 16.10. If I left my ldapi setting using a name as I used to, the login prompt never appears. If I change the ldapi setting to the IP of the authentication server, the login works perfectly. The authentication server name resolution works fine on 16.10 (after login) and on previous version even during login. It seems to me my problem is related to some ordering issue. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: libpam-ldap 184-8.7ubuntu1 ProcVersionSignature: Ubuntu 4.8.0-44.47-generic 4.8.17 Uname: Linux 4.8.0-44-generic x86_64 ApportVersion: 2.20.3-0ubuntu8.2 Architecture: amd64 Date: Tue Mar 28 14:33:27 2017 InstallationDate: Installed on 2017-03-27 (1 days ago) InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: libpam-ldap UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1676977/+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 1750627] Re: Upgrade TZ do address 2018-19's Brazilian DST
tzdata 2018c release was announced in January/2018 at http://mm.icann.org/pipermail/tz-announce/2018-January/48.html -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1750627 Title: Upgrade TZ do address 2018-19's Brazilian DST Status in tzdata package in Ubuntu: Confirmed Bug description: Please upgrade Xenial and Trusty tzdata package to 2018c to address changes in 2018-2019 Brazil's DST. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1750627/+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 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS
** Description changed: Steps to reproduce: - 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE, or 17.10 or 18.04 LTS. + 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: - 1. Ubuntu 16.04 LTS with Marco and Compton work normally with keyboard layout switcher. + 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: marco 1.18.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Fri Sep 29 16:18:02 2017 InstallationDate: Installed on 2017-08-26 (33 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: marco UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1720364 Title: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS Status in MATE Desktop: New Status in ubuntu-mate: New Status in X.Org X server: Confirmed Status in marco package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Status in xorg-hwe-16.04 package in Ubuntu: Confirmed Status in xorg package in Debian: Unknown Bug description: Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE (Xorg 1.19.5), or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS (Xorg 1.18.4) with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: marco 1.18.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Fri Sep 29 16:18:02 2017 InstallationDate: Installed on 2017-08-26 (33 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: marco UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1720364/+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 1720519] Re: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load.
By commenting the lines from /etc/pulse/default.pa #.ifexists module-switch-on-connect.so #load-module module-switch-on-connect #.endif And reinstalling pulse audio and alsa-base as here: apt-get remove --purge pulseaudio rm -rf /etc/pulse apt-get install pulseaudio reboot I managed to get the audio again, but I cannot control it with the volume controls of my keyboard, neither with thw sound tray icon(that completely dissapeared) -- 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/1720519 Title: KDE/Kubuntu: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. Status in PulseAudio: Confirmed Status in pulseaudio package in Ubuntu: Triaged Bug description: Pulseaudio daemon does not start after the update to Kubuntu 17.10 beta2, because the module fails to load although it is there. From 'pulseaudio -vv' E: [pulseaudio] module.c: Module "module-switch-on-connect" should be loaded once at most. Refusing to load. E: [pulseaudio] main.c: Module load failed. E: [pulseaudio] main.c: Failed to initialize daemon. PS sorry I am not a seasoned bug reporter. Let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: pulseaudio 1:10.0-2ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic x86_64 ApportVersion: 2.20.7-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: ben2809 F...m chrome /dev/snd/controlC0: ben2809 F chrome /dev/snd/timer: ben2809 f chrome CurrentDesktop: KDE Date: Sat Sep 30 11:20:55 2017 InstallationDate: Installed on 2017-04-07 (175 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321) PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: Upgraded to artful on 2017-09-30 (0 days ago) dmi.bios.date: 10/29/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.10 dmi.board.name: B150M-ITX dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd10/29/2015:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnB150M-ITX:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/pulseaudio/+bug/1720519/+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 1750627] Re: Upgrade TZ do address 2018-19's Brazilian DST
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: tzdata (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to tzdata in Ubuntu. https://bugs.launchpad.net/bugs/1750627 Title: Upgrade TZ do address 2018-19's Brazilian DST Status in tzdata package in Ubuntu: Confirmed Bug description: Please upgrade Xenial and Trusty tzdata package to 2018c to address changes in 2018-2019 Brazil's DST. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1750627/+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 1752728] Re: My pc is going in blank after sleep and nothing works
** Information type changed from Private Security to Public -- 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/1752728 Title: My pc is going in blank after sleep and nothing works Status in xorg package in Ubuntu: New Bug description: My pc is going in blank after sleep and nothing works ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity Date: Thu Mar 1 17:12:11 2018 DistUpgraded: Fresh install DistroCodename: xenial DistroVariant: ubuntu DpkgLog: GraphicsCard: Subsystem: Dell Device [1028:0774] NVIDIA Corporation Device [10de:1c60] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell Device [1028:07c0] InstallationDate: Installed on 2017-09-27 (155 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) MachineType: Alienware Alienware 15 R3 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-36-generic.efi.signed root=UUID=55e321af-6860-4c50-a132-9e8fe6024cd7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/14/2017 dmi.bios.vendor: Alienware dmi.bios.version: 1.2.0 dmi.board.name: Alienware 15 R3 dmi.board.vendor: Alienware dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Alienware dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnAlienware:bvr1.2.0:bd09/14/2017:svnAlienware:pnAlienware15R3:pvr1.2.0:rvnAlienware:rnAlienware15R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified: dmi.product.family: Alienware dmi.product.name: Alienware 15 R3 dmi.product.version: 1.2.0 dmi.sys.vendor: Alienware version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1 version.ia32-libs: ia32-libs N/A version.libdrm2: libdrm2 2.4.83-1~16.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1 version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1 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/1752728/+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 1752844] Re: Line drawing bug in applications using opengl 1
So you mean mesa 17.2.x is buggy? Please test 17.3.3: https://launchpad.net/~ubuntu-x-swat/+archive/ubuntu/updates is the bug hw/driver specific? ** Changed in: mesa (Ubuntu) Status: New => Incomplete ** Changed in: mesa (Ubuntu) Assignee: (unassigned) => Timo Aaltonen (tjaalton) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to mesa in Ubuntu. https://bugs.launchpad.net/bugs/1752844 Title: Line drawing bug in applications using opengl 1 Status in mesa package in Ubuntu: Incomplete Bug description: On Ubuntu 16.04.3, as from the update fixing https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1735594, the line rendering in applications using Opengl 1 is incorrect. Blender and various games by Kenta Cho (tumiki-figthers, torus- trooper, parsec47, titanion) are affected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1752844/+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 1752888] [NEW] package libgstreamer0.10-0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', 它与软件包 libgstreamer0.10-0:i38
Public bug reported: package libgstreamer0.10-0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', 它与软件包 libgstreamer0.10-0:i386 中的其他实例不同 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgstreamer0.10-0 (not installed) ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 2 21:24:03 2018 ErrorMessage: 尝试覆盖共享的 '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', 它与软件包 libgstreamer0.10-0:i386 中的其他实例不同 InstallationDate: Installed on 2018-02-28 (2 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: gstreamer0.10 Title: package libgstreamer0.10-0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', 它与软件包 libgstreamer0.10-0:i386 中的其他实例不同 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gstreamer0.10 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package xenial -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gstreamer0.10 in Ubuntu. https://bugs.launchpad.net/bugs/1752888 Title: package libgstreamer0.10-0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', 它与软件包 libgstreamer0.10-0:i386 中的其他实例不同 Status in gstreamer0.10 package in Ubuntu: New Bug description: package libgstreamer0.10-0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', 它与软件包 libgstreamer0.10-0:i386 中的其他实例不同 ProblemType: Package DistroRelease: Ubuntu 16.04 Package: libgstreamer0.10-0 (not installed) ProcVersionSignature: Ubuntu 4.13.0-36.40~16.04.1-generic 4.13.13 Uname: Linux 4.13.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Fri Mar 2 21:24:03 2018 ErrorMessage: 尝试覆盖共享的 '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', 它与软件包 libgstreamer0.10-0:i386 中的其他实例不同 InstallationDate: Installed on 2018-02-28 (2 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) RelatedPackageVersions: dpkg 1.18.4ubuntu1.3 apt 1.2.25 SourcePackage: gstreamer0.10 Title: package libgstreamer0.10-0 (not installed) failed to install/upgrade: 尝试覆盖共享的 '/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', 它与软件包 libgstreamer0.10-0:i386 中的其他实例不同 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gstreamer0.10/+bug/1752888/+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 385687] Re: EOG doesn't display .svg w/ multiple lines of text properly
which is in the current bionic version ** Changed in: librsvg (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/385687 Title: EOG doesn't display .svg w/ multiple lines of text properly Status in librsvg: Fix Released Status in librsvg package in Ubuntu: Fix Released Bug description: Binary package hint: eog Both in previews in nautilus (which comes from eog, I think?) and in EOG itself, SVGs that have multiple lines of text in one 'box' show up as a solid box where you would expect to see text. By the way, the SVGs where made with inkscape. In fact, I'll attach them to this bug report. Ubuntu version: Description: Ubuntu 9.04 Release: 9.04 apt-cache policy eog eog: Installed: 2.26.1-0ubuntu1 Candidate: 2.26.1-0ubuntu1 Version table: *** 2.26.1-0ubuntu1 0 500 http://us.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/385687/+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 385687] Re: EOG doesn't display .svg w/ multiple lines of text properly
That has been fixed upstream in https://gitlab.gnome.org/GNOME/librsvg/commit/d38cb2e3 ** Changed in: librsvg (Ubuntu) Status: Triaged => Fix Committed -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/385687 Title: EOG doesn't display .svg w/ multiple lines of text properly Status in librsvg: Fix Released Status in librsvg package in Ubuntu: Fix Released Bug description: Binary package hint: eog Both in previews in nautilus (which comes from eog, I think?) and in EOG itself, SVGs that have multiple lines of text in one 'box' show up as a solid box where you would expect to see text. By the way, the SVGs where made with inkscape. In fact, I'll attach them to this bug report. Ubuntu version: Description: Ubuntu 9.04 Release: 9.04 apt-cache policy eog eog: Installed: 2.26.1-0ubuntu1 Candidate: 2.26.1-0ubuntu1 Version table: *** 2.26.1-0ubuntu1 0 500 http://us.archive.ubuntu.com jaunty/main Packages 100 /var/lib/dpkg/status To manage notifications about this bug go to: https://bugs.launchpad.net/librsvg/+bug/385687/+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 1705595] Re: g_unix_signal_source_new does not support SIGWINCH
** Changed in: glib Status: Unknown => Fix Released ** Changed in: glib Importance: Unknown => Medium -- 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/1705595 Title: g_unix_signal_source_new does not support SIGWINCH Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Released Bug description: This is a request for upstream #769534 (https://bugzilla.gnome.org/show_bug.cgi?id=769534) to be incorporated into Xenial. It is a one-line change, and was incorporated in 2.53.1. To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/1705595/+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 1752876] [NEW] sfdisk: allow disabling boot flag on MBR partition table
Public bug reported: I would like to propose the following patch for Ubuntu 18.04 LTS https://github.com/karelzak/util-linux/commit/8175ed3d74adacc895657ded7546cb3c5deeabad [Impact] * This patch allows to use sfdisk to remove boot flag from all MBR partitions. At the moment you can only "move" boot flag to other partitions. * Derivatives of Ubuntu that use Calamares might be impacted by this. At the moment KDE Partition Manager and KPMcore (which is used by Calamares installer) are working on migrating to Polkit, so that they won't need to run GUI as root. One of the steps was moving from libparted backend to sfdisk backend for partitioning operations, so kpmcore will require 2.32 or 2.31.1 with this patch to have full functionality. [Test Case] Assuming that your want to deactivate boot flag on /dev/sdb which has MBR partition table: sudo sfdisk --activate /dev/sdb - Without this patch you should see an error message. With the patch it will print: The bootable flag on partition 1 is disabled now. The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. [Regression Potential] . * Should be extremely low. The change only adds a couple of lines in one file which parses arguments of "sfdisk --activate". Nothing would change unless you run sfdisk --activate * This patch does not change any libraries in util-linux, no need to worry about API/ABI stability. * GPT users are not affected at all. [Other Info] * This patch is part of util-linux 2.32. ** Affects: util-linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to util-linux in Ubuntu. https://bugs.launchpad.net/bugs/1752876 Title: sfdisk: allow disabling boot flag on MBR partition table Status in util-linux package in Ubuntu: New Bug description: I would like to propose the following patch for Ubuntu 18.04 LTS https://github.com/karelzak/util-linux/commit/8175ed3d74adacc895657ded7546cb3c5deeabad [Impact] * This patch allows to use sfdisk to remove boot flag from all MBR partitions. At the moment you can only "move" boot flag to other partitions. * Derivatives of Ubuntu that use Calamares might be impacted by this. At the moment KDE Partition Manager and KPMcore (which is used by Calamares installer) are working on migrating to Polkit, so that they won't need to run GUI as root. One of the steps was moving from libparted backend to sfdisk backend for partitioning operations, so kpmcore will require 2.32 or 2.31.1 with this patch to have full functionality. [Test Case] Assuming that your want to deactivate boot flag on /dev/sdb which has MBR partition table: sudo sfdisk --activate /dev/sdb - Without this patch you should see an error message. With the patch it will print: The bootable flag on partition 1 is disabled now. The partition table has been altered. Calling ioctl() to re-read partition table. Syncing disks. [Regression Potential] . * Should be extremely low. The change only
[Touch-packages] [Bug 1752882] [NEW] Systemd sysv install fails with update-rc.d: error: unable to read /etc/init.d/enable
Public bug reported: The bionic builds of cloud images for one of our partners fails when installing/enabling NTP in the image during livecdrootfs build: + chroot mountpoint_gce systemctl --root / enable ntp.service Synchronizing state of ntp.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install --root=/ enable ntp update-rc.d: error: unable to read /etc/init.d/enable On Xnox's request I am filing a bug here and assigning to him. Please let me know if you need further information. ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1752882 Title: Systemd sysv install fails with update-rc.d: error: unable to read /etc/init.d/enable Status in systemd package in Ubuntu: New Bug description: The bionic builds of cloud images for one of our partners fails when installing/enabling NTP in the image during livecdrootfs build: + chroot mountpoint_gce systemctl --root / enable ntp.service Synchronizing state of ntp.service with SysV service script with /lib/systemd/systemd-sysv-install. Executing: /lib/systemd/systemd-sysv-install --root=/ enable ntp update-rc.d: error: unable to read /etc/init.d/enable On Xnox's request I am filing a bug here and assigning to him. Please let me know if you need further information. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1752882/+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 1665148] Re: Closed GtkExpander exposes underlying elements
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions at https://wiki.ubuntu.com/Bugs/Upstream/GNOME. If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance. ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1665148 Title: Closed GtkExpander exposes underlying elements Status in gtk+3.0 package in Ubuntu: New Bug description: This a very minor issue (and maybe a feature, not a bug) GTK3-based audio-recorder has a GtkExpander widget. It contains a listbox and some other elements. The listbox can be shown and activated event the GtkExpander is closed. Screenshot: http://bildr.no/view/dys1WkhP The application: https://launchpad.net/~audio-recorder To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1665148/+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 1751252] Re: ubiquity crashed with signal 5 in _XEventsQueued()
** Tags added: id-5a9829e833b1e20a0cfd336c
--
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/1751252
Title:
ubiquity crashed with signal 5 in _XEventsQueued()
Status in glib2.0 package in Ubuntu:
New
Status in ubiquity package in Ubuntu:
Triaged
Status in glib2.0 source package in Bionic:
New
Status in ubiquity source package in Bionic:
Triaged
Bug description:
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+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 1720364] Re: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS
** Bug watch added: Debian Bug tracker #891915 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891915 ** Also affects: xorg (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891915 Importance: Unknown Status: Unknown -- 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/1720364 Title: Unable to use shortcuts with keyboard layout switcher on Ubuntu MATE, 16.04 (with HWE), 17.10 and 18.04 LTS Status in MATE Desktop: New Status in ubuntu-mate: New Status in X.Org X server: Confirmed Status in marco package in Ubuntu: Confirmed Status in xorg package in Ubuntu: Confirmed Status in xorg-hwe-16.04 package in Ubuntu: Confirmed Status in xorg package in Debian: Unknown Bug description: Steps to reproduce: 1. Install ubuntu-mate-desktop on Ubuntu 16.04 LTS with HWE, or 17.10 or 18.04 LTS. 2. Set-up two keyboard layouts - English and Russian 3. Set as keyboard layout switcher 4. Try to use shortcuts starting from : 4.1. Open Firefox, open new tab, go to some site in it, close tab, try to click to restore closed tab. 4.2. Open mate-terminal, try to open new tab with , or copy (), or paste (). 4.3. Open pluma, write some text, try to navigate in it with . Expected results: switches keyboard layout, shortcuts starting from work normally. Actual results: switches keyboard layout, shortcuts starting from do not work. Notes: 1. Ubuntu 16.04 LTS with Marco and Compton work normally with keyboard layout switcher. 2. This problem was discovered before on 13.10, 14.04 and other modern versions with GNOME desktop (Metacity and Compiz) - see bug 1245473. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: marco 1.18.1-3ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-12.13-generic 4.13.3 Uname: Linux 4.13.0-12-generic i686 ApportVersion: 2.20.7-0ubuntu1 Architecture: i386 CurrentDesktop: MATE Date: Fri Sep 29 16:18:02 2017 InstallationDate: Installed on 2017-08-26 (33 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha i386 (20170826) SourcePackage: marco UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mate-desktop/+bug/1720364/+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 1707606] Re: [nautilus] no sidebar mouseover selection displayed
Marco, could you have a look to that one once we enter the bugfixing part of the cycle (and when you look at refreshing our theme)? ** Changed in: ubuntu-themes (Ubuntu) Importance: Undecided => Low ** Changed in: ubuntu-themes (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-themes (Ubuntu) Assignee: (unassigned) => Marco Trevisan (Treviño) (3v1n0) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to ubuntu-themes in Ubuntu. https://bugs.launchpad.net/bugs/1707606 Title: [nautilus] no sidebar mouseover selection displayed Status in ubuntu-themes package in Ubuntu: Confirmed Bug description: Using nautilus 3.24 in artful, if you dnd a file over one of the folders in the sidebar with Adwaita you get a green selection displayed around the target entry. When using Ambiance there is no such indication To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-themes/+bug/1707606/+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 1751252] Re: ubiquity crashed with signal 5 in _XEventsQueued()
Steve, what makes you think it might be a glib issue?
--
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/1751252
Title:
ubiquity crashed with signal 5 in _XEventsQueued()
Status in glib2.0 package in Ubuntu:
New
Status in ubiquity package in Ubuntu:
Triaged
Status in glib2.0 source package in Bionic:
New
Status in ubiquity source package in Bionic:
Triaged
Bug description:
Crashed in a VM in the middle of installation. The host is Bionic up
to date.
From the journal
Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3
ip:7f5a76936961 sp:7ffde5090c50 error:0 in
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 757, in
Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 135, in run
Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/share/ubiquity/install.py", line 505, in copy_all
Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 +
copy_progress)
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 83, in
Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw:
self.command(command, *args, **kw))
Feb 23 12:52:41 ubuntu /install.py[6858]: File
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for
int() with base 10: ''
ProblemType: Crash
DistroRelease: Ubuntu 18.04
Package: ubiquity 18.04.1
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
Date: Fri Feb 23 12:52:28 2018
ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr
keyboard-configuration/variantcode=oss
InterpreterPath: /usr/bin/python3.6
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
LANG=C.UTF-8
SHELL=/bin/bash
Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
Signal: 5
SourcePackage: ubiquity
StacktraceTop:
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
_XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: ubiquity crashed with signal 5 in _XEventsQueued()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1751252/+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
