[Touch-packages] [Bug 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken

2019-09-30 Thread Bug Watch Updater
Launchpad has imported 22 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=1725499.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2019-06-30T22:05:33+00:00 ubizjak wrote:

Created attachment 1586097
Xorg log file

Description of problem:

After update of xorg-x11-server-common and xorg-x11-server-Xorg packages
to version 1.20.5-3.fc30, the tooltips got corrupted in KDE.

Version-Release number of selected component (if applicable):

xorg-x11-server-Xorg (1.20.5-3.fc30)
xorg-x11-server-common (1.20.5-3.fc30)

How reproducible:

Always.

Steps to Reproduce:
1. Hoover the mouse pointer over the tool.
2.
3.

Actual results:
Corrupted tooltip.

Expected results:


Additional info:

$ uname -a
Linux localhost.localdomain 5.1.15-300.fc30.x86_64 #1 SMP Tue Jun 25 14:07:22 
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org (0x1002)
Device: AMD CYPRESS (DRM 2.50.0 / 5.1.15-300.fc30.x86_64, LLVM 8.0.0) 
(0x6898)
Version: 19.0.6
Accelerated: yes
Video memory: 1024MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 4.3
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1


I have rolled back the above packages to 1.20.4-3.fc30, where everything works 
OK.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841718/comments/0


On 2019-07-01T19:58:54+00:00 ubizjak wrote:

Created attachment 1586435
Screenshot of the corrupted tooltip

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841718/comments/1


On 2019-07-04T02:00:09+00:00 robin.a.meade wrote:

Corruption happens to me on Gnome on Fedora 30 after the update from:

xorg-x11-server-Xorg-1.20.4-3.fc30
xorg-x11-server-common-1.20.4-3.fc30.x86_64

to:

xorg-x11-server-Xorg-1.20.5-3.fc30.x86_64
xorg-x11-server-common-1.20.5-3.fc30.x86_64

I get corrupted icons in Gnome's top panel (specifically the Quake and Dropbox 
icons (I use the topicons-plus Gnome extension)).
I also get corrupted tooltips in Firefox, e.g., hovering my mouse over my 
account circle in GMail produces corruption similar to the screenshot shown on 
this bug.
As suggested by OP, downgrading xorg made the problem go away:

$ glxinfo -B
name of display: :0
display: :0  screen: 0
direct rendering: Yes
Extended renderer info (GLX_MESA_query_renderer):
Vendor: X.Org (0x1002)
Device: AMD TURKS (DRM 2.50.0 / 5.1.15-300.fc30.x86_64, LLVM 8.0.0) (0x6740)
Version: 19.0.8
Accelerated: yes
Video memory: 1024MB
Unified memory: no
Preferred profile: core (0x1)
Max core profile version: 3.3
Max compat profile version: 3.1
Max GLES1 profile version: 1.1
Max GLES[23] profile version: 3.1
...

A comment on a different bug describes a similar problem, and he has an AMD 
card as well:
https://bugzilla.redhat.com/show_bug.cgi?id=1726419#c1

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841718/comments/2


On 2019-07-04T06:52:18+00:00 ofourdan wrote:

Can you please try if either of these two scratch (test) builds fix the
issue:

xorg-x11-server-1.20.5-3.1test.fc30
https://koji.fedoraproject.org/koji/taskinfo?taskID=36015101

or:

xorg-x11-server-1.20.5-3.2test.fc30
https://koji.fedoraproject.org/koji/taskinfo?taskID=36027647

And report if either fix the corruption issue?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841718/comments/3


On 2019-07-04T10:26:05+00:00 ubizjak wrote:

(In reply to Olivier Fourdan from comment #3)
> Can you please try if either of these two scratch (test) builds fix the

I will be away from the keyboard today, but will report tomorrow
(friday) afternoon.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1841718/comments/4


On 2019-07-04T18:19:26+00:00 bugzilla_acct_1959 wrote:

(In reply to Olivier Fourdan from comment #3)
> Can you please try if either of these two scratch (test) builds fix the
> issue:
> 
> xorg-x11-server-1.20.5-3.1test.fc30
> https://koji.fedoraproject.org/koji/taskinfo?taskID=36015101
> 
> or:
> 
> xorg-x11-server-1.20.5-3.2test.fc30
> https://koji.fedoraproject.org/koji/taskinfo?taskID=36027647
> 
> And report if either fix the corruption issue?

I have the same tooltip corruption issues under cinnamon.

xorg-x11-server-1.20.5-3.1test.fc30 DOES fix 

[Touch-packages] [Bug 1694367] Re: Screen tearing in 16.10 onwards

2019-09-30 Thread Bug Watch Updater
Launchpad has imported 20 comments from the remote bug at
https://bugs.freedesktop.org/show_bug.cgi?id=101229.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2017-05-30T06:31:18+00:00 Paul wrote:

Created attachment 131571
glxinfo

System exhibits uncontrolled screen-tearing that can be seen when moving
windows, watching videos or playing games, or any graphical movement in
general. The tearing gradually shifts up or down the screen, suggesting
its a cycle frequency miss-match (or floating-point error).

Has affected mesa 12 and kernel 4.8 onwards.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/1


On 2017-05-30T07:47:20+00:00 Michel Dänzer wrote:

Please attach the Xorg log file and the output of xrandr and dmesg
corresponding to the problem.

Can you create a video demonstrating the problem when moving windows? If
not, please describe which desktop environment / window manager /
compositing manager you're using.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/2


On 2017-05-30T22:27:27+00:00 Paul wrote:

Created attachment 131583
xorg

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/3


On 2017-05-30T22:28:00+00:00 Paul wrote:

Created attachment 131584
display modes

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/4


On 2017-05-30T22:28:47+00:00 Paul wrote:

Created attachment 131585
dmesg | radeon

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/5


On 2017-05-30T22:41:49+00:00 Paul wrote:

(In reply to Michel Dänzer from comment #1)
> Can you create a video demonstrating the problem when moving windows? If
> not, please describe which desktop environment / window manager /
> compositing manager you're using.

Don't think I can show a video as I don't have a high-end camera or
capture card, but it affects vanilla Kubuntu 16.10 and 17.04 at least.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/6


On 2017-05-31T03:30:20+00:00 Michel Dänzer wrote:

Which rendering backend and tearing prevention method are selected in
the kwin settings?

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/7


On 2017-05-31T22:16:36+00:00 Paul wrote:

(In reply to Michel Dänzer from comment #6)
> Which rendering backend and tearing prevention method are selected in the
> kwin settings?

XRender and auto, I have tried the full-repaint but it didn't seem to
have an effect.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/8


On 2017-06-01T03:13:38+00:00 Michel Dänzer wrote:

To prevent tearing, you need to either choose OpenGL instead of XRender
and an appropriate tearing prevention setting, or enable TearFree with

xrandr --output eDP --set TearFree on

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/9


On 2017-06-06T01:06:57+00:00 Paul wrote:

(In reply to Michel Dänzer from comment #8)
> To prevent tearing, you need to either choose OpenGL instead of XRender and
> an appropriate tearing prevention setting, or enable TearFree with
> 
> xrandr --output eDP --set TearFree on

it's less obvious, but there still appears to be screen tearing when
running via openGL 3.1 using full-screen-repaints.

It's also reasonably obvious that for some GUIs their buttons will
update their two triangles across two frames instead of one, this seems
to be a much rarer occurrence with the above settings however.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1694367/comments/10


On 2017-06-06T01:19:30+00:00 Michel Dänzer wrote:

(In reply to Paul from comment #9)
> it's less obvious, but there still appears to be screen tearing

How does that manifest, and when you do what?

> when running via openGL 3.1 using full-screen-repaints.

FWIW, since DRI3 is enabled, "Re-use screen content" is the most
efficient setting.


> It's also reasonably obvious that for some GUIs their buttons will update
> 

[Touch-packages] [Bug 1846148] [NEW] Realtek ALC256M with DTS Audio Processing internal microphone doesn't work on Redmi Book 14 2019

2019-09-30 Thread Lilian Tao
Public bug reported:

Sound works okay but the internal mic doesn't work.
When I plug in headset, the mic on headset also doens't work.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  lilian 1689 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct  1 12:27:10 2019
InstallationDate: Installed on 2019-09-21 (9 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Title: PCI/internal sound card not detected
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/19/2019
dmi.bios.vendor: TIMI
dmi.bios.version: RMRCM400P0100
dmi.board.name: TM1901
dmi.board.vendor: TIMI
dmi.chassis.type: 10
dmi.chassis.vendor: TIMI
dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
dmi.product.family: Mi Laptop
dmi.product.name: RedmiBook 14
dmi.product.sku: TM1901-24822
dmi.sys.vendor: TIMI

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic third-party-packages

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

Title:
  Realtek ALC256M with DTS Audio Processing internal microphone doesn't
  work on Redmi Book 14 2019

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound works okay but the internal mic doesn't work.
  When I plug in headset, the mic on headset also doens't work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  lilian 1689 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 12:27:10 2019
  InstallationDate: Installed on 2019-09-21 (9 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/19/2019
  dmi.bios.vendor: TIMI
  dmi.bios.version: RMRCM400P0100
  dmi.board.name: TM1901
  dmi.board.vendor: TIMI
  dmi.chassis.type: 10
  dmi.chassis.vendor: TIMI
  dmi.modalias: 
dmi:bvnTIMI:bvrRMRCM400P0100:bd08/19/2019:svnTIMI:pnRedmiBook14:pvr:rvnTIMI:rnTM1901:rvr:cvnTIMI:ct10:cvr:
  dmi.product.family: Mi Laptop
  dmi.product.name: RedmiBook 14
  dmi.product.sku: TM1901-24822
  dmi.sys.vendor: TIMI

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1846148/+subscriptions

-- 
Mailing list: https://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 1846090] Re: GDX1505:00 27C6:01F1 Touchpad Screenpad support

2019-09-30 Thread Daniel van Vugt
Do you mean the screen doesn't light up, or the touchpad is
unresponsive?

Certainly the attached files suggest the second screen is not seen as
connected or powered on.

** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Summary changed:

- GDX1505:00 27C6:01F1 Touchpad Screenpad support
+ Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad Screenpad support

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

Title:
  Asus UX580GD (GDX1505:00 27C6:01F1) Touchpad Screenpad support

Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad
  and screen - all in one)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Oct  1 00:53:26 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 5.0.0-29-generic, x86_64: installed
   virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1021]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:180e]
  InstallationDate: Installed on 2019-09-27 (3 days ago)
  InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 13d3:5755 IMC Networks 
   Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
   Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX550GDX.302
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX550GDX
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook Pro
  dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://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 1841718] Re: [radeon] Rendering of combo boxes and tooltips is broken

2019-09-30 Thread Daniel van Vugt
** Bug watch added: Red Hat Bugzilla #1725499
   https://bugzilla.redhat.com/show_bug.cgi?id=1725499

** Also affects: xserver-xorg-video-ati (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=1725499
   Importance: Unknown
   Status: Unknown

** Also affects: xserver-xorg-video-ati (Ubuntu)
   Importance: Undecided
   Status: New

** No longer affects: gtk+3.0 (Ubuntu Eoan)

** No longer affects: gtk+3.0 (Ubuntu)

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

Title:
  [radeon] Rendering of combo boxes and tooltips is broken

Status in Mutter:
  New
Status in mesa package in Ubuntu:
  Triaged
Status in mutter package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  New
Status in mesa source package in Eoan:
  Triaged
Status in mutter source package in Eoan:
  Invalid
Status in xserver-xorg-video-ati source package in Eoan:
  New
Status in xserver-xorg-video-ati package in Fedora:
  Unknown

Bug description:
  Combo boxes are broken (cf screenshot) Tested in gnome-control-center
  and gtk3-demo.

  Tooltips are also garbage.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-shell 3.33.91-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 28 07:08:33 2019
  DisplayManager: gdm3
  InstallationDate: Installed on 2014-07-15 (1869 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140520)
  RelatedPackageVersions: mutter-common 3.33.91-1ubuntu1
  SourcePackage: gnome-shell
  UpgradeStatus: Upgraded to eoan on 2018-03-24 (521 days ago)

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

-- 
Mailing list: https://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 1773148] Autopkgtest regression report (systemd/237-3ubuntu10.31)

2019-09-30 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulseaudio/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  /lib/systemd/systemd-
  
journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

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

Bug description:
  [Impact]

   * systemd aborts journald, upon watchdog expiry and generates lots of crash 
reports
   * it appears that journald is simply stuck in fsync
   * it has been agreed to disable watchdog timer on journald

  [Test Case]

   * watch drop-off of errors w.r.t. watchdog timer

  [Regression Potential]

   * Potentially journald does get stuck, and thus is no longer
  automatically restarted with a sigabrt crash. However, so far, it is
  not known to do that.

  
  [Other Info]
   
   * Original bug report

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
237-3ubuntu10, the problem page at 
https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://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 1776626] Autopkgtest regression report (systemd/237-3ubuntu10.31)

2019-09-30 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulseaudio/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab
  part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * cryptsetup in bionic supports creating luks volumes with a non-
  standard sector-size option, and thus this option also needs to be
  used when activating the LUKS volumes. Add sector-size= option support
  to /etc/crypttab.

  [Test Case]

   * Create a plain LUKS volume with sector-size 4096
   * Specify sector-size=4096 option in /etc/crypttab
   * reload systemd, start systemd-cryptsetup@.service for that volume
   * check the journal, to ensure that `sector-size` option was recognized and 
is active. (i.e. there is not error messages about unrecognized option 
`sector-size` from systemd-cryptsetup)

  [Regression Potential]

   * This is an optional argument, not used by default. Currently custom
  sector-size crypttab does not work correctly, and thus cannot regress.

  [Other Info]
   
   * Original bug report

  Support fast clear key dm-crypt with 4k support

  Extend /etc/crypttab  to enable 4k sector support in plain mode

  The proposed enhancements are posted on github, see
   https://github.com/systemd/systemd/issues/8881

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions

-- 
Mailing list: https://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 1670291] Autopkgtest regression report (systemd/237-3ubuntu10.31)

2019-09-30 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulseaudio/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Released
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions

-- 
Mailing list: https://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 1671951] Autopkgtest regression report (systemd/237-3ubuntu10.31)

2019-09-30 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulseaudio/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions

-- 
Mailing list: 

[Touch-packages] [Bug 1773859] Autopkgtest regression report (systemd/237-3ubuntu10.31)

2019-09-30 Thread Ubuntu SRU Bot
All autopkgtests for the newly accepted systemd (237-3ubuntu10.31) for bionic 
have finished running.
The following regressions have been reported in tests triggered by the package:

gvfs/1.36.1-0ubuntu1.3.3 (ppc64el, amd64)
netplan.io/0.97-0ubuntu1~18.04.1 (amd64)
apt/1.6.12 (arm64, ppc64el)
pulseaudio/unknown (armhf)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/bionic/update_excuses.html#systemd

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

-- 
Mailing list: https://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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

2019-09-30 Thread Daniel van Vugt
I understand the concern but would personally prefer keeping it as-is.
It's better to have a paper trail than to hide any history of what came
before.

I'm happy to manually set bug 1663528 to Won't Fix again for bionic.

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Incomplete
Status in pulseaudio source package in Disco:
  Fix Committed
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions

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


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

2019-09-30 Thread Daniel van Vugt
Here I've decoded your EDID using 'xxd' and then 'edid-decode':

EDID version: 1.3
Manufacturer: SAM Model 509 Serial Number 1
Made in week 48 of 2008
Digital display
Maximum image size: 16 cm x 9 cm
Gamma: 2.20
RGB color display
First detailed timing is preferred timing
Display x,y Chromaticity:
  Red:   0.6396, 0.3300
  Green: 0.2998, 0.5996
  Blue:  0.1503, 0.0595
  White: 0.3125, 0.3291
Established timings supported:
  720x400@70Hz 9:5 HorFreq: 31469 Hz Clock: 28.320 MHz
  640x480@60Hz 4:3 HorFreq: 31469 Hz Clock: 25.175 MHz
  640x480@67Hz 4:3 HorFreq: 35000 Hz Clock: 30.240 MHz
  640x480@72Hz 4:3 HorFreq: 37900 Hz Clock: 31.500 MHz
  640x480@75Hz 4:3 HorFreq: 37500 Hz Clock: 31.500 MHz
  800x600@60Hz 4:3 HorFreq: 37900 Hz Clock: 40.000 MHz
  800x600@72Hz 4:3 HorFreq: 48100 Hz Clock: 50.000 MHz
  800x600@75Hz 4:3 HorFreq: 46900 Hz Clock: 49.500 MHz
  832x624@75Hz 4:3 HorFreq: 49726 Hz Clock: 57.284 MHz
  1024x768@60Hz 4:3 HorFreq: 48400 Hz Clock: 65.000 MHz
  1024x768@70Hz 4:3 HorFreq: 56500 Hz Clock: 75.000 MHz
  1024x768@75Hz 4:3 HorFreq: 6 Hz Clock: 78.750 MHz
  1280x1024@75Hz 5:4 HorFreq: 8 Hz Clock: 135.000 MHz
  1152x870@75Hz 192:145 HorFreq: 67500 Hz Clock: 108.000 MHz
Standard timings supported:
  1152x864@75Hz 4:3 HorFreq: 67500 Hz Clock: 108.000 MHz
  1280x800@60Hz 16:10
  1280x960@60Hz 4:3 HorFreq: 6 Hz Clock: 108.000 MHz
  1280x1024@60Hz 5:4 HorFreq: 64000 Hz Clock: 108.000 MHz
  1440x900@60Hz 16:10 HorFreq: 55500 Hz Clock: 88.750 MHz
  1440x900@75Hz 16:10 HorFreq: 82300 Hz Clock: 156.000 MHz
  1680x1050@60Hz 16:10 HorFreq: 64700 Hz Clock: 119.000 MHz
Detailed mode: Clock 148.500 MHz, 160 mm x 90 mm
   1920 2008 2052 2200 hborder 0
   1080 1084 1089 1125 vborder 0
   +hsync +vsync 
   VertFreq: 60 Hz, HorFreq: 67500 Hz
Detailed mode: Clock 85.500 MHz, 160 mm x 90 mm
   1360 1424 1536 1792 hborder 0
768  771  777  795 vborder 0
   +hsync +vsync 
   VertFreq: 60 Hz, HorFreq: 47712 Hz
Monitor ranges (GTF): 24-75Hz V, 26-81kHz H, max dotclock 230MHz
Monitor name: SAMSUNG
Has 1 extension blocks
Checksum: 0x6f (valid)

CTA extension block
Extension version: 3
35 bytes of CTA data
  Video data block
VIC  16 1920x1080@60Hz 16:9 (native) HorFreq: 67500 Hz Clock: 148.500 MHz
VIC  31 1920x1080@50Hz 16:9  HorFreq: 56250 Hz Clock: 148.500 MHz
VIC   4 1280x720@60Hz 16:9  HorFreq: 45000 Hz Clock: 74.250 MHz
VIC  19 1280x720@50Hz 16:9  HorFreq: 37500 Hz Clock: 74.250 MHz
VIC   5 1920x1080i@60Hz 16:9  HorFreq: 33750 Hz Clock: 74.250 MHz
VIC  20 1920x1080i@50Hz 16:9  HorFreq: 28125 Hz Clock: 74.250 MHz
VIC   3 720x480@60Hz 16:9  HorFreq: 31469 Hz Clock: 27.000 MHz
VIC  18 720x576@50Hz 16:9  HorFreq: 31250 Hz Clock: 27.000 MHz
VIC  32 1920x1080@24Hz 16:9  HorFreq: 27000 Hz Clock: 74.250 MHz
VIC  33 1920x1080@25Hz 16:9  HorFreq: 28125 Hz Clock: 74.250 MHz
VIC  34 1920x1080@30Hz 16:9  HorFreq: 33750 Hz Clock: 74.250 MHz
  Audio data block
Linear PCM, max channels 2
  Supported sample rates (kHz): 48 44.1 32
  Supported sample sizes (bits): 24 20 16
  Speaker allocation data block
Speaker map:
  FL/FR - Front Left/Right
  Extended tag: Video capability data block
YCbCr quantization: No Data (0)
RGB quantization: No Data (0)
PT scan behaviour: No Data (0)
IT scan behaviour: Support both over- and underscan (3)
CE scan behaviour: Support both over- and underscan (3)
  Extended tag: Colorimetry data block
xvYCC601
xvYCC709
  Vendor-specific data block, OUI 000c03 (HDMI)
Source physical address 1.0.0.0
Supports_AI
DC_36bit
DC_30bit
DC_Y444
Maximum TMDS clock: 225MHz
Underscans PC formats by default
Basic audio support
Supports YCbCr 4:4:4
Supports YCbCr 4:2:2
1 native detailed modes
Detailed mode: Clock 74.250 MHz, 160 mm x 90 mm
   1280 1390 1430 1650 hborder 0
720  725  730  750 vborder 0
   +hsync +vsync 
   VertFreq: 60 Hz, HorFreq: 45000 Hz
Detailed mode: Clock 74.250 MHz, 160 mm x 90 mm
   1280 1720 1760 1980 hborder 0
720  725  730  750 vborder 0
   +hsync +vsync 
   VertFreq: 50 Hz, HorFreq: 37500 Hz
Detailed mode: Clock 74.250 MHz, 160 mm x 90 mm
   1920 2008 2052 2200 hborder 0
540  542  547  562 vborder 0
   +hsync +vsync interlaced 
   VertFreq: 60 Hz, HorFreq: 33750 Hz
Detailed mode: Clock 74.250 MHz, 160 mm x 90 mm
   1920 2448 2492 2640 hborder 0
540  542  547  562 vborder 0
   +hsync +vsync interlaced 
   VertFreq: 50 Hz, HorFreq: 28125 Hz
Checksum: 0x1d (valid)

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

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

2019-09-30 Thread Daniel van Vugt
To be absolutely sure you would need to:

1. Convert the display's EDID into binary from hex:

00004c2d09050100
30120103801009780aee91a3544c9926
0f5054bdef80714f8100814081809500
950fb3000101023a801871382d40582c
4500a05a001e662150b051001b30
40703600a05a001e00fd0018
4b1a5117000a20202020202000fc
0053414d53554e470a2020202020016f
020327f14b901f041305140312202122
230907078301e2000fe305030167
030c001000b82d011d007251d01e206e
285500a05a001e011d00bc52d01e
20b8285540a05a001e011d801871
1c1620582c2500a05a009e011d80
d0721c1620102c2580a05a009e00
001d

2. Use an EDID decoding tool to verify it yourself. Some are available
in the Ubuntu archive, but also you can google for online EDID decoders.

** No longer affects: xrandr (Ubuntu)

-- 
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 1257612] Re: divide by zero error in radeon_surface.c when opening chrome with WebGL enabled

2019-09-30 Thread Bug Watch Updater
** Changed in: nouveau
   Status: Confirmed => Unknown

** Bug watch added: gitlab.freedesktop.org/mesa/drm/issues #12
   https://gitlab.freedesktop.org/mesa/drm/issues/12

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

Title:
  divide by zero error in radeon_surface.c when opening chrome with
  WebGL enabled

Status in Nouveau Xorg driver:
  Unknown
Status in libdrm package in Ubuntu:
  New

Bug description:
  Passing a tile_split of zero to eg_surface_init_2d causes a divide by
  zero error. Launching chromium with WebGL enabled on a AMD Llano
  (A8-3850) exhibits this behavior and webgl then fails to work. The
  attached patch fixes the problem and allows WebGL to work in chrome on
  this platform.

  Additional information:

  lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  Package version: 
  libdrm_2.4.46-1ubuntu1

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

-- 
Mailing list: https://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 1257612]

2019-09-30 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has
been closed from further activity.

You can subscribe and participate further through the new bug through
this link to our GitLab instance:
https://gitlab.freedesktop.org/mesa/drm/issues/12.

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

Title:
  divide by zero error in radeon_surface.c when opening chrome with
  WebGL enabled

Status in Nouveau Xorg driver:
  Unknown
Status in libdrm package in Ubuntu:
  New

Bug description:
  Passing a tile_split of zero to eg_surface_init_2d causes a divide by
  zero error. Launching chromium with WebGL enabled on a AMD Llano
  (A8-3850) exhibits this behavior and webgl then fails to work. The
  attached patch fixes the problem and allows WebGL to work in chrome on
  this platform.

  Additional information:

  lsb_release -rd
  Description:  Ubuntu 13.10
  Release:  13.10

  Package version: 
  libdrm_2.4.46-1ubuntu1

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

-- 
Mailing list: https://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 1840510] Re: Please enable PGO and LTO for arm64

2019-09-30 Thread Bug Watch Updater
** Changed in: python3-defaults (Debian)
   Status: Unknown => Fix Released

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

Title:
  Please enable PGO and LTO for arm64

Status in python3-defaults package in Ubuntu:
  New
Status in python3-defaults package in Debian:
  Fix Released

Bug description:
  The rules file conditionally enables PGO and LTO in the python3 build
  and while it's enabled for many platforms it's not enabled for arm64.
  This is worth about 30% performance. Please enable it.

  A patch is available here with the original debian bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1840510/+subscriptions

-- 
Mailing list: https://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 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP

2019-09-30 Thread Bug Watch Updater
** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  systemd-networkd fails to apply static IPv4 when the static IP is the
  same as previously configured by DHCP

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

Bug description:
  In bionic, running systemd 237-3ubuntu10.22 and netplan.io
  0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an
  interface with a static IPv4 address if the statically confiugred
  address is the same as the interface already has gotten from DHCP.

  This will cause the interface to loose its IP address when the DHCP
  lease exires, even though you've told netplan to configure it as
  static.

  I expect systemd-networkd to actually configure an IP address as
  static, regardless of what address the interface has before from DHCP.

  # lsb_release  -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  # apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.22

  # apt-cache policy netplan.io
  netplan.io:
Installed: 0.97-0ubuntu1~18.04.1

  A paste of systemd-networkd's debug log when I run "netplan apply" and
  the interface already has the static IP configured from DHCP.

  It seems like upon a restart, systemd-networkd will allways add
  whatever IP config it had before the service stopped, and then apply
  changes (if any). Since my new config has the same IP as it already
  had, it does nothing even though the new config has static
  configuration.

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

-- 
Mailing list: https://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 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-09-30 Thread Bug Watch Updater
** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

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

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

-- 
Mailing list: https://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 1773859] Re: upgrades to 18.04 fail

2019-09-30 Thread Kees Cook
Hmm, I don't have any systems left with systemd-shim installed, so I
can't do a "real world" test of this. The test case is the description
seems reasonable, so if that passes, I would consider this bug fixed. :)
Thanks!

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

-- 
Mailing list: https://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 1834875] Re: cloud-init growpart race with udev

2019-09-30 Thread Dan Streetman
> The lack of events is not the issue

I'm not saying it is.  But you seem to have it under control; I was just
offering my opinion.

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

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  Incomplete
Status in cloud-utils:
  New
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  Cosmic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions

-- 
Mailing list: https://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 1815172] Re: [bionic] drm/i915: softpin broken, needs to be fixed for 32bit mesa

2019-09-30 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-65.74

---
linux (4.15.0-65.74) bionic; urgency=medium

  * bionic/linux: 4.15.0-65.74 -proposed tracker (LP: #1844403)

  * arm64: large modules fail to load (LP: #1841109)
- arm64/kernel: kaslr: reduce module randomization range to 4 GB
- arm64/kernel: don't ban ADRP to work around Cortex-A53 erratum #843419
- arm64: fix undefined reference to 'printk'
- arm64/kernel: rename module_emit_adrp_veneer->module_emit_veneer_for_adrp
- [config] Remove CONFIG_ARM64_MODULE_CMODEL_LARGE

  * CVE-2018-20976
- xfs: clear sb->s_fs_info on mount failure

  * br_netfilter: namespace sysctl operations (LP: #1836910)
- net: bridge: add bitfield for options and convert vlan opts
- net: bridge: convert nf call options to bits
- netfilter: bridge: port sysctls to use brnf_net
- netfilter: bridge: namespace bridge netfilter sysctls
- netfilter: bridge: prevent UAF in brnf_exit_net()

  * tuntap: correctly set SOCKWQ_ASYNC_NOSPACE (LP: #1830756)
- tuntap: correctly set SOCKWQ_ASYNC_NOSPACE

  * Bionic update: upstream stable patchset 2019-08-30 (LP: #1842114)
- HID: Add 044f:b320 ThrustMaster, Inc. 2 in 1 DT
- MIPS: kernel: only use i8253 clocksource with periodic clockevent
- mips: fix cacheinfo
- netfilter: ebtables: fix a memory leak bug in compat
- ASoC: dapm: Fix handling of custom_stop_condition on DAPM graph walks
- bonding: Force slave speed check after link state recovery for 802.3ad
- can: dev: call netif_carrier_off() in register_candev()
- ASoC: Fail card instantiation if DAI format setup fails
- st21nfca_connectivity_event_received: null check the allocation
- st_nci_hci_connectivity_event_received: null check the allocation
- ASoC: ti: davinci-mcasp: Correct slot_width posed constraint
- net: usb: qmi_wwan: Add the BroadMobi BM818 card
- qed: RDMA - Fix the hw_ver returned in device attributes
- isdn: mISDN: hfcsusb: Fix possible null-pointer dereferences in
  start_isoc_chain()
- netfilter: ipset: Fix rename concurrency with listing
- isdn: hfcsusb: Fix mISDN driver crash caused by transfer buffer on the 
stack
- perf bench numa: Fix cpu0 binding
- can: sja1000: force the string buffer NULL-terminated
- can: peak_usb: force the string buffer NULL-terminated
- net/ethernet/qlogic/qed: force the string buffer NULL-terminated
- NFSv4: Fix a potential sleep while atomic in nfs4_do_reclaim()
- HID: input: fix a4tech horizontal wheel custom usage
- SMB3: Kernel oops mounting a encryptData share with CONFIG_DEBUG_VIRTUAL
- net: cxgb3_main: Fix a resource leak in a error path in 'init_one()'
- net: hisilicon: make hip04_tx_reclaim non-reentrant
- net: hisilicon: fix hip04-xmit never return TX_BUSY
- net: hisilicon: Fix dma_map_single failed on arm64
- libata: have ata_scsi_rw_xlat() fail invalid passthrough requests
- libata: add SG safety checks in SFF pio transfers
- x86/lib/cpu: Address missing prototypes warning
- drm/vmwgfx: fix memory leak when too many retries have occurred
- perf ftrace: Fix failure to set cpumask when only one cpu is present
- perf cpumap: Fix writing to illegal memory in handling cpumap mask
- perf pmu-events: Fix missing "cpu_clk_unhalted.core" event
- selftests: kvm: Adding config fragments
- HID: wacom: correct misreported EKR ring values
- HID: wacom: Correct distance scale for 2nd-gen Intuos devices
- Revert "dm bufio: fix deadlock with loop device"
- ceph: don't try fill file_lock on unsuccessful GETFILELOCK reply
- libceph: fix PG split vs OSD (re)connect race
- drm/nouveau: Don't retry infinitely when receiving no data on i2c over AUX
- gpiolib: never report open-drain/source lines as 'input' to user-space
- userfaultfd_release: always remove uffd flags and clear vm_userfaultfd_ctx
- x86/retpoline: Don't clobber RFLAGS during CALL_NOSPEC on i386
- x86/apic: Handle missing global clockevent gracefully
- x86/CPU/AMD: Clear RDRAND CPUID bit on AMD family 15h/16h
- x86/boot: Save fields explicitly, zero out everything else
- x86/boot: Fix boot regression caused by bootparam sanitizing
- dm kcopyd: always complete failed jobs
- dm btree: fix order of block initialization in btree_split_beneath
- dm space map metadata: fix missing store of apply_bops() return value
- dm table: fix invalid memory accesses with too high sector number
- dm zoned: improve error handling in reclaim
- dm zoned: improve error handling in i/o map code
- dm zoned: properly handle backing device failure
- genirq: Properly pair kobject_del() with kobject_add()
- mm, page_owner: handle THP splits correctly
- mm/zsmalloc.c: migration can leave pages in ZS_EMPTY indefinitely
- mm/zsmalloc.c: fix race condition in zs_destroy_pool
- xfs: fix missing ILOCK unlock when 

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

2019-09-30 Thread Dan Watkins
The lack of events is not the issue.  We see all the events from the
kernel that we would expect to see during a resize, and we see the same
number (and type) of events on both the passing and the failing
instances.

The problem is that if udev processes the sda1 event first then, at
least some of the time, it doesn't detect that sda1 has a partition on
it, so it doesn't create the by-partuuid symlink for that partition.
See comments #23 and #24 for more detail.

** Also affects: linux-azure (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  Incomplete
Status in cloud-utils:
  New
Status in linux-azure package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  Cosmic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions

-- 
Mailing list: https://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 1773859] Please test proposed package

2019-09-30 Thread Steve Langasek
Hello Kees, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.31 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

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

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

[Touch-packages] [Bug 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

2019-09-30 Thread Steve Langasek
a version of systemd with this change was accepted into bionic in error
and has now been withdrawn.  a test case is needed here before it's
accepted properly.

** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Committed => 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/1784454

Title:
  kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC 
image on a z/VM guest
  leads to a kernel panic:

  /lib/debian-installer/start-udev: line 15: can't create 
/sys/module/scsi_mod/par
  ameters/scan: Permission denied 
  ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ 
exitcode=0x00
  000100 
  ¬0.845071|  
  ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic 
#157-Ubun
  tu 
  ¬0.845077|7d107c20 7d107cb0 0002 
000
  0  
 7d107d50 7d107cc8 7d107cc8 00114732  
 008b 009a304c 009f11d0 000b  
 7d107d10 7d107cb0    
 040001cdf800 00114732 7d107cb0 7d107d10  
  ¬0.845089| Call Trace: 
  ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) 
  ¬0.845095|  ¬<001146e2>| show_stack+0x72/0xf8 
  ¬0.845099|  ¬<00555752>| dump_stack+0x82/0xb8 
  ¬0.845101|  ¬<00286390>| panic+0x108/0x250 
  ¬0.845104|  ¬<00166228>| do_exit+0xac0/0xba0 
  ¬0.845106|  ¬<001663c8>| do_group_exit+0x50/0xe0 
  ¬0.845108|  ¬<00166488>| __wake_up_parent+0x0/0x28 
  ¬0.845111|  ¬<007eadda>| system_call+0xee/0x28c 
  ¬0.845113|  ¬<03ff8953983a>| 0x3ff8953983a 
  00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000  
0010F8CA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions

-- 
Mailing list: https://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 1671951] Please test proposed package

2019-09-30 Thread Steve Langasek
Hello Ryan, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.31 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This 

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

2019-09-30 Thread Dan Streetman
** Also affects: systemd (Ubuntu Eoan)
   Importance: High
 Assignee: Dan Streetman (ddstreet)
   Status: Triaged

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

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to 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
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  New
Status in systemd source package in Eoan:
  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 1670291] Please test proposed package

2019-09-30 Thread Steve Langasek
Hello Damiön, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.31 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Released
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions

-- 
Mailing list: https://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 1776626] Please test proposed package

2019-09-30 Thread Steve Langasek
Hello bugproxy, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.31 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab
  part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * cryptsetup in bionic supports creating luks volumes with a non-
  standard sector-size option, and thus this option also needs to be
  used when activating the LUKS volumes. Add sector-size= option support
  to /etc/crypttab.

  [Test Case]

   * Create a plain LUKS volume with sector-size 4096
   * Specify sector-size=4096 option in /etc/crypttab
   * reload systemd, start systemd-cryptsetup@.service for that volume
   * check the journal, to ensure that `sector-size` option was recognized and 
is active. (i.e. there is not error messages about unrecognized option 
`sector-size` from systemd-cryptsetup)

  [Regression Potential]

   * This is an optional argument, not used by default. Currently custom
  sector-size crypttab does not work correctly, and thus cannot regress.

  [Other Info]
   
   * Original bug report

  Support fast clear key dm-crypt with 4k support

  Extend /etc/crypttab  to enable 4k sector support in plain mode

  The proposed enhancements are posted on github, see
   https://github.com/systemd/systemd/issues/8881

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions

-- 
Mailing list: https://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 1773148] Please test proposed package

2019-09-30 Thread Steve Langasek
Hello errors.ubuntu.com, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.31 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

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

Title:
  /lib/systemd/systemd-
  
journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

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

Bug description:
  [Impact]

   * systemd aborts journald, upon watchdog expiry and generates lots of crash 
reports
   * it appears that journald is simply stuck in fsync
   * it has been agreed to disable watchdog timer on journald

  [Test Case]

   * watch drop-off of errors w.r.t. watchdog timer

  [Regression Potential]

   * Potentially journald does get stuck, and thus is no longer
  automatically restarted with a sigabrt crash. However, so far, it is
  not known to do that.

  
  [Other Info]
   
   * Original bug report

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
237-3ubuntu10, the problem page at 
https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://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 1840510] Re: Please enable PGO and LTO for arm64

2019-09-30 Thread Brian Murray
** Bug watch added: Debian Bug tracker #934812
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812

** Also affects: python3-defaults (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812
   Importance: Unknown
   Status: Unknown

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

Title:
  Please enable PGO and LTO for arm64

Status in python3-defaults package in Ubuntu:
  New
Status in python3-defaults package in Debian:
  Unknown

Bug description:
  The rules file conditionally enables PGO and LTO in the python3 build
  and while it's enabled for many platforms it's not enabled for arm64.
  This is worth about 30% performance. Please enable it.

  A patch is available here with the original debian bug report:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=934812

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1840510/+subscriptions

-- 
Mailing list: https://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 1834875] Re: cloud-init growpart race with udev

2019-09-30 Thread Dan Streetman
> You're proposing retriggering events and _then_ waiting

I'm proposing make sure that the uevent(s) for the specific partition
you're interested in have started processing before you start waiting,
which is what the retriggering does.

But it could be a kernel bug, sure.

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

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  Incomplete
Status in cloud-utils:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  Cosmic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions

-- 
Mailing list: https://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 1846090] [NEW] GDX1505:00 27C6:01F1 Touchpad Screenpad support

2019-09-30 Thread Ilya
Public bug reported:

Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad and
screen - all in one)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-29-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Tue Oct  1 00:53:26 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 435.21, 5.0.0-29-generic, x86_64: installed
 virtualbox, 5.2.32, 5.0.0-29-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:3e9b] (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Device [1043:1021]
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] [1043:180e]
InstallationDate: Installed on 2019-09-27 (3 days ago)
InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 13d3:5755 IMC Networks 
 Bus 001 Device 004: ID 8087:0aaa Intel Corp. 
 Bus 001 Device 003: ID 04f3:2544 Elan Microelectronics Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. ZenBook Pro 15 UX550GDX_UX580GD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=4fba8275-1f29-4ddc-8a1c-e239d3b76c14 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: UX550GDX.302
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: UX550GDX
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX550GDX.302:bd10/09/2018:svnASUSTeKCOMPUTERINC.:pnZenBookPro15UX550GDX_UX580GD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX550GDX:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ZenBook Pro
dmi.product.name: ZenBook Pro 15 UX550GDX_UX580GD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic third-party-packages ubuntu

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

Title:
  GDX1505:00 27C6:01F1 Touchpad Screenpad support

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu does not support asus zenbook pro UX580GD screenpad (touchpad
  and screen - all in one)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  435.21  Sun Aug 25 08:17:57 
CDT 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Tue Oct  1 00:53:26 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 435.21, 

[Touch-packages] [Bug 1503426] Re: package libgl1-mesa-glx 10.1.3-0ubuntu0.5 failed to install/upgrade: 73.3516:subprocess installed post-installation script returned error exit status 2

2019-09-30 Thread Timo Aaltonen
best to close then

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

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

Title:
  package libgl1-mesa-glx 10.1.3-0ubuntu0.5 failed to install/upgrade:
  73.3516:subprocess installed post-installation script returned error
  exit status 2

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  dont know

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  ProcVersionSignature: Ubuntu 3.13.0-65.106-generic 3.13.11-ckt26
  Uname: Linux 3.13.0-65-generic i686
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.16
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Tue Oct  6 22:23:51 2015
  DistUpgraded: 2014-10-04 21:58:08,179 DEBUG enabling apt cron job
  DistroCodename: trusty
  DistroVariant: ubuntu
  DkmsStatus:
   fglrx-core, 15.200, 3.13.0-53-generic, i686: installed
   fglrx-core, 15.200, 3.13.0-65-generic, i686: installed
  DuplicateSignature: 
package:libgl1-mesa-glx:10.1.3-0ubuntu0.5:73.3516:subprocess installed 
post-installation script returned error exit status 2
  ErrorMessage: 73.3516:subprocess installed post-installation script returned 
error exit status 2
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2115]
   Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] 
[1002:9591] (prog-if 00 [VGA controller])
 Subsystem: Lenovo Device [17aa:2116]
  InstallationDate: Installed on 2013-03-11 (939 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release i386 
(20120817.3)
  MachineType: LENOVO 2055WJ5
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-65-generic 
root=UUID=36beee87-735a-4fa3-be27-9ffde707bfa6 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.17.5ubuntu5.4
   apt  1.0.1ubuntu2.10
  SourcePackage: mesa
  Title: package libgl1-mesa-glx 10.1.3-0ubuntu0.5 failed to install/upgrade: 
73.3516:subprocess installed post-installation script returned error exit 
status 2
  UpgradeStatus: Upgraded to trusty on 2014-10-04 (367 days ago)
  dmi.bios.date: 01/09/2009
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET56WW (2.02 )
  dmi.board.name: 2055WJ5
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6FET56WW(2.02):bd01/09/2009:svnLENOVO:pn2055WJ5:pvrThinkPadT500:rvnLENOVO:rn2055WJ5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 2055WJ5
  dmi.product.version: ThinkPad T500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.11.3+14.04.20150313-0ubuntu1
  version.libdrm2: libdrm2 2.4.60-2~ubuntu14.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.6
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue Oct  6 22:35:23 2015
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16467 
   vendor LEN
  xserver.version: 2:1.15.1-0ubuntu2.7

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

-- 
Mailing list: https://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 1770268] Re: [GeForce GTX 1080] 18.04 DisplayPort 15m cable no display

2019-09-30 Thread Timo Aaltonen
still the same with 18.04.3/19.04?

** Package changed: mesa (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 mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1770268

Title:
  [GeForce GTX 1080]  18.04 DisplayPort 15m cable no display

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  related: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable no display after 
starting "EFI VGA"
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1747488

  related: [GeForce GTX 1080] 17.10.1 DisplayPort 15m cable monitor flickering
  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1747492

  
  See related bug reports.

  The same behavior is seen with Ubuntu 18.04.

  Setting `nomodeset` in the grub kernel line is the only way for the
  installer to be displayed. If `nomodeset` is not set, the installer
  will boot into full resolution 3440x1440 and no display is able to
  reach the monitor.

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

-- 
Mailing list: https://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 1751407] Re: package libegl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2

2019-09-30 Thread Timo Aaltonen
Setting up libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1) ...
 update-alternatives: error: cannot stat file 
'/usr/bin/java/jdk-9.0.4/bin/jar': Not a directory
 dpkg: error processing package libegl1-mesa:amd64 (--configure):
  subprocess installed post-installation script returned error exit status 2

** Changed in: mesa (Ubuntu)
   Status: New => Invalid

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

Title:
  package libegl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 2

Status in mesa package in Ubuntu:
  Invalid

Bug description:
  The new application  installation is failed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libegl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32~16.04.2-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Feb 24 10:52:45 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libegl1-mesa:amd64:17.2.8-0ubuntu0~16.04.1
   Setting up libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1) ...
   update-alternatives: error: cannot stat file 
'/usr/bin/java/jdk-9.0.4/bin/jar': Not a directory
   dpkg: error processing package libegl1-mesa:amd64 (--configure):
subprocess installed post-installation script returned error exit status 2
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 2
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   NVIDIA Corporation G98M [Quadro NVS 160M] [10de:06eb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo G98M [Quadro NVS 160M] [17aa:3a25]
  InstallationDate: Installed on 2018-02-22 (1 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: LENOVO ZHAOYANG E43
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.10.0-28-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: mesa
  Title: package libegl1-mesa:amd64 17.2.8-0ubuntu0~16.04.1 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/26/2008
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 0DCN56WW
  dmi.board.name: LE9
  dmi.board.vendor: Lenovo
  dmi.board.version: Rev 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Lenovo
  dmi.chassis.version: Rev 1.0
  dmi.modalias: 
dmi:bvnLENOVO:bvr0DCN56WW:bd12/26/2008:svnLENOVO:pnZHAOYANGE43:pvrRev1.0:rvnLenovo:rnLE9:rvrRev1.0:cvnLenovo:ct10:cvrRev1.0:
  dmi.product.name: ZHAOYANG E43
  dmi.product.version: Rev 1.0
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.3+16.04.20171116-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Feb 24 10:46:39 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs: Output  LVDS-1   
VGA-1
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

-- 
Mailing list: https://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 881526] Re: AMD graphics hardware hangs with an homogeneous coloured screen or blank screen, and with chirp coming from the graphics card

2019-09-30 Thread Timo Aaltonen
closing as it's reported to be caused by overheating

** Changed in: mesa (Ubuntu)
   Status: Triaged => Invalid

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

Title:
  AMD graphics hardware hangs with an homogeneous coloured screen or
  blank screen, and with chirp coming from the graphics card

Status in Mesa:
  Confirmed
Status in mesa package in Ubuntu:
  Invalid

Bug description:
  Happens at random, but more frequently running videos on YouTube with
  the HTML5 player (https://www.youtube.com/html5) or with the XBMC home
  theatre software.

  /var/log/kern.log:
  Oct 25 14:53:46 lt9630 kernel: [  737.900416] INFO: rcu_sched_state detected 
stall on CPU 2 (t=15000 jiffies)
  Oct 25 14:55:46 lt9630 kernel: [  857.813946] [fglrx] ASIC hang happened
  Oct 25 14:55:46 lt9630 kernel: [  857.813950] Pid: 1149, comm: Xorg Tainted: 
P C  3.0.0-12-generic #20-Ubuntu
  Oct 25 14:55:46 lt9630 kernel: [  857.813951] Call Trace:
  Oct 25 14:55:46 lt9630 kernel: [  857.813985]  [] 
KCL_DEBUG_OsDump+0xe/0x10 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814003]  [] 
firegl_hardwareHangRecovery+0x1c/0x50 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814036]  [] ? 
_ZN4Asic9WaitUntil15ResetASICIfHungEv+0x9/0x10 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814068]  [] ? 
_ZN4Asic9WaitUntil15WaitForCompleteEv+0x6c/0xb0 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814099]  [] ? 
_ZN15ExecutableUnits10CPRingIdleE15idle_WaitMethod12_QS_CP_RING_+0xe4$
  Oct 25 14:55:46 lt9630 kernel: [  857.814127]  [] ? 
_ZN10CMMSurfaceD1Ev+0xcb/0xe0 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814158]  [] ? 
_ZN15ExecutableUnits7PM4idleE15idle_WaitMethod+0x4b/0x90 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814187]  [] ? 
_ZN15QS_PRIVATE_CORE9QsPM4idleE15idle_WaitMethod+0x31/0x60 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814215]  [] ? 
_ZN10QS_PRIVATE11synchronizeEv+0x2a/0x30 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814243]  [] ? 
_Z8uCWDDEQCmjjPvjS_+0x3b5/0x10c0 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814246]  [] ? 
down+0x2e/0x50
  Oct 25 14:55:46 lt9630 kernel: [  857.814266]  [] ? 
firegl_cmmqs_CWDDE_32+0x332/0x440 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814285]  [] ? 
firegl_cmmqs_CWDDE32+0x70/0x100 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814288]  [] ? 
security_capable+0x2a/0x30
  Oct 25 14:55:46 lt9630 kernel: [  857.814306]  [] ? 
firegl_cmmqs_createdriver+0x170/0x170 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814322]  [] ? 
firegl_ioctl+0x1e8/0x250 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814333]  [] ? 
ip_firegl_unlocked_ioctl+0xe/0x20 [fglrx]
  Oct 25 14:55:46 lt9630 kernel: [  857.814335]  [] ? 
do_vfs_ioctl+0x8a/0x340
  Oct 25 14:55:46 lt9630 kernel: [  857.814338]  [] ? 
vfs_read+0x10d/0x180
  Oct 25 14:55:46 lt9630 kernel: [  857.814339]  [] ? 
sys_ioctl+0x91/0xa0
  Oct 25 14:55:46 lt9630 kernel: [  857.814342]  [] ? 
system_call_fastpath+0x16/0x1b
  Oct 25 14:55:46 lt9630 kernel: [  857.814345] pubdev:0xa02fd600, num 
of device:1 , name:fglrx, major 8, minor 88.
  Oct 25 14:55:46 lt9630 kernel: [  857.814346] device 0 : 0x88019b85 .

  Oct 25 14:55:46 lt9630 kernel: [  857.814345] pubdev:0xa02fd600, num 
of device:1 , name:fglrx, major 8, minor 88.
  Oct 25 14:55:46 lt9630 kernel: [  857.814346] device 0 : 0x88019b85 .
  Oct 25 14:55:46 lt9630 kernel: [  857.814348] Asic ID:0x6779, revision:0x3c, 
MMIOReg:0xc90012b8.
  Oct 25 14:55:46 lt9630 kernel: [  857.814349] FB phys addr: 0xc000, MC 
:0xf, Total FB size :0x4000.
  Oct 25 14:55:46 lt9630 kernel: [  857.814351] gart table MC:0xf0f8fd000, 
Physical:0xcf8fd000, size:0x402000.
  Oct 25 14:55:46 lt9630 kernel: [  857.814353] mc_node :FB, total 1 zones
  Oct 25 14:55:46 lt9630 kernel: [  857.814354] MC start:0xf, 
Physical:0xc000, size:0xfd0.
  Oct 25 14:55:46 lt9630 kernel: [  857.814356] Mapped heap -- Offset:0x0, 
size:0xf8fd000, reference count:33, mapping count:0,
  Oct 25 14:55:46 lt9630 kernel: [  857.814357] Mapped heap -- Offset:0x0, 
size:0x100, reference count:1, mapping count:0,
  Oct 25 14:55:46 lt9630 kernel: [  857.814359] Mapped heap -- 
Offset:0xf8fd000, size:0x403000, reference count:1, mapping count:0,
  Oct 25 14:55:46 lt9630 kernel: [  857.814360] mc_node :INV_FB, total 1 zones
  Oct 25 14:55:46 lt9630 kernel: [  857.814362] MC start:0xf0fd0, 
Physical:0xcfd0, size:0x3030.
  Oct 25 14:55:46 lt9630 kernel: [  857.814363] Mapped heap -- 
Offset:0x302f4000, size:0xc000, reference count:1, mapping count:0,
  Oct 25 14:55:46 lt9630 kernel: [  857.814365] mc_node :GART_USWC, total 2 
zones
  Oct 25 14:55:46 lt9630 kernel: [  857.814366] MC start:0x4010, 
Physical:0x0, size:0x5000.
  Oct 25 14:55:46 lt9630 kernel: [  857.814367] 

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

2019-09-30 Thread Steve Langasek
Hello Ryan, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  

[Touch-packages] [Bug 1670291] Re: Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

2019-09-30 Thread Steve Langasek
Hello Damiön, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done-bionic
** Tags added: verification-needed verification-needed-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/1670291

Title:
  Landscape: Upgrade 14.04.5 to 16.04.2 fails unable to reboot

Status in landscape-client package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in landscape-client source package in Trusty:
  Fix Released
Status in systemd source package in Trusty:
  New
Status in landscape-client source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in landscape-client source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in landscape-client source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  https://github.com/systemd/systemd/pull/10061

  [Impact]

   * When logind is not available, shutdown command fails to schedule a
  shutdown, and despite its intentions to immediately shutdown, does not
  do so.

  [Test Case]

sudo systemctl mask systemd-logind.service
sudo systemctl stop systemd-logind.service
shutdown +1

  The expectation is that system goes to shutdown.

  It is buggy if the system remains up - i.e. command returns to shell
  with exit code 1.

  [Regression Potential]

   * It is a corner case to run against systemd-shim logind / or logind
  not otherwise available. The function still performs a clean-shutdown,
  and should not cause loss of work.

  [Other Info]
   
   * Original bug report, running against systemd-shim/systemd-service post 
trusty->xenial upgrade, pre-reboot.

  
  Used Landscape (Paid Canonical Subscription) to upgrade one of my machines.

  Landscape only shows "In Progress" for more than 8 hours now and asked
  for a reboot of the machine in a second alert.

  In the reboot attempt I get the message:
  =
  Failed to set wall message, ignoring: Method "SetWallMessage" with signature 
"sb" on interface "org.freedesktop.login1.Manager" doesn't exist
  Failed to call ScheduleShutdown in logind, proceeding with immediate 
shutdown: Method "ScheduleShutdown" with signature "st" on interface 
"org.freedesktop.login1.Manager" doesn't exist
  =

  Steps to reproduce:
  * Fully updated 14.04.5 machine
  * Open Landscape
  * Choose the machine
  * Choose Packages
  * This computer can be upgraded to a newer release
  * Apply
  * Wait 2 hours
  * Alert comes in a seperate Landscape message Machine is ready for reboot
  * Choose Info... Power
  * Deliver to selected computers as soon as possible
  * Error message

  I found this thread on reddit about this issue maybe the solution can be 
built into the upgrade script
  
https://www.reddit.com/r/linuxquestions/comments/4wy3go/trying_to_run_as_user_instance_but_the_system_has/

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/landscape-client/+bug/1670291/+subscriptions

-- 
Mailing list: https://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 1773859] Re: upgrades to 18.04 fail

2019-09-30 Thread Steve Langasek
Hello Kees, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Bionic)
   Status: Triaged => Fix Committed

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue the upgrade.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

2019-09-30 Thread Steve Langasek
Hello errors.ubuntu.com, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  /lib/systemd/systemd-
  
journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

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

Bug description:
  [Impact]

   * systemd aborts journald, upon watchdog expiry and generates lots of crash 
reports
   * it appears that journald is simply stuck in fsync
   * it has been agreed to disable watchdog timer on journald

  [Test Case]

   * watch drop-off of errors w.r.t. watchdog timer

  [Regression Potential]

   * Potentially journald does get stuck, and thus is no longer
  automatically restarted with a sigabrt crash. However, so far, it is
  not known to do that.

  
  [Other Info]
   
   * Original bug report

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
237-3ubuntu10, the problem page at 
https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://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 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part

2019-09-30 Thread Steve Langasek
Hello bugproxy, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Bionic)
   Status: In Progress => Fix Committed

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab
  part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

   * cryptsetup in bionic supports creating luks volumes with a non-
  standard sector-size option, and thus this option also needs to be
  used when activating the LUKS volumes. Add sector-size= option support
  to /etc/crypttab.

  [Test Case]

   * Create a plain LUKS volume with sector-size 4096
   * Specify sector-size=4096 option in /etc/crypttab
   * reload systemd, start systemd-cryptsetup@.service for that volume
   * check the journal, to ensure that `sector-size` option was recognized and 
is active. (i.e. there is not error messages about unrecognized option 
`sector-size` from systemd-cryptsetup)

  [Regression Potential]

   * This is an optional argument, not used by default. Currently custom
  sector-size crypttab does not work correctly, and thus cannot regress.

  [Other Info]
   
   * Original bug report

  Support fast clear key dm-crypt with 4k support

  Extend /etc/crypttab  to enable 4k sector support in plain mode

  The proposed enhancements are posted on github, see
   https://github.com/systemd/systemd/issues/8881

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions

-- 
Mailing list: https://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 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

2019-09-30 Thread Steve Langasek
Hello Frank, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.30 in a few
hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: systemd (Ubuntu Bionic)
   Status: Incomplete => Fix Committed

** Tags removed: verification-done verification-done-bionic
** Tags added: verification-needed verification-needed-bionic

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

Title:
  kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC 
image on a z/VM guest
  leads to a kernel panic:

  /lib/debian-installer/start-udev: line 15: can't create 
/sys/module/scsi_mod/par
  ameters/scan: Permission denied 
  ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ 
exitcode=0x00
  000100 
  ¬0.845071|  
  ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic 
#157-Ubun
  tu 
  ¬0.845077|7d107c20 7d107cb0 0002 
000
  0  
 7d107d50 7d107cc8 7d107cc8 00114732  
 008b 009a304c 009f11d0 000b  
 7d107d10 7d107cb0    
 040001cdf800 00114732 7d107cb0 7d107d10  
  ¬0.845089| Call Trace: 
  ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) 
  ¬0.845095|  ¬<001146e2>| show_stack+0x72/0xf8 
  ¬0.845099|  ¬<00555752>| dump_stack+0x82/0xb8 
  ¬0.845101|  ¬<00286390>| panic+0x108/0x250 
  ¬0.845104|  ¬<00166228>| do_exit+0xac0/0xba0 
  ¬0.845106|  ¬<001663c8>| do_group_exit+0x50/0xe0 
  ¬0.845108|  ¬<00166488>| __wake_up_parent+0x0/0x28 
  ¬0.845111|  ¬<007eadda>| system_call+0xee/0x28c 
  ¬0.845113|  ¬<03ff8953983a>| 0x3ff8953983a 
  00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000  
0010F8CA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions

-- 
Mailing list: https://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 1780842] Re: package libglx-mesa0 18.0.0~rc5-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package nv

2019-09-30 Thread Timo Aaltonen
*** This bug is a duplicate of bug 1753796 ***
https://bugs.launchpad.net/bugs/1753796

** This bug has been marked a duplicate of bug 1753796
   Conflict between libglx-mesa and nvidia-390 on Ubuntu 18.04 (pre-release)

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

Title:
  package libglx-mesa0 18.0.0~rc5-1ubuntu1 failed to install/upgrade:
  trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0',
  which is also in package nvidia-396 396.26-0ubuntu1

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  The major system change occurred when I upgraded the nvidia driver.
  At that point I have a system dependency issue with lib-mesa0 trying
  to overwrite a file that the nvidia driver created.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libglx-mesa0 18.0.0~rc5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.26  Mon Apr 30 18:01:39 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   libglx-mesa0:amd64: Install
   libglx-mesa0:i386: Install
   libglapi-mesa:i386: Install
   libglapi-mesa:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jul  9 14:07:16 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 4.15.0-24-generic, x86_64: installed
   nvidia-396, 396.26, 4.15.0-24-generic, x86_64: installed
  DpkgTerminalLog:
   Preparing to unpack .../libglx-mesa0_18.0.5-0ubuntu0~18.04.1_amd64.deb ...
   De-configuring libglx-mesa0:i386 (18.0.0~rc5-1ubuntu1) ...
   Unpacking libglx-mesa0:amd64 (18.0.5-0ubuntu0~18.04.1) over 
(18.0.0~rc5-1ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libglx-mesa0_18.0.5-0ubuntu0~18.04.1_amd64.deb 
(--unpack):
trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which 
is also in package nvidia-396 396.26-0ubuntu1
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package 
nvidia-396 396.26-0ubuntu1
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] Device [1462:11ad]
   NVIDIA Corporation GP106M [GeForce GTX 1060 Mobile] [10de:1c20] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP106M [GeForce GTX 
1060 Mobile] [1462:11ad]
  InstallationDate: Installed on 2018-05-30 (40 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Micro-Star International Co., Ltd. GS63VR 7RF
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=e77cd1c5-8736-401d-bd7f-0f4ecc27bfcb ro quiet splash intel_iommu=on 
vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  Renderer: Software
  SourcePackage: mesa
  Title: package libglx-mesa0 18.0.0~rc5-1ubuntu1 failed to install/upgrade: 
trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is 
also in package nvidia-396 396.26-0ubuntu1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/26/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16K2IMS.314
  dmi.board.asset.tag: Default string
  dmi.board.name: MS-16K2
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16K2IMS.314:bd10/26/2017:svnMicro-StarInternationalCo.,Ltd.:pnGS63VR7RF:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16K2:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrN/A:
  dmi.product.family: GS
  dmi.product.name: GS63VR 7RF
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.nvidia-graphics-drivers: 

[Touch-packages] [Bug 1002978] Re: [meta-bug] Inverted Internal microphone (phase inversion)

2019-09-30 Thread Gsus
I have the same problem with a lenovo V110 and ALC236.

I don't see an option to invert the channel or even mute permanently a
channel.

Kernel 5.2.0

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

Title:
  [meta-bug] Inverted Internal microphone (phase inversion)

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  This is a metabug for all machines that are having phase inverted
  internal microphones.

  If your internal mic is either completely silent (no signal), or you
  can possibly pick a very small sound, with much background noise, even
  though you have set gain to maximum, there is something you could try.

  Install the pavucontrol application, start it and go to the "Input Devices" 
tab. Unlock the channels (there is a keylock icon), then mute the right channel 
while keeping the left channel at the volume you want.
  If the internal mic is now working correctly, you have an inverted internal 
mic, so that your right channel cancels out the left one.

  (If you're not running PulseAudio, you can try doing the same through
  AlsaMixer instead (see https://wiki.ubuntu.com/Audio/Alsamixer ), try
  changing "Capture" level or "Internal Mic" or "Internal Mic Boost"
  using the Q,E,Z,C keys.)

  If so, please file a separate bug against the alsa-driver for your
  issue, make sure hardware info gets attached to it (either alsa-info
  as per https://wiki.ubuntu.com/Audio/AlsaInfo or the standard ones
  that follows when you do "ubuntu-bug alsa-driver" ), then write a
  comment in this bug, with your machine name and a pointer to the other
  bug.

  As time permits, I'll try to work on fixing them for the next Ubuntu release. 
Thanks!
   -- David Henningsson

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1002978/+subscriptions

-- 
Mailing list: https://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 1846053] [NEW] Use llvm 9 or even llvm-10

2019-09-30 Thread KOLANICH
Public bug reported:

1. llvm 9 has been released, but mesa in the repo still uses llvm 8.
2. llvm 9 bitcode libs for OpenCL cause llvm-8-based mesa to fail because their 
file format has changed
3. There was a bug in llvm-8-based mesa in disco that caused the OpenCL 
compiler to hang on the kernels combining hyperbolic and circular functions. 
There were no hang after I have rebuilt mesa and dri against llvm-10.

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

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

Title:
  Use llvm 9 or even llvm-10

Status in mesa package in Ubuntu:
  New

Bug description:
  1. llvm 9 has been released, but mesa in the repo still uses llvm 8.
  2. llvm 9 bitcode libs for OpenCL cause llvm-8-based mesa to fail because 
their file format has changed
  3. There was a bug in llvm-8-based mesa in disco that caused the OpenCL 
compiler to hang on the kernels combining hyperbolic and circular functions. 
There were no hang after I have rebuilt mesa and dri against llvm-10.

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

-- 
Mailing list: https://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 1784454] Re: kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

2019-09-30 Thread Steve Langasek
this bug lacks a clear SRU test case for bionic (there is obviously no
4.4 kernel in 18.04).

** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Committed => 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/1784454

Title:
  kernel panic on booting kernel 4.4 based d-i from 16.04.5 RC image

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in debian-installer package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  New
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Incomplete

Bug description:
  Booting d-i based on kernel 4.4 (from ./boot folder) from the 16.04.5 RC 
image on a z/VM guest
  leads to a kernel panic:

  /lib/debian-installer/start-udev: line 15: can't create 
/sys/module/scsi_mod/par
  ameters/scan: Permission denied 
  ¬0.845071| Kernel panic - not syncing: Attempted to kill initÜ 
exitcode=0x00
  000100 
  ¬0.845071|  
  ¬0.845075| CPU: 0 PID: 1 Comm: /init Not tainted 4.4.0-131-generic 
#157-Ubun
  tu 
  ¬0.845077|7d107c20 7d107cb0 0002 
000
  0  
 7d107d50 7d107cc8 7d107cc8 00114732  
 008b 009a304c 009f11d0 000b  
 7d107d10 7d107cb0    
 040001cdf800 00114732 7d107cb0 7d107d10  
  ¬0.845089| Call Trace: 
  ¬0.845093| (¬<0011461a>| show_trace+0xfa/0x150) 
  ¬0.845095|  ¬<001146e2>| show_stack+0x72/0xf8 
  ¬0.845099|  ¬<00555752>| dump_stack+0x82/0xb8 
  ¬0.845101|  ¬<00286390>| panic+0x108/0x250 
  ¬0.845104|  ¬<00166228>| do_exit+0xac0/0xba0 
  ¬0.845106|  ¬<001663c8>| do_group_exit+0x50/0xe0 
  ¬0.845108|  ¬<00166488>| __wake_up_parent+0x0/0x28 
  ¬0.845111|  ¬<007eadda>| system_call+0xee/0x28c 
  ¬0.845113|  ¬<03ff8953983a>| 0x3ff8953983a 
  00: HCPGIR450W CP entered; disabled wait PSW 00020001 8000  
0010F8CA

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1784454/+subscriptions

-- 
Mailing list: https://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 1846006] Re: package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk3:amd64 is not ready for configuration cannot configure (current status 'half-inst

2019-09-30 Thread Gunnar Hjalmarsson
Your system seems not to be quite updated. What if you do:

sudo apt update
sudo apt upgrade

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

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

Title:
  package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade:
  package ibus-gtk3:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  The PC keeps giving that there is a bug and tells to report it

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ibus-gtk3:amd64 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Mon Sep 30 22:50:47 2019
  DuplicateSignature:
   package:ibus-gtk3:amd64:1.5.11-1ubuntu2
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package ibus-gtk3:amd64 (--configure):
package ibus-gtk3:amd64 is not ready for configuration
  ErrorMessage: package ibus-gtk3:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-03-28 (551 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.29ubuntu0.1
  SourcePackage: ibus
  Title: package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package ibus-gtk3:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1846048] [NEW] volume+ volume- key repeat don't work

2019-09-30 Thread Eugene
Public bug reported:

Description:Ubuntu Eoan Ermine (development branch)
Release:19.10

What expected:
Hold down the volume up or down button on a keyboard. The sound level gradually 
increases to a maximum or decreases to a minimum.

What happened instead:
The sound level decreases or increases by one step and does not change anymore. 
Repeat keystroke works in terminal or browser.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  eugene 2396 F pulseaudio
 /dev/snd/controlC1:  eugene 2396 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 30 22:13:24 2019
InstallationDate: Installed on 2019-09-29 (1 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic
Symptom_Jack: Green Line Out, Rear
Symptom_PulseAudioLog:
 
Symptom_Type: Volume slider, or mixer problems
Title: [AB350M-DS3H V2, Realtek ALC887-VD, Green Line Out, Rear] volume slider 
problem
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2019
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F42a
dmi.board.asset.tag: Default string
dmi.board.name: AB350M-DS3H V2-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF42a:bd07/31/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: AB350M-DS3H V2
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-09-29T14:32:22.851648

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  volume+ volume- key repeat don't work

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu Eoan Ermine (development branch)
  Release:  19.10

  What expected:
  Hold down the volume up or down button on a keyboard. The sound level 
gradually increases to a maximum or decreases to a minimum.

  What happened instead:
  The sound level decreases or increases by one step and does not change 
anymore. Repeat keystroke works in terminal or browser.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  eugene 2396 F pulseaudio
   /dev/snd/controlC1:  eugene 2396 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 30 22:13:24 2019
  InstallationDate: Installed on 2019-09-29 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulseAudioLog:
   
  Symptom_Type: Volume slider, or mixer problems
  Title: [AB350M-DS3H V2, Realtek ALC887-VD, Green Line Out, Rear] volume 
slider problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/31/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F42a
  dmi.board.asset.tag: Default string
  dmi.board.name: AB350M-DS3H V2-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF42a:bd07/31/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350M-DS3HV2:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350M-DS3HV2-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
  

[Touch-packages] [Bug 1834875] Re: cloud-init growpart race with udev

2019-09-30 Thread Dan Watkins
I don't think we're looking for a way to wait for udev.  For this bug to
present, udev has to have processed all of the available events (i.e.
there's nothing left to wait for), and have done so incorrectly
(probably as a result of its interaction with the Azure kernel, as this
doesn't reproduce on the generic kernel).

And, to be clear, your proposal isn't just a "wait".  You're proposing
retriggering events and _then_ waiting.  This sounds like a potential
workaround, but I believe it would further mask the underlying problem.
We (as Ubuntu) control every part of this, so I think we should be able
to fix this properly, rather than working around a linux-azure/udev
issue in cloud-init and/or cloud-image-utils.

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

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  Incomplete
Status in cloud-utils:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  Cosmic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions

-- 
Mailing list: https://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 1836695] Re: systemd fails to setup static routes at boot when using DHCP

2019-09-30 Thread Dan Streetman
> @ddstreet It seems to work as expected in Eoan!

excellent!  now I need to figure out (again) which upstream commit fixes
this, as I know I found it before but apparently forgot to include the
info in this bug...

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

Title:
  systemd fails to setup static routes at boot when using DHCP

Status in netplan:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Disco:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  a systemd-networkd configuration that uses ipv4 dhcp but ignores the
  dhcp-provided route, and instead sets up a static route, and also does
  not include a static ipv4 address, fails to actually create the static
  route.

  This is due to networkd attempting to set up the static route before
  the dhcp ipv4 address is assigned, and the kernel does not allow
  creation of the route before setting up corresponding ipv4 address.

  this results in a network that does have the dhcp-provided ipv4
  address, but is missing both its dhcp-provided route (because networkd
  is configured to ignore it) and the static route (because networkd was
  not able to create it).

  [test case]

  (remove or unconfigure netplan, so it will not conflict with this
  manual networkd configuration)

  create a networkd config file, e.g.:

  $ cat /etc/systemd/network/10-eth0.network 
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [Route]
  Destination=10.0.0.0/8
  Gateway=10.202.51.1

  [DHCP]
  UseRoutes=false

  
  then *reboot* the system, and check that the static route was not applied:

  $ ip r
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.254 

  
  note that because networkd does not remove ipv4 addresses that it manages 
(including dhcpv4 addresses), restarting networkd after the initial boot
  will correctly create the static route, e.g.:

  ubuntu@lp1836695-b:~$ ip r
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.254 
  ubuntu@lp1836695-b:~$ sudo systemctl restart systemd-networkd
  ubuntu@lp1836695-b:~$ ip r
  10.0.0.0/8 via 10.202.51.1 dev eth0 proto static 
  10.202.51.0/24 dev eth0 proto kernel scope link src 10.202.51.254 

  [regression potential]

  adjusting how networkd works always carries the risk of breaking
  networking.

  TBD detailed regression potential after analyzing fix.

  [other info]

  original description:

  --

  
  Consider the following setup:

  network:
    version: 2
    renderer: networkd
    ethernets:
  ens4:
    dhcp-identifier: mac
    dhcp4: yes
    dhcp4-overrides:
  use-dns: no
  use-ntp: no
  send-hostname: no
  use-hostname: no
  use-routes: no
    routes:
    - to: 10.0.0.0/8
  via: 10.50.0.1
    optional: true

  Thus I only need to get the IP address by DHCP, then add some static
  routes. This setup doesn't work. Apparently `routes` keyword only
  works when using static addresses.

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

-- 
Mailing list: https://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 1828220] Re: apt-get --install-suggests applied recursively

2019-09-30 Thread whitis
I would also point out not only is the recursive interpretation of
--install-suggests incorrect, it is internally inconsistent.

apt-get --dry-run remove --purge -o APT::AutoRemove::Suggests-
Important=0 --auto-remove geda geda-utils geda-examples kicad kicad-doc-
en librecad oregano qelectrotech xcircuit gerbv pcb pcb-gtk pcb-common
pcb-rnd pcb2gcode visolate caneda fritzing

Does not appear to recurse.   Neither does substituting "autoremove" for
"purge" or trying to remove suggests on "clang" the same way.

--install-suggests and install-recommends should default to a recursion
level of 1 and allow you to specify a greater level of recursion in the
unlikely event you desire.

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

Title:
  apt-get --install-suggests applied recursively

Status in apt package in Ubuntu:
  Opinion

Bug description:
  In a blatent violation of the principal of least surprise, --install-
  suggests installs packages that are in the suggested packages for
  packages that are not listed on the command line.  It installs
  suggested packages for other packages deep in the dependency
  hierarchy.

  Do not type this command except on an expendable (virtual) machine:
  sudo apt-get --install-suggests install -y geda geda-utils geda-examples 
kicad kicad-doc-en librecad oregano qelectrotech xcircuit gerbv pcb pcb-gtk 
pcb-common pcb-rnd pcb2gcode visolate caneda fritzing

  
  In this case, something installed clang which depends on clang-6.0.   
clang-6.0 very foolishly suggested gnustep which, since apt inappropriately 
applied --installed-suggests many layers down the dependency tree, then 
installed the entire gnustep suite of applications.   Gnustep, after several 
more layers of inappropriate suggestsions, caused roaraudio to be installed 
which caused errors on every apt-get install command.

  aptitude why roaraudio
  i   clang  Depends  clang-6.0 (>= 6.0~)
  i A clang-6.0  Suggests gnustep
  i A gnustepSuggests mpdcon.app 
  i A mpdcon.app Suggests mpd
  i A mpdDepends  libroar2   
  i A libroar2   Suggests libmuroar0 
  i A libmuroar0 Suggests roaraudio | muroard

  clang later gets installed explicitly, so I cant trace the specific
  path back to the CAD packages that were installed but clang-6.0 and
  roaraudio are first installed after the listed apt-get command above.
  Which ultimately installs 2675 packages.   Tracing forward with
  debtree --with-suggests also doesn't make it clear why clang was
  installed but debtree doesn't include dependencies of recommended
  packages.

  
  The actual recommends of these packages listed on the apt-get command were 
rather modest:
  Recommends: geda-gsymcheck, geda-gattrib
  Recommends: geda
  Recommends: xsltproc
  Recommends: gnucap
  Recommends: qelectrotech-examples (= 1:0.5-2), qelectrotech-data (= 1:0.5-2), 
qttranslations5-l10n
  Recommends: extra-xdg-menus
  Recommends: extra-xdg-menus

  The following command suggests that a single package, geda, is sufficient to 
reproduce the bug.
  apt-rdepends --follow=Depends,PreDepends,Suggests,Recommends geda | fgrep -i 
clang
  It also shows that adding Suggests blows up the dependency tree from 664 
lines of dependency info to 49965 lines corresponding to 5865 unique packages 
vs 173.

  clang traces back to i18nspector (through python), though it isn't
  clear why that was needed.  It may trace baqck to check-all-the-things
  and from ther to devscripts but for some reason that isn't included in
  the apt-rdepends output. debmake, gem2deb, git-buildpackage,
  javahelper, duck, devscripts-el, svn-buildpackage, and mozzila-
  devscipts all depend on devscripts.   Like many dependencies that
  should not have been followed, check-all-the-things was only a
  suggests.

  i18nspector -> python3-rply -> python3-appdirs -> clang/clang-6.0

  This debacle left me with about 6368 packages installed and about 20GB
  of extra disk space wasted compared to running a fairly similar set of
  many apt-get commands, without selectively including --install-
  recommends on a few, on another machine.  And ultimately, it appears
  will be necessary to completely reinstall this computer from scratch
  to undo the damage.   In total, there were only about 50 packages
  included in "Suggests" without recursion.

  Not only does --install-suggests behave incorrectly but the man page
  fails to document this destructive behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.10
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  7 23:11:00 2019
  InstallationDate: Installed on 2019-05-02 (5 days ago)
  InstallationMedia: Ubuntu 

[Touch-packages] [Bug 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-09-30 Thread Dan Streetman
Can you provide networkd conf file(s) and steps to reproduce the issue
please?

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

Title:
  IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

-- 
Mailing list: https://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 1828220] Re: apt-get --install-suggests applied recursively

2019-09-30 Thread whitis
The claim that it does what it says it does is false.

What it, in fact does, is consider suggested packages of OTHER packages
as a dependency for installing.   This recursive behavior is not
advertised and not acceptable.   For that behavior, one should have to
use an option such as --install-suggests-recursive and not --install-
suggests.


There is an enormous difference between installing the packages suggested by 
the package geda and installing the packages suggested many levels deep.   Even 
without a defective suggests list, this would not be expected or desired 
behavior.

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

Title:
  apt-get --install-suggests applied recursively

Status in apt package in Ubuntu:
  Opinion

Bug description:
  In a blatent violation of the principal of least surprise, --install-
  suggests installs packages that are in the suggested packages for
  packages that are not listed on the command line.  It installs
  suggested packages for other packages deep in the dependency
  hierarchy.

  Do not type this command except on an expendable (virtual) machine:
  sudo apt-get --install-suggests install -y geda geda-utils geda-examples 
kicad kicad-doc-en librecad oregano qelectrotech xcircuit gerbv pcb pcb-gtk 
pcb-common pcb-rnd pcb2gcode visolate caneda fritzing

  
  In this case, something installed clang which depends on clang-6.0.   
clang-6.0 very foolishly suggested gnustep which, since apt inappropriately 
applied --installed-suggests many layers down the dependency tree, then 
installed the entire gnustep suite of applications.   Gnustep, after several 
more layers of inappropriate suggestsions, caused roaraudio to be installed 
which caused errors on every apt-get install command.

  aptitude why roaraudio
  i   clang  Depends  clang-6.0 (>= 6.0~)
  i A clang-6.0  Suggests gnustep
  i A gnustepSuggests mpdcon.app 
  i A mpdcon.app Suggests mpd
  i A mpdDepends  libroar2   
  i A libroar2   Suggests libmuroar0 
  i A libmuroar0 Suggests roaraudio | muroard

  clang later gets installed explicitly, so I cant trace the specific
  path back to the CAD packages that were installed but clang-6.0 and
  roaraudio are first installed after the listed apt-get command above.
  Which ultimately installs 2675 packages.   Tracing forward with
  debtree --with-suggests also doesn't make it clear why clang was
  installed but debtree doesn't include dependencies of recommended
  packages.

  
  The actual recommends of these packages listed on the apt-get command were 
rather modest:
  Recommends: geda-gsymcheck, geda-gattrib
  Recommends: geda
  Recommends: xsltproc
  Recommends: gnucap
  Recommends: qelectrotech-examples (= 1:0.5-2), qelectrotech-data (= 1:0.5-2), 
qttranslations5-l10n
  Recommends: extra-xdg-menus
  Recommends: extra-xdg-menus

  The following command suggests that a single package, geda, is sufficient to 
reproduce the bug.
  apt-rdepends --follow=Depends,PreDepends,Suggests,Recommends geda | fgrep -i 
clang
  It also shows that adding Suggests blows up the dependency tree from 664 
lines of dependency info to 49965 lines corresponding to 5865 unique packages 
vs 173.

  clang traces back to i18nspector (through python), though it isn't
  clear why that was needed.  It may trace baqck to check-all-the-things
  and from ther to devscripts but for some reason that isn't included in
  the apt-rdepends output. debmake, gem2deb, git-buildpackage,
  javahelper, duck, devscripts-el, svn-buildpackage, and mozzila-
  devscipts all depend on devscripts.   Like many dependencies that
  should not have been followed, check-all-the-things was only a
  suggests.

  i18nspector -> python3-rply -> python3-appdirs -> clang/clang-6.0

  This debacle left me with about 6368 packages installed and about 20GB
  of extra disk space wasted compared to running a fairly similar set of
  many apt-get commands, without selectively including --install-
  recommends on a few, on another machine.  And ultimately, it appears
  will be necessary to completely reinstall this computer from scratch
  to undo the damage.   In total, there were only about 50 packages
  included in "Suggests" without recursion.

  Not only does --install-suggests behave incorrectly but the man page
  fails to document this destructive behavior.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.10
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  7 23:11:00 2019
  InstallationDate: Installed on 2019-05-02 (5 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   

[Touch-packages] [Bug 1843479] Re: gzip in Ubuntu Eoan results in Exec format error on WSL1

2019-09-30 Thread Hayden Barnes
This was determined to be a bug in the WSL1 ELF loader and fix is
inbound from the WSL side.
https://github.com/microsoft/WSL/issues/4461#issuecomment-536023805

Please close on Ubuntu.

** Bug watch added: github.com/microsoft/WSL/issues #4461
   https://github.com/microsoft/WSL/issues/4461

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

Title:
  gzip in Ubuntu Eoan results in Exec format error on WSL1

Status in gzip package in Ubuntu:
  Confirmed

Bug description:
  Summary:

  Running gzip on WSL1 results in the following error:

  $ gzip
  -bash: /bin/gzip: cannot execute binary file: Exec format error

  What I expect to happen:

  gzip executes correctly on WSL1.

  What happens instead:

  gzip fails with an Exec format error.

  Notes:

  I suspect a change in how gzip is being built for Eoan is causing
  issues with ELF parsing on the WSL1 translation layer. For example:

  On Disco with gzip 1.9-3:

  $ file /bin/gzip
  /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, for GNU/Linux 
3.2.0, BuildID[sha1]=efa859c26eaf8e035efe9a139361e2a60cd17b3e, stripped

  On Eoan with gzip 1.10-0ubuntu3:

  $ file /bin/gzip
  /bin/gzip: ELF 64-bit LSB pie executable, x86-64, version 1 (SYSV), 
dynamically linked, interpreter /lib64/ld-linux-x86-64.so.2, 
BuildID[sha1]=bc0f5994544c2a469d04c914bf4bf44b4ded6040, for GNU/Linux 3.2.0, 
stripped

  Eoan ships with gzip 1.10, while Disco ships with gzip 1.9, but I do
  not believe this is an issue in 1.10 because this error does not occur
  when building gzip from GNU project source on Ubuntu Eoan.

  Justifications:

  WSL1 will need to be patched in future Windows builds for this change
  in ELF. However that patch will likely not be backported to older
  builds of Windows, including Windows Enterprise/Server 2019.

  To ensure Eoan can run on current and older builds of Windows Ubuntu
  should consider looking at how it's building gzip and see if it can be
  made to 'play nice' until WSL1 can be updated.

  This was originally reported here:
  https://github.com/microsoft/WSL/issues/4461

  Details:

  Description:Ubuntu Eoan Ermine (development branch)
  Release:19.10

  gzip:
Installed: 1.10-0ubuntu3
Candidate: 1.10-0ubuntu3
Version table:
   *** 1.10-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

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

-- 
Mailing list: https://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 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-09-30 Thread Dan Streetman
** Bug watch added: github.com/systemd/systemd/issues #12886
   https://github.com/systemd/systemd/issues/12886

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

Title:
  IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

-- 
Mailing list: https://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 1846025] [NEW] cron can crash (SIGSEGV) when trying to re-parent orphans

2019-09-30 Thread buck huppmann
Public bug reported:

We sometimes have people come and go, leaving behind
old crontab files that, when they return, and are given
the same username, no longer have the correct uid.
This can cause cron to crash when it has the old crontab
file on its orphans list. Below's a lightly-edited
backtrace, with username replaced by "joeuser".

Here's the user's (former) crontab:

-rw--- 1 48031 crontab 1216 Jul 26 15:36
/var/spool/cron/crontabs/joeuser

Whereas his new uid is

# id -u joeuser
48529

This is on bionic with cron 3.0pl1-128.1ubuntu1

--buck

Core was generated by `/usr/sbin/cron -f'.
Program terminated with signal SIGSEGV, Segmentation fault.
#0  find_user (name=, db=0x0, db@entry=0x55fc9fe93ea0)
at database.c:316
316 database.c: No such file or directory.
(gdb) bt
#0  find_user (name=, db=0x0, db@entry=0x55fc9fe93ea0)
at database.c:316
#1  force_rescan_user (old_db=old_db@entry=0x0, 
new_db=new_db@entry=0x7fffe687cb50, 
fname=fname@entry=0x55fc9fe93ea0 "joeuser", old_mtime=old_mtime@entry=0)
at database.c:588
#2  0x55fc9f2b03ab in process_crontab (uname=0x55fc9fe93df0 "joeuser", 
fname=, tabname=0x55fc9fe93ec0 "crontabs/joeuser", 
statbuf=statbuf@entry=0x7fffe687ca80, new_db=new_db@entry=0x7fffe687cb50, 
old_db=old_db@entry=0x0) at database.c:460
#3  0x55fc9f2b0ba6 in check_orphans (db=0x7fffe687cb50) at database.c:639
#4  0x55fc9f2af6ce in main (argc=, argv=)
at cron.c:178

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

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

Title:
  cron can crash (SIGSEGV) when trying to re-parent orphans

Status in cron package in Ubuntu:
  New

Bug description:
  We sometimes have people come and go, leaving behind
  old crontab files that, when they return, and are given
  the same username, no longer have the correct uid.
  This can cause cron to crash when it has the old crontab
  file on its orphans list. Below's a lightly-edited
  backtrace, with username replaced by "joeuser".

  Here's the user's (former) crontab:

  -rw--- 1 48031 crontab 1216 Jul 26 15:36
  /var/spool/cron/crontabs/joeuser

  Whereas his new uid is

  # id -u joeuser
  48529

  This is on bionic with cron 3.0pl1-128.1ubuntu1

  --buck

  Core was generated by `/usr/sbin/cron -f'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  find_user (name=, db=0x0, db@entry=0x55fc9fe93ea0)
  at database.c:316
  316   database.c: No such file or directory.
  (gdb) bt
  #0  find_user (name=, db=0x0, db@entry=0x55fc9fe93ea0)
  at database.c:316
  #1  force_rescan_user (old_db=old_db@entry=0x0, 
  new_db=new_db@entry=0x7fffe687cb50, 
  fname=fname@entry=0x55fc9fe93ea0 "joeuser", old_mtime=old_mtime@entry=0)
  at database.c:588
  #2  0x55fc9f2b03ab in process_crontab (uname=0x55fc9fe93df0 "joeuser", 
  fname=, tabname=0x55fc9fe93ec0 "crontabs/joeuser", 
  statbuf=statbuf@entry=0x7fffe687ca80, new_db=new_db@entry=0x7fffe687cb50, 
  old_db=old_db@entry=0x0) at database.c:460
  #3  0x55fc9f2b0ba6 in check_orphans (db=0x7fffe687cb50) at database.c:639
  #4  0x55fc9f2af6ce in main (argc=, argv=)
  at cron.c:178

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

-- 
Mailing list: https://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 1834875] Re: cloud-init growpart race with udev

2019-09-30 Thread Dan Streetman
I think that is the correct way to wait for udev to process a specific
device's changes.

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

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  Incomplete
Status in cloud-utils:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  Cosmic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions

-- 
Mailing list: https://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 1845950] Re: Bug reporting doesn't work upon a crash

2019-09-30 Thread Brian Murray
Could you please attach the file /etc/apport/crashdb.conf to your bug
report? Thanks in advance.

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

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

Title:
  Bug reporting doesn't work upon a crash

Status in apport package in Ubuntu:
  Incomplete

Bug description:
  On eoan, after an initial startup / login, if an application crashes
  and I click "report", I get a prompt saying the crash is reported and
  to check the web page open in the browser to see if I have any
  additional information.. except it never opens a page. The dialog just
  disappears, the crash log stays in /var/crash and nothing happens.

  The only way to actually file it is to run ubuntu-bug  which does
  work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: called for pid 3409, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3941) Mon Sep 30 07:28:15 2019: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:2696160:2019-09-26 13:17:54.338476419 -0500:2019-09-26 
13:17:55.338476419 -0500:/var/crash/_opt_google_chrome_chrome.1000.crash
   640:1000:117:2499555:2019-09-30 07:28:32.538634538 -0500:2019-09-30 
07:28:33.538634538 -0500:/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 30 07:34:38 2019
  InstallationDate: Installed on 2018-07-24 (432 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (72 days ago)

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

-- 
Mailing list: https://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 1846006] Re: package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk3:amd64 is not ready for configuration cannot configure (current status 'half-inst

2019-09-30 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade:
  package ibus-gtk3:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in ibus package in Ubuntu:
  New

Bug description:
  The PC keeps giving that there is a bug and tells to report it

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ibus-gtk3:amd64 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Mon Sep 30 22:50:47 2019
  DuplicateSignature:
   package:ibus-gtk3:amd64:1.5.11-1ubuntu2
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package ibus-gtk3:amd64 (--configure):
package ibus-gtk3:amd64 is not ready for configuration
  ErrorMessage: package ibus-gtk3:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-03-28 (551 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.29ubuntu0.1
  SourcePackage: ibus
  Title: package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package ibus-gtk3:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1845998] Re: No audio from Dell Lattitude E5530 - looks like everything should be working fine, but no sound.

2019-09-30 Thread Chris
Don't know how to remove the bug - but it fixed itself after a reboot
:shrug:

** Changed in: alsa-driver (Ubuntu)
   Status: New => Invalid

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

Title:
  No audio from Dell Lattitude E5530 - looks like everything should be
  working fine, but no sound.

Status in alsa-driver package in Ubuntu:
  Invalid

Bug description:
  Release: Ubunto 18.04.3 LTS

  Expected Behaviour:
  Sound to come out of the speakers

  Actual Behaviour:
  No sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Sep 30 17:18:10 2019
  InstallationDate: Installed on 2019-09-11 (18 days ago)
  InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1845998/+subscriptions

-- 
Mailing list: https://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 1846006] [NEW] package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: package ibus-gtk3:amd64 is not ready for configuration cannot configure (current status 'half-in

2019-09-30 Thread Pamu
Public bug reported:

The PC keeps giving that there is a bug and tells to report it

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: ibus-gtk3:amd64 1.5.11-1ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-62-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.19
Architecture: amd64
Date: Mon Sep 30 22:50:47 2019
DuplicateSignature:
 package:ibus-gtk3:amd64:1.5.11-1ubuntu2
 Processing triggers for mime-support (3.59ubuntu1) ...
 dpkg: error processing package ibus-gtk3:amd64 (--configure):
  package ibus-gtk3:amd64 is not ready for configuration
ErrorMessage: package ibus-gtk3:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
InstallationDate: Installed on 2018-03-28 (551 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.29ubuntu0.1
SourcePackage: ibus
Title: package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package ibus-gtk3:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade:
  package ibus-gtk3:amd64 is not ready for configuration  cannot
  configure (current status 'half-installed')

Status in ibus package in Ubuntu:
  New

Bug description:
  The PC keeps giving that there is a bug and tells to report it

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ibus-gtk3:amd64 1.5.11-1ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-62.69~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  Date: Mon Sep 30 22:50:47 2019
  DuplicateSignature:
   package:ibus-gtk3:amd64:1.5.11-1ubuntu2
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package ibus-gtk3:amd64 (--configure):
package ibus-gtk3:amd64 is not ready for configuration
  ErrorMessage: package ibus-gtk3:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-03-28 (551 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.29ubuntu0.1
  SourcePackage: ibus
  Title: package ibus-gtk3:amd64 1.5.11-1ubuntu2 failed to install/upgrade: 
package ibus-gtk3:amd64 is not ready for configuration  cannot configure 
(current status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

2019-09-30 Thread Patrick O'Keeffe
Hi apologies if this is the wrong thread. Just wanted to report I see
this issue on the Raspberry Pi build of Ubuntu MATE 16.04 running `mate-
control-center` 1.16.1-1~xenial4.0 and `systemd` 229-4ubuntu21.22.

I see resolution failures using `sudo` afterwards so even though it
still works, stdout gets polluted with error messages. I would call that
an ill effect.

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

Title:
  [hostnamed] Changing hostname doesn't update /etc/hosts

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  Confirmed
Status in gnome-control-center package in Debian:
  Fix Released

Bug description:
  GUI
  ---
  1a. Run sudo gnome-control-center, or...
  1b. Save the gnome-control-center.pkla from 
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556
 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run 
gnome-control-center as an admin user

  2. Enter the Details panel
  3. The "Device name" (hostname) text field should be editable; change the 
text to something else.
  4. The hostname is updated instantly which can be verified by looking in 
/etc/hostname. However /etc/hosts/ is not updated.

  Command line
  
  hostnamectl set-hostname

  The hostnamed documentation at 
http://www.freedesktop.org/wiki/Software/systemd/hostnamed says
  "To properly handle name lookups with changing local hostnames without having 
to edit /etc/hosts for them we recommend using hostnamed in combination with 
nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ "

  Without /etc/hosts being handled correctly, the hostnamed integration
  is only half-working.


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 08:52:57 2013
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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

-- 
Mailing list: https://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 1845998] [NEW] No audio from Dell Lattitude E5530 - looks like everything should be working fine, but no sound.

2019-09-30 Thread Chris
Public bug reported:

Release: Ubunto 18.04.3 LTS

Expected Behaviour:
Sound to come out of the speakers

Actual Behaviour:
No sound.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base (not installed)
ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
Uname: Linux 4.15.0-64-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Mon Sep 30 17:18:10 2019
InstallationDate: Installed on 2019-09-11 (18 days ago)
InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic uec-images

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

Title:
  No audio from Dell Lattitude E5530 - looks like everything should be
  working fine, but no sound.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Release: Ubunto 18.04.3 LTS

  Expected Behaviour:
  Sound to come out of the speakers

  Actual Behaviour:
  No sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Sep 30 17:18:10 2019
  InstallationDate: Installed on 2019-09-11 (18 days ago)
  InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1845998/+subscriptions

-- 
Mailing list: https://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 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

2019-09-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: unity-control-center (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  [hostnamed] Changing hostname doesn't update /etc/hosts

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  Confirmed
Status in gnome-control-center package in Debian:
  Fix Released

Bug description:
  GUI
  ---
  1a. Run sudo gnome-control-center, or...
  1b. Save the gnome-control-center.pkla from 
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556
 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run 
gnome-control-center as an admin user

  2. Enter the Details panel
  3. The "Device name" (hostname) text field should be editable; change the 
text to something else.
  4. The hostname is updated instantly which can be verified by looking in 
/etc/hostname. However /etc/hosts/ is not updated.

  Command line
  
  hostnamectl set-hostname

  The hostnamed documentation at 
http://www.freedesktop.org/wiki/Software/systemd/hostnamed says
  "To properly handle name lookups with changing local hostnames without having 
to edit /etc/hosts for them we recommend using hostnamed in combination with 
nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ "

  Without /etc/hosts being handled correctly, the hostnamed integration
  is only half-working.


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 08:52:57 2013
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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

-- 
Mailing list: https://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 1162475] Re: [hostnamed] Changing hostname doesn't update /etc/hosts

2019-09-30 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: gnome-control-center (Ubuntu Xenial)
   Status: New => Confirmed

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

Title:
  [hostnamed] Changing hostname doesn't update /etc/hosts

Status in gnome-control-center package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in unity-control-center package in Ubuntu:
  Won't Fix
Status in gnome-control-center source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Triaged
Status in unity-control-center source package in Xenial:
  Confirmed
Status in gnome-control-center package in Debian:
  Fix Released

Bug description:
  GUI
  ---
  1a. Run sudo gnome-control-center, or...
  1b. Save the gnome-control-center.pkla from 
https://bazaar.launchpad.net/~ubuntu-desktop/gnome-control-center/ubuntu/revision/556
 to /var/lib/polkit-1/localauthority/10-vendor.d/ and then run 
gnome-control-center as an admin user

  2. Enter the Details panel
  3. The "Device name" (hostname) text field should be editable; change the 
text to something else.
  4. The hostname is updated instantly which can be verified by looking in 
/etc/hostname. However /etc/hosts/ is not updated.

  Command line
  
  hostnamectl set-hostname

  The hostnamed documentation at 
http://www.freedesktop.org/wiki/Software/systemd/hostnamed says
  "To properly handle name lookups with changing local hostnames without having 
to edit /etc/hosts for them we recommend using hostnamed in combination with 
nss-myhostname: http://0pointer.de/lennart/projects/nss-myhostname/ "

  Without /etc/hosts being handled correctly, the hostnamed integration
  is only half-working.


  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu18
  ProcVersionSignature: Ubuntu 3.8.0-15.25-generic 3.8.4
  Uname: Linux 3.8.0-15-generic x86_64
  ApportVersion: 2.9.2-0ubuntu5
  Architecture: amd64
  Date: Sun Mar 31 08:52:57 2013
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup26.0-0ubuntu1
   gnome-control-center-signon 0.1.5-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.03.26-0ubuntu1

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

-- 
Mailing list: https://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 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP

2019-09-30 Thread Dan Streetman
Hmm looks like https://github.com/systemd/systemd/issues/11458

** Bug watch added: github.com/systemd/systemd/issues #11458
   https://github.com/systemd/systemd/issues/11458

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

Title:
  systemd-networkd fails to apply static IPv4 when the static IP is the
  same as previously configured by DHCP

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  In bionic, running systemd 237-3ubuntu10.22 and netplan.io
  0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an
  interface with a static IPv4 address if the statically confiugred
  address is the same as the interface already has gotten from DHCP.

  This will cause the interface to loose its IP address when the DHCP
  lease exires, even though you've told netplan to configure it as
  static.

  I expect systemd-networkd to actually configure an IP address as
  static, regardless of what address the interface has before from DHCP.

  # lsb_release  -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  # apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.22

  # apt-cache policy netplan.io
  netplan.io:
Installed: 0.97-0ubuntu1~18.04.1

  A paste of systemd-networkd's debug log when I run "netplan apply" and
  the interface already has the static IP configured from DHCP.

  It seems like upon a restart, systemd-networkd will allways add
  whatever IP config it had before the service stopped, and then apply
  changes (if any). Since my new config has the same IP as it already
  had, it does nothing even though the new config has static
  configuration.

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

-- 
Mailing list: https://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 1832754] Re: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs.

2019-09-30 Thread Bug Watch Updater
** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  "shutdown[1]: Failed to wait for process: Protocol error" at shutdown
  or reboot and hangs.

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

Bug description:
  I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait
  for process: Protocol error" at shutdown or reboot and hangs.

  systemd: 237-3ubuntu10.22

  It's this issue:
  https://github.com/systemd/systemd/issues/8155

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

-- 
Mailing list: https://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 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP

2019-09-30 Thread Dan Streetman
Thanks!  that clarifies it - I think this is a bug upstream with
systemd.

> if I set "dhcp4: no" explicit when confiugring static addressing, it
behaves as expected

are you sure?  that isn't what I would expect, it seems the problem is
networkd doesn't adjust the address lifetime when networkd is restarted
and the address changes from dhcp->static; i would not expect the
DHCP=no param it fix that.  Although that's a netplan config, so
possibly netplan does something additional under the covers, other than
what systemd-networkd does.

> It seems like upon a restart, systemd-networkd will allways add
whatever IP config it had before the service stopped, and then apply
changes

not exactly, what's happening is when you stop networkd, it does not
remove network configuration that it manages, so in this case it would
leave the dhcp address on the interface.  then when you (re)start
networkd, it does not change existing addresses that it manages, so it
sees that the interface already has the address that it's been
configured to use as a static address, and does not change it.  It looks
like networkd needs to also check the address's lifetime to make sure
static addrs have their lifetime set to 'forever' (I have not actually
checked the code yet to verify this).

If you reboot, or manually remove the address, or just bring the
interface down and back up, networkd will re-add the address with
'forever' lft, so this should only be a problem when you have manually
changed the config for an address from dhcp->static using the same ip
address, and then restart networkd without rebooting, at least IIUC.

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

Title:
  systemd-networkd fails to apply static IPv4 when the static IP is the
  same as previously configured by DHCP

Status in systemd package in Ubuntu:
  New

Bug description:
  In bionic, running systemd 237-3ubuntu10.22 and netplan.io
  0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an
  interface with a static IPv4 address if the statically confiugred
  address is the same as the interface already has gotten from DHCP.

  This will cause the interface to loose its IP address when the DHCP
  lease exires, even though you've told netplan to configure it as
  static.

  I expect systemd-networkd to actually configure an IP address as
  static, regardless of what address the interface has before from DHCP.

  # lsb_release  -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  # apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.22

  # apt-cache policy netplan.io
  netplan.io:
Installed: 0.97-0ubuntu1~18.04.1

  A paste of systemd-networkd's debug log when I run "netplan apply" and
  the interface already has the static IP configured from DHCP.

  It seems like upon a restart, systemd-networkd will allways add
  whatever IP config it had before the service stopped, and then apply
  changes (if any). Since my new config has the same IP as it already
  had, it does nothing even though the new config has static
  configuration.

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

-- 
Mailing list: https://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 1834875] Re: cloud-init growpart race with udev

2019-09-30 Thread Dan Watkins
Dan, are you asking for that to get more debugging information, or are
you suggesting that as a fix for this?

(I'm yet to be convinced that this isn't a regression in (the
kernel|src:systemd), so I don't think that we should have to run _any_
additional commands to address this.)

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

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  Incomplete
Status in cloud-utils:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  Cosmic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions

-- 
Mailing list: https://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 1773148] Re: /lib/systemd/systemd-journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

2019-09-30 Thread Brian Murray
** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => High

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

Title:
  /lib/systemd/systemd-
  
journald:6:fsync:fsync_directory_of_file:journal_file_rotate:do_rotate:server_rotate

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

Bug description:
  [Impact]

   * systemd aborts journald, upon watchdog expiry and generates lots of crash 
reports
   * it appears that journald is simply stuck in fsync
   * it has been agreed to disable watchdog timer on journald

  [Test Case]

   * watch drop-off of errors w.r.t. watchdog timer

  [Regression Potential]

   * Potentially journald does get stuck, and thus is no longer
  automatically restarted with a sigabrt crash. However, so far, it is
  not known to do that.

  
  [Other Info]
   
   * Original bug report

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
systemd.  This problem was most recently seen with package version 
237-3ubuntu10, the problem page at 
https://errors.ubuntu.com/problem/ff29f7ff39be0e227f0187ad72e5d458e95f6fcf 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.

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

-- 
Mailing list: https://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 1832754] Re: "shutdown[1]: Failed to wait for process: Protocol error" at shutdown or reboot and hangs.

2019-09-30 Thread Dan Streetman
** Bug watch added: github.com/systemd/systemd/issues #8155
   https://github.com/systemd/systemd/issues/8155

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

Title:
  "shutdown[1]: Failed to wait for process: Protocol error" at shutdown
  or reboot and hangs.

Status in systemd:
  Unknown
Status in systemd package in Ubuntu:
  New

Bug description:
  I am using Xubuntu 18.04 64 bit and got "shutdown[1]: Failed to wait
  for process: Protocol error" at shutdown or reboot and hangs.

  systemd: 237-3ubuntu10.22

  It's this issue:
  https://github.com/systemd/systemd/issues/8155

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

-- 
Mailing list: https://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 1834138] Re: PA: Don't restore the streams to sinks/sources with only unavailable ports

2019-09-30 Thread Łukasz Zemczak
@Daniel @Sebastien the upload generally looks good, but I'm slightly worried 
about the Launchpad-Bugs-Fixed: including the bug number of 1663528 - which has 
been reverted as part of the upload. We don't really have good ways to tag a 
bug as 'fix reverted' via the LP changelog parsing, and when we accept the SRU 
right now, the bug will be marked for verification and we'd have to make sure 
to switch it to 'Won't Fix' again after release. I guess the easiest way would 
be to re-upload 1:11.1-1ubuntu7.4 without the changelog entry of 
1:11.1-1ubuntu7.3, but with an additional mention of a fix for 1556439 in one 
version. I would normally re-upload myself to save you the trouble, but I guess 
that would break your workflow (I got yelled at for doing that once before).
Could you consider re-uploading with that changelog modification? It would save 
much trouble and possible future confusion. Thanks.

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

Title:
  PA: Don't restore the streams to sinks/sources with only unavailable
  ports

Status in HWE Next:
  New
Status in OEM Priority Project:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Bionic:
  Incomplete
Status in pulseaudio source package in Disco:
  Fix Committed
Status in pulseaudio source package in Eoan:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  The Lenovo P520 machine has dual analogue codecs, so there are two
  sinks and two sources in the PA, one has the front headphone and front
  microphone, the other has the rear lineout, linein and rear
  microphone, and the rear microphone always shows up in the gnome-
  sound-setting, When we plug a microphone to front audio jack, there
  are two input devices: rear mic and front mic in the gnome-sound-
  setting, and suppose users select the the front mic to record sound
  via audio app like arecord, the front mic will be bond the arecord,
  after the front mic is unplugged, there is only one rear mic left in
  the gnome-sound-setting, but the binding will not be changed, the
  arecrod still bind to front mic, under this situation if users record
  sound via arecord, they will find they can't record any sound from any
  other input devices even they are listed in the gnome-sound-setting.
  This problem also happens to output devices too.

  [Test Case]

  After applying this patch, I did the same test: unplug the front mic,
  then use the arecord to record sound, the app can record sound from
  rear mic now. After I plug the front mic back, the arecord still
  record from front mic. Also did the similar test for output devices,
  it worked as expected too.

  [Regression Potential]

  Low, Just make a simple check when creating new streams
  (sink_input/source_output), If the restored device (sink/source) has
  ports and all ports are unavialble, it will not restore the binding,
  otherwise it will work as before.

  For the Bionic, This SRU also includes the fix of LP: #1556439, this
  fix is safe and is very low possible to introduce any regression too,
  because it just adds a sink-input/source-output state checking, if the
  sink-input/source-output is unlinking or unlinked, it is useless to
  move it to a new sink/source, furthermore it will trigger an assertion
  that make the pulseaudio crash, adding this check can fix this problem
  (LP: #1556439).

  [Other Info]

  No more info here

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1834138/+subscriptions

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


[Touch-packages] [Bug 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part

2019-09-30 Thread Balint Reczey
Apparently the 237-3ubuntu10.10 upload got overwritten by a security upload, 
too, thus the fix is still not present in systemd.
I'm preparing a new upload and intend to fix this bug.

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

Title:
  [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab
  part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * cryptsetup in bionic supports creating luks volumes with a non-
  standard sector-size option, and thus this option also needs to be
  used when activating the LUKS volumes. Add sector-size= option support
  to /etc/crypttab.

  [Test Case]

   * Create a plain LUKS volume with sector-size 4096
   * Specify sector-size=4096 option in /etc/crypttab
   * reload systemd, start systemd-cryptsetup@.service for that volume
   * check the journal, to ensure that `sector-size` option was recognized and 
is active. (i.e. there is not error messages about unrecognized option 
`sector-size` from systemd-cryptsetup)

  [Regression Potential]

   * This is an optional argument, not used by default. Currently custom
  sector-size crypttab does not work correctly, and thus cannot regress.

  [Other Info]
   
   * Original bug report

  Support fast clear key dm-crypt with 4k support

  Extend /etc/crypttab  to enable 4k sector support in plain mode

  The proposed enhancements are posted on github, see
   https://github.com/systemd/systemd/issues/8881

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions

-- 
Mailing list: https://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 1776626] Re: [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab part

2019-09-30 Thread Balint Reczey
** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Released => In Progress

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

Title:
  [18.10 FEAT] Support 4k sectors for fast clear key dm-crypt - crypttab
  part

Status in Ubuntu on IBM z Systems:
  Fix Released
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Won't Fix
Status in systemd source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * cryptsetup in bionic supports creating luks volumes with a non-
  standard sector-size option, and thus this option also needs to be
  used when activating the LUKS volumes. Add sector-size= option support
  to /etc/crypttab.

  [Test Case]

   * Create a plain LUKS volume with sector-size 4096
   * Specify sector-size=4096 option in /etc/crypttab
   * reload systemd, start systemd-cryptsetup@.service for that volume
   * check the journal, to ensure that `sector-size` option was recognized and 
is active. (i.e. there is not error messages about unrecognized option 
`sector-size` from systemd-cryptsetup)

  [Regression Potential]

   * This is an optional argument, not used by default. Currently custom
  sector-size crypttab does not work correctly, and thus cannot regress.

  [Other Info]
   
   * Original bug report

  Support fast clear key dm-crypt with 4k support

  Extend /etc/crypttab  to enable 4k sector support in plain mode

  The proposed enhancements are posted on github, see
   https://github.com/systemd/systemd/issues/8881

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1776626/+subscriptions

-- 
Mailing list: https://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 1834875] Re: cloud-init growpart race with udev

2019-09-30 Thread Dan Streetman
Pretty sure you need to actually try what I suggested in comment 40, but
of course use the specific dev/partition you're missing the udev symlink
for.

e.g. if you need the symlink for /dev/sda1 then instead of:

$ growpart /dev/sda 1 ; udevadm settle ; ls /dev/disk/by-uuid/$UUID

you should do

$ growpart /dev/sda 1 ; udevadm trigger -w /dev/sda1 ; ls /dev/disk/by-
uuid/$UUID

the -w param is relatively new to udevadm so for older releases like
bionic do 'udevadm trigger /dev/sda1 ; udevadm settle'

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

Title:
  cloud-init growpart race with udev

Status in cloud-init:
  Incomplete
Status in cloud-utils:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  On Azure, it happens regularly (20-30%), that cloud-init's growpart
  module fails to extend the partition to full size.

  Such as in this example:

  

  2019-06-28 12:24:18,666 - util.py[DEBUG]: Running command ['growpart', 
'--dry-run', '/dev/sda', '1'] with allowed return codes [0] (shell=False, 
capture=True)
  2019-06-28 12:24:19,157 - util.py[DEBUG]: Running command ['growpart', 
'/dev/sda', '1'] with allowed return codes [0] (shell=False, capture=True)
  2019-06-28 12:24:19,726 - util.py[DEBUG]: resize_devices took 1.075 seconds
  2019-06-28 12:24:19,726 - handlers.py[DEBUG]: finish: 
init-network/config-growpart: FAIL: running config-growpart with frequency 
always
  2019-06-28 12:24:19,727 - util.py[WARNING]: Running module growpart () failed
  2019-06-28 12:24:19,727 - util.py[DEBUG]: Running module growpart () failed
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/cloudinit/stages.py", line 812, in 
_run_modules
  freq=freq)
File "/usr/lib/python3/dist-packages/cloudinit/cloud.py", line 54, in run
  return self._runners.run(name, functor, args, freq, clear_on_fail)
File "/usr/lib/python3/dist-packages/cloudinit/helpers.py", line 187, in run
  results = functor(*args)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
351, in handle
  func=resize_devices, args=(resizer, devices))
File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 2521, in 
log_time
  ret = func(*args, **kwargs)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
298, in resize_devices
  (old, new) = resizer.resize(disk, ptnum, blockdev)
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
159, in resize
  return (before, get_size(partdev))
File "/usr/lib/python3/dist-packages/cloudinit/config/cc_growpart.py", line 
198, in get_size
  fd = os.open(filename, os.O_RDONLY)
  FileNotFoundError: [Errno 2] No such file or directory: 
'/dev/disk/by-partuuid/a5f2b49f-abd6-427f-bbc4-ba5559235cf3'

  

  @rcj suggested this is a race with udev. This seems to only happen on
  Cosmic and later.

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1834875/+subscriptions

-- 
Mailing list: https://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 1840946] Re: Include cloud-id in user-agent string

2019-09-30 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/373413

** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/373414

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

Title:
  Include cloud-id in user-agent string

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  In Progress
Status in base-files source package in Bionic:
  In Progress
Status in base-files source package in Disco:
  In Progress

Bug description:
  [Impact]

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  [Test Case]
  a) confirm that the motd message is still displayed:
  $ sudo sh /etc/update-motd.d/50-motd-news --force

   * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
     Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

   https://ubuntu.com/kubernetes/docs/release-notes

  b) confirm that cloud_id is set in the user-agent. This should be
  tested in lxd, gce, aws, and azure. Here is an example for lxd:

  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl 
.*cloud_id/"
  + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 
Ubuntu/16.04.6/LTS GNU/Linux/4.15.0-64-generic/x86_64 
Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz uptime/921.00/900.00 cloud_id/lxd -o- 
https://motd.ubuntu.com

  For each of the mentioned clouds, we expect cloud_id to be set to
  their short names: aws, gce, azure.

  For xenial, there is an extra test case:
  c) list the timers to confirm motd-news is active, and will run sometime in 
the next 12h following the installation of the updated package:
  $ systemctl list-timers
  NEXT LEFT LAST PASSED
UNIT ACTIVATES
  Mon 2019-09-30 19:38:55 UTC  6h left  n/a  n/a   
motd-news.timer  motd-news.service
  Mon 2019-09-30 22:45:13 UTC  9h left  n/a  n/a   
apt-daily.timer  apt-daily.service
  Tue 2019-10-01 06:12:11 UTC  16h left n/a  n/a   
apt-daily-upgrade.timer  apt-daily-upgrade.service
  Tue 2019-10-01 13:11:41 UTC  23h left Mon 2019-09-30 13:11:41 UTC  14min ago 
systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service

  [Regression Potential]
  This change adds a new parameter to the already existing user-agent string. 
This relies on the cloud-id tool from cloud-init. Even though it's considered 
trusted to some degree, it may be possible for some clouds to override their 
name in the data fed to cloud-init, which is what cloud-id parses. Therefore 
some precautions were taken when handling its contents:
  - set value to unknown if cloud-id fails, doesn't exist, or produce an empty 
value
  - sanitize the output of cloud-id, and truncate it to a maximum length
  - use a tempfile to store the intermediate output of cloud-id instead of a 
shell variable. One reason being avoiding storing a potentially large amount of 
data in a shell variable, and the other is to avoid mistakes when manipulating 
a shell variable that could contain shell metacharacters.

  [Other Info]
  For xenial, this is also finishing the fix for bug #1637800 which was stuck 
in the SRU queue due to it failing checks. Since the xenial package isn't using 
debhelper, manual dh snippets were added to the maintainer scripts, but they 
missed the dh_systemd_enable chunks. I'm also skipping starting 
motd-news.service, since the timer unit will handle that. This avoids an 
annoying error message about trying to start a unit that is not enabled.

  [Original Description]
  I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

-- 
Mailing list: https://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 1845652] Re: rsync sends everything, not just changes

2019-09-30 Thread peterzay
The following

rsync -v -a -r -W -p -o -g -t --delete --stats 
--exclude=".*" 
--exclude="/snap*" 
~ 
/media/$USER/USB-128GB-3/ 
>bkp_log

copies all contents of home folder each time it is run.

The expectation is that only changed files will be copied and replaced
on the target.

This is reproducible.


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

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

Title:
  rsync sends everything, not just changes

Status in rsync package in Ubuntu:
  New

Bug description:
  Repeated runs of rsync from PC to USB key send everything, not just
  the changes.

  This is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: rsync 3.1.3-6
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 09:18:19 2019
  InstallationDate: Installed on 2019-06-10 (109 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1840946] Re: Include cloud-id in user-agent string

2019-09-30 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/373411

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

Title:
  Include cloud-id in user-agent string

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  In Progress
Status in base-files source package in Bionic:
  In Progress
Status in base-files source package in Disco:
  In Progress

Bug description:
  [Impact]

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  [Test Case]
  a) confirm that the motd message is still displayed:
  $ sudo sh /etc/update-motd.d/50-motd-news --force

   * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
     Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.

   https://ubuntu.com/kubernetes/docs/release-notes

  b) confirm that cloud_id is set in the user-agent. This should be
  tested in lxd, gce, aws, and azure. Here is an example for lxd:

  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl 
.*cloud_id/"
  + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 
Ubuntu/16.04.6/LTS GNU/Linux/4.15.0-64-generic/x86_64 
Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz uptime/921.00/900.00 cloud_id/lxd -o- 
https://motd.ubuntu.com

  For each of the mentioned clouds, we expect cloud_id to be set to
  their short names: aws, gce, azure.

  For xenial, there is an extra test case:
  c) list the timers to confirm motd-news is active, and will run sometime in 
the next 12h following the installation of the updated package:
  $ systemctl list-timers
  NEXT LEFT LAST PASSED
UNIT ACTIVATES
  Mon 2019-09-30 19:38:55 UTC  6h left  n/a  n/a   
motd-news.timer  motd-news.service
  Mon 2019-09-30 22:45:13 UTC  9h left  n/a  n/a   
apt-daily.timer  apt-daily.service
  Tue 2019-10-01 06:12:11 UTC  16h left n/a  n/a   
apt-daily-upgrade.timer  apt-daily-upgrade.service
  Tue 2019-10-01 13:11:41 UTC  23h left Mon 2019-09-30 13:11:41 UTC  14min ago 
systemd-tmpfiles-clean.timer systemd-tmpfiles-clean.service

  [Regression Potential]
  This change adds a new parameter to the already existing user-agent string. 
This relies on the cloud-id tool from cloud-init. Even though it's considered 
trusted to some degree, it may be possible for some clouds to override their 
name in the data fed to cloud-init, which is what cloud-id parses. Therefore 
some precautions were taken when handling its contents:
  - set value to unknown if cloud-id fails, doesn't exist, or produce an empty 
value
  - sanitize the output of cloud-id, and truncate it to a maximum length
  - use a tempfile to store the intermediate output of cloud-id instead of a 
shell variable. One reason being avoiding storing a potentially large amount of 
data in a shell variable, and the other is to avoid mistakes when manipulating 
a shell variable that could contain shell metacharacters.

  [Other Info]
  For xenial, this is also finishing the fix for bug #1637800 which was stuck 
in the SRU queue due to it failing checks. Since the xenial package isn't using 
debhelper, manual dh snippets were added to the maintainer scripts, but they 
missed the dh_systemd_enable chunks. I'm also skipping starting 
motd-news.service, since the timer unit will handle that. This avoids an 
annoying error message about trying to start a unit that is not enabled.

  [Original Description]
  I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.

  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one
  is available.

  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1840946/+subscriptions

-- 
Mailing list: https://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 1637800] Re: add a motd script for news

2019-09-30 Thread Andreas Hasenack
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git/base-files/+merge/373411

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

Title:
  add a motd script for news

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed

Bug description:
  Add a new update-motd script for printing news and/or important
  notices.

  == SRU ==

  [IMPACT]
  We should add important security messages or other news to the MOTD.

  [TEST CASE]
  Login to the system and ensure that the "news" section of the motd is 
displayed.  Note that you might need to force trigger an update by running 
'sudo update-motd'.

  [REGRESSION POTENTIAL]
  No reasonable regression potential.  The script simply prints 2 lines of text 
to the MOTD.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1637800/+subscriptions

-- 
Mailing list: https://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 1845652] Re: rsync sends everything, not just changes

2019-09-30 Thread Rafael David Tinoco
Hello peterzay,

IF you are facing something like:

https://unix.stackexchange.com/questions/85993/why-rsync-attempts-to-
copy-file-that-is-already-up-to-date

Then I would recommend reading the 1st answer to that question, which
explains why and when rsync would try to re-sync everything again.

If not,

Could you please provide a better description of the problem, and,
perhaps, a way on how to reproduce, step by step, the issue you are
facing ?

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

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

Title:
  rsync sends everything, not just changes

Status in rsync package in Ubuntu:
  Incomplete

Bug description:
  Repeated runs of rsync from PC to USB key send everything, not just
  the changes.

  This is reproducible.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: rsync 3.1.3-6
  ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 27 09:18:19 2019
  InstallationDate: Installed on 2019-06-10 (109 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: rsync
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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

2019-09-30 Thread Jamie Strandboge
** Changed in: pulseaudio (Ubuntu Xenial)
   Status: In Progress => Triaged

** Changed in: pulseaudio (Ubuntu Bionic)
   Status: In Progress => Triaged

-- 
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:
  Triaged
Status in pulseaudio source package in Bionic:
  Triaged

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]

  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  

[Touch-packages] [Bug 1840946] Re: Include cloud-id in user-agent string

2019-09-30 Thread Andreas Hasenack
** Description changed:

  [Impact]
  
  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one is
  available.
  
+ [Test Case]
+ a) confirm that the motd message is still displayed:
+ $ sudo sh /etc/update-motd.d/50-motd-news --force
  
- [Test Case]
+  * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
+Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.
  
-  * detailed instructions how to reproduce the bug
+  https://ubuntu.com/kubernetes/docs/release-notes
  
-  * these should allow someone who is not familiar with the affected
-    package to reproduce the bug and verify that the updated package fixes
-    the problem.
+ b) confirm that cloud_id is set in the user-agent. This should be tested
+ in lxd, gce, aws, and azure. Here is an example for lxd:
+ 
+ $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl 
.*cloud_id/"
+ + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 
Ubuntu/16.04.6/LTS GNU/Linux/4.15.0-64-generic/x86_64 
Intel(R)/Core(TM)/i7-7600U/CPU/@/2.80GHz uptime/921.00/900.00 cloud_id/lxd -o- 
https://motd.ubuntu.com
+ 
+ For each of the mentioned clouds, we expect cloud_id to be set to their
+ short names: aws, gce, azure.
  
  [Regression Potential]
+ This change adds a new parameter to the already existing user-agent string. 
This relies on the cloud-id tool from cloud-init. Even though it's considered 
trusted to some degree, it may be possible for some clouds to override their 
name in the data fed to cloud-init, which is what cloud-id parses. Therefore 
some precautions were taken when handling its contents:
+ - set value to unknown if cloud-id fails, doesn't exist, or produce an empty 
value
+ - sanitize the output of cloud-id, and truncate it to a maximum length
+ - use a tempfile to store the intermediate output of cloud-id instead of a 
shell variable. One reason being avoiding storing a potentially large amount of 
data in a shell variable, and the other is to avoid mistakes when manipulating 
a shell variable that could contain shell metacharacters.
  
-  * discussion of how regressions are most likely to manifest as a result
- of this change.
- 
-  * It is assumed that any SRU candidate patch is well-tested before
-    upload and has a low overall risk of regression, but it's important
-    to make the effort to think about what ''could'' happen in the
-    event of a regression.
- 
-  * This both shows the SRU team that the risks have been considered,
-    and provides guidance to testers in regression-testing the SRU.
  
  [Other Info]
- 
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
+ For xenial, this is also finishing the fix for bug #1637800 which was stuck 
in the SRU queue due to it failing checks. Since the xenial package isn't using 
debhelper, manual dh snippets were added to the maintainer scripts, but they 
missed the dh_systemd_enable chunks. I'm also skipping starting 
motd-news.service, since the timer unit will handle that. This avoids an 
annoying error message about trying to start a unit that is not enabled.
  
  [Original Description]
  I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.
  
  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one is
  available.
  
  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

** Description changed:

  [Impact]
  
  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one is
  available.
  
  [Test Case]
  a) confirm that the motd message is still displayed:
  $ sudo sh /etc/update-motd.d/50-motd-news --force
  
-  * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
-Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.
+  * Kata Containers are now fully integrated in Charmed Kubernetes 1.16!
+    Yes, charms take the Krazy out of K8s Kata Kluster Konstruction.
  
-  https://ubuntu.com/kubernetes/docs/release-notes
+  https://ubuntu.com/kubernetes/docs/release-notes
  
  b) confirm that cloud_id is set in the user-agent. This should be tested
  in lxd, gce, aws, and azure. Here is an example for lxd:
  
  $ sudo sh -x /etc/update-motd.d/50-motd-news --force 2>&1| grep -E "curl 
.*cloud_id/"
  + curl --connect-timeout 60 --max-time 60 -A curl/7.47.0-1ubuntu2.14 

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

2019-09-30 Thread Balint Reczey
** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Committed => In Progress

** Changed in: systemd (Ubuntu Bionic)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  networkd should allow configuring IPV6 MTU

Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  In Progress

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its larger header overhead.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1671951/+subscriptions

-- 
Mailing list: https://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 1840946] Re: [FFe] include cloud-id in user-agent string

2019-09-30 Thread Andreas Hasenack
** Description changed:

- I'm preemptively filing this bug in case this isn't uploaded before the
- feature freeze.
+ [Impact]
+ 
+  * An explanation of the effects of the bug on users and
+ 
+  * justification for backporting the fix to the stable release.
+ 
+  * In addition, it is helpful, but not required, to include an
+explanation of how the upload fixes this bug.
+ 
+ [Test Case]
+ 
+  * detailed instructions how to reproduce the bug
+ 
+  * these should allow someone who is not familiar with the affected
+package to reproduce the bug and verify that the updated package fixes
+the problem.
+ 
+ [Regression Potential]
+ 
+  * discussion of how regressions are most likely to manifest as a result
+ of this change.
+ 
+  * It is assumed that any SRU candidate patch is well-tested before
+upload and has a low overall risk of regression, but it's important
+to make the effort to think about what ''could'' happen in the
+event of a regression.
+ 
+  * This both shows the SRU team that the risks have been considered,
+and provides guidance to testers in regression-testing the SRU.
+ 
+ [Other Info]
+  
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
+ 
+ [Original Description]
+ I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.
  
  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one is
  available.
  
  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

** Summary changed:

- [FFe] include cloud-id in user-agent string
+ Include cloud-id in user-agent string

** Description changed:

  [Impact]
  
-  * An explanation of the effects of the bug on users and
+ We would like to include a cloud_id/$name parameter to the user-agent
+ string that is sent to https://motd.ubuntu.com. This will allow the
+ server part of motd.ubuntu.com to serve cloud-specific content if one is
+ available.
  
-  * justification for backporting the fix to the stable release.
- 
-  * In addition, it is helpful, but not required, to include an
-explanation of how the upload fixes this bug.
  
  [Test Case]
  
-  * detailed instructions how to reproduce the bug
+  * detailed instructions how to reproduce the bug
  
-  * these should allow someone who is not familiar with the affected
-package to reproduce the bug and verify that the updated package fixes
-the problem.
+  * these should allow someone who is not familiar with the affected
+    package to reproduce the bug and verify that the updated package fixes
+    the problem.
  
  [Regression Potential]
  
-  * discussion of how regressions are most likely to manifest as a result
+  * discussion of how regressions are most likely to manifest as a result
  of this change.
  
-  * It is assumed that any SRU candidate patch is well-tested before
-upload and has a low overall risk of regression, but it's important
-to make the effort to think about what ''could'' happen in the
-event of a regression.
+  * It is assumed that any SRU candidate patch is well-tested before
+    upload and has a low overall risk of regression, but it's important
+    to make the effort to think about what ''could'' happen in the
+    event of a regression.
  
-  * This both shows the SRU team that the risks have been considered,
-and provides guidance to testers in regression-testing the SRU.
+  * This both shows the SRU team that the risks have been considered,
+    and provides guidance to testers in regression-testing the SRU.
  
  [Other Info]
-  
-  * Anything else you think is useful to include
-  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
-  * and address these questions in advance
+ 
+  * Anything else you think is useful to include
+  * Anticipate questions from users, SRU, +1 maintenance, security teams and 
the Technical Board
+  * and address these questions in advance
  
  [Original Description]
  I'm preemptively filing this bug in case this isn't uploaded before the 
feature freeze.
  
  We would like to include a cloud_id/$name parameter to the user-agent
  string that is sent to https://motd.ubuntu.com. This will allow the
  server part of motd.ubuntu.com to serve cloud-specific content if one is
  available.
  
  There is an MP for this already at
  https://code.launchpad.net/~ahasenack/ubuntu/+source/base-files/+git
  /base-files/+merge/371370

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

Title:
  Include cloud-id in 

[Touch-packages] [Bug 1845810] Re: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise floor

2019-09-30 Thread Robie Basak
Oh, I didn't notice that apport sent this to alsa-driver. Reassigning
since I believe this to be a kernel regression.

** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu)

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

Title:
  [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] High noise
  floor

Status in linux package in Ubuntu:
  New

Bug description:
  Since linux-image-4.15.0-60-generic 4.15.0-60.67, the background noise
  in my headphones has increased to unreasonable levels. In linux-
  image-4.15.0-58-generic 4.15.0-58.64 and previous kernels the noise
  was present but at a bearable level, which I had always assumed was a
  hardware design issue. Now, with the increased noise floor, the
  headphone socket is essentially unusable.

  This is a regression in a stable release (Bionic). The problem
  consistently reproduces as follows:

  OK: linux-image-4.15.0-58-generic 4.15.0-58.64
  BAD: linux-image-4.15.0-60-generic4.15.0-60.67
  BAD: linux-image-4.15.0-62-generic4.15.0-62.69
  BAD: linux-image-4.15.0-64-generic4.15.0-64.73

  Steps to reproduce:

  Hardware: Dell XPS 9360 (shipped with Ubuntu). I'm using a manually
  reinstalled Ubuntu Bionic, not the OEM installation. Mostly everything
  is on defaults.

  1. Boot with no headphones connected
  2. Log in
  3. Plug the headphones in

  Expected: normal noise level
  Actual: very high noise level. Playback does work correctly but the SnR is 
terrible.

  The "Select Audio Device" prompt appears, but the noise problem is
  present before I make a selection. If I select Headphones or Headset
  (I'm using a headset) then the noise remains after a brief (~0.5s)
  interruption. If I select Microphone then the noise goes, but then the
  audio comes through the speakers and not the headset as required.

  I have tried messing with alsamixer but haven't found anything to
  explain or reduce the noise. Switching to a previous kernel fixes the
  problem immediately with no settings change required.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18
  Uname: Linux 4.15.0-64-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  robie  2126 F pulseaudio
robie  3648 F alsamixer
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Sep 28 23:51:05 2019
  InstallationDate: Installed on 2017-05-11 (870 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170507)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 13 9360, Realtek ALC3246, Black Headphone Out, Front] Background 
noise or low volume
  UpgradeStatus: Upgraded to bionic on 2018-07-28 (427 days ago)
  dmi.bios.date: 03/14/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.11.0
  dmi.board.name: 00GCYR
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr2.11.0:bd03/14/2019:svnDellInc.:pnXPS139360:pvr:rvnDellInc.:rn00GCYR:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9360
  dmi.sys.vendor: Dell Inc.

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

-- 
Mailing list: https://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 1283610] Re: indicator-datetime-service crashed with SIGABRT in g_assertion_message()

2019-09-30 Thread Ars Ivci
Clock disappeared from panel. Everything else is OK

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

Title:
  indicator-datetime-service crashed with SIGABRT in
  g_assertion_message()

Status in Indicator Date and Time:
  Fix Released
Status in indicator-datetime package in Ubuntu:
  Fix Released

Bug description:
  Upgraded from 13.10 to 14.04 alpha 1 via update manager -d.  This
  popped up after reboot and subsequent login.

  ProblemType: Crash
  DistroRelease: Ubuntu 14.04
  Package: indicator-datetime 13.10.0+14.04.20140219.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-11.31-generic 3.13.3
  Uname: Linux 3.13.0-11-generic i686
  NonfreeKernelModules: nvidia wl
  ApportVersion: 2.13.2-0ubuntu5
  Architecture: i386
  CrashCounter: 1
  CurrentDesktop: Unity
  Date: Sat Feb 22 16:52:41 2014
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  InstallationDate: Installed on 2013-09-14 (161 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-datetime/indicator-datetime-service
  ProcEnviron:
   PATH=(custom, user)
   LANGUAGE=en_US
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6
  SourcePackage: indicator-datetime
  StacktraceTop:
   g_assertion_message () from /lib/i386-linux-gnu/libglib-2.0.so.0
   g_assertion_message_expr () from /lib/i386-linux-gnu/libglib-2.0.so.0
   ?? ()
   
unity::indicator::datetime::PlannerEds::Impl::on_source_enabled(_ESourceRegistry*,
 _ESource*, void*) ()
   g_cclosure_marshal_VOID__OBJECTv () from 
/usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-datetime-service crashed with SIGABRT in 
g_assertion_message()
  UpgradeStatus: Upgraded to trusty on 2014-02-23 (0 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-datetime/+bug/1283610/+subscriptions

-- 
Mailing list: https://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 1845950] [NEW] Bug reporting doesn't work upon a crash

2019-09-30 Thread Dean Henrichsmeyer
Public bug reported:

On eoan, after an initial startup / login, if an application crashes and
I click "report", I get a prompt saying the crash is reported and to
check the web page open in the browser to see if I have any additional
information.. except it never opens a page. The dialog just disappears,
the crash log stays in /var/crash and nothing happens.

The only way to actually file it is to run ubuntu-bug  which does
work as expected.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apport 2.20.11-0ubuntu7
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog:
 ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: called for pid 3409, signal 
6, core limit 0, dump mode 1
 ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
 ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: debug: session gdbus call: 
(true,)
 
 ERROR: apport (pid 3941) Mon Sep 30 07:28:15 2019: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CrashReports:
 640:1000:117:2696160:2019-09-26 13:17:54.338476419 -0500:2019-09-26 
13:17:55.338476419 -0500:/var/crash/_opt_google_chrome_chrome.1000.crash
 640:1000:117:2499555:2019-09-30 07:28:32.538634538 -0500:2019-09-30 
07:28:33.538634538 -0500:/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 30 07:34:38 2019
InstallationDate: Installed on 2018-07-24 (432 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2019-07-19 (72 days ago)

** Affects: apport (Ubuntu)
 Importance: High
 Status: New


** Tags: amd64 apport-bug eoan

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

Title:
  Bug reporting doesn't work upon a crash

Status in apport package in Ubuntu:
  New

Bug description:
  On eoan, after an initial startup / login, if an application crashes
  and I click "report", I get a prompt saying the crash is reported and
  to check the web page open in the browser to see if I have any
  additional information.. except it never opens a page. The dialog just
  disappears, the crash log stays in /var/crash and nothing happens.

  The only way to actually file it is to run ubuntu-bug  which does
  work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: called for pid 3409, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3941) Mon Sep 30 07:28:15 2019: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:2696160:2019-09-26 13:17:54.338476419 -0500:2019-09-26 
13:17:55.338476419 -0500:/var/crash/_opt_google_chrome_chrome.1000.crash
   640:1000:117:2499555:2019-09-30 07:28:32.538634538 -0500:2019-09-30 
07:28:33.538634538 -0500:/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 30 07:34:38 2019
  InstallationDate: Installed on 2018-07-24 (432 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (72 days ago)

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

-- 
Mailing list: https://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

2019-09-30 Thread Balint Reczey
@ddstreet True, but it ran fine when running the test locally with standard lxd 
virt on amd64, so I did not want to skip it on all containers.
I'll be happy to merge it away when the Salsa PR lands in Debian and gets 
merged to Ubuntu.

-- 
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 1792167] Re: Display size detected incorrectly

2019-09-30 Thread Dark Dragon
How can I check if the hardware is really sending faulty data or if it
is just incorrectly parsed?

** Also affects: xrandr (Ubuntu)
   Importance: Undecided
   Status: New

-- 
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
Status in xrandr package in Ubuntu:
  New

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 1845909] Re: IPv6 link local address is assigned even when LinkLocalAddressing=no|ipv4

2019-09-30 Thread Zhang Youfu
Emm, I think the issue I referenced above is an incorrect one.

https://github.com/systemd/systemd/issues/9890
&
https://github.com/systemd/systemd/pull/11423

I think `debian/patches/networkd-honour-LinkLocalAddressing.patch` might
be an incorrect backport of this upstream bug.

** Bug watch added: github.com/systemd/systemd/issues #9890
   https://github.com/systemd/systemd/issues/9890

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

Title:
  IPv6 link local address is assigned even when
  LinkLocalAddressing=no|ipv4

Status in systemd package in Ubuntu:
  New

Bug description:
  upstream issue: https://github.com/systemd/systemd/issues/12886
  upstream patch: https://github.com/systemd/systemd/pull/13565

  The upstream fix will be available in systemd 244.
  Backport please. Thanks.

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

-- 
Mailing list: https://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 1844902] Re: Pulseaudio broken after update

2019-09-30 Thread Daniel van Vugt
Thanks. I think the relevant update was:

Start-Date: 2019-09-21  17:34:40
Commandline: apt install paprefs
Requested-By: david (1000)
Install: gnome-icon-theme:amd64 (3.12.0-1ubuntu3, automatic), paprefs:amd64 
(0.9.10-2), pulseaudio-module-zeroconf:amd64 (1:8.0-0ubuntu3.10, automatic), 
libglademm-2.4-1v5:amd64 (2.6.7-5, automatic), libgtkmm-2.4-1v5:amd64 
(1:2.24.4-2, automatic), pulseaudio-module-gconf:amd64 (1:8.0-0ubuntu3.10, 
automatic), libgconfmm-2.6-1v5:amd64 (2.28.3-0ubuntu3, automatic)
End-Date: 2019-09-21  17:34:48

That wasn't a system update really. It looks like you installed
something like 'paprefs' manually, which might then automatically
install 'pulseaudio-module-gconf' and 'pulseaudio-module-zeroconf'.

I don't really know if any of those are broken or just not configured
correctly, but it sounds like you just need to uninstall them:

  sudo apt remove paprefs pulseaudio-module-zeroconf pulseaudio-module-
gconf

or something like that.

** Summary changed:

- Pulseaudio broken after update
+ Pulseaudio broken after installing 'paprefs'

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

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

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

Title:
  Pulseaudio broken after installing 'paprefs'

Status in paprefs package in Ubuntu:
  New

Bug description:
  after the update on 21/9/19 of pulseaudio to 1:8.0-0ubuntu3.10 I get
  no sound and when killing the demon it restarts with the following
  error - [pulseaudio] main.c: pa_pid_file_create() failed.  Reboot does
  not restore sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.10
  ProcVersionSignature: Ubuntu 4.4.0-157.185-generic 4.4.181
  Uname: Linux 4.4.0-157-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1745 F pulseaudio
   /dev/snd/controlC0:  david  1745 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep 22 11:05:48 2019
  InstallationDate: Installed on 2017-01-03 (991 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: GKPPT10H.86A.0036.2012.1213.1503
  dmi.board.name: DCP847SKE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G80890-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrGKPPT10H.86A.0036.2012.1213.1503:bd12/13/2012:svn:pn:pvr:rvnIntelCorporation:rnDCP847SKE:rvrG80890-102:cvn:ct3:cvr:

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

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


Re: [Touch-packages] [Bug 1844902] Re: Pulseaudio broken after update

2019-09-30 Thread David Wise
Hi Daniel - see attached

Cheers


*Your reason and your passion are the rudder and the sails of your
seafaring soul.*
*Kahlil Gibran*


On Mon, Sep 30, 2019 at 6:36 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> That's strange -- version 1:8.0-0ubuntu3.10 was actually released last
> year on 2018-05-03. So if you're experiencing a new problem then maybe
> pulseaudio is not the cause.
>
> Please attach the file:
>
>   /var/log/apt/history.log
>
> so we can find out...
>
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1844902
>
> Title:
>   Pulseaudio broken after update
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   after the update on 21/9/19 of pulseaudio to 1:8.0-0ubuntu3.10 I get
>   no sound and when killing the demon it restarts with the following
>   error - [pulseaudio] main.c: pa_pid_file_create() failed.  Reboot does
>   not restore sound.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: pulseaudio 1:8.0-0ubuntu3.10
>   ProcVersionSignature: Ubuntu 4.4.0-157.185-generic 4.4.181
>   Uname: Linux 4.4.0-157-generic x86_64
>   ApportVersion: 2.20.1-0ubuntu2.19
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  david  1745 F pulseaudio
>/dev/snd/controlC0:  david  1745 F pulseaudio
>   CurrentDesktop: Unity
>   Date: Sun Sep 22 11:05:48 2019
>   InstallationDate: Installed on 2017-01-03 (991 days ago)
>   InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64
> (20160420.1)
>   ProcEnviron:
>LANGUAGE=en_AU:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=en_AU.UTF-8
>SHELL=/bin/bash
>   SourcePackage: pulseaudio
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/13/2012
>   dmi.bios.vendor: Intel Corp.
>   dmi.bios.version: GKPPT10H.86A.0036.2012.1213.1503
>   dmi.board.name: DCP847SKE
>   dmi.board.vendor: Intel Corporation
>   dmi.board.version: G80890-102
>   dmi.chassis.type: 3
>   dmi.modalias:
> dmi:bvnIntelCorp.:bvrGKPPT10H.86A.0036.2012.1213.1503:bd12/13/2012:svn:pn:pvr:rvnIntelCorporation:rnDCP847SKE:rvrG80890-102:cvn:ct3:cvr:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1844902/+subscriptions
>


** Attachment added: "history.log"
   
https://bugs.launchpad.net/bugs/1844902/+attachment/5292730/+files/history.log

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

Title:
  Pulseaudio broken after update

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  after the update on 21/9/19 of pulseaudio to 1:8.0-0ubuntu3.10 I get
  no sound and when killing the demon it restarts with the following
  error - [pulseaudio] main.c: pa_pid_file_create() failed.  Reboot does
  not restore sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.10
  ProcVersionSignature: Ubuntu 4.4.0-157.185-generic 4.4.181
  Uname: Linux 4.4.0-157-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1745 F pulseaudio
   /dev/snd/controlC0:  david  1745 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep 22 11:05:48 2019
  InstallationDate: Installed on 2017-01-03 (991 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: GKPPT10H.86A.0036.2012.1213.1503
  dmi.board.name: DCP847SKE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G80890-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrGKPPT10H.86A.0036.2012.1213.1503:bd12/13/2012:svn:pn:pvr:rvnIntelCorporation:rnDCP847SKE:rvrG80890-102:cvn:ct3:cvr:

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

-- 
Mailing list: https://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 1844609] Re: my screen flickering

2019-09-30 Thread Daniel van Vugt
Yes the kernel log (CurrentDmesg.txt) suggests a disk is faulty so you
should replace that before doing anything else...

Then if the screen flickering persists please attach a video of the
problem here so we can better understand what you mean.

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

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

Title:
  my screen flickering

Status in Ubuntu:
  Incomplete

Bug description:
  my screen flickering

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-145.171-generic 4.4.176
  Uname: Linux 4.4.0-145-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Thu Sep 19 08:21:46 2019
  DistUpgraded: 2019-04-13 18:00:45,594 ERROR found exception: 'E:Sub-process 
/usr/bin/dpkg returned an error code (1), E:Sub-process /usr/bin/dpkg returned 
an error code (1)'
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.135, 4.4.0-142-generic, i686: installed
   nvidia-304, 304.135, 4.4.0-145-generic, i686: installed
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:0651]
  InstallationDate: Installed on 2016-08-30 (1114 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release i386 (20140417)
  MachineType: Dell Inc. Inspiron 3542
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-145-generic 
root=UUID=bde73db5-64dd-43a8-ae3d-32ce5c3ed7d4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2019-04-13 (158 days ago)
  dmi.bios.date: 05/27/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0KHNVP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd05/27/2014:svnDellInc.:pnInspiron3542:pvrNotSpecified:rvnDellInc.:rn0KHNVP:rvrA03:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 3542
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Sep 19 07:39:29 2019
  xserver.configfile: default
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   16620 
   vendor AUO
  xserver.version: 2:1.18.4-0ubuntu0.8

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

-- 
Mailing list: https://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 1833193] Re: systemd-networkd fails to apply static IPv4 when the static IP is the same as previously configured by DHCP

2019-09-30 Thread Lars Erik Pedersen
Repro instructions:
- (Enable systemd-networkd debug logging)
- Start a server with its interface configured with DHCP
- In the netplan config, configure the interface wtih static addressing, using 
the exact same address as it already has gotten from DHCP
- Either wait for the initial DHCP lease time to expire, and observe that the 
interface loses its address; OR observe in the debug log that networkd applied 
the address with a lease time, even though you told netplan to use static 
addressing

Networkd config with static addressing:
cat /run/systemd/network/10-netplan-ens3.network 
[Match]
MACAddress=

[Network]
LinkLocalAddressing=ipv6
Address=10.212.132.107/24
Gateway=10.212.132.1
DNS=8.8.8.8
DNS=8.8.4.4
Domains=

Networkd config with DHCP:
cat /run/systemd/network/10-netplan-ens3.network
[Match]
MACAddress=
[Network]
DHCP=ipv4
LinkLocalAddressing=ipv6

[DHCP]
RouteMetric=100
UseMTU=true

Debug log output from systemd-networkd when netplan tells it to apply static 
addressing when the interface already has an address from DHCP:
Sep 30 10:36:15 nettest1 systemd[1]: Stopped Network Service.
Sep 30 10:36:16 nettest1 systemd[1]: Starting Network Service...

Sep 30 10:36:16 nettest1 systemd-networkd[6086]: ens3: Adding address: 
10.212.132.107/24 (valid for 11h 52min 55s)

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

Title:
  systemd-networkd fails to apply static IPv4 when the static IP is the
  same as previously configured by DHCP

Status in systemd package in Ubuntu:
  New

Bug description:
  In bionic, running systemd 237-3ubuntu10.22 and netplan.io
  0.97-0ubuntu1~18.04.1, systemd-networkd fails to configure an
  interface with a static IPv4 address if the statically confiugred
  address is the same as the interface already has gotten from DHCP.

  This will cause the interface to loose its IP address when the DHCP
  lease exires, even though you've told netplan to configure it as
  static.

  I expect systemd-networkd to actually configure an IP address as
  static, regardless of what address the interface has before from DHCP.

  # lsb_release  -rd
  Description:  Ubuntu 18.04.2 LTS
  Release:  18.04

  # apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.22

  # apt-cache policy netplan.io
  netplan.io:
Installed: 0.97-0ubuntu1~18.04.1

  A paste of systemd-networkd's debug log when I run "netplan apply" and
  the interface already has the static IP configured from DHCP.

  It seems like upon a restart, systemd-networkd will allways add
  whatever IP config it had before the service stopped, and then apply
  changes (if any). Since my new config has the same IP as it already
  had, it does nothing even though the new config has static
  configuration.

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

-- 
Mailing list: https://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 1844860] Re: Freezing system

2019-09-30 Thread Daniel van Vugt
The kernel log suggests the nouveau kernel driver is having trouble:

[ 5703.539644] nouveau :00:0d.0: bus: MMIO write of 052a0001 FAULT at 00b000
[ 5704.875835] nouveau :00:0d.0: bus: MMIO write of 05270001 FAULT at 00b010
[ 5705.738769] nouveau :00:0d.0: bus: MMIO write of 05270001 FAULT at 00b010
[ 5705.740773] nouveau :00:0d.0: bus: MMIO write of 05270001 FAULT at 00b010
[ 5712.157743] rfkill: input handler disabled
[ 5713.532579] nouveau :00:0d.0: bus: MMIO write of 08c70001 FAULT at 00b020
[ 5723.226473] nouveau :00:0d.0: bus: MMIO write of 0a4c0001 FAULT at 00b030
[ 5723.241081] nouveau :00:0d.0: bus: MMIO write of  FAULT at 00b030
[ 5763.349926] nouveau :00:0d.0: bus: MMIO write of 0c450001 FAULT at 00b030
[ 5767.257346] nouveau :00:0d.0: bus: MMIO write of  FAULT at 00b030
[ 5860.400801] nouveau :00:0d.0: bus: MMIO write of 0a4e0001 FAULT at 00b030
[ 5860.462603] nouveau :00:0d.0: bus: MMIO write of  FAULT at 00b030
[ 5877.109887] nouveau :00:0d.0: bus: MMIO write of 0a4e0001 FAULT at 00b030
[ 5877.130526] nouveau :00:0d.0: bus: MMIO write of  FAULT at 00b030

To verify if that is the main problem, please try installing the
proprietary Nvidia driver instead via:

  Software & Updates > Additional Drivers > ...


** Tags added: nouveau

** Summary changed:

- Freezing system
+ [nouveau] Freezing system

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  [nouveau] Freezing system

Status in Ubuntu:
  Incomplete

Bug description:
  The system getting frozen suddenly, no-longer peripheral material
  access (keyb, mouse etc..). Seems correlated with theFirefox navigator
  use.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-29.31~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompositorRunning: None
  Date: Sat Sep 21 13:08:30 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] C61 [GeForce 6150SE nForce 430] 
[1025:0394]
  InstallationDate: Installed on 2019-08-03 (48 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 04f9:0027 Brother Industries, Ltd HL-2030 Laser 
Printer
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: eMachines EL1358
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-29-generic 
root=UUID=52e5db54-2ea1-48ba-9efe-6b23d1188404 ro
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/20/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-B1
  dmi.board.name: EL1358
  dmi.board.vendor: eMachines
  dmi.chassis.type: 3
  dmi.chassis.vendor: eMachines
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/20/2011:svneMachines:pnEL1358:pvr:rvneMachines:rnEL1358:rvr:cvneMachines:ct3:cvr:
  dmi.product.family: eMachines Desktop
  dmi.product.name: EL1358
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.sys.vendor: eMachines
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

-- 
Mailing list: https://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 1844902] Re: Pulseaudio broken after update

2019-09-30 Thread Daniel van Vugt
That's strange -- version 1:8.0-0ubuntu3.10 was actually released last
year on 2018-05-03. So if you're experiencing a new problem then maybe
pulseaudio is not the cause.

Please attach the file:

  /var/log/apt/history.log

so we can find out...


** Changed in: pulseaudio (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/1844902

Title:
  Pulseaudio broken after update

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  after the update on 21/9/19 of pulseaudio to 1:8.0-0ubuntu3.10 I get
  no sound and when killing the demon it restarts with the following
  error - [pulseaudio] main.c: pa_pid_file_create() failed.  Reboot does
  not restore sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.10
  ProcVersionSignature: Ubuntu 4.4.0-157.185-generic 4.4.181
  Uname: Linux 4.4.0-157-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.19
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  david  1745 F pulseaudio
   /dev/snd/controlC0:  david  1745 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep 22 11:05:48 2019
  InstallationDate: Installed on 2017-01-03 (991 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   LANGUAGE=en_AU:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/13/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: GKPPT10H.86A.0036.2012.1213.1503
  dmi.board.name: DCP847SKE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G80890-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrGKPPT10H.86A.0036.2012.1213.1503:bd12/13/2012:svn:pn:pvr:rvnIntelCorporation:rnDCP847SKE:rvrG80890-102:cvn:ct3:cvr:

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

-- 
Mailing list: https://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 1842284] Re: initramfs does not copy ehci-platform

2019-09-30 Thread Launchpad Bug Tracker
This bug was fixed in the package initramfs-tools - 0.122ubuntu8.15

---
initramfs-tools (0.122ubuntu8.15) xenial; urgency=medium

  * hook-functions: include ehci-platform from HWE kernel.
(LP: #1842284)

 -- Ike Panhc   Wed, 04 Sep 2019 15:24:58 +0800

** Changed in: initramfs-tools (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  initramfs does not copy ehci-platform

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  If you install Ubuntu onto USB storage behind a Platform USB host controller, 
it will not be able to boot because the generated initramfs will not include 
the host controller driver.

  [Test Case]
  Install to a USB stick attached to platform USB controller and reboot. 
Booting will fail because it will be unable to find the root file system.

  [Regression Risk]
  Driver is only loaded when system requires ehci-platform, minimizing the 
impact to all other systems.

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

-- 
Mailing list: https://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 1842284] Update Released

2019-09-30 Thread Łukasz Zemczak
The verification of the Stable Release Update for initramfs-tools has
completed successfully and the package is now being released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  initramfs does not copy ehci-platform

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in initramfs-tools source package in Xenial:
  Fix Committed
Status in initramfs-tools source package in Bionic:
  Fix Released
Status in initramfs-tools source package in Disco:
  Fix Released
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  If you install Ubuntu onto USB storage behind a Platform USB host controller, 
it will not be able to boot because the generated initramfs will not include 
the host controller driver.

  [Test Case]
  Install to a USB stick attached to platform USB controller and reboot. 
Booting will fail because it will be unable to find the root file system.

  [Regression Risk]
  Driver is only loaded when system requires ehci-platform, minimizing the 
impact to all other systems.

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

-- 
Mailing list: https://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 1832421] Re: openssl reboot needed message using incorrect path to X server

2019-09-30 Thread Launchpad Bug Tracker
This bug was fixed in the package openssl - 1.1.1b-1ubuntu2.4

---
openssl (1.1.1b-1ubuntu2.4) disco; urgency=medium

  * Import libraries/restart-without-asking as used in postinst, to
prevent failure to configure the package without debconf database.
LP: #1832919

 -- Dimitri John Ledkov   Thu, 20 Jun 2019 18:31:25
+0100

** Changed in: openssl (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  openssl reboot needed message using incorrect path to X server

Status in openssl package in Ubuntu:
  Fix Released
Status in openssl source package in Bionic:
  Fix Released
Status in openssl source package in Cosmic:
  Fix Committed
Status in openssl source package in Disco:
  Fix Released
Status in openssl source package in Eoan:
  Fix Released

Bug description:
  [Impact]

   * On desktop, upgrading libssl1.1 does not show reboot required
  notification

  [Test Case]

   * Boot ubuntu desktop
   * Upgrade libssl1.1
   * Observe reboot notification pop-up from update-notifier is _not_ shown

  [Regression Potential]

   * Tweaking postinst only to correct for the Xorg path. Current code
  is innert, but is well excercised in prior releases.

  [Other Info]

   * Original bug report:

  Hello, the openssl library postinst file is using pidof /usr/bin/X,
  but that doesn't appear to be the path to the X11 server any more:

  debian/libssl1.1.postinst:

  # Only issue the reboot notification for servers; we proxy this by
  # testing that the X server is not running (LP: #244250)
  if ! pidof /usr/bin/X > /dev/null && [ -x 
/usr/share/update-notifier/notify-reboot-required ]; then
  /usr/share/update-notifier/notify-reboot-required
  fi

  On my 18.04 LTS laptop:

  $ ps auxw | grep Xorg
  root  2440  0.5  0.4 495932 78996 tty7 Rsl+ May10 264:45 
/usr/lib/xorg/Xorg :0 vt7 -nolisten tcp -auth /var/l

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openssl 1.1.1-1ubuntu2.1~18.04.1
  ProcVersionSignature: Ubuntu 4.15.0-50.54-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  Date: Tue Jun 11 18:06:51 2019
  InstallationDate: Installed on 2012-10-18 (2427 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120823.1)
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: openssl
  UpgradeStatus: Upgraded to bionic on 2018-05-02 (406 days ago)

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

-- 
Mailing list: https://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 1772512] Re: Unable to install i386 and amd64 arch at the same time

2019-09-30 Thread Timo Aaltonen
https://bugs.launchpad.net/ubuntu/+source/libxkbcommon/+bug/1772512/comments/6

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

Title:
  Unable to install i386 and amd64 arch at the same time

Status in libxkbcommon package in Ubuntu:
  Fix Released
Status in libxkbcommon source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  libxkbcommon-dev:i386/amd64 can't be installed at the same time, because the 
package isn't properly multi-archified in bionic

  [Test case]
  apt install libxkbcommon-dev:i386 libxkbcommon-dev:amd64

  should succeed

  [Regression potential]
  not really

  
  --

  Not sure if this is intended, but it's not possible to install two
  architectures of the libxkbcommon-dev at the same time. On Ubuntu
  16.04 and 18.04 apt-get says that they are in conflict.

  The package is a dependency for libegl1-mesa-dev, which I need to have
  installed in 64 and 32-bit variants.

  Please see the example output below:

  $ lsb_release --all
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04 LTS
  Release:  18.04
  Codename: bionic

  $ sudo apt-get install libxkbcommon-dev:*
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libxkbcommon-dev : Conflicts: libxkbcommon-dev:i386 but 0.8.0-1 is to be 
installed
   libxkbcommon-dev:i386 : Conflicts: libxkbcommon-dev but 0.8.0-1 is to be 
installed
  E: Unable to correct problems, you have held broken packages.

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

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


  1   2   >