[Touch-packages] [Bug 1789781] Re: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

2018-08-29 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

** Changed in: initramfs-tools (Ubuntu)
   Importance: Undecided => Low

** Changed in: initramfs-tools (Ubuntu)
   Status: New => Invalid

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

Title:
  package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in initramfs-tools package in Ubuntu:
  Invalid

Bug description:
  start sistem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.11
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Aug 28 10:44:36 2018
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2018-02-07 (203 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1789634] Status changed to Confirmed

2018-08-29 Thread Ubuntu Kernel Bot
This change was made by a bot.

** Changed in: linux (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/1789634

Title:
  computer does not reemerge from hibernate

Status in linux package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  I put the computer in hibernate
  I came back and pressed start button to reawake machine.
  No response.
  Black screen.

  Had to force hard reboot to get machine back to functional status.

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  posting this to systemd as that is power management package (as I understand)
  apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.3
Candidate: 237-3ubuntu10.3
Version table:
   *** 237-3ubuntu10.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 29 14:31:57 2018
  InstallationDate: Installed on 2018-08-24 (4 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Studio 1737
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=2b8227a7-271c-4d4c-8a2b-faa238133be0 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P792H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Studio 1737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1789634] Re: computer does not reemerge from hibernate

2018-08-29 Thread Kai-Heng Feng
** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  computer does not reemerge from hibernate

Status in linux package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I put the computer in hibernate
  I came back and pressed start button to reawake machine.
  No response.
  Black screen.

  Had to force hard reboot to get machine back to functional status.

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  posting this to systemd as that is power management package (as I understand)
  apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.3
Candidate: 237-3ubuntu10.3
Version table:
   *** 237-3ubuntu10.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 29 14:31:57 2018
  InstallationDate: Installed on 2018-08-24 (4 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Studio 1737
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=2b8227a7-271c-4d4c-8a2b-faa238133be0 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P792H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Studio 1737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1789781] [NEW] package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: подпроцесс установлен сценарий post-installation возвратил код ошибки 1

2018-08-29 Thread dmitriy
Public bug reported:

start sistem

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: initramfs-tools 0.122ubuntu8.11
ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Tue Aug 28 10:44:36 2018
ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
InstallationDate: Installed on 2018-02-07 (203 days ago)
InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade:
  подпроцесс установлен сценарий post-installation возвратил код ошибки
  1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  start sistem

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: initramfs-tools 0.122ubuntu8.11
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Tue Aug 28 10:44:36 2018
  ErrorMessage: подпроцесс установлен сценарий post-installation возвратил код 
ошибки 1
  InstallationDate: Installed on 2018-02-07 (203 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.122ubuntu8.11 failed to install/upgrade: 
подпроцесс установлен сценарий post-installation возвратил код ошибки 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1789778] Re: system crash due to snd_hda_intel

2018-08-29 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. It sounds like some part of the system has crashed. To
help us find the cause of the crash please follow these steps:

1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.

2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where
ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine.
Do you find any links to recent problems on that page? If so then please
send the links to us.

3. If step 2 also failed then apply the workaround from bug 994921,
reboot, reproduce the crash, and retry step 1.

Please take care to avoid attaching .crash files to bugs as we are
unable to process them as file attachments. It would also be a security
risk for yourself.


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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  system crash due to snd_hda_intel

Status in Ubuntu:
  Incomplete

Bug description:
  After recent updates my system can suddenly crash. 
  It starts with laggy sound until it completely freezes after which I need to 
do hard reset.

  Crash will happen only while playing Dota 2 (steam) - for now.

  # journalctl -b-1
  ..
  Aug 29 18:56:19 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
snd_pcm_avail() returned a value that is exceptionally large: 500416 bytes 
(2836 ms).
  Aug 29 18:56:19 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report 
this issue to the ALSA developers.
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
snd_pcm_dump():
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Soft volume PCM
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Control: PCM Playback Volume
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
min_dB: -51
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
max_dB: 0
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
resolution: 256
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Its setup is:
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  stream   : PLAYBACK
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  access   : MMAP_INTERLEAVED
  Aug 29 18:56:22 T460 /usr/lib/gdm3/gdm-x-session[1491]: (EE) client bug: 
timer event6 debounce: offset negative (-8ms)
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  format   : S16_LE
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  subformat: STD
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  channels : 2
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  rate : 44100
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  exact rate   : 44100 (44100/1)
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  msbits   : 16
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  buffer_size  : 16384
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  period_size  : 8192
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  period_time  : 185759
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  tstamp_mode  : ENABLE
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  tstamp_type  : MONOTONIC
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  period_step  : 1
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  avail_min: 14778
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  period_event : 0
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  start_threshold  : -1
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  stop_threshold   : 4611686018427387904
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  silence_threshold: 0
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  silence_size : 0
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
  boundary : 4611686018427387904
  Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Slave: Hardware PCM card 0 'HDA Intel PCH' device 0 

[Touch-packages] [Bug 1789778] [NEW] system crash due to snd_hda_intel

2018-08-29 Thread Filip Curic
Public bug reported:

After recent updates my system can suddenly crash. 
It starts with laggy sound until it completely freezes after which I need to do 
hard reset.

Crash will happen only while playing Dota 2 (steam) - for now.

# journalctl -b-1
..
Aug 29 18:56:19 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
snd_pcm_avail() returned a value that is exceptionally large: 500416 bytes 
(2836 ms).
Aug 29 18:56:19 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report 
this issue to the ALSA developers.
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
snd_pcm_dump():
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Soft volume PCM
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Control: PCM Playback Volume
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
min_dB: -51
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
max_dB: 0
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
resolution: 256
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Its setup is:
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
stream   : PLAYBACK
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
access   : MMAP_INTERLEAVED
Aug 29 18:56:22 T460 /usr/lib/gdm3/gdm-x-session[1491]: (EE) client bug: timer 
event6 debounce: offset negative (-8ms)
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
format   : S16_LE
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
subformat: STD
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
channels : 2
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
rate : 44100
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
exact rate   : 44100 (44100/1)
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
msbits   : 16
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
buffer_size  : 16384
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_size  : 8192
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_time  : 185759
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
tstamp_mode  : ENABLE
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
tstamp_type  : MONOTONIC
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_step  : 1
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
avail_min: 14778
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_event : 0
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
start_threshold  : -1
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
stop_threshold   : 4611686018427387904
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
silence_threshold: 0
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
silence_size : 0
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
boundary : 4611686018427387904
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Slave: Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Its setup is:
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
stream   : PLAYBACK
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
access   : MMAP_INTERLEAVED
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
format   : S16_LE
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
subformat: STD
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
channels : 2
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
rate : 44100
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
exact rate   : 44100 (44100/1)
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
msbits   : 16
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
buffer_size  : 16384
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_size  : 8192
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_time  : 185759
Aug 29 18:56:20 T460 pulseaudio[1662]: 

[Touch-packages] [Bug 1789778] [NEW] system crash due to snd_hda_intel

2018-08-29 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

After recent updates my system can suddenly crash. 
It starts with laggy sound until it completely freezes after which I need to do 
hard reset.

Crash will happen only while playing Dota 2 (steam) - for now.

# journalctl -b-1
..
Aug 29 18:56:19 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
snd_pcm_avail() returned a value that is exceptionally large: 500416 bytes 
(2836 ms).
Aug 29 18:56:19 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Most likely this is a bug in the ALSA driver 'snd_hda_intel'. Please report 
this issue to the ALSA developers.
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
snd_pcm_dump():
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Soft volume PCM
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Control: PCM Playback Volume
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
min_dB: -51
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
max_dB: 0
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
resolution: 256
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Its setup is:
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
stream   : PLAYBACK
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
access   : MMAP_INTERLEAVED
Aug 29 18:56:22 T460 /usr/lib/gdm3/gdm-x-session[1491]: (EE) client bug: timer 
event6 debounce: offset negative (-8ms)
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
format   : S16_LE
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
subformat: STD
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
channels : 2
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
rate : 44100
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
exact rate   : 44100 (44100/1)
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
msbits   : 16
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
buffer_size  : 16384
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_size  : 8192
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_time  : 185759
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
tstamp_mode  : ENABLE
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
tstamp_type  : MONOTONIC
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_step  : 1
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
avail_min: 14778
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_event : 0
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
start_threshold  : -1
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
stop_threshold   : 4611686018427387904
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
silence_threshold: 0
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
silence_size : 0
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
boundary : 4611686018427387904
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Slave: Hardware PCM card 0 'HDA Intel PCH' device 0 subdevice 0
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c: 
Its setup is:
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
stream   : PLAYBACK
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
access   : MMAP_INTERLEAVED
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
format   : S16_LE
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
subformat: STD
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
channels : 2
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
rate : 44100
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
exact rate   : 44100 (44100/1)
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
msbits   : 16
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
buffer_size  : 16384
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_size  : 8192
Aug 29 18:56:20 T460 pulseaudio[1662]: [alsa-sink-ALC293 Analog] alsa-util.c:   
period_time  : 185759
Aug 29 18:56:20 T460 

[Touch-packages] [Bug 1788739] Re: When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset information is printed to syslog

2018-08-29 Thread chris pollock
** Package changed: rsyslog (Ubuntu) => gdm3 (Ubuntu)

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

Title:
  When starting Evolution /usr/lib/gdm3/gdm-x-session[2309]: (II)
  modeset information is printed to syslog

Status in gdm3 package in Ubuntu:
  Incomplete

Bug description:
  This started the same day I did the upgrade from 16.04LTS to 18.04LTS.
  Package/system information below:

  lsb_release -crid
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

  apt-cache policy gdm3
  gdm3:
Installed: 3.28.2-0ubuntu1.4
Candidate: 3.28.2-0ubuntu1.4

  apt-cache policy evolution
  evolution:
Installed: 3.28.1-2
Candidate: 3.28.1-2

  The output written to syslog is:

  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
EDID vendor "ACR", prod id 22
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Using hsync ranges from config file
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Using vrefresh ranges from config file
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Printing DDC gathered Modelines:
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1680x1050"x0.0  119.00  1680 1728 1760 1840  1050 1053 1059 1080 
-hsync -vsync (64.7 kHz eP)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "800x600"x0.0   40.00  800 840 968 1056  600 601 605 628 +hsync +vsync 
(37.9 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "800x600"x0.0   36.00  800 824 896 1024  600 601 603 625 +hsync +vsync 
(35.2 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 656 720 840  480 481 484 500 -hsync -vsync 
(37.5 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "640x480"x0.0   31.50  640 664 704 832  480 489 492 520 -hsync -vsync 
(37.9 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "640x480"x0.0   30.24  640 704 768 864  480 483 486 525 -hsync -vsync 
(35.0 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "640x480"x0.0   25.18  640 656 752 800  480 490 492 525 -hsync -vsync 
(31.5 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "720x400"x0.0   28.32  720 738 846 900  400 412 414 449 -hsync +vsync 
(31.5 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1280x1024"x0.0  135.00  1280 1296 1440 1688  1024 1025 1028 1066 
+hsync +vsync (80.0 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1024x768"x0.0   78.75  1024 1040 1136 1312  768 769 772 800 +hsync 
+vsync (60.0 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1024x768"x0.0   75.00  1024 1048 1184 1328  768 771 777 806 -hsync 
-vsync (56.5 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1024x768"x0.0   65.00  1024 1048 1184 1344  768 771 777 806 -hsync 
-vsync (48.4 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "832x624"x0.0   57.28  832 864 928 1152  624 625 628 667 -hsync -vsync 
(49.7 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "800x600"x0.0   49.50  800 816 896 1056  600 601 604 625 +hsync +vsync 
(46.9 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "800x600"x0.0   50.00  800 856 976 1040  600 637 643 666 +hsync +vsync 
(48.1 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1152x864"x0.0  108.00  1152 1216 1344 1600  864 865 868 900 +hsync 
+vsync (67.5 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1280x1024"x0.0  108.00  1280 1328 1440 1688  1024 1025 1028 1066 
+hsync +vsync (64.0 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1680x1050"x0.0  146.25  1680 1784 1960 2240  1050 1053 1059 1089 
-hsync +vsync (65.3 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1440x900"x0.0  136.75  1440 1536 1688 1936  900 903 909 942 -hsync 
+vsync (70.6 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline "1440x900"x0.0  106.50  1440 1520 1672 1904  900 903 909 934 -hsync 
+vsync (55.9 kHz e)
  Aug 23 20:52:50 localhost /usr/lib/gdm3/gdm-x-session[2309]: (II) modeset(0): 
Modeline 

[Touch-packages] [Bug 1789758] Re: bluetooth headphones a2dp profile does not function after suspend

2018-08-29 Thread Daniel van Vugt
Reassigned to pulseaudio. Bluetooth audio is a software feature
implemented in pulseaudio, not in bluez.

** Tags added: a2dp

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

** Tags added: resume suspend-resume

** Summary changed:

- bluetooth headphones a2dp profile does not function after suspend
+ bluetooth headphones a2dp profile does not function after suspend, only HSP

** No longer affects: bluez (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/1789758

Title:
  bluetooth headphones a2dp profile does not function after suspend,
  only HSP

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2) $ apt-cache policy bluez
  bluez:
Installed: 5.48-0ubuntu3.1
Candidate: 5.48-0ubuntu3.1
Version table:
   *** 5.48-0ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.48-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) bluetooth headphones stay working in a2dp mode even after suspend

  4) bluetooth headphones connect but no sound will come out of a2dp
  mode, only in HSP profile

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 18:07:26 2018
  InstallationDate: Installed on 2018-05-26 (95 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180525)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9e84ffd4-d629-4dcd-a6c4-6648d1a34665 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: RKPPT10H.86A.0041.2015.0316.1442
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D53427RKE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G87971-406
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0041.2015.0316.1442:bd03/16/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-406:cvn:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 48:51:B7:07:93:F5  ACL MTU: 1021:5  SCO MTU: 96:5
DOWN 
RX bytes:5617087 acl:790 sco:22622 events:634625 errors:0
TX bytes:540631745 acl:632348 sco:22584 commands:537 errors:0

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

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


[Touch-packages] [Bug 1789688] Re: Syste-sim package post-removal script subprocess returned error exit status 2

2018-08-29 Thread Daniel van Vugt
Do you mean this package?

systemd-shim 9-1bzr4ubuntu1 [origin: unknown]


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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Syste-sim package post-removal script subprocess returned error exit
  status 2

Status in Ubuntu:
  Incomplete

Bug description:
  System-sim package post-removal script subprocess returned error exit
  status 2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Aug 29 12:44:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Wrestler [Radeon HD 6310] [104d:9082]
  InstallationDate: Installed on 2011-09-19 (2536 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: Sony Corporation VPCYB15KX
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=8ed5b153-f958-4b95-b6b4-66b959d46b7e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2010
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0160Z7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0160Z7:bd12/22/2010:svnSonyCorporation:pnVPCYB15KX:pvrC9015CZJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCYB15KX
  dmi.product.version: C9015CZJ
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Fri Aug 24 12:37:01 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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


[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

2018-08-29 Thread Daniel van Vugt
Actually the fix was reverted back in May 2018:

https://git.launchpad.net/~ubuntu-audio-dev/pulseaudio/commit/?h=ubuntu-
xenial=3b148dcc243

So the fix is not in xenial.

** Changed in: pulseaudio (Ubuntu Xenial)
 Assignee: (unassigned) => Hui Wang (hui.wang)

** Changed in: pulseaudio (Ubuntu Xenial)
   Status: Fix Released => 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/1750947

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Confirmed

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  The patch will check all ports under each profile, if a profile only
  contains unavailable ports, this profile will be set to unavailable as
  well. Without this patch, all profiles are always available, then if a
  profile includes a unusable hdmi-output, and pulseaudio select this
  profile to be active (since its priority is the highest), the kernel
  audio driver will crash.

  I think this patch will not introduce regression:
  1) It is a correct logic to set a profile to be unavailable if it only 
contains unavailable ports.
  2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
  3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop 
and 1 dell desktop, all worked well as before
  4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

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

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


[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

2018-08-29 Thread Bin Li
** Changed in: gdm3 (Ubuntu)
 Assignee: (unassigned) => Bin Li (binli)

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

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  In Progress
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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


[Touch-packages] [Bug 1788448] Re: CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11

2018-08-29 Thread Leonidas S. Barbosa
Hi Joseph!

Yep, I'm working on this. Soon as possible it'll be released/update.

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

Title:
  CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11

Status in libx11 package in Ubuntu:
  New

Bug description:
  There are 3 security issues reported in libx11 that are fixed upstream
  in libx11 1.6.6.

  Bugs announced:
  https://lists.x.org/archives/xorg-announce/2018-August/002915.html

  Release announcement of libx11 1.6.6 with commits fixing them listed:
  https://lists.x.org/archives/xorg-announce/2018-August/002916.html

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

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


[Touch-packages] [Bug 1789764] [NEW] package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers looping, abandoned

2018-08-29 Thread Salman A. Kamkoriwala
Public bug reported:

Upgrade to 18.04 error

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: fontconfig 2.12.6-0ubuntu2
ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18
Uname: Linux 4.15.0-33-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Thu Aug 30 02:42:47 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2018-04-24 (127 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: fontconfig
Title: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-08-29 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers
  looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Upgrade to 18.04 error

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: fontconfig 2.12.6-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-33.36-lowlatency 4.15.18
  Uname: Linux 4.15.0-33-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Aug 30 02:42:47 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2018-04-24 (127 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.12.6-0ubuntu2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-08-29 (0 days ago)

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

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


[Touch-packages] [Bug 1781049] Re: WiFI hard blocked after resuming laptop (RTL 8723BE)

2018-08-29 Thread Dexter
Hello,
Blacklisting the below modules one after the another individually or all of 
them did no good. The hard-block bug is still there. [2]

blacklist hp_wmi
blacklist hp_wireless

Also, while going through the output of dmesg, I found a few lines that
might be of interest (not that I have any experience, as my handle
suggests, I'm a noob at Linux) or help you guys.

# ** *
dmesg snippets (when no modules are blacklisted) [2]

HP Wireless hotkeys as /devices/virtual/input/input8
hp_wmi: query 0xd returned error 0x5
HP WMI hotkeys as /devices/virtual/input/input10

[   96.374587] iwlwifi :08:00.0: reporting RF_KILL (radio disabled)
[   96.374700] iwlwifi :08:00.0: RF_KILL bit toggled to disable radio.

# ** *
Files that sparked my interest:

The file at '/sys/devices/virtual/input/input8/uevent' has the following 
contents:
PRODUCT=19/0/0/0
NAME="HP Wireless hotkeys"
PHYS="hpq6001/input0"
PROP=0
EV=3
KEY=80 0 0 0
MODALIAS=input:b0019vpe-e0,1,kF7,ramlsfw

The file at '/sys/devices/virtual/input/input10/uevent' has the following 
contents:
PRODUCT=19/0/0/0
NAME="HP WMI hotkeys"
PHYS="wmi/input0"
PROP=0
EV=33
KEY=40 0 10007 2102400 0 0
MSC=10
SW=0
MODALIAS=input:b0019vpe-e0,1,4,5,k8A,8D,94,99,E0,E1,E2,F0,166,ram4,lsfw

Trying to emulate some keys by trying to write to the file results in
I/O errors. (suggested on the internet)

# ** *

Files from attached after copying as root, but with some errors: [1]
cp: error reading 'input10/power/autosuspend_delay_ms': Input/output error
cp: error reading 'input10/event9/power/autosuspend_delay_ms': Input/output 
error
cp: error reading 'input8/power/autosuspend_delay_ms': Input/output error
cp: error reading 'input8/event7/power/autosuspend_delay_ms': Input/output error
cp: error reading 'mice/power/autosuspend_delay_ms': Input/output error

# ** *

[1] Files from /sys/devices/virtual/input
[2] Attached 3 dmesg logs with the filenames explaining the test case. 

# ** *

Thank you for your time!

** Attachment added: "Contains dmesg output and files from path [1]"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1781049/+attachment/5182401/+files/attachments.tar

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

Title:
  WiFI hard blocked after resuming laptop (RTL 8723BE)

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

Bug description:
  I installed a fresh copy of Ubuntu 18.04 and everything seems to work
  fine, till I suspended and resumed the laptop. After resume, the wifi
  is hard blocked is rfkill. Reinstalling drivers, different drivers,
  nothing helped. All this was done under Secure Boot disabled under
  Ubuntu and BIOS (UEFI).

  The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If
  any further info is required, I'll add it on notification. I am
  familiar with Linux, any help will be really appreciated.

  
  P.S: If this wifi card is the issue, please suggest some PCI-mini card that 
will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 
5.0)

  Thank you all!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythreya   1281 F pulseaudio
   /dev/snd/controlC1:  mythreya   1281 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-26 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion Notebook
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash 

[Touch-packages] [Bug 1789476] Re: glib apps using GSubprocess communicate might crash on g_subprocess_communicate_cancelled

2018-08-29 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~3v1n0/ubuntu/+source/glib2.0/+git/glib2.0/+merge/354012

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

Title:
  glib apps using GSubprocess communicate might crash on
  g_subprocess_communicate_cancelled

Status in glib2.0 package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Glib apps using subprocess communicate and cancellable is cancelled
  crashes

  [ Test case ]

  Run the attached example with
   gjs subprocess-cancelled.js

  Should not crash, or running:
   valgrind gjs subprocess-cancelled.js

  should not return any read error (as the one mentioned below)

  [ Regression potential ]

  Really low, the only thing that could happen is that the subprocess
  isn't really cancelled.

  ---

  Fixed upstream in
  https://gitlab.gnome.org/GNOME/glib/merge_requests/266

  #0  g_cancellable_cancel (cancellable=0x6) at 
../../glib/gio/gcancellable.c:486
  #1  0x77ab8d1d in g_subprocess_communicate_cancelled 
(user_data=) at ../../glib/gio/gsubprocess.c:1535

  --

  ==25871== Memcheck, a memory error detector
  ==25871== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==25871== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
  ==25871== Command: gjs /tmp/subprocess-cancelled.js
  ==25871== 
  ==25871== Warning: set address range perms: large range [0x377ee1e21000, 
0x377f21e21000) (noaccess)
  ==25871== Invalid read of size 8
  ==25871==at 0x4EC5604: g_subprocess_communicate_cancelled 
(gsubprocess.c:1535)
  ==25871==by 0x547A0F4: g_main_dispatch (gmain.c:3177)
  ==25871==by 0x547A0F4: g_main_context_dispatch (gmain.c:3830)
  ==25871==by 0x547A4BF: g_main_context_iterate.isra.26 (gmain.c:3903)
  ==25871==by 0x547A54B: g_main_context_iteration (gmain.c:3964)
  ==25871==by 0x6C4EDAD: ffi_call_unix64 (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4)
  ==25871==by 0x6C4E71E: ffi_call (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4)
  ==25871==by 0x5775607: ??? (in /usr/lib/libgjs.so.0.0.0)
  ==25871==by 0x5776F53: ??? (in /usr/lib/libgjs.so.0.0.0)
  ==25871==by 0x8A3FF6B: CallJSNative (jscntxtinlines.h:239)
  ==25871==by 0x8A3FF6B: js::InternalCallOrConstruct(JSContext*, 
JS::CallArgs const&, js::MaybeConstruct) (Interpreter.cpp:447)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1789476/+subscriptions

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


[Touch-packages] [Bug 1789476] Re: glib apps using GSubprocess communicate might crash on g_subprocess_communicate_cancelled

2018-08-29 Thread Treviño
Added test case

** Description changed:

+ [ Impact ]
+ 
+ Glib apps using subprocess communicate and cancellable is cancelled
+ crashes
+ 
+ [ Test case ]
+ 
+ Run the attached example with
+  gjs subprocess-cancelled.js
+ 
+ Should not crash, or running:
+  valgrind gjs subprocess-cancelled.js
+ 
+ should not return any read error (as the one mentioned below)
+ 
+ [ Regression potential ]
+ 
+ Really low, the only thing that could happen is that the subprocess
+ isn't really cancelled.
+ 
+ ---
+ 
  Fixed upstream in https://gitlab.gnome.org/GNOME/glib/merge_requests/266
  
  #0  g_cancellable_cancel (cancellable=0x6) at 
../../glib/gio/gcancellable.c:486
  #1  0x77ab8d1d in g_subprocess_communicate_cancelled 
(user_data=) at ../../glib/gio/gsubprocess.c:1535
+ 
+ --
+ 
+ ==25871== Memcheck, a memory error detector
+ ==25871== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
+ ==25871== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
+ ==25871== Command: gjs /tmp/subprocess-cancelled.js
+ ==25871== 
+ ==25871== Warning: set address range perms: large range [0x377ee1e21000, 
0x377f21e21000) (noaccess)
+ ==25871== Invalid read of size 8
+ ==25871==at 0x4EC5604: g_subprocess_communicate_cancelled 
(gsubprocess.c:1535)
+ ==25871==by 0x547A0F4: g_main_dispatch (gmain.c:3177)
+ ==25871==by 0x547A0F4: g_main_context_dispatch (gmain.c:3830)
+ ==25871==by 0x547A4BF: g_main_context_iterate.isra.26 (gmain.c:3903)
+ ==25871==by 0x547A54B: g_main_context_iteration (gmain.c:3964)
+ ==25871==by 0x6C4EDAD: ffi_call_unix64 (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4)
+ ==25871==by 0x6C4E71E: ffi_call (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4)
+ ==25871==by 0x5775607: ??? (in /usr/lib/libgjs.so.0.0.0)
+ ==25871==by 0x5776F53: ??? (in /usr/lib/libgjs.so.0.0.0)
+ ==25871==by 0x8A3FF6B: CallJSNative (jscntxtinlines.h:239)
+ ==25871==by 0x8A3FF6B: js::InternalCallOrConstruct(JSContext*, 
JS::CallArgs const&, js::MaybeConstruct) (Interpreter.cpp:447)

** Attachment added: "test case: subprocess-cancelled.js"
   
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1789476/+attachment/5182398/+files/subprocess-cancelled.js

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

Title:
  glib apps using GSubprocess communicate might crash on
  g_subprocess_communicate_cancelled

Status in glib2.0 package in Ubuntu:
  In Progress

Bug description:
  [ Impact ]

  Glib apps using subprocess communicate and cancellable is cancelled
  crashes

  [ Test case ]

  Run the attached example with
   gjs subprocess-cancelled.js

  Should not crash, or running:
   valgrind gjs subprocess-cancelled.js

  should not return any read error (as the one mentioned below)

  [ Regression potential ]

  Really low, the only thing that could happen is that the subprocess
  isn't really cancelled.

  ---

  Fixed upstream in
  https://gitlab.gnome.org/GNOME/glib/merge_requests/266

  #0  g_cancellable_cancel (cancellable=0x6) at 
../../glib/gio/gcancellable.c:486
  #1  0x77ab8d1d in g_subprocess_communicate_cancelled 
(user_data=) at ../../glib/gio/gsubprocess.c:1535

  --

  ==25871== Memcheck, a memory error detector
  ==25871== Copyright (C) 2002-2017, and GNU GPL'd, by Julian Seward et al.
  ==25871== Using Valgrind-3.13.0 and LibVEX; rerun with -h for copyright info
  ==25871== Command: gjs /tmp/subprocess-cancelled.js
  ==25871== 
  ==25871== Warning: set address range perms: large range [0x377ee1e21000, 
0x377f21e21000) (noaccess)
  ==25871== Invalid read of size 8
  ==25871==at 0x4EC5604: g_subprocess_communicate_cancelled 
(gsubprocess.c:1535)
  ==25871==by 0x547A0F4: g_main_dispatch (gmain.c:3177)
  ==25871==by 0x547A0F4: g_main_context_dispatch (gmain.c:3830)
  ==25871==by 0x547A4BF: g_main_context_iterate.isra.26 (gmain.c:3903)
  ==25871==by 0x547A54B: g_main_context_iteration (gmain.c:3964)
  ==25871==by 0x6C4EDAD: ffi_call_unix64 (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4)
  ==25871==by 0x6C4E71E: ffi_call (in 
/usr/lib/x86_64-linux-gnu/libffi.so.6.0.4)
  ==25871==by 0x5775607: ??? (in /usr/lib/libgjs.so.0.0.0)
  ==25871==by 0x5776F53: ??? (in /usr/lib/libgjs.so.0.0.0)
  ==25871==by 0x8A3FF6B: CallJSNative (jscntxtinlines.h:239)
  ==25871==by 0x8A3FF6B: js::InternalCallOrConstruct(JSContext*, 
JS::CallArgs const&, js::MaybeConstruct) (Interpreter.cpp:447)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1789476/+subscriptions

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


[Touch-packages] [Bug 1789758] [NEW] bluetooth headphones a2dp profile does not function after suspend

2018-08-29 Thread Ryan Harper
Public bug reported:

1) lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04

2) $ apt-cache policy bluez
bluez:
  Installed: 5.48-0ubuntu3.1
  Candidate: 5.48-0ubuntu3.1
  Version table:
 *** 5.48-0ubuntu3.1 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 5.48-0ubuntu3 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

3) bluetooth headphones stay working in a2dp mode even after suspend

4) bluetooth headphones connect but no sound will come out of a2dp mode,
only in HSP profile

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: bluez 5.48-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
Uname: Linux 4.15.0-30-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 29 18:07:26 2018
InstallationDate: Installed on 2018-05-26 (95 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180525)
InterestingModules: rfcomm bnep btusb bluetooth
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9e84ffd4-d629-4dcd-a6c4-6648d1a34665 ro quiet splash vt.handoff=1
SourcePackage: bluez
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/16/2015
dmi.bios.vendor: Intel Corp.
dmi.bios.version: RKPPT10H.86A.0041.2015.0316.1442
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: D53427RKE
dmi.board.vendor: Intel Corporation
dmi.board.version: G87971-406
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0041.2015.0316.1442:bd03/16/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-406:cvn:ct3:cvr:
dmi.product.family: To be filled by O.E.M.
hciconfig:
 hci0:  Type: Primary  Bus: USB
BD Address: 48:51:B7:07:93:F5  ACL MTU: 1021:5  SCO MTU: 96:5
DOWN 
RX bytes:5617087 acl:790 sco:22622 events:634625 errors:0
TX bytes:540631745 acl:632348 sco:22584 commands:537 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/1789758

Title:
  bluetooth headphones a2dp profile does not function after suspend

Status in bluez package in Ubuntu:
  New

Bug description:
  1) lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  2) $ apt-cache policy bluez
  bluez:
Installed: 5.48-0ubuntu3.1
Candidate: 5.48-0ubuntu3.1
Version table:
   *** 5.48-0ubuntu3.1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   5.48-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  3) bluetooth headphones stay working in a2dp mode even after suspend

  4) bluetooth headphones connect but no sound will come out of a2dp
  mode, only in HSP profile

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 18:07:26 2018
  InstallationDate: Installed on 2018-05-26 (95 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180525)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-30-generic 
root=UUID=9e84ffd4-d629-4dcd-a6c4-6648d1a34665 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/16/2015
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: RKPPT10H.86A.0041.2015.0316.1442
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: D53427RKE
  dmi.board.vendor: Intel Corporation
  dmi.board.version: G87971-406
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrRKPPT10H.86A.0041.2015.0316.1442:bd03/16/2015:svn:pn:pvr:rvnIntelCorporation:rnD53427RKE:rvrG87971-406:cvn:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 48:51:B7:07:93:F5  ACL MTU: 1021:5  SCO MTU: 96:5
DOWN 
RX bytes:5617087 acl:790 sco:22622 events:634625 errors:0
TX bytes:540631745 acl:632348 sco:22584 commands:537 errors:0

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

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

[Touch-packages] [Bug 1786576] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: instalado lvm2 paquete post-installation guión el subproceso devolvió un error con estado de salida 1

2018-08-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: instalado
  lvm2 paquete post-installation guión el subproceso devolvió un error
  con estado de salida 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  the error reads 
  Failed to restart lvm2-lvmetad.service: Unit lvm2-lvmetad.socket is masked.
  invoke-rc.d: initscript lvm2-lvmetad, action "restart" failed.
  ● lvm2-lvmetad.service - LVM2 metadata daemon
 Loaded: loaded (/lib/systemd/system/lvm2-lvmetad.service; static; vendor 
preset: enabled)
 Active: active (exited) since Fri 2018-08-10 18:48:40 CDT; 1h 57min ago
   Docs: man:lvmetad(8)
  Tasks: 0 (limit: 4915)
 CGroup: /system.slice/lvm2-lvmetad.service

  ago 10 18:48:40 lv-426 systemd[1]: Starting LSB: LVM2 metadata daemon...
  ago 10 18:48:40 lv-426 systemd[1]: Started LSB: LVM2 metadata daemon.
  dpkg: error al procesar el paquete lvm2 (--configure):
   instalado lvm2 paquete post-installation guión el subproceso devolvió un 
error con estado de salida 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-30.32-generic 4.15.18
  Uname: Linux 4.15.0-30-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Aug 10 20:46:31 2018
  ErrorMessage: instalado lvm2 paquete post-installation guión el subproceso 
devolvió un error con estado de salida 1
  InstallationDate: Installed on 2018-07-22 (20 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: lvm2
  Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: instalado 
lvm2 paquete post-installation guión el subproceso devolvió un error con estado 
de salida 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1788448] Re: CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11

2018-08-29 Thread Joseph Yasi
It looks like libx11-1.6.6 was pulled into cosmic. So this is fixed
there. This still needs a backport to earlier releases.

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

Title:
  CVE-2018-14598 CVE-2018-14599 CVE-2018-14600 in libx11

Status in libx11 package in Ubuntu:
  New

Bug description:
  There are 3 security issues reported in libx11 that are fixed upstream
  in libx11 1.6.6.

  Bugs announced:
  https://lists.x.org/archives/xorg-announce/2018-August/002915.html

  Release announcement of libx11 1.6.6 with commits fixing them listed:
  https://lists.x.org/archives/xorg-announce/2018-August/002916.html

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

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


[Touch-packages] [Bug 1789750] Re: apport-gtk crashed with SIGABRT in g_assertion_message_error()

2018-08-29 Thread Apport retracing service
*** This bug is a duplicate of bug 1756469 ***
https://bugs.launchpad.net/bugs/1756469

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1789750/+attachment/5182358/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1789750/+attachment/5182360/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1789750/+attachment/5182364/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1789750/+attachment/5182365/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1789750/+attachment/5182366/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1789750/+attachment/5182367/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1789750/+attachment/5182368/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of private bug 1756469

** Tags removed: need-amd64-retrace

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

Title:
  apport-gtk crashed with SIGABRT in g_assertion_message_error()

Status in apport package in Ubuntu:
  New

Bug description:
  The system crashed during the update of the virtualbox guest addition
  drivers during the system upgrade from 4.17.0-7 to 4.17.0-9

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: apport-gtk 2.20.10-0ubuntu9
  ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12
  Uname: Linux 4.17.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CrashReports:
   640:1000:118:7015528:2018-08-29 17:59:46.687878370 -0400:2018-08-29 
17:59:47.687878370 -0400:/var/crash/_usr_bin_rhythmbox.1000.crash
   640:1000:118:17562022:2018-08-29 18:00:31.657382249 -0400:2018-08-29 
18:00:32.657382249 -0400:/var/crash/_usr_share_apport_apport-gtk.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 18:00:23 2018
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-05 (85 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180603)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
  Signal: 6
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_error () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGABRT in g_assertion_message_error()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

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

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


[Touch-packages] [Bug 1788322] Re: Approximately every 2mins this is written to syslog - rsyslogd: action 'action 3' resumed (module 'builtin:omfile') [v8.32.0 try http://www.rsyslog.com/e/2359

2018-08-29 Thread chris pollock
Please mark this bug as invalid. After several replies to a question at
LinuxQuestions.org on this I discovered that the permissions for
/var/log/cron.log were incorrect. I corrected that problem this
afternoon and the reported issue has been corrected.

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

Title:
  Approximately every 2mins this is written to syslog - rsyslogd: action
  'action 3' resumed (module 'builtin:omfile') [v8.32.0 try
  http://www.rsyslog.com/e/2359

Status in rsyslog package in Ubuntu:
  New

Bug description:
  I'm not sure this is a bug but instead is a configuration option
  missing in the /etc/rsyslog.conf.

  This is on a Ubuntu 18.04.1LTS system that was upgraded last week from
  16.04.5LTS. The version of rsyslog installed is:

  apt-cache policy rsyslog
  rsyslog:
Installed: 8.32.0-1ubuntu4
Candidate: 8.32.0-1ubuntu4

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  The complete output is here:

  https://pastebin.com/AxYYQaw5

  I went to the links noted. The first one http://www.rsyslog.com/e/2359
  from what I can read tells me that whatever action is referenced it was
  resumed. I assume in this case it refers to this "resumed (module
  'builtin:omfile'" The 2nd link http://www.rsyslog.com/e/2007 seems to
  give me a fix for this. I've looked for what is mentioned in the 2nd
  link in my /etc/rsyslog.conf file and in my /etc/rsyslog.d/50-
  default.conf:

  The 2nd link refers to this:

  "A frequent case for this error message on Debian-based distributions
  (like raspbian) is that rsyslog.conf contains the instruction to write
  to the xconsole pipe, but this pipe is never read. If so, you can
  simply delete these lines to remove the error message. These lines are
  usually found at the end of rsyslog.conf."

  My current /etc/rsyslog.conf file is here
  https://pastebin.com/WZVhryNW

  If I need to add some lines to the .conf file I'm not sure what they
  should be.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2014-10-24 (1401 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  Package: rsyslog 8.32.0-1ubuntu4
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Tags:  bionic
  Uname: Linux 4.15.0-33-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-08-17 (8 days ago)
  UserGroups: adm cdrom dip kvm libvirt libvirtd lpadmin netdev plugdev 
sambashare sudo
  _MarkForUpload: True
  modified.conffile..etc.logcheck.ignore.d.server.rsyslog: [deleted]

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

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


[Touch-packages] [Bug 1789750] [NEW] apport-gtk crashed with SIGABRT in g_assertion_message_error()

2018-08-29 Thread BertN45
Public bug reported:

The system crashed during the update of the virtualbox guest addition
drivers during the system upgrade from 4.17.0-7 to 4.17.0-9

ProblemType: Crash
DistroRelease: Ubuntu 18.10
Package: apport-gtk 2.20.10-0ubuntu9
ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12
Uname: Linux 4.17.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu9
Architecture: amd64
CrashReports:
 640:1000:118:7015528:2018-08-29 17:59:46.687878370 -0400:2018-08-29 
17:59:47.687878370 -0400:/var/crash/_usr_bin_rhythmbox.1000.crash
 640:1000:118:17562022:2018-08-29 18:00:31.657382249 -0400:2018-08-29 
18:00:32.657382249 -0400:/var/crash/_usr_share_apport_apport-gtk.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 29 18:00:23 2018
ExecutablePath: /usr/share/apport/apport-gtk
InstallationDate: Installed on 2018-06-05 (85 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180603)
InterpreterPath: /usr/bin/python3.6
PackageArchitecture: all
ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1
PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
Signal: 6
SourcePackage: apport
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_assertion_message_error () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
Title: apport-gtk crashed with SIGABRT in g_assertion_message_error()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

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


** Tags: amd64 apport-crash cosmic need-amd64-retrace

** Information type changed from Private to Public

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

Title:
  apport-gtk crashed with SIGABRT in g_assertion_message_error()

Status in apport package in Ubuntu:
  New

Bug description:
  The system crashed during the update of the virtualbox guest addition
  drivers during the system upgrade from 4.17.0-7 to 4.17.0-9

  ProblemType: Crash
  DistroRelease: Ubuntu 18.10
  Package: apport-gtk 2.20.10-0ubuntu9
  ProcVersionSignature: Ubuntu 4.17.0-7.8-generic 4.17.12
  Uname: Linux 4.17.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu9
  Architecture: amd64
  CrashReports:
   640:1000:118:7015528:2018-08-29 17:59:46.687878370 -0400:2018-08-29 
17:59:47.687878370 -0400:/var/crash/_usr_bin_rhythmbox.1000.crash
   640:1000:118:17562022:2018-08-29 18:00:31.657382249 -0400:2018-08-29 
18:00:32.657382249 -0400:/var/crash/_usr_share_apport_apport-gtk.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 18:00:23 2018
  ExecutablePath: /usr/share/apport/apport-gtk
  InstallationDate: Installed on 2018-06-05 (85 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Alpha amd64 (20180603)
  InterpreterPath: /usr/bin/python3.6
  PackageArchitecture: all
  ProcCmdline: /usr/bin/python3 /usr/share/apport/apport-gtk
  Python3Details: /usr/bin/python3.6, Python 3.6.6+, python3-minimal, 3.6.6-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
  Signal: 6
  SourcePackage: apport
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   g_assertion_message_error () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgtk-3.so.0
  Title: apport-gtk crashed with SIGABRT in g_assertion_message_error()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxsf

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

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


[Touch-packages] [Bug 1781049] Re: WiFI hard blocked after resuming laptop (RTL 8723BE)

2018-08-29 Thread Dexter
Hello!
I've tested the rc1 release kernel (4.19.0-041900rc1-generic), and sure enough, 
the bug persists. WiFi hard-blocked after suspend-resume. 

Driver issues can be ruled out as I've installed a new wifi card form intel 
(Wireless 3165, iwlwifi driver: 4.19.0-041900rc1-generic, firmware: 
29.1044073957.0)
and the problem exists with both the cards, on both the kernel versions. 

As far as I know, from dmesg, reports that some hardware switch is being 
flipped, while there is none on my model (HP AB035TX - Manual here [0]).
The 'Airplane Mode' key only works on soft blocks. 

Any solutions are really helpful!
Thank you very much for your time!
Regards, 
Dexter

[0] My Laptop manual - http://h10032.www1.hp.com/ctg/Manual/c04642845

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

Title:
  WiFI hard blocked after resuming laptop (RTL 8723BE)

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

Bug description:
  I installed a fresh copy of Ubuntu 18.04 and everything seems to work
  fine, till I suspended and resumed the laptop. After resume, the wifi
  is hard blocked is rfkill. Reinstalling drivers, different drivers,
  nothing helped. All this was done under Secure Boot disabled under
  Ubuntu and BIOS (UEFI).

  The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If
  any further info is required, I'll add it on notification. I am
  familiar with Linux, any help will be really appreciated.

  
  P.S: If this wifi card is the issue, please suggest some PCI-mini card that 
will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 
5.0)

  Thank you all!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythreya   1281 F pulseaudio
   /dev/snd/controlC1:  mythreya   1281 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-26 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion Notebook
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.87
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8096
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-30T14:39:45.608645
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2018-06-28T16:23:51.596655
  nmcli-con:
   NAME   UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH 

[Touch-packages] [Bug 1781049] Re: WiFI hard blocked after resuming laptop (RTL 8723BE)

2018-08-29 Thread Dexter
** Tags removed: rtl8723be
** Tags added: kernel-bug-exists-upstream resume suspend

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

Title:
  WiFI hard blocked after resuming laptop (RTL 8723BE)

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

Bug description:
  I installed a fresh copy of Ubuntu 18.04 and everything seems to work
  fine, till I suspended and resumed the laptop. After resume, the wifi
  is hard blocked is rfkill. Reinstalling drivers, different drivers,
  nothing helped. All this was done under Secure Boot disabled under
  Ubuntu and BIOS (UEFI).

  The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If
  any further info is required, I'll add it on notification. I am
  familiar with Linux, any help will be really appreciated.

  
  P.S: If this wifi card is the issue, please suggest some PCI-mini card that 
will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 
5.0)

  Thank you all!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythreya   1281 F pulseaudio
   /dev/snd/controlC1:  mythreya   1281 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-26 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion Notebook
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.87
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8096
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-30T14:39:45.608645
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2018-06-28T16:23:51.596655
  nmcli-con:
   NAME   UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   NETGEAR71  1a9d81bf-e7f5-4f8a-956f-96180dc493e1  wifi  1531450229  Thu 
12 Jul 2018 09:50:29 PM CDT  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlo1activated  
/org/freedesktop/NetworkManager/ActiveConnection/2  --
   Ethernet   81087af0-5c8d-451f-84c0-1a95c6034098  ethernet  1530214661  Thu 
28 Jun 2018 02:37:41 PM CDT  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  -- --   
   --
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  

[Touch-packages] [Bug 161058]

2018-08-29 Thread Gitlab-migration
-- GitLab Migration Automatic Message --

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

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

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

Title:
  some ~/.fonts.conf settings do no override desktop-wide gnome settings
  (hinting style)

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  I didn't fill out the package field, since this seems to be an
  interaction between multiple packages (gnome-setting-daemon, libgtk,
  libcairo, pango/cairo).

  In the 'Appearance' control app, under the font settings, I like to
  use 'Subpixel' and 'Full' hinting by default, since this looks good
  for most bundled fonts.

  However, there is occasionally a font (especially in the msttcorefonts
  package) that doesn't look good with these settings. So I want to
  override their rendering settings using .fonts.conf. My main tactic is
  to usually turn on the autohinter in 'hintslight' mode for certain
  fonts. Lets take Times new Roman as an example.. the .fonts.conf
  incantation to do this would be:

   

   Times New Roman
   
   true
   true
   hintslight 
   

  The odd thing about this is that the 'autohint' and 'hinting' edits
  seem to work, but the 'hintstyle' edit is always overridden by the
  control applet's settings. I can verify this by launching gedit each
  time after tweaking these settings.

  "fc-match -v 'Times New Roman'" does return the right settings, so its
  something in the chain of gtk libraries that is messing it up.

  Interstingly, it's not all possible edit settings that are ignored. It
  seems to only be hintstyle. For example if I were to say:

  
   

   Times New Roman
   
false  
   

  Then this works correctly. Only Times New Roman will be non-antialiased even 
in gedit. Even setting "hinting" to "false" works.. its only the hintstyle 
setting that doesn't work.
  [lspci]
  00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX 
Host bridge [8086:7190] (rev 01)
Subsystem: VMware Inc Device [15ad:1976]
  00:0f.0 VGA compatible controller [0300]: VMware Inc Abstract SVGA II Adapter 
[15ad:0405]
Subsystem: VMware Inc Abstract SVGA II Adapter [15ad:0405]

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

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


[Touch-packages] [Bug 161058] Re: some ~/.fonts.conf settings do no override desktop-wide gnome settings (hinting style)

2018-08-29 Thread Bug Watch Updater
** Changed in: cairo
   Status: Confirmed => Unknown

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

Title:
  some ~/.fonts.conf settings do no override desktop-wide gnome settings
  (hinting style)

Status in cairo:
  Unknown
Status in cairo package in Ubuntu:
  Confirmed

Bug description:
  I didn't fill out the package field, since this seems to be an
  interaction between multiple packages (gnome-setting-daemon, libgtk,
  libcairo, pango/cairo).

  In the 'Appearance' control app, under the font settings, I like to
  use 'Subpixel' and 'Full' hinting by default, since this looks good
  for most bundled fonts.

  However, there is occasionally a font (especially in the msttcorefonts
  package) that doesn't look good with these settings. So I want to
  override their rendering settings using .fonts.conf. My main tactic is
  to usually turn on the autohinter in 'hintslight' mode for certain
  fonts. Lets take Times new Roman as an example.. the .fonts.conf
  incantation to do this would be:

   

   Times New Roman
   
   true
   true
   hintslight 
   

  The odd thing about this is that the 'autohint' and 'hinting' edits
  seem to work, but the 'hintstyle' edit is always overridden by the
  control applet's settings. I can verify this by launching gedit each
  time after tweaking these settings.

  "fc-match -v 'Times New Roman'" does return the right settings, so its
  something in the chain of gtk libraries that is messing it up.

  Interstingly, it's not all possible edit settings that are ignored. It
  seems to only be hintstyle. For example if I were to say:

  
   

   Times New Roman
   
false  
   

  Then this works correctly. Only Times New Roman will be non-antialiased even 
in gedit. Even setting "hinting" to "false" works.. its only the hintstyle 
setting that doesn't work.
  [lspci]
  00:00.0 Host bridge [0600]: Intel Corporation 440BX/ZX/DX - 82443BX/ZX/DX 
Host bridge [8086:7190] (rev 01)
Subsystem: VMware Inc Device [15ad:1976]
  00:0f.0 VGA compatible controller [0300]: VMware Inc Abstract SVGA II Adapter 
[15ad:0405]
Subsystem: VMware Inc Abstract SVGA II Adapter [15ad:0405]

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

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


[Touch-packages] [Bug 1788643] Re: zombies pile up, system becomes unresponsive

2018-08-29 Thread David Coronel
Hi Ivan,

I launched an Hadoop HDInsight cluster in Azure and I see it runs on 6
nodes (2 head nodes and 4 worker nodes). Are those nodes the kind of
nodes that this issue is about? If so, is there a way I can have access
to those nodes or is it intentionally blocked for Azure users?

In any case, I think the first step in troubleshooting this issue would
be to run an sosreport while the system is experiencing the issue.

Install sosreport:

sudo apt update
sudo apt install sosreport


Run sosreport:

sudo sosreport -a

A root-only owned archive and a checksum file will be created in /tmp.

If you need help sending us the sosreport privately, you can talk to
Stephen Zarkos who has access to our support portal and FTP server.

Thanks,
David

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

Title:
  zombies pile up, system becomes unresponsive

Status in systemd package in Ubuntu:
  New

Bug description:
  Description:Ubuntu 16.04.5 LTS
  Release:16.04

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

  This problem is in Azure. We are seeing these problems on different
  systems. Worker nodes (Ubuntu 16.04) in a hadoop cluster start piling
  up zombies and become unresponsive. The syslog and the kernel logs
  don't provide much information.

  The only error we could correlate with what we are seeing was in the
  audit logs. See at the end of this message, the "Connection timed out"
  and the "Cannot create session: Already running in a session"
  messages.

  Our first suspect was memory pressure on the machines. We added
  logging and settings to reboot on out of memory, but all these turned
  to be red herrings.

  Aug 18 19:11:08 wn2-d3ncsp su[112600]: Successful su for root by root
  Aug 18 19:11:08 wn2-d3ncsp su[112600]: + ??? root:root
  Aug 18 19:11:08 wn2-d3ncsp su[112600]: pam_unix(su:session): session opened 
for user root by (uid=0)
  Aug 18 19:11:08 wn2-d3ncsp systemd-logind[1486]: New session c8 of user root.
  Aug 18 19:11:26 wn2-d3ncsp sshd[112690]: Did not receive identification 
string from 10.84.93.35
  Aug 18 19:11:34 wn2-d3ncsp su[112600]: pam_systemd(su:session): Failed to 
create session: Connection timed out
  Aug 18 19:11:34 wn2-d3ncsp su[112600]: pam_unix(su:session): session closed 
for user root
  Aug 18 19:11:34 wn2-d3ncsp systemd-logind[1486]: Removed session c8.

   
  Aug 18 19:12:03 wn2-d3ncsp sudo: ehiadmin : TTY=pts/1 ; PWD=/home/ehiadmin ; 
USER=root ; COMMAND=/bin/su -
  Aug 18 19:12:03 wn2-d3ncsp sudo: pam_unix(sudo:session): session opened for 
user root by ehiadmin(uid=0)
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: Successful su for root by root
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: + /dev/pts/1 root:root
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: pam_unix(su:session): session opened 
for user root by ehiadmin(uid=0)
  Aug 18 19:12:03 wn2-d3ncsp su[113085]: pam_systemd(su:session): Cannot create 
session: Already running in a session
  Aug 18 19:12:42 wn2-d3ncsp sshd[113274]: Did not receive identification 
string from 10.84.93.42
  Aug 18 19:13:37 wn2-d3ncsp su[113085]: pam_unix(su:session): session closed 
for user root
  Aug 18 19:13:37 wn2-d3ncsp sudo: pam_unix(sudo:session): session closed for 
user root
  Aug 18 19:13:37 wn2-d3ncsp sshd[112285]: pam_unix(sshd:session): session 
closed for user ehiadmin
  Aug 18 19:13:37 wn2-d3ncsp systemd-logind[1486]: Removed session 1291.

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

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


[Touch-packages] [Bug 575542] Re: resize2fs does not respect flex_bg

2018-08-29 Thread Theodore Ts'o
Yes, this has been fixed quite a while ago.  :-)

Online resize with flex_bg was fixed in 2012 --- call with the v3.10
kernel or so.

Offline resize was fixed around that time (e2fsprogs 1.43), but there
have been some bugs with flex_bg and off-line resizing, so I'd recommend
using at least e2fsprogs 1.44.x if you want to off-line resize file
systems with flex_bg.  And on-line resizing is actually going to be
safer in general --- mainly because it's less capable --- the scary bits
with off-line resizing are things that on-line resize can't do, like
shrink the file system or move the inode table around to make room for
more block group descriptors than were originally reserved at mkfs time.

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

Title:
  resize2fs does not respect flex_bg

Status in e2fsprogs package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: e2fsprogs

  When running resize2fs to perform an online extend of an ext4
  filesystem, it does not respect the flex_bg feature.  Instead, it lays
  out the added block groups with their normal non flex_bg positions.

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

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


[Touch-packages] [Bug 1789723] [NEW] installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-08-29 Thread John Busch
Public bug reported:

Ver 18 install failed at the clean up stage.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd-sysv 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic i686
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
Date: Wed Aug 29 13:36:29 2018
ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
InstallationDate: Installed on 2013-09-08 (1816 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.3ubuntu0.1
SourcePackage: systemd
Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
UpgradeStatus: Upgraded to bionic on 2018-08-29 (0 days ago)

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


** Tags: apport-package bionic i386 third-party-packages

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

Title:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Ver 18 install failed at the clean up stage.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Wed Aug 29 13:36:29 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-09-08 (1816 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release i386 (20130424)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: Upgraded to bionic on 2018-08-29 (0 days ago)

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

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


[Touch-packages] [Bug 1789717] [NEW] Totem Won't Play AV1 Video

2018-08-29 Thread Lonnie Lee Best
Public bug reported:

Totem cannot yet play the new AV1 format (an open and royalty-free video coding 
format):
https://en.wikipedia.org/wiki/AV1

Sample videos can be download from here for testing:
https://www.elecard.com/videos

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Aug 29 14:01:52 2018
InstallationDate: Installed on 2018-07-19 (41 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

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

Title:
  Totem Won't Play AV1 Video

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Totem cannot yet play the new AV1 format (an open and royalty-free video 
coding format):
  https://en.wikipedia.org/wiki/AV1

  Sample videos can be download from here for testing:
  https://www.elecard.com/videos

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer1.0-0 1.8.3-1~ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Aug 29 14:01:52 2018
  InstallationDate: Installed on 2018-07-19 (41 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1789717/+subscriptions

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


[Touch-packages] [Bug 1787873] Re: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers looping, abandoned

2018-08-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: hicolor-icon-theme (Ubuntu)
   Status: New => Confirmed

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

Title:
  package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers
  looping, abandoned

Status in hicolor-icon-theme package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04 -> 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: hicolor-icon-theme 0.17-2
  Uname: Linux 4.15.16-041516-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Fri Aug 17 09:17:18 2018
  Dependencies:
   
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2016-10-07 (681 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3
  SourcePackage: hicolor-icon-theme
  Title: package hicolor-icon-theme 0.17-2 failed to install/upgrade: triggers 
looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-08-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/hicolor-icon-theme/+bug/1787873/+subscriptions

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


[Touch-packages] [Bug 1789645] Re: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal

2018-08-29 Thread Timo Aaltonen
** No longer affects: wayland (Ubuntu)

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

Title:
  Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under
  Wayland session of Gnome Shell cause Ctrl+C interrupt for program
  running under Gnome Terminal

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello!

  I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text 
with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for running 
program. This happen even when I do this inside virt-viewer connection to 
virtual machine.
  Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work.

  A also find that switch keyboard layout with default Alt+Shift cause
  Opera display it's menu (seems like this is reaction to Alt like it
  was pressed as separate buttong) which interrupt text typing. Issue is
  not reproducible if user press Shift first, however many people used
  to hold Alt first and then press Shift.

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

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


[Touch-packages] [Bug 1789644] Re: Gnome Shell 3.29.90 crash in Wayland session on Evolution launch if external display attached

2018-08-29 Thread Timo Aaltonen
** No longer affects: wayland (Ubuntu)

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

Title:
  Gnome Shell 3.29.90 crash in Wayland session on Evolution launch if
  external display attached

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Hello!

  In Ubuntu 18.10 Gnome Shell 3.29.90 Wayland session always crash for
  me back to GDM3 when I close warning message that appear on Evolution
  3.29.90 (window that inform user that he is running unstable version
  of Evolution). Seems like this happen only if external display
  attached.

  Dell Latitude 7285
  Dock: Belkin USB-C Express Dock 3.1 HD F4U093
  External display: Dell UP3017

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

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


[Touch-packages] [Bug 1768830] Re: the audio can't work on Lenovo machines with dual analogue codecs under ubuntu 18.04

2018-08-29 Thread Anthony Wong
** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  the audio can't work on Lenovo machines with dual analogue codecs
  under ubuntu 18.04

Status in HWE Next:
  Fix Released
Status in alsa-lib package in Ubuntu:
  Fix Released
Status in alsa-lib source package in Bionic:
  Fix Released

Bug description:
  Steps:
  1. Install the ubuntu 18.04 on the machine of Lenovo P520.
  2. Login system.
  3. Plug in an external headset to record and playback in front and rear panel.

  Expected result:
  Output and input audio should work in front and rear panel.

  Actual result:
  Front panel audio doesn't work at all.
  Just output audio working, input audio does't work in rear panel.

  SRU Document:

  [Impact]

  We have several Lenovo machines like Lenovo P520 which have 2 analogue
  audio codecs on them, the internal speaker and front headset are
  connected to the 1st codec, the Rear mic, Line in and Line out are
  connected to the 2nd codec. So far, under ubuntu 18.04 with the alsa-
  lib/libasound2 v1.1.3-5, only the audio devices (internal speaker and
  front headset) on the 1st codec can work. To make all audio devices
  work on this machine, upstream provided 3 patches for kernel audio
  driver and 5 patches for alsa-lib. The kernel patches are already in
  the linux-4.12, so this is not a problem anymore under 18.04 since we
  use linux-4.15 in 18.04. For the 5 patches of alsa-lib, we need to
  backport them to v1.1.3-5, the 5 patches are list as below:

  2b9b3f01 ucm: Assure the user input card name not to exceed max size of card 
long name (it is in the alsa-lib v1.1.4)
  4b9297e6 ucm: Load device-specific configuration file based on the card long 
name (it is in the alsa-lib v1.1.4)
  b7e56af8 conf/ucm: Add dual HD-audio codecs config for Lenovo (it is in the 
alsa-lib v1.1.6)
  181f8e25 ucm: adding the folder of card_long_name when finding verb conf file 
(it is in the alsa-lib v1.1.6+)
  81db276f conf/ucm: increase the input volume for LineIn (it is in the 
alsa-lib v1.1.6+)

  Some explanation for these 5 patches, to make the audio work, the
  alsa-lib needs to add an audio configuration file and verb conf file
  for lenovo machines with dual codecs, these two files are put in a
  folder named by card_long_name, and the name of configuration file
  itself is also named by card_long_name, this is implemented by the
  patches of NO. 3rd and 5th.

  But the alsa-lib v1.1.3-5 itself doesn't support to search conf file with 
card_long_name, it only support searching with card_name, So we need to 
backport 3 patches to let alsa-lib v1.1.3-5 support to search with 
card_long_name, these 3 patches are No. 1st, 2nd and 4th.
   
  [Test Case]

  On the Lenovo machines with dual codecs (p520), I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can find the conf file and can parse the conf file
  successfully, and I tested the internal speaker, front headset, rear
  mic, line out and line in, all audio devices work well.

  On a HP and Dell machines without dual codecs, I insatlled the
  libasound2 v1.1.3-5ubuntu1 and libasound2-data v1.1.3-5ubuntu1, the
  alsa-lib can't find conf file by card_long_name and card_name, the
  pulseaudio will drive the sound card as before, so all audio functions
  worked well as before.

  [Regression Potential]

  After adding these 5 patches, there 2 two changes introduced into the
  alsa-lib v1.1.3-5ubuntu1:

  1) before: only have folder and conf files named by card_name; after: has one 
folder and conf file named by card_long_name, this folder and conf file will 
not affect others,
  2) before: the ucm parser will search the conf file/folder by card_name only; 
 after: the ucm parser will search the conf file/foler by card_long_name first, 
if it fails, it will fallback to use card_name to search again. So this change 
is compatible with old version.

  There is no regression since there is only one folder named by
  card_long_name in v1.1.3-5ubuntu1, if it runs on lenovo machine with
  dual codecs, it will find the conf file by card_long_name, if it runs
  on other machines, the search by card_long_name will definitely fail
  and fall back to search by card_name, then it will be same as before.
  So the objective of these 5 patches is to let lenovo machines with
  dual codecs find the conf file by card_long_name, let other machines
  fail to search by card_long_name, then fallback to original searching
  method - search by card_name.

  [Other Info]

  Since I could not find the alsa-lib repository in canonical, I just
  generated the debdiff with "apt-get source ...".

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

-- 
Mailing list: 

[Touch-packages] [Bug 1750947] Re: pulseaudio print lots of error when selecting unavailable profile

2018-08-29 Thread Anthony Wong
** Changed in: pulseaudio (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

** Changed in: hwe-next
   Status: New => Fix Released

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

Title:
  pulseaudio print lots of error when selecting unavailable profile

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released

Bug description:
  SRU Document:

  [Impact]

  A HDMI audio device usually has several output ports, each port
  represents a profile in pulseaudio, without this patch, the puseaudio
  always choose the first profile no matter it is active or not.

  [Test Case]

  connect each port of HDMI device, and check if the profile of that
  port is active or not.

  [Regression Potential]

  The patch will check all ports under each profile, if a profile only
  contains unavailable ports, this profile will be set to unavailable as
  well. Without this patch, all profiles are always available, then if a
  profile includes a unusable hdmi-output, and pulseaudio select this
  profile to be active (since its priority is the highest), the kernel
  audio driver will crash.

  I think this patch will not introduce regression:
  1) It is a correct logic to set a profile to be unavailable if it only 
contains unavailable ports.
  2) pulseaudio-artful and pulseaudio-bionic already include this patch, they 
work very well
  3) I tested this patch on 1 lenovo laptop, 1 lenovo desktop, 1 dell laptop 
and 1 dell desktop, all worked well as before
  4) tested this patch on two dell machines (LOAD5-DVT2-A2 and Dawson-JC-C 
without analogue audio) which have unusable hdmi-output profile on them, the 
kernel driver did not crash anymore and audio function worked very well.

  [Other Info]

  Only pulseaudio-xenial has this problem.

  we need to backport this commit to pulseaudio-xenial.

  
https://cgit.freedesktop.org/pulseaudio/pulseaudio/commit/?id=a222a07920731f3c4967faccab7469af50b428a4

  After printing out the error logs, the kernel crashes and system
  hangs.

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

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


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

2018-08-29 Thread Michel-Ekimia
We seem to hit the same problem here.

Can you post you NetworkManager.conf file ? if it was not upgraded
correctly that could be the issue

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

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

  testuser ☼ dig dcpdc001.orgsdomain.net +nocookie

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

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

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

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

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

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

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

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

  nameserver 127.0.0.53
  search orgsdomain

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

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

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

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

[Touch-packages] [Bug 1781049] Re: WiFI hard blocked after resuming laptop (RTL 8723BE)

2018-08-29 Thread Dexter
Yes, sure, could I take a few days? Have exams going on right now. I'll post my 
results as soon as possible. Also, any chance the bug-uploader can merge all 
uploads to one comment? Makes the bug report all cluttered up. 
Thank you

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

Title:
  WiFI hard blocked after resuming laptop (RTL 8723BE)

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

Bug description:
  I installed a fresh copy of Ubuntu 18.04 and everything seems to work
  fine, till I suspended and resumed the laptop. After resume, the wifi
  is hard blocked is rfkill. Reinstalling drivers, different drivers,
  nothing helped. All this was done under Secure Boot disabled under
  Ubuntu and BIOS (UEFI).

  The WiFI card is Realtek 8723BE. laptop is HP AB035TX Pavilion 15. If
  any further info is required, I'll add it on notification. I am
  familiar with Linux, any help will be really appreciated.

  
  P.S: If this wifi card is the issue, please suggest some PCI-mini card that 
will work with my Ubuntu, even after suspend and resume (Ideally a 2.4/5G + BT 
5.0)

  Thank you all!
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mythreya   1281 F pulseaudio
   /dev/snd/controlC1:  mythreya   1281 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-06-26 (16 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  IpRoute:
   default via 192.168.1.1 dev wlo1 proto dhcp metric 600 
   169.254.0.0/16 dev wlo1 scope link metric 1000 
   192.168.1.0/24 dev wlo1 proto kernel scope link src 192.168.1.6 metric 600
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0bda:b006 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 05c8:0379 Cheng Uei Precision Industry Co., Ltd 
(Foxlink) 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Hewlett-Packard HP Pavilion Notebook
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.10.6-2ubuntu1
  PackageArchitecture: amd64
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=300b2c4a-387a-49b5-9cb6-93de471ebbdb ro quiet splash nouveau.runpm=0 
vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-23-generic N/A
   linux-backports-modules-4.15.0-23-generic  N/A
   linux-firmware 1.173.1
  Tags:  bionic
  Uname: Linux 4.15.0-23-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/26/2018
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.87
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 8096
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 89.33
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.87:bd02/26/2018:svnHewlett-Packard:pnHPPavilionNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8096:rvr89.33:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion Notebook
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: Hewlett-Packard
  modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf:
   [connection]
   wifi.powersave = 2
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-30T14:39:45.608645
  mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 
2018-06-28T16:23:51.596655
  nmcli-con:
   NAME   UUID  TYPE  TIMESTAMP   
TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
   NETGEAR71  1a9d81bf-e7f5-4f8a-956f-96180dc493e1  wifi  1531450229  Thu 
12 Jul 2018 09:50:29 PM CDT  yes  0 no
/org/freedesktop/NetworkManager/Settings/2  yes wlo1activated  
/org/freedesktop/NetworkManager/ActiveConnection/2  --
   Ethernet   81087af0-5c8d-451f-84c0-1a95c6034098  ethernet  1530214661  Thu 
28 Jun 2018 02:37:41 PM CDT  yes  0 no
/org/freedesktop/NetworkManager/Settings/1  no  --  --   

[Touch-packages] [Bug 1789516] Re: ubuntu-bug crashes when filing bug for usb storage when udisks2 is not installed.

2018-08-29 Thread Brian Murray
** Package changed: apport (Ubuntu) => apport-symptoms (Ubuntu)

** Changed in: apport-symptoms (Ubuntu)
   Status: New => Triaged

** Changed in: apport-symptoms (Ubuntu)
   Importance: Undecided => Medium

** Tags added: cosmic

** Tags added: rls-cc-incoming

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

Title:
  ubuntu-bug crashes when filing bug for usb storage when udisks2 is not
  installed.

Status in apport-symptoms package in Ubuntu:
  Triaged

Bug description:
  If udisks2 is not installed, the following actions cause ubuntu-bug to
  crash:

  1. Run ubuntu-bug
  2. Click on "External or internal storage devices" -> OK
  3. Click on "Removable storage device is not mounted automatically" -> OK
  4. Click Close
  5. Connect offending device
  6. Click Close

  Result:
  ERROR: symptom script /usr/share/apport/symptoms/storage.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/ui.py", line 108, in 
thread_collect_info
  package = symb['run'](report, ui)
File "/usr/share/apport/symptoms/storage.py", line 29, in run
  return problem_removable(report, ui)
File "/usr/share/apport/symptoms/storage.py", line 52, in problem_removable
  universal_newlines=True)
File "/usr/lib/python3.6/subprocess.py", line 709, in __init__
  restore_signals, start_new_session)
File "/usr/lib/python3.6/subprocess.py", line 1344, in _execute_child
  raise child_exception_type(errno_num, err_msg, err_filename)
  FileNotFoundError: [Errno 2] No such file or directory: 'udisksctl': 
'udisksctl'

  Installing udisks2 solves the issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7.2
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CrashReports:
   640:1000:134:5505230:2018-08-20 12:15:41.972497262 -0700:2018-08-20 
12:15:29.675580645 -0700:/var/crash/_usr_bin_lyx.1000.crash
   600:0:134:1189445:2018-08-20 17:04:50.652675440 -0700:2018-08-20 
17:04:49.540680686 -0700:/var/crash/indicator-applet-session.0.crash
   600:0:134:1058633:2018-08-20 13:12:02.353175760 -0700:2018-08-20 
13:12:01.353169322 -0700:/var/crash/texlive-fonts-extra-doc.0.crash
   640:0:134:2053111:2018-08-20 13:54:02.571655686 -0700:2018-08-20 
13:53:55.195695778 -0700:/var/crash/_usr_sbin_synaptic.0.crash
  CurrentDesktop: XFCE
  Date: Tue Aug 28 16:37:24 2018
  InstallationDate: Installed on 2010-11-05 (2853 days ago)
  InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 
(20100816.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to bionic on 2018-08-16 (12 days ago)

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

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


[Touch-packages] [Bug 575542] Re: resize2fs does not respect flex_bg

2018-08-29 Thread Phillip Susi
You haven't happened to fix this in the last 8 years have you Ted? ;)

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

Title:
  resize2fs does not respect flex_bg

Status in e2fsprogs package in Ubuntu:
  Triaged
Status in linux package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: e2fsprogs

  When running resize2fs to perform an online extend of an ext4
  filesystem, it does not respect the flex_bg feature.  Instead, it lays
  out the added block groups with their normal non flex_bg positions.

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

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


[Touch-packages] [Bug 1789688] [NEW] Syste-sim package post-removal script subprocess returned error exit status 2

2018-08-29 Thread Henning Christensen
Public bug reported:

System-sim package post-removal script subprocess returned error exit
status 2

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Wed Aug 29 12:44:30 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
   Subsystem: Sony Corporation Wrestler [Radeon HD 6310] [104d:9082]
InstallationDate: Installed on 2011-09-19 (2536 days ago)
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: Sony Corporation VPCYB15KX
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=8ed5b153-f958-4b95-b6b4-66b959d46b7e ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2010
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0160Z7
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0160Z7:bd12/22/2010:svnSonyCorporation:pnVPCYB15KX:pvrC9015CZJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.family: VAIO
dmi.product.name: VPCYB15KX
dmi.product.version: C9015CZJ
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Fri Aug 24 12:37:01 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: radeon

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


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

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

Title:
  Syste-sim package post-removal script subprocess returned error exit
  status 2

Status in xorg package in Ubuntu:
  New

Bug description:
  System-sim package post-removal script subprocess returned error exit
  status 2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Wed Aug 29 12:44:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310] [1002:9802] 
(prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Wrestler [Radeon HD 6310] [104d:9082]
  InstallationDate: Installed on 2011-09-19 (2536 days ago)
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
  MachineType: Sony Corporation VPCYB15KX
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=8ed5b153-f958-4b95-b6b4-66b959d46b7e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2010
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: R0160Z7
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrR0160Z7:bd12/22/2010:svnSonyCorporation:pnVPCYB15KX:pvrC9015CZJ:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCYB15KX
  dmi.product.version: C9015CZJ
  

[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

2018-08-29 Thread Bin Li
I made a merge request on packaging tree, is it ok? Thanks!

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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


[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

2018-08-29 Thread Launchpad Bug Tracker
** Merge proposal linked:
   https://code.launchpad.net/~binli/ubuntu/+source/gdm3/+git/gdm3/+merge/353981

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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


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

2018-08-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Status in systemd package in Ubuntu:
  Confirmed

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

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

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

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

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

  testuser ☼ dig dcpdc001.orgsdomain.net +nocookie

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

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

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

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

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

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

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

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

  nameserver 127.0.0.53
  search orgsdomain

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

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

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

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

[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

2018-08-29 Thread Bin Li
@seb128,

 Could you help check if this debdiff is ok? Thanks!

** Attachment added: "gdm3_3.29.91-1ubuntu2_3.29.91-1ubuntu3.diff.gz"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5182212/+files/gdm3_3.29.91-1ubuntu2_3.29.91-1ubuntu3.diff.gz

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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


[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

2018-08-29 Thread Bin Li
Here is the patch for upstream, we need merge it into 3.29.91.

https://gitlab.gnome.org/GNOME/gdm/merge_requests/35


** Patch added: "0002-data-Makefile.am.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5182208/+files/0002-data-Makefile.am.patch

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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


[Touch-packages] [Bug 1788486] Re: apt behaviour when package with strict dependencies rules and version -gt in -updates than -security.

2018-08-29 Thread Eric Desrochers
Thanks for the clarification Julian.

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

Title:
  apt behaviour when package with strict dependencies rules and version
  -gt in -updates than -security.

Status in apt package in Ubuntu:
  Won't Fix
Status in landscape-client package in Ubuntu:
  Won't Fix
Status in apt source package in Xenial:
  Won't Fix
Status in landscape-client source package in Xenial:
  Won't Fix
Status in apt source package in Bionic:
  Won't Fix
Status in landscape-client source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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


[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

2018-08-29 Thread Bin Li
Here is the patch for
https://gitlab.gnome.org/GNOME/gdm/merge_requests/38


** Patch added: "0003-data-61-gdm.rules.in.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5182209/+files/0003-data-61-gdm.rules.in.patch

** Patch removed: "disable-wayland-bydefault.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5159579/+files/disable-wayland-bydefault.patch

** Patch removed: "ubuntu_disable_wayland_huawei_chipsets.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5160787/+files/ubuntu_disable_wayland_huawei_chipsets.patch

** Patch removed: "0001-Disable-wayland-for-Huawei-Hi1710-LP-1780076.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5179560/+files/0001-Disable-wayland-for-Huawei-Hi1710-LP-1780076.patch

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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


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

2018-08-29 Thread Ryan Harper
On Wed, Aug 29, 2018 at 8:41 AM Dimitri John Ledkov
 wrote:
>
> Do we need this in bionic?

Yes

>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1671951
>
> Title:
>   networkd should allow configuring IPV6 MTU
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+subscriptions

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

Title:
  networkd should allow configuring IPV6 MTU

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

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

  Upstream has discussed this issue here:

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

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

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

  
  Some context from those discussions

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

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

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

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

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

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


[Touch-packages] [Bug 1788486] Re: apt behaviour when package with strict dependencies rules and version -gt in -updates than -security.

2018-08-29 Thread Julian Andres Klode
Again: The security notice is about source packages, not binary
packages. libsystemd0 and systemd are both part of the systemd source
package, so obviously both need to be upgraded if installed.

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

Title:
  apt behaviour when package with strict dependencies rules and version
  -gt in -updates than -security.

Status in apt package in Ubuntu:
  Won't Fix
Status in landscape-client package in Ubuntu:
  Won't Fix
Status in apt source package in Xenial:
  Won't Fix
Status in landscape-client source package in Xenial:
  Won't Fix
Status in apt source package in Bionic:
  Won't Fix
Status in landscape-client source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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


[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

2018-08-29 Thread Bin Li
@seb128,

 Fine, let met try, could you tell me which one is used for packaging
branch. Thanks!

remotes/origin/ubuntu/cosmic
remotes/origin/ubuntu/cosmic-devel
remotes/origin/ubuntu/cosmic-proposed

remotes/origin/applied/ubuntu/cosmic
remotes/origin/applied/ubuntu/cosmic-devel
remotes/origin/applied/ubuntu/cosmic-proposed

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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


[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

2018-08-29 Thread Bin Li
Now the !38 was accepted too.

https://gitlab.gnome.org/GNOME/gdm/merge_requests/38

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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


[Touch-packages] [Bug 1788486] Re: apt behaviour when package version -gt in -update than -security with strict dependencies rules

2018-08-29 Thread Eric Desrochers
Then if 'apt' nor 'landscape' can't have viable change. The only other
workaround I can think of would be to modify the way USN database pickle
works to include dependencies for package with USN vulnerability to
avoid this situation like this at least for dependencies within the same
source package.

Example :
In this case, if instead of only flagging systemd, the USN was also flagging 
libsystemd0 (part of the same source package) the problem wouldn't have happen.

I would like to have security thought about this ?

- Eric

** Summary changed:

- apt behaviour when package version -gt in -update than -security with strict 
dependencies rules
+ apt behaviour when package version -gt in -updates than -security with strict 
dependencies rules

** Summary changed:

- apt behaviour when package version -gt in -updates than -security with strict 
dependencies rules
+ apt behaviour when package with strict dependencies rules and version -gt in 
-updates than -security.

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

Title:
  apt behaviour when package with strict dependencies rules and version
  -gt in -updates than -security.

Status in apt package in Ubuntu:
  Won't Fix
Status in landscape-client package in Ubuntu:
  Won't Fix
Status in apt source package in Xenial:
  Won't Fix
Status in landscape-client source package in Xenial:
  Won't Fix
Status in apt source package in Bionic:
  Won't Fix
Status in landscape-client source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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


[Touch-packages] [Bug 1788486] Re: apt behaviour with strict dependencies

2018-08-29 Thread Eric Desrochers
Then if 'apt' nor 'landscape' can have viable change. The only other
workaround I can think of would be to modify the way USN database pickle
works to include dependencies for package with USN vulnerability to
avoid this situation like this at least for dependencies within the same
source package.

Example :
In this case, if instead of only flagging systemd, the USN was also flagging 
libsystemd0 (part of the same source package) the problem wouldn't have happen.

I would like to have security thought about this ?

- Eric


** Summary changed:

- apt behaviour with strict dependencies
+ apt behaviour when package version -gt in -update than -security with strict 
dependencies rules

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

Title:
  apt behaviour when package with strict dependencies rules and version
  -gt in -updates than -security.

Status in apt package in Ubuntu:
  Won't Fix
Status in landscape-client package in Ubuntu:
  Won't Fix
Status in apt source package in Xenial:
  Won't Fix
Status in landscape-client source package in Xenial:
  Won't Fix
Status in apt source package in Bionic:
  Won't Fix
Status in landscape-client source package in Bionic:
  Won't Fix

Bug description:
  [Impact]

  We notice that situation while investigating a security update using
  Landscape, but it also applies to 'apt' outside the Landscape context.

  'apt' should be smarter to detect/install packages with strict
  dependencies such as systemd[1] when a version is specified for
  upgrade (Ex: $ apt-get install systemd=229-4ubuntu-21.1).

  It should automatically install the dependencies (if any) from that
  same version as well instead of failing trying to install the highest
  version available (if any) while installing the specified version for
  the one mentionned :

  
  $ apt-get install systemd=229-4ubuntu-21.1
  
  "systemd : Depends: libsystemd0 (= 229-4ubuntu21.1) but 229-4ubuntu21.4 is to 
be installed"
  =

  To face that problem :
  - Package with lower version should be found in -security ( Ex: 
systemd/229-4ubuntu21.1 )
  - Package with higher version should be found in -updates ( Ex: 
systemd/229-4ubuntu21.4 )
  - Package should have strict dependencies ( Ex: libsystemd0 (= 
${binary:Version}) )
  - The upgrade should only specify version for the package, without it's 
dependencies. (Ex: $ apt-get install systemd=229-4ubuntu-21.1" #systemd without 
libsystemd0 depends)

  Using systemd is a good reproducer, I'm sure finding other package
  with the same situation is easy.

  It has been easily reproduced with systemd on Xenial and Bionic so
  far.

  [1] debian/control
  Depends: ${shlibs:Depends},
  ${misc:Depends},
  libsystemd0 (= ${binary:Version}),
  ...

  [Workaround]
  If package + dependencies are specified, the upgrade work just fine :

  Ex: $ apt-get install systemd=229-4ubuntu-21.1
  libsystemd0=229-4ubuntu-21.1

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

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


[Touch-packages] [Bug 1789645] Re: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal

2018-08-29 Thread RussianNeuroMancer
** Description changed:

  Hello!
  
- I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy
- text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for
- running program. This happen even when I do this inside virt-viewer
- connection to virtual machine.
+ I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text 
with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for running 
program. This happen even when I do this inside virt-viewer connection to 
virtual machine.
+ Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work.
  
  A also find that switch keyboard layout with default Alt+Shift cause
  Opera display it's menu (seems like this is reaction to Alt like it was
  pressed as separate buttong) which interrupt text typing. Issue is not
  reproducible if user press Shift first, however many people used to hold
  Alt first and then press Shift.

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

Title:
  Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under
  Wayland session of Gnome Shell cause Ctrl+C interrupt for program
  running under Gnome Terminal

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

Bug description:
  Hello!

  I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy text 
with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for running 
program. This happen even when I do this inside virt-viewer connection to 
virtual machine.
  Other related hotkeys such as Ctrl+Shift+V, Ctrl+Shift+T also won't work.

  A also find that switch keyboard layout with default Alt+Shift cause
  Opera display it's menu (seems like this is reaction to Alt like it
  was pressed as separate buttong) which interrupt text typing. Issue is
  not reproducible if user press Shift first, however many people used
  to hold Alt first and then press Shift.

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

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


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

2018-08-29 Thread Dimitri John Ledkov
This is now in cosmic.

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

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

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

Title:
  networkd should allow configuring IPV6 MTU

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

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

  Upstream has discussed this issue here:

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

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

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

  
  Some context from those discussions

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

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

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

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

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

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


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

2018-08-29 Thread Dimitri John Ledkov
Do we need this in bionic?

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

Title:
  networkd should allow configuring IPV6 MTU

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

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

  Upstream has discussed this issue here:

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

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

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

  
  Some context from those discussions

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

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

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

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

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

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


[Touch-packages] [Bug 1789645] Re: Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under Gnome Terminal

2018-08-29 Thread RussianNeuroMancer
** Summary changed:

- Attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause Ctrl+C 
interrupt for running program 
+ Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under 
Wayland session of Gnome Shell cause Ctrl+C interrupt for program running under 
Gnome Terminal

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

Title:
  Attempt to copy text with Ctrl+Shift+C in Gnome Terminal running under
  Wayland session of Gnome Shell cause Ctrl+C interrupt for program
  running under Gnome Terminal

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

Bug description:
  Hello!

  I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy
  text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for
  running program. This happen even when I do this inside virt-viewer
  connection to virtual machine.

  A also find that switch keyboard layout with default Alt+Shift cause
  Opera display it's menu (seems like this is reaction to Alt like it
  was pressed as separate buttong) which interrupt text typing. Issue is
  not reproducible if user press Shift first, however many people used
  to hold Alt first and then press Shift.

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

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


[Touch-packages] [Bug 1785775] Re: New 2.42 version

2018-08-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  New 2.42 version

Status in librsvg package in Ubuntu:
  Confirmed

Bug description:
  There is a new upstream version available but it depends on a new
  toolchain which we don't want yet

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

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


[Touch-packages] [Bug 1789645] [NEW] Attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause Ctrl+C interrupt for running program

2018-08-29 Thread RussianNeuroMancer
Public bug reported:

Hello!

I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy
text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for
running program. This happen even when I do this inside virt-viewer
connection to virtual machine.

A also find that switch keyboard layout with default Alt+Shift cause
Opera display it's menu (seems like this is reaction to Alt like it was
pressed as separate buttong) which interrupt text typing. Issue is not
reproducible if user press Shift first, however many people used to hold
Alt first and then press Shift.

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: gnome-shell (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Attempt to copy text with Ctrl+Shift+C in Gnome Terminal cause Ctrl+C
  interrupt for running program

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

Bug description:
  Hello!

  I find that in Gnome Shell 3.29.90 (Wayland session) attempt to copy
  text with Ctrl+Shift+C in Gnome Terminal cause interrupt (Ctrl+C)  for
  running program. This happen even when I do this inside virt-viewer
  connection to virtual machine.

  A also find that switch keyboard layout with default Alt+Shift cause
  Opera display it's menu (seems like this is reaction to Alt like it
  was pressed as separate buttong) which interrupt text typing. Issue is
  not reproducible if user press Shift first, however many people used
  to hold Alt first and then press Shift.

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

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


[Touch-packages] [Bug 1780227] Re: locking sockets broken due to missing AppArmor socket mediation patches

2018-08-29 Thread  Christian Ehrhardt 
Thanks John for having that already fixed.
I wanted to let everybody subscribed here know that as of today Cosmic has the 
new systemd 239.
That said people (like me) who reboot rarely and still have a kernel before 
that will from now on see this when booting a cosmic container:

# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-08-29 10:39:04 UTC; 10min 
ago

And obviously name resolution in there is broken due to that.

I hope people will find bug 1789627 and not debug too long on their own
to eventually get here.

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

Title:
  locking sockets broken due to missing AppArmor socket mediation
  patches

Status in apparmor package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in apparmor source package in Xenial:
  Invalid
Status in linux source package in Xenial:
  Fix Released
Status in apparmor source package in Bionic:
  Invalid
Status in linux source package in Bionic:
  Fix Released

Bug description:
  Hey,

  Newer systemd makes use of locks placed on AF_UNIX sockets created
  with the socketpair() syscall to synchronize various bits and pieces
  when isolating services. On kernels prior to 4.18 that do not have
  backported the AppArmor socket mediation patchset this will cause the
  locks to be denied with EACCESS. This causes systemd to be broken in
  LXC and LXD containers that do not run unconfined which is a pretty
  big deal. We have seen various bug reports related to this. See for
  example [1] and [2].

  If feasible it would be excellent if we could backport the socket
  mediation patchset to all LTS kernels. Afaict, this should be 4.4 and
  4.15. This will unbreak a whole range of use-cases.

  The socket mediation patchset is available here:
  
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=80a17a5f501ea048d86f81d629c94062b76610d4

  
  [1]: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1575779
  [2]: https://github.com/systemd/systemd/issues/9493

  Thanks!
  Christian

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

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


[Touch-packages] [Bug 1789644] [NEW] Gnome Shell 3.29.90 crash in Wayland session on Evolution launch if external display attached

2018-08-29 Thread RussianNeuroMancer
Public bug reported:

Hello!

In Ubuntu 18.10 Gnome Shell 3.29.90 Wayland session always crash for me
back to GDM3 when I close warning message that appear on Evolution
3.29.90 (window that inform user that he is running unstable version of
Evolution). Seems like this happen only if external display attached.

Dell Latitude 7285
Dock: Belkin USB-C Express Dock 3.1 HD F4U093
External display: Dell UP3017

** Affects: gnome-shell (Ubuntu)
 Importance: Undecided
 Status: New

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

** Also affects: wayland
   Importance: Undecided
   Status: New

** No longer affects: wayland

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

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

Title:
  Gnome Shell 3.29.90 crash in Wayland session on Evolution launch if
  external display attached

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

Bug description:
  Hello!

  In Ubuntu 18.10 Gnome Shell 3.29.90 Wayland session always crash for
  me back to GDM3 when I close warning message that appear on Evolution
  3.29.90 (window that inform user that he is running unstable version
  of Evolution). Seems like this happen only if external display
  attached.

  Dell Latitude 7285
  Dock: Belkin USB-C Express Dock 3.1 HD F4U093
  External display: Dell UP3017

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

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


[Touch-packages] [Bug 1714518] Re: GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network shares in file chooser

2018-08-29 Thread adaucyjr
I'm using Debian Stretch. Is it possible to fix this problem using this
patch for Ubuntu?

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

Title:
  GTK+3 doesn't show FUSE/GVFS, smb (SMB/CIFS), sftp (SFTP/SSH) network
  shares in file chooser

Status in GTK+:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 source package in Trusty:
  Triaged
Status in gtk+3.0 source package in Xenial:
  Triaged
Status in gtk+3.0 source package in Artful:
  Won't Fix

Bug description:
  Steps to reproduce:
  1. Install any Gtk3 application such as Firefox or Chromium which use modern 
file-chooser dialog. 
  2. Mount network location through fstab or file-manager ("smb://" = SMB/CIFS, 
"sftp://; = SFTP/SSH and so on)
  3. Try to save/open file to/from the remote location from Gtk3 application.

  Expected results:
  * user is able to find network folder and save/open file to/from it with 
GtkFileChooser dialog

  Actual results:
  * user is unable to find network folder and save/open file to/from it with 
GtkFileChooser dialog and many user applications are affected

  -
  Original bug description is below:

  GTK+3 doesn't show FUSE network shares in file chooser - it used to do
  so in GTK+2, and the GTK+3 documentation still mentions it should do
  it.

  In the mean time, every user of every application switching to GTK+3
  -- including Chromium, at some point between 58 and 60 -- (a change
  which happened in 16.04 LTS!!), loses the functionality to open or
  save directly to a network share.

  I had chosen 16.04 LTS for deploying our workstations at work, and my 50 
users have been suddenly unable to do a simple operation they have to do dozens 
of times a day.
  They now have to "buffer" these files to their local filesystem when saving 
them and before uploading them, and then copy them to the company's network 
shares.
  They were already a little bit grumpy when it stopped working with Firefox, 
and are now really side-eyeing me when they apply updates and find Chromium 
broken.

  I have reported the bug upstream and provided a patch to fix this. I
  hope you'll be able and willing to include it to Ubuntu's GTK+3
  package.

  Thanks in advance.

  Colin

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

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


[Touch-packages] [Bug 1789627] Re: systemd-resolved of systemd 239 is failing in cosmic containers

2018-08-29 Thread  Christian Ehrhardt 
*** This bug is a duplicate of bug 1780227 ***
https://bugs.launchpad.net/bugs/1780227

On Container restart I found a bunch of unrelated apparmor denies that look 
like:
[1220983.698955] audit: type=1400 audit(1535545118.043:8745): apparmor="DENIED" 
operation="mount" info="failed flags match" error=-13 
profile="lxd-cpaelzer-cosmic-systemd_" name="/run/" pid=21102 
comm="mount" flags="rw, nosuid, nodev, remount"

That is LXD on the Host being denied to do things

Further when restarting systemd-resolved I saw these:
[1221051.971026] audit: type=1400 audit(1535545186.315:8854): apparmor="DENIED" 
operation="file_lock" profile="lxd-cpaelzer-cosmic-systemd_" 
pid=22329 comm="(resolved)" family="unix" sock_type="dgram" protocol=0 addr=none

Knowing that I also realized that the broken systems all had no reboot for 
quite some time, but the repro KVMs are obviously new.
With that in mind I found bug 1780227 sounds close enough I think.

Rebooted the host to a newer kernel and e voila that is it.

That said I'll make this a dup, but this is a rather "hard" impact.
We should make known that Cosmic since today fails to work in containers prior 
to Kernels:
- 4.4.0-134.160
- 4.15.0-33.36

Unfortunately the Guest-Container can enforce no dependencies onto the host 
kernel.
I'll discuss potential extra communication in standup today.

** This bug has been marked a duplicate of bug 1780227
   locking sockets broken due to missing AppArmor socket mediation patches

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

Title:
  systemd-resolved of systemd 239 is failing in cosmic containers

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  a few hours ago I realized that some of my containers have no working dns 
resolution anymore.
  Usually I'd think I broke something in my host network, but I was suspicious 
s it hit me on my laptop and on a server at about the same time.

  After a while I found that in those containers I have:
  systemd-resolve --status
  Failed to get global data: Failed to activate service 
'org.freedesktop.resolve1': timed out (service_start_timeout=25000ms)

  Later I found two more things leading me to some assumptions:
  1. I had no resolv.conf so the service seems to have issues
  root@c:~# ll /etc/resolv.conf 
  lrwxrwxrwx 1 root root 39 Aug 28 22:18 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf
  root@c:~# ll /run/systemd/resolve/stub-resolv.conf
  ls: cannot access '/run/systemd/resolve/stub-resolv.conf': No such file or 
directory

  2. I realized this only affects cosmic container
  Bionic container on the same machine is ok (so Host network should be ok I 
think).
  I didn't realize at first as other cosmic's were ok, but those were the 
containers not updated yet and tonight there was a publish of 
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu4


  Knowing that I checked logs and found:
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: Dependency failed for Wait for Network to be 
Configured.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd-wait-online.service: Job 
systemd-networkd-wait-online.service/start failed with result 'dependency'.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 1.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[1]: Starting Network Service...
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[1]: cloud-init.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: Starting Initial cloud-init job (metadata 
service crawler)...
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  

[Touch-packages] [Bug 1780165] Re: tc does not display value of prio and quantum options of htb on bionic

2018-08-29 Thread Ubuntu Foundations Team Bug Bot
The attachment "Fix miss of  htb option value of tc command" seems to be
a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]

** Tags added: patch

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

Title:
  tc does not display value of prio and quantum options of htb on bionic

Status in iproute2 package in Ubuntu:
  New

Bug description:
  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.

  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic
  $ uname -a
  Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -l | grep iproute
  ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
  $

  I sent the patch for this bug to ML of upstream.

  https://www.spinics.net/lists/netdev/msg511127.html

  I think that the above patch can be applied for the bionic.

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

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


[Touch-packages] [Bug 1789630] Re: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: installed systemd-shim package post-removal script subprocess returned error exit status 2

2018-08-29 Thread Eduardo dos Santos Barretto
** Information type changed from Private Security to Public

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

Title:
  package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade:
  installed systemd-shim package post-removal script subprocess returned
  error exit status 2

Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 failed to upgrade from 16.04 - resulting in black screen
  GUI failure

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd-sysv 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic i686
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: i386
  Date: Tue Aug 28 21:00:00 2018
  ErrorMessage: installed systemd-shim package post-removal script subprocess 
returned error exit status 2
  InstallationDate: Installed on 2013-01-10 (2056 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release i386 (20121017.2)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 
3.6.5-3ubuntu1
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.3ubuntu0.1
  SourcePackage: systemd
  Title: package systemd-sysv 237-3ubuntu10.3 failed to install/upgrade: 
installed systemd-shim package post-removal script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1789627] Re: systemd-resolved of systemd 239 is failing in cosmic containers

2018-08-29 Thread  Christian Ehrhardt 
Pattern?: I realized that in all good cases before I had lxd running in 18.10
So I added these runs with the same but with 18.04 KVMs
 x86->KVM-18.04->Container (lxc from deb): ok
 x86->KVM-18.04->Container (lxc from snap): ok

Ok, that wasn't the reason either :-/

I need to investigate the actual error around "Failed to update dynamic
user credentials: Permission denied".

So far the issue reproduces on these systems:
- Diamond (ppc64 18.10 deb)
- Horsea (x86 18.04 deb)
- my Laptop (18.04 snap)

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

Title:
  systemd-resolved of systemd 239 is failing in cosmic containers

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  a few hours ago I realized that some of my containers have no working dns 
resolution anymore.
  Usually I'd think I broke something in my host network, but I was suspicious 
s it hit me on my laptop and on a server at about the same time.

  After a while I found that in those containers I have:
  systemd-resolve --status
  Failed to get global data: Failed to activate service 
'org.freedesktop.resolve1': timed out (service_start_timeout=25000ms)

  Later I found two more things leading me to some assumptions:
  1. I had no resolv.conf so the service seems to have issues
  root@c:~# ll /etc/resolv.conf 
  lrwxrwxrwx 1 root root 39 Aug 28 22:18 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf
  root@c:~# ll /run/systemd/resolve/stub-resolv.conf
  ls: cannot access '/run/systemd/resolve/stub-resolv.conf': No such file or 
directory

  2. I realized this only affects cosmic container
  Bionic container on the same machine is ok (so Host network should be ok I 
think).
  I didn't realize at first as other cosmic's were ok, but those were the 
containers not updated yet and tonight there was a publish of 
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu4


  Knowing that I checked logs and found:
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: Dependency failed for Wait for Network to be 
Configured.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd-wait-online.service: Job 
systemd-networkd-wait-online.service/start failed with result 'dependency'.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 1.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[1]: Starting Network Service...
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[1]: cloud-init.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: Starting Initial cloud-init job (metadata 
service crawler)...
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 2.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[165]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[1]: Starting Network Service...
  Aug 29 10:23:25 c systemd[165]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network 

[Touch-packages] [Bug 1789637] [NEW] Proper support for frontend lock

2018-08-29 Thread Balint Reczey
Public bug reported:

Frontend lock support for apt and dpkg is tracked in LP: #1781169, this
bug tracks unattended-upgrades changes

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

Title:
  Proper support for frontend lock

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Frontend lock support for apt and dpkg is tracked in LP: #1781169,
  this bug tracks unattended-upgrades changes

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

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


[Touch-packages] [Bug 1789634] [NEW] computer does not reemerge from hibernate

2018-08-29 Thread pleabargain
Public bug reported:

I put the computer in hibernate
I came back and pressed start button to reawake machine.
No response.
Black screen.

Had to force hard reboot to get machine back to functional status.

lsb_release -rd
Description:Ubuntu 18.04.1 LTS
Release:18.04


posting this to systemd as that is power management package (as I understand)
apt-cache policy systemd
systemd:
  Installed: 237-3ubuntu10.3
  Candidate: 237-3ubuntu10.3
  Version table:
 *** 237-3ubuntu10.3 500
500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
100 /var/lib/dpkg/status
 237-3ubuntu10 500
500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.3
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: LXDE
Date: Wed Aug 29 14:31:57 2018
InstallationDate: Installed on 2018-08-24 (4 days ago)
InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Studio 1737
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=2b8227a7-271c-4d4c-8a2b-faa238133be0 ro quiet splash vt.handoff=1
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/14/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0P792H
dmi.board.vendor: Dell Inc.
dmi.board.version: A09
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: A09
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09:
dmi.product.name: Studio 1737
dmi.product.version: A09
dmi.sys.vendor: Dell Inc.

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

Title:
  computer does not reemerge from hibernate

Status in systemd package in Ubuntu:
  New

Bug description:
  I put the computer in hibernate
  I came back and pressed start button to reawake machine.
  No response.
  Black screen.

  Had to force hard reboot to get machine back to functional status.

  lsb_release -rd
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04

  
  posting this to systemd as that is power management package (as I understand)
  apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.3
Candidate: 237-3ubuntu10.3
Version table:
   *** 237-3ubuntu10.3 500
  500 http://us.archive.ubuntu.com/ubuntu bionic-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   237-3ubuntu10 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.3
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: LXDE
  Date: Wed Aug 29 14:31:57 2018
  InstallationDate: Installed on 2018-08-24 (4 days ago)
  InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Studio 1737
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=UUID=2b8227a7-271c-4d4c-8a2b-faa238133be0 ro quiet splash vt.handoff=1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/14/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0P792H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A09
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A09
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/14/2011:svnDellInc.:pnStudio1737:pvrA09:rvnDellInc.:rn0P792H:rvrA09:cvnDellInc.:ct8:cvrA09:
  dmi.product.name: Studio 1737
  dmi.product.version: A09
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1789627] Re: systemd-resolved of systemd 239 is failing in cosmic containers

2018-08-29 Thread  Christian Ehrhardt 
Some more back and forth,

Interim summary:
x86-18.10->Container (liblxc1 from git): ok
x86-18.10->Container (liblxc1 from deb): ok
ppc-18.10->Container (lxc from deb) : broken
x86-18.04->Container (lxc from snap): broken
x86->KVM-18.10->Container (lxc from deb): ok
x86->KVM-18.10->Container (lxc from snap): ok

I do not recognize the pattern yet :-/

But the PPC based test is on diamond which many of you have access to,
please give that a try there.

This blocks all sort of work, so I'd appreciate if we could find what the root 
cause is.
For the potential that more than just me are affected to have non-usable 
containers this is crit I think - we can rate it down once we know why it only 
affects some systems.

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

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

Title:
  systemd-resolved of systemd 239 is failing in cosmic containers

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  a few hours ago I realized that some of my containers have no working dns 
resolution anymore.
  Usually I'd think I broke something in my host network, but I was suspicious 
s it hit me on my laptop and on a server at about the same time.

  After a while I found that in those containers I have:
  systemd-resolve --status
  Failed to get global data: Failed to activate service 
'org.freedesktop.resolve1': timed out (service_start_timeout=25000ms)

  Later I found two more things leading me to some assumptions:
  1. I had no resolv.conf so the service seems to have issues
  root@c:~# ll /etc/resolv.conf 
  lrwxrwxrwx 1 root root 39 Aug 28 22:18 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf
  root@c:~# ll /run/systemd/resolve/stub-resolv.conf
  ls: cannot access '/run/systemd/resolve/stub-resolv.conf': No such file or 
directory

  2. I realized this only affects cosmic container
  Bionic container on the same machine is ok (so Host network should be ok I 
think).
  I didn't realize at first as other cosmic's were ok, but those were the 
containers not updated yet and tonight there was a publish of 
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu4


  Knowing that I checked logs and found:
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: Dependency failed for Wait for Network to be 
Configured.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd-wait-online.service: Job 
systemd-networkd-wait-online.service/start failed with result 'dependency'.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 1.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[1]: Starting Network Service...
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[1]: cloud-init.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: Starting Initial cloud-init job (metadata 
service crawler)...
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 2.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[165]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[1]: Starting Network Service...
  Aug 29 10:23:25 c systemd[165]: systemd-networkd.service: Failed at step USER 
spawning 

[Touch-packages] [Bug 1789627] Re: systemd-resolved of systemd 239 is failing in cosmic containers

2018-08-29 Thread  Christian Ehrhardt 
Then OTOH on a Fresh Cosmic VM it works to spawn a cosmic container.

ubuntu@c-systemd:~$ lxc launch ubuntu-daily:cosmic/amd64 c
Creating c
Starting c  
ubuntu@c-systemd:~$ lxc exec c bash
root@c:~# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2018-08-29 11:15:16 UTC; 29s ago
 Docs: man:systemd-resolved.service(8)
   https://www.freedesktop.org/wiki/Software/systemd/resolved
   
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
   
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
 Main PID: 152 (systemd-resolve)
   Status: "Processing requests..."
Tasks: 1 (limit: 1152)
   Memory: 6.5M
   CGroup: /system.slice/systemd-resolved.service
   └─152 /lib/systemd/systemd-resolved

Aug 29 11:15:16 c systemd[1]: Starting Network Name Resolution...
Aug 29 11:15:16 c systemd-resolved[152]: Positive Trust Anchors:
Aug 29 11:15:16 c systemd-resolved[152]: . IN DS 19036 8 2 
49aac11d7b6f6446702e54a1607371607a1a41855200fd2ce1cdde32f24e8fb5
Aug 29 11:15:16 c systemd-resolved[152]: . IN DS 20326 8 2 
e06d44b80b8f1d39a95c0b0d7c65d08458e880409bbc683457104237c7f8ec8d
Aug 29 11:15:16 c systemd-resolved[152]: Negative trust anchors: 
10.in-addr.arpa 16.172.in-addr.arpa 17.172.in-addr.arpa 18.172.in-addr.arpa 
19.172.in-addr.arpa 20.172.in
Aug 29 11:15:16 c systemd-resolved[152]: Using system hostname 'c'.
Aug 29 11:15:16 c systemd[1]: Started Network Name Resolution.

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

Title:
  systemd-resolved of systemd 239 is failing in cosmic containers

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  a few hours ago I realized that some of my containers have no working dns 
resolution anymore.
  Usually I'd think I broke something in my host network, but I was suspicious 
s it hit me on my laptop and on a server at about the same time.

  After a while I found that in those containers I have:
  systemd-resolve --status
  Failed to get global data: Failed to activate service 
'org.freedesktop.resolve1': timed out (service_start_timeout=25000ms)

  Later I found two more things leading me to some assumptions:
  1. I had no resolv.conf so the service seems to have issues
  root@c:~# ll /etc/resolv.conf 
  lrwxrwxrwx 1 root root 39 Aug 28 22:18 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf
  root@c:~# ll /run/systemd/resolve/stub-resolv.conf
  ls: cannot access '/run/systemd/resolve/stub-resolv.conf': No such file or 
directory

  2. I realized this only affects cosmic container
  Bionic container on the same machine is ok (so Host network should be ok I 
think).
  I didn't realize at first as other cosmic's were ok, but those were the 
containers not updated yet and tonight there was a publish of 
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu4


  Knowing that I checked logs and found:
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: Dependency failed for Wait for Network to be 
Configured.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd-wait-online.service: Job 
systemd-networkd-wait-online.service/start failed with result 'dependency'.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 1.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[1]: Starting Network Service...
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[1]: cloud-init.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: Starting Initial cloud-init job (metadata 
service crawler)...
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main 

[Touch-packages] [Bug 1789627] Re: systemd-resolved of systemd 239 is failing in cosmic containers

2018-08-29 Thread  Christian Ehrhardt 
The result of the Test Free did is here as well, and now I wonder what I did.
It is working for him just fine ... ?

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

Title:
  systemd-resolved of systemd 239 is failing in cosmic containers

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  a few hours ago I realized that some of my containers have no working dns 
resolution anymore.
  Usually I'd think I broke something in my host network, but I was suspicious 
s it hit me on my laptop and on a server at about the same time.

  After a while I found that in those containers I have:
  systemd-resolve --status
  Failed to get global data: Failed to activate service 
'org.freedesktop.resolve1': timed out (service_start_timeout=25000ms)

  Later I found two more things leading me to some assumptions:
  1. I had no resolv.conf so the service seems to have issues
  root@c:~# ll /etc/resolv.conf 
  lrwxrwxrwx 1 root root 39 Aug 28 22:18 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf
  root@c:~# ll /run/systemd/resolve/stub-resolv.conf
  ls: cannot access '/run/systemd/resolve/stub-resolv.conf': No such file or 
directory

  2. I realized this only affects cosmic container
  Bionic container on the same machine is ok (so Host network should be ok I 
think).
  I didn't realize at first as other cosmic's were ok, but those were the 
containers not updated yet and tonight there was a publish of 
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu4


  Knowing that I checked logs and found:
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: Dependency failed for Wait for Network to be 
Configured.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd-wait-online.service: Job 
systemd-networkd-wait-online.service/start failed with result 'dependency'.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 1.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[1]: Starting Network Service...
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[1]: cloud-init.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: Starting Initial cloud-init job (metadata 
service crawler)...
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 2.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[165]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[1]: Starting Network Service...
  Aug 29 10:23:25 c systemd[165]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 3.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: 

[Touch-packages] [Bug 1789627] Re: systemd-resolved failing in cosmic

2018-08-29 Thread  Christian Ehrhardt 
I got a report of 239-7ubuntu4 that Metal isn't affected and works being
upgraded.

Knowing that I fetched a cosmic VM which as of the current image starts
with 239-7ubuntu4 as well and works fine.

Free was so kind to double check if it is me and spawned a cosmic
container as well on his system.

I have seen that there is a new systemd in cosmic-proposed.
I tested upgrading the working bionic right through onto 239-7ubuntu5 but it 
fails with the same errors.

Updating the bug title/description to break in containers only as it
seems.

** Summary changed:

- systemd-resolved failing in cosmic
+ systemd-resolved of systemd 239 is failing in cosmic containers

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

Title:
  systemd-resolved of systemd 239 is failing in cosmic containers

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  a few hours ago I realized that some of my containers have no working dns 
resolution anymore.
  Usually I'd think I broke something in my host network, but I was suspicious 
s it hit me on my laptop and on a server at about the same time.

  After a while I found that in those containers I have:
  systemd-resolve --status
  Failed to get global data: Failed to activate service 
'org.freedesktop.resolve1': timed out (service_start_timeout=25000ms)

  Later I found two more things leading me to some assumptions:
  1. I had no resolv.conf so the service seems to have issues
  root@c:~# ll /etc/resolv.conf 
  lrwxrwxrwx 1 root root 39 Aug 28 22:18 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf
  root@c:~# ll /run/systemd/resolve/stub-resolv.conf
  ls: cannot access '/run/systemd/resolve/stub-resolv.conf': No such file or 
directory

  2. I realized this only affects cosmic container
  Bionic container on the same machine is ok (so Host network should be ok I 
think).
  I didn't realize at first as other cosmic's were ok, but those were the 
containers not updated yet and tonight there was a publish of 
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu4


  Knowing that I checked logs and found:
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: Dependency failed for Wait for Network to be 
Configured.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd-wait-online.service: Job 
systemd-networkd-wait-online.service/start failed with result 'dependency'.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 1.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[1]: Starting Network Service...
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[1]: cloud-init.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: Starting Initial cloud-init job (metadata 
service crawler)...
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 2.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
  Aug 29 10:23:25 c systemd[165]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[1]: Starting Network Service...
  Aug 29 10:23:25 c systemd[165]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, 

[Touch-packages] [Bug 1789627] Re: systemd-resolved of systemd 239 is failing in cosmic containers

2018-08-29 Thread  Christian Ehrhardt 
But OTOH picking a random system - here a powerpc box and starting a
cosmic container reproduces the same issue:

cpaelzer@diamond:~$ lxc launch ubuntu-daily:c cpaelzer-cosmic-systemd
Creating cpaelzer-cosmic-systemd

  
Starting cpaelzer-cosmic-systemd
cpaelzer@diamond:~$ cat /etc/os-release 
NAME="Ubuntu"
VERSION="18.10 (Cosmic Cuttlefish)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu Cosmic Cuttlefish (development branch)"
VERSION_ID="18.10"
HOME_URL="https://www.ubuntu.com/;
SUPPORT_URL="https://help.ubuntu.com/;
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
VERSION_CODENAME=cosmic
UBUNTU_CODENAME=cosmic
cpaelzer@diamond:~$ lxc exec cpaelzer-cosmic-systemd bash
root@cpaelzer-cosmic-systemd:~# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-08-29 11:10:32 UTC; 1min 
15s ago
 Docs: man:systemd-resolved.service(8)
   https://www.freedesktop.org/wiki/Software/systemd/resolved
   
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
   
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
  Process: 179 ExecStart=/lib/systemd/systemd-resolved (code=exited, 
status=217/USER)
 Main PID: 179 (code=exited, status=217/USER)

Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: systemd-resolved.service: 
Service has no hold-off time (RestartSec=0), scheduling restart.
Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: systemd-resolved.service: 
Scheduled restart job, restart counter is at 5.
Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: Stopped Network Name 
Resolution.
Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: systemd-resolved.service: 
Start request repeated too quickly.
Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: systemd-resolved.service: 
Failed with result 'exit-code'.
Aug 29 11:10:32 cpaelzer-cosmic-systemd systemd[1]: Failed to start Network 
Name Resolution.

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

Title:
  systemd-resolved of systemd 239 is failing in cosmic containers

Status in systemd package in Ubuntu:
  New

Bug description:
  Hi,
  a few hours ago I realized that some of my containers have no working dns 
resolution anymore.
  Usually I'd think I broke something in my host network, but I was suspicious 
s it hit me on my laptop and on a server at about the same time.

  After a while I found that in those containers I have:
  systemd-resolve --status
  Failed to get global data: Failed to activate service 
'org.freedesktop.resolve1': timed out (service_start_timeout=25000ms)

  Later I found two more things leading me to some assumptions:
  1. I had no resolv.conf so the service seems to have issues
  root@c:~# ll /etc/resolv.conf 
  lrwxrwxrwx 1 root root 39 Aug 28 22:18 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf
  root@c:~# ll /run/systemd/resolve/stub-resolv.conf
  ls: cannot access '/run/systemd/resolve/stub-resolv.conf': No such file or 
directory

  2. I realized this only affects cosmic container
  Bionic container on the same machine is ok (so Host network should be ok I 
think).
  I didn't realize at first as other cosmic's were ok, but those were the 
containers not updated yet and tonight there was a publish of 
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu4


  Knowing that I checked logs and found:
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
  Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
  Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
  Aug 29 10:23:25 c systemd[1]: Dependency failed for Wait for Network to be 
Configured.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd-wait-online.service: Job 
systemd-networkd-wait-online.service/start failed with result 'dependency'.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart 
job, restart counter is at 1.
  Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
  Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to 

[Touch-packages] [Bug 1767312] Re: [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264 videos

2018-08-29 Thread Christopher Snowhill
I only thought to mention the PPA to indicate that the bug still occurs
even in fairly bleeding edge Mesa code. I also still think it's either
something wrong with gstreamer-vaapi, or something that gstreamer-vaapi
is doing different from what mpv does for the same exact video. It
should probably be reported to upstream Mesa, just in case it really is
their bug.

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

Title:
  [radeon] Totem with gstreamer1.0-vaapi and Xorg: wrong color on H264
  videos

Status in gstreamer-vaapi package in Ubuntu:
  Confirmed
Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  Ii've found a bug on Ubuntu 18.04 (other distros, as fedora 27, debian 
stable, debian testing) aren't affected).
  When i try to reproduce a video that use h264 codec, i've wrong colors.
  I've a notebook with APU AMD A10 8700p, and integrated gpu radeon r6

  WORKAROUND:
  sudo apt remove gstreamer1.0-vaapi
  or
  sudo apt remove mesa-va-drivers

  See also bug 1720820.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer-vaapi/+bug/1767312/+subscriptions

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


[Touch-packages] [Bug 1744372] Re: gparted does not start - Unit -.mount does not exist, proceeding anyway.

2018-08-29 Thread Eduardo Gutierrez
*** This bug is a duplicate of bug 1652282 ***
https://bugs.launchpad.net/bugs/1652282

I have a similar problem not using Wayland. Ubuntu 18.04.1

eduardo@MiPcLinux:~$ sudo gparted
[sudo] contraseña para eduardo: 
Unit -.mount does not exist, proceeding anyway.
==
libparted : 3.2
==
¡No se puede hacer una partición fuera del disco!

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

Title:
  gparted does not start - Unit -.mount does not exist, proceeding
  anyway.

Status in gparted package in Ubuntu:
  Confirmed
Status in wayland package in Ubuntu:
  Invalid

Bug description:
  1. fresh ubuntu 18.04 daily: lsb_release -rd
  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  2. install gparted with Software:
  gparted:
    Installiert:   0.30.0-3ubuntu1
    Installationskandidat: 0.30.0-3ubuntu1
    Versionstabelle:
   *** 0.30.0-3ubuntu1 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  3. launch with icon - enter password - nothing.
  4.launch in terminal:
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  No protocol specified

  (gpartedbin:8328): Gtk-WARNING **: cannot open display: :0
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  How to Fix: run xhost +local: before gparted! # this only bypass the
  wayland restriction; meaning a security violation (not a fix !!! )

  thomas@ubuntu-1804:~$ xhost +local:
  non-network local connections being added to access control list
  thomas@ubuntu-1804:~$ gparted
  Unit -.mount does not exist, proceeding anyway.
  Created symlink /run/systemd/system/-.mount → /dev/null.
  Created symlink /run/systemd/system/boot-efi.mount → /dev/null.
  Created symlink /run/systemd/system/home.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns-vlc.mnt.mount → /dev/null.
  Created symlink /run/systemd/system/run-snapd-ns.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-1000.mount → /dev/null.
  Created symlink /run/systemd/system/run-user-120.mount → /dev/null.
  Created symlink /run/systemd/system/snap-core-3748.mount → /dev/null.
  Created symlink /run/systemd/system/snap-vlc-113.mount → /dev/null.
  Created symlink /run/systemd/system/tmp.mount → /dev/null.
  Gtk-Message: Failed to load module "canberra-gtk-module"
  ==
  libparted : 3.2
  ==
  Removed /run/systemd/system/-.mount.
  Removed /run/systemd/system/boot-efi.mount.
  Removed /run/systemd/system/home.mount.
  Removed /run/systemd/system/run-snapd-ns-vlc.mnt.mount.
  Removed /run/systemd/system/run-snapd-ns.mount.
  Removed /run/systemd/system/run-user-1000.mount.
  Removed /run/systemd/system/run-user-120.mount.
  Removed /run/systemd/system/snap-core-3748.mount.
  Removed /run/systemd/system/snap-vlc-113.mount.
  Removed /run/systemd/system/tmp.mount.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gparted 0.30.0-3ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jan 19 19:45:14 2018
  InstallationDate: Installed on 2018-01-18 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180111)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: gparted
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://launchpad.net/~touch-packages

[Touch-packages] [Bug 1789627] [NEW] systemd-resolved failing in cosmic

2018-08-29 Thread  Christian Ehrhardt 
Public bug reported:

Hi,
a few hours ago I realized that some of my containers have no working dns 
resolution anymore.
Usually I'd think I broke something in my host network, but I was suspicious s 
it hit me on my laptop and on a server at about the same time.

After a while I found that in those containers I have:
systemd-resolve --status
Failed to get global data: Failed to activate service 
'org.freedesktop.resolve1': timed out (service_start_timeout=25000ms)

Later I found two more things leading me to some assumptions:
1. I had no resolv.conf so the service seems to have issues
root@c:~# ll /etc/resolv.conf 
lrwxrwxrwx 1 root root 39 Aug 28 22:18 /etc/resolv.conf -> 
../run/systemd/resolve/stub-resolv.conf
root@c:~# ll /run/systemd/resolve/stub-resolv.conf
ls: cannot access '/run/systemd/resolve/stub-resolv.conf': No such file or 
directory

2. I realized this only affects cosmic container
Bionic container on the same machine is ok (so Host network should be ok I 
think).
I didn't realize at first as other cosmic's were ok, but those were the 
containers not updated yet and tonight there was a publish of 
https://launchpad.net/ubuntu/+source/systemd/239-7ubuntu4


Knowing that I checked logs and found:
Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
Aug 29 10:23:25 c systemd[158]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
Aug 29 10:23:25 c systemd[1]: Dependency failed for Wait for Network to be 
Configured.
Aug 29 10:23:25 c systemd[1]: systemd-networkd-wait-online.service: Job 
systemd-networkd-wait-online.service/start failed with result 'dependency'.
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no hold-off 
time (RestartSec=0), scheduling restart.
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart job, 
restart counter is at 1.
Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
Aug 29 10:23:25 c systemd[1]: Starting Network Service...
Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
Aug 29 10:23:25 c systemd[1]: cloud-init.service: Failed to reset devices.list: 
Operation not permitted
Aug 29 10:23:25 c systemd[161]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
Aug 29 10:23:25 c systemd[1]: Starting Initial cloud-init job (metadata service 
crawler)...
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no hold-off 
time (RestartSec=0), scheduling restart.
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart job, 
restart counter is at 2.
Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
Aug 29 10:23:25 c systemd[165]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
Aug 29 10:23:25 c systemd[1]: Starting Network Service...
Aug 29 10:23:25 c systemd[165]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with result 
'exit-code'.
Aug 29 10:23:25 c systemd[1]: Failed to start Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Service has no hold-off 
time (RestartSec=0), scheduling restart.
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Scheduled restart job, 
restart counter is at 3.
Aug 29 10:23:25 c systemd[1]: Stopped Network Service.
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed to reset 
devices.list: Operation not permitted
Aug 29 10:23:25 c systemd[1]: Starting Network Service...
Aug 29 10:23:25 c systemd[168]: systemd-networkd.service: Failed to update 
dynamic user credentials: Permission denied
Aug 29 10:23:25 c systemd[168]: systemd-networkd.service: Failed at step USER 
spawning /lib/systemd/systemd-networkd: Permission denied
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Main process exited, 
code=exited, status=217/USER
Aug 29 10:23:25 c systemd[1]: systemd-networkd.service: Failed with 

[Touch-packages] [Bug 1789627] Re: systemd-resolved failing in cosmic

2018-08-29 Thread  Christian Ehrhardt 
- Dropped my special KVM-LXD profile that I usually use
- Spawned a new Bionic container
  # working
- upgraded to systemd of cosmic

Right on upgrade I get the breakage:
The following packages will be upgraded:
  libnss-systemd libpam-systemd libsystemd0 systemd
4 upgraded, 0 newly installed, 0 to remove and 307 not upgraded.
Need to get 3404 kB of archives.
After this operation, 470 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://archive.ubuntu.com/ubuntu cosmic/main amd64 libnss-systemd amd64 
239-7ubuntu4 [111 kB]
Get:2 http://archive.ubuntu.com/ubuntu cosmic/main amd64 libpam-systemd amd64 
239-7ubuntu4 [114 kB]
Get:3 http://archive.ubuntu.com/ubuntu cosmic/main amd64 systemd amd64 
239-7ubuntu4 [2967 kB]
Get:4 http://archive.ubuntu.com/ubuntu cosmic/main amd64 libsystemd0 amd64 
239-7ubuntu4 [214 kB]
Fetched 3404 kB in 1s (4342 kB/s)   
(Reading database ... 28491 files and directories currently installed.)
Preparing to unpack .../libnss-systemd_239-7ubuntu4_amd64.deb ...
Unpacking libnss-systemd:amd64 (239-7ubuntu4) over (237-3ubuntu10.3) ...
Preparing to unpack .../libpam-systemd_239-7ubuntu4_amd64.deb ...
Unpacking libpam-systemd:amd64 (239-7ubuntu4) over (237-3ubuntu10.3) ...
Preparing to unpack .../systemd_239-7ubuntu4_amd64.deb ...
Unpacking systemd (239-7ubuntu4) over (237-3ubuntu10.3) ...
Preparing to unpack .../libsystemd0_239-7ubuntu4_amd64.deb ...
Unpacking libsystemd0:amd64 (239-7ubuntu4) over (237-3ubuntu10.3) ...
Setting up libsystemd0:amd64 (239-7ubuntu4) ...
Processing triggers for ureadahead (0.100.0-20) ...
Processing triggers for libc-bin (2.27-3ubuntu1) ...
Setting up systemd (239-7ubuntu4) ...
Installing new version of config file /etc/systemd/journald.conf ...
Installing new version of config file /etc/systemd/logind.conf ...
Installing new version of config file /etc/systemd/resolved.conf ...
Installing new version of config file /etc/systemd/system.conf ...
Warning: The unit file, source configuration file or drop-ins of 
systemd-networkd.service changed on disk. Run 'systemctl daemon-reload' to 
reload units.
Warning: Stopping systemd-networkd.service, but it can still be activated by:
  systemd-networkd.socket
Warning: The unit file, source configuration file or drop-ins of 
systemd-resolved.service changed on disk. Run 'systemctl daemon-reload' to 
reload units.
Job for systemd-resolved.service failed because the control process exited with 
error code.
See "systemctl status systemd-resolved.service" and "journalctl -xe" for 
details.
dpkg: error processing package systemd (--configure):
 installed systemd package post-installation script subprocess returned error 
exit status 1
Processing triggers for man-db (2.8.3-2) ...
Processing triggers for dbus (1.12.2-1ubuntu1) ...
dpkg: dependency problems prevent configuration of libnss-systemd:amd64:
 libnss-systemd:amd64 depends on systemd (= 239-7ubuntu4); however:
  Package systemd is not configured yet.

dpkg: error processing package libnss-systemd:amd64 (--configure):
 dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of libpam-systemd:amd64:
 libpam-systemd:amd64 depends on systemd (= 239-7ubuntu4); however:
  Package systemd is not configured yet.

dpkg: error processing package libpam-systemd:amd64 (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup 
error from a previous failure.

  No apport report written because the error message 
indicates its a followup error from a previous failure.
  Errors were encountered while 
processing:
 systemd
 libnss-systemd:amd64
 libpam-systemd:amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
root@b-systemd:~# systemctl status systemd-resolved
● systemd-resolved.service - Network Name Resolution
   Loaded: loaded (/lib/systemd/system/systemd-resolved.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2018-08-29 10:55:44 UTC; 19s ago
 Docs: man:systemd-resolved.service(8)
   https://www.freedesktop.org/wiki/Software/systemd/resolved
   
https://www.freedesktop.org/wiki/Software/systemd/writing-network-configuration-managers
   
https://www.freedesktop.org/wiki/Software/systemd/writing-resolver-clients
  Process: 819 ExecStart=/lib/systemd/systemd-resolved (code=exited, 
status=217/USER)
 Main PID: 819 (code=exited, status=217/USER)

Aug 29 10:55:44 b-systemd systemd[1]: systemd-resolved.service: Service has no 
hold-off time (RestartSec=0), scheduling restart.
Aug 29 10:55:44 b-systemd systemd[1]: systemd-resolved.service: Scheduled 
restart job, restart counter is at 5.
Aug 29 10:55:44 b-systemd systemd[1]: Stopped Network Name Resolution.
Aug 29 10:55:44 b-systemd systemd[1]: systemd-resolved.service: 

[Touch-packages] [Bug 1780165] Re: tc does not display value of prio and quantum options of htb on bionic

2018-08-29 Thread fumihiko kakuma
Attach the patch for this problem.

** Patch added: "Fix miss of  htb option value of tc command"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1780165/+attachment/5182070/+files/tc-htb.patch

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

Title:
  tc does not display value of prio and quantum options of htb on bionic

Status in iproute2 package in Ubuntu:
  New

Bug description:
  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.

  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic
  $ uname -a
  Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -l | grep iproute
  ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
  $

  I sent the patch for this bug to ML of upstream.

  https://www.spinics.net/lists/netdev/msg511127.html

  I think that the above patch can be applied for the bionic.

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

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


[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

2018-08-29 Thread  Christian Ehrhardt 
The suggested mitigation is in bionic-unapproved for the consideration
of the SRU team.

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Fix Released
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Triaged
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  Fix Released
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago)

To manage notifications about 

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

2018-08-29 Thread  Christian Ehrhardt 
@Erich - infinite hangs are usually due to the kernel somewhere, while
suggesting dig was a good idea just to try I wonder if we would have to
find what "host" actually hangs on to be sure that "dig" in turn will
not some day block on just the same.

Can one of you affected when the "host" command hangs check if it is spinning 
in userspace or if it is a kernel wchan?
$ cat /proc//wchan
and
$ perf top -p 
$ strace -rtf -p 
should help to get an idea what it is blocking on.

@Trent - you said you started on strace already, maybe you can provide the full 
logs here?
Also was it spinning in strace (on the same things) or just waiting?

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Fix Released
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Invalid
Status in avahi source package in Bionic:
  Triaged
Status in bind9 source package in Bionic:
  Confirmed
Status in avahi source package in Cosmic:
  Fix Released
Status in bind9 source package in Cosmic:
  Confirmed
Status in avahi package in Debian:
  New

Bug description:
  [Impact]

   * Network connections for some users fail (in some cases a direct
  interface, in others when connecting a VPN) because the 'host' command
  to check for .local in DNS called by /usr/lib/avahi/avahi-daemon-
  check-dns.sh never times out like it should - leaving the script
  hanging indefinitely blocking interface up and start-up. This appears
  to be a bug in host caused in some circumstances however we implement
  a workaround to call it under 'timeout' as the issue with 'host' has
  not easily been identified, and in any case acts as a fall-back.

  [Test Case]

   * Multiple people have been unable to create a reproducer on a
  generic machine (e.g. it does not occur in a VM), I have a specific
  machine I can reproduce it on (a Skull Canyon NUC with Intel I219-LM)
  by simply "ifdown br0; ifup br0" and there are clearly 10s of other
  users affected in varying circumstances that all involve the same
  symptoms but no clear test case exists. Best I can suggest is that I
  test the patch on my system to ensure it works as expected, and the
  change is only 1 line which is fairly easily auditible and
  understandable.

  [Regression Potential]

   * The change is a single line change to the shell script to call host with 
"timeout". When tested on working and non-working system this appears to 
function as expected. I believe the regression potential for this is 
subsequently low.
   * In attempt to anticipate possible issues, I checked that the timeout 
command is in the same path (/usr/bin) as the host command that is already 
called without a path, and the coreutils package (which contains timeout) is an 
Essential package. I also checked that timeout is not a built-in in bash, for 
those that have changed /bin/sh to bash (just in case).

  [Other Info]
   
   * N/A

  [Original Bug Description]

  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  

[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

2018-08-29 Thread Sebastien Bacher
Since you have your changes in git, could you open a merge request
against the packaging branch directly? that makes more sense than having
a debdiff in the bug

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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


[Touch-packages] [Bug 1774857] Re: sort doesn't sort and uniq loses data for many non-Latin scripts on UTF-8 locales

2018-08-29 Thread Miikka-Markus Alhonen
One user on debbugs.gnu.org reported that the problem is more likely
related to the locale / glibc than coreutils, and that it occurs on
Ubuntu 18.04 but not Fedora 28, in case that helps any. He thought it
might have already been fixed in glibc, since Fedora tends to be more up
to date than Ubuntu.

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

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

Title:
  sort doesn't sort and uniq loses data for many non-Latin scripts on
  UTF-8 locales

Status in coreutils package in Ubuntu:
  New
Status in glibc package in Ubuntu:
  New

Bug description:
  I’ve found out that sort doesn’t sort strings for many non-Latin
  scripts at all if the locale you’re using is one of en_US.UTF-8,
  fr_FR.UTF-8 or fi_FI.UTF-8 (probably others, too, but these are the
  ones I have tested). For locales ”C” and ko_KR.UTF-8, things work as
  expected. Here’s a test case:

  Open xterm, launch sort and input some lines of Syriac, Ethiopic,
  Korean, Japanese (Hiragana or Katakana, not Han) or Thai text
  repeating one of the lines twice. Here’s an example in Syriac:

  ܡܠܬܐ
  ܒܝܬܐ
  ܒܪܢܫܐ
  ܡܠܬܐ

  Sort produces the following:

  ܡܠܬܐ
  ܒܝܬܐ
  ܡܠܬܐ
  ܒܪܢܫܐ

  Here strings are ordered only according to their length but not
  characters. Even the two instances of the word ܡܠܬܐ are found on non-
  adjacent lines (1 and 3). The expected sort order based on Unicode
  points would be:

  ܒܝܬܐ
  ܒܪܢܫܐ
  ܡܠܬܐ
  ܡܠܬܐ

  If you further pass sort’s output to uniq, it produces the following:

  ܡܠܬܐ
  ܒܪܢܫܐ

  Here the word on line 2 ܒܝܬܐ is completely lost since, like sort, uniq
  seems to consider all Syriac strings of equal length as the same.

  Although this issue affects locale, I think it is not a locale issue
  per se, since perl seems to handle similar cases expectedly. For
  instance, the following command produces the expected result:

  perl -CDS -e 'use locale; use utf8; @str = ("ܡܠܬܐ", "ܒܝܬܐ", "ܒܪܢܫܐ",
  "ܡܠܬܐ"); foreach $i (sort @str) { print "$i\n"; }'

  Curiously enough, codepoints in Plane 1 seem to count as two
  codepoints of the basic plane, so that if you sort | uniq the
  following (six codepoints of Syriac and three codepoints of
  Phoenician):

  ܥܠܝܟܘܢ
  ँउक

  you get ”ܥܠܝܟܘܢ" as the result whereas ”ँउक” is lost. This is of
  course due to the UTF-8 representation of Plane 1 characters as two
  surrogate characters on the basic plane.

  Also curiously, LTR scripts seem to conflate with each other and RTL
  scripts among themselves but not across the directionality line, so
  that if you sort | uniq the following (three codepoints each in
  Ethiopic, Hangul, Syriac, Hiragana and Thai):

  ዘመን
  스물셋
  ܐܢܐ
  わたし
  ฟ้า

  you are left with:

  ܐܢܐ
  ዘመን

  That’s one line of Syriac and one line of Ethiopic; everything else
  was lost. This issue does not seem to affect most Indic scripts
  (Devanagari, Bengali, Telugu etc.) or Arabic. For CJK, things work as
  expected for the main Unicode block (4E00..9FFF) but not for Extension
  A (3400..4DBF, such as 㗖 or 㡘 or 㰋). For Greek, monotonic accents work
  fine but all polytonic letters are conflated (αὐλὸς and αὐλῆς conflate
  to αὐλῆς). For Hebrew, letters and vowel marks work fine but
  cantillation marks are conflated.

  
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  coreutils:
Installed: 8.28-1ubuntu1
Candidate: 8.28-1ubuntu1
Version table:
   *** 8.28-1ubuntu1 500
  500 http://mr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: coreutils 8.28-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jun  3 10:13:06 2018
  InstallationDate: Installed on 2017-02-13 (474 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=fi_FI.UTF-8
   SHELL=/bin/bash
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to bionic on 2018-05-31 (2 days ago)

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

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


[Touch-packages] [Bug 1772975] Re: /lib/udev/ifupdown-hotplug is not executable

2018-08-29 Thread Sworddragon
On checking this again with ifupdown 0.8.34ubuntu2 the file is now
executable.

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

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

Title:
  /lib/udev/ifupdown-hotplug is not executable

Status in ifupdown package in Ubuntu:
  Fix Released

Bug description:
  I'm using Ubuntu 18.10 dev with ifupdown 0.8.32ubuntu1 and /lib/udev
  /ifupdown-hotplug is not executable resulting in an error message at
  boot about missing permissions on that file and some negative side-
  effects (like /sys/class/net/eth0/carrier containing 0 instead of 1
  which might break things).

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

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


[Touch-packages] [Bug 1780076] Re: 18.04 login screen is skewed/distorted (incorrect stride) when using hibmc_drm graphics

2018-08-29 Thread Bin Li
I made two patches for upstream. Now the !35 was accepted, just wait for
!38.

https://gitlab.gnome.org/GNOME/gdm/merge_requests/35

https://gitlab.gnome.org/GNOME/gdm/merge_requests/38

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride) when using
  hibmc_drm graphics

Status in gdm3 package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New

Bug description:
  Upstream: https://gitlab.gnome.org/GNOME/mutter/issues/219

  We found the login screen is blur, with Huawei's chip.

  05:00.0 VGA compatible controller [0300]: Huawei Technologies Co.,
  Ltd. Hi1710 [iBMC Intelligent Management system chip w/VGA support]
  [19e5:1711] (rev 01)

  When we set the Wayland to disable, it could login.

  [daemon]
  # Uncoment the line below to force the login screen to use Xorg
  WaylandEnable=false

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

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


[Touch-packages] [Bug 1789523] Re: The ssh-agent launcher script fails to relaunch ssh-agent

2018-08-29 Thread Christopher Snowhill
Freedesktop tells me it's a downstream Debian script file.

https://gitlab.freedesktop.org/xorg/meta/issues/6

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

Title:
  The ssh-agent launcher script fails to relaunch ssh-agent

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  There is an issue with the Xsession, in which logging out and logging
  back in again does not clear environment variables, so the ssh-agent
  script thinks that the agent is already running, and thus does not
  bother to start it again.

  I have altered the script, albeit in not the most pretty way, to
  detect if the agent is already running, and if not, force a restart.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: x11-common 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: KDE
  Date: Tue Aug 28 17:33:34 2018
  Dependencies: lsb-base 9.20170808ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 4.15.0-32-generic, x86_64: installed
   anbox, 1, 4.15.0-33-generic, x86_64: installed
   nvidia, 396.54, 4.15.0-33-generic, x86_64: installed
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480] 
[1002:67df] (rev c7) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon RX 480 [1043:04fb]
  InstallationDate: Installed on 2018-08-04 (24 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: MSI MS-7751
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash amdgpu.dc=0 mem=33554428k 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/09/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V10.11
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z77A-GD65 (MS-7751)
  dmi.board.vendor: MSI
  dmi.board.version: 2.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 2.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV10.11:bd10/09/2013:svnMSI:pnMS-7751:pvr2.0:rvnMSI:rnZ77A-GD65(MS-7751):rvr2.0:cvnMSI:ct3:cvr2.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7751
  dmi.product.version: 2.0
  dmi.sys.vendor: MSI
  mtime.conffile..etc.X11.Xsession.d.90x11-common_ssh-agent: 
2018-08-28T17:23:14.025376
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.94+git1808281609.f3d90e8~b~padoka0
  version.libgl1-mesa-dri: libgl1-mesa-dri 
1:18.3~git180816191500.b618d7e~b~padoka0
  version.libgl1-mesa-glx: libgl1-mesa-glx 
1:18.3~git180816191500.b618d7e~b~padoka0
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.0.99+git1808290006.cba8fe4~b~padoka0
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1806121919.3d39506~b~padoka0
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1789244] Re: Sound driver does not appear to show

2018-08-29 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => New

** Summary changed:

- Sound driver does not appear to show
+ Sound driver does not appear to show [Intel HDMI/DP LPE Audio]

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

Title:
  Sound driver does not appear to show [Intel HDMI/DP LPE Audio]

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Using my Thomson Neo 10, which is a French made notebook with a UK
  qwerty keyboard, however it appears all support for this notebook is
  that all support is in other languages including french and it is not
  clear what the actual drivers are in order to attempt to find a way of
  installing it myself.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 27 17:24:50 2018
  InstallationDate: Installed on 2018-08-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: E.C116CM.Thomson.A01
  dmi.bios.version: 5.11
  dmi.board.asset.tag: WS_reserve
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: WS_reserve
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnE.C116CM.Thomson.A01:bvr5.11:bd05/18/2018:svnThomson:pnUK-NEO10A-2WH32:pvrWS_reserve:rvnDefaultstring:rnDefaultstring:rvrWS_reserve:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: UK-NEO10A-2WH32
  dmi.product.version: WS_reserve
  dmi.sys.vendor: Thomson

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

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


[Touch-packages] [Bug 1789244] Re: Sound driver does not appear to show

2018-08-29 Thread Richie Legend
As requested,

** Attachment added: "daemon.conf"
   
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1789244/+attachment/5182050/+files/daemon.conf

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

Title:
  Sound driver does not appear to show

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Using my Thomson Neo 10, which is a French made notebook with a UK
  qwerty keyboard, however it appears all support for this notebook is
  that all support is in other languages including french and it is not
  clear what the actual drivers are in order to attempt to find a way of
  installing it myself.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/pcmC1D1p', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', 
'/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Aug 27 17:24:50 2018
  InstallationDate: Installed on 2018-08-27 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2018
  dmi.bios.vendor: E.C116CM.Thomson.A01
  dmi.bios.version: 5.11
  dmi.board.asset.tag: WS_reserve
  dmi.board.name: Default string
  dmi.board.vendor: Default string
  dmi.board.version: WS_reserve
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnE.C116CM.Thomson.A01:bvr5.11:bd05/18/2018:svnThomson:pnUK-NEO10A-2WH32:pvrWS_reserve:rvnDefaultstring:rnDefaultstring:rvrWS_reserve:cvnDefaultstring:ct10:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: UK-NEO10A-2WH32
  dmi.product.version: WS_reserve
  dmi.sys.vendor: Thomson

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

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


[Touch-packages] [Bug 1789577] Re: An Unresponsive Window Freezes the Whole Desktop

2018-08-29 Thread Daniel van Vugt
Please report this bug to the Gnome developers here:

  https://gitlab.gnome.org/GNOME/mutter/issues/new

and then tell us the ID of the new bug.

** Package changed: xorg (Ubuntu) => gnome-shell (Ubuntu)

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

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

** 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 xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1789577

Title:
  An Unresponsive Window Freezes the Whole Desktop

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

Bug description:
  When debugging UI Applications, this application becomes naturally
  unresponsive when reaching an execution breakpoint. As a consequence,
  I see the "Force Quit or Wait" dialog, which freezes the whole
  desktop. I have no idea why that is, but it is super annoying.

  And this is of course not only the case when debugging, but happens as well 
for a "normal" application freeze. Why does a frozen application should 
immediately require my attention, no matter what else I am doing? Why does this 
require my whole desktop to freeze and wait for my input? 
  Sometimes I just notice a desktop freeze and dont know whats going on until I 
find this stupid "Quit or Wait" dialog. Super annoying.
  Please make this window not freeze everything else, nothing is so important 
that the whole desktop should freeze to force input.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 10:00:02 2018
  DistUpgraded: 2018-08-22 12:49:08,163 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:222e]
   NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e]
  InstallationDate: Installed on 2017-12-15 (256 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: LENOVO 20EQS00600
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: Upgraded to bionic on 2018-08-22 (6 days ago)
  dmi.bios.date: 06/28/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1EET69W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20EQS00600
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET69W(1.42):bd06/28/2017:svnLENOVO:pn20EQS00600:pvrThinkPadP50:rvnLENOVO:rn20EQS00600:rvrNODPK:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad P50
  dmi.product.name: 20EQS00600
  dmi.product.version: ThinkPad P50
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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


[Touch-packages] [Bug 1789577] [NEW] An Unresponsive Window Freezes the Whole Desktop

2018-08-29 Thread bananenkasper
Public bug reported:

When debugging UI Applications, this application becomes naturally
unresponsive when reaching an execution breakpoint. As a consequence, I
see the "Force Quit or Wait" dialog, which freezes the whole desktop. I
have no idea why that is, but it is super annoying.

And this is of course not only the case when debugging, but happens as well for 
a "normal" application freeze. Why does a frozen application should immediately 
require my attention, no matter what else I am doing? Why does this require my 
whole desktop to freeze and wait for my input? 
Sometimes I just notice a desktop freeze and dont know whats going on until I 
find this stupid "Quit or Wait" dialog. Super annoying.
Please make this window not freeze everything else, nothing is so important 
that the whole desktop should freeze to force input.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
Uname: Linux 4.15.0-33-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Aug 29 10:00:02 2018
DistUpgraded: 2018-08-22 12:49:08,163 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 530 [17aa:222e]
 NVIDIA Corporation GM107GLM [Quadro M1000M] [10de:13b1] (rev a2) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GM107GLM [Quadro M1000M] [17aa:222e]
InstallationDate: Installed on 2017-12-15 (256 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
MachineType: LENOVO 20EQS00600
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to bionic on 2018-08-22 (6 days ago)
dmi.bios.date: 06/28/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: N1EET69W (1.42 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EQS00600
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1EET69W(1.42):bd06/28/2017:svnLENOVO:pn20EQS00600:pvrThinkPadP50:rvnLENOVO:rn20EQS00600:rvrNODPK:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad P50
dmi.product.name: 20EQS00600
dmi.product.version: ThinkPad P50
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic false-gpu-hang freeze 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/1789577

Title:
  An Unresponsive Window Freezes the Whole Desktop

Status in xorg package in Ubuntu:
  New

Bug description:
  When debugging UI Applications, this application becomes naturally
  unresponsive when reaching an execution breakpoint. As a consequence,
  I see the "Force Quit or Wait" dialog, which freezes the whole
  desktop. I have no idea why that is, but it is super annoying.

  And this is of course not only the case when debugging, but happens as well 
for a "normal" application freeze. Why does a frozen application should 
immediately require my attention, no matter what else I am doing? Why does this 
require my whole desktop to freeze and wait for my input? 
  Sometimes I just notice a desktop freeze and dont know whats going on until I 
find this stupid "Quit or Wait" dialog. Super annoying.
  Please make this window not freeze everything else, nothing is so important 
that the whole desktop should freeze to force input.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  

[Touch-packages] [Bug 1751657] Re: man journalctl gives info about -g option not present in command

2018-08-29 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

Title:
  man journalctl gives info about -g option not present in command

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  man journalctl documents a --grep option, however:

  $ journalctl -g a
  journalctl: invalid option -- 'g'

  $ journalctl --grep a
  Compiled without pattern matching support

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  Date: Sun Feb 25 21:53:29 2018
  InstallationDate: Installed on 2017-06-21 (248 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0cf3:e300 Atheros Communications, Inc. 
   Bus 001 Device 003: ID 0c45:6713 Microdia 
   Bus 001 Device 004: ID 10d7:1102  
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 15 9560
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-generic.efi.signed 
root=UUID=18bdf6ee-e85b-4eb2-8fd1-68cf15fe1167 ro quiet splash 
acpi_rev_override=5 pci=noaer vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2018-02-17 (8 days ago)
  dmi.bios.date: 12/15/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.7.0
  dmi.board.name: 05FFDN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.7.0:bd12/15/2017:svnDellInc.:pnXPS159560:pvr:rvnDellInc.:rn05FFDN:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 15 9560
  dmi.sys.vendor: Dell Inc.

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

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


[Touch-packages] [Bug 1334329] Re: Sound input settings not saved

2018-08-29 Thread Daniel van Vugt
Normally we would ask you to log a new bug, but since comment #43 looks
like it was not accompanied by a fix, and wasn't the original reporter,
then we can reopen this one...


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

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

** Tags added: bionic xenial

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

Title:
  Sound input settings not saved

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When attempting to set my preferred sound input device, simply leaving
  sound preferences and going back to sound preferences, and selecting
  input, causes the default SPDIF to be selected again, and not the
  internal microphone I preferred.  I made a video to demonstrate what I
  mean by this here:  http://youtu.be/9Q9EQvLl_rA

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  I really don't know.  It's just the sound preferences.

  3) What you expected to happen
  For my selected sound input to be saved.

  4) What happened instead
  Keeps defaulting to the top sound input

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brandon   23953 F pulseaudio
   /dev/snd/controlC0:  brandon   23953 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 25 11:20:14 2014
  InstallationDate: Installed on 2014-04-26 (60 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Caicos HDMI Audio [Radeon HD 6400 Series] - HDA ATI HDMI
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/12
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B27.1201241646
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245A3940C91C80
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245A3940C91C80
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80:
  dmi.product.name: MacBookPro8,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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


[Touch-packages] [Bug 1334329] Re: Sound input settings not saved

2018-08-29 Thread Ville Ranki
Looks like this is back in 18.04.

I'd like to use laptop's internal mic for telcos, but after boot Ubuntu
always defaults to another sound input and it has to be manually
selected. Can anyone reproduce?

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

Title:
  Sound input settings not saved

Status in alsa-driver package in Ubuntu:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  When attempting to set my preferred sound input device, simply leaving
  sound preferences and going back to sound preferences, and selecting
  input, causes the default SPDIF to be selected again, and not the
  internal microphone I preferred.  I made a video to demonstrate what I
  mean by this here:  http://youtu.be/9Q9EQvLl_rA

  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  14.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  I really don't know.  It's just the sound preferences.

  3) What you expected to happen
  For my selected sound input to be saved.

  4) What happened instead
  Keeps defaulting to the top sound input

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  brandon   23953 F pulseaudio
   /dev/snd/controlC0:  brandon   23953 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Jun 25 11:20:14 2014
  InstallationDate: Installed on 2014-04-26 (60 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH successful
  Symptom_Card: Caicos HDMI Audio [Radeon HD 6400 Series] - HDA ATI HDMI
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through plughw:PCH 
successful
  Symptom_Type: None of the above
  Title: [HDA-Intel - HDA Intel PCH, recording] Recording problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/12
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP81.88Z.0047.B27.1201241646
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-94245A3940C91C80
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro8,2
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-94245A3940C91C80
  dmi.modalias: 
dmi:bvnAppleInc.:bvrMBP81.88Z.0047.B27.1201241646:bd01/24/12:svnAppleInc.:pnMacBookPro8,2:pvr1.0:rvnAppleInc.:rnMac-94245A3940C91C80:rvrMacBookPro8,2:cvnAppleInc.:ct10:cvrMac-94245A3940C91C80:
  dmi.product.name: MacBookPro8,2
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

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

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