[Touch-packages] [Bug 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)

[linux_joy]

See https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1767568/comments/33 :
> (..) I have noticed that the /etc/kbd/config is present on 16.04, I believe 
> it was missing on 18.04. (...)

Please, can someone tell me: Why was /etc/kbd/config (and also
/etc/kbd/remap) removed on kbd package Version 2.0.4-2ubuntu1 in bionic?
If it had been left, the console could still blank and powerdown (DPMS)!

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

Title:
  Ubuntu server enables screenblanking, concealing crashdumps (DPMS is
  not used)

Status in kbd package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in kbd source package in Zesty:
  Invalid
Status in linux source package in Zesty:
  Fix Released
Status in kbd package in Debian:
  Fix Released

Bug description:
  James Rice of Jump Networks noticed that there is a screen-blanker
  enabled on Ubuntu Server.

  James notes that this blanking is not enabling DPMS power saving
  (thereby negating any power-saving benefit), and is simply turning the
  screen content blank.   This means that the crash output is invisible
  which is unhelpful on a server (virtual or otherwise).

  Ideally the screen should (at a minimum) be turned on and unblanked at
  the point of an OOPs/crash being printed.

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

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

[Touch-packages] [Bug 1831252] Re: panic=-1 is completely ignored by the initrd causing unexpected behaviour

[Tiago Stürmer Daitx]

I tested the initramfs-tools in xenial-proposed, bionic-proposed, and 
disco-proposed with all 3 testcases (panic=-1, panic=10, and no panic), 
everything worked as expected:
- panic=-1 rebooted instantly after the root partition is not found
- panic=10 rebooted after 10 seconds
- no "panic" entry caused to drop into a basic shell

ii  initramfs-tools  0.122ubuntu8.16  all  generic modular initramfs generator 
(automation)
ii  initramfs-tools  0.130ubuntu3.9   all  generic modular initramfs generator 
(automation)
ii  initramfs-tools  0.131ubuntu19.2  all  generic modular initramfs generator 
(automation)


multipass@xenial:~$ apt-cache policy initramfs-tools
initramfs-tools:
  Installed: 0.122ubuntu8.16
  Candidate: 0.122ubuntu8.16
  Version table:
 *** 0.122ubuntu8.16 400
400 http://archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 0.122ubuntu8.15 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
 0.122ubuntu8.14 500
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
 0.122ubuntu8 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages


multipass@bionic:~$ apt-cache policy initramfs-tools
initramfs-tools:
  Installed: 0.130ubuntu3.9
  Candidate: 0.130ubuntu3.9
  Version table:
 *** 0.130ubuntu3.9 400
400 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 0.130ubuntu3.8 500
500 http://archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages
 0.130ubuntu3.6 500
500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
 0.130ubuntu3 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages


multipass@disco:~$ apt-cache policy initramfs-tools
initramfs-tools:
  Installed: 0.131ubuntu19.2
  Candidate: 0.131ubuntu19.2
  Version table:
 *** 0.131ubuntu19.2 400
400 http://archive.ubuntu.com/ubuntu disco-proposed/main amd64 Packages
100 /var/lib/dpkg/status
 0.131ubuntu19.1 500
500 http://archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
 0.131ubuntu19 500
500 http://archive.ubuntu.com/ubuntu disco/main amd64 Packages

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

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

Title:
  panic=-1 is completely ignored by the initrd causing unexpected
  behaviour

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 Committed
Status in initramfs-tools source package in Disco:
  Fix Committed
Status in initramfs-tools source package in Eoan:
  Fix Released

Bug description:
  [Impact]
  in Ubuntu Core we default to using panic=-1 on the kernel command line 
(documented at [1]) to speed up the auto-rollback mechanism of the kernel. on a 
kernel level this works just fine and the system reboots immediately ...

  when in the initramfs during boot and a panic occurs, no reboot
  happens at all, the initrd spawns a shell regardless of the panic=
  value ...

  
  [Test case]

  Before booting change root=$foo to root=x$foo - this will make it
  panic. Then test that

  1) "panic=-1" causes an immediate reboot
  2) "panic=5" waits 5 seconds
  3) no "panic" drops you to a shell

  [Regression potential]
  This adds some very specific checks for -1 in places that use ${panic}, as 
such the regression potential is somewhat limited. If there were a regression, 
it could be a syntax error (causing boot to fail) or a sleep not working 
correctly (causing sleep to, well, not sleep) - but that's unrealistic.

  
  [Other info]
  this is caused by a filter in  /usr/share/initramfs-tools/init

  panic=*)
  panic="${x#panic=}"
  case ${panic} in
  *[![:digit:].]*)
  panic=
  ;;
  esac
  ;;

  this function only lets positive values through, else panic= simply
  gets unset

  the panic() function itself is also not capable of handling negative
  values, it has a sleep call that interprets negative values as
  commandline options instead of simply ignoring a negative sleep time
  [2] (line 11).

  the filter in the init script should allow the -1 value (to comply
  with the kernel documentation and behaviour) and the panic() function
  should properly skip the sleep call when a negative value for panic=
  is set.

  [1] 

[Touch-packages] [Bug 1841296] Re: Update to 2.4.3

[Bug Watch Updater]

** Changed in: libshout (Debian)
   Status: New => Fix Released

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

Title:
  Update to 2.4.3

Status in libshout package in Ubuntu:
  Triaged
Status in libshout package in Debian:
  Fix Released

Bug description:
  The new version includes new features

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

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

[Touch-packages] [Bug 938751] Re: Images are washed out or colors are skewed in some apps

[jon grahaqm]

** Changed in: chromium-browser (Ubuntu)
 Assignee: (unassigned) => jon grahaqm (skyking2630)

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

Title:
  Images are washed out or colors are skewed in some apps

Status in Eye of GNOME:
  New
Status in chromium-browser package in Ubuntu:
  Confirmed
Status in colord package in Ubuntu:
  Confirmed
Status in eog package in Ubuntu:
  Confirmed

Bug description:
  Images are washed out or colors are skewed in some apps, notably
  Chrome/Chromium and Image Viewer (eog).

  Workaround:

  Settings > Devices > Colour >
  and disable or remove your monitor's colour profile

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

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

[Touch-packages] [Bug 1827498] Re: Geoclue 2 very high memory usage

[Andrew Gaul]

Oddly my system reports 2.5.5 installed but 2.5.3 active:

$ /usr/libexec/geoclue --version
2.5.3

It appears 2.5.4 and 2.5.5 address some memory leaks:

https://gitlab.freedesktop.org/geoclue/geoclue/issues/120

** Bug watch added: gitlab.freedesktop.org/geoclue/geoclue/issues #120
   https://gitlab.freedesktop.org/geoclue/geoclue/issues/120

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

Title:
  Geoclue 2 very high memory usage

Status in geoclue package in Ubuntu:
  Confirmed

Bug description:
  After geoclue 2 running at high CPU for some minutes I found CPU usage
  had dropped to zero but geoclue was still hogging a whopping 11GB of
  memory (the PC has 16GB). I stopped the geoclue service to recover the
  memory.

  Kubuntu 18.04

  $ apt-cache policy geoclue-2.0
  geoclue-2.0:
Installed: 2.4.7-1ubuntu1
Candidate: 2.4.7-1ubuntu1
Version table:
   *** 2.4.7-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Happy to provide other info on request.

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

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

[Touch-packages] [Bug 1850874] Re: gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just to update the screen

[TomaszChmielewski]

There is one more change I did after upgrading from 19.04 to 19.10.

This is a KVM VM - and for some reason, the GUI (X) sometimes freezes
after the VM is paused/saved/resumed, while SSH still works (this was
also before 19.10 and behaviour did not improve in 19.10).


I've changed to Wayland to see if it this kind of freezing happens there as 
well (so far, it doesn't).


High CPU usage on all cores happens with Wayland only. I've just checked, it 
doesn't happen with regular X; CPU usage is normal/low there.

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

Title:
  gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU
  cores just to update the screen

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

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1827498] Re: Geoclue 2 very high memory usage

[Andrew Gaul]

Using Fedora 31 with geoclue2-2.5.5-1.fc31 I also see an RSS of over 3
GB.  gnome-shell is using almost as much; perhaps these are related?

USER PID %CPU %MEMVSZ   RSS TTY  STAT START   TIME COMMAND
geoclue 1520  0.3 19.3 7513496 3139312 ? Ssl  Oct03 129:56 
/usr/libexec/geoclue
gaul1850  1.8 15.5 5809552 2533988 ? Ssl  Oct03 766:09 
/usr/bin/gnome-shell

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

Title:
  Geoclue 2 very high memory usage

Status in geoclue package in Ubuntu:
  Confirmed

Bug description:
  After geoclue 2 running at high CPU for some minutes I found CPU usage
  had dropped to zero but geoclue was still hogging a whopping 11GB of
  memory (the PC has 16GB). I stopped the geoclue service to recover the
  memory.

  Kubuntu 18.04

  $ apt-cache policy geoclue-2.0
  geoclue-2.0:
Installed: 2.4.7-1ubuntu1
Candidate: 2.4.7-1ubuntu1
Version table:
   *** 2.4.7-1ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  Happy to provide other info on request.

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

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

[Touch-packages] [Bug 1850551] Re: Xorg freeze

[Steve Beattie]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I recently upgraded to ubuntu-18.04 and the screen starts to freeze
  randomly. The CPU used to gets overheated on minimal use.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-66.75-generic 4.15.18
  Uname: Linux 4.15.0-66-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 30 02:03:51 2019
  DistUpgraded: 2019-07-26 05:15:58,339 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.15.0-64-generic, x86_64: installed
   bbswitch, 0.8, 4.15.0-66-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Dell HD Graphics 620 [1028:078b]
 Subsystem: Dell Sun XT [Radeon HD 8670A/8670M/8690M / R5 M330 / M430 / R7 
M520] [1028:078b]
  InstallationDate: Installed on 2018-02-01 (635 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Inspiron 15-3567
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-66-generic 
root=UUID=bf1c9a5c-ebb8-4edf-8bde-0767ec9746b0 ro nouveau.modeset=0 
drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2019-07-25 (95 days ago)
  dmi.bios.date: 03/23/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.06.00
  dmi.board.name: 0D53F5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.06.00:bd03/23/2017:svnDellInc.:pnInspiron15-3567:pvr:rvnDellInc.:rn0D53F5:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 15-3567
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.100+git1910210630.c69c9c~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.3~git1909090730.ae5ac2~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.3~git1909090730.ae5ac2~oibaf~b
  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:19.1.0+git1910151930.b9bd80~oibaf~b
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1910071930.bff5ec~oibaf~b
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git1906080730.ec2b45~oibaf~b

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

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

[Touch-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

[RevAngel]

One question just came to my mind:

why does a power event count as a new connect or reconnect? Yes, it
shouldn't! The physical connection status normally should not change
with a power event.

Just my thoughts that might help you to figure out how to solve things.

Bye!

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

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

[Touch-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

[RevAngel]

Thank you for the workaround, Daniel!

It definitely seems to overlap with bug 1847570, the described behavior
there matches with my report, when you think about it.

So thank you for the link to the bug as well!

Bye!

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

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

[Touch-packages] [Bug 1850969] Re: x11 session all mouse or keyboard action ignored

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  x11 session all mouse or keyboard action ignored

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Starting with x1 session all mouse or keyboard action are ignored. Only mouse 
arrow moves on the desktop.
  was able to exit only with cntrl+alt+f3
  wayland session works fine.
  Also booting from USB live and selecting 'try ubuntu' has the same problem.
  selecting install the install run smoothly but the just installed system has 
the problem.

  same problem with ISO dated 20191030 20191031 20191101 and 20191021
  after update+upgrade

  corrado@corrado-p13-ff-1101:~/Desktop$ inxi -Fx
  System:Host: corrado-p13-ff-1101 Kernel: 5.3.0-18-generic x86_64 bits: 64 
compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.1 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 
  Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: 
kernel bus ID: 00:02.0 
 Display: wayland server: X.Org 1.20.5 driver: i915 resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
v: 4.5 Mesa 19.2.1 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
 bus ID: 00:1f.3 
 Sound Server: ALSA v: k5.3.0-18-generic 
  Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
  Drives:Local Storage: total: 931.51 GiB used: 4.87 GiB (0.5%) 
 ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
temp: 34 C 
  Partition: ID-1: / size: 15.62 GiB used: 4.87 GiB (31.2%) fs: ext4 dev: 
/dev/sda13 
 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 38.5 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 205 Uptime: 16m Memory: 7.49 GiB used: 1.11 GiB (14.8%) 
Init: systemd runlevel: 5 Compilers: 
 gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 
  corrado@corrado-p13-ff-1101:~/Desktop$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 18:13:53 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191101)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=062c7ec4-2948-49df-934f-d054f397e4c4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Fi

[Touch-packages] [Bug 1850775] Re: DNS info is not loaded by dhclient

[Dan Streetman]

@pengpengs can you test with the systemd versions from this ppa:
https://launchpad.net/~ddstreet/+archive/ubuntu/systemd

I suspect this might be caused by bug 1849608

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

Title:
  DNS info is not loaded by dhclient

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi Team,

  Could you please help to confirm if this is an issue on Ubuntu19.10
  Desktop?

  1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
 supersede domain-name "vmware.com";
 supersede domain-name-servers 10.117.0.1;

  2. Reboot

  3. check DNS info by "systemd-resolve --status", the DNS domain and
  server is not set. But /run/systemd/resolved.conf.d/isc-
  dhcp-v4-ens160.conf contains the new DNS domain and server.

  4. Manually run "systemctl try-reload-or-restart systemd-
  resolved.service" and then DNS is set correctly, "systemd-resolve
  --status" output have the new DNS domain and server.

  
  I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

  Thanks,
  Pengpeng

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

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

[Touch-packages] [Bug 1850823] Re: plz help mw

[Steve Beattie]

Thanks for taking the time to report this bug and helping to make Ubuntu
better. We appreciate the difficulties you are facing, but this appears
to be a "regular" (non-security) bug.  I have unmarked it as a security
issue since this bug does not show evidence of allowing attackers to
cross privilege boundaries nor directly cause loss of data/privacy.
Please feel free to report any other bugs you may find.

** Information type changed from Private Security to Public

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

Title:
  plz help mw

Status in xorg package in Ubuntu:
  New

Bug description:
  like big and big issue

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  Uname: Linux 5.3.0-19-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Oct 31 22:38:46 2019
  DistUpgraded: 2019-10-31 07:37:10,130 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: eoan
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake GT2 [HD Graphics 520] 
[103c:8329]
 Subsystem: Hewlett-Packard Company Radeon R7 M520 [103c:8329]
  InstallationDate: Installed on 2019-10-29 (2 days ago)
  InstallationMedia: Ubuntu 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 004: ID 05c8:03ac Cheng Uei Precision Industry Co., Ltd 
(Foxlink) HP TrueVision HD Camera
   Bus 001 Device 003: ID 0bda:b009 Realtek Semiconductor Corp. 802.11n WLAN 
Adapter
   Bus 001 Device 005: ID 148f:7601 Ralink Technology, Corp. MT7601U Wireless 
Adapter
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP Laptop 15-bs0xx
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-19-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to eoan on 2019-10-31 (0 days ago)
  dmi.bios.date: 05/10/2017
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.10
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8329
  dmi.board.vendor: HP
  dmi.board.version: 23.27
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.10:bd05/10/2017:svnHP:pnHPLaptop15-bs0xx:pvrType1ProductConfigId:rvnHP:rn8329:rvr23.27:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV HP Notebook
  dmi.product.name: HP Laptop 15-bs0xx
  dmi.product.sku: 2EY79PA#ACJ
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.99-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1850929] Re: python3-apport regression: missing argument in Report.add_proc_environ call

[Brian Murray]

** Tags added: regression-update

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

** Changed in: apport (Ubuntu)
   Importance: Undecided => High

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

Title:
  python3-apport regression: missing argument in Report.add_proc_environ
  call

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  This is a regression in the 2.20.9-0ubuntu7.8 security update of
  apport

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

  Reproduce the bug:

  $ python3
  Python 3.6.8 (default, Oct  7 2019, 12:59:55) 
  [GCC 8.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import apport
  >>> import os
  >>> report = apport.Report()
  >>> report.add_proc_info(os.getpid(), extraenv=['PYTHONHOME', 'PYTHONPATH'])
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/apport/report.py", line 543, in 
add_proc_info
  self.add_proc_environ(pid, extraenv)
File "/usr/lib/python3/dist-packages/apport/report.py", line 610, in 
add_proc_environ
  env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
_read_file
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
  TypeError: argument should be integer or None, not list

  Patch below:

  # diff -u  /usr/lib/python3/dist-packages/apport/report.py 
/usr/lib/python3/dist-packages/apport/report.py.new 
  --- /usr/lib/python3/dist-packages/apport/report.py   2019-11-01 
14:16:39.375968798 +0100
  +++ /usr/lib/python3/dist-packages/apport/report.py.new   2019-11-01 
14:17:58.035128006 +0100
  @@ -540,7 +540,7 @@
   self['ProcCwd'] = os.readlink('cwd', dir_fd=proc_pid_fd)
   except OSError:
   pass
  -self.add_proc_environ(pid, extraenv)
  +self.add_proc_environ(pid, proc_pid_fd, extraenv)
   self['ProcStatus'] = _read_file('status', dir_fd=proc_pid_fd)
   self['ProcCmdline'] = _read_file('cmdline', 
dir_fd=proc_pid_fd).rstrip('\0')
   self['ProcMaps'] = _read_maps(proc_pid_fd)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: python3-apport 2.20.9-0ubuntu7.8
  ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
  Uname: Linux 4.15.0-58-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  CrashReports: 640:1000:1004:35152:2019-11-01 14:00:47.150214442 
+0100:2019-11-01 14:00:47.150214442 +0100:/var/crash/_usr_bin_snimpy.1000.crash
  Date: Fri Nov  1 14:18:16 2019
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1844853] Re: IBus no longer works in Qt applications after upgrade

[Iain Lane]

I've sponsored all the SRUs now. I also backported the testcase for
bionic. On xenial the same testcase *hangs*. That is likely to be due to
some assumptions about gdbus that aren't true back then, but be sure to
verify this release extra carefully.

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

Title:
  IBus no longer works in Qt applications after upgrade

Status in GLib:
  Fix Released
Status in ibus:
  Fix Released
Status in glib2.0 package in Ubuntu:
  Fix Committed
Status in ibus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  In Progress
Status in glib2.0 source package in Bionic:
  In Progress
Status in glib2.0 source package in Disco:
  In Progress
Status in glib2.0 source package in Eoan:
  In Progress
Status in glib2.0 source package in Focal:
  Fix Committed
Status in ibus source package in Focal:
  Fix Released
Status in glib2.0 package in Debian:
  Fix Released

Bug description:
  [Impact]

  IBus was broken for Qt applications as a regression due to the fix of
  CVE-2019-14822. As a result the IBus patch was disabled temporarily,
  which fixed IBus from a usability POV.

  The real fix has been made in glib2.0, and the proposed updates in the
  below PPA will allow the IBus patch to be re-enabled.

  https://launchpad.net/~gunnarhj/+archive/ubuntu/glib2.0

  [Test Case]

   * On a standard Ubuntu {eoan,disco,bionic,xenial} installation
 - Upgrade the glib2.0 packages from
   {eoan,disco,bionic,xenial}-proposed
     - Upgrade the ibus packages from
   https://launchpad.net/~ubuntu-security-proposed/+archive/ubuntu/ppa
     - Install some IBus input method, e.g. ibus-libpinyin
     - Install some Qt application, e.g. Kate

  * Relogin (maybe reboot)

  * Add the input method to the input sources

  * Open the Qt app and try to input something using the IBus IM

  => Find that the transliteration works as expected

  [Regression Potential]

  The applicable patches origin from glib upstream:
  https://gitlab.gnome.org/GNOME/glib/merge_requests/1176
  Consequently the changes have been reviewed by the glib maintainer, but also 
tested by the IBus maintainer, by me (gunnarhj), and - of course - the author 
Simon McVittie. The changes have been in Debian unstable since 2019-10-30.

  [Original description]

  Kubuntu Release 18.04.3 LTS

  Expected behavior:
  ibus continues working as before after applying security update 
1.5.17-ubuntu5.1 from version 1.5.17-ubuntu5.

  Observed behavior:
  ibus is not usable anymore in Qt applications.

  After updating ibus and the related packages ibus-gtk, ibus-gtk3, 
libibus-1.0-5 and gir1.2-ibus-1.0 all from version 1.5.17-ubuntu5 to 
1.5.17-ubuntu5.1, I can no longer use ibus in Qt applications. Using 
shift-space no longer changes the selected input method and even when i switch 
to the mozc input method in a gtk application, i can not use it in any Qt 
applications.
  When starting qtconfig in a terminal, I also get the following message:

  Bus::open: Connect ibus failed!
  IBusInputContext::createInputContext: no connection to ibus-daemon

  This bug was not present in version 1.5.17-3ubuntu5 and I also
  confirmed that downgrading the packages to version 1.5.17-3ubuntu4
  restores ibus functionality in Qt applications.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu5.1
  ProcVersionSignature: Ubuntu 5.0.0-30.32~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-30-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 21 07:58:56 2019
  InstallationDate: Installed on 2019-06-28 (84 days ago)
  InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1850969] Re: x11 session all mouse or keyboard action ignored

[corrado venturini]

** Summary changed:

- x1 session all mouse or keyboard action ignored
+ x11 session all mouse or keyboard action ignored

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

Title:
  x11 session all mouse or keyboard action ignored

Status in xorg package in Ubuntu:
  New

Bug description:
  Starting with x1 session all mouse or keyboard action are ignored. Only mouse 
arrow moves on the desktop.
  was able to exit only with cntrl+alt+f3
  wayland session works fine.
  Also booting from USB live and selecting 'try ubuntu' has the same problem.
  selecting install the install run smoothly but the just installed system has 
the problem.

  same problem with ISO dated 20191030 20191031 20191101 and 20191021
  after update+upgrade

  corrado@corrado-p13-ff-1101:~/Desktop$ inxi -Fx
  System:Host: corrado-p13-ff-1101 Kernel: 5.3.0-18-generic x86_64 bits: 64 
compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.1 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 
  Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: 
kernel bus ID: 00:02.0 
 Display: wayland server: X.Org 1.20.5 driver: i915 resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
v: 4.5 Mesa 19.2.1 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
 bus ID: 00:1f.3 
 Sound Server: ALSA v: k5.3.0-18-generic 
  Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
  Drives:Local Storage: total: 931.51 GiB used: 4.87 GiB (0.5%) 
 ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
temp: 34 C 
  Partition: ID-1: / size: 15.62 GiB used: 4.87 GiB (31.2%) fs: ext4 dev: 
/dev/sda13 
 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 38.5 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 205 Uptime: 16m Memory: 7.49 GiB used: 1.11 GiB (14.8%) 
Init: systemd runlevel: 5 Compilers: 
 gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 
  corrado@corrado-p13-ff-1101:~/Desktop$

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu9
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  1 18:13:53 2019
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
  InstallationDate: Installed on 2019-11-01 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191101)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
   Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=062c7ec4-2948-49df-934f-d054f397e4c4 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/11/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.10
  dmi.board.name: H110M-G/M.2
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: To Be Filled By O.E.M.
  dmi.produ

[Touch-packages] [Bug 1821376] Re: Report packages kept back by origins

[Balint Reczey]

root@uu-sru-bb:~# apt list --upgradable 
Listing... Done
apport/bionic-updates,bionic-security 2.20.9-0ubuntu7.8 all [upgradable from: 
2.20.9-0ubuntu7.7]
snapd/bionic-updates 2.40+18.04 amd64 [upgradable from: 2.37.4+18.04.1]
root@uu-sru-bb:~# perl -MMIME::QuotedPrint -pe 
'$_=MIME::QuotedPrint::decode($_);' /var/mail/mail
>From r...@uu-sru-bb.lxd Fri Nov 01 17:48:17 2019
Return-path: 
Envelope-to: r...@uu-sru-bb.lxd
Delivery-date: Fri, 01 Nov 2019 17:48:17 +
Received: from root by uu-sru-bb.lxd with local (Exim 4.90_1)
(envelope-from )
id 1iQb21-00014X-Mj
for r...@uu-sru-bb.lxd; Fri, 01 Nov 2019 17:48:17 +
Subject: [package on hold] unattended-upgrades result for uu-sru-bb: True
To: r...@uu-sru-bb.lxd
Auto-Submitted: auto-generated
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: root 
Message-Id: 
Date: Fri, 01 Nov 2019 17:48:17 +

Unattended upgrade returned: True

Packages that were upgraded:
 
Packages with upgradable origin but kept back:
 Ubuntu bionic-updates:
  snapd apport 


Unattended-upgrades log:
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic, o=Ubuntu,a=bionic-updates
Packages that will be upgraded: 


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

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

Title:
  Report packages kept back by origins

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  * Packages kept back are listed in the email report, but it is not
  clear from which origins they are installable. This information may
  help administrators to decide if the packages need to be manually
  upgraded.

  [Test Case]

  * test_mail.py test is updated to check if the kept back packages are
  reported per origin and this is checked at build time.

  *  For manual testing:
    1. Configure u-u to allow upgrades from the -updates pocket and send email 
with the upgrade report.
    2. Set up the system to have a few packages upgradable from both the 
-security and -updates pockets.
    3. Mark a subset of packages which are upgradable as held, marking packages 
from each of the pockets.
    4. Run u-u and observe the kept packages listed in the email. Each package 
is listed only in the allowed origin providing the highest version. (LP: 
#1848697 covers listing them in all origins from which the packages could be 
upgraded to.)

  [Regression Potential]

  * Unattended upgrades may crash while trying to perform updates or
  while trying to send the summary email. Build-time tests and
  autopkgtests include testing both functions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821376/+subscriptions

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

[Touch-packages] [Bug 1821376] Re: Report packages kept back by origins

[Balint Reczey]

Tested 1.10ubuntu5.2 on Disco:

root@uu-sru-dd:~# apt list --upgradable 
Listing... Done
apport/disco-updates,disco-security 2.20.10-0ubuntu27.2 all [upgradable from: 
2.20.10-0ubuntu27.1]
snapd/disco-updates 2.40+19.04 amd64 [upgradable from: 2.38+19.04]
root@uu-sru-dd:~# perl -MMIME::QuotedPrint -pe 
'$_=MIME::QuotedPrint::decode($_);' /var/mail/mail
>From r...@uu-sru-dd.lxd Fri Nov 01 17:48:11 2019
Return-path: 
Envelope-to: r...@uu-sru-dd.lxd
Delivery-date: Fri, 01 Nov 2019 17:48:11 +
Received: from root by uu-sru-dd.lxd with local (Exim 4.92)
(envelope-from )
id 1iQb1v-0001Pj-9M
for r...@uu-sru-dd.lxd; Fri, 01 Nov 2019 17:48:11 +
Subject: [package on hold] unattended-upgrades result for uu-sru-dd.lxd: SUCCESS
To: r...@uu-sru-dd.lxd
Auto-Submitted: auto-generated
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: root 
Message-Id: 
Date: Fri, 01 Nov 2019 17:48:11 +

Unattended upgrade result: All upgrades installed

Packages with upgradable origin but kept back:
 Ubuntu disco-updates:
  snapd apport 

Unattended-upgrades log:
Initial blacklist : 
Initial whitelist: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=disco, o=Ubuntu,a=disco-security, 
o=UbuntuESM,a=disco, o=Ubuntu,a=disco-updates
Packages that will be upgraded: 

root@uu-sru-dd:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion   Architecture Description
+++-===-=--===
ii  unattended-upgrades 1.10ubuntu5.2 all  automatic installation of 
security upgrades


** Description changed:

  [Impact]
  
  * Packages kept back are listed in the email report, but it is not clear
  from which origins they are installable. This information may help
  administrators to decide if the packages need to be manually upgraded.
  
  [Test Case]
  
  * test_mail.py test is updated to check if the kept back packages are
  reported per origin and this is checked at build time.
  
  *  For manual testing:
-   1. Configure u-u to allow upgrades from the -updates pocket and send email 
with the upgrade report.
-   2. Set up the system to have a few packages upgradable from both the 
-security and -updates pockets.
-   3. Mark a subset of packages which are upgradable as held, marking packages 
from each of the pockets.
-   4. Run u-u and observe the kept packages listed in the email. Each package 
is listed only in the allowed origin providing the highest version. (LP: 
#1848697 covers listing them in all origins from which the packages could be 
upgraded to.)
+   1. Configure u-u to allow upgrades from the -updates pocket and send email 
with the upgrade report.
+   2. Set up the system to have a few packages upgradable from both the 
-security and -updates pockets.
+   3. Mark a subset of packages which are upgradable as held, marking packages 
from each of the pockets.
+   4. Run u-u and observe the kept packages listed in the email. Each package 
is listed only in the allowed origin providing the highest version. (LP: 
#1848697 covers listing them in all origins from which the packages could be 
upgraded to.)
  
  [Regression Potential]
  
  * Unattended upgrades may crash while trying to perform updates or while
  trying to send the summary email. Build-time tests and autopkgtests
  include testing both functions.

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

Title:
  Report packages kept back by origins

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  * Packages kept back are listed in the email report, but it is not
  clear from which origins they are installable. This information may
  help administrators to decide if the packages need to be manually
  upgraded.

  [Test Case]

  * test_mail.py test is updated to check if the kept back packages are
  reported per origin and this is checked at build time.

  *  For manual testing:
    1. Configure u-u to allow upgrades from the -updates pocket and send email 
with the upgrade report.
    2. Set up the system to have a few packages upgradable from both the 
-security and -updates pockets.
    3. Mark a subset of packages which are upgradable as held, marking packages 
from each of the pockets.
    4. Run u-u and observe the kept packages listed in the email. Each package 
is listed only in the allowed origin 

[Touch-packages] [Bug 1821376] Re: Report packages kept back by origins

[Balint Reczey]

root@uu-sru-x:~# apt list --upgradable 
Listing... Done
apport/xenial-updates,xenial-security 2.20.1-0ubuntu2.20 all [upgradable from: 
2.20.1-0ubuntu2.19]
snapd/xenial-updates 2.40 amd64 [upgradable from: 2.37.4ubuntu0.1]
root@uu-sru-x:~# perl -MMIME::QuotedPrint -pe 
'$_=MIME::QuotedPrint::decode($_);' /var/mail/mail
>From r...@uu-sru-x.lxd Fri Nov 01 17:48:17 2019
Return-path: 
Envelope-to: r...@uu-sru-x.lxd
Delivery-date: Fri, 01 Nov 2019 17:48:17 +
Received: from root by uu-sru-x.lxd with local (Exim 4.86_2)
(envelope-from )
id 1iQb21-0001Jg-4W
for r...@uu-sru-x.lxd; Fri, 01 Nov 2019 17:48:17 +
Subject: [package on hold] unattended-upgrades result for uu-sru-x: True
To: r...@uu-sru-x.lxd
Auto-Submitted: auto-generated
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: root 
Message-Id: 
Date: Fri, 01 Nov 2019 17:48:17 +

Unattended upgrade returned: True

Packages that were upgraded:
 
Packages with upgradable origin but kept back:
 Ubuntu xenial-updates:
  snapd apport 


Unattended-upgrades log:
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial, o=Ubuntu,a=xenial-updates
Packages that will be upgraded: 

root@uu-sru-x:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.4 all  automatic 
installation of security upgrades

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

Title:
  Report packages kept back by origins

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  * Packages kept back are listed in the email report, but it is not
  clear from which origins they are installable. This information may
  help administrators to decide if the packages need to be manually
  upgraded.

  [Test Case]

  * test_mail.py test is updated to check if the kept back packages are
  reported per origin and this is checked at build time.

  *  For manual testing:
    1. Configure u-u to allow upgrades from the -updates pocket and send email 
with the upgrade report.
    2. Set up the system to have a few packages upgradable from both the 
-security and -updates pockets.
    3. Mark a subset of packages which are upgradable as held, marking packages 
from each of the pockets.
    4. Run u-u and observe the kept packages listed in the email. Each package 
is listed only in the allowed origin providing the highest version. (LP: 
#1848697 covers listing them in all origins from which the packages could be 
upgraded to.)

  [Regression Potential]

  * Unattended upgrades may crash while trying to perform updates or
  while trying to send the summary email. Build-time tests and
  autopkgtests include testing both functions.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1821376/+subscriptions

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

[Touch-packages] [Bug 1850969] Re: x1 session all mouse or keyboard action ignored

[corrado venturini]

same problem on a different hardware with an install from 
Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191019)
after updates

corrado@corrado-HP-p6-ff-1019:~$ inxi -Fx
System:
  Host: corrado-HP-p6-ff-1019 Kernel: 5.3.0-18-generic x86_64 bits: 64 
compiler: gcc 
  v: 9.2.1 Desktop: Gnome 3.34.1 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
Machine:
  Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook PC 
  v: 0991100600087 serial:  
  Mobo: Hewlett-Packard model: 2211 v: 86.49 serial:  UEFI: 
Insyde 
  v: F.36 date: 12/18/2014 
Battery:
  ID-1: BAT1 charge: 12.7 Wh condition: 18.9/18.9 Wh (100%) model: 13-42 
OA03031 
  status: Charging 
CPU:
  Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT MCP arch: 
Haswell 
  rev: 1 L2 cache: 3072 KiB 
  flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 
19156 
  Speed: 798 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 799 2: 799 3: 798 
4: 798 
Graphics:
  Device-1: Intel Haswell-ULT Integrated Graphics vendor: Hewlett-Packard 
driver: i915 
  v: kernel bus ID: 00:02.0 
  Display: wayland server: X.Org 1.20.5 driver: i915 resolution: 1366x768~60Hz 
  OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 19.2.1 
  direct render: Yes 
Audio:
  Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard driver: 
snd_hda_intel 
  v: kernel bus ID: 00:03.0 
  Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: 
snd_hda_intel 
  v: kernel bus ID: 00:1b.0 
  Sound Server: ALSA v: k5.3.0-18-generic 
Network:
  Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: Hewlett-Packard 
  driver: r8169 v: kernel port: 3000 bus ID: 08:00.0 
  IF: enp8s0 state: up speed: 100 Mbps duplex: full mac: 5c:b9:01:06:ba:ce 
  Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: Hewlett-Packard 
  driver: rt2800pci v: 2.3.0 port: 3000 bus ID: 09:00.0 
  IF: wlp9s0f0 state: down mac: ac:d1:b8:82:03:5d 
Drives:
  Local Storage: total: 465.76 GiB used: 6.31 GiB (1.4%) 
  ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 465.76 GiB 
Partition:
  ID-1: / size: 31.25 GiB used: 6.30 GiB (20.1%) fs: ext4 dev: /dev/sda6 
  ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: /dev/sda2 
Sensors:
  System Temperatures: cpu: 47.0 C mobo: 47.0 C 
  Fan Speeds (RPM): N/A 
Info:
  Processes: 207 Uptime: 4m Memory: 3.78 GiB used: 1.18 GiB (31.3%) Init: 
systemd 
  runlevel: 5 Compilers: gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 
corrado@corrado-HP-p6-ff-1019:~$

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

Title:
  x11 session all mouse or keyboard action ignored

Status in xorg package in Ubuntu:
  New

Bug description:
  Starting with x1 session all mouse or keyboard action are ignored. Only mouse 
arrow moves on the desktop.
  was able to exit only with cntrl+alt+f3
  wayland session works fine.
  Also booting from USB live and selecting 'try ubuntu' has the same problem.
  selecting install the install run smoothly but the just installed system has 
the problem.

  same problem with ISO dated 20191030 20191031 20191101 and 20191021
  after update+upgrade

  corrado@corrado-p13-ff-1101:~/Desktop$ inxi -Fx
  System:Host: corrado-p13-ff-1101 Kernel: 5.3.0-18-generic x86_64 bits: 64 
compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.1 
 Distro: Ubuntu 20.04 LTS (Focal Fossa) 
  Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  UEFI: American Megatrends v: P1.10 
 date: 05/11/2017 
  CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT 
MCP arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
 flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
 Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 
  Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: 
kernel bus ID: 00:02.0 
 Display: wayland server: X.Org 1.20.5 driver: i915 resolution: 
1920x1080~60Hz 
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) 
v: 4.5 Mesa 19.2.1 direct render: Yes 
  Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
 bus ID: 00:1f.3 
 Sound Server: ALSA v: k5.3.0-18-generic 
  Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
 IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
  Drives:Local Storage: total: 931.51 GiB used: 4.87 GiB (0.5%) 
 ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
temp: 34 C 
  Partition: ID-1: / size: 15.62 GiB used: 4.87 GiB (31.2%) fs: ext4 dev: 
/dev/sda13 
 ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap 

[Touch-packages] [Bug 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back

[Balint Reczey]

root@uu-sru-bb:~# unattended-upgrade --verbose
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=bionic, o=Ubuntu,a=bionic-security, 
o=UbuntuESM,a=bionic
Packages that will be upgraded: file libidn2-0 libmagic-mgc libmagic1 
libxslt1.1 python3-apport python3-problem-report
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
(Reading database ... 28655 files and directories currently installed.)
Preparing to unpack .../libidn2-0_2.0.4-1.1ubuntu0.2_amd64.deb ...
Unpacking libidn2-0:amd64 (2.0.4-1.1ubuntu0.2) over (2.0.4-1.1build2) ...
Setting up libidn2-0:amd64 (2.0.4-1.1ubuntu0.2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Log ended: 2019-11-01  17:09:03

Log started: 2019-11-01  17:09:04
(Reading database ... 28655 files and directories currently installed.)
Preparing to unpack .../libxslt1.1_1.1.29-5ubuntu0.2_amd64.deb ...
Unpacking libxslt1.1:amd64 (1.1.29-5ubuntu0.2) over (1.1.29-5ubuntu0.1) ...
Setting up libxslt1.1:amd64 (1.1.29-5ubuntu0.2) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Log ended: 2019-11-01  17:09:07

Log started: 2019-11-01  17:09:08
(Reading database ... 28655 files and directories currently installed.)
Preparing to unpack .../python3-apport_2.20.9-0ubuntu7.8_all.deb ...
Unpacking python3-apport (2.20.9-0ubuntu7.8) over (2.20.9-0ubuntu7.7) ...
Setting up python3-apport (2.20.9-0ubuntu7.8) ...
Log ended: 2019-11-01  17:09:12

Log started: 2019-11-01  17:09:12
(Reading database ... 28655 files and directories currently installed.)
Preparing to unpack .../python3-problem-report_2.20.9-0ubuntu7.8_all.deb ...
Unpacking python3-problem-report (2.20.9-0ubuntu7.8) over (2.20.9-0ubuntu7.7) 
...
Setting up python3-problem-report (2.20.9-0ubuntu7.8) ...
Log ended: 2019-11-01  17:09:15

Log started: 2019-11-01  17:09:15
(Reading database ... 28655 files and directories currently installed.)
Preparing to unpack .../file_1%3a5.32-2ubuntu0.3_amd64.deb ...
Unpacking file (1:5.32-2ubuntu0.3) over (1:5.32-2ubuntu0.2) ...
Preparing to unpack .../libmagic1_1%3a5.32-2ubuntu0.3_amd64.deb ...
Unpacking libmagic1:amd64 (1:5.32-2ubuntu0.3) over (1:5.32-2ubuntu0.2) ...
Preparing to unpack .../libmagic-mgc_1%3a5.32-2ubuntu0.3_amd64.deb ...
Unpacking libmagic-mgc (1:5.32-2ubuntu0.3) over (1:5.32-2ubuntu0.2) ...
Setting up libmagic-mgc (1:5.32-2ubuntu0.3) ...
Setting up libmagic1:amd64 (1:5.32-2ubuntu0.3) ...
Setting up file (1:5.32-2ubuntu0.3) ...
Processing triggers for man-db (2.8.3-2ubuntu0.1) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
All upgrades installed
root@uu-sru-bb:~# update-motd
Welcome to Ubuntu 18.04.3 LTS (GNU/Linux 5.0.0-32-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

  System information as of Fri Nov  1 17:28:59 UTC 2019

  System load:1.65  Processes:   24
  Usage of /home: unknown   Users logged in: 0
  Memory usage:   0%IP address for eth0: 10.84.73.22
  Swap usage: 48%

0 packages can be updated.
0 updates are security updates.


1 updates could not be installed automatically. For more details,
see /var/log/unattended-upgrades/unattended-upgrades.log

root@uu-sru-bb:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion Architecture Description
+++-===-===--===
ii  unattended-upgrades 1.1ubuntu1.18.04.12 all  automatic installation 
of security upgrades


** Description changed:

  [Impact]
  
-  * MOTD does not go into details about upgradable packages being security 
fixes or just normal updates.
-  * Users should be made aware if some of the security updates could not have 
been applied.
-  * The fix is adding a snipped to MOTD where the number of packages kept back 
by unattended-upgrades is shown.
+  * MOTD does not go into details about upgradable packages being security 
fixes or just normal updates.
+  * Users should be made aware if some of the security updates could not have 
been applied.
+  * The fix is adding a snipped to MOTD where the number of packages kept back 
by unattended-upgrades is shown.
  
  [Test Case]
  
-  * The debian/tests/upgrade-all-security is extended to check if the number 
of kept back packages are shown in MOTD and a new test is added 
(test/test_motd.py) to check if the list of kept back packages are saved 
properly.
-  * To test the fix manually:
-1. Mark a package upgradable from the -security pocket as held, then run 
unattended-upgrades.
-2. Observe MOTD messate showing the number of packages being kept back.
+  * The debian/tests/upgrade-all-security is 

[Touch-packages] [Bug 1850964] Re: Always explain why packages are held back in logs even without debugging enabled

[Balint Reczey]

** Summary changed:

- Explain why packages are held back in logs even without debugging enabled
+ Always explain why packages are held back in logs even without debugging 
enabled

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

Title:
  Always explain why packages are held back in logs even without
  debugging enabled

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  [Impact]

   * Unattended-upgrades' log does not contain information about why
  held packages are kept back unless debugging is enabled. Users should
  be explained why packages are kept back to let them easily resolve the
  issues keeping the packages from being upgraded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1850964/+subscriptions

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

[Touch-packages] [Bug 1850969] [NEW] x1 session all mouse or keyboard action ignored

[corrado venturini]

Public bug reported:

Starting with x1 session all mouse or keyboard action are ignored. Only mouse 
arrow moves on the desktop.
was able to exit only with cntrl+alt+f3
wayland session works fine.
Also booting from USB live and selecting 'try ubuntu' has the same problem.
selecting install the install run smoothly but the just installed system has 
the problem.

same problem with ISO dated 20191030 20191031 20191101 and 20191021
after update+upgrade

corrado@corrado-p13-ff-1101:~/Desktop$ inxi -Fx
System:Host: corrado-p13-ff-1101 Kernel: 5.3.0-18-generic x86_64 bits: 64 
compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.1 
   Distro: Ubuntu 20.04 LTS (Focal Fossa) 
Machine:   Type: Desktop Mobo: ASRock model: H110M-G/M.2 serial:  UEFI: American Megatrends v: P1.10 
   date: 05/11/2017 
CPU:   Topology: Dual Core model: Intel Core i3-7100 bits: 64 type: MT MCP 
arch: Kaby Lake rev: 9 L2 cache: 3072 KiB 
   flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx 
bogomips: 31199 
   Speed: 801 MHz min/max: 800/3900 MHz Core speeds (MHz): 1: 800 2: 
800 3: 800 4: 800 
Graphics:  Device-1: Intel HD Graphics 630 vendor: ASRock driver: i915 v: 
kernel bus ID: 00:02.0 
   Display: wayland server: X.Org 1.20.5 driver: i915 resolution: 
1920x1080~60Hz 
   OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2) v: 
4.5 Mesa 19.2.1 direct render: Yes 
Audio: Device-1: Intel 100 Series/C230 Series Family HD Audio vendor: 
ASRock driver: snd_hda_intel v: kernel 
   bus ID: 00:1f.3 
   Sound Server: ALSA v: k5.3.0-18-generic 
Network:   Device-1: Intel Ethernet I219-V vendor: ASRock driver: e1000e v: 
3.2.6-k port: f040 bus ID: 00:1f.6 
   IF: enp0s31f6 state: up speed: 100 Mbps duplex: full mac: 
70:85:c2:44:7b:86 
Drives:Local Storage: total: 931.51 GiB used: 4.87 GiB (0.5%) 
   ID-1: /dev/sda vendor: Toshiba model: DT01ACA100 size: 931.51 GiB 
temp: 34 C 
Partition: ID-1: / size: 15.62 GiB used: 4.87 GiB (31.2%) fs: ext4 dev: 
/dev/sda13 
   ID-2: swap-1 size: 8.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
Sensors:   System Temperatures: cpu: 38.5 C mobo: N/A 
   Fan Speeds (RPM): N/A 
Info:  Processes: 205 Uptime: 16m Memory: 7.49 GiB used: 1.11 GiB (14.8%) 
Init: systemd runlevel: 5 Compilers: 
   gcc: 9.2.1 Shell: bash v: 5.0.3 inxi: 3.0.36 
corrado@corrado-p13-ff-1101:~/Desktop$

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  1 18:13:53 2019
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:5912] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: ASRock Incorporation HD Graphics 630 [1849:5912]
InstallationDate: Installed on 2019-11-01 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20191101)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 046d:c016 Logitech, Inc. Optical Wheel Mouse
 Bus 001 Device 002: ID 058f:6377 Alcor Micro Corp. AU6375 4-LUN card reader
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-18-generic 
root=UUID=062c7ec4-2948-49df-934f-d054f397e4c4 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/11/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: H110M-G/M.2
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd05/11/2017:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH110M-G/M.2:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.sku: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.99-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
version.xs

[Touch-packages] [Bug 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back

[Balint Reczey]

root@uu-sru-x:~# unattended-upgrade --verbose
Initial blacklisted packages: 
Initial whitelisted packages: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=xenial, o=Ubuntu,a=xenial-security, 
o=UbuntuESM,a=xenial
Packages that will be upgraded: 
root@uu-sru-x:~# update-motd
Welcome to Ubuntu 16.04.6 LTS (GNU/Linux 5.0.0-32-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

0 packages can be updated.
0 updates are security updates.


1 updates could not be installed automatically. For more details,
see /var/log/unattended-upgrades/unattended-upgrades.log

root@uu-sru-x:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersionArchitecture Description
+++-===-==--===
ii  unattended-upgrades 1.1ubuntu1.18.04.7~16.04.4 all  automatic 
installation of security upgrades


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

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

Title:
  unattended-upgrades should tell the user (via motd) when security
  updates are held back

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * MOTD does not go into details about upgradable packages being security 
fixes or just normal updates.
   * Users should be made aware if some of the security updates could not have 
been applied.
   * The fix is adding a snipped to MOTD where the number of packages kept back 
by unattended-upgrades is shown.

  [Test Case]

   * The debian/tests/upgrade-all-security is extended to check if the number 
of kept back packages are shown in MOTD and a new test is added 
(test/test_motd.py) to check if the list of kept back packages are saved 
properly.
   * To test the fix manually:
     1. Mark a package upgradable from the -security pocket as held, then run 
unattended-upgrades.
     2. Observe MOTD messate showing the number of packages being kept back.

  [Regression Potential]

   * Unattended-upgrades may crash when saving kept packages and always
  return with failure. MOTD may hang or print error while printing the
  packages kept back by u-u.

   * It is not a regression, but the log referenced in MOTD does not
  always contain explanation why each package was kept back, unless
  debugging is enabled. One case where packages are not mentioned in the
  log is when the packages are held using 'apt-mark hold' command.

  [Original Bug Text]

  Currently we have the following pieces as part of the default UX on
  Ubuntu 18.04 and later:

   1) unattended-upgrades automatically installs security updates daily by 
default
   2) the motd reports the number of available updates, including security 
updates.

  A user who knows about 1) also knows that a non-zero number of pending
  security updates listed in 2) is nothing to worry about.

  However, unattended-upgrades will also cleverly detect when a security
  update cannot safely be installed non-interactively due to conffile
  changes on the system.

  In this case, unattended-upgrades should also inform the user via the
  motd that these updates are not being installed.  Otherwise, there's
  nothing to tell the user that the non-zero count of available security
  updates in motd is a *problem*.

  Suggested wording:

   N security updates will not be automatically installed due to local changes.
   See /var/log/foo for details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1823070/+subscriptions

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

[Touch-packages] [Bug 1850964] Re: Explain why packages are held back in logs even without debugging enabled

[Balint Reczey]

** Description changed:

  [Impact]
  
-  * Unattended-upgrades' log does not contain information about why
- particular packages are kept back unless debugging is enabled. Users
- should be explained why packages are kept back to let them easily
- resolve the issues keeping the packages from being upgraded.
+  * Unattended-upgrades' log does not contain information about why held
+ packages are kept back unless debugging is enabled. Users should be
+ explained why packages are kept back to let them easily resolve the
+ issues keeping the packages from being upgraded.

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

Title:
  Always explain why packages are held back in logs even without
  debugging enabled

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  [Impact]

   * Unattended-upgrades' log does not contain information about why
  held packages are kept back unless debugging is enabled. Users should
  be explained why packages are kept back to let them easily resolve the
  issues keeping the packages from being upgraded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1850964/+subscriptions

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

[Touch-packages] [Bug 1850966] Re: Stuck at "Refreshing software cache" after enabling repository not updated for Eoan

[Efthimios Chaskaris]

** Package changed: software-properties (Ubuntu) => ubuntu

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

Title:
  Stuck at "Refreshing software cache" after enabling repository not
  updated for Eoan

Status in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Open Software and Updates
  2. Go to "other software" and enable, for example, a repository disabled 
during upgrade to Eoan which is not updated for Eoan yet
  3. Press close and then reload on the dialog that opens.
  4. Refreshing software cache dialog is stuck

  After closing the dialogs by right clicking on the windows and the
  open apps bar, re opening Software and updates only shows a white
  square you can't interact with.

  Ubuntu 19.10

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

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

[Touch-packages] [Bug 1823070] Re: unattended-upgrades should tell the user (via motd) when security updates are held back

[Balint Reczey]

root@uu-sru-dd:~# unattended-upgrade --verbose
Initial blacklist : 
Initial whitelist: 
Starting unattended upgrades script
Allowed origins are: o=Ubuntu,a=disco, o=Ubuntu,a=disco-security, 
o=UbuntuESM,a=disco
Packages that will be upgraded: file libidn2-0 libmagic-mgc libmagic1 
libxslt1.1 python3-apport python3-problem-report
Writing dpkg log to /var/log/unattended-upgrades/unattended-upgrades-dpkg.log
(Reading database ... 28941 files and directories currently installed.)
Preparing to unpack .../libidn2-0_2.0.5-1ubuntu0.3_amd64.deb ...
Unpacking libidn2-0:amd64 (2.0.5-1ubuntu0.3) over (2.0.5-1) ...
Setting up libidn2-0:amd64 (2.0.5-1ubuntu0.3) ...
Processing triggers for libc-bin (2.29-0ubuntu2) ...
Log ended: 2019-11-01  17:08:54

Log started: 2019-11-01  17:08:55
(Reading database ... 28941 files and directories currently installed.)
Preparing to unpack .../file_1%3a5.35-4ubuntu0.1_amd64.deb ...
Unpacking file (1:5.35-4ubuntu0.1) over (1:5.35-4) ...
Preparing to unpack .../libmagic1_1%3a5.35-4ubuntu0.1_amd64.deb ...
Unpacking libmagic1:amd64 (1:5.35-4ubuntu0.1) over (1:5.35-4) ...
Preparing to unpack .../libmagic-mgc_1%3a5.35-4ubuntu0.1_amd64.deb ...
Unpacking libmagic-mgc (1:5.35-4ubuntu0.1) over (1:5.35-4) ...
Setting up libmagic-mgc (1:5.35-4ubuntu0.1) ...
Setting up libmagic1:amd64 (1:5.35-4ubuntu0.1) ...
Setting up file (1:5.35-4ubuntu0.1) ...
Processing triggers for libc-bin (2.29-0ubuntu2) ...
Processing triggers for man-db (2.8.5-2) ...
Log ended: 2019-11-01  17:08:59

Log started: 2019-11-01  17:09:00
(Reading database ... 28941 files and directories currently installed.)
Preparing to unpack .../python3-apport_2.20.10-0ubuntu27.2_all.deb ...
Unpacking python3-apport (2.20.10-0ubuntu27.2) over (2.20.10-0ubuntu27.1) ...
Setting up python3-apport (2.20.10-0ubuntu27.2) ...
Log ended: 2019-11-01  17:09:04

Log started: 2019-11-01  17:09:04
(Reading database ... 28941 files and directories currently installed.)
Preparing to unpack .../python3-problem-report_2.20.10-0ubuntu27.2_all.deb ...
Unpacking python3-problem-report (2.20.10-0ubuntu27.2) over 
(2.20.10-0ubuntu27.1) ...
Setting up python3-problem-report (2.20.10-0ubuntu27.2) ...
Log ended: 2019-11-01  17:09:07

Log started: 2019-11-01  17:09:08
(Reading database ... 28941 files and directories currently installed.)
Preparing to unpack .../libxslt1.1_1.1.32-2ubuntu0.2_amd64.deb ...
Unpacking libxslt1.1:amd64 (1.1.32-2ubuntu0.2) over (1.1.32-2ubuntu0.1) ...
Setting up libxslt1.1:amd64 (1.1.32-2ubuntu0.2) ...
Processing triggers for libc-bin (2.29-0ubuntu2) ...
All upgrades installed
root@uu-sru-dd:~# update-motd
Welcome to Ubuntu 19.04 (GNU/Linux 5.0.0-32-generic x86_64)

 * Documentation:  https://help.ubuntu.com
 * Management: https://landscape.canonical.com
 * Support:https://ubuntu.com/advantage

  System information as of Fri Nov  1 17:09:55 UTC 2019

  System load:1.99  Processes:   26
  Usage of /home: unknown   Users logged in: 0
  Memory usage:   0%IP address for eth0: 10.84.73.43
  Swap usage: 49%

0 updates can be installed immediately.
0 of these updates are security updates.


1 updates could not be installed automatically. For more details,
see /var/log/unattended-upgrades/unattended-upgrades.log

root@uu-sru-dd:~# dpkg -l unattended-upgrades | cat
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ NameVersion   Architecture Description
+++-===-=--===
ii  unattended-upgrades 1.10ubuntu5.2 all  automatic installation of 
security upgrades


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

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

Title:
  unattended-upgrades should tell the user (via motd) when security
  updates are held back

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Committed

Bug description:
  [Impact]

   * MOTD does not go into details about upgradable packages being security 
fixes or just normal updates.
   * Users should be made aware if some of the security updates could not have 
been applied.
   * The fix is adding a snipped to MOTD where the number of packages kept back 
by unattended-upgrades is shown.

  [Test Case]

   * The debian/tests/upgrade-all-security is extended to check if the number 
of kept back packages are shown in MOTD and a new test is added 
(test/test_motd.py) to check if the list of kept back packages are saved 

[Touch-packages] [Bug 1850966] [NEW] Stuck at "Refreshing software cache" after enabling repository not updated for Eoan

[Efthimios Chaskaris]

Public bug reported:

Steps to reproduce:
1. Open Software and Updates
2. Go to "other software" and enable, for example, a repository disabled during 
upgrade to Eoan which is not updated for Eoan yet
3. Press close and then reload on the dialog that opens.
4. Refreshing software cache dialog is stuck

After closing the dialogs by right clicking on the windows and the open
apps bar, re opening Software and updates only shows a white square you
can't interact with.

Ubuntu 19.10

** Affects: ubuntu
 Importance: Undecided
 Status: New


** Tags: eoan

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

Title:
  Stuck at "Refreshing software cache" after enabling repository not
  updated for Eoan

Status in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Open Software and Updates
  2. Go to "other software" and enable, for example, a repository disabled 
during upgrade to Eoan which is not updated for Eoan yet
  3. Press close and then reload on the dialog that opens.
  4. Refreshing software cache dialog is stuck

  After closing the dialogs by right clicking on the windows and the
  open apps bar, re opening Software and updates only shows a white
  square you can't interact with.

  Ubuntu 19.10

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

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

[Touch-packages] [Bug 1850964] [NEW] Explain why packages are held back in logs even without debugging enabled

[Balint Reczey]

Public bug reported:

[Impact]

 * Unattended-upgrades' log does not contain information about why held
packages are kept back unless debugging is enabled. Users should be
explained why packages are kept back to let them easily resolve the
issues keeping the packages from being upgraded.

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Explain why packages are held back in logs even without debugging
  enabled

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  [Impact]

   * Unattended-upgrades' log does not contain information about why
  held packages are kept back unless debugging is enabled. Users should
  be explained why packages are kept back to let them easily resolve the
  issues keeping the packages from being upgraded.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1850964/+subscriptions

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

[Touch-packages] [Bug 1850961] [NEW] Curl 7.58 CPU high usage problem

[Sunhyung Lee]

Public bug reported:

Refer to https://github.com/aws/aws-sdk-cpp/issues/1253

I found HTTP request issue when I was testing my application which does long 
polling a certain REST API for every 100ms and after some duration of time, CPU 
spikes up to 100% because of curl.
For the clear test, I made simple HTTP request application which is in the link 
above and ran it with curl 7.58 and curl 7.66 the latest.
The sample application also shown same problem with curl 7.58 but worked fine 
with curl 7.66 the latest.
This test has done with Docker Ubuntu 18.04 LTS and Ubuntu 18.04 LTS in WSL.

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

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

Title:
  Curl 7.58 CPU high usage problem

Status in curl package in Ubuntu:
  New

Bug description:
  Refer to https://github.com/aws/aws-sdk-cpp/issues/1253

  I found HTTP request issue when I was testing my application which does long 
polling a certain REST API for every 100ms and after some duration of time, CPU 
spikes up to 100% because of curl.
  For the clear test, I made simple HTTP request application which is in the 
link above and ran it with curl 7.58 and curl 7.66 the latest.
  The sample application also shown same problem with curl 7.58 but worked fine 
with curl 7.66 the latest.
  This test has done with Docker Ubuntu 18.04 LTS and Ubuntu 18.04 LTS in WSL.

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

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

[Touch-packages] [Bug 1850775] Re: DNS info is not loaded by dhclient

[Joshua Powers]

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

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

Title:
  DNS info is not loaded by dhclient

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  Hi Team,

  Could you please help to confirm if this is an issue on Ubuntu19.10
  Desktop?

  1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
 supersede domain-name "vmware.com";
 supersede domain-name-servers 10.117.0.1;

  2. Reboot

  3. check DNS info by "systemd-resolve --status", the DNS domain and
  server is not set. But /run/systemd/resolved.conf.d/isc-
  dhcp-v4-ens160.conf contains the new DNS domain and server.

  4. Manually run "systemctl try-reload-or-restart systemd-
  resolved.service" and then DNS is set correctly, "systemd-resolve
  --status" output have the new DNS domain and server.

  
  I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

  Thanks,
  Pengpeng

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

-- 
Mailing list: https://launchpad.net/~touch-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] Re: networkd should allow configuring IPV6 MTU

[Dan Streetman]

I opened this upstream
https://github.com/systemd/systemd/pull/13915

-- 
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 Released
Status in systemd source package in Bionic:
  Triaged
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Triaged

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 1848354] Re: upgrade-between-snapshots autopkgtest is flaky

[Balint Reczey]

@sil2100 there are more bugs fixed in the u-u SRUs in Disco and older
and the Eoan upload is needed to unblock them thus I suggest dropping
all block-proposed tags.

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

Title:
  upgrade-between-snapshots autopkgtest is flaky

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in unattended-upgrades source package in Bionic:
  Fix Committed
Status in unattended-upgrades source package in Disco:
  Fix Committed
Status in unattended-upgrades source package in Eoan:
  Fix Committed

Bug description:
  [Impact]

   * Flaky upgrade-between-snapshots autopkgtest prevents developers to
  use the test efficiently.

  [Test Case]

   * Run autopkgtests, observe the upgrade-between-snapshots test
  passing or failing but being marked as FLAKY.

  [Regression Potential]

   * None, the test was failing often due to connectivity/internal
  errors of snapshot.debian.org.

  [Other Info]

   * The whole autopkgtest is marked to be failing on amd64 to mitigate
  the single flaky test, this marking can be removed after marking this
  single flaky test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1848354/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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] Re: networkd should allow configuring IPV6 MTU

[Ryan Harper]

Testing with @ddstreet's systemd ppa, I can confirm that bionic, disco
and eoan correctly set MTU on first boot, no systemd-restart needed.

-- 
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 Released
Status in systemd source package in Bionic:
  Triaged
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Triaged

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 1845337] Re: Disco autopkgtest @ armhf fails root-unittests -> test-execute -> exec-dynamicuser-statedir.service

[Balint Reczey]

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

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

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

Title:
  Disco autopkgtest @ armhf fails root-unittests -> test-execute ->
  exec-dynamicuser-statedir.service

Status in qemu package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Released
Status in qemu source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Triaged

Bug description:
  [impact]

  due to recent change to run armhf tests in nested lxd container,
  autopkgtest for systemd on disco fails consistently.

  [test case]

  see test results, linked in original description below.

  [regression potential]

  very low, autopkgtest fix only.

  [other info]

  original description:
  ---

  Since the recent few weeks systemd autopkgtest @ armhf @ disco fail
  [1].

  The log is very (very) long and partially interwoven due to concurrent 
execution.
  Somewhere in between we see this subcase is the one failing: root-unittests
  Of this test (which again has many subtests) it is: test-execute
  And of this again it is (always):

  I'll attach bad and good case full and stripped logs.

  The diff of those comes down to just:
  1. execute a find in a shell
  2. shell exits
  3. exec-dynamicuser-statedir.service: Main process exited, code=exited, 
status=0/SUCCESS
  vs
  3. exec-dynamicuser-statedir.service: Main process exited, code=exited, 
status=1/FAILURE
  4. in the bad case that triggers an assertion
  The find that fails is:

  find / -path /var/tmp -o -path /tmp -o -path /proc -o -path
  /dev/mqueue -o -path /dev/shm -o -path /sys/fs/bpf

  Good and bad case are the same most recent version
  systemd/240-6ubuntu5.7.

  Maybe something is bad in the containers we have for armhf in regard to these 
paths?
  Was there any change we'd know of?

  If there is nothing known, could we force-badtest it to get it out of
  the way of ongoing migrations?

  [1]: http://autopkgtest.ubuntu.com/packages/s/systemd/disco/armhf

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

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

[Touch-packages] [Bug 1850931] [NEW] screen corruption after sleep mode

[Xtien]

Public bug reported:

When my laptop goes into sleep mode, and I log back in, the screen is 
corrupted. I wanted to report with ubuntu-bug, but that doesn't open a browser 
window so it doesn't report a bug.
I'll attach a screenshot of the corrupted screen. It stays corrupted until I 
restart the computer. The laptop is a new Dell XPS 15 with a GEforce GTX 1650 
card.
I use Ubuntu 19.04.

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

** Attachment added: "Screenshot from 2019-11-01 14-36-26.png"
   
https://bugs.launchpad.net/bugs/1850931/+attachment/5302044/+files/Screenshot%20from%202019-11-01%2014-36-26.png

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

Title:
  screen corruption after sleep mode

Status in xorg package in Ubuntu:
  New

Bug description:
  When my laptop goes into sleep mode, and I log back in, the screen is 
corrupted. I wanted to report with ubuntu-bug, but that doesn't open a browser 
window so it doesn't report a bug.
  I'll attach a screenshot of the corrupted screen. It stays corrupted until I 
restart the computer. The laptop is a new Dell XPS 15 with a GEforce GTX 1650 
card.
  I use Ubuntu 19.04.

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

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

[Touch-packages] [Bug 1850932] [NEW] [SRU] Backport 2.62.2-2

[Iain Lane]

Public bug reported:

[ Description ]

I'm creating this bug report to have a place to describe the proposed
backport of glib2.0 2.62.2-2 from focal.

The main purpose of this backport (as opposed to -1) is to fix bug
#1844853.

But there are several other changes. There are many cherry-picks to
improve the testsuite's reliability. At the time of upload they weren't
in the stable branch, but now they almost all are. These commits can be
considered to be tested under
https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

The two that are not are:

commit 2b1e706b2f0007982f4fe6a70734d4490e4093a3
Author: Simon McVittie 
Date:   Tue Oct 29 16:27:53 2019 +

gdbus-server-auth test: Create temporary directory for Unix socket

This avoids failure to listen on the given address on non-Linux Unix
kernels, where abstract sockets do not exist and so unix:tmpdir is
equivalent to unix:dir.

To avoid bugs like this one recurring, run most of these tests using
the unix:dir address type, where Linux is equivalent to other Unix
kernels; just do one unix:tmpdir test, to check that we still
interoperate with libdbus when using abstract sockets on Linux.

Resolves: GNOME/glib#1920
Fixes: 9f962ebe "Add a test for GDBusServer authentication"
Signed-off-by: Simon McVittie 

commit 9f962ebeac1d67223579ad0d261c4c8215f7c427
Author: Simon McVittie 
Date:   Fri Oct 11 19:02:55 2019 +0100

Add a test for GDBusServer authentication

In particular, if libbdus is available, we test interoperability with
a libdbus client: see GNOME/glib#1831. Because that issue describes a
race condition, we do each test repeatedly to try to hit the failing
case.

Signed-off-by: Simon McVittie 

which are both testsuite fixes. There are some additional non-upstream
changes:

   * d/p/debian/mimeapps-test-Mark-as-flaky.patch:
 Drop patch, hopefully no longer needed with #941550 fixed
   * d/p/debian/taptestrunner-Stop-looking-like-an-executable-script.patch:
 Make taptestrunner non-executable to avoid a Lintian warning

the former is again a testsuite fix. The latter is a fix to the test
runner, which is relevant for the installed tests (run via autopkgtest)
but not otherwise.

[ QA ]

The testsuite fixes will verify themselves during the build and
autopkgtest.

[ Regression potential ]

all test fixes> Build failures or autopkgtest failures.

** Affects: glib2.0 (Ubuntu)
 Importance: Undecided
 Status: Fix Released

** Affects: glib2.0 (Ubuntu Eoan)
 Importance: Undecided
 Assignee: Iain Lane (laney)
 Status: In Progress

** Also affects: glib2.0 (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: glib2.0 (Ubuntu)
   Status: New => Fix Released

** Changed in: glib2.0 (Ubuntu Eoan)
   Status: New => Triaged

** Changed in: glib2.0 (Ubuntu Eoan)
   Status: Triaged => In Progress

** Changed in: glib2.0 (Ubuntu Eoan)
 Assignee: (unassigned) => Iain Lane (laney)

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

Title:
  [SRU] Backport 2.62.2-2

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Eoan:
  In Progress

Bug description:
  [ Description ]

  I'm creating this bug report to have a place to describe the proposed
  backport of glib2.0 2.62.2-2 from focal.

  The main purpose of this backport (as opposed to -1) is to fix bug
  #1844853.

  But there are several other changes. There are many cherry-picks to
  improve the testsuite's reliability. At the time of upload they
  weren't in the stable branch, but now they almost all are. These
  commits can be considered to be tested under
  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  The two that are not are:

  commit 2b1e706b2f0007982f4fe6a70734d4490e4093a3
  Author: Simon McVittie 
  Date:   Tue Oct 29 16:27:53 2019 +

  gdbus-server-auth test: Create temporary directory for Unix socket
  
  This avoids failure to listen on the given address on non-Linux Unix
  kernels, where abstract sockets do not exist and so unix:tmpdir is
  equivalent to unix:dir.
  
  To avoid bugs like this one recurring, run most of these tests using
  the unix:dir address type, where Linux is equivalent to other Unix
  kernels; just do one unix:tmpdir test, to check that we still
  interoperate with libdbus when using abstract sockets on Linux.
  
  Resolves: GNOME/glib#1920
  Fixes: 9f962ebe "Add a test for GDBusServer authentication"
  Signed-off-by: Simon McVittie 

  commit 9f962ebeac1d67223579ad0d261c4c8215f7c427
  Author: Simon McVittie 
  Date:   Fri Oct 11 19:02:55 2019 +0100

  Add a test for GDBusServer authentication
  
  In particular, if libbdus is available, we test interoperability with
  a libdbus 

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

[Balint Reczey]

@ddstreet You systemd builds in the PPA fix the issue for me on Bionic
and Disco, IPv6 MTU is applied after reboot with the configuration.

-- 
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 Released
Status in systemd source package in Bionic:
  Triaged
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Triaged

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

[Dimitri John Ledkov]

Some observations:
* growpart uses sfdisk without --no-tell-kernel option, meaning that it does 
notify kernel about partition changes
* growpart later calls partx, which may be redundant / cause no changes or 
events
* as a side note, partprobe, blockdev --rereadpt can also be used to reread 
partition tables, I'm not sure the difference between them
* growpart does not take exclusive lock of the device, meaning sgdisk is known 
to be racy with udev events

Imho the sequency of commands should be:
* take flock on the device, to neutralise udev
* modify device with sfdisk
* reread partitions tables (i would say with blockdev --rereadpt, rather than 
partx/partprobe) 
* release the flock
* udevadm trigger --action=add --wait device (or trigger && settle)

This way it ensures that no udev events are processed for the device
whilst we are operating and rereading the device partitions, and then we
release the lock, at which point everything has to be quiet and steady,
trigger, settle, done.


See:
   sfdisk  uses  BLKRRPART (reread partition table) ioctl to make sure that 
the device is not used
   by system or another tools (see also --no-reread).  It's possible that 
this feature or  another
   sfdisk  activity  races with udevd.  The recommended way how to avoid 
possible collisions is to
   use exclusive flock for the whole-disk device to serialize device 
access.  The  exclusive  lock
   will cause udevd to skip the event handling on the device.  For example:

  flock /dev/sdc sfdisk /dev/sdc

   Note, this semantic is not currently supported by udevd for MD
and DM devices.

at http://manpages.ubuntu.com/manpages/eoan/en/man8/sfdisk.8.html

-- 
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 1671951] Re: networkd should allow configuring IPV6 MTU

[Balint Reczey]

I have not tested first boot, @raharper could you please test that?

-- 
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 Released
Status in systemd source package in Bionic:
  Triaged
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Triaged

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

[Dimitri John Ledkov]

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/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:
  Incomplete

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 1850929] [NEW] python3-apport regression: missing argument in Report.add_proc_environ call

[Mikael Magnusson]

Public bug reported:

This is a regression in the 2.20.9-0ubuntu7.8 security update of apport

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

Reproduce the bug:

$ python3
Python 3.6.8 (default, Oct  7 2019, 12:59:55) 
[GCC 8.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import apport
>>> import os
>>> report = apport.Report()
>>> report.add_proc_info(os.getpid(), extraenv=['PYTHONHOME', 'PYTHONPATH'])
Traceback (most recent call last):
  File "", line 1, in 
  File "/usr/lib/python3/dist-packages/apport/report.py", line 543, in 
add_proc_info
self.add_proc_environ(pid, extraenv)
  File "/usr/lib/python3/dist-packages/apport/report.py", line 610, in 
add_proc_environ
env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
  File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in _read_file
with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
  File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
TypeError: argument should be integer or None, not list

Patch below:

# diff -u  /usr/lib/python3/dist-packages/apport/report.py 
/usr/lib/python3/dist-packages/apport/report.py.new 
--- /usr/lib/python3/dist-packages/apport/report.py 2019-11-01 
14:16:39.375968798 +0100
+++ /usr/lib/python3/dist-packages/apport/report.py.new 2019-11-01 
14:17:58.035128006 +0100
@@ -540,7 +540,7 @@
 self['ProcCwd'] = os.readlink('cwd', dir_fd=proc_pid_fd)
 except OSError:
 pass
-self.add_proc_environ(pid, extraenv)
+self.add_proc_environ(pid, proc_pid_fd, extraenv)
 self['ProcStatus'] = _read_file('status', dir_fd=proc_pid_fd)
 self['ProcCmdline'] = _read_file('cmdline', 
dir_fd=proc_pid_fd).rstrip('\0')
 self['ProcMaps'] = _read_maps(proc_pid_fd)

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: python3-apport 2.20.9-0ubuntu7.8
ProcVersionSignature: Ubuntu 4.15.0-58.64-generic 4.15.18
Uname: Linux 4.15.0-58-generic x86_64
ApportLog:
 
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
CrashReports: 640:1000:1004:35152:2019-11-01 14:00:47.150214442 
+0100:2019-11-01 14:00:47.150214442 +0100:/var/crash/_usr_bin_snimpy.1000.crash
Date: Fri Nov  1 14:18:16 2019
PackageArchitecture: all
SourcePackage: apport
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic patch uec-images

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

Title:
  python3-apport regression: missing argument in Report.add_proc_environ
  call

Status in apport package in Ubuntu:
  New

Bug description:
  This is a regression in the 2.20.9-0ubuntu7.8 security update of
  apport

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

  Reproduce the bug:

  $ python3
  Python 3.6.8 (default, Oct  7 2019, 12:59:55) 
  [GCC 8.3.0] on linux
  Type "help", "copyright", "credits" or "license" for more information.
  >>> import apport
  >>> import os
  >>> report = apport.Report()
  >>> report.add_proc_info(os.getpid(), extraenv=['PYTHONHOME', 'PYTHONPATH'])
  Traceback (most recent call last):
File "", line 1, in 
File "/usr/lib/python3/dist-packages/apport/report.py", line 543, in 
add_proc_info
  self.add_proc_environ(pid, extraenv)
File "/usr/lib/python3/dist-packages/apport/report.py", line 610, in 
add_proc_environ
  env = _read_file('environ', dir_fd=proc_pid_fd).replace('\n', '\\n')
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
_read_file
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
File "/usr/lib/python3/dist-packages/apport/report.py", line 73, in 
  with open(path, 'rb', opener=lambda path, mode: os.open(path, mode, 
dir_fd=dir_fd)) as fd:
  TypeError: argument should be integer or None, not list

  Patch below:

  # diff -u  /usr/lib/python3/dist-packages/apport/report.py 
/usr/lib/python3/dist-packages/apport/report.py.new 
  --- /usr/lib/python3/dist-packages/apport/report.py   2019-11-01 
14:16:39.375968798 +0100
  +++ /usr/lib/python3/dist-packages/apport/report.py.new   2019-11-01 
14:17:58.035128006 +0100
  @@ -540,7 +540,7 @@
   self['ProcCwd'] = os.readlink('cwd', dir_fd=proc_pid_fd)
   except OSError:
   pass
  -self.add_proc_environ(pid, extraenv)
  +self.add_proc_environ(pid, proc_pid_fd, extraenv)
   self['ProcStatus'] = _read_file('status', dir_fd=proc_pid_fd)
   self['ProcCmdline'] = _read_file('cmdline', 
dir_fd=proc_pid_fd).rstrip('\0')
   self['ProcMaps'] = 

[Touch-packages] [Bug 1850122] Re: ubuntu-bug lightdm no password box

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  ubuntu-bug lightdm no password box

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  As explained in this topic

  https://discourse.ubuntubudgie.org/t/updated-to-19-10-lock-screen-
  problem/2597

  The PC after waking up from sleep there is no password box in the screen to 
resume work.
  So far this problem is seen in Ubuntu Budgie and Solus Budgie.

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

-- 
Mailing list: https://launchpad.net/~touch-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

[Francis Ginther]

** Tags added: id-5dbb311b74e3f364d8f98c56

-- 
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 1849156] Re: systemd-timesyncd.service broken on upgrade to 19.10 if ntp was installed

[Francis Ginther]

** Tags added: id-5dbb33265d09bf5e5d2ca5df

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

Title:
  systemd-timesyncd.service broken on upgrade to 19.10 if ntp was
  installed

Status in ntp package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Confirmed
Status in ntp source package in Eoan:
  New
Status in systemd source package in Eoan:
  New
Status in ntp source package in Focal:
  New
Status in systemd source package in Focal:
  Confirmed

Bug description:
  Ubuntu 19.10's systemd package introduced /lib/systemd/system/systemd-
  timesyncd.service.d/disable-with-time-daemon.conf.  This prevents
  systemd-timesyncd.service from starting if the ntp package has been
  installed.  However, ntp.service has a Conflicts directive for
  systemd-timesyncd.service.  If both services are enabled, neither will
  start on boot.  This breaks upgrades from < 19.10 to 19.10 for systems
  that have both ntp and systemd installed.

  Possible workarounds:

  - Uninstall ntp
  - Disable systemd-timesyncd.service

  % lsb_release -rd
  Description:Ubuntu 19.10
  Release:19.10

  % apt-cache policy systemd
  systemd:
Installed: 242-7ubuntu3
Candidate: 242-7ubuntu3
Version table:
   *** 242-7ubuntu3 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/main amd64 
Packages
  100 /var/lib/dpkg/status

  % apt-cache policy ntp
  ntp:
Installed: 1:4.2.8p12+dfsg-3ubuntu2
Candidate: 1:4.2.8p12+dfsg-3ubuntu2
Version table:
   *** 1:4.2.8p12+dfsg-3ubuntu2 500
  500 http://us-east-1.ec2.archive.ubuntu.com/ubuntu eoan/universe 
amd64 Packages
  100 /var/lib/dpkg/status

  % dpkg -S 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
  systemd: 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf

  % sudo systemctl status ntp
  ● ntp.service - Network Time Service
 Loaded: loaded (/lib/systemd/system/ntp.service; enabled; vendor preset: 
enabled)
 Active: inactive (dead)
   Docs: man:ntpd(8)

  % sudo systemctl status systemd-timesyncd.service
  ● systemd-timesyncd.service - Network Time Synchronization
 Loaded: loaded (/lib/systemd/system/systemd-timesyncd.service; enabled; 
vendor preset: enabled)
Drop-In: /lib/systemd/system/systemd-timesyncd.service.d
 └─disable-with-time-daemon.conf
 Active: inactive (dead)
  Condition: start condition failed at Mon 2019-10-21 12:05:38 EDT; 29s ago
   Docs: man:systemd-timesyncd.service(8)

  Oct 21 12:05:38 ubuntu systemd[1]: Condition check resulted in Network
  Time Synchronization being skipped.

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

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

[Touch-packages] [Bug 1850917] [NEW] QT apps have differing scaling on dual monitor setup

[Matthias]

Public bug reported:

I have a dual monitor setup with Nvidia Geforce GT1030. The card has a HDMI and 
a Display port output. Both displays are attached to different monitor brands 
with the same resolution. Gnome apps scale the same on both displays, but some 
QT apps like Backintime 1.2.1 or rstudio 1.2.1 have different scales on both 
displays.
Scaling changes when apps are moved on the desktop from one screen to the other.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
.proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03: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  430.26  Tue Jun  4 17:40:52 
CDT 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.8
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  1 11:51:46 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 430.26, 4.15.0-66-generic, x86_64: installed
 nvidia, 430.26, 5.0.0-31-generic, x86_64: installed
 nvidia, 430.26, 5.0.0-32-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP108 [GeForce GT 1030] [10de:1d01] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GP108 [GeForce GT 1030] [1043:8621]
InstallationDate: Installed on 2019-09-06 (55 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805)
MachineType: Dell Inc. OptiPlex 790
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=UUID=d079c1c3-6df2-4c44-89d8-a5b8462e9eeb ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/30/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0HY9JP
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd12/30/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA01:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 790
dmi.product.version: 01
dmi.sys.vendor: Dell 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.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
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 qt 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/1850917

Title:
  QT apps have differing scaling on dual monitor setup

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a dual monitor setup with Nvidia Geforce GT1030. The card has a HDMI 
and a Display port output. Both displays are attached to different monitor 
brands with the same resolution. Gnome apps scale the same on both displays, 
but some QT apps like Backintime 1.2.1 or rstudio 1.2.1 have different scales 
on both displays.
  Scaling changes when apps are moved on the desktop from one screen to the 
other.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  .proc.driver.nvidia.gpus..03.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:03: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  430.26  Tue Jun  4 17:40:52 
CDT 2019
   GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
  ApportVersion: 2.20.9-0ubuntu7.8
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  

[Touch-packages] [Bug 1850775] Re: DNS info is not loaded by dhclient

[Pengpeng Sun]

Thanks Till, which systemd service's dependency got changed?

I compared /lib/systemd/system/systemd-resolved.conf between 18.04 and
19.10, they are same. There is "After=systemd-sysusers.service systemd-
networkd.service".

I do NOT know when and who triggers /etc/dhcp/dhclient-enter-
hooks.d/resolved script at boot, but it's possible that when this script
executed, systemd-resolved.service is not ready for reload or restart.

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

Title:
  DNS info is not loaded by dhclient

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Hi Team,

  Could you please help to confirm if this is an issue on Ubuntu19.10
  Desktop?

  1. Update /etc/dhcp/dhclient.conf file to include below 2 new lines.
 supersede domain-name "vmware.com";
 supersede domain-name-servers 10.117.0.1;

  2. Reboot

  3. check DNS info by "systemd-resolve --status", the DNS domain and
  server is not set. But /run/systemd/resolved.conf.d/isc-
  dhcp-v4-ens160.conf contains the new DNS domain and server.

  4. Manually run "systemctl try-reload-or-restart systemd-
  resolved.service" and then DNS is set correctly, "systemd-resolve
  --status" output have the new DNS domain and server.

  
  I tried the same steps on Ubuntu18.04 Desktop, no such issue. DNS updated 
correctly after reboot.

  Thanks,
  Pengpeng

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

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

[Touch-packages] [Bug 1850874] Re: gnome-shell 100% CPU usage on all cores when animated gif is displayed

[Daniel van Vugt]

I'm not sure what changed to make 19.10 heavier than 19.04, but I can
explain what you are seeing.

What you are seeing is an OpenGL-based application (Firefox or Chromium)
that is being forced to update its entire window constantly. Since it is
OpenGL-based, gnome-shell does not have the opportunity to identify just
the small area of the screen that is changing, but has to update the
entire application window at full frame rate. To do that in software
without a GPU is expected to use a lot of CPU and multiple threads,
sorry.


** Summary changed:

- gnome-shell 100% CPU usage on all cores when animated gif is displayed
+ gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU cores just 
to update the screen

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => Low

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Triaged

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

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

** Changed in: mesa (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  gnome-shell (via Mesa/LLVMpipe in a virtual machine) uses all CPU
  cores just to update the screen

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

Bug description:
  This started to happen with Ubuntu 19.10.

  When an animated gif is displayed in a browser, gnome-shell begins
  using 100% CPU on all cores.

  To reproduce:

  1) open Firefox, or Chromium

  2) load an URL where an animated gif is displayed - you can also use
  this direct link to https://i.stack.imgur.com/h6viz.gif

  3) gnome-shell will start using 100% CPU on all cores (as long as 
Firefox/Chromium window is in the foreground)
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.1
  Architecture: amd64
  DisplayManager: gdm3
  DistroRelease: Ubuntu 19.10
  GsettingsChanges:
   
  InstallationDate: Installed on 2019-05-12 (172 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  Package: gnome-shell 3.34.1-1ubuntu1
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1
  RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1
  Tags:  eoan
  Uname: Linux 5.3.0-19-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-10-16 (15 days ago)
  UserGroups:
   
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

[Daniel van Vugt]

Switching on connect is an intentional design choice for Ubuntu. It's
been like that for a few years although PulseAudio 13.0 in Ubuntu 19.10
has introduced extra sensitivity with respect to HDMI events...

If you would like to disable it then please just comment out this line:

  load-module module-switch-on-connect

in /etc/pulse/default.pa

So this isn't a bug, but it does seem to overlap with bug 1847570 so
please see that too.

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

** Tags added: eoan

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

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

[Touch-packages] [Bug 1850887] Re: Audio / Sound reverts to HDMI when power event occurs

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1847570, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.

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

Title:
  Audio / Sound reverts to HDMI when power event occurs

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  PulseAudio reverts the sound to HDMI all the time when a HDMI related
  power event occurs. That means, although I have set another USB sound
  device plugged in and set as default under sound settings, when an
  application like Kodi or the system shuts off the HDMI monitor and I
  reactivate the monitor, the sound is set to HDMI output again and
  again.

  That probably has to do with the fix to the reported Bug # 1711101 and
  definitely not happened at Ubuntu 19.04. I switched to Ubuntu 19.10
  two days ago.

  Setting the USB device as default does not help, even when done by
  PulseAudio mixer (gui) and removing HDMI output from the alternatives
  option.

  Expected behavior:
  PulseAudio keeps the sound setting to the selected device

  Actual behavior: 
  PulseAudio changes to HDMI at every HDMI power event

  Annoying manual workaround:
  Setting the desired Audio option on the control panel after every HDMI power 
event again

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Component: pulseaudio
  Version: 1:13.0-1ubuntu1

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

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