[Touch-packages] [Bug 1845802] Re: Corrupt/skewed gnome-shell panel rendering

[Daniel van Vugt]

** Summary changed:

- Smeared top panel and hint tips on Plank and browser icon
+ Corrupt/skewed gnome-shell panel rendering

** Tags added: radeon

** Summary changed:

- Corrupt/skewed gnome-shell panel rendering
+ [radeon] Corrupt/skewed gnome-shell panel rendering

** Package changed: xorg (Ubuntu) => mutter (Ubuntu)

** Also affects: gnome-shell (Ubuntu)
   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/1845802

Title:
  [radeon] Corrupt/skewed gnome-shell panel rendering

Status in gnome-shell package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  It would take more than one snapshot, but this all happens on Dell
  external monitor:

  1. Top panel has blurred/smeared icons.
  2. Hint tips on browser icons are also smeared.
  3. Plank tips are smeared or blurry on some icons.

  Screenshot after exiting full screen (could not restore to full) and top 
panel was set to autohide and would not budge.
  https://justpaste.it/7rqzp

  Otherwise, everything is okay on laptop monitor itself.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: Budgie:GNOME
  Date: Sat Sep 28 13:23:08 2019
  DistUpgraded: Fresh install
  DistroCodename: eoan
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Seymour [Radeon HD 6400M/7400M 
Series] [1002:6760] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 6470M [103c:161e]
  InstallationDate: Installed on 2019-09-28 (0 days ago)
  InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic 
root=UUID=64852f66-77ef-4b0f-b326-aec23cfe7db3 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/06/2017
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.65
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.4E
  dmi.chassis.asset.tag: CNU148133S
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.65:bd04/06/2017:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.4E:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.sku: LQ168AW#ABA
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.1.6-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20190820-0ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845802/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1805183] Re: systemd-resolved constantly restarts on Bionic upgraded from Xenial

[Louis Bouchard]

Ok, I'll have a look at it; I only backported the Eoan fix to Bionic

-- 
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/1805183

Title:
  systemd-resolved constantly restarts on Bionic upgraded from Xenial

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  Won't Fix
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  Log noise due to needless restart of resolved on lease expiry, maybe loss of 
cached state?
  Application that require Name Resolution may fail while the service is being 
unnecessarily restarted

  [Test case]
  (1) Append make_resolv_conf to the end of the file, so it gets executed
  (2) Execute the file with bash -x and different settings and ensure there are 
no restarts if the settings are the same, and that there are if settings 
change; for example:

  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart
  sudo new_domain_name_servers=8.8.8.8 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => no restart
  sudo new_domain_name_servers=8.8.4.4 interface="wlp61s0" reason=REBIND bash 
-x debian/extra/dhclient-enter-resolved-hook
  => should restart

  [Regression potential]
  The change only restarts resolved when the settings change. If there's a bug 
in the logic, resolved might not be restarted when it should be. Also, since 
there will be less restarts of resolved, it will run longer, so if there are 
memory leaks they will become more apparent.

  [Original bug report]
  If a cloud server is upgraded from Xenial to Bionic, the dhclient system 
remains in place and any DHCP lease refreshes cause a needless restart of the 
system-resolved daemon

  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPREQUEST of 10.226.209.106 on 
ens3 to 10.226.209.105 port 67 (xid=0x2bd41d7d)
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: DHCPACK of 10.226.209.106 from 
10.226.209.105
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopping Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Stopped Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting Network Name Resolution...
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Positive Trust Anchors:
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 1
  Nov 26 16:59:41 srv-qvjhx systemd-resolved[1609]: Using system hostname 
'srv-qvjhx'.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started Network Name Resolution.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Starting 
resolvconf-pull-resolved.service...
  Nov 26 16:59:41 srv-qvjhx dhclient[825]: bound to 10.226.209.106 -- renewal 
in 1466 seconds.
  Nov 26 16:59:41 srv-qvjhx systemd[1]: Started 
resolvconf-pull-resolved.service.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.25
  ProcVersionSignature: Ubuntu 4.4.0-139.165-generic 4.4.160
  Uname: Linux 4.4.0-139-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CrashDB: ubuntu
  Date: Mon Nov 26 16:17:52 2018
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1805183/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1844763] Re: file /etc/network/interfaces is missing in eoan-desktop-amd64.iso

[vmware-gos-Yuhua]

No file /etc/network/interfaces in ubuntu-19.10-beta-desktop-amd64.iso.

-- 
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/1844763

Title:
  file /etc/network/interfaces is missing in eoan-desktop-amd64.iso

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The file /etc/network/interfaces is missing after install guestOS with
  eoan-desktop-amd64.iso(daily build Sep-17-2019) in ESXi.

  This issue cause a failure for VMware Guest OS Customization

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1844763/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1843754] Re: mir ftbfs in eoan (ppc64el)

[Chris Halse Rogers]

** Changed in: mir (Ubuntu)
   Status: Confirmed => Fix Released

-- 
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/1843754

Title:
  mir ftbfs in eoan (ppc64el)

Status in mir package in Ubuntu:
  Fix Released

Bug description:
  https://launchpadlibrarian.net/441268300/buildlog_ubuntu-eoan-
  ppc64el.mir_1.1.1-0ubuntu3_BUILDING.txt.gz

  63% tests passed, 159 tests failed out of 424

  Total Test time (real) = 603.12 sec

  The following tests FAILED:
  5 - miral_wlcs_tests.BadBufferTest.* (Failed)
  7 - miral_wlcs_tests.CopyCutPaste.* (Failed)
  8 - miral_wlcs_tests.ClientSurfaceEventsTest.* (Failed)
  9 - miral_wlcs_tests.FrameSubmission.* (Failed)
 10 - miral_wlcs_tests.XdgSurfaceV6Test.* (Failed)
 11 - miral_wlcs_tests.XdgToplevelV6Test.* (Failed)
 12 - miral_wlcs_tests.XdgToplevelV6ConfigurationTest.* (Failed)
 13 - miral_wlcs_tests.XdgSurfaceStableTest.* (Failed)
 14 - miral_wlcs_tests.XdgToplevelStableTest.* (Failed)
 15 - miral_wlcs_tests.XdgToplevelStableConfigurationTest.* (Failed)
 16 - miral_wlcs_tests.SelfTest.* (Failed)
 17 - miral_wlcs_tests.TestServer.* (Failed)
 18 - 
miral_wlcs_tests.PointerCrossingSurfaceCorner/SurfacePointerMotionTest.* 
(Failed)
 19 - 
miral_wlcs_tests.PointerCrossingSurfaceEdge/SurfacePointerMotionTest.* (Failed)
 20 - miral_wlcs_tests.WlShellSurface/TouchTest.* (Failed)
 21 - miral_wlcs_tests.XdgShellV6Surface/TouchTest.* (Failed)
 22 - miral_wlcs_tests.XdgShellStableSurface/TouchTest.* (Failed)
 23 - miral_wlcs_tests.Subsurface/TouchTest.* (Failed)
 24 - miral_wlcs_tests.NormalRegion/SurfaceWithInputRegions.* (Failed)
 25 - miral_wlcs_tests.SmallerRegion/SurfaceWithInputRegions.* (Failed)
 26 - miral_wlcs_tests.ClippedLargerRegion/SurfaceWithInputRegions.* 
(Failed)
 27 - miral_wlcs_tests.MultiRectRegionEdges/SurfaceWithInputRegions.* 
(Failed)
 28 - miral_wlcs_tests.MultiRectRegionCorners/SurfaceWithInputRegions.* 
(Failed)
 29 - miral_wlcs_tests.WlShellSurface/SurfaceTypesWithInputRegion.* 
(Failed)
 30 - miral_wlcs_tests.XdgShellV6Surface/SurfaceTypesWithInputRegion.* 
(Failed)
 31 - 
miral_wlcs_tests.XdgShellStableSurface/SurfaceTypesWithInputRegion.* (Failed)
 32 - miral_wlcs_tests.Subsurface/SurfaceTypesWithInputRegion.* (Failed)
 33 - miral_wlcs_tests.WlShellSubsurfaces/SubsurfaceTest.* (Failed)
 34 - miral_wlcs_tests.XdgShellV6Subsurfaces/SubsurfaceTest.* (Failed)
 35 - miral_wlcs_tests.XdgShellStableSubsurfaces/SubsurfaceTest.* 
(Failed)
 36 - miral_wlcs_tests.TouchInputSubsurfaces/SubsurfaceTest.* (Failed)
 37 - miral_wlcs_tests.Default/XdgPopupV6Test.* (Failed)
 38 - miral_wlcs_tests.Anchor/XdgPopupV6Test.* (Failed)
 39 - miral_wlcs_tests.Gravity/XdgPopupV6Test.* (Failed)
 40 - miral_wlcs_tests.AnchorRect/XdgPopupV6Test.* (Failed)
 41 - miral_wlcs_tests.Default/XdgPopupStableTest.* (Failed)
 42 - miral_wlcs_tests.Anchor/XdgPopupStableTest.* (Failed)
 43 - miral_wlcs_tests.Gravity/XdgPopupStableTest.* (Failed)
 44 - miral_wlcs_tests.AnchorRect/XdgPopupStableTest.* (Failed)
 45 - miral_wlcs_tests.ZeroSizeAnchorRect/XdgPopupStableTest.* (Failed)
 46 - mir_acceptance_tests.ServerSignalDeathTest.* (Failed)
 47 - mir_acceptance_tests.ServerShutdownDeathTest.* (Failed)
 48 - mir_acceptance_tests.ServerDisconnectDeathTest.* (Failed)
 49 - mir_acceptance_tests.ClientLibraryErrorsDeathTest.* (Failed)
 50 - mir_acceptance_tests.ServerSignal/AbortDeathTest.* (Timeout)
 51 - mir_acceptance_tests.ServerShutdown/OnSignalDeathTest.* (Timeout)
 52 - mir_acceptance_tests.ClientMediatedUserGestures.* (Failed)
 53 - mir_acceptance_tests.DragAndDrop.* (Failed)
 54 - mir_acceptance_tests.ServerConfigurationWrapping.* (Failed)
 56 - mir_acceptance_tests.ServerSignal.* (Failed)
 57 - mir_acceptance_tests.ServerStopCallback.* (Failed)
 58 - mir_acceptance_tests.ApplicationNotRespondingDetection.* (Failed)
 60 - mir_acceptance_tests.TestClientInput.* (Failed)
 61 - mir_acceptance_tests.TestClientInputKeyRepeat.* (Failed)
 62 - mir_acceptance_tests.TestClientInputWithTwoScreens.* (Failed)
 63 - mir_acceptance_tests.ClientLibraryCallbacks.* (Failed)
 64 - mir_acceptance_tests.ClientLibraryThread.* (Failed)
 65 - mir_acceptance_tests.ClientSurfaceEvents.* (Failed)
 66 - mir_acceptance_tests.ClientSurfaceStartupEvents.* (Failed)
 67 - mir_acceptance_tests.ClientSurfaceCreationResizeEvent.* (Failed)
 68 - mir_acceptance_tests.SurfaceSwapBuffers.* (Failed)
 69 - 

[Touch-packages] [Bug 1845825] Re: i2c_designware and i2c_hid failures on shutdown

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1845825

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu)

** Changed in: linux (Ubuntu)
   Status: New => Incomplete

-- 
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/1845825

Title:
  i2c_designware and i2c_hid failures on shutdown

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  1. Using Ubuntu 19.10
  2. Shutdown system
  3. System get stuck at the windows with this messages:

  i2c_designware.o: controller timed out
  i2c_hid: failed to change power settings.

  It might not be related to the shutdown not happening, still that's
  the only clue I have.

  I attach the screenshot and dmesg output after the following boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845825/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1048203] Re: (CVE-2012-4412) glibc: strcoll() integer overflow leading to buffer overflow

[Bug Watch Updater]

** Changed in: fedora
   Status: Confirmed => Won't Fix

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to eglibc in Ubuntu.
https://bugs.launchpad.net/bugs/1048203

Title:
  (CVE-2012-4412) glibc: strcoll() integer overflow leading to buffer
  overflow

Status in GLibC:
  Fix Released
Status in eglibc package in Ubuntu:
  Fix Released
Status in eglibc package in Debian:
  Fix Released
Status in Fedora:
  Won't Fix
Status in Gentoo Linux:
  Fix Released

Bug description:
  An integer overflow, leading to buffer overflow flaw was found in the
  way the implementation of strcoll() routine, used to compare two
  strings based on the current locale, of glibc, the GNU libc libraries,
  performed calculation of memory requirements / allocation, needed for
  storage of the strings. If an application linked against glibc was
  missing an application-level sanity checks for validity of strcoll()
  arguments and accepted untrusted input, an attacker could use this
  flaw to cause the particular application to crash or, potentially,
  execute arbitrary code with the privileges of the user running the
  application.

  Upstream bug report (including reproducer):
  [1] http://sourceware.org/bugzilla/show_bug.cgi?id=14547

To manage notifications about this bug go to:
https://bugs.launchpad.net/glibc/+bug/1048203/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

[Daniel van Vugt]

Sorry I lost track of this bug. The attachment in comment #7 shows:

HDMI-1 connected 1920x1080+1366+0 (0x8b) normal (normal left inverted
right x axis y axis) 160mm x 90mm

So the hardware is indeed reporting itself as ~7.2 inches. This is a
hardware fault (incorrect EDID data?) I have seen before. Probably the
best we can hope for is to add heuristics to detect faulty hardware, but
that would be unreliable and unlikely to ever happen.


** Changed in: mutter (Ubuntu)
   Status: Confirmed => Invalid

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Confirmed => Invalid

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1792167

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  My external monitor is detected as 7" although it is 32". All
  applications which use Qt auto scaling have huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  It seems not related to the display server, compositor or window
  manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as
  well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on
  Wayland).

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1792167] Re: Display size detected incorrectly

[Daniel van Vugt]

** Changed in: mutter (Ubuntu)
   Status: Expired => New

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: Expired => Confirmed

** Changed in: mutter (Ubuntu)
   Status: New => Confirmed

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1792167

Title:
  Display size detected incorrectly

Status in mutter package in Ubuntu:
  Invalid
Status in qtbase-opensource-src package in Ubuntu:
  Invalid

Bug description:
  My external monitor is detected as 7" although it is 32". All
  applications which use Qt auto scaling have huge controls!

  It seems like many users have the same problem
  (https://ubuntuforums.org/showthread.php?t=2390362) and thus disable
  Qt auto scaling. I think the solution should be to fix the size
  detection instead.

  It seems not related to the display server, compositor or window
  manager since the problem appeared in Ubuntu 17.04 (Mir, Unity) as
  well es 18.04 (Mutter, Gnome). I tried it with both Wayland and X (on
  Wayland).

  Further, it seems not related to graphics driver, since I personally
  use the open source driver with my internal Intel card, whereas
  someone else uses a proprietary Nvidia driver
  (https://askubuntu.com/q/1066879/206608).

  If it is in the wrong category, please move it / add the corresponding
  packages.

  If you need any further information to tackle the problem, just tell me!
  ---
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-09-05 (372 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Package: qtbase-opensource-src
  PackageArchitecture: amd64
  Tags:  bionic
  Uname: Linux 4.18.7-041807-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom davfs2 dip docker lpadmin plugdev sambashare sudo 
vboxusers video voice
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1792167/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1767322] Re: "Activation of network connection failed" popup shows incessantly

[Ghost]

Oddly i have had the same issue and I today i was getting annoyed so i
went to wifi and switched from my 5G to 2.4 and it has been solid since.
I will update if anything changes. Can finally not have to run a
constant ping to keep it alive. on 5G when running a constant ping that
would prevent the issue from happening

-- 
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/1767322

Title:
  "Activation of network connection failed" popup shows incessantly

Status in linux package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  All network connections work normally, however the popup "Activation
  of network connection failed" keeps showing.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 27 20:04:56 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-04-03 (24 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180402)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0 proto dhcp metric 600 
   169.254.0.0/16 dev virbr1 scope link metric 1000 linkdown 
   192.168.1.0/24 dev wlp2s0 proto kernel scope link src 192.168.1.128 metric 
600 
   192.168.100.0/24 dev virbr1 proto kernel scope link src 192.168.100.1 
linkdown 
   192.168.122.0/24 dev virbr0 proto kernel scope link src 192.168.122.1 
linkdown
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767322/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1840640] Re: sync_file_range fails in nspawn containers on arm, ppc

[Dan Streetman]

** Also affects: systemd (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

** Tags added: next-ddstreet systemd

-- 
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/1840640

Title:
  sync_file_range fails in nspawn containers on arm, ppc

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  New

Bug description:
  ARM has two sync_file_range syscalls, sync_file_range and
  sync_file_range2. The former is apparently not used, and glibc calls
  the latter whenever a userspace program calls sync_file_range. I'm
  guessing systemd-nspawn doesn't know this, because the follow code
  consistently fails in an nspawn container on ARM:

  #define _GNU_SOURCE
  #include 
  #include 
  #include 
  #include 

  void main()
  {
  int f = open("/tmp/syncrange.test",O_CREAT|O_RDWR,0666);
  int r=sync_file_range(f, 0, 0, 0);
  if (r)
  perror("sync_file_range");
  close(f);
  }

  This seems to be causing problems specifically for borg(backup) and
  postgres:

  https://github.com/borgbackup/borg/issues/4710
  
https://www.postgresql.org/message-id/flat/CA%2BhUKG%2BydOUT4zjxb6QmJWy8U9WbC-q%2BJWV7wLsEY9Df%3Dmw0Mw%40mail.gmail.com#ac8f14897647dc7eae3c7e7cbed36d93

  The solution should be to cherrypick
  https://github.com/systemd/systemd/pull/13352, I am currently waiting
  for systemd to rebuild on a slow ARM box. Any chance of an SRU?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd-container 237-3ubuntu10.24
  Uname: Linux 4.14.66+ armv7l
  NonfreeKernelModules: extcon_usb_gpio
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: armhf
  Date: Mon Aug 19 11:10:48 2019
  ProcEnviron:
   TERM=screen
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1840640/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1841928] Re: systemd service file not triggering the bash script

[Dan Streetman]

I just tested this and it works fine.  Maybe your problem is that you
have your bootscript path set to "/usr/bin/local/" (which doesn't exist
by default) when you meant "/usr/local/bin" (which does exist)?

In any case this seems 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/1841928

Title:
  systemd  service file not triggering the bash script

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=16.04
  DISTRIB_CODENAME=xenial
  DISTRIB_DESCRIPTION="Ubuntu 16.04.6 LTS"

  systemd:
Installed: 229-4ubuntu21.21
Candidate: 229-4ubuntu21.22
Version table:
   229-4ubuntu21.22 500
  500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu 
xenial-updates/main amd64 Packages
   *** 229-4ubuntu21.21 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://eu-central-1.ec2.archive.ubuntu.com/ubuntu xenial/main 
amd64 Packages

  Computer type: AWS EC2 instance

  I am creating a systemd service file like this:

  ##
  bootscript=/usr/bin/local/luksautomount.sh
  servicename=luksautomount

  cat > $bootscript <> /tmp/it-works
  EOF

  chmod +x $bootscript

  cat > /etc/systemd/system/$servicename.service 

[Touch-packages] [Bug 1843007] Re: namespace: make MountFlags=shared work again

[Dan Streetman]

** Also affects: systemd (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

** Tags added: next-ddstreet

-- 
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/1843007

Title:
  namespace: make MountFlags=shared work again

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New

Bug description:
  Systemd in Bionic fails to handle MountFlags correctly. Would you mind
  to include
  
https://github.com/systemd/systemd/commit/37ed15d7edaf59a1fc7c9e3552cd93a83f3814ef
  into Bionic? This bug seriously affects Docker > 18.6, see the Docker
  release notes for 18.09.1 (https://docs.docker.com/engine/release-
  notes/#18091).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1843007/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1843352] Re: systemd package version 237-3ubuntu10.28 breaks local network DNS resolution

[Dan Streetman]

** Changed in: systemd (Ubuntu)
   Status: New => Incomplete

-- 
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/1843352

Title:
  systemd package version 237-3ubuntu10.28 breaks local network DNS
  resolution

Status in systemd package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to the latest package the systemd-resolved service
  fails to resolve names for local network.Manually invoking nslookup
  works fine.

  The only suspicious output from journalctl seems:
  systemd-resolved[858]: Server returned error NXDOMAIN, mitigating potential 
DNS violation DVE-2018-0001, retrying transaction with reduced feature level 
UDP.

  The latest change in that package is:
   * SECURITY UPDATE: Unprivileged users are granted access to privileged
  systemd-resolved D-Bus methods
  - d/p/0001-shared-but-util-drop-trusted-annotation-from-bus_ope.patch:
drop trusted annotation from bus_open_system_watch_bind()
  - CVE-2019-15718

   -- Chris Coulson   Thu, 29 Aug 2019
  23:30:33 +0100

  Please revert this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1843352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes

[Dan Streetman]

** Tags added: next-ddstreet

-- 
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/1839290

Title:
  systemd doesn't restart a service after crashes

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  Fix Released

Bug description:
  Affected versions of OS and systemd:
  $ cat /etc/issue
  Ubuntu 16.04.6 LTS \n \l
  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Affected packages:
  systemd 229-4ubuntu21.22 and previous versions.

  Expected behaviour you didn't see:
  Scheduling restart of failed service.
  A process crashed by sigabrt and didn't restart.

  Description:
  The bug was reported to a systemd upstream repository: 
https://github.com/systemd/systemd/issues/11456
  The bug was fixed and accepted to the master branch: 
https://github.com/systemd/systemd/pull/11467/files

  Action:
  Include this patch to Ubuntu 16.04 and other version of Ubuntu which are 
supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839290/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes

[Dan Streetman]

** Changed in: systemd (Ubuntu Disco)
   Status: New => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1839290

Title:
  systemd doesn't restart a service after crashes

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  Fix Released

Bug description:
  Affected versions of OS and systemd:
  $ cat /etc/issue
  Ubuntu 16.04.6 LTS \n \l
  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Affected packages:
  systemd 229-4ubuntu21.22 and previous versions.

  Expected behaviour you didn't see:
  Scheduling restart of failed service.
  A process crashed by sigabrt and didn't restart.

  Description:
  The bug was reported to a systemd upstream repository: 
https://github.com/systemd/systemd/issues/11456
  The bug was fixed and accepted to the master branch: 
https://github.com/systemd/systemd/pull/11467/files

  Action:
  Include this patch to Ubuntu 16.04 and other version of Ubuntu which are 
supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839290/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1839290] Re: systemd doesn't restart a service after crashes

[Dan Streetman]

** Also affects: systemd (Ubuntu Disco)
   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/1839290

Title:
  systemd doesn't restart a service after crashes

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Xenial:
  New
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  Fix Released

Bug description:
  Affected versions of OS and systemd:
  $ cat /etc/issue
  Ubuntu 16.04.6 LTS \n \l
  $ systemd --version
  systemd 229
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ -LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN

  Affected packages:
  systemd 229-4ubuntu21.22 and previous versions.

  Expected behaviour you didn't see:
  Scheduling restart of failed service.
  A process crashed by sigabrt and didn't restart.

  Description:
  The bug was reported to a systemd upstream repository: 
https://github.com/systemd/systemd/issues/11456
  The bug was fixed and accepted to the master branch: 
https://github.com/systemd/systemd/pull/11467/files

  Action:
  Include this patch to Ubuntu 16.04 and other version of Ubuntu which are 
supported.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1839290/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1842352] Re: autopkgtest: boot-and-services test fails in armhf containers

[Dan Streetman]

> masking Apparmor test only on arm

er, the is_container check is enough (although just ignores the
problem), you don't need to also check for arm.

-- 
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/1842352

Title:
  autopkgtest: boot-and-services test fails in armhf containers

Status in systemd package in Ubuntu:
  New

Bug description:
  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-eoan/eoan/armhf/s/systemd/20190902_092319_bc0af@/log.gz

  ...
  test_udev (__main__.ServicesTest) ... skipped 'udev does not work in 
containers'

  ==
  ERROR: test_profile (__main__.AppArmorTest)
  AppArmor confined unit
  --
  Traceback (most recent call last):
File 
"/tmp/autopkgtest.3bj70k/build.TYC/src/debian/tests/boot-and-services", line 
286, in test_profile
  subprocess.check_call(['apparmor_parser', '-r', '-v', aa_profile.name])
File "/usr/lib/python3.7/subprocess.py", line 347, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['apparmor_parser', '-r', '-v', 
'/tmp/aa_violator.hg3olay4']' returned non-zero exit status 243.

  --
  Ran 23 tests in 5.848s

  FAILED (errors=1, skipped=5)

  ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1842352/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1759836] Re: systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

[Dan Streetman]

@stan thanks for testing on Disco.

if anyone can please test the package on Bionic, that would be
appreciated, this fix won't be released until someone affected by this
problem tests the proposed fix and verifies it fixes it.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to bluez in Ubuntu.
https://bugs.launchpad.net/bugs/1759836

Title:
  systemd-udevd consumes 100% of CPU due to hid2hci udev rule from bluez

Status in linux:
  Confirmed
Status in The Ubuntu Power Consumption Project:
  New
Status in bluez package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Invalid
Status in bluez source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Invalid
Status in bluez source package in Disco:
  Fix Committed
Status in linux source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Invalid
Status in bluez source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Invalid
Status in systemd source package in Eoan:
  Invalid
Status in bluez package in Debian:
  New

Bug description:
  [impact]

  on specific Dell systems, with a specific usb bluetooth device built-
  in, the udev rule 'hid2hci' provided by the 'bluez' package causes an
  endless loop of uevents resulting from 'bind' or 'unbind' kernel
  uevents.  These new events were added to the kernel after the
  'hid2hci' udev rule was written.

  [test case]

  the specific Dell system is required to be able to reproduce this, or
  at least the specific usb bluetooth hardware included in that system.

  Reproducing this is reportedly easy, for example comment 75 indicates
  it happens on every boot.

  When this happens, any process monitor (e.g. ps, top, etc) will show
  the 'udevd' process using 100% of a cpu, and 'udevadm monitor' should
  show repeated 'bind' and 'unbind' events as mentioned in comment 39.

  [regression potential]

  as this alters what kernel uevents the 'hid2hci' udev rule processes,
  regressions would involve the affected usb bluetooth device failing to
  be set up, or otherwise not processing the uevents correctly.

  [other info]

  this is not fixed yet upstream, as of my last check, but has been
  submitted upstream as mentioned in comment 95.

  
  original description:

  --

  
  The systemd-udevd proccess consumes 100% of a thread everytime, but i'm not 
noticing any difference in my computer.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Mar 29 08:52:54 2018
  InstallationDate: Installed on 2018-03-05 (23 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180304)
  MachineType: Dell Inc. Inspiron N5010
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-13-generic 
root=UUID=3c29e292-f1ae-45e1-a0ed-a82524278ce1 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf

   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 08R0GW
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A12
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A12
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd01/25/2011:svnDellInc.:pnInspironN5010:pvrA12:rvnDellInc.:rn08R0GW:rvrA12:cvnDellInc.:ct8:cvrA12:
  dmi.product.name: Inspiron N5010
  dmi.product.version: A12
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel/+bug/1759836/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1831787] Re: Bogus routes after DHCP lease change

[Dan Streetman]

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/12490
   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/1831787

Title:
  Bogus routes after DHCP lease change

Status in netplan:
  Invalid
Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  Triaged

Bug description:
  Netplan config:

  network:
version: 2
renderer: networkd
ethernets:
  eno4:
dhcp4: no
  eno1np0:
dhcp4: no
addresses: 
  - 172.16.0.2/24
bridges:
  br0:
dhcp4: yes
interfaces:
  - eno4

  On initial boot, machine got 10.0.15.109 IP address:

  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: Configured
  May 03 13:09:41 ceph2 systemd-networkd[29349]: br0: DHCPv4 address 
10.0.15.109/23 via 10.0.15.253

  At one point, DHCP server reserver this IP address and client
  eventually picked up new IP address:

  May 03 15:01:12 ceph2 systemd-networkd[1137]: br0: DHCPv4 address
  10.0.15.128/23 via 10.0.15.253

  This resulted in IP addresses:

  # ip -o a
  1: loinet 127.0.0.1/8 scope host lo\   valid_lft forever 
preferred_lft forever
  1: loinet6 ::1/128 scope host \   valid_lft forever preferred_lft 
forever
  2: eno1np0inet 172.16.0.2/24 brd 172.16.0.255 scope global eno1np0\   
valid_lft forever preferred_lft forever
  2: eno1np0inet6 fe80::b226:28ff:fe53:56be/64 scope link \   valid_lft 
forever preferred_lft forever
  6: br0inet 10.0.15.128/23 brd 10.0.15.255 scope global dynamic br0\   
valid_lft 503sec preferred_lft 503sec
  6: br0inet6 fe80::b8d7:5eff:fe6b:62a/64 scope link \   valid_lft 
forever preferred_lft forever

  So far, everything is fine. But, the routes on the machine are bogus:

  # ip r
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.109 metric 100 
  default via 10.0.15.253 dev br0 proto dhcp src 10.0.15.128 metric 100 
  10.0.14.0/23 dev br0 proto kernel scope link src 10.0.15.128 
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.109 metric 100 
  10.0.15.253 dev br0 proto dhcp scope link src 10.0.15.128 metric 100 
  172.16.0.0/24 dev eno1np0 proto kernel scope link src 172.16.0.2 

  routes with src 10.0.15.109 should have been removed when lease was
  renewed. I'm not sure if this is a bug in netplan or systemd. This is
  18.04, systemd 37-3ubuntu10.21, netplan 0.40.1~18.04.4.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1831787/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1823171] Re: systemd-resolve hides DS records in explicit queries

[Dan Streetman]

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Dan Streetman (ddstreet)

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu)
   Status: New => In Progress

** Tags added: systemd

-- 
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/1823171

Title:
  systemd-resolve hides DS records in explicit queries

Status in systemd package in Ubuntu:
  In Progress

Bug description:
  When querying for DS resource records on a DNSSEC signed domain using
  dig, the DS records are not shown when the system is using systemd-
  resolve.

  Run: dig +short DS ripe.net

  Expected: something like
  40991 8 2 D8D3C88263D58930A8B5FE16427130AB84CA73A4988385B2F4B121A7 2E5299A6

  Actual result: no output.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.15
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Thu Apr  4 14:14:06 2019
  MachineType: MSI MS-7A70
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=/dev/mapper/system-slash ro
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/03/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.80
  dmi.board.asset.tag: Default string
  dmi.board.name: B250M PRO-VDH (MS-7A70)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.80:bd07/03/2018:svnMSI:pnMS-7A70:pvr2.0:rvnMSI:rnB250MPRO-VDH(MS-7A70):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: Default string
  dmi.product.name: MS-7A70
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823171/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1836461] Re: DirectoryMode is not considered in systemd automount

[Dan Streetman]

I marked this as invalid, but if you do believe there is a bug I missed
please feel free to reopen to clarify.

-- 
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/1836461

Title:
  DirectoryMode is not considered in systemd automount

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  With the following systemd mount unit file

  [Unit]
  Description=Additional drive

  [Mount]
  What=/dev/disk/by-label/some-label
  Where=/media/disk-with-some-label
  DirectoryMode=0777

  [Install]
  WantedBy=multi-user.target

  and the following automount unit file

  [Unit]
  Description=Automount Additional Drive

  [Automount]
  Where=/media/disk-with-some-label
  DirectoryMode=0777

  [Install]
  WantedBy=multi-user.target

  If I do 
  systemctl start 

  and check the permissions on /media/disk-with-some-label it is 0755 instead 
of 0777. I checked that 
  /media/disk-with-some-label did not exist before starting the service.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.24
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 13 22:58:08 2019
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5ee Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook 15 G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--notebook--vg-root ro nomodeset nosplash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q70 Ver. 01.01.05
  dmi.board.name: 842A
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 15.2B.00
  dmi.chassis.asset.tag: 5CD8394RP8
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.01.05:bd08/07/2018:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.2B.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 15
  dmi.product.name: HP ZBook 15 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1836461/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1836461] Re: DirectoryMode is not considered in systemd automount

[Dan Streetman]

> DirectoryMode=0777

so, you might misunderstand what this parameter does; with the mount and
automount units, it sets the mode *only* for directories that need to be
created *up to* the actual mountpoint.  So if you had:

[Mount]
What=/dev/disk/by-label/some-label
Where=/media/one/two/disk-with-some-label
DirectoryMode=0777

then the dirs /media/one and /media/one/two will be (note: [1]) mode
0777.  However, /media/one/two/disk-with-some-label will not be affected
by DirectoryMode, for both automount and mount units.

For mount units, the directory that is the actual mountpoint has its
mode replaced by the actual mode of the root directory of the mount.
For example:

root@lp1836461:/tmp# ls -ld a
drwxr-xr-x 2 root root 4096 Sep 29 20:59 a
root@lp1836461:/tmp# mount /dev/sda1 a
root@lp1836461:/tmp# ls -ld a
drwx-- 3 root root 1024 Sep 29 20:02 a
root@lp1836461:/tmp# umount a
root@lp1836461:/tmp# ls -ld a
drwxr-xr-x 2 root root 4096 Sep 29 20:59 a

in that example /tmp/a has mode 0755, while the root directory in the
filesystem at /dev/sda1 has mode 0700.  The DirectoryMode specified to
the mount unit will not change the filesystem's root dir mode.

For automount units, the DirectoryMode similarly only sets the mode for
newly created dirs leading up to the actual mountpoint.  Additionally,
while the mountpoint is waiting for automount, its mode is set to 0755,
but that doesn't matter because any actual access to the directory (e.g.
ls) will cause it to automount the filesystem, which will replace the
'fake' 0755 mode with the actual mode of the filesystem's root dir.


[1] - looks like there is a bug upstream that sets intermediate
automount dirs to 0555, which I'll open a bug for, but for the
description of your use, that doesn't appear important.

** 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/1836461

Title:
  DirectoryMode is not considered in systemd automount

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  With the following systemd mount unit file

  [Unit]
  Description=Additional drive

  [Mount]
  What=/dev/disk/by-label/some-label
  Where=/media/disk-with-some-label
  DirectoryMode=0777

  [Install]
  WantedBy=multi-user.target

  and the following automount unit file

  [Unit]
  Description=Automount Additional Drive

  [Automount]
  Where=/media/disk-with-some-label
  DirectoryMode=0777

  [Install]
  WantedBy=multi-user.target

  If I do 
  systemctl start 

  and check the permissions on /media/disk-with-some-label it is 0755 instead 
of 0777. I checked that 
  /media/disk-with-some-label did not exist before starting the service.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.24
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 13 22:58:08 2019
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5ee Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 058f:6387 Alcor Micro Corp. Flash Drive
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP ZBook 15 G5
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-43-generic 
root=/dev/mapper/ubuntu--notebook--vg-root ro nomodeset nosplash
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/07/2018
  dmi.bios.vendor: HP
  dmi.bios.version: Q70 Ver. 01.01.05
  dmi.board.name: 842A
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 15.2B.00
  dmi.chassis.asset.tag: 5CD8394RP8
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ70Ver.01.01.05:bd08/07/2018:svnHP:pnHPZBook15G5:pvr:rvnHP:rn842A:rvrKBCVersion15.2B.00:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN HP ZBook 15
  dmi.product.name: HP ZBook 15 G5
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1836461/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1805426] Re: Not able to log in into Google Account, aswell as Microsoft account

[Matheus Reich]

** Changed in: gnome-online-accounts (Ubuntu)
   Status: New => Invalid

-- 
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/1805426

Title:
  Not able to log in into Google Account, aswell as Microsoft account

Status in gnome-initial-setup package in Ubuntu:
  Invalid
Status in gnome-online-accounts package in Ubuntu:
  Invalid

Bug description:
  After the first boot up of Ubuntu 18.10, it invites me to log-in into
  several accounts, including Google and Microsoft accounts. After I
  log-in into Ubuntu One, my next step is to log in my Google Account,
  but the log-in page never loads, and when it does (after a couple of
  minutes), and I insert my log in credentials, it fails the log-in
  process, all of this happens with the Microsoft account too. The
  Ubuntu One account logs-in without a hitch, but the rest does not.

  1) Description:   Ubuntu 18.10
  Release:  18.10

  2) gnome-initial-setup:
Instalado: 3.30.0-1ubuntu3
Candidato: 3.30.0-1ubuntu3.1
Tabela de versão:
   3.30.0-1ubuntu3.1 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 
Packages
   *** 3.30.0-1ubuntu3 500
  500 http://br.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: gnome-initial-setup 3.30.0-1ubuntu3
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Nov 27 11:12:31 2018
  ExecutablePath: /usr/lib/gnome-initial-setup/gnome-initial-setup
  InstallationDate: Installed on 2018-11-27 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  ProcEnviron:
   LANGUAGE=pt_BR:pt:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_BR.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-initial-setup
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1805426/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1781428] Re: please enable snap mediation support

[Jamie Strandboge]

** Description changed:

  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.
  
  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all connected
  clients (snaps or not), record by classic snaps (see bug 1787324) and
  record by strict mode snaps if either the pulseaudio or new-in-
  snapd-2.41 audio-record interfaces were connected. With this change,
  snapd is in a position to migrate snaps to the new audio-playback and
  audio-record interfaces and properly mediate audio recording (see
  https://forum.snapcraft.io/t/upcoming-pulseaudio-interface-
  deprecation/13418).
  
  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not, whether
  the pulseaudio or audio-record interfaces are connected. Adjusting
  pulseaudio in the manner does not require coordination with any release
  of snapd. It does need a newer version of snapd-glib, which was recently
  updated to 1.49 in the last SRU.
  
  [Test Case]
  
- Since the pulseaudio mediation behavior triggers when the security label
- starts with 'snap.' it is su
+ IMPORTANT: if updating pulseaudio while the session is running, either
+ need to reboot for the test or kill pulseaudio so it can restart with
+ the new snap policy
  
  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes
  
  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes
  
  $ paplay /tmp/out.wav && echo "yes"
  yes
  
  For confined, non-snap applications:
  $ sudo apt-get install evince
  
  $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav
  && echo yes
  
  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes
  
  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes
  
  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic
  
  $ snap run --shell test-snapd-classic-confinement
  
  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)
  
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes
  
  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes
  
  $ paplay /tmp/out.wav && echo "yes"
  yes
  
  For strict snaps with pulseaudio:
  $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap
  
  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -
  
  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...
  
  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/
  
  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes
  
  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)
  
  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes
  
  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes
  
  For strict snaps with audio-playback/audio-record:
  $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04
  $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap
  
  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
  audio-recordtest-snapd-audio-record:audio-record--
  
  $ test-snapd-audio-record.play --help  # ensure SNAP dirs are created
  ...
  
  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-audio-
  record/common/
  
  $ test-snapd-audio-record.play 
/var/snap/test-snapd-audio-record/common/Noise.wav && echo yes
  

[Touch-packages] [Bug 1781428] Re: please enable snap mediation support

[Jamie Strandboge]

** Description changed:

  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.
  
  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all connected
  clients (snaps or not), record by classic snaps (see bug 1787324) and
  record by strict mode snaps if either the pulseaudio or new-in-
  snapd-2.41 audio-record interfaces were connected. With this change,
  snapd is in a position to migrate snaps to the new audio-playback and
  audio-record interfaces and properly mediate audio recording (see
  https://forum.snapcraft.io/t/upcoming-pulseaudio-interface-
  deprecation/13418).
  
  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not, whether
  the pulseaudio or audio-record interfaces are connected. Adjusting
  pulseaudio in the manner does not require coordination with any release
  of snapd. It does need a newer version of snapd-glib, which was recently
  updated to 1.49 in the last SRU.
  
  [Test Case]
  
  Since the pulseaudio mediation behavior triggers when the security label
  starts with 'snap.' it is su
  
  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes
  
  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes
  
  $ paplay /tmp/out.wav && echo "yes"
  yes
  
  For confined, non-snap applications:
  $ sudo apt-get install evince
  
  $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav
  && echo yes
  
  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes
  
  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes
  
- 
  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic
  
  $ snap run --shell test-snapd-classic-confinement
  
  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)
  
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes
  
  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes
  
  $ paplay /tmp/out.wav && echo "yes"
  yes
  
  For strict snaps with pulseaudio:
  $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap
  
  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -
  
  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...
  
  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/
  
  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes
  
  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)
  
  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes
  
  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes
  
- 
  For strict snaps with audio-playback/audio-record:
+ $ sudo snap refresh core --candidate # make sure have 2.41. 'install' on 16.04
  $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap
  
  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
  audio-recordtest-snapd-audio-record:audio-record--
  
  $ test-snapd-audio-record.play --help  # ensure SNAP dirs are created
  ...
  
  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-audio-
  record/common/
  
  $ test-snapd-audio-record.play 
/var/snap/test-snapd-audio-record/common/Noise.wav && echo yes
  xcb_connection_has_error() returned true
  yes
  
  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to 

[Touch-packages] [Bug 1781428] Re: please enable snap mediation support

[Jamie Strandboge]

Attaching test-snapd-pulseaudio and test-snapd-audio-record snaps.

-- 
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/1781428

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  Since the pulseaudio mediation behavior triggers when the security
  label starts with 'snap.' it is su

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  
  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For strict snaps with pulseaudio:
  $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes

  
  For strict snaps with audio-playback/audio-record:
  $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap

  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
  audio-recordtest-snapd-audio-record:audio-record--

  $ test-snapd-audio-record.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp 

[Touch-packages] [Bug 1781428] Re: please enable snap mediation support

[Jamie Strandboge]

** Description changed:

+ [Impact]
+ Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.
  
- # Original summary: pulseaudio built with --enable-snappy but 'Enable
- Snappy support: no'
+ To correct this situation but not regress existing behavior, Ubuntu
+ 19.04's pulseaudio was updated patch to allow playback to all connected
+ clients (snaps or not), record by classic snaps (see bug 1787324) and
+ record by strict mode snaps if either the pulseaudio or new-in-
+ snapd-2.41 audio-record interfaces were connected. With this change,
+ snapd is in a position to migrate snaps to the new audio-playback and
+ audio-record interfaces and properly mediate audio recording (see
+ https://forum.snapcraft.io/t/upcoming-pulseaudio-interface-
+ deprecation/13418).
+ 
+ The patch to pulseaudio consists of adding a module, enabling it in
+ default.pa and then when it is enabled, pulseaudio when faced with a
+ record operation will, when the connecting process is a snap (ie, its
+ security label (ie, apparmor label) starts with 'snap.'), query snapd
+ via its control socket to ask if the snap is classic and if not, whether
+ the pulseaudio or audio-record interfaces are connected. Adjusting
+ pulseaudio in the manner does not require coordination with any release
+ of snapd. It does need a newer version of snapd-glib, which was recently
+ updated to 1.49 in the last SRU.
+ 
+ [Test Case]
+ 
+ Since the pulseaudio mediation behavior triggers when the security label
+ starts with 'snap.' it is su
+ 
+ For unconfined applications:
+ $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
+ yes
+ 
+ $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
+ ^Cyes
+ 
+ $ paplay /tmp/out.wav && echo "yes"
+ yes
+ 
+ For confined, non-snap applications:
+ $ sudo apt-get install evince
+ 
+ $ aa-exec -p /usr/bin/evince -- paplay /usr/share/sounds/alsa/Noise.wav
+ && echo yes
+ 
+ $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
+ ^Cyes
+ 
+ $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
+ yes
+ 
+ 
+ For classic snaps:
+ $ sudo snap install test-snapd-classic-confinement --classic
+ 
+ $ snap run --shell test-snapd-classic-confinement
+ 
+ $ cat /proc/self/attr/current   # verify we are classic confined
+ snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)
+ 
+ $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
+ yes
+ 
+ $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
+ ^Cyes
+ 
+ $ paplay /tmp/out.wav && echo "yes"
+ yes
+ 
+ For strict snaps with pulseaudio:
+ $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap
+ 
+ $ snap connections test-snapd-pulseaudio
+ Interface   Plug  Slot Notes
+ pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -
+ 
+ $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
+ ...
+ 
+ $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
+ pulseaudio/common/
+ 
+ $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
+ xcb_connection_has_error() returned true
+ yes
+ 
+ (note, the xcb_connection_has_error() message is due to the x11
+ interface not being connecting which is unrelated to mediation. x11 is
+ left out to ensure that just audio-playback/audio-record are tested)
+ 
+ $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
+ ...
+ ^Cyes
+ 
+ $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
+ ...
+ yes
+ 
+ 
+ For strict snaps with audio-playback/audio-record:
+ $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap
+ 
+ $ snap connections test-snapd-audio-record  # record not connected
+ Interface   PlugSlot Notes
+ audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
+ audio-recordtest-snapd-audio-record:audio-record--
+ 
+ $ test-snapd-audio-record.play --help  # ensure SNAP dirs are created
+ ...
+ 
+ $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-audio-
+ record/common/
+ 
+ $ test-snapd-audio-record.play 
/var/snap/test-snapd-audio-record/common/Noise.wav && echo yes
+ xcb_connection_has_error() returned true
+ yes
+ 
+ (note, the xcb_connection_has_error() message is due to the x11
+ interface not being connecting which is 

[Touch-packages] [Bug 1781428] Re: please enable snap mediation support

[Jamie Strandboge]

** Attachment added: "test-snapd-audio-record_1_amd64.snap"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+attachment/5292539/+files/test-snapd-audio-record_1_amd64.snap

-- 
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/1781428

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  In Progress
Status in pulseaudio source package in Bionic:
  In Progress

Bug description:
  [Impact]
  Ubuntu 16.10 added rudimentary snap support to disable audio recording if the 
connecting process was a snap. By Ubuntu 18.04, something changed in the build 
resulting in 'Enable Snappy support: no' with audio recording no longer being 
mediated by pulseaudio (access to the pulseaudio socket continued to be 
mediated by snapd's apparmor policy). This resulted in any application with the 
pulseaudio interface connected to be able to also record. Ubuntu 16.04 never 
had mediation patches and always allowed recording when the pulseaudio 
interface was connected.

  To correct this situation but not regress existing behavior, Ubuntu
  19.04's pulseaudio was updated patch to allow playback to all
  connected clients (snaps or not), record by classic snaps (see bug
  1787324) and record by strict mode snaps if either the pulseaudio or
  new-in-snapd-2.41 audio-record interfaces were connected. With this
  change, snapd is in a position to migrate snaps to the new audio-
  playback and audio-record interfaces and properly mediate audio
  recording (see https://forum.snapcraft.io/t/upcoming-pulseaudio-
  interface-deprecation/13418).

  The patch to pulseaudio consists of adding a module, enabling it in
  default.pa and then when it is enabled, pulseaudio when faced with a
  record operation will, when the connecting process is a snap (ie, its
  security label (ie, apparmor label) starts with 'snap.'), query snapd
  via its control socket to ask if the snap is classic and if not,
  whether the pulseaudio or audio-record interfaces are connected.
  Adjusting pulseaudio in the manner does not require coordination with
  any release of snapd. It does need a newer version of snapd-glib,
  which was recently updated to 1.49 in the last SRU.

  [Test Case]

  Since the pulseaudio mediation behavior triggers when the security
  label starts with 'snap.' it is su

  For unconfined applications:
  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For confined, non-snap applications:
  $ sudo apt-get install evince

  $ aa-exec -p /usr/bin/evince -- paplay
  /usr/share/sounds/alsa/Noise.wav && echo yes

  $ rm -f /tmp/out.wav ; aa-exec -p /usr/bin/evince -- parecord /tmp/out.wav && 
echo "yes"  # ctrl-c to stop recording
  ^Cyes

  $ aa-exec -p /usr/bin/evince -- paplay /tmp/out.wav && echo "yes"
  yes

  
  For classic snaps:
  $ sudo snap install test-snapd-classic-confinement --classic

  $ snap run --shell test-snapd-classic-confinement

  $ cat /proc/self/attr/current   # verify we are classic confined
  snap.test-snapd-classic-confinement.test-snapd-classic-confinement (complain)

  $ paplay /usr/share/sounds/alsa/Noise.wav && echo "yes"
  yes

  $ rm -f /tmp/out.wav ; parecord /tmp/out.wav && echo "yes"  # ctrl-c to stop 
recording
  ^Cyes

  $ paplay /tmp/out.wav && echo "yes"
  yes

  For strict snaps with pulseaudio:
  $ sudo snap install --dangerous ./test-snapd-pulseaudio_1_amd64.snap

  $ snap connections test-snapd-pulseaudio
  Interface   Plug  Slot Notes
  pulseaudio  test-snapd-pulseaudio:pulseaudio  :pulseaudio  -

  $ test-snapd-pulseaudio.play --help  # ensure SNAP dirs are created
  ...

  $ sudo cp /usr/share/sounds/alsa/Noise.wav /var/snap/test-snapd-
  pulseaudio/common/

  $ test-snapd-pulseaudio.play /var/snap/test-snapd-pulseaudio/common/Noise.wav 
&& echo yes
  xcb_connection_has_error() returned true
  yes

  (note, the xcb_connection_has_error() message is due to the x11
  interface not being connecting which is unrelated to mediation. x11 is
  left out to ensure that just audio-playback/audio-record are tested)

  $ test-snapd-pulseaudio.record /tmp/out.wav && echo yes # should pass
  ...
  ^Cyes

  $ test-snapd-pulseaudio.play /tmp/out.wav && echo yes
  ...
  yes

  
  For strict snaps with audio-playback/audio-record:
  $ sudo snap install --dangerous ./test-snapd-audio-record_1_amd64.snap

  $ snap connections test-snapd-audio-record  # record not connected
  Interface   PlugSlot Notes
  audio-playback  test-snapd-audio-record:audio-playback  :audio-playback  -
  audio-recordtest-snapd-audio-record:audio-record-   

[Touch-packages] [Bug 1781428] Re: pulseaudio built with --enable-snappy but 'Enable Snappy support: no'

[Jamie Strandboge]

** Description changed:

+ 
+ # Original summary: pulseaudio built with --enable-snappy but 'Enable
+ Snappy support: no'
+ 
+ # Original description
+ 
  From https://launchpadlibrarian.net/377100864/buildlog_ubuntu-cosmic-
  amd64.pulseaudio_1%3A12.0-1ubuntu1_BUILDING.txt.gz:
  
  ...
  dh_auto_configure -- --enable-x11 --disable-hal-compat 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--with-module-dir=\${prefix}/lib/pulse-12.0/modules 
--with-zsh-completion-dir=\${datadir}/zsh/vendor-completions 
--with-bash-completion-dir=\${datadir}/bash-completion/completions 
--with-systemduserunitdir=\${prefix}/lib/systemd/user --enable-snappy 
--disable-bluez4 --enable-gsettings --disable-gconf
   ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-x11 --disable-hal-compat 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--with-module-dir=\${prefix}/lib/pulse-12.0/modules 
--with-zsh-completion-dir=\${datadir}/zsh/vendor-completions 
--with-bash-completion-dir=\${datadir}/bash-completion/completions 
--with-systemduserunitdir=\${prefix}/lib/systemd/user --enable-snappy 
--disable-bluez4 --enable-gsettings --disable-gconf
  ...
  Enable Ubuntu trust store: no
  Enable Snappy support: no
  Enable Apparmor:   yes
  
- 
- At this point, the patch should probably be dropped, otherwise applications 
like chromium, etc will no longer be able to record.
+ At this point, the patch should probably be dropped, otherwise
+ applications like chromium, etc will no longer be able to record.

** Summary changed:

- pulseaudio built with --enable-snappy but 'Enable Snappy support: no'
+ please enable snap mediation support

-- 
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/1781428

Title:
  please enable snap mediation support

Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:

  # Original summary: pulseaudio built with --enable-snappy but 'Enable
  Snappy support: no'

  # Original description

  From https://launchpadlibrarian.net/377100864/buildlog_ubuntu-cosmic-
  amd64.pulseaudio_1%3A12.0-1ubuntu1_BUILDING.txt.gz:

  ...
  dh_auto_configure -- --enable-x11 --disable-hal-compat 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--with-module-dir=\${prefix}/lib/pulse-12.0/modules 
--with-zsh-completion-dir=\${datadir}/zsh/vendor-completions 
--with-bash-completion-dir=\${datadir}/bash-completion/completions 
--with-systemduserunitdir=\${prefix}/lib/systemd/user --enable-snappy 
--disable-bluez4 --enable-gsettings --disable-gconf
   ./configure --build=x86_64-linux-gnu --prefix=/usr 
--includedir=\${prefix}/include --mandir=\${prefix}/share/man 
--infodir=\${prefix}/share/info --sysconfdir=/etc --localstatedir=/var 
--disable-silent-rules --libdir=\${prefix}/lib/x86_64-linux-gnu 
--libexecdir=\${prefix}/lib/x86_64-linux-gnu --disable-maintainer-mode 
--disable-dependency-tracking --enable-x11 --disable-hal-compat 
--libdir=\${prefix}/lib/x86_64-linux-gnu 
--with-module-dir=\${prefix}/lib/pulse-12.0/modules 
--with-zsh-completion-dir=\${datadir}/zsh/vendor-completions 
--with-bash-completion-dir=\${datadir}/bash-completion/completions 
--with-systemduserunitdir=\${prefix}/lib/systemd/user --enable-snappy 
--disable-bluez4 --enable-gsettings --disable-gconf
  ...
  Enable Ubuntu trust store: no
  Enable Snappy support: no
  Enable Apparmor:   yes

  At this point, the patch should probably be dropped, otherwise
  applications like chromium, etc will no longer be able to record.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1781428/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1845836] [NEW] package linux-image-4.4.0-164-generic 4.4.0-164.192 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[zhangfeng]

Public bug reported:

no

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-164-generic 4.4.0-164.192
Uname: Linux 4.8.0-040800-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Fri Sep 27 18:57:03 2019
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
InstallationDate: Installed on 2018-07-05 (451 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.29ubuntu0.1
SourcePackage: initramfs-tools
Title: package linux-image-4.4.0-164-generic 4.4.0-164.192 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1845836

Title:
  package linux-image-4.4.0-164-generic 4.4.0-164.192 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  no

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-164-generic 4.4.0-164.192
  Uname: Linux 4.8.0-040800-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Fri Sep 27 18:57:03 2019
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  InstallationDate: Installed on 2018-07-05 (451 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.29ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-164-generic 4.4.0-164.192 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1845836/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1843627] Re: evolution-calendar-factory crashed with SIGSEGV in tcache_get()

[Andreas Remchen]

The problem is with active calendar of my Google account. Everything
works very well with Nextcloud.

-- 
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/1843627

Title:
  evolution-calendar-factory crashed with SIGSEGV in tcache_get()

Status in evolution-data-server:
  Fix Released
Status in evolution-data-server package in Ubuntu:
  Confirmed

Bug description:
  https://gitlab.gnome.org/GNOME/evolution/issues/616

  ---

  I don't know what happened.

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: evolution-data-server 3.33.91-3
  ProcVersionSignature: Ubuntu 5.3.0-10.11-generic 5.3.0-rc8
  Uname: Linux 5.3.0-10-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Sep 11 13:41:26 2019
  ExecutablePath: /usr/libexec/evolution-calendar-factory
  InstallationDate: Installed on 2018-12-02 (282 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcCmdline: /usr/libexec/evolution-calendar-factory
  ProcEnviron:
   LANG=es_CL.UTF-8
   LANGUAGE=es_CL:es
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
  SegvAnalysis:
   Segfault happened at: 0x7f36355653ae <__GI___libc_malloc+286>:   mov
(%r8),%rsi
   PC (0x7f36355653ae) ok
   source "(%r8)" (0x7f36) not located in a known VMA region (needed 
readable region)!
   destination "%rsi" ok
   Stack memory exhausted (SP below stack segment)
  SegvReason: reading unknown VMA
  Signal: 11
  SourcePackage: evolution-data-server
  StacktraceTop:
   tcache_get (tc_idx=) at malloc.c:2937
   __GI___libc_malloc (bytes=32) at malloc.c:3051
   g_malloc () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_datalist_id_set_data_full () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   () at /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
  Title: evolution-calendar-factory crashed with SIGSEGV in tcache_get()
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (282 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

To manage notifications about this bug go to:
https://bugs.launchpad.net/evolution-data-server/+bug/1843627/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1782679] Re: systemd-resolved can't resolve at all, need to add nameservers to resolve.conf

[Dmitry Lapshin]

Any progress here? systemd-resolved has plus that it's integrated with
DNS options from systemd-networkd, but for end user it has many issues,
especially related to DNSSEC.

-- 
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/1782679

Title:
  systemd-resolved can't resolve at all, need to add nameservers to
  resolve.conf

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu 18.04 (upgraded from 17.10) on a machine with both
  ethernet and wifi interfaces. When I boot, my ethernet connection
  enp0s31f6 is brought up by Network Manager and given three nameserver
  addresses via DHCP, 10.1.13.10, 10.1.141.10, 10.1.13.36. Running nmcli
  shows the three nameservers under "DNS configuration". Running
  "systemd-resolve --status" shows them under a "Link 2 (enp0s31f6)"
  section. I can do a "ip route get to X" and ping each one
  successfully. No other connection is active.

  testuser ☼ systemd-resolve --status
  Global
DNS Domain: orgsdomain.net
DNSSEC NTA: 10.in-addr.arpa
16.172.in-addr.arpa
168.192.in-addr.arpa
17.172.in-addr.arpa
18.172.in-addr.arpa
19.172.in-addr.arpa
20.172.in-addr.arpa
21.172.in-addr.arpa
22.172.in-addr.arpa
23.172.in-addr.arpa
24.172.in-addr.arpa
25.172.in-addr.arpa
26.172.in-addr.arpa
27.172.in-addr.arpa
28.172.in-addr.arpa
29.172.in-addr.arpa
30.172.in-addr.arpa
31.172.in-addr.arpa
corp
d.f.ip6.arpa
home
internal
intranet
lan
local
private
test

  Link 3 (wlp4s0)
Current Scopes: none
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no

  Link 2 (enp0s31f6)
Current Scopes: DNS
 LLMNR setting: yes
  MulticastDNS setting: no
DNSSEC setting: no
  DNSSEC supported: no
   DNS Servers: 10.1.13.10
10.1.141.10
10.1.13.36
DNS Domain: orgsdomain.net

  However, when I actually try to resolve a name, even the name of one
  of the nameservers, dig claims that "connection timed out: no servers
  could be reached".

  testuser ☼ dig dcpdc001.orgsdomain.net +nocookie

  ; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> dcpdc001.orgsdomain.net +nocookie
  ;; global options: +cmd
  ;; connection timed out; no servers could be reached

  Note that this name should resolve to 10.1.13.10, the first
  nameserver. The "+nocookie" option is there to work around an issue
  with Windows DNS servers. But other than that, the servers themselves
  work fine if I tell dig where to look:

  testuser ☼ dig dcpdc001.orgsdomain.net +nocookie @10.1.13.10

  ; <<>> DiG 9.11.3-1ubuntu1.1-Ubuntu <<>> dcpdc001.orgsdomain.net +nocookie 
@10.1.13.10
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61294
  ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4000
  ;; QUESTION SECTION:
  ;dcpdc001.orgsdomain.net.  IN  A

  ;; ANSWER SECTION:
  dcpdc001.orgsdomain.net.   3600IN  A   10.1.13.10

  ;; Query time: 2 msec
  ;; SERVER: 10.1.13.10#53(10.1.13.10)
  ;; WHEN: Fri Jul 20 10:56:27 AEST 2018
  ;; MSG SIZE  rcvd: 65

  I have configured resolvconf to use dynamic updates. /etc/resolv.conf
  points to /run/resolvconf/resolv.conf. This file contains only (non-
  comments):

  nameserver 127.0.0.53
  search orgsdomain

  If I add "nameserver 10.1.13.10" to this file manually, suddenly dig
  can resolve again (without the @...), and anything else that needs to
  resolve names can do so. Removing the nameserver breaks that again.

  I don't know much about the servers. They're part of a Windows-based
  network, but since I can use them if I edit resolv.conf or give dig
  the address, I don't think they're the issue (except in the sense that
  maybe they require a feature that systemd-resolved doesn't support?).

  I increased the logging level of systemd-resolved to "debug" and
  "journalctl -f -u systemd-resolved" shows this during a failed query:

  Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Got DNS stub UDP query 
packet for id 19836
  Jul 20 10:33:23 heerij-ubuntu systemd-resolved[2352]: Looking up RR for 
dcpdc001.orgsdomain.net IN A.
  Jul 

[Touch-packages] [Bug 1845825] [NEW] i2c_designware and i2c_hid failures on shutdown

[Daniele Dellafiore]

Public bug reported:

1. Using Ubuntu 19.10
2. Shutdown system
3. System get stuck at the windows with this messages:

i2c_designware.o: controller timed out
i2c_hid: failed to change power settings.

It might not be related to the shutdown not happening, still that's the
only clue I have.

I attach the screenshot and dmesg output after the following boot.

** Affects: pulseaudio (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: eoan

** Attachment added: "dmesg"
   https://bugs.launchpad.net/bugs/1845825/+attachment/5292444/+files/dmesg

-- 
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/1845825

Title:
  i2c_designware and i2c_hid failures on shutdown

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  1. Using Ubuntu 19.10
  2. Shutdown system
  3. System get stuck at the windows with this messages:

  i2c_designware.o: controller timed out
  i2c_hid: failed to change power settings.

  It might not be related to the shutdown not happening, still that's
  the only clue I have.

  I attach the screenshot and dmesg output after the following boot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1845825/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp

[Touch-packages] [Bug 1845494] Re: gdb 8.1-0ubuntu3.1 freezes before call main function while debugging 32bit application

[Matthias Klose]

** Changed in: gdb (Ubuntu)
 Assignee: (unassigned) => Manoj Iyer (manjo)

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to gdb in Ubuntu.
https://bugs.launchpad.net/bugs/1845494

Title:
  gdb 8.1-0ubuntu3.1 freezes before call main function while debugging
  32bit application

Status in gdb package in Ubuntu:
  New

Bug description:
  gdb 8.1ubuntu3.1 run binary 64bit without problem.
  If compile for 32bit target (g++ -m32 ..) then it can't load libraries
  before call main(), i mean it gets frozen.
  gdb 8.1-0ubuntu3 works with 32 and 64 bit binaries without problem.

  Here is log:
  g++ -m32 -o test test.cpp
  gdb ./test

  GNU gdb (Ubuntu 8.1-0ubuntu3.1) 8.1.0.20180409-git
  Copyright (C) 2018 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from ./test...(no debugging symbols found)...done.
  (gdb) run
  Starting program: /tmp/test
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.
  exit()
  ^C
  Program received signal SIGINT, Interrupt.
  0xf7fd9be0 in ?? () from /lib/ld-linux.so.2

  lsb_release -a
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.3 LTS
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdb/+bug/1845494/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help   : https://help.launchpad.net/ListHelp