[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

[mohammad sadegh dehghan niri]

i also having same problem with wired connection!! ubuntu 16.04.4

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:

[Touch-packages] [Bug 1666432] Re: Internet drops every few minutes on wired and wireless connection

[mohammad sadegh dehghan niri]

i also having same problem with wired connection!! ubuntu 16.04.4

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

Title:
  Internet drops every few minutes on wired and wireless connection

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Internet drops every 1-30 minutes when connected via wired or wireless
  (i.e., this is a problem on both wired and wireless) even though
  connection icon indicates the computer is still connected.

  Disconnecting and reconnecting via the connection icon resets internet
  temporarily until the next time.

  Dropped internet is discovered with "The site can't be reached"
  screens in Chromium, or error messages when downloading/updating in
  Terminal, or missing connection in Ubuntu Software app, or stalled
  syncing in Insync application (occurred even without Insync).

  Internet drops more frequently on wireless than on wired.

  It seems to disconnect more frequently with heavier internet use
  (e.g., downloading multiple files, opening several webpages in quick
  succession).

  This is a fresh install (yesterday) of Ubuntu 16.04 on a Dell Inspiron
  15 5567 (dual boot). It occurs when running Live CD as well though.

  Ethernet and wifi both work without randomly disconnecting in Windows
  10 on the same machine, and ethernet and wifi work on other machines
  running Ubuntu and Windows with the same router, so it is not a
  hardware or router issue.

  Output from sudo lshw -class network

  *-network
     description: Wireless interface
     product: Wireless 3165
     vendor: Intel Corporation
     physical id: 0
     bus info: pci@:02:00.0
     logical name: wlp2s0
     version: 79
     serial: 58:fb:84:55:21:52
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress bus_master cap_list ethernet physical 
wireless
     configuration: broadcast=yes driver=iwlwifi 
driverversion=4.4.0-62-generic firmware=17.352738.0 ip=192.168.1.15 latency=0 
link=yes multicast=yes wireless=IEEE 802.11abgn
     resources: irq:283 memory:df10-df101fff
    *-network
     description: Ethernet interface
     product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller
     vendor: Realtek Semiconductor Co., Ltd.
     physical id: 0
     bus info: pci@:03:00.0
     logical name: enp3s0
     version: 07
     serial: 18:db:f2:3c:d5:37
     size: 10Mbit/s
     capacity: 100Mbit/s
     width: 64 bits
     clock: 33MHz
     capabilities: pm msi pciexpress msix vpd bus_master cap_list ethernet 
physical tp mii 10bt 10bt-fd 100bt 100bt-fd autonegotiation
     configuration: autonegotiation=on broadcast=yes driver=r8169 
driverversion=2.3LK-NAPI duplex=half firmware=rtl8106e-1_0.0.1 06/29/12 
latency=0 link=no multicast=yes port=MII speed=10Mbit/s
     resources: irq:279 ioport:d000(size=256) memory:df00-df000fff 
memory:d030-d0303fff

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: network-manager 1.2.2-0ubuntu0.16.04.3
  ProcVersionSignature: Ubuntu 4.4.0-62.83-generic 4.4.40
  Uname: Linux 4.4.0-62-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Feb 21 16:36:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-02-20 (1 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.1.1 dev wlp2s0  proto static  metric 600
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000
   192.168.1.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.1.15  
metric 600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION   CON-UUID  CON-PATH
   wlp2s0  wifi  connected/org/freedesktop/NetworkManager/Devices/0  
pr500k-9912ec-1  36301ded-0ac5-4a86-9621-87290ef159af  
/org/freedesktop/NetworkManager/ActiveConnection/5
   enp3s0  ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/1  -- 
  ----
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/2  -- 
  ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.2.2connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:

[Touch-packages] [Bug 1780552] Re: i am suffering from updraged to 18.04.

[aadarsshvelu]

** Summary changed:

- i am suffering from updraged to 18.04.
+ Doesn't  detected my sound card

** Description changed:

- fix the bug soon. i using without sound since may.I am looking for a
+ Can't turn on the audio in control Panel!!
+ 
+ No Sound  Symbol indicates in status bar!!
+ 
+ Fix the bug soon. i using without sound since may.I am looking for a
  update to fix.But i Still looking to get any update from your side.I
  send bug report before a week.No Replays from you.
  
+ Please replay me soon
  
- Please replay me soon
+ I'M looking for some to fix the Bug!
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  7 20:49:19 2018
  InstallationDate: Installed on 2018-02-11 (146 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0PNFDX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0PNFDX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.

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

Title:
  Doesn't  detected my sound card

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Can't turn on the audio in control Panel!!

  No Sound  Symbol indicates in status bar!!

  Fix the bug soon. i using without sound since may.I am looking for a
  update to fix.But i Still looking to get any update from your side.I
  send bug report before a week.No Replays from you.

  Please replay me soon

  I'M looking for some to fix the Bug!

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  7 20:49:19 2018
  InstallationDate: Installed on 2018-02-11 (146 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0PNFDX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0PNFDX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1780853] Re: [GeForce GTX 960M] Xorg freeze

[Daniel van Vugt]

It sounds like some part of the system has crashed. Please:

1. Apply the workaround from bug 994921.

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

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


** Summary changed:

- Xorg freeze
+ [GeForce GTX 960M] Xorg freeze

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

** Tags added: nouveau nvidia

** Changed in: xorg-server (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/1780853

Title:
  [GeForce GTX 960M] Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Just installed 18.04 yesterday from live usb, live usb boots fine,
  install will not boot unless nomodeset is entered at boot. Will hang
  showing start job for gpu-manager running. Also hangs on issuing
  reboot saying stop job for gpu-manager or session 1. Tried purging
  nvidia-* and was able to boot a few times, then after software updater
  ran it began having the issue again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  9 16:32:11 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d6d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d6d]
  InstallationDate: Installed on 2018-07-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 002: ID 04f2:b450 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. GL752VW
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=3cb644e4-6352-449b-8711-623733d99f27 ro nomodeset vga=799
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL752VW.214
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL752VW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL752VW.214:bd04/18/2016:svnASUSTeKCOMPUTERINC.:pnGL752VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL752VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: GL
  dmi.product.name: GL752VW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1780850] Re: monitor incorrect

[Daniel van Vugt]

Please describe in more detail what the problem is.

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

** Changed in: xorg-server (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/1780850

Title:
  monitor incorrect

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Wrong monitor performance, unable to set well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jul  9 21:36:32 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS482/RS485 [Radeon Xpress 
1100/1150] [1458:d000]
  InstallationDate: Installed on 2018-02-28 (130 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: FUJITSU SIEMENS GA-K8RS482M
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=ae28586a-e989-4c32-9ab5-ceee8bacba22 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2005
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: GA-K8RS482M
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/27/2005:svnFUJITSUSIEMENS:pnGA-K8RS482M:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8RS482M:rvrx.x:cvn:ct3:cvr:
  dmi.product.name: GA-K8RS482M
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Jul  9 21:00:59 2018
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1

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

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

[Touch-packages] [Bug 1779905] Re: 'apt install pulseaudio-module-jack' fails with error

[Daniel van Vugt]

** Tags added: xenial

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

Title:
  'apt install pulseaudio-module-jack' fails with error

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I try to load pulseaudio-module-jack modules, I get an error:

  Failure: Module initialization failed

  When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules.

  So I then tried to install it with `sudo apt install pulseaudio-
  module-jack` after first running `sudo apt update`. The output gives
  me this error:

  
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Package pulseaudio-module-jack is not available, but is referred to by 
another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source

  E: Package 'pulseaudio-module-jack' has no installation candidate

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

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

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

[Daniel van Vugt]

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

** This bug has been marked a duplicate of bug 1780860
   Xorg freeze

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  radeon ring backup+oxd3/ox/140
  radeon rsp:bbb2029afbe0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jul  9 23:15:13 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 630] [1043:8400]
  InstallationDate: Installed on 2018-07-06 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=03812000-7685-4c0e-a864-1161fc28656b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: 970 Pro3 R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd10/02/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Pro3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

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

[Daniel van Vugt]

It appears you now have only a GeForce GT 630 installed, using the
nouveau driver.

If you want to report a bug against your Radeon card then please:
 1. Reinstall that radeon card.
 2. Boot the machine and instead of logging in hit Ctrl+Alt+F4. Now log into 
the text terminal.
 3. Run this command to send us new system information:
 apport-collect 1780860

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

** Changed in: xorg-server (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/1780860

Title:
  Xorg freeze

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  radeon ring backup+oxd3/ox/140
  radeon rsp:bbb2029afbe0 
  I changed grafics card from msi R7870 twin froser iii I want to put it back
  since it does the same with the asus gt630

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jul  9 23:15:13 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 630] [1043:8400]
  InstallationDate: Installed on 2018-07-06 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=03812000-7685-4c0e-a864-1161fc28656b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: 970 Pro3 R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd10/02/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Pro3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Daniel van Vugt]

Yes that was released a few hours ago:
https://launchpad.net/ubuntu/+source/linux-firmware/1.157.20

George: as the original reporter can you confirm that today's update to
the 'linux-firmware' package has fixed it?

** Changed in: linux-firmware (Ubuntu)
   Status: Confirmed => Incomplete

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

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

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

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

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-firmware package in Ubuntu:
  Incomplete

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
     Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
     Status: "Running"
     CGroup: /system.slice/bluetooth.service
     └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
   hci0 24:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung 

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[Daniel van Vugt]

You can ignore comment #29 now. The proper official fix for 18.04 is:
https://launchpad.net/ubuntu/+source/bluez/5.48-0ubuntu3.1/+build/15084683

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1780885] Re: hangs at Building initial module for 4.15.0-23-generic (promptless password prompt)

[Andrew McLeod]

Further info: I am running bionic, upgraded from xenial -> zesty ->
bionic, and have done previous apt-get upgrade's in bionic without
running into this issue.

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

Title:
  hangs at Building initial module for 4.15.0-23-generic (promptless
  password prompt)

Status in apt package in Ubuntu:
  New

Bug description:
  This bug may more specifically be with dkms, but assume most people
  will hit it this way

  sudo apt-get update ; sudo apt-get upgrade would hang at:

  Building initial module for 4.15.0-23-generic

  after a few seconds, keypresses/enter were not being registered, but
  there is a secret password prompt - i.e., at this point, when things
  appear to have hung, entering your password twice will continue the
  process. It may also be related to 'secure boot' but I am unsure.

  Similar issue and resolution found here:

  https://github.com/teejee2008/ukuu/issues/81

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

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

[Touch-packages] [Bug 1780885] [NEW] hangs at Building initial module for 4.15.0-23-generic (promptless password prompt)

[Andrew McLeod]

Public bug reported:

This bug may more specifically be with dkms, but assume most people will
hit it this way

sudo apt-get update ; sudo apt-get upgrade would hang at:

Building initial module for 4.15.0-23-generic

after a few seconds, keypresses/enter were not being registered, but
there is a secret password prompt - i.e., at this point, when things
appear to have hung, entering your password twice will continue the
process. It may also be related to 'secure boot' but I am unsure.

Similar issue and resolution found here:

https://github.com/teejee2008/ukuu/issues/81

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

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

Title:
  hangs at Building initial module for 4.15.0-23-generic (promptless
  password prompt)

Status in apt package in Ubuntu:
  New

Bug description:
  This bug may more specifically be with dkms, but assume most people
  will hit it this way

  sudo apt-get update ; sudo apt-get upgrade would hang at:

  Building initial module for 4.15.0-23-generic

  after a few seconds, keypresses/enter were not being registered, but
  there is a secret password prompt - i.e., at this point, when things
  appear to have hung, entering your password twice will continue the
  process. It may also be related to 'secure boot' but I am unsure.

  Similar issue and resolution found here:

  https://github.com/teejee2008/ukuu/issues/81

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

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

[Touch-packages] [Bug 1672822] Re: sound only coming from left speaker on acer predator (fresh install)

[Daniel van Vugt]

Having said that, this sounds like very specific hardware with a very
specific problem. So in this case I'm happy to reopen this bug.

** Tags added: bionic

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

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

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

Title:
  sound only coming from left speaker on acer predator (fresh install)

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

Bug description:
  Ubuntu version: Ubuntu  16.10 and a fresh install of 17.04 and even
  fedora F25-WORK-x86_64-20170228 via live usb

  Device: acer predator: G9-593-7757 15,6"/i7-7700/32 GB RAM/512 GB
  SSD/1 TB HDD/GTX1070

  expected: sound comes out of both left and right speaker and the
  subwoofer

  what happened instead:
  Sound only comes out of the left speaker or subwoofer.

  More system information:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  audio chip (on motherboard): VGA Chip nVidia N17E-G2-A1 GP104-725-A1

  note that that is only 1 device, one would expect several here.

  I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following:
  # This file is part of PulseAudio.
  #
  # PulseAudio is free software; you can redistribute it and/or modify
  # it under the terms of the GNU Lesser General Public License as published by
  # the Free Software Foundation; either version 2 of the License, or
  # (at your option) any later version.
  #
  # PulseAudio is distributed in the hope that it will be useful, but
  # WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  # General Public License for more details.
  #
  # You should have received a copy of the GNU Lesser General Public License
  # along with PulseAudio; if not, see .

  ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
  ## more information. Default values are commented out.  Use either ; or # for
  ## commenting.

  ; daemonize = no
  ; fail = yes
  ; allow-module-loading = yes
  ; allow-exit = yes
  ; use-pid-file = yes
  ; system-instance = no
  ; local-server-type = user
  ; enable-shm = yes
  ; enable-memfd = yes
  ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
  ; lock-memory = no
  ; cpu-limit = no

  ; high-priority = yes
  ; nice-level = -11

  ; realtime-scheduling = yes
  ; realtime-priority = 5

  ; exit-idle-time = 20
  ; scache-idle-time = 20

  ; dl-search-path = (depends on architecture)

  ; load-default-script-file = yes
  ; default-script-file = /etc/pulse/default.pa

  ; log-target = auto
  ; log-level = notice
  ; log-meta = no
  ; log-time = no
  ; log-backtrace = 0

  ; resample-method = speex-float-1
  ; enable-remixing = yes
   enable-lfe-remixing = yes
  ; lfe-crossover-freq = 0

  flat-volumes = no

  ; rlimit-fsize = -1
  ; rlimit-data = -1
  ; rlimit-stack = -1
  ; rlimit-core = -1
  ; rlimit-as = -1
  ; rlimit-rss = -1
  ; rlimit-nproc = -1
  ; rlimit-nofile = 256
  ; rlimit-memlock = -1
  ; rlimit-locks = -1
  ; rlimit-sigpending = -1
  ; rlimit-msgqueue = -1
  ; rlimit-nice = 31
  ; rlimit-rtprio = 9
  ; rlimit-rttime = 20

  ; default-sample-format = s16le
  ; default-sample-rate = 44100
  ; alternate-sample-rate = 48000
  default-sample-channels = 3
  default-channel-map = front-left,front-right,lfe

  ; default-fragments = 4
  ; default-fragment-size-msec = 25

  ; enable-deferred-volume = yes
  deferred-volume-safety-margin-usec = 1
  ; deferred-volume-extra-delay-usec = 0

  but this did not work. I also tried various other permutations to see
  if changing the order of  front-left,front-right,lfe would work but it
  did not. I also tried to see if it would work in fedora but the same
  problem occurred there. When on ubuntu 16.10 at first only the
  subwoofer seemed to be working and altering the file only the left
  speaker was working. On ubuntu 17.04 only the left speaker was working
  regardless of how I altered the above file.

  
  Note that the speakers work perfectly fine on windows 10. 

  Looking around online there seem to be a lot of problems with acer
  predator laptops and sound on ubuntu.

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

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

[Touch-packages] [Bug 1672822] Re: sound only coming from left speaker on acer predator (fresh install)

[Daniel van Vugt]

This bug has been closed for 5 months due to no response from the
original reporter.

If you have any problems at all then please discuss them in new bug
reports.

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

Title:
  sound only coming from left speaker on acer predator (fresh install)

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

Bug description:
  Ubuntu version: Ubuntu  16.10 and a fresh install of 17.04 and even
  fedora F25-WORK-x86_64-20170228 via live usb

  Device: acer predator: G9-593-7757 15,6"/i7-7700/32 GB RAM/512 GB
  SSD/1 TB HDD/GTX1070

  expected: sound comes out of both left and right speaker and the
  subwoofer

  what happened instead:
  Sound only comes out of the left speaker or subwoofer.

  More system information:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  audio chip (on motherboard): VGA Chip nVidia N17E-G2-A1 GP104-725-A1

  note that that is only 1 device, one would expect several here.

  I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following:
  # This file is part of PulseAudio.
  #
  # PulseAudio is free software; you can redistribute it and/or modify
  # it under the terms of the GNU Lesser General Public License as published by
  # the Free Software Foundation; either version 2 of the License, or
  # (at your option) any later version.
  #
  # PulseAudio is distributed in the hope that it will be useful, but
  # WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  # General Public License for more details.
  #
  # You should have received a copy of the GNU Lesser General Public License
  # along with PulseAudio; if not, see .

  ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
  ## more information. Default values are commented out.  Use either ; or # for
  ## commenting.

  ; daemonize = no
  ; fail = yes
  ; allow-module-loading = yes
  ; allow-exit = yes
  ; use-pid-file = yes
  ; system-instance = no
  ; local-server-type = user
  ; enable-shm = yes
  ; enable-memfd = yes
  ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
  ; lock-memory = no
  ; cpu-limit = no

  ; high-priority = yes
  ; nice-level = -11

  ; realtime-scheduling = yes
  ; realtime-priority = 5

  ; exit-idle-time = 20
  ; scache-idle-time = 20

  ; dl-search-path = (depends on architecture)

  ; load-default-script-file = yes
  ; default-script-file = /etc/pulse/default.pa

  ; log-target = auto
  ; log-level = notice
  ; log-meta = no
  ; log-time = no
  ; log-backtrace = 0

  ; resample-method = speex-float-1
  ; enable-remixing = yes
   enable-lfe-remixing = yes
  ; lfe-crossover-freq = 0

  flat-volumes = no

  ; rlimit-fsize = -1
  ; rlimit-data = -1
  ; rlimit-stack = -1
  ; rlimit-core = -1
  ; rlimit-as = -1
  ; rlimit-rss = -1
  ; rlimit-nproc = -1
  ; rlimit-nofile = 256
  ; rlimit-memlock = -1
  ; rlimit-locks = -1
  ; rlimit-sigpending = -1
  ; rlimit-msgqueue = -1
  ; rlimit-nice = 31
  ; rlimit-rtprio = 9
  ; rlimit-rttime = 20

  ; default-sample-format = s16le
  ; default-sample-rate = 44100
  ; alternate-sample-rate = 48000
  default-sample-channels = 3
  default-channel-map = front-left,front-right,lfe

  ; default-fragments = 4
  ; default-fragment-size-msec = 25

  ; enable-deferred-volume = yes
  deferred-volume-safety-margin-usec = 1
  ; deferred-volume-extra-delay-usec = 0

  but this did not work. I also tried various other permutations to see
  if changing the order of  front-left,front-right,lfe would work but it
  did not. I also tried to see if it would work in fedora but the same
  problem occurred there. When on ubuntu 16.10 at first only the
  subwoofer seemed to be working and altering the file only the left
  speaker was working. On ubuntu 17.04 only the left speaker was working
  regardless of how I altered the above file.

  
  Note that the speakers work perfectly fine on windows 10. 

  Looking around online there seem to be a lot of problems with acer
  predator laptops and sound on ubuntu.

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

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

[DH]

#29 Fix confirmed on Ubuntu 18.04 on Miix 700 / Intel 8260

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Fix Released
Status in bluez source package in Bionic:
  Fix Committed
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  [Impact]

  Users of Bluetooth audio have no sound after they suspend and resume
  the system.

  [Test Case]

   1. Connect to Bluetooth audio device
   2. Suspend & Resume
   3. Reconnect to Bluetooth device.

  [Regression Potential]

  Low. Although common Bluetooth code is modified in the fix, it has
  been released as a patch in other distros for some time already.

  [Other Info]

  Already released to cosmic as part of bluez version 5.50.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
    BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
    UP RUNNING PSCAN
    RX bytes:5025 acl:32 sco:0 events:202 errors:0
    TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1745828] Re: [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

[Zero]

This is now working again as of Linux-Firmware 1.157.20 received today.

THANK YOU, THANK YOU, THANK YOU!!!

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

Title:
  [rtl8821a] Ubuntu 16.04 can't find any Bluetooth devices

Status in bluez package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in linux-firmware package in Ubuntu:
  Confirmed

Bug description:
  It is ON and VISIBLE in the control panel.  My iPhone can see two
  other devices but it can't see the computer, and the computer  can't
  see anything, even if left searching for tens of minutes.

  The previous answers listed below suggest the following diagnostics

  Bluetooth not working after update
  How can I make my bluetooth works on Ubuntu 16.04?
  Ubuntu 16.04 bluetooth not working (Dell XPS13)
  Bluetooth (Atheros AR3012) not working on Ubuntu 16.04
  Bluetooth not working on Ubuntu 16.04 LTS
  Bluetooth cannot find any devices
  Stuck on a bluetooth problem

  The service seems to be running

  /home >sudo service bluetooth status
  ● bluetooth.service - Bluetooth service
     Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor 
preset
     Active: active (running) since Thu 2018-01-25 09:16:43 GMT; 1h 46min ago
   Docs: man:bluetoothd(8)
   Main PID: 790 (bluetoothd)
     Status: "Running"
     CGroup: /system.slice/bluetooth.service
     └─790 /usr/lib/bluetooth/bluetoothd

  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.87
  Jan 25 09:18:31 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: Endpoint registered: 
sender=:1.12
  Jan 25 09:20:32 george-CM6330 bluetoothd[790]: RFCOMM server failed for 
Headset
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:20:50 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.
  Jan 25 09:21:01 george-CM6330 bluetoothd[790]: Endpoint unregistered: 
sender=:1.

  and not blocked

  /home >rfkill list
  0: hci0: Bluetooth
   Soft blocked: no
   Hard blocked: no
  1: phy0: Wireless LAN
   Soft blocked: no
   Hard blocked: no

  I have edited /etc/bluetooth/main.conf to include

  AutoEnable=true

  but I noted that the entire file was commented out.

  The kernel seems reasonably up to date

   >uname -a
  Linux george-CM6330 4.13.0-26-generic #29~16.04.2-Ubuntu SMP Tue Jan 9 
22:00:44 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

  I wonder if I need a device driver, but I have no idea how to find
  out.  The following diagnostics may help some of you knowledgeable
  people find out.

   >hcitool dev
  Devices:
   hci0 24:0A:64:F5:EE:86

  and the output of dmsg is

  >dmesg | grep Blue
  [2.030855] usb 1-1.4: Product: Bluetooth Radio
  [   13.806355] Bluetooth: Core ver 2.22
  [   13.806369] Bluetooth: HCI device and connection manager initialized
  [   13.806372] Bluetooth: HCI socket layer initialized
  [   13.806373] Bluetooth: L2CAP socket layer initialized
  [   13.806377] Bluetooth: SCO socket layer initialized
  [   13.827384] Bluetooth: hci0: rtl: examining hci_ver=06 hci_rev=000a 
lmp_ver=06 lmp_subver=8821
  [   13.827386] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_config.bin
  [   13.865327] Bluetooth: hci0: rtl: loading rtl_bt/rtl8821a_fw.bin
  [   13.877382] Bluetooth: hci0: rom_version status=0 version=1
  [   13.877387] Bluetooth: cfg_sz 0, total size 17428
  [   16.550280] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [   16.550281] Bluetooth: BNEP filters: protocol multicast
  [   16.550284] Bluetooth: BNEP socket layer initialized
  [   27.868345] Bluetooth: RFCOMM TTY layer initialized
  [   27.868350] Bluetooth: RFCOMM socket layer initialized
  [   27.868354] Bluetooth: RFCOMM ver 1.11

  and of lsusb is

  >lsusb
  Bus 002 Device 003: ID 046d:c52f Logitech, Inc. Unifying Receiver
  Bus 002 Device 006: ID 04b8:0849 Seiko Epson Corp. Stylus SX205
  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 002: ID 04e8:6123 Samsung Electronics Co., Ltd
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 004: ID 13d3:3414 IMC Networks
  Bus 001 Device 003: ID 058f:6366 Alcor Micro Corp. Multi Flash Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  Thanking you in anticipation
  ---
  ApportVersion: 

[Touch-packages] [Bug 1672822] Re: sound only coming from left speaker on acer predator (fresh install)

[CleverSageLife]

@rotten hdajackretask worked for me.  Confirmed.

My Acer Predator 15 G9-593-72VT has:
Card: HDA Intel PCH
Chip: Realtek ALC255


FIXING IT BY SETTING THE PINS AKA JACK RETASKING:


STEP 1: INSTALL THE FOLLOWING SUITE OF APPS:
sudo apt-get install alsa-tools-gui

STEP 2: RUN THIS PARTICULAR APP FROM THE SUITE AT THE TERMINAL:
hdajackretask

STEP 3: CHECK THE FOLLOWING BOX:
show unconnected pins

STEP 4: SET THE PINS AS FOLLOWS: 
0x14 to "Internal Speaker" (do NOT check the box for override)
0x17 to "Internal Speaker LFE" (check the box for override)
0x1b to "Internal Speaker (Back)" (check the box for override)

STEP 5: TEST IT 
(play a song or stream a video?)


STEP 6: IF THE TEST SUCCEEDS, CLICK BUTTON:
Install Boot Override
(you will need to put in an admin password)

STEP 7: REBOOT
See if the settings stuck after a restart.

At any time, if something goes wonky, restart the computer, and try
again. I found that sometimes the sound quits and freezes while applying
different configs, but a restart resets it back to normal.

https://i.imgur.com/B6iYgcN.jpg

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

Title:
  sound only coming from left speaker on acer predator (fresh install)

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

Bug description:
  Ubuntu version: Ubuntu  16.10 and a fresh install of 17.04 and even
  fedora F25-WORK-x86_64-20170228 via live usb

  Device: acer predator: G9-593-7757 15,6"/i7-7700/32 GB RAM/512 GB
  SSD/1 TB HDD/GTX1070

  expected: sound comes out of both left and right speaker and the
  subwoofer

  what happened instead:
  Sound only comes out of the left speaker or subwoofer.

  More system information:

  $ aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC255 Analog [ALC255 Analog]
    Subdevices: 1/1
    Subdevice #0: subdevice #0

  audio chip (on motherboard): VGA Chip nVidia N17E-G2-A1 GP104-725-A1

  note that that is only 1 device, one would expect several here.

  I attempted to fix this by modifying the /etc/pulse/deamon.conf into the 
following:
  # This file is part of PulseAudio.
  #
  # PulseAudio is free software; you can redistribute it and/or modify
  # it under the terms of the GNU Lesser General Public License as published by
  # the Free Software Foundation; either version 2 of the License, or
  # (at your option) any later version.
  #
  # PulseAudio is distributed in the hope that it will be useful, but
  # WITHOUT ANY WARRANTY; without even the implied warranty of
  # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU
  # General Public License for more details.
  #
  # You should have received a copy of the GNU Lesser General Public License
  # along with PulseAudio; if not, see .

  ## Configuration file for the PulseAudio daemon. See pulse-daemon.conf(5) for
  ## more information. Default values are commented out.  Use either ; or # for
  ## commenting.

  ; daemonize = no
  ; fail = yes
  ; allow-module-loading = yes
  ; allow-exit = yes
  ; use-pid-file = yes
  ; system-instance = no
  ; local-server-type = user
  ; enable-shm = yes
  ; enable-memfd = yes
  ; shm-size-bytes = 0 # setting this 0 will use the system-default, usually 64 
MiB
  ; lock-memory = no
  ; cpu-limit = no

  ; high-priority = yes
  ; nice-level = -11

  ; realtime-scheduling = yes
  ; realtime-priority = 5

  ; exit-idle-time = 20
  ; scache-idle-time = 20

  ; dl-search-path = (depends on architecture)

  ; load-default-script-file = yes
  ; default-script-file = /etc/pulse/default.pa

  ; log-target = auto
  ; log-level = notice
  ; log-meta = no
  ; log-time = no
  ; log-backtrace = 0

  ; resample-method = speex-float-1
  ; enable-remixing = yes
   enable-lfe-remixing = yes
  ; lfe-crossover-freq = 0

  flat-volumes = no

  ; rlimit-fsize = -1
  ; rlimit-data = -1
  ; rlimit-stack = -1
  ; rlimit-core = -1
  ; rlimit-as = -1
  ; rlimit-rss = -1
  ; rlimit-nproc = -1
  ; rlimit-nofile = 256
  ; rlimit-memlock = -1
  ; rlimit-locks = -1
  ; rlimit-sigpending = -1
  ; rlimit-msgqueue = -1
  ; rlimit-nice = 31
  ; rlimit-rtprio = 9
  ; rlimit-rttime = 20

  ; default-sample-format = s16le
  ; default-sample-rate = 44100
  ; alternate-sample-rate = 48000
  default-sample-channels = 3
  default-channel-map = front-left,front-right,lfe

  ; default-fragments = 4
  ; default-fragment-size-msec = 25

  ; enable-deferred-volume = yes
  deferred-volume-safety-margin-usec = 1
  ; deferred-volume-extra-delay-usec = 0

  but this did not work. I also tried various other permutations to see
  if changing the order of  front-left,front-right,lfe would work but it
  did not. I also tried to see if it would work in fedora but the same
  problem occurred there. When on ubuntu 16.10 at first only the
  

[Touch-packages] [Bug 1576844] Re: Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

[kinwolf]

I went to Linux Mint 19(ubuntu 18.04) and got this bug now.  I was using
kernel 4.11 in mint 18 without problem.  This look like a regression

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

Title:
  Touchpad/Trackpad freezes then eventually unfreezes (repeatedly)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Several times yesterday and today (April 28-29, 2016) the touchpad
  (trackpad) on the Dell XPS 13 9343 has frozen.  Other functions
  (keyboard, screen, etc.) have been fine but the pointer has been
  frozen in place.  Then after 1-3 minutes functionality returns.

  Thank you very much for your assistance and I'd be happy to provide
  more information.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.38-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: wl
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: [core,composite,opengl,cube,rotate]
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Apr 29 16:09:32 2016
  DistUpgraded: 2016-04-27 15:53:13,798 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bcmwl, 6.30.223.248+bdcom, 4.2.0-36-generic, x86_64: installed
   bcmwl, 6.30.223.248+bdcom, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
     Subsystem: Dell Broadwell-U Integrated Graphics [1028:0665]
  InstallationDate: Installed on 2015-08-06 (267 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-22-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (2 days ago)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Apr 27 15:54:22 2016
  xserver.configfile: default
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5152
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2

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

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

[Touch-packages] [Bug 1780359] Re: circular dependency between libcups2-dev and libcupsimage2-dev (2.2.7-1ubuntu2) on bionic

[Bug Watch Updater]

** Changed in: cups (Debian)
   Status: Unknown => Won't Fix

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

Title:
  circular dependency between libcups2-dev and libcupsimage2-dev
  (2.2.7-1ubuntu2) on bionic

Status in cups package in Ubuntu:
  New
Status in cups package in Debian:
  Won't Fix

Bug description:
  Circular dependency between libcups2-dev and libcupsimage2-dev
  (2.2.7-1ubuntu2) on ubuntu-18.04 (bionic).

  root@qvb58jams52fr9r:~# apt-cache depends libcups2-dev
  libcups2-dev
Depends: libcupsimage2-dev
Depends: libcups2
Depends: dpkg-dev
  root@qvb58jams52fr9r:~# apt-cache depends libcupsimage2-dev
  libcupsimage2-dev
Depends: libcupsimage2
Depends: libcups2-dev
Depends: libpng-dev
Depends: libtiff-dev
Depends: libjpeg-dev
  libjpeg-turbo8-dev
Depends: zlib1g-dev
Recommends: libcupsfilters-dev

  One of my pipelines failed to install libcupsimage2-dev:
  15:36:57 Some packages could not be installed. This may mean that you have
  15:36:57 requested an impossible situation or if you are using the unstable
  15:36:57 distribution that some required packages have not yet been created
  15:36:57 or been moved out of Incoming.
  15:36:57 The following information may help to resolve the situation:
  15:36:57 
  15:36:57 The following packages have unmet dependencies:
  15:36:57  libcups2-dev : Depends: libcupsimage2-dev (= 2.2.7-1ubuntu2) but it 
is not going to be installed
  15:36:57 W: --force-yes is deprecated, use one of the options starting with 
--allow instead.
  15:36:57 E: Unable to correct problems, you have held broken packages.

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

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

[Touch-packages] [Bug 1670959] Re: systemd-resolved using 100% CPU

[Pieter]

Ubuntu 18.04.

edited   $sudo vim /etc/resolv.conf

changed

nameserver 127.0.0.1

to

nameserver 127.0.0.53

CPU calmed down.

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

Title:
  systemd-resolved using 100% CPU

Status in dnsmasq package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Sometimes systemd-resolved process is using 100% CPU.
  After a while it changes back to normal.

  It happens usually after connecting to the (wifi) network, like
  starting the OS.

  strace output:

  sendmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"6\215\201\200\0\1\0\1\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\300\f\0\34\0\1\0\0\10\235\0\20&\6(\0\0024\0Y%L\4\6#f&\214\0\0)\377\326\0\0\0\0\0\0",
 81}], msg_controllen=28, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}], 
msg_flags=0}, 0) = 81
  sendmsg(3, {msg_name(0)=NULL, 
msg_iov(4)=[{"PRIORITY=6\nSYSLOG_FACILITY=3\nCODE_FILE=../src/resolve/resolved-dns-stub.c\nCODE_LINE=363\nCODE_FUNCTION=dns_stub_process_query\nSYSLOG_IDENTIFIER=systemd-resolved\n",
 160}, {"MESSAGE=", 8}, {"Processing query...", 19}, {"\n", 1}], 
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 188
  epoll_wait(4, [{EPOLLIN, {u32=3176459184, u64=94565471415216}}], 16, -1) = 1
  clock_gettime(CLOCK_BOOTTIME, {44665, 938069872}) = 0
  recvfrom(12, NULL, 0, MSG_PEEK|MSG_TRUNC, NULL, NULL) = 53
  recvmsg(12, {msg_name(16)={sa_family=AF_INET, sin_port=htons(33589), 
sin_addr=inet_addr("127.0.0.1")}, 
msg_iov(1)=[{"Z\262\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 3936}], msg_controllen=56, [{cmsg_len=28, cmsg_level=SOL_IP, 
cmsg_type=IP_PKTINFO, {ipi_ifindex=if_nametoindex("lo"), 
ipi_spec_dst=inet_addr("127.0.0.53"), ipi_addr=inet_addr("127.0.0.53")}}, 
{cmsg_len=20, cmsg_level=SOL_IP, cmsg_type=IP_TTL, {ttl=64}}], msg_flags=0}, 0) 
= 53
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\365I", 2, GRND_NONBLOCK)= 2
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  getrandom("\203;", 2, GRND_NONBLOCK)= 2
  clock_gettime(CLOCK_BOOTTIME, {44665, 938446937}) = 0
  open("/run/systemd/netif/links/3", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such 
file or directory)
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  stat("/etc/resolv.conf", {st_mode=S_IFREG|0644, st_size=303, ...}) = 0
  socket(AF_INET, SOCK_DGRAM|SOCK_CLOEXEC|SOCK_NONBLOCK, IPPROTO_IP) = 18
  connect(18, {sa_family=AF_INET, sin_port=htons(53), 
sin_addr=inet_addr("127.0.0.1")}, 16) = 0
  epoll_ctl(4, EPOLL_CTL_ADD, 18, {EPOLLIN, {u32=3176610576, 
u64=94565471566608}}) = 0
  write(18, 
"\203;\1\20\0\1\0\0\0\0\0\1\4cs41\3wac\vedgecastcdn\3net\0\0\34\0\1\0\0)\2\0\0\0\0\0\0\0",
 53) = 53
  clock_gettime(CLOCK_BOOTTIME, {44665, 938833717}) = 0
  clock_gettime(CLOCK_BOOTTIME, {44665, 938875138}) = 0
  epoll_ctl(4, EPOLL_CTL_DEL, 18, NULL)   = 0
  close(18)   = 0

  journalctl output:

  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:35 parsec systemd-resolved[1512]: Processing query...
  Mar 08 08:25:41 parsec dnsmasq[1545]: Maximum number of concurrent DNS 
queries reached (max: 150)

  As you can see, I would use it together with dnsmasq.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: systemd 232-18ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
  Uname: Linux 4.10.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Wed Mar  8 08:20:18 2017
  MachineType: Hewlett-Packard HP EliteBook Folio 1020 G1
  ProcEnviron:
   LANGUAGE=en_US:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/zsh
  ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.10.0-9-generic 
root=UUID=a54fe703-35d4-47ac-9c6e-4034421531fb ro rootflags=subvol=@
  SourcePackage: systemd
  UpgradeStatus: Upgraded to zesty on 2015-05-24 (653 days ago)
  dmi.bios.date: 03/09/2015
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: M77 Ver. 01.05
  dmi.board.name: 2271
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 91.4C
  dmi.chassis.asset.tag: CNU51199KV
  

[Touch-packages] [Bug 1780165] Re: tc does not display value of prio and quantum options of htb on bionic

[fumihiko kakuma]

Please backport the following.

https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/tc/q_htb.c?id=d529ea2ff417eed1d48c580e099388aaace16ce9

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

Title:
  tc does not display value of prio and quantum options of htb on bionic

Status in iproute2 package in Ubuntu:
  New

Bug description:
  For example when I execute the following commandline, tc does not
  display value of prio and quantum option.

  # tc qdisc add dev eno2 root handle 1: htb default 10
  # tc class add dev eno2 parent 1: classid 1:1 htb rate 100mbit
  # tc class add dev eno2 parent 1:1 classid 1:10 htb rate 1mibit
  # tc class add dev eno2 parent 1:1 classid 1:20 htb quantum 1000 rate 50mibit 
prio 1
  # tc -d class show dev eno2
  class htb 1:10 parent 1:1 prio quantum rate 1048Kbit ceil 1048Kbit linklayer 
ethernet burst 1599b/1 mpu 0b cburst 1599b/1 mpu 0b level 0
  class htb 1:1 root rate 100Mbit ceil 100Mbit linklayer ethernet burst 1600b/1 
mpu 0b cburst 1600b/1 mpu 0b level 7
  class htb 1:20 parent 1:1 prio quantum rate 52428Kbit ceil 52428Kbit 
linklayer ethernet burst 1592b/1 mpu 0b cburst 1592b/1 mpu 0b level 0
  #

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 18.04 LTS
  Release:18.04
  Codename:   bionic
  $ uname -a
  Linux vajk471iaa0s 4.15.0-20-generic #21-Ubuntu SMP Tue Apr 24 06:16:15 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
  $ dpkg -l | grep iproute
  ii  iproute2  4.15.0-2ubuntu1 
 amd64networking and traffic control tools
  $

  I sent the patch for this bug to ML of upstream.

  https://www.spinics.net/lists/netdev/msg511127.html

  I think that the above patch can be applied for the bionic.

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

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

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

[con-1428]

Public bug reported:

radeon ring backup+oxd3/ox/140
radeon rsp:bbb2029afbe0 
I changed grafics card from msi R7870 twin froser iii I want to put it back
since it does the same with the asus gt630

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompositorRunning: None
Date: Mon Jul  9 23:15:13 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 630] [1043:8400]
InstallationDate: Installed on 2018-07-06 (3 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=03812000-7685-4c0e-a864-1161fc28656b ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 10/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: 970 Pro3 R2.0
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd10/02/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Pro3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  radeon ring backup+oxd3/ox/140
  radeon rsp:bbb2029afbe0 
  I changed grafics card from msi R7870 twin froser iii I want to put it back
  since it does the same with the asus gt630

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jul  9 23:15:13 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 630] [1043:8400]
  InstallationDate: Installed on 2018-07-06 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=03812000-7685-4c0e-a864-1161fc28656b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: 970 Pro3 R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 

[Touch-packages] [Bug 1780552] Re: i am suffering from updraged to 18.04.

[Seth Arnold]

** 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 alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/1780552

Title:
  i am suffering from updraged to 18.04.

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  fix the bug soon. i using without sound since may.I am looking for a
  update to fix.But i Still looking to get any update from your side.I
  send bug report before a week.No Replays from you.

  
  Please replay me soon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/hwC1D0', 
'/dev/snd/pcmC1D0c', '/dev/snd/pcmC1D0p', '/dev/snd/controlC1', 
'/dev/snd/by-path', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', 
'/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', 
'/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] 
failed with exit code 1:
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  7 20:49:19 2018
  InstallationDate: Installed on 2018-02-11 (146 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  PackageArchitecture: all
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: alsa-driver
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/22/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 0PNFDX
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd04/22/2016:svnDellInc.:pnInspiron3558:pvr:rvnDellInc.:rn0PNFDX:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 3558
  dmi.sys.vendor: Dell Inc.

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

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

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

[con-1428]

Public bug reported:

radeon ring backup+oxd3/ox/140
radeon rsp:bbb2029afbe0

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompositorRunning: None
Date: Mon Jul  9 23:15:13 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 630] [1043:8400]
InstallationDate: Installed on 2018-07-06 (3 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=03812000-7685-4c0e-a864-1161fc28656b ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLogOld:
 
dmi.bios.date: 10/02/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.50
dmi.board.name: 970 Pro3 R2.0
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd10/02/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Pro3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.family: To Be Filled By O.E.M.
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  radeon ring backup+oxd3/ox/140
  radeon rsp:bbb2029afbe0

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Mon Jul  9 23:15:13 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 630] [10de:0f00] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 630] [1043:8400]
  InstallationDate: Installed on 2018-07-06 (3 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=03812000-7685-4c0e-a864-1161fc28656b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLogOld:
   
  dmi.bios.date: 10/02/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.50
  dmi.board.name: 970 Pro3 R2.0
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd10/02/2013:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn970Pro3R2.0:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  

[Touch-packages] [Bug 1780506] Re: Password visible in systemd password prompt if user types too slow

[Seth Arnold]

Nice find. When I tested this, it also left the terminal echo off:

sarnold@hunt:/etc/apparmor.d$ systemctl daemon-reload 
 AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
Authentication is required to reload the systemd state.
Authenticating as: Seth Arnold,,, (sarnold)
Password: Failed to reload daemon: Method call timed out
polkit-agent-helper-1: pam_authenticate failed: Authentication failure
sarnold@hunt:/etc/apparmor.d$ STRENGEHEIM: command not found
...

Thanks

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

Title:
  Password visible in systemd password prompt if user types too slow

Status in systemd package in Ubuntu:
  New

Bug description:
  When systemd prompts for a password (for example, using systemctl
  without sudo and requiring authentication), it times out if the user
  does not type the password fast enough (after about 30 seconds or so).

  This results in the password becoming visible on the next prompt from
  bash (or whatever shell was being used) as the password is left on
  standard input.

  
  Perhaps this package should consume the input when timing out. Not sure if 
this is possible, but a security issue.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu21.2
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Fri Jul  6 17:31:46 2018
  InstallationDate: Installed on 2015-03-06 (1218 days ago)
  InstallationMedia: Ubuntu-Server 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Dell Inc. PowerEdge R310
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-119-generic 
root=/dev/mapper/hostname--vg-root ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to xenial on 2016-08-26 (679 days ago)
  dmi.bios.date: 03/03/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.4
  dmi.board.name: 05XKKK
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A02
  dmi.chassis.type: 23
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.4:bd03/03/2011:svnDellInc.:pnPowerEdgeR310:pvr:rvnDellInc.:rn05XKKK:rvrA02:cvnDellInc.:ct23:cvr:
  dmi.product.name: PowerEdge R310
  dmi.sys.vendor: Dell Inc.

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

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

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

[Andrew Smith]

Public bug reported:

Just installed 18.04 yesterday from live usb, live usb boots fine,
install will not boot unless nomodeset is entered at boot. Will hang
showing start job for gpu-manager running. Also hangs on issuing reboot
saying stop job for gpu-manager or session 1. Tried purging nvidia-* and
was able to boot a few times, then after software updater ran it began
having the issue again.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul  9 16:32:11 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a day
GpuHangReproducibility: Seems to happen randomly
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d6d]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d6d]
InstallationDate: Installed on 2018-07-08 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 002: ID 04f2:b450 Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. GL752VW
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=3cb644e4-6352-449b-8711-623733d99f27 ro nomodeset vga=799
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL752VW.214
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL752VW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL752VW.214:bd04/18/2016:svnASUSTeKCOMPUTERINC.:pnGL752VW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL752VW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: GL
dmi.product.name: GL752VW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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


** Tags: amd64 apport-bug bionic freeze ubuntu

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Just installed 18.04 yesterday from live usb, live usb boots fine,
  install will not boot unless nomodeset is entered at boot. Will hang
  showing start job for gpu-manager running. Also hangs on issuing
  reboot saying stop job for gpu-manager or session 1. Tried purging
  nvidia-* and was able to boot a few times, then after software updater
  ran it began having the issue again.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  9 16:32:11 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Seems to happen randomly
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 530 [1043:1d6d]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:1d6d]
  InstallationDate: Installed on 2018-07-08 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux 

[Touch-packages] [Bug 1779302] Re: should retry reading key from keyserver (in _recv_key)

[Launchpad Bug Tracker]

** Branch linked: lp:~smoser/software-properties/trunk.lp-1779302-retry-
recv-keys

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

Title:
  should retry reading key from keyserver (in _recv_key)

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Some recent events have made keyservers less reliable than they were
  previously:
    https://bitbucket.org/skskeyserver/sks-keyserver/issues/57
    https://bitbucket.org/skskeyserver/sks-keyserver/issues/60

  We have seen a greatly increased failure rate of retreiving keys
  from the key servers, both in cloud-init and with using apt-add-repository.

  Here is an example failure:
    
https://jenkins.ubuntu.com/server/view/cloud-init,%20curtin,%20streams/job/cloud-init-integration-nocloud-kvm-x/191/console

  The stdout/stderr that is a result of running:
  $ add-apt-repository --yes ppa:cloud-init-devel/daily

  gpg: keyring `/tmp/tmp4s88x_yf/secring.gpg' created
  gpg: keyring `/tmp/tmp4s88x_yf/pubring.gpg' created
  gpg: requesting key E4D304DF from hkp server keyserver.ubuntu.com
  gpgkeys: key 1FF0D8535EF7E719E5C81B9C083D06FBE4D304DF can't be retrieved
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  gpg: keyserver communications error: keyserver helper general error
  gpg: keyserver communications error: unknown pubkey algorithm
  gpg: keyserver receive failed: unknown pubkey algorithm
  Failed to add key.

  Retries on reading the key make sense here to be more resilient to
  transient network or remote service resources.  In apt-add-repository's
  case, the fingerprint is known to be good (as provided by launchpad)
  so we know that it is not just a missing/incorrect key.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-common 0.96.24.33
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 28 22:28:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (1072 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1779905] Re: 'apt-get install pulseaudio-module-jack' fails with error

[Todd Chaffee]

Thank you, I appreciate being able to keep all the history for this bug.
I've reworded the title, description, and set the status back to new.

** Summary changed:

- Missing pulseaudio-module-jack files, cannot load module
+ 'apt-get install pulseaudio-module-jack' fails with error

** Description changed:

  When I try to load pulseaudio-module-jack modules, I get an error:
  
  Failure: Module initialization failed
  
  When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules.
  
- I'm on Ubuntu 16.04.04.
+ So I then tried to install it with `sudo apt install pulseaudio-module-
+ jack` after first running `sudo apt update`. The output gives me this
+ error:
+ 
+ 
+ Reading package lists... Done
+ Building dependency tree
+ Reading state information... Done
+ Package pulseaudio-module-jack is not available, but is referred to by 
another package.
+ This may mean that the package is missing, has been obsoleted, or
+ is only available from another source
+ 
+ E: Package 'pulseaudio-module-jack' has no installation candidate

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

** Summary changed:

- 'apt-get install pulseaudio-module-jack' fails with error
+ 'apt install pulseaudio-module-jack' fails with error

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

Title:
  'apt install pulseaudio-module-jack' fails with error

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  When I try to load pulseaudio-module-jack modules, I get an error:

  Failure: Module initialization failed

  When I look in /usr/lib/pulse-8.0/modules/ there are no jack modules.

  So I then tried to install it with `sudo apt install pulseaudio-
  module-jack` after first running `sudo apt update`. The output gives
  me this error:

  
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Package pulseaudio-module-jack is not available, but is referred to by 
another package.
  This may mean that the package is missing, has been obsoleted, or
  is only available from another source

  E: Package 'pulseaudio-module-jack' has no installation candidate

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

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

[Touch-packages] [Bug 1780850] [NEW] monitor incorrect

[JÁNOS]

Public bug reported:

Wrong monitor performance, unable to set well.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-24-generic i686
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Mon Jul  9 21:36:32 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd RS482/RS485 [Radeon Xpress 
1100/1150] [1458:d000]
InstallationDate: Installed on 2018-02-28 (130 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
MachineType: FUJITSU SIEMENS GA-K8RS482M
ProcEnviron:
 LANGUAGE=hu
 PATH=(custom, no user)
 LANG=hu_HU.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=ae28586a-e989-4c32-9ab5-ceee8bacba22 ro recovery nomodeset
Renderer: Software
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2005
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: GA-K8RS482M
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/27/2005:svnFUJITSUSIEMENS:pnGA-K8RS482M:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8RS482M:rvrx.x:cvn:ct3:cvr:
dmi.product.name: GA-K8RS482M
dmi.sys.vendor: FUJITSU SIEMENS
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Jul  9 21:00:59 2018
xserver.configfile: default
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  monitor incorrect

Status in xorg package in Ubuntu:
  New

Bug description:
  Wrong monitor performance, unable to set well.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic i686
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jul  9 21:36:32 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS482/RS485 [Radeon Xpress 1100/1150] 
[1002:5974] (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS482/RS485 [Radeon Xpress 
1100/1150] [1458:d000]
  InstallationDate: Installed on 2018-02-28 (130 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  MachineType: FUJITSU SIEMENS GA-K8RS482M
  ProcEnviron:
   LANGUAGE=hu
   PATH=(custom, no user)
   LANG=hu_HU.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=ae28586a-e989-4c32-9ab5-ceee8bacba22 ro recovery nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2005
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F3
  dmi.board.name: GA-K8RS482M
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF3:bd10/27/2005:svnFUJITSUSIEMENS:pnGA-K8RS482M:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-K8RS482M:rvrx.x:cvn:ct3:cvr:
  dmi.product.name: GA-K8RS482M
  dmi.sys.vendor: FUJITSU SIEMENS
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.libdrm2: libdrm2 

[Touch-packages] [Bug 1780842] [NEW] package libglx-mesa0 18.0.0~rc5-1ubuntu1 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/libGLX_indirect.so.0', which is also in package

[jason.her...@gmail.com]

Public bug reported:

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

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

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


** Tags: amd64 apport-package bionic ubuntu

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

Title:
  package libglx-mesa0 18.0.0~rc5-1ubuntu1 failed to install/upgrade:
  trying to overwrite 

[Touch-packages] [Bug 1780843] Re: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other in

[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 perl in Ubuntu.
https://bugs.launchpad.net/bugs/1780843

Title:
  package libperl5.26 5.26.2-6 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz',
  which is different from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  The message in terminal (hungarian): Az alábbi csomagoknak teljesítetlen 
függőségei vannak
  depency problem

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libperl5.26 5.26.2-6
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu5
  Architecture: amd64
  Date: Mon Jul  9 20:57:56 2018
  DuplicateSignature:
   package:libperl5.26:5.26.2-6
   Unpacking libperl5.26:i386 (5.26.2-6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-RAPyb4/04-libperl5.26_5.26.2-6_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2018-03-30 (100 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu3
   apt  1.7.0~alpha1
  SourcePackage: perl
  Title: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is 
different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[und3ath]

Mysql Workbench is also affected and removed after updating to curl4
from curl3

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

Title:
  After last updated libcurl3 on libcurl4, some apps are removed.

Status in curl package in Ubuntu:
  Confirmed

Bug description:
  Hi!

  After last updated libcurl3 on libcurl4, system (Kubuntu 18.04 bionic) 
deleted such applications as:
  virtualbox-5.2
  opera-stable
  slack-desktop
  mongodb

  I really need these applications, I installed them with broken
  dependencies, but they are deleted after each update. Is it possible
  to make the dependence of the libcurl3 in libcurl4, and not remove it
  altogether from system?

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

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

[Touch-packages] [Bug 1780843] [NEW] package libperl5.26 5.26.2-6 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other

[Wohlrab Ferenc Erik]

Public bug reported:

The message in terminal (hungarian): Az alábbi csomagoknak teljesítetlen 
függőségei vannak
depency problem

ProblemType: Package
DistroRelease: Ubuntu 18.10
Package: libperl5.26 5.26.2-6
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu5
Architecture: amd64
Date: Mon Jul  9 20:57:56 2018
DuplicateSignature:
 package:libperl5.26:5.26.2-6
 Unpacking libperl5.26:i386 (5.26.2-6) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-RAPyb4/04-libperl5.26_5.26.2-6_i386.deb (--unpack):
  trying to overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', 
which is different from other instances of package libperl5.26:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
InstallationDate: Installed on 2018-03-30 (100 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu3
 apt  1.7.0~alpha1
SourcePackage: perl
Title: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is 
different from other instances of package libperl5.26:i386
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package cosmic package-conflict

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

Title:
  package libperl5.26 5.26.2-6 failed to install/upgrade: trying to
  overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz',
  which is different from other instances of package libperl5.26:i386

Status in perl package in Ubuntu:
  New

Bug description:
  The message in terminal (hungarian): Az alábbi csomagoknak teljesítetlen 
függőségei vannak
  depency problem

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libperl5.26 5.26.2-6
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu5
  Architecture: amd64
  Date: Mon Jul  9 20:57:56 2018
  DuplicateSignature:
   package:libperl5.26:5.26.2-6
   Unpacking libperl5.26:i386 (5.26.2-6) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-RAPyb4/04-libperl5.26_5.26.2-6_i386.deb (--unpack):
trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libperl5.26/changelog.Debian.gz', which is different from other 
instances of package libperl5.26:i386
  InstallationDate: Installed on 2018-03-30 (100 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu3
   apt  1.7.0~alpha1
  SourcePackage: perl
  Title: package libperl5.26 5.26.2-6 failed to install/upgrade: trying to 
overwrite shared '/usr/share/doc/libperl5.26/changelog.Debian.gz', which is 
different from other instances of package libperl5.26:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1154241] Re:

[Dick]

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

http://balance.stevewynter.com

Old Coot

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

Title:
  update manager error

Status in apt package in Ubuntu:
  New

Bug description:
  hi i was updating ubuntu 12.04 and came across this error

  An unresolvable problem occurred while initializing the package
  information.

  Please report this bug against the 'update-manager' package and include the 
following error message
  E:Encountered a section with no Package: header, E:Problem with MergeList 
/var/lib/apt/lists/us.archive.ubuntu.com_ubuntu_dists_precise-updates_main_i18n_Translation-en,
 E:The package lists or status file could not be parsed or opened.'

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

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

[Touch-packages] [Bug 1780359] Re: circular dependency between libcups2-dev and libcupsimage2-dev (2.2.7-1ubuntu2) on bionic

[Molly Waggett]

Can do, thanks for looking into this.

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

Title:
  circular dependency between libcups2-dev and libcupsimage2-dev
  (2.2.7-1ubuntu2) on bionic

Status in cups package in Ubuntu:
  New
Status in cups package in Debian:
  Unknown

Bug description:
  Circular dependency between libcups2-dev and libcupsimage2-dev
  (2.2.7-1ubuntu2) on ubuntu-18.04 (bionic).

  root@qvb58jams52fr9r:~# apt-cache depends libcups2-dev
  libcups2-dev
Depends: libcupsimage2-dev
Depends: libcups2
Depends: dpkg-dev
  root@qvb58jams52fr9r:~# apt-cache depends libcupsimage2-dev
  libcupsimage2-dev
Depends: libcupsimage2
Depends: libcups2-dev
Depends: libpng-dev
Depends: libtiff-dev
Depends: libjpeg-dev
  libjpeg-turbo8-dev
Depends: zlib1g-dev
Recommends: libcupsfilters-dev

  One of my pipelines failed to install libcupsimage2-dev:
  15:36:57 Some packages could not be installed. This may mean that you have
  15:36:57 requested an impossible situation or if you are using the unstable
  15:36:57 distribution that some required packages have not yet been created
  15:36:57 or been moved out of Incoming.
  15:36:57 The following information may help to resolve the situation:
  15:36:57 
  15:36:57 The following packages have unmet dependencies:
  15:36:57  libcups2-dev : Depends: libcupsimage2-dev (= 2.2.7-1ubuntu2) but it 
is not going to be installed
  15:36:57 W: --force-yes is deprecated, use one of the options starting with 
--allow instead.
  15:36:57 E: Unable to correct problems, you have held broken packages.

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

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

[Touch-packages] [Bug 1780359] Re: circular dependency between libcups2-dev and libcupsimage2-dev (2.2.7-1ubuntu2) on bionic

[Till Kamppeter]

Didier, thanks. So it seems to be an upstream bug as it is a circular
dependency in the header files. Can you report that upstream? Thanks.

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

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

Title:
  circular dependency between libcups2-dev and libcupsimage2-dev
  (2.2.7-1ubuntu2) on bionic

Status in cups package in Ubuntu:
  New
Status in cups package in Debian:
  Unknown

Bug description:
  Circular dependency between libcups2-dev and libcupsimage2-dev
  (2.2.7-1ubuntu2) on ubuntu-18.04 (bionic).

  root@qvb58jams52fr9r:~# apt-cache depends libcups2-dev
  libcups2-dev
Depends: libcupsimage2-dev
Depends: libcups2
Depends: dpkg-dev
  root@qvb58jams52fr9r:~# apt-cache depends libcupsimage2-dev
  libcupsimage2-dev
Depends: libcupsimage2
Depends: libcups2-dev
Depends: libpng-dev
Depends: libtiff-dev
Depends: libjpeg-dev
  libjpeg-turbo8-dev
Depends: zlib1g-dev
Recommends: libcupsfilters-dev

  One of my pipelines failed to install libcupsimage2-dev:
  15:36:57 Some packages could not be installed. This may mean that you have
  15:36:57 requested an impossible situation or if you are using the unstable
  15:36:57 distribution that some required packages have not yet been created
  15:36:57 or been moved out of Incoming.
  15:36:57 The following information may help to resolve the situation:
  15:36:57 
  15:36:57 The following packages have unmet dependencies:
  15:36:57  libcups2-dev : Depends: libcupsimage2-dev (= 2.2.7-1ubuntu2) but it 
is not going to be installed
  15:36:57 W: --force-yes is deprecated, use one of the options starting with 
--allow instead.
  15:36:57 E: Unable to correct problems, you have held broken packages.

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

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

[Touch-packages] [Bug 1780359] Re: circular dependency between libcups2-dev and libcupsimage2-dev (2.2.7-1ubuntu2) on bionic

[Didier Raboud]

Nope. The bug is present in Debian for long:
https://bugs.debian.org/838831

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

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

Title:
  circular dependency between libcups2-dev and libcupsimage2-dev
  (2.2.7-1ubuntu2) on bionic

Status in cups package in Ubuntu:
  New

Bug description:
  Circular dependency between libcups2-dev and libcupsimage2-dev
  (2.2.7-1ubuntu2) on ubuntu-18.04 (bionic).

  root@qvb58jams52fr9r:~# apt-cache depends libcups2-dev
  libcups2-dev
Depends: libcupsimage2-dev
Depends: libcups2
Depends: dpkg-dev
  root@qvb58jams52fr9r:~# apt-cache depends libcupsimage2-dev
  libcupsimage2-dev
Depends: libcupsimage2
Depends: libcups2-dev
Depends: libpng-dev
Depends: libtiff-dev
Depends: libjpeg-dev
  libjpeg-turbo8-dev
Depends: zlib1g-dev
Recommends: libcupsfilters-dev

  One of my pipelines failed to install libcupsimage2-dev:
  15:36:57 Some packages could not be installed. This may mean that you have
  15:36:57 requested an impossible situation or if you are using the unstable
  15:36:57 distribution that some required packages have not yet been created
  15:36:57 or been moved out of Incoming.
  15:36:57 The following information may help to resolve the situation:
  15:36:57 
  15:36:57 The following packages have unmet dependencies:
  15:36:57  libcups2-dev : Depends: libcupsimage2-dev (= 2.2.7-1ubuntu2) but it 
is not going to be installed
  15:36:57 W: --force-yes is deprecated, use one of the options starting with 
--allow instead.
  15:36:57 E: Unable to correct problems, you have held broken packages.

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

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

[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd

[Nivedita Singhvi]

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

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

Title:
  [SRU] debhelper support override from /etc/tmpfiles.d for systemd

Status in debhelper:
  Fix Released
Status in debhelper package in Ubuntu:
  Fix Released
Status in rsyslog package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in debhelper source package in Xenial:
  Won't Fix
Status in rsyslog source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Confirmed
Status in debhelper source package in Artful:
  Won't Fix
Status in rsyslog source package in Artful:
  Invalid
Status in systemd source package in Artful:
  Confirmed
Status in debhelper source package in Bionic:
  Won't Fix
Status in rsyslog source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  /var/log's Permission is going back to 755
  after upgrading systemd
  if there are rsyslog's configuration on /var/lib/tmpfiles.d/

  Affected X, A, B, C

  This is because rsyslog's pkg has 00rsyslog.conf and copied it on 
/var/lib/tmpfiles.d/ when it is installing.
  after upgrading systemd, systemd only refresh it's own tmpfiles so disappear 
conf for 00rsyslog.conf ( it doesn't remove file itself )
  so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back 
permission to 775

  [Test Case]

  1. deploy 16.04 vm
  2. check ll /var (775)
  3. apt install --reinstall systemd
  4. check ll /var (755)

  [Regression Potential]
  This fix changes debhelper's override process by using absolute path to 
filename. so if the other pkgs using debhelper e.g systemd are there, It should 
be re-build with new debhelper after patching in theory, now only systemd is 
affected. but building is not affected. also, pkg like rsyslog which is using 
systemd's tmpfile system need to be changed to use 
/etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 
00rsyslog.conf.

  [Others]

  For this issue, need to fix below pkgs

  debhelper
  systemd ( rebuilding with new debhelper is needed )
  rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, 
to support override supported by debhelper )

  [Original description]

  Upgrading or reinstalling the systemd package when using rsyslogd
  results in bad permissions (0755 instead of 0775) being set on
  /var/log/. As a consequence of this, rsyslogd can no longer create new
  files within this directory, resulting in lost log messages.

  The default configuration of rsyslogd provided by Ubuntu runs the
  daemon as syslog:syslog and sets ownership of /var/log to syslog:adm
  with mode 0775.

  Systemd's default tmpfiles configuration sets /var/log to 0755 in
  /usr/lib/tmpfiles.d/var.conf, however this is overridden in
  /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package
  rsyslog.

  It looks as though an upgrade of the systemd package fails to take
  /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated
  below. This results in /var/log receiving mode 0755 instead of the
  expected 0775:

  nick @ log2.be1.ams1:~ $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  nick @ log2.be1.ams1:~ $ apt policy systemd
  systemd:
    Installed: 229-4ubuntu21.1
    Candidate: 229-4ubuntu21.1
    Version table:
   *** 229-4ubuntu21.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  nick @ log2.be1.ams1:~ $ apt policy rsyslog
  rsyslog:
    Installed: 8.16.0-1ubuntu3
    Candidate: 8.16.0-1ubuntu3
    Version table:
   *** 8.16.0-1ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  nick @ log2.be1.ams1:~ $ grep -F /var/log /usr/lib/tmpfiles.d/var.conf
  d /var/log 0755 - - -
  f /var/log/wtmp 0664 root utmp -
  f /var/log/btmp 0600 root utmp -

  nick @ log2.be1.ams1:~ $ cat /usr/lib/tmpfiles.d/00rsyslog.conf
  # Override systemd's default tmpfiles.d/var.conf to make /var/log writable by
  # the syslog group, so that rsyslog can run as user.
  # See tmpfiles.d(5) for details.

  # Type PathMode UID  GID  Age Argument
  d /var/log 0775 root syslog -

  nick @ log2.be1.ams1:~ $ ls -ld /var/log
  drwxrwxr-x 8 root syslog 4096 Feb  7 13:45 /var/log

  nick @ log2.be1.ams1:~ $ sudo apt install --reinstall systemd
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  0 upgraded, 0 

[Touch-packages] [Bug 1748147] Re: [SRU] debhelper support override from /etc/tmpfiles.d for systemd

[Nivedita Singhvi]

Tested, works.

Repro (Xenial):
# dpkg -l | grep systemd
ii  systemd  229-4ubuntu21.2
amd64system and service manager

/var# ll
drwxrwxr-x  8 root syslog 4096 Jul  9 06:25 log/  <--775

# apt install --reinstall systemd

/var# ll
drwxr-xr-x  8 root syslog 4096 Jul  9 06:25 log/  <-- 755


Bionic (Verified):
# dpkg -l | grep systemd
ii  systemd   237-3ubuntu10.2   
amd64system and service manager

/var# ll
drwxrwxr-x  8 root syslog 4096 Jul  9 13:09 log/<-- 775

# apt install --reinstall systemd
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 2895 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic-proposed/main amd64 systemd amd64 
237-3ubuntu10.2 [2895 kB]
...

/var# ll
drwxrwxr-x  8 root syslog 4096 Jul  9 13:09 log/ <-- 775

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

Title:
  [SRU] debhelper support override from /etc/tmpfiles.d for systemd

Status in debhelper:
  Fix Released
Status in debhelper package in Ubuntu:
  Fix Released
Status in rsyslog package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Fix Committed
Status in debhelper source package in Xenial:
  Won't Fix
Status in rsyslog source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Confirmed
Status in debhelper source package in Artful:
  Won't Fix
Status in rsyslog source package in Artful:
  Invalid
Status in systemd source package in Artful:
  Confirmed
Status in debhelper source package in Bionic:
  Won't Fix
Status in rsyslog source package in Bionic:
  Invalid
Status in systemd source package in Bionic:
  Fix Committed

Bug description:
  [Impact]

  /var/log's Permission is going back to 755
  after upgrading systemd
  if there are rsyslog's configuration on /var/lib/tmpfiles.d/

  Affected X, A, B, C

  This is because rsyslog's pkg has 00rsyslog.conf and copied it on 
/var/lib/tmpfiles.d/ when it is installing.
  after upgrading systemd, systemd only refresh it's own tmpfiles so disappear 
conf for 00rsyslog.conf ( it doesn't remove file itself )
  so, systemd-tmpfiles --create /var/lib/tmpfiles.d/00rsyslog.conf back 
permission to 775

  [Test Case]

  1. deploy 16.04 vm
  2. check ll /var (775)
  3. apt install --reinstall systemd
  4. check ll /var (755)

  [Regression Potential]
  This fix changes debhelper's override process by using absolute path to 
filename. so if the other pkgs using debhelper e.g systemd are there, It should 
be re-build with new debhelper after patching in theory, now only systemd is 
affected. but building is not affected. also, pkg like rsyslog which is using 
systemd's tmpfile system need to be changed to use 
/etc/tmpfiles.d/[SAME_FILENAME_IN_VAR_LIB_TMPFILES.D_FOR_OVERRIDING] instead of 
00rsyslog.conf.

  [Others]

  For this issue, need to fix below pkgs

  debhelper
  systemd ( rebuilding with new debhelper is needed )
  rsyslog ( 00rsyslog.conf to var.conf and location should be /etc/tmpfiles.d, 
to support override supported by debhelper )

  [Original description]

  Upgrading or reinstalling the systemd package when using rsyslogd
  results in bad permissions (0755 instead of 0775) being set on
  /var/log/. As a consequence of this, rsyslogd can no longer create new
  files within this directory, resulting in lost log messages.

  The default configuration of rsyslogd provided by Ubuntu runs the
  daemon as syslog:syslog and sets ownership of /var/log to syslog:adm
  with mode 0775.

  Systemd's default tmpfiles configuration sets /var/log to 0755 in
  /usr/lib/tmpfiles.d/var.conf, however this is overridden in
  /usr/lib/tmpfiles.d/00rsyslog.conf which is provided by package
  rsyslog.

  It looks as though an upgrade of the systemd package fails to take
  /usr/lib/tmpfiles.d/00rsyslog.conf into account, as demonstrated
  below. This results in /var/log receiving mode 0755 instead of the
  expected 0775:

  nick @ log2.be1.ams1:~ $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04
  Codename: xenial

  nick @ log2.be1.ams1:~ $ apt policy systemd
  systemd:
    Installed: 229-4ubuntu21.1
    Candidate: 229-4ubuntu21.1
    Version table:
   *** 229-4ubuntu21.1 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu4 500
  500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages

  nick @ log2.be1.ams1:~ $ apt policy rsyslog
  rsyslog:
    Installed: 8.16.0-1ubuntu3
    Candidate: 8.16.0-1ubuntu3
    Version 

[Touch-packages] [Bug 1780606] Re: NetworkManager not able to manage WWAN devices in 18.04 server

[Mathieu Trudel-Lapierre]

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

** Changed in: network-manager (Ubuntu)
   Importance: Undecided => High

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

Title:
  NetworkManager not able to manage WWAN devices in 18.04 server

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  Installed a 18.04 server image, and installed NetworkManager.

  NetworkManager comes with a "/usr/lib/NetworkManager/conf.d/10
  -globally-managed-devices.conf" file where it speciefies that all
  devices are by default unmanaged except for types "wifi" and "wwan".

  Now, the problem is that the filter should apply to "gsm" or "cdma"
  types, not "wwan".

  E.g.:
[keyfile]
unmanaged-devices=*,except:type:wifi,except:type:gsm,except:type:cdma

  Before the change:
  $ nmcli d
  DEVICETYPE  STATE  CONNECTION 
  wlan0 wifi   connected  Bumbu
  eth0  ethernet  unmanaged  -- 
  cdc-wdm0  gsm   unmanaged  -- 
  loloopback  unmanaged  -- 

  After the change:
  $ nmcli d
  DEVICETYPE  STATE  CONNECTION 
  wlan0 wifi   connected  Bumbu
  cdc-wdm0  gsm   connected  cell   
  eth0  ethernet  unmanaged  -- 
  loloopback  unmanaged  --

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

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

[Touch-packages] [Bug 1780818] Re: networkd crash with "Assertion 'h' failed at ../src/basic/hashmap.c:1223, function hashmap_put(). Aborting."

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  networkd crash with "Assertion 'h' failed at
  ../src/basic/hashmap.c:1223, function hashmap_put(). Aborting."

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

Bug description:
  When configuring a VRF in a .netdev unit, networkd fails with
  "Assertion 'h' failed at ../src/basic/hashmap.c:1223, function
  hashmap_put(). Aborting."

  This is a upstream bug tracked and fixed here:
  https://github.com/systemd/systemd/issues/9150

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul  9 17:58:55 2018
  InstallationDate: Installed on 2017-09-26 (286 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
  MachineType: HP HP ZBook Studio G3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=11aea77b-8d9f-4103-b638-d6e76fe96b4f ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2017-12-08 (213 days ago)
  dmi.bios.date: 03/29/2018
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.26
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.73
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.26:bd03/29/2018:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.73:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Curtis Gedak]

To help others with reverting to a prior version of libgl1-mesa
graphics drivers, I have provided the following download links.

libgl1-mesa .deb packages (14 files) - Search for "Downloadable files"
--

https://launchpad.net/ubuntu/xenial/amd64/libegl1-mesa/17.2.8-0ubuntu0~16.04.1

https://launchpad.net/ubuntu/xenial/amd64/libgbm1/17.2.8-0ubuntu0~16.04.1

https://launchpad.net/ubuntu/xenial/amd64/libgl1-mesa-dri/17.2.8-0ubuntu0~16.04.1
https://launchpad.net/ubuntu/xenial/i386/libgl1-mesa-dri/17.2.8-0ubuntu0~16.04.1

https://launchpad.net/ubuntu/xenial/amd64/libgl1-mesa-glx/17.2.8-0ubuntu0~16.04.1
https://launchpad.net/ubuntu/xenial/i386/libgl1-mesa-glx//17.2.8-0ubuntu0~16.04.1

https://launchpad.net/ubuntu/xenial/amd64/libglapi-mesa/17.2.8-0ubuntu0~16.04.1
https://launchpad.net/ubuntu/xenial/i386/libglapi-mesa/17.2.8-0ubuntu0~16.04.1

https://launchpad.net/ubuntu/xenial/amd64/libgles2-mesa/17.2.8-0ubuntu0~16.04.1

https://launchpad.net/ubuntu/xenial/amd64/libosmesa6/17.2.8-0ubuntu0~16.04.1
https://launchpad.net/ubuntu/xenial/i386/libosmesa6/17.2.8-0ubuntu0~16.04.1

https://launchpad.net/ubuntu/xenial/amd64/libwayland-
egl1-mesa/17.2.8-0ubuntu0~16.04.1

https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

https://launchpad.net/ubuntu/xenial/amd64/mesa-vdpau-
drivers/17.2.8-0ubuntu0~16.04.1


libllvm5 .deb packages (2 files) - Search for "Binary Package"
--

https://ubuntu.pkgs.org/16.04/ubuntu-updates-main-i386/libllvm5.0_5.0-3~16.04.1_i386.deb.html
https://ubuntu.pkgs.org/16.04/ubuntu-updates-main-amd64/libllvm5.0_5.0-3~16.04.1_amd64.deb.html

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

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  

[Touch-packages] [Bug 1779302] Re: should retry reading key from keyserver (in _recv_key)

[Scott Moser]

I saw this "in the wild" with /var/log/cloud-init.log showing:

2018-07-09 15:20:22,666 - util.py[DEBUG]: Running command 
['add-apt-repository', 'cloud-archive:ocata'] with allowed return codes [0] 
(shell=False, capture=True)
2018-07-09 15:20:24,907 - cc_apt_configure.py[ERROR]: add-apt-repository failed.
Traceback (most recent call last):
  File "/usr/lib/python3/dist-packages/cloudinit/config/cc_apt_configure.py", 
line 615, in add_apt_sources
util.subp(["add-apt-repository", source], target=target)
  File "/usr/lib/python3/dist-packages/cloudinit/util.py", line 1957, in subp
cmd=args)
cloudinit.util.ProcessExecutionError: Unexpected error while running command.
Command: ['add-apt-repository', 'cloud-archive:ocata']
Exit code: 1
Reason: -
Stdout:  Ubuntu Cloud Archive for OpenStack Ocata
 More info: https://wiki.ubuntu.com/ServerTeam/CloudArchive
Reading package lists...
Building dependency tree...
Reading state information...
Failed to add key.
Stderr: E: Unable to locate package ubuntu-cloud-keyring


** Description changed:

  Some recent events have made keyservers less reliable than they were
  previously:
-   https://bitbucket.org/skskeyserver/sks-keyserver/issues/57
-   https://bitbucket.org/skskeyserver/sks-keyserver/issues/60
+   https://bitbucket.org/skskeyserver/sks-keyserver/issues/57
+   https://bitbucket.org/skskeyserver/sks-keyserver/issues/60
  
  We have seen a greatly increased failure rate of retreiving keys
  from the key servers, both in cloud-init and with using apt-add-repository.
  
- 
  Here is an example failure:
-   
https://jenkins.ubuntu.com/server/view/cloud-init,%20curtin,%20streams/job/cloud-init-integration-nocloud-kvm-x/191/console
+   
https://jenkins.ubuntu.com/server/view/cloud-init,%20curtin,%20streams/job/cloud-init-integration-nocloud-kvm-x/191/console
  
  The stdout/stderr that is a result of running:
- $ add-apt-repository --yes ppa:cloud-init-deve/daily
+ $ add-apt-repository --yes ppa:cloud-init-devel/daily
  
  gpg: keyring `/tmp/tmp4s88x_yf/secring.gpg' created
  gpg: keyring `/tmp/tmp4s88x_yf/pubring.gpg' created
  gpg: requesting key E4D304DF from hkp server keyserver.ubuntu.com
  gpgkeys: key 1FF0D8535EF7E719E5C81B9C083D06FBE4D304DF can't be retrieved
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  gpg: keyserver communications error: keyserver helper general error
  gpg: keyserver communications error: unknown pubkey algorithm
  gpg: keyserver receive failed: unknown pubkey algorithm
  Failed to add key.
  
  Retries on reading the key make sense here to be more resilient to
  transient network or remote service resources.  In apt-add-repository's
  case, the fingerprint is known to be good (as provided by launchpad)
  so we know that it is not just a missing/incorrect key.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: software-properties-common 0.96.24.33
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jun 28 22:28:53 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (1072 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  should retry reading key from keyserver (in _recv_key)

Status in software-properties package in Ubuntu:
  Confirmed

Bug description:
  Some recent events have made keyservers less reliable than they were
  previously:
    https://bitbucket.org/skskeyserver/sks-keyserver/issues/57
    https://bitbucket.org/skskeyserver/sks-keyserver/issues/60

  We have seen a greatly increased failure rate of retreiving keys
  from the key servers, both in cloud-init and with using apt-add-repository.

  Here is an example failure:
    
https://jenkins.ubuntu.com/server/view/cloud-init,%20curtin,%20streams/job/cloud-init-integration-nocloud-kvm-x/191/console

  The stdout/stderr that is a result of running:
  $ add-apt-repository --yes ppa:cloud-init-devel/daily

  gpg: keyring `/tmp/tmp4s88x_yf/secring.gpg' created
  gpg: keyring `/tmp/tmp4s88x_yf/pubring.gpg' created
  gpg: requesting key E4D304DF from hkp server keyserver.ubuntu.com
  gpgkeys: key 1FF0D8535EF7E719E5C81B9C083D06FBE4D304DF can't be retrieved
  gpg: no 

[Touch-packages] [Bug 1749728] Re: Installing packages fails when launched via Firefox ("open with")

[William Geiger]

from my auth.log file:

before modifying the terminal flag in gdebi.desktop

Jul  8 15:20:46 johndoe-Latitude-D630 polkitd(authority=local): Operator
of unix-session:c2 FAILED to authenticate to gain authorization for
action com.ubuntu.pkexec.gdebi.gtk for unix-process:998:23188
[/lib/systemd/systemd --user] (owned by unix-user:johndoe)

Jul  8 15:20:46 johndoe-Latitude-D630 pkexec[4230]: johndoe: Error
executing command as another user: Request dismissed [USER=root]
[TTY=unknown] [CWD=/home/johndoe/tmp] [COMMAND=/usr/bin/gdebi-gtk --non-
interactive /home/johndoe/tmp/mozilla_johndoe0/ghex_3.18.3-3_amd64.deb]

after modifying the terminal flag in gdebi.desktop


Jul  8 15:35:26 johndoe-Latitude-D630 polkitd(authority=local): Operator of 
unix-session:c2 successfully authenticated as unix-user:johndoe to gain 
ONE-SHOT authorization for action com.ubuntu.pkexec.gdebi.gtk for 
unix-process:5533:234898 [/usr/lib/firefox/firefox] (owned by unix-user:johndoe)

Jul  8 15:35:26 johndoe-Latitude-D630 pkexec:
pam_unix(polkit-1:session): session opened for user root by (uid=1000)

Jul  8 15:35:26 johndoe-Latitude-D630 pkexec[5699]: johndoe: Executing
command [USER=root] [TTY=unknown] [CWD=/home/johndoe] [COMMAND=/usr/bin
/gdebi-gtk --non-interactive
/home/johndoe/tmp/mozilla_johndoe0/ghex_3.18.3-3_amd64.deb]

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

Title:
  Installing packages fails when launched via Firefox ("open with")

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When launched from Firefox with the "open with" function, GDebi is
  unable to complete installing the package. The GDebi window does open,
  but after selecting to "install" the package the window closes and the
  package is left uninstalled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdebi 0.9.5.7+nmu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 15 17:08:31 2018
  InstallationDate: Installed on 2018-02-15 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180215)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1780818] [NEW] networkd crash with "Assertion 'h' failed at ../src/basic/hashmap.c:1223, function hashmap_put(). Aborting."

[Andreas Schultz]

Public bug reported:

When configuring a VRF in a .netdev unit, networkd fails with "Assertion
'h' failed at ../src/basic/hashmap.c:1223, function hashmap_put().
Aborting."

This is a upstream bug tracked and fixed here:
https://github.com/systemd/systemd/issues/9150

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.2
ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
Uname: Linux 4.15.0-12-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon Jul  9 17:58:55 2018
InstallationDate: Installed on 2017-09-26 (286 days ago)
InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
MachineType: HP HP ZBook Studio G3
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=11aea77b-8d9f-4103-b638-d6e76fe96b4f ro
SourcePackage: systemd
UpgradeStatus: Upgraded to bionic on 2017-12-08 (213 days ago)
dmi.bios.date: 03/29/2018
dmi.bios.vendor: HP
dmi.bios.version: N82 Ver. 01.26
dmi.board.name: 80D4
dmi.board.vendor: HP
dmi.board.version: KBC Version 11.73
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.26:bd03/29/2018:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.73:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP ZBook Studio G3
dmi.sys.vendor: HP

** Affects: systemd
 Importance: Unknown
 Status: Unknown

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


** Tags: amd64 apport-bug bionic package-from-proposed third-party-packages

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

** Also affects: systemd via
   https://github.com/systemd/systemd/issues/9150
   Importance: Unknown
   Status: Unknown

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

Title:
  networkd crash with "Assertion 'h' failed at
  ../src/basic/hashmap.c:1223, function hashmap_put(). Aborting."

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

Bug description:
  When configuring a VRF in a .netdev unit, networkd fails with
  "Assertion 'h' failed at ../src/basic/hashmap.c:1223, function
  hashmap_put(). Aborting."

  This is a upstream bug tracked and fixed here:
  https://github.com/systemd/systemd/issues/9150

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.2
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon Jul  9 17:58:55 2018
  InstallationDate: Installed on 2017-09-26 (286 days ago)
  InstallationMedia: Ubuntu-Server 17.10 "Artful Aardvark" - Alpha amd64 
(20170924)
  MachineType: HP HP ZBook Studio G3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-12-generic.efi.signed 
root=UUID=11aea77b-8d9f-4103-b638-d6e76fe96b4f ro
  SourcePackage: systemd
  UpgradeStatus: Upgraded to bionic on 2017-12-08 (213 days ago)
  dmi.bios.date: 03/29/2018
  dmi.bios.vendor: HP
  dmi.bios.version: N82 Ver. 01.26
  dmi.board.name: 80D4
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 11.73
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN82Ver.01.26:bd03/29/2018:svnHP:pnHPZBookStudioG3:pvr:rvnHP:rn80D4:rvrKBCVersion11.73:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP ZBook Studio G3
  dmi.sys.vendor: HP

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

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

[Touch-packages] [Bug 1749728] Re: Installing packages fails when launched via Firefox ("open with")

[William Geiger]

after some sleep I have a couple of additional comments:

the /usr/share/application-registry/gdebi.applications file the mime
list should be comma-delimited or at least that is what they did in the
liboffice.application file (it is the only other file in the directory).

while the steps in my previous post got gdebi to work from Thunar &
Opera it DID NOT fix Firefox.

For firefox the only thing I have found to work was to set
Terminal=true in the gdebi.desktop file. If you have multiple copies of
this file make sure you change the one in:

/usr/share/applications/gdebi.desktop:

I have one at:

/home/johndoe/.local/share/applications/gdebi.desktop

it was created by trying to edit via the Whisker Menu

I have another one at:

/home/johndoe/.local/share/applications/gdebi.desktop

it was created by trying to edit via MenuLibre 

if anyone whishes to contact me they can do so @ whgi...@yahoo.com

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

Title:
  Installing packages fails when launched via Firefox ("open with")

Status in gdebi package in Ubuntu:
  Confirmed

Bug description:
  When launched from Firefox with the "open with" function, GDebi is
  unable to complete installing the package. The GDebi window does open,
  but after selecting to "install" the package the window closes and the
  package is left uninstalled.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdebi 0.9.5.7+nmu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: MATE
  Date: Thu Feb 15 17:08:31 2018
  InstallationDate: Installed on 2018-02-15 (0 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180215)
  PackageArchitecture: all
  SourcePackage: gdebi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Curtis Gedak]

Thanks @Pascal for indicating that the drop down menu lists do appear by
selecting XRender as the rendering engine.

Unfortunately XRender has other issues.  The reason I originally changed
away from using the default settings is because then I had issues with
screen tearing [1] and an inability to login due to SDDM login screen
hangs [2].

[1] https://askubuntu.com/questions/764302/screen-tearing-on-
kubuntu-16-04-with-intel-drivers

[2] https://askubuntu.com/questions/765364/kubuntu-16-04-sddm-login-
screen-hangs/

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

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  '17.2.8-0ubuntu0~16.04.1' version.

  For example:

  
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

  I also discovered that some of these depended on
  libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:

libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb


  WORKAROUND (ROLLBACK TO PRIOR VERSION)

  Install older versions with:

  sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \

[Touch-packages] [Bug 1780807] Re: Please provide ED25519 support in 18.04 OpenSSL

[Michael Steffens]

** Description changed:

  Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking
  support for the ED25519 signature algorithm.
  
  As ED25519 is quickly gaining traction as most demanded and preferred
  elliptic curve algorithm, it would be a substantial issue not to have
- any support for it in the remaining lifetime of Ubuntu LTS releases most
+ any support for it in the remaining lifetime of Ubuntu LTS released most
  recently.
  
  OpenSSL is introducing ED25519 with their 1.1.1 release, which is
  currently in beta (openssl-1.1.1-pre8 as of today). I suggest to upgrade
  Bionic libss1.1 to OpenSSL 1.1.1, once finally released by OpenSSL.

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

Title:
  Please provide ED25519 support in 18.04 OpenSSL

Status in openssl package in Ubuntu:
  New

Bug description:
  Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking
  support for the ED25519 signature algorithm.

  As ED25519 is quickly gaining traction as most demanded and preferred
  elliptic curve algorithm, it would be a substantial issue not to have
  any support for it in the remaining lifetime of Ubuntu LTS released
  most recently.

  OpenSSL is introducing ED25519 with their 1.1.1 release, which is
  currently in beta (openssl-1.1.1-pre8 as of today). I suggest to
  upgrade Bionic libss1.1 to OpenSSL 1.1.1, once finally released by
  OpenSSL.

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

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

[Touch-packages] [Bug 1702793] Re: Full backport SRU for unattended-upgrades

[Eric Desrochers]

Any update/progress on the full backport of 'uu' ?

** Tags added: ua

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

Title:
  Full backport SRU for unattended-upgrades

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  [Impact]

  * I would like to propose a one-off full backport of unattended-upgrades
  1.2ubuntu1 to Bionic, Artful, Xenial and possibly Trusty releases because 
selectively backporting fixes for crashes and for issues that made u-u 
unreliable would be more risky thanks to the huge number of fixes and the
  inter-dependencies between them.

  [Test Case]

  * Since this backport involves fixing several bugs and this bug itself covers 
the full backport I suggest that this bug should be considered verified when 
the following list of bugs are verified:
   - TODO add most important bugs
  and the following tests are passing:
   - TODO add tests not covered by bugs above

  [Regression Potential]

  * Due to this update covering the full backport unattended-upgrades can 
regress in any imaginable way including failing to install, upgrade, run, or 
removing essential packages from the system. Those are unlikely.
  * There are open bugs about u-u being slower than in the past, thus this may 
be a likely regression but IMO the pending speed optimizations should not be 
blocking the backport because the reliability issues are more important to fix 
and speed optimizations can be cherry-picked later.
  * LP: #1773033 is a regression causing u-u to not install upgrades on 
shutdown when the system was started on battery. I have a WIP fix and can add 
the fix to the SRU if needed.

  [Other Info]

  I asked for an exception for the package in following the SRU process:
  https://lists.ubuntu.com/archives/ubuntu-release/2018-May/004479.html

  I'm preparing the backport in ppa:rbalint/scratch and also run
  autopkgtests on it in addition to testing it manually in VMs.

  [Original Bug Text]

  Changes to support day-of-week patching and logging to syslog were
  added to upstream (https://github.com/mvo5/unattended-upgrades) over a
  year ago. These changes are not present in the latest Xenial nor
  Trusty packages (0.90 and 0.82.1) - requesting that these changes be
  pulled from upstream.

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

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

[Touch-packages] [Bug 1780548] Re: SSH server won't start, exit code 255

[Joshua Powers]

Per the comment above, please take a look at your sshd_cofig file and
verify it is valid. I am marking this incomplete until then.

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

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

Title:
  SSH server won't start, exit code 255

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  I keep trying to set up external SSH access using openssh server on my
  18.04 system and it throws back this error

  sudo service ssh status
  ● ssh.service - OpenBSD Secure Shell server
 Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: 
enabled)
 Active: failed (Result: exit-code) since Sat 2018-07-07 09:33:19 CDT; 
12min ago
Process: 3243 ExecStartPre=/usr/sbin/sshd -t (code=exited, status=255)

  Jul 07 09:33:19 warehouse systemd[1]: ssh.service: Service hold-off time 
over, scheduling restart.
  Jul 07 09:33:19 warehouse systemd[1]: ssh.service: Scheduled restart job, 
restart counter is at 5.
  Jul 07 09:33:19 warehouse systemd[1]: Stopped OpenBSD Secure Shell server.
  Jul 07 09:33:19 warehouse systemd[1]: ssh.service: Start request repeated too 
quickly.
  Jul 07 09:33:19 warehouse systemd[1]: ssh.service: Failed with result 
'exit-code'.
  Jul 07 09:33:19 warehouse systemd[1]: Failed to start OpenBSD Secure Shell 
server.

  I was in the process of uninstalling the openssh-server and ssh
  packages and was prompted to start a bug report.  If it's in error,
  just let me know.  My ssh config file is all default except for
  passwordauthentication = yes.  I've toggled that to default as well,
  and still get the same error.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: openssh-server 1:7.6p1-4
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_23_25_generic_40
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   openssh-server:amd64: Install
   ssh:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Sat Jul  7 09:48:11 2018
  ErrorMessage: installed openssh-server package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2018-07-07 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.2
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 1: Bad configuration option: \342\200\213\342\200\213
   /etc/ssh/sshd_config: terminating, 1 bad configuration options
  SourcePackage: openssh
  Title: package openssh-server 1:7.6p1-4 failed to install/upgrade: installed 
openssh-server package post-installation script subprocess 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/openssh/+bug/1780548/+subscriptions

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

[Touch-packages] [Bug 1779956] Re: GDPR Compliance

[Bug Watch Updater]

** Changed in: systemd
   Status: Unknown => Fix Released

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

Title:
  GDPR Compliance

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

Bug description:
  The systemd project is experimenting and working with various ideas
  that have privacy ramifications. This includes the work in systemd-
  resolved and systemd-timesyncd that creates a possibility for
  disclosure of personal information to Google or similar providers
  through default code paths. The data remitted such as client IP
  addresses, subdomains containing usernames or unique IDs, banking
  domains and similar data may be considered personal data under the
  GDPR and other EU law.

  These components are currently in a state where it is legally dubious
  whether they comply or can be made to comply. In particular, systemd's
  default configuration unless otherwise configured and compiled
  discloses personal information to Google without consent or methods to
  withdraw consent and without plain-language privacy policy. This
  design overall is considered flawed by the GDPR.

  I had reported this concern upstream as it impacts all distributions,
  but the systemd project has shown disinterest in working on "privacy
  by design" and making their work compliant. This lack of concern and
  future work by the systemd project may interfere with distributions'
  efforts to make their distributions compliant.

  As such, this work upstream and future work by upstream may interfere
  with any compliance efforts by Ubuntu to ensure compliance with the
  GDPR as systemd cannot be relied upon as "compliant out of the box"
  software.

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

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

[Touch-packages] [Bug 1780807] [NEW] Please provide ED25519 support in 18.04 OpenSSL

[Michael Steffens]

Public bug reported:

Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking
support for the ED25519 signature algorithm.

As ED25519 is quickly gaining traction as most demanded and preferred
elliptic curve algorithm, it would be a substantial issue not to have
any support for it in the remaining lifetime of Ubuntu LTS releases most
recently.

OpenSSL is introducing ED25519 with their 1.1.1 release, which is
currently in beta (openssl-1.1.1-pre8 as of today). I suggest to upgrade
Bionic libss1.1 to OpenSSL 1.1.1, once finally released by OpenSSL.

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

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

Title:
  Please provide ED25519 support in 18.04 OpenSSL

Status in openssl package in Ubuntu:
  New

Bug description:
  Current libss1.1 version in Bionic is 1.1.0g-2ubuntu4.1 and lacking
  support for the ED25519 signature algorithm.

  As ED25519 is quickly gaining traction as most demanded and preferred
  elliptic curve algorithm, it would be a substantial issue not to have
  any support for it in the remaining lifetime of Ubuntu LTS releases
  most recently.

  OpenSSL is introducing ED25519 with their 1.1.1 release, which is
  currently in beta (openssl-1.1.1-pre8 as of today). I suggest to
  upgrade Bionic libss1.1 to OpenSSL 1.1.1, once finally released by
  OpenSSL.

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

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

[Nicorac]

The behavior is not reproducible, maybe a race condition?
I'm actually not getting IP addres for static interface too :-(

I agree, let's continue there:
https://bugs.launchpad.net/netplan/+bug/1768827

-- 
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:
  Confirmed
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 Committed
Status in netplan.io source package in Bionic:
  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

  - 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 

[Touch-packages] [Bug 1774617] Re: Filter out snaps from GNOME Software

[Robert Ancell]

I've reassigned it to software-properties - that is where those settings
live.

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

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

Title:
  Filter out snaps from GNOME Software

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  An option should be provided in Software & Updates to filter out snaps
  from GNOME Software. Perhaps this should also affect the command-line
  (just as disabling restricted and multiverse would affect the command-
  line). Perhaps a dialogue box should be created when turning off snaps
  and the dialogue should ask whether to remove snapd entirely (first
  removing the snaps) or to set the refresh timer to monthly ( which is
  as close to turning it off as possible, timer CLI is here:
  https://snapdocs.labix.org/configuration-options/87 ), or to remove
  all snaps, or just to remove them from GNOME Software (for snaps, this
  could just hide apps that have their source listed as 'Snap Store').

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: software-properties-gtk 0.96.24.32.3
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: communitheme:ubuntu:GNOME
  Date: Fri Jun  1 10:33:24 2018
  InstallationDate: Installed on 2017-08-03 (301 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to bionic on 2018-04-22 (40 days ago)

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

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

[Touch-packages] [Bug 1780798] Re: package libdrm-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64 2.

[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 libdrm in Ubuntu.
https://bugs.launchpad.net/bugs/1780798

Title:
  package libdrm-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in
  package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0

Status in libdrm package in Ubuntu:
  New

Bug description:
  I clicked on software and problem occurred when it did not load properly.
  can attempt to load again.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libdrm-common (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   [  OK  ] Started LSB: Speech Dispatcher.
   [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
   [  OK  ] Started LSB: Record successful boot for GRUB.
  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 Jul  9 09:35:45 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DuplicateSignature:
   package:libdrm-common:(not installed)
   Unpacking libdrm-common (2.4.91-2~16.04.1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack):
trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in 
package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0
  ErrorMessage: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is 
also in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01d2]
 Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01d2]
  InstallationDate: Installed on 2017-09-29 (282 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Dell DM051
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=abe400d9-984a-4f2a-afaa-0c6aa3156fbf ro quiet splash nomodeset 
vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  Renderer: Software
  SourcePackage: libdrm
  Title: package libdrm-common (not installed) failed to install/upgrade: 
trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package 
libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/08/2007
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0RD203
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/08/2007:svnDellInc.:pnDellDM051:pvr:rvnDellInc.:rn0RD203:rvr:cvnDellInc.:ct6:cvr:
  dmi.product.name: Dell DM051
  dmi.sys.vendor: Dell Inc.
  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 1:17.2.1-0~x~padoka0
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.1-0~x~padoka0
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Mon Jul  9 09:02:56 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard Hub KEYBOARD, id 8
   inputDell Dell USB Keyboard Hub KEYBOARD, id 9
   inputLogitech Optical USB Mouse MOUSE, id 10
  xserver.errors:
   open /dev/dri/card0: No such file or directory
   open /dev/dri/card0: No such file or directory
   Screen 0 deleted because of no matching config section.
   AIGLX: reverting to software rendering
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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

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

[Touch-packages] [Bug 1780798] [NEW] package libdrm-common (not installed) failed to install/upgrade: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package libdrm-amdgpu1:amd64

[Ron Kieper]

Public bug reported:

I clicked on software and problem occurred when it did not load properly.
can attempt to load again.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libdrm-common (not installed)
ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
.tmp.unity_support_test.1:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
BootLog:
 [  OK  ] Started LSB: Speech Dispatcher.
 [  OK  ] Started LSB: Set the CPU Frequency Scaling governor to 
"ondemand".
 [  OK  ] Started LSB: Record successful boot for GRUB.
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 Jul  9 09:35:45 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DuplicateSignature:
 package:libdrm-common:(not installed)
 Unpacking libdrm-common (2.4.91-2~16.04.1) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libdrm-common_2.4.91-2~16.04.1_all.deb (--unpack):
  trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package 
libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0
ErrorMessage: trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also 
in package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01d2]
   Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01d2]
InstallationDate: Installed on 2017-09-29 (282 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Dell Inc. Dell DM051
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=abe400d9-984a-4f2a-afaa-0c6aa3156fbf ro quiet splash nomodeset 
vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
Renderer: Software
SourcePackage: libdrm
Title: package libdrm-common (not installed) failed to install/upgrade: trying 
to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in package 
libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/08/2007
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0RD203
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA07:bd01/08/2007:svnDellInc.:pnDellDM051:pvr:rvnDellInc.:rn0RD203:rvr:cvnDellInc.:ct6:cvr:
dmi.product.name: Dell DM051
dmi.sys.vendor: Dell Inc.
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 1:17.2.1-0~x~padoka0
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 1:17.2.1-0~x~padoka0
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
xserver.bootTime: Mon Jul  9 09:02:56 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDell Dell USB Keyboard Hub KEYBOARD, id 8
 inputDell Dell USB Keyboard Hub KEYBOARD, id 9
 inputLogitech Optical USB Mouse MOUSE, id 10
xserver.errors:
 open /dev/dri/card0: No such file or directory
 open /dev/dri/card0: No such file or directory
 Screen 0 deleted because of no matching config section.
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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


** Tags: amd64 apport-package compiz-0.9 package-conflict ubuntu xenial

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

Title:
  package libdrm-common (not installed) failed to install/upgrade:
  trying to overwrite '/usr/share/libdrm/amdgpu.ids', which is also in
  package libdrm-amdgpu1:amd64 2.4.83-3~x~padoka0

Status in libdrm package in Ubuntu:
  New

Bug description:
  I clicked on software and problem occurred when it did not load properly.
  can attempt to load again.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libdrm-common (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-24.26~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  .tmp.unity_support_test.1:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   [ 

[Touch-packages] [Bug 1774617] [NEW] Filter out snaps from GNOME Software

[Launchpad Bug Tracker]

You have been subscribed to a public bug:

An option should be provided in Software & Updates to filter out snaps
from GNOME Software. Perhaps this should also affect the command-line
(just as disabling restricted and multiverse would affect the command-
line). Perhaps a dialogue box should be created when turning off snaps
and the dialogue should ask whether to remove snapd entirely (first
removing the snaps) or to set the refresh timer to monthly ( which is as
close to turning it off as possible, timer CLI is here:
https://snapdocs.labix.org/configuration-options/87 ), or to remove all
snaps, or just to remove them from GNOME Software (for snaps, this could
just hide apps that have their source listed as 'Snap Store').

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: software-properties-gtk 0.96.24.32.3
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
ApportVersion: 2.20.9-0ubuntu7
Architecture: amd64
CurrentDesktop: communitheme:ubuntu:GNOME
Date: Fri Jun  1 10:33:24 2018
InstallationDate: Installed on 2017-08-03 (301 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to bionic on 2018-04-22 (40 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Wishlist
 Status: Triaged


** Tags: amd64 apport-bug bionic wayland-session
-- 
Filter out snaps from GNOME Software
https://bugs.launchpad.net/bugs/1774617
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to software-properties in Ubuntu.

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

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

[Bin Li]

Talked with Jonas Ådahl, he suggest we try below patch, I will try it
when back office.

https://gitlab.gnome.org/GNOME/mutter/merge_requests/155

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

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

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

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

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

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

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

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

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

[Touch-packages] [Bug 1780791] [NEW] /lib/systemd/systemd-journald:6:journal_file_move_to_object:journal_file_find_field_object_with_hash:journal_file_append_field:journal_file_append_data:journal_fil

[errors.ubuntu.com bug bridge]

Public bug reported:

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

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


** Tags: artful bionic vivid wily xenial yakkety zesty

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

Title:
  /lib/systemd/systemd-
  
journald:6:journal_file_move_to_object:journal_file_find_field_object_with_hash:journal_file_append_field:journal_file_append_data:journal_file_append_entry

Status in systemd package in Ubuntu:
  New

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

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

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

I'd be a bit surprised if there really was a regression due to the
change, we're more likely seeing something going down due to the DHCP
server being slow to respond, possibly because it already responded
before?

What does the 'networkctl' command show immediately after boot?

Let's continue debugging this on your own bug (1768827).

-- 
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:
  Confirmed
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 Committed
Status in netplan.io source package in Bionic:
  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

  - 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
     

[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Pascal Peter]

Hello,

I also confirm this bug on 2 computers with Kubuntu 16.04.

By selecting XRender as the rendering engine everything works.

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

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  '17.2.8-0ubuntu0~16.04.1' version.

  For example:

  
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

  I also discovered that some of these depended on
  libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:

libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb


  WORKAROUND (ROLLBACK TO PRIOR VERSION)

  Install older versions with:

  sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb

  
  After rebooting, all the issues disappeared.

  For example I was once again able to left-click on the Firefox **three
  line/bar** menu and view the drop down list menu.  Also the KDE bottom
  menu bar retured to the normal "breeze" light grey colour.

To manage notifications about this bug go to:

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

[Nicorac]

Sorry for the confusion.

Current version (0.36.2):
- both devices not renamed after boot (have original enp.. names)
- static and dynamic IPs correctly assigned

Proposed version (0.36.3):
- both devices correctly renamed after boot:
  :91 gets renamed eth_static
  :f5 gets renamed to eth_dhcp
- only eth_static got the configured static address, eth_dhcp not configured 
(need to call "ifconfig -a" to show it)

No VB Additions, just plain Ubuntu Server 18.04 install followed by "apt
update && apt dist-upgrade".

-- 
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:
  Confirmed
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 Committed
Status in netplan.io source package in Bionic:
  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

  - 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
  

[Touch-packages] [Bug 1780767] [NEW] Some tests are flaky due to timeout

[Didier Roche]

Public bug reported:

The autopkgtests are sometimes passing, sometimes stuck for more than 2h:
http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64.
It's blocking randomly on different tests.

All tests that are stucked, implements closing a request via a timeout
(and then, executing "run"). The bet is that the timeout is short enough
(1s) so that, when autopkgtests infra is busy, time to execute the bash
subcommand is taking more than a second, and so "dismissing" is ran
before execution happens and the whole testsuite hangs.

There are few instances of setting this timeout function:
$ grep eout_add_sec test/*
test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c)
test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c)

Short term solution could be to increase the timeout. Long term would be
to eliminate this potential race implementing cancelling differently.

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

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

Title:
  Some tests are flaky due to timeout

Status in apport package in Ubuntu:
  New

Bug description:
  The autopkgtests are sometimes passing, sometimes stuck for more than 2h:
  http://autopkgtest.ubuntu.com/packages/apport/cosmic/amd64.
  It's blocking randomly on different tests.

  All tests that are stucked, implements closing a request via a timeout
  (and then, executing "run"). The bet is that the timeout is short
  enough (1s) so that, when autopkgtests infra is busy, time to execute
  the bash subcommand is taking more than a second, and so "dismissing"
  is ran before execution happens and the whole testsuite hangs.

  There are few instances of setting this timeout function:
  $ grep eout_add_sec test/*
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, cont)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c)
  test/test_ui_gtk.py:GLib.timeout_add_seconds(1, c)

  Short term solution could be to increase the timeout. Long term would
  be to eliminate this potential race implementing cancelling
  differently.

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

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

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

[Daniel van Vugt]

Cheers

** Summary changed:

- 18.04 login screen is skewed/distorted (incorrect stride)
+ 18.04 login screen is skewed/distorted (incorrect stride) when using 
hibmc_drm graphics

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

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

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

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

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

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

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

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

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

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

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

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

[Bin Li]

Daniel,

 Thanks for your help, I've report a new one.

https://gitlab.gnome.org/GNOME/mutter/issues/219

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride)

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

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

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

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

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

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

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

[Touch-packages] [Bug 1776782] Re: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed lvm2 package post-installation script subprocess returned error exit status 1

[Launchpad Bug Tracker]

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

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

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

Title:
  package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed
  lvm2 package post-installation script subprocess returned error exit
  status 1

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  Error received when installing qemu/Kvm:
  installed lvm2 package post-installation script subprocess returned error 
exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: lvm2 2.02.176-4.1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Thu Jun 14 01:11:46 2018
  ErrorMessage: installed lvm2 package post-installation script subprocess 
returned error exit status 1
  InstallationDate: Installed on 2018-06-07 (6 days ago)
  InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: lvm2
  Title: package lvm2 2.02.176-4.1ubuntu3 failed to install/upgrade: installed 
lvm2 package post-installation script subprocess 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/lvm2/+bug/1776782/+subscriptions

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

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

[Daniel van Vugt]

Thanks. Please report the bug to upstream here:

  https://gitlab.gnome.org/GNOME/mutter/issues

also mentioning it is:

05:00.0 VGA compatible controller: Huawei Technologies Co., Ltd. Hi1710 [iBMC 
Intelligent Management system chip w/VGA support] (rev 01)
Kernel driver in use: hibmc-drm
Kernel modules: hibmc_drm

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride)

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

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

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

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

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

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

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

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

[Bin Li]

Here is the log from Huawei arm server. Thanks!

** Attachment added: "lspci-k.log"
   
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1780076/+attachment/5161325/+files/lspci-k.log

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

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride)

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

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

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

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

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

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

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

[Touch-packages] [Bug 1780359] Re: circular dependency between libcups2-dev and libcupsimage2-dev (2.2.7-1ubuntu2) on bionic

[Till Kamppeter]

Didier, did you change anythin in the dependencies of the CUPS package
recently?

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

Title:
  circular dependency between libcups2-dev and libcupsimage2-dev
  (2.2.7-1ubuntu2) on bionic

Status in cups package in Ubuntu:
  New

Bug description:
  Circular dependency between libcups2-dev and libcupsimage2-dev
  (2.2.7-1ubuntu2) on ubuntu-18.04 (bionic).

  root@qvb58jams52fr9r:~# apt-cache depends libcups2-dev
  libcups2-dev
Depends: libcupsimage2-dev
Depends: libcups2
Depends: dpkg-dev
  root@qvb58jams52fr9r:~# apt-cache depends libcupsimage2-dev
  libcupsimage2-dev
Depends: libcupsimage2
Depends: libcups2-dev
Depends: libpng-dev
Depends: libtiff-dev
Depends: libjpeg-dev
  libjpeg-turbo8-dev
Depends: zlib1g-dev
Recommends: libcupsfilters-dev

  One of my pipelines failed to install libcupsimage2-dev:
  15:36:57 Some packages could not be installed. This may mean that you have
  15:36:57 requested an impossible situation or if you are using the unstable
  15:36:57 distribution that some required packages have not yet been created
  15:36:57 or been moved out of Incoming.
  15:36:57 The following information may help to resolve the situation:
  15:36:57 
  15:36:57 The following packages have unmet dependencies:
  15:36:57  libcups2-dev : Depends: libcupsimage2-dev (= 2.2.7-1ubuntu2) but it 
is not going to be installed
  15:36:57 W: --force-yes is deprecated, use one of the options starting with 
--allow instead.
  15:36:57 E: Unable to correct problems, you have held broken packages.

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

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

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

[Bin Li]

Daniel,

 Thanks a lot! I will ask someone to help it.

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

Title:
  18.04 login screen is skewed/distorted (incorrect stride)

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

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

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

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

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

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

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

[Touch-packages] [Bug 1772607] Re: Mesa 18.0.5 stable release

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 18.0.5-0ubuntu0~18.04.1

---
mesa (18.0.5-0ubuntu0~18.04.1) bionic; urgency=medium

  * New upstream release. (LP: #1772607)
- fix wayland apps blocking on eglswapBuffers (LP: #1774170)

 -- Timo Aaltonen   Tue, 22 May 2018 11:31:23 +0300

** Changed in: mesa (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Mesa 18.0.5 stable release

Status in libglvnd package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libglvnd source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Ubuntu 18.04 shipped with mesa 18.0.0~rc5, and deserves to get the last point 
release of the series.

  [Test Case]
  Check on intel/radeon hw that things still work fine.

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems.

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

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

[Touch-packages] [Bug 1772607] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for libglvnd has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Mesa 18.0.5 stable release

Status in libglvnd package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libglvnd source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Ubuntu 18.04 shipped with mesa 18.0.0~rc5, and deserves to get the last point 
release of the series.

  [Test Case]
  Check on intel/radeon hw that things still work fine.

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems.

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

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

[Touch-packages] [Bug 1772607] Re: Mesa 18.0.5 stable release

[Launchpad Bug Tracker]

This bug was fixed in the package libglvnd - 1.0.0-2ubuntu2.1

---
libglvnd (1.0.0-2ubuntu2.1) bionic; urgency=medium

  * control: Drop the alternate depends on lib{egl,glx}-vendor, the
default provided by mesa should always be installed. (LP: #1770913)
  * control: Bump Breaks/Replaces on old mesa egl/glx packages to verify
upgrades with xenial backports work. (LP: #1772607)

 -- Timo Aaltonen   Tue, 05 Jun 2018 17:16:05 +0300

** Changed in: libglvnd (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Mesa 18.0.5 stable release

Status in libglvnd package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in libglvnd source package in Bionic:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  Ubuntu 18.04 shipped with mesa 18.0.0~rc5, and deserves to get the last point 
release of the series.

  [Test Case]
  Check on intel/radeon hw that things still work fine.

  [Regression potential]
  Mesa stable releases are tested by vendor CI systems.

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

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

[Touch-packages] [Bug 1774170] Re: Applications block on eglswapBuffers due to buggy mesa version

[Launchpad Bug Tracker]

This bug was fixed in the package mesa - 18.0.5-0ubuntu0~18.04.1

---
mesa (18.0.5-0ubuntu0~18.04.1) bionic; urgency=medium

  * New upstream release. (LP: #1772607)
- fix wayland apps blocking on eglswapBuffers (LP: #1774170)

 -- Timo Aaltonen   Tue, 22 May 2018 11:31:23 +0300

** Changed in: mesa (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  Applications block on eglswapBuffers due to buggy mesa version

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  The mesa version that is available after installing packages has a bug that 
leads to wayland applications blocking on eglSwapBuffers if egl swap interval 
is set to Zero.

  Ubuntu version: 18.04 LTS
  Currently available mesa version for installation: 18.0.0~rc5

  Versions where the bug is fixed:
  17.3.8, 18.0.2, 18.1.0, or later

  [Test case]
  More details about the bug, how to reproduce it and the right mesa versions 
to use in here:
  https://bugs.freedesktop.org/show_bug.cgi?id=106719

  Would be so good if it is possible to provide one of the mesa versions
  where the problem does not exist as a package for installation.

  Thanks

  Output from running:
  apt-cache policy libegl-mesa0

  libegl-mesa0:
    Installed: 18.0.0~rc5-1ubuntu1
    Candidate: 18.0.0~rc5-1ubuntu1
    Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  [Regression potential]
  none known, and we're SRUing 18.0.5 which is the last one of the series so 
shouldn't have regressions caused by earlier bugfixes..

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

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

[Touch-packages] [Bug 1774170] Update Released

[Łukasz Zemczak]

The verification of the Stable Release Update for mesa has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  Applications block on eglswapBuffers due to buggy mesa version

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  The mesa version that is available after installing packages has a bug that 
leads to wayland applications blocking on eglSwapBuffers if egl swap interval 
is set to Zero.

  Ubuntu version: 18.04 LTS
  Currently available mesa version for installation: 18.0.0~rc5

  Versions where the bug is fixed:
  17.3.8, 18.0.2, 18.1.0, or later

  [Test case]
  More details about the bug, how to reproduce it and the right mesa versions 
to use in here:
  https://bugs.freedesktop.org/show_bug.cgi?id=106719

  Would be so good if it is possible to provide one of the mesa versions
  where the problem does not exist as a package for installation.

  Thanks

  Output from running:
  apt-cache policy libegl-mesa0

  libegl-mesa0:
    Installed: 18.0.0~rc5-1ubuntu1
    Candidate: 18.0.0~rc5-1ubuntu1
    Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  [Regression potential]
  none known, and we're SRUing 18.0.5 which is the last one of the series so 
shouldn't have regressions caused by earlier bugfixes..

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

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

[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal

[Łukasz Zemczak]

Thanks for all the testing Brian! As with any python3 upload, this also
seems to come with quite a lot reported autopkgtest regressions. Could
you take a look at those and see if they're related to the changes or
not (both bionic and artful)?

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

Title:
  python3-minimal should predepend on versioned version of
  python3-minimal

Status in python3-defaults package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in python3-defaults source package in Artful:
  Fix Committed
Status in ubuntu-release-upgrader source package in Artful:
  Invalid
Status in python3-defaults source package in Bionic:
  Fix Committed
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid
Status in python3-defaults package in Debian:
  Fix Released

Bug description:
  [Impact]
  Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 
LTS can fail if python3-minimial is unpacked before python3.x-minimal so a 
system won't have a usable python3 symlink. Then upgrades will fail because 
py3clean, used in prerm scripts of python3 packages, will fail with "not found".

  [Test Case]
  1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for 
Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt
  2) dpkg --unpack python3-minimal...
  3) dpkg --unpack python3-apt...

  Observe the following Traceback:

  Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ...
  /var/lib/dpkg/info/python3-apt.prerm: 6: 
/var/lib/dpkg/info/python3-apt.prerm: py3clean: not found
  dpkg: warning: subprocess old pre-removal script returned error exit status 
127
  dpkg: trying script from the new package instead ...
  /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found
  dpkg: error processing archive 
/home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack):
   subprocess new pre-removal script returned error exit status 127
  /var/lib/dpkg/info/python3-apt.postinst: 6: 
/var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 127

  With the deb python3-minimal from -proposed you won't be able to
  unpack python3-minimal without first installing python3.6-minimal.
  While that may qualify as verification it'd still be good to test
  unpacking python3-apt. To do that you'll need to install
  python3.6-minimal from the target release by editing you
  /etc/apt/sources.list to the new release, running 'apt-get update',
  and then 'apt-get install python3.6-minimal'. After that's all done
  you can try steps 2 and 3 from the test case again and you should not
  receive a Traceback.

  [Regression Potential]
  Its possible this could cause or reveal different upgrade failures so some 
extensive (desktop, cloud, server) upgrade testing should be done.

  
  [A Portion of the Original Description (it was a huge blob of failure)]
  do-release-upgrade -d  on my 16.04 LTS unity laptop lead to an install 
failure:

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

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

[Touch-packages] [Bug 1780449] Re: [regression] i965 graphics corruption after recent xenial updates

[Daniel van Vugt]

In that case please start by trying older versions of mesa to see if
that caused the problem.

I would hazard a guess that downgrading to the previous version:
 https://launchpad.net/ubuntu/+source/mesa/17.2.8-0ubuntu0~16.04.1
might fix the problem...?

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

Title:
  [regression] i965 graphics corruption after recent xenial updates

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 16.04.4 LTS. Since the original release two years
  ago it was working absolutely fine on a variety of machines. Now, on
  this particular machine I have two monitors:

  1. Dell 24" 1200x1920 (portrait) connected via D-SUB/VGA port
  2. AOC 28" 1920x1080 (landscape) connected via DVI-D

  I have made an upgrade today and the following packages were upgraded:

  https://paste.ubuntu.com/p/5cf8hq6JQK/

  Note that the list includes mesa libraries and xserver-xorg* packages
  which are most suspect.

  Here is my /var/log/Xorg.0.log:

  https://paste.ubuntu.com/p/tB6yGhDT2S/

  Here is the output of "sudo lspci -vvx":

  https://paste.ubuntu.com/p/VVctSFwFSm/

  As you can see, there is nothing special about this machine: a pretty
  vanilla desktop with i5-3570K cpus (NOT overclocked!) and 16GB RAM.
  Oh, I forgot to say what actually happens and why the system is
  unusable: even if I create a single gnome-terminal window (say on the
  Dell monitor) after a couple of seconds (of typing in the terminal)
  large size rectangles appear on the other monitor. And if I start
  Chrome (on a monitor different from the one gnome-terminal is running
  on) then bits of the terminal sometimes appear on one of Chrome's tabs
  and vice versa, i.e. bits (rectangular shape) of Chrome's tabs appear
  on the terminal. Sometimes the content of the terminal gets corrupted.
  And all this happens reasonably quickly (on the order of 5-10
  seconds), which means you can't do any work at all. Also, creating
  other windows (I started pavucontrol in the background) makes the mess
  even worse, i.e. they all keep overwriting each other's rendering
  context.

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

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

[Touch-packages] [Bug 1780449] Re: [regression] i965 graphics corruption after recent xenial updates

[Tigran Aivazian]

I don't use apport infrastructure because I always uninstall such things
("security" etc) after installation of Ubuntu, which makes it boot about
20 times faster (0.9 seconds vs 15 seconds).

However, I am a Linux kernel developer with more than 20 years'
experience, so I am sure I can provide all the information you require
manually. What else do you need to see, other than lspci -vvx and
Xorg.0.log which I have provided already?

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

Title:
  [regression] i965 graphics corruption after recent xenial updates

Status in mesa package in Ubuntu:
  Incomplete
Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I am using Ubuntu 16.04.4 LTS. Since the original release two years
  ago it was working absolutely fine on a variety of machines. Now, on
  this particular machine I have two monitors:

  1. Dell 24" 1200x1920 (portrait) connected via D-SUB/VGA port
  2. AOC 28" 1920x1080 (landscape) connected via DVI-D

  I have made an upgrade today and the following packages were upgraded:

  https://paste.ubuntu.com/p/5cf8hq6JQK/

  Note that the list includes mesa libraries and xserver-xorg* packages
  which are most suspect.

  Here is my /var/log/Xorg.0.log:

  https://paste.ubuntu.com/p/tB6yGhDT2S/

  Here is the output of "sudo lspci -vvx":

  https://paste.ubuntu.com/p/VVctSFwFSm/

  As you can see, there is nothing special about this machine: a pretty
  vanilla desktop with i5-3570K cpus (NOT overclocked!) and 16GB RAM.
  Oh, I forgot to say what actually happens and why the system is
  unusable: even if I create a single gnome-terminal window (say on the
  Dell monitor) after a couple of seconds (of typing in the terminal)
  large size rectangles appear on the other monitor. And if I start
  Chrome (on a monitor different from the one gnome-terminal is running
  on) then bits of the terminal sometimes appear on one of Chrome's tabs
  and vice versa, i.e. bits (rectangular shape) of Chrome's tabs appear
  on the terminal. Sometimes the content of the terminal gets corrupted.
  And all this happens reasonably quickly (on the order of 5-10
  seconds), which means you can't do any work at all. Also, creating
  other windows (I started pavucontrol in the background) makes the mess
  even worse, i.e. they all keep overwriting each other's rendering
  context.

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

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

[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Christian Kaenzig]

Hello,

I confirm this bug also affects me on several Kubuntu 16.04 machines
since this morning, apparently following the unattended upgrades that
happened on Friday.

The symptoms are as described int the bugerport. I see them in okular
and a custom Python application that uses PyQt4. The bug makes these
applications unusable.

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

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  '17.2.8-0ubuntu0~16.04.1' version.

  For example:

  
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

  I also discovered that some of these depended on
  libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:

libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb


  WORKAROUND (ROLLBACK TO PRIOR VERSION)

  Install older versions with:

  sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb

  
  After rebooting, all the issues disappeared.

  For example I was once again able to left-click on the Firefox **three
  line/bar** menu and view 

[Touch-packages] [Bug 1780664] Re: Recent libgl-mesa graphics update prevents drop down list menu appearing in apps like firefox three line/bar menu icon

[Launchpad Bug Tracker]

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

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

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

Title:
  Recent libgl-mesa graphics update prevents drop down list menu
  appearing in apps like firefox three line/bar menu icon

Status in mesa package in Ubuntu:
  Confirmed

Bug description:
  PROBLEM

  Recent libgl-mesa 18.0.5-0ubuntu0~16.04.1 graphics update prevents
  drop down list menu appearing in apps like firefox three line/bar menu
  icon.

  After recently applying updates, left clicking on some application
  menus and icons no longer displays a drop-down menu list.

  For example in Firefox when I left-click on the **three line/bar**
  icon in the upper right-hand corner, the normal drop down list menu
  does not display.  Also the menu drop down doesn't display in
  keypassx.  Further xchat-gnome doesn't even display a window.

  Another anomaly is that my KDE bottom menu bar changed to a dark
  theme.

  
  BACKGROUND

  I'm using Kubuntu 16.04 on an Intel i7-7700k computer with Intel HD
  Graphics.  I have KDE **System Settings -> Compositor** enabled with:

 Scale method  :Accurate
 Rendering backend: OpenGL 3.1
 OpenGL interface:  GLX
 Tearing prevention ("vsync"):  Full screen repaints
 Keep window thumbnails:Only for Shown Windows

  
  INVESTIGATION

  After several hours of searching the Internet I found one other case
  of a similar problem.

 Firefox's Menu Bar won't open
 https://support.mozilla.org/en-US/questions/1194760

  The reported solution was to rollback the graphics drivers.

  
  Because the issues cropped up after applying updates on July 6, 2018,
  I tracked down the list of recent updates with:

 grep -A 2 'Start-Date: 2018-07-06' /var/log/apt/history.log | tail
  -1 >packages.txt

  After some editing to place packages on separate lines, and
  identifying the grahics libraries, I arrived at the following list:

  --

  libgles2-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libglapi-mesa:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libxatracker2:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libegl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgbm1:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libwayland-egl1-mesa:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-dri:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libosmesa6:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  libgl1-mesa-glx:i386 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)
  mesa-vdpau-drivers:amd64 (17.2.8-0ubuntu0~16.04.1 18.0.5-0ubuntu0~16.04.1)

  --

  To revert to the prior graphic drivers I tracked down the '.deb'
  packages for each of the above packages and downloaded the
  '17.2.8-0ubuntu0~16.04.1' version.

  For example:

  
https://launchpad.net/ubuntu/xenial/amd64/libxatracker2/17.2.8-0ubuntu0~16.04.1

  I also discovered that some of these depended on
  libllvm5.0_5.0-3~16.04.1 so I also downloaded the following files:

libllvm5.0_5.0-3~16.04.1_amd64.deb
libllvm5.0_5.0-3~16.04.1_i386.deb


  WORKAROUND (ROLLBACK TO PRIOR VERSION)

  Install older versions with:

  sudo dpkg -i \
libllvm5.0_5.0-3~16.04.1_amd64.deb \
libllvm5.0_5.0-3~16.04.1_i386.deb \
libegl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgbm1_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-dri_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libgl1-mesa-glx_17.2.8-0ubuntu0~16.04.1_i386.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libglapi-mesa_17.2.8-0ubuntu0~16.04.1_i386.deb \
libgles2-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libosmesa6_17.2.8-0ubuntu0~16.04.1_i386.deb \
libwayland-egl1-mesa_17.2.8-0ubuntu0~16.04.1_amd64.deb \
libxatracker2_17.2.8-0ubuntu0~16.04.1_amd64.deb \
mesa-vdpau-drivers_17.2.8-0ubuntu0~16.04.1_amd64.deb

  
  After rebooting, all the issues disappeared.

  For example I was once again able to left-click on the Firefox **three
  line/bar** menu and view the drop down list menu.  Also the KDE bottom
  menu bar retured to the normal "breeze" light grey colour.

To manage notifications about this bug go to:

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

[Daniel Axtens]

Hi,

I'm a bit confused then.

This is the netplan config you mentioned:

network:
  version: 2
  renderer: networkd
  ethernets:
id0:
  match:
macaddress: 08:00:27:6b:d8:91
  set-name: eth_static
  addresses: [ 1.2.3.4/16 ]
  gateway4: 5.6.7.8
id1:
  match:
macaddress: 08:00:27:23:68:f5
  set-name: eth_dhcp
  dhcp4: true


With the current version (not the -proposed version), my understanding
is that both devices keep their original names, neither device comes
up at all, and neither device will get an IP, dynamic or static. But
if I understand your comment correctly, you're saying that one of the
devices (the one with mac :f5) comes up and gets a DHCP IP? Is that
right? And if so, what is the device called - eth_dhcp or something
else?

Do you have virtualbox guest additions? I wonder if that's doing
something funky. And just checking you don't have ifupdown installed?

Regards,
Daniel

-- 
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:
  Confirmed
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 Committed
Status in netplan.io source package in Bionic:
  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

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

  

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

[Nicorac]

@Daniel: no, it's a regression to me because set-name never worked and
now DHCP stopped working too.

But I'm not testing the same environment as you, I'm on VirtualBox and this is 
my original bug report (linked to this one):
https://bugs.launchpad.net/netplan/+bug/1768827

-- 
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:
  Confirmed
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 Committed
Status in netplan.io source package in Bionic:
  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

  - 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 

[Touch-packages] [Bug 1780510] Re: pulseaudio does not resume playback via built in speakers, despite rebooting ubuntu

[Daniel van Vugt]

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

This sounds like a duplicate of bug 1711101.

** This bug has been marked a duplicate of bug 1711101
   Audio doesn't auto switch away from HDMI after unplugging HDMI

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

Title:
  pulseaudio does not resume playback via built in speakers, despite
  rebooting ubuntu

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  Adding on information to this bug:
  https://bugs.launchpad.net/bugs/1711101

  This time pulseaudio failed to start despite rebooting ubuntu

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  koli   3409 F pulseaudio
   /dev/snd/controlC0:  koli   3409 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul  7 09:48:34 2018
  InstallationDate: Installed on 2018-05-12 (55 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1770774] Re: ubuntu-MATE - top of windows disappear under panel

[Chris Guiver]

I bumped my box to 18.10 (development), and issue still occurs.

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

Title:
  ubuntu-MATE - top of windows disappear under panel

Status in xorg package in Ubuntu:
  New

Bug description:
  UBUNTU-MATE or MATE (1.20.1)

  // see also https://github.com/mate-desktop/mate-panel/issues/303
  rflbianco's comment may 10, 2018  (I opted not to comment there)

  I have two monitors, one above & slightly to right of the primary one
  (primary is bottom, and to left of one above it; overlap is about
  66%).  When I typed `ubuntu-bug` into mate-terminal and apport window
  opened, the top of it including minimize/maximize/close buttons were
  hidden by top panel (primary or my lower monitor).

  My theme is Panetheon (with dock on left on bottom/primary monitor
  with 'show hide buttons' naturally ticked to enable me to access
  hidden top of windows.

  Most new windows are opened top left on my primary (lower) monitor
  (eg. just now I opened "about me" & its top left without
  minimize/close or "Mugshot title bar visible UNTIL i click 'hide
  panel'. To view the button top left of window requires me to click
  'hide' on the right side of monitor which requires mouse movement.

  This does NOT cause crashes or anything. Its just annoying and I'm
  opting to use XFCE (which is also installed on my box).  It's been
  doing this since I dist-upgraded to 18.04 (from 17.10). I can re-
  produce easily as top left appears to be default position for windows
  to open (with exceptions; eg. chromium doesn't open top left under
  panel, but in its last position).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Sat May 12 09:55:31 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.15.0-19-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cedar [Radeon HD 5000/6000/7350/8350 
Series] [1002:68f9] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Radeon HD 6350 [103c:2126]
  InstallationDate: Installed on 2017-11-16 (176 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: Dell Inc. OptiPlex 960
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=afa7971f-3dd5-4b30-9c98-0af3e56a6f2b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0F428D
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.asset.tag: 1701283234
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd12/05/2011:svnDellInc.:pnOptiPlex960:pvr:rvnDellInc.:rn0F428D:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.name: OptiPlex 960
  dmi.sys.vendor: Dell Inc.
  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.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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