Re: [Touch-packages] [Bug 1780510] Re: pulseaudio does not resume playback via built in speakers, despite rebooting ubuntu

[sn0m]

Hi

I was playing an mkv file in vlc on my tv screen through a HDMI cable 
connected to my laptopt that runs ubuntu 18.04.

Sound was also playing on TV speakers via the HDMI cable as well.

I disconnected the HDMI cable and found out that sound would not reverse 
back to laptop built in speakers.

I rebooted the laptop and the problem persisted.

I therefore connected earplugs to it and than I was able to switch back 
to built in speakers.

There is a bug with pulseaudio? I think that is causing all this
trouble.

Regards

Koli


On 09/07/18 12:55, Daniel van Vugt wrote:
> Please describe in more detail what the problem is.
>
> ** Changed in: pulseaudio (Ubuntu)
> Status: New => Incomplete
>

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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 1780707] Re: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 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 initramfs-tools in Ubuntu.
https://bugs.launchpad.net/bugs/1780707

Title:
  package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After installing a fresh install of ubuntu 18.04, the software updater
  asked me to update and after saying yes, it reported this error about
  initramfs-tools.

  Also, another error just appeared which is much worse ... Here is what
  the dialog says:

  An unhandlable error occured
  There seems to be a programming error in aptdaemon, the software that allows 
you to install/remove software and to perform other package management related 
tasks.

  
  Not that the install was a full erase of a partition and now an update or 
merge

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.1
  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: Sun Jul  8 22:33:38 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2018-07-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  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
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1780707] [NEW] package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[Montecreasor]

Public bug reported:

After installing a fresh install of ubuntu 18.04, the software updater
asked me to update and after saying yes, it reported this error about
initramfs-tools.

Also, another error just appeared which is much worse ... Here is what
the dialog says:

An unhandlable error occured
There seems to be a programming error in aptdaemon, the software that allows 
you to install/remove software and to perform other package management related 
tasks.


Not that the install was a full erase of a partition and now an update or merge

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: initramfs-tools 0.130ubuntu3.1
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: Sun Jul  8 22:33:38 2018
Df:
 
Dmesg:
 
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 2
InstallationDate: Installed on 2018-07-09 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
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
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic

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

Title:
  package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 2

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  After installing a fresh install of ubuntu 18.04, the software updater
  asked me to update and after saying yes, it reported this error about
  initramfs-tools.

  Also, another error just appeared which is much worse ... Here is what
  the dialog says:

  An unhandlable error occured
  There seems to be a programming error in aptdaemon, the software that allows 
you to install/remove software and to perform other package management related 
tasks.

  
  Not that the install was a full erase of a partition and now an update or 
merge

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: initramfs-tools 0.130ubuntu3.1
  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: Sun Jul  8 22:33:38 2018
  Df:
   
  Dmesg:
   
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 2
  InstallationDate: Installed on 2018-07-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  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
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.130ubuntu3.1 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1780653] Re: my ubuntu partition does not restart

[Daniel van Vugt]

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

Title:
  my ubuntu partition does not restart

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  when i put my laptop in the pose mode or when i close my laptop and  i
  reopen it there is no responce from the system

  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 x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Jul  8 16:16:56 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:8101]
 Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265] 
[103c:811c]
  InstallationDate: Installed on 2017-05-18 (416 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: HP HP ProBook 450 G3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=ac6b4707-30fd-4b3b-8710-48d6f01a6ca1 ro plymouth:debug 
vesafb.invalid=1 nopat drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.15
  dmi.board.name: 8101
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 40.63
  dmi.chassis.asset.tag: 5CD6074RF7
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.15:bd11/07/2016:svnHP:pnHPProBook450G3:pvr:rvnHP:rn8101:rvrKBCVersion40.63:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 450 G3
  dmi.sys.vendor: HP
  version.compiz: compiz N/A
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-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: Fri Aug 11 23:29:19 2017
  xserver.configfile: default
  xserver.errors: modeset(0): failed to set mode: Permission denied
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6.1~16.04.2
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1780513] Re: buggy rendering of chrome based applications

[Daniel van Vugt]

This sounds like a problem with the nouveau graphics driver. If the
nvidia driver fixes it for you then please keep using that.

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

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

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

Title:
  buggy rendering of chrome based applications

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

Bug description:
  When using intel videocard and xserver-xorg-video-intel, 
  - mattermost desktop
  - visual studio code
  and postman

  do not render correctly, hovering the mouse over the window generates
  white square artifacts. Blinking contents tend to disappear...

  This is fixed by using the nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: i3
  Date: Sat Jul  7 12:08:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-24-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1a10]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1a10]
  InstallationDate: Installed on 2018-05-31 (36 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 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X580VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=bbcaa243-6163-41d8-ae82-b8298e8b4699 ro quiet splash nmi_watchdog=0 
pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nouveau.runpm=0 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X580VD.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X580VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX580VD.312:bd12/22/2017:svnASUSTeKCOMPUTERINC.:pnX580VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X580VD
  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.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/linux/+bug/1780513/+subscriptions

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

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

[Ubuntu Kernel Bot]

This change was made by a bot.

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

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

Title:
  buggy rendering of chrome based applications

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

Bug description:
  When using intel videocard and xserver-xorg-video-intel, 
  - mattermost desktop
  - visual studio code
  and postman

  do not render correctly, hovering the mouse over the window generates
  white square artifacts. Blinking contents tend to disappear...

  This is fixed by using the nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: i3
  Date: Sat Jul  7 12:08:19 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-24-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Device [8086:591b] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Device [1043:1a10]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Mobile] 
[1043:1a10]
  InstallationDate: Installed on 2018-05-31 (36 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 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 13d3:56a2 IMC Networks 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X580VD
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=bbcaa243-6163-41d8-ae82-b8298e8b4699 ro quiet splash nmi_watchdog=0 
pcie_aspm=force drm.vblankoffdelay=1 i915.semaphores=1 nouveau.runpm=0 
vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/22/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X580VD.312
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X580VD
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX580VD.312:bd12/22/2017:svnASUSTeKCOMPUTERINC.:pnX580VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX580VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X580VD
  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.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/linux/+bug/1780513/+subscriptions

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

[Touch-packages] [Bug 1780677] Re: X session crash after resuming from suspend

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


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

Title:
  X session crash after resuming from suspend

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7

  First I suspended my laptop, while a few applications were running
  (Firefox, Chrome and some others much smaller). A couple of hours
  later, I opened the lid and expected the Gnome session would resume.

  What happened instead was a crash of the X server, then the login page
  was shown again and a new Gnome session started: the old session got
  killed!

  In the Xorg.0.log.old file I found this, not sure if related:

  [ 21189.337] (II) NVIDIA(GPU-0): Deleting GPU-0
  [ 21189.338] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
  [ 21189.338] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
  [ 21189.338] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
  [ 21189.338] (II) Server terminated successfully (0). Closing log file.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
  Uname: Linux 4.15.0-24-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una 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  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Jul  8 23:03:30 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-24-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05cc]
   NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc]
  InstallationDate: Installed on 2018-06-21 (17 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Precision M4800
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic 
root=/dev/mapper/vg-root ro scsi_mod.scan=sync quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/02/2014
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0T3YTY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  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.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

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

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

[Touch-packages] [Bug 1780693] [NEW] package pulseaudio 1:11.1-1ubuntu7.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configurati

[Wilber]

Public bug reported:

na

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
Uname: Linux 4.15.0-20-generic x86_64
NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40
ApportVersion: 2.20.9-0ubuntu7.2
AptOrdering:
 libpulse-mainloop-glib0:amd64: Install
 libpulse0:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1013 F pulseaudio
  wilber 1365 F pulseaudio
Date: Sun Jul  8 22:55:37 2018
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2018-07-09 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
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
SourcePackage: pulseaudio
Title: package pulseaudio 1:11.1-1ubuntu7.1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
dmi.product.family: Virtual Machine
dmi.product.name: VirtualBox
dmi.product.version: 1.2
dmi.sys.vendor: innotek GmbH

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


** Tags: amd64 apport-package bionic

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

Title:
  package pulseaudio 1:11.1-1ubuntu7.1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  na

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_40
  ApportVersion: 2.20.9-0ubuntu7.2
  AptOrdering:
   libpulse-mainloop-glib0:amd64: Install
   libpulse0:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1013 F pulseaudio
wilber 1365 F pulseaudio
  Date: Sun Jul  8 22:55:37 2018
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2018-07-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  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
  SourcePackage: pulseaudio
  Title: package pulseaudio 1:11.1-1ubuntu7.1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

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

-- 
Mailing list: https://launchpad.net/~touch-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: Dual monitor system unusable after xorg+mesa upgrade

[Daniel van Vugt]

Please:

1. Run 'apport-collect 1780449' to send us more information about the
machine.

2. Take a photo of the corruption and attach it here.

** Tags added: regression-update xenial

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

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

** Summary changed:

- Dual monitor system unusable after xorg+mesa upgrade
+ [regression] Graphics corruption after recent xenial updates

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

** Changed in: xorg-server (Ubuntu)
   Status: New => Incomplete

** Summary changed:

- [regression] Graphics corruption after recent xenial updates
+ [regression] i965 graphics corruption after recent xenial updates

-- 
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/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 1780510] Re: pulseaudio does not resume playback via built in speakers, despite rebooting ubuntu

[Daniel van Vugt]

Please describe in more detail what the problem is.

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/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 1780439] Re: Dual Monitor not detect on VGA

[Daniel van Vugt]

According to your Xrandr.txt your machine doesn't have a VGA port. It
only has a built-in LCD, HDMI and/or DisplayPort.

So please explain in more detail what the problem is. Do you mean you
have plugged in a monitor and it's not working? If so then please plug
it in again, run 'xrandr' in a terminal while it's plugged in and send
us the output:

  xrandr > xrandragain.txt


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

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

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

Title:
  Dual Monitor not detect on VGA

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I can able to use monitor via HDMI but VGA is not working.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  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
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jul  6 18:58:09 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell UHD Graphics 620 [1028:0810]
 Subsystem: Dell Topaz XT [Radeon R7 M260/M265 / M340/M360 / M440/M445] 
[1028:0810]
  InstallationDate: Installed on 2018-06-11 (25 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. Inspiron 5570
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=3df9f896-71aa-40c0-b273-a8f786cebfd5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/25/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.0.6
  dmi.board.name: 0YDF7T
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.0.6:bd10/25/2017:svnDellInc.:pnInspiron5570:pvr:rvnDellInc.:rn0YDF7T:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: Inspiron
  dmi.product.name: Inspiron 5570
  dmi.sys.vendor: Dell Inc.
  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/1780439/+subscriptions

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

[Touch-packages] [Bug 1780409] Re: wifi on 16.04

[Daniel van Vugt]

It appears you have:

  Intel Corporation Centrino Ultimate-N 6300

using the iwlwifi kernel module, so reassigning to the kernel.

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

Title:
  wifi on 16.04

Status in linux package in Ubuntu:
  New

Bug description:
  Has trouble finding my router wifi. Sometimes finds my neighbour's but not 
mine. Others do not have this problem. Advice in Help sometimes works to 
connect.
  When found, the connection 'arcs' icon shows a connection but then changes to 
the double arrow logo (usually associated with wire connection).
  Currently connected but showing double arrow. Drop-down menu shows no 
available wifi's.

  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 x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  BootLog:
   
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Fri Jul  6 10:21:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller [103c:161c]
  InstallationDate: Installed on 2018-02-18 (137 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP EliteBook 8460p
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=533de285-2d90-4e13-8140-a65b8d250094 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68SCF Ver. F.08
  dmi.board.name: 161C
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 97.45
  dmi.chassis.asset.tag: m705800
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68SCFVer.F.08:bd08/26/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.45:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN
  dmi.product.name: HP EliteBook 8460p
  dmi.product.version: A0001D02
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-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: Thu Jul  5 13:59:06 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

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

[Touch-packages] [Bug 1780680] Re: Older version in artful than in xenial

[Anders Kaseorg]

** Description changed:

  These packages have an older version in artful than in xenial.
  
  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1
  
  Some of these are older in bionic than in xenial too.
  
- Shouldn’t there be an automated check for this?
+ Shouldn’t there be an automated check for this?  (See also: bug 1780679,
+ bug 1780681.)

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

Title:
  Older version in artful than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  New
Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in patch package in Ubuntu:
  New
Status in python-pyvmomi package in Ubuntu:
  New
Status in snapcraft package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  New

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?  (See also: bug
  1780679, bug 1780681.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions

-- 
Mailing list: https://launchpad.net/~touch-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 for the patch, but again that's only a workaround. We would like
to aim for a fix instead, but if it's an uncommon chipset then that may
take a long time...

Please provide a full listing of 'lspci -k' and then we can do the right
thing and log an upstream bug. After that's done it will be fine to just
patch in a workaround.

-- 
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 1779905] Re: Missing pulseaudio-module-jack files, cannot load module

[Daniel van Vugt]

We can keep this bug ID but you'll need to reword the bug title and
description to encompass the actual problem. The initial problem you
reported is invalid - that was the jack module not working. Because the
jack module wasn't installed.

Please reword the bug title and description however you like, and when
done set the bug status back to 'New'.


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

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

Title:
  Missing pulseaudio-module-jack files, cannot load module

Status in pulseaudio package in Ubuntu:
  Incomplete

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.

  I'm on Ubuntu 16.04.04.

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 1770082] Re: systemd-networkd not renaming devices on boot

[Daniel Axtens]

Hi,

I have confirmed that the Bionic package works on the cloud service
where the bug was originally observed. With this package, the affected
migrations now succeed.

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:

  1: lo:  mtu 65536 qdisc noqueue state UNKNOWN group 
default qlen 1000
  link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
  inet 127.0.0.1/8 scope host lo
     valid_lft forever preferred_lft forever
  inet6 ::1/128 scope host
     valid_lft forever preferred_lft forever
  3: myiface3:  mtu 1500 qdisc fq_codel state 
UP group default qlen 1000
  link/ether 52:54:00:de:bd:f6 brd ff:ff:ff:ff:ff:ff
  inet 192.168.122.151/24 brd 192.168.122.255 scope global dynamic myiface3
     valid_lft 3575sec preferred_lft 3575sec
  inet6 fe80::5054:ff:fede:bdf6/64 scope link
     valid_lft forever preferred_lft forever

  So names are successfully changed with netplan apply.

  This seems to be some udev-related timing or 

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

[Daniel Axtens]

Hi,

I can verify correct behaviour with renaming, static IPs and DHCP with
KVM. I'm about to check some cloud services as well.

Nicorac, are you claiming this is a regression or just an incomplete
fix?

If it's just an incomplete fix, I think we should spin that out into
another bug and fix it after this SRU goes through.

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:

  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 1718931] Re: No VPN autoconnect

[Nicholas Stommel]

Well...it has been quite some time and this bug has received absolutely
*zero* attention from the Gnome Shell Gitlab here
https://gitlab.gnome.org/GNOME/gnome-shell/issues/123 escalated from the
Gnome Bugzilla tracker after Gnome shell development moved to Gitlab.
The issue is fully present in Ubuntu 18.04 AND in the newer version of
the Gnome shell and NetworkManager in Fedora 28. Before v3.26.X, auto-
connect worked fine through the NetworkManager in the Gnome environment.
I'm afraid to report that months later, absolutely nothing has been done
to address what should be a relatively high-priority bug in the Gnome
Shell. If anyone has the capabilities to reach out farther than I
already have, please do so. This critical bug has been sitting idle with
no attention for months, and persists across newer versions of the Gnome
shell, namely 3.28.X, seemingly independent of distribution.

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

Title:
  No VPN autoconnect

Status in NetworkManager:
  Incomplete
Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  When setting up VPN to auto connect with wifi (done through nm-
  connection-editor) the wifi never manages to connect. However if I
  unselect the auto connect option while it is attempting a reconnection
  then it manages to connect to both (wifi and VPN). Doing the
  connection manually also poses no issues

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: network-manager 1.8.2-1ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-11.12-generic 4.13.1
  Uname: Linux 4.13.0-11-generic x86_64
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Sep 22 13:15:55 2017
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2017-09-09 (12 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170908)
  IpRoute:
   default via 192.168.0.1 dev wlp6s0 proto static metric 600 
   169.254.0.0/16 dev wlp6s0 scope link metric 1000 
   192.168.0.0/24 dev wlp6s0 proto kernel scope link src 192.168.0.18 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  STATE  DBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp6s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
VM5055940   85b8f881-7ed9-477a-9c39-9afb5a40bda9  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
   ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.8.2connected  started  full  enabled enabled  
enabled  enabled  enabled

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

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

[Daniel Axtens]

** Tags removed: verification-failed-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/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 timing or priority issue that I'm
  still trying to hunt down.

  This breaks some forms of migration in certain 

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

[Jochem Blok]

Geachte heer/mevrouw,

Bedankt voor uw e-mail!

Op maandag ben ik niet aan het werk. Mijn werkdagen zijn dinsdag tot en
met vrijdag. Ik zal uw mail dan in behandeling nemen.




Met vriendelijke groet,


Jochem Blok
Programmeur









E: jochem.b...@fasterforward.nl


T: +31 (0) 164 210 240


Faster Forward | Stationsstraat 
14
4611 CC Bergen op Zoom | 
www.fasterforward.nl






  


Op deze e-mail is een disclaimer van toepassing, ga 
naar www.fasterforward.nl/e-mail-disclaimer
A disclaimer is applicable to this email, please refer 
to www.fasterforward.nl/e-mail-disclaimer




Van: Evgeniy (1754...@bugs.launchpad.net)Datum: 09-07-2018 01:45Aan: 
jochem.b...@fasterforward.nl (jochem.b...@fasterforward.nl)Onderwerp: [bug 
1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.
+1 to #66

--
You received this bug notification because you are subscribed to
the bug
report.
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


** Attachment added: "logo2015.png"
   
https://bugs.launchpad.net/bugs/1754294/+attachment/5161209/+files/logo2015.png

** Attachment added: "linkedin-icon.png"
   
https://bugs.launchpad.net/bugs/1754294/+attachment/5161210/+files/linkedin-icon.png

** Attachment added: "facebook-icon.png"
   
https://bugs.launchpad.net/bugs/1754294/+attachment/5161211/+files/facebook-icon.png

** Attachment added: "twitter-icon.png"
   
https://bugs.launchpad.net/bugs/1754294/+attachment/5161212/+files/twitter-icon.png

-- 
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 1754294] Re: After last updated libcurl3 on libcurl4, some apps are removed.

[Evgeniy]

+1 to #66

-- 
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 1760612] Re: ERROR:service_manager_context.cc(252)] Attempting to run unsupported native service: /usr/lib/chromium-browser/content_utility.service

[Launchpad Bug Tracker]

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

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

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

Title:
  ERROR:service_manager_context.cc(252)] Attempting to run unsupported
  native service: /usr/lib/chromium-browser/content_utility.service

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  Was sending a previous report via a not opened chromium browser, and
  these output were displayed into the terminal:

  
  oem@lapubu:~$ ubuntu-bug apt-xapian-index
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=
  [2237:2281:0402/144056.666268:ERROR:nss_util.cc(724)] After loading Root 
Certs, loaded==false: NSS error code: -8018
  [2237:2237:0402/144112.274986:ERROR:gpu_process_transport_factory.cc(1019)] 
Lost UI shared context.
  
[2237:2237:0402/144130.282625:ERROR:navigation_entry_screenshot_manager.cc(135)]
 Invalid entry with unique id: 1
  [2237:2281:0402/144619.994476:ERROR:service_manager_context.cc(252)] 
Attempting to run unsupported native service: 
/usr/lib/chromium-browser/content_utility.service
  ^CTraceback (most recent call last):
File "/usr/share/apport/apport-gtk", line 598, in 
  app.run_argv()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 663, in run_argv
  return self.run_report_bug()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 503, in 
run_report_bug
  self.file_report()
File "/usr/lib/python3/dist-packages/apport/ui.py", line 1274, in 
file_report
  self.open_url(url)
File "/usr/lib/python3/dist-packages/apport/ui.py", line 1147, in open_url
  (pid, status) = os.wait()

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic i686
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: i386
  CurrentDesktop: LXDE
  Date: Mon Apr  2 15:13:17 2018
  InstallationDate: Installed on 2013-10-21 (1624 days ago)
  InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Anders Kaseorg]

Until this is uploaded to bionic, the version in bionic is older than in
xenial (bug 1780680), which is going to interfere with upgrades.

-- 
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 Committed
Status in mesa source package in Bionic:
  Fix Committed

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 1542755] Re:

[maryh]

http://bridge.joehendricksphotography.com

Mary Hamilton

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

Title:
  at least 3 reinstalls due to no onshut down or restart. msg  start up
  sometimes, tried boot repair,something was missing, sorry I can't
  remember terminology.  Problems started with  specialized downloads.
  Sound recorder(bad)sound converter,pixel swapper, great apps. I was
  thinking my att router has been compromised via win 10 updates..

Status in gcc-4.8 package in Ubuntu:
  Invalid

Bug description:
  Ubuntu 14.04 over a year using with all updates worked great, then the
  Libre Office Writer went fooey,several re-installs,fixed.Then, I
  thought all my photos were getting shared live maybe via Libre Ofiice
  app

   Then  Firefox sync caused me a lot of grief when I installed it on
  two win10 desktops with Sync Not syncing now tho.

  I swapped the mouse, which doesn't want to function well. Got firefox
  straight maybe, then Ubuntu started hanging on restart or shut down. I
  tried running a boot repair, it said my registry was missing. I tried
  for a clean install, but I think all it did was add a copy. No
  reinstall would shut down.Tried a different version,same problem. I
  have an att router & have been installing updates et al, on 2 other
  desktops. As soon as I get a Win 10 going, something seems to stop
  working on Ubuntu. I prefer Ubuntu for multiple reasons. Win 10 seems
  to be a barebones with a big buynow catalog or surf the win10 web.
  However, it has a working Sound recorder, & AIO dell usb XP
  printer,fax etc.

   Also, I have a Nook reader with lots of apps I don't use. I've
  started using the OverDrive only app, as the google library
  chromeconnection kept me confused. added new windows, froze books,etc.
  It is wifi which I leave on continuously.

  I just learned Sudo init O. Used it one time. Worked fine.  These
  "bugs" seem to be attempts to wreak havoc,  I have copies of my
  files/photos on DVD, which I download to desktop when I re-install.

  So sorry. I break things worse trying to repair them many times, but
  I'm experienced at starting over, just don't like to. I am trying to
  avoid wiping the hd, reformatting, etc. Very time consuming for a
  little old lady pushing 70. Time is precious, but so is money,lol, so
  I do it myself.This bug reequest popped up, so maybe you can connect
  something from others with similar occurances.

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: cpp-4.8 4.8.2-19ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-32.57-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  Date: Sat Feb  6 18:53:42 2016
  DuplicateSignature: package:cpp-4.8:4.8.2-19ubuntu1:cannot copy extracted 
data for './usr/bin/cpp-4.8' to '/usr/bin/cpp-4.8.dpkg-new': unexpected end of 
file or stream
  ErrorMessage: cannot copy extracted data for './usr/bin/cpp-4.8' to 
'/usr/bin/cpp-4.8.dpkg-new': unexpected end of file or stream
  InstallationDate: Installed on 2016-02-06 (0 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: gcc-4.8
  Title: package cpp-4.8 4.8.2-19ubuntu1 failed to install/upgrade: cannot copy 
extracted data for './usr/bin/cpp-4.8' to '/usr/bin/cpp-4.8.dpkg-new': 
unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-4.8/+bug/1542755/+subscriptions

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

[Touch-packages] [Bug 1780680] [NEW] Older version in artful than in xenial

[Anders Kaseorg]

Public bug reported:

These packages have an older version in artful than in xenial.

fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
libdrm 2.4.83-1 < 2.4.91-2~16.04.1
mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
snapcraft 2.42+17.10 < 2.42.1
wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

Some of these are older in bionic than in xenial too.

Shouldn’t there be an automated check for this?

** Affects: fuse-umfuse-ext2 (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

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

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

** Affects: wireless-regdb (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: artful bionic

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

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

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

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

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

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

** Also affects: wireless-regdb (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Older version in artful than in xenial

Status in fuse-umfuse-ext2 package in Ubuntu:
  New
Status in libclc package in Ubuntu:
  New
Status in libdrm package in Ubuntu:
  New
Status in mesa package in Ubuntu:
  New
Status in patch package in Ubuntu:
  New
Status in python-pyvmomi package in Ubuntu:
  New
Status in snapcraft package in Ubuntu:
  New
Status in wireless-regdb package in Ubuntu:
  New

Bug description:
  These packages have an older version in artful than in xenial.

  fuse-umfuse-ext2 0.4-1.1ubuntu0.1 < 0.4-1.1ubuntu0.16.04.1
  libclc 0.2.0+git20170330-3 < 0.2.0+git20180312-1~16.04.1
  libdrm 2.4.83-1 < 2.4.91-2~16.04.1
  mesa 17.2.8-0ubuntu0~17.10.1 < 18.0.5-0ubuntu0~16.04.1
  patch 2.7.5-1ubuntu0.2 < 2.7.5-1ubuntu0.16.04.1
  python-pyvmomi 5.5.0-2014.1.1-3 < 6.5.0.2017.5-0ubuntu1~16.04.1
  snapcraft 2.42+17.10 < 2.42.1
  wireless-regdb 2016.06.10-0ubuntu1 < 2018.05.09-0ubuntu1~16.04.1

  Some of these are older in bionic than in xenial too.

  Shouldn’t there be an automated check for this?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fuse-umfuse-ext2/+bug/1780680/+subscriptions

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

[Touch-packages] [Bug 1780677] [NEW] X session crash after resuming from suspend

[giacof]

Public bug reported:

Description:Ubuntu 18.04 LTS
Release:18.04

xorg:
  Installed: 1:7.7+19ubuntu7

First I suspended my laptop, while a few applications were running
(Firefox, Chrome and some others much smaller). A couple of hours later,
I opened the lid and expected the Gnome session would resume.

What happened instead was a crash of the X server, then the login page
was shown again and a new Gnome session started: the old session got
killed!

In the Xorg.0.log.old file I found this, not sure if related:

[ 21189.337] (II) NVIDIA(GPU-0): Deleting GPU-0
[ 21189.338] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
[ 21189.338] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
[ 21189.338] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
[ 21189.338] (II) Server terminated successfully (0). Closing log file.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-24.26-generic 4.15.18
Uname: Linux 4.15.0-24-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] È una 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  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
BootLog: Error: [Errno 13] Permesso negato: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Jul  8 23:03:30 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-24-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05cc]
 NVIDIA Corporation GK107GLM [Quadro K1100M] [10de:0ff6] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GK107GLM [Quadro K1100M] [1028:15cc]
InstallationDate: Installed on 2018-06-21 (17 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: Dell Inc. Precision M4800
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-24-generic 
root=/dev/mapper/vg-root ro scsi_mod.scan=sync quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/02/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0T3YTY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd01/02/2014:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0T3YTY:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4800
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
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.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: xorg (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  X session crash after resuming from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  xorg:
Installed: 1:7.7+19ubuntu7

  First I suspended my laptop, while a few applications were running
  (Firefox, Chrome and some others much smaller). A couple of hours
  later, I opened the lid and expected the Gnome session would resume.

  What happened instead was a crash of the X server, then the login page
  was shown again and a new Gnome session started: the old session got
  killed!

  In the Xorg.0.log.old file I found this, not sure if related:

  [ 21189.337] (II) NVIDIA(GPU-0): Deleting GPU-0
  [ 21189.338] (WW) xf86CloseConsole: KDSETMODE failed: Input/output error
  [ 21189.338] (WW) xf86CloseConsole: VT_GETMODE failed: Input/output error
  [ 21189.338] (WW) xf86CloseConsole: VT_ACTIVATE failed: Input/output error
  [ 21189.338] (II) Server 

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

[Curtis Gedak]

Public bug reported:

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.

** Affects: mesa (Ubuntu)
 Importance: Undecided
 Status: 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/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:
  New

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 

Re: [Touch-packages] [Bug 1779622] Re: issue is regarding boot hanging between work

[afnan arshad]

thanks for reviewing but where is the solution? what i am suppose to
do in order to fix it...it is getting worse..

On Thu, Jul 5, 2018 at 5:16 AM, Alex Murray  wrote:
> ** Information type changed from Private Security to Public
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1779622
>
> Title:
>   issue is regarding boot hanging between work
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   the system get hang while booting and also when shutting down. while
>   work some of keyboard functions stop working like brightness control
>   and  sound control. at times system has to be force shut down. at
>   times some of the application do not get opened.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: xorg 1:7.7+13ubuntu3
>   ProcVersionSignature: Ubuntu 4.4.0-128.154-generic 4.4.131
>   Uname: Linux 4.4.0-128-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.1-0ubuntu2.18
>   Architecture: amd64
>   BootLog:
>Scanning for Btrfs filesystems
>UBUNTU: clean, 272012/29777920 files, 3537812/119111424 blocks
>   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  2 12:59:44 2018
>   DistUpgraded: Fresh install
>   DistributionChannelDescriptor:
># This is a distribution channel descriptor
># For more information see 
> http://wiki.ubuntu.com/DistributionChannelDescriptor
>canonical-oem-somerville-xenial-amd64-20160624-2
>   DistroCodename: xenial
>   DistroVariant: ubuntu
>   GraphicsCard:
>Intel Corporation Device [8086:5916] (rev 02) (prog-if 00 [VGA controller])
>  Subsystem: Dell Device [1028:0767]
>   InstallationDate: Installed on 2018-02-22 (129 days ago)
>   InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 
> 20160624-10:47
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 004: ID 8087:0a2a Intel Corp.
>Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
> Reader Controller
>Bus 001 Device 002: ID 0c45:6a06 Microdia
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: Dell Inc. Inspiron 5567
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-128-generic.efi.signed 
> root=UUID=a581e6e4-3ec8-44a1-96df-744ef70e8b7e ro acpi_rev_override 
> locale=en_US plymouth:debug drm.debug=0xe
>   SourcePackage: xorg
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 01/12/2017
>   dmi.bios.vendor: Dell Inc.
>   dmi.bios.version: 1.1.0
>   dmi.board.name: 0C6XG5
>   dmi.board.vendor: Dell Inc.
>   dmi.board.version: A00
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: Dell Inc.
>   dmi.modalias: 
> dmi:bvnDellInc.:bvr1.1.0:bd01/12/2017:svnDellInc.:pnInspiron5567:pvr:rvnDellInc.:rn0C6XG5:rvrA00:cvnDellInc.:ct10:cvr:
>   dmi.product.name: Inspiron 5567
>   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.83-1~16.04.1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
>   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
>   version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel 
> 2:2.99.917+git20160325-1ubuntu1.2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
> 1:1.0.12-1build2
>   xserver.bootTime: Mon Jul  2 12:45:36 2018
>   xserver.configfile: default
>   xserver.errors:
>
>   xserver.logfile: /var/log/Xorg.0.log
>   xserver.outputs:
>product id1317
>vendor LGD
>   xserver.version: 2:1.18.4-0ubuntu0.7
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1779622/+subscriptions

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

Title:
  issue is regarding boot hanging between work

Status in xorg package in Ubuntu:
  New

Bug description:
  the system get hang while booting and also when shutting down. while
  work some of keyboard functions stop working like brightness control
  and  sound control. at times system has to be force shut down. at
  times some of the application do not get opened.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: 

[Touch-packages] [Bug 1194176] Re: Allow service icons at service level, not just application level

[gf]

Hello Jeremy,
Thank you for submitting this bug and reporting a problem with icons and UOA.  
You made this bug report in 2013 and there have been several versions of Ubuntu 
since then. 

Could you confirm that this is no longer a problem and that we can close the 
ticket? 
If it is still a problem, are you still interested in finding a solution to 
this bug? 
If you are, could you run the following (only once):
apport-collect 1194176
and upload the updated logs and and any other logs that are relevant for this 
particular issue. 

Thank you again for helping make Ubuntu better. 
G

** Changed in: gnome-control-center-signon (Ubuntu)
   Status: New => Incomplete

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

Title:
  Allow service icons at service level, not just application level

Status in gnome-control-center-signon package in Ubuntu:
  Incomplete

Bug description:
  evolution-data-server-uoa 3.8.3-0ubuntu4 provides several different
  services and a single icon isn't sufficient to represent all of them.
  They don't want to use the evolution icon since EDS is more than just
  Evolution (it's also used by Thunderbird, GNOME Contacts,  etc.). This
  was discussed at https://bugzilla.gnome.org/701964

  Services provided by eds-uoa
  ---
  google-calendar.service
  google-contacts.service
  google-gmail.service
  yahoo-calendar.service
  yahoo-mail.service

  Currently, it appears that UOA only looks at the .desktop for an icon but 
evolution-data-server-uoa.desktop doesn't have an icon. However, 
/usr/share/accounts/services/google-calendar.service sets calendar
  /usr/share/accounts/service_types/calendar.service-type sets 
x-office-calendar

  I believe the current behavior for settings the service icon is something 
like:
  1. Use the .desktop icon
  2. If not set, don't show an icon at all. This makes the eds services look 
out of place.

  Suggested improved behavior
  1. Use an icon in the /services/*.service
  2. If not set, fallback to the .desktop icon
  3. If not set, fallback to the icon set by the corresponding 
service_types/*.service_type
  4. Set a generic icon

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: gnome-control-center-signon 0.1.7~daily13.06.18-0ubuntu1
  ProcVersionSignature: Ubuntu 3.9.0-7.15-generic 3.9.7
  Uname: Linux 3.9.0-7-generic x86_64
  ApportVersion: 2.10.2-0ubuntu2
  Architecture: amd64
  Date: Mon Jun 24 11:30:31 2013
  InstallationDate: Installed on 2013-06-14 (10 days ago)
  InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Alpha amd64 
(20130613)
  MarkForUpload: True
  SourcePackage: gnome-control-center-signon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center-signon/+bug/1194176/+subscriptions

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

I finally got around to tracking down this problem it seems to be a
mimeinfo.cache issue.

If the reader is not familiar mimeinfo is part of the freedesktop and
contains all the mime types and their program associations.

for deb packages the primary mime type (called media types now because
why not } is:

application/vnd.debian.binary-package

with 2 depreciated alternates:

application/x-deb
application/x-debian-package

this is documented @ https://www.iana.org/assignments/media-
types/application/vnd.debian.binary-package

the entire mime list is @ http://www.iana.org/assignments/media-types/

these definitions are combined with default applications and put into
defaults.list file(s). On my system I have several . They are
located @:

/etc/g/etc/xfce4/defaults.list
nome/defaults.list
/usr/share/applications/defaults.list
/usr/share/xfce4/applications/defaults.list
/usr/share/xubuntu/applications/defaults.list

now I am not 100% but I believe that the mimeinfo.cache file is created
from the default.list (God only knows which one) and updated every time
a program/package is installed. This is all part of the Freedesktop/xdg
stuff and you can read the docs/specs @ their website.


 On my system I have 2 of these files:

/usr/share/applications/mimeinfo.cache
/home/johndoe/.local/share/applications/mimeinfo.cache

to "fix" the problem with launching gdebi from the Thunar context menu
(right mouse menu) I edited the /usr/share/applications/mimeinfo.cache
file so the only app association with the deb packages was gdebi.desktop
(and of course there are multiple of these on my system ):

application/vnd.debian.binary-package=gdebi.desktop;
application/x-deb=gdebi.desktop;
application/x-debian-package;

I also modified my in the same manner but it seems that the file in
/usr/share/applications/mimeinfo.cache is the critical one for Thunar,

To get Gdebi to work from the opera downloads via open downloaded .deb
file I had to add the mime associations to
/home/johndoe/.config/mimeapps.list (yea! another MIME file)

Now there is yet another MIME file /usr/share/mime/mime.cache which is a
binary file. It can be updated via the command:

$ sudo update-mime-database /usr/share/mime/

I don't know who or what uses it but I am at the tail end of an all-
nighter hunting down this bug so I updated it.

There is one more file that should be looked at:

/usr/share/application-registry/gdebi.applications

the last line in the file is:

mime_types=application/x-deb

I changed it to:

mime_types=application/x-deb;application/vnd.debian.binary-
package;application/x-debian-package;

not sure if it matters nor if it should be comma separated or semi-colon
separated perhaps the package maintainer can chime in.

I hope this is somewhat helpful. If you are reading this and NOT on an
xubuntu system you file locations may be different. use your favorite
file search utility (I use catfish) and look for "mimeinfo",
"defaults.list", "mime", and "gdebi"

-- 
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 1746286] Re: Update libharfbuzz to 1.7.4

[Hans Joachim Desserud]

harfbuzz 1.8.2-2 has been synced from Debian to Ubuntu Cosmic (will
become 18.10).

Since you mentioned kitty, I requested that synced as well (bug
1780551), so it too will be available in the next Ubuntu release. :)

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

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

Title:
  Update libharfbuzz to 1.7.4

Status in harfbuzz package in Ubuntu:
  Fix Released

Bug description:
  Available here: https://www.freedesktop.org/software/harfbuzz/release/

  
  Current version of libharfbuzz-dev is 1.4.2-1, same with libharfbuzz0b 
(strange name?). 

  It's used in the pretty awesome terminal Kitty;
  https://github.com/kovidgoyal/kitty

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

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

[Touch-packages] [Bug 1780653] [NEW] my ubuntu partition does not restart

[djawed bek]

Public bug reported:

when i put my laptop in the pose mode or when i close my laptop and  i
reopen it there is no responce from the system

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 x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Jul  8 16:16:56 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:8101]
   Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265] [103c:811c]
InstallationDate: Installed on 2017-05-18 (416 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
MachineType: HP HP ProBook 450 G3
ProcEnviron:
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=ac6b4707-30fd-4b3b-8710-48d6f01a6ca1 ro plymouth:debug 
vesafb.invalid=1 nopat drm.debug=0xe
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/07/2016
dmi.bios.vendor: HP
dmi.bios.version: N78 Ver. 01.15
dmi.board.name: 8101
dmi.board.vendor: HP
dmi.board.version: KBC Version 40.63
dmi.chassis.asset.tag: 5CD6074RF7
dmi.chassis.type: 10
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.15:bd11/07/2016:svnHP:pnHPProBook450G3:pvr:rvnHP:rn8101:rvrKBCVersion40.63:cvnHP:ct10:cvr:
dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
dmi.product.name: HP ProBook 450 G3
dmi.sys.vendor: HP
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-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: Fri Aug 11 23:29:19 2017
xserver.configfile: default
xserver.errors: modeset(0): failed to set mode: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu6.1~16.04.2
xserver.video_driver: modeset

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


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

Title:
  my ubuntu partition does not restart

Status in xorg package in Ubuntu:
  New

Bug description:
  when i put my laptop in the pose mode or when i close my laptop and  i
  reopen it there is no responce from the system

  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 x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Jul  8 16:16:56 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Hewlett-Packard Company Skylake Integrated Graphics [103c:8101]
 Subsystem: Hewlett-Packard Company Topaz XT [Radeon R7 M260/M265] 
[103c:811c]
  InstallationDate: Installed on 2017-05-18 (416 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: HP HP ProBook 450 G3
  ProcEnviron:
   PATH=(custom, no user)
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=ac6b4707-30fd-4b3b-8710-48d6f01a6ca1 ro plymouth:debug 
vesafb.invalid=1 nopat drm.debug=0xe
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/07/2016
  dmi.bios.vendor: HP
  dmi.bios.version: N78 Ver. 01.15
  dmi.board.name: 8101
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 40.63
  dmi.chassis.asset.tag: 5CD6074RF7
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrN78Ver.01.15:bd11/07/2016:svnHP:pnHPProBook450G3:pvr:rvnHP:rn8101:rvrKBCVersion40.63:cvnHP:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 450 G3
  dmi.sys.vendor: HP
  

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

[fumihiko kakuma]

The patch was merged in upstream.

-- 
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 1780618] Re: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[Hans Joachim Desserud]

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

** This bug has been marked a duplicate of bug 1780616
   package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers 
looping, abandoned

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Upgrading from 16.04 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Jul  8 05:09:36 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-01-23 (531 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.2.27
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-07-08 (0 days ago)

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

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

[Touch-packages] [Bug 1780622] [NEW] Audio outpt doesn't match what's selected

[Bret Ancowitz]

Public bug reported:

18.04 Ubuntu Budgie
3.28.1 per software center?

I have three sources of sound output: Laptop speakers, USB headphones,
and speakers plugged into an external monitor via displayport.  On boot,
for example, the headphones are listed as the output source in the
settings menu, but sound is actually going to the displayport speakers.
If I click the speakers, then back to the headphones, all is well.  This
often happens on boot or after resuming from sleep or lock.  Thanks!

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
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  bretaa 2681 F pulseaudio
 /dev/snd/controlC0:  bretaa 2681 F pulseaudio
 /dev/snd/controlC1:  bretaa 2681 F pulseaudio
CurrentDesktop: Budgie:GNOME
Date: Sun Jul  8 08:14:27 2018
InstallationDate: Installed on 2018-05-03 (66 days ago)
InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/29/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.04RSA2
dmi.board.asset.tag: Tag 12345
dmi.board.name: Oryx Pro
dmi.board.vendor: System76, Inc.
dmi.board.version: oryp2-ess
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: System76, Inc.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA2:bd09/29/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2-ess:rvnSystem76,Inc.:rnOryxPro:rvroryp2-ess:cvnSystem76,Inc.:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: Oryx Pro
dmi.product.version: oryp2-ess
dmi.sys.vendor: System76, Inc.

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


** Tags: amd64 apport-bug bionic

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

Title:
  Audio outpt doesn't match what's selected

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  18.04 Ubuntu Budgie
  3.28.1 per software center?

  I have three sources of sound output: Laptop speakers, USB headphones,
  and speakers plugged into an external monitor via displayport.  On
  boot, for example, the headphones are listed as the output source in
  the settings menu, but sound is actually going to the displayport
  speakers.  If I click the speakers, then back to the headphones, all
  is well.  This often happens on boot or after resuming from sleep or
  lock.  Thanks!

  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
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  bretaa 2681 F pulseaudio
   /dev/snd/controlC0:  bretaa 2681 F pulseaudio
   /dev/snd/controlC1:  bretaa 2681 F pulseaudio
  CurrentDesktop: Budgie:GNOME
  Date: Sun Jul  8 08:14:27 2018
  InstallationDate: Installed on 2018-05-03 (66 days ago)
  InstallationMedia: Ubuntu-Budgie 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/29/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05.04RSA2
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: Oryx Pro
  dmi.board.vendor: System76, Inc.
  dmi.board.version: oryp2-ess
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: System76, Inc.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05.04RSA2:bd09/29/2016:svnSystem76,Inc.:pnOryxPro:pvroryp2-ess:rvnSystem76,Inc.:rnOryxPro:rvroryp2-ess:cvnSystem76,Inc.:ct10:cvrN/A:
  dmi.product.family: Not Applicable
  dmi.product.name: Oryx Pro
  dmi.product.version: oryp2-ess
  dmi.sys.vendor: System76, Inc.

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

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

[Alex Murray]

It looks like the ssh server configuration file has become corrupted -
notice the error message:

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

Have you edit this file? Can you please make sure it is valid.

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

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 1780618] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[Dave Dixon]

Public bug reported:

Upgrading from 16.04 to 18.04

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Sun Jul  8 05:09:36 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2017-01-23 (531 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.2.27
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-07-08 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Upgrading from 16.04 to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Jul  8 05:09:36 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-01-23 (531 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.2.27
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-07-08 (0 days ago)

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

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

[Touch-packages] [Bug 1780616] [NEW] package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: triggers looping, abandoned

[Dave Dixon]

Public bug reported:

Upgrading from 16.04 to 18.04.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: fontconfig 2.11.94-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
Uname: Linux 4.4.0-130-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Sun Jul  8 05:09:36 2018
ErrorMessage: triggers looping, abandoned
InstallationDate: Installed on 2017-01-23 (531 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.2.27
SourcePackage: fontconfig
Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
UpgradeStatus: Upgraded to bionic on 2018-07-08 (0 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  New

Bug description:
  Upgrading from 16.04 to 18.04.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: fontconfig 2.11.94-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.4.0-130.156-generic 4.4.134
  Uname: Linux 4.4.0-130-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Sun Jul  8 05:09:36 2018
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2017-01-23 (531 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.2.27
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1.1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to bionic on 2018-07-08 (0 days ago)

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

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

[Touch-packages] [Bug 600758] Re:

[Chris Thompson]

http://centre.joehendricksphotography.com

Chris Thompson

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

Title:
  Updates failing

Status in apt package in Ubuntu:
  Expired

Bug description:
  Binary package hint: apt

  When trying to update and download bug/security fixes I get the follow
  result. This happens with apt-get or update manager

  chris@snoopy:~$ sudo apt-get update
  [sudo] password for chris: 
  Hit http://archive.ubuntu.com lucid Release.gpg
  Ign http://archive.ubuntu.com/ubuntu/ lucid/main Translation-en_US
 
  Ign http://archive.ubuntu.com/ubuntu/ lucid/restricted Translation-en_US  
 
  Ign http://archive.ubuntu.com/ubuntu/ lucid/universe Translation-en_US
  
  Ign http://archive.ubuntu.com/ubuntu/ lucid/multiverse Translation-en_US  
  
  Hit http://archive.ubuntu.com lucid-updates Release.gpg   
  
  Ign http://archive.ubuntu.com/ubuntu/ lucid-updates/main Translation-en_US

  Ign http://archive.ubuntu.com/ubuntu/ lucid-updates/restricted 
Translation-en_US  
  Ign http://archive.ubuntu.com/ubuntu/ lucid-updates/universe 
Translation-en_US
  Ign http://archive.ubuntu.com/ubuntu/ lucid-updates/multiverse 
Translation-en_US  
  Hit http://archive.ubuntu.com lucid-security Release.gpg  

  Ign http://archive.ubuntu.com/ubuntu/ lucid-security/main Translation-en_US   

  Ign http://archive.ubuntu.com/ubuntu/ lucid-security/restricted 
Translation-en_US 
  Ign http://archive.ubuntu.com/ubuntu/ lucid-security/universe 
Translation-en_US   
  Ign http://archive.ubuntu.com/ubuntu/ lucid-security/multiverse 
Translation-en_US 
  Hit http://archive.ubuntu.com lucid Release   

  Hit http://archive.ubuntu.com lucid-updates Release   

  Hit http://archive.ubuntu.com lucid-security Release  
  
  Hit http://archive.ubuntu.com lucid/main Packages 
  
  Hit http://archive.ubuntu.com lucid/restricted Packages   

  Hit http://archive.ubuntu.com lucid/main Sources  

  Hit http://archive.ubuntu.com lucid/restricted Sources

  Hit http://archive.ubuntu.com lucid/universe Packages 

  Hit http://archive.ubuntu.com lucid/universe Sources  

  Hit http://archive.ubuntu.com lucid/multiverse Packages   

  Hit http://archive.ubuntu.com lucid/multiverse Sources

  Hit http://archive.ubuntu.com lucid-updates/main Packages 

  Hit http://archive.ubuntu.com lucid-updates/restricted Packages   

  Hit http://archive.ubuntu.com lucid-updates/main Sources  

  Hit http://archive.ubuntu.com lucid-updates/restricted Sources

  Hit http://archive.ubuntu.com lucid-updates/universe Packages 

  Hit http://archive.ubuntu.com lucid-updates/universe Sources  

  Hit http://archive.ubuntu.com lucid-updates/multiverse Packages   

  Hit http://archive.ubuntu.com lucid-updates/multiverse Sources

  Hit http://archive.ubuntu.com lucid-security/main Packages

  Hit http://archive.ubuntu.com lucid-security/restricted Packages  

  Hit http://archive.ubuntu.com lucid-security/main Sources 

  Hit http://archive.ubuntu.com lucid-security/restricted Sources   

  Hit http://archive.ubuntu.com lucid-security/universe Packages

  Hit http://archive.ubuntu.com lucid-security/universe Sources 

  Hit http://archive.ubuntu.com lucid-security/multiverse Packages  

  Hit http://archive.ubuntu.com lucid-security/multiverse Sources   

  Hit http://packages.medibuntu.org lucid Release.gpg   

  Ign 

[Touch-packages] [Bug 1703479] Re: Ubuntu 17.04 & Kubuntu 17.04 LiveCD writes to bios/hardware clock; thereby messing up my installed Windows 10 Pro laptop time

[Launchpad Bug Tracker]

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

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

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

Title:
  Ubuntu 17.04 & Kubuntu 17.04 LiveCD writes to bios/hardware clock;
  thereby messing up my installed Windows 10 Pro laptop time

Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I created Live USB thumb drives of Ubuntu & Kubuntu 17.04 and when I
  went to try them out, all was fine because the clock displayed in
  Ubuntu & Kubuntu was correct.  I had assumed that Ubuntu & Kubuntu OS
  would assume that it was forbidden to alter the bios/hardware clock
  because that would defeat the entire purpose of a Live environment.

  I had assumed that the two Linux OS would perform a check to see if
  the bios/hardware clock was set to UTC.  If the bios/hardware clock
  was set to UTC then great.  Still the Live OS should not touch the
  bios clock with out permission.  The two Linux OS should via a dialog
  box ask the user if the clock can be changed via ntpdate or ntp and a
  warning that doing so will likely alter the time to an incorrect time
  in Windows.

  If the bios/hardware clock is found to be non-UTC then the two Linux
  OS should simply display that time and not use ntpdate or ntp.  At
  this point if the user wishes to correct the time in the two Linux OS,
  The two Linux OS should warn the user that giving the two Linux OS
  permission to change the time will mess up Windows.

  In an Live environment the bios/hardware clock should never be written
  to, instead only read from and the time simply be an accurate
  reflection of the bios/hardware clock.  Any writing to the
  bios/hardware clock should first be prompted by a permission dialog
  box and it should display a warning that altering the clock in Ubuntu
  & Kubuntu will most likely mess up the time in Windows.

  Upon shutdown of the Live session the Ubuntu & Kubuntu should offer to
  restore the bios/hardware clock to what it was when first booting the
  Live session.

  Inaccurate time in Windows has no doubt it's fair share of problems.
  Accurate time is important and accurate ticking is even more
  important.  The bios/hardware clock should never be written to without
  user permission.

  User permission on Linux is granted by installing ntpdate or ntp and
  possibly the editing of config files.  This can also be done during
  the install process where you choose your timezone and tick the option
  to update time via Internet.

  User permission on Windows is done during install time as well as post
  install fiddling with the time and date settings in Windows.

  Both Linux and Windows fail in warning user about changing
  bios/hardware clock.

  Please do not write to the bios/hardware clock without user permission
  and please display a warning that doing so may adversely affect other
  operating systems.

  I fully expect no surprises when I am done with the live session and I
  boot back into Windows.

  Maybe it's my fault, maybe I changed the clock in the Live session.
  But and But I was never warned that changing the time display in
  Ubuntu & Kubuntu was changing the bios/hardware clock and that my
  Windows OS was all screwed up time wise.

  This is my first Windows computer since I switched to Linux in 1996,
  so maybe I am simply uneducated in how time works in Windows.  I use
  UTC on all my Linux machines.  It's so much easier to use local time
  on Windows.

  I'm happy to help debug.

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

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

[Touch-packages] [Bug 1703479] Re: Ubuntu 17.04 & Kubuntu 17.04 LiveCD writes to bios/hardware clock; thereby messing up my installed Windows 10 Pro laptop time

[David Balažic]

Sorry, I forgot this: Is there a boot option I can set to change this
behavior? Either to use local-time in HW clock or simply prevent writing
to HW clock in live mode?

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

Title:
  Ubuntu 17.04 & Kubuntu 17.04 LiveCD writes to bios/hardware clock;
  thereby messing up my installed Windows 10 Pro laptop time

Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I created Live USB thumb drives of Ubuntu & Kubuntu 17.04 and when I
  went to try them out, all was fine because the clock displayed in
  Ubuntu & Kubuntu was correct.  I had assumed that Ubuntu & Kubuntu OS
  would assume that it was forbidden to alter the bios/hardware clock
  because that would defeat the entire purpose of a Live environment.

  I had assumed that the two Linux OS would perform a check to see if
  the bios/hardware clock was set to UTC.  If the bios/hardware clock
  was set to UTC then great.  Still the Live OS should not touch the
  bios clock with out permission.  The two Linux OS should via a dialog
  box ask the user if the clock can be changed via ntpdate or ntp and a
  warning that doing so will likely alter the time to an incorrect time
  in Windows.

  If the bios/hardware clock is found to be non-UTC then the two Linux
  OS should simply display that time and not use ntpdate or ntp.  At
  this point if the user wishes to correct the time in the two Linux OS,
  The two Linux OS should warn the user that giving the two Linux OS
  permission to change the time will mess up Windows.

  In an Live environment the bios/hardware clock should never be written
  to, instead only read from and the time simply be an accurate
  reflection of the bios/hardware clock.  Any writing to the
  bios/hardware clock should first be prompted by a permission dialog
  box and it should display a warning that altering the clock in Ubuntu
  & Kubuntu will most likely mess up the time in Windows.

  Upon shutdown of the Live session the Ubuntu & Kubuntu should offer to
  restore the bios/hardware clock to what it was when first booting the
  Live session.

  Inaccurate time in Windows has no doubt it's fair share of problems.
  Accurate time is important and accurate ticking is even more
  important.  The bios/hardware clock should never be written to without
  user permission.

  User permission on Linux is granted by installing ntpdate or ntp and
  possibly the editing of config files.  This can also be done during
  the install process where you choose your timezone and tick the option
  to update time via Internet.

  User permission on Windows is done during install time as well as post
  install fiddling with the time and date settings in Windows.

  Both Linux and Windows fail in warning user about changing
  bios/hardware clock.

  Please do not write to the bios/hardware clock without user permission
  and please display a warning that doing so may adversely affect other
  operating systems.

  I fully expect no surprises when I am done with the live session and I
  boot back into Windows.

  Maybe it's my fault, maybe I changed the clock in the Live session.
  But and But I was never warned that changing the time display in
  Ubuntu & Kubuntu was changing the bios/hardware clock and that my
  Windows OS was all screwed up time wise.

  This is my first Windows computer since I switched to Linux in 1996,
  so maybe I am simply uneducated in how time works in Windows.  I use
  UTC on all my Linux machines.  It's so much easier to use local time
  on Windows.

  I'm happy to help debug.

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

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

[Touch-packages] [Bug 1703479] Re: Ubuntu 17.04 & Kubuntu 17.04 LiveCD writes to bios/hardware clock; thereby messing up my installed Windows 10 Pro laptop time

[David Balažic]

This also happens with 18.04.

 - have hw clock on local time (other timezone than UTC+0)
 - have a working ethernet connection (DHCP, with internet connection)
 - boot ubuntu-18.04-desktop-amd64.iso from a DVD (boy, does it takes it's 
time...)
 - optionally reboot into Windows
 - check time: it is set to UTC in HW clock, which means wrong clock in Windows

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

Title:
  Ubuntu 17.04 & Kubuntu 17.04 LiveCD writes to bios/hardware clock;
  thereby messing up my installed Windows 10 Pro laptop time

Status in ntp package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I created Live USB thumb drives of Ubuntu & Kubuntu 17.04 and when I
  went to try them out, all was fine because the clock displayed in
  Ubuntu & Kubuntu was correct.  I had assumed that Ubuntu & Kubuntu OS
  would assume that it was forbidden to alter the bios/hardware clock
  because that would defeat the entire purpose of a Live environment.

  I had assumed that the two Linux OS would perform a check to see if
  the bios/hardware clock was set to UTC.  If the bios/hardware clock
  was set to UTC then great.  Still the Live OS should not touch the
  bios clock with out permission.  The two Linux OS should via a dialog
  box ask the user if the clock can be changed via ntpdate or ntp and a
  warning that doing so will likely alter the time to an incorrect time
  in Windows.

  If the bios/hardware clock is found to be non-UTC then the two Linux
  OS should simply display that time and not use ntpdate or ntp.  At
  this point if the user wishes to correct the time in the two Linux OS,
  The two Linux OS should warn the user that giving the two Linux OS
  permission to change the time will mess up Windows.

  In an Live environment the bios/hardware clock should never be written
  to, instead only read from and the time simply be an accurate
  reflection of the bios/hardware clock.  Any writing to the
  bios/hardware clock should first be prompted by a permission dialog
  box and it should display a warning that altering the clock in Ubuntu
  & Kubuntu will most likely mess up the time in Windows.

  Upon shutdown of the Live session the Ubuntu & Kubuntu should offer to
  restore the bios/hardware clock to what it was when first booting the
  Live session.

  Inaccurate time in Windows has no doubt it's fair share of problems.
  Accurate time is important and accurate ticking is even more
  important.  The bios/hardware clock should never be written to without
  user permission.

  User permission on Linux is granted by installing ntpdate or ntp and
  possibly the editing of config files.  This can also be done during
  the install process where you choose your timezone and tick the option
  to update time via Internet.

  User permission on Windows is done during install time as well as post
  install fiddling with the time and date settings in Windows.

  Both Linux and Windows fail in warning user about changing
  bios/hardware clock.

  Please do not write to the bios/hardware clock without user permission
  and please display a warning that doing so may adversely affect other
  operating systems.

  I fully expect no surprises when I am done with the live session and I
  boot back into Windows.

  Maybe it's my fault, maybe I changed the clock in the Live session.
  But and But I was never warned that changing the time display in
  Ubuntu & Kubuntu was changing the bios/hardware clock and that my
  Windows OS was all screwed up time wise.

  This is my first Windows computer since I switched to Linux in 1996,
  so maybe I am simply uneducated in how time works in Windows.  I use
  UTC on all my Linux machines.  It's so much easier to use local time
  on Windows.

  I'm happy to help debug.

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

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

[Touch-packages] [Bug 1780612] [NEW] package libfaad2:amd64 2.8.8-1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato installarlo nuovamente prima

[Francesco Peverelli]

Public bug reported:

i have no idea

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: libfaad2:amd64 2.8.8-1
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: Sun Jul  8 12:30:42 2018
Dependencies:
 gcc-8-base 8-20180414-1ubuntu2
 libc6 2.27-3ubuntu1
 libgcc1 1:8-20180414-1ubuntu2
ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
InstallationDate: Installed on 2017-12-26 (193 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
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
SourcePackage: faad2
Title: package libfaad2:amd64 2.8.8-1 failed to install/upgrade: il pacchetto 
si trova in uno stato di inconsistenza critico: è consigliato  installarlo 
nuovamente prima di tentare la configurazione.
UpgradeStatus: Upgraded to bionic on 2018-05-05 (63 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package libfaad2:amd64 2.8.8-1 failed to install/upgrade: il pacchetto
  si trova in uno stato di inconsistenza critico: è consigliato
  installarlo nuovamente prima di tentare la configurazione.

Status in faad2 package in Ubuntu:
  New

Bug description:
  i have no idea

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfaad2:amd64 2.8.8-1
  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: Sun Jul  8 12:30:42 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
  ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
  InstallationDate: Installed on 2017-12-26 (193 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  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
  SourcePackage: faad2
  Title: package libfaad2:amd64 2.8.8-1 failed to install/upgrade: il pacchetto 
si trova in uno stato di inconsistenza critico: è consigliato  installarlo 
nuovamente prima di tentare la configurazione.
  UpgradeStatus: Upgraded to bionic on 2018-05-05 (63 days ago)

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

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

Partially working here on fully updated Ubuntu 18.04 Server on
VirtualBox :(

I've enabled -proposed repo and updated both nplan/bionic-proposed and
netplan.ion/bionic-proposed packages.

Now interfaces got renamed, but IPs are not assigned at boot (both DHCP and 
static ones).
Calling "netplan generate && netplan apply" after boot only sets the static IPs 
while DHCP still remains unset.


# dpkg -s netplan.io
Package: netplan.io
Status: install ok installed
Priority: important
Section: net
Architecture: amd64
Version: 0.36.3

# cat /etc/netplan/01-netcfg.yaml
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

*** (just after boot) ***
# ifconfig -a
eth_dhcp: flags=4098  mtu 1500
ether 08:00:27:23:68:f5  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth_static: flags=4098  mtu 1500
ether 08:00:27:6b:d8:91  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 2  bytes 78 (78.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2  bytes 78 (78.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


*** (after "netplan apply") ***
eth_dhcp: flags=4098  mtu 1500
ether 08:00:27:23:68:f5  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth_static: flags=4098  mtu 1500
inet 1.2.3.4  netmask 255.255.0.0  broadcast 1.2.255.255
inet6 fe80::a00:27ff:fe6b:d891  prefixlen 64  scopeid 0x20
ether 08:00:27:6b:d8:91  txqueuelen 1000  (Ethernet)
RX packets 0  bytes 0 (0.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 0  bytes 0 (0.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1000  (Local Loopback)
RX packets 2  bytes 78 (78.0 B)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 2  bytes 78 (78.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


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

** Tags removed: verification-needed

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

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

[Aleksander Morgado]

Public bug reported:

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

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

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

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

Status in network-manager package in Ubuntu:
  New

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 1775392] Re: at-spi-bus-launcher makes Xorg crash when resuming from suspend

[Launchpad Bug Tracker]

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

** Changed in: at-spi2-core (Ubuntu)
   Status: New => Confirmed

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

Title:
  at-spi-bus-launcher makes Xorg crash when resuming from suspend

Status in at-spi2-core package in Ubuntu:
  Confirmed

Bug description:
  If at-spi2-core is installed, when resuming from suspend messages like
  these are logged in systemd journal:

  at-spi-bus-launcher[31720]: XIO:  fatal IO error 11 (Resource temporarily 
unavailable) on X server ":0.0"
  at-spi-bus-launcher[31720]:   after 8065 requests (8065 known processed) 
with 0 events remaining.

  The number of requests vary, it can reach more than 15000. Depending
  on the number of requests, the Xorg server crashes with SIGBUS.
  Depending on the exact moment Xorg crashes, when lightdm manages to
  recover, it shows a login greeter, or worst case scenario, it can't
  recover, a black screen is shown and the desptop session doesn't
  start.

  It took me a long time to discover the cause. The visible symptom was:
  once in a while when resuming from suspend, I got a login greeter
  instead of an unlock greeter, or a black screen which forced me to
  power down. Investigating, I found out that whenever that happened,
  there was a Xorg core left behind. Looking at the journal messages
  before the crash, there was always that flood of at-spi2-core
  requests. So I uninstalled at-spi2-core and Xorg never crashed
  anymore.

  This is a quite severe bug, which makes it impossible to use at-
  spi2-core.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: at-spi2-core (not installed)
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jun  6 09:10:12 2018
  InstallationDate: Installed on 2018-04-28 (38 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  SourcePackage: at-spi2-core
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1775392/+subscriptions

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

[Touch-packages] [Bug 1772629] Re: Automatic logout when resuming from suspend on Xubuntu 18.04

[Launchpad Bug Tracker]

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

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

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

Title:
  Automatic logout when resuming from suspend on Xubuntu 18.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  When my Xubuntu 18.04 laptop resumes from suspend, systemd-logind
  automatically logs out of the current session if the laptop has stayed
  suspended for more than a couple of hours. If the interval between
  suspend and resume is short, it doesn't log out. I still haven't
  discovered how long this interval has to be in order to cause the
  logout.

  I enabled debug on the systemd-logind.service, creating file
  _/etc/systemd/system/systemd-logind.service.d/10-debug.conf_:

  [Service]
  Environment=SYSTEMD_LOG_LEVEL=debug

  which causes systemd-logind to log all D-Bus messages it handles, but
  couldn't spot anything that might have caused the logout.

  I scanned all systemd journal messages (`journalctl`) before systemd-
  logind starts killing the current session, investigated all that
  looked suspicious but couldn't find anything that might influence an
  automatic logout. Here are some of the messages that striked me as
  suspicious (they are not sequential, but pulled from different
  occasions):

  upowerd[1600]: unhandled action 'unbind' on 
/sys/devices/pci:00/:00:1a.0/usb1/1-1/1-1.4/1-1.4:1.0
  polkitd(authority=local)[840]: Unregistered Authentication Agent for 
unix-session:c2 (system bus name :1.46, object path 
/org/gnome/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected 
from bus)
  wpa_supplicant[811]: dbus: fill_dict_with_properties 
dbus_interface=fi.w1.wpa_supplicant1.Interface dbus_property=Stations getter 
failed
  wpa_supplicant[811]: dbus: wpa_dbus_get_object_properties: failed to get 
object properties: (none) none
  at-spi-bus-launcher[7031]: XIO:  fatal IO error 11 (Resource temporarily 
unavailable) on X server ":0.0"
  at-spi-bus-launcher[7031]:   after 30333 requests (30333 known processed) 
with 0 events remaining.
  systemd-logind[779]: Inhibitor xfce4-power-manager (xfce4-power-manager 
handles these events) pid=8611 uid=1000 mode=block stopped
  systemd-logind[779]: Electing new display for user paulo
  systemd-logind[779]: Ignoring session c8

  logind config doesn't have anything that might cause this:

  paulo:~$ loginctl show-session
  EnableWallMessages=no
  NAutoVTs=6
  KillUserProcesses=no
  RebootToFirmwareSetup=no
  IdleHint=no
  IdleSinceHint=0
  IdleSinceHintMonotonic=0
  BlockInhibited=handle-power-key:handle-suspend-key:handle-hibernate-key
  DelayInhibited=sleep
  InhibitDelayMaxUSec=5s
  HandlePowerKey=poweroff
  HandleSuspendKey=suspend
  HandleHibernateKey=hibernate
  HandleLidSwitch=suspend
  HandleLidSwitchDocked=ignore
  HoldoffTimeoutUSec=30s
  IdleAction=ignore
  IdleActionUSec=30min
  PreparingForShutdown=no
  PreparingForSleep=no
  Docked=no
  RemoveIPC=yes
  RuntimeDirectorySize=615313408
  InhibitorsMax=8192
  NCurrentInhibitors=5
  SessionsMax=8192
  NCurrentSessions=1
  UserTasksMax=10813

  I can't find any anything that might cause an automatic logout after a
  time interval. I'm really stumped.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  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
  CurrentDesktop: XFCE
  Date: Tue May 22 07:36:59 2018
  InstallationDate: Installed on 2018-04-28 (23 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Inspiron N5110
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=c4c2d11a-634c-4105-9991-e2fb5c18e1dc ro net.ifnames=0 quiet splash 
vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 08FDW5
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A06
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd05/26/2011:svnDellInc.:pnInspironN5110:pvrNotSpecified:rvnDellInc.:rn08FDW5:rvrA06:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron N5110
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.

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

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