[Touch-packages] [Bug 1779638] [NEW] package python3-software-properties 0.96.24.32.3 failed to install/upgrade: installed python3-software-properties package post-installation script subprocess retur

[Kakaový Venček]

Public bug reported:

i was installing system update after fresh installation of ubuntu 18.04
aaand the installtion returned and error saying that that package failed
to install, thats all i know

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: python3-software-properties 0.96.24.32.3
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.2
Architecture: amd64
Date: Mon Jul  2 11:58:08 2018
DuplicateSignature:
 package:python3-software-properties:0.96.24.32.3
 Setting up python3-software-properties (0.96.24.32.3) ...
 Segmentation fault (core dumped)
 dpkg: error processing package python3-software-properties (--configure):
  installed python3-software-properties package post-installation script 
subprocess returned error exit status 139
ErrorMessage: installed python3-software-properties package post-installation 
script subprocess returned error exit status 139
InstallationDate: Installed on 2018-07-02 (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.1
SourcePackage: software-properties
Title: package python3-software-properties 0.96.24.32.3 failed to 
install/upgrade: installed python3-software-properties package 
post-installation script subprocess returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package python3-software-properties 0.96.24.32.3 failed to
  install/upgrade: installed python3-software-properties package post-
  installation script subprocess returned error exit status 139

Status in software-properties package in Ubuntu:
  New

Bug description:
  i was installing system update after fresh installation of ubuntu
  18.04 aaand the installtion returned and error saying that that
  package failed to install, thats all i know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-software-properties 0.96.24.32.3
  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.2
  Architecture: amd64
  Date: Mon Jul  2 11:58:08 2018
  DuplicateSignature:
   package:python3-software-properties:0.96.24.32.3
   Setting up python3-software-properties (0.96.24.32.3) ...
   Segmentation fault (core dumped)
   dpkg: error processing package python3-software-properties (--configure):
installed python3-software-properties package post-installation script 
subprocess returned error exit status 139
  ErrorMessage: installed python3-software-properties package post-installation 
script subprocess returned error exit status 139
  InstallationDate: Installed on 2018-07-02 (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.1
  SourcePackage: software-properties
  Title: package python3-software-properties 0.96.24.32.3 failed to 
install/upgrade: installed python3-software-properties package 
post-installation script subprocess returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1779638] Re: package python3-software-properties 0.96.24.32.3 failed to install/upgrade: installed python3-software-properties package post-installation script subprocess returne

[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 software-properties in
Ubuntu.
https://bugs.launchpad.net/bugs/1779638

Title:
  package python3-software-properties 0.96.24.32.3 failed to
  install/upgrade: installed python3-software-properties package post-
  installation script subprocess returned error exit status 139

Status in software-properties package in Ubuntu:
  New

Bug description:
  i was installing system update after fresh installation of ubuntu
  18.04 aaand the installtion returned and error saying that that
  package failed to install, thats all i know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: python3-software-properties 0.96.24.32.3
  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.2
  Architecture: amd64
  Date: Mon Jul  2 11:58:08 2018
  DuplicateSignature:
   package:python3-software-properties:0.96.24.32.3
   Setting up python3-software-properties (0.96.24.32.3) ...
   Segmentation fault (core dumped)
   dpkg: error processing package python3-software-properties (--configure):
installed python3-software-properties package post-installation script 
subprocess returned error exit status 139
  ErrorMessage: installed python3-software-properties package post-installation 
script subprocess returned error exit status 139
  InstallationDate: Installed on 2018-07-02 (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.1
  SourcePackage: software-properties
  Title: package python3-software-properties 0.96.24.32.3 failed to 
install/upgrade: installed python3-software-properties package 
post-installation script subprocess returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1235245] Re: upstart-monitor cannot run without gtk libraries installed

[Cameron Norman]

** Attachment added: "lp.1235245"
   
https://bugs.launchpad.net/upstart/+bug/1235245/+attachment/5158612/+files/lp.1235245

** Changed in: upstart
 Assignee: (unassigned) => Cameron Norman (cameronnemo)

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

Title:
  upstart-monitor cannot run without gtk libraries installed

Status in upstart :
  New
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  "upstart-monitor -n" should revert to cli operation. It attempts to do
  this, but then barfs on class UpstartEventsGui(Gtk.Window) since Gtk
  is not imported unless the required gtk libraries are installed.

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

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

[Touch-packages] [Bug 1779657] [NEW] apt autoremove not removing old kernels

[Vasya Pupkin]

Public bug reported:

I noticed that apt autoremove stopped removing old kernels recently.
Currently I have 6 installed and apt autoremove does not try to remove
old ones:

$ sudo apt autoremove --purge 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

In /etc/apt/apt.conf.d/01autoremove-kernels it is said to only keep last
three versions:

# list of different kernel versions:
4.15.0-24.26~16.04.1
4.15.0-23.25~16.04.1
4.15.0-22.24~16.04.1
4.15.0-15.16~16.04.1
4.13.0-45.50~16.04.1
4.13.0-43.48~16.04.1
# Installing kernel: 4.13.0-45.50~16.04.1 (4.13.0-45-generic)
# Running kernel: 4.15.0-23.25~16.04.1 (4.15.0-23-generic)
# Last kernel: 4.15.0-24.26~16.04.1
# Previous kernel: 4.15.0-23.25~16.04.1
# Kernel versions list to keep:
4.13.0-45.50~16.04.1
4.15.0-23.25~16.04.1
4.15.0-24.26~16.04.1
# Kernel packages (version part) to protect:
4\.13\.0-45-generic
4\.15\.0-23-generic
4\.15\.0-24-generic

It was working fine previously and I didn't change anything that could
break this functionality.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: apt 1.2.26
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
CurrentDesktop: Unity
Date: Mon Jul  2 14:12:03 2018
InstallationDate: Installed on 2018-01-19 (164 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
SourcePackage: apt
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Summary changed:

- apt autoremove not removing old 4.15 kernels
+ apt autoremove not removing old kernels

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

Title:
  apt autoremove not removing old kernels

Status in apt package in Ubuntu:
  New

Bug description:
  I noticed that apt autoremove stopped removing old kernels recently.
  Currently I have 6 installed and apt autoremove does not try to remove
  old ones:

  $ sudo apt autoremove --purge 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

  In /etc/apt/apt.conf.d/01autoremove-kernels it is said to only keep
  last three versions:

  # list of different kernel versions:
  4.15.0-24.26~16.04.1
  4.15.0-23.25~16.04.1
  4.15.0-22.24~16.04.1
  4.15.0-15.16~16.04.1
  4.13.0-45.50~16.04.1
  4.13.0-43.48~16.04.1
  # Installing kernel: 4.13.0-45.50~16.04.1 (4.13.0-45-generic)
  # Running kernel: 4.15.0-23.25~16.04.1 (4.15.0-23-generic)
  # Last kernel: 4.15.0-24.26~16.04.1
  # Previous kernel: 4.15.0-23.25~16.04.1
  # Kernel versions list to keep:
  4.13.0-45.50~16.04.1
  4.15.0-23.25~16.04.1
  4.15.0-24.26~16.04.1
  # Kernel packages (version part) to protect:
  4\.13\.0-45-generic
  4\.15\.0-23-generic
  4\.15\.0-24-generic

  It was working fine previously and I didn't change anything that could
  break this functionality.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apt 1.2.26
  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
  CurrentDesktop: Unity
  Date: Mon Jul  2 14:12:03 2018
  InstallationDate: Installed on 2018-01-19 (164 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1779658] [NEW] Dropping to shell twice crashes system

[Tobias]

Public bug reported:

If you have an X session open, and you drop to shell using ctrl+alt+fN (e.g. ctrl+alt+f6), return to X session using ctrl+alt+f2 (or f1), and 
repeat once more:
Expected result:
- Normal functioning X session
Real result:
- No interaction with the system possible anymore.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
Uname: Linux 4.15.0-23-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..25.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:25: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)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jul  2 13:24:01 2018
DistUpgraded: 2018-06-06 15:37:57,793 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
 nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
 virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050] [1458:3747]
InstallationDate: Installed on 2018-02-22 (129 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
MachineType: Micro-Star International Co., Ltd. MS-7A34
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=6c4a23a4-85d5-4ec4-b6f1-cfececbb0353 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-06-06 (25 days ago)
dmi.bios.date: 09/19/2017
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.90
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: B350 TOMAHAWK (MS-7A34)
dmi.board.vendor: Micro-Star International Co., Ltd.
dmi.board.version: 1.0
dmi.chassis.asset.tag: To be filled by O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: Micro-Star International Co., Ltd.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd09/19/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
dmi.product.family: To be filled by O.E.M.
dmi.product.name: MS-7A34
dmi.product.version: 1.0
dmi.sys.vendor: Micro-Star International Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.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/1779658

Title:
  Dropping to shell twice crashes system

Status in xorg package in Ubuntu:
  New

Bug description:
  If you have an X session open, and you drop to shell using ctrl+alt+fN (e.g. ctrl+alt+f6), return to X session using ctrl+alt+f2 (or f1), and 
repeat once more:
  Expected result:
  - Normal functioning X session
  Real result:
  - No interaction with the system possible anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..25.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:25:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 

[Touch-packages] [Bug 1772844] Re: snapd didn't initialize all the seeded snaps

[Chen-Han Hsiao (Stanley)]

** Changed in: oem-priority
   Status: Confirmed => Fix Released

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

Title:
  snapd didn't initialize all the seeded snaps

Status in OEM Priority Project:
  Fix Released
Status in snapd:
  New
Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  snapd didn't initialize all the seeded snaps

  bionic-desktop-amd64.iso (20180522)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: snapd 2.32.9+18.04
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May 22 22:59:18 2018
  InstallationDate: Installed on 2018-05-23 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180522)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1772844/+subscriptions

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

[Touch-packages] [Bug 1779129] Re: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package libfdisk1:amd64 is not ready for conf

[Julian Andres Klode]

In order to debug this further, we need a copy of /var/log/apt/term.log.

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

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

Title:
  package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: lib/x86_64-linux-
  gnu/libfdisk.so.1.1.0] failed to install/upgrade: package
  libfdisk1:amd64 is not ready for configuration  cannot configure
  (current status 'half-installed')

Status in apt package in Ubuntu:
  Incomplete

Bug description:
  i was installing latex-maker and as it ended i got that error.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: 
lib/x86_64-linux-gnu/libfdisk.so.1.1.0]
  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
  Architecture: amd64
  Date: Thu Jun 28 07:03:23 2018
  DpkgTerminalLog:
   dpkg: error processing package libfdisk1:amd64 (--configure):
package libfdisk1:amd64 is not ready for configuration
cannot configure (current status 'half-installed')
  ErrorMessage: package libfdisk1:amd64 is not ready for configuration  cannot 
configure (current status 'half-installed')
  InstallationDate: Installed on 2018-06-18 (10 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: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] No such file or directory: "/root/Error: command ['which', 
'python'] failed with exit code 1:": "/root/Error: command ['which', 'python'] 
failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: util-linux
  Title: package libfdisk1:amd64 2.31.1-0.4ubuntu3 [modified: 
lib/x86_64-linux-gnu/libfdisk.so.1.1.0] failed to install/upgrade: package 
libfdisk1:amd64 is not ready for configuration  cannot configure (current 
status 'half-installed')
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1651818] Re: busybox-initramfs needs different compile options to work with cryptroot-unlock

[Joachim Gehrung]

I would also be interested to see this bug fixed in Bionic.

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

Title:
  busybox-initramfs needs different compile options to work with
  cryptroot-unlock

Status in busybox package in Ubuntu:
  Won't Fix
Status in cryptsetup package in Ubuntu:
  Fix Released
Status in cryptsetup source package in Bionic:
  Confirmed

Bug description:
  The cryptroot-unlock script in the cryptsetup package does not work in 
initramfs.
  It fails because "ps -e" is not available in busybox for initramfs.
  When building the package with

  CONFIG_DESKTOP=y
  CONFIG_EXTRA_COMPAT=y

  the needed commands (ps, grep) with parameter are there and it works.
  Tetsted on Ubuntu GNOME 16.10.

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

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

[Touch-packages] [Bug 710618] Re: Please support libkibi

[Julian Andres Klode]

Won't fix as before

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

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

Title:
  Please support libkibi

Status in apt package in Ubuntu:
  Won't Fix

Bug description:
  Binary package hint: apt

  Please support libkibi [1] for displaying sizes.

  SizeToStr (in apt-pkg/contrib/strutl.cc) should be modified to call
  kibi_format_size or kibi_n_format_size.

  [1] https://launchpad.net/libkibi

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

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

[Touch-packages] [Bug 184354] Re: apt should honor http 302 (was: http 302 status reported as error)

[Julian Andres Klode]

Closed as it has been fixed as mentioned in previous comment.

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

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

Title:
  apt should honor http 302 (was: http 302 status reported as error)

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Binary package hint: update-manager

  adept_updater launches Distribution Upgrade tool for "Upgrading
  Kubuntu to Version 7.10"  During the Preparing the upgrade step it
  reports "Errror during update  A problem occured during the update.
  This is usually some sort of network problem, please check your
  network connection and retry."

  The listed errors are:
  Failed to fetch 
http://medibuntu.sos-sts.com/repo/dists/feisty/free/binary-i386/Packages.gz 302 
Found
  Failed to fetch 
http://medibuntu.sos-sts.com/repo/dists/feisty/non-free/binary-i386/Packages.gz 
302 Found
  Failed to fetch 
http://medibuntu.sos-sts.com/repo/dists/feisty/free/source/Sources.gz 302 Found
  Failed to fetch 
http://medibuntu.sos-sts.com/repo/dists/feisty/non-free/source/Sources.gz 302 
Found

  302 responses are http temporary redirects, the Distribution upgrade
  tool should fetch the package from the redirected location and go on
  its way.  There is no error to present to the user.

  After closing the error dialog, the program exits.  The 302 responses
  are preventing a successful upgrade.

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

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

[Touch-packages] [Bug 1766307] Re: Crash low-graphics mode

[Rogério Nunes Wolff]

I've updated my Ubuntu every day and this bug continues.

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

Title:
  Crash low-graphics mode

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Since friday, 4/20/2018, when I did an upgrade in Ubuntu, I receive an
  error message:

  The system is running in low-graphics mode

  Your screen, graphics cards, and input device settings could not
  be detected correctly. You will need to configure these yourself.

  Then, using tab key, I press OK, then I choose try the default, and
  everything works fine after this. But this is very annoying.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-39-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  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 Apr 23 13:54:49 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-304, 304.135, 4.13.0-38-generic, x86_64: installed
   nvidia-304, 304.135, 4.13.0-39-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] 2nd Generation Core 
Processor Family Integrated Graphics Controller [1462:7788]
  InstallationDate: Installed on 2017-09-14 (221 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 002 Device 003: ID 04b3:310c IBM Corp. Wheel Mouse
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: MSI MS-7788
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-39-generic 
root=UUID=2f8e3cb0-6af1-44b7-b3fa-ea29171c708d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/18/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: V2.3
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H61M-P31 (G3) (MS-7788)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrV2.3:bd01/18/2012:svnMSI:pnMS-7788:pvr1.0:rvnMSI:rnH61M-P31(G3)(MS-7788):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7788
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  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: Mon Apr 23 12:51:59 2018
  xserver.configfile: default
  xserver.devices:

  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:

  xserver.version: 2:1.19.5-0ubuntu2~16.04.1

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

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

[Touch-packages] [Bug 948461] Re: apt-get hashsum/size mismatch because s3 mirrors don't support http pipelining correctly

[Julian Andres Klode]

This was fixed in 1.1 or later, not entirely sure about the exact
version.

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

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

Title:
  apt-get hashsum/size mismatch because s3 mirrors don't support http
  pipelining correctly

Status in apt package in Ubuntu:
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in apt source package in Lucid:
  Won't Fix
Status in cloud-init source package in Lucid:
  Fix Released
Status in apt source package in Maverick:
  Won't Fix
Status in cloud-init source package in Maverick:
  Fix Released
Status in apt source package in Natty:
  Won't Fix
Status in cloud-init source package in Natty:
  Fix Released
Status in apt source package in Oneiric:
  Won't Fix
Status in cloud-init source package in Oneiric:
  Fix Released
Status in apt source package in Precise:
  Won't Fix
Status in cloud-init source package in Precise:
  Fix Released
Status in apt source package in Hardy:
  Won't Fix
Status in cloud-init source package in Hardy:
  Won't Fix

Bug description:
  [Problem]
  When using S3 mirrors, the apt client requests files A,B,C,D in the same 
request, but S3 responds with files B,C,D,A or some other arbitrary ordering.  
Apt then saves the files under the wrong file names.

  This is due to a bug in Amazon AWS S3, where http pipelining does not
  work in violation of RFC 2068.  apt uses http pipelining currently, so
  this prevents apt from using mirrors hosted on S3 cloud instances.

  [Impact]
  Blocks use of S3 mirrors for providing ubuntu updates.  Affects Hardy, Lucid, 
Maverick, Oneiric, Natty, and Precise.

  Use of S3 mirrors is considered as a way of enhancing our mirror
  services.  Currently mirrors have moments of instability, so having
  the option of switching to S3 mirrors is very important for update
  reliability.

  [Development Fix]
  Fixed in Precise's cloud-init as of these comments, which adds an 
apt_pipelining option, turned off by default but configurable.
  http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/536
  http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/revision/537

  [Stable Fix]
  TODO

  [Text Case]
  1) Launch an instance in EC2
  2) Run: sed -i 
"s,ec2.archive.ubuntu.com,ec2.archive.ubuntu.com.s3.amazonaws.com,g" 
/etc/apt/sources.list
  3.) Set your apt debug levels to whatever you want
  4) Run "apt-get -y update"
  5) Run "apt-get -y install firefox xorg libreoffice > /tmp/install.log 2>&1"
  Broken Behavior:  Cached files are being misnamed
  Fixed Behavior:  Cached files are properly named

  The S3 EC2 mirrors seem to reproduce it most reliably.   The
  downloaded files are whole and match the proper checksums, but they
  have the wrong content.

  [Regression Potential]
  http pipelining is an optimization technique in apt which allows multiple 
requests to be made at the same time.  When it works, it provides a small 
performance boost, but when it doesn't the failures are arbitrary and not 
adequately explained.

  Thus, the expected regression is slightly slower apt behavior for
  non-S3 cloud users.  However, testing shows the impact is less than a
  few seconds so will likely be unnoticed.  In the off chance that it
  does inadvertently cause non-trivial performance impact, the change is
  configurable on a per-host instance.

  [Original Report]
  [SRU: Cloud-Init]
  r536 and r537 contains a fix that:
    1.) Disables APT pipelining on first boot for new Cloud Images instances
    2.) Disables APT pipelining on installation for existing cloud-images.

  The rational for this SRU is due to the Mirror situation for EC2 Cloud
  images. Currently, the mirrors are proving to have moments of
  instability that is causing both end-user and development pain. In
  order to address this, we built out Amazon AWS S3 mirrors.
  Unfortantly, due to a bug in S3, apt http pipeling does not work with
  S3. As a result, in order to provide enhanced availability for the
  Cloud Image repositories in EC2, apt http pipelining needs to be
  disabled ahead of flipping the new S3 mirrors as the active mirrors.

  The performance impact of this change is unnoticable and in testing,
  has proven to provide no ill effect. http pipeplining allows for
  multiple requests to be made at the same time. The apt change log
  states that http pipelining is a "micro-enhancement" and within the
  EC2 environment shaves a few seconds of many requests. When apt http
  pipeling works, at best, it saves a few seconds, when it fails against
  a buggy HTTP1.1 server or behind a proxy that does not support it, the
  failures are arbitrary and not adiquetly explained. This change will
  enhance the Cloud Images by making apt request packages sequentially
  instead of in batches and prevent arbitrary failures caused 

[Touch-packages] [Bug 849736] Re: apt-cache policy silently shows inaccurate information when any file in /etc/apt/sources.list.d is unreadable

[Julian Andres Klode]

We made things work better for unreadable files, so I think that's fixed
in cosmic and probably bionic.

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

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

Title:
  apt-cache policy silently shows inaccurate information when any file
  in /etc/apt/sources.list.d is unreadable

Status in apt package in Ubuntu:
  Fix Released

Bug description:
  Version: 0.8.16~exp5ubuntu8
  Release:  11.10

  I've noticed some odd behaviour from apt-cache policy where it
  pretends, without protest, that package versions in PPAs don't exist.

  The trigger seems to be a newly-added source whose .list file I set up
  to be only readable by root (it contains authentication information).

  When any file in /etc/apt/sources.list.d is unreadable, apt-cache
  won't try to read further files, and it also apparently discards
  information from any of the files it did manage to read.  (Assuming it
  reads them as it goes — I was only tracing calls to open(2).)

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

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

[Touch-packages] [Bug 1275787] Re: apt does not declare all the symbols, others get auto-added with the most current version

[Julian Andres Klode]

I think we have gotten better at this, but it seems pointless to
constantly keep a bug open here. When we add a new symbol it is usually
not used by anything and it will eventually get added to the file.

If there are any specific instances where packages use new symbols we do
not declare, file a bug about these specific issues.

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

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

Title:
  apt does not declare all the symbols, others get auto-added with the
  most current version

Status in apt package in Ubuntu:
  Invalid

Bug description:
  (You can disregard the old version in this, that's just due to my
  environment. It also applies to the current version in precise.)

  It seems that apt does not declare all the symbols it exports and does
  not fail on symbol file mismatches. Hence the new symbols are
  automatically added with the most current version used at time of
  build, even if they were already available previously. This means that
  if you fork apt on your system, you need to needlessly rebuild python-
  apt whenever it depends on a newer version in the base distribution.
  The obvious fix is to add all the symbols and fail whenever there is a
  mismatch and new ones popped up. Like this the symbols file is
  basically useless because you will always find some functions that
  need the most current version.

   _Z11SHA256_DataPKhmPc@Base 0.8.16~exp12ubuntu10.10
   _Z11SHA384_DataPKhmPc@Base 0.8.16~exp12ubuntu10.10
   _Z11SHA512_DataPKhmPc@Base 0.8.16~exp12ubuntu10.10
   _Z13SHA256_UpdateP11_SHA256_CTXPKhm@Base 0.8.16~exp12ubuntu10.10
   _Z13SHA384_UpdateP11_SHA512_CTXPKhm@Base 0.8.16~exp12ubuntu10.10
   _Z13SHA512_UpdateP11_SHA512_CTXPKhm@Base 0.8.16~exp12ubuntu10.10
   _Z19GetListOfFilesInDirRKSsb@Base 0.8.16~exp12ubuntu10.10
   
_Z22IsDuplicateDescriptionN8pkgCache12DescIteratorERK12HashSumValueILi128EERKSs@Base
 0.8.16~exp12ubuntu10.10
   _Z31StartsWithGPGClearTextSignatureRKSs@Base 0.8.16~exp12ubuntu10.10
   _Z6SigINTi@Base 0.8.16~exp12ubuntu10.10
   _ZN17pkgCacheGenerator14MergeListGroupERNS_10ListParserERKSs@Base 
0.8.16~exp12ubuntu10.10
   
_ZN17pkgCacheGenerator16MergeListPackageERNS_10ListParserERN8pkgCache11PkgIteratorE@Base
 0.8.16~exp12ubuntu10.10
   
_ZN17pkgCacheGenerator16MergeListVersionERNS_10ListParserERN8pkgCache11PkgIteratorERKSsRPNS2_11VerIteratorE@Base
 0.8.16~exp12ubuntu10.10
   
_ZN17pkgCacheGenerator18AddImplicitDependsERN8pkgCache11GrpIteratorERNS0_11PkgIteratorERNS0_11VerIteratorE@Base
 0.8.16~exp12ubuntu10.10
   
_ZN17pkgCacheGenerator18AddImplicitDependsERN8pkgCache11VerIteratorERNS0_11PkgIteratorE@Base
 0.8.16~exp12ubuntu10.10
   _ZN17pkgPackageManager10SigINTStopE@Base 0.8.16~exp12ubuntu10.10
   _ZN17pkgPackageManager11SmartUnPackEN8pkgCache11PkgIteratorEbi@Base 
0.8.16~exp12ubuntu10.10
   _ZN17pkgPackageManager14SmartConfigureEN8pkgCache11PkgIteratorEi@Base 
0.8.16~exp12ubuntu10.10
   _ZN23SummationImplementation5AddFDER6FileFdy@Base 0.8.16~exp12ubuntu10.10
   
_ZN3APT14CacheSetHelper14canNotFindTaskEPNS_25PackageContainerInterfaceER12pkgCacheFileSs@Base
 0.8.16~exp12ubuntu10.10
   
_ZN3APT14CacheSetHelper15canNotFindRegExEPNS_25PackageContainerInterfaceER12pkgCacheFileSs@Base
 0.8.16~exp12ubuntu10.10
   
_ZN3APT14CacheSetHelper16canNotFindAllVerEPNS_25VersionContainerInterfaceER12pkgCacheFileRKN8pkgCache11PkgIteratorE@Base
 0.8.16~exp12ubuntu10.10
   
_ZN3APT14CacheSetHelper17canNotFindPackageEPNS_25PackageContainerInterfaceER12pkgCacheFileRKSs@Base
 0.8.16~exp12ubuntu10.10
   
_ZN3APT14CacheSetHelper17showTaskSelectionERKN8pkgCache11PkgIteratorERKSs@Base 
0.8.16~exp12ubuntu10.10
   
_ZN3APT14CacheSetHelper18showRegExSelectionERKN8pkgCache11PkgIteratorERKSs@Base 
0.8.16~exp12ubuntu10.10
   
_ZN3APT14CacheSetHelper19showSelectedVersionERKN8pkgCache11PkgIteratorENS1_11VerIteratorERKSsb@Base
 0.8.16~exp12ubuntu10.10
   
_ZN3APT14CacheSetHelper21canNotFindCandInstVerEPNS_25VersionContainerInterfaceER12pkgCacheFileRKN8pkgCache11PkgIteratorE@Base
 0.8.16~exp12ubuntu10.10
   
_ZN3APT14CacheSetHelper21canNotFindInstCandVerEPNS_25VersionContainerInterfaceER12pkgCacheFileRKN8pkgCache11PkgIteratorE@Base
 0.8.16~exp12ubuntu10.10
   
_ZN3APT16PackageContainerISt3setIN8pkgCache11PkgIteratorESt4lessIS3_ESaIS3_EEE14setConstructorERKNS_25PackageContainerInterface11ConstructorE@Base
 0.8.16~exp12ubuntu10.10
   
_ZN3APT16PackageContainerISt3setIN8pkgCache11PkgIteratorESt4lessIS3_ESaIS3_EEE5clearEv@Base
 0.8.16~exp12ubuntu10.10
   
_ZN3APT16PackageContainerISt3setIN8pkgCache11PkgIteratorESt4lessIS3_ESaIS3_EEE6insertERKS3_@Base
 0.8.16~exp12ubuntu10.10
   
_ZN3APT16PackageContainerISt4listIN8pkgCache11PkgIteratorESaIS3_EEE14setConstructorERKNS_25PackageContainerInterface11ConstructorE@Base
 0.8.16~exp12ubuntu10.10
   

[Touch-packages] [Bug 1015495] Re: “duplicate sources” error message during an Ubuntu Live CD session

[Julian Andres Klode]

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

** This bug is no longer a duplicate of bug 975312
   duplicated sources list entry
** This bug has been marked a duplicate of bug 1697120
   artful's apt-file and aptitude complains about Ubuntu sources.list

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

Title:
  “duplicate sources” error message during an Ubuntu Live CD session

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1) boot into live cd
  2) click 'Try Ubuntu'
  3) launch terminal (e.g. click big fat button -> search for 'Terminal')
  4) type $ sudo apt-get update
  5) see errors:

  Reading package lists... Done
  W: Duplicate sources.list entry cdrom://Ubuntu 12.04 LTS _Precise Pangolin_ - 
Release amd64 (20120425)/ precise/main i386 Packages 
(/var/lib/apt/lists/Ubuntu%2012.04%20LTS%20%5fPrecise%20Pangolin%5f%20-%20Release%20amd64%20(20120425)_dists_precise_main_binary-i386_Packages)
  W: Duplicate sources.list entry cdrom://Ubuntu 12.04 LTS _Precise Pangolin_ - 
Release amd64 (20120425)/ precise/restricted i386 Packages 
(/var/lib/apt/lists/Ubuntu%2012.04%20LTS%20%5fPrecise%20Pangolin%5f%20-%20Release%20amd64%20(20120425)_dists_precise_restricted_binary-i386_Packages)
  W: You may want to run apt-get update to correct these problems

  Expected:
  5) don't see any Duplicate sources.list errors.

  Same with quantal daily live 2012-06-19

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

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

[Touch-packages] [Bug 975312] Re: duplicated sources list entry

[Julian Andres Klode]

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

** This bug has been marked a duplicate of bug 1697120
   artful's apt-file and aptitude complains about Ubuntu sources.list

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

Title:
  duplicated sources list entry

Status in apt package in Ubuntu:
  Triaged
Status in ubiquity package in Ubuntu:
  Triaged

Bug description:
  Hello
  Start a live session of today's amd64 build and run sudo apt-get update, it 
will return:

  W: Duplicate sources.list entry cdrom://Ubuntu 12.04 LTS _Precise Pangolin_ - 
Beta amd64 (20120406)/ precise/main i386 Packages 
(/var/lib/apt/lists/Ubuntu%2012.04%20LTS%20%5fPrecise%20Pangolin%5f%20-%20Beta%20amd64%20(20120406)_dists_precise_main_binary-i386_Packages)
  W: Duplicate sources.list entry cdrom://Ubuntu 12.04 LTS _Precise Pangolin_ - 
Beta amd64 (20120406)/ precise/restricted i386 Packages 
(/var/lib/apt/lists/Ubuntu%2012.04%20LTS%20%5fPrecise%20Pangolin%5f%20-%20Beta%20amd64%20(20120406)_dists_precise_restricted_binary-i386_Packages)
  W: È consigliato eseguire "apt-get update" per correggere questi problemi

  
  Thanks
  fabio

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: ubiquity 2.10.8
  ProcVersionSignature: Ubuntu 3.2.0-22.35-generic 3.2.14
  Uname: Linux 3.2.0-22-generic x86_64
  ApportVersion: 2.0-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.314
  Date: Fri Apr  6 16:48:48 2012
  InstallCmdLine: noprompt cdrom-detect/try-usb=true persistent 
file=/cdrom/preseed/ubuntu.seed boot=casper initrd=/casper/initrd.lz quiet 
splash -- debian-installer/language=it keyboard-configuration/layoutcode?=it 
oem-config/enable=true
  LiveMediaBuild: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120406)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1779667] [NEW] Unlocking existing session yields black screen. Closing session does not help as affected user cannot open a successful X session until next reboot. Other users ar

[gouri]

Public bug reported:

# Context

* Xubuntu 18.04 using lightdm, no specific customization, no 
xscreensaver/gnome-screensaver.
* Problem observed two machines:
** one machine with several users often swapping sessions,
** one machine with just one regular user who just locks/unlocks session often


# Action

* Open a XFCE session.
* Lock it.
* On greeter, type password to unlock.


# Expected

* Get back to opened session.


# Observed

* After typing password, screen turns to black.  All pixels are fully black.
* Not even a mouse pointer is visible.


# Reproducible

* Seems random.
* Perhaps one time out of 20-50 unlock operations.
* Never occurred in 16.04 14.04


# Detailed information

>From start:

* On unlocking an already opened session, after typing password screen
turns to full black.


## Investigation: is machine still okay?

* As a sanity check, switching to text VT works, login on text VT works.


## Investigation: problem does not affect all sessions at once

* Bug observed both in one system with one user at a time, and on another 
system with two users alternating X sessions.
* From tty1, using "dm-tool switch-to-greeter" with proper environment works, 
allows to select other user's session, type password and return to that other 
user's opened session. Any attempt to return to affected user session yields 
black screen.


## Investigation: problem affects user even after closing all their programs

* Manually killing affected user processes allows to close faulty session and 
see lightdm greeter come back.
* Trying to reopen a session (as usual with lightdm) as affected user shows an 
error dialog:

"Unable to contact settings server
Failed to connect to socket /run/user/1000/bus: Connection refused"
and a "Close" button.

Clicking on it yields a second dialog :

"Unable to load failsafe session
Unable to determine a failsafe session name. Possible causes:
xfconfd isn't running (D-Bus setup problem);
environment variable $XDG_CONFIG_DIRS is set incorrectly (must include "/etc"),
or xfce4-session is installed incorrectly."
and a "Quit" button.

Clicking "quit" button goes back to lightdm greeter.


## Investigation: reboot solves the problem

* Rebooting the machine solves the problem (but closes all user sessions and 
processes).
* Problem reappears after a few days.


## Investigation: startx affected, too

* From text VT, startx has same behavior as running from lightdm and
thus also cannot reach a working XFCE desktop.


## Investigation: affected user has no dbus-daemon running.

* No "/usr/bin/dbus-daemon" runs as affected user while it runs as other
users.


## Additional information

* It is believed that the multi-user system makes the bug more salient than 
usual workflow because users switch more often from one session to another.
* It is believed that the single-user system makes the bug more salient than 
usual workflow because users often locks and unlocks their session.


1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

Description:Ubuntu 18.04 LTS
Release:18.04

Actually Xubuntu 18.04.

2) The version of the package you are using, via 'apt-cache policy
pkgname' or by checking in Software Center

export LC_ALL=C ; apt-cache policy dbus

dbus:
  Installed: 1.12.2-1ubuntu1
  Candidate: 1.12.2-1ubuntu1
  Version table:
 *** 1.12.2-1ubuntu1 500
500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status


3) What you expected to happen
4) What happened instead

Described above.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dbus 1.12.2-1ubuntu1
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: Mon Jul  2 13:43:08 2018
InstallationDate: Installed on 2018-05-25 (38 days ago)
InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Unlocking existing session yields black screen. Closing session does
  not help as affected user cannot open a successful X session until
  next reboot. Other users are ok.

Status in dbus package in Ubuntu:
  New

Bug description:
  # Context

  * Xubuntu 18.04 using lightdm, no specific customization, no 
xscreensaver/gnome-screensaver.
  * Problem observed two machines:
  ** one machine with several users often swapping sessions,
  ** one machine with just one regular user who just locks/unlocks session often

  
  # Action

  * Open a XFCE session.
  * 

[Touch-packages] [Bug 1779667] Re: Unlocking existing session yields black screen. Closing session does not help as affected user cannot open a successful X session until next reboot. Other users are

[gouri]

Also, the problem is not specific to any user.

It randomly affects any of the users of the machine.  At that moment
only that user is affected.

Next time it may affect the same user or another.

We believe that it may affect several users at a time, if we keep the
machine running until problem affects a second user.  In practice,
however, users have some work to do, so we reboot the machine to let
them continue their work.

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

Title:
  Unlocking existing session yields black screen. Closing session does
  not help as affected user cannot open a successful X session until
  next reboot. Other users are ok.

Status in dbus package in Ubuntu:
  New

Bug description:
  # Context

  * Xubuntu 18.04 using lightdm, no specific customization, no 
xscreensaver/gnome-screensaver.
  * Problem observed two machines:
  ** one machine with several users often swapping sessions,
  ** one machine with just one regular user who just locks/unlocks session often

  
  # Action

  * Open a XFCE session.
  * Lock it.
  * On greeter, type password to unlock.

  
  # Expected

  * Get back to opened session.

  
  # Observed

  * After typing password, screen turns to black.  All pixels are fully black.
  * Not even a mouse pointer is visible.

  
  # Reproducible

  * Seems random.
  * Perhaps one time out of 20-50 unlock operations.
  * Never occurred in 16.04 14.04

  
  # Detailed information

  From start:

  * On unlocking an already opened session, after typing password screen
  turns to full black.

  
  ## Investigation: is machine still okay?

  * As a sanity check, switching to text VT works, login on text VT
  works.

  
  ## Investigation: problem does not affect all sessions at once

  * Bug observed both in one system with one user at a time, and on another 
system with two users alternating X sessions.
  * From tty1, using "dm-tool switch-to-greeter" with proper environment works, 
allows to select other user's session, type password and return to that other 
user's opened session. Any attempt to return to affected user session yields 
black screen.

  
  ## Investigation: problem affects user even after closing all their programs

  * Manually killing affected user processes allows to close faulty session and 
see lightdm greeter come back.
  * Trying to reopen a session (as usual with lightdm) as affected user shows 
an error dialog:

  "Unable to contact settings server
  Failed to connect to socket /run/user/1000/bus: Connection refused"
  and a "Close" button.

  Clicking on it yields a second dialog :

  "Unable to load failsafe session
  Unable to determine a failsafe session name. Possible causes:
  xfconfd isn't running (D-Bus setup problem);
  environment variable $XDG_CONFIG_DIRS is set incorrectly (must include 
"/etc"),
  or xfce4-session is installed incorrectly."
  and a "Quit" button.

  Clicking "quit" button goes back to lightdm greeter.

  
  ## Investigation: reboot solves the problem

  * Rebooting the machine solves the problem (but closes all user sessions and 
processes).
  * Problem reappears after a few days.

  
  ## Investigation: startx affected, too

  * From text VT, startx has same behavior as running from lightdm and
  thus also cannot reach a working XFCE desktop.

  
  ## Investigation: affected user has no dbus-daemon running.

  * No "/usr/bin/dbus-daemon" runs as affected user while it runs as
  other users.

  
  ## Additional information

  * It is believed that the multi-user system makes the bug more salient than 
usual workflow because users switch more often from one session to another.
  * It is believed that the single-user system makes the bug more salient than 
usual workflow because users often locks and unlocks their session.


  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  Actually Xubuntu 18.04.

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  export LC_ALL=C ; apt-cache policy dbus

  dbus:
Installed: 1.12.2-1ubuntu1
Candidate: 1.12.2-1ubuntu1
Version table:
   *** 1.12.2-1ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  4) What happened instead

  Described above.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dbus 1.12.2-1ubuntu1
  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: Mon Jul  2 13:43:08 2018
  InstallationDate: Installed on 2018-05-25 (38 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   

[Touch-packages] [Bug 106127] Re: Wish: Clarify apt-get error message(s)

[Julian Andres Klode]

These days we mostly fetch based on what the InRelease file tells us, so
this message is seen less. In any case, it's not an error, otherwise it
would tell you, it's just progress logging.

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

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

Title:
  Wish: Clarify apt-get error message(s)

Status in apt package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: apt

  apt-get update sometimes gives rows with "Ign":
  Läs:1 http://se.archive.ubuntu.com feisty Release.gpg [191B]
  Ign http://se.archive.ubuntu.com feisty/main Translation-sv_SE
  ...

  It seems that missing files (404-errors) in a repo are reported as
  "Ign". People ask on local forums "Ign? Is apt ignoring repos, and
  why?" - receiving many suggestions but no answers. A "not found" error
  should show as not found/not there. If it surely should've been there,
  "missing" becomes appropriate.

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

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

[Touch-packages] [Bug 1627747] Re: [UX+API] Provide generic API for communication and data exchange

[Peter Bittner]

See the Purism "Design report #4: symbiotic applications" for a very
similar approach:

- https://puri.sm/posts/librem5-progress-report-8/

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

Title:
  [UX+API] Provide generic API for communication and data exchange

Status in Canonical System Image:
  New
Status in qtubuntu package in Ubuntu:
  Confirmed

Bug description:
  As a provider for online communication (instant messaging, voice, video, etc.)
  I want to have a simple, generic API that allows me to plug in to the Ubuntu 
Touch platform
  So that I can develop a "plugin into Ubuntu Touch" with little effort
  And without explicit need to design a user interface and interactions.

  Background and Motivation
  =

  Lemma: Smart phones, tablets, notebooks and desktop computers are
  multi-purpose communication devices that are used by humans to
  exchange information and getting things done. Information managed by
  all those devices has different forms: From static (slow) data, such
  as files, emails and calendar entries, to dynamic and ephemeral data
  (instant messages and real-time communication). But they all serve the
  same human goal that is invariant across all devices and device
  platforms (operating systems): Interact and exchange data.

  Proposal
  

  It should be possible to provide a platform that provides:

  - A generic API allowing external platforms to send and receive data
  (e.g. send voice or video stream, send and receive files, send and
  receive various types of messages)

  - Unified communication to the device users (a single front-end that
  allows unified access to information exchanged, e.g. text messages, IM
  chats protocols, voice and video call protocols, related files,
  images, contacts)

  - The user interface should allow to filter, group and sort all the
  information, empowering the user over the vast amount of data. (This
  way it should even be possible to easily build what we today know as
  specific "apps" by simply applying filtering and grouping to the
  unified communication data handling application, plus add a nice skin
  or theme.)

  (Doesn't this even match with the concept of "scopes" in a certain
  way?)

  Solution Examples
  =

  This API would allow to have a single telephony app (if you want so)
  that

  - makes voice phone calls via a (default) plugin
  - makes video phone calls via a (default) plugin
  - makes free emergency phone calls via a (not uninstallable) plugin
  - handles text messages and multimedia messages via a (default) plugin

  (Until here all features existing in the phone today. Keypad,
  keyboard, text panels, history views are provided appropriately for
  the different types of information "automatically".)

  - allows searching for a contact, a contact group, a communication or 
communication history (with the goal to initiate a call or other type of 
communication) [NOTE: this is scattered across several apps today: Contacts, 
Messaging, Phone]
  - allow instant messengers to send and receive their data stream (e.g. 
Telegram, Hangups, Hangouts, Ring, Skype, Slack, Viber, WhatsApp, etc.) via 
plugins developed by the various platform providers or community people
  - make VoIP calls (voice, video, presence information via SIP or XMPP) via 
generic (configurable) or specific plugins (preconfigured by e.g. a SIP 
provider of your region)

  (No proprietary "apps" should be developed, but plugins that deal with
  transforming and shipping the data. The plugins get the information
  they require, based on permission sets.)

  Similar Concepts, Related Bugs, Plugin Ideas
  

  - Bug 1533104 ("VOIP")
  - Bug 1535755 ("Show contact details from social accounts")
  - Bug 1627753 ("Greeter should be a scopes app (showing specific scopes)")
  - Bug 1544670 ("Unique lock screen design w/ circle gestures to unlock")
  - Telepathy plugins (telephony voice data flows through the ofono plugin
  of Telepathy, according to Felipe De La Puente), 
https://lists.launchpad.net/ubuntu-phone/msg22870.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1627747/+subscriptions

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

[Touch-packages] [Bug 1779569] Re:  looks odd in thunderbird, chrome/chromium, okish in firefox

[Jeremy Bicha]

Dimitri, see my comment 12 on bug 1761844 which points out that is
likely bug 1644021 which I helped fix in the beta PPA, but I don't
handle Firefox/Thunderbird uploads directly to Ubuntu. You're welcome to
talk to Chris about this issue though…

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

Title:
   looks odd in thunderbird, chrome/chromium, okish in firefox

Status in Mozilla Thunderbird:
  Unknown
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  New install of 18.04 and thunderbird is showing weird images in odd
  places for some email.  See screen shot for example.  In this case it
  is a weird rainbow, but I have also seen other things like a big stop
  sign and other strange stuff.

  
  Emoji support is inconsistent:
  - google chrome title is good
  - firefox title is good
  - google chrome contents, is bad, black ascii icon
  - fiefox contents, is ok, not the same icon as in the title
  - thunderbird content is ok, but too huge

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

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

[Touch-packages] [Bug 1548392]

[Ajax-a]

pm-utils hasn't been touched in eight years, none of this is likely to
get addressed. Closing bugs and disabling the bz product.

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

Title:
  Fix for 1172692 fails to restore hibernation mode with suspend-hybrid

Status in pm-utils:
  Won't Fix
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The patch provided in upstream bug
   and implemented
  through 28-suspend-hybrid.patch causes error messages "sh: I/O error"
  when resuming with suspend-hybrid and hibernate kernel methods.

  With suspend-hybrid it also forces the hibernation mode, as shown in
  /sys/power/disk, to "suspend" instead of restoring the original mode
  which is what the patch tried to do.

  Please see the upstream bug for a review of the provided patch with
  proposed fixes.

  Affects all Ubuntu and derived versions with pm-utils
  1.4.1-9fix.ubuntu12.10 or later.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 16:44:52 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548392/+subscriptions

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

[Touch-packages] [Bug 1779767] [NEW] Default cron PATH does not include /snap/bin

[Mike Pontillo]

Public bug reported:

I recently changed from a .deb install of LXD to a snap, and was
surprised that one of my crontab scripts stopped working.

I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas
my default shell also includes "/snap/bin".

It seems to me that for the best user experience with snaps, "/snap/bin"
should be part of the default $PATH in cron.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cron 3.0pl1-128.1ubuntu1
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 
kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon 
znvpair
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Jul  2 14:30:06 2018
InstallationDate: Installed on 2017-12-20 (194 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cron
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Description changed:

- I recently change from a .deb install of LXD to a snap, and was
+ I recently changed from a .deb install of LXD to a snap, and was
  surprised that one of my crontab scripts stopped working.
  
  I see that $PATH in a cron script only contains "/usr/bin:/bin", whereas
  my default shell also includes "/snap/bin".
  
  It seems to me that for the best user experience with snaps, "/snap/bin"
  should be part of the default $PATH in cron.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cron 3.0pl1-128.1ubuntu1
  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 
kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  2 14:30:06 2018
  InstallationDate: Installed on 2017-12-20 (194 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Default cron PATH does not include /snap/bin

Status in cron package in Ubuntu:
  New

Bug description:
  I recently changed from a .deb install of LXD to a snap, and was
  surprised that one of my crontab scripts stopped working.

  I see that $PATH in a cron script only contains "/usr/bin:/bin",
  whereas my default shell also includes "/snap/bin".

  It seems to me that for the best user experience with snaps,
  "/snap/bin" should be part of the default $PATH in cron.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cron 3.0pl1-128.1ubuntu1
  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 
kpatch_livepatch_Ubuntu_4_15_0_20_21_generic_39 
livepatch_livepatch_Ubuntu_4_15_0_20_21_generic_ zfs zunicode zavl icp zcommon 
znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jul  2 14:30:06 2018
  InstallationDate: Installed on 2017-12-20 (194 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171219)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cron
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1779583] Re: cron do_command.c attempts a fork() without testing for errors

[Alexis Wilke]

** Tags removed: trusty
** Tags added: xenial

** Description changed:

  The do_command.c file calls fork() twice.
  
  For the first fork(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.
  
  The second fork(), however, is used inside an if() statement like this:
  
  if (*input_data && fork() == 0) { ... }
  
  Here we can see a couple of problems. After the if block, we have this
  statement:
  
  children++;
  
  which means that we will have to wait on TWO children. However, (1) the
  *input_data could return false and thus the second child may not be
  created at all. (2) the fork() could return -1 meaning that no other
  child is created.
  
  I suppose that the child_process() probably always or nearly always has
  some input_data. Otherwise it would block waiting for a child that was
  never started. And of course, it is relatively rare that fork() fails,
  unless you are running our of RAM (heap or stack can't be allocated) or
  process space (too many processes running concurrently.)
  
  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).
  
  The children variable gets incremented only when the fork() happens and
  succeeds (default: block in the new switch().)
  
- The do_command.c file did not change between 16.04 (trusty) and 18.04
+ The do_command.c file did not change between 16.04 (xenial) and 18.04
  (bionic beaver), so the patch will work for either version.

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

Title:
  cron do_command.c attempts a fork() without testing for errors

Status in cron package in Ubuntu:
  New

Bug description:
  The do_command.c file calls fork() twice.

  For the first fork(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.

  The second fork(), however, is used inside an if() statement like
  this:

  if (*input_data && fork() == 0) { ... }

  Here we can see a couple of problems. After the if block, we have this
  statement:

  children++;

  which means that we will have to wait on TWO children. However, (1)
  the *input_data could return false and thus the second child may not
  be created at all. (2) the fork() could return -1 meaning that no
  other child is created.

  I suppose that the child_process() probably always or nearly always
  has some input_data. Otherwise it would block waiting for a child that
  was never started. And of course, it is relatively rare that fork()
  fails, unless you are running our of RAM (heap or stack can't be
  allocated) or process space (too many processes running concurrently.)

  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).

  The children variable gets incremented only when the fork() happens
  and succeeds (default: block in the new switch().)

  The do_command.c file did not change between 16.04 (xenial) and 18.04
  (bionic beaver), so the patch will work for either version.

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

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

[Touch-packages] [Bug 958825] Re: Ubuntu installation footprint should be below 4GB (optionally)

[gf]

Hello Komputes,
Thank you for submitting this bug and reporting a problem with the Ubuntu 
installation size.

You made this bug report in 2012 and there have been several versions of
Ubuntu since then including the minimal install of 18.04.

Could you confirm that this is no longer a problem and that we can close the 
ticket? 
Or, if it is still a problem, could you run the following (only once):
apport-collect 958825

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: ubuntu-meta (Ubuntu)
   Status: New => Incomplete

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

Title:
  Ubuntu installation footprint should be below 4GB (optionally)

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  The footprint for Ubuntu installation has increased greatly. Ubiquity
  should utilize the screen where it says

  [HAS AT LEAST 4.5 GB available drive space]

  to make that size changeable by removing optional packages making it
  possible to install Ubuntu on smaller drives.

  Some ideas of "optional" packages. Some are quite large and I find that not 
everyone uses these:
  Libre Office
  Thunderbird
  Ubuntu-one
  Gwibber
  Empathy
  Rhytmbox/Banshee
  Gnome Games
  Totem
  Shotwell

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: ubiquity (not installed)
  ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11
  Uname: Linux 3.2.0-19-generic-pae i686
  NonfreeKernelModules: wl
  ApportVersion: 1.94.1-0ubuntu2
  Architecture: i386
  Date: Sun Mar 18 16:11:13 2012
  InstallCmdLine: noprompt cdrom-detect/try-usb=true 
file=/cdrom/preseed/ubuntu.seed vga=788 initrd=/install/initrd.gz quiet --
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120222)
  ProcEnviron:
   TERM=xterm
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: ubiquity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1003461] Re: Print dialog doesn't display the status message for printers correct

[gf]

Closed per reporter’s comment above; not a bug anymore.

** Changed in: gtk+3.0 (Ubuntu)
   Status: New => Invalid

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

Title:
  Print dialog doesn't display the status message for printers correct

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  The normal print dialog doesn't show the correct status for printers
  instead it displays some random characters.

  Firefox and Thunderbird show the correct status which in my case would
  be:

  Printer 'Dell-5350dn-DKinvoice' has no toner left.
  Printer 'Dell-5350dn-white' has no toner left.

  The characters I see in the print dialogs for eog or gedit for example
  change with every mouse move. It doesn't matter which window has the
  focus, the characters constantly change when moving the mouse.

  
  My setup is I have one pysical DELL 5350dn printer with 4 paper trays and to 
access them quickly I've installed 4 printers with the defaults sets to the 
individual trays.
  However out of those 4 only two show those messages, the other two don't show 
any status at all. Also in Friefox the other two don't say that it is out of 
toner.

  I've attached a screenshot of the dialog.

  Not sure if this is related to this bug or if it is seperate bug. For
  the printers with this status the Firefox/ Thunderbird print dialog
  doesn't display any printer icon. It should be the printer with the
  yellow/orange triangle with the "!" in it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1003461/+subscriptions

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

[Touch-packages] [Bug 1779569] Re:  looks odd in thunderbird, chrome/chromium, okish in firefox

[Jeremy Bicha]

Web browsers have their own system for rendering text and therefore
color emoji. Firefox currently uses a version of EmojiOne but is
switching to the Twitter emoji set. See
https://bugzilla.mozilla.org/1358240

Honestly, the bug report you filed is too broad and in some cases is
already duplicated by existing bugs.

For reference, you might find this page interesting (it's a large page):
https://unicode.org/emoji/charts/full-emoji-list.html

Ubuntu 18.04 LTS installs the Google emoji font by default and that page
does actually display correctly for me with Firefox. Web pages can
specify a particular color emoji font though. Therefore, you will see
different emoji sets on different web pages and that's not really a bug.

** No longer affects: ubuntu-meta (Ubuntu)

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

Title:
   looks odd in thunderbird, chrome/chromium, okish in firefox

Status in Mozilla Thunderbird:
  Unknown
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New

Bug description:
  New install of 18.04 and thunderbird is showing weird images in odd
  places for some email.  See screen shot for example.  In this case it
  is a weird rainbow, but I have also seen other things like a big stop
  sign and other strange stuff.

  
  Emoji support is inconsistent:
  - google chrome title is good
  - firefox title is good
  - google chrome contents, is bad, black ascii icon
  - fiefox contents, is ok, not the same icon as in the title
  - thunderbird content is ok, but too huge

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

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

[Touch-packages] [Bug 1548392] Re: Fix for 1172692 fails to restore hibernation mode with suspend-hybrid

[Bug Watch Updater]

** Changed in: pm-utils
   Status: Confirmed => Won't Fix

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

Title:
  Fix for 1172692 fails to restore hibernation mode with suspend-hybrid

Status in pm-utils:
  Won't Fix
Status in pm-utils package in Ubuntu:
  Confirmed

Bug description:
  The patch provided in upstream bug
   and implemented
  through 28-suspend-hybrid.patch causes error messages "sh: I/O error"
  when resuming with suspend-hybrid and hibernate kernel methods.

  With suspend-hybrid it also forces the hibernation mode, as shown in
  /sys/power/disk, to "suspend" instead of restoring the original mode
  which is what the patch tried to do.

  Please see the upstream bug for a review of the provided patch with
  proposed fixes.

  Affects all Ubuntu and derived versions with pm-utils
  1.4.1-9fix.ubuntu12.10 or later.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: pm-utils 1.4.1-13ubuntu0.2 [modified: usr/lib/pm-utils/pm-functions]
  ProcVersionSignature: Ubuntu 4.2.0-29.34~14.04.1-generic 4.2.8-ckt3
  Uname: Linux 4.2.0-29-generic i686
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: i386
  Date: Mon Feb 22 16:44:52 2016
  InstallationDate: Installed on 2016-02-21 (0 days ago)
  InstallationMedia: Lubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1548392/+subscriptions

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

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

[Dimitri John Ledkov ]

An empty match, does not match any interfaces hence none are
configured

What's the output of $ networkctl ? i suspect no interfaces are
maganaged, right?

Note the config mentioned in this bug report looks buggy, and different
from the askubuntu reference - which does appear to have a valid config.

** Also affects: netplan.io (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  systemd-networkd does not configure DHCPv4

Status in netplan.io package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
 valid_lft forever preferred_lft forever
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
 valid_lft forever preferred_lft forever
  ```

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1779721/+subscriptions

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

[Touch-packages] [Bug 1234424]

[Ajax-a]

pm-utils hasn't been touched in eight years, none of this is likely to
get addressed. Closing bugs and disabling the bz product.

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

Title:
  Don't quirk SVGA if vmwgfx kernel driver is loaded

Status in pm-utils:
  Won't Fix
Status in pm-utils package in Ubuntu:
  Fix Released

Bug description:
  If you try to suspend the VM from within it, it fails to go up again
  because pm-utils power cycles the VGA devices which leaves the kernel
  driver in the wrong state. Leading to a hanged VM.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1234424/+subscriptions

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

[Touch-packages] [Bug 1779569] Re:  looks odd in thunderbird, chrome/chromium, okish in firefox

[Amr Ibrahim]

A quick workaround is to install fonts-symbola, as mentioned before,
that will make Thunderbird use the emojis from their, but they are black
and white.

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

Title:
   looks odd in thunderbird, chrome/chromium, okish in firefox

Status in Mozilla Thunderbird:
  Unknown
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  New install of 18.04 and thunderbird is showing weird images in odd
  places for some email.  See screen shot for example.  In this case it
  is a weird rainbow, but I have also seen other things like a big stop
  sign and other strange stuff.

  
  Emoji support is inconsistent:
  - google chrome title is good
  - firefox title is good
  - google chrome contents, is bad, black ascii icon
  - fiefox contents, is ok, not the same icon as in the title
  - thunderbird content is ok, but too huge

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

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

Re: [Touch-packages] [Bug 1779411] Re: info about bug appeared on screen earlier today

[paul]

hello daniel,

   thanks for your response. i'll try to work through your list. i'm 
presuming that i must use the terminal to search crash logs. so far, i 
can't get the terminal to recognize my commands. i'm presuming i must 
use sudo commands to get access to the files. however, no combination of 
commands i've used so far get me in to the crash logs. do you have any 
ideas for me? also, one more hint. when restarting my computer and 
firefox, an unprompted ad block plus page is opening, telling me that ad 
block plus has been installed. however, i haven't added any abp 
installations since upgrading to 18.04 a few weeks ago( abp carried over 
from 16.10 which was previously my os). more and more of the sites i 
visit recognize the abp and require me to delete it before they'll allow 
me to access their site. i'm wondering if i should delete the program 
altogether and reinstall.

   thanks again for responding to my problem. paul retallack


On 07/01/2018 07:25 PM, Daniel van Vugt wrote:
> 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.
>
> ** Changed in: xorg (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/1779411

Title:
  info about bug appeared on screen earlier today

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  i was watching hawaiian volcano videos this morning and the screen
  locked up. i restarted the computer and the error message
  appeared(error with 18.04 was the message). however, prior to that,
  grub appeared to show a problem beginning to form about a week ago.
  grub used to be a short startup leading to give me a choice of which
  hard drive i wanted to begin with(1 tb wd black and a 250gb samsung
  ssd. both drives have linux 18.04, one ubuntu and one kubuntu. only
  the ubuntu is acting up. for the past two days, grub is showing me
  every line of the startup process, although the ubuntu is otherwise
  starting normally. i know enough to enter code correctly in the
  terminal(e.g. sudo apt-get upgrade etc) and like the simplicity and
  independence of linux but regret that i must have the code spelled out
  for me if mistakes are to be avoided. i'm old and don't mind admitting
  it. hope this helps. cheers. paul.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Jun 29 13:48:50 2018
  DistUpgraded: 2018-06-05 12:53:32,893 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4250] [1002:9715] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS880 [Radeon HD 4250] [1458:d000]
  InstallationDate: Installed on 2015-05-30 (1125 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-880GM-UD2H
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=1b13c61c-0cc4-4160-9da5-fddeca76ae93 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-06-05 (24 days ago)
  dmi.bios.date: 03/24/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-880GM-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd03/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-880GM-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 

[Touch-packages] [Bug 1779569] Re:  looks odd in thunderbird, chrome/chromium, okish in firefox

[Amr Ibrahim]

The Thunderbird part in a duplicate of bug #1761844. Upstream
Thunderbird says it will be fixed in version 60.

** Bug watch added: Mozilla Bugzilla #1390015
   https://bugzilla.mozilla.org/show_bug.cgi?id=1390015

** Also affects: thunderbird via
   https://bugzilla.mozilla.org/show_bug.cgi?id=1390015
   Importance: Unknown
   Status: Unknown

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

Title:
   looks odd in thunderbird, chrome/chromium, okish in firefox

Status in Mozilla Thunderbird:
  Unknown
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  New install of 18.04 and thunderbird is showing weird images in odd
  places for some email.  See screen shot for example.  In this case it
  is a weird rainbow, but I have also seen other things like a big stop
  sign and other strange stuff.

  
  Emoji support is inconsistent:
  - google chrome title is good
  - firefox title is good
  - google chrome contents, is bad, black ascii icon
  - fiefox contents, is ok, not the same icon as in the title
  - thunderbird content is ok, but too huge

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

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

[Touch-packages] [Bug 1777062] Re: Logitech M535 mouse only pairs successfully after 4-5 tries

[Launchpad Bug Tracker]

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

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

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

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

Title:
  Logitech M535 mouse only pairs successfully after 4-5 tries

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I've had my mouse (Logitech M535) paired and working since upgrading
  to 18.04. I had to re-do the pairing after connecting to a different
  machine and now it takes 4-5 tries of pair/remove to connect the
  mouse, on every reboot / sleep cycle.

  The logs show:
  cze 15 07:45:37 michal-laptop bluetoothd[4168]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 07:46:14 michal-laptop bluetoothd[4168]: Can't get HIDP connection info

  But neither actually seem critical as this is shown upon successful
  pairing as well.

  a bluetoothctl session of a failed pairing:
  [bluetooth]# pair 34:88:5D:3E:A1:A4 
  Attempting to pair with 34:88:5D:3E:A1:A4
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes
  Pairing successful
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: no
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: no

  The mouse continues in pairing mode.

  When using the gnome-control-center Bluetooth module:
  cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:40 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:41 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:42 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)
  cze 15 08:23:43 michal-laptop bluetoothd[19188]: 34:88:5D:3E:A1:A4: error 
updating services: Device or resource busy (16)

  Finally when it connects:
  [NEW] Device 34:88:5D:3E:A1:A4 Bluetooth Mouse M336/M337/M535
  [CHG] Device 34:88:5D:3E:A1:A4 Trusted: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Connected: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Modalias: usb:v046DpB014d1200
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1000--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1124--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 UUIDs: 1200--1000-8000-00805f9b34fb
  [CHG] Device 34:88:5D:3E:A1:A4 ServicesResolved: yes
  [CHG] Device 34:88:5D:3E:A1:A4 Paired: yes

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Jun 15 07:46:38 2018
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Dell Inc. XPS 12-9Q33
  ProcKernelCmdLine: BOOT_IMAGE=/ROOT/ubuntu@/boot/vmlinuz-4.15.0-23-generic 
root=ZFS=username-laptop/ROOT/ubuntu ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: Upgraded to bionic on 2018-02-07 (127 days ago)
  dmi.bios.date: 03/03/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.name: XPS 12-9Q33
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd03/03/2015:svnDellInc.:pnXPS12-9Q33:pvrA08:rvnDellInc.:rnXPS12-9Q33:rvrA08:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: XPS 12-9Q33
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 5C:51:4F:1D:50:3C  ACL MTU: 1021:5  SCO MTU: 96:5
UP RUNNING PSCAN ISCAN 
RX bytes:16702 acl:290 sco:0 events:716 errors:0
TX bytes:44162 acl:142 sco:0 commands:427 errors:0

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

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

[Touch-packages] [Bug 1779721] Re: systemd-networkd does not configure DHCPv4

[Benjamin Drung]

You can also reproduce this issue with the official cloud image. See
https://askubuntu.com/questions/1030081/ubuntu-18-04-cloud-image-does-
not-get-dhcp-ipv4-address

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

Title:
  systemd-networkd does not configure DHCPv4

Status in systemd package in Ubuntu:
  New

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
 valid_lft forever preferred_lft forever
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
 valid_lft forever preferred_lft forever
  ```

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

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

[Touch-packages] [Bug 1234424] Re: Don't quirk SVGA if vmwgfx kernel driver is loaded

[Bug Watch Updater]

** Changed in: pm-utils
   Status: Confirmed => Won't Fix

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

Title:
  Don't quirk SVGA if vmwgfx kernel driver is loaded

Status in pm-utils:
  Won't Fix
Status in pm-utils package in Ubuntu:
  Fix Released

Bug description:
  If you try to suspend the VM from within it, it fails to go up again
  because pm-utils power cycles the VGA devices which leaves the kernel
  driver in the wrong state. Leading to a hanged VM.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/pm-utils/+bug/1234424/+subscriptions

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

[Touch-packages] [Bug 1779569] Re:  looks odd in thunderbird, chrome/chromium, okish in firefox

[Dimitri John Ledkov ]

The expected behaviour is a colorful emoji though. In the body of google
chrome/chromium too... Not the black ones.

Basically, gnome-terminal (or any other fully gtk3 native app) gets
these right. But the listed browsers is a mixed bag result.

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

Title:
   looks odd in thunderbird, chrome/chromium, okish in firefox

Status in Mozilla Thunderbird:
  Unknown
Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  New install of 18.04 and thunderbird is showing weird images in odd
  places for some email.  See screen shot for example.  In this case it
  is a weird rainbow, but I have also seen other things like a big stop
  sign and other strange stuff.

  
  Emoji support is inconsistent:
  - google chrome title is good
  - firefox title is good
  - google chrome contents, is bad, black ascii icon
  - fiefox contents, is ok, not the same icon as in the title
  - thunderbird content is ok, but too huge

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

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

[Touch-packages] [Bug 1722185] Re: Crash installing packages using debconf

[Steve Langasek]

Hello errors.ubuntu.com, or anyone else affected,

Accepted packagekit into bionic-proposed. The package will build now and
be available at
https://launchpad.net/ubuntu/+source/packagekit/1.1.9-1ubuntu2.18.04.1
in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-bionic to verification-done-bionic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-bionic. In either case, without details of
your testing we will not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: packagekit (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

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

Title:
  Crash installing packages using debconf

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  Installing .deb package via PackageKit (e.g. using GNOME Software) don't work 
reliably when the packages use debconf. This is due to a faulty implementation 
of debconf handling in PackageKit.

  [Test Case]
  1. Download opera deb file from opera.com
  2. Run the file to launch gnome-software
  3. Install it
  4. Proceed with the debconf prompt

  Expected result:
  A debconf dialog appears asking if you want to "update Opera with the rest of 
the system?". The dialog closes when completed and the package is installed.

  Actual result:
  The dialog shows, but never closes and becomes unresponsive. Force closing 
the dialog causes a crash.

  [Regression Potential]
  The change is quite large, so there is a reasonable chance of introducing new 
bugs in debconf handling. However, the existing code has some obviously wrong 
codepaths, so the new code is probably a lower risk than the existing code.

  Crash reports:
  https://errors.ubuntu.com/problem/f111546905209e7288c7f8ba5f8f19eea4d97bad

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

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

[Touch-packages] [Bug 1698270] Re: Totem pauses and stutters during video playback even when CPU usage is low

[Daniel van Vugt]

** Changed in: clutter-1.0 (Ubuntu)
   Status: Won't Fix => New

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

Title:
  Totem pauses and stutters during video playback even when CPU usage is
  low

Status in GStreamer:
  Confirmed
Status in GTK+:
  Fix Released
Status in totem-pl-parser:
  Expired
Status in clutter-1.0 package in Ubuntu:
  New
Status in clutter-gst-3.0 package in Ubuntu:
  Incomplete
Status in clutter-gtk package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Incomplete
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in totem-pl-parser package in Ubuntu:
  Fix Released

Bug description:
  Totem pauses and stutters during video playback even when CPU usage is
  low.

  After figuring out how to play videos with full hardware accelerated
  decoding (e.g. <= 10% CPU), I was surprised to find Totem still pauses
  and stutters during playback. Other apps like Mplayer, VLC and even
  gst-play-1.0 never have this problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: totem 3.24.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-22.24-generic 4.10.15
  Uname: Linux 4.10.0-22-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Fri Jun 16 12:03:18 2017
  InstallationDate: Installed on 2017-05-03 (44 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170502)
  SourcePackage: totem
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)

[Daniel van Vugt]

Thanks. Can you please test v4.15-rc1 to be sure?

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1779411] Re: info about bug appeared on screen earlier today

[Daniel van Vugt]

You can check /var/crash by:

  * Opening "Files", Ctrl+L, type "/var/crash"; or
  * In a terminal:
  cd /var/crash
  ls

If there are any crash files then you will need to be using the terminal
option before 'ubuntu-bug' will work.

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

Title:
  info about bug appeared on screen earlier today

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  i was watching hawaiian volcano videos this morning and the screen
  locked up. i restarted the computer and the error message
  appeared(error with 18.04 was the message). however, prior to that,
  grub appeared to show a problem beginning to form about a week ago.
  grub used to be a short startup leading to give me a choice of which
  hard drive i wanted to begin with(1 tb wd black and a 250gb samsung
  ssd. both drives have linux 18.04, one ubuntu and one kubuntu. only
  the ubuntu is acting up. for the past two days, grub is showing me
  every line of the startup process, although the ubuntu is otherwise
  starting normally. i know enough to enter code correctly in the
  terminal(e.g. sudo apt-get upgrade etc) and like the simplicity and
  independence of linux but regret that i must have the code spelled out
  for me if mistakes are to be avoided. i'm old and don't mind admitting
  it. hope this helps. cheers. paul.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompositorRunning: None
  Date: Fri Jun 29 13:48:50 2018
  DistUpgraded: 2018-06-05 12:53:32,893 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4250] [1002:9715] 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd RS880 [Radeon HD 4250] [1458:d000]
  InstallationDate: Installed on 2015-05-30 (1125 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  MachineType: Gigabyte Technology Co., Ltd. GA-880GM-UD2H
  ProcEnviron:
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=1b13c61c-0cc4-4160-9da5-fddeca76ae93 ro
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-06-05 (24 days ago)
  dmi.bios.date: 03/24/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F4
  dmi.board.name: GA-880GM-UD2H
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF4:bd03/24/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-880GM-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-880GM-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-880GM-UD2H
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Jun  5 08:12:34 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1779708] Re: My screen got deconfigurtated

[Daniel van Vugt]

Firstly, please take a photo of the problem and attach it here.

Secondly, 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.


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

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

Title:
  My screen got deconfigurtated

Status in Ubuntu:
  Incomplete

Bug description:
  WHen I get into google or some other programs, my screen fails, and
  don't work any longer. It became a screen like that of the Tv shows
  when there is not signal, and it just doesn't respond any more. I
  can't do anything, and I must restart the PC, the screen doesn't allow
  me to do any other operation. I previously have the 16.04 LTS ubuntu
  with unity and conpiz, and I tried to actualize it to 18.04  LTS
  version, the bug began.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jul  2 10:07:31 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
  InstallationDate: Installed on 2015-04-16 (1172 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=78b08060-d316-4ee6-92e7-4f94861741cd ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/15/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F1
  dmi.board.name: M68MT-S2
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/15/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: M68MT-S2
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.92+git20180609.c1f2d9b9-0ubuntu0ricotz~18.04.1
  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 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Mon Jul  2 09:02:38 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Generic Wheel Mouse MOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1768379] Re: python3-minimal should predepend on versioned version of python3-minimal

[Seth Arnold]

Hello Nataly, try this, all as root (sudo before each command, or one
sudo -s before them all..)

apt-get update
apt-get install python3.6-minimal
apt-get install python3-minimal
apt-get install python3
apt-get install -f

Thanks

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

Title:
  python3-minimal should predepend on versioned version of
  python3-minimal

Status in python3-defaults package in Ubuntu:
  Triaged
Status in ubuntu-release-upgrader package in Ubuntu:
  Invalid
Status in python3-defaults source package in Artful:
  Fix Committed
Status in ubuntu-release-upgrader source package in Artful:
  Invalid
Status in python3-defaults source package in Bionic:
  Fix Committed
Status in ubuntu-release-upgrader source package in Bionic:
  Invalid
Status in python3-defaults package in Debian:
  Fix Released

Bug description:
  [Impact]
  Release upgrades from Ubuntu 16.04 LTS to either Ubuntu 17.10 or Ubuntu 18.04 
LTS can fail if python3-minimial is unpacked before python3.x-minimal so a 
system won't have a usable python3 symlink. Then upgrades will fail because 
py3clean, used in prerm scripts of python3 packages, will fail with "not found".

  [Test Case]
  1) on a Ubuntu 16.04 LTS system with python3-apt installed download debs for 
Ubuntu 17.10 or 18.04 LTS of python3-minimal and python3-apt
  2) dpkg --unpack python3-minimal...
  3) dpkg --unpack python3-apt...

  Observe the following Traceback:

  Preparing to unpack .../python3-apt_1.4.0_beta3build2_amd64.deb ...
  /var/lib/dpkg/info/python3-apt.prerm: 6: 
/var/lib/dpkg/info/python3-apt.prerm: py3clean: not found
  dpkg: warning: subprocess old pre-removal script returned error exit status 
127
  dpkg: trying script from the new package instead ...
  /var/lib/dpkg/tmp.ci/prerm: 6: /var/lib/dpkg/tmp.ci/prerm: py3clean: not found
  dpkg: error processing archive 
/home/jak/Downloads/python3-apt_1.4.0_beta3build2_amd64.deb (--unpack):
   subprocess new pre-removal script returned error exit status 127
  /var/lib/dpkg/info/python3-apt.postinst: 6: 
/var/lib/dpkg/info/python3-apt.postinst: py3compile: not found
  dpkg: error while cleaning up:
   subprocess installed post-installation script returned error exit status 127

  With the deb python3-minimal from -proposed you won't be able to
  unpack python3-minimal without first installing python3.6-minimal.
  While that may qualify as verification it'd still be good to test
  unpacking python3-apt. To do that you'll need to install
  python3.6-minimal from the target release by editing you
  /etc/apt/sources.list to the new release, running 'apt-get update',
  and then 'apt-get install python3.6-minimal'. After that's all done
  you can try steps 2 and 3 from the test case again and you should not
  receive a Traceback.

  [Regression Potential]
  Its possible this could cause or reveal different upgrade failures so some 
extensive (desktop, cloud, server) upgrade testing should be done.

  
  [A Portion of the Original Description (it was a huge blob of failure)]
  do-release-upgrade -d  on my 16.04 LTS unity laptop lead to an install 
failure:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1768379/+subscriptions

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

[Touch-packages] [Bug 1779658] Re: Dropping to shell twice crashes system

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

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

Title:
  Dropping to shell twice crashes system

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  If you have an X session open, and you drop to shell using ctrl+alt+fN (e.g. ctrl+alt+f6), return to X session using ctrl+alt+f2 (or f1), and 
repeat once more:
  Expected result:
  - Normal functioning X session
  Real result:
  - No interaction with the system possible anymore.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..25.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:25: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)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jul  2 13:24:01 2018
  DistUpgraded: 2018-06-06 15:37:57,793 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-22-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-23-generic, x86_64: installed
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GP107 [GeForce GTX 1050] [10de:1c81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd GP107 [GeForce GTX 1050] 
[1458:3747]
  InstallationDate: Installed on 2018-02-22 (129 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Micro-Star International Co., Ltd. MS-7A34
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=6c4a23a4-85d5-4ec4-b6f1-cfececbb0353 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-06-06 (25 days ago)
  dmi.bios.date: 09/19/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.90
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B350 TOMAHAWK (MS-7A34)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.90:bd09/19/2017:svnMicro-StarInternationalCo.,Ltd.:pnMS-7A34:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB350TOMAHAWK(MS-7A34):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7A34
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.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/1779658/+subscriptions

-- 
Mailing 

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

[Daniel van Vugt]

** Tags added: suspend-resume

** Summary changed:

- Xorg freeze
+ After putting my laptop to suspend (lid down), it does not wake up again

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

Title:
  After putting my laptop to suspend (lid down), it does not wake up
  again

Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I am using Ubuntu 16.04. After putting my laptop to suspend (lid
  down), it does not wake up again. This does not happen when I lock it
  (windows key + L) it resumes operation on keypress. This has started
  happening around 1 month ago, I am not exactly sure. This is an Asus
  K501UW

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.10.0-041000-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.130  Wed Mar 21 03:37:26 
PDT 2018
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  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: Mon Jul  2 20:22:52 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Continuously
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Since a couple weeks or more
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:11e0]
 Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:11e0]
  InstallationDate: Installed on 2016-11-02 (606 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. K501UW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-041000-generic 
root=UUID=5e76175a-3add-425a-938f-e3e5c13bd41b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/30/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K501UW.203
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K501UW
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: K501UW
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-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 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jul  2 20:13:27 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7

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

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

[Touch-packages] [Bug 1779782] [NEW] package poppler-utils 0.41.0-0ubuntu1.7 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su c

[Mari Carmen]

Public bug reported:

Hi. I have no idea what this is. Apparently everything is fine, no crashes at 
all. Since I upgraded (always in Terminal) this issue pop's up when I restart 
the pc.
My computer knowledge is really low, so I hope you can detect if it's a bug or 
not.

Sorry if I waisted your time. I was uncertain if this is important or
not.

Have a nice day.
Kind regards from Spain.

Mari Carmen

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: poppler-utils 0.41.0-0ubuntu1.7
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: Mon Jul  2 18:14:06 2018
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2018-01-29 (154 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: poppler
Title: package poppler-utils 0.41.0-0ubuntu1.7 failed to install/upgrade: El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package xenial

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

Title:
  package poppler-utils 0.41.0-0ubuntu1.7 failed to install/upgrade: El
  paquete está en un estado grave de inconsistencia - debe reinstalarlo
  antes de intentar su configuración.

Status in poppler package in Ubuntu:
  New

Bug description:
  Hi. I have no idea what this is. Apparently everything is fine, no crashes at 
all. Since I upgraded (always in Terminal) this issue pop's up when I restart 
the pc.
  My computer knowledge is really low, so I hope you can detect if it's a bug 
or not.

  Sorry if I waisted your time. I was uncertain if this is important or
  not.

  Have a nice day.
  Kind regards from Spain.

  Mari Carmen

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: poppler-utils 0.41.0-0ubuntu1.7
  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: Mon Jul  2 18:14:06 2018
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2018-01-29 (154 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: poppler
  Title: package poppler-utils 0.41.0-0ubuntu1.7 failed to install/upgrade: El 
paquete está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 86281] Re: unable to record sound with istanbul

[Bug Watch Updater]

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

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

Title:
  unable to record sound with istanbul

Status in Istanbul:
  Won't Fix
Status in istanbul package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: istanbul

  steko@cycnus:~$ istanbul 
  DEBUG: final pipeline: oggmux name=mux ! filesink location=/tmp/tmp8aQuFY 
istximagesrc name=videosource ! video/x-raw-rgb,framerate=10/1 ! videorate ! 
ffmpegcolorspace ! videoscale method=1 ! 
video/x-raw-yuv,width=1280,height=800,framerate=10/1 ! theoraenc ! queue ! mux. 
gconfaudiosrc name=audiosource ! audioconvert ! vorbisenc ! queue ! mux.

  When I start recording, I get an error alert :
  There was an error recording: Risorsa occupata o non disponibile.

  Debug Information:
  gstalsasrc.c(608): gst_alsasrc_open (): /pipeline0/audiosource/bin0/alsasrc0:
  Device 'default' is busy

  I have PulseAudio installed instead of ESD (don't know if it's
  related, just a guess)

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

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

[Touch-packages] [Bug 1771764] Re: iproute2: unable to add ip lwt mpls route on xenial

[Khaled El Mously]

Proposed fix for lp #1771764 and lp #1771783

** Patch added: "proposed-fix-1771764-1771783.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771764/+attachment/5158998/+files/proposed-fix-1771764-1771783.debdiff

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

Title:
  iproute2: unable to add ip lwt mpls route on xenial

Status in iproute2 package in Ubuntu:
  Incomplete

Bug description:
  The following command does not work:

  $ ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev ntfp2
  Error: "nexthop" or end of line is expected instead of "encap"

  In fact, iproute2 version points to v4.3.0, but the xenial kernel is a 4.4.
  $ ip -V
  ip utility, iproute2-ss151103

  =>
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=6720eceff7b4

  With an iproute2 v4.4.0 (iproute2-ss160111), that command works:
  $ modprobe mpls_iptunnel
  $ ./ip/ip route add 10.201.0.0/24 nexthop encap mpls 300 via 10.200.0.1 dev 
ntfp2
  $ ./ip/ip r
  [snip]
  10.201.0.0/24  encap mpls  300 via 10.200.0.1 dev ntfp2

  At least, this patch is missing:
  1e5293056a02 ("lwtunnel: Add encapsulation support to ip route")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=1e5293056a02

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

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

[Touch-packages] [Bug 1771783] Re: iproute2: frr route protocols are not converted to string on xenial

[Khaled El Mously]

Proposed fix for lp #1771764 and lp #1771783

Please ignore the first proposal.

** Patch added: "proposed-fix-1771764-1771783.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/iproute2/+bug/1771783/+attachment/5159000/+files/proposed-fix-1771764-1771783.debdiff

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

Title:
  iproute2: frr route protocols are not converted to string on xenial

Status in iproute2 package in Ubuntu:
  New

Bug description:
  FRR puts its own proto numbers when inserting a route, example:
  $ ip route
  [snip]
  2.2.2.0/24 via 3.3.3.2 dev eth2  proto 188  metric 20 

  iproute2 defines some protocols, but not all:
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/tree/etc/iproute2/rt_protos

  A patch has been pushed upstream so that external applications can define 
their protocols numbers:
  719e331ff619 ("Add support for rt_protos.d")
  
https://git.kernel.org/pub/scm/network/iproute2/iproute2.git/commit/?id=719e331ff619

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

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

[Touch-packages] [Bug 590300] Re: RIdiculously misleading error message from passwd

[Matthew Kenigsberg]

I don't think this is a problem with shadow - it looks like that error
message is being given by pam. It makes a little more sense for
pam_chauthtok to give that error.

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

Title:
  RIdiculously misleading error message from passwd

Status in shadow package in Ubuntu:
  Triaged

Bug description:
  In Ubuntu server 10.04 LTS, I typed passwd to change my password and
  accidentally typed the new password in response to the prompt for the
  current password.  Instead of saying "incorrect password" or something
  equally reasonable, which would have caused me to smack my forehead
  and do it right the next time, I got the insane response "passwd:
  Authentication token manipulation error"!  This caused me to go down a
  rathole for fifteen minutes, reading many pages with many possible
  reasons for this error, none of which were "you mistyped your original
  password".

  This is a real user-interface FAIL and is certainly a regression in
  understandability.  It's obviously been there for a while; 9.04 does
  this, although I note that Hoary 5.04 (yes, I still have a machine
  that old) says "passwd: Authentication failure" instead, which, while
  still not exactly user-friendly, at least puts "authentication" and
  "failure"  -and nothing else- into the error to give people half a
  clue that maybe they mistyped something.  (It's still not an error
  message users should see, compared to "incorrect password".)  But the
  current error message is so obfuscated ("token manipulation error"---
  wtf is -that-?) that it's absolutely no help at all---either to a user
  trying to figure out what's going on, -or- to Google, considering how
  many other scenarios cause it to spit out that error message.

  Yuck.

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

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

[Touch-packages] [Bug 1779690] Re: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127

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

Title:
  package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 127

Status in apt package in Ubuntu:
  New

Bug description:
  Prompt to send bug report.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1441 F pulseaudio
eric   2355 F pulseaudio
  Date: Mon Jul  2 07:10:03 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  InstallationDate: Installed on 2018-04-27 (66 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 04f3:24c6 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 04f2:b59c Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. Q534UXK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=272c1568-fcce-4cb1-829d-2fb04fdcdd33 ro quiet splash vt.handoff=1
  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: grub-pc N/A
  SourcePackage: apt
  Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Q534UXK.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Q534UXK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 31
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrQ534UXK.304:bd12/05/2016:svnASUSTeKCOMPUTERINC.:pnQ534UXK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ534UXK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
  dmi.product.family: Q
  dmi.product.name: Q534UXK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1779667] Re: Unlocking existing session yields black screen. Closing session does not help as affected user cannot open a successful X session until next reboot. Other users are

[Simon McVittie]

Please attach anything vaguely relevant-looking from the system log
(systemd Journal if you use systemd, or /var/log/syslog). The bug will
probably be somewhere in the vicinity of logind, PAM, dbus-daemon,
lightdm, X or XFCE, or possibly graphics drivers in the kernel (which
have been known to lock up during fast-user-switching), but without
looking at the log it's impossible to say which.

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

Title:
  Unlocking existing session yields black screen. Closing session does
  not help as affected user cannot open a successful X session until
  next reboot. Other users are ok.

Status in dbus package in Ubuntu:
  New

Bug description:
  # Context

  * Xubuntu 18.04 using lightdm, no specific customization, no 
xscreensaver/gnome-screensaver.
  * Problem observed two machines:
  ** one machine with several users often swapping sessions,
  ** one machine with just one regular user who just locks/unlocks session often

  
  # Action

  * Open a XFCE session.
  * Lock it.
  * On greeter, type password to unlock.

  
  # Expected

  * Get back to opened session.

  
  # Observed

  * After typing password, screen turns to black.  All pixels are fully black.
  * Not even a mouse pointer is visible.

  
  # Reproducible

  * Seems random.
  * Perhaps one time out of 20-50 unlock operations.
  * Never occurred in 16.04 14.04

  
  # Detailed information

  From start:

  * On unlocking an already opened session, after typing password screen
  turns to full black.

  
  ## Investigation: is machine still okay?

  * As a sanity check, switching to text VT works, login on text VT
  works.

  
  ## Investigation: problem does not affect all sessions at once

  * Bug observed both in one system with one user at a time, and on another 
system with two users alternating X sessions.
  * From tty1, using "dm-tool switch-to-greeter" with proper environment works, 
allows to select other user's session, type password and return to that other 
user's opened session. Any attempt to return to affected user session yields 
black screen.

  
  ## Investigation: problem affects user even after closing all their programs

  * Manually killing affected user processes allows to close faulty session and 
see lightdm greeter come back.
  * Trying to reopen a session (as usual with lightdm) as affected user shows 
an error dialog:

  "Unable to contact settings server
  Failed to connect to socket /run/user/1000/bus: Connection refused"
  and a "Close" button.

  Clicking on it yields a second dialog :

  "Unable to load failsafe session
  Unable to determine a failsafe session name. Possible causes:
  xfconfd isn't running (D-Bus setup problem);
  environment variable $XDG_CONFIG_DIRS is set incorrectly (must include 
"/etc"),
  or xfce4-session is installed incorrectly."
  and a "Quit" button.

  Clicking "quit" button goes back to lightdm greeter.

  
  ## Investigation: reboot solves the problem

  * Rebooting the machine solves the problem (but closes all user sessions and 
processes).
  * Problem reappears after a few days.

  
  ## Investigation: startx affected, too

  * From text VT, startx has same behavior as running from lightdm and
  thus also cannot reach a working XFCE desktop.

  
  ## Investigation: affected user has no dbus-daemon running.

  * No "/usr/bin/dbus-daemon" runs as affected user while it runs as
  other users.

  
  ## Additional information

  * It is believed that the multi-user system makes the bug more salient than 
usual workflow because users switch more often from one session to another.
  * It is believed that the single-user system makes the bug more salient than 
usual workflow because users often locks and unlocks their session.


  
  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu

  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  Actually Xubuntu 18.04.

  2) The version of the package you are using, via 'apt-cache policy
  pkgname' or by checking in Software Center

  export LC_ALL=C ; apt-cache policy dbus

  dbus:
Installed: 1.12.2-1ubuntu1
Candidate: 1.12.2-1ubuntu1
Version table:
   *** 1.12.2-1ubuntu1 500
  500 http://fr.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  
  3) What you expected to happen
  4) What happened instead

  Described above.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dbus 1.12.2-1ubuntu1
  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: Mon Jul  2 13:43:08 2018
  InstallationDate: Installed on 2018-05-25 (38 days ago)
  InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no 

[Touch-packages] [Bug 1779569] Re: thunderbird showing weird images in some mail

[Dimitri John Ledkov ]

** Attachment added: "rainbow-bug.png"
   
https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1779569/+attachment/5158835/+files/rainbow-bug.png

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

** Also affects: ubuntu-meta (Ubuntu)
   Importance: Undecided
   Status: New

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

** Description changed:

  New install of 18.04 and thunderbird is showing weird images in odd
  places for some email.  See screen shot for example.  In this case it is
  a weird rainbow, but I have also seen other things like a big stop sign
  and other strange stuff.
+ 
+ 
+ Emoji support is inconsistent:
+ - google chrome title is good
+ - firefox title is good
+ - google chrome contents, is bad, black ascii icon
+ - fiefox contents, is ok, not the same icon as in the title
+ - thunderbird content is ok, but too huge

** Summary changed:

- thunderbird showing weird images in some mail
+  looks odd in thunderbird showing weird images in some mai

** Summary changed:

-  looks odd in thunderbird showing weird images in some mai
+  looks odd in thunderbird, chrome/chromium, okish in firefox

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

Title:
   looks odd in thunderbird, chrome/chromium, okish in firefox

Status in chromium package in Ubuntu:
  New
Status in firefox package in Ubuntu:
  New
Status in thunderbird package in Ubuntu:
  New
Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  New install of 18.04 and thunderbird is showing weird images in odd
  places for some email.  See screen shot for example.  In this case it
  is a weird rainbow, but I have also seen other things like a big stop
  sign and other strange stuff.

  
  Emoji support is inconsistent:
  - google chrome title is good
  - firefox title is good
  - google chrome contents, is bad, black ascii icon
  - fiefox contents, is ok, not the same icon as in the title
  - thunderbird content is ok, but too huge

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

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

[Touch-packages] [Bug 1779720] [NEW] Thinkpad Extra Buttons - two keys not recognized

[Wilmer Ansgariusson]

Public bug reported:

These two keys out of Thinkpad Extra Buttons are not recognized when
trying to setup keyboard shortcuts in settings:

"Keyboard Icon" Button: MSC_SCAN 49
"Star Icon" Button: MSC_SCAN 45

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: udev 237-3ubuntu10
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
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules 
70-snap.gimp.rules 70-snap.canonical-livepatch.rules 70-snap.keepassxc.rules
Date: Mon Jul  2 18:28:58 2018
InstallationDate: Installed on 2018-07-01 (0 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
MachineType: LENOVO 20KHCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=40e13b59-4cfd-42bb-a056-6e9b72aa999c ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/13/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET40W (1.15 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET40W(1.15):bd04/13/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHCTO1WW
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

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

Title:
  Thinkpad Extra Buttons - two keys not recognized

Status in systemd package in Ubuntu:
  New

Bug description:
  These two keys out of Thinkpad Extra Buttons are not recognized when
  trying to setup keyboard shortcuts in settings:

  "Keyboard Icon" Button: MSC_SCAN 49
  "Star Icon" Button: MSC_SCAN 45

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10
  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
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.spotify.rules 70-snap.core.rules 
70-snap.gimp.rules 70-snap.canonical-livepatch.rules 70-snap.keepassxc.rules
  Date: Mon Jul  2 18:28:58 2018
  InstallationDate: Installed on 2018-07-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: LENOVO 20KHCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=40e13b59-4cfd-42bb-a056-6e9b72aa999c ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/13/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET40W (1.15 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET40W(1.15):bd04/13/2018:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHCTO1WW
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1779690] [NEW] package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 127

[Eric Kiesow]

Public bug reported:

Prompt to send bug report.

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-24-generic 4.15.0-24.26
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1441 F pulseaudio
  eric   2355 F pulseaudio
Date: Mon Jul  2 07:10:03 2018
ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
InstallationDate: Installed on 2018-04-27 (66 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 04f3:24c6 Elan Microelectronics Corp. 
 Bus 001 Device 002: ID 04f2:b59c Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. Q534UXK
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=272c1568-fcce-4cb1-829d-2fb04fdcdd33 ro quiet splash vt.handoff=1
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: grub-pc N/A
SourcePackage: apt
Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/05/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: Q534UXK.304
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: Q534UXK
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 31
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrQ534UXK.304:bd12/05/2016:svnASUSTeKCOMPUTERINC.:pnQ534UXK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ534UXK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:
dmi.product.family: Q
dmi.product.name: Q534UXK
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.

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


** Tags: amd64 apport-package bionic need-duplicate-check

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

Title:
  package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 127

Status in apt package in Ubuntu:
  New

Bug description:
  Prompt to send bug report.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-image-4.15.0-24-generic 4.15.0-24.26
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1441 F pulseaudio
eric   2355 F pulseaudio
  Date: Mon Jul  2 07:10:03 2018
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  InstallationDate: Installed on 2018-04-27 (66 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 04f3:24c6 Elan Microelectronics Corp. 
   Bus 001 Device 002: ID 04f2:b59c Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. Q534UXK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=272c1568-fcce-4cb1-829d-2fb04fdcdd33 ro quiet splash vt.handoff=1
  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: grub-pc N/A
  SourcePackage: apt
  Title: package linux-image-4.15.0-24-generic 4.15.0-24.26 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 127
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/05/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: Q534UXK.304
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: Q534UXK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset 

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

[Nikhil Pinnaparaju]

Public bug reported:

I am using Ubuntu 16.04. After putting my laptop to suspend (lid down),
it does not wake up again. This does not happen when I lock it (windows
key + L) it resumes operation on keypress. This has started happening
around 1 month ago, I am not exactly sure. This is an Asus K501UW

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
Uname: Linux 4.10.0-041000-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.130  Wed Mar 21 03:37:26 
PDT 2018
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
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: Mon Jul  2 20:22:52 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Continuously
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Since a couple weeks or more
GraphicsCard:
 Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Skylake Integrated Graphics [1043:11e0]
   Subsystem: ASUSTeK Computer Inc. GM107M [GeForce GTX 960M] [1043:11e0]
InstallationDate: Installed on 2016-11-02 (606 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 0bda:57ed Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. K501UW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-041000-generic 
root=UUID=5e76175a-3add-425a-938f-e3e5c13bd41b ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/30/2016
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K501UW.203
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K501UW
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK501UW.203:bd03/30/2016:svnASUSTeKCOMPUTERINC.:pnK501UW:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnK501UW:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.name: K501UW
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-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 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.2
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Mon Jul  2 20:13:27 2018
xserver.configfile: /etc/X11/xorg.conf
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7

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


** Tags: amd64 apport-bug compiz-0.9 freeze third-party-packages 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/1779704

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  I am using Ubuntu 16.04. After putting my laptop to suspend (lid
  down), it does not wake up again. This does not happen when I lock it
  (windows key + L) it resumes operation on keypress. This has started
  happening around 1 month ago, I am not exactly sure. This is an Asus
  K501UW

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  Uname: Linux 4.10.0-041000-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: 

[Touch-packages] [Bug 1779583] Re: cron do_command.c attempts a fork() without testing for errors

[Brian Murray]

** Tags added: cosmic

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

Title:
  cron do_command.c attempts a fork() without testing for errors

Status in cron package in Ubuntu:
  New

Bug description:
  The do_command.c file calls fork() twice.

  For the first fork(), the possibility for an error is checked properly
  and an error emitted (see
  https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1702785 for an
  example when that happens: message is "can't fork".) This first fork()
  makes use of a switch() statement as expected.

  The second fork(), however, is used inside an if() statement like
  this:

  if (*input_data && fork() == 0) { ... }

  Here we can see a couple of problems. After the if block, we have this
  statement:

  children++;

  which means that we will have to wait on TWO children. However, (1)
  the *input_data could return false and thus the second child may not
  be created at all. (2) the fork() could return -1 meaning that no
  other child is created.

  I suppose that the child_process() probably always or nearly always
  has some input_data. Otherwise it would block waiting for a child that
  was never started. And of course, it is relatively rare that fork()
  fails, unless you are running our of RAM (heap or stack can't be
  allocated) or process space (too many processes running concurrently.)

  I have a proposed patch to fix the problem. It uses a switch() which
  emits an error in case the fork() fails, but let the program go on as
  before (instead of an immediate exit as in the first fork()).

  The children variable gets incremented only when the fork() happens
  and succeeds (default: block in the new switch().)

  The do_command.c file did not change between 16.04 (trusty) and 18.04
  (bionic beaver), so the patch will work for either version.

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

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

[Touch-packages] [Bug 1779721] [NEW] systemd-networkd does not configure DHCPv4

[Benjamin Drung]

Public bug reported:

I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
systemd 237-3ubuntu10) which has following netplan configuration:

```
root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
all:
  match: {}
  dhcp4: yes
root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
[Match]

[Network]
DHCP=ipv4

[DHCP]
UseMTU=true
RouteMetric=100
```

Despite having DHCPv4 configured, no IPv4 address is configured on the
ethernet device:

```
root@ubuntu:~# ip a show ens6
2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
inet6 fe80::1:71ff:fe8f:cc72/64 scope link
   valid_lft forever preferred_lft forever
```

The kernel dmesg has no related messages and the journal log also looks
normal:

```
root@ubuntu:~# journalctl -u systemd-networkd
Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
```

Calling dhclient sets up the device correctly:

```
root@ubuntu:~# dhclient ens6
root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
lease {
  interface "ens6";
  fixed-address 87.106.172.36;
  option subnet-mask 255.255.255.255;
  option dhcp-lease-time 600;
  option routers 87.106.172.1;
  option dhcp-message-type 5;
  option domain-name-servers 46.16.74.70,46.16.72.37;
  option dhcp-server-identifier 87.106.172.1;
  option interface-mtu 64000;
  option host-name "ubuntu-18_04-fkb-2018-07-02";
  renew 1 2018/07/02 16:46:51;
  rebind 1 2018/07/02 16:51:31;
  expire 1 2018/07/02 16:52:46;
}
root@ubuntu:~# ip a show ens6
2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
inet 87.106.172.36/32 brd 87.106.172.36 scope global ens6
   valid_lft forever preferred_lft forever
inet6 fe80::1:71ff:fe8f:cc72/64 scope link 
   valid_lft forever preferred_lft forever
```

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

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

Title:
  systemd-networkd does not configure DHCPv4

Status in systemd package in Ubuntu:
  New

Bug description:
  I have an up-to-date Ubuntu 18.04 (bionic) server installation (with
  systemd 237-3ubuntu10) which has following netplan configuration:

  ```
  root@ubuntu:~# cat /etc/netplan/01-netcfg.yaml 
  # This file describes the network interfaces available on your system
  # For more information, see netplan(5).
  network:
version: 2
renderer: networkd
ethernets:
  all:
match: {}
dhcp4: yes
  root@ubuntu:~# cat /run/systemd/network/10-netplan-all.network  
  [Match]

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100
  ```

  Despite having DHCPv4 configured, no IPv4 address is configured on the
  ethernet device:

  ```
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  link/ether 02:01:71:8f:cc:72 brd ff:ff:ff:ff:ff:ff
  inet6 fe80::1:71ff:fe8f:cc72/64 scope link
 valid_lft forever preferred_lft forever
  ```

  The kernel dmesg has no related messages and the journal log also
  looks normal:

  ```
  root@ubuntu:~# journalctl -u systemd-networkd
  Jul 02 16:36:51 ubuntu systemd[1]: Starting Network Service...
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: ens6: Gained IPv6LL
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: Enumeration completed
  Jul 02 16:36:51 ubuntu systemd[1]: Started Network Service.
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Link is not managed by us
  Jul 02 16:36:51 ubuntu systemd-networkd[1790]: lo: Configured
  ```

  Calling dhclient sets up the device correctly:

  ```
  root@ubuntu:~# dhclient ens6
  root@ubuntu:~# cat /var/lib/dhcp/dhclient.leases
  lease {
interface "ens6";
fixed-address 87.106.172.36;
option subnet-mask 255.255.255.255;
option dhcp-lease-time 600;
option routers 87.106.172.1;
option dhcp-message-type 5;
option domain-name-servers 46.16.74.70,46.16.72.37;
option dhcp-server-identifier 87.106.172.1;
option interface-mtu 64000;
option host-name "ubuntu-18_04-fkb-2018-07-02";
renew 1 2018/07/02 16:46:51;
rebind 1 2018/07/02 16:51:31;
expire 1 2018/07/02 16:52:46;
  }
  root@ubuntu:~# ip a show ens6
  2: ens6:  mtu 64000 qdisc fq_codel state UP 
group default qlen 1000
  

[Touch-packages] [Bug 1779708] [NEW] My screen got deconfigurtated

[Alfonso Mahecha V.]

Public bug reported:

WHen I get into google or some other programs, my screen fails, and
don't work any longer. It became a screen like that of the Tv shows when
there is not signal, and it just doesn't respond any more. I can't do
anything, and I must restart the PC, the screen doesn't allow me to do
any other operation. I previously have the 16.04 LTS ubuntu with unity
and conpiz, and I tried to actualize it to 18.04  LTS version, the bug
began.

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
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Mon Jul  2 10:07:31 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
InstallationDate: Installed on 2015-04-16 (1172 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=78b08060-d316-4ee6-92e7-4f94861741cd ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/15/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F1
dmi.board.name: M68MT-S2
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF1:bd11/15/2010:svnGigabyteTechnologyCo.,Ltd.:pnM68MT-S2:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnM68MT-S2:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: M68MT-S2
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.92+git20180609.c1f2d9b9-0ubuntu0ricotz~18.04.1
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 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Jul  2 09:02:38 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputAT Translated Set 2 keyboard KEYBOARD, id 8
 inputImPS/2 Generic Wheel Mouse MOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4
xserver.video_driver: nouveau

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


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

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

Title:
  My screen got deconfigurtated

Status in xorg package in Ubuntu:
  New

Bug description:
  WHen I get into google or some other programs, my screen fails, and
  don't work any longer. It became a screen like that of the Tv shows
  when there is not signal, and it just doesn't respond any more. I
  can't do anything, and I must restart the PC, the screen doesn't allow
  me to do any other operation. I previously have the 16.04 LTS ubuntu
  with unity and conpiz, and I tried to actualize it to 18.04  LTS
  version, the bug began.

  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
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Mon Jul  2 10:07:31 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 7025 / nForce 630a] [10de:03d6] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd C61 [GeForce 7025 / nForce 630a] 
[1458:d000]
  InstallationDate: Installed on 2015-04-16 (1172 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. M68MT-S2
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-24-generic 
root=UUID=78b08060-d316-4ee6-92e7-4f94861741cd ro quiet splash 

[Touch-packages] [Bug 1769075] Re: [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel 4.15 and later)

[Vasilis]

I've tried the kernels from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D 
and the last one that I found workding was the 4.14.52,
I presume that the next one is the 4.15.rc1, which shows the problem.
Are there somewhere more builds in between those two that I can search?

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

Title:
  [regression][bionic] Bluetooth keyboard battery reports 0% (in kernel
  4.15 and later)

Status in bluez package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  I've recently upgraded to 18.04 from 17.10 and after the upgrade "upower -d"
  reports always 0% as battery percentage of the bluetooth Logitech K810 
keyboard.
  Which is a bit annoying since I get a KDE warning on the battery.

  Device: /org/freedesktop/UPower/devices/keyboard_hid_34o88o5do5eo0co2f_battery
native-path:  hid-34:88:5d:5e:0c:2f-battery
model:Logitech K810
power supply: no
updated:  Fri 04 May 2018 09:20:43 AM CEST (51 seconds ago)
has history:  yes
has statistics:   yes
keyboard
  present: yes
  rechargeable:yes
  state:   unknown
  warning-level:   none
  percentage:  0%
  icon-name:  'battery-missing-symbolic'

  My guess is that the issue is in the bluetooth rather in the upowerd
  since the reporting in the /sys/devices shows battery level of 0
  --- 
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  bnv1714 F pulseaudio
   /dev/snd/pcmC0D0p:   bnv1714 F...m pulseaudio
   /dev/snd/controlC0:  bnv1714 F pulseaudio
  CurrentDesktop: KDE
  DistroRelease: Ubuntu 18.04
  HibernationDevice: RESUME=UUID=e962613c-fc88-4740-8f0a-997838d3c2cf
  InstallationDate: Installed on 2017-11-02 (185 days ago)
  InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 
(20171017.1)
  IwConfig:
   lono wireless extensions.
   
   enp0s25   no wireless extensions.
  MachineType: Dell Inc. Precision Tower 5810
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: linux (not installed)
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-generic 
root=UUID=4940c5fe-b600-4f27-8586-c6ac06ccea99 ro vga=773 quiet
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  RelatedPackageVersions:
   linux-restricted-modules-4.15.0-20-generic N/A
   linux-backports-modules-4.15.0-20-generic  N/A
   linux-firmware 1.173
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  Tags:  bionic
  Uname: Linux 4.15.0-20-generic x86_64
  UpgradeStatus: Upgraded to bionic on 2018-04-30 (7 days ago)
  UserGroups: adm cdrom dialout dip kvm lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/08/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A19
  dmi.board.name: 0K240Y
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA19:bd05/08/2017:svnDellInc.:pnPrecisionTower5810:pvr:rvnDellInc.:rn0K240Y:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision Tower 5810
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 878667] Re: Some Ubuntu apps look poorly integrated

[gf]

Hello Glennz,
Thank you for submitting this bug and reporting a problem with the layout in 
"Natty" version of Ubuntu.

You made this bug report in 2011 and there have been several versions of
Ubuntu and Thunderbird since then.

Could you confirm that this is no longer a problem and that we can close the 
ticket? 
Or, if it is still a problem, could you run the following (only once):
apport-collect 878667

and upload the updated logs and and any other logs that are relevant for
this particular issue.

Thank you again for helping make Ubuntu and Thunderbird better.

G

** Changed in: ubuntu-meta (Ubuntu)
   Status: New => Incomplete

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

Title:
  Some Ubuntu apps look poorly integrated

Status in ubuntu-meta package in Ubuntu:
  Incomplete

Bug description:
  Ubuntu apps started to look less integrated in Natty, but in Oneiric it´s 
just terrible.
  Ubuntu One, Firefox, Thunderbird, Ubuntu Software Center, Nautilus, Settings 
Manager, they all look very different.
  Ubuntu One and USC looked fine a while ago, TB and FF use Xul so they are 
harder to integrate (but still), Nautilus looks weird because the toolbar got 
black, Settings Manager might be a GNOME3 problem.
  It gives Ubuntu a very unprofessional touch to it and we are becoming the 
next "That Redmond OS" in this way.
  I hope there is a way to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: ubuntu-desktop 1.245
  ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4
  Uname: Linux 3.0.0-12-generic i686
  ApportVersion: 1.23-0ubuntu3
  Architecture: i386
  Date: Thu Oct 20 07:58:46 2011
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  SourcePackage: ubuntu-meta
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1756238] Re: gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

[Launchpad Bug Tracker]

** Merge proposal linked:
   
https://code.launchpad.net/~canonical-desktop-team/ubuntu/+source/vte2.91/+git/vte2.91/+merge/348850

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

Title:
  gdebi-gtk broken in 18.04 error: unable to read filedescriptor flags

Status in gdebi package in Ubuntu:
  Triaged
Status in vte2.91 package in Ubuntu:
  Fix Released
Status in vte2.91 source package in Bionic:
  Fix Released

Bug description:
  When using gdebi-gtk to install a .deb the install fails with the
  message:-

  dpkg: error: unable to read filedescriptor flags for : Bad file descriptor

  This only occurs via the gdebi-gtk GUI front end, packages install perfectly 
if done via the CLI with:
  sudo gdebi /path/to/packagename.deb

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

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