[Touch-packages] [Bug 1801264] Re: Wifi drops out 1-30 minutes after boot on Ubuntu 18.10

[Cristian Aravena Romero]

Please reproduce the problem, do a hard reset and then run this command:

  journalctl -b-1 > prev_boot.txt

and send us the resulting file prev_boot.txt

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  Wifi drops out 1-30 minutes after boot on Ubuntu 18.10

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  I will boot, Wifi connects fine, and then the wifi drops out and no
  connection can be made until a restart. When I try to reconnect it
  "Connection Failed: Activation of network connection failed".  The
  Wifi works fine on phone and on Fedora 29.

  Network Manager 1.12.4

  Expected:

  Wifi stays connected

  Happened:

  Wifi drops out after 1-30 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 13:38:42 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-02 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IpRoute:
   default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 
   192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   enp0s20f0u2  ethernet  connected
/org/freedesktop/NetworkManager/Devices/3  Wired connection 1  
a79e5d9a-26c0-34c5-a20d-5a371d0eafd6  
/org/freedesktop/NetworkManager/ActiveConnection/9 
   wlp1s0   wifi  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
disabled  enabled  enabled

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

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

[Touch-packages] [Bug 1790416] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all (ALC3246)

[Launchpad Bug Tracker]

[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all (ALC3246)

Status in alsa-driver package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  O notebook travou,e posteriormente fui reproduzir áudio é simplesmente
  não reproduz, aparece como esta tocando, mas não sai som, nem nos
  alto-falantes interno nem fones-de-auvidos. nesse intermédio no painel
  de controle  apareceu "saída fictícia". Atualmente esta aparecendo os
  alto falantes e de HDMI, mas continua a não toca nada.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   hallison   2403 F...m pulseaudio
   /dev/snd/controlC0:  hallison   2403 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep  2 18:11:19 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-18 (472 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   hallison   2403 F...m pulseaudio
   /dev/snd/controlC0:  hallison   2403 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0P1MTV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/03/2017:svnDellInc.:pnInspiron5566:pvr:rvnDellInc.:rn0P1MTV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5566
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1790416] Re: [HDA-Intel - HDA Intel PCH, playback] No sound at all (ALC3246)

[Launchpad Bug Tracker]

[Expired for pulseaudio (Ubuntu) because there has been no activity for
60 days.]

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

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

Title:
  [HDA-Intel - HDA Intel PCH, playback] No sound at all (ALC3246)

Status in alsa-driver package in Ubuntu:
  Expired
Status in pulseaudio package in Ubuntu:
  Expired

Bug description:
  O notebook travou,e posteriormente fui reproduzir áudio é simplesmente
  não reproduz, aparece como esta tocando, mas não sai som, nem nos
  alto-falantes interno nem fones-de-auvidos. nesse intermédio no painel
  de controle  apareceu "saída fictícia". Atualmente esta aparecendo os
  alto falantes e de HDMI, mas continua a não toca nada.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-134.160-generic 4.4.140
  Uname: Linux 4.4.0-134-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   hallison   2403 F...m pulseaudio
   /dev/snd/controlC0:  hallison   2403 F pulseaudio
  CurrentDesktop: Unity
  Date: Sun Sep  2 18:11:19 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  InstallationDate: Installed on 2017-05-18 (472 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Áudio interno - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   hallison   2403 F...m pulseaudio
   /dev/snd/controlC0:  hallison   2403 F pulseaudio
  Symptom_Type: No sound at all
  Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/03/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.7
  dmi.board.name: 0P1MTV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.7:bd02/03/2017:svnDellInc.:pnInspiron5566:pvr:rvnDellInc.:rn0P1MTV:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.name: Inspiron 5566
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1801264] [NEW] Wifi drops out 1-30 minutes after boot on Ubuntu 18.10

[Luke Anscombe]

Public bug reported:

I will boot, Wifi connects fine, and then the wifi drops out and no
connection can be made until a restart. When I try to reconnect it
"Connection Failed: Activation of network connection failed".  The Wifi
works fine on phone and on Fedora 29.

Network Manager 1.12.4

Expected:

Wifi stays connected

Happened:

Wifi drops out after 1-30 minutes.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: network-manager 1.12.4-1ubuntu1
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  2 13:38:42 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-11-02 (0 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
IpRoute:
 default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 
 169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 
 192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 
metric 100
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=false
 WWANEnabled=true
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE   TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 enp0s20f0u2  ethernet  connected/org/freedesktop/NetworkManager/Devices/3  
Wired connection 1  a79e5d9a-26c0-34c5-a20d-5a371d0eafd6  
/org/freedesktop/NetworkManager/ActiveConnection/9 
 wlp1s0   wifi  unavailable  /org/freedesktop/NetworkManager/Devices/2  
--  ----
 
 lo   loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  
--  ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
WWAN-HW  WWAN
 running  1.12.4   connected  started  full  enabled enabled  
disabled  enabled  enabled

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug cosmic wayland-session

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

Title:
  Wifi drops out 1-30 minutes after boot on Ubuntu 18.10

Status in network-manager package in Ubuntu:
  New

Bug description:
  I will boot, Wifi connects fine, and then the wifi drops out and no
  connection can be made until a restart. When I try to reconnect it
  "Connection Failed: Activation of network connection failed".  The
  Wifi works fine on phone and on Fedora 29.

  Network Manager 1.12.4

  Expected:

  Wifi stays connected

  Happened:

  Wifi drops out after 1-30 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 13:38:42 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-02 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  IpRoute:
   default via 192.168.42.129 dev enp0s20f0u2 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s20f0u2 scope link metric 1000 
   192.168.42.0/24 dev enp0s20f0u2 proto kernel scope link src 192.168.42.66 
metric 100
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=false
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE   TYPE  STATEDBUS-PATH
  CONNECTION  CON-UUID  CON-PATH
   
   enp0s20f0u2  ethernet  connected
/org/freedesktop/NetworkManager/Devices/3  Wired connection 1  
a79e5d9a-26c0-34c5-a20d-5a371d0eafd6  
/org/freedesktop/NetworkManager/ActiveConnection/9 
   wlp1s0   wifi  unavailable  
/org/freedesktop/NetworkManager/Devices/2  --  --   
 -- 
   lo   loopback  unmanaged
/org/freedesktop/NetworkManager/Devices/1  --  --   
 --
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI  WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled  

[Touch-packages] [Bug 1766872] Re: 'Enable Network' in recovery mode not working properly.

[Cory F. Cohen]

With friendly-recovery version 0.2.38ubuntu1, selecting the check
filesystems option results in an error message like:

/etc/default/rcS: file or directory not found

This file does not exist on my system.  I don't know if the problem I'm
reporting is related to this issue, but it does seem to be the same as
another bug that was marked as a duplicate of this one (1767685).

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

Title:
  'Enable Network' in recovery mode not working properly.

Status in friendly-recovery package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Won't Fix
Status in friendly-recovery source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Won't Fix
Status in friendly-recovery source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Won't Fix
Status in friendly-recovery source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Won't Fix
Status in friendly-recovery source package in Disco:
  Invalid
Status in systemd source package in Disco:
  Won't Fix

Bug description:
  [Impact]

   * network menu in recovery mode doesn't work correctly, blocking at
  starting systemd services depends to enable networking.

  [Test Case]

   * Boot w/ Xenial or Bionic in recovery mode via grub
   * Choose "network" in friendly-recovery menu

   The network won't be activated and it'll be stuck at systemd-tty-ask-
  password :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask

  [Regression Potential]

  * Low.
  * All options works fine.
  * Cosmic has the same changes already in place.

  * According to xnox, resume option fails to boot now.
  After verification the 'resume' has the same effect before/after that change, 
it boots up but still seems to stick in 'recovery' option according to 
/proc/cmdline so I don't see any obvious behaviour change before and after.

  [Other Info]

   * Upstream :
  
https://bazaar.launchpad.net/~ubuntu-core-dev/friendly-recovery/ubuntu/changes/161?start_revid=161
  Revision  154 to 161

  [Original Description]

  This bug has been noticed after the introduction of the fix of (LP:
  #1682637) in Bionic.

  I have notice a block in Bionic when choosing 'Enable Network' option
  in recovery mode on different bionic vanilla system and I can
  reproduce all the time.

  I also asked colleagues to give it a try (for a second pair of eye on
  this) and they have the same result as me.

  Basically, when choosing 'Enable Network' it get block or lock.
  If we hit 'ctrl-c', then a shell arrive and the system has network 
connectivity.

  Here's what I find while enabling "systemd.debug-shell=1" from vtty9 :

  # pstree
  systemd-+-bash---pstree
  |-recovery-menu---network---systemctl---systemd-tty-ask
  |-systemd-journal
  

  # ps
  root 486 473 0 08:29 tty1 00:00:00 /bin/systemd-tty-ask-password-agent

  root 473 486 0 08:29 tty1 00:00:00 systemctl start dbus.socket

  root 486 283 0 08:29 tty1 00:00:00 /bin/sh /lib/recovery-
  mode/options/network

  Additionally,

  systemd-analyze blame:
  "Bootup is not yet finished. Please try again later"

  "systemctl list-jobs" is showing a 100 jobs in 'waiting' state

  The only 'running' unit is friendly-recovery.service :
  52 friendly-recovery.service start running

  The rest are all "waiting". My understanding is that "waiting" units
  will be executed only after those which are "running" are completed.
  Which explain why the "ctlr-c" allow the boot to continue.

  All the systemd special unit important at boot-up are waiting.
  7 sysinit.target start waiting
  3 basic.target   start waiting
  .

  Seems like systemd is not fully initialise in 'Recovery Mode' and
  doesn't allow any 'systemctl start' operation without
  password/passphrase request, which I suspect is hidden by the
  recovery-mode menu.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/friendly-recovery/+bug/1766872/+subscriptions

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

[Touch-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade

[Daniel van Vugt]

1. Can you please confirm where you are looking when you say "it no
longer shows any of the audio output devices"? Are you looking in
Settings > Sound > Output ?

2. Can you please try booting Ubuntu from USB:
   http://releases.ubuntu.com/18.10/
   and tell us if the problem still occurs in the live USB session?

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

Title:
  [System76 Oryx Pro] no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

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

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

[Touch-packages] [Bug 1799026] Re: Trojitá plaintext emails are displayed letter by letter

[Simon Quigley]

I can confirm that this fixes the issue with 5.212.0~alpha2-12ubuntu1.1
in Cosmic as well. Marking the bug tags.

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

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

Title:
  Trojitá plaintext emails are displayed letter by letter

Status in qtwebkit-opensource-src package in Ubuntu:
  Fix Released
Status in qtwebkit-opensource-src source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  Without this fix, when viewing plaintext emails in Trojitá, each
  letter is on its own line, making it difficult to read messages at
  best.

  Two fixes from upstream QtWebkit can fix this problem.

  [Test Case]

  Open any email when signed into an IMAP server with Trojitá, and if
  the email is an HTML email, select the "Plaintext" tab if it isn't
  selected already.

  It should be displayed normally, with a regular sized font.

  [Regression Potential]

  Little to none. If another QtWebkit-using package depends on the way
  this has already worked in an unsafe way, it could break, but this is
  unlikely.

  I could also see how it could potential to break if the email is very,
  very, very large, because it has to refresh the view, but at most you
  would expect some slowness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1799026/+subscriptions

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

[Touch-packages] [Bug 1800899] Re: Line out and headphones audio output keep swithing causing crackles in sound

[Daniel van Vugt]

Thanks.

It sounds like there is a bad connection in the port on the back panel.
That would explain both crackling and flickering settings. The
flickering would be Ubuntu quickly detecting spurious insertion/removal
or connection/disconnection of the headphones. So this sounds like a
hardware problem with that port.

** Package changed: alsa-driver (Ubuntu) => ubuntu

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

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

Title:
  Line out and headphones audio output keep swithing causing crackles in
  sound

Status in Ubuntu:
  Invalid

Bug description:
  There is an audio crackle every few seconds when I use headphones.
  Under the sound tab in settings the "Line Out-Built-in Audio" device
  flickers at the exact moment there is a crackle. By opening the
  pavucontrol audio manager I can see the "Built-in Audio Analog Stereo"
  output device port keeps switching to "Headphones (unplugged)" from
  "Line Out(plugged in)" for an instance.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  george10877 F pulseaudio
   /dev/snd/controlC2:  george10877 F pulseaudio
   /dev/snd/controlC0:  george10877 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 31 20:21:09 2018
  InstallationDate: Installed on 2018-10-09 (21 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulseAudioLog:
   Οκτ 31 18:49:55 LinuxPC dbus-daemon[775]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.38' (uid=1000 pid=1298 comm="/usr/bin/pulseaudio --start 
--log-target=syslog " label="unconfined")
   Οκτ 31 18:49:58 LinuxPC dbus-daemon[775]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.44' 
(uid=1000 pid=1298 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined")
   Οκτ 31 19:49:44 LinuxPC dbus-daemon[775]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.211' 
(uid=1000 pid=10877 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined")
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [To be filled by O.E.M., Realtek ALC887-VD, Green Line Out, Rear] 
Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170-HD3P-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd11/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3P-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

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

[Cristian Aravena Romero]

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19

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

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

** Description changed:

  The screen freezes suddenly when i'm trying to play an online video or
  when i have too many tabs or folders open.
+ 
+ ---
+ 
+ CurrentDmesg.txt:
+ [ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
+ [ 5465.753954] ata1.00: irq_stat 0x4008
+ [ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
+ [ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma 
131072 in
+ res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409 
(media error) 
+ [ 5465.753973] ata1.00: status: { DRDY ERR }
+ [ 5465.753976] ata1.00: error: { UNC }
+ [ 5466.031887] ata1.00: configured for UDMA/133
+ [ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
+ [ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current] 
+ [ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error - 
auto reallocate failed
+ [ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01 
00 00
+ [ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
+ [ 5466.031994] ata1: EH complete
+ 
+ ---
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 01:04:22 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
   nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
  DpkgLog:
  
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Very infrequently
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
     Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
  InstallationDate: Installed on 2018-10-04 (28 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: LENOVO 80QQ
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E0CN63WW
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Nano 5B6
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40700 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 100-15IBD
  dmi.modalias: 
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80QQ
  dmi.product.version: Lenovo ideapad 100-15IBD
  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.2
  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

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

Title:
  Xorg freeze

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

Bug 

[Touch-packages] [Bug 1801202] [NEW] Xorg freeze

[Maria]

Public bug reported:

The screen freezes suddenly when i'm trying to play an online video or
when i have too many tabs or folders open.

---

CurrentDmesg.txt:
[ 5465.753948] ata1.00: exception Emask 0x0 SAct 0x1c04 SErr 0x0 action 0x0
[ 5465.753954] ata1.00: irq_stat 0x4008
[ 5465.753959] ata1.00: failed command: READ FPDMA QUEUED
[ 5465.753969] ata1.00: cmd 60/00:10:00:9b:f5/01:00:53:00:00/40 tag 2 ncq dma 
131072 in
res 41/40:00:c0:9b:f5/00:01:53:00:00/00 Emask 0x409 
(media error) 
[ 5465.753973] ata1.00: status: { DRDY ERR }
[ 5465.753976] ata1.00: error: { UNC }
[ 5466.031887] ata1.00: configured for UDMA/133
[ 5466.031915] sd 0:0:0:0: [sda] tag#2 FAILED Result: hostbyte=DID_OK 
driverbyte=DRIVER_SENSE
[ 5466.031921] sd 0:0:0:0: [sda] tag#2 Sense Key : Medium Error [current] 
[ 5466.031925] sd 0:0:0:0: [sda] tag#2 Add. Sense: Unrecovered read error - 
auto reallocate failed
[ 5466.031932] sd 0:0:0:0: [sda] tag#2 CDB: Read(10) 28 00 53 f5 9b 00 00 01 00 
00
[ 5466.031935] print_req_error: I/O error, dev sda, sector 1408605120
[ 5466.031994] ata1: EH complete

---

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri Nov  2 01:04:22 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
 nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
DpkgLog:

ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Very infrequently
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:382b]
   Subsystem: Lenovo GM108M [GeForce 920MX] [17aa:382b]
InstallationDate: Installed on 2018-10-04 (28 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: LENOVO 80QQ
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=b0abddd7-646b-4707-bf44-54c3fc3ea828 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: E0CN63WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Nano 5B6
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 100-15IBD
dmi.modalias: 
dmi:bvnLENOVO:bvrE0CN63WW:bd10/21/2016:svnLENOVO:pn80QQ:pvrLenovoideapad100-15IBD:rvnLENOVO:rnNano5B6:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrLenovoideapad100-15IBD:
dmi.product.family: IDEAPAD
dmi.product.name: 80QQ
dmi.product.version: Lenovo ideapad 100-15IBD
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.2
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: linux (Ubuntu)
 Importance: Undecided
 Status: Confirmed

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


** Tags: amd64 apport-bug bionic freeze ubuntu

** Description changed:

  The screen freezes suddenly when i'm trying to play an online video or
  when i have too many tabs open.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Nov  2 01:04:22 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
-  nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
-  nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
+  nvidia, 390.77, 4.15.0-36-generic, x86_64: installed
+  nvidia, 390.77, 4.15.0-38-generic, x86_64: installed
  DpkgLog:
-  
+ 
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Very infrequently
  GraphicsCard:
-  Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a2e] 
(rev 09) (prog-if 00 

[Touch-packages] [Bug 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11

[Launchpad Bug Tracker]

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

** Changed in: openjdk-lts (Ubuntu)
   Status: New => Confirmed

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

Title:
  bold font rendeing in Java is broken in Cosmic with OpenJDK 11

Status in freetype package in Ubuntu:
  Confirmed
Status in openjdk-lts package in Ubuntu:
  New

Bug description:
  Since update to Cosmic, I see that bold fonts in Java have broken
  rendering. See attached 400% scaled PNG for illustration. The 'r' in
  bold rendering of "Hello World" shows basically a vertical line from
  the end of the hook end. I am not entirely sure this is freetype issue
  but some sources (https://github.com/adobe/brackets/issues/14290)
  suggest there is a bug in the 2.8.1 version that Cosmic seems to
  install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]).

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

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

[Touch-packages] [Bug 1799026] Re: Trojitá plaintext emails are displayed letter by letter

[Dan Simmons]

I have tested the qtwebkit patch in cosmic-proposed. Plaintext emails
are now displayed properly.

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

Title:
  Trojitá plaintext emails are displayed letter by letter

Status in qtwebkit-opensource-src package in Ubuntu:
  Fix Released
Status in qtwebkit-opensource-src source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

  Without this fix, when viewing plaintext emails in Trojitá, each
  letter is on its own line, making it difficult to read messages at
  best.

  Two fixes from upstream QtWebkit can fix this problem.

  [Test Case]

  Open any email when signed into an IMAP server with Trojitá, and if
  the email is an HTML email, select the "Plaintext" tab if it isn't
  selected already.

  It should be displayed normally, with a regular sized font.

  [Regression Potential]

  Little to none. If another QtWebkit-using package depends on the way
  this has already worked in an unsafe way, it could break, but this is
  unlikely.

  I could also see how it could potential to break if the email is very,
  very, very large, because it has to refresh the view, but at most you
  would expect some slowness.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtwebkit-opensource-src/+bug/1799026/+subscriptions

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

[Touch-packages] [Bug 1801183] [NEW] all servers stuck in INIT after reboot

[Andrew Schulman]

Public bug reported:

Since I updated to 18.04.1 (ntp version 1:4.2.8p10+dfsg-5ubuntu7.1),
ntpd at boot leaves all remote servers in the INIT state:

$ ntpq -c peers
Thu Nov  1 06:33:19 EDT 2018
 remote   refid  st t when poll reach   delay   offset  jitter
==
 otc2.psu.edu.INIT.  16 u-   6400.0000.000   0.000
 ntp-2.vt.edu.INIT.  16 u-   6400.0000.000   0.000
 dns3.cit.cornel .INIT.  16 u-   6400.0000.000   0.000

This happens after every reboot. I have to restart the ntp service, then
it runs normally again.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: ntp 1:4.2.8p10+dfsg-5ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  1 18:23:58 2018
InstallationDate: Installed on 2015-05-01 (1280 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
NtpStatus:
 remote   refid  st t when poll reach   delay   offset  jitter
 ==
 +otc2.psu.edu146.186.222.43 u  344 137m  375   31.6120.222   1.043
 *ntp-2.vt.edu198.82.247.164   2 u  89m 137m  377   14.9301.267   2.263
 +dns3.cit.cornel 146.186.222.14   2 u 2032 137m  377   23.5622.050   1.578
SourcePackage: ntp
UpgradeStatus: Upgraded to bionic on 2018-09-27 (35 days ago)
modified.conffile..etc.default.ntp: [modified]
modified.conffile..etc.ntp.conf: [modified]
mtime.conffile..etc.default.ntp: 2016-04-29T06:09:59.875852
mtime.conffile..etc.ntp.conf: 2016-07-19T06:06:23.592683

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

Title:
  all servers stuck in INIT after reboot

Status in ntp package in Ubuntu:
  New

Bug description:
  Since I updated to 18.04.1 (ntp version 1:4.2.8p10+dfsg-5ubuntu7.1),
  ntpd at boot leaves all remote servers in the INIT state:

  $ ntpq -c peers
  Thu Nov  1 06:33:19 EDT 2018
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   otc2.psu.edu.INIT.  16 u-   6400.0000.000   0.000
   ntp-2.vt.edu.INIT.  16 u-   6400.0000.000   0.000
   dns3.cit.cornel .INIT.  16 u-   6400.0000.000   0.000

  This happens after every reboot. I have to restart the ntp service,
  then it runs normally again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 18:23:58 2018
  InstallationDate: Installed on 2015-05-01 (1280 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  NtpStatus:
   remote   refid  st t when poll reach   delay   offset  jitter
   
==
   +otc2.psu.edu146.186.222.43 u  344 137m  375   31.6120.222   
1.043
   *ntp-2.vt.edu198.82.247.164   2 u  89m 137m  377   14.9301.267   
2.263
   +dns3.cit.cornel 146.186.222.14   2 u 2032 137m  377   23.5622.050   
1.578
  SourcePackage: ntp
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (35 days ago)
  modified.conffile..etc.default.ntp: [modified]
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.default.ntp: 2016-04-29T06:09:59.875852
  mtime.conffile..etc.ntp.conf: 2016-07-19T06:06:23.592683

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

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

[Touch-packages] [Bug 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11

[Václav Haisman]

** Project changed: openjdk => openjdk-lts (Ubuntu)

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

Title:
  bold font rendeing in Java is broken in Cosmic with OpenJDK 11

Status in freetype package in Ubuntu:
  Confirmed
Status in openjdk-lts package in Ubuntu:
  New

Bug description:
  Since update to Cosmic, I see that bold fonts in Java have broken
  rendering. See attached 400% scaled PNG for illustration. The 'r' in
  bold rendering of "Hello World" shows basically a vertical line from
  the end of the hook end. I am not entirely sure this is freetype issue
  but some sources (https://github.com/adobe/brackets/issues/14290)
  suggest there is a bug in the 2.8.1 version that Cosmic seems to
  install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]).

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

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

[Touch-packages] [Bug 1801181] Re: Pixelized display

[Cristian Aravena Romero]

** Package changed: xorg (Ubuntu) => xorg-server (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/1801181

Title:
  Pixelized display

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

Bug description:
  Artefakty upgrading to 18.04 lts three iż a problem without display.
  I have no duch problem on 16.04 lts

  ---

  CurrentDmesg.txt:
  [   29.779035] radeon :01:00.0: r600_check_texture_resource:1566 tex 
pitch (1680, 0x40, 1) invalid
  [   29.779082] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
  [   30.612745] radeon :01:00.0: r600_check_texture_resource:1566 tex 
pitch (1680, 0x40, 1) invalid
  [   30.612804] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !

  --

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Thu Nov  1 22:51:23 2018
  DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py')
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
     Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:2115]
   Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] 
[1002:9591] (prog-if 00 [VGA controller])
     Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116]
  InstallationDate: Installed on 2015-03-10 (1332 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 2087A37
  PccardctlIdent:
   Socket 0:
     no product info available
  PccardctlStatus:
   Socket 0:
     no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET93WW (3.23 )
  dmi.board.name: 2087A37
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T500
  dmi.product.name: 2087A37
  dmi.product.version: ThinkPad T500
  dmi.sys.vendor: LENOVO
  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.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Nov  1 20:57:30 2018
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8

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

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

[Touch-packages] [Bug 1760220] Re: ubuntu-bug with program path says as a snap does not belong to a package

[Launchpad Bug Tracker]

This bug was fixed in the package apport - 2.20.10-0ubuntu14

---
apport (2.20.10-0ubuntu14) disco; urgency=medium

  * apport/ui.py: when using ubuntu-bug properly handle executables which
start with /snap/bin. (LP: #1760220)

 -- Brian Murray   Thu, 01 Nov 2018 09:30:11 -0700

** Changed in: apport (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  ubuntu-bug with program path says as a snap does not belong to a
  package

Status in apport package in Ubuntu:
  Fix Released

Bug description:
  apport's ui.py file contains the following code:

   809 # executable?
   810 elif '/' in self.args[0]:
   811 pkg = apport.packaging.get_file_package(self.args[0])
   812 if not pkg:
   813 optparser.error('%s does not belong to a package.' % 
self.args[0])
   814 sys.exit(1)
   815 self.args = []
   816 self.options.filebug = True
   817 self.options.package = pkg

  This will not provide any useful information about what to do if the
  'executable' is provided by a snap. Information similar to
  https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
  should be provided if the path is from a snap.

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

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

[Touch-packages] [Bug 1769480] Re: Ubuntu 18.04 - networkmanager dont show other wifi after few minutes

[Martin]

Is there any chance to reactivate that topic? I have the same issue on a fresh 
Lubuntu 18.10 installation on my Sony Vaio Notebook.
After 5 minutes the tray icon (nm-tray) only shows the current wifi connection 
(which still works), no others anymore.

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

Title:
  Ubuntu 18.04 - networkmanager dont show other wifi after few minutes

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

Bug description:
  how to reproduce:

  dd the iso to an usb drive and boot from it.
  List all wifi devices in live-mode and connect to one of it. Use the web for 
some minutes. Open up the wifi on the top right again and list the available 
networks - it dont show any others any more. Just the one you are connected to.

  How to overcome the bug: put the computer into airplane mode and go
  away from airplane mode again. Or: disconnect the usb wifi device and
  connect it again.

  Does this bug exist also on installed 18.04 and updated to last (apt update, 
apt upgrade, apt dist-upgrade)?
  Yes

  What wifi device is been used:
  ieee80211 phy0: rt2x00_set_rt: Info - RT chipset 3572, rev 0223 detected
  ieee80211 phy0: rt2x00_set_rf: Info - RF chipset 0009 detected
  ieee80211 phy0: Selected rate control algorithm 'minstrel_ht'
  usbcore: registered new interface driver rt2800usb
  ...
  ieee80211 phy0: rt2x00lib_request_firmware: Info - Loading firmware file 
'rt2870.bin'
  ieee80211 phy0: rt2x00lib_request_firmware: Info - Firmware detected - 
version: 0.36

  uname -a
  Linux t 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

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

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

[Touch-packages] [Bug 1801183] Re: all servers stuck in INIT after reboot

[Andrew Schulman]

OK, looking in /var/log/syslog, I see these entries from this morning's
boot:

Nov  1 06:27:47 helium ntpd[1212]: ntpd 4.2.8p10@1.3728-o (1): Starting
Nov  1 06:27:47 helium ntpd[1212]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -4g -u 125:135
Nov  1 06:27:47 helium ntpd[1243]: proto: precision = 0.042 usec (-24)
Nov  1 06:27:47 helium ntpd[1243]: restrict: ignoring line 11, address/host 
'louie.udel.edu' unusable.
Nov  1 06:27:47 helium ntpd[1243]: restrict: ignoring line 12, address/host 
'clock.psu.edu' unusable.
Nov  1 06:27:47 helium ntpd[1243]: restrict: ignoring line 13, address/host 
'ntp-2.vt.edu' unusable.
Nov  1 06:27:47 helium ntpd[1243]: restrict: ignoring line 14, address/host 
'ntp0.cornell.edu' unusable.
Nov  1 06:27:47 helium ntpd[1243]: Listen and drop on 0 v4wildcard 0.0.0.0:123
Nov  1 06:27:47 helium ntpd[1243]: Listen normally on 1 lo 127.0.0.1:123
Nov  1 06:27:47 helium ntpd[1243]: Listening on routing socket on fd #18 for 
interface updates
Nov  1 06:27:52 helium ntpd[1243]: Listen normally on 2 eth0 192.168.1.2:123
Nov  1 06:27:52 helium ntpd[1243]: new interface(s) found: waking up resolver
Nov  1 06:33:40 helium ntpd[1243]: ntpd exiting on signal 15 (Terminated)
Nov  1 06:33:40 helium ntpd[1243]: 128.118.25.3 local addr 192.168.1.2 -> 
Nov  1 06:33:40 helium ntpd[1243]: 198.82.247.71 local addr 192.168.1.2 -> 

Nov  1 06:33:40 helium ntpd[1243]: 132.236.56.250 local addr 192.168.1.2 -> 

Nov  1 06:33:40 helium ntpd[3473]: ntpd 4.2.8p10@1.3728-o (1): Starting
Nov  1 06:33:40 helium ntpd[3473]: Command line: /usr/sbin/ntpd -p 
/var/run/ntpd.pid -4g -u 125:135
Nov  1 06:33:40 helium ntpd[3476]: proto: precision = 0.058 usec (-24)
Nov  1 06:33:40 helium ntpd[3476]: Listen and drop on 0 v4wildcard 0.0.0.0:123
Nov  1 06:33:40 helium ntpd[3476]: Listen normally on 1 lo 127.0.0.1:123
Nov  1 06:33:40 helium ntpd[3476]: Listen normally on 2 eth0 192.168.1.2:123
Nov  1 06:33:40 helium ntpd[3476]: Listening on routing socket on fd #19 for 
interface updates

So ntpd is at first ignoring all of the 'restrict' commands because the
hostnames are 'unusable'. Why would that be? Is ntpd trying to start
before the external network interface is up?

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

Title:
  all servers stuck in INIT after reboot

Status in ntp package in Ubuntu:
  New

Bug description:
  Since I updated to 18.04.1 (ntp version 1:4.2.8p10+dfsg-5ubuntu7.1),
  ntpd at boot leaves all remote servers in the INIT state:

  $ ntpq -c peers
  Thu Nov  1 06:33:19 EDT 2018
   remote   refid  st t when poll reach   delay   offset  jitter
  ==
   otc2.psu.edu.INIT.  16 u-   6400.0000.000   0.000
   ntp-2.vt.edu.INIT.  16 u-   6400.0000.000   0.000
   dns3.cit.cornel .INIT.  16 u-   6400.0000.000   0.000

  This happens after every reboot. I have to restart the ntp service,
  then it runs normally again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ntp 1:4.2.8p10+dfsg-5ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 18:23:58 2018
  InstallationDate: Installed on 2015-05-01 (1280 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  NtpStatus:
   remote   refid  st t when poll reach   delay   offset  jitter
   
==
   +otc2.psu.edu146.186.222.43 u  344 137m  375   31.6120.222   
1.043
   *ntp-2.vt.edu198.82.247.164   2 u  89m 137m  377   14.9301.267   
2.263
   +dns3.cit.cornel 146.186.222.14   2 u 2032 137m  377   23.5622.050   
1.578
  SourcePackage: ntp
  UpgradeStatus: Upgraded to bionic on 2018-09-27 (35 days ago)
  modified.conffile..etc.default.ntp: [modified]
  modified.conffile..etc.ntp.conf: [modified]
  mtime.conffile..etc.default.ntp: 2016-04-29T06:09:59.875852
  mtime.conffile..etc.ntp.conf: 2016-07-19T06:06:23.592683

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

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

[Touch-packages] [Bug 1760220] Re: ubuntu-bug with program path says as a snap does not belong to a package

[Brian Murray]

** Also affects: apport (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

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

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

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

Title:
  ubuntu-bug with program path says as a snap does not belong to a
  package

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Bionic:
  Triaged
Status in apport source package in Cosmic:
  Triaged

Bug description:
  apport's ui.py file contains the following code:

   809 # executable?
   810 elif '/' in self.args[0]:
   811 pkg = apport.packaging.get_file_package(self.args[0])
   812 if not pkg:
   813 optparser.error('%s does not belong to a package.' % 
self.args[0])
   814 sys.exit(1)
   815 self.args = []
   816 self.options.filebug = True
   817 self.options.package = pkg

  This will not provide any useful information about what to do if the
  'executable' is provided by a snap. Information similar to
  https://code.launchpad.net/~juliank/ubuntu/bionic/apport/snap/+merge/342207
  should be provided if the path is from a snap.

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

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

[Touch-packages] [Bug 1778219] Re: unattended-upgrades hangs on shutdown, leaves system in a broken state

[Eric Desrochers]

This affects Bionic reported on (LP: #1796376). It was only fixed for
Cosmic.

I have tested w/ a test package of 'u-u' and it fixes the problem so
far, but I have asked impacted user to give it a try as well for double-
confirmation.

If it fixes the problem, I'll SRU it for Bionic.

- Eric

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

** Also affects: unattended-upgrades (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: init-system-helpers (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

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

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

Title:
  unattended-upgrades hangs on shutdown, leaves system in a broken state

Status in apt package in Ubuntu:
  Invalid
Status in init-system-helpers package in Ubuntu:
  Invalid
Status in snapd package in Ubuntu:
  New
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  New
Status in init-system-helpers source package in Bionic:
  New
Status in snapd source package in Bionic:
  New
Status in unattended-upgrades source package in Bionic:
  Confirmed

Bug description:
  [Impact]

   * Unattended-upgrades hangs and gets killed when installing upgrades
  that stat/stop services on shutdown, leaving the system in a broken
  state

  [Test Case]

   * Install an updated bionic system:
 $ lxc launch ubuntu:18.04 uu-shutdown-test
 # apt update
 ...

   * When testing the fixed version, install upgrade u-u at this point checking 
that u-u.service is set up before and is wanted by shutdown.target:
  # systemd-analyze dot | grep unatt
"unattended-upgrades.service"->"-.mount" [color="green"];
"unattended-upgrades.service"->"system.slice" [color="green"];
"unattended-upgrades.service"->"network.target" [color="green"];
"unattended-upgrades.service"->"systemd-journald.socket" 
[color="green"];
"unattended-upgrades.service"->"local-fs.target" [color="green"];
"unattended-upgrades.service"->"-.mount" [color="black"];
"unattended-upgrades.service"->"system.slice" [color="black"];
"shutdown.target"->"unattended-upgrades.service" [color="green"];
"shutdown.target"->"unattended-upgrades.service" [color="grey66"];
 Color legend: black = Requires
   dark blue = Requisite
   dark grey = Wants
   red   = Conflicts
   green = After

   * Configure u-u to run on shutdown and install -updates:
 # echo 'Unattended-Upgrade::InstallOnShutdown "true";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-on-shutdown
 # echo 'Unattended-Upgrade::Allowed-Origins:: 
"${distro_id}:${distro_codename}-updates";' > 
/etc/apt/apt.conf.d/51unattended-upgrades-updates-too

   * Downgrade snapd:
 # apt install snapd=2.32.5+18.04
   
   * # reboot

   * With not fixed u-u observe the upgrade process being stuck:
# pstree| grep unatt
  
`-unattended-upgr---unattended-upgr-+-unattended-upgr---dpkg---snapd.prerm---systemctl
  `-{unattended-upgr}

   * With fixed u-u observe snapd update taking place and system
  rebooting after a few seconds with all updates installed

   * Since this fix is partially reverting the fix for LP: #1654600
  please test LP: #1654600 as well to avoid regressions.

  [Regression Potential]

   * As part of the fix manual changes were made to postinst to properly 
transition from coupling u-u.service with multi-user.target to coupling it with 
shutdown.target again which can make u-u started during normal boot when there 
is a bug in the implementation.
  on-testing the SRU.
   * Due to relationship changes between u-u.service, other services and 
targets u-u may fail to run on shutdown in case of an unexpected regression.

  [Original Bug Text]

  When using unattended-upgrades with "InstallOnShutdown" on Bionic, the
  package installation on various packages hangs until the systemd
  ShutdownTimeout (30min) is expired and systemd kills all processes and
  powers off/reboots the system.

  This leaves packages in an unconfigured, broken state. At least
  sometimes this cannot be fixed with a "dpkg --configure -a", but
  instead requires the user to manually reinstall the package that
  caused the hang.

  This appears to be a deadlock, because the hanging commands are always
  "systemctl stop ..." or "systemctl restart ...", etc.. If I understand
  this correctly, those systemctl commands block because systemd tries
  to shutdown the system and tries to satisfy all dependencies for the
  shutdown targets before those systemctl 

[Touch-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

[Eric Desrochers]

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

** Also affects: unattended-upgrades (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Disco)
   Importance: Medium
   Status: Invalid

** Also affects: unattended-upgrades (Ubuntu Bionic)
   Importance: Undecided
   Status: New

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

** Also affects: unattended-upgrades (Ubuntu Cosmic)
   Importance: Undecided
   Status: New

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

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

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

** Changed in: unattended-upgrades (Ubuntu Cosmic)
   Status: New => Fix Released

** Changed in: unattended-upgrades (Ubuntu Disco)
   Status: New => Fix Released

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

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

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Invalid
Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in linux source package in Bionic:
  Invalid
Status in unattended-upgrades source package in Bionic:
  Confirmed
Status in linux source package in Cosmic:
  Invalid
Status in unattended-upgrades source package in Cosmic:
  Fix Released
Status in linux source package in Disco:
  Invalid
Status in unattended-upgrades source package in Disco:
  Fix Released

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

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

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

[Touch-packages] [Bug 1801172] Re: Network Manager fails to require VPN

[Cristian Aravena Romero]

Please reproduce the problem, do a hard reset and then run this command:

  journalctl -b-1 > prev_boot.txt

and send us the resulting file prev_boot.txt

** Changed in: network-manager (Ubuntu)
   Status: New => Incomplete

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

Title:
  Network Manager fails to require VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  In Network Manager you can require that the local network requires a
  particular VPN connection. This works without issue, when networking
  is enabled, VPN connects automatically. But should there be any
  service interruption, Network Manager will reconnect using the local
  network and then exposing the real IP address.

  This issue only started to occur in 18.04 using GNome desktop
  environment. This was not an issue in 16.04 using GNome or Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 16:16:08 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.7.1 dev enp0s3 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000 
   192.168.7.0/24 dev enp0s3 proto kernel scope link src 192.168.7.143 metric 
100
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Wired connection 1  f6168b50-a792-36c3-8c34-cae535a9f95f  ethernet  
1541106764  Thu 01 Nov 2018 04:12:44 PM CDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s3  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp0s3  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  f6168b50-a792-36c3-8c34-cae535a9f95f  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1801181] Re: Pixelized display

[Cristian Aravena Romero]

Did this issue start happening after an update/upgrade? Was there a
prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer
to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest
v4.19 kernel[0].

If this bug is fixed in the mainline kernel, please add the following
tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag:
'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as
"Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19

** Description changed:

  Artefakty upgrading to 18.04 lts three iż a problem without display.
  I have no duch problem on 16.04 lts
+ 
+ ---
+ 
+ CurrentDmesg.txt:
+ [   29.779035] radeon :01:00.0: r600_check_texture_resource:1566 tex 
pitch (1680, 0x40, 1) invalid
+ [   29.779082] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
+ [   30.612745] radeon :01:00.0: r600_check_texture_resource:1566 tex 
pitch (1680, 0x40, 1) invalid
+ [   30.612804] [drm:radeon_cs_ioctl [radeon]] *ERROR* Invalid command stream !
+ 
+ --
+ 
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Thu Nov  1 22:51:23 2018
  DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py')
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
-  bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed
-  bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed
+  bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed
+  bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
-  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
-Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:2115]
-  Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] 
[1002:9591] (prog-if 00 [VGA controller])
-Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116]
+  Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
+    Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:2115]
+  Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] 
[1002:9591] (prog-if 00 [VGA controller])
+    Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116]
  InstallationDate: Installed on 2015-03-10 (1332 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 2087A37
  PccardctlIdent:
-  Socket 0:
-no product info available
+  Socket 0:
+    no product info available
  PccardctlStatus:
-  Socket 0:
-no card
+  Socket 0:
+    no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago)
  dmi.bios.date: 10/12/2012
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6FET93WW (3.23 )
  dmi.board.name: 2087A37
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T500
  dmi.product.name: 2087A37
  dmi.product.version: ThinkPad T500
  dmi.sys.vendor: LENOVO
  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.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Nov  1 20:57:30 2018
  xserver.configfile: default
  xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8

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

[Touch-packages] [Bug 1725840] Re: resolvconf not correctly configured after update from 17.04 to 17.10

[Damiön la Bagh]

This issue is also happening in Ubuntu 16.04LTS with backports enabled.
So I think there is something foobar with systemd-resolved and not
resolvconf.

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

Title:
  resolvconf not correctly configured after update from 17.04 to 17.10

Status in Cubic:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Confirmed

Bug description:
  After having updated my laptop from Ubuntu 17.04 to 17.10, the DNS
  lookup on my wireless network connection did not work any more.

  As it seems, the file /etc/resolv.conf was static and contained wrong
  data assigned by the NetworkManager. When I changed the file content
  manually to

nameserver 127.0.0.53

  DNS lookup worked fine. After reboot, however, I had to repeat this
  operation since NetworkManager seems to have replaced the file
  content.

  Finally, I found a solution. Running

  sudo dpkg-reconfigure resolvconf

  the file /etc/resolv.conf was replaced by the link

  /etc/resolv.conf -> ../run/resolvconf/resolv.conf

  Now, the wireless network seems to work properly.

  Hence, there must be some kind of bug during the update process from
  Ubuntu 17.04 to 17.10 that impedes resolvconf to be configured
  properly.

  Best regards,

  Artur

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: resolvconf 1.79ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Oct 21 23:17:38 2017
  InstallationDate: Installed on 2013-10-18 (1463 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: Upgraded to artful on 2017-10-19 (1 days ago)

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

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

[Touch-packages] [Bug 1799014] Re: bold font rendeing in Java is broken in Cosmic with OpenJDK 11

[Václav Haisman]

Here is a small test application that shows the issue.

** Attachment added: "HelloWorldSwing.java"
   
https://bugs.launchpad.net/ubuntu/+source/freetype/+bug/1799014/+attachment/5208006/+files/HelloWorldSwing.java

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

Title:
  bold font rendeing in Java is broken in Cosmic with OpenJDK 11

Status in freetype package in Ubuntu:
  Confirmed
Status in openjdk-lts package in Ubuntu:
  New

Bug description:
  Since update to Cosmic, I see that bold fonts in Java have broken
  rendering. See attached 400% scaled PNG for illustration. The 'r' in
  bold rendering of "Hello World" shows basically a vertical line from
  the end of the hook end. I am not entirely sure this is freetype issue
  but some sources (https://github.com/adobe/brackets/issues/14290)
  suggest there is a bug in the 2.8.1 version that Cosmic seems to
  install (libfreetype6/cosmic,now 2.8.1-2ubuntu2 amd64 [installed]).

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

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

[Touch-packages] [Bug 1801181] [NEW] Pixelized display

[Bogumil Roehrich]

Public bug reported:

Artefakty upgrading to 18.04 lts three iż a problem without display.
I have no duch problem on 16.04 lts

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Thu Nov  1 22:51:23 2018
DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py')
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed
 bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:2115]
 Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] 
[1002:9591] (prog-if 00 [VGA controller])
   Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116]
InstallationDate: Installed on 2015-03-10 (1332 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: LENOVO 2087A37
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic 
root=UUID=76e45c9b-b94c-414a-9c7f-cfbbafb58a1a ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-11-01 (0 days ago)
dmi.bios.date: 10/12/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: 6FET93WW (3.23 )
dmi.board.name: 2087A37
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr6FET93WW(3.23):bd10/12/2012:svnLENOVO:pn2087A37:pvrThinkPadT500:rvnLENOVO:rn2087A37:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T500
dmi.product.name: 2087A37
dmi.product.version: ThinkPad T500
dmi.sys.vendor: LENOVO
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.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Thu Nov  1 20:57:30 2018
xserver.configfile: default
xserver.errors: RADEON(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8

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


** Tags: amd64 apport-bug bionic 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/1801181

Title:
  Pixelized display

Status in xorg package in Ubuntu:
  New

Bug description:
  Artefakty upgrading to 18.04 lts three iż a problem without display.
  I have no duch problem on 16.04 lts

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Thu Nov  1 22:51:23 2018
  DistUpgraded: 2018-11-01 22:32:47,052 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py ([Errno 2] No such file or directory: 
'./xorg_fix_proprietary.py')
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.271+bdcom, 4.15.0-38-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.4.0-130-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:2115]
   Advanced Micro Devices, Inc. [AMD/ATI] RV635/M86 [Mobility Radeon HD 3650] 
[1002:9591] (prog-if 00 [VGA controller])
 Subsystem: Lenovo RV635/M86 [Mobility Radeon HD 3650] [17aa:2116]
  InstallationDate: Installed on 2015-03-10 (1332 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: LENOVO 2087A37
  PccardctlIdent:
   Socket 0:
 no product info available
  

[Touch-packages] [Bug 1801172] Re: Network Manager fails to require VPN

[Cristian Aravena Romero]

Your system is updated/upgrade?
--
Cristian Aravena Romero (caravena)

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

Title:
  Network Manager fails to require VPN

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  In Network Manager you can require that the local network requires a
  particular VPN connection. This works without issue, when networking
  is enabled, VPN connects automatically. But should there be any
  service interruption, Network Manager will reconnect using the local
  network and then exposing the real IP address.

  This issue only started to occur in 18.04 using GNome desktop
  environment. This was not an issue in 16.04 using GNome or Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 16:16:08 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.7.1 dev enp0s3 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000 
   192.168.7.0/24 dev enp0s3 proto kernel scope link src 192.168.7.143 metric 
100
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  STATE 
 ACTIVE-PATH SLAVE 
   Wired connection 1  f6168b50-a792-36c3-8c34-cae535a9f95f  ethernet  
1541106764  Thu 01 Nov 2018 04:12:44 PM CDT  yes  4294966297
no/org/freedesktop/NetworkManager/Settings/1  yes enp0s3  activated 
 /org/freedesktop/NetworkManager/ActiveConnection/1  --
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   enp0s3  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  
Wired connection 1  f6168b50-a792-36c3-8c34-cae535a9f95f  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Touch-packages] [Bug 1801172] [NEW] Network Manager fails to require VPN

[Espresso]

Public bug reported:

In Network Manager you can require that the local network requires a
particular VPN connection. This works without issue, when networking is
enabled, VPN connects automatically. But should there be any service
interruption, Network Manager will reconnect using the local network and
then exposing the real IP address.

This issue only started to occur in 18.04 using GNome desktop
environment. This was not an issue in 16.04 using GNome or Unity.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.10.6-2ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Nov  1 16:16:08 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2018-11-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
IpRoute:
 default via 192.168.7.1 dev enp0s3 proto dhcp metric 100 
 169.254.0.0/16 dev enp0s3 scope link metric 1000 
 192.168.7.0/24 dev enp0s3 proto kernel scope link src 192.168.7.143 metric 100
IwConfig:
 enp0s3no wireless extensions.
 
 lono wireless extensions.
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-con:
 NAMEUUID  TYPE  TIMESTAMP  
 TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  READONLY  
DBUS-PATH   ACTIVE  DEVICE  STATE  
ACTIVE-PATH SLAVE 
 Wired connection 1  f6168b50-a792-36c3-8c34-cae535a9f95f  ethernet  1541106764 
 Thu 01 Nov 2018 04:12:44 PM CDT  yes  4294966297no
/org/freedesktop/NetworkManager/Settings/1  yes enp0s3  activated  
/org/freedesktop/NetworkManager/ActiveConnection/1  --
nmcli-dev:
 DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 enp0s3  ethernet  connected  /org/freedesktop/NetworkManager/Devices/2  Wired 
connection 1  f6168b50-a792-36c3-8c34-cae535a9f95f  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  -- 
 ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

Title:
  Network Manager fails to require VPN

Status in network-manager package in Ubuntu:
  New

Bug description:
  In Network Manager you can require that the local network requires a
  particular VPN connection. This works without issue, when networking
  is enabled, VPN connects automatically. But should there be any
  service interruption, Network Manager will reconnect using the local
  network and then exposing the real IP address.

  This issue only started to occur in 18.04 using GNome desktop
  environment. This was not an issue in 16.04 using GNome or Unity.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Nov  1 16:16:08 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-11-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  IpRoute:
   default via 192.168.7.1 dev enp0s3 proto dhcp metric 100 
   169.254.0.0/16 dev enp0s3 scope link metric 1000 
   192.168.7.0/24 dev enp0s3 proto kernel scope link src 192.168.7.143 metric 
100
  IwConfig:
   enp0s3no wireless extensions.
   
   lono wireless extensions.
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAMEUUID  TYPE  
TIMESTAMP   TIMESTAMP-REAL   AUTOCONNECT  AUTOCONNECT-PRIORITY  
READONLY  DBUS-PATH   ACTIVE  DEVICE  

[Touch-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode

[Eric Desrochers]

The package include the following upstream fix :
https://github.com/mvo5/unattended-upgrades/commit/cda637b0d89973fd46382418893a23bef4195a2f
 

** Also 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/1796376

Title:
  Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable
  with unattended-upgrades on shutdown mode

Status in linux package in Ubuntu:
  Confirmed
Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  Since the following linux-cloud-tools-common package versions :

  Xenial : 4.4.0-135.161
  Bionic : 4.15.0-34.37

  the Systemd service unit file for hv-kvp-daemon has been modified with new 
dependencies that make the package unable to be upgraded with 
unattended-upgrades on shutdown mode.
  Unattended-upgrades hangs with the linux-cloud-tools-common package during 
"Preparing to unpack". The server restarts after the unattended-upgrades 
service timeout expires.

  - Package state after reboot :

  iFR linux-cloud-tools-common  4.15.0-34.37
  all  Linux kernel version specific cloud tools for version
  4.15.0

  - Unattended-upgrades dpkg logs :

  Log started: 2018-10-05  17:59:04
  (Reading database ... 52043 files and directories currently installed.)
  Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ...
  Log ended: 2018-10-05  18:00:54

  - Impact :

  The current impact is very important as all security updates are
  blocked until you manually fix each server with :

  dpkg --configure -a
  apt install --only-upgrade linux-cloud-tools-common

  - Workaround/Fix :

  As a simple straightforward fix, replacing :

  Before=shutdown.target cloud-init-local.service walinuxagent.service

  with :

  Before=shutdown.target walinuxagent.service

  makes the package upgradable during shutdown.

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

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

[Touch-packages] [Bug 1799868] Re: seq command has problems near its max integer

[C de-Avillez]

Closing INVALID, then, given this is a known, documented limitation.

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

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

Title:
  seq command has problems near its max integer

Status in coreutils package in Ubuntu:
  Invalid

Bug description:
  I can use seq(1) to generate sequences of large numbers if I use the
  default increment:

  $ seq 170141183460469231731687303715884105721 
170141183460469231731687303715884105725
  170141183460469231731687303715884105721
  170141183460469231731687303715884105722
  170141183460469231731687303715884105723
  170141183460469231731687303715884105724
  170141183460469231731687303715884105725
  $

  However, if I use an increment of 2 (which should stop 2 short of the max 
int,) it starts with the max integer+1 (2^127) and outputs it forever:
  $ seq 170141183460469231731687303715884105721 2 
170141183460469231731687303715884105725 | less
  170141183460469231731687303715884105728
  170141183460469231731687303715884105728
  170141183460469231731687303715884105728
  170141183460469231731687303715884105728
  .
  .
  .

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: coreutils 8.28-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 24 20:17:15 2018
  SourcePackage: coreutils
  UpgradeStatus: Upgraded to bionic on 2018-08-19 (66 days ago)

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

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

[Touch-packages] [Bug 1764965] Re: [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x faster

[José Miguel Sarasola]

Coming back from Pop!_OS 18.10 (Based on Ubuntu 18.10,
4.18.0-10-generic)

Still haven't tried with Audacity, but gnome-sound-recorded and Telegram
Desktop have been fixed in my case.

All I did this time was setting

default-sample-rate = 48000

on /etc/pulse/daemon.conf and restarting (Probably restarting pulseaudio
is enough).

before this, trying to send an audio recording through Telegram would
end in an "muted" audio. Now it's working perfectly.

You can try with arecord

arecord -f cd -d 10 test.wav -> For recording
aplay test.wav -> For playing (Probably gonna end up in noise)

arecord -f cd -d 10 -r 48000 test-mic.wav -> recording with the 48000
sample rate should provide good results

PD: Remember to increase a bit the mic volume from the sound settings

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

Title:
  [Realtek ALC1220 ASUS PRIME X370] Recording is very slow and plays 10x
  faster

Status in sound-2.6 (alsa-kernel):
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Recording applications (audacity, arecord, gnome-sound-recorder)
  record extremely slowly (at what seems to be 0,1x speed), which means
  that at playback the sound is played at a very high pitch and much
  faster than the original.

  To help you understand the issue, I've attached an archive containing two 
files recorded at the same time, one with arecord -f cd and the other with a 
stand-alone Olympus recorder.
  A video of Audacity's behavior when trying to record is also available: 
https://youtu.be/Fe20eQNvZVA
  Look at the seconds hand of the xclock and how much it is moving before 
Audacity is done recording one second of audio.

  Things I've already tried:
  *  Purging and reinstalling Audacity
  *  Purging and reinstalling Pulseaudio following the guide on the Ubuntu Wiki
  *  Running audacity with this command: Exec=env PULSE_LATENCY_MSEC=30 
audacity as suggested on AskUbuntu
  *  Reinstalling Ubuntu on a new hard disk
  *  Running audacity on a live CD (in Ubuntu version 16.04.3, 17.10.1, 18.04 
daily and Xubuntu 17.10.1, 18.04)

  The machine is a Ryzen 5 1600 with an ASUS X370 Prime motherboard.

  The problem can be reproduced as follows:

  * Boot a live DVD of Ubuntu/Xubuntu 16.04.3, 17.10.1, 18.04 (versions I've 
tested with)
  * Install audacity via the terminal
  * Start recording, microphone is connected to the rear microphone jack.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  jacopo 2417 F pulseaudio
   /dev/snd/controlC0:  jacopo 2417 F pulseaudio
  CurrentDesktop: Unity
  Date: Wed Apr 18 09:35:50 2018
  InstallationDate: Installed on 2018-03-03 (45 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Pink Mic, Rear
  Symptom_Type: None of the above
  Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Recording 
problem
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/06/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 3805
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME X370-PRO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr3805:bd03/06/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEX370-PRO:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/sound-2.6/+bug/1764965/+subscriptions

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

[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.325.1

---
ubuntu-meta (1.325.1) trusty; urgency=medium

  * Refreshed dependencies
  * Added ubuntu-advantage-tools to minimal LP: #1686183
  * Manually updated to include ubuntu-advantage-tools addition only.

 -- Dimitri John Ledkov   Thu, 25 Oct 2018 10:38:11
+0100

** Changed in: ubuntu-meta (Ubuntu Trusty)
   Status: Fix Committed => Fix Released

** Changed in: ubuntu-meta (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Ship ubuntu-advantage in ubuntu-minimal

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Precise:
  Fix Released
Status in ubuntu-meta source package in Precise:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  Fix Released
Status in ubuntu-meta source package in Trusty:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Yakkety:
  Won't Fix
Status in ubuntu-meta source package in Yakkety:
  Won't Fix
Status in ubuntu-advantage-tools source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  Won't Fix
Status in ubuntu-advantage-tools source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released

Bug description:
  The ubuntu-advantage-tools package is a bit odd as it was first landed
  in precise to support the ESM effort inside canonical. [0]  In order
  to bring this package up to date across other series in ubuntu, it has
  been recommended by the Ubuntu Foundations team to land into trusty
  next, then forward-port pocket-copy to all supported series until we
  get to the devel release.

  The version here:

  https://github.com/CanonicalLtd/ubuntu-advantage-
  script/releases/tag/v2

  ... has all on-disk bits correctly working, for all series, but no-ops
  on any release other than precise (ESM is only for "unsupported" LTS
  releases as it were).  This is a request to land ubuntu-advantage-
  tools into trusty, then pocket-copy it to supported series of ubuntu
  once that is finished.

  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help

   * Run sudo ubuntu-advantage enable  (without sudo it will warn
  you), but you need to be an ubuntu-advantage customer to get that
  token.  In the end, the script simply adds and removes an
  /etc/apt/sources.list.d entry.

   * Verify that the MOTD does not contain any mention of ubuntu-
  advantage esm or precise and its end of life

   * Verify that ubuntu-advantage enable-esm  installs needed 
dependencies:
- create the following file and its contents to have apt not install 
recommended packages by default:
  $ cat /etc/apt/apt.conf.d/no-recommends
  APT::Install-Recommends "false";
- remove ca-certificates and apt-transport-https:
  $ sudo apt remove ca-certificates apt-transport-https
- run sudo ubuntu-advantage enable-esm  and verify that the two 
removed packages are reinstalled

   * you can contact me (d...@canonical.com) if you would like a token
  for test purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

  [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04
  -esm-extended-security-maintenance/

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

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

[Touch-packages] [Bug 1686183] Re: Ship ubuntu-advantage in ubuntu-minimal

[Launchpad Bug Tracker]

This bug was fixed in the package ubuntu-meta - 1.361.2

---
ubuntu-meta (1.361.2) xenial; urgency=medium

  * Refreshed dependencies
  * Added ubuntu-advantage-tools to minimal LP: #1686183
  * Update config to use git, and all pockets.
  * Note above is added by monkey-patching germinate to not exclude
minimal packages, which do not appear in debootstrap output.

 -- Dimitri John Ledkov   Thu, 25 Oct 2018 10:13:59
+0100

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

Title:
  Ship ubuntu-advantage in ubuntu-minimal

Status in ubuntu-advantage-tools package in Ubuntu:
  Fix Released
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-advantage-tools source package in Precise:
  Fix Released
Status in ubuntu-meta source package in Precise:
  Fix Released
Status in ubuntu-advantage-tools source package in Trusty:
  Fix Released
Status in ubuntu-meta source package in Trusty:
  Fix Released
Status in ubuntu-advantage-tools source package in Xenial:
  Fix Released
Status in ubuntu-meta source package in Xenial:
  Fix Released
Status in ubuntu-advantage-tools source package in Yakkety:
  Won't Fix
Status in ubuntu-meta source package in Yakkety:
  Won't Fix
Status in ubuntu-advantage-tools source package in Zesty:
  Fix Released
Status in ubuntu-meta source package in Zesty:
  Won't Fix
Status in ubuntu-advantage-tools source package in Artful:
  Fix Released
Status in ubuntu-meta source package in Artful:
  Fix Released

Bug description:
  The ubuntu-advantage-tools package is a bit odd as it was first landed
  in precise to support the ESM effort inside canonical. [0]  In order
  to bring this package up to date across other series in ubuntu, it has
  been recommended by the Ubuntu Foundations team to land into trusty
  next, then forward-port pocket-copy to all supported series until we
  get to the devel release.

  The version here:

  https://github.com/CanonicalLtd/ubuntu-advantage-
  script/releases/tag/v2

  ... has all on-disk bits correctly working, for all series, but no-ops
  on any release other than precise (ESM is only for "unsupported" LTS
  releases as it were).  This is a request to land ubuntu-advantage-
  tools into trusty, then pocket-copy it to supported series of ubuntu
  once that is finished.

  [Impact]

   * Allow ubuntu-advantage users to access the extended security
  maintenance script with a simple command line tool.  This script needs
  to hit precise machines and be easy for ubuntu-advantage customers to
  enable, thus basefiles was chosen as a home.

  [Test Case]

   * Run ubuntu-advantage, it should print out help

   * Run sudo ubuntu-advantage enable  (without sudo it will warn
  you), but you need to be an ubuntu-advantage customer to get that
  token.  In the end, the script simply adds and removes an
  /etc/apt/sources.list.d entry.

   * Verify that the MOTD does not contain any mention of ubuntu-
  advantage esm or precise and its end of life

   * Verify that ubuntu-advantage enable-esm  installs needed 
dependencies:
- create the following file and its contents to have apt not install 
recommended packages by default:
  $ cat /etc/apt/apt.conf.d/no-recommends
  APT::Install-Recommends "false";
- remove ca-certificates and apt-transport-https:
  $ sudo apt remove ca-certificates apt-transport-https
- run sudo ubuntu-advantage enable-esm  and verify that the two 
removed packages are reinstalled

   * you can contact me (d...@canonical.com) if you would like a token
  for test purposes.

  [Regression Potential]

   * Low, this is a new script, not included in any automated startup
  paths.

  [Other Info]

   * http://blog.dustinkirkland.com/2017/03/ubuntu-1204-esm.html

  [0] https://insights.ubuntu.com/2017/03/14/introducing-ubuntu-12-04
  -esm-extended-security-maintenance/

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

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

[Touch-packages] [Bug 1716654] Re: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, dropouts or crackling sound

[Luca Mastromatteo]

I'm getting the same on ALC892

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

Title:
  [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns,
  dropouts or crackling sound

Status in alsa-driver package in Ubuntu:
  Won't Fix

Bug description:
  Have checked under windows (same computer in dual-boot & same
  headset), and the sound is crystal clear, so 99% sure this is not a
  hardware problem.

  Motherboard is ASUS Crosshair Hero 6.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.12.0-13.14-generic 4.12.10
  Uname: Linux 4.12.0-13-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC3:  paul   2587 F pulseaudio
   /dev/snd/controlC0:  paul   2587 F pulseaudio
   /dev/snd/controlC1:  paul   2587 F pulseaudio
   /dev/snd/controlC2:  paul   2587 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Sep 12 11:48:05 2017
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic 
successful
  Symptom_Card: HD-Audio Generic - HD-Audio Generic
  Symptom_Jack: Pink Mic, Rear
  Symptom_PulseAudioRecordingTest: PulseAudio recording test through 
plughw:Generic successful
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [System Product Name, Realtek ALC1220, Pink Mic, Rear] Underruns, 
dropouts or crackling sound
  UpgradeStatus: Upgraded to artful on 2017-08-31 (11 days ago)
  dmi.bios.date: 07/28/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1501
  dmi.board.asset.tag: Default string
  dmi.board.name: CROSSHAIR VI HERO
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1501:bd07/28/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCROSSHAIRVIHERO:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2017-09-12T11:37:48.670242

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

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

[Touch-packages] [Bug 1799007] Re: [System76 Oryx Pro] no sound after 18.10 upgrade

[Tessa]

ahhh well like I said that crash dump was from after uninstalling the
jack packages. things are still broken without jack installed. no sound
in any app.

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

Title:
  [System76 Oryx Pro] no sound after 18.10 upgrade

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading to 18.10, the sound in my System76 Oryx Pro no longer
  works, it no longer shows any of the audio output devices, not even
  the builtin HDMI which usually always shows.

  Not sure what happened, but this is a major regression and needs to be fixed. 
Note that this isn't the same as the bug with Timidity taking exclusive 
soundcard access 
(https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1797714) as I don't 
have any timidity packages installed.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  tessa 11703 F pulseaudio
   /dev/snd/controlC0:  tessa 11703 F pulseaudio
   /dev/snd/pcmC0D0c:   tessa 11703 F...m pulseaudio
   /dev/snd/pcmC0D0p:   tessa 11703 F...m pulseaudio
  CurrentDesktop: pop:GNOME
  DistroRelease: Pop!_OS 18.10
  InstallationDate: Installed on 2018-03-05 (230 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset 
nvidia
  Package: pulseaudio 1:12.2-0ubuntu4 [origin: Ubuntu]
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Daemon 
not responding.
  Tags: third-party-packages cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UnreportableReason: This is not an official Pop!_OS package. Please remove 
any third party package and try again.
  UpgradeStatus: Upgraded to cosmic on 2018-10-18 (3 days ago)
  UserGroups: adm audio cdrom chrome-remote-desktop dip docker libvirt lpadmin 
plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.02dRSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76
  dmi.board.version: oryp3-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.02dRSA2:bd02/20/2017:svnSystem76:pnOryxPro:pvroryp3-ess:rvnSystem76:rnOryxPro:rvroryp3-ess:cvnSystem76:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.sku: Not Applicable
  dmi.product.version: oryp3-ess
  dmi.sys.vendor: System76

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

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

[Touch-packages] [Bug 1801148] [NEW] package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it befor

[Neha]

Public bug reported:

Unable to open skype

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83
Uname: Linux 4.4.0-94-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 gir1.2-unity-5.0: Configure
 upower: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Nov  1 13:11:35 2018
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-xenial-amd64-20160624-2
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-10-31 (1 days ago)
InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1
 apt  1.2.29
SourcePackage: libunity
Title: package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package third-party-packages xenial

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

Title:
  package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libunity package in Ubuntu:
  New

Bug description:
  Unable to open skype

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83
  Uname: Linux 4.4.0-94-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   gir1.2-unity-5.0: Configure
   upower: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Nov  1 13:11:35 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-10-31 (1 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.29
  SourcePackage: libunity
  Title: package gir1.2-unity-5.0:amd64 7.1.4+15.10.20151002-0ubuntu2 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

Verification-done on bionic with netplan.io 0.40.1~18.04.2:

Using the following config:

network:
version: 2
ethernets:
maas0:
addresses:
- 10.3.21.29/20
gateway4: 10.3.16.1
match:
macaddress: 52:54:00:4d:3e:84
mtu: 1500
set-name: maas0

The interface renaming is correctly done at boot time; then changing
set-name to 'maas1', bringing down the interface with 'ip link set dev
maas0 down', and running 'netplan apply'; the interface is correctly
renamed:


ubuntu@nice-baboon:~$ sudo vi /etc/netplan/50-cloud-init.yaml 
ubuntu@nice-baboon:~$ sudo netplan apply
ubuntu@nice-baboon:~$ ip addr
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: maas0:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
link/ether 52:54:00:4d:3e:84 brd ff:ff:ff:ff:ff:ff
inet 10.3.21.29/20 brd 10.3.31.255 scope global maas0
   valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe4d:3e84/64 scope link 
   valid_lft forever preferred_lft forever
ubuntu@nice-baboon:~$ 
ubuntu@nice-baboon:~$ sudo vi /etc/netplan/50-cloud-init.yaml 
ubuntu@nice-baboon:~$ ip link set dev maas0 down
RTNETLINK answers: Operation not permitted
ubuntu@nice-baboon:~$ sudo !!
sudo ip link set dev maas0 down
ubuntu@nice-baboon:~$ ip addr
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: maas0:  mtu 1500 qdisc fq_codel state DOWN group 
default qlen 1000
link/ether 52:54:00:4d:3e:84 brd ff:ff:ff:ff:ff:ff
inet 10.3.21.29/20 brd 10.3.31.255 scope global maas0
   valid_lft forever preferred_lft forever
ubuntu@nice-baboon:~$ sudo netplan apply
ubuntu@nice-baboon:~$ ip addr
1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
inet 127.0.0.1/8 scope host lo
   valid_lft forever preferred_lft forever
inet6 ::1/128 scope host 
   valid_lft forever preferred_lft forever
2: maas1:  mtu 1500 qdisc fq_codel state UP 
group default qlen 1000
link/ether 52:54:00:4d:3e:84 brd ff:ff:ff:ff:ff:ff
inet 10.3.21.29/20 brd 10.3.31.255 scope global maas1
   valid_lft forever preferred_lft forever
inet6 fe80::5054:ff:fe4d:3e84/64 scope link 
   valid_lft forever preferred_lft forever


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

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

** Tags removed: verification-needed-xenial

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

Title:
  systemd-networkd not renaming devices on boot

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

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  

[Touch-packages] [Bug 1794169] Re: AWS ubuntu became unreachable after ssh login

[Marc Deslauriers]

** Information type changed from Public 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/1794169

Title:
  AWS ubuntu became unreachable after ssh login

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

Bug description:
  I've reached strange situation with Ubuntu 18.04 LTS with latest
  kernel on AWS m5.xlarge instance.

  System became unreachable after series of successful ssh logins.
  systemd -user became zombie and block main systemd daemon (PID 1).

  I've created bug https://github.com/systemd/systemd/issues/10123 but
  it was closed with "there's a problem with your kernel".
  https://github.com/systemd/systemd/issues/10123#issuecomment-423984751

  Symptoms are very similar to
  https://github.com/systemd/systemd/issues/8598

  apetren+ 26679  0.0  0.0  0 0 ?Z02:56   0:00  \_ 
[(sd-pam)] 
  apetren+ 26855  0.0  0.0  76636  7816 ?Ds   02:57   0:00 
/lib/systemd/systemd --user
  apetren+ 26856  0.0  0.0  0 0 ?Z02:57   0:00  \_ 
[(sd-pam)] 
  apetren+ 26954  0.0  0.0  0 0 ?Zs   02:57   0:00  \_ [kill] 

  apetren+ 27053  0.0  0.0  76636  7496 ?Ss   02:58   0:00 
/lib/systemd/systemd --user
  apetren+ 27054  0.0  0.0 193972  2768 ?S02:58   0:00  \_ (sd-pam)

  This situation is repeatable on 7 instances 1-2 times per week.

  how to repeat: 1. Install ubuntu 18.04 LTS from official ubuntu image
  2. update kernel and packages to latest version 3. from another
  instance run

  while `true` ;do ssh ubu...@your.instance.ip "hostname; ps -ef|grep
  defunc |grep -v grep" ; done

  By this command in couple of days I have 2->4->6->8... zombies and in
  a hour system is frozen...

  sudo reboot is not working, because systemd with PID 1 is unreachable.
  kill -9 1 -- not working as well.

  # uname -r:
  Linux mainframe04 4.15.0-1021-aws #21-Ubuntu SMP Tue Aug 28 10:23:07 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  # cat /etc/lsb-release
  DISTRIB_ID=Ubuntu
  DISTRIB_RELEASE=18.04
  DISTRIB_CODENAME=bionic
  DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

  # systemd --version
  systemd 237
  +PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
+GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN2 +IDN -PCRE2 
default-hierarchy=hybrid

  
  AWS instance m5.xlarge

  Please let me know if you need any information.
  --- 
  ProblemType: Bug
  AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 
2: ls: cannot access '/dev/snd/': No such file or directory
  AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 
'arecord'
  CRDA: N/A
  DistroRelease: Ubuntu 18.04
  Ec2AMI: ami-91caece9
  Ec2AMIManifest: (unknown)
  Ec2AvailabilityZone: us-west-2b
  Ec2InstanceType: m5.xlarge
  Ec2Kernel: unavailable
  Ec2Ramdisk: unavailable
  IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
  Lsusb: Error: command ['lsusb'] failed with exit code 1:
  MachineType: Amazon EC2 m5.xlarge
  Package: systemd 237-3ubuntu10.3
  PackageArchitecture: amd64
  PciMultimedia:
   
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1021-aws 
root=UUID=a4278387-5a07-46eb-a726-ae1e22673af4 ro console=tty1 console=ttyS0 
nvme.io_timeout=4294967295
  ProcVersionSignature: Ubuntu 4.15.0-1021.21-aws 4.15.18
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-1021-aws N/A
   linux-backports-modules-4.15.0-1021-aws  N/A
   linux-firmware   N/A
  RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
  Tags:  bionic ec2-images
  Uname: Linux 4.15.0-1021-aws x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: docker
  WifiSyslog:
   
  _MarkForUpload: True
  dmi.bios.date: 10/16/2017
  dmi.bios.vendor: Amazon EC2
  dmi.bios.version: 1.0
  dmi.board.asset.tag: i-02cfe7fcd8a997085
  dmi.board.vendor: Amazon EC2
  dmi.chassis.asset.tag: Amazon EC2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Amazon EC2
  dmi.modalias: 
dmi:bvnAmazonEC2:bvr1.0:bd10/16/2017:svnAmazonEC2:pnm5.xlarge:pvr:rvnAmazonEC2:rn:rvr:cvnAmazonEC2:ct1:cvr:
  dmi.product.name: m5.xlarge
  dmi.sys.vendor: Amazon EC2

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

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

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

Verification-done for cosmic using netplan.io 0.40.2.1:

I have verified that renames happen correctly with the config provided
in test cases and the config I have shown for the testing on bionic.

In all cases, set-name is applied as the new name for the interface, as
expected. On reboot, this is sufficient for the interface to be renamed.
After boot, the interface must first be brought down before it can be
renamed (this is expected behavior, renaming does not work on a busy
interface).

** Tags added: verification-done-cosmic

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

Title:
  systemd-networkd not renaming devices on boot

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

Bug description:
  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.

  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
  - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.

  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.

  === systemd issue ===

  Renaming devices doesn't seem to work.

  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:

  [Match]
  MACAddress=52:54:00:c1:c9:bb

  [Link]
  Name=myiface3

  I expect this to cause the device with that MAC address to be renamed
  to  myiface3. However, when I reboot, I instead see:

  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff

  The device is not renamed.

  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.

  The renaming does work if I boot with net.ifnames=0, and oddly, it
  also works if I unbind the device and rebind it as netplan apply does.
  No setting of NamePolicy seems to help.

  === Original Bug ==

  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.

  Say I take this 50-cloud-init.yaml file:

  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3

  Say I change set-name to 'myiface3' and reboot. I expect that the
  device will be called myiface3 and brought up fine with dhcp. However,
  instead I see:

  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff

  The name has not been changed, and the device has not been brought up.

  If I run netplan apply however, I see the following:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  

[Touch-packages] [Bug 1800555] Re: Computer slow. Error reports appear.

[Cristian Aravena Romero]

** Package changed: xorg (Ubuntu) => xorg-server (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/1800555

Title:
  Computer slow. Error reports appear.

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Computer slow. Error reports appear. Says system is running on low
  graphics sometimes. Makes me log in most of the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
  Uname: Linux 4.4.0-138-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   [  OK  ] Stopped WPA supplicant.
   [  OK  ] Started Show Plymouth Boot Screen.
Starting Hold until boot process finishes up...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 29 17:37:27 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1]
  InstallationDate: Installed on 2016-09-11 (778 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard p6710f
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic 
root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.07
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 4CE0480TV4
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6710f
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 29 17:32:25 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 8
   inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1800333] Re: Ubuntu dock not working properly

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

** Package changed: systemd (Ubuntu) => gnome-shell-extension-ubuntu-
dock (Ubuntu)

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

Title:
  Ubuntu dock not working properly

Status in gnome-shell-extension-ubuntu-dock package in Ubuntu:
  New

Bug description:
  Ubuntu 18.10
  Linux mbpr13b 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux
  Upgrade from Ubuntu 18.04, all updates applied

  Ubuntu dock has several issues (some reported elsewhere)

  a) dock does not allow to relocate on screen (does not honour gsetting 
dock-position)
  b) dock does not react to hotkeys (even though are set in gsettings)
  c) dock does not hide on lock screen 
(https://www.queryxchange.com/q/3_1085426/desktop-is-visible-is-visible-after-suspend/)
  d) dock does allow application launch, termination and some commands when 
machine in locked
  e) dock appears after resume from RAM
  f) dash button does not react on first mouse click when applications are open
  g) dock changes size if applications are open and a dot indicates the fact

  here are the Gnome settings:

  gsettings list-recursively org.gnome.shell.extensions.dash-to-dock
  org.gnome.shell.extensions.dash-to-dock click-action 'previews'
  org.gnome.shell.extensions.dash-to-dock preferred-monitor -1
  org.gnome.shell.extensions.dash-to-dock force-straight-corner false
  org.gnome.shell.extensions.dash-to-dock show-show-apps-button true
  org.gnome.shell.extensions.dash-to-dock show-windows-preview true
  org.gnome.shell.extensions.dash-to-dock animation-time 0.20001
  org.gnome.shell.extensions.dash-to-dock scroll-action 'switch-workspace'
  org.gnome.shell.extensions.dash-to-dock height-fraction 0.90002
  org.gnome.shell.extensions.dash-to-dock activate-single-window true
  org.gnome.shell.extensions.dash-to-dock running-indicator-dominant-color false
  org.gnome.shell.extensions.dash-to-dock custom-theme-customize-running-dots 
true
  org.gnome.shell.extensions.dash-to-dock minimize-shift true
  org.gnome.shell.extensions.dash-to-dock show-apps-at-top true
  org.gnome.shell.extensions.dash-to-dock pressure-threshold 100.0
  org.gnome.shell.extensions.dash-to-dock show-delay 0.25
  org.gnome.shell.extensions.dash-to-dock icon-size-fixed true
  org.gnome.shell.extensions.dash-to-dock intellihide-mode 'ALL_WINDOWS'
  org.gnome.shell.extensions.dash-to-dock customize-alphas false
  org.gnome.shell.extensions.dash-to-dock apply-custom-theme false
  org.gnome.shell.extensions.dash-to-dock hot-keys true
  org.gnome.shell.extensions.dash-to-dock extend-height true
  org.gnome.shell.extensions.dash-to-dock background-color '#ff'
  org.gnome.shell.extensions.dash-to-dock shortcut-timeout 2.0
  org.gnome.shell.extensions.dash-to-dock transparency-mode 'ADAPTIVE'
  org.gnome.shell.extensions.dash-to-dock multi-monitor false
  org.gnome.shell.extensions.dash-to-dock shortcut-text 'q'
  org.gnome.shell.extensions.dash-to-dock isolate-workspaces false
  org.gnome.shell.extensions.dash-to-dock max-alpha 0.80004
  org.gnome.shell.extensions.dash-to-dock app-shift-hotkey-10 
['0']
  org.gnome.shell.extensions.dash-to-dock hide-delay 0.20001
  org.gnome.shell.extensions.dash-to-dock show-favorites true
  org.gnome.shell.extensions.dash-to-dock 
custom-theme-running-dots-border-color '#e95420'
  org.gnome.shell.extensions.dash-to-dock 
custom-theme-running-dots-border-width 0
  org.gnome.shell.extensions.dash-to-dock app-hotkey-10 ['0']
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-1 ['1']
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-2 ['2']
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-3 ['3']
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-4 ['4']
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-5 ['5']
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-6 ['6']
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-8 ['8']
  org.gnome.shell.extensions.dash-to-dock app-ctrl-hotkey-9 ['9']
  org.gnome.shell.extensions.dash-to-dock app-hotkey-1 ['1']
  org.gnome.shell.extensions.dash-to-dock app-hotkey-2 ['2']
  org.gnome.shell.extensions.dash-to-dock isolate-monitors false
  org.gnome.shell.extensions.dash-to-dock app-hotkey-4 ['4']
  org.gnome.shell.extensions.dash-to-dock app-hotkey-5 ['5']
  

[Touch-packages] [Bug 1770082] Re: systemd-networkd not renaming devices on boot

[Mathieu Trudel-Lapierre]

** Description changed:

  [Impact]
  Systems relying on renaming network interfaces at boot and when 'netplan 
apply' is run.
  
  [Test case]
  - Write a new netplan YAML (adjusting for current system as necessary):
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: myif0
- 
+ - Bring down interface : 'ip link set dev ens3 down'
  - Run 'netplan apply'
  - Verify that the device is correctly renamed to 'myif0'.
  - Reboot.
  - Make sure the device is correctly renamed to 'myif0'.
  
  [Regression potential]
  Changes in rename logic to add udev rules may otherwise impact applying 
different settings to the network interfaces. Changes in settings on network 
interfaces, missing parameters (especially on bonds, bridges) should be 
investigated as potential regressions. Other failures to apply network settings 
might also happen if there's a race between applying renames via the udev 
rules, and using the new names to apply configuration changes to the interfaces.
  
  === systemd issue ===
  
  Renaming devices doesn't seem to work.
  
  If I disable all other network configuration and create
  /etc/systemd/network/10-network.link with:
  
  [Match]
  MACAddress=52:54:00:c1:c9:bb
  
  [Link]
  Name=myiface3
  
  I expect this to cause the device with that MAC address to be renamed to
  myiface3. However, when I reboot, I instead see:
  
  $ ip l
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN mode 
DEFAULT group default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  2: ens3:  mtu 1500 qdisc noop state DOWN mode DEFAULT 
group default qlen 1000
  link/ether 52:54:00:c1:c9:bb brd ff:ff:ff:ff:ff:ff
  
  The device is not renamed.
  
  This link file is pretty much identical to Example 2 in
  https://www.freedesktop.org/software/systemd/man/systemd.link.html.
  
  The renaming does work if I boot with net.ifnames=0, and oddly, it also
  works if I unbind the device and rebind it as netplan apply does. No
  setting of NamePolicy seems to help.
  
  === Original Bug ==
  
  'set-name:' doesn't change the name of a network interface on boot, it
  only works when you do netplan apply.
  
  Say I take this 50-cloud-init.yaml file:
  
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  ens3:
  dhcp4: true
  match:
  macaddress: 52:54:00:de:bd:f6
  set-name: ens3
  
  Say I change set-name to 'myiface3' and reboot. I expect that the device
  will be called myiface3 and brought up fine with dhcp. However, instead
  I see:
  
  $ ip a
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  2: ens3:  mtu 1500 qdisc noop state DOWN group default 
qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  
  The name has not been changed, and the device has not been brought up.
  
  If I run netplan apply however, I see the following:
  
  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever
  
  So names are successfully changed with netplan apply.
  
  This seems to be some udev-related timing or priority issue that I'm
  still trying to hunt down.
  
  This breaks some forms of migration in certain cloud environments.

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

Title:
  systemd-networkd not renaming devices on boot

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

[Touch-packages] [Bug 1800219] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.13 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in openssl package in Ubuntu:
  New

Bug description:
  there is a status 1 error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.13
  ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83
  Uname: Linux 4.4.0-94-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Oct 27 00:59:32 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature:
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.13) ...
   debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by 
another process: Resource temporarily unavailable
   dpkg: error processing package libssl1.0.0:amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-08-07 (80 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.13 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1800219] Re: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.13 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Apport retracing service]

** Tags removed: need-duplicate-check

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

Title:
  package libssl1.0.0:amd64 1.0.2g-1ubuntu4.13 failed to
  install/upgrade: subprocess installed post-installation script
  returned error exit status 1

Status in openssl package in Ubuntu:
  New

Bug description:
  there is a status 1 error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libssl1.0.0:amd64 1.0.2g-1ubuntu4.13
  ProcVersionSignature: Ubuntu 4.4.0-94.117-generic 4.4.83
  Uname: Linux 4.4.0-94-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Sat Oct 27 00:59:32 2018
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-xenial-amd64-20160624-2
  DuplicateSignature:
   Setting up libssl1.0.0:amd64 (1.0.2g-1ubuntu4.13) ...
   debconf: DbDriver "config": /var/cache/debconf/config.dat is locked by 
another process: Resource temporarily unavailable
   dpkg: error processing package libssl1.0.0:amd64 (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-08-07 (80 days ago)
  InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
20160624-10:47
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: openssl
  Title: package libssl1.0.0:amd64 1.0.2g-1ubuntu4.13 failed to 
install/upgrade: subprocess installed post-installation script returned error 
exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1801128] [NEW] OpenSSH 7.7 -w tunnel bug

[Adam Jacobs]

Public bug reported:

Just upgraded to cosmic, which picks up OpenSSH 7.7.

OpenSSH 7.7 has known bug
https://bugzilla.mindrot.org/show_bug.cgi?id=2855 which is fixed in
OpenSSH 7.8.  It's a regression that completely breaks -w tunneling.

The OpenSSH bug contains a trivial two-line patch to fix the bug.  I
downloaded the Ubuntu openssh package source, applied the patch and
rebuilt, and can confirm that is does fix the problem.

Any chance we could get this patch backported to Cosmic?

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: openssh-client 1:7.7p1-4
ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
Uname: Linux 4.18.0-10-generic x86_64
ApportVersion: 2.20.10-0ubuntu13
Architecture: amd64
Date: Thu Nov  1 09:36:16 2018
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions:
 ssh-askpass   N/A
 libpam-sshN/A
 keychain  N/A
 ssh-askpass-gnome N/A
SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
SourcePackage: openssh
UpgradeStatus: Upgraded to cosmic on 2018-11-01 (0 days ago)

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


** Tags: amd64 apport-bug cosmic

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

Title:
  OpenSSH 7.7 -w tunnel bug

Status in openssh package in Ubuntu:
  New

Bug description:
  Just upgraded to cosmic, which picks up OpenSSH 7.7.

  OpenSSH 7.7 has known bug
  https://bugzilla.mindrot.org/show_bug.cgi?id=2855 which is fixed in
  OpenSSH 7.8.  It's a regression that completely breaks -w tunneling.

  The OpenSSH bug contains a trivial two-line patch to fix the bug.  I
  downloaded the Ubuntu openssh package source, applied the patch and
  rebuilt, and can confirm that is does fix the problem.

  Any chance we could get this patch backported to Cosmic?

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: openssh-client 1:7.7p1-4
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  Uname: Linux 4.18.0-10-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  Date: Thu Nov  1 09:36:16 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.7p1 Ubuntu-4, OpenSSL 1.0.2n  7 Dec 2017
  SourcePackage: openssh
  UpgradeStatus: Upgraded to cosmic on 2018-11-01 (0 days ago)

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

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

[Touch-packages] [Bug 1801028] Re: Virus bug on ubuntu 16.4 32bits

[Marc Deslauriers]

Thanks for your comments. This does not appear to be a bug report and we
are closing it. We appreciate the difficulties you are facing, but it
would make more sense to raise your question in the support tracker.
Please visit https://answers.launchpad.net/ubuntu/+addquestion

** Information type changed from Private Security to Public

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

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

Title:
  Virus bug on ubuntu 16.4 32bits

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Hello.Sorry but I'm French I'll do my best to explain.

  The Bug I'm reporting happened from a mail that I opened, I mean a kind of 
virus.
  It blow up my picture back screen and fix sometime the image in a way that I 
can't 
  move it out.
  I'm trying actually to fight against it but I don't know enough to win.So I 
need
  help anyway.
   thank you. Oliver

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
  Uname: Linux 4.4.0-138-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Nov  1 09:31:25 2018
  DistUpgraded: 2017-10-22 20:28:39,732 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] G94 [GeForce 9600 GT] 
[1462:1270]
  InstallationDate: Installed on 2016-04-18 (926 days ago)
  InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  MachineType: Dell Inc. Vostro 410
  ProcEnviron:
   LANGUAGE=fr_FR
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic 
root=UUID=011baf0e-1274-4ca0-9f7e-2929ae27e3fc ro plymouth:debug drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-10-22 (374 days ago)
  dmi.bios.date: 06/20/2008
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.3
  dmi.board.name: 0J584C
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.3:bd06/20/2008:svnDellInc.:pnVostro410:pvr:rvnDellInc.:rn0J584C:rvrA00:cvnDellInc.:ct3:cvrOEM:
  dmi.product.name: Vostro 410
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Thu Nov  1 09:26:52 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputUSB Optical MouseMOUSE, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1800555] Re: Computer slow. Error reports appear.

[Marc Deslauriers]

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

** Information type changed from Private Security to Public

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

Title:
  Computer slow. Error reports appear.

Status in xorg package in Ubuntu:
  New

Bug description:
  Computer slow. Error reports appear. Says system is running on low
  graphics sometimes. Makes me log in most of the time.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-138.164-generic 4.4.155
  Uname: Linux 4.4.0-138-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   [  OK  ] Stopped WPA supplicant.
   [  OK  ] Started Show Plymouth Boot Screen.
Starting Hold until boot process finishes up...
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Oct 29 17:37:27 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1]
  InstallationDate: Installed on 2016-09-11 (778 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard p6710f
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-138-generic 
root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.07
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 4CE0480TV4
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6710f
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Oct 29 17:32:25 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 8
   inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.errors:
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
   /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

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

-- 
Mailing list: https://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 856776] Re: Cannot declare itself as another username with CUPS server

[Jonathan Allard]

*laughs*

Indeed, I do not need this anymore. I've had time to graduate university
(where CUPS was useful), move homes a bunch of times, change OSes, among
other things. Have a good triage!

On Thu, Nov 1, 2018 at 11:06 AM gf <856...@bugs.launchpad.net> wrote:

> Hello Jonathan,
> Thank you for submitting this feature/enhancement request for the cups
> package.  You made this request quite some time ago and Ubuntu has been
> updated since then.
>
> Do you think this feature/enhancement is still needed or can we close
> this bug report?
>
> Thank you again for helping make Ubuntu better.
> G
> [Ubuntu Bug Squad volunteer triager]
>
> ** Changed in: cups (Ubuntu)
>Status: Confirmed => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/856776
>
> Title:
>   Cannot declare itself as another username with CUPS server
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/common-print-dialog-gtk/+bug/856776/+subscriptions
>

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

Title:
  Cannot declare itself as another username with CUPS server

Status in Common Print Dialog:
  New
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Originally posted on http://askubuntu.com/questions/61095/use-
  different-username-on-cups-remote-printing :

  > I'm using CUPS to print on an enterprise network. The job gets submitted 
fine, but I need to submit it as another username. Now  I'm `jon` but I need to 
send it as say `jonallard`.
  > 
  > On the command line, one could print as such
  > 
  > lp -U jonallard -d printer1 file.ext
  > 
  > How do I customize the *username* part when using the GUI printing dialogs 
and the Printing system settings?
  > 
  > It is possible that it isn't, in fact, possible to add this username to the 
Ubuntu print config. If so, where should I ask for an improvement?"

  Martin Owens -doctormo-@AskUbuntu suggested I add the username in the
  IPP URI directly. The printer address dialog won't let me do that.

  Is this a bug or is there some hidden place to put this username or
  should it be improved?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: system-config-printer-gnome 1.3.1+20110222-0ubuntu16.3
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  CupsErrorLog:
   
  Date: Thu Sep 22 16:17:38 2011
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/python2.7
  Lpstat: device for uprint-mono: 
ipp://cups.ncs.mcgill.ca:631/printers/mcgill_mono
  MachineType: LENOVO 427637U
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: uprint-mono: Generic PCL Laser Printer
  ProcEnviron:
   LANGUAGE=en_CA:en
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=264a98b8-d582-4814-bb46-81adf856e638 ro splash vga=795 quiet splash 
vt.handoff=7
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8BET44WW (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 427637U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8BET44WW(1.24):bd05/13/2011:svnLENOVO:pn427637U:pvrThinkPadW520:rvnLENOVO:rn427637U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 427637U
  dmi.product.version: ThinkPad W520
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/common-print-dialog-gtk/+bug/856776/+subscriptions

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

[Touch-packages] [Bug 1800877] Re: iproute2/xenial: Add support for the VF Trust setting (fix IPv6 multicast under SR-IOV on Mellanox adapters)

[Mauricio Faria de Oliveira]

Hi Eric,

Thanks for reviewing.
This is the debdiff v2, addressing the points you brought up (numbered patches, 
bug-ubuntu dep3 tag).

cheers,
Mauricio

** Patch removed: "iproute2_xenial_vf-trust.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+attachment/5207579/+files/iproute2_xenial_vf-trust.debdiff

** Patch added: "iproute2_xenial_vf-trust_v2.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1800877/+attachment/5207902/+files/iproute2_xenial_vf-trust_v2.debdiff

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

Title:
  iproute2/xenial: Add support for the VF Trust setting (fix IPv6
  multicast under SR-IOV on Mellanox adapters)

Status in iproute2 package in Ubuntu:
  Fix Released
Status in iproute2 source package in Xenial:
  In Progress

Bug description:
  [Impact]

   * An VM's VF cannot receive IPv6 multicast traffic
     from other VMs' VFs in the same Mellanox adapter
     _if_ its VF trust setting is not enabled, and on
     Xenial currently iproute2 _cannot_ enable it.

   * This breaks IPv6 NDP (Neighbor Discovery Protocol)
     in that scenario.

   * This upload adds three iproute2 upstream commits
     to enable/disable the VF setting, which resolves
     that problem/limitation.

  [Test Case]

   * Check 'ip link help' for the 'trust' option:

     Before:

   # ip link help 2>&1 | grep trust
   

     After:

   # ip link help 2>&1 | grep trust
   [ trust { on | off} ] ]

   * Check 'ip link show dev PF' for 'trust on|off' field in VFs.

     Before: (trust field _is not_ present)

   # ip link show dev ens1f0
   ...
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto

     After: (trust field _is_ present)

   # ip link show dev ens1f0
   ...
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

   * Set the VF trust on/off and check it:

   Set VF 0 trust on:

   # ip link set ens1f0 vf 0 trust on
   # ip link show dev ens1f0 | grep trust
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust on
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

   Set VF 0 trust off:

   # ip link set ens1f0 vf 0 trust off
   # ip link show dev ens1f0 | grep trust
   vf 0 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off
   vf 1 MAC 00:00:00:00:00:00, spoof checking on, link-state auto, trust off

  [Regression Potential]

   * Regression potential is low because the commits just add the
     netlink attribute for the userspace-kernel interface and the
     ways to set/clear it, and show the current value to the user.

   * Regressions could happen _if_ the user turns the setting on
     (it's disabled by default) and there's a problem/bug likely
     in _other_ component that depends on that setting (which is
     something to fix on such component).

  [Other Info]

   * The users that reported this problem have verified
     the test package with these changes, and confirmed
     that it now works correctly for IPv6 NDP/multicast.

   * Upstream commits:
   
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=dddf1b44126e
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=fe9322781e63
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=b6d77d9ee312

   * Only affect Xenial release :

   # rmadison iproute2
   iproute2 | 4.3.0-1ubuntu3.16.04.3 | xenial-updates
   iproute2 | 4.15.0-2ubuntu1| bionic 
   iproute2 | 4.18.0-1ubuntu2| cosmic
   iproute2 | 4.18.0-1ubuntu2| disco  

   # iproute2 upstream vcs

   $ git describe --contains dddf1b44126e
   v4.4.0~67

   $ git describe --contains b6d77d9ee312
   v4.5.0~47

   $ git describe --contains fe9322781e63
   v4.6.0~32

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

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

[Touch-packages] [Bug 814908] Re: lpstat should return failure when cupsd is not running

[gf]

Hello Benjamin,
Thank you for submitting this feature/enhancement request for the cups package. 
 You made this request quite some time ago and Ubuntu has been updated since 
then. 

Do you think this feature/enhancement is still needed or can we close
this bug report?

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

** Changed in: cups (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  lpstat should return failure when cupsd is not running

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  We find ourselves needing to programmatically check whether cupsd is running 
(so that we can use lpadmin to add our site's printers for our users, but there 
are many other possible reasons one might want to do this).  'lpstat -r' seems 
the obvious way to do so, but the command always returns zero (success).
  Thus, we are forced to parse the text output of 'lpstat -r', which is quite 
fragile to that text changing in a future release.  'lpstat -r' should return 
nonzero when cupsd is not running, allowing for a robust determination of 
whether cupsd is running (and thus other commands will fail).

  This bug was observed in natty, with cups 1.4.6-5ubuntu1.3

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

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

[Touch-packages] [Bug 856776] Re: Cannot declare itself as another username with CUPS server

[gf]

Hello Jonathan,
Thank you for submitting this feature/enhancement request for the cups package. 
 You made this request quite some time ago and Ubuntu has been updated since 
then. 

Do you think this feature/enhancement is still needed or can we close
this bug report?

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

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

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

Title:
  Cannot declare itself as another username with CUPS server

Status in Common Print Dialog:
  New
Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Originally posted on http://askubuntu.com/questions/61095/use-
  different-username-on-cups-remote-printing :

  > I'm using CUPS to print on an enterprise network. The job gets submitted 
fine, but I need to submit it as another username. Now  I'm `jon` but I need to 
send it as say `jonallard`.
  > 
  > On the command line, one could print as such
  > 
  > lp -U jonallard -d printer1 file.ext
  > 
  > How do I customize the *username* part when using the GUI printing dialogs 
and the Printing system settings?
  > 
  > It is possible that it isn't, in fact, possible to add this username to the 
Ubuntu print config. If so, where should I ask for an improvement?"

  Martin Owens -doctormo-@AskUbuntu suggested I add the username in the
  IPP URI directly. The printer address dialog won't let me do that.

  Is this a bug or is there some hidden place to put this username or
  should it be improved?

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: system-config-printer-gnome 1.3.1+20110222-0ubuntu16.3
  ProcVersionSignature: Ubuntu 2.6.38-11.48-generic 2.6.38.8
  Uname: Linux 2.6.38-11-generic x86_64
  NonfreeKernelModules: nvidia
  Architecture: amd64
  CupsErrorLog:
   
  Date: Thu Sep 22 16:17:38 2011
  ExecutablePath: /usr/share/system-config-printer/system-config-printer.py
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
  InterpreterPath: /usr/bin/python2.7
  Lpstat: device for uprint-mono: 
ipp://cups.ncs.mcgill.ca:631/printers/mcgill_mono
  MachineType: LENOVO 427637U
  PackageArchitecture: all
  Papersize: letter
  PpdFiles: uprint-mono: Generic PCL Laser Printer
  ProcEnviron:
   LANGUAGE=en_CA:en
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.38-11-generic 
root=UUID=264a98b8-d582-4814-bb46-81adf856e638 ro splash vga=795 quiet splash 
vt.handoff=7
  SourcePackage: system-config-printer
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 8BET44WW (1.24 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 427637U
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr8BET44WW(1.24):bd05/13/2011:svnLENOVO:pn427637U:pvrThinkPadW520:rvnLENOVO:rn427637U:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 427637U
  dmi.product.version: ThinkPad W520
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/common-print-dialog-gtk/+bug/856776/+subscriptions

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

[Touch-packages] [Bug 343801] Re: cupsd.conf defaults need to allow reprint of jobs

[gf]

Sorry, I meant: ".. with the *cups* package."


** Changed in: cups (Ubuntu)
   Status: Triaged => Incomplete

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

Title:
  cupsd.conf defaults need to allow reprint of jobs

Status in CUPS:
  New
Status in cups package in Ubuntu:
  Incomplete
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: cups

  if you see the screen shots in this thread
  http://ubuntuforums.org/showthread.php?t=820916 you will see what im
  talking about i think it would be much nicer if /etc/cups/cupsd.conf
  contained these 2 lines by default

  # preserve last 50 print jobs

  PreserveJobFiles Yes
  MaxJobs 50

  
  you can make max jobs higher but the "PreserveJobFiles Yes" is important as 
it allows users to reprint jobs that fail due to 
  various reasons. its handy and other distros are using this as a default 
option

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

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

[Touch-packages] [Bug 322210] Re: [needs-packaging] PPD for Dymo LabelWriter 400 not complete

[gf]

Sorry, I meant: ".. with the *cups* package."  :)

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

Title:
  [needs-packaging] PPD for Dymo LabelWriter 400 not complete

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cups

  Release: 8.10
  Cups package version: 1.3.9-2ubuntu6.1

  I installed Dymo LabelWriter 400 with the Multi-Purpose labels 11354.
  I chose the only available driver: Dymo Label Printer, 1.3

  Problem: I could not set the correct label size as the Multi-Purpose
  labels are missing from the ppd-file. The result is that I get
  printouts which do not fit the labels.

  Solution:
  I downloaded the driver from the manufacturer and extracted the lines for the 
Multi-Purpose labels from their ppd-file.
  drivers page: 
https://global.dymo.com/enUS/RNW/RNW.html?pg=std_adp.php_faqid=101
  driver file: http://www.dymo.com/media/Software/dymo-cups-drivers-1.0.3.tar.gz

  What should be done is that the ppd-file in cups should be updated
  with all the labels in the manufacturers ppd. Depending on their
  license.

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

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

[Touch-packages] [Bug 322210] Re: [needs-packaging] PPD for Dymo LabelWriter 400 not complete

[gf]

Hello Ben,
Thank you for submitting this feature/enhancement request for the hplip 
package.  You made this request quite some time ago and Ubuntu has been updated 
since then. 

Do you think this feature/enhancement is still needed or can we close
this bug report?

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

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

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

Title:
  [needs-packaging] PPD for Dymo LabelWriter 400 not complete

Status in cups package in Ubuntu:
  Incomplete

Bug description:
  Binary package hint: cups

  Release: 8.10
  Cups package version: 1.3.9-2ubuntu6.1

  I installed Dymo LabelWriter 400 with the Multi-Purpose labels 11354.
  I chose the only available driver: Dymo Label Printer, 1.3

  Problem: I could not set the correct label size as the Multi-Purpose
  labels are missing from the ppd-file. The result is that I get
  printouts which do not fit the labels.

  Solution:
  I downloaded the driver from the manufacturer and extracted the lines for the 
Multi-Purpose labels from their ppd-file.
  drivers page: 
https://global.dymo.com/enUS/RNW/RNW.html?pg=std_adp.php_faqid=101
  driver file: http://www.dymo.com/media/Software/dymo-cups-drivers-1.0.3.tar.gz

  What should be done is that the ppd-file in cups should be updated
  with all the labels in the manufacturers ppd. Depending on their
  license.

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

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

[Touch-packages] [Bug 343801] Re: cupsd.conf defaults need to allow reprint of jobs

[gf]

Hello Kemble,
Thank you for submitting this feature/enhancement request for the hplip 
package.  You made this request quite some time ago and Ubuntu has been updated 
since then. 

Do you think this feature/enhancement is still needed or can we close
this bug report?

Thank you again for helping make Ubuntu better. 
G
[Ubuntu Bug Squad volunteer triager]

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

Title:
  cupsd.conf defaults need to allow reprint of jobs

Status in CUPS:
  New
Status in cups package in Ubuntu:
  Incomplete
Status in system-config-printer package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: cups

  if you see the screen shots in this thread
  http://ubuntuforums.org/showthread.php?t=820916 you will see what im
  talking about i think it would be much nicer if /etc/cups/cupsd.conf
  contained these 2 lines by default

  # preserve last 50 print jobs

  PreserveJobFiles Yes
  MaxJobs 50

  
  you can make max jobs higher but the "PreserveJobFiles Yes" is important as 
it allows users to reprint jobs that fail due to 
  various reasons. its handy and other distros are using this as a default 
option

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

-- 
Mailing list: https://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 1799868] Re: seq command has problems near its max integer

[Kevin O'Gorman]

I dont usually read info pages since I have trouble navigating them.  But
reading what you quoted made clear what happened.

I would personally have preferred it if seq would notice when the increment
is not doing anything, and instead of producing infinite output, complained
and quit as it does when the starting value is too large.  The fact that it
does that in one case is part of why I thought it was a bug to not do it in
another.

But to be honest, I'd have implemented unlimited integers rather than using
floating point, perhaps by making it use Python under the covers, since
that's how Python normally works.  Well maybe I wouldn't do it that way in
coreutils  But I'd do it.  It's not that hard if you're not doing
multiply or divide.

On Mon, Oct 29, 2018 at 4:00 PM C de-Avillez  wrote:

> Hello Kevin, and thank you for opening this bug and helping make Ubuntu
> better.
>
> The info page for seq (info seq) has the following note:
>
> " On most systems, seq can produce whole-number output for values up to
> at least 2^{53}.  Larger integers are approximated.  The details differ
> depending on your floating-point implementation.  *Note Floating
> point::.  A common case is that ‘seq’ works with integers through
> 2^{64}, and larger integers may not be numerically correct:
>
>  $ seq 5000 2 5004
>  5000
>  5000
>  5004
>
>However, note that when limited to non-negative whole numbers, an
> increment of 1 and no format-specifying option, seq can print
> arbitrarily large numbers.
>
>Be careful when using ‘seq’ with outlandish values: otherwise you may
> see surprising results, as ‘seq’ uses floating point internally.  For
> example, on the x86 platform, where the internal representation uses a
> 64-bit fraction, the command:
>
>  seq 1 0.001 1.009
>
>outputs 1.007 twice and skips 1.008."
>
> Now, 2^64 is 18446744073709551616, which is *much* smaller than the
> values you are using. So... you are in the boundary of the map, where it
> is written "here be dragons."
>
> I ran 'seq' with your initial value, and increment of 1, and varying
> end-values, all larger than the initial value. All seemed to work
> correctly. But the moment I changed the increment... things went south
> very fast (including what seemed as an infinite loop, with 'seq'
> outputting the same value over and over).
>
> I am in a mind of closing this bug INVALID, but wanted to have your
> input before that.
>
> Thank you.
>
> ** Changed in: coreutils (Ubuntu)
>Status: New => Incomplete
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1799868
>
> Title:
>   seq command has problems near its max integer
>
> Status in coreutils package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I can use seq(1) to generate sequences of large numbers if I use the
>   default increment:
>
>   $ seq 170141183460469231731687303715884105721
> 170141183460469231731687303715884105725
>   170141183460469231731687303715884105721
>   170141183460469231731687303715884105722
>   170141183460469231731687303715884105723
>   170141183460469231731687303715884105724
>   170141183460469231731687303715884105725
>   $
>
>   However, if I use an increment of 2 (which should stop 2 short of the
> max int,) it starts with the max integer+1 (2^127) and outputs it forever:
>   $ seq 170141183460469231731687303715884105721 2
> 170141183460469231731687303715884105725 | less
>   170141183460469231731687303715884105728
>   170141183460469231731687303715884105728
>   170141183460469231731687303715884105728
>   170141183460469231731687303715884105728
>   .
>   .
>   .
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: coreutils 8.28-1ubuntu1
>   ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
>   Uname: Linux 4.15.0-36-generic x86_64
>   NonfreeKernelModules: nvidia_modeset nvidia
>   ApportVersion: 2.20.9-0ubuntu7.4
>   Architecture: amd64
>   CurrentDesktop: ubuntu:GNOME
>   Date: Wed Oct 24 20:17:15 2018
>   SourcePackage: coreutils
>   UpgradeStatus: Upgraded to bionic on 2018-08-19 (66 days ago)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/coreutils/+bug/1799868/+subscriptions
>


-- 
Kevin O'Gorman
#define QUESTION ((bb) || (!bb))   /* Shakespeare */

Please consider the environment before printing this email.


** Attachment added: "unnamed"
   https://bugs.launchpad.net/bugs/1799868/+attachment/5207860/+files/unnamed

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

Title:
  seq command has problems near its max integer

Status in coreutils package in Ubuntu:
  Incomplete

Bug description:
  I can use seq(1) 

[Touch-packages] [Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep

[Snaker]

Sometimes appindicators workaround doesn't work and icons disappear
again, but noticeably less often.

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

Title:
  icons from qt applications disappear after screen lock/sleep

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Indicators of some Qt apps are not showing after unlocking the screen
  or shell restart.

  
  [Test case]

  - Login to 17.10
  - launch dropbox (if not already launched)
  - Launch telegram (snap version or without libappindicator support)
  - Observe icons in taskbar
  - Lock screen with Super+L
  - Unlock screen
  - Icons should still be there

  
  [Possible regressions]

  Icons that should be hidden could be visible instead

  The fix doesn't apply to snapped applications

  In the Ubuntu Xorg session, with the Ubuntu Appindicator extension
  enabled, the tray icons for QT apps (in my case, both owncloud-client
  from the Ubuntu repos and enpass, from their own repo) show up after
  first logging in. But once the screen has been left idle long enough
  to be put to sleep, and is then woken up (I don't actually have screen
  *lock* enabled, but it still goes comes back to the clock screen and a
  further gesture is needed to scroll that up to get the desktop), then
  the icons for those QT apps are gone. Non-QT apps (eg: in my case
  hexchat, from the ubuntu repos) remain.

  For a while and due to inattention it seemed more random than that,
  but I'm fairly sure now it's just the display sleep/wake thing that
  kills it.

  The applications are still running in the background (so for instance
  enpass is still available via the browser extension), and can be seen
  in the process list. It's just the icons that have disappeared. If I
  then kill those apps (from the commandline with 'kill [pid]' because
  there's no other interface to do it from) and relaunch them, they
  reappear back in the appindicator area.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 24 17:12:43 2017
  Dependencies:

  InstallationDate: Installed on 2017-07-30 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to artful on 2017-08-22 (2 days ago)

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

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

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

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358162

** Merge proposal linked:
   
https://code.launchpad.net/~simpoir/ubuntu/+source/landscape-client/+git/landscape-client/+merge/358163

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

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

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

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

  [Impact]

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

  [Test Case]

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

  The expectation is that system goes to shutdown.

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

  [Regression Potential]

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade

[DSHR]

diff --git a/sound/usb/quirks-table.h b/sound/usb/quirks-table.h
index 08aa78007020..849953e5775c 100644
--- a/sound/usb/quirks-table.h
+++ b/sound/usb/quirks-table.h
@@ -3346,19 +3346,14 @@ AU0828_DEVICE(0x2040, 0x7270, "Hauppauge", "HVR-950Q"),
.ifnum = 0,
.type = QUIRK_AUDIO_STANDARD_MIXER,
},
-   /* Capture */
-   {
-   .ifnum = 1,
-   .type = QUIRK_IGNORE_INTERFACE,
-   },
/* Playback */
{
-   .ifnum = 2,
+   .ifnum = 1,
.type = QUIRK_AUDIO_FIXED_ENDPOINT,
.data = &(const struct audioformat) {
.formats = SNDRV_PCM_FMTBIT_S16_LE,
.channels = 2,
-   .iface = 2,
+   .iface = 1,
.altsetting = 1,
.altset_idx = 1,
.attributes = UAC_EP_CS_ATTR_FILL_MAX |

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  

[Touch-packages] [Bug 1773697] Re: [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed with error -22 after kernel upgrade

[DSHR]

Seems to be fixed with the daily kernel image linux-image-
unsigned-4.19.0-999-lowlatency

% uname -a ✔  175  13:35:02
Linux ThinkPad-X220 4.19.0-999-lowlatency #201810312202 SMP PREEMPT Thu Nov 1 
02:11:24 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

This version contains kernel commit c369c8db15d51fa175d2ba85928f79d16af6b562
that fixes the issue for me.

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

Title:
  [USB-Audio - PX USB, playback] snd-usb-audio: probe of 2-3:1.0 failed
  with error -22 after kernel upgrade

Status in alsa-driver package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  Bug report has been generated on a partially working configuration.
  That allows ubuntu-bug to do more work.

  USB-Audio Connection on Bowers & Wilkens PX Bluetooth Headphones
  started working when upgrading kernel from 4.13 to 4.15 series. Then
  it suddenly stopped working again on newer kernels. The bug report has
  been generated on the latest working mainline kernel 4.15.7. All newer
  kernels have some usb quirks in place, which should fix the playback
  sample rates to 48 kHz. The quirk seems not to be working correctly
  and hinder the audio system to recognize the USB-device as a sound
  device.

  The Headphones work on kernels before 4,15.7 when manually configuring
  pulseaudio to a default samplerate of 48 kHz.

  PX Headphones are on the newest firmware level.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.15.7-041507-lowlatency x86_64
  AlsaInfo: Error: command ['/usr/share/alsa-base/alsa-info.sh', '--stdout', 
'--no-upload'] failed with exit code 1: mktemp: failed to create directory via 
template '/tmp/zsh-1000/alsa-info.XX': No such file or directory
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  CurrentDesktop: GNOME
  Date: Sun May 27 22:21:53 2018
  InstallationDate: Installed on 2016-02-05 (841 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:USB successful
  Symptom_Card: PX USB - PX USB
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dshr   2729 F pulseaudio
   /dev/snd/controlC1:  dshr   2729 F pulseaudio
   /dev/snd/controlC0:  dshr   2729 F pulseaudio
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [USB-Audio - PX USB, playback] No sound at all
  UpgradeStatus: Upgraded to bionic on 2018-05-27 (0 days ago)
  dmi.bios.date: 06/23/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N11ET33W (1.09 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20CJS00Q00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN11ET33W(1.09):bd06/23/2015:svnLENOVO:pn20CJS00Q00:pvrThinkPadT550:rvnLENOVO:rn20CJS00Q00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T550
  dmi.product.name: 20CJS00Q00
  dmi.product.version: ThinkPad T550
  dmi.sys.vendor: LENOVO
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu13
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  dshr   3423 F pulseaudio
   /dev/snd/pcmC0D0c:   dshr   3423 F...m pulseaudio
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 18.10
  InstallationDate: Installed on 2018-02-07 (248 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180128)
  MachineType: LENOVO 4291QQ1
  Package: linux (not installed)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-10-generic 
root=UUID=5501522a-496f-40cb-9b68-8ef9726b16c9 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.18.0-10.11-generic 4.18.12
  RelatedPackageVersions:
   linux-restricted-modules-4.18.0-10-generic N/A
   linux-backports-modules-4.18.0-10-generic  N/A
   linux-firmware 1.175
  Tags:  cosmic
  Uname: Linux 4.18.0-10-generic x86_64
  UpgradeStatus: Upgraded to cosmic on 2018-09-30 (13 days ago)
  UserGroups: adm cdrom dip 

[Touch-packages] [Bug 1800899] Re: Line out and headphones audio output keep swithing causing crackles in sound

[George Panagiotopoulos]

Upgrading to Ubuntu 18.10 didn't seem to help. Using a different set of
headphones also didn't work. Other audio sources work fine. Unplugging
the headphones from the line out port in the back panel of the computer
and plugging it in the front headphones port stops the crackling and the
flickering in the settings. Headphones work fine now.

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

Title:
  Line out and headphones audio output keep swithing causing crackles in
  sound

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  There is an audio crackle every few seconds when I use headphones.
  Under the sound tab in settings the "Line Out-Built-in Audio" device
  flickers at the exact moment there is a crackle. By opening the
  pavucontrol audio manager I can see the "Built-in Audio Analog Stereo"
  output device port keeps switching to "Headphones (unplugged)" from
  "Line Out(plugged in)" for an instance.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  george10877 F pulseaudio
   /dev/snd/controlC2:  george10877 F pulseaudio
   /dev/snd/controlC0:  george10877 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Oct 31 20:21:09 2018
  InstallationDate: Installed on 2018-10-09 (21 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Green Line Out, Rear
  Symptom_PulseAudioLog:
   Οκτ 31 18:49:55 LinuxPC dbus-daemon[775]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.38' (uid=1000 pid=1298 comm="/usr/bin/pulseaudio --start 
--log-target=syslog " label="unconfined")
   Οκτ 31 18:49:58 LinuxPC dbus-daemon[775]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.44' 
(uid=1000 pid=1298 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined")
   Οκτ 31 19:49:44 LinuxPC dbus-daemon[775]: [system] Activating via systemd: 
service name='org.bluez' unit='dbus-org.bluez.service' requested by ':1.211' 
(uid=1000 pid=10877 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined")
  Symptom_Type: Underruns, dropouts, or "crackling" sound
  Title: [To be filled by O.E.M., Realtek ALC887-VD, Green Line Out, Rear] 
Underruns, dropouts or crackling sound
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/23/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F4
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Z170-HD3P-CF
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF4:bd11/23/2015:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ170-HD3P-CF:rvrx.x:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1004541] Re: apt-get update did not run even after updating apt.conf file

[Julian Andres Klode]

Closing as per David's comment from 2012

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

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

Title:
  apt-get update did not run even after updating apt.conf file

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Generally I am a FEDORA user. I formatted my system and installed ubuntu 
yesterday.I could not update even after the correct network setting.My network 
connection is correct and I am able to browse through net.
  I updated apt.conf for proxy settings
  I updated the source.list file too
  but bug remains same

  I installed system twice and changed apt.conf :
  "Acquire::http::username:password@proxy.server:80/"
  as
  "Acquire :: http ::  username : gkm010mkg@ee...@proxy.cse.iitb.ac.in:80/"
  then I realized the big bug

  my password contained @ symbol.and the SOFTWARE WRITTEN TO READ THE APT.CONF 
READS IT 'LEFT TO RIGHT'; AS MY PASSWD CONTAINED @ SYMBOL, IT TOOK 
'ee...@proxt.cse.iitb.ac.in' as the server address INSTEAD OF 
'proxy.cse.iitb.ac.in',and obviously could not fetch it..!!
  
::REMEDY
  THE SOFTWARE SHOULD BE RECODED AS READING APT.CONF FROM RIGHT TO LEFT FOR 
ROBUSTNESS.

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

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

[Touch-packages] [Bug 1798868] Re: Compiz Crashed with SIGSEGV [Radeon]

[Dash]

I have the same problem, needed datas were given at
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1741447/comments/68

Daniel

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

Title:
  Compiz Crashed with SIGSEGV [Radeon]

Status in mesa package in Ubuntu:
  New

Bug description:
  Symptoms:
  On login, the desktop takes a long time to load, and when it does, everything 
blinks. It is possible (but difficult) to open a terminal and execute commands, 
through the right-click desktop menu.

  I first noticed the issue in mid-July of 2018.

  System:
  Acer 5100
  Ubuntu 16.04 (64-bit)
  Graphics card: VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] RS482M [Mobility Radeon Xpress 200]

  Believed to be mesa-related, as symptoms very similar to bug #1741447
  and #1735594. I have been informed by a mesa developer that my issue
  is different because that bug affects Intel GPUs. This system has a
  Radeon GPU.

  Log files are as attached to bug #1795709. That bug was declared
  invalid by Apport because it says I don't have the necessary debug
  packages installed. However, I could not find the debug packages in
  the repository, so that is why I am submitting this report manually.

  Many thanks for any help.

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

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

[Touch-packages] [Bug 1765451] Re: im trying

[Daniel van Vugt]

Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!


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

Title:
  im trying

Status in Ubuntu:
  Incomplete

Bug description:
  im am new to this but am trying. thankyou

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Thu Apr 19 11:40:16 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Sony Corporation Core Processor Integrated Graphics Controller 
[104d:9071]
  InstallationDate: Installed on 2009-01-01 (3395 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release i386 
(20140722.2)
  MachineType: Sony Corporation VPCEB3KFX
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=62bd1ac0-0e27-483e-9dd9-5b13196e0971 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 08/17/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R1100Y8
  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:bvnAmericanMegatrendsInc.:bvrR1100Y8:bd08/17/2010:svnSonyCorporation:pnVPCEB3KFX:pvrC6069R1G:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.family: VAIO
  dmi.product.name: VPCEB3KFX
  dmi.product.version: C6069R1G
  dmi.sys.vendor: Sony Corporation
  version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu Apr 19 10:07:52 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.5-0ubuntu2

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

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

[Touch-packages] [Bug 1766005] Re: tengo problemas

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.

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

** Changed in: ubuntu
   Status: New => Won't Fix

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

Title:
  tengo problemas

Status in Ubuntu:
  Won't Fix

Bug description:
  programas que abren , va lento , tegeta grafica intel hd no es hd , todo 
recien instalado 
  ayuda que soy bastante nuevo

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 21 21:02:45 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Pegatron HD Graphics 520 [1b0a:226e]
  InstallationDate: Installed on 2018-04-13 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Medion E7419 MD99852
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic.efi.signed 
root=UUID=c0f87936-50b0-415c-bded-43764272cfee ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/07/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 212
  dmi.board.asset.tag: Default string
  dmi.board.name: D17SUN
  dmi.board.vendor: Medion
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 10
  dmi.chassis.vendor: Medion
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr212:bd01/07/2016:svnMedion:pnE7419MD99852:pvr1.0:rvnMedion:rnD17SUN:rvr1.0:cvnMedion:ct10:cvr1.0:
  dmi.product.family: Default string
  dmi.product.name: E7419 MD99852
  dmi.product.version: 1.0
  dmi.sys.vendor: Medion
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/+bug/1766005/+subscriptions

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

[Touch-packages] [Bug 1764768] Re: i dont know do it yourself

[Daniel van Vugt]

Thank you for reporting this bug to Ubuntu.
Ubuntu 17.10 (artful) reached end-of-life on July 19, 2018.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases 

We appreciate that this bug may be old and you might not be interested
in discussing it any more. But if you are then please upgrade to the
latest Ubuntu version and re-test. If you then find the bug is still
present in the newer Ubuntu version, please add a comment here telling
us which new version it is in and change the bug status to Confirmed.


** Changed in: xorg (Ubuntu)
   Status: New => Won't Fix

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

Title:
  i dont know do it yourself

Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  screen resolution not getting incresed

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg 1:7.7+19ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 17 20:05:38 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation 82G33/G31 Express Integrated Graphics Controller 
[8086:29c2] (rev 10) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation 82G33/G31 Express Integrated Graphics 
Controller [8086:29c2]
  InstallationDate: Installed on 2018-04-17 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic 
root=UUID=df0f2577-5cb5-4904-923c-6c5a09311940 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/27/2008
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: PRG3110H.86A.0047.2008.0227.1745
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DG31PR
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE39516-300
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrPRG3110H.86A.0047.2008.0227.1745:bd02/27/2008:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAE39516-300:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  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/1764768/+subscriptions

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

[Touch-packages] [Bug 1800329] Re: Ubnutu 18.04 LTS KDE Neon does not resolve local (or single name) queries through DHCP assigned DNS (cached) server on local network

[Venca B Spam]

I tried to find a reasonable solution and looks that there are different
approaches.

I wanted to stay at most within the distribution layout while keeping
all business requirements fulfilled. This is what I tested:

```code


# Install required package and reconfigure service plans (i.e. disable 
systemd-resolved, enable dnsmasq
sudo apt-get install dnsmasq
sudo systemctl disable systemd-resolved
sudo systemctl stop systemd-resolved
sudo systemctl enable dnsmasq

# These two lines should work on most environments, but .. :-)
# Just add or change 'dns=dnsmasq' to your NetworkManager.conf to the section 
[main]
#sudo cp /etc/NetworkManager/NetworkManager.conf 
/etc/NetworkManager/NetworkManager.conf.backup
#sudo bash -c 'cat /etc/NetworkManager/NetworkManager.conf.backup |sed -e 
"s/^dns=.*//"| sed -e "s/\[main\]/\[main\]\ndns=dnsmasq/" 
>/etc/NetworkManager/NetworkManager.conf'

# Restart NetworkManager to make the change above applied
sudo systemctl restart NetworkManager

# This removes the systemd resolv.conf link only if it has NetworkManager 
replacement :-)
ls /var/run/NetworkManager/resolv.conf && sudo rm /etc/resolv.conf 

# And add NetworkManager's resolv.conf available for the system resolver
sudo ln -s /var/run/NetworkManager/resolv.conf /etc/resolv.conf


```

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

Title:
  Ubnutu 18.04 LTS KDE Neon does not resolve local (or single name)
  queries through DHCP assigned DNS (cached) server on local network

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Ubnutu 18.04 KDE Neon does not resolve local (or single name) queries
  through DHCP assigned DNS (cached) server on local network.

  ** How to reproduce? **

  1. Let's have local network (e.g. 192.168.123.0/24) connected to the Internet 
through router called GATE
  2. The GATE provides local DNS server cache (via Dnsmasq) and contains couple 
of local name translations (e.g. SuperCooolLocalServer pointing to 
192.168.123.50).
  3. Let's have fresh new Ubuntu 18.04 (KDE Neon)
  4. Connect to the local network through WIFI (WPA2 encrypted, jsut enter 
password)

  ** What happens? **

  Any desktop application trying to connect to SuperCooolLocalServer
  will fail when resolving the name to IP.

  When tested in terminal "host SuperCooolLocalServer" will return
  SERVFAIL.

  ** What is expected? **

  The system should resolve the name SuperCooolLocalServer to
  192.168.123.50 as it did until Ubuntu 16.04 LTS.

  ** Observation **

  The system should do the resolution in the same logic as other home
  appliances running various operating systems (my iPhone, my wife's
  Galaxy, ours Ubuntu 16.04LTS, Windows 7, 8.1 10 and our other network
  components running various Linux based distributions.)

  I did quick test and the bug shows also on clean Ubuntu 18.04 (without
  the KDE Neon flavour).

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

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