[Touch-packages] [Bug 2042367] Re: eglinfo device platform eglInitialize failed

[Dean Wheatley]

I have upgraded from 22.04 to 23.10 and this issue is fixed:

Device platform:
Device #0:

EGL device extensions string:
EGL_EXT_device_drm, EGL_EXT_device_drm_render_node
Platform Device platform:
EGL API version: 1.5
EGL vendor string: Mesa Project
EGL version string: 1.5
EGL client APIs: OpenGL OpenGL_ES



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

Title:
  eglinfo device platform eglInitialize failed

Status in mesa package in Ubuntu:
  New

Bug description:
  On an Intel NUC13RNGi9 system with 13900K processor with integrated
  Intel UHD 770 Graphics, the command "eglinfo" fails to initialize the
  Device platform:

  $ eglinfo
  ...

  Device platform:
  eglinfo: eglInitialize failed

  
  The other platforms (X11, Wayland, GBM) initialize.

  The reason I am reporting is I'm trying to fix an issue in my system
  where:

  EGLDisplay display = eglGetDisplay(EGL_DEFAULT_DISPLAY)

  is returning EGL_NO_DISPLAY

  on my system, and I think it's due to the Device platform failing to
  initialize.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 09:42:40 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:a780] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:3033]
  InstallationDate: Installed on 2023-10-30 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Intel(R) Client Systems NUC13RNGi9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2023
  dmi.bios.release: 5.27
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: SBRPL579.0056.2023.0204.0233
  dmi.board.name: NUC13SBBi9
  dmi.board.vendor: Intel Corporation
  dmi.board.version: M58736-304
  dmi.chassis.type: 35
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2.0
  dmi.ec.firmware.release: 44.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrSBRPL579.0056.2023.0204.0233:bd02/04/2023:br5.27:efr44.0:svnIntel(R)ClientSystems:pnNUC13RNGi9:pvrM89920-304:rvnIntelCorporation:rnNUC13SBBi9:rvrM58736-304:cvnIntelCorporation:ct35:cvr2.0:skuRNUC13RNGi9:
  dmi.product.family: RN
  dmi.product.name: NUC13RNGi9
  dmi.product.sku: RNUC13RNGi9
  dmi.product.version: M89920-304
  dmi.sys.vendor: Intel(R) Client Systems
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

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


-- 
Mailing list: https://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 2042367] [NEW] eglinfo device platform eglInitialize failed

[Dean Wheatley]

Public bug reported:

On an Intel NUC13RNGi9 system with 13900K processor with integrated
Intel UHD 770 Graphics, the command "eglinfo" fails to initialize the
Device platform:

$ eglinfo
...

Device platform:
eglinfo: eglInitialize failed


The other platforms (X11, Wayland, GBM) initialize.

The reason I am reporting is I'm trying to fix an issue in my system
where:

EGLDisplay display = eglGetDisplay(EGL_DEFAULT_DISPLAY)

is returning EGL_NO_DISPLAY

on my system, and I think it's due to the Device platform failing to
initialize.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
Uname: Linux 6.2.0-36-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Nov  1 09:42:40 2023
DistUpgraded: Fresh install
DistroCodename: jammy
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation Device [8086:a780] (rev 04) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:3033]
InstallationDate: Installed on 2023-10-30 (1 days ago)
InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
MachineType: Intel(R) Client Systems NUC13RNGi9
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/04/2023
dmi.bios.release: 5.27
dmi.bios.vendor: Intel Corp.
dmi.bios.version: SBRPL579.0056.2023.0204.0233
dmi.board.name: NUC13SBBi9
dmi.board.vendor: Intel Corporation
dmi.board.version: M58736-304
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.ec.firmware.release: 44.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrSBRPL579.0056.2023.0204.0233:bd02/04/2023:br5.27:efr44.0:svnIntel(R)ClientSystems:pnNUC13RNGi9:pvrM89920-304:rvnIntelCorporation:rnNUC13SBBi9:rvrM58736-304:cvnIntelCorporation:ct35:cvr2.0:skuRNUC13RNGi9:
dmi.product.family: RN
dmi.product.name: NUC13RNGi9
dmi.product.sku: RNUC13RNGi9
dmi.product.version: M89920-304
dmi.sys.vendor: Intel(R) Client Systems
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.113-2~ubuntu0.22.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.0.4-0ubuntu1~22.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.4-2ubuntu1.7~22.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1

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


** Tags: amd64 apport-bug jammy ubuntu wayland-session

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

Title:
  eglinfo device platform eglInitialize failed

Status in xorg package in Ubuntu:
  New

Bug description:
  On an Intel NUC13RNGi9 system with 13900K processor with integrated
  Intel UHD 770 Graphics, the command "eglinfo" fails to initialize the
  Device platform:

  $ eglinfo
  ...

  Device platform:
  eglinfo: eglInitialize failed

  
  The other platforms (X11, Wayland, GBM) initialize.

  The reason I am reporting is I'm trying to fix an issue in my system
  where:

  EGLDisplay display = eglGetDisplay(EGL_DEFAULT_DISPLAY)

  is returning EGL_NO_DISPLAY

  on my system, and I think it's due to the Device platform failing to
  initialize.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 6.2.0-36.37~22.04.1-generic 6.2.16
  Uname: Linux 6.2.0-36-generic x86_64
  ApportVersion: 2.20.11-0ubuntu82.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Nov  1 09:42:40 2023
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:a780] (rev 04) (prog-if 00 [VGA controller])
 Subsystem: Intel Corporation Device [8086:3033]
  InstallationDate: Installed on 2023-10-30 (1 days ago)
  InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 
(20230807.2)
  MachineType: Intel(R) Client Systems NUC13RNGi9
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.2.0-36-generic 
root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/04/2023
 

[Touch-packages] [Bug 1969375] Re: systemd-cryptenroll does not support TPM2 devices

[Dean Huffman]

Thank you, I am away on holiday until next wednesday but I will test
during the second half of next week

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

Title:
  systemd-cryptenroll does not support TPM2 devices

Status in systemd package in Ubuntu:
  In Progress
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  In Progress

Bug description:
  [Impact]

   * TPM2/FIDO cannot be used to unlock luks encrpyted block devices
   * due to missing build-time support in systemd
   * Error message: "TPM2 not supported on this build."

  [Test Plan]

  # 1: check no new binary deps have been introduced to the systemd package, 
other than "libssl3", which is already installed by default.
  # Compare to this version of systemd 249.11-0ubuntu3.1:
  $ apt-cache depends systemd
  systemd
PreDepends: libblkid1
PreDepends: libc6
PreDepends: libcap2
PreDepends: libgcrypt20
PreDepends: liblz4-1
PreDepends: liblzma5
PreDepends: libselinux1
PreDepends: libzstd1
Depends: libacl1
Depends: libapparmor1
Depends: libaudit1
Depends: libcrypt1
Depends: libcryptsetup12
Depends: libgnutls30
Depends: libgpg-error0
Depends: libip4tc2
Depends: libkmod2
Depends: liblz4-1
Depends: libmount1
Depends: libpam0g
Depends: libseccomp2
Depends: libsystemd0
Depends: util-linux
Depends: mount
Depends: adduser
Conflicts: 
Conflicts: 
Conflicts: 
Breaks: resolvconf
Breaks: udev
   |Recommends: 
  dbus
Recommends: 
  dbus-broker
  dbus
Recommends: networkd-dispatcher
   |Recommends: systemd-timesyncd
Recommends: 
  chrony
  ntp
  ntpsec
  openntpd
  systemd-timesyncd
Suggests: systemd-container
Suggests: policykit-1

  # 2: check that systemd-cryptenroll doesn't have any undefined symbols that 
prevent it from running:
  $ systemd-cryptenroll --help  # this should not crash
  systemd-cryptenroll [OPTIONS...] BLOCK-DEVICE

  Enroll a security token or authentication credential to a LUKS volume.

-h --helpShow this help
   --version Show package version
   --passwordEnroll a user-supplied password
   --recovery-keyEnroll a recovery key
   --pkcs11-token-uri=URI
 Specify PKCS#11 security token URI
   --fido2-device=PATH
 Enroll a FIDO2-HMAC security token
   --fido2-with-client-pin=BOOL
 Whether to require entering a PIN to unlock the volume
   --fido2-with-user-presence=BOOL
 Whether to require user presence to unlock the volume
   --fido2-with-user-verification=BOOL
 Whether to require user verification to unlock the 
volume
   --tpm2-device=PATH
 Enroll a TPM2 device
   --tpm2-pcrs=PCR1+PCR2+PCR3+…
 Specify TPM2 PCRs to seal against
   --wipe-slot=SLOT1,SLOT2,…
 Wipe specified slots

  See the systemd-cryptenroll(1) man page for details.

  # initial setup
  $ dd if=/dev/zero of=encrypted.img bs=1 count=0 seek=100M
  $ echo -n "s0s3cur3" | cryptsetup luksFormat encrypted.img -
  $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img
   Please enter passphrase for disk volume: s0s3cur3
  Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img.
  $ sudo mkfs.ext4 /dev/mapper/volume
  $ sudo mount /dev/mapper/volume /mnt
  $ sudo touch /mnt/TPM_TEST
  $ ls -la /mnt
  drwxr-xr-x  3 root root  4096 Jun  7 15:06 .
  drwxr-xr-x 20 root root  4096 Apr 20 11:45 ..
  drwx--  2 root root 16384 Jun  7 15:06 lost+found
  -rw-r--r--  1 root root 0 Jun  7 15:06 TPM_TEST
  $ sudo umount /dev/mapper/volume
  $ sudo cryptsetup luksClose volume
  $ ls -la /mnt # empty

  # 3: check non-TPM use cases (--password & --recovery-key) of 
systemd-cryptenroll have not regressed.
  # enroll additional password
  $ systemd-cryptenroll --password encrypted.img
   Please enter current passphrase for disk 
/home/lukas/canonical/systemd-dbg/encrypted.img: s0s3cur3
   Please enter new passphrase for disk 
/home/lukas/canonical/systemd-dbg/encrypted.img: s0s3cr3t
   Please enter new passphrase for disk 
/home/lukas/canonical/systemd-dbg/encrypted.img (repeat): s0s3cr3t
  New password enrolled as key slot 1.
  $ sudo /usr/lib/systemd/systemd-cryptsetup attach volume encrypted.img
   Please enter passphrase for disk volume: s0s3cr3t
  Set cipher aes, mode xts-plain64, key size 512 bits for device encrypted.img.
  $ sudo cryptsetup luksClose volume
  $ systemd-cryptenroll --wipe-slot=1 encrypted.img
  Wiped slot 1.

  # enroll additional recovery-key
  $ systemd-cryptenroll --recovery-key encrypted.img
   Please 

[Touch-packages] [Bug 1969375] [NEW] systemd-cryptenroll does not support TPM2 devices

[Dean Huffman]

Public bug reported:

systemd-cryptenroll can make use of tpm2 modules to bind against secure
boot pcrs and enable auto unlocking of luks devices.

Following the instructions here:
https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll

the following commands fail on ubuntu jammy (5.15.0-25-generic)

root@testbox:~# systemd-cryptenroll --tpm2-device=list
TPM2 not supported on this build.
root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3
 Please enter current passphrase for disk /dev/sda3: ***
root@testbox:~# echo $?
1

It appears that this issue has been resolved in the debian build for
systemd here:  https://salsa.debian.org/systemd-
team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8

Can we get the same modifications to the Jammy systemd build?

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


** Tags: luks systemd tpm2

** Package changed: linux (Ubuntu) => systemd (Ubuntu)

** Description changed:

  systemd-cryptenroll can make use of tpm2 modules to bind against secure
- boot pcrs an enable auto unlocking of luks devices.
+ boot pcrs and enable auto unlocking of luks devices.
  
- Following the instructions here: 
+ Following the instructions here:
  https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll
  
  the following commands fail on ubuntu jammy (5.15.0-25-generic)
  
  root@testbox:~# systemd-cryptenroll --tpm2-device=list
  TPM2 not supported on this build.
  root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3
   Please enter current passphrase for disk /dev/sda3: ***
  root@testbox:~# echo $?
  1
  
  It appears that this issue has been resolved in the debian build for
  systemd here:  https://salsa.debian.org/systemd-
  team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8
  
  Can we get the same modifications to the Jammy systemd build?

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

Title:
  systemd-cryptenroll does not support TPM2 devices

Status in systemd package in Ubuntu:
  New

Bug description:
  systemd-cryptenroll can make use of tpm2 modules to bind against
  secure boot pcrs and enable auto unlocking of luks devices.

  Following the instructions here:
  https://wiki.archlinux.org/title/Trusted_Platform_Module#systemd-cryptenroll

  the following commands fail on ubuntu jammy (5.15.0-25-generic)

  root@testbox:~# systemd-cryptenroll --tpm2-device=list
  TPM2 not supported on this build.
  root@testbox:~# systemd-cryptenroll --tpm2-device=auto --tpm2-pcrs=7 /dev/sda3
   Please enter current passphrase for disk /dev/sda3: ***
  root@testbox:~# echo $?
  1

  It appears that this issue has been resolved in the debian build for
  systemd here:  https://salsa.debian.org/systemd-
  team/systemd/-/commit/6b5e99f1d7f63c0c83007de9f98f7745f4a564f8

  Can we get the same modifications to the Jammy systemd build?

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


-- 
Mailing list: https://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 1966376] [NEW] Video playback not so great

[Dean Fernandez]

Public bug reported:

Video playback always results in lines across the screen no matter what 
platform you're viewing it in. 
I am no expert in these sort of things but will be willing to help find out 
what the issue is and maybe a sollution!

Ubuntu 20.04.4 LTS X86_64
XFCE (Xubuntu)

xorg Version:
Version table:
 *** 1:7.7+19ubuntu14 500
500 http://za.archive.ubuntu.com/ubuntu focal/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: xorg 1:7.7+19ubuntu14
ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CompositorRunning: None
Date: Fri Mar 25 07:17:50 2022
DistUpgraded: Fresh install
DistroCodename: focal
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1355]
InstallationDate: Installed on 2022-02-18 (34 days ago)
InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 04f2:b5e0 Chicony Electronics Co., Ltd VGA WebCam
 Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire A315-54K
ProcEnviron:
 LANGUAGE=en_ZA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-37-generic 
root=UUID=855fae32-2844-4d07-955b-e32d41f1cd23 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/05/2019
dmi.bios.release: 1.3
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.03
dmi.board.asset.tag: Type2 - Board Serial Number
dmi.board.name: Sleepy_KL
dmi.board.vendor: KBL
dmi.board.version: V1.03
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.03
dmi.ec.firmware.release: 1.3
dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.03:bd07/05/2019:br1.3:efr1.3:svnAcer:pnAspireA315-54K:pvrV1.03:rvnKBL:rnSleepy_KL:rvrV1.03:cvnAcer:ct10:cvrV1.03:sku:
dmi.product.family: Aspire 3
dmi.product.name: Aspire A315-54K
dmi.product.sku: 
dmi.product.version: V1.03
dmi.sys.vendor: Acer
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.107-8ubuntu1~20.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.6-0ubuntu0.1~20.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20200226-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


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

Title:
  Video playback not so great

Status in xorg package in Ubuntu:
  New

Bug description:
  Video playback always results in lines across the screen no matter what 
platform you're viewing it in. 
  I am no expert in these sort of things but will be willing to help find out 
what the issue is and maybe a sollution!

  Ubuntu 20.04.4 LTS X86_64
  XFCE (Xubuntu)

  xorg Version:
  Version table:
   *** 1:7.7+19ubuntu14 500
  500 http://za.archive.ubuntu.com/ubuntu focal/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu14
  ProcVersionSignature: Ubuntu 5.13.0-37.42~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CompositorRunning: None
  Date: Fri Mar 25 07:17:50 2022
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] HD Graphics 620 [1025:1355]
  InstallationDate: Installed on 2022-02-18 (34 days ago)
  InstallationMedia: Xubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 
(20210819.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b5e0 Chicony Electronics Co., Ltd VGA WebCam
   Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire A315-54K
  ProcEnviron:
   

[Touch-packages] [Bug 1886572] Re: Remove uptime from the motd-news user agent

[Dean Henrichsmeyer]

Sorry, I mean there's no amd64 version in bionic-proposed.

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  Fix Committed

Bug description:
  [Impact] 
  The uptime value in the user-agent string sent to the motd-news server is 
unused and not necessary. It should be removed.

  [Test Case]
  Inspect the /etc/update-motd.d/50-motd-news script and verify that uptime is 
no longer used.

  Previous version:
  $ grep uptime /etc/update-motd.d/50-motd-news 
  # Some messages may only be pertinent before or after some amount of uptime
  read up idle < /proc/uptime
  uptime="uptime/$up/$idle"
  USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime cloud_id/$cloud_id"

  Updated version:
  $ grep uptime /etc/update-motd.d/50-motd-news
   (no output)

  
  [Regression Potential] 
  The server side, if it were checking this value, could be surprised by this 
change.

  [Other Info]
  N/A

  [Original Description]
  I don't why that was included but it shouldn't be. Please remove it.

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

-- 
Mailing list: https://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 1886572] Please test proposed package

[Dean Henrichsmeyer]

There's no amd64 version of this package as far as I can tell.

On Fri, Aug 21, 2020 at 6:21 AM Timo Aaltonen <1886...@bugs.launchpad.net>
wrote:

> Hello Dean, or anyone else affected,
>
> Accepted base-files into xenial-proposed. The package will build now and
> be available at https://launchpad.net/ubuntu/+source/base-
> files/9.4ubuntu4.13 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, what testing has been
> performed on the package and change the tag from verification-needed-
> xenial to verification-done-xenial. If it does not fix the bug for you,
> please add a comment stating that, and change the tag to verification-
> failed-xenial. 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 for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1886572
>
> Title:
>   Remove uptime from the motd-news user agent
>
> Status in base-files package in Ubuntu:
>   Fix Released
> Status in base-files source package in Xenial:
>   Fix Committed
> Status in base-files source package in Bionic:
>   Fix Committed
> Status in base-files source package in Focal:
>   Fix Committed
>
> Bug description:
>   [Impact]
>   The uptime value in the user-agent string sent to the motd-news server
> is unused and not necessary. It should be removed.
>
>   [Test Case]
>   Inspect the /etc/update-motd.d/50-motd-news script and verify that
> uptime is no longer used.
>
>   Previous version:
>   $ grep uptime /etc/update-motd.d/50-motd-news
>   # Some messages may only be pertinent before or after some amount of
> uptime
>   read up idle < /proc/uptime
>   uptime="uptime/$up/$idle"
>   USER_AGENT="curl/$curl_ver $lsb $platform $cpu $uptime
> cloud_id/$cloud_id"
>
>   Updated version:
>   $ grep uptime /etc/update-motd.d/50-motd-news
>(no output)
>
>
>   [Regression Potential]
>   The server side, if it were checking this value, could be surprised by
> this change.
>
>   [Other Info]
>   N/A
>
>   [Original Description]
>   I don't why that was included but it shouldn't be. Please remove it.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/base-files/+bug/1886572/+subscriptions
>
> Launchpad-Notification-Type: bug
> Launchpad-Bug: distribution=ubuntu; sourcepackage=base-files;
> component=main; status=Fix Released; importance=High; assignee=
> andr...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=xenial;
> sourcepackage=base-files; component=main; status=Fix Committed;
> importance=Undecided; assignee=andr...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=bionic;
> sourcepackage=base-files; component=main; status=Fix Committed;
> importance=Undecided; assignee=andr...@canonical.com;
> Launchpad-Bug: distribution=ubuntu; distroseries=focal;
> sourcepackage=base-files; component=main; status=Fix Committed;
> importance=Undecided; assignee=andr...@canonical.com;
> Launchpad-Bug-Tags: verification-needed verification-needed-bionic
> verification-needed-focal verification-needed-xenial
> Launchpad-Bug-Information-Type: Public
> Launchpad-Bug-Private: no
> Launchpad-Bug-Security-Vulnerability: no
> Launchpad-Bug-Commenters: ahasenack dean janitor tjaalton
> Launchpad-Bug-Reporter: Dean Henrichsmeyer (dean)
> Launchpad-Bug-Modifier: Timo Aaltonen (tjaalton)
> Launchpad-Message-Rationale: Subscriber
> Launchpad-Message-For: dean
>

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  Fix Released
Status in base-files source package in Xenial:
  Fix Committed
Status in base-files source package in Bionic:
  Fix Committed
Status in base-files source package in Focal:
  F

[Touch-packages] [Bug 1886572] [NEW] Remove uptime from the motd-news user agent

[Dean Henrichsmeyer]

Public bug reported:

I don't why that was included but it shouldn't be. Please remove it.

** Affects: base-files (Ubuntu)
 Importance: High
 Assignee: Andreas Hasenack (ahasenack)
 Status: New

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

Title:
  Remove uptime from the motd-news user agent

Status in base-files package in Ubuntu:
  New

Bug description:
  I don't why that was included but it shouldn't be. Please remove it.

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

-- 
Mailing list: https://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 1847570] Re: PulseAudio automatically switches to HDMI sound output on login

[Matthew M. Dean]

I still get this issue even on focal, or atleast the fix is the same. I
have a USB headset and upon reboot it always switches to the USB headset
regardless if HDMI was selected last. It's a desktop so things don't get
unplugged.

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

Title:
  PulseAudio automatically switches to HDMI sound output on login

Status in PulseAudio:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Eoan:
  Fix Released
Status in pulseaudio source package in Focal:
  Fix Released

Bug description:
  [Impact]

  On my freshly installed eoan system I have two output devices:
  - HDMI/DisplayPort 2 - GK208 ...
  - Line Out - Family 17h ...

  When I login into the system pulseaudio always select the "wrong"
  one (HDMI) and I need to go to gnome-settings/Sound/Output Device
  and switch to "line out". This applies to every login/logout not
  just reboots.

  [Test Case]

  0. Plug in a monitor that supports HDMI audio (one that appears in
  your Settings>Sound)

  1. Log out and in again.

  Verify the default audio device in Settings is still speakers or
  headphones. Not the monitor's HDMI audio device.

  [Regression Potential]

  The behaviour is changed back to what it was before 19.10, some users
  might find it inconvenient and prefer the auto switch but the feedback
  we got shows it's unreliable and an annoying for the majority of our
  users so we will got back to default to safest behaviour.

  The fix proposed just reverts to the same code used in PulseAudio 12
  and earlier. It has also been released and verified on focal already.

  [Workaround]

  Comment out:

  load-module module-switch-on-port-available
  load-module module-switch-on-connect

  from /etc/pulse/default.pa

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

-- 
Mailing list: https://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 1859031] [NEW] Cursor freezes with synergy software kvm

[Dean Anderson]

Public bug reported:

I'm using the synergy software KVM to share a mouse and keyboard between
two machines, with my Ubuntu workstation as the client.  When attempting
to drag-and-drop within Qt apps, the mouse cursor will freeze for
several seconds.  Cursor freezes also occur intermittently as well.  I
have an issue report for synergy as well: https://github.com/symless
/synergy-core/issues/6487

This issue seems to be a regression related to update 1.6.4-3ubuntu0.2.
The current workaround is to pin all libx11 packages to the previous
(0.1) versions.

Release Version: Ubuntu 18.04.3 LTS
Package Version: libx11-6:amd64 2:1.6.4-3ubuntu0.2

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libx11-6 2:1.6.4-3ubuntu0.1
ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
Uname: Linux 5.0.0-37-generic x86_64
NonfreeKernelModules: 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.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.33.01  Wed Nov 13 00:00:22 
UTC 2019
 GCC version:  gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1)
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: KDE
Date: Thu Jan  9 09:13:29 2020
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 NVIDIA Corporation GP104GLM [Quadro P5200 Mobile] [10de:1bb5] (rev a1) 
(prog-if 00 [VGA controller])
   Subsystem: Dell GP104GLM [Quadro P5200 Mobile] [1028:1832]
InstallationDate: Installed on 2018-07-30 (527 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Dell Inc. Precision 7730
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic 
root=UUID=6599bc95-d2cf-4bb0-b32d-653b78ae0fe9 ro quiet splash acpi=force 
vt.handoff=1
SourcePackage: libx11
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/11/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.12.1
dmi.board.name: 0MG0JR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd11/11/2019:svnDellInc.:pnPrecision7730:pvr:rvnDellInc.:rn0MG0JR:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Precision
dmi.product.name: Precision 7730
dmi.product.sku: 0832
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~18.04.3
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~18.04.3
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
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

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


** Tags: amd64 apport-bug bionic possible-manual-nvidia-install ubuntu

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

Title:
  Cursor freezes with synergy software kvm

Status in libx11 package in Ubuntu:
  New

Bug description:
  I'm using the synergy software KVM to share a mouse and keyboard
  between two machines, with my Ubuntu workstation as the client.  When
  attempting to drag-and-drop within Qt apps, the mouse cursor will
  freeze for several seconds.  Cursor freezes also occur intermittently
  as well.  I have an issue report for synergy as well:
  https://github.com/symless/synergy-core/issues/6487

  This issue seems to be a regression related to update
  1.6.4-3ubuntu0.2.  The current workaround is to pin all libx11
  packages to the previous (0.1) versions.

  Release Version: Ubuntu 18.04.3 LTS
  Package Version: libx11-6:amd64 2:1.6.4-3ubuntu0.2

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libx11-6 2:1.6.4-3ubuntu0.1
  ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21
  Uname: Linux 5.0.0-37-generic x86_64
  NonfreeKernelModules: 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.suspend: suspend hibernate resume
  .proc.driver.nvidia.suspend_depth: default modeset uvm
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  440.33.01  Wed Nov 13 

[Touch-packages] [Bug 1845950] Re: Bug reporting doesn't work upon a crash

[Dean Henrichsmeyer]

Here it is.

** Attachment added: "crashdb.conf"
   
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1845950/+attachment/5293314/+files/crashdb.conf

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

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

Title:
  Bug reporting doesn't work upon a crash

Status in apport package in Ubuntu:
  New

Bug description:
  On eoan, after an initial startup / login, if an application crashes
  and I click "report", I get a prompt saying the crash is reported and
  to check the web page open in the browser to see if I have any
  additional information.. except it never opens a page. The dialog just
  disappears, the crash log stays in /var/crash and nothing happens.

  The only way to actually file it is to run ubuntu-bug  which does
  work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: called for pid 3409, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3941) Mon Sep 30 07:28:15 2019: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:2696160:2019-09-26 13:17:54.338476419 -0500:2019-09-26 
13:17:55.338476419 -0500:/var/crash/_opt_google_chrome_chrome.1000.crash
   640:1000:117:2499555:2019-09-30 07:28:32.538634538 -0500:2019-09-30 
07:28:33.538634538 -0500:/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 30 07:34:38 2019
  InstallationDate: Installed on 2018-07-24 (432 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (72 days ago)

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

-- 
Mailing list: https://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 1845950] [NEW] Bug reporting doesn't work upon a crash

[Dean Henrichsmeyer]

Public bug reported:

On eoan, after an initial startup / login, if an application crashes and
I click "report", I get a prompt saying the crash is reported and to
check the web page open in the browser to see if I have any additional
information.. except it never opens a page. The dialog just disappears,
the crash log stays in /var/crash and nothing happens.

The only way to actually file it is to run ubuntu-bug  which does
work as expected.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: apport 2.20.11-0ubuntu7
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportLog:
 ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: called for pid 3409, signal 
6, core limit 0, dump mode 1
 ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
 ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: debug: session gdbus call: 
(true,)
 
 ERROR: apport (pid 3941) Mon Sep 30 07:28:15 2019: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CrashReports:
 640:1000:117:2696160:2019-09-26 13:17:54.338476419 -0500:2019-09-26 
13:17:55.338476419 -0500:/var/crash/_opt_google_chrome_chrome.1000.crash
 640:1000:117:2499555:2019-09-30 07:28:32.538634538 -0500:2019-09-30 
07:28:33.538634538 -0500:/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
CurrentDesktop: ubuntu:GNOME
Date: Mon Sep 30 07:34:38 2019
InstallationDate: Installed on 2018-07-24 (432 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: apport
UpgradeStatus: Upgraded to eoan on 2019-07-19 (72 days ago)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Bug reporting doesn't work upon a crash

Status in apport package in Ubuntu:
  New

Bug description:
  On eoan, after an initial startup / login, if an application crashes
  and I click "report", I get a prompt saying the crash is reported and
  to check the web page open in the browser to see if I have any
  additional information.. except it never opens a page. The dialog just
  disappears, the crash log stays in /var/crash and nothing happens.

  The only way to actually file it is to run ubuntu-bug  which does
  work as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: apport 2.20.11-0ubuntu7
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: called for pid 3409, 
signal 6, core limit 0, dump mode 1
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: executable: 
/usr/lib/tracker/tracker-miner-fs (command line 
"/usr/lib/tracker/tracker-miner-fs")
   ERROR: apport (pid 3941) Mon Sep 30 07:28:14 2019: debug: session gdbus 
call: (true,)
   
   ERROR: apport (pid 3941) Mon Sep 30 07:28:15 2019: wrote report 
/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:117:2696160:2019-09-26 13:17:54.338476419 -0500:2019-09-26 
13:17:55.338476419 -0500:/var/crash/_opt_google_chrome_chrome.1000.crash
   640:1000:117:2499555:2019-09-30 07:28:32.538634538 -0500:2019-09-30 
07:28:33.538634538 -0500:/var/crash/_usr_lib_tracker_tracker-miner-fs.1000.crash
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Sep 30 07:34:38 2019
  InstallationDate: Installed on 2018-07-24 (432 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to eoan on 2019-07-19 (72 days ago)

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

-- 
Mailing list: https://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 1815509] Re: Shutdown hung by firmware update daemon

[Dean Henrichsmeyer]

It's the last thing seen on the console when it happens. The machine in
question has been updated to disco and I haven't seen the behavior.

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

Title:
  Shutdown hung by firmware update daemon

Status in fwupd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  When rebooting my desktop, the shutdown sequence hangs for a long time
  on "Stopping firmware update daemon." It eventually will reboot but it
  hangs there for quite some time before doing so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.12
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 11 13:39:51 2019
  InstallationDate: Installed on 2018-07-24 (202 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

-- 
Mailing list: https://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 1822881] [NEW] Whenever an application accesses the audio device there's a loud pop

[Dean Henrichsmeyer]

Public bug reported:

Upon an upgrade to disco, now when anything access the audio output I
get a loud pop. Happens with a browser (firefox and chrome), spotify,
etc. It's independent of the application.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC2:  dean   3841 F pulseaudio
 /dev/snd/controlC0:  dean   3841 F pulseaudio
 /dev/snd/controlC1:  dean   3841 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr  2 15:45:32 2019
InstallationDate: Installed on 2018-07-24 (252 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to disco on 2019-04-02 (0 days ago)
dmi.bios.date: 05/16/2018
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
dmi.board.name: NUC6i7KYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H90766-406
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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


** Tags: amd64 apport-bug disco

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

Title:
  Whenever an application accesses the audio device there's a loud pop

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Upon an upgrade to disco, now when anything access the audio output I
  get a loud pop. Happens with a browser (firefox and chrome), spotify,
  etc. It's independent of the application.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  dean   3841 F pulseaudio
   /dev/snd/controlC0:  dean   3841 F pulseaudio
   /dev/snd/controlC1:  dean   3841 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr  2 15:45:32 2019
  InstallationDate: Installed on 2018-07-24 (252 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: Upgraded to disco on 2019-04-02 (0 days ago)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

-- 
Mailing list: https://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 1815509] Re: Shutdown hung by firmware update daemon

[Dean Henrichsmeyer]

This seems intermittent for me. I admit I don't reboot often but I've
been unable to reproduce it, even with leaving fwupd enabled.

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

Title:
  Shutdown hung by firmware update daemon

Status in fwupd package in Ubuntu:
  Incomplete
Status in systemd package in Ubuntu:
  New

Bug description:
  When rebooting my desktop, the shutdown sequence hangs for a long time
  on "Stopping firmware update daemon." It eventually will reboot but it
  hangs there for quite some time before doing so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.12
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 11 13:39:51 2019
  InstallationDate: Installed on 2018-07-24 (202 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

-- 
Mailing list: https://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 1815509] [NEW] Shutdown hung by firmware update daemon

[Dean Henrichsmeyer]

Public bug reported:

When rebooting my desktop, the shutdown sequence hangs for a long time
on "Stopping firmware update daemon." It eventually will reboot but it
hangs there for quite some time before doing so.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10.12
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 11 13:39:51 2019
InstallationDate: Installed on 2018-07-24 (202 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724)
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/16/2018
dmi.bios.vendor: Intel Corp.
dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
dmi.board.name: NUC6i7KYB
dmi.board.vendor: Intel Corporation
dmi.board.version: H90766-406
dmi.chassis.type: 3
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

Title:
  Shutdown hung by firmware update daemon

Status in systemd package in Ubuntu:
  New

Bug description:
  When rebooting my desktop, the shutdown sequence hangs for a long time
  on "Stopping firmware update daemon." It eventually will reboot but it
  hangs there for quite some time before doing so.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10.12
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 11 13:39:51 2019
  InstallationDate: Installed on 2018-07-24 (202 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180724)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-45-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/16/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: KYSKLi70.86A.0055.2018.0516.1629
  dmi.board.name: NUC6i7KYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H90766-406
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrKYSKLi70.86A.0055.2018.0516.1629:bd05/16/2018:svn:pn:pvr:rvnIntelCorporation:rnNUC6i7KYB:rvrH90766-406:cvnIntelCorporation:ct3:cvr1.0:

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

-- 
Mailing list: https://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 1787460] [NEW] Unattended upgrades removed linux-image-generic

[Dean Henrichsmeyer]

Public bug reported:

On a fairly fresh install of 18.04 with no modifications whatsoever to
the unattended-upgrades configuration, it decided to remove linux-image-
generic which also removed linux-modules-extra which caused sound
drivers to disappear, etc.

The relative snippet from /var/log/unattended-upgrades/unattended-
upgrades.log is:

2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
2018-08-15 06:18:09,477 INFO Packages that are kept back: linux-headers-generic
2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
2018-08-15 06:18:39,238 INFO All upgrades installed
2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
2018-08-15 06:18:42,818 INFO Packages that are kept back:

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: unattended-upgrades 1.1ubuntu1.18.04.5
ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
Uname: Linux 4.15.0-32-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.9-0ubuntu7.3
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Aug 16 13:17:30 2018
InstallationDate: Installed on 2018-07-24 (23 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180724)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: unattended-upgrades
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: unattended-upgrades (Ubuntu)
 Importance: High
 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 unattended-upgrades in
Ubuntu.
https://bugs.launchpad.net/bugs/1787460

Title:
  Unattended upgrades removed linux-image-generic

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  On a fairly fresh install of 18.04 with no modifications whatsoever to
  the unattended-upgrades configuration, it decided to remove linux-
  image-generic which also removed linux-modules-extra which caused
  sound drivers to disappear, etc.

  The relative snippet from /var/log/unattended-upgrades/unattended-
  upgrades.log is:

  2018-08-15 06:18:00,048 INFO Starting unattended upgrades script
  2018-08-15 06:18:00,048 INFO Allowed origins are: o=Ubuntu,a=bionic, 
o=Ubuntu,a=bionic-security, o=UbuntuESM,a=bionic
  2018-08-15 06:18:01,552 INFO Removing unused kernel packages: 
linux-headers-generic linux-image-generic linux-headers-4.15.0-32-generic 
linux-headers-4.15.0-32
  2018-08-15 06:18:01,588 WARNING Keeping auto-removable linux-headers-generic 
package(s) because it would also remove the following packages which should be 
kept in this step: libxml2 linux-image-4.15.0-32-generic 
linux-modules-4.15.0-32-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:09,476 INFO Packages that were successfully auto-removed: 
linux-headers-4.15.0-32 linux-headers-4.15.0-32-generic linux-headers-generic 
linux-image-generic
  2018-08-15 06:18:09,477 INFO Packages that are kept back: 
linux-headers-generic
  2018-08-15 06:18:10,300 INFO Packages that will be upgraded: libxml2 
linux-image-generic
  2018-08-15 06:18:10,300 INFO Writing dpkg log to 
/var/log/unattended-upgrades/unattended-upgrades-dpkg.log
  2018-08-15 06:18:39,238 INFO All upgrades installed
  2018-08-15 06:18:42,818 INFO Packages that were successfully auto-removed: 
linux-image-generic linux-modules-extra-4.15.0-32-generic
  2018-08-15 06:18:42,818 INFO Packages that are kept back:

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: unattended-upgrades 1.1ubuntu1.18.04.5
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.9-0ubuntu7.3
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 16 13:17:30 2018
  InstallationDate: Installed on 2018-07-24 (23 days ago)
  InstallationMedia: Ubuntu 

[Touch-packages] [Bug 1764803] [NEW] failed install of nvidia-drivers-390

[Dean ford]

Public bug reported:

insulation method using ubuntu-driver, blacklisting nouveau.
also tried with the ppa added and driver from nvidia.com. All failed which 
hasnt happed before when installing (K)ubuntu 

Black screen after reboot
GPU running hot
Kubuntu 18.04 final beta

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xserver-xorg 1:7.7+19ubuntu6
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
NonfreeKernelModules: 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  390.48  Thu Mar 22 00:42:57 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
ApportVersion: 2.20.9-0ubuntu5
Architecture: amd64
BootLog: /dev/sda1: clean, 226700/2428272 files, 2097944/9707520 blocks
Date: Tue Apr 17 17:30:25 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] 2nd Generation Core Processor Family 
Integrated Graphics Controller [1025:0504]
 NVIDIA Corporation GF108M [GeForce GT 630M] [10de:0de9] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Acer Incorporated [ALI] GF108M [GeForce GT 620M/630M/635M/640M 
LE] [1025:0505]
InstallationDate: Installed on 2018-04-12 (4 days ago)
InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404)
MachineType: Acer Aspire 5755G
ProcEnviron:
 LANGUAGE=en_GB:en
 TERM=linux
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-15-generic 
root=UUID=7ce01f2b-9fff-47af-a177-4bb10ec8e87f ro acpi_osi=Linux 
acpi_backlight=vendor quiet nomodset splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/07/2011
dmi.bios.vendor: Acer
dmi.bios.version: V1.15
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JV51_HR
dmi.board.vendor: Acer
dmi.board.version: Base Board Version
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.15
dmi.modalias: 
dmi:bvnAcer:bvrV1.15:bd10/07/2011:svnAcer:pnAspire5755G:pvrV1.15:rvnAcer:rnJV51_HR:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.15:
dmi.product.name: Aspire 5755G
dmi.product.version: V1.15
dmi.sys.vendor: Acer
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-1ubuntu3
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 N/A

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

Title:
  failed install of nvidia-drivers-390

Status in xorg package in Ubuntu:
  New

Bug description:
  insulation method using ubuntu-driver, blacklisting nouveau.
  also tried with the ppa added and driver from nvidia.com. All failed which 
hasnt happed before when installing (K)ubuntu 

  Black screen after reboot
  GPU running hot
  Kubuntu 18.04 final beta

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xserver-xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  NonfreeKernelModules: 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  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu5
  Architecture: amd64
  BootLog: /dev/sda1: clean, 226700/2428272 files, 2097944/9707520 blocks
  Date: Tue Apr 17 17:30:25 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 390.48, 4.15.0-15-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA 

[Touch-packages] [Bug 1750884] Re: [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic, leads to no DNS resolution

[Dean Henrichsmeyer]

Let's make sure this is fixed for bionic. The scope of nameservers has
changed and maas should do the right thing.

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

Title:
  [2.4, bionic] /etc/resolv.conf not configured correctly in Bionic,
  leads to no DNS resolution

Status in cloud-init:
  New
Status in MAAS:
  Triaged
Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  When deploying Bionic, /etc/resolv.conf is not configured correctly,
  which leads to no DNS resolution. In the output below, you will see
  that netplan config is correctly to the 10.90.90.1 nameserver, but in
  resolv.conf that's a local address.

  Resolv.conf should really be configured to use the provided DNS
  server(s). That said, despite that fact, DNS resolution doesn't work
  with the local address.

  Bionic
  --

  ubuntu@node01:~$ cat /etc/netplan/50-cloud-init.yaml
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  network:
  version: 2
  ethernets:
  enp0s25:
  match:
  macaddress: b8:ae:ed:7d:17:d2
  mtu: 1500
  nameservers:
  addresses:
  - 10.90.90.1
  search:
  - maaslab
  - maas
  set-name: enp0s25
  bridges:
  br0:
  addresses:
  - 10.90.90.3/24
  gateway4: 10.90.90.1
  interfaces:
  - enp0s25
  parameters:
  forward-delay: 15
  stp: false
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 127.0.0.53

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  ping: google.com: Temporary failure in name resolution

  [...]

  ubuntu@node01:~$ sudo vim /etc/resolv.conf
  ubuntu@node01:~$ cat /etc/resolv.conf
  # This file is managed by man:systemd-resolved(8). Do not edit.
  #
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.
  nameserver 10.90.90.1

  search maaslab maas
  ubuntu@node01:~$ ping google.com
  PING google.com (172.217.0.174) 56(84) bytes of data.
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=1 ttl=52 
time=4.46 ms
  64 bytes from mia09s16-in-f14.1e100.net (172.217.0.174): icmp_seq=2 ttl=52 
time=4.38 ms

  =
  Xenial
  ==

  ubuntu@node05:~$ cat /etc/network/interfaces.d/50-cloud-init.cfg
  # This file is generated from information provided by
  # the datasource.  Changes to it will not persist across an instance.
  # To disable cloud-init's network configuration capabilities, write a file
  # /etc/cloud/cloud.cfg.d/99-disable-network-config.cfg with the following:
  # network: {config: disabled}
  auto lo
  iface lo inet loopback
  dns-nameservers 10.90.90.1
  dns-search maaslab maas

  auto enp0s25
  iface enp0s25 inet static
  address 10.90.90.162/24
  gateway 10.90.90.1
  mtu 1500
  ubuntu@node05:~$ cat /etc/resolv.conf
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  nameserver 10.90.90.1
  search maaslab maas

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1750884/+subscriptions

-- 
Mailing list: https://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 1636573] Re: xinit flooding syslog

[Dean Robinson]

** Changed in: pyopenssl (Ubuntu Yakkety)
   Status: Triaged => Fix Released

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

Title:
  xinit flooding syslog

Status in pyOpenSSL:
  Fix Released
Status in pyopenssl package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in pyopenssl source package in Yakkety:
  Fix Released
Status in xorg source package in Yakkety:
  Invalid

Bug description:
  I am using xinit (1.3.4-3ubuntu1) to start an X11 session as follows
  (kodi is a media center):

  /usr/bin/xinit /usr/bin/dbus-launch --exit-with-session /usr/bin/kodi-
  standalone -- :1 -nolisten tcp vt8

  This used to work fine with Ubuntu 16.04, but since the upgrade to
  16.10 lots of log messages are sent to syslog. They are all
  repetitions of the following two lines:

  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_bytes() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.
  Oct 24 22:54:50 tiger xinit[26430]: extern "Python": function 
Cryptography_rand_status() called, but @ffi.def_extern() was not called in the 
current subinterpreter.  Returning 0.

  These messages amount to >200 GB per day, so this is eating up all the
  disk space.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Tue Oct 25 18:41:22 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2012-01-06 (1753 days ago)
  InstallationMedia: Kubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (11 days ago)

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

-- 
Mailing list: https://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 1616809] Re: Indicator-network doesn't reflect the connection status and throws "Network error" in browser and other apps

[Che Dean]

My indicator shows Ting 4G but I have no data connection.

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

Title:
  Indicator-network doesn't reflect the connection status and throws
  "Network error" in browser and other apps

Status in Canonical System Image:
  New
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  Pro 5 on latest rc-proposed.

  The network is not updated at all or with a very long delay. Most
  of the times when I leave my home wifi and go out, I can still notice
  the "no network" icon after 15 minutes or more even though the mobile
  data shows as 4G (see attached screenshot). The problem is more
  apparent when moving from wifi to mobile data then going from mobile
  data to wifi, but the problems occur quite often both ways.

  In some form or another, this has been an issue on every UT phone I
  have owned (Nexus 4 several years back, Bq Aquaris E4.5 and Meizu Pro
  5). The problem is that apps on the phone seems to ask the network
  indicator about the connection status, not checking if the device is
  actually connected or not, and therefore throwing me the dreadful
  "Network error" in any app that needs an internet connection.

  Wouldn't it be better if the actual connection status determined the
  state for the apps trying to connect?

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

-- 
Mailing list: https://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 1611010] Re: yakkety desktop - non-english installation crashes with /plugininstall.py: ValueError: invalid literal for int() with base 10: ''

[Dean]

Problem installing Xenial most recent daily desktop AMD64 builds (3
previous days) while selecting English keyboard and Ecuador timezone.

Same problem of crash during setting language.

Workaround was updating sources.list, update, reinstall apt tzdata
language-selector-common language-pack-en-base language-pack-en
(everything was up to date so I doubt this did anything) followed by
running ubiquity and selecting a US location to match the keyboard.

This went fine after various failed attempts and ubiquity previously crashing 
every time on setting language. Now location merely needs to be updated on 
reboot, if it isn't broken.
Perhaps doing this after all other things in the installer...

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

Title:
  yakkety desktop - non-english installation crashes with
  /plugininstall.py: ValueError: invalid literal for int() with base 10:
  ''

Status in apt package in Ubuntu:
  Fix Released
Status in ubiquity package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in ubiquity source package in Xenial:
  Triaged

Bug description:
  Enviroment: Ubuntu 16.10.5 Yakkety Yak http://cdimage.ubuntu.com
  /daily-live/current/

  HW: Toshiba portege Z30-A12T | Intel i5+intel graphics | SSD hd

  Preconditions: W10+Xenial xerus installed, internet connection, 3rd
  party sw and updates selected

  Steps to reproduce:

  1º Click something else on Installation type screen>select /dev/sdaX where 
Xenial is installed, use it to mount / and leave some space to create the /home 
partition(ext4)
  2º Then click back and select erase ubuntu 16.04.1 and install Yakkety
  3º Installation starts

  Current result: After a little time installing it crashes and a window
  shows up to let the user know that some info is being gathered to send
  it to developers, and finally firefox opens on the bug report web on
  ubiquity package

  Expected result: No crashes during installation

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: ubiquity 16.10.5
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.376
  Date: Mon Aug  8 15:50:56 2016
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  LiveMediaBuild: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160808)
  ProcEnviron:
   LANGUAGE=es_ES.UTF-8
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
  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/1611010/+subscriptions

-- 
Mailing list: https://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 280571] Re: NetworkManager does not auto-connect to VPNs marked "Connect Automatically"

[Dean Robinson]

** Package changed: network-manager (Ubuntu) => network-manager-openvpn
(Ubuntu)

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

Title:
  NetworkManager does not auto-connect to VPNs marked "Connect
  Automatically"

Status in NetworkManager:
  Fix Released
Status in network-manager-openvpn package in Ubuntu:
  Fix Released
Status in network-manager package in Debian:
  Fix Released

Bug description:
  VPN connections marked "Connect Automatically" are not activated when
  a wired or wireless network becomes available.

  Fixed upstream in commit:

  commit ece5e209cdc409a21e249dacbdbc953a1db4c6b7
  Author: Jiří Klimeš 
  Date:   Tue Aug 21 17:49:41 2012 +0200

  core: VPN autoconnect feature (bgo #560471) (rh #483120)

  We go through the SECONDARIES state where we check if there are some
  secondary
  (VPN or other) UUIDs that are to be activated before progressing to
  ACTIVATED.
  In case of an error with a secondary UUID or its activation, the base
  connection
  can't activate successfully.

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

-- 
Mailing list: https://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 1619689] [NEW] package cups 2.1.3-4 failed to install/upgrade: triggers looping, abandoned

[Dean Provins]

Public bug reported:

Have not updated cupsd.conf for a long time.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: cups 2.1.3-4
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
CupsErrorLog: E [02/Sep/2016:07:35:02 -0600] Unknown directive BrowseAddress on 
line 7 of /etc/cups/cupsd.conf.
Date: Thu Sep  1 18:36:28 2016
ErrorMessage: triggers looping, abandoned
Lpstat:
 device for Hewlett-Packard-HP-LaserJet-5MP: 
hp:/par/HP_LaserJet_5MP?device=/dev/parport1
 device for HP-LaserJet: parallel:/dev/lp1
MachineType: System manufacturer System Product Name
Papersize: letter
PpdFiles:
 Hewlett-Packard-HP-LaserJet-5MP: HP LaserJet 5MP Postscript (recommended)
 HP-LaserJet: HP LaserJet Foomatic/laserjet (recommended)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=72be9d99-d37a-44d7-85b3-6af71e450efc ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=72be9d99-d37a-44d7-85b3-6af71e450efc ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: cups
Title: package cups 2.1.3-4 failed to install/upgrade: triggers looping, 
abandoned
UpgradeStatus: Upgraded to xenial on 2016-08-15 (17 days ago)
dmi.bios.date: 10/16/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1002
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8B75-M
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1002:bd10/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
mtime.conffile..etc.cups.cupsd.conf: 2015-09-04T14:54:28.973348

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

Title:
  package cups 2.1.3-4 failed to install/upgrade: triggers looping,
  abandoned

Status in cups package in Ubuntu:
  New

Bug description:
  Have not updated cupsd.conf for a long time.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: cups 2.1.3-4
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CupsErrorLog: E [02/Sep/2016:07:35:02 -0600] Unknown directive BrowseAddress 
on line 7 of /etc/cups/cupsd.conf.
  Date: Thu Sep  1 18:36:28 2016
  ErrorMessage: triggers looping, abandoned
  Lpstat:
   device for Hewlett-Packard-HP-LaserJet-5MP: 
hp:/par/HP_LaserJet_5MP?device=/dev/parport1
   device for HP-LaserJet: parallel:/dev/lp1
  MachineType: System manufacturer System Product Name
  Papersize: letter
  PpdFiles:
   Hewlett-Packard-HP-LaserJet-5MP: HP LaserJet 5MP Postscript (recommended)
   HP-LaserJet: HP LaserJet Foomatic/laserjet (recommended)
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=72be9d99-d37a-44d7-85b3-6af71e450efc ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=72be9d99-d37a-44d7-85b3-6af71e450efc ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: cups
  Title: package cups 2.1.3-4 failed to install/upgrade: triggers looping, 
abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-15 (17 days ago)
  dmi.bios.date: 10/16/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1002
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8B75-M
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1002:bd10/16/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8B75-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  mtime.conffile..etc.cups.cupsd.conf: 2015-09-04T14:54:28.973348

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

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

[Touch-packages] [Bug 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml

[Dean Montgomery]

that `const char *media_types` either needs more added to it or a way to hook 
in an external file containing that list.  Google search turns up some common 
"Unknown media type":
all
chemical
uri
interface
map
fonts
vms
zz-aplication

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

Title:
  Unknown media types in /usr/share/mime/packages/kde.xml

Status in shared-mime-info:
  Confirmed
Status in kde4libs package in Ubuntu:
  Invalid
Status in shared-mime-info package in Ubuntu:
  Triaged
Status in kde4libs package in Debian:
  New
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  Here is the problem:

  # update-mime-database /usr/share/mime
  [...]
  Unknown media type in type 'uri/mms'

  Unknown media type in type 'uri/mmst'

  Unknown media type in type 'uri/mmsu'

  Unknown media type in type 'uri/pnm'

  Unknown media type in type 'uri/rtspt'

  Unknown media type in type 'uri/rtspu'

  It seems to come from this file:
/usr/share/mime/packages/kde.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/289592/+subscriptions

-- 
Mailing list: https://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 289592] Re: Unknown media types in /usr/share/mime/packages/kde.xml

[Dean Montgomery]

In package shared-mime-info there is update-mime-database.c and around
line 51 there is a hard-programmed list of mime types used to flag
invalid MIME types


/* This is the list of directories to scan when finding old type files to
 * delete. It is also used to warn about invalid MIME types.
 */
const char *media_types[] = {
  "text",
  "application",
  "image",
  "audio",
  "inode",
  "video",
  "message",
  "model",
  "multipart",
  "x-content",
  "x-epoc",
  "x-scheme-handler",
};


in the get_type function around line 261 the program scans the hard-
coded list of mime types or it returns the error that everyone is
complaining about.


  for (i = 0; i < G_N_ELEMENTS(media_types); i++)
  {
if (strcmp(media_types[i], type->media) == 0)
  return type;
  }

  g_warning("Unknown media type in type '%s'", name);


Dean M.

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

Title:
  Unknown media types in /usr/share/mime/packages/kde.xml

Status in shared-mime-info:
  Confirmed
Status in kde4libs package in Ubuntu:
  Invalid
Status in shared-mime-info package in Ubuntu:
  Triaged
Status in kde4libs package in Debian:
  New
Status in shared-mime-info package in Debian:
  Confirmed

Bug description:
  Here is the problem:

  # update-mime-database /usr/share/mime
  [...]
  Unknown media type in type 'uri/mms'

  Unknown media type in type 'uri/mmst'

  Unknown media type in type 'uri/mmsu'

  Unknown media type in type 'uri/pnm'

  Unknown media type in type 'uri/rtspt'

  Unknown media type in type 'uri/rtspu'

  It seems to come from this file:
/usr/share/mime/packages/kde.xml

To manage notifications about this bug go to:
https://bugs.launchpad.net/shared-mime-info/+bug/289592/+subscriptions

-- 
Mailing list: https://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 572063] Re: [NO SOUND] 10.04 - Intel Corporation 82801H HD Audio Controller (rev 03)

[Dean]

20160521
workaround: use PulseAudio Volume control, don't use ubuntu packaged volume 
control. replug HDMI at TV.
May 21,2016  Ubuntu 14.04
The standard volume control in the settings manager on unity does not reassign 
HDMI correctly.
If I use the PulseAudio volume control (pavucontrol) only, then I can switch 
the output back and forth using the "Playback on" button on the playback tab. 
Configuration Tab can also make changes but is not simple.
Note: my TV remembers the sound is not present when I use the standard ubuntu 
volume control to switch back to pc speakers. I have to replug the  HDMI cable 
on the TV to reset TV after closing the standard volume control.

my hardware contains both DPORT and HDMI. 3.13.0-86-generic 64 bit

Initially 20160521 I removed alsa and pulsaudio. Then I reloaded both with all 
suggested extra software (apt-get). this worked to get audio through HDMI. but 
as soon as I switched back to pc speakers, I could not get it to work any more.
tried many things till a random combination of settings with plugging HDMI at 
TV set got it working.
Then there were more problems after switching back to pc speakers using 
standard volume control.
finally discovered that PulseAudio volume control will switch output ports 
correctly, but fuctionality is dissabled as soon as you use the ubuntu volume 
control to switch back to pc speakers.

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

Title:
  [NO SOUND] 10.04 - Intel Corporation 82801H HD Audio Controller (rev
  03)

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Binary package hint: pulseaudio

  1)
  rprice@alienware:~/Desktop$ lsb_release -rd
  Description:  Ubuntu 10.04 LTS
  Release:  10.04

  -
  2)
  rprice@alienware:~/Desktop$ apt-cache policy pulseaudio
  pulseaudio:
    Installed: 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
    Candidate: 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
    Version table:
   *** 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14 0
  500 http://us.archive.ubuntu.com/ubuntu/ lucid/main Packages
  100 /var/lib/dpkg/status

  -
  3)
  Audio to work after installation with both analog and digital (HDMI)

  -
  4)
  Audio does not work after installation.  I have been able to get it working 
by making a file under /etc/modprobe.d with the following:

  $ cat /etc/modprobe.d/sound
  options snd_hda_intel model=mbp3

  The problem with this is when I go to use HDMI out to my TV, I have to
  change analog to digital.  When I am done, if I want audio back on the
  laptop, I have to switch from digital to analog.  It doesn't "Just
  work".  Please let me know if I need to upload any other information.
  I am not very good with audio issues.  ;(

  
  -


  ProblemType: Bug
  DistroRelease: Ubuntu 10.04
  Package: pulseaudio 1:0.9.22~0.9.21+stable-queue-32-g8478-0ubuntu14
  ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
  Uname: Linux 2.6.32-21-generic x86_64
  NonfreeKernelModules: nvidia
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  rprice 1447 F pulseaudio
  Card0.Amixer.info:
   Card hw:0 'Intel'/'HDA Intel at 0xf060 irq 22'
     Mixer name : 'Realtek ALC889A'
     Components : 'HDA:10ec0885,152d0770,00100103'
     Controls  : 22
     Simple ctrls  : 12
  Date: Fri Apr 30 01:58:26 2010
  ExecutablePath: /usr/bin/pulseaudio
  InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100406.1)
  ProcEnviron:
   LANG=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  XsessionErrors:
   (polkit-gnome-authentication-agent-1:1466): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed
   (gnome-terminal:1562): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion 
`entry != NULL && entry->lock_count > 0' failed
  dmi.bios.date: 08/29/2008
  dmi.bios.vendor: Quanta
  dmi.bios.version: vX36 P3
  dmi.board.name: m15x
  dmi.board.vendor: Alienware
  dmi.board.version: Not Applicable
  dmi.chassis.type: 1
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnQuanta:bvrvX36P3:bd08/29/2008:svnAlienware:pnm15x:pvrNotApplicable:rvnAlienware:rnm15x:rvrNotApplicable:cvnAlienware:ct1:cvrN/A:
  dmi.product.name: m15x
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Alienware

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

-- 
Mailing list: https://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 1509106] [NEW] package libqtgui4 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 failed to install/upgrade: cannot copy extracted data for './usr/lib/x86_64-linux-gnu/qt4/plugins/imageform

[Dean Woody]

Public bug reported:

just got this while loading mythbuntu.  don't know much else.  thanks

ProblemType: Package
DistroRelease: Ubuntu 14.04
Package: libqtgui4 4:4.8.5+git192-g085f851+dfsg-2ubuntu4
ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
Uname: Linux 3.16.0-30-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
Date: Thu Oct 22 17:44:12 2015
DuplicateSignature: 
package:libqtgui4:4:4.8.5+git192-g085f851+dfsg-2ubuntu4:cannot copy extracted 
data for './usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so' to 
'/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so.dpkg-new': 
unexpected end of file or stream
ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so' to 
'/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so.dpkg-new': 
unexpected end of file or stream
InstallationDate: Installed on 2015-10-22 (0 days ago)
InstallationMedia: Mythbuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
SourcePackage: qt4-x11
Title: package libqtgui4 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so' to 
'/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so.dpkg-new': 
unexpected end of file or stream
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package trusty

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

Title:
  package libqtgui4 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 failed to
  install/upgrade: cannot copy extracted data for './usr/lib/x86_64
  -linux-gnu/qt4/plugins/imageformats/libqmng.so' to '/usr/lib/x86_64
  -linux-gnu/qt4/plugins/imageformats/libqmng.so.dpkg-new': unexpected
  end of file or stream

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  just got this while loading mythbuntu.  don't know much else.  thanks

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libqtgui4 4:4.8.5+git192-g085f851+dfsg-2ubuntu4
  ProcVersionSignature: Ubuntu 3.16.0-30.40~14.04.1-generic 3.16.7-ckt3
  Uname: Linux 3.16.0-30-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Thu Oct 22 17:44:12 2015
  DuplicateSignature: 
package:libqtgui4:4:4.8.5+git192-g085f851+dfsg-2ubuntu4:cannot copy extracted 
data for './usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so' to 
'/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so.dpkg-new': 
unexpected end of file or stream
  ErrorMessage: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so' to 
'/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so.dpkg-new': 
unexpected end of file or stream
  InstallationDate: Installed on 2015-10-22 (0 days ago)
  InstallationMedia: Mythbuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: qt4-x11
  Title: package libqtgui4 4:4.8.5+git192-g085f851+dfsg-2ubuntu4 failed to 
install/upgrade: cannot copy extracted data for 
'./usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so' to 
'/usr/lib/x86_64-linux-gnu/qt4/plugins/imageformats/libqmng.so.dpkg-new': 
unexpected end of file or stream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1386323] Re: is friend app not available in 14.10?

[dean]

Bug also confirmed in Vivid (15.04).  App UI runs but no content
received from Facebook and Twitter accounts (in my specific case).

Ran app in terminal.  Log listed below.

dean@Z68XMain-Box:~$ friends-app
virtual void OnlineAccounts::Plugin::registerTypes(const char*) 
Ubuntu.OnlineAccounts
virtual void FriendsPlugin::registerTypes(const char*) Friends 
virtual void OnlineAccountsClient::Plugin::registerTypes(const char*) 
Ubuntu.OnlineAccounts.Client
MODEL:  com.canonical.Friends.Streams 
MODEL:  com.canonical.Friends.Streams 
MODEL:  com.canonical.Friends.Streams 
STREAM:  reply_to/  ROWS:  0 
SERVICE:ROWS:  0 
STREAM:  mentions  ROWS:  0 
SERVICE:ROWS:  0 
account-service-model.cpp 292 update
account-service-model.cpp 292 update
account-service.cpp 100 setObjectHandle Accounts::AccountService(0x23ffa90)
qml: Facebook Supports send
account-service.cpp 100 setObjectHandle Accounts::AccountService(0x23fcc30)
qml: Twitter Supports send
qml: accounts.count: 2
file:///usr/lib/x86_64-linux-gnu/qt5/qml/Ubuntu/Components/ListItems/IconVisual.qml:41:5:
 QML ImageWithFallback: Failed to get image from provider: 
image://theme/instagram
static void StreamModelPrivate::onModelReady(GObject*, GParamSpec*, 
StreamModelPrivate*)   0 
STREAM:ROWS:  0 
SERVICE:ROWS:  0 
static void StreamModelPrivate::onModelReady(GObject*, GParamSpec*, 
StreamModelPrivate*)   0 
STREAM:  mentions  ROWS:  0 
SERVICE:ROWS:  0 
static void StreamModelPrivate::onModelReady(GObject*, GParamSpec*, 
StreamModelPrivate*)   0 
STREAM:  reply_to/  ROWS:  0 
SERVICE:ROWS:  0 
file:///usr/share/friends-app/qml/ConversationDetails.qml:30:5: QML 
QQuickImage: Error downloading 
http://open.mapquestapi.com/staticmap/v4/getmap?size=160,160zoom=12center=0,0 
- server replied: Forbidden

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

Title:
  is friend app not available in 14.10?

Status in friends-app package in Ubuntu:
  Confirmed

Bug description:
  is friend app not available in 14.10. I used to get notifications in the 
previous versions of ubuntu.
  Its not working in 14.10.

  I was using the friends app till ubuntu 14.04 as soon as I updated to ubuntu 
14.10, the friends app is not working.
  I used to get notifications (notify osd) in the previous version. Neither the 
app is getting updated with the latest feeds from
  twitter and facebook nor I am getting any notifications.

  I tried uninstalling and reinstalling as well as remove the online accounts 
from the systems settings menu and added the accounts again.
  Neither way it doesnt seems to work.

  It was reallt a very good application. Please some one help me on
  this.

  Is the friends app still supported in the latest version of ubuntu?

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

-- 
Mailing list: https://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 1459463] [NEW] File in /etc/skel/ ending in Space causes adduser to fail

[Dean]

Public bug reported:

Repro is quite simple, place a file in `/etc/skel/` who's filename ends with 
the space character.
When running `adduser`, an error `No such file or directory` will be thrown.

Instructions:

$ sudo touch  /etc/skel/file-with-space 
$ sudo adduser test

What I expected to happen:

- User to be created

What happened instead:

- Error thrown, user not created.

Example:

$ sudo touch  /etc/skel/file-with-space 
$ sudo adduser test
Adding user `test' ...
Adding new group `test' (1001) ...
Adding new user `test' (1001) with group `test' ...
Creating home directory `/home/test' ...
Copying files from `/etc/skel' ...
Stopped: open /etc/skel/./file-with-space : No such file or directory
Removing directory `/home/test' ...
Removing user `test' ...
Removing group `test' ...
groupdel: group 'test' does not exist
adduser: `groupdel test' returned error code 6. Exiting.

$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04

$ apt-cache policy adduser 
adduser:
  Installed: 3.113+nmu3ubuntu3
  Candidate: 3.113+nmu3ubuntu3
  Version table:
 *** 3.113+nmu3ubuntu3 0
500 http://au.archive.ubuntu.com/ubuntu/ utopic/main amd64 
Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: adduser 3.113+nmu3ubuntu3
ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
Uname: Linux 3.13.0-46-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.14.1-0ubuntu3.7
Architecture: amd64
CurrentDesktop: Unity
Date: Thu May 28 09:22:23 2015
InstallationDate: Installed on 2013-11-06 (567 days ago)
InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 (20131016.1)
PackageArchitecture: all
SourcePackage: adduser
UpgradeStatus: Upgraded to trusty on 2015-03-08 (80 days ago)

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


** Tags: adduser amd64 apport-bug trusty

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

Title:
  File in /etc/skel/ ending in Space causes adduser to fail

Status in adduser package in Ubuntu:
  New

Bug description:
  Repro is quite simple, place a file in `/etc/skel/` who's filename ends with 
the space character.
  When running `adduser`, an error `No such file or directory` will be thrown.

  Instructions:

$ sudo touch  /etc/skel/file-with-space 
$ sudo adduser test

  What I expected to happen:

  - User to be created

  What happened instead:

  - Error thrown, user not created.

  Example:

$ sudo touch  /etc/skel/file-with-space 
$ sudo adduser test
Adding user `test' ...
Adding new group `test' (1001) ...
Adding new user `test' (1001) with group `test' ...
Creating home directory `/home/test' ...
Copying files from `/etc/skel' ...
Stopped: open /etc/skel/./file-with-space : No such file or directory
Removing directory `/home/test' ...
Removing user `test' ...
Removing group `test' ...
groupdel: group 'test' does not exist
adduser: `groupdel test' returned error code 6. Exiting.

$ lsb_release -rd
Description:Ubuntu 14.04.2 LTS
Release:14.04

$ apt-cache policy adduser 
adduser:
  Installed: 3.113+nmu3ubuntu3
  Candidate: 3.113+nmu3ubuntu3
  Version table:
 *** 3.113+nmu3ubuntu3 0
500 http://au.archive.ubuntu.com/ubuntu/ utopic/main amd64 
Packages
100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: adduser 3.113+nmu3ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-46.77-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu May 28 09:22:23 2015
  InstallationDate: Installed on 2013-11-06 (567 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Release amd64 
(20131016.1)
  PackageArchitecture: all
  SourcePackage: adduser
  UpgradeStatus: Upgraded to trusty on 2015-03-08 (80 days ago)

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

-- 
Mailing list: https://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 488710] Re: pdftops too slow with certain PDF files

[Dean Montgomery]

Resolved this issue by lowering and creating custom DPI values.

Default DPI from foomatic postcript PPDs is usually 600 DPI or 1200 DPI.
Ghostscript `pdftops` and `gs` both take a long time converting high DPI
values.  The 600 DPI also creates a large postscript file which in turn
are slow over the network as well as slow spooling on the printer
itself.  Printers have low RAM  small CPU.

When I lowered DPI to 300 the print jobs were almost instantaneous.
However the print quality was degraded.

I modified the PPD files for dozen or so laser printers and found that
400DPI is identical to 600DPI in terms of print quality.  With our
printers I found the sweet spot to be 350DPI for print quality and
maximum speed.

To get custom time/quality sweet spot DPI values, you will need to edit your 
PPD file:
cp /etc/cups/ppd/MYPRINTER.ppd $HOME/
Edit MYPRINTER.ppd  'Resolution' section and add 350 and 400 DPI.

*DefaultResolution: 350x350dpi
*Resolution 150x150dpi/150x150 DPI: /HWResolution[150 150]setpagedevice
*Resolution 300x300dpi/300x300 DPI: /HWResolution[300 300]setpagedevice
*Resolution 350x350dpi/350x350 DPI: /HWResolution[350 350]setpagedevice
*Resolution 400x400dpi/400x400 DPI: /HWResolution[400 400]setpagedevice
*Resolution 600x600dpi/600x600 DPI: /HWResolution[600 600]setpagedevice

You may want to update the ModelName, ShortNickName and NickName to
indicate that this file has been modified.

You can then either use the web interface to upload your custom ppd file or 
copy it to /usr/local/share/ppd/MYPRINTER.ppd
Then restart cups service.  Your custom PPD option will then appear in the 
pick-list when Modify Printer.

Once the PPD is installed then go to the Default Options to set the DPI
Resolution.   You may want to test the timing/quality for 300, 350, 400,
600.  I had 2 printers where 300DPI quality was just as good as the 600
DPI.

If an end-user enjoys the long print delay so they can socialize at the
printer - or enjoys burning CPU cycles imagining that their 1200dpi is
actually better quality,  then all they have to do is increase the DPI
setting on the print dialog before they send their job.

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

Title:
  pdftops too slow with certain PDF files

Status in poppler package in Ubuntu:
  Triaged
Status in xpdf package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: cups

  The attached file won't print either from evince or lpr. Printing via xpdf 
causes xpdf to hang. 
  A debug log is attached, the relevant job number is 593.
  Maybe relevant: in the document print status, the printer is shown as 
Printer not connected? However, other files print OK.

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

-- 
Mailing list: https://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 1401148] Re: Re/starting an lxc container corrupts all network namespaces on the same physical host

[Dean Henrichsmeyer]

** Tags added: landscape

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

Title:
  Re/starting an lxc container corrupts all network namespaces on the
  same physical host

Status in lxc package in Ubuntu:
  New

Bug description:
  Context: Neutron gateway north/south routing server which manages a
  large number of network namespaces; also hosts a few LXC containers
  for misc lightweight control plane services.

  Problem:  If I restart one of the lxc containers, all of the
  namespaces get corrupted in someway; attempting to exec anything in
  any namespace fails with:

  seting the network namespace qrouter-4b575c81-39bb-439f-81e1-e59e3759a287 
failed: Invalid argument
  seting the network namespace qrouter-1f5e26df-f8c5-4246-9485-3f9df8e39c40 
failed: Invalid argument
  seting the network namespace qrouter-c3bf179e-9532-43f9-88af-752b66592cd6 
failed: Invalid argument
  seting the network namespace qrouter-3d4550ca-4de6-44e3-90b5-1b60c3d58ed1 
failed: Invalid argument
  seting the network namespace qrouter-4fc4c3c2-68bf-4954-8b32-d47d8d84086e 
failed: Invalid argument
  seting the network namespace qrouter-0890d9ea-f0c8-4e69-bf1a-4896213a82a0 
failed: Invalid argument
  seting the network namespace qrouter-0f7e0655-f84b-4aaa-82aa-75f01a59411e 
failed: Invalid argument

  I also see:

  Dec 10 15:16:00 cofgod kernel: [ 4604.274359] type=1400 
audit(1418224560.675:132): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-0ba77ab2-b3ee-4752-88af-b19313c10f9d/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274405] type=1400 
audit(1418224560.675:134): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-25006453-2caa-4aa4-bdeb-e4822dc700d6/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274436] type=1400 
audit(1418224560.675:136): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-2fec74e8-d507-4650-beb4-8da459ea0039/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274451] type=1400 
audit(1418224560.675:137): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-33d8fa40-c158-4377-bc8f-d252e38d4943/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274466] type=1400 
audit(1418224560.675:138): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-394517c0-e48a-43e7-8778-96c601607733/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274482] type=1400 
audit(1418224560.675:139): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qdhcp-41e21850-decf-49f8-97fb-cbb3aa5932e3/ pid=8790 
comm=lxc-start flags=rw, slave
  Dec 10 15:16:00 cofgod kernel: [ 4604.274497] type=1400 
audit(1418224560.675:140): apparmor=DENIED operation=mount info=failed 
type match error=-13 profile=/usr/bin/lxc-start 
name=/run/netns/qrouter-e9837293-c017-4d85-a601-cae5e83719a2/ pid=8790 
comm=lxc-start flags=rw, slave

  In the kern.log

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lxc 1.0.6-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  Date: Wed Dec 10 15:24:45 2014
  SourcePackage: lxc
  UpgradeStatus: No upgrade log present (probably fresh install)
  defaults.conf:
   lxc.network.type = veth
   lxc.network.link = lxcbr0
   lxc.network.flags = up
   lxc.network.hwaddr = 00:16:3e:xx:xx:xx

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

-- 
Mailing list: https://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 1240336] Re: Not authorized to perform operation / Unable to determine the session we are in: No session for pid

[Rob Dean]

I'm having this problem on upgrade to Utopic (Kubuntu system) - ie
unable to mount USB, clicking shutdown gets me to the login screen. I've
tried appending

session required pam_loginuid.so
session required pam_systemd.so

to /etc/pam.d/lightdm and rebooting but didn't fix the problem. Anyone
have any other suggestions?

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

Title:
  Not authorized to perform operation / Unable to determine the session
  we are in: No session for pid

Status in “gdm” package in Ubuntu:
  Confirmed
Status in “lightdm” package in Ubuntu:
  Confirmed
Status in “lxdm” package in Ubuntu:
  Confirmed
Status in “policykit-desktop-privileges” package in Ubuntu:
  Confirmed

Bug description:
  After a new install of 64 bit Ubuntu 13.10 on my second partition, I
  used dpkg to reinstall all the same packages I had on my 32 bit 13.04
  partition.  I copied all my home directory files over and updated all
  the packages.  I now find that I don't have permissions to change the
  network settings; I can't mount my other hard drive or any USB stick
  using nautilus, or (udisks without using sudo)' I can't run synaptic
  by clicking on the GUI (I have to go to a terminal and sudo synaptic);
  etc.  I can't find any documentation on the configuration of
  policykit-desktop-privileges, so I'm filing this bug.  For me it
  appears to be totally broken.  Maybe someone can help me out.

  Thanks,

  Rob

  ProblemType: Bug
  DistroRelease: Ubuntu 13.10
  Package: policykit-desktop-privileges 0.16
  ProcVersionSignature: Ubuntu 3.11.0-12.19-generic 3.11.3
  Uname: Linux 3.11.0-12-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2
  Architecture: amd64
  Date: Tue Oct 15 20:20:55 2013
  InstallationDate: Installed on 2013-10-09 (7 days ago)
  InstallationMedia: Ubuntu 13.10 Saucy Salamander - Beta amd64 (20131008)
  MarkForUpload: True
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: policykit-desktop-privileges
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1069802] Re: keyboard shortcut changes aren't preserved

[Dean Henrichsmeyer]

A bit of additional information. I *believe* if you
logout/restart/reboot by clicking the icon in the top right and using
the menu, the navigation shortcuts are preserved. If you restart by any
other method, IE, reboot, init 6, shutdown, etc then the navigational
shortcuts are wiped. I'll update this if I find out to the contrary but
so far that's what I've found.

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

Title:
  keyboard shortcut changes aren't preserved

Status in Unity:
  Confirmed
Status in “unity” package in Ubuntu:
  Confirmed

Bug description:
  When I change keyboard shortcuts (such as changing desktops) via the
  keyboard settings in system preferences, they are not preserved across
  restarts.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: unity 6.8.0-0ubuntu2
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  Date: Mon Oct 22 15:09:29 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Release amd64 (20111012)
  SourcePackage: unity
  UpgradeStatus: Upgraded to quantal on 2012-10-19 (2 days ago)

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

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