date:20191022

You have been subscribed to a public bug:

# lsinitramfs /boot/initrd.img-5.3.0-18-generic | fgrep usr/lib/modprobe.d
usr/lib/modprobe.d
usr/lib/modprobe.d/aliases.conf
usr/lib/modprobe.d/blacklist_linux_5.3.0-13-generic.conf
usr/lib/modprobe.d/blacklist_linux_5.3.0-17-generic.conf
usr/lib/modprobe.d/blacklist_linux_5.3.0-18-generic.conf
usr/lib/modprobe.d/fbdev-blacklist.conf
usr/lib/modprobe.d/systemd.conf

I don't think this is the intended behavior.

The blacklists may have same contents most of the times. But when they
don't, (user changed kernel package/flavor/etc.) this may cause
unexpected issues.

** Affects: initramfs-tools (Ubuntu)
 Importance: Wishlist
 Status: Confirmed


** Tags: eoan
-- 
initramfs contains modprobe blacklist from all installed kernel versions
https://bugs.launchpad.net/bugs/1847946
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to initramfs-tools in Ubuntu.

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

[Touch-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

> * Which values do the environment variables have?

$ env | grep -E 'XMOD|_IM'
GTK_IM_MODULE=ibus
QT4_IM_MODULE=ibus
XMODIFIERS=@im=ibus
CLUTTER_IM_MODULE=ibus
QT_IM_MODULE=ibus
$

I don't know where these are being set, because Xsession is hell.

> * Are you possibly on Wayland?

No.

> * Can you reproduce it on a fresh 19.10 (or with a newly created
user)?

No.

> Assuming that you are on standard Ubuntu, using ibus-setup for
> adding/removing input sources is not the 'right' way

That's not really a satisfactory position, given that the ibus-setup
command is shipped in the ibus package, which is seeded as part of the
Ubuntu Desktop.  If the command should not be used, it should not be
present.

> it's supposed to be done in Settings -> Region & Language (probably not
> significant for this issue, but still...).

I can't find anything under the settings screens that resembles the
selection of input methods presented by ibus-setup.  ibus-setup presents
'Chinese SunPinyin', Settings only presents 'Chinese'; and removing the
Chinese input method from ibus-setup's config doesn't change what's
displayed in Settings (Chinese is still listed here).

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

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  New

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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

[Touch-packages] [Bug 1825940] Re: [graphics] Enable ICL

2019-10-22 Thread quanxian

** Changed in: intel
   Status: Fix Committed => Fix Released

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

Title:
  [graphics] Enable ICL

Status in intel:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in linux-oem-osp1 package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in linux-oem-osp1 source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Ice Lake (ICL) graphics needs to be enabled for OEM OSP1 image which is based 
on 18.04.3 graphics stack with linux-oem-osp1 kernel.

  
  [Test case]
  The usual desktop usage, graphics tests etc.

  
  [Regression potential]
  Linux-oem-osp1 kernel is a new kernel used only on new OEM enablements, and 
it can't regress any currently running system.

  Mesa backports are limited to ICL, so they shouldn't regress earlier
  generations either.

  --

  Original description:

  ICL graphics is not enabled in 19.04.
  if you want to use 19.04 on ICL platform, you need do like this

  Add kernel option
  i915.alpha_support=1

  Target Release:19.10
  Target Kernel: 5.2
  Target Mesa: 19.1

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

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

[Touch-packages] [Bug 1844775] Re: HDR support for Ubuntu

2019-10-22 Thread Gary Wang

For #15, 
Sorry for causing you confusion, just put related HDR patch of Gemini Lake for 
your reference. 

The patch for GLK were in i915 upstream.
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?h=v5.4-rc4&id=44b42ebfccfd9d6ef377a25e99ae0085b071e868

Gary

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

Title:
  HDR support for Ubuntu

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

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

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

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

2019-10-22 Thread Lilian Tao

@hui.wang,

Thanks a lot for the reply.

1)
sudo hdajacksensetest -a
Pin 0x12 (Internal Mic): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x18 (Not connected): present = No
Pin 0x19 (Not connected): present = Yes
Pin 0x1a (Not connected): present = No
Pin 0x1b (Not connected): present = No
Pin 0x1d (Not connected): present = No
Pin 0x1e (Not connected): present = No
Pin 0x21 (Black Headphone, Left side): present = No


2) plug in

3)

 sudo hdajacksensetest -a
Pin 0x12 (Internal Mic): present = No
Pin 0x13 (Not connected): present = No
Pin 0x14 (Internal Speaker): present = No
Pin 0x18 (Not connected): present = No
Pin 0x19 (Not connected): present = Yes
Pin 0x1a (Not connected): present = No
Pin 0x1b (Not connected): present = No
Pin 0x1d (Not connected): present = No
Pin 0x1e (Not connected): present = No
Pin 0x21 (Black Headphone, Left side): present = Yes

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

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

Status in alsa-driver package in Ubuntu:
  Confirmed

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

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

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

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

[Touch-packages] [Bug 1849405] Re: Repeated keypresses from bluetooth keyboard

Please try:

  * Logging into 'Ubuntu' instead of 'Ubuntu on Wayland'. That will mean
key events are first handled by the 'Xorg' process and won't get delayed
or lost by high CPU in the 'gnome-shell' process.

  * Moving away from wifi devices that might be using 2.4GHz
frequencies, as they will interfere with Bluetooth and cause packet
loss, and some resends. I don't know how unique the resends of lost
packets are for Bluetooth keyboards...

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

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

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

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

Title:
  Repeated keypresses from bluetooth keyboard

Status in bluez package in Ubuntu:
  Incomplete
Status in mutter package in Ubuntu:
  Incomplete

Bug description:
  I have a Microsoft Surface bluetooth keyboard, and semi-frequently
  (e.g. around every 10-15mins) end up with repeated keypresses being
  made (e.g. apppt get update).

  This seems to happen when the machine is under slight stress, or when
  a new notification pops up in gnome, so it could be related to wayland
  possibly - but even if wayland or other processes are causing stress,
  I should imagine the bluetooth hid driver should not cause repeated
  key presses.

  Please let me know if you require further information about my
  environment, it's difficult to know where to begin with determining
  which process is the root cause of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Wed Oct 23 09:38:20 2019
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude 7480
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7480
  dmi.product.sku: 07A0
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:63:3F:E9:51:8C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0
TX bytes:605292 acl:98 sco:0 commands:2484 errors:0

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

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

[Touch-packages] [Bug 1849263] Re: Cdrom to CD-ROM

You can close this bug report. I have reported a new one for python-apt
here: #1849406

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

Title:
  Cdrom to CD-ROM

Status in python-apt package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  app Software & Updates > tab Ubuntu Software > section Installable from 
CD-ROM/DVD
  The string "Cdrom with Ubuntu [...]" is wrong! The string must be "CD-ROM 
with Ubuntu [...]". This is present in every Ubuntu since forever. Fix this, 
this is getting ridiculous now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1849263/+subscriptions

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

[Touch-packages] [Bug 1849406] [NEW] Ubuntu 19.10: "Cdrom" to "Physical media"

Public bug reported:

Do this: open the app Software & Updates > select first tab named Ubuntu
Software (if not already by default) > observe section Installable from
CD-ROM/DVD

In those good ol' days, Ubuntu was installable only from a CD and later
from a DVD. Nowadays, USB thumb drives are superceding this, which makes
the whole string wrong, even the title.

So, I propose this:
Installable from physical media
Physical media with Ubuntu [...]

This makes it future-proof as well, since god-knows-what is going to
exist in the future to boot Ubuntu from, but it will be physical media
for sure.

Care to fix this? Also, I would gladly make a PR request to speed up the
process (provided you tell me how).

** Affects: python-apt (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Ubuntu 19.10: "Cdrom" to "Physical media"

Status in python-apt package in Ubuntu:
  New

Bug description:
  Do this: open the app Software & Updates > select first tab named
  Ubuntu Software (if not already by default) > observe section
  Installable from CD-ROM/DVD

  In those good ol' days, Ubuntu was installable only from a CD and
  later from a DVD. Nowadays, USB thumb drives are superceding this,
  which makes the whole string wrong, even the title.

  So, I propose this:
  Installable from physical media
  Physical media with Ubuntu [...]

  This makes it future-proof as well, since god-knows-what is going to
  exist in the future to boot Ubuntu from, but it will be physical media
  for sure.

  Care to fix this? Also, I would gladly make a PR request to speed up
  the process (provided you tell me how).

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1849406/+subscriptions

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

[Touch-packages] [Bug 1849405] [NEW] Repeated keypresses from bluetooth keyboard

2019-10-22 Thread Matt Austin

Public bug reported:

I have a Microsoft Surface bluetooth keyboard, and semi-frequently (e.g.
around every 10-15mins) end up with repeated keypresses being made (e.g.
apppt get update).

This seems to happen when the machine is under slight stress, or when a
new notification pops up in gnome, so it could be related to wayland
possibly - but even if wayland or other processes are causing stress, I
should imagine the bluetooth hid driver should not cause repeated key
presses.

Please let me know if you require further information about my
environment, it's difficult to know where to begin with determining
which process is the root cause of this.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.2
ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
Uname: Linux 5.0.0-32-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Wed Oct 23 09:38:20 2019
InterestingModules: rfcomm bnep btusb bluetooth
MachineType: Dell Inc. Latitude 7480
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/04/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.1
dmi.board.name: 00F6D3
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 7480
dmi.product.sku: 07A0
dmi.sys.vendor: Dell Inc.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: F8:63:3F:E9:51:8C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0
TX bytes:605292 acl:98 sco:0 commands:2484 errors:0

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


** Tags: amd64 apport-bug bionic

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

Title:
  Repeated keypresses from bluetooth keyboard

Status in bluez package in Ubuntu:
  New

Bug description:
  I have a Microsoft Surface bluetooth keyboard, and semi-frequently
  (e.g. around every 10-15mins) end up with repeated keypresses being
  made (e.g. apppt get update).

  This seems to happen when the machine is under slight stress, or when
  a new notification pops up in gnome, so it could be related to wayland
  possibly - but even if wayland or other processes are causing stress,
  I should imagine the bluetooth hid driver should not cause repeated
  key presses.

  Please let me know if you require further information about my
  environment, it's difficult to know where to begin with determining
  which process is the root cause of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.2
  ProcVersionSignature: Ubuntu 5.0.0-32.34~18.04.2-generic 5.0.21
  Uname: Linux 5.0.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Wed Oct 23 09:38:20 2019
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. Latitude 7480
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_AU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-32-generic 
root=/dev/mapper/sarasota--kf--vg-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/04/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.15.1
  dmi.board.name: 00F6D3
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.15.1:bd07/04/2019:svnDellInc.:pnLatitude7480:pvr:rvnDellInc.:rn00F6D3:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude 7480
  dmi.product.sku: 07A0
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: F8:63:3F:E9:51:8C  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:1658613 acl:66750 sco:0 events:15708 errors:0
TX bytes:605292 acl:98 sco:0 commands:2484 errors:0

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

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

[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

We have configured PulseAudio in Ubuntu to prefer newly plugged in audio
devices, which up until 19.04 was uncontroversial. The bug here is that
the new version of PulseAudio thinks logging in with an HDMI/DisplayPort
monitor already attached counts as newly plugged-in.

If you need a workaround then see comment #3.

Upstream is working on it so please keep an eye on:
https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/749

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Eoan:
  Triaged

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

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

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

[Touch-packages] [Bug 1844775] Re: HDR support for Ubuntu

That certainly looks HDR related. But if Ubuntu is to be able to use HDR
then gnome-shell/mutter first should enable use of a deep colour
framebuffer. Actually, for me, that's the only part I care about :) Can
anyone confirm what the minimum Intel GPU required is for 10-bpc?

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

Title:
  HDR support for Ubuntu

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

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

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

[Touch-packages] [Bug 1849263] Re: Cdrom to CD-ROM

I would also argue that in those days, Ubuntu is installable from a USB
thumb drive as well, not just from a CD/DVD as in the good ol' days,
which makes the whole string wrong, even the title.

So, I propose this:
Installable from physical media
Physical media with Ubuntu [...]

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

Title:
  Cdrom to CD-ROM

Status in python-apt package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  app Software & Updates > tab Ubuntu Software > section Installable from 
CD-ROM/DVD
  The string "Cdrom with Ubuntu [...]" is wrong! The string must be "CD-ROM 
with Ubuntu [...]". This is present in every Ubuntu since forever. Fix this, 
this is getting ridiculous now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1849263/+subscriptions

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

[Touch-packages] [Bug 1849399] Re: ibus in 19.10 breaks the delete key, maps to ☭

2019-10-22 Thread Gunnar Hjalmarsson

Hi Steve,

I can't reproduce it here (with a Swedish keyboard). Some questions to
start with:

* Which values do the environment variables have?

  env | grep -E 'XMOD|_IM'

* Are you possibly on Wayland?

* Can you reproduce it on a fresh 19.10 (or with a newly created user)?

Assuming that you are on standard Ubuntu, using ibus-setup for
adding/removing input sources is not the 'right' way - it's supposed to
be done in Settings -> Region & Language (probably not significant for
this issue, but still...).

GNOME always starts IBus if it's installed (and it's installed by
default on Ubuntu).

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

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  Incomplete

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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

[Touch-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices

2019-10-22 Thread Michael Gold

This just started happening to me and I realized its after I used my
headphones in a conference call.  Selecting the headphone input in Sound
Settings silently switched the output profile to HSP/HFD mode.  The only
"bug" here is that when the call ended and I turned off the microphone
(selecting a different input device) it didn't restore A2DP output, so
you have to do it manually.

With that manual selection, "call from" is gone.

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

Title:
  Annoying "call from" message when connecting Bose devices

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

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

[Touch-packages] [Bug 1849399] [NEW] ibus in 19.10 breaks the delete key, maps to ☭

Public bug reported:

After upgrade to 19.10, I found that my Delete key was not working as a
Delete key, but that instead if I hit Delete twice it would print the
character ☭.

Since others were not reporting this issue, I had a look around at my
input config and remembered that I had ibus configured from a long time
ago in order to support Chinese input.

If I disable ibus (either by unsetting the environment variables; or by
killing ibus-daemon), then the Delete key works again as expected.

This is a regression in behavior since Ubuntu 19.04, where I had the
same input setup on my desktop but the Delete key worked without
problems.

I'm also not sure how to disable ibus, now that I am in this situation;
or if ibus is expected to always be running.

The problem persists if I run ibus-setup and remove Chinese SunPinyin
from the list of input methods, leaving only "English - English (US)".

** Affects: ibus (Ubuntu)
 Importance: High
 Status: New

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

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

Title:
  ibus in 19.10 breaks the delete key, maps  to ☭

Status in ibus package in Ubuntu:
  New

Bug description:
  After upgrade to 19.10, I found that my Delete key was not working as
  a Delete key, but that instead if I hit Delete twice it would print
  the character ☭.

  Since others were not reporting this issue, I had a look around at my
  input config and remembered that I had ibus configured from a long
  time ago in order to support Chinese input.

  If I disable ibus (either by unsetting the environment variables; or
  by killing ibus-daemon), then the Delete key works again as expected.

  This is a regression in behavior since Ubuntu 19.04, where I had the
  same input setup on my desktop but the Delete key worked without
  problems.

  I'm also not sure how to disable ibus, now that I am in this
  situation; or if ibus is expected to always be running.

  The problem persists if I run ibus-setup and remove Chinese SunPinyin
  from the list of input methods, leaving only "English - English (US)".

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

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

[Touch-packages] [Bug 1848731] Re: Audio output device changes upon unlock/login

*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570

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

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

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

Title:
  Audio output device changes upon unlock/login

Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a ThinkPad X250 and updated To Ubuntu 19.10 today from 19.04.

  
  Locking/Suspending and logging in changes my audio output device.
  This did not happen in 19.04.

  
   How to reproduce 

  When I lock my session with key combination "Win+L" and then unlock it again, 
the sound that's been playing through my headphones/speakers stops playing. 
When I check the audio settings, "HDMI/DisplayPort 2 - Built-in audio" is 
selected.
  When I select "Headphones - Built-in audio", sound continues playing.

  There is no related log output in dmesg.

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

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

[Touch-packages] [Bug 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

2019-10-22 Thread Lonnie Lee Best

I have 2 4K monitors, that do not even have speakers hooked up to them
(but they apparently have Audio Controllers). Ubuntu 19.10 gnome-
control-center chooses one of these speakerless monitors over my
Laptop's built-in speakers on each reboot. It will not persist my
preference.

Screenshot: https://i.stack.imgur.com/kLYWy.png
AskUbuntu: https://askubuntu.com/questions/1183052/

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  New
Status in pulseaudio package in Ubuntu:
  Triaged
Status in pulseaudio source package in Eoan:
  Triaged

Bug description:
  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  I would be good if it would remember this choice so that I have
  to do it only once.

  Or maybe (if that is technically possible)
  just output on both output devices by default - this would be
  even more user friendly for newbies who will have a hard time
  finding the right place to change this (or maybe have UI in the
  volume slider to select outputs if there are more than one?
  But anyway, my immediate concern is that it should just remember
  my choice :)

  Please let me know if I can provide more information. Happy to
  dig into code if needed but I will need some pointers.

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

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

[Touch-packages] [Bug 1849263] Re: Cdrom to CD-ROM

** Changed in: software-properties (Ubuntu)
   Status: New => Opinion

** Changed in: software-properties (Ubuntu)
   Status: Opinion => Invalid

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

Title:
  Cdrom to CD-ROM

Status in python-apt package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  Invalid

Bug description:
  app Software & Updates > tab Ubuntu Software > section Installable from 
CD-ROM/DVD
  The string "Cdrom with Ubuntu [...]" is wrong! The string must be "CD-ROM 
with Ubuntu [...]". This is present in every Ubuntu since forever. Fix this, 
this is getting ridiculous now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1849263/+subscriptions

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

[Touch-packages] [Bug 1849183] Re: Bluetooth devices doesn't get listed while turn off and then on

The log has those warnings
'Bluetooth: hci0: unexpected event for opcode 0x2005'
It's more likely to be a kernel issue

** No longer affects: gnome-bluetooth (Ubuntu)

** No longer affects: gnome-control-center (Ubuntu)

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

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

Title:
  Bluetooth devices doesn't get listed while turn off and then on

Status in linux package in Ubuntu:
  New

Bug description:
  When System Starts, first time Bluetooth devices(Say headphones) get
  connected smoothly. But after a point when headphones get
  disconnected, If I tried to reconnect Bluetooth settings don't list
  the devices. I turned it on/off multiple times but doesn't work. The
  only way that'd work after a system restart. Please can you check into
  this

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-31.33~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-31-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  raghuvar   1999 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 21 23:39:04 2019
  InstallationDate: Installed on 2019-06-30 (113 days ago)
  InstallationMedia:
   
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4WCN43WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 320-15IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr4WCN43WW:bd12/22/2018:svnLENOVO:pn80XL:pvrLenovoideapad320-15IKB:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad320-15IKB:
  dmi.product.family: ideapad 320-15IKB
  dmi.product.name: 80XL
  dmi.product.sku: LENOVO_MT_80XL_BU_idea_FM_ideapad 320-15IKB
  dmi.product.version: Lenovo ideapad 320-15IKB
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1849273] Re: network connection fails to re-establish on resume from suspend

the log has 'wlan0: authentication with ...  timed out' warnings, looks
like rather a kernel/driver/wpasupplicant issue

** Package changed: network-manager (Ubuntu) => linux (Ubuntu)

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

Title:
  network connection fails to re-establish on resume from suspend

Status in linux package in Ubuntu:
  New

Bug description:
  The network connection doesn't reestablish on resume from suspend and
  the laptop has to be restarted.

  Restarting networking or network-manager doesn't make it reconnect
  either.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 09:28:30 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-03 (2239 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2018-01-26 (633 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE   STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connecting  started  limited   enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1844329] Re: Test bug for update-excuse-bionic

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

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

Title:
  Test bug for update-excuse-bionic

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Feel free to close it tomorrow.

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

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

[Touch-packages] [Bug 1383858] Re: expr-simplify optimization slows click/snap policy compilation

2019-10-22 Thread Ivan Baldo

Hello.
Can you guys take a look at this suggestion please?
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1830502/comments/18
Thanks!!!

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

Title:
  expr-simplify optimization slows click/snap policy compilation

Status in AppArmor:
  Triaged
Status in apparmor package in Ubuntu:
  Fix Released
Status in click-apparmor package in Ubuntu:
  Fix Released
Status in apparmor package in Ubuntu RTM:
  Fix Released
Status in click-apparmor package in Ubuntu RTM:
  Fix Released

Bug description:
  AppArmor has several optimization options that can be used to help
  speed up policy compiles for certain types of policy. Currently, we
  are using expr tree simplification option by default, which has
  dramatic affects on policy compiles for the evince profile. However,
  with click profiles not using expr tree simplification (ie, adding the
  '-O no-expr-simplify' option) can improve click policy generation by
  44% (375 vs 210 seconds).

  On Krillin, the difference is even more substantial: 636 vs 233
  seconds (63%).

  Short term for rtm is to to use '-O no-expr-simplify' when compiling
  policy in /var/lib/apparmor/profiles but leave /etc/apparmor.d alone.
  We can do the same with click-apparmor. Note: the fix for bug #1385947
  must be included with this fix.

  The long term fix is to adjust expr tree simplification to be more
  efficient (at least as fast as without) and drop the '-O no-expr-
  simplify' option.

  Justification: apparmor policy recompilation is not expected to happen
  as part of the normal user experience (see bug #1350598 for a lot of
  detail) and it is expected to only happen on upgrades from 14.10 to
  15.04 or to fix very serious apparmor or apparmor policy bugs. None of
  these bugs are currently scheduled for OTA. However, *if* we ever need
  to fix one of these, policy will have to be recompiled.

  Choices:
  1. do nothing for RTM since policy recompiles are expected to be rare, but do 
apply this change to 15.04. Policy is expected to be recompiled on upgrades to 
15.04 and upgrades would use the new option
  2. apply this change in OTA. This is problematic because this change alone 
will trigger a policy recompilation that would not otherwise be needed. 
Optionally, this change could accompany a severe bug fix

  Risk:
  The change consists of a small modification to the apparmor upstart job and a 
change to the arguments click-apparmor gives to apparmor_parser. The risk 
assessment is considered low because of the size of the change and the simple 
test case will immediately indicate if either were applied incorrectly.

  Test case:
  1. run aa-status | wc -l and note the result
  2. install the new apparmor and click-apparmor packages and verify there are 
no errors during installation
  3. reboot
  4. run aa-status | wc -l and compare to '1'
  5. run 'sudo start apparmor' and make sure it finishes in a few seconds

  If they are the same, it indicates the upstart job is properly loading
  the profiles generated by click apparmor.

  While these changes may occur separately, landing them at the same
  time along with a regenerated custom tarball (for preinstalled policy)
  will reduce policy recompiles.

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

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

[Touch-packages] [Bug 1830502] Re: apparmor uses excessive memory leading to oom kill

2019-10-22 Thread Ivan Baldo

The biggest problem is that it isn't easily disabled because it is hardcoded in 
the script instead of being in /etc/apparmor/parser.conf.
Instead of hardcoding, it would had been better to just update that conffile 
and let dpkg update it if the user didn't change it (which is highly likely) or 
on new installs.

In /lib/apparmor/functions we have this:
# LP: #1383858 - expr tree simplification is too slow for some
# policy on 32bit ARM, so disable it for now
cache_extra_args=
if [ -d "$PROFILES_CACHE_VAR" ] && [ "$pdir" = "$PROFILES_VAR" ]; then
cache_extra_args="-O no-expr-simplify"
fi

So now for machines with 2Gib of RAM and Snaps, Ubuntu 18.04 has become 
unusable.
I know the minimum requirements are 4Gib but it did actually work fine with 
2Gib before so it is a bit sad to loose that capability.

My suggestion is to just revert that change and do it in parser.conf
instead, so at least we have the option to easily modify it to retain
some 2Gib support.

Thanks a lot for considering this!!!

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

Title:
  apparmor uses excessive memory leading to oom kill

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  When attempting to load the profile from comment #7, apparmor uses
  excessive amounts of memory leading to being killed by the OOM killer
  and thus the apparmor.service failing.

  Original bug description:

  On Ubuntu 18.04.2 LTS Desktop, after running out of space on my disk,
  my system was unable to finish booting and I had to go into recovery
  mode and remove a number of files before the system would boot. After
  doing so I discovered that now the apparmor.service systemd unit
  always fails to start. I see this in dmesg:

  [ 1066.975360] Out of memory: Kill process 6799 (apparmor_parser) score 796 
or sacrifice child
  [ 1066.975364] Killed process 6799 (apparmor_parser) total-vm:15057348kB, 
anon-rss:15046148kB, file-rss:0kB, shmem-rss:0kB
  [ 1067.406595] oom_reaper: reaped process 6799 (apparmor_parser), now 
anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

  Whenever apparmor.service is attempted to be started by systemd, i.e.
  either on boot, or later with `systemctl start apparmor`.

  The log from journalctl doesn't show any actual issues with any
  profiles just this:

  -- Reboot --
  May 25 17:00:58 systemd[1]: Starting AppArmor initialization...
  May 25 17:00:58 apparmor[1521]:  * Starting AppArmor profiles
  May 25 17:00:58 apparmor[1521]: Skipping profile in /etc/apparmor.d/disable: 
usr.bin.firefox
  May 25 17:00:58 apparmor[1521]: Skipping profile in /etc/apparmor.d/disable: 
usr.sbin.rsyslogd
  May 25 17:01:40 apparmor[1521]:...fail!
  May 25 17:01:40 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  May 25 17:01:40 systemd[1]: apparmor.service: Failed with result 'exit-code'.
  May 25 17:01:40 systemd[1]: Failed to start AppArmor initialization.
  May 25 17:04:53 systemd[1]: Starting AppArmor initialization...
  May 25 17:04:53 apparmor[4747]:  * Starting AppArmor profiles
  May 25 17:04:53 apparmor[4747]: Skipping profile in /etc/apparmor.d/disable: 
usr.bin.firefox
  May 25 17:04:53 apparmor[4747]: Skipping profile in /etc/apparmor.d/disable: 
usr.sbin.rsyslogd
  May 25 17:05:25 apparmor[4747]:...fail!
  May 25 17:05:25 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  May 25 17:05:25 systemd[1]: apparmor.service: Failed with result 'exit-code'.
  May 25 17:05:25 systemd[1]: Failed to start AppArmor initialization.

  I can see that apparmor profiles are active after doing this (using
  aa-status), but it's still troubling that apparmor runs into an issue
  without actually saying what the error is.

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

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

[Touch-packages] [Bug 1849368] Re: apt-get update issues invalid range requests for previously completed downloads

That is, a server would usually respond with 200 ok with the complete
file if it does not support ranges.

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

Title:
  apt-get update issues invalid range requests for previously completed
  downloads

Status in apt package in Ubuntu:
  New

Bug description:
  When an apt-get update fails, for instance due to a mismatch between
  the Release and Packages.gz due to a mirror sync/index update, it
  leaves files in the /var/lib/apt/lists/partial for the distribution:

  15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
   1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
   15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

  In this case both Release and Release.gpg were complete, however when
  running apt-get update again it issues the revalidation requests for
  these resources with Range headers that are the length of the file
  resulting in '416 Requested Range Not Satisfiable':

  GET .../Release HTTP/1.1
  Cache-Control: max-age=0
  Accept: text/*
  Range: bytes=13860-
  If-Range: Tue, 22 Oct 2019 12:50:05 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.6.12)

  HTTP/1.1 416 Requested Range Not Satisfiable

  It appears:

  - There's no way for apt-get to know if the file is complete so this logic 
will always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
  - The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

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

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

[Touch-packages] [Bug 1849368] Re: apt-get update issues invalid range requests for previously completed downloads

RFC 7233 allows clients to send range request without checking whether
the server supports them.

The reason being that servers generally, if they do not support ranges,
be ignoring any range values.

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

Title:
  apt-get update issues invalid range requests for previously completed
  downloads

Status in apt package in Ubuntu:
  New

Bug description:
  When an apt-get update fails, for instance due to a mismatch between
  the Release and Packages.gz due to a mirror sync/index update, it
  leaves files in the /var/lib/apt/lists/partial for the distribution:

  15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
   1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
   15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

  In this case both Release and Release.gpg were complete, however when
  running apt-get update again it issues the revalidation requests for
  these resources with Range headers that are the length of the file
  resulting in '416 Requested Range Not Satisfiable':

  GET .../Release HTTP/1.1
  Cache-Control: max-age=0
  Accept: text/*
  Range: bytes=13860-
  If-Range: Tue, 22 Oct 2019 12:50:05 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.6.12)

  HTTP/1.1 416 Requested Range Not Satisfiable

  It appears:

  - There's no way for apt-get to know if the file is complete so this logic 
will always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
  - The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

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

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

[Touch-packages] [Bug 1830502] Re: apparmor uses excessive memory leading to oom kill

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

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

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

Title:
  apparmor uses excessive memory leading to oom kill

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  When attempting to load the profile from comment #7, apparmor uses
  excessive amounts of memory leading to being killed by the OOM killer
  and thus the apparmor.service failing.

  Original bug description:

  On Ubuntu 18.04.2 LTS Desktop, after running out of space on my disk,
  my system was unable to finish booting and I had to go into recovery
  mode and remove a number of files before the system would boot. After
  doing so I discovered that now the apparmor.service systemd unit
  always fails to start. I see this in dmesg:

  [ 1066.975360] Out of memory: Kill process 6799 (apparmor_parser) score 796 
or sacrifice child
  [ 1066.975364] Killed process 6799 (apparmor_parser) total-vm:15057348kB, 
anon-rss:15046148kB, file-rss:0kB, shmem-rss:0kB
  [ 1067.406595] oom_reaper: reaped process 6799 (apparmor_parser), now 
anon-rss:0kB, file-rss:0kB, shmem-rss:0kB

  Whenever apparmor.service is attempted to be started by systemd, i.e.
  either on boot, or later with `systemctl start apparmor`.

  The log from journalctl doesn't show any actual issues with any
  profiles just this:

  -- Reboot --
  May 25 17:00:58 systemd[1]: Starting AppArmor initialization...
  May 25 17:00:58 apparmor[1521]:  * Starting AppArmor profiles
  May 25 17:00:58 apparmor[1521]: Skipping profile in /etc/apparmor.d/disable: 
usr.bin.firefox
  May 25 17:00:58 apparmor[1521]: Skipping profile in /etc/apparmor.d/disable: 
usr.sbin.rsyslogd
  May 25 17:01:40 apparmor[1521]:...fail!
  May 25 17:01:40 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  May 25 17:01:40 systemd[1]: apparmor.service: Failed with result 'exit-code'.
  May 25 17:01:40 systemd[1]: Failed to start AppArmor initialization.
  May 25 17:04:53 systemd[1]: Starting AppArmor initialization...
  May 25 17:04:53 apparmor[4747]:  * Starting AppArmor profiles
  May 25 17:04:53 apparmor[4747]: Skipping profile in /etc/apparmor.d/disable: 
usr.bin.firefox
  May 25 17:04:53 apparmor[4747]: Skipping profile in /etc/apparmor.d/disable: 
usr.sbin.rsyslogd
  May 25 17:05:25 apparmor[4747]:...fail!
  May 25 17:05:25 systemd[1]: apparmor.service: Main process exited, 
code=exited, status=123/n/a
  May 25 17:05:25 systemd[1]: apparmor.service: Failed with result 'exit-code'.
  May 25 17:05:25 systemd[1]: Failed to start AppArmor initialization.

  I can see that apparmor profiles are active after doing this (using
  aa-status), but it's still troubling that apparmor runs into an issue
  without actually saying what the error is.

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

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

[Touch-packages] [Bug 1849368] Re: apt-get update issues invalid range requests for previously completed downloads

2019-10-22 Thread Danny Thomas

Looking deeper, I think we might also have a backend that's not
correctly handling If-Range and returning the 416 before considering if
the Release file is out of date, which is why we get stuck in a file
size mismatch between Releases and Packages.gz.

Does look like there are maybe some issues around the handling of that
error, and certainly the check for the host supporting range support.

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

Title:
  apt-get update issues invalid range requests for previously completed
  downloads

Status in apt package in Ubuntu:
  New

Bug description:
  When an apt-get update fails, for instance due to a mismatch between
  the Release and Packages.gz due to a mirror sync/index update, it
  leaves files in the /var/lib/apt/lists/partial for the distribution:

  15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
   1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
   15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

  In this case both Release and Release.gpg were complete, however when
  running apt-get update again it issues the revalidation requests for
  these resources with Range headers that are the length of the file
  resulting in '416 Requested Range Not Satisfiable':

  GET .../Release HTTP/1.1
  Cache-Control: max-age=0
  Accept: text/*
  Range: bytes=13860-
  If-Range: Tue, 22 Oct 2019 12:50:05 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.6.12)

  HTTP/1.1 416 Requested Range Not Satisfiable

  It appears:

  - There's no way for apt-get to know if the file is complete so this logic 
will always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
  - The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

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

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

[Touch-packages] [Bug 1849368] Re: apt-get update issues invalid range requests for previously completed downloads

Ah the 416 should be fine if the content range is correct (*/complete
size) then apt should realise that it has a complete file.

If there is an issue somewhere else this might need further
investigation at a later point.

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

Title:
  apt-get update issues invalid range requests for previously completed
  downloads

Status in apt package in Ubuntu:
  New

Bug description:
  When an apt-get update fails, for instance due to a mismatch between
  the Release and Packages.gz due to a mirror sync/index update, it
  leaves files in the /var/lib/apt/lists/partial for the distribution:

  15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
   1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
   15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

  In this case both Release and Release.gpg were complete, however when
  running apt-get update again it issues the revalidation requests for
  these resources with Range headers that are the length of the file
  resulting in '416 Requested Range Not Satisfiable':

  GET .../Release HTTP/1.1
  Cache-Control: max-age=0
  Accept: text/*
  Range: bytes=13860-
  If-Range: Tue, 22 Oct 2019 12:50:05 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.6.12)

  HTTP/1.1 416 Requested Range Not Satisfiable

  It appears:

  - There's no way for apt-get to know if the file is complete so this logic 
will always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
  - The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

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

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

[Touch-packages] [Bug 1849368] Re: apt-get update issues invalid range requests for previously completed downloads

My understanding is that this is a server bug and apt is complying with
the http specification.

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

Title:
  apt-get update issues invalid range requests for previously completed
  downloads

Status in apt package in Ubuntu:
  New

Bug description:
  When an apt-get update fails, for instance due to a mismatch between
  the Release and Packages.gz due to a mirror sync/index update, it
  leaves files in the /var/lib/apt/lists/partial for the distribution:

  15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
   1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
   15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

  In this case both Release and Release.gpg were complete, however when
  running apt-get update again it issues the revalidation requests for
  these resources with Range headers that are the length of the file
  resulting in '416 Requested Range Not Satisfiable':

  GET .../Release HTTP/1.1
  Cache-Control: max-age=0
  Accept: text/*
  Range: bytes=13860-
  If-Range: Tue, 22 Oct 2019 12:50:05 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.6.12)

  HTTP/1.1 416 Requested Range Not Satisfiable

  It appears:

  - There's no way for apt-get to know if the file is complete so this logic 
will always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
  - The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

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

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

[Touch-packages] [Bug 942856] Proposed package removed from archive

The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

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

Title:
  NetworkManager does not support AES-encrypted private keys for WPA
  802.1x authentication

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  In Progress

Bug description:
  * Impact

  Selecting AES-{192,256}-CBC keys to connect isn't working

  * Test case

  1. Start with a working (cleartext or DES-3) private key/cert for a network.  
Set up a connection and verify that everything works.
  2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in 
working-key.pem -out aes-key.pem -aes256" (the output should have a line 
starting with "DEK-Info: AES-256-CBC,")
  3. Delete the settings for the test network and attempt to reconnect using 
the new key. 

  That should work

  * Regression potential

  That's new code for an extra type of keys, it shouldn't impact
  existing options

  --

  NetworkManager does not appear to support private keys encrypted with
  AES.  At the very least, it will not validate such a key in nm-util
  when setting up a WPA 802.1x TLS wifi connection.

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

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

[Touch-packages] [Bug 942856] Proposed package removed from archive

The version of network-manager in the proposed pocket of Bionic that was
purported to fix this bug report has been removed because one or more
bugs that were to be fixed by the upload have failed verification and
been in this state for more than 10 days.

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

Title:
  NetworkManager does not support AES-encrypted private keys for WPA
  802.1x authentication

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  In Progress

Bug description:
  * Impact

  Selecting AES-{192,256}-CBC keys to connect isn't working

  * Test case

  1. Start with a working (cleartext or DES-3) private key/cert for a network.  
Set up a connection and verify that everything works.
  2. Re-encrypt the key with AES-256 with this command: "openssl rsa -in 
working-key.pem -out aes-key.pem -aes256" (the output should have a line 
starting with "DEK-Info: AES-256-CBC,")
  3. Delete the settings for the test network and attempt to reconnect using 
the new key. 

  That should work

  * Regression potential

  That's new code for an extra type of keys, it shouldn't impact
  existing options

  --

  NetworkManager does not appear to support private keys encrypted with
  AES.  At the very least, it will not validate such a key in nm-util
  when setting up a WPA 802.1x TLS wifi connection.

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

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

[Touch-packages] [Bug 1838836] Re: network-manager needs to be restarted frequently

2019-10-22 Thread Chelmite

Till Kamppeter (till-kamppeter) wrote on 2019-08-06:  asking me to post
the full log. I did on 8/08. Nothing has happened on this list for two
months. Is there no solution to this problem?

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

Title:
  network-manager needs to be restarted frequently

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a System 76 serval running Ubuntu 19.04 64-bit. The wifi stops
  working frequently and the network-manager service needs to be
  restarted. It will die on its own, but can be triggered by switching
  wifi 3 times (sometimes more, sometimes fewer)!

  When it is working, I have:
  ```
  % usr/bin/sudo nmcli device
  DEVICE   TYPE  STATE CONNECTION 
  wlp62s0  wifi  connected ATT964 
  p2p-dev-wlp62s0  wifi-p2p  disconnected  -- 
  enp59s0  ethernet  unavailable   -- 
  lo   loopback  unmanaged --   
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
 description: Wireless interface
 product: Wireless 8260
 vendor: Intel Corporation
 physical id: 0
 bus info: pci@:3e:00.0
 logical name: wlp62s0
 version: 3a
 serial: e4:b3:18:e3:11:e7
 width: 64 bits
 clock: 33MHz
 capabilities: pm msi pciexpress bus_master cap_list ethernet 
physical wireless
 configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 ip=192.168.1.64 latency=0 
link=yes multicast=yes wireless=IEEE 802.11
 resources: irq:133 memory:dc20-dc201fff
  % /usr/bin/sudo lspci -vnnn | grep -A 9 Network
  3e:00.0 Network controller [0280]: Intel Corporation Wireless 8260 
[8086:24f3] (rev 3a)
Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010]
Flags: bus master, fast devsel, latency 0, IRQ 133
Memory at dc20 (64-bit, non-prefetchable) [size=8K]
Capabilities: [c8] Power Management version 3
Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
Capabilities: [40] Express Endpoint, MSI 00
Capabilities: [100] Advanced Error Reporting
Capabilities: [140] Device Serial Number e4-b3-18-ff-ff-e3-11-e7
Capabilities: [14c] Latency Tolerance Reporting
  ```
  If I switch between my two wifi routers three times (sometimes more times) 
using the Select Network command on the taskbar, wifi stops working.

  Issuing the commands above yields the following differences:
  ```
  % /usr/bin/sudo nmcli device
  DEVICE   TYPE  STATECONNECTION 
  enp59s0  ethernet  unavailable  -- 
  wlp62s0  wifi  unavailable  -- 
  p2p-dev-wlp62s0  wifi-p2p  unavailable  -- 
  lo   loopback  unmanaged
  
  % /usr/bin/sudo lshw -C network
   ...snip...
*-network
   ...snip...
  configuration: broadcast=yes driver=iwlwifi 
driverversion=5.0.0-21-generic firmware=36.9f0a2d68.0 latency=0 link=no 
multicast=yes wireless=IEEE 802.11
  ```
  /var/log/syslog reports the following after failing to switch wifi networks:
  ```
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): disconnecting for new activation request.
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5482] 
device (wlp62s0): state change: activated -> deactivating (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5485] 
manager: NetworkManager state is now DISCONNECTING
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5548] 
audit: op="connection-activate" uuid="1574892b-31aa-43ae-a67a-bd732876e327" 
name="ATT964" pid=21476 uid=1010 result="success"
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5550] 
device (wlp62s0): state change: deactivating -> disconnected (reason 
'new-activation', sys-iface-state: 'managed')
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): canceled DHCP transaction, DHCP client pid 2181
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5562] 
dhcp4 (wlp62s0): state changed bound -> done
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5572] 
dhcp6 (wlp62s0): canceled DHCP transaction, DHCP client pid 2318
  Jul 16 19:20:32 serval NetworkManager[617]:   [1563330032.5572] 
dhcp6 (wlp62s0): state changed bound -> done
  Jul 16 19:20:32 serval kernel: [209888.953314] wlp62s0: deauthenticating 
from 10:7b:ef:cc:ab:a3 by local choice (Reason: 3=DEAUTH_LEAVING)
  Jul 16 19:20:32 serval wpa_supplicant[667]: wlp62s0: 
CTRL-EVENT

[Touch-packages] [Bug 1849368] Re: apt-get update issues invalid range requests for previously completed downloads

2019-10-22 Thread Danny Thomas

Excuse the slightly bogus filenames in that listing - I manually
redacted our host/distribution details.

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

Title:
  apt-get update issues invalid range requests for previously completed
  downloads

Status in apt package in Ubuntu:
  New

Bug description:
  When an apt-get update fails, for instance due to a mismatch between
  the Release and Packages.gz due to a mirror sync/index update, it
  leaves files in the /var/lib/apt/lists/partial for the distribution:

  15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
   1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
   15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

  In this case both Release and Release.gpg were complete, however when
  running apt-get update again it issues the revalidation requests for
  these resources with Range headers that are the length of the file
  resulting in '416 Requested Range Not Satisfiable':

  GET .../Release HTTP/1.1
  Cache-Control: max-age=0
  Accept: text/*
  Range: bytes=13860-
  If-Range: Tue, 22 Oct 2019 12:50:05 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.6.12)

  HTTP/1.1 416 Requested Range Not Satisfiable

  It appears:

  - There's no way for apt-get to know if the file is complete so this logic 
will always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
  - The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

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

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

[Touch-packages] [Bug 1849368] [NEW] apt-get update issues invalid range requests for previously completed downloads

2019-10-22 Thread Danny Thomas

Public bug reported:

When an apt-get update fails, for instance due to a mismatch between the
Release and Packages.gz due to a mirror sync/index update, it leaves
files in the /var/lib/apt/lists/partial for the distribution:

15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
 1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
 15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

In this case both Release and Release.gpg were complete, however when
running apt-get update again it issues the revalidation requests for
these resources with Range headers that are the length of the file
resulting in '416 Requested Range Not Satisfiable':

GET .../Release HTTP/1.1
Cache-Control: max-age=0
Accept: text/*
Range: bytes=13860-
If-Range: Tue, 22 Oct 2019 12:50:05 GMT
User-Agent: Debian APT-HTTP/1.3 (1.6.12)

HTTP/1.1 416 Requested Range Not Satisfiable

It appears:

- There's no way for apt-get to know if the file is complete so this logic will 
always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
- The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

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

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

Title:
  apt-get update issues invalid range requests for previously completed
  downloads

Status in apt package in Ubuntu:
  New

Bug description:
  When an apt-get update fails, for instance due to a mismatch between
  the Release and Packages.gz due to a mirror sync/index update, it
  leaves files in the /var/lib/apt/lists/partial for the distribution:

  15466565 16 -rw-r--r--   1 root root13860 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release
   1543  4 -rw-r--r--   1 root root  475 Oct 22 12:50 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_Release.gpg
   15471150  0 -rw-r--r--   1 root root0 Oct 22 12:52 
/var/lib/apt/lists/partial/ourhost_internal_repo_dists_main_main_binary-amd64_Packages.gz.FAILED

  In this case both Release and Release.gpg were complete, however when
  running apt-get update again it issues the revalidation requests for
  these resources with Range headers that are the length of the file
  resulting in '416 Requested Range Not Satisfiable':

  GET .../Release HTTP/1.1
  Cache-Control: max-age=0
  Accept: text/*
  Range: bytes=13860-
  If-Range: Tue, 22 Oct 2019 12:50:05 GMT
  User-Agent: Debian APT-HTTP/1.3 (1.6.12)

  HTTP/1.1 416 Requested Range Not Satisfiable

  It appears:

  - There's no way for apt-get to know if the file is complete so this logic 
will always be hit if the file exists 
https://github.com/Debian/apt/blob/master/methods/http.cc#L956-L962
  - The logic for determining whether a server supports range requests is only 
entered if an Accept-Range header exists, however an absence of this header 
means support is not available - 
https://github.com/Debian/apt/blob/master/methods/basehttp.cc#L251

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

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

[Touch-packages] [Bug 1849324] Re: Xorg logs spammed with failed page flip messages

2019-10-22 Thread Timo Aaltonen

that commit is in server-1.20-branch, and eoan has a git snapshot of it
which includes that commit


note that the source is not the modeset driver but 'AMDGPU', which means maybe 
this might help:

https://bugs.freedesktop.org/show_bug.cgi?id=110417

** Bug watch added: freedesktop.org Bugzilla #110417
   https://bugs.freedesktop.org/show_bug.cgi?id=110417

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (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/1849324

Title:
  Xorg logs spammed with failed page flip messages

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  New

Bug description:
  Please read this bug report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1645553

  I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source
  2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these
  messages are still being spammed into my Xorg logs.

  ```
  [  6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily 
unavailable
  [  6794.424] (EE) AMDGPU(0): present flip failed
  [  6794.457] Failed to get FB for flip
  ```

  A potential fix has already been merged here:
  
https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193

  Fedora users already have it. I haven't tested Fedora to see if that
  fixes my problem.

  If that fix is already in Ubuntu, I believe we're talking about a new
  bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1849324/+subscriptions

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

[Touch-packages] [Bug 1732612] Re: Alt+Printscreen not working (doesn't generate keypress event)

2019-10-22 Thread James Mark Chan

Has this been fixed? I'm using Ubuntu 18.04 with gnome desktop and the
ctrl alt print screen is not always reliable. I'm using Shutter as a
work around for the mean while.

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

Title:
  Alt+Printscreen not working (doesn't generate keypress event)

Status in systemd package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed

Bug description:
  Since I have upgraded to Ubuntu 17.10 Alt+PrintScreen doesn't work on
  my computer. I'm using Unity DE, with default settings.

  The problem is not about taking screnshots.

  xev recognizes when I press down the alt key, but nothing happens when
  I press Print Screen with alt being pressed (it does when PrintScreen
  is pressed by itself)

  Here is evtest output when I press Alt+Printscreen:

  # Alt pressed down:
  Event: time 1510817663.883489, -- SYN_REPORT 
  Event: time 1510817663.923476, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.923476, -- SYN_REPORT 
  Event: time 1510817663.963479, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 2
  Event: time 1510817663.963479, -- SYN_REPORT 
  Event: time 1510817663.993036, type 4 (EV_MSC), code 4 (MSC_SCAN), value 70046

  # Print screen pressed
  Event: time 1510817663.993036, -- SYN_REPORT 
  Event: time 1510817664.945032, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0

  # Alt released
  Event: time 1510817664.945032, -- SYN_REPORT 
  Event: time 1510817664.945086, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 1
  Event: time 1510817664.945086, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 1
  Event: time 1510817664.945086, -- SYN_REPORT 
  Event: time 1510817664.945097, type 1 (EV_KEY), code 99 (KEY_SYSRQ), value 0
  Event: time 1510817664.945097, type 1 (EV_KEY), code 56 (KEY_LEFTALT), value 0
  Event: time 1510817664.945097, -- SYN_REPORT 

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: udev 234-2ubuntu12.1
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  CustomUdevRuleFiles: 67-xorg-wizardpen.rules 99-displaylink.rules 
60-vboxdrv.rules 70-snap.core.rules 99-anbox.rules
  Date: Thu Nov 16 08:29:46 2017
  InstallationDate: Installed on 2017-03-26 (234 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Beta amd64 (20170321)
  MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M.
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.13.0-16-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to artful on 2017-10-23 (23 days ago)
  dmi.bios.date: 10/24/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F1
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF1:bd10/24/2012:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ77-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1833479] Re: libjack-jackd2-0 double close on a failure to connect to jackd which causes crashes in multithreaded programs

2019-10-22 Thread Joseph Yasi

jackd2 released version 1.9.13 which includes this fix.

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

Title:
  libjack-jackd2-0 double close on a failure to connect to jackd which
  causes crashes in multithreaded programs

Status in jackd2 package in Ubuntu:
  Confirmed
Status in jackd2 package in Debian:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.04, I started experiencing sporadic
  crashes in kodi when turning my AV receiver on. Ubuntu 19.04 upgraded
  alsa-plugins to 1.1.8. For alsa-plugins >= 1.1.7, the ALSA jack plugin
  is enabled by default in /etc/alsa/conf.d/50-jack.conf.

  The crashes are caused by a race condition when kodi's audio engine
  thread is enumerating the ALSA sound devices, and the udev thread is
  enumerating the udev devices triggered by the sound device add from
  turning the AVR on.

  When enumerating the ALSA jack plugin device, it tries to connect to
  connect to jackd. Since I don't have jackd installed, it fails to
  connect. libjack closes the socket on error, and then closes it again
  in it's cleanup code. Since it's closing the same file descriptor
  twice, it interacts with other threads that have potentially opened
  file descriptors, and causes the crash.

  This same bug could potentially affect other multi-threaded programs
  that enumerate ALSA devices.

  Fix committed upstream:
  
https://github.com/jackaudio/jack2/commit/dad4b5702782eef3bd66e3c3f4fefaaae3571208

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

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

[Touch-packages] [Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

2019-10-22 Thread dann frazier

Unreproducible w/ >= disco versions, so marking them Invalid.

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

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Invalid
Status in gdb source package in Bionic:
  In Progress
Status in gdb source package in Disco:
  Invalid
Status in gdb source package in Eoan:
  Invalid
Status in gdb source package in Focal:
  Invalid

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu).

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested using the above test case on 
amd64, i386 and s390x.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

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

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

[Touch-packages] [Bug 1793410] Re: [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal microphone not working

2019-10-22 Thread James Pollock

The response was “The MIC is bulit into the in mainboard of the unit.”
Does that help? Happy to ask again if that still doesn’t answer your
question.

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

Title:
  [Acer Swift SF315-52, Realtek ALC256, Mic, Internal] Internal
  microphone not working

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recently bought a new Acer Swift 3 laptop and installed Ubuntu 18.04
  on it. Everything works except the internal microphone. I have also
  tested with an external microphone and this didn't work either.

  I have worked my way through all the suggested solutions I could find,
  including trying to reconfigure the pins using hdajacketask. In
  pavucontrol I have options for Internal Microphone and Microphone
  (unplugged) but the internal mic only captures static noise.

  The latest HD-Audio Codec-Specific Models has configurations for
  alc255-acer and alc256 for some other models, but setting options snd-
  hda-intel model=MODEL in /etc/modprobe.d/alsa-base.conf does not solve
  the issue with any of these.

  Some info -

  lspci | grep -I audio:

  00:1f.3 Multimedia audio controller: Intel Corporation Sunrise Point-
  LP HD Audio (rev 21)

  
  cat /proc/asound/cards:

   0 [PCH ]: HDA-Intel - HDA Intel PCH
HDA Intel PCH at 0xdf1a8000 irq 127

  
  dmesg | grep snd:

  [3.944593] snd_hda_core: loading out-of-tree module taints kernel.
  [3.956337] snd_soc_skl: Unknown symbol snd_hdac_display_power (err 0)
  [3.956422] snd_soc_skl: Unknown symbol snd_hdac_i915_exit (err 0)
  [4.000880] snd_hda_intel :00:1f.3: Probing card using HDA DKMS, 
version 0.201808050301~ubuntu18.04.1
  [4.000895] snd_hda_intel :00:1f.3: enabling device ( -> 0002)
  [4.013061] snd_hda_codec_realtek hdaudioC0D0: autoconfig for ALC256: 
line_outs=1 (0x14/0x0/0x0/0x0/0x0) type:speaker
  [4.013063] snd_hda_codec_realtek hdaudioC0D0:speaker_outs=0 
(0x0/0x0/0x0/0x0/0x0)
  [4.013065] snd_hda_codec_realtek hdaudioC0D0:hp_outs=1 
(0x21/0x0/0x0/0x0/0x0)
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:mono: mono_out=0x0
  [4.013066] snd_hda_codec_realtek hdaudioC0D0:inputs:
  [4.013068] snd_hda_codec_realtek hdaudioC0D0:  Mic=0x18
  [4.013069] snd_hda_codec_realtek hdaudioC0D0:  Internal Mic=0x12

  
  info on node 12 from cat /proc/asound/card*/codec\#*:

  Node 0x12 [Pin Complex] wcaps 0x40040b: Stereo Amp-In
Control: name="Internal Mic Boost Volume", index=0, device=0
  ControlAmp: chs=3, dir=In, idx=0, ofs=0
Amp-In caps: ofs=0x00, nsteps=0x03, stepsize=0x27, mute=0
Amp-In vals:  [0x02 0x02]
Pincap 0x0020: IN
Pin Default 0x4000: [N/A] Line Out at Ext N/A
  Conn = Unknown, Color = Unknown
  DefAssociation = 0x0, Sequence = 0x0
Pin-ctls: 0x20: IN
Power states:  D0 D1 D2 D3 EPSS
Power: setting=D0, actual=D0

  Let me know if you need any other information.

  James

  ---

  Tags:  bionic
  Uname: Linux 4.15.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  _MarkForUpload: True
  dmi.bios.date: 06/22/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V1.04
  dmi.board.asset.tag: Default string
  dmi.board.name: Erdinger_KL
  dmi.board.vendor: KBL
  dmi.board.version: V1.04
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V1.04
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV1.04:bd06/22/2018:svnAcer:pnSwiftSF315-52:pvrV1.04:rvnKBL:rnErdinger_KL:rvrV1.04:cvnAcer:ct10:cvrV1.04:
  dmi.product.family: Swift 3
  dmi.product.name: Swift SF315-52
  dmi.product.version: V1.04
  dmi.sys.vendor: Acer

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

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

[Touch-packages] [Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

2019-10-22 Thread dann frazier

** Description changed:

  [Impact]
- After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop 
- on breakpoint when running a 32-bit application (on 64-bit Ubuntu). 
+ After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
+ on breakpoint when running a 32-bit application (on 64-bit Ubuntu).
  
  [Test Case]
  This can be reproduced with a simple “hello world” program:
  
  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.
  
  --- (and not stopping nor outputting the text…) ---
  
  [Regression Risk]
- Test case ran on arm64 and regression tested on amd64/i386.
+ Test case ran on arm64 and regression tested using the above test case on 
amd64, i386 and s390x.
  
  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

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

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Invalid
Status in gdb source package in Bionic:
  In Progress
Status in gdb source package in Disco:
  New
Status in gdb source package in Eoan:
  Invalid
Status in gdb source package in Focal:
  Invalid

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu).

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested using the above test case on 
amd64, i386 and s390x.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

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

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

[Touch-packages] [Bug 1848916] Re: software-properties-gtk don't started

2019-10-22 Thread Alex_ander

Hi, no problem
$ software-properties-gtk
Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in 
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 118, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
118, in __init__
self.reload_sourceslist()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
613, in reload_sourceslist
self.distro.get_sources(self.sourceslist)
  File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
(self.id, self.codename))
aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/focal

This is a typical problem at the beginning of testing Ubuntu, but I
decided to leave a report, just in case.

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

Title:
  software-properties-gtk don't started

Status in software-properties package in Ubuntu:
  Incomplete

Bug description:
  Xubuntu 20.04, software-properties-gtk don't started

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: software-properties-gtk 0.98.5
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  Date: Sun Oct 20 11:55:28 2019
  InstallationDate: Installed on 2019-10-07 (12 days ago)
  InstallationMedia: Xubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1848916/+subscriptions

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

[Touch-packages] [Bug 1849263] Re: Cdrom to CD-ROM

2019-10-22 Thread Hans Joachim Desserud

Thanks for reporting.

Looks like these strings in fact originate from python-apt, see for
instance https://git.launchpad.net/ubuntu/+source/python-
apt/tree/data/templates/Ubuntu.info.in#n146

** Also affects: python-apt (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: python-apt (Ubuntu)
   Status: New => Confirmed

** Tags added: eoan focal

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

Title:
  Cdrom to CD-ROM

Status in python-apt package in Ubuntu:
  Confirmed
Status in software-properties package in Ubuntu:
  New

Bug description:
  app Software & Updates > tab Ubuntu Software > section Installable from 
CD-ROM/DVD
  The string "Cdrom with Ubuntu [...]" is wrong! The string must be "CD-ROM 
with Ubuntu [...]". This is present in every Ubuntu since forever. Fix this, 
this is getting ridiculous now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1849263/+subscriptions

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

[Touch-packages] [Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

2019-10-22 Thread Frank Heimes

Tested gdb 8.1-0ubuntu3.2~ppa.1 from ppa:dannf/lp1848200 on s390x and it
works fine.

ubuntu@hwe0002:~$ uname -a
Linux hwe0002 4.15.0-66-generic #75-Ubuntu SMP Tue Oct 1 05:22:41 UTC 2019 
s390x s390x s390x GNU/Linux
ubuntu@hwe0002:~$ gdb hello
GNU gdb (Ubuntu 8.1-0ubuntu3.2~ppa.1) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later 
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "s390x-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
.
Find the GDB manual and other documentation resources online at:
.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from hello...done.
(gdb) b hello.c:5
Breakpoint 1 at 0x740: file hello.c, line 5.
(gdb) run
Starting program: /home/ubuntu/hello 

Breakpoint 1, main () at hello.c:5
5  printf("Hello, World!");
(gdb) quit

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Invalid
Status in gdb source package in Bionic:
  In Progress
Status in gdb source package in Disco:
  Confirmed
Status in gdb source package in Eoan:
  Invalid
Status in gdb source package in Focal:
  Invalid

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop 
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu). 

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested on amd64/i386.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

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

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

[Touch-packages] [Bug 1846290] Re: Ubuntu 19.10 incorrectly selects audio output source

*** This bug is a duplicate of bug 1847570 ***
https://bugs.launchpad.net/bugs/1847570

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

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

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

Title:
  Ubuntu 19.10 incorrectly selects audio output source

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have two monitors hooked up to an AMD RX570 via displayport.  In the
  sound settings they appear as "Ellesmere HDMI Audio [Radeon RX
  470/480/560/570/580/590]" and Ubuntu 19.10 selected one of them as the
  output device by default.  My speakers are connected to a green mini-
  jack line out jack on the motherboard.  Switching to line out gives me
  sound, and I have no other issues.

  Originally, I had upgraded to the beta from the command line in 19.04.
  I had not experienced this issue in 19.04, but upon first booting into
  19.10, I had to switch output device back to line out.  A fresh
  install of the beta iso gave the same result (one of my monitors
  connected to my video card was selected by default).  Note that my
  monitors are Dell U2415s but they do have line out jacks.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bick   1719 F pulseaudio
   /dev/snd/controlC0:  bick   1719 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct  2 00:19:28 2019
  InstallationDate: Installed on 2019-10-02 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] - HDA 
ATI HDMI
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bick   1719 F pulseaudio
   /dev/snd/controlC0:  bick   1719 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [System Product Name, ATI R6xx HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/12/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1820
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B450-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1820:bd09/12/2019:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB450-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.sku: SKU
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Touch-packages] [Bug 1848617] Re: cloud-init configures network incorrectly on the ubuntu1804 template VM of Azure

2019-10-22 Thread Dan Watkins

Hi!

I believe this is an issue with ifupdown, rather than cloud-init.  As
such, I've added an ifupdown task and marked cloud-init's task as
Invalid.  If it's determined that we won't fix this in ifupdown, then
please move the cloud-init task back to New and we can consider working
around this in cloud-init.

In the meantime, you'll have to modify /etc/network/interfaces yourself
to perform the sourcing.


Thanks!

Dan

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

** Summary changed:

- cloud-init configures network incorrectly on the ubuntu1804 template VM of 
Azure
+ Installing ifupdown on bionic does not install a /etc/network/interfaces that 
sources /etc/network/interfaces.d/*

** Changed in: cloud-init
   Status: New => Invalid

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

Title:
  Installing ifupdown on bionic does not install a
  /etc/network/interfaces that sources /etc/network/interfaces.d/*

Status in cloud-init:
  Invalid
Status in ifupdown package in Ubuntu:
  New

Bug description:
  For the ubuntu1804 template VM of Azure, the file /etc/network/interfaces 
lacks a line:
  source /etc/network/interfaces.d/*
  So the VM can't get configurations under /etc/network/interfaces.d/
  After installing ifupdown on the VM, cloud-init will rewrite file 
/etc/network/interfaces.d/50-cloud-init.cfg rather than 
/etc/netplan/50-cloud-init.yaml, but 
/etc/network/interfaces.d/50-cloud-init.cfg won't take effect.

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

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

[Touch-packages] [Bug 1849261] Re: Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= and Restart=

** Summary changed:

- Update systemd for ubuntu 18.04 with requested fix.
+ Update systemd for ubuntu 18.04 with fix for interaction between OnFailure= 
and Restart=

** Description changed:

- Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386 ppc64el 
s390x is available,
- version 238 contains 9298 commits
- version 239 contains 7690 commits
- version 240 contains 4081 commits
+ Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386
+ ppc64el s390x is available,
  
  The pull request for 240 is now requested to backport to 237 for Ubuntu
  18.04, which is integrated within the IBM product.
  
  Pull request: https://github.com/systemd/systemd/pull/9158

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

Title:
  Update systemd for ubuntu 18.04 with fix for interaction between
  OnFailure= and Restart=

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386
  ppc64el s390x is available,

  The pull request for 240 is now requested to backport to 237 for
  Ubuntu 18.04, which is integrated within the IBM product.

  Pull request: https://github.com/systemd/systemd/pull/9158

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

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

** Also affects: ntp (Ubuntu Eoan)
   Importance: Undecided
   Status: New

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

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

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 1849324] [NEW] Xorg logs spammed with failed page flip messages

2019-10-22 Thread Douglas Silva

Public bug reported:

Please read this bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1645553

I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source
2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these
messages are still being spammed into my Xorg logs.

```
[  6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily unavailable
[  6794.424] (EE) AMDGPU(0): present flip failed
[  6794.457] Failed to get FB for flip
```

A potential fix has already been merged here:
https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193

Fedora users already have it. I haven't tested Fedora to see if that
fixes my problem.

If that fix is already in Ubuntu, I believe we're talking about a new
bug.

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

** Attachment added: "The Xorg log file, currently 15 MB large"
   https://bugs.launchpad.net/bugs/1849324/+attachment/5299212/+files/Xorg.0.log

** Description changed:

- This bug has already been discussed here:
+ Please read this bug report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1645553
  
  I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source
  2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these
  messages are still being spammed into my Xorg logs.
  
  ```
  [  6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily 
unavailable
  [  6794.424] (EE) AMDGPU(0): present flip failed
  [  6794.457] Failed to get FB for flip
  ```
  
  A fix has already been merged here:
  
https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193
  
  Fedora users already have it. I haven't tested Fedora to see if that
  fixes my problem.
  
  If that fix is already in Ubuntu, I believe we're talking about a new
  bug.

** Description changed:

  Please read this bug report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1645553
  
  I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source
  2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these
  messages are still being spammed into my Xorg logs.
  
  ```
  [  6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily 
unavailable
  [  6794.424] (EE) AMDGPU(0): present flip failed
  [  6794.457] Failed to get FB for flip
  ```
  
- A fix has already been merged here:
+ A potential fix has already been merged here:
  
https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193
  
  Fedora users already have it. I haven't tested Fedora to see if that
  fixes my problem.
  
  If that fix is already in Ubuntu, I believe we're talking about a new
  bug.

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

Title:
  Xorg logs spammed with failed page flip messages

Status in xorg package in Ubuntu:
  New

Bug description:
  Please read this bug report:
  https://bugzilla.redhat.com/show_bug.cgi?id=1645553

  I'm running Ubuntu MATE 19.10 Eoan, currently with xorg-server-source
  2:1.20.5+git20191008-0ubuntu1 (xorg 1:7.7+19ubuntu12), and these
  messages are still being spammed into my Xorg logs.

  ```
  [  6794.424] (WW) AMDGPU(0): Page flip failed: Resource temporarily 
unavailable
  [  6794.424] (EE) AMDGPU(0): present flip failed
  [  6794.457] Failed to get FB for flip
  ```

  A potential fix has already been merged here:
  
https://gitlab.freedesktop.org/xorg/xserver/commit/26fe29f4fa53cbb7d51892e2cf397c084093812f?merge_request_iid=193

  Fedora users already have it. I haven't tested Fedora to see if that
  fixes my problem.

  If that fix is already in Ubuntu, I believe we're talking about a new
  bug.

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

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

disable-with-time-daemon.conf was reintroduced after observing the regression 
reported at:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902026

The final solution is being discussed at
https://github.com/systemd/systemd/issues/7104 .

I'm tempted to just split systemd-timesyncd to a separate package and
let .deb Conflicts take care of this. @xnox, what do you think?

** Bug watch added: Debian Bug tracker #902026
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=902026

** Bug watch added: github.com/systemd/systemd/issues #7104
   https://github.com/systemd/systemd/issues/7104

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

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

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

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

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

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 1849298] Re: unattended-upgrade is checking o=UbuntuESM, a=eoan-security when disabled in config

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Invalid

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

Title:
  unattended-upgrade is checking o=UbuntuESM,a=eoan-security when
  disabled in config

Status in unattended-upgrades package in Ubuntu:
  Invalid

Bug description:
  My /etc/apt/apt.conf.d/50unattended-upgrades file looks like this:

  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  //  "${distro_id}ESM:${distro_codename}";
  //  "${distro_id}ESM:${distro_codename}-security";
  "${distro_id}:${distro_codename}-updates";
  "${distro_id}:${distro_codename}-proposed";
  "${distro_id}:${distro_codename}-backports";
  };

  Nevertheless, the logs show that o=UbuntuESM,a=eoan-security is
  allowed for updates despite not being enabled in config:

  2019-10-22 08:10:46,075 INFO Initial blacklist :
  2019-10-22 08:10:46,077 INFO Initial whitelist:
  2019-10-22 08:10:46,077 INFO Starting unattended upgrades script
  2019-10-22 08:10:46,077 INFO Allowed origins are: o=Ubuntu,a=eoan, 
o=Ubuntu,a=eoan-security, o=Ubuntu,a=eoan-updates, o=Ubuntu,a=eoan-proposed, 
o=Ubuntu,a=eoan-backports, o=UbuntuESM,a=eoan-security

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

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

[Touch-packages] [Bug 1848969] Re: src/date-time.cpp:171:GDateTime* unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

Could you get a backtrace using gdb?

** Tags added: rls-ee-incoming rls-ff-incoming

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

Title:
  src/date-time.cpp:171:GDateTime*
  unity::indicator::datetime::DateTime::get() const: assertion failed:
  (m_dt)

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Ubuntu 19.10, indicator-datetime
  15.10+19.10.20190819.1-0ubuntu1 crashes right from the start:

  $ /usr/lib/x86_64-linux-gnu/indicator-datetime/indicator-datetime-service 
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.442: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): Indicator-Datetime-WARNING **: 01:46:35.448: Unrecognized 
TZID: 'Etc/Utc'
  (process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.457: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.457: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  [...]
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libecal-CRITICAL **: 01:46:35.458: 
e_cal_component_datetime_get_value: assertion 'dt != NULL' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  (process:17641): libical-glib-CRITICAL **: 01:46:35.458: i_cal_time_as_timet: 
assertion 'I_CAL_IS_TIME (tt)' failed
  **
  
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)
  Bail out! 
Indicator-Datetime:ERROR:/build/indicator-datetime-P60bPZ/indicator-datetime-15.10+19.10.20190819.1/src/date-time.cpp:171:GDateTime*
 unity::indicator::datetime::DateTime::get() const: assertion failed: (m_dt)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1848969/+subscriptions

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

[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

** Tags removed: rls-ee-incoming

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+subscriptions

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

[Touch-packages] [Bug 1849298] Re: unattended-upgrade is checking o=UbuntuESM, a=eoan-security when disabled in config

2019-10-22 Thread Dominic

Not sure I can close the bug. Nevertheless it's confusing to have this
configuration in two places. Maybe deserves a review.

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

Title:
  unattended-upgrade is checking o=UbuntuESM,a=eoan-security when
  disabled in config

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  My /etc/apt/apt.conf.d/50unattended-upgrades file looks like this:

  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  //  "${distro_id}ESM:${distro_codename}";
  //  "${distro_id}ESM:${distro_codename}-security";
  "${distro_id}:${distro_codename}-updates";
  "${distro_id}:${distro_codename}-proposed";
  "${distro_id}:${distro_codename}-backports";
  };

  Nevertheless, the logs show that o=UbuntuESM,a=eoan-security is
  allowed for updates despite not being enabled in config:

  2019-10-22 08:10:46,075 INFO Initial blacklist :
  2019-10-22 08:10:46,077 INFO Initial whitelist:
  2019-10-22 08:10:46,077 INFO Starting unattended upgrades script
  2019-10-22 08:10:46,077 INFO Allowed origins are: o=Ubuntu,a=eoan, 
o=Ubuntu,a=eoan-security, o=Ubuntu,a=eoan-updates, o=Ubuntu,a=eoan-proposed, 
o=Ubuntu,a=eoan-backports, o=UbuntuESM,a=eoan-security

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

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

[Touch-packages] [Bug 1849298] Re: unattended-upgrade is checking o=UbuntuESM, a=eoan-security when disabled in config

2019-10-22 Thread Dominic

I just realised it's enabled by /etc/apt/apt.conf.d/51ubuntu-advantage-
esm. Closing bug.

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

Title:
  unattended-upgrade is checking o=UbuntuESM,a=eoan-security when
  disabled in config

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  My /etc/apt/apt.conf.d/50unattended-upgrades file looks like this:

  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  //  "${distro_id}ESM:${distro_codename}";
  //  "${distro_id}ESM:${distro_codename}-security";
  "${distro_id}:${distro_codename}-updates";
  "${distro_id}:${distro_codename}-proposed";
  "${distro_id}:${distro_codename}-backports";
  };

  Nevertheless, the logs show that o=UbuntuESM,a=eoan-security is
  allowed for updates despite not being enabled in config:

  2019-10-22 08:10:46,075 INFO Initial blacklist :
  2019-10-22 08:10:46,077 INFO Initial whitelist:
  2019-10-22 08:10:46,077 INFO Starting unattended upgrades script
  2019-10-22 08:10:46,077 INFO Allowed origins are: o=Ubuntu,a=eoan, 
o=Ubuntu,a=eoan-security, o=Ubuntu,a=eoan-updates, o=Ubuntu,a=eoan-proposed, 
o=Ubuntu,a=eoan-backports, o=UbuntuESM,a=eoan-security

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

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

[Touch-packages] [Bug 1849298] [NEW] unattended-upgrade is checking o=UbuntuESM, a=eoan-security when disabled in config

2019-10-22 Thread Dominic

Public bug reported:

My /etc/apt/apt.conf.d/50unattended-upgrades file looks like this:

Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
//  "${distro_id}ESM:${distro_codename}";
//  "${distro_id}ESM:${distro_codename}-security";
"${distro_id}:${distro_codename}-updates";
"${distro_id}:${distro_codename}-proposed";
"${distro_id}:${distro_codename}-backports";
};

Nevertheless, the logs show that o=UbuntuESM,a=eoan-security is allowed
for updates despite not being enabled in config:

2019-10-22 08:10:46,075 INFO Initial blacklist :
2019-10-22 08:10:46,077 INFO Initial whitelist:
2019-10-22 08:10:46,077 INFO Starting unattended upgrades script
2019-10-22 08:10:46,077 INFO Allowed origins are: o=Ubuntu,a=eoan, 
o=Ubuntu,a=eoan-security, o=Ubuntu,a=eoan-updates, o=Ubuntu,a=eoan-proposed, 
o=Ubuntu,a=eoan-backports, o=UbuntuESM,a=eoan-security

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

Title:
  unattended-upgrade is checking o=UbuntuESM,a=eoan-security when
  disabled in config

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  My /etc/apt/apt.conf.d/50unattended-upgrades file looks like this:

  Unattended-Upgrade::Allowed-Origins {
  "${distro_id}:${distro_codename}";
  "${distro_id}:${distro_codename}-security";
  // Extended Security Maintenance; doesn't necessarily exist for
  // every release and this system may not have it installed, but if
  // available, the policy for updates is such that unattended-upgrades
  // should also install from here by default.
  //  "${distro_id}ESM:${distro_codename}";
  //  "${distro_id}ESM:${distro_codename}-security";
  "${distro_id}:${distro_codename}-updates";
  "${distro_id}:${distro_codename}-proposed";
  "${distro_id}:${distro_codename}-backports";
  };

  Nevertheless, the logs show that o=UbuntuESM,a=eoan-security is
  allowed for updates despite not being enabled in config:

  2019-10-22 08:10:46,075 INFO Initial blacklist :
  2019-10-22 08:10:46,077 INFO Initial whitelist:
  2019-10-22 08:10:46,077 INFO Starting unattended upgrades script
  2019-10-22 08:10:46,077 INFO Allowed origins are: o=Ubuntu,a=eoan, 
o=Ubuntu,a=eoan-security, o=Ubuntu,a=eoan-updates, o=Ubuntu,a=eoan-proposed, 
o=Ubuntu,a=eoan-backports, o=UbuntuESM,a=eoan-security

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

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

[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-10-22 Thread Till Kamppeter

Sorry for the late reply, I was on a conference last week.

I installed the PPA now and tested with the reproducer of the initial
posting. This works for me. Also the machine in general seems to work OK
with this version of network-manager.

Thank you very much Dariusz for packaging this version.

So now the 1.10.14 should be removed from -proposed (to avoid need of an
epoch), and the version from the PPA of Dariusz should get uploaded into
-proposed, and then the reporters of the regressions in the 1.10.14 SRU
informed (by comments in their bug reports) for the new SRU being
verified.

Could someone from the release team initiate the process by removing
1.10.14 from -proposed? Thanks.

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

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

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

[Touch-packages] [Bug 1633319] Re: memory leak in indicator-datetime

2019-10-22 Thread Martin Wimpress

** Tags removed: yakkety
** Tags added: rls-ee-incoming

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+subscriptions

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

[Touch-packages] [Bug 1849158] Re: Include the systemd package version in journal output

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

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

Title:
  Include the systemd package version in journal output

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm currently debugging something based on journal output.  I,
  helpfully, know what kernel was running due to this line:

kernel: Linux version 5.3.0-13-generic (buildd@lgw01-amd64-012) (gcc
  version 9.2.1 20190909 (Ubuntu 9.2.1-8ubuntu1)) #14-Ubuntu SMP Tue Sep
  24 02:46:08 UTC 2019 (Ubuntu 5.3.0-13.14-generic 5.3.0)

  but it's not entirely clear which version of systemd was running:

systemd[1]: systemd 242 running in system mode. ()

  Even during in eoan's development cycle, we've had a number of
  different "systemd 242"s that this could be.  In a stable LTS, we'll
  have many more (32 and counting "systemd 237"s in bionic, for
  example).  It would be good if we captured this information in the
  journal somewhere.

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

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

[Touch-packages] [Bug 1849261] Re: Update systemd for ubuntu 18.04 with requested fix.

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

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

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

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

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

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

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

Title:
  Update systemd for ubuntu 18.04 with requested fix.

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  New
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386 ppc64el 
s390x is available,
  version 238 contains 9298 commits
  version 239 contains 7690 commits
  version 240 contains 4081 commits

  The pull request for 240 is now requested to backport to 237 for
  Ubuntu 18.04, which is integrated within the IBM product.

  Pull request: https://github.com/systemd/systemd/pull/9158

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

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

[Touch-packages] [Bug 1849261] Re: Update systemd for ubuntu 18.04 with requested fix.

2019-10-22 Thread Dimitri John Ledkov

We will not be upgrading systemd to a new upstream release in 18.04.

W.r.t.
https://github.com/systemd/systemd/pull/9158
https://github.com/systemd/systemd/issues/8398

I thought we tried to backport that before, let me ping a few people if
that was the case or not.

** Bug watch added: github.com/systemd/systemd/issues #8398
   https://github.com/systemd/systemd/issues/8398

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

Title:
  Update systemd for ubuntu 18.04 with requested fix.

Status in Ubuntu on IBM z Systems:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Within Ubunutu 18.04 systemd 237-3ubuntu10.31: amd64 arm64 armhf i386 ppc64el 
s390x is available,
  version 238 contains 9298 commits
  version 239 contains 7690 commits
  version 240 contains 4081 commits

  The pull request for 240 is now requested to backport to 237 for
  Ubuntu 18.04, which is integrated within the IBM product.

  Pull request: https://github.com/systemd/systemd/pull/9158

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

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

[Touch-packages] [Bug 1848862] Re: HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work

Thank you for the bug report. We regularly backport fixes of systemd for
bugs affecting a broad set of users, but this particular problem affect
only users of this specific laptop model.

Could you please report the problem at systemd upstream to automatically
get Ubuntu fixed, too, when packaging the first fixed upstream release?

There is already a similar problem reported against an other HP EliteBook model:
https://github.com/systemd/systemd/issues/13463


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

** Bug watch added: github.com/systemd/systemd/issues #13463
   https://github.com/systemd/systemd/issues/13463

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

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

Title:
  HP Elitebook 840 G1 - 19.10 - Microphone mute key does not work

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I just installed Ubuntu 19.10 on my HP Elitebook 840 G1. Switching
  from Windows to Ubuntu for personal use.

  The mic does not enable/disable with FN+F8 combo and the light is
  constantly on.

  I found the following solution to my problem. However, I do not know how to 
implement it in Ubuntu 19.10 (new to Ubuntu and generally not as techinical).
  
https://wiki.archlinux.org/index.php/HP_EliteBook_840_G1#Enable_the_microphone_muting_key

  1. Would greatly appreciate if someone could point me to step by step 
instructions to install the code from the link above. I can report back if this 
resolve the issue.
  2. Also, is there a way to incorporate a fix for this issue with HP laptops 
in Ubuntu going forward? When I was searching for a fix, I found this to be a 
widespread issue with various HP laptops and Ubuntu dating back a couple years.

  Many thanks.

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

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

[Touch-packages] [Bug 1844775] Re: HDR support for Ubuntu

2019-10-22 Thread Timo Aaltonen

Still not upstream? We'll have kernel 5.4 in 20.04, and likely won't be
backporting big patchsets like this for it. Sounds like these would have
to wait for the 20.04.2 HWE update in early 2021.. (backported from
20.10)

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

Title:
  HDR support for Ubuntu

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

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

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

[Touch-packages] [Bug 1848200] Re: gdb not stopping on breakpoint in a 32-bit program

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

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

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

Title:
  gdb not stopping on breakpoint in a 32-bit program

Status in gdb package in Ubuntu:
  Invalid
Status in gdb source package in Bionic:
  In Progress
Status in gdb source package in Disco:
  Confirmed
Status in gdb source package in Eoan:
  Invalid
Status in gdb source package in Focal:
  Invalid

Bug description:
  [Impact]
  After upgrading gdb from 8.1-0ubuntu3 to 8.1-0ubuntu3.1, gdb does not stop 
  on breakpoint when running a 32-bit application (on 64-bit Ubuntu). 

  [Test Case]
  This can be reproduced with a simple “hello world” program:

  $ cat hello.c
  #include 
  int main()
  {
     // printf() displays the string inside quotation
     printf("Hello, World!");
     return 0;
  }
  $ gcc -ggdb -m32 hello.c
  $ gdb a.out
  (gdb) b hello.c:5
  Breakpoint 1 at 0x536: file hello.c, line 5.
  (gdb) run
  Starting program: /home/user/sandbox/a.out
  warning: Breakpoint address adjusted from 0xf7fd9be0 to 0xf7fd9be0.
  warning: Breakpoint address adjusted from 0xf7fda195 to 0xf7fda195.
  warning: Breakpoint address adjusted from 0xf7fdbd1c to 0xf7fdbd1c.
  warning: Breakpoint address adjusted from 0xf7fdb924 to 0xf7fdb924.
  warning: Breakpoint address adjusted from 0xf7fe99b3 to 0xf7fe99b3.
  warning: Breakpoint address adjusted from 0xf7fea401 to 0xf7fea401.
  warning: Breakpoint address adjusted from 0xf7fea706 to 0xf7fea706.

  --- (and not stopping nor outputting the text…) ---

  [Regression Risk]
  Test case ran on arm64 and regression tested on amd64/i386.

  This regression was fixed on the upstream gdb-8.1 branch within a few
  weeks of the breakage back in May 2018. Since then there have been no
  other fixes in this area on that branch, implying this fixed the issue
  and there were no further regressions discovered.

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

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

[Touch-packages] [Bug 1848865] Re: Spurious "key_press_event" when focus on entry widget using LANG=th_TH.UTF-8

2019-10-22 Thread Ratchanan Srirattanamet

** Bug watch added: gitlab.gnome.org/GNOME/gtk/issues #2216
   https://gitlab.gnome.org/GNOME/gtk/issues/2216

** Also affects: gtk via
   https://gitlab.gnome.org/GNOME/gtk/issues/2216
   Importance: Unknown
   Status: Unknown

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

Title:
  Spurious "key_press_event" when focus on entry widget using
  LANG=th_TH.UTF-8

Status in GTK+:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  GTK+3 will emit spurious "key_press_event" if the focus is currently
  on "GtkEntry" and the locale is set to th_TH.UTF-8. This issue seems
  to disappear if the locale is set to something else (tested with
  C.UTF-8 and en_US.UTF-8), and the presence of iBus and gnome-shell
  affects this.

  Step to reproduce:
  1. Boot into Xubuntu. Install package "language-pack-th" (for locale) and 
"libgtk-3-dev" for compiling demo program.
  2. Download & compile the demo program "gtk3-entry-keyboard-event" attached 
in this bug. (The program is licensed under MIT.)
  3. Run the program with LANG=th_TH.UTF-8. The window will contain an input 
box on top and a button on the bottom.
  4. Click in the input box, then press a key on the keyboard. The program will 
print one line for each "key_press_event" delivered to the window, with keyval 
and hardware_keycode.

  Expected result: only a single line is printed. For example for "a":
  "window: 0x0061 0x0026"

  Actual result: 
- With LANG=th_TH.UTF-8, two lines are printed. The first line is the above 
line, while the second line has both values as zero: "window: 00 00"
- If, instead, the locale is LANG=C.UTF-8, the program will print only one 
line as expected.
- If iBus is installed and enabled, then 2 lines are printed with both 
lines containing the same code, no matter which locale it runs under.
- If this same program is run in Gnome-based Ubuntu session, then only one 
line is printed no matter which locale it runs under.

  This program is tested on Fedora and Manjaro with the correct result.
  Thus, this issue is Ubuntu-specific.

  I've tested it on Ubuntu 19.10 with pretty much the same result,
  except the iBus case is now working correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 19 18:06:23 2019
  InstallationDate: Installed on 2018-05-03 (533 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1848865] Re: Spurious "key_press_event" when focus on entry widget using LANG=th_TH.UTF-8

2019-10-22 Thread Bug Watch Updater

** Changed in: gtk
   Status: Unknown => New

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

Title:
  Spurious "key_press_event" when focus on entry widget using
  LANG=th_TH.UTF-8

Status in GTK+:
  New
Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  GTK+3 will emit spurious "key_press_event" if the focus is currently
  on "GtkEntry" and the locale is set to th_TH.UTF-8. This issue seems
  to disappear if the locale is set to something else (tested with
  C.UTF-8 and en_US.UTF-8), and the presence of iBus and gnome-shell
  affects this.

  Step to reproduce:
  1. Boot into Xubuntu. Install package "language-pack-th" (for locale) and 
"libgtk-3-dev" for compiling demo program.
  2. Download & compile the demo program "gtk3-entry-keyboard-event" attached 
in this bug. (The program is licensed under MIT.)
  3. Run the program with LANG=th_TH.UTF-8. The window will contain an input 
box on top and a button on the bottom.
  4. Click in the input box, then press a key on the keyboard. The program will 
print one line for each "key_press_event" delivered to the window, with keyval 
and hardware_keycode.

  Expected result: only a single line is printed. For example for "a":
  "window: 0x0061 0x0026"

  Actual result: 
- With LANG=th_TH.UTF-8, two lines are printed. The first line is the above 
line, while the second line has both values as zero: "window: 00 00"
- If, instead, the locale is LANG=C.UTF-8, the program will print only one 
line as expected.
- If iBus is installed and enabled, then 2 lines are printed with both 
lines containing the same code, no matter which locale it runs under.
- If this same program is run in Gnome-based Ubuntu session, then only one 
line is printed no matter which locale it runs under.

  This program is tested on Fedora and Manjaro with the correct result.
  Thus, this issue is Ubuntu-specific.

  I've tested it on Ubuntu 19.10 with pretty much the same result,
  except the iBus case is now working correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 19 18:06:23 2019
  InstallationDate: Installed on 2018-05-03 (533 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1844775] Re: HDR support for Ubuntu

2019-10-22 Thread Gary Wang

For related commits of i915's HDR support with Gemini Lake,
https://github.com/freedesktop/drm-tip/c...85b071e868
https://patchwork.freedesktop.org/series/25091/#rev15

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

Title:
  HDR support for Ubuntu

Status in ffmpeg package in Ubuntu:
  Fix Released
Status in intel-media-driver package in Ubuntu:
  Fix Released
Status in libva package in Ubuntu:
  Fix Released
Status in mesa package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Triaged
Status in weston package in Ubuntu:
  Confirmed

Bug description:
  This is a tracker bug for getting HDR support integrated in Ubuntu.

  Kernel
  i915:
  - 5.3 (Ice Lake)
  - plus at least https://patchwork.freedesktop.org/series/65656/
  - gen4+ needs https://patchwork.freedesktop.org/series/63373/
  - so anything beyond initial Ice Lake support will not be in 5.4

  Mesa
  - needs current git master plus
  https://gitlab.freedesktop.org/mesa/mesa/merge_requests/1942

  Mutter:
  https://gitlab.gnome.org/GNOME/mutter/merge_requests/804

  Weston:
  
https://gitlab.freedesktop.org/ajax/weston/commit/591c95ddeb67324778cbbb5d0102bdd1a1721d99

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

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

[Touch-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)

This sounds like it could be related to bug 1711101, which was fixed in
Ubuntu 19.10. Please test Ubuntu 19.10 and tell us if it is still a
problem.

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

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

Title:
No audio after unplugging HDMI (with workaround)

Status in pulseaudio package in Ubuntu:
Incomplete

Bug description:
Background:
My audio used to work correctly. I recently attached the device to my TV
using HDMI. The audio kept playing from laptop's speakers. So, from settings, I
changed the audio output to HDMI. It worked correctly.

Issue:
After removing the cable, I had no audio. I could go to the settings > audio
page, and see that the output was set back to speakers. The test sounds from
the settings worked, but no sound from other apps.

Expected:
System and apps sound to come out of laptop's speakers.

Workaround:
What I did to fix this, was to reattach the HDMI cable to the TV, this time
the audio started automatically playing on the TV (while the first time I had
to explicitly select it). I went to settings > audio and I changed the audio
output (which was now set on HDMI) back to the laptop's speakers. Once
detaching the HDMI, the audio continued working correctly from the speakers
like it used to do.

Summary:
In short, the automatic audio switching for HDMI, is not working correctly,
and especially is not switching properly for applications. Possibly it is just
switching for some low level interface.

Willing to help with triaging and test.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
Uname: Linux 4.15.0-65-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: giorgia1786 F pulseaudio
/dev/snd/controlC2: giorgia1786 F pulseaudio
/dev/snd/controlC1: giorgia1786 F pulseaudio
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Tue Oct 22 10:41:15 2019
InstallationDate: Installed on 2018-09-17 (399 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2018
dmi.bios.vendor: Alienware
dmi.bios.version: A15
dmi.board.name: 068R5X
dmi.board.vendor: Alienware
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A15
dmi.modalias:
dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15:
dmi.product.family: 00
dmi.product.name: Alienware 17
dmi.product.version: A15
dmi.sys.vendor: Alienware

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

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

[Touch-packages] [Bug 1707611] Re: Sound does not automatically switch to HDMI when connected

I think this is fixed in recent releases. Please confirm or just let the
bug expire...

** Changed in: pulseaudio (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Sound does not automatically switch to HDMI when connected

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When connecting a HDMI cable or other audio device, the user must
  manually click on the "sound volume" in the top-right and switch to
  the newly connected device.

  Example: you connect a HDMI cable to the television, but then you must
  manually choose the HDMI sound option; it does not get selected
  automatically.

  Often times e.g. when the HDMI cable is disconnected, the user must
  then manually click on the "speakers" or "line out" setting - EVEN IF
  IT'S ALREADY SELECTED, it must be clicked on again for the sound to
  work through the computer's speakers.

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

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

[Touch-packages] [Bug 1849273] [NEW] network connection fails to re-establish on resume from suspend

2019-10-22 Thread Jean-Baptiste Lallement

Public bug reported:

The network connection doesn't reestablish on resume from suspend and
the laptop has to be restarted.

Restarting networking or network-manager doesn't make it reconnect
either.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: network-manager 1.20.4-2ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Tue Oct 22 09:28:30 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2013-09-03 (2239 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
ProcEnviron:
 TERM=screen-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to focal on 2018-01-26 (633 days ago)
nmcli-nm:
 RUNNING  VERSION  STATE   STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI 
WWAN-HW  WWAN
 running  1.20.4   connecting  started  limited   enabled enabled  
enabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
  network connection fails to re-establish on resume from suspend

Status in network-manager package in Ubuntu:
  New

Bug description:
  The network connection doesn't reestablish on resume from suspend and
  the laptop has to be restarted.

  Restarting networking or network-manager doesn't make it reconnect
  either.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: network-manager 1.20.4-2ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
  Uname: Linux 5.3.0-18-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct 22 09:28:30 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-09-03 (2239 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130902)
  ProcEnviron:
   TERM=screen-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to focal on 2018-01-26 (633 days ago)
  nmcli-nm:
   RUNNING  VERSION  STATE   STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.20.4   connecting  started  limited   enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)

$sudo lshw -C display
  *-display 
   description: VGA compatible controller
   product: GK106M [GeForce GTX 770M]
   vendor: NVIDIA Corporation
   physical id: 0
   bus info: pci@:01:00.0
   version: a1
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress vga_controller bus_master cap_list rom
   configuration: driver=nouveau latency=0
   resources: irq:29 memory:d000-d0ff memory:a000-afff 
memory:b000-b1ff ioport:4000(size=128) memory:d108-d10f
  *-display
   description: VGA compatible controller
   product: 4th Gen Core Processor Integrated Graphics Controller
   vendor: Intel Corporation
   physical id: 2
   bus info: pci@:00:02.0
   version: 06
   width: 64 bits
   clock: 33MHz
   capabilities: msi pm vga_controller bus_master cap_list rom
   configuration: driver=i915 latency=0
   resources: irq:30 memory:d200-d23f memory:c000-cfff 
ioport:5000(size=64) memory:c-d

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

Title:
  No audio after unplugging HDMI (with workaround)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Background:
  My audio used to work correctly. I recently attached the device to my TV 
using HDMI. The audio kept playing from laptop's speakers. So, from settings, I 
changed the audio output to HDMI. It worked correctly.

  Issue:
  After removing the cable, I had no audio. I could go to the settings > audio 
page, and see that the output was set back to speakers. The test sounds from 
the settings worked, but no sound from other apps.

  Expected:
  System and apps sound to come out of laptop's speakers.

  Workaround:
  What I did to fix this, was to reattach the HDMI cable to the TV, this time 
the audio started automatically playing on the TV (while the first time I had 
to explicitly select it). I went to settings > audio and I changed the audio 
output (which was now set on HDMI) back to the laptop's speakers. Once 
detaching the HDMI, the audio continued working correctly from the speakers 
like it used to do.

  Summary:
  In short, the automatic audio switching for HDMI, is not working correctly, 
and especially is not switching properly for applications. Possibly it is just 
switching for some low level interface.


  
  Willing to help with triaging and test.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giorgia1786 F pulseaudio
   /dev/snd/controlC2:  giorgia1786 F pulseaudio
   /dev/snd/controlC1:  giorgia1786 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Oct 22 10:41:15 2019
  InstallationDate: Installed on 2018-09-17 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 068R5X
  dmi.board.vendor: Alienware
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15:
  dmi.product.family: 00
  dmi.product.name: Alienware 17
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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

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

[Touch-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)

$sudo lshw -C multimedia
  *-multimedia  
   description: Audio device
   product: GK106 HDMI Audio Controller
   vendor: NVIDIA Corporation
   physical id: 0.1
   bus info: pci@:01:00.1
   version: a1
   width: 32 bits
   clock: 33MHz
   capabilities: pm msi pciexpress cap_list
   configuration: driver=snd_hda_intel latency=0
   resources: irq:17 memory:d100-d1003fff
  *-multimedia:0
   description: Audio device
   product: Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller
   vendor: Intel Corporation
   physical id: 3
   bus info: pci@:00:03.0
   version: 06
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list
   configuration: driver=snd_hda_intel latency=0
   resources: irq:27 memory:d291-d2913fff
  *-usb
   description: Video
   product: Laptop_Integrated_Webcam_FHD
   vendor: CN0W58PR724873AA07XPA00
   physical id: 5
   bus info: usb@1:1.5
   version: 34.15
   capabilities: usb-2.00
   configuration: driver=uvcvideo maxpower=500mA speed=480Mbit/s
  *-multimedia:1
   description: Audio device
   product: 8 Series/C220 Series Chipset High Definition Audio Controller
   vendor: Intel Corporation
   physical id: 1b
   bus info: pci@:00:1b.0
   version: 05
   width: 64 bits
   clock: 33MHz
   capabilities: pm msi pciexpress bus_master cap_list
   configuration: driver=snd_hda_intel latency=0
   resources: irq:31 memory:d2914000-d2917fff

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

Title:
  No audio after unplugging HDMI (with workaround)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Background:
  My audio used to work correctly. I recently attached the device to my TV 
using HDMI. The audio kept playing from laptop's speakers. So, from settings, I 
changed the audio output to HDMI. It worked correctly.

  Issue:
  After removing the cable, I had no audio. I could go to the settings > audio 
page, and see that the output was set back to speakers. The test sounds from 
the settings worked, but no sound from other apps.

  Expected:
  System and apps sound to come out of laptop's speakers.

  Workaround:
  What I did to fix this, was to reattach the HDMI cable to the TV, this time 
the audio started automatically playing on the TV (while the first time I had 
to explicitly select it). I went to settings > audio and I changed the audio 
output (which was now set on HDMI) back to the laptop's speakers. Once 
detaching the HDMI, the audio continued working correctly from the speakers 
like it used to do.

  Summary:
  In short, the automatic audio switching for HDMI, is not working correctly, 
and especially is not switching properly for applications. Possibly it is just 
switching for some low level interface.


  
  Willing to help with triaging and test.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giorgia1786 F pulseaudio
   /dev/snd/controlC2:  giorgia1786 F pulseaudio
   /dev/snd/controlC1:  giorgia1786 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Oct 22 10:41:15 2019
  InstallationDate: Installed on 2018-09-17 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 068R5X
  dmi.board.vendor: Alienware
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15:
  dmi.product.family: 00
  dmi.product.name: Alienware 17
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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

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

[Touch-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)

Also, in the logs, many of those:

```
snd_hda_intel :01:00.1: Disabling via vga_switcheroo
```
and
```
snd_hda_intel :01:00.1: Enabling via vga_switcheroo
```

from device: "+pci::01:00.1"

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

Title:
  No audio after unplugging HDMI (with workaround)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Background:
  My audio used to work correctly. I recently attached the device to my TV 
using HDMI. The audio kept playing from laptop's speakers. So, from settings, I 
changed the audio output to HDMI. It worked correctly.

  Issue:
  After removing the cable, I had no audio. I could go to the settings > audio 
page, and see that the output was set back to speakers. The test sounds from 
the settings worked, but no sound from other apps.

  Expected:
  System and apps sound to come out of laptop's speakers.

  Workaround:
  What I did to fix this, was to reattach the HDMI cable to the TV, this time 
the audio started automatically playing on the TV (while the first time I had 
to explicitly select it). I went to settings > audio and I changed the audio 
output (which was now set on HDMI) back to the laptop's speakers. Once 
detaching the HDMI, the audio continued working correctly from the speakers 
like it used to do.

  Summary:
  In short, the automatic audio switching for HDMI, is not working correctly, 
and especially is not switching properly for applications. Possibly it is just 
switching for some low level interface.


  
  Willing to help with triaging and test.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giorgia1786 F pulseaudio
   /dev/snd/controlC2:  giorgia1786 F pulseaudio
   /dev/snd/controlC1:  giorgia1786 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Oct 22 10:41:15 2019
  InstallationDate: Installed on 2018-09-17 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 068R5X
  dmi.board.vendor: Alienware
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15:
  dmi.product.family: 00
  dmi.product.name: Alienware 17
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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

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

[Touch-packages] [Bug 1849268] [NEW] No audio after unplugging HDMI (with workaround)

Public bug reported:

Background:
My audio used to work correctly. I recently attached the device to my TV using 
HDMI. The audio kept playing from laptop's speakers. So, from settings, I 
changed the audio output to HDMI. It worked correctly.

Issue:
After removing the cable, I had no audio. I could go to the settings > audio 
page, and see that the output was set back to speakers. The test sounds from 
the settings worked, but no sound from other apps.

Expected:
System and apps sound to come out of laptop's speakers.

Workaround:
What I did to fix this, was to reattach the HDMI cable to the TV, this time the 
audio started automatically playing on the TV (while the first time I had to 
explicitly select it). I went to settings > audio and I changed the audio 
output (which was now set on HDMI) back to the laptop's speakers. Once 
detaching the HDMI, the audio continued working correctly from the speakers 
like it used to do.

Summary:
In short, the automatic audio switching for HDMI, is not working correctly, and 
especially is not switching properly for applications. Possibly it is just 
switching for some low level interface.


Willing to help with triaging and test.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
Uname: Linux 4.15.0-65-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  giorgia1786 F pulseaudio
 /dev/snd/controlC2:  giorgia1786 F pulseaudio
 /dev/snd/controlC1:  giorgia1786 F pulseaudio
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Tue Oct 22 10:41:15 2019
InstallationDate: Installed on 2018-09-17 (399 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/29/2018
dmi.bios.vendor: Alienware
dmi.bios.version: A15
dmi.board.name: 068R5X
dmi.board.vendor: Alienware
dmi.board.version: A03
dmi.chassis.type: 8
dmi.chassis.vendor: Alienware
dmi.chassis.version: A15
dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15:
dmi.product.family: 00
dmi.product.name: Alienware 17
dmi.product.version: A15
dmi.sys.vendor: Alienware

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


** Tags: amd64 apport-bug bionic

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

Title:
  No audio after unplugging HDMI (with workaround)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Background:
  My audio used to work correctly. I recently attached the device to my TV 
using HDMI. The audio kept playing from laptop's speakers. So, from settings, I 
changed the audio output to HDMI. It worked correctly.

  Issue:
  After removing the cable, I had no audio. I could go to the settings > audio 
page, and see that the output was set back to speakers. The test sounds from 
the settings worked, but no sound from other apps.

  Expected:
  System and apps sound to come out of laptop's speakers.

  Workaround:
  What I did to fix this, was to reattach the HDMI cable to the TV, this time 
the audio started automatically playing on the TV (while the first time I had 
to explicitly select it). I went to settings > audio and I changed the audio 
output (which was now set on HDMI) back to the laptop's speakers. Once 
detaching the HDMI, the audio continued working correctly from the speakers 
like it used to do.

  Summary:
  In short, the automatic audio switching for HDMI, is not working correctly, 
and especially is not switching properly for applications. Possibly it is just 
switching for some low level interface.


  
  Willing to help with triaging and test.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giorgia1786 F pulseaudio
   /dev/snd/controlC2:  giorgia1786 F pulseaudio
   /dev/snd/controlC1:  giorgia1786 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Oct 22 10:41:15 2019
  InstallationDate: Installed on 2018-09-17 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 068R5X
  dmi.board.vendor: Alienware
  dm

[Touch-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)

I found the following in the logs:

```
snd_hda_codec_hdmi hdaudioC2D0: out of range cmd 0:7:707:ffbf
```

from device: +hdaudio:hdaudioC2D0

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

Title:
  No audio after unplugging HDMI (with workaround)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Background:
  My audio used to work correctly. I recently attached the device to my TV 
using HDMI. The audio kept playing from laptop's speakers. So, from settings, I 
changed the audio output to HDMI. It worked correctly.

  Issue:
  After removing the cable, I had no audio. I could go to the settings > audio 
page, and see that the output was set back to speakers. The test sounds from 
the settings worked, but no sound from other apps.

  Expected:
  System and apps sound to come out of laptop's speakers.

  Workaround:
  What I did to fix this, was to reattach the HDMI cable to the TV, this time 
the audio started automatically playing on the TV (while the first time I had 
to explicitly select it). I went to settings > audio and I changed the audio 
output (which was now set on HDMI) back to the laptop's speakers. Once 
detaching the HDMI, the audio continued working correctly from the speakers 
like it used to do.

  Summary:
  In short, the automatic audio switching for HDMI, is not working correctly, 
and especially is not switching properly for applications. Possibly it is just 
switching for some low level interface.


  
  Willing to help with triaging and test.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giorgia1786 F pulseaudio
   /dev/snd/controlC2:  giorgia1786 F pulseaudio
   /dev/snd/controlC1:  giorgia1786 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Oct 22 10:41:15 2019
  InstallationDate: Installed on 2018-09-17 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 068R5X
  dmi.board.vendor: Alienware
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15:
  dmi.product.family: 00
  dmi.product.name: Alienware 17
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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

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

[Touch-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)

$lspci -nnk | grep -A2 Audio
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core 
Processor HD Audio Controller [8086:0c0c] (rev 06)
Subsystem: Dell Xeon E3-1200 v3/4th Gen Core Processor HD Audio 
Controller [1028:05aa]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
--
00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset 
High Definition Audio Controller [8086:8c20] (rev 05)
Subsystem: Dell 8 Series/C220 Series Chipset High Definition Audio 
Controller [1028:05aa]
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
--
01:00.1 Audio device [0403]: NVIDIA Corporation GK106 HDMI Audio Controller 
[10de:0e0b] (rev ff)
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel

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

Title:
  No audio after unplugging HDMI (with workaround)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Background:
  My audio used to work correctly. I recently attached the device to my TV 
using HDMI. The audio kept playing from laptop's speakers. So, from settings, I 
changed the audio output to HDMI. It worked correctly.

  Issue:
  After removing the cable, I had no audio. I could go to the settings > audio 
page, and see that the output was set back to speakers. The test sounds from 
the settings worked, but no sound from other apps.

  Expected:
  System and apps sound to come out of laptop's speakers.

  Workaround:
  What I did to fix this, was to reattach the HDMI cable to the TV, this time 
the audio started automatically playing on the TV (while the first time I had 
to explicitly select it). I went to settings > audio and I changed the audio 
output (which was now set on HDMI) back to the laptop's speakers. Once 
detaching the HDMI, the audio continued working correctly from the speakers 
like it used to do.

  Summary:
  In short, the automatic audio switching for HDMI, is not working correctly, 
and especially is not switching properly for applications. Possibly it is just 
switching for some low level interface.


  
  Willing to help with triaging and test.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  giorgia1786 F pulseaudio
   /dev/snd/controlC2:  giorgia1786 F pulseaudio
   /dev/snd/controlC1:  giorgia1786 F pulseaudio
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Tue Oct 22 10:41:15 2019
  InstallationDate: Installed on 2018-09-17 (399 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/29/2018
  dmi.bios.vendor: Alienware
  dmi.bios.version: A15
  dmi.board.name: 068R5X
  dmi.board.vendor: Alienware
  dmi.board.version: A03
  dmi.chassis.type: 8
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: A15
  dmi.modalias: 
dmi:bvnAlienware:bvrA15:bd01/29/2018:svnAlienware:pnAlienware17:pvrA15:rvnAlienware:rn068R5X:rvrA03:cvnAlienware:ct8:cvrA15:
  dmi.product.family: 00
  dmi.product.name: Alienware 17
  dmi.product.version: A15
  dmi.sys.vendor: Alienware

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

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

[Touch-packages] [Bug 1849268] Re: No audio after unplugging HDMI (with workaround)

I also had:

```
snd_hda_codec_hdmi hdaudioC2D0: HDMI: invalid ELD buf size -1
```

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

Title:
No audio after unplugging HDMI (with workaround)

Status in pulseaudio package in Ubuntu:
New

Expected:
System and apps sound to come out of laptop's speakers.

Willing to help with triaging and test.

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

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

[Touch-packages] [Bug 1848865] Re: Spurious "key_press_event" when focus on entry widget using LANG=th_TH.UTF-8

2019-10-22 Thread Ratchanan Srirattanamet

I'll report this upstream. However, as I cannot reproduce it on other
distros, this might as well be an Ubuntu-specific bug.

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

Title:
  Spurious "key_press_event" when focus on entry widget using
  LANG=th_TH.UTF-8

Status in gtk+3.0 package in Ubuntu:
  New

Bug description:
  GTK+3 will emit spurious "key_press_event" if the focus is currently
  on "GtkEntry" and the locale is set to th_TH.UTF-8. This issue seems
  to disappear if the locale is set to something else (tested with
  C.UTF-8 and en_US.UTF-8), and the presence of iBus and gnome-shell
  affects this.

  Step to reproduce:
  1. Boot into Xubuntu. Install package "language-pack-th" (for locale) and 
"libgtk-3-dev" for compiling demo program.
  2. Download & compile the demo program "gtk3-entry-keyboard-event" attached 
in this bug. (The program is licensed under MIT.)
  3. Run the program with LANG=th_TH.UTF-8. The window will contain an input 
box on top and a button on the bottom.
  4. Click in the input box, then press a key on the keyboard. The program will 
print one line for each "key_press_event" delivered to the window, with keyval 
and hardware_keycode.

  Expected result: only a single line is printed. For example for "a":
  "window: 0x0061 0x0026"

  Actual result: 
- With LANG=th_TH.UTF-8, two lines are printed. The first line is the above 
line, while the second line has both values as zero: "window: 00 00"
- If, instead, the locale is LANG=C.UTF-8, the program will print only one 
line as expected.
- If iBus is installed and enabled, then 2 lines are printed with both 
lines containing the same code, no matter which locale it runs under.
- If this same program is run in Gnome-based Ubuntu session, then only one 
line is printed no matter which locale it runs under.

  This program is tested on Fedora and Manjaro with the correct result.
  Thus, this issue is Ubuntu-specific.

  I've tested it on Ubuntu 19.10 with pretty much the same result,
  except the iBus case is now working correctly.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgtk-3-0 3.22.30-1ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-65.74-generic 4.15.18
  Uname: Linux 4.15.0-65-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 19 18:06:23 2019
  InstallationDate: Installed on 2018-05-03 (533 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1848865/+subscriptions

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

[Touch-packages] [Bug 1849263] [NEW] Cdrom to CD-ROM