[Touch-packages] [Bug 1808710] Re: !xcb_xlib_threads_sequence_lost error with GTK2 applications

2019-04-24 Thread Alex Fedorov
Unfortunately, setting LIBGL_DRI3_DISABLE to true did not help to bypass
the bug.

On the other hand, the bug does not manifest itself if there is only one
active CPU core. The number of active CPU cores can be controlled by
'maxcpus' kernel parameter: add 'maxcpus=1' to
GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub, then run update-grub as
root.

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

Title:
  !xcb_xlib_threads_sequence_lost error with GTK2 applications

Status in gtk+2.0 package in Ubuntu:
  Confirmed

Bug description:
  GTK2 applications randomly crash or freeze with same error. See
  attached files.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1808710/+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 1826311] [NEW] Cannot Login to Google with Advanced Protection Enabled

2019-04-24 Thread Kenneth Fechter
Public bug reported:

Description:Ubuntu 19.04
Release:19.04


gnome-online-accounts:
  Installed: 3.32.0-1ubuntu1
  Candidate: 3.32.0-1ubuntu1
  Version table:
 *** 3.32.0-1ubuntu1 500
500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
100 /var/lib/dpkg/status

1) Open Online accounts and select google (From settings or during OS setup)
2) enter username and password.

What I expect: I get the prompt to plug-in my 2 factor hardware key
What actually happens: I get a prompt saying, "You can only use your Security 
keys with Google Chrome"


Not sure if this is actually fixable, I know desktop firefox has hidden 
settings to allow u2f, but not sure if that extends to the embedded browsers 
(if gnome-online-accounts even uses an embedded firefox for its browser)

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-online-accounts 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Thu Apr 25 00:16:27 2019
InstallationDate: Installed on 2019-04-25 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-online-accounts
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gnome-online-accounts (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug disco

** Attachment added: "Screenshot of the "chrome only" dialog."
   
https://bugs.launchpad.net/bugs/1826311/+attachment/5258858/+files/Screenshot%20from%202019-04-25%2000-26-40.png

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

Title:
  Cannot Login to Google with Advanced Protection Enabled

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 19.04
  Release:  19.04

  
  gnome-online-accounts:
Installed: 3.32.0-1ubuntu1
Candidate: 3.32.0-1ubuntu1
Version table:
   *** 3.32.0-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

  1) Open Online accounts and select google (From settings or during OS setup)
  2) enter username and password.

  What I expect: I get the prompt to plug-in my 2 factor hardware key
  What actually happens: I get a prompt saying, "You can only use your Security 
keys with Google Chrome"

  
  Not sure if this is actually fixable, I know desktop firefox has hidden 
settings to allow u2f, but not sure if that extends to the embedded browsers 
(if gnome-online-accounts even uses an embedded firefox for its browser)

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Apr 25 00:16:27 2019
  InstallationDate: Installed on 2019-04-25 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1826311/+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 1826310] [NEW] display driver issue

2019-04-24 Thread ganesh
Public bug reported:

display driver issue

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
Uname: Linux 4.15.0-48-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Thu Apr 25 09:24:56 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [103c:3397]
InstallationDate: Installed on 2013-12-07 (1964 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
ProcEnviron:
 LANGUAGE=en_IN:en
 PATH=(custom, no user)
 LANG=en_IN
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=e586694b-5243-4be0-924c-d519be6aa981 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/16/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: K01 v02.90
dmi.board.asset.tag: INA346Z6BB
dmi.board.name: 3397
dmi.board.vendor: Hewlett-Packard
dmi.chassis.asset.tag: INA346Z6BB
dmi.chassis.type: 4
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:
dmi.product.family: 103C_53307F G=D
dmi.product.name: HP Compaq Elite 8300 SFF
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.98+git1904191830.be3b07~oibaf~b
version.libgl1-mesa-dri: libgl1-mesa-dri 19.1~git1904241930.09e477~oibaf~b
version.libgl1-mesa-glx: libgl1-mesa-glx 19.1~git1904241930.09e477~oibaf~b
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:19.0.1+git1903191930.36703f~oibaf~b
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git1903011933.6afed3~oibaf~b
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.16+git1904230730.ec2b45~oibaf~b
xserver.bootTime: Sat Feb 23 19:10:12 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.4-0ubuntu0.8

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


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

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

Title:
  display driver issue

Status in xorg package in Ubuntu:
  New

Bug description:
  display driver issue

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-48.51-generic 4.15.18
  Uname: Linux 4.15.0-48-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu Apr 25 09:24:56 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[8086:0162] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Xeon E3-1200 v2/3rd Gen Core processor 
Graphics Controller [103c:3397]
  InstallationDate: Installed on 2013-12-07 (1964 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MachineType: Hewlett-Packard HP Compaq Elite 8300 SFF
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-48-generic 
root=UUID=e586694b-5243-4be0-924c-d519be6aa981 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/16/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: K01 v02.90
  dmi.board.asset.tag: INA346Z6BB
  dmi.board.name: 3397
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: INA346Z6BB
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrK01v02.90:bd07/16/2013:svnHewlett-Packard:pnHPCompaqElite8300SFF:pvr:rvnHewlett-Packard:rn3397:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F G=D
  dmi.product.name: HP Compaq Elite 8300 SFF
  dmi.sys.vendor: Hewlett-Packard
  

[Touch-packages] [Bug 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted

2019-04-24 Thread Hui Wang
Ok, thanks.

I will contact Realtek to find the root cause.

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

Title:
  [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric
  background noise when volume is not muted

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

Bug description:
  Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start 
hearing a static/electric (some internal?) sound if the volume isn't muted. 
Something similar occurs with my other earbuds with mic, just much quieter and 
less noticable. It works fine on Windows 10 running on the same machine, and on 
my Android phone. I don't notice is when something is playing, but the 
frequency of the sound changes when I play something, then pause it, the 
background noise will sound slightly different.
  This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB 
and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with 
alsamixer and pavucontrol settings, and nothing fixed this background noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davidkoplik   1891 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 26 20:17:59 2018
  InstallationDate: Installed on 2018-12-26 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background 
noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

2019-04-24 Thread Phil Gorman
On 25/4/19 8:31 am, Troels Petersen wrote:
> I also reverted to Linux kernel 4.18.0-13-generic (The one that ships
> with Ubuntu 18.10) after upgrading to 19.04.
>
> System: HP Spectre 13 v000nf, 8 GB Memory, Dual core Intel i5-6200U CPU
> @ 2.30 GHz, Intel HD Graphics 520 (Skylake GT2)
>
> When running 'sudo apt upgrade' it complains about a missing dkms.conf
> file:
>
> Setting up linux-headers-5.0.0-13-generic (5.0.0-13.14) ...
> /etc/kernel/header_postinst.d/dkms:
> Error! Could not locate dkms.conf file.
> File: /var/lib/dkms/igfxdcd/1.1.11/source/dkms.conf does not exist.
> run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4
> dpkg: error processing package linux-headers-5.0.0-13-generic (--configure):
>   installed linux-headers-5.0.0-13-generic package post-installation script 
> subprocess returned error exit status 1
> dpkg: dependency problems prevent configuration of linux-headers-generic:
>   linux-headers-generic depends on linux-headers-5.0.0-13-generic; however:
>Package linux-headers-5.0.0-13-generic is not configured yet.
>
> dpkg: error processing package linux-headers-generic (--configure):
>   dependency problems - leaving unconfigured
> Setting up linux-image-5.0.0-13-generic (5.0.0-13.14) ...
> No apport report written because the error message indicates its a followup 
> error from a previous failure.
>   dpkg: dependency problems prevent configuration of linux-generic:
>   linux-generic depends on linux-headers-generic (= 5.0.0.13.14); however:
>Package linux-headers-generic is not configured yet.
>
> dpkg: error processing package linux-generic (--configure):
>   dependency problems - leaving unconfigured
> No apport report written because the error message indicates its a followup 
> error from a previous failure.
>   Processing triggers for linux-image-5.0.0-13-generic (5.0.0-13.14) ...
> /etc/kernel/postinst.d/dkms:
> Error! Could not locate dkms.conf file.
> File: /var/lib/dkms/igfxdcd/1.1.11/source/dkms.conf does not exist.
> run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
> dpkg: error processing package linux-image-5.0.0-13-generic (--configure):
>   installed linux-image-5.0.0-13-generic package post-installation script 
> subprocess returned error exit status 1
> No apport report written because MaxReports is reached already
>Errors were 
> encountered while processing:
>   linux-headers-5.0.0-13-generic
>   linux-headers-generic
>   linux-generic
>   linux-image-5.0.0-13-generic
> E: Sub-process /usr/bin/dpkg returned an error code (1)
>

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in Ubuntu MATE:
  New
Status in bamf package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mime-support package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH 

[Touch-packages] [Bug 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

2019-04-24 Thread Troels Petersen
I also reverted to Linux kernel 4.18.0-13-generic (The one that ships
with Ubuntu 18.10) after upgrading to 19.04.

System: HP Spectre 13 v000nf, 8 GB Memory, Dual core Intel i5-6200U CPU
@ 2.30 GHz, Intel HD Graphics 520 (Skylake GT2)

When running 'sudo apt upgrade' it complains about a missing dkms.conf
file:

Setting up linux-headers-5.0.0-13-generic (5.0.0-13.14) ...
/etc/kernel/header_postinst.d/dkms:
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/igfxdcd/1.1.11/source/dkms.conf does not exist.
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 4
dpkg: error processing package linux-headers-5.0.0-13-generic (--configure):
 installed linux-headers-5.0.0-13-generic package post-installation script 
subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-generic:
 linux-headers-generic depends on linux-headers-5.0.0-13-generic; however:
  Package linux-headers-5.0.0-13-generic is not configured yet.

dpkg: error processing package linux-headers-generic (--configure):
 dependency problems - leaving unconfigured
Setting up linux-image-5.0.0-13-generic (5.0.0-13.14) ...
No apport report written because the error message indicates its a followup 
error from a previous failure.
 dpkg: dependency problems prevent configuration of linux-generic:
 linux-generic depends on linux-headers-generic (= 5.0.0.13.14); however:
  Package linux-headers-generic is not configured yet.

dpkg: error processing package linux-generic (--configure):
 dependency problems - leaving unconfigured
No apport report written because the error message indicates its a followup 
error from a previous failure.
 Processing triggers for linux-image-5.0.0-13-generic (5.0.0-13.14) ...
/etc/kernel/postinst.d/dkms:
Error! Could not locate dkms.conf file.
File: /var/lib/dkms/igfxdcd/1.1.11/source/dkms.conf does not exist.
run-parts: /etc/kernel/postinst.d/dkms exited with return code 4
dpkg: error processing package linux-image-5.0.0-13-generic (--configure):
 installed linux-image-5.0.0-13-generic package post-installation script 
subprocess returned error exit status 1
No apport report written because MaxReports is reached already
  Errors were 
encountered while processing:
 linux-headers-5.0.0-13-generic
 linux-headers-generic
 linux-generic
 linux-image-5.0.0-13-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in Ubuntu MATE:
  New
Status in bamf package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mime-support package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet 

[Touch-packages] [Bug 1803993] Re: Password appears on the VT1 screen

2019-04-24 Thread Balint Reczey
** Changed in: gdm3 (Ubuntu)
   Status: Confirmed => Invalid

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

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Invalid
Status in plymouth package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  (continued from bug 1767918)

  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+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 1826274] [NEW] Headset keeps disconnecting after upgrade to Disco

2019-04-24 Thread Witold Krecicki
Public bug reported:

I'm using Bose QC35 headset and Dell XPS 9570 laptop. It was working
perfectly on Cosmic, after upgrade to Disco when headsed is switched to
HSP/HFP mode in pavucontrol I'm getting bursts of following messages in
dmesg:

Apr 24 23:27:28 daffy kernel: [53021.123542] Bluetooth: hci0: SCO packet for 
unknown connection handle 65534
Apr 24 23:27:28 daffy kernel: [53021.123551] Bluetooth: hci0: SCO packet for 
unknown connection handle 0
Apr 24 23:27:28 daffy kernel: [53021.143555] Bluetooth: hci0: SCO packet for 
unknown connection handle 63744
Apr 24 23:27:28 daffy kernel: [53021.153575] Bluetooth: hci0: SCO packet for 
unknown connection handle 1
Apr 24 23:27:28 daffy kernel: [53021.173563] Bluetooth: hci0: SCO packet for 
unknown connection handle 63744

Then, after at most a few minutes, after one of bursts like above,
pulseaudio reports:

Apr 24 23:27:28 daffy pulseaudio[2733]: W: [bluetooth] module-
bluez5-device.c: SCO packet received of unaligned size: 5 (the size
differs between runs)

And the headset is getting disconnected from pulseaudio - it's still
connected via Bluetooth, but it's status in pavucontrol switches to
'Disabled'.

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

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

Title:
  Headset keeps disconnecting after upgrade to Disco

Status in bluez package in Ubuntu:
  New

Bug description:
  I'm using Bose QC35 headset and Dell XPS 9570 laptop. It was working
  perfectly on Cosmic, after upgrade to Disco when headsed is switched
  to HSP/HFP mode in pavucontrol I'm getting bursts of following
  messages in dmesg:

  Apr 24 23:27:28 daffy kernel: [53021.123542] Bluetooth: hci0: SCO packet for 
unknown connection handle 65534
  Apr 24 23:27:28 daffy kernel: [53021.123551] Bluetooth: hci0: SCO packet for 
unknown connection handle 0
  Apr 24 23:27:28 daffy kernel: [53021.143555] Bluetooth: hci0: SCO packet for 
unknown connection handle 63744
  Apr 24 23:27:28 daffy kernel: [53021.153575] Bluetooth: hci0: SCO packet for 
unknown connection handle 1
  Apr 24 23:27:28 daffy kernel: [53021.173563] Bluetooth: hci0: SCO packet for 
unknown connection handle 63744

  Then, after at most a few minutes, after one of bursts like above,
  pulseaudio reports:

  Apr 24 23:27:28 daffy pulseaudio[2733]: W: [bluetooth] module-
  bluez5-device.c: SCO packet received of unaligned size: 5 (the size
  differs between runs)

  And the headset is getting disconnected from pulseaudio - it's still
  connected via Bluetooth, but it's status in pavucontrol switches to
  'Disabled'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1826274/+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 1506744] Re: Newly installed applications do not show in the dash

2019-04-24 Thread Treviño
** Changed in: bamf (Ubuntu)
   Status: In Progress => Triaged

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

Title:
  Newly installed applications do not show in the dash

Status in GLib:
  Expired
Status in bamf package in Ubuntu:
  Triaged
Status in gnome-menus package in Ubuntu:
  Fix Released
Status in libunity package in Ubuntu:
  Fix Released
Status in unity package in Ubuntu:
  Invalid
Status in gnome-menus source package in Xenial:
  Fix Released
Status in libunity source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  I am running 15.10 development version fully up to date, I installed it a few 
days ago and I have an issue with newly installed applications not appearing in 
the dash when I search for them, they can be started via console but the 
icons/launchers of newly installed applications will only appear in the dash 
after session is restarted.

  [Test case]
  1. Install a new applicaiton (using apt-get or the software center)
  2. Make sure the application is listed in the Unity Dash

  [Possible Regressions]
  Unity fails to list all the applications, not just the newly installed ones.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: unity 7.3.2+15.10.20151002.2-0ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Fri Oct 16 08:41:39 2015
  InstallationDate: Installed on 2015-10-11 (4 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20151011)
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)Z

To manage notifications about this bug go to:
https://bugs.launchpad.net/glib/+bug/1506744/+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 1718927] Re: No HDMI sound after suspend/resume on 16.04

2019-04-24 Thread Richard Anthony Horan
Update.  It is an intermittent problem for me.  It is working again.

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

Title:
  No HDMI sound after suspend/resume on 16.04

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1770919] Re: use_tempaddr is reset to 0, despite /etc/sysctl.d

2019-04-24 Thread Shivaram Lingamneni
systemd-networkd resets the value as per `systemd.network(5)`:
'IPv6PrivacyExtensions= [...]  When "kernel", the kernel's default
setting will be left in place. Defaults to "no".'

This will be fixed with
https://bugs.launchpad.net/ubuntu/+source/netplan.io/+bug/1750392

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

Title:
  use_tempaddr is reset to 0, despite /etc/sysctl.d

Status in systemd package in Ubuntu:
  New

Bug description:
  I'm on a fresh install of 18.04 Server. It ships with the following
  file in /etc/sysctl.d:

  # cat /etc/sysctl.d/10-ipv6-privacy.conf
  # IPv6 Privacy Extensions (RFC 4941)
  # ---
  # IPv6 typically uses a device's MAC address when choosing an IPv6 address
  # to use in autoconfiguration. Privacy extensions allow using a randomly
  # generated IPv6 address, which increases privacy.
  #
  # Acceptable values:
  #0 - don’t use privacy extensions.
  #1 - generate privacy addresses
  #2 - prefer privacy addresses and use them over the normal addresses.
  net.ipv6.conf.all.use_tempaddr = 2
  net.ipv6.conf.default.use_tempaddr = 2

  however, on boot, my physical NIC enp0s31f6 ends up with use_tempaddr
  set to 0:

  # for i in $(ls /proc/sys/net/ipv6/conf/*/use_tempaddr); do echo $i; cat $i; 
done;
  /proc/sys/net/ipv6/conf/all/use_tempaddr
  2
  /proc/sys/net/ipv6/conf/default/use_tempaddr
  2
  /proc/sys/net/ipv6/conf/enp0s31f6/use_tempaddr
  0
  /proc/sys/net/ipv6/conf/lo/use_tempaddr
  -1

  Explicitly adding the following line to 10-ipv6-privacy.conf does not
  fix:

  net.ipv6.conf.enp0s31f6.use_tempaddr = 2

  It appears that a later stage of the boot process reapplies the 0
  value. A workaround is to add the line, then create an additional
  systemd unit that runs `systemctl restart systemd-sysctl.service` at
  the end of the boot process.

  I think the expected behavior, given the contents of
  /etc/sysctl.d/10-ipv6-privacy.conf, is that all NICs should come up
  with use_tempaddr set to 2. This does not happen; moreover, the
  workaround is counterintuitive.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1770919/+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 1767453] Re: package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 1

2019-04-24 Thread miguelquiros
I think I have found the culprit. It is a package called "autofirma", 
distributed by the Spanish Administration to perform digital signatures with 
the official certificates provided by the government.
Apparently, there is some kind of incompatibility between the files generated 
by this package and the postinstallation script of this version of 
ca-certificates.
I have just removed (purge) the autofirma package, then update ca-certificates 
to 20180409 without any problem and, after that, reinstalled autofirma 
(probably I may need to uninstall it again when another ca-certificates version 
comes out).
As autofirma is not an ubuntu-provided package, this should not be considered a 
bug after all. In any case, the information may be useful for any other Spanish 
user finding the same problem.

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 1

Status in ca-certificates package in Ubuntu:
  Confirmed

Bug description:
  Happened during upgrade to ubunut 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Fri Apr 27 17:51:26 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1767453/+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 1823730] Re: Bionic: interface stuck in state "configuring" on a VM with two NICs, DHCP, and the secondary NIC configured to ignore routes from DHCP

2019-04-24 Thread Dan Streetman
*** This bug is a duplicate of bug 1804478 ***
https://bugs.launchpad.net/bugs/1804478

commit 223932c786ada7f758a7b7878a6ad2dae0d1e5fb was just added to
systemd in bionic via bug 1804478.

** This bug has been marked a duplicate of bug 1804478
   netplan dhcp interface with no default route causes 
systemd-networkd-wait-online to hang

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

Title:
  Bionic: interface stuck in state "configuring" on a VM with two NICs,
  DHCP, and the secondary NIC configured to ignore routes from DHCP

Status in systemd package in Ubuntu:
  New

Bug description:
  [Impact]

  Network interfaces not using route information from DHCP4 do not reach
  configured state, but remain 'configuring' on Bionic.

  [Test Case]

   1) Launch a VM with two network interfaces connected to ports on
  distinct network, each configured using DHCP4.

   2) Configure systemd-networkd to set up both interfaces via DHCP, but to 
ignore DHCP route information (plus possibly other system wide configuration 
supposed to be unambiguous, like DNS) from secondary interface. You can do so
  * either directly in /etc/systemd/network/, as shown in 
https://github.com/systemd/systemd/issues/9289,
  * or via netplan.io 0.96-0ubuntu0.18.04.2, as shown in 
https://bugs.launchpad.net/netplan/+bug/1759014/comments/48.

   3) Reboot.

   4) Both interfaces should now be reported as configured:

  # networkctl -a
  IDX LINK TYPE   OPERATIONAL SETUP
    1 lo   loopback   carrier unmanaged
    2 ens3 ether  routableconfigured
    3 ens4 ether  routableconfigured

  3 links listed.

  [Other Info]

  The issue is known for systemd releases before 239, and was fixed with
  
https://github.com/systemd/systemd/commit/223932c786ada7f758a7b7878a6ad2dae0d1e5fb.

  I have tested it by manually merging that fix into sources of systemd
  237-3ubuntu10.15, rebuilding and installing the package. Worked fine.

  See also https://bugs.launchpad.net/netplan/+bug/1759014 and
  https://bugs.launchpad.net/netplan/+bug/1776228.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823730/+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 1718927] Re: No HDMI sound after suspend/resume on 16.04

2019-04-24 Thread Richard Anthony Horan
I am having the same problem with Ubuntu 18.04.02 with HDMI audio.  No
sound on Resume and it can't be selected as a sound source after resume.
A reboot is the only fix.

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

Title:
  No HDMI sound after suspend/resume on 16.04

Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  When plugging in a HDMI TV to Lenovo Carbon 3rd Edition, sound works
  perfectly, but when I suspend computer and resume it there is no sound
  via HDMI in TV. However sound via built in speakers works fine. The
  only thing I can do to restore sound is to reboot the machine. Similar
  problem was discussed in following thread
  https://ubuntuforums.org/showthread.php?t=2251651 with no solution. I
  tested it on several versions of kernel 4.4.0 and on 4.4.8. Still no
  solution.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1718927/+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 1803993] Re: Password appears on the VT1 screen

2019-04-24 Thread Balint Reczey
Forwarded proposed fix to systemd upstream:
https://github.com/systemd/systemd/pull/12378

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

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

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  (continued from bug 1767918)

  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+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 1801540]

2019-04-24 Thread alex32.com
I have the same problem with MSI B450 Tomahawk Motherboard

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

Title:
  Microphone distorted sound on ALC892

Status in Linux:
  Confirmed
Status in linux package in Ubuntu:
  Incomplete
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Not sure if I'll report this upstream but there is definitely an issue
  with microphone recording on my desktop, this is not happening on my
  laptop which has a different codec.

  Already tried all workarounds possible, no luck. Only with my desktop
  with this particular motherboard. No issues in Windows, the sound
  recorded in there is distorted and has some static and robotic tone on
  high-pitch.

  alsa-info on the attachments

To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1801540/+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 701856] Re: Brother's printer/scanner drivers awkward to find and install

2019-04-24 Thread Tommy Trussell
Here's a procedure that worked for me in Ubuntu 18.04 Bionic.

For this procedure the user is "bob"

1) Install the latest brscan2 package (I have brscan2-0.2.5-1.amd64.deb
which I downloaded in 2014)

2) Manually link the drivers brscan2 installed into /usr/lib/x86_64
-linux-gnu/sane/ and /usr/lib/x86_64-linux-gnu/

  bob:~$ cd /usr/lib/x86_64-linux-gnu/sane

  bob:/usr/lib/x86_64-linux-gnu/sane$ sudo ln -sf /usr/lib64/sane
/libsane-brother2.so

[sudo] password for bob:

  bob:/usr/lib/x86_64-linux-gnu/sane$ sudo ln -sf 
/usr/lib64/sane/libsane-brother2.so.1
  bob:/usr/lib/x86_64-linux-gnu/sane$ sudo ln -sf 
/usr/lib64/sane/libsane-brother2.so.1.0.7 
  
  bob:/usr/lib/x86_64-linux-gnu/sane$ cd ..
  
  bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrcolm2.so
  bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrcolm2.so.1
  bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrcolm2.so.1.0.1 
  bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrscandec2.so
  bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrscandec2.so.1
  bob:/usr/lib/x86_64-linux-gnu$ sudo ln -sf /usr/lib64/libbrscandec2.so.1.0.0 


3) At this point scanimage -L should detect the scanner when run as root. 

  $ sudo scanimage -L

3a) If it doesn't work and especially if you're running something other
than Ubuntu Bionic, you might make verify SANE is looking in the right
directory using the debug flag

  $ SANE_DEBUG_DLL=128 scanimage -L

4) Create a udev file so the scanner is accessible to a scanner group

  $ sudo gedit /lib/udev/rules.d/96-brother-scanner.rules

   -- with the following contents:

# Brother DCP-7020 scanner
SUBSYSTEMS=="usb" \
, ATTRS{idVendor}=="04f9" \
, ATTRS{idProduct}=="0183" \
, ACTION=="add", \
, MODE="0664", \
, GROUP="scanner" \
, ENV{libsane_matched}="yes"

# note this udev instruction ends lines with \
# backslash so the single comma-separated 
# udev command is not crammed onto one line. 
# END OF FILE


5) Add the user bob to the scanner group (as specified in the udev file above):

  $ sudo adduser bob scanner

6) If you're bob and you weren't already in the group you'll have to log
out and back in, or reboot the system. To reload udev:

  $ sudo udevadm control --reload-rules

--> Everything should work after you reboot / login / reload. Yay.

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

Title:
  Brother's printer/scanner drivers awkward to find and install

Status in cups package in Ubuntu:
  Opinion

Bug description:
  Binary package hint: cupsys

  Hello,

  I have the multifonction laser printer and scan Brother DCP-7030.

  It works very well in Ubuntu, but with some hard configuration.
  Printer is automatically detected when connected in USB, but Ubuntu
  does not propose DCP-7030 drivers, only DCP-7025, and it doesn't work
  well.

  To get DCP-7030 fully recognized and well printing / scanning, I have to do 
this (it's a short summary) :
  http://solutions.brother.com/linux/en_us/before.html

  - Printer BROTHER DCP-7030 :

  cd ~/desktop
  sudo aa-complain cupsd
  sudo mkdir /usr/share/cups/model
  http://solutions.brother.com/linux/en_us/download_prn.html#DCP-7030
  sudo dpkg -i --force-all --force-architecture brdcp7030lpr-2.0.2-1.i386.deb
  sudo dpkg -i --force-all --force-architecture 
cupswrapperDCP7030-2.0.2-1.i386.deb
  http://127.0.0.1:631/printers/DCP7030 : OK

  After that printer works

  
  - SCANNING :

  Install scan-key-tools  /  Brscan3
  http://solutions.brother.com/linux/en_us/download_scn.html#brscan3
  http://solutions.brother.com/linux/en_us/instruction_scn1a.html

  sudo gedit /lib/udev/rules.d/50-udev-default.rules : in section
  "libusb device nodes", replacer 0664 by 0666

  sudo lsusb
  Bus 001 Device 004: ID 04f9:01a Brother Industries, Ltd
  Go to dev/bus/usb : bus 1 and device 4 is root owned
  Open it in Nautilus as root, change it to my user name and take ownership

  Now Simple Scan works, Brother-DCP is seen.

  But... big problem !

  At each restart of Ubuntu or DCP Brother, permission resets and comes
  back to root, I have to change ownership and re-log each time, this is
  not nice...

  Is it a way to "protect" the file against erasing or permission change
  ?

  It's also true for other models than DCP-7030 (like DCP-7040...). I do
  not know if it is a Cups / Ubuntu "bug" or Openprinting missing for
  new drivers, but as Brother gives functional drivers for Linux, this
  should be easily implemented I hope, as more and more materials are
  natively identified in Ubuntu.

  Thanks in advance for your help. Best regards,

  Xavier

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

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

[Touch-packages] [Bug 1825639] Re: Pulseaudio skips some time in the audio buffer, causing a bluetooth delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth 4.0]

2019-04-24 Thread Hammad R
I will report back once I have had time to re-modify my BIOS to remove
the WiFi whitelist, and then test my Intel 7260 on there with
coexistance (I'm sure the iwlwifi implements coexistence on all wifi +
bt cards, but its there for sure on my one anyway). This may take a few
weeks, but thanks for helping me out Daniel.

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

Title:
  Pulseaudio skips some time in the audio buffer, causing a bluetooth
  delay and crackling/clicking sound. [Broadcom Corp. BCM20702 Bluetooth
  4.0]

Status in bluez package in Ubuntu:
  Invalid

Bug description:
  This is the same problem in
  https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/405294 and
  even though I have pulseaudio 12.2 (on Xubuntu 18.10), this problem
  persists (this T430 laptop has inbuilt Bluetooth).

  This makes listening to music or any audio over Bluetooth almost
  unbearable - while it is temporarily fixed by running `pactl suspend-
  sink 1 && pactl suspend-sink 0` it soon returns. I have even updated
  the BIOS but the problem persists.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: bluez 5.50-0ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
  Uname: Linux 4.18.0-11-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Apr 20 13:10:59 2019
  InstallationDate: Installed on 2018-11-26 (144 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 2349G4G
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic 
root=UUID=0e4c79dc-6836-4dcb-a54a-2c5842e1f6c1 ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/19/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G1ETB9WW (2.79 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 2349G4G
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG1ETB9WW(2.79):bd02/19/2019:svnLENOVO:pn2349G4G:pvrThinkPadT430:rvnLENOVO:rn2349G4G:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad T430
  dmi.product.name: 2349G4G
  dmi.product.sku: LENOVO_MT_2349
  dmi.product.version: ThinkPad T430
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 24:FD:52:8C:5D:82  ACL MTU: 1021:8  SCO MTU: 64:1
UP RUNNING PSCAN 
RX bytes:65823 acl:64 sco:0 events:9052 errors:0
TX bytes:15368368 acl:17880 sco:0 commands:101 errors:0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1825639/+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 1809856] Re: [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric background noise when volume is not muted

2019-04-24 Thread Chris
This noise disappears when running this command.

sudo ./hda-verb /dev/snd/hwC0D0 0x1d SET_PIN_WIDGET_CONTROL 0x0

The noise returns when running this command.

sudo hda-verb /dev/snd/hwC0D0 0x1d SET_PIN_WIDGET_CONTROL 0x20

Thanks!

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

Title:
  [XPS 13 9370, Realtek ALC3271, Headphone Out, Right] Static/Electric
  background noise when volume is not muted

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

Bug description:
  Whenever I plug in my Sennheiser HD1 Wired headphones with mic, I start 
hearing a static/electric (some internal?) sound if the volume isn't muted. 
Something similar occurs with my other earbuds with mic, just much quieter and 
less noticable. It works fine on Windows 10 running on the same machine, and on 
my Android phone. I don't notice is when something is playing, but the 
frequency of the sound changes when I play something, then pause it, the 
background noise will sound slightly different.
  This is from an installed Ubuntu 18.10. I have tried booting 18.10 Live USB 
and 18.04.1 LTS Live USB, and the issue still occurs. I have tried playing with 
alsamixer and pavucontrol settings, and nothing fixed this background noise.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  davidkoplik   1891 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Dec 26 20:17:59 2018
  InstallationDate: Installed on 2018-12-26 (0 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Right
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: High background noise, or volume is too low
  Title: [XPS 13 9370, Realtek ALC3271, Black Headphone Out, Right] Background 
noise or low volume
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/04/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.6.3
  dmi.board.name: 0F6P3V
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.6.3:bd11/04/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1809856/+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 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails

2019-04-24 Thread Kevin L.
https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/60

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

Title:
  Gnome Online Accounts fails to sign in Exchange emails

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 and/or on fresh install, a known-working
  Exchange email setup fails to sign in, giving "Error 7: Unexpected
  response from server".  Tested the same settings and credentials on a
  new install of 18.10 and it worked.

  I have Evolution and Evolution-ews installed on all instances, working
  in 18.10, not in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 16:38:32 2019
  InstallationDate: Installed on 2018-03-24 (391 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+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 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails

2019-04-24 Thread Kevin L.
I have submitted upstream: GNOME/gnome-online-accounts#60

Thanks for your attention to this!

** Bug watch added: gitlab.gnome.org/GNOME/gnome-online-accounts/issues #60
   https://gitlab.gnome.org/GNOME/gnome-online-accounts/issues/60

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

Title:
  Gnome Online Accounts fails to sign in Exchange emails

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 and/or on fresh install, a known-working
  Exchange email setup fails to sign in, giving "Error 7: Unexpected
  response from server".  Tested the same settings and credentials on a
  new install of 18.10 and it worked.

  I have Evolution and Evolution-ews installed on all instances, working
  in 18.10, not in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 16:38:32 2019
  InstallationDate: Installed on 2018-03-24 (391 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+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 1826151] Thanks for the reply

2019-04-24 Thread djennane
Sent from my Huawei Mobile

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

Title:
  Can someone help me out and explain or point me in the right direction
  on how to check video drivers and see if my video card running okay

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Can someone help me out and explain or point me in the right direction
  on how to check video drivers and see if my video card running okay

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 09:56:02 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3675]
   NVIDIA Corporation GK107M [GeForce GT 745M] [10de:0fe3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GeForce GT 745A [17aa:3675]
  InstallationDate: Installed on 2019-04-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 10123
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I8KT15AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrI8KT15AUS:bd04/18/2013:svnLENOVO:pn10123:pvrIdeaCentreA730:rvnLENOVO:rnSHARKBAY:rvr3194STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.family: IdeaCentre
  dmi.product.name: 10123
  dmi.product.sku: LENOVO_MT_1012
  dmi.product.version: IdeaCentre A730
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1826151/+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 1822062] Re: Race condition on boot between cups and sssd

2019-04-24 Thread Ubuntu Foundations Team Bug Bot
The attachment "eoan-cups.debdiff" seems to be a debdiff.  The ubuntu-
sponsors team has been subscribed to the bug report so that they can
review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issue please contact him.]

** Tags added: patch

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  In Progress
Status in cups source package in Xenial:
  New
Status in cups source package in Bionic:
  New
Status in cups source package in Cosmic:
  New
Status in cups source package in Disco:
  New
Status in cups source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1826222] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/eoan

2019-04-24 Thread Sebastien Bacher
** Changed in: python-apt (Ubuntu)
   Importance: Undecided => High

** Changed in: python-apt (Ubuntu)
   Status: Confirmed => Fix Committed

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

Title:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources(): Error:
  could not find a distribution template for Ubuntu/eoan

Status in python-apt package in Ubuntu:
  Fix Committed

Bug description:
  [Impact]
  The 'Configuration' button of update-manager does not work.

  [Test Case]
  $ sudo update-manager
  Traceback (most recent call last):
    File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
    File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826222/+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 1822062] Re: Race condition on boot between cups and sssd

2019-04-24 Thread Eric Desrochers
There is a debian->ubuntu sync right now in eoan-proposed.

I'll sponsor it once the actual sync is completed and found in eoan-
releases.

Meanwhile, could you please report a bug and forward the patch to debian
to make sure the problem is fix to prevent re-introducing the issue at
next debian->ubuntu sync/merge.

- Eric

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  In Progress
Status in cups source package in Xenial:
  New
Status in cups source package in Bionic:
  New
Status in cups source package in Cosmic:
  New
Status in cups source package in Disco:
  New
Status in cups source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1826151] Re: Can someone help me out and explain or point me in the right direction on how to check video drivers and see if my video card running okay

2019-04-24 Thread Nowres Rafid
There was a good tool called jockey, but I don't know why it was removed
and what replaced it.

For you graphics card, you have 2 options:
- Nouveau: Free opensource driver for nvidia cards
- Proprietary driver from Nvidia

I recommend you use the proprietary driver for maximum performance. For
better compatibility and integration, use nouveau the opensource one.

 To check if the proprietary driver is installed run:
ubuntu-drivers debug

at the bottom it will list each compatible proprietary driver and
whether it's installed or not.

Other tools that may help you:
nvidia-smi
nvidia-settings
glxinfo | egrep "OpenGL vendor|OpenGL renderer*"

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

Title:
  Can someone help me out and explain or point me in the right direction
  on how to check video drivers and see if my video card running okay

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Can someone help me out and explain or point me in the right direction
  on how to check video drivers and see if my video card running okay

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 09:56:02 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3675]
   NVIDIA Corporation GK107M [GeForce GT 745M] [10de:0fe3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GeForce GT 745A [17aa:3675]
  InstallationDate: Installed on 2019-04-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 10123
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I8KT15AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrI8KT15AUS:bd04/18/2013:svnLENOVO:pn10123:pvrIdeaCentreA730:rvnLENOVO:rnSHARKBAY:rvr3194STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.family: IdeaCentre
  dmi.product.name: 10123
  dmi.product.sku: LENOVO_MT_1012
  dmi.product.version: IdeaCentre A730
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1826151/+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 1826222] Re: software-properties-gtk crashed with aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not find a distribution template for Ubuntu/eoan

2019-04-24 Thread El jinete sin cabeza
** Summary changed:

- The 'Configuration' button of update-manager does not work
+ software-properties-gtk crashed with 
aptsources.distro.NoDistroTemplateException in get_sources(): Error: could not 
find a distribution template for Ubuntu/eoan

** Description changed:

- $ sudo update-manager 
+ The 'Configuration' button of update-manager does not work.
+ 
+ $ sudo update-manager
  Traceback (most recent call last):
-   File "/usr/bin/software-properties-gtk", line 100, in 
- app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
- SoftwareProperties.__init__(self, options=options, datadir=datadir)
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
- self.reload_sourceslist()
-   File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
- self.distro.get_sources(self.sourceslist)
-   File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
- (self.id, self.codename))
+   File "/usr/bin/software-properties-gtk", line 100, in 
+ app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
+ SoftwareProperties.__init__(self, options=options, datadir=datadir)
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
+ self.reload_sourceslist()
+   File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
+ self.distro.get_sources(self.sourceslist)
+   File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
+ (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

** Description changed:

+ [Impact]
  The 'Configuration' button of update-manager does not work.
  
+ [Test Case]
  $ sudo update-manager
  Traceback (most recent call last):
    File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
    File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
    File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

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

Title:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources(): Error:
  could not find a distribution template for Ubuntu/eoan

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  [Impact]
  The 'Configuration' button of update-manager does not work.

  [Test Case]
  $ sudo update-manager
  Traceback (most recent call last):
    File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
    File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",

[Touch-packages] [Bug 1822062] Re: Race condition on boot between cups and sssd

2019-04-24 Thread Eric Desrochers
** Changed in: cups (Ubuntu Eoan)
   Importance: Undecided => Medium

** Changed in: cups (Ubuntu Eoan)
   Status: New => In Progress

** Changed in: cups (Ubuntu Eoan)
 Assignee: (unassigned) => Victor Tapia (vtapia)

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  In Progress
Status in cups source package in Xenial:
  New
Status in cups source package in Bionic:
  New
Status in cups source package in Cosmic:
  New
Status in cups source package in Disco:
  New
Status in cups source package in Eoan:
  In Progress

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1803993] Re: Password appears on the VT1 screen

2019-04-24 Thread Balint Reczey
** Changed in: systemd (Ubuntu)
   Importance: Undecided => High

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Balint Reczey (rbalint)

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  (continued from bug 1767918)

  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+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 1822062] Re: Race condition on boot between cups and sssd

2019-04-24 Thread Victor Tapia
** Patch added: "cosmic-cups.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258669/+files/cosmic-cups.debdiff

** Patch removed: "disco-cups.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258668/+files/disco-cups.debdiff

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  New
Status in cups source package in Xenial:
  New
Status in cups source package in Bionic:
  New
Status in cups source package in Cosmic:
  New
Status in cups source package in Disco:
  New
Status in cups source package in Eoan:
  New

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1822062] Re: Race condition on boot between cups and sssd

2019-04-24 Thread Victor Tapia
** Patch added: "bionic-cups.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258670/+files/bionic-cups.debdiff

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  New
Status in cups source package in Xenial:
  New
Status in cups source package in Bionic:
  New
Status in cups source package in Cosmic:
  New
Status in cups source package in Disco:
  New
Status in cups source package in Eoan:
  New

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1822062] Re: Race condition on boot between cups and sssd

2019-04-24 Thread Victor Tapia
** Patch added: "xenial-cups.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258671/+files/xenial-cups.debdiff

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  New
Status in cups source package in Xenial:
  New
Status in cups source package in Bionic:
  New
Status in cups source package in Cosmic:
  New
Status in cups source package in Disco:
  New
Status in cups source package in Eoan:
  New

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1822062] Re: Race condition on boot between cups and sssd

2019-04-24 Thread Victor Tapia
** Description changed:

+ [Impact]
+ 
+  * When cups has set the "SystemGroup" directive to an external group
+ provided through sss and cups starts before sssd has finished booting,
+ cups will crash because the group does not exist.
+ 
+  * The patch adds an "After=sssd.service" clause to the service unit
+ file.
+ 
+ [Test Case]
+ 
+  * Configure an external authentication service (LDAP, AD...) and create
+ a group, for instance "lpadmins@tests.local"
+ 
+  * Set SystemGroup to match that group (SystemGroup =
+ "lpadmins@tests.local")
+ 
+  * Reboot
+ 
+  * If cups has started before sssd has finished booting, cups will crash:
+ Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
+ 
+  * If cups starts after sssd, it will work fine.
+ 
+ [Regression Potential]
+ 
+  * Minimal: this patch affects just the ordering of the service unit
+ file.
+ 
+ [Other Info]
+  
+  * Upstream: 
https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d
+ 
+ [Original description]
+ 
  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:
  
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.
  
  If sssd is running before cups starts, everything works as expected.

** Also affects: cups (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: cups (Ubuntu Xenial)
   Importance: Undecided
   Status: New

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

** Also affects: cups (Ubuntu Disco)
   Importance: Undecided
   Status: New

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

** Description changed:

  [Impact]
  
-  * When cups has set the "SystemGroup" directive to an external group
+  * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.
  
-  * The patch adds an "After=sssd.service" clause to the service unit
+  * The patch adds an "After=sssd.service" clause to the service unit
  file.
  
  [Test Case]
  
-  * Configure an external authentication service (LDAP, AD...) and create
+  * Configure an external authentication service (LDAP, AD...) and create
  a group, for instance "lpadmins@tests.local"
  
-  * Set SystemGroup to match that group (SystemGroup =
- "lpadmins@tests.local")
+  * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
+ SystemGroup lpadmins@tests.local
  
-  * Reboot
+  * Reboot
  
-  * If cups has started before sssd has finished booting, cups will crash:
+  * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  
-  * If cups starts after sssd, it will work fine.
+  * If cups starts after sssd, it will work fine.
  
  [Regression Potential]
  
-  * Minimal: this patch affects just the ordering of the service unit
+  * Minimal: this patch affects just the ordering of the service unit
  file.
  
  [Other Info]
-  
-  * Upstream: 
https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d
+ 
+  * Upstream:
+ https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d
  
  [Original description]
  
  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active 

[Touch-packages] [Bug 1822062] Re: Race condition on boot between cups and sssd

2019-04-24 Thread Victor Tapia
** Patch added: "disco-cups.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258667/+files/disco-cups.debdiff

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  New
Status in cups source package in Xenial:
  New
Status in cups source package in Bionic:
  New
Status in cups source package in Cosmic:
  New
Status in cups source package in Disco:
  New
Status in cups source package in Eoan:
  New

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1822062] Re: Race condition on boot between cups and sssd

2019-04-24 Thread Victor Tapia
** Patch added: "disco-cups.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+attachment/5258668/+files/disco-cups.debdiff

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

Title:
  Race condition on boot between cups and sssd

Status in cups package in Ubuntu:
  New
Status in cups source package in Xenial:
  New
Status in cups source package in Bionic:
  New
Status in cups source package in Cosmic:
  New
Status in cups source package in Disco:
  New
Status in cups source package in Eoan:
  New

Bug description:
  [Impact]

   * When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist.

   * The patch adds an "After=sssd.service" clause to the service unit
  file.

  [Test Case]

   * Configure an external authentication service (LDAP, AD...) and
  create a group, for instance "lpadmins@tests.local"

   * Set SystemGroup to match that group in /etc/cups/cups-files.conf:
  SystemGroup lpadmins@tests.local

   * Reboot

   * If cups has started before sssd has finished booting, cups will crash:
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.

   * If cups starts after sssd, it will work fine.

  [Regression Potential]

   * Minimal: this patch affects just the ordering of the service unit
  file.

  [Other Info]

   * Upstream:
  https://github.com/apple/cups/commit/4d0f1959a3f46973caec2cd41828c59674fe195d

  [Original description]

  When cups has set the "SystemGroup" directive to an external group
  provided through sss and cups starts before sssd has finished booting,
  cups will crash because the group does not exist. For instance, with a
  group named lpadmins@tests.local served from Active Directory through
  sssd, if the sssd service hasn't booted before cups:

  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started CUPS Scheduler.
  Mar 27 10:10:33 cups-sssd systemd[1]: Started Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unknown SystemGroup 
"lpadmins@tests.local" on line 19 of /etc/cups/cups-files.conf.
  Mar 27 10:10:33 cups-sssd cupsd[21463]: Unable to read 
"/etc/cups/cups-files.conf" due to errors.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Main process exited, 
code=exited, status=1/FAILURE
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Failed with result 
'exit-code'.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Service hold-off time 
over, scheduling restart.
  Mar 27 10:10:33 cups-sssd systemd[1]: cups.service: Scheduled restart job, 
restart counter is at 2.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopping Make remote CUPS printers 
available locally...
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped Make remote CUPS printers 
available locally.
  Mar 27 10:10:33 cups-sssd systemd[1]: Stopped CUPS Scheduler.

  If sssd is running before cups starts, everything works as expected.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062/+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 1826222] Re: The 'Configuration' button of update-manager does not work

2019-04-24 Thread corrado venturini
solved after installing proposed

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

Title:
  The 'Configuration' button of update-manager does not work

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  $ sudo update-manager 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826222/+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 1826222] Re: The 'Configuration' button of update-manager does not work

2019-04-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: python-apt (Ubuntu)
   Status: New => Confirmed

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

Title:
  The 'Configuration' button of update-manager does not work

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  $ sudo update-manager 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826222/+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 1826222] Re: The 'Configuration' button of update-manager does not work

2019-04-24 Thread El jinete sin cabeza
@Sebastien

> Does https://bugs.launchpad.net/ubuntu/+source/python-
apt/1.9.0~alpha0~ubuntu1 fix your issue?

Yes, Now it works correctly.

** Attachment added: "$ dpkg -l | grep python-apt"
   
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826222/+attachment/5258649/+files/dpkg_-l_-_grep_python-apt.txt

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

Title:
  The 'Configuration' button of update-manager does not work

Status in python-apt package in Ubuntu:
  Confirmed

Bug description:
  $ sudo update-manager 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826222/+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 1826151] Re: Can someone help me out and explain or point me in the right direction on how to check video drivers and see if my video card running okay

2019-04-24 Thread Nowres Rafid
This is a question

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

** Converted to question:
   https://answers.launchpad.net/ubuntu/+source/xorg/+question/680421

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

Title:
  Can someone help me out and explain or point me in the right direction
  on how to check video drivers and see if my video card running okay

Status in xorg package in Ubuntu:
  Invalid

Bug description:
  Can someone help me out and explain or point me in the right direction
  on how to check video drivers and see if my video card running okay

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 09:56:02 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3675]
   NVIDIA Corporation GK107M [GeForce GT 745M] [10de:0fe3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GeForce GT 745A [17aa:3675]
  InstallationDate: Installed on 2019-04-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 10123
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I8KT15AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrI8KT15AUS:bd04/18/2013:svnLENOVO:pn10123:pvrIdeaCentreA730:rvnLENOVO:rnSHARKBAY:rvr3194STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.family: IdeaCentre
  dmi.product.name: 10123
  dmi.product.sku: LENOVO_MT_1012
  dmi.product.version: IdeaCentre A730
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1826151/+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 1826222] Re: The 'Configuration' button of update-manager does not work

2019-04-24 Thread Sebastien Bacher
Does https://bugs.launchpad.net/ubuntu/+source/python-
apt/1.9.0~alpha0~ubuntu1 fix your issue?

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

** Changed in: python-apt (Ubuntu)
   Status: Confirmed => New

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

Title:
  The 'Configuration' button of update-manager does not work

Status in python-apt package in Ubuntu:
  New

Bug description:
  $ sudo update-manager 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826222/+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 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails

2019-04-24 Thread Sebastien Bacher
Thanks, it does sound like an upstream issue indeed and should be
reported upstream on https://gitlab.gnome.org/GNOME/gnome-online-
accounts/. Could you do that or would you prefer us to resubmit it there
for you?

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

Title:
  Gnome Online Accounts fails to sign in Exchange emails

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 and/or on fresh install, a known-working
  Exchange email setup fails to sign in, giving "Error 7: Unexpected
  response from server".  Tested the same settings and credentials on a
  new install of 18.10 and it worked.

  I have Evolution and Evolution-ews installed on all instances, working
  in 18.10, not in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 16:38:32 2019
  InstallationDate: Installed on 2018-03-24 (391 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+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 1825738] Re: could not find a distribution template for Ubuntu/eoan

2019-04-24 Thread Sebastien Bacher
*** This bug is a duplicate of bug 1826222 ***
https://bugs.launchpad.net/bugs/1826222

** This bug has been marked a duplicate of bug 1826222
   The 'Configuration' button of update-manager does not work

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

Title:
  could not find a distribution template for Ubuntu/eoan

Status in software-properties package in Ubuntu:
  New

Bug description:
  software-properties-gtk crashed with
  aptsources.distro.NoDistroTemplateException in get_sources(): Error:
  could not find a distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 20:18:19 2019
  InstallationDate: Installed on 2019-04-21 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190421)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1825738/+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 1826222] Re: The 'Configuration' button of update-manager does not work

2019-04-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: software-properties (Ubuntu)
   Status: New => Confirmed

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

Title:
  The 'Configuration' button of update-manager does not work

Status in python-apt package in Ubuntu:
  New

Bug description:
  $ sudo update-manager 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826222/+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 1823871] Re: After unattended-upgrade of systemd IP configuration removed from interfaces

2019-04-24 Thread Domonkos Tomcsanyi
** Changed in: systemd (Ubuntu)
   Status: Incomplete => New

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

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

Title:
  After unattended-upgrade of systemd IP configuration removed from
  interfaces

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Info:
  Ubuntu Server 18.04 LTS, 4.15.0-43-generic, fresh installation (December, 
2018).
  HP DL380 server

  I had this issue already twice in the past couple of months. After unattended 
upgrade of systemd my server's public IP address is removed from the interface.
  I statically configure the IP address using the interfaces file. I have opted 
out of the YML based network configuration. This is my apt history log:

  Start-Date: 2019-04-09  06:15:01
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: systemd-sysv:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:07

  Start-Date: 2019-04-09  06:15:12
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: udev:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), libudev1:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19)
  End-Date: 2019-04-09  06:15:56

  Start-Date: 2019-04-09  06:15:59
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libsystemd0:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), 
libpam-systemd:amd64 (237-3ubuntu10.13, 237-3ubuntu10.19), systemd:amd64 
(237-3ubuntu10.13, 237-3ubuntu10.19), libnss-systemd:amd64 (237-3ubuntu10.13, 
237-3ubuntu10.19)
  End-Date: 2019-04-09  06:16:15

  
  After that my server was unavailable from the Internet. When I logged in via 
out of band management and simply brought down and up the interface everything 
went back to normal. As said above this is the second time I had this issue. 
Last time it was unattended upgrades and it was systemd again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1823871/+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 1826222] Re: The 'Configuration' button of update-manager does not work

2019-04-24 Thread El jinete sin cabeza
See LP: #1825738

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

Title:
  The 'Configuration' button of update-manager does not work

Status in software-properties package in Ubuntu:
  New

Bug description:
  $ sudo update-manager 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1826222/+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 1826183] Re: /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-upgrade@2268:main:run:get_auto_removable::__iter__:keys:

2019-04-24 Thread Brian Murray
On Wed, Apr 24, 2019 at 10:46:58AM -, Julian Andres Klode wrote:
> Crazy, who has invalid unicode in package names?

I think I've seen that before with unofficial repositories.

--
Brian Murray

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

Title:
  /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-
  upgrade@2268:main:run:get_auto_removable::__iter__:keys:

Status in python-apt package in Ubuntu:
  New

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

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2268, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1732, in main
  install_start_time)
File "/usr/bin/unattended-upgrade", line 1906, in run
  auto_removable = get_auto_removable(cache)
File "/usr/bin/unattended-upgrade", line 1557, in get_auto_removable
  return {pkg.name for pkg in cache
File "/usr/bin/unattended-upgrade", line 1557, in 
  return {pkg.name for pkg in cache
File "/usr/lib/python3/dist-packages/apt/cache.py", line 333, in __iter__
  for pkgname in self.keys():
File "/usr/lib/python3/dist-packages/apt/cache.py", line 361, in keys
  for p in self._cache.packages
File "/usr/lib/python3/dist-packages/apt/cache.py", line 362, in 
  if self.__is_real_pkg(p))
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 16: 
invalid continuation byte

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826183/+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 1826223] [NEW] lvm not detected in initramfs after upgrade to 19.04

2019-04-24 Thread Nowres Rafid
Public bug reported:

Hello,

After upgrading to 19.04, I was unable to boot into linux 5.0 kernel, I got an 
lvm not found message after providing my luks passphrase
I fell back to an older kernel version to be able to boot into my system

Here is my grub entry:

```
menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-a895fab8-6c63-4707-ace2-eaf1f4f3e02a' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  
7fc86ec8-e5ac-4a11-9153-622e7a9ace07
else
  search --no-floppy --fs-uuid --set=root 
7fc86ec8-e5ac-4a11-9153-622e7a9ace07
fi
linux   /vmlinuz-5.0.0-13-generic root=/dev/mapper/vg00-root ro  
nosplash
initrd  /initrd.img-5.0.0-13-generic
}
```

Nowres

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


** Tags: regression-release

** Tags added: regression-release

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

Title:
  lvm not detected in initramfs after upgrade to 19.04

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Hello,

  After upgrading to 19.04, I was unable to boot into linux 5.0 kernel, I got 
an lvm not found message after providing my luks passphrase
  I fell back to an older kernel version to be able to boot into my system

  Here is my grub entry:

  ```
  menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os 
$menuentry_id_option 'gnulinux-simple-a895fab8-6c63-4707-ace2-eaf1f4f3e02a' {
recordfail
load_video
gfxmode $linux_gfx_mode
insmod gzio
if [ x$grub_platform = xxen ]; then insmod xzio; insmod lzopio; fi
insmod part_msdos
insmod ext2
set root='hd1,msdos1'
if [ x$feature_platform_search_hint = xy ]; then
  search --no-floppy --fs-uuid --set=root --hint-bios=hd1,msdos1 
--hint-efi=hd1,msdos1 --hint-baremetal=ahci1,msdos1  
7fc86ec8-e5ac-4a11-9153-622e7a9ace07
else
  search --no-floppy --fs-uuid --set=root 
7fc86ec8-e5ac-4a11-9153-622e7a9ace07
fi
linux   /vmlinuz-5.0.0-13-generic root=/dev/mapper/vg00-root ro  
nosplash
initrd  /initrd.img-5.0.0-13-generic
  }
  ```

  Nowres

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1826223/+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 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails

2019-04-24 Thread KEVIN M LYON
And on the one machine, the install of 18.10 had the EWS account
working, then on upgrade it wouldn't connect--kept asking for the
password even after entering multiple times. I deleted the account and
tried to set up again, but it failed with this same error.

On all of my installs (even fresh installs) the Microsoft Exchange
option on Online Accounts appears with a red icon instead of the
Exchange icon.

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

Title:
  Gnome Online Accounts fails to sign in Exchange emails

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 and/or on fresh install, a known-working
  Exchange email setup fails to sign in, giving "Error 7: Unexpected
  response from server".  Tested the same settings and credentials on a
  new install of 18.10 and it worked.

  I have Evolution and Evolution-ews installed on all instances, working
  in 18.10, not in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 16:38:32 2019
  InstallationDate: Installed on 2018-03-24 (391 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+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 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails

2019-04-24 Thread KEVIN M LYON
The error is in the Online Accounts menu from the settings panel.  The
Error 7 appears as a red box over the account sign in window after I
enter the same credentials and server address I used in 18.10.  I tested
this on Majaro, Pop_OS and Ubuntu with Gnome 3.32 and it happens on all
of them, so seems to be related to Gnome itself.

I believe we're on Exchange 2010 still.  The account doesn't show up at
all in Evolution since it never gets added to Online Accounts or
Seahorse due to the error.

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

Title:
  Gnome Online Accounts fails to sign in Exchange emails

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 and/or on fresh install, a known-working
  Exchange email setup fails to sign in, giving "Error 7: Unexpected
  response from server".  Tested the same settings and credentials on a
  new install of 18.10 and it worked.

  I have Evolution and Evolution-ews installed on all instances, working
  in 18.10, not in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 16:38:32 2019
  InstallationDate: Installed on 2018-03-24 (391 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+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 1826222] [NEW] The 'Configuration' button of update-manager does not work

2019-04-24 Thread El jinete sin cabeza
Public bug reported:

$ sudo update-manager 
Traceback (most recent call last):
  File "/usr/bin/software-properties-gtk", line 100, in 
app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
SoftwareProperties.__init__(self, options=options, datadir=datadir)
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
self.reload_sourceslist()
  File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
self.distro.get_sources(self.sourceslist)
  File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
(self.id, self.codename))
aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: software-properties-gtk 0.97.11
Uname: Linux 5.1.0-050100rc6-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 24 10:21:47 2019
InstallationDate: Installed on 2018-12-02 (142 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  The 'Configuration' button of update-manager does not work

Status in software-properties package in Ubuntu:
  New

Bug description:
  $ sudo update-manager 
  Traceback (most recent call last):
File "/usr/bin/software-properties-gtk", line 100, in 
  app = SoftwarePropertiesGtk(datadir=options.data_dir, options=options, 
file=file)
File 
"/usr/lib/python3/dist-packages/softwareproperties/gtk/SoftwarePropertiesGtk.py",
 line 115, in __init__
  SoftwareProperties.__init__(self, options=options, datadir=datadir)
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
117, in __init__
  self.reload_sourceslist()
File 
"/usr/lib/python3/dist-packages/softwareproperties/SoftwareProperties.py", line 
612, in reload_sourceslist
  self.distro.get_sources(self.sourceslist)
File "/usr/lib/python3/dist-packages/aptsources/distro.py", line 93, in 
get_sources
  (self.id, self.codename))
  aptsources.distro.NoDistroTemplateException: Error: could not find a 
distribution template for Ubuntu/eoan

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: software-properties-gtk 0.97.11
  Uname: Linux 5.1.0-050100rc6-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 10:21:47 2019
  InstallationDate: Installed on 2018-12-02 (142 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (142 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1826222/+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 1803993] Re: Password appears on the VT1 screen

2019-04-24 Thread Balint Reczey
It looks like systemd is changing the mode (see argument=3) on VT1 on
logouts.

#define K_RAW   0x00
#define K_XLATE 0x01
#define K_MEDIUMRAW 0x02
#define K_UNICODE   0x04
#define K_OFF   0x04
#define KDGKBMODE   0x4B44  /* gets current keyboard mode */
#define KDSKBMODE   0x4B45  /* sets current keyboard mode */

test@test-Standard-PC-i440FX-PIIX-1996:~$ sudo sysdig evt.type=ioctl | grep  
request=4B45
[sudo] password for test:
5657343 15:21:51.819076315 1 Xorg (1069) > ioctl fd=11(/dev/tty1) 
request=4B45 argument=4
5657453 15:21:51.820019063 0 systemd-logind (575) > ioctl fd=22(/dev/tty1) 
request=4B45 argument=3
5753055 15:21:52.771635876 0 systemd-logind (575) > ioctl fd=21(/dev/tty1) 
request=4B45 argument=4
20723813 15:49:41.368621972 1 systemd (23717) > ioctl fd=3(/dev/tty2) 
request=4B45 argument=3 
22605710 15:53:04.107253025 1 systemd-logind (575) > ioctl fd=23(/dev/tty3) 
request=4B45 argument=4 
22612602 15:53:04.142057934 1 Xorg (24089) > ioctl fd=11(/dev/tty3) 
request=4B45 argument=4 
24077108 15:53:28.705600119 0 Xorg (24089) > ioctl fd=11(/dev/tty3) 
request=4B45 argument=4 
24077278 15:53:28.706353493 1 systemd-logind (575) > ioctl fd=24(/dev/tty3) 
request=4B45 argument=3 
24626343 15:53:58.336589416 0 systemd-logind (575) > ioctl fd=22(/dev/tty1) 
request=4B45 argument=3 
24804326 15:53:59.385872243 0 systemd-logind (575) > ioctl fd=21(/dev/tty1) 
request=4B45 argument=4 
25515114 15:54:12.915072995 1 systemd-logind (575) > ioctl fd=23(/dev/tty3) 
request=4B45 argument=4 
25520504 15:54:12.929480424 1 Xorg (25112) > ioctl fd=11(/dev/tty3) 
request=4B45 argument=4 
26921037 15:54:46.872029874 1 Xorg (25112) > ioctl fd=11(/dev/tty3) 
request=4B45 argument=4 
26921239 15:54:46.872654795 1 systemd-logind (575) > ioctl fd=24(/dev/tty3) 
request=4B45 argument=3 
27104852 15:54:53.870639078 1 systemd-logind (575) > ioctl fd=23(/dev/tty3) 
request=4B45 argument=4 
27112208 15:54:53.894217722 1 Xorg (25697) > ioctl fd=11(/dev/tty3) 
request=4B45 argument=4 
28677455 15:55:44.581119464 0 Xorg (25697) > ioctl fd=11(/dev/tty3) 
request=4B45 argument=4 
28678288 15:55:44.592966138 1 systemd-logind (575) > ioctl fd=24(/dev/tty3) 
request=4B45 argument=3 


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

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

Title:
  Password appears on the VT1 screen

Status in gdm3 package in Ubuntu:
  Confirmed
Status in plymouth package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  New

Bug description:
  (continued from bug 1767918)

  This was found when an administrative error made /home directory
  inaccessible.  Any users that tried to login after that, were not able
  to (which is expected) but their password appears on the VT1 screen.
  Under normal circumstances, VT1 is not visible. But once the system
  was sent into this compromised mode, one can press ctrl+alt+F1 and
  then ctrl+alt+F2 and get a momentary glance at VT1. One can keep
  toggling between these key combinations in order to make out the
  password(s) on VT1.

  As a further test, I wanted to see if a non-super user could cause
  this condition, and it is in fact possible. As a regular user, I made
  their own home directory not writable and then removed ~/.config and
  logged out. Then logged in as that user again, and although that user
  can't login the system does go into that mode where passwords appear
  on VT1 and are viewable with the key combinations mentioned herein.
  Further, any other users that login will see no problem, but when they
  logon their passwords also appear on VT1 and are viewable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.28.3-0ubuntu18.04.3
  Uname: Linux 4.19.2-041902-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Nov 19 08:32:59 2018
  InstallationDate: Installed on 2018-08-25 (85 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1803993/+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 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails

2019-04-24 Thread Sebastien Bacher
Could you provide some extra details on what you are doing exactly. Is the 
account reporting an error in the settings/online account panel? Or in 
evolution?
Where is "Error 7: Unexpected response from server" displayed?
What version of exchange/server are you using?

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

Title:
  Gnome Online Accounts fails to sign in Exchange emails

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 and/or on fresh install, a known-working
  Exchange email setup fails to sign in, giving "Error 7: Unexpected
  response from server".  Tested the same settings and credentials on a
  new install of 18.10 and it worked.

  I have Evolution and Evolution-ews installed on all instances, working
  in 18.10, not in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 16:38:32 2019
  InstallationDate: Installed on 2018-03-24 (391 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+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 1798313] Re: traceoute6 gives error sendto: Invalid argument

2019-04-24 Thread Aaron Dudek
Is there any plan to fix this bug in the 178.04 LTS version?

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

Title:
  traceoute6 gives error sendto: Invalid argument

Status in Iputils:
  Fix Released
Status in iputils package in Ubuntu:
  Confirmed
Status in iputils package in Debian:
  Fix Released

Bug description:
  When running the following command all get is an error. (traceroute6.db works)
  # traceroute6.iputils 2001:4860:4860::
  traceroute to 2001:4860:4860:: (2001:4860:4860::) from 
2a00:8780:3:42:b92a:b222:8bed:4a9b, 30 hops max, 24 byte packets
  sendto: Invalid argument
   1 traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *sendto: Invalid argument
  traceroute: wrote 2001:4860:4860:: 24 chars, ret=-1
   *

  This seems like a regression of Debian bug https://bugs.debian.org
  /cgi-bin/bugreport.cgi?bug=843264

  Package version installed:
  iputils-tracepath 3:20161105-1ubuntu2 amd64

  # lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu 18.04.1 LTS
  Release:  18.04
  Codename: bionic

To manage notifications about this bug go to:
https://bugs.launchpad.net/iputils/+bug/1798313/+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 1825591] Re: Ubuntu 18.04 LTS (WSL) fails to launch in Windows 10 1903

2019-04-24 Thread Jeb E.
** Also affects: systemd
   Importance: Undecided
   Status: New

** Also affects: wslu
   Importance: Undecided
   Status: New

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

Title:
  Ubuntu 18.04 LTS (WSL) fails to launch in Windows 10 1903

Status in systemd:
  New
Status in wslu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 LTS for WSL, official Microsoft Store package by
  Canonical, fails to open at all on Windows 10 May 2019 Feature Update.

  Link to issue in Microsoft Feedback Hub: https://aka.ms/AA4ubdp

To manage notifications about this bug go to:
https://bugs.launchpad.net/systemd/+bug/1825591/+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 1826056] Re: Desktop context: Keep aligned, Organize desktop by name missing in 19.04

2019-04-24 Thread Andrea Azzarone
** Package changed: tracker (Ubuntu) => gnome-shell-extension-desktop-
icons (Ubuntu)

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

Title:
  Desktop context: Keep aligned, Organize desktop by name missing in
  19.04

Status in gnome-shell-extension-desktop-icons package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 to 19.04 the desktop context menu no longer
  contains the choices:

  Keep aligned
  Organize desktop by name

  These were very useful to me. I would like them to be restored.

  Ubuntu 19.04, 64bit
  Gnome 3.32.1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1826056/+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 1825970] Re: "white noice" after resume from suspend

2019-04-24 Thread Stuardo -StR- Rodríguez
*** This bug is a duplicate of bug 1809407 ***
https://bugs.launchpad.net/bugs/1809407

confirmed as duplicate

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

Title:
  "white noice" after resume from suspend

Status in xorg package in Ubuntu:
  New

Bug description:
  As a user, after I open my laptop to resume using it after it
  suspended by closing it, the background and some parts of some windows
  have this "white noice" instead.

  I can get rid of it if I restart gnome (alt+f2 / r / enter) but it's
  still very annoying.

  I'm using the latest nvidia driver 418

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-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  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1)
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 04:02:14 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   anbox, 1, 5.0.0-13-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
   virtualbox, 6.0.6, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:054f]
   NVIDIA Corporation GK107M [GeForce GT 640M] [10de:0fd2] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GeForce GT 640M [1028:054f]
  InstallationDate: Installed on 2019-04-21 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: Dell Inc. XPS L521X
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=c42be4da-3229-4479-9793-032fb532c7e5 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/22/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 029M77
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A14
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/22/2013:svnDellInc.:pnXPSL521X:pvrA14:rvnDellInc.:rn029M77:rvrA00:cvnDellInc.:ct8:cvrA14:
  dmi.product.family: 103C_5335KV
  dmi.product.name: XPS L521X
  dmi.product.sku: XPS L521X
  dmi.product.version: A14
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1825970/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-04-24 Thread Balint Reczey
** Description changed:

  (console-setup)
  [Impact]
  
   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.
  
- [Workaround]
- 
- Reboot (or restart X) and the problem will go away.
- 
  [Test Case]
- 
- [racb] Note that upgrading to the fixed package will not fix the problem
- for affected users; you must reboot (or restart X) as above. The fix
- only prevents the problem occurring again.
  
   * Ssh to a system or open a terminal and unset DISPLAY
  
  $ echo $DISPLAY
  
  $
  
   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $
  
+On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode 
to observe the change:
+$  sudo kbd_mode -s -C /dev/tty1
+$ sudo kbd_mode -C /dev/tty1
+The keyboard is in raw (scancode) mode
+ 
   * Install or reinstall kbd-configuration
  
     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...
  
   * With the fixed package you should see the note above and the kbd mode
- must stay the same:
+ must stay the same (on Xenial check VT1: sudo kbd_mode -C /dev/tty1):
  
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $
  
   * The unfixed package sets the kbd mode to unicode:
  
     $  sudo kbd_mode
     The keyboard is in Unicode (UTF-8) mode
     $
  
  [Regression Potential]
  
   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.
  
  [Original Bug Text]
  WORKAROUND:
  
  sudo kbd_mode -s
  
  ORIGINAL DESCRIPTION:
  
  I'm running Ubuntu Lucid development branch.
  
  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.
  
  I'm pretty sure that my keyboard is not malfunctioning as I can use all
  my applications normally. (Pressing O and Ctrl-O do not have the same
  effect.)
  
  I'm not sure which package I should file this bug against. I'll happily
  do an apport-collect once I know.

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Committed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Committed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Committed
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

 On Xenial X runs on VT7 thus the graphical environment is not affected in 
the default configuration, but the keyboard-configuration postinst maintaner 
script still changes mode on vt1-6, thus at the beginning set VT1 to raw mode 
to observe the change:
 $  sudo kbd_mode -s -C /dev/tty1
 $ sudo kbd_mode -C /dev/tty1
 The keyboard is in raw (scancode) mode

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     

[Touch-packages] [Bug 1822270] Re: Debconf readline frontend does not show options

2019-04-24 Thread Heitor Alves de Siqueira
** Tags added: sts

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

Title:
  Debconf readline frontend does not show options

Status in debconf package in Ubuntu:
  Confirmed
Status in debconf source package in Xenial:
  Confirmed
Status in debconf source package in Bionic:
  Confirmed
Status in debconf source package in Cosmic:
  Confirmed
Status in debconf source package in Disco:
  Confirmed
Status in debconf source package in Eoan:
  Confirmed

Bug description:
  [Impact]
  debconf prompts the user for input before displaying options

  [Description]
  When upgrading packages with apt or dpkg, debconf scripts are ran through 
'run-parts' with the '--report' flag. This causes script output to be handled 
through pipes set up by run-parts, and buffers output from maintainer scripts 
nicely for formatting.

  If debconf makes use of the readline frontend, any prompts will bypass
  the run-parts buffers and be displayed directly to /dev/tty. This
  generally causes the prompt to be displayed before the user gets any
  of the available options for it, and printing will block until the
  user inputs a valid option.

  [Test Case]
  1) Deploy a VM through e.g. uvt-kvm
  $ uvt-kvm create disco release=disco

  2) Remove the whiptail package to force the readline frontend in debconf
  root@disco:~# apt remove --purge whiptail -y

  3) Install grub-legacy-ec2 and prepare /boot/grub/menu.lst for an upgrade 
through run-parts
  root@disco:~# apt update && apt install -y grub-legacy-ec2
  root@disco:~# rm -f /boot/grub/menu.lst*
  root@disco:~# touch -d "4 years ago" /boot/grub/menu.lst

  4) Invoke run-parts as in a kernel upgrade (kernel version doesn't matter, we 
just need it to think menu.lst needs an upgrade)
  root@disco:~# run-parts --exit-on-error --arg=5.0.0 /etc/kernel/postinst.d 
--report
  ...
  /etc/kernel/postinst.d/x-grub-legacy-ec2:
  debconf: unable to initialize frontend: Dialog
  debconf: (No usable dialog-like program is installed, so the dialog based 
frontend cannot be used. at /usr/share/perl5/Debconf/FrontEnd/Dialog.pm line 
76.)
  debconf: falling back to frontend: Readline
  Searching for GRUB installation directory ... found: /boot/grub
  Searching for default file ... found: /boot/grub/default
  Testing for an existing GRUB menu.lst file ... found: /boot/grub/menu.lst
  Searching for splash image ... none found, skipping ...
  What would you like to do about menu.lst? 

  The "What would you like to do about menu.lst?" prompt will block
  until the user enter a valid option, even though it's being displayed
  before the available options.

  [Regression Potential]
  We could hit regressions if changing debconf's printing to /dev/tty is 
expected by other programs. The changes are needed only in the readline 
frontend, so that would minimize impact of any possible regressions. The fixes 
will be thoroughly tested with autopkgtest and use-case scenarios.

  # # # #

  [Original Description]
  When upgrading the kernel on a recent Bionic minimal image, the user is 
prompted to resolve a conflict in the file /boot/grub/menu.lst.

  The minimal images do not have dialog/whiptail installed, so debconf
  falls back to using the readline frontend.

  The user sees the prompt: "What would you like to do about menu.lst?"
  but is not presented with the list of options to choose from.

  If a valid option is typed in, debconf will continue processing
  correctly and the list of options  appears on the screen. See also
  https://pastebin.ubuntu.com/p/8xvSn88SKG/

  STEPS TO REPRODUCE:

  Launch the minimal Bionic image with serial 20190212 http://cloud-
  images.ubuntu.com/minimal/releases/bionic/release-20190212/ubuntu-18.04
  -minimal-cloudimg-amd64.img

  for example via multipass and run `apt-get update` and `apt-get dist-
  upgrade`.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1822270/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-04-24 Thread Balint Reczey
Xorg and the kernel are doing the right thing here.

** No longer affects: linux (Ubuntu)

** Changed in: xorg-server (Ubuntu Bionic)
   Status: Confirmed => Invalid

** Changed in: xorg-server (Ubuntu Cosmic)
   Status: Confirmed => Invalid

** Changed in: xorg-server (Ubuntu Disco)
   Status: Confirmed => Invalid

** Changed in: xorg-server (Ubuntu Eoan)
   Status: Confirmed => Invalid

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Committed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Committed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Committed
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Workaround]

  Reboot (or restart X) and the problem will go away.

  [Test Case]

  [racb] Note that upgrading to the fixed package will not fix the
  problem for affected users; you must reboot (or restart X) as above.
  The fix only prevents the problem occurring again.

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same:

     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * The unfixed package sets the kbd mode to unicode:

     $  sudo kbd_mode
     The keyboard is in Unicode (UTF-8) mode
     $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1826183] Re: /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-upgrade@2268:main:run:get_auto_removable::__iter__:keys:

2019-04-24 Thread Balint Reczey
There are many corruptions reported at
https://errors.ubuntu.com/?package=unattended-upgrades=week=1.10ubuntu5
:-(

On Wed, Apr 24, 2019 at 1:01 PM Julian Andres Klode
 wrote:
>
> Probably a memory corruption somewhere, but this would need some deep
> digging.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1826183
>
> Title:
>   /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-
>   upgrade@2268:main:run:get_auto_removable::__iter__:keys:
>
> Status in python-apt package in Ubuntu:
>   New
>
> Bug description:
>   The Ubuntu Error Tracker has been receiving reports about a problem 
> regarding unattended-upgrades.  This problem was most recently seen with 
> package version 1.10ubuntu5, the problem page at 
> https://errors.ubuntu.com/problem/e0067211bd138f2644f4d2a86a6337280970ebe0 
> contains more details, including versions of packages affected, stacktrace or 
> traceback, and individual crash reports.
>   If you do not have access to the Ubuntu Error Tracker and are a software 
> developer, you can request it at http://forms.canonical.com/reports/.
>
>   Traceback (most recent call last):
> File "/usr/bin/unattended-upgrade", line 2268, in 
>   sys.exit(main(options))
> File "/usr/bin/unattended-upgrade", line 1732, in main
>   install_start_time)
> File "/usr/bin/unattended-upgrade", line 1906, in run
>   auto_removable = get_auto_removable(cache)
> File "/usr/bin/unattended-upgrade", line 1557, in get_auto_removable
>   return {pkg.name for pkg in cache
> File "/usr/bin/unattended-upgrade", line 1557, in 
>   return {pkg.name for pkg in cache
> File "/usr/lib/python3/dist-packages/apt/cache.py", line 333, in __iter__
>   for pkgname in self.keys():
> File "/usr/lib/python3/dist-packages/apt/cache.py", line 361, in keys
>   for p in self._cache.packages
> File "/usr/lib/python3/dist-packages/apt/cache.py", line 362, in 
>   if self.__is_real_pkg(p))
>   UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 16: 
> invalid continuation byte
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826183/+subscriptions


-- 
Balint Reczey
Ubuntu & Debian Developer

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

Title:
  /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-
  upgrade@2268:main:run:get_auto_removable::__iter__:keys:

Status in python-apt package in Ubuntu:
  New

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

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2268, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1732, in main
  install_start_time)
File "/usr/bin/unattended-upgrade", line 1906, in run
  auto_removable = get_auto_removable(cache)
File "/usr/bin/unattended-upgrade", line 1557, in get_auto_removable
  return {pkg.name for pkg in cache
File "/usr/bin/unattended-upgrade", line 1557, in 
  return {pkg.name for pkg in cache
File "/usr/lib/python3/dist-packages/apt/cache.py", line 333, in __iter__
  for pkgname in self.keys():
File "/usr/lib/python3/dist-packages/apt/cache.py", line 361, in keys
  for p in self._cache.packages
File "/usr/lib/python3/dist-packages/apt/cache.py", line 362, in 
  if self.__is_real_pkg(p))
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 16: 
invalid continuation byte

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826183/+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 520546] Please test proposed package

2019-04-24 Thread Robie Basak
Hello David, or anyone else affected,

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

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

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

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

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Committed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Committed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Committed
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Workaround]

  Reboot (or restart X) and the problem will go away.

  [Test Case]

  [racb] Note that upgrading to the fixed package will not fix the
  problem for affected users; you must reboot (or restart X) as above.
  The fix only prevents the problem occurring again.

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same:

     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * The unfixed package sets the kbd mode to unicode:

     $  sudo kbd_mode
     The keyboard is in Unicode (UTF-8) mode
     $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 520546] Please test proposed package

2019-04-24 Thread Robie Basak
Hello David, or anyone else affected,

Accepted console-setup into cosmic-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu9.2 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-cosmic to verification-done-cosmic. If it does not
fix the bug for you, please add a comment stating that, and change the
tag to verification-failed-cosmic. In either case, details of your
testing will help us make a better decision.

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

** Changed in: console-setup (Ubuntu Bionic)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Committed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Committed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Committed
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Workaround]

  Reboot (or restart X) and the problem will go away.

  [Test Case]

  [racb] Note that upgrading to the fixed package will not fix the
  problem for affected users; you must reboot (or restart X) as above.
  The fix only prevents the problem occurring again.

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same:

     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * The unfixed package sets the kbd mode to unicode:

     $  sudo kbd_mode
     The keyboard is in Unicode (UTF-8) mode
     $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 520546] Please test proposed package

2019-04-24 Thread Robie Basak
Hello David, or anyone else affected,

Accepted console-setup into disco-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/console-
setup/1.178ubuntu12.1 in a few hours, and then in the -proposed
repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-disco to verification-done-disco. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-disco. In either case, details of your testing
will help us make a better decision.

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

** Changed in: console-setup (Ubuntu Cosmic)
   Status: Confirmed => Fix Committed

** Tags added: verification-needed-cosmic

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Committed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Committed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Committed
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Workaround]

  Reboot (or restart X) and the problem will go away.

  [Test Case]

  [racb] Note that upgrading to the fixed package will not fix the
  problem for affected users; you must reboot (or restart X) as above.
  The fix only prevents the problem occurring again.

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY

  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
     $ sudo kbd_mode
     The keyboard is in some unknown mode
     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * Install or reinstall kbd-configuration

     $ sudo apt install --reinstall keyboard-configuration
     ...
     Setting up keyboard-configuration (1.178ubuntu11) ...
     Your console font configuration will be updated the next time your system
     boots. If you want to update it now, run 'setupcon' from a virtual console.
     ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same:

     $ sudo kbd_mode
     The keyboard is in raw (scancode) mode
     $

   * The unfixed package sets the kbd mode to unicode:

     $  sudo kbd_mode
     The keyboard is in Unicode (UTF-8) mode
     $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

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

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

[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-04-24 Thread Robie Basak
Accepting the fix into stable releases. Note that the fix only prevents
new breakages; existing affected users will not be unbroken without
rebooting (or rebooting X).

** Description changed:

- 
  (console-setup)
  [Impact]
  
-  * keyboard-configuration's postinst changes keyboard mode breaking X
+  * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.
+ 
+ [Workaround]
+ 
+ Reboot (or restart X) and the problem will go away.
  
  [Test Case]
  
-  * Ssh to a system or open a terminal and unset DISPLAY
+ [racb] Note that upgrading to the fixed package will not fix the problem
+ for affected users; you must reboot (or restart X) as above. The fix
+ only prevents the problem occurring again.
  
- $ echo $DISPLAY
- 
- $
+  * Ssh to a system or open a terminal and unset DISPLAY
  
-  * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
-$ sudo kbd_mode
-The keyboard is in some unknown mode
-$ sudo kbd_mode
-The keyboard is in raw (scancode) mode
-$
+ $ echo $DISPLAY
  
-  * Install or reinstall kbd-configuration
+ $
  
-$ sudo apt install --reinstall keyboard-configuration 
-...
-Setting up keyboard-configuration (1.178ubuntu11) ...
-Your console font configuration will be updated the next time your system
-boots. If you want to update it now, run 'setupcon' from a virtual console.
-...
+  * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
+    $ sudo kbd_mode
+    The keyboard is in some unknown mode
+    $ sudo kbd_mode
+    The keyboard is in raw (scancode) mode
+    $
  
-  * With the fixed package you should see the note above and the kbd mode
+  * Install or reinstall kbd-configuration
+ 
+    $ sudo apt install --reinstall keyboard-configuration
+    ...
+    Setting up keyboard-configuration (1.178ubuntu11) ...
+    Your console font configuration will be updated the next time your system
+    boots. If you want to update it now, run 'setupcon' from a virtual console.
+    ...
+ 
+  * With the fixed package you should see the note above and the kbd mode
  must stay the same:
  
-$ sudo kbd_mode
-The keyboard is in raw (scancode) mode
-$
+    $ sudo kbd_mode
+    The keyboard is in raw (scancode) mode
+    $
  
-  * The unfixed package sets the kbd mode to unicode:
+  * The unfixed package sets the kbd mode to unicode:
  
-$  sudo kbd_mode
-The keyboard is in Unicode (UTF-8) mode
-$
+    $  sudo kbd_mode
+    The keyboard is in Unicode (UTF-8) mode
+    $
  
  [Regression Potential]
  
-  * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
-  * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.
+  * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
+  * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.
  
  [Original Bug Text]
  WORKAROUND:
  
  sudo kbd_mode -s
  
  ORIGINAL DESCRIPTION:
  
  I'm running Ubuntu Lucid development branch.
  
  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.
  
  I'm pretty sure that my keyboard is not malfunctioning as I can use all
  my applications normally. (Pressing O and Ctrl-O do not have the same
  effect.)
  
  I'm not sure which package I should file this bug against. I'll happily
  do an apport-collect once I know.

** Changed in: console-setup (Ubuntu Disco)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-disco

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Bionic:
  Fix Committed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Committed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Committed
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Invalid
Status in 

[Touch-packages] [Bug 1826183] Re: /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-upgrade@2268:main:run:get_auto_removable::__iter__:keys:

2019-04-24 Thread Julian Andres Klode
Probably a memory corruption somewhere, but this would need some deep
digging.

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

Title:
  /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-
  upgrade@2268:main:run:get_auto_removable::__iter__:keys:

Status in python-apt package in Ubuntu:
  New

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

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2268, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1732, in main
  install_start_time)
File "/usr/bin/unattended-upgrade", line 1906, in run
  auto_removable = get_auto_removable(cache)
File "/usr/bin/unattended-upgrade", line 1557, in get_auto_removable
  return {pkg.name for pkg in cache
File "/usr/bin/unattended-upgrade", line 1557, in 
  return {pkg.name for pkg in cache
File "/usr/lib/python3/dist-packages/apt/cache.py", line 333, in __iter__
  for pkgname in self.keys():
File "/usr/lib/python3/dist-packages/apt/cache.py", line 361, in keys
  for p in self._cache.packages
File "/usr/lib/python3/dist-packages/apt/cache.py", line 362, in 
  if self.__is_real_pkg(p))
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 16: 
invalid continuation byte

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826183/+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 1826183] Re: /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-upgrade@2268:main:run:get_auto_removable::__iter__:keys:

2019-04-24 Thread Julian Andres Klode
Crazy, who has invalid unicode in package names?

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

Title:
  /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-
  upgrade@2268:main:run:get_auto_removable::__iter__:keys:

Status in python-apt package in Ubuntu:
  New

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

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2268, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1732, in main
  install_start_time)
File "/usr/bin/unattended-upgrade", line 1906, in run
  auto_removable = get_auto_removable(cache)
File "/usr/bin/unattended-upgrade", line 1557, in get_auto_removable
  return {pkg.name for pkg in cache
File "/usr/bin/unattended-upgrade", line 1557, in 
  return {pkg.name for pkg in cache
File "/usr/lib/python3/dist-packages/apt/cache.py", line 333, in __iter__
  for pkgname in self.keys():
File "/usr/lib/python3/dist-packages/apt/cache.py", line 361, in keys
  for p in self._cache.packages
File "/usr/lib/python3/dist-packages/apt/cache.py", line 362, in 
  if self.__is_real_pkg(p))
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 16: 
invalid continuation byte

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826183/+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 1796911] Re: libnss-systemd was denied talking to pid1

2019-04-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  libnss-systemd was denied talking to pid1

Status in apparmor package in Ubuntu:
  Confirmed

Bug description:
  cosmic
  apparmor 2.12-4ubuntu8
  kernel 4.18.0-8-generic #9-Ubuntu 

  I'm getting these audit messages in dmesg showing apparmor denied errors:
  [   68.649187] audit: type=1107 audit(1539094926.655:32): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1091 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  161.059989] audit: type=1107 audit(1539095018.957:33): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1191 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  437.582034] audit: type=1107 audit(1539095295.553:34): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1534 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'
  [  468.184231] audit: type=1107 audit(1539095326.159:35): pid=605 uid=105 
auid=4294967295 ses=4294967295 subj==unconfined msg='apparmor="DENIED" 
operation="dbus_method_call"  bus="system" path="/org/freedesktop/systemd1" 
interface="org.freedesktop.systemd1.Manager" member="GetDynamicUsers" 
mask="send" name="org.freedesktop.systemd1" pid=1577 label="/usr/sbin/named" 
peer_pid=1 peer_label="unconfined"
  exe="/usr/bin/dbus-daemon" sauid=105 hostname=? addr=? 
terminal=?'

  I pinged #ubuntu-hardened, and xnox had these comments:
   ha
   ahasenack, libnss-systemd was denied talking to pid1
   to query dynamicusers i think
   so i think something somehwere need adjustemnt to allow libnss-systemd 
to talk to pid1 and call GetDynamicUsers
   LookupDynamicUserByName LookupDynamicUserByUID GetDynamicUsers
   as well

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1796911/+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 1826183] [NEW] /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-upgrade@2268:main:run:get_auto_removable::__iter__:keys:

2019-04-24 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 2268, in 
sys.exit(main(options))
  File "/usr/bin/unattended-upgrade", line 1732, in main
install_start_time)
  File "/usr/bin/unattended-upgrade", line 1906, in run
auto_removable = get_auto_removable(cache)
  File "/usr/bin/unattended-upgrade", line 1557, in get_auto_removable
return {pkg.name for pkg in cache
  File "/usr/bin/unattended-upgrade", line 1557, in 
return {pkg.name for pkg in cache
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 333, in __iter__
for pkgname in self.keys():
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 361, in keys
for p in self._cache.packages
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 362, in 
if self.__is_real_pkg(p))
UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 16: 
invalid continuation byte

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


** Tags: disco

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

Title:
  /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-
  upgrade@2268:main:run:get_auto_removable::__iter__:keys:

Status in python-apt package in Ubuntu:
  New

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

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2268, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1732, in main
  install_start_time)
File "/usr/bin/unattended-upgrade", line 1906, in run
  auto_removable = get_auto_removable(cache)
File "/usr/bin/unattended-upgrade", line 1557, in get_auto_removable
  return {pkg.name for pkg in cache
File "/usr/bin/unattended-upgrade", line 1557, in 
  return {pkg.name for pkg in cache
File "/usr/lib/python3/dist-packages/apt/cache.py", line 333, in __iter__
  for pkgname in self.keys():
File "/usr/lib/python3/dist-packages/apt/cache.py", line 361, in keys
  for p in self._cache.packages
File "/usr/lib/python3/dist-packages/apt/cache.py", line 362, in 
  if self.__is_real_pkg(p))
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 16: 
invalid continuation byte

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826183/+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 1826183] Re: /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-upgrade@2268:main:run:get_auto_removable::__iter__:keys:

2019-04-24 Thread Balint Reczey
** Package changed: unattended-upgrades (Ubuntu) => python-apt (Ubuntu)

** Description changed:

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
unattended-upgrades.  This problem was most recently seen with package version 
1.10ubuntu5, the problem page at 
https://errors.ubuntu.com/problem/e0067211bd138f2644f4d2a86a6337280970ebe0 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker and are a software 
developer, you can request it at http://forms.canonical.com/reports/.
+ 
+ Traceback (most recent call last):
+   File "/usr/bin/unattended-upgrade", line 2268, in 
+ sys.exit(main(options))
+   File "/usr/bin/unattended-upgrade", line 1732, in main
+ install_start_time)
+   File "/usr/bin/unattended-upgrade", line 1906, in run
+ auto_removable = get_auto_removable(cache)
+   File "/usr/bin/unattended-upgrade", line 1557, in get_auto_removable
+ return {pkg.name for pkg in cache
+   File "/usr/bin/unattended-upgrade", line 1557, in 
+ return {pkg.name for pkg in cache
+   File "/usr/lib/python3/dist-packages/apt/cache.py", line 333, in __iter__
+ for pkgname in self.keys():
+   File "/usr/lib/python3/dist-packages/apt/cache.py", line 361, in keys
+ for p in self._cache.packages
+   File "/usr/lib/python3/dist-packages/apt/cache.py", line 362, in 
+ if self.__is_real_pkg(p))
+ UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 16: 
invalid continuation byte

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

Title:
  /usr/bin/unattended-upgrade:UnicodeDecodeError:/usr/bin/unattended-
  upgrade@2268:main:run:get_auto_removable::__iter__:keys:

Status in python-apt package in Ubuntu:
  New

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

  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 2268, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1732, in main
  install_start_time)
File "/usr/bin/unattended-upgrade", line 1906, in run
  auto_removable = get_auto_removable(cache)
File "/usr/bin/unattended-upgrade", line 1557, in get_auto_removable
  return {pkg.name for pkg in cache
File "/usr/bin/unattended-upgrade", line 1557, in 
  return {pkg.name for pkg in cache
File "/usr/lib/python3/dist-packages/apt/cache.py", line 333, in __iter__
  for pkgname in self.keys():
File "/usr/lib/python3/dist-packages/apt/cache.py", line 361, in keys
  for p in self._cache.packages
File "/usr/lib/python3/dist-packages/apt/cache.py", line 362, in 
  if self.__is_real_pkg(p))
  UnicodeDecodeError: 'utf-8' codec can't decode byte 0xe4 in position 16: 
invalid continuation byte

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1826183/+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 1824724] Re: aa-logprof: german translation: ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen

2019-04-24 Thread Christian Boltz
> id appears to be the only one to pick different letters.

For the records: changing the hotkeys is allowed, but you have to make
sure that you don't cause hotkey conflicts. To be sure, run the updated
translation through the AppArmor utils tests - or ask me to run these
tests ;-)

> and if it's considered important enough

Currently aa-logprof (and likely also aa-genprof and aa-mergeprof) are
completely broken by these translations - IMHO that qualifies as
"important enough" ;-)

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

Title:
  aa-logprof: german translation: ERROR: PromptUser: Ungültiges
  Tastenkürzel für V: Änderungen ansehen

Status in AppArmor:
  New
Status in Ubuntu Translations:
  New
Status in language-pack-de package in Ubuntu:
  New
Status in language-pack-de-base package in Ubuntu:
  New

Bug description:
  after the last Erl(a)uben [Allow] theres an errormessage:
  "ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen"
  see here:

  Profil:  /usr/bin/snap
  Pfad:/sys/kernel/security/apparmor/features/policy/versions/v5
  Neuer Modus: r
  Schweregrad: 4

   [1 - /sys/kernel/security/apparmor/features/policy/versions/v5 r,]
  Erl(a)uben / [A(b)lehnen] / (I)gnorieren / (G)lob / Glob with (E)xtension / 
(N)eu / Audi(t) / Abb(r)echen / En(d)e
  /sys/kernel/security/apparmor/features/policy/versions/v5 r, wird zum Profil 
hinzugefügt.

  ERROR: PromptUser: Ungültiges Tastenkürzel für V: Änderungen ansehen
  [view changes]

  imho it's a translation error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1824724/+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 1825590] Re: "software & updates" freezes after selecting "canonical partners¨

2019-04-24 Thread Sebastien Bacher
looks like bug #1734095 then (though the other one describe the auth
failing but no locking)

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

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => New

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

Title:
  "software & updates" freezes after selecting "canonical partners¨

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  On a fresh install of 19.04, in "Software & Updates" when I select
  "Canonical Partners" the window "Authentication Required" pops up.
  After typing the password the mouse freezes, and can be unfrozen with
  CTRL+ALT+DEL. But the "Canonical Partners" cannot be selected, check
  box stays empty, mouse freezes again. Even after cold restart.

  WORKAROUND
  Select "Canonical Partners Sources" instead. After authorizing I can now also 
select "Canonical Partners". This was impossible before.

  After this I can select and deselect Canonical Partner in "Software & 
Updates".
  The previous authorization window, which opened first, and when the mouse 
froze, stays open and cannot be closed with CANCEL or ALT+F4.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: software-properties-gtk 0.97.11
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 20 00:17:33 2019
  ExecutablePath: /usr/bin/software-properties-gtk
  InstallationDate: Installed on 2019-04-19 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  InterpreterPath: /usr/bin/python3.7
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: N/A
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1825590/+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 1825580] Re: Gnome Online Accounts fails to sign in Exchange emails

2019-04-24 Thread Sebastien Bacher
thanks

** Changed in: gnome-online-accounts (Ubuntu)
   Status: Incomplete => New

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

Title:
  Gnome Online Accounts fails to sign in Exchange emails

Status in gnome-online-accounts package in Ubuntu:
  New

Bug description:
  After upgrading from 18.10 and/or on fresh install, a known-working
  Exchange email setup fails to sign in, giving "Error 7: Unexpected
  response from server".  Tested the same settings and credentials on a
  new install of 18.10 and it worked.

  I have Evolution and Evolution-ews installed on all instances, working
  in 18.10, not in 19.04.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gnome-online-accounts 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 19 16:38:32 2019
  InstallationDate: Installed on 2018-03-24 (391 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180208)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to disco on 2019-03-12 (38 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1825580/+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 1825886] Re: /usr/bin/unattended-upgrade:AttributeError:/usr/bin/unattended-upgrade@2268:main:run:calculate_upgradable_pkgs:try_to_upgrade:mark_upgrade_adjusted:call_adjusted:tra

2019-04-24 Thread Balint Reczey
https://github.com/mvo5/unattended-upgrades/pull/194

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

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

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => In Progress

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

Title:
  /usr/bin/unattended-upgrade:AttributeError:/usr/bin/unattended-
  
upgrade@2268:main:run:calculate_upgradable_pkgs:try_to_upgrade:mark_upgrade_adjusted:call_adjusted:transitive_dependencies:transitive_dependencies

Status in unattended-upgrades package in Ubuntu:
  In Progress
Status in unattended-upgrades source package in Bionic:
  New
Status in unattended-upgrades source package in Cosmic:
  New
Status in unattended-upgrades source package in Disco:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1825886/+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 1826157] [NEW] /usr/bin/unattended-upgrade:apt_pkg.Error:try_to_upgrade:rewind_cache:mark_install:/usr/bin/unattended-upgrade@2268:main:run:calculate_upgradable_pkgs:try_to_upgra

2019-04-24 Thread errors.ubuntu.com bug bridge
Public bug reported:

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

** Affects: unattended-upgrades (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: disco

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

Title:
  /usr/bin/unattended-
  upgrade:apt_pkg.Error:try_to_upgrade:rewind_cache:mark_install:/usr/bin
  /unattended-
  
upgrade@2268:main:run:calculate_upgradable_pkgs:try_to_upgrade:rewind_cache:mark_install

Status in unattended-upgrades package in Ubuntu:
  New

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1826157/+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 1824998] Re: Zanata is messing up the translations

2019-04-24 Thread Rodrigo Lledó
I consider this problem solved as the problem was notified to Lubomir
Rintel. He said he will be more careful in the future.

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

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

Title:
  Zanata is messing up the translations

Status in NetworkManager:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  Hi

  Today is actually impossible to keep NM translations in good shape
  since Zanata (a tool used in Fedora and Red Hat) is messing up the
  translations.

  Example:

  https://translations.launchpad.net/ubuntu/disco/+source/network-
  manager/+pots/networkmanager/es/870/+translate

  Which literally means:
  One of the functions of the swimming boat (3) is a function of the boat's 
control unit.

  Or translating "master" as "dominate"

  This is hilarous but also frustrating.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1824998/+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 1824753] Re: When I pass the Qt application to the secondary monitor the characters of the application increase

2019-04-24 Thread Patrick
I don't know if it's the GNOME 3.30 to 3.32 update or the Qt update. I
know it happens with other distros because I tried Manjaro Gnome and it
also suffers this bug. I left a message in the forums with another video
https://forum.manjaro.org/t/gnome-two-monitors-and-qt-problems/83075

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

Title:
  When I pass the Qt application to the secondary monitor the characters
  of the application increase

Status in qtbase-opensource-src package in Ubuntu:
  New
Status in vlc package in Ubuntu:
  Invalid

Bug description:
  Hi. I have recently installed Ubuntu 19.04 RC. Everything works fine except 
the Qt applications. I have two monitors and when I pass the Qt application to 
the secondary monitor the characters of the application increase. They happen 
to the traditionally installed Qt applications and to those installed with 
Flatpak and Snap. I leave you a video in which you can see the problem with the 
VLC application.
  https://youtu.be/tEZJONsinU4
  https://i.imgur.com/R7GubxF.png?fb
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2019-04-14 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190413.2)
  NonfreeKernelModules: nvidia_modeset nvidia
  Package: mutter 3.32.0+git20190410-1ubuntu1
  PackageArchitecture: amd64
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcVersionSignature: Ubuntu 5.0.0-11.12-generic 5.0.6
  Tags:  disco
  Uname: Linux 5.0.0-11-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1824753/+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 1826151] [NEW] Can someone help me out and explain or point me in the right direction on how to check video drivers and see if my video card running okay

2019-04-24 Thread djennane
Public bug reported:

Can someone help me out and explain or point me in the right direction
on how to check video drivers and see if my video card running okay

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-18-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Apr 24 09:56:02 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3675]
 NVIDIA Corporation GK107M [GeForce GT 745M] [10de:0fe3] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Lenovo GeForce GT 745A [17aa:3675]
InstallationDate: Installed on 2019-04-24 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
MachineType: LENOVO 10123
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/18/2013
dmi.bios.vendor: LENOVO
dmi.bios.version: I8KT15AUS
dmi.board.name: SHARKBAY
dmi.board.vendor: LENOVO
dmi.board.version: 3194 STD
dmi.chassis.type: 13
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnLENOVO:bvrI8KT15AUS:bd04/18/2013:svnLENOVO:pn10123:pvrIdeaCentreA730:rvnLENOVO:rnSHARKBAY:rvr3194STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
dmi.product.family: IdeaCentre
dmi.product.name: 10123
dmi.product.sku: LENOVO_MT_1012
dmi.product.version: IdeaCentre A730
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
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: 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/1826151

Title:
  Can someone help me out and explain or point me in the right direction
  on how to check video drivers and see if my video card running okay

Status in xorg package in Ubuntu:
  New

Bug description:
  Can someone help me out and explain or point me in the right direction
  on how to check video drivers and see if my video card running okay

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-18.19~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-18-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Apr 24 09:56:02 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller 
[17aa:3675]
   NVIDIA Corporation GK107M [GeForce GT 745M] [10de:0fe3] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GeForce GT 745A [17aa:3675]
  InstallationDate: Installed on 2019-04-24 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  MachineType: LENOVO 10123
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.18.0-18-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/18/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: I8KT15AUS
  dmi.board.name: SHARKBAY
  dmi.board.vendor: LENOVO
  dmi.board.version: 3194 STD
  dmi.chassis.type: 13
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnLENOVO:bvrI8KT15AUS:bd04/18/2013:svnLENOVO:pn10123:pvrIdeaCentreA730:rvnLENOVO:rnSHARKBAY:rvr3194STD:cvnToBeFilledByO.E.M.:ct13:cvrToBeFilledByO.E.M.:
  dmi.product.family: IdeaCentre
  

[Touch-packages] [Bug 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)

2019-04-24 Thread Paul van Tilburg
This fix caused a regression in our Dracut-based boot setup.
Since this patch was incorporated (237-3ubuntu10.17), some of several of the 
(PC-type) models we provide to our customers that tend to have "slow I/O", no 
longer boot because Dracut times out waiting for the root file system to come 
online because the systemd-crypt@ service can no longer be started.
We are currently using a build of this source package that doesn't include this 
patch to fix this temporarily.

I have filed a bug eport at Systemd's GitHub too, this contains more 
information:
https://github.com/systemd/systemd/issues/12371.

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

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

Title:
  Please backport "fix race between daemon-reload and other commands
  #8803" to 16.04 (for UC16) and 18.04 (for UC18)

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Released
Status in systemd source package in Bionic:
  Fix Released

Bug description:
  [Impact]
  On Ubuntu Core we recently hit the a race in daemon-reload and systemctl 
twice. This race is fixed in systemd upstream: "fix race between daemon-reload 
and other commands #8803" and a subsequent fix in "PR#11121".

  Note that this is a general problem in systemd with daemon-reload and
  systemctl commands, we just happen to hit it more often on Ubuntu Core
  but the test-case below explodes just fine on a normal Ubuntu release
  like 16.04 or 18.04 (not on 18.10+ as its fixed there).

  [TEST CASE]
  To reproduce its enough to run:

  for i in $(seq 50); do
    systemctl daemon-reload &
    systemctl start ssh &
  done

  This will result in "systemctl start ssh" hanging in ppoll. With the
  patch applied the hangs go away.

  [REGRESSION POTENTIAL]
  Medium/High, this change is already in the systemd upstream and in use disco 
and later but the backport required some manual resolving of conflicts the code 
because changed between 229,237 and the fixed code in 240. Its also
  not fully clear if the fix relies on the new systemd "coldplug" functionality 
that was added in more recent git revisions.

  The upstream fix is https://github.com/systemd/systemd/pull/8803 and
  https://github.com/systemd/systemd/pull/11121

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

2019-04-24 Thread Tony den Haan
Updated Ubuntu-18.04 LTS, rebooted and problem is gone.

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in console-setup source package in Bionic:
  Confirmed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Confirmed
Status in console-setup source package in Cosmic:
  Confirmed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Confirmed
Status in console-setup source package in Disco:
  In Progress
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Confirmed
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Confirmed

Bug description:
  
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY
  
  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
 $ sudo kbd_mode
 The keyboard is in some unknown mode
 $ sudo kbd_mode
 The keyboard is in raw (scancode) mode
 $

   * Install or reinstall kbd-configuration

 $ sudo apt install --reinstall keyboard-configuration 
 ...
 Setting up keyboard-configuration (1.178ubuntu11) ...
 Your console font configuration will be updated the next time your system
 boots. If you want to update it now, run 'setupcon' from a virtual console.
 ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same:

 $ sudo kbd_mode
 The keyboard is in raw (scancode) mode
 $

   * The unfixed package sets the kbd mode to unicode:

 $  sudo kbd_mode
 The keyboard is in Unicode (UTF-8) mode
 $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1821863] Re: Need to add Intel CML related pci-id's

2019-04-24 Thread Launchpad Bug Tracker
This bug was fixed in the package linux-oem - 4.15.0-1036.41

---
linux-oem (4.15.0-1036.41) bionic; urgency=medium

  * linux-oem: 4.15.0-1036.41 -proposed tracker (LP: #1822803)

  * Need to add Intel CML related pci-id's (LP: #1821863)
- drm/i915/cml: Introduce Comet Lake PCH
- drm/i915/cml: Add CML PCI IDS

  * [SRU] [B/OEM] Fix ACPI bug that causes boot failure (LP: #1819921)
- SAUCE: ACPI / bus: Add some Lenovo laptops in list of acpi table term list

  * Miscellaneous Ubuntu changes
- [Config] update configs following rebase to 4.15.0-48.51

  [ Ubuntu: 4.15.0-48.51 ]

  * linux: 4.15.0-48.51 -proposed tracker (LP: #1822820)
  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction
  * 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes
triggers system hang on i386 (LP: #1812845)
- btrfs: raid56: properly unmap parity page in finish_parity_scrub()
  * [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats
(LP: #1719545)
- cpupower : Fix header name to read idle state name
  * [amdgpu] screen corruption when using touchpad (LP: #1818617)
- drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
- drm/amdgpu: Free VGA stolen memory as soon as possible.
  * [SRU][B/C/OEM]IOMMU: add kernel dma protection (LP: #1820153)
- ACPICA: AML parser: attempt to continue loading table after error
- ACPI / property: Allow multiple property compatible _DSD entries
- PCI / ACPI: Identify untrusted PCI devices
- iommu/vt-d: Force IOMMU on for platform opt in hint
- iommu/vt-d: Do not enable ATS for untrusted devices
- thunderbolt: Export IOMMU based DMA protection support to userspace
- iommu/vt-d: Disable ATS support on untrusted devices
  * Add basic support to NVLink2 passthrough (LP: #1819989)
- powerpc/powernv/npu: Do not try invalidating 32bit table when 64bit table 
is
  enabled
- powerpc/powernv: call OPAL_QUIESCE before OPAL_SIGNAL_SYSTEM_RESET
- powerpc/powernv: Export opal_check_token symbol
- powerpc/powernv: Make possible for user to force a full ipl cec reboot
- powerpc/powernv/idoa: Remove unnecessary pcidev from pci_dn
- powerpc/powernv: Move npu struct from pnv_phb to pci_controller
- powerpc/powernv/npu: Move OPAL calls away from context manipulation
- powerpc/pseries/iommu: Use memory@ nodes in max RAM address calculation
- powerpc/pseries/npu: Enable platform support
- powerpc/pseries: Remove IOMMU API support for non-LPAR systems
- powerpc/powernv/npu: Check mmio_atsd array bounds when populating
- powerpc/powernv/npu: Fault user page into the hypervisor's pagetable
  * Huawei Hi1822 NIC has poor performance (LP: #1820187)
- net-next: hinic: fix a problem in free_tx_poll()
- hinic: remove ndo_poll_controller
- net-next/hinic: add checksum offload and TSO support
- hinic: Fix l4_type parameter in hinic_task_set_tunnel_l4
- net-next/hinic:replace multiply and division operators
- net-next/hinic:add rx checksum offload for HiNIC
- net-next/hinic:fix a bug in set mac address
- net-next/hinic: fix a bug in rx data flow
- net: hinic: fix null pointer dereference on pointer hwdev
- hinic: optmize rx refill buffer mechanism
- net-next/hinic:add shutdown callback
- net-next/hinic: replace disable_irq_nosync/enable_irq
  * [CONFIG] please enable highdpi font FONT_TER16x32 (LP: #1819881)
- Fonts: New Terminus large console font
- [Config]: enable highdpi Terminus 16x32 font support
  * [19.04 FEAT] qeth: Enhanced link speed - kernel part (LP: #1814892)
- s390/qeth: report 25Gbit link speed
  * CVE-2017-5754
- x86/nmi: Fix NMI uaccess race against CR3 switching
- x86/mm: Fix documentation of module mapping range with 4-level paging
- x86/pti: Enable global pages for shared areas
- x86/pti: Never implicitly clear _PAGE_GLOBAL for kernel image
- x86/pti: Leave kernel text global for !PCID
- x86/pti: Fix boot problems from Global-bit setting
- x86/pti: Fix boot warning from Global-bit setting
- x86/pti: Reduce amount of kernel text allowed to be Global
- x86/pti: Disallow global kernel text with RANDSTRUCT
- x86/entry/32: Add explicit 'l' instruction suffix
- x86/asm-offsets: Move TSS_sp0 and TSS_sp1 to asm-offsets.c
- x86/entry/32: Rename TSS_sysenter_sp0 to TSS_entry2task_stack
- x86/entry/32: Load task stack from x86_tss.sp1 in SYSENTER handler
- x86/entry/32: Put ESPFIX code into a macro
- x86/entry/32: Unshare NMI return path
- x86/entry/32: Split off return-to-kernel path
- x86/entry/32: Enter the kernel via trampoline stack
- x86/entry/32: Leave the kernel via trampoline stack
- x86/entry/32: Introduce SAVE_ALL_NMI and RESTORE_ALL_NMI
- x86/entry/32: Handle Entry from Kernel-Mode on Entry-Stack
- x86/entry/32: 

[Touch-packages] [Bug 1826126] [NEW] ubuntu-bug fails to attach apport file

2019-04-24 Thread Paulo Matos
Public bug reported:

https://help.ubuntu.com/community/ReportingBugs

reports that 
```
 If this is to be added to an existing bug report, also use the -u option:

ubuntu-bug -c FILENAME.apport -u BUGNUMBER

Please do not attach the .apport or .crash file to the report, as this is not 
the same as performing the above mentioned steps.
```

However, I fail to do this:
```
$ ubuntu-bug -c cartsheel.apport -u 1826125
Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash 
file]

ubuntu-bug: error: -u/--update-bug option cannot be used together with options 
for a new report
```

This is either a ubuntu-bug or a documentation bug.

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

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

Title:
  ubuntu-bug fails to attach apport file

Status in apport package in Ubuntu:
  New

Bug description:
  https://help.ubuntu.com/community/ReportingBugs

  reports that 
  ```
   If this is to be added to an existing bug report, also use the -u option:

  ubuntu-bug -c FILENAME.apport -u BUGNUMBER

  Please do not attach the .apport or .crash file to the report, as this is not 
the same as performing the above mentioned steps.
  ```

  However, I fail to do this:
  ```
  $ ubuntu-bug -c cartsheel.apport -u 1826125
  Usage: ubuntu-bug [options] [symptom|pid|package|program path|.apport/.crash 
file]

  ubuntu-bug: error: -u/--update-bug option cannot be used together with 
options for a new report
  ```

  This is either a ubuntu-bug or a documentation bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1826126/+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 1693540] Re: package linux-image-4.8.0-53-generic (not installed) failed to install/upgrade: subprocess new pre-installation script returned error exit status 128

2019-04-24 Thread Po-Hsu Lin
I will close this as 4.8 is not supported anymore.

Please feel free to open a new bug report if you have encounter this
again.

** Changed in: linux-hwe (Ubuntu)
   Status: Fix Committed => Fix Released

** Changed in: linux-hwe (Ubuntu)
   Status: Fix Released => Invalid

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

Title:
  package linux-image-4.8.0-53-generic (not installed) failed to
  install/upgrade: subprocess new pre-installation script returned error
  exit status 128

Status in debconf package in Ubuntu:
  Fix Released
Status in linux-hwe package in Ubuntu:
  Invalid

Bug description:
  it show there's bug in my system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.8.0-53-generic (not installed)
  ProcVersionSignature: Ubuntu 4.8.0-52.55~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-52-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu May 25 08:42:40 2017
  ErrorMessage: subprocess new pre-installation script returned error exit 
status 128
  InstallationDate: Installed on 2017-04-03 (51 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: linux-hwe
  Title: package linux-image-4.8.0-53-generic (not installed) failed to 
install/upgrade: subprocess new pre-installation script returned error exit 
status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/debconf/+bug/1693540/+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 1818204] Re: Qualcomm Atheros QCA9377 wireless does not work

2019-04-24 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-48.51

---
linux (4.15.0-48.51) bionic; urgency=medium

  * linux: 4.15.0-48.51 -proposed tracker (LP: #1822820)

  * Packaging resync (LP: #1786013)
- [Packaging] update helper scripts
- [Packaging] resync retpoline extraction

  * 3b080b2564287be91605bfd1d5ee985696e61d3c in ubuntu_btrfs_kernel_fixes
triggers system hang on i386 (LP: #1812845)
- btrfs: raid56: properly unmap parity page in finish_parity_scrub()

  * [P9][LTCTest][Opal][FW910] cpupower monitor shows multiple stop Idle_Stats
(LP: #1719545)
- cpupower : Fix header name to read idle state name

  * [amdgpu] screen corruption when using touchpad (LP: #1818617)
- drm/amdgpu/gmc: steal the appropriate amount of vram for fw hand-over (v3)
- drm/amdgpu: Free VGA stolen memory as soon as possible.

  * [SRU][B/C/OEM]IOMMU: add kernel dma protection (LP: #1820153)
- ACPICA: AML parser: attempt to continue loading table after error
- ACPI / property: Allow multiple property compatible _DSD entries
- PCI / ACPI: Identify untrusted PCI devices
- iommu/vt-d: Force IOMMU on for platform opt in hint
- iommu/vt-d: Do not enable ATS for untrusted devices
- thunderbolt: Export IOMMU based DMA protection support to userspace
- iommu/vt-d: Disable ATS support on untrusted devices

  * Add basic support to NVLink2 passthrough (LP: #1819989)
- powerpc/powernv/npu: Do not try invalidating 32bit table when 64bit table 
is
  enabled
- powerpc/powernv: call OPAL_QUIESCE before OPAL_SIGNAL_SYSTEM_RESET
- powerpc/powernv: Export opal_check_token symbol
- powerpc/powernv: Make possible for user to force a full ipl cec reboot
- powerpc/powernv/idoa: Remove unnecessary pcidev from pci_dn
- powerpc/powernv: Move npu struct from pnv_phb to pci_controller
- powerpc/powernv/npu: Move OPAL calls away from context manipulation
- powerpc/pseries/iommu: Use memory@ nodes in max RAM address calculation
- powerpc/pseries/npu: Enable platform support
- powerpc/pseries: Remove IOMMU API support for non-LPAR systems
- powerpc/powernv/npu: Check mmio_atsd array bounds when populating
- powerpc/powernv/npu: Fault user page into the hypervisor's pagetable

  * Huawei Hi1822 NIC has poor performance (LP: #1820187)
- net-next: hinic: fix a problem in free_tx_poll()
- hinic: remove ndo_poll_controller
- net-next/hinic: add checksum offload and TSO support
- hinic: Fix l4_type parameter in hinic_task_set_tunnel_l4
- net-next/hinic:replace multiply and division operators
- net-next/hinic:add rx checksum offload for HiNIC
- net-next/hinic:fix a bug in set mac address
- net-next/hinic: fix a bug in rx data flow
- net: hinic: fix null pointer dereference on pointer hwdev
- hinic: optmize rx refill buffer mechanism
- net-next/hinic:add shutdown callback
- net-next/hinic: replace disable_irq_nosync/enable_irq

  * [CONFIG] please enable highdpi font FONT_TER16x32 (LP: #1819881)
- Fonts: New Terminus large console font
- [Config]: enable highdpi Terminus 16x32 font support

  * [19.04 FEAT] qeth: Enhanced link speed - kernel part (LP: #1814892)
- s390/qeth: report 25Gbit link speed

  * CVE-2017-5754
- x86/nmi: Fix NMI uaccess race against CR3 switching
- x86/mm: Fix documentation of module mapping range with 4-level paging
- x86/pti: Enable global pages for shared areas
- x86/pti: Never implicitly clear _PAGE_GLOBAL for kernel image
- x86/pti: Leave kernel text global for !PCID
- x86/pti: Fix boot problems from Global-bit setting
- x86/pti: Fix boot warning from Global-bit setting
- x86/pti: Reduce amount of kernel text allowed to be Global
- x86/pti: Disallow global kernel text with RANDSTRUCT
- x86/entry/32: Add explicit 'l' instruction suffix
- x86/asm-offsets: Move TSS_sp0 and TSS_sp1 to asm-offsets.c
- x86/entry/32: Rename TSS_sysenter_sp0 to TSS_entry2task_stack
- x86/entry/32: Load task stack from x86_tss.sp1 in SYSENTER handler
- x86/entry/32: Put ESPFIX code into a macro
- x86/entry/32: Unshare NMI return path
- x86/entry/32: Split off return-to-kernel path
- x86/entry/32: Enter the kernel via trampoline stack
- x86/entry/32: Leave the kernel via trampoline stack
- x86/entry/32: Introduce SAVE_ALL_NMI and RESTORE_ALL_NMI
- x86/entry/32: Handle Entry from Kernel-Mode on Entry-Stack
- x86/entry/32: Simplify debug entry point
- x86/entry/32: Add PTI cr3 switch to non-NMI entry/exit points
- x86/entry/32: Add PTI CR3 switches to NMI handler code
- x86/entry: Rename update_sp0 to update_task_stack
- x86/pgtable: Rename pti_set_user_pgd() to pti_set_user_pgtbl()
- x86/pgtable/pae: Unshare kernel PMDs when PTI is enabled
- x86/pgtable/32: Allocate 8k page-tables when PTI is enabled
- x86/pgtable: Move pgdp kernel/user conversion functions to pgtable.h

[Touch-packages] [Bug 1823667] Re: SRU: pcre3 ftbfs with cosmic toolchain updates

2019-04-24 Thread Matthias Klose
** Changed in: pcre3 (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  SRU: pcre3 ftbfs with cosmic toolchain updates

Status in pcre3 package in Ubuntu:
  Fix Released
Status in pcre3 source package in Cosmic:
  Fix Released

Bug description:
  Fix the symbols file error by backporting the disco upload, marking
  more symbols as optional.

  Test case: the package builds, in current 18.10, and with the planned 
toolchain updates in ppa:ubuntu-toolchain-r/ppa.
  Regression potential: Should be the same as for every no-change rebuild.

  https://launchpadlibrarian.net/418304485/buildlog_ubuntu-cosmic-
  amd64.pcre3_2%3A8.39-11_BUILDING.txt.gz

  dh_makeshlibs -plibpcre3 --add-udeb="libpcre3-udeb" -V 'libpcre3 (>= 1:8.35)' 
-- -c4
  dh_makeshlibs -plibpcrecpp0v5 -V 'libpcrecpp0v5 (>= 7.7)' -- -c4
  dpkg-gensymbols: warning: some symbols or patterns disappeared in the symbols 
file: see diff output below
  dpkg-gensymbols: warning: debian/libpcrecpp0v5/DEBIAN/symbols doesn't match 
completely debian/libpcrecpp0v5.symbols
  --- debian/libpcrecpp0v5.symbols (libpcrecpp0v5_2:8.39-11_amd64)
  +++ dpkg-gensymbolsc5z0KV 2019-04-08 00:54:17.137602850 +
  @@ -80,9 +80,9 @@
    (c++)"pcrecpp::Scanner::SetSkipExpression(char const*)@Base" 7.7
    (c++)"pcrecpp::Scanner::Skip(char const*)@Base" 7.7
    (c++)"pcrecpp::Scanner::~Scanner()@Base" 7.7
  -#MISSING: 2:8.39-9# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
  +#MISSING: 2:8.39-11# (c++|optional=STL)"std::vector 
>::_M_insert_aux(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 7.7
    (c++|optional=STL)"void std::__cxx11::basic_string, std::allocator >::_M_construct(char 
const*, char const*, std::forward_iterator_tag)@Base" 2:8.39-10
  -#MISSING: 2:8.39-9# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
  +#MISSING: 2:8.39-11# (c++|optional=STL)"void 
std::vector 
>::_M_emplace_back_aux(pcrecpp::StringPiece&&)@Base" 
2:8.39-2
    (c++|optional=STL)"void std::vector >::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece const&)@Base" 2:8.39-4
    (c++|optional=STL)"void std::vector 
>::_M_realloc_insert(__gnu_cxx::__normal_iterator > >, 
pcrecpp::StringPiece&&)@Base" 2:8.39-9
  - (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  +#MISSING: 2:8.39-11# (c++)"void std::vector 
>::emplace_back(pcrecpp::StringPiece&&)@Base" 2:8.39-10
  dh_makeshlibs: failing due to earlier errors
  make: *** [debian/rules:116: binary-arch] Error 2
  dpkg-buildpackage: error: fakeroot debian/rules binary subprocess returned 
exit status 2
  

  Build finished at 20190408-0054

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pcre3/+bug/1823667/+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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

2019-04-24 Thread Phil Gorman
System: Dell Studio XPS 8300 64bit. memory: 7.8 GiB. CPU: Intel® Core™ i7-2600 
CPU @ 3.40GHz × 8. 
Graphics AMD® Juniper.

Upgrading from perfectly good 18.10.

Before this bug appeared another error message had stated
/usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such
file or directory.

Grub indicated the presence of 5.0.0.13.14 but login failed. I can log
in with the previous kernel but it's very slow.  Using Gimp 2.10.10 I'm
experiencing odd behavior in tools, followed by hanging, before totally
freezing the computer. After giving it 90 minutes It was still unusable,
Control alt delete didn't work.The system required a hard reboot, losing
hours of work.

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in Ubuntu MATE:
  New
Status in bamf package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mime-support package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+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 1815889] Re: qemu-system-x86_64 crashed with signal 31 in __pthread_setaffinity_new()

2019-04-24 Thread Thomas Huth
** Changed in: qemu
   Status: Fix Committed => Fix Released

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

Title:
  qemu-system-x86_64 crashed with signal 31 in
  __pthread_setaffinity_new()

Status in Mesa:
  Won't Fix
Status in QEMU:
  Fix Released
Status in mesa package in Ubuntu:
  Fix Released
Status in qemu package in Ubuntu:
  Invalid
Status in mesa source package in Disco:
  Fix Released
Status in mesa source package in Eoan:
  Triaged
Status in qemu source package in Eoan:
  Triaged

Bug description:
  Unable to launch Default Fedora 29 images in gnome-boxes

  ProblemType: Crash
  DistroRelease: Ubuntu 19.04
  Package: qemu-system-x86 1:3.1+dfsg-2ubuntu1
  ProcVersionSignature: Ubuntu 4.19.0-12.13-generic 4.19.18
  Uname: Linux 4.19.0-12-generic x86_64
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  Date: Thu Feb 14 11:00:45 2019
  ExecutablePath: /usr/bin/qemu-system-x86_64
  KvmCmdLine: COMMAND STAT  EUID  RUID   PID  PPID %CPU COMMAND
  MachineType: Dell Inc. Precision T3610
  ProcEnviron: PATH=(custom, user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.19.0-12-generic 
root=UUID=939b509b-d627-4642-a655-979b44972d17 ro splash quiet vt.handoff=1
  Signal: 31
  SourcePackage: qemu
  StacktraceTop:
   __pthread_setaffinity_new (th=, cpusetsize=128, 
cpuset=0x7f5771fbf680) at ../sysdeps/unix/sysv/linux/pthread_setaffinity.c:34
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
   start_thread (arg=) at pthread_create.c:486
   clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95
  Title: qemu-system-x86_64 crashed with signal 31 in 
__pthread_setaffinity_new()
  UpgradeStatus: Upgraded to disco on 2018-11-14 (91 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video
  dmi.bios.date: 11/14/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A18
  dmi.board.name: 09M8Y8
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA18:bd11/14/2018:svnDellInc.:pnPrecisionT3610:pvr00:rvnDellInc.:rn09M8Y8:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision T3610
  dmi.product.sku: 05D2
  dmi.product.version: 00
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mesa/+bug/1815889/+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 1826003] Re: software properties unknown to ubuntu software

2019-04-24 Thread corrado venturini
Problem disappeared after today updates

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

Title:
  software properties unknown to ubuntu software

Status in software-properties package in Ubuntu:
  New

Bug description:
  open the dash, right click on 'software properties' select 'show
  details' gnome software opens with a message 'unable to find
  "software-properties-gtk.desktop"

  corrado@corrado-HP-p4-ee:~$ inxi -Fx
  System:Host: corrado-HP-p4-ee Kernel: 5.0.0-13-generic x86_64 bits: 64 
compiler: gcc v: 8.3.0 Desktop: Gnome 3.32.0 
 Distro: Ubuntu 19.10 (Eoan EANIMAL) 
  Machine:   Type: Laptop System: Hewlett-Packard product: HP 250 G3 Notebook 
PC v: 0991100600087 
 serial:  
 Mobo: Hewlett-Packard model: 2211 v: 86.49 serial:  
UEFI: Insyde v: F.36 date: 12/18/2014 
  Battery:   ID-1: BAT1 charge: 16.0 Wh condition: 20.0/20.0 Wh (100%) model: 
13-42 OA03031 status: Discharging 
  CPU:   Topology: Dual Core model: Intel Core i5-4210U bits: 64 type: MT 
MCP arch: Haswell rev: 1 L2 cache: 3072 KiB 
 flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 
19156 
 Speed: 798 MHz min/max: 800/2700 MHz Core speeds (MHz): 1: 798 2: 
798 3: 798 4: 798 
  Graphics:  Device-1: Intel Haswell-ULT Integrated Graphics vendor: 
Hewlett-Packard driver: i915 v: kernel 
 bus ID: 00:02.0 
 Display: x11 server: X.Org 1.20.4 driver: i915 resolution: 
1366x768~60Hz 
 OpenGL: renderer: Mesa DRI Intel Haswell Mobile v: 4.5 Mesa 19.0.2 
direct render: Yes 
  Audio: Device-1: Intel Haswell-ULT HD Audio vendor: Hewlett-Packard 
driver: snd_hda_intel v: kernel bus ID: 00:03.0 
 Device-2: Intel 8 Series HD Audio vendor: Hewlett-Packard driver: 
snd_hda_intel v: kernel bus ID: 00:1b.0 
 Sound Server: ALSA v: k5.0.0-13-generic 
  Network:   Device-1: Realtek RTL810xE PCI Express Fast Ethernet vendor: 
Hewlett-Packard driver: r8169 v: kernel 
 port: 3000 bus ID: 08:00.0 
 IF: enp8s0 state: down mac: 5c:b9:01:06:ba:ce 
 Device-2: Ralink RT3290 Wireless 802.11n 1T/1R PCIe vendor: 
Hewlett-Packard driver: rt2800pci v: 2.3.0 
 port: 3000 bus ID: 09:00.0 
 IF: wlp9s0f0 state: up mac: ac:d1:b8:82:03:5d 
  Drives:Local Storage: total: 465.76 GiB used: 5.88 GiB (1.3%) 
 ID-1: /dev/sda vendor: Seagate model: ST500LT012-1DG142 size: 
465.76 GiB 
  Partition: ID-1: / size: 31.25 GiB used: 5.87 GiB (18.8%) fs: ext4 dev: 
/dev/sda4 
 ID-2: swap-1 size: 4.00 GiB used: 0 KiB (0.0%) fs: swap dev: 
/dev/sda2 
  Sensors:   System Temperatures: cpu: 41.0 C mobo: N/A 
 Fan Speeds (RPM): N/A 
  Info:  Processes: 209 Uptime: 2h 44m Memory: 3.78 GiB used: 1.14 GiB 
(30.0%) Init: systemd runlevel: 5 Compilers: 
 gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33 
  corrado@corrado-HP-p4-ee:~$ locale
  LANG=en_US.UTF-8
  LANGUAGE=
  LC_CTYPE="en_US.UTF-8"
  LC_NUMERIC=it_IT.UTF-8
  LC_TIME=it_IT.UTF-8
  LC_COLLATE="en_US.UTF-8"
  LC_MONETARY=it_IT.UTF-8
  LC_MESSAGES="en_US.UTF-8"
  LC_PAPER=it_IT.UTF-8
  LC_NAME=it_IT.UTF-8
  LC_ADDRESS=it_IT.UTF-8
  LC_TELEPHONE=it_IT.UTF-8
  LC_MEASUREMENT=it_IT.UTF-8
  LC_IDENTIFICATION=it_IT.UTF-8
  LC_ALL=
  corrado@corrado-HP-p4-ee:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-software 3.30.6-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Apr 23 17:13:53 2019
  ExecutablePath: /usr/bin/gnome-software
  InstallationDate: Installed on 2019-04-21 (1 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan EANIMAL" - Alpha amd64 (20190421)
  InstalledPlugins:
   gnome-software-plugin-flatpak N/A
   gnome-software-plugin-snap3.30.6-2ubuntu3
  SourcePackage: gnome-software
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1826003/+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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

2019-04-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: mime-support (Ubuntu)
   Status: New => Confirmed

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in Ubuntu MATE:
  New
Status in bamf package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mime-support package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

2019-04-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in Ubuntu MATE:
  New
Status in bamf package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mime-support package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+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 1825420] Re: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to install/upgrade: triggers looping, abandoned

2019-04-24 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to
  install/upgrade: triggers looping, abandoned

Status in Ubuntu MATE:
  New
Status in bamf package in Ubuntu:
  Confirmed
Status in dpkg package in Ubuntu:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in linux-firmware package in Ubuntu:
  Confirmed
Status in mime-support package in Ubuntu:
  Confirmed

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 18.10 installed
  2. Install all updates to it
  3. Switch to Main server
  4. Launch update-manager
  5. Confirm upgrading to 19.04
  6. Wait for upgrade process to finish

  Expected results:
  * upgrade process ended without errors

  Actual results:
  * upgrade process ended with warning message:

  Could not install 'linux-image-5.0.0-13-generic'
  The upgrade will continue but the 'linux-image-5.0.0-13-generic' package 
may not be in a working state. Please consider submitting a bug report about it.

  triggers looping, abandoned

  Workaround:

Run recommended `dpkg --configure -a` before actual reboot.

  System info: running VirtualBox guest with virtualbox-guest-x11
  (6.0.6-dfsg-1) inside VirtualBox 5.1.38 host.

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: linux-image-5.0.0-13-generic 5.0.0-13.14
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  mate   1542 F pulseaudio
  Date: Thu Apr 18 22:56:56 2019
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2019-02-17 (60 days ago)
  InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  IwConfig:
   lono wireless extensions.
   
   enp0s3no wireless extensions.
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: innotek GmbH VirtualBox
  ProcFB: 0 vboxdrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-17-generic 
root=UUID=01417e27-d554-4ce8-91bc-1dda8392c976 ro quiet splash
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not 
accessible: Permission denied
   No PulseAudio daemon running, or not running as session daemon.
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions: grub-pc 2.02+dfsg1-12ubuntu2
  RfKill:
   
  SourcePackage: linux
  StagingDrivers: vboxvideo
  Title: package linux-image-5.0.0-13-generic 5.0.0-13.14 failed to 
install/upgrade: triggers looping, abandoned
  UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1825420/+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