date:20190318

Actually it looks like just vesafb starting in low resolution:

[0.532845] vesafb: mode is 1280x1024x32, linelength=5120, pages=0
[0.532846] vesafb: scrolling: redraw
[0.532847] vesafb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[0.532854] vesafb: framebuffer at 0xf100, mapped to 0x(ptrval), 
using 5120k, total 5120k

which is then later corrected by nouveaufb:

[   15.346865] fb: switching to nouveaufb from VESA VGA
...
[   16.853149] nouveau :01:00.0: DRM: allocated 1920x1080 fb: 0x6, bo 
4d979e0c

so it sounds like the main issue is that vesafb is used at all during
boot.

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

** Tags removed: nvidia

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

Title:
  Wrong resolution during boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting the startup screen is in low resolution while before it
  was in high resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-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
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 18:04:57 2019
  DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b]
  InstallationDate: Installed on 2018-01-04 (437 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: ASUSTeK COMPUTER INC. CM6870
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago)
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6870
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Desktop
  dmi.product.name: CM6870
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  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:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Sep 26 20:09:04 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820685/+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 1820685] Re: Wrong resolution during boot

Low resolution during boot is something usually caused by the Nvidia
proprietary driver. So I wonder if you might still have some remnants of
that installed?

** Tags added: nouveau nvidia

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

Title:
  Wrong resolution during boot

Status in linux package in Ubuntu:
  Incomplete

Bug description:
  When booting the startup screen is in low resolution while before it
  was in high resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-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
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 18:04:57 2019
  DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b]
  InstallationDate: Installed on 2018-01-04 (437 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: ASUSTeK COMPUTER INC. CM6870
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago)
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6870
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.family: Desktop
  dmi.product.name: CM6870
  dmi.product.version: System Version
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
  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:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Wed Sep 26 20:09:04 2018
  xserver.configfile: default
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4~16.04.1
  xserver.video_driver: nouveau

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820685/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

No problem. If the issue doesn't return after 60 days and there are no
further comments then this bug will automatically close.

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

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

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1652101] Re: Can't create nested AppArmor namespaces

2019-03-18 Thread brian mullan

how does this get assigned to someone so it might get fixed?

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

Title:
  Can't create nested AppArmor namespaces

Status in AppArmor:
  Confirmed
Status in apparmor package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed

Bug description:
  A user with CAP_MAC_ADMIN in the init namespace can create an AppArmor
  policy namespace and load a profile belonging to that AppArmor
  namespace. Once that's done, the user can confine a process with that
  namespaced AppArmor profile and enter into a user namespace. That
  process can then load additional AppArmor profiles inside of the
  AppArmor and user namespace. Here's an example:

  We need to set up the namespace, n1, and load the profile, p1.
  $ export rules="file, signal, unix, dbus, ptrace, mount, pivot_root, 
capability,"
  $ sudo mkdir /sys/kernel/security/apparmor/policy/namespaces/n1
  $ echo "profile p1 { $rules }" | sudo apparmor_parser -qrn n1

  Now we enter into confinement using the AppArmor namespace and profile and 
then enter into an unprivileged user namespace
  $ aa-exec -n n1 -p p1 -- unshare -Ur

  We can now load profiles as the privileged user inside of the unprivileged 
user namespace
  # echo "profile test {}" | apparmor_parser -qr

  The reason for this bug report is that we cannot create a nested
  AppArmor policy namespace inside of the unprivileged user namespace

  # mkdir /sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1
  mkdir: cannot create directory 
‘/sys/kernel/security/apparmor/policy/namespaces/n1/namespaces/p1’: Permission 
denied

  If that worked, we could adjust LXD to read
  /sys/kernel/security/apparmor/.ns_name to get the current AppArmor
  namespace, then create a new namespace under the current namespace,
  and leverage the nested namespace for its nested containers.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apparmor/+bug/1652101/+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 1820770] [NEW] when printing from the internet at Wikipedia the 8 page document only printed pages 2, 3, 4 and did not print 1, 5, 6, 7 and 8.

2019-03-18 Thread Shane Horton

Public bug reported:

Other random internet pages do not print at all.  The printer is a
Brother HL-L2305W.  I have been to brother and installed the driver
package from them with the same result.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.3
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 18 16:18:36 2019
InstallationDate: Installed on 2018-12-25 (83 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lpstat:
 device for HL-L2305-2: usb://Brother/HL-L2305%20series?serial=U63934M4N615987
 device for HLL2305: usb://Brother/HL-L2305%20series?serial=U63934M4N615987
MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
Papersize: letter
PpdFiles:
 Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HLL2305.ppd', 
'/etc/cups/ppd/HL-L2305-2.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HLL2305.ppd: Permission denied
 grep: /etc/cups/ppd/HL-L2305-2.ppd: Permission denied
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=15257050-0864-47a7-8179-fe818fbcbe2f ro quiet splash vt.handoff=1
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/16/2013
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.37
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 1693
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 14.16
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.37:bd01/16/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1693:rvrKBCVersion14.16:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
dmi.product.name: HP Pavilion g6 Notebook PC
dmi.product.version: 05931120461620100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apparmor apport-bug bionic

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

Title:
  when printing from the internet at Wikipedia the 8 page document only
  printed pages 2,3,4 and did not print 1,5,6,7 and 8.

Status in cups package in Ubuntu:
  New

Bug description:
  Other random internet pages do not print at all.  The printer is a
  Brother HL-L2305W.  I have been to brother and installed the driver
  package from them with the same result.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.3
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 16:18:36 2019
  InstallationDate: Installed on 2018-12-25 (83 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lpstat:
   device for HL-L2305-2: usb://Brother/HL-L2305%20series?serial=U63934M4N615987
   device for HLL2305: usb://Brother/HL-L2305%20series?serial=U63934M4N615987
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  Papersize: letter
  PpdFiles:
   Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/HLL2305.ppd', 
'/etc/cups/ppd/HL-L2305-2.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/HLL2305.ppd: Permission denied
   grep: /etc/cups/ppd/HL-L2305-2.ppd: Permission denied
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-46-generic 
root=UUID=15257050-0864-47a7-8179-fe818fbcbe2f ro quiet splash vt.handoff=1
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/16/2013
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.37
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 1693
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 14.16
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.37:bd01/16/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr05931120461620100:rvnHewlett-Packard:rn1693:rvrKBCVersion14.16:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=MIN
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.version: 05931120461620100
  dmi.sys.vendor: Hewlett-Packard

To manage notifications about this bug go to:

[Touch-packages] [Bug 1820172] Re: [regression] Python async test fails with OpenSSL 1.1.1b

2019-03-18 Thread Brian Murray

** Also affects: openssl (Ubuntu Disco)
   Importance: High
   Status: New

** Also affects: python3.7 (Ubuntu Disco)
   Importance: High
   Status: New

** Tags removed: rls-dd-incoming

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

Title:
  [regression] Python async test fails with OpenSSL 1.1.1b

Status in Python:
  New
Status in openssl package in Ubuntu:
  New
Status in python3.7 package in Ubuntu:
  New
Status in openssl source package in Disco:
  New
Status in python3.7 source package in Disco:
  New

Bug description:
  Python async test fails with OpenSSL 1.1.1b, after upgrading from
  1.1.1. Reported also in the Python tracker.

To manage notifications about this bug go to:
https://bugs.launchpad.net/python/+bug/1820172/+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 1808864] Re: Poor translation of zh_CN gpasswd(1) man page

2019-03-18 Thread Adolfo Jayme

** Changed in: ubuntu-translations
 Assignee: (unassigned) => Ubuntu Simplified Chinese Translators 
(ubuntu-l10n-zh-cn)

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

Title:
  Poor translation of zh_CN gpasswd(1) man page

Status in Ubuntu Translations:
  New
Status in language-pack-zh-hans package in Ubuntu:
  New
Status in shadow package in Ubuntu:
  New

Bug description:
  man -l /usr/share/man/zh_CN/man1/gpasswd.1.gz

  The zh_CN version of gpasswd(1) not only is partially done, but also
  contains an error in the first sentence. The translator confused the
  verb "administer" with the person "administrator." The section
  heading, originally "Notes (noun) about group passwords," was
  translated as "Please note (verb) the group passwords." Even Google
  translate does better!

  Translation errors
  ==
  gpasswd - administer /etc/group and /etc/gshadow
  gpasswd - 管理员 /etc/group 和 /etc/gshadow
^^ 管理员 -- administrator
   管理 -- administer

  Notes about group passwords
  请注意组密码
  ^^ 请注意…… -- please note (v.)
 关于……的说明 -- notes (n.) about

  Typos
  =
  -h, --help
  Display help message and exit.

  -h, --help
  现实帮助信息并退出。
   显示 Xiǎnshì -- display
   现实 Xiànshí -- reality

  Correct Google translate results (this but unironically)
  
  "gpasswd - administer /etc/group and /etc/gshadow"
  "gpasswd - 管理 /etc/group 和 /etc/gshadow"

  "Notes about group passwords"
  "关于组密码的说明"

  "Display help message and exit."
  "显示帮助消息并退出。"

  Notes about my system
  =
  $ lsb_release -rd
  Description:Ubuntu 18.04.1 LTS
  Release:18.04
  $ apt-cache policy passwd
  passwd:
Installed: 1:4.5-1ubuntu1
Candidate: 1:4.5-1ubuntu1
Version table:
   *** 1:4.5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-translations/+bug/1808864/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

2019-03-18 Thread Filip Golab

** Attachment added: "dmesgafter.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+attachment/5247408/+files/dmesgafter.txt

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

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

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1818802] Re: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails after a while

2019-03-18 Thread Filip Golab

** Attachment added: "journalafter.txt"
   
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+attachment/5247407/+files/journalafter.txt

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

Title:
  [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails
  after a while

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

Bug description:
  Audio dies after few seconds, returns after few minutes and dies again

  filip@ux433:~$ lsb_release -rd
  Description:  Ubuntu 18.10
  Release:  18.10

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  Uname: Linux 4.20.14-042014-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  filip  8566 F pulseaudio
   /dev/snd/pcmC0D0p:   filip  8566 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Mar  6 10:11:01 2019
  InstallationDate: Installed on 2019-01-05 (59 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Speaker, Internal
  Symptom_PulseAudioLog: mar 06 10:04:08 ux433 dbus-daemon[3008]: [system] 
Activating via systemd: service name='org.freedesktop.RealtimeKit1' 
unit='rtkit-daemon.service' requested by ':1.37' (uid=121 pid=6142 
comm="/usr/bin/pulseaudio --daemonize=no ")
  Symptom_Type: Sound works for a while, then breaks
  Title: [ZenBook UX433FN_UX433FN, Realtek ALC294, Speaker, Internal] fails 
after a while
  UpgradeStatus: Upgraded to cosmic on 2019-01-28 (36 days ago)
  dmi.bios.date: 11/21/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX433FN.301
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX433FN
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX433FN.301:bd11/21/2018:svnASUSTeKCOMPUTERINC.:pnZenBookUX433FN_UX433FN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX433FN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ZenBook
  dmi.product.name: ZenBook UX433FN_UX433FN
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818802/+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 1819487] Re: sshd crashed on s390x with hw crypto enabled

This bug was fixed in the package openssl-ibmca - 2.0.2-0ubuntu2

---
openssl-ibmca (2.0.2-0ubuntu2) disco; urgency=medium

  * Rework error string init and exit. LP: #1819487

 -- Dimitri John Ledkov   Mon, 18 Mar 2019 15:03:08
+

** Changed in: openssl-ibmca (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  sshd crashed on s390x with hw crypto enabled

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssh package in Ubuntu:
  Invalid
Status in openssl-ibmca package in Ubuntu:
  Fix Released

Bug description:
  While using today's daily image of disco (either in z/VM or on LPAR)
  and enabling s309x hardware crypto support in openssh, sshd crashes
  with the following messages:

  $ ssh ubuntu@localhost
  The authenticity of host 'localhost (::1)' can't be established.
  ECDSA key fingerprint is SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
  ubuntu@localhost's password:
  packet_write_wait: Connection to ::1 port 22: Broken pipe
  (local session is sufficient to reproduce)

  Steps to reproduce - on disco daily:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  Codename: disco
  $ uname -a
  Linux zlin42 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:25:21 UTC 2019 s390x 
s390x s390x GNU/Linux

  - enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  - sudo apt-get install openssl-ibmca libica-utils libica3
  - sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  - sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' 
/etc/ssl/openssl.cnf
  - sudo sed -i '10i openssl_conf = openssl_def' /etc/ssl/openssl.cnf
  - afterwards ssh login attempts fail (existing session are unaffected):
     $ ssh ubuntu@localhost
     The authenticity of host 'localhost (::1)' can't be established.
     ECDSA key fingerprint is 
SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
     Are you sure you want to continue connecting (yes/no)? yes
     Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
     ubuntu@localhost's password:
     packet_write_wait: Connection to ::1 port 22: Broken pipe

  [94629.032586] User process fault: interruption code 003b ilc:2 in 
libpthread-2.29.so[3ff7d48+1c000]
  [94629.032597] Failing address:  TEID: 0800
  [94629.032598] Fault in primary space mode while using user ASCE.
  [94629.032601] AS:0007450281c7 R3:0024
  [94629.032606] CPU: 0 PID: 8183 Comm: sshd Not tainted 5.0.0-7-generic 
#8-Ubuntu
  [94629.032607] Hardware name: IBM 2964 N63 400 (LPAR)
  [94629.032608] User PSW : 070520018000 03ff7d48e954
  [94629.032610]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
RI:0 EA:3
  [94629.032611] User GPRS:    
03ff7e0085c8
  [94629.032612]03ff7e510108 03ff7db1c3a8  
03fff857eea0
  [94629.032613]03ff7e525040 02aa3f5ec090 03ff7e4916f0 
03ff7e4921a8
  [94629.032614]03ff7db17c18 0002 03ff7e07238a 
03fff857ea20
  [94629.032622] User Code: 03ff7d48e946: b9040012  lgr %r1,%r2
    03ff7d48e94a: e3f0ff60ff71  lay 
%r15,-160(%r15)
   #03ff7d48e950: 4700  bc  0,0
   >03ff7d48e954: 58202018  l   
%r2,24(%r2)
    03ff7d48e958: b24f00b0  ear %r11,%a0
    03ff7d48e95c: ebbb002d  sllg
%r11,%r11,32
    03ff7d48e962: b24f00b1  ear %r11,%a1
    03ff7d48e966: 5920b0d0  c   
%r2,208(%r11)
  [94629.032634] Last Breaking-Event-Address:
  [94629.032638]  [<03ff7df773b4>] 0x3ff7df773b4

  For more details see attachments ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: s390x
  DistroRelease: Ubuntu 19.04
  Package: openssh-server 1:7.9p1-9
  PackageArchitecture: s390x
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code -11:
  Tags:  disco
  Uname: Linux 5.0.0-7-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: pkcs11
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1819487/+subscriptions

-- 
Mailing

[Touch-packages] [Bug 1623530] Re: Apport should be disabled by default

2019-03-18 Thread Fernando Contreras

I agree with Luis I'm new in Ubuntu and this message is really painful
to my eyes, you should run that on the background.

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

Title:
  Apport should be disabled by default

Status in Apport:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I work with large communities (US, India, Latin America) and almost
  the number one issue they have with Ubuntu or simply scares them off
  is the fact that errors keep popping up every time. Some times
  multiples times per minutes, per hour, per day.

  The reason is how apport works by default. The "solution" is going to
  /etc/default/apport and setting the option to 0 (Disable). I do
  understand the full benefit or submitting automatically all bug
  reports, but this has gotten (And most Ubuntu users will be able to
  confirm) out of hand with some many popup questions about some bug or
  another that are simply fixed the moment the report is going to be
  send (eg: Compiz issue that was fixed a couple of milliseconds later,
  unity issue, dash issue, firefox issue, etc..). All of them have
  mechanism to handle failures and basically heal themselves.

  The question regarding this is:

  Leaving apport enable by default on an Ubuntu installation simply
  scares or annoys end users (a lot may I add). Leaving it disabled, it
  will not send a bug report, but there is no issue in simply creating
  an ubuntu-bug report through the terminal. So the sending of the
  report is still valid, but is not forced onto the user (And not forced
  so many times).

  This report is back by about 3 years going back and forth with the
  same apport issue and seeing probably around 500 users I have helped
  myself with the same issue, since this makes Ubuntu less productive to
  the actual user, even from start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 14 08:16:03 2016
  InstallationDate: Installed on 2016-04-22 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1623530/+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 1623530] Re: Apport should be disabled by default

2019-03-18 Thread Luis Alvarado

Guys, this has created more issues to newcomers than anything else I
teach them. It should not be alerting the user EVERY TIME an app crashes
(which simply comes back up after a second). It apport needs to be
enabled to send or gather information it should ask ONCE during the
installation process if the user wants to sent the information without
being prompted every time an app crashes (and an option if they do want
to be prompted). This basically promotes a new comer to leave ubuntu
because they think the whole thing is broken. From a usability stand
point, it is still the worse idea ever when trying to promote the
system, The suggestions mentioned 12+ months ago have not being applied
nor a feedback (which would be welcomed) received. It is very
frustrating to explain to every new ubuntu user I teach or bring to use
ubuntu (which already tops 5000+ users) that they need to disable apport
to avoid the bug report popups.

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

Title:
  Apport should be disabled by default

Status in Apport:
  Confirmed
Status in One Hundred Papercuts:
  Confirmed
Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I work with large communities (US, India, Latin America) and almost
  the number one issue they have with Ubuntu or simply scares them off
  is the fact that errors keep popping up every time. Some times
  multiples times per minutes, per hour, per day.

  The reason is how apport works by default. The "solution" is going to
  /etc/default/apport and setting the option to 0 (Disable). I do
  understand the full benefit or submitting automatically all bug
  reports, but this has gotten (And most Ubuntu users will be able to
  confirm) out of hand with some many popup questions about some bug or
  another that are simply fixed the moment the report is going to be
  send (eg: Compiz issue that was fixed a couple of milliseconds later,
  unity issue, dash issue, firefox issue, etc..). All of them have
  mechanism to handle failures and basically heal themselves.

  The question regarding this is:

  Leaving apport enable by default on an Ubuntu installation simply
  scares or annoys end users (a lot may I add). Leaving it disabled, it
  will not send a bug report, but there is no issue in simply creating
  an ubuntu-bug report through the terminal. So the sending of the
  report is still valid, but is not forced onto the user (And not forced
  so many times).

  This report is back by about 3 years going back and forth with the
  same apport issue and seeing probably around 500 users I have helped
  myself with the same issue, since this makes Ubuntu less productive to
  the actual user, even from start.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: apport 2.20.1-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Sep 14 08:16:03 2016
  InstallationDate: Installed on 2016-04-22 (144 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.default.apport:
   # set this to 0 to disable apport, or to 1 to enable it
   # you can temporarily override this with
   # sudo service apport start force_start=1
   enabled=0
  mtime.conffile..etc.default.apport: 2016-08-12T16:38:06.249273

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1623530/+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 1820743] [NEW] Pulseaudio is sometimes broken after resume from suspend

2019-03-18 Thread Pedro Côrte-Real

Public bug reported:

Sometimes when resuming from suspend pulseaudio is broken and only the
dummy output is available. After "pulseaudio -k" audio again works.
Here's what I found in the logs:

$ journalctl --since "1 day ago" | grep pulseaudio
Mar 17 19:40:51 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 17 21:29:49 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 09:01:13 coulson pulseaudio[9869]: [alsa-sink-ALC293 Analog] 
alsa-sink.c: snd_pcm_mmap_begin: File descriptor in bad state
Mar 18 09:06:25 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 09:32:40 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 09:47:36 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.
Mar 18 18:16:42 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: Failed 
to create sink input: sink is suspended.

--- Here I ran pulseaudio -k ---

Mar 18 19:08:13 coulson pulseaudio[26606]: [pulseaudio] backend-ofono.c: Failed 
to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
Mar 18 19:08:13 coulson pulseaudio[26612]: [pulseaudio] pid.c: Daemon already 
running.
Mar 18 19:08:13 coulson pulseaudio[26614]: [pulseaudio] pid.c: Daemon already 
running.
Mar 18 19:08:13 coulson pulseaudio[26616]: [pulseaudio] pid.c: Daemon already 
running.


The "Failed to create sink input" seems to happen on every resume but only some 
times does it actually break. Don't know if the ofono message is related or not.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.2
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  pedrocr   26606 F pulseaudio
CurrentDesktop: GNOME
Date: Mon Mar 18 19:11:09 2019
InstallationDate: Installed on 2018-05-31 (291 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1CET66W (1.34 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FAS5TS00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1CET66W(1.34):bd03/22/2018:svnLENOVO:pn20FAS5TS00:pvrThinkPadT460s:rvnLENOVO:rn20FAS5TS00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460s
dmi.product.name: 20FAS5TS00
dmi.product.version: ThinkPad T460s
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug bionic

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

Title:
  Pulseaudio is sometimes broken after resume from suspend

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Sometimes when resuming from suspend pulseaudio is broken and only the
  dummy output is available. After "pulseaudio -k" audio again works.
  Here's what I found in the logs:

  $ journalctl --since "1 day ago" | grep pulseaudio
  Mar 17 19:40:51 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 17 21:29:49 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 09:01:13 coulson pulseaudio[9869]: [alsa-sink-ALC293 Analog] 
alsa-sink.c: snd_pcm_mmap_begin: File descriptor in bad state
  Mar 18 09:06:25 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 09:32:40 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 09:47:36 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.
  Mar 18 18:16:42 coulson pulseaudio[9447]: W: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.

  --- Here I ran pulseaudio -k ---

  Mar 18 19:08:13 coulson pulseaudio[26606]: [pulseaudio] backend-ofono.c: 
Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
  Mar 18 19:08:13 coulson pulseaudio[26612]: [pulseaudio] pid.c: Daemon already 
running.
  Mar 18 19:08:13 coulson pulseaudio[26614]: [pulseaudio] pid.c: Daemon

[Touch-packages] [Bug 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

** Description changed:

  [Impact]
  
-  * The new modemmanager package adds DW5820e support.
-  * This modemmanager version is needed to support new devices.
+  * The new modemmanager package adds DW5820e support.
+  * This modemmanager version is needed to support new devices.
  
  [Test Case]
  
-  * install modemmanager, libmbim, and libqmi from -proposed
-  * reboot and try WWAN function to see if any regression there.
-  * perform general dogfooding of its reverse dependencies (network-
-manager, gnome-control-center etc.)
+  * install modemmanager, libmbim, and libqmi from -proposed
+  * reboot and try WWAN function to see if any regression there.
+  * perform general dogfooding of its reverse dependencies (network-
+    manager, gnome-control-center etc.)
  
  [Regression Potential]
  
-  * The package comes from Zesty and should not have regression there.
-  * Every new upstream release can potentially break existing dependencies 
-if any of the required features have been changed/removed, so besides 
-regular testing a general dogfooding session with the new modemmanager 
-is advised.
+  * The package comes from Disco and should not have regression there.
+  * Every new upstream release can potentially break existing dependencies
+    if any of the required features have been changed/removed, so besides
+    regular testing a general dogfooding session with the new modemmanager
+    is advised.
  
  [Original Description]
  
  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  In Progress
Status in libqmi source package in Bionic:
  In Progress
Status in modemmanager source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
     manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Disco and should not have regression there.
   * Every new upstream release can potentially break existing dependencies
     if any of the required features have been changed/removed, so besides
     regular testing a general dogfooding session with the new modemmanager
     is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1819615/+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 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove

My apt doesn't have that option (yet?)

Instead I used:

# apt-get --dry-run autoremove  | grep ^Remv
Remv ccnet [6.1.5-1]
Remv libccnet0 [6.1.5-1]
Remv libseafile0 [6.1.8-1240~ubuntu16.04.1]
Remv libsearpc1 [3.0.8.3-138~ubuntu16.04.1]
Remv linux-headers-4.15.0-36-generic [4.15.0-36.39]
Remv linux-headers-4.15.0-36 [4.15.0-36.39]
Remv linux-modules-extra-4.15.0-36-generic [4.15.0-36.39]
Remv linux-image-4.15.0-36-generic [4.15.0-36.39]
Remv linux-modules-4.15.0-36-generic [4.15.0-36.39]
Remv python-searpc [3.0.8-1]

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

Title:
  /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-
  upgrade@1991:main:do_auto_remove

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Confirmed

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.1ubuntu1.18.04.5, the problem page at 
https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e 
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/1795696/+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 1818953] Re: mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by executing perl script, multiple architectures

2019-03-18 Thread Steve Langasek

On Sat, Mar 16, 2019 at 04:53:35PM -, Niko Tyni wrote:
> On Thu, Mar 14, 2019 at 12:25:22AM -, Dimitri John Ledkov wrote:
> > @ntyni excellent analysis! i like it a lot, and the patch is clean and
> > easy to understand.

> > Are you going to make a debian upload soon, or should I cherrypick that
> > for Ubuntu now?

> Fixed in Debian 5.28.1-5, which I've just uploaded.

Thanks, I've synced this to Ubuntu but unfortunately it's failing on the
newly-added arch-specific tests for NDBM:

autopkgtest [11:12:06]: test ndbm: [---
testing NDBM reading...
buster-ndbm OK
opening NDBM file failed: No such file or directory at -e line 1.
autopkgtest [11:12:06]: test ndbm: ---]
ndbm FAIL non-zero exit status 1
autopkgtest [11:12:07]: test ndbm:  - - - - - - - - - - results - - - - - - - - 
- -
autopkgtest [11:12:07]: test ndbm:  - - - - - - - - - - stderr - - - - - - - - 
- -
opening NDBM file failed: No such file or directory at -e line 1.

So this is currently blocked in disco-proposed.

-- 
Steve Langasek   Give me a lever long enough and a Free OS
Debian Developer   to set it on, and I can move the world.
Ubuntu Developer   https://www.debian.org/
slanga...@ubuntu.com vor...@debian.org

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

Title:
  mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by
  executing perl script, multiple architectures

Status in The Ubuntu-power-systems project:
  Confirmed
Status in perl package in Ubuntu:
  Confirmed
Status in perl source package in Disco:
  Confirmed
Status in perl package in Debian:
  Unknown

Bug description:
  == Comment: #0 - NAGENDRA P. DONTAMSETTY  - 2019-02-28 
00:14:49 ==
  ---Problem Description---
  Perl core dumping core on UBUNTU 19.04 by executing perl script
   
  ---uname output---
  root@p8ct1p13:/tmp# uname -a Linux p8ct1p13.in.ibm.com 4.19.0-13-generic 
#14-Ubuntu SMP Thu Feb 7 21:50:00 UTC 2019 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = ppc64le and power8 
   
  ---Debugger Data---
  root@p8ct1p13:/tmp# file core
  core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1 
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1 
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0, 
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'
   
   
  ---Steps to Reproduce---
   Description:  Perl core dumpinmg core on UBUNTU 19.04 by exec cmd "mkrsrc"

  
  root@p8ct1p13:/tmp# uname -a
  Linux p8ct1p13.in.ibm.com 4.19.0-13-generic #14-Ubuntu SMP Thu Feb 7 21:50:00 
UTC 2019 ppc64le ppc64le ppc64le GNU/Linux

  
  root@p8ct1p13:~# cat /etc/os-release
  NAME="Ubuntu"
  VERSION="19.04 (Disco Dingo)"
  ID=ubuntu
  ID_LIKE=debian
  PRETTY_NAME="Ubuntu Disco Dingo (development branch)"
  VERSION_ID="19.04"
  HOME_URL="https://www.ubuntu.com/;
  SUPPORT_URL="https://help.ubuntu.com/;
  BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/;
  
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy;
  VERSION_CODENAME=disco
  UBUNTU_CODENAME=disco

  
  root@p8ct1p13:~# ctversion -bv
  RSCT_Build_Name=rsholxs002a 3.2.4.2 RSCT_Build_Time=19043.16:11:49 
RSCT_Build_Context=ppc64le_linux_2

  
  root@p8ct1p13:/tmp# mkrsrc IBM.Ray Name="fvt1" 
NodeNameList={"p8ct1p09.in.ibm.com"} ManualMode=0 Int32=00 String="Initial Test 
String 2"
  perl: mbrtowc.c:105: __mbrtowc: Assertion `__mbsinit (data.__statep)' failed.
  Aborted (core dumped)

  root@p8ct1p13:/tmp# file core
  core: ELF 64-bit LSB core file, 64-bit PowerPC or cisco 7500, version 1 
(SYSV), SVR4-style, from '/usr/bin/perl /usr/bin/mkrsrc IBM.Ray Name=fvt1 
NodeNameList={p8ct1p09.in.ibm.c', real uid: 0, effective uid: 0, real gid: 0, 
effective gid: 0, execfn: '/usr/bin/mkrsrc', platform: 'power8'

  
  root@p8ct1p13:/tmp# which mkrsrc
  /usr/bin/mkrsrc

  root@p8ct1p13:/tmp# file /usr/bin/mkrsrc

  /usr/bin/mkrsrc: symbolic link to /opt/rsct/bin/mkrsrc

  root@p8ct1p13:/tmp# file /opt/rsct/bin/mkrsrc
  /opt/rsct/bin/mkrsrc: Perl script text executable
   
  Contact Information = Nagendra Dontamsetty/ndont...@in.ibm.com, 
Anirban/anirb...@in.ibm.com 
   
  Userspace tool common name: perl 5 
   
  The userspace tool has the following bit modes: 64bit 

  Userspace rpm: ii  perl  5.28.1-4
  ppc64el

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for Nagendra Dontamsetty/ndont...@in.ibm.com, 
Anirban/anirb...@in.ibm.com: 
  -Post a private note with access information to the machine that is currently 
in the debugger.
  -Attach ltrace and strace of userspace application.

To manage notifications about this bug go to:

[Touch-packages] [Bug 1820691] [NEW] WSL give error in installing (required for openfoam installtion)

2019-03-18 Thread mehul

Public bug reported:

To use OpenFOAM in windows I have to install OpenFOAM in WSL(windows
subsystem for Linux)

OpenFOAM is highly depended on libXt-dev version 1.1.5_1, while direct
installing it from the terminal or from synaptic package manager it
gives me a hash mismatch error.

so I try to install it with downloading .deb file from the Ubuntu
repository but it gives me a lzma error telling that archive is corrupt.

so please help to install these packages; so, I can install OpenFOAM and
continue my work.

Thanks.

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

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

Title:
  WSL give error in installing (required for openfoam installtion)

Status in libxt package in Ubuntu:
  New

Bug description:
  To use OpenFOAM in windows I have to install OpenFOAM in WSL(windows
  subsystem for Linux)

  OpenFOAM is highly depended on libXt-dev version 1.1.5_1, while direct
  installing it from the terminal or from synaptic package manager it
  gives me a hash mismatch error.

  so I try to install it with downloading .deb file from the Ubuntu
  repository but it gives me a lzma error telling that archive is
  corrupt.

  so please help to install these packages; so, I can install OpenFOAM
  and continue my work.

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libxt/+bug/1820691/+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 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove

Yes, thanks!

The output of apt list --autoremovable would be useful as well.

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

Title:
  /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-
  upgrade@1991:main:do_auto_remove

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Confirmed

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.1ubuntu1.18.04.5, the problem page at 
https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e 
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/1795696/+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 1820685] [NEW] Wrong resolution during boot

2019-03-18 Thread Bart van Pelt

Public bug reported:

When booting the startup screen is in low resolution while before it was
in high resolution.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
Uname: Linux 4.15.0-46-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
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 18 18:04:57 2019
DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed
GraphicsCard:
 NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b]
InstallationDate: Installed on 2018-01-04 (437 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: ASUSTeK COMPUTER INC. CM6870
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago)
dmi.bios.date: 12/25/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0708
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: CM6870
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: Rev X.0x
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0708:bd12/25/2012:svnASUSTeKCOMPUTERINC.:pnCM6870:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnCM6870:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.family: Desktop
dmi.product.name: CM6870
dmi.product.version: System Version
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.2
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:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Wed Sep 26 20:09:04 2018
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4~16.04.1
xserver.video_driver: nouveau

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


** Tags: amd64 apport-bug bionic resolution 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/1820685

Title:
  Wrong resolution during boot

Status in xorg package in Ubuntu:
  New

Bug description:
  When booting the startup screen is in low resolution while before it
  was in high resolution.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Uname: Linux 4.15.0-46-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
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Mar 18 18:04:57 2019
  DistUpgraded: 2018-09-26 21:31:06,974 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-46-generic, x86_64: installed
  GraphicsCard:
   NVIDIA Corporation GF108 [GeForce GT 530] [10de:0de5] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GF108 [GeForce GT 530] [1043:839b]
  InstallationDate: Installed on 2018-01-04 (437 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: ASUSTeK COMPUTER INC. CM6870
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-46-generic 
root=UUID=4aa7afed-ca87-4f94-9a08-c806fccfbd1d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to bionic on 2018-09-26 (172 days ago)
  dmi.bios.date: 12/25/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0708
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: CM6870
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type:

[Touch-packages] [Bug 1819487] Re: sshd crashed on s390x with hw crypto enabled

2019-03-18 Thread Frank Heimes

** Changed in: openssl-ibmca (Ubuntu)
   Status: New => Fix Committed

** Changed in: ubuntu-z-systems
   Status: Triaged => Fix Committed

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

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

Title:
  sshd crashed on s390x with hw crypto enabled

Status in Ubuntu on IBM z Systems:
  Fix Committed
Status in openssh package in Ubuntu:
  Invalid
Status in openssl-ibmca package in Ubuntu:
  Fix Committed

Bug description:
  While using today's daily image of disco (either in z/VM or on LPAR)
  and enabling s309x hardware crypto support in openssh, sshd crashes
  with the following messages:

  $ ssh ubuntu@localhost
  The authenticity of host 'localhost (::1)' can't be established.
  ECDSA key fingerprint is SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
  ubuntu@localhost's password:
  packet_write_wait: Connection to ::1 port 22: Broken pipe
  (local session is sufficient to reproduce)

  Steps to reproduce - on disco daily:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  Codename: disco
  $ uname -a
  Linux zlin42 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:25:21 UTC 2019 s390x 
s390x s390x GNU/Linux

  - enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  - sudo apt-get install openssl-ibmca libica-utils libica3
  - sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  - sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' 
/etc/ssl/openssl.cnf
  - sudo sed -i '10i openssl_conf = openssl_def' /etc/ssl/openssl.cnf
  - afterwards ssh login attempts fail (existing session are unaffected):
     $ ssh ubuntu@localhost
     The authenticity of host 'localhost (::1)' can't be established.
     ECDSA key fingerprint is 
SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
     Are you sure you want to continue connecting (yes/no)? yes
     Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
     ubuntu@localhost's password:
     packet_write_wait: Connection to ::1 port 22: Broken pipe

  [94629.032586] User process fault: interruption code 003b ilc:2 in 
libpthread-2.29.so[3ff7d48+1c000]
  [94629.032597] Failing address:  TEID: 0800
  [94629.032598] Fault in primary space mode while using user ASCE.
  [94629.032601] AS:0007450281c7 R3:0024
  [94629.032606] CPU: 0 PID: 8183 Comm: sshd Not tainted 5.0.0-7-generic 
#8-Ubuntu
  [94629.032607] Hardware name: IBM 2964 N63 400 (LPAR)
  [94629.032608] User PSW : 070520018000 03ff7d48e954
  [94629.032610]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
RI:0 EA:3
  [94629.032611] User GPRS:    
03ff7e0085c8
  [94629.032612]03ff7e510108 03ff7db1c3a8  
03fff857eea0
  [94629.032613]03ff7e525040 02aa3f5ec090 03ff7e4916f0 
03ff7e4921a8
  [94629.032614]03ff7db17c18 0002 03ff7e07238a 
03fff857ea20
  [94629.032622] User Code: 03ff7d48e946: b9040012  lgr %r1,%r2
    03ff7d48e94a: e3f0ff60ff71  lay 
%r15,-160(%r15)
   #03ff7d48e950: 4700  bc  0,0
   >03ff7d48e954: 58202018  l   
%r2,24(%r2)
    03ff7d48e958: b24f00b0  ear %r11,%a0
    03ff7d48e95c: ebbb002d  sllg
%r11,%r11,32
    03ff7d48e962: b24f00b1  ear %r11,%a1
    03ff7d48e966: 5920b0d0  c   
%r2,208(%r11)
  [94629.032634] Last Breaking-Event-Address:
  [94629.032638]  [<03ff7df773b4>] 0x3ff7df773b4

  For more details see attachments ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: s390x
  DistroRelease: Ubuntu 19.04
  Package: openssh-server 1:7.9p1-9
  PackageArchitecture: s390x
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code -11:
  Tags:  disco
  Uname: Linux 5.0.0-7-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: pkcs11
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1819487/+subscriptions

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

[Touch-packages] [Bug 1818282] Re: systemd-networkd - RoutingPolicyRule does not apply correctly

This bug was fixed in the package systemd - 240-6ubuntu2

---
systemd (240-6ubuntu2) disco; urgency=medium

  * d/p/network-remove-routing-policy-rule-from-foreign-rule.patch
  * d/p/network-do-not-remove-rule-when-it-is-requested-by-e.patch
- Fix RoutingPolicyRule does not apply correctly (LP: #1818282)

 -- Ioanna Alifieraki   Mon, 04
Mar 2019 10:32:19 +

** Changed in: systemd (Ubuntu Disco)
   Status: Fix Committed => Fix Released

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

Title:
  systemd-networkd - RoutingPolicyRule does not apply correctly

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  In Progress
Status in systemd source package in Cosmic:
  In Progress
Status in systemd source package in Disco:
  Fix Released
Status in systemd package in Debian:
  New

Bug description:
  [Impact]

  When attaching multiple IPs on secondary interface the routing policy rules 
do not
  apply for all IPs.
  The rules that are applied after restarting networkd are random.

  The issue has been reported and addressed upstream.

  [Test Case]

  Attach multiple IPs to secondary interface, config file:

  $ cat /etc/systemd/network/ens8.network
  [Match]
  Name=ens8

  [Network]
  Address=172.31.28.195/20
  Address=172.31.24.151/20
  Address=172.31.24.152/20
  Address=172.31.24.153/20

  [Route]
  Destination=0.0.0.0/0
  Gateway=172.31.16.1
  Table=1000

  [Route]
  Destination=172.31.24.153
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.28.195
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.151
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [Route]
  Destination=172.31.24.152
  Gateway=0.0.0.0
  Scope=link
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.153
  Table=1000

  [RoutingPolicyRule]
  From=172.31.28.195
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.152
  Table=1000

  [RoutingPolicyRule]
  From=172.31.24.151
  Table=1000

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart networkd

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.153 lookup 1000
  0:from 172.31.28.195 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  - restart again

  $ sudo systemctl restart systemd-networkd

  $ ip rule show
  0:from all lookup local
  0:from 172.31.24.151 lookup 1000
  0:from 172.31.24.152 lookup 1000
  32766:from all lookup main
  32767:from all lookup default

  The behaviour is random

  [Regression Potential]

  May impact the systemd-networkd service functionality.

  [Other]

  Affects Disco Bionic and Cosmic.

  Upstream bug : https://github.com/systemd/systemd/issues/11280
  Upstream fix : https://github.com/systemd/systemd/pull/11795/commits

  $ lsb_release -rd
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04

  Systemd version :
  systemd:
    Installed: 240-6ubuntu1
    Candidate: 240-6ubuntu1
    Version table:
   *** 240-6ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
  100 /var/lib/dpkg/status

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1818282/+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 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove

Luckily I found an older machine I didn't fix manually today :)

[...]
check_conffile_prompt(/var/cache/apt/archives/gnupg2_2.2.4-1ubuntu1.2_all.deb)
found pkg: gnupg2
No conffiles in deb /var/cache/apt/archives/gnupg2_2.2.4-1ubuntu1.2_all.deb 
(There is no member named 'conffiles')
blacklist: []
whitelist: []
Removing unused kernel packages: linux-modules-4.15.0-36-generic 
linux-image-4.15.0-36-generic linux-headers-4.15.0-36-generic 
linux-modules-extra-4.15.0-36-generic linux-headers-4.15.0-36
Keeping 5 auto-removable package(s) because it would also remove the following 
packages which should be kept in this step: apt apt-transport-https apt-utils 
avahi-autoipd avahi-daemon avahi-utils bind9-host chromium-browser 
chromium-browser-l10n chromium-codecs-ffmpeg cups cups-bsd cups-client 
cups-common cups-core-drivers cups-daemon cups-ipp-utils cups-ppdc 
cups-server-common dnsutils file firefox firefox-locale-en gdm3 ghostscript 
ghostscript-x gir1.2-gdm-1.0 gir1.2-gnomebluetooth-1.0 gir1.2-gnomedesktop-3.0 
gir1.2-javascriptcoregtk-4.0 gir1.2-polkit-1.0 gir1.2-webkit2-4.0 
gnome-bluetooth gnome-desktop3-data gnupg-agent gnupg2 gvfs gvfs-backends 
gvfs-bin gvfs-common gvfs-daemons gvfs-fuse gvfs-libs initramfs-tools 
initramfs-tools-bin initramfs-tools-core krb5-locales libapt-inst2.0 
libapt-pkg5.0 libarchive13 libavahi-client3 libavahi-common-data 
libavahi-common3 libavahi-core7 libavahi-glib1 libavahi-ui-gtk3-0 libbind9-160 
libcaca0 libconfuse-common libconfuse2 libcups2 libcupscgi1 libcupsimage2 
libcupsmime1 libcupsppdc1 libcurl3-gnutls libdns-export1100 libdns1100 
libexiv2-14 libfreerdp-client2-2 libfreerdp2-2 libgd3 libgdm1 
libgnome-bluetooth13 libgnome-desktop-3-17 libgs9 libgs9-common 
libgssapi-krb5-2 libirs160 libisc-export169 libisc169 libisccc160 libisccfg160 
libjavascriptcoregtk-4.0-18 libk5crypto3 libkrb5-3 libkrb5support0 libldb1 
liblwres160 libmagic-mgc libmagic1 libnss-myhostname libnss-systemd libnss3 
libpam-systemd libpolkit-agent-1-0 libpolkit-backend-1-0 libpolkit-gobject-1-0 
libpoppler-glib8 libpoppler73 libraw16 libssl1.0.0 libssl1.1 libsystemd0 
libtiff5 libu2f-udev libudev1 libvncclient1 libwavpack1 libwebkit2gtk-4.0-37 
libwebkit2gtk-4.0-37-gtk2 libwinpr2-2 libzmq5 linux-firmware linux-generic 
linux-generic-hwe-16.04 linux-headers-4.15.0-46 linux-headers-4.15.0-46-generic 
linux-headers-generic linux-image-4.15.0-46-generic linux-image-generic 
linux-libc-dev linux-modules-4.15.0-46-generic 
linux-modules-extra-4.15.0-46-generic nplan openjdk-8-jdk 
openjdk-8-jdk-headless openjdk-8-jre openjdk-8-jre-headless openssl policykit-1 
poppler-utils python-ldb python3-lxml snapd systemd systemd-sysv thunderbird 
thunderbird-gnome-support thunderbird-locale-en thunderbird-locale-en-us tzdata 
ubuntu-core-launcher udev
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1998, in 
sys.exit(main(options))
  File "/usr/bin/unattended-upgrade", line 1798, in main
options.verbose or options.debug, options.dry_run)
  File "/usr/bin/unattended-upgrade", line 1495, in do_auto_remove
if res:
UnboundLocalError: local variable 'res' referenced before assignment
Error in atexit._run_exitfuncs:
FileNotFoundError: [Errno 2] No such file or directory: 
'/var/run/unattended-upgrades.pid'



Does that help already?

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

Title:
  /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-
  upgrade@1991:main:do_auto_remove

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Confirmed

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.1ubuntu1.18.04.5, the problem page at 
https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e 
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/1795696/+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 1819615] Re: For additional hardware support, modemmanager needs to be upgraded to 1.10 on Bionic

** Description changed:

+ [Impact]
+ 
+  * The new modemmanager package adds DW5820e support.
+  * This modemmanager version is needed to support new devices.
+ 
+ [Test Case]
+ 
+  * install modemmanager, libmbim, and libqmi from -proposed
+  * reboot and try WWAN function to see if any regression there.
+  * perform general dogfooding of its reverse dependencies (network-
+manager, gnome-control-center etc.)
+ 
+ [Regression Potential]
+ 
+  * The package comes from Zesty and should not have regression there.
+  * Every new upstream release can potentially break existing dependencies 
+if any of the required features have been changed/removed, so besides 
+regular testing a general dogfooding session with the new modemmanager 
+is advised.
+ 
+ [Original Description]
+ 
  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

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

Title:
  For additional hardware support, modemmanager needs to be upgraded to
  1.10 on Bionic

Status in libmbim package in Ubuntu:
  Fix Released
Status in libqmi package in Ubuntu:
  Fix Released
Status in modemmanager package in Ubuntu:
  Fix Released
Status in libmbim source package in Bionic:
  In Progress
Status in libqmi source package in Bionic:
  In Progress
Status in modemmanager source package in Bionic:
  In Progress

Bug description:
  [Impact]

   * The new modemmanager package adds DW5820e support.
   * This modemmanager version is needed to support new devices.

  [Test Case]

   * install modemmanager, libmbim, and libqmi from -proposed
   * reboot and try WWAN function to see if any regression there.
   * perform general dogfooding of its reverse dependencies (network-
 manager, gnome-control-center etc.)

  [Regression Potential]

   * The package comes from Zesty and should not have regression there.
   * Every new upstream release can potentially break existing dependencies 
 if any of the required features have been changed/removed, so besides 
 regular testing a general dogfooding session with the new modemmanager 
 is advised.

  [Original Description]

  To have Bionic, the current LTS, working with as wide of a range of
  modems as possible we need to have it upgraded to the current 1.10
  versions. Also the underlying libraries need to get upgraded
  appropriately.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libmbim/+bug/1819615/+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 1817627] Re: systemd-analyze verify reports failure

2019-03-18 Thread Karlis

I use separate mountpoint for /tmp directory and also am affected by
this issue on latest Ubuntu 18.04.2 with all package updates installed.

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

Title:
  systemd-analyze verify reports failure

Status in Ubuntu Manpage Repository:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Version 237 and 238 of systemd-analyze have a known issue:
  https://github.com/systemd/systemd/issues/8592

  When will a fix be posted?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1817627/+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 1817627] Re: systemd-analyze verify reports failure

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

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

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

Title:
  systemd-analyze verify reports failure

Status in Ubuntu Manpage Repository:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Version 237 and 238 of systemd-analyze have a known issue:
  https://github.com/systemd/systemd/issues/8592

  When will a fix be posted?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-manpage-repository/+bug/1817627/+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 1818253] Re: 18.10 when lid closed and opened again no keyboard

2019-03-18 Thread silvagroup

The previously posted log was from this nightmare:

This is a major bug in this regard, my system was totally unusable for
an hour.

Had a phone call had to attend to and some items related top that,
system turned off screen when I finally got back to my system, could not
use the keyboard, touch screen was unresponsive, on screen keyboard
would not activate, on board touch pad was unresponsive, Bluetooth mouse
moved but clicks were unresponsive, even power button was unresponsive,
again after an hour of messing with things was lucky enough to get an
occasional touch screen keyboard and was finally able to a terminal and
after 15 trying to get a touch screen keyboard was able to reboot.

This is a very serious regression, this worked absolutely great in
18.04.

Sorry it appear I haven't provided a log before this, but I did, didn't
realize that for some reason the log and my detailed explanation of
events actually wasn't posted.

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

Title:
  18.10 when lid closed and opened again no keyboard

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

Bug description:
  Using Dell Inspiron 7000 w/Intel corei7.
  With 18.04 power settings had options for what to do when lid was closed.
  Now available with Gnome-tweak in 18.10.
  However does not work correctly. 

  Did Google search happening to others as well especially with detach
  keyboards which is not my case.

  With 18.10 and tweak setting to suspend when lid closed, the system
  does suspend, however when lid is closed it appears that the on board
  keyboard gets totally dropped when lid is opened back up.

  Have to use touch screen to switch user, then touch screen again at
  login to get a screen keyboard,  sometimes I get the on board keyboard
  back, usually have to reboot to get on on board keyboard back.

  If I power off or restart keyboard works fine.

  Definite regression this has worked for several older versions of
  Ubuntu, at least on this system.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818253/+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 1560286] Re: Evince displays pdf file fine, but prints colors inverted

The previous has the right color onces 1.15.12-1ubuntu0.1 installed on
cosmic, marked cosmic verified as well now

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

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

Title:
  Evince displays pdf file fine, but prints colors inverted

Status in cairo package in Ubuntu:
  Fix Released
Status in cairo source package in Bionic:
  Fix Released
Status in cairo source package in Cosmic:
  Fix Committed

Bug description:
  * Impact
  In some files images are printed with inverted colors

  * Test case
  open 
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+attachment/5226857/+files/978-1-57896-287-7%20LL4%20SW%20Sem%201%20Reduced%20p.17.pdf
 in evince, click on the print preview, the colors should be right

  * Regression potential
  it's a change in the code dealing with specific adobe file, test opening the 
example in different document viewer and try with some other files (the bug has 
several example), they should display the correct image/colors

  

  I have several pdf files that when opened by evince, they appear to be fine 
until I try to print them.  When I do, they print with the colors inverted (the 
printout looks like a photograph negative).  This color inversion also occurs 
when viewed in the print preview screen.  If I click on File > Properties, I 
get some information...
  Producer : Adobe Acrobat 15.10 Image Conversion Plug-in
  Creator : Adobe Acrobat 15.10
  ...
  Format : PDF-1.6
  ...

  I am running ubuntu 14.04 LTS

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: evince 3.10.3-0ubuntu10.2
  ProcVersionSignature: Ubuntu 3.13.0-83.127-generic 3.13.11-ckt35
  Uname: Linux 3.13.0-83-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.14.1-0ubuntu3.19
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Mar 21 21:01:45 2016
  ExecutablePath: /usr/bin/evince
  InstallationDate: Installed on 2012-07-24 (1336 days ago)
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: evince
  UpgradeStatus: Upgraded to trusty on 2014-09-29 (539 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cairo/+bug/1560286/+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 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove

@mk-uone No, but up to this point no one reported this bug re-occuring. Thank 
you for your additional info.
Could you please debug how u-u fails on you system by running u-u --verbose 
--debug while I prepare the backport?

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

Title:
  /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-
  upgrade@1991:main:do_auto_remove

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Confirmed

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.1ubuntu1.18.04.5, the problem page at 
https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e 
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/1795696/+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 1820614] Re: Mail notification's headlines do not mention autoremovals

2019-03-18 Thread Bug Watch Updater

** Changed in: unattended-upgrades (Debian)
   Status: Unknown => Fix Released

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

Title:
  Mail notification's headlines do not mention autoremovals

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Debian:
  Fix Released

Bug description:
  We run unattended-upgrades happily with 'Unattended-Upgrade::Mail'
  active and 'Unattended-Upgrade::Remove-Unused-Dependencies'

  Sometimes a UU run would not install nor hold anything, but only
  autoremove packages that have become obsolete, typically old kernels.
  In such cases, UU's mail notification reads:

  """
   Unattended upgrade returned: True
   
   Warning: A reboot is required to complete this upgrade.

   Packages that were upgraded:
   
   Package installation log:
   [...]
  """

  Which is quite irritating.

  It would be very helpful if it also contained a line "Packages that
  were (auto-)removed:"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1820614/+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 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove

> The overall effect seems to be installing security updates one day
later in some rare cases.

Are you sure about that?

root@lab:~# journalctl  | grep -i unbound
[...]
Mar 01 06:33:17 lab apt.systemd.daily[4984]: UnboundLocalError: local variable 
'res' referenced before assignment
Mar 02 06:17:17 lab apt.systemd.daily[15459]: UnboundLocalError: local variable 
'res' referenced before assignment
Mar 03 06:37:37 lab apt.systemd.daily[25767]: UnboundLocalError: local variable 
'res' referenced before assignment
Mar 04 06:42:43 lab apt.systemd.daily[3280]: UnboundLocalError: local variable 
'res' referenced before assignment
Mar 05 06:46:11 lab apt.systemd.daily[16970]: UnboundLocalError: local variable 
'res' referenced before assignment
Mar 06 06:13:43 lab apt.systemd.daily[30101]: UnboundLocalError: local variable 
'res' referenced before assignment
Mar 07 06:08:17 lab apt.systemd.daily[10414]: UnboundLocalError: local variable 
'res' referenced before assignment
Mar 08 06:25:43 lab apt.systemd.daily[23872]: UnboundLocalError: local variable 
'res' referenced before assignment
Mar 09 06:34:18 lab apt.systemd.daily[4459]: UnboundLocalError: local variable 
'res' referenced before assignment
Mar 10 06:02:57 lab apt.systemd.daily[15978]: UnboundLocalError: local variable 
'res' referenced before assignment
Mar 11 06:36:01 lab apt.systemd.daily[29894]: UnboundLocalError: local variable 
'res' referenced before assignment

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

Title:
  /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-
  upgrade@1991:main:do_auto_remove

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Confirmed

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.1ubuntu1.18.04.5, the problem page at 
https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e 
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/1795696/+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 1819487] Re: sshd crashed on s390x with hw crypto enabled

2019-03-18 Thread Frank Heimes

I just verified the updated package:
$ apt-cache policy openssl-ibmca
openssl-ibmca:
  Installed: 2.0.2-0ubuntu2
  Candidate: 2.0.2-0ubuntu2
  Version table:
 *** 2.0.2-0ubuntu2 100
100 /var/lib/dpkg/status
 2.0.2-0ubuntu1 500
500 http://us.ports.ubuntu.com/ubuntu-ports disco/universe s390x 
Packages
and it looks like it fixes the problem.
With this package installed and hw crypto enabled,
I can again remotely (and locally) login again into that disco system w/o a 
sshd crash.
Thanks!

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

Title:
  sshd crashed on s390x with hw crypto enabled

Status in Ubuntu on IBM z Systems:
  Triaged
Status in openssh package in Ubuntu:
  New
Status in openssl-ibmca package in Ubuntu:
  New

Bug description:
  While using today's daily image of disco (either in z/VM or on LPAR)
  and enabling s309x hardware crypto support in openssh, sshd crashes
  with the following messages:

  $ ssh ubuntu@localhost
  The authenticity of host 'localhost (::1)' can't be established.
  ECDSA key fingerprint is SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
  ubuntu@localhost's password:
  packet_write_wait: Connection to ::1 port 22: Broken pipe
  (local session is sufficient to reproduce)

  Steps to reproduce - on disco daily:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  Codename: disco
  $ uname -a
  Linux zlin42 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:25:21 UTC 2019 s390x 
s390x s390x GNU/Linux

  - enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  - sudo apt-get install openssl-ibmca libica-utils libica3
  - sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  - sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' 
/etc/ssl/openssl.cnf
  - sudo sed -i '10i openssl_conf = openssl_def' /etc/ssl/openssl.cnf
  - afterwards ssh login attempts fail (existing session are unaffected):
     $ ssh ubuntu@localhost
     The authenticity of host 'localhost (::1)' can't be established.
     ECDSA key fingerprint is 
SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
     Are you sure you want to continue connecting (yes/no)? yes
     Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
     ubuntu@localhost's password:
     packet_write_wait: Connection to ::1 port 22: Broken pipe

  [94629.032586] User process fault: interruption code 003b ilc:2 in 
libpthread-2.29.so[3ff7d48+1c000]
  [94629.032597] Failing address:  TEID: 0800
  [94629.032598] Fault in primary space mode while using user ASCE.
  [94629.032601] AS:0007450281c7 R3:0024
  [94629.032606] CPU: 0 PID: 8183 Comm: sshd Not tainted 5.0.0-7-generic 
#8-Ubuntu
  [94629.032607] Hardware name: IBM 2964 N63 400 (LPAR)
  [94629.032608] User PSW : 070520018000 03ff7d48e954
  [94629.032610]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
RI:0 EA:3
  [94629.032611] User GPRS:    
03ff7e0085c8
  [94629.032612]03ff7e510108 03ff7db1c3a8  
03fff857eea0
  [94629.032613]03ff7e525040 02aa3f5ec090 03ff7e4916f0 
03ff7e4921a8
  [94629.032614]03ff7db17c18 0002 03ff7e07238a 
03fff857ea20
  [94629.032622] User Code: 03ff7d48e946: b9040012  lgr %r1,%r2
    03ff7d48e94a: e3f0ff60ff71  lay 
%r15,-160(%r15)
   #03ff7d48e950: 4700  bc  0,0
   >03ff7d48e954: 58202018  l   
%r2,24(%r2)
    03ff7d48e958: b24f00b0  ear %r11,%a0
    03ff7d48e95c: ebbb002d  sllg
%r11,%r11,32
    03ff7d48e962: b24f00b1  ear %r11,%a1
    03ff7d48e966: 5920b0d0  c   
%r2,208(%r11)
  [94629.032634] Last Breaking-Event-Address:
  [94629.032638]  [<03ff7df773b4>] 0x3ff7df773b4

  For more details see attachments ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: s390x
  DistroRelease: Ubuntu 19.04
  Package: openssh-server 1:7.9p1-9
  PackageArchitecture: s390x
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code -11:
  Tags:  disco
  Uname: Linux 5.0.0-7-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

[Touch-packages] [Bug 1819487] Re: sshd crashed on s390x with hw crypto enabled

2019-03-18 Thread Dimitri John Ledkov

This PPA:
https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3681

Will soon have openssl-ibmca with above mentioned patch, built and
published.

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

Title:
  sshd crashed on s390x with hw crypto enabled

Status in Ubuntu on IBM z Systems:
  Triaged
Status in openssh package in Ubuntu:
  New
Status in openssl-ibmca package in Ubuntu:
  New

Bug description:
  While using today's daily image of disco (either in z/VM or on LPAR)
  and enabling s309x hardware crypto support in openssh, sshd crashes
  with the following messages:

  $ ssh ubuntu@localhost
  The authenticity of host 'localhost (::1)' can't be established.
  ECDSA key fingerprint is SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
  ubuntu@localhost's password:
  packet_write_wait: Connection to ::1 port 22: Broken pipe
  (local session is sufficient to reproduce)

  Steps to reproduce - on disco daily:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  Codename: disco
  $ uname -a
  Linux zlin42 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:25:21 UTC 2019 s390x 
s390x s390x GNU/Linux

  - enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  - sudo apt-get install openssl-ibmca libica-utils libica3
  - sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  - sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' 
/etc/ssl/openssl.cnf
  - sudo sed -i '10i openssl_conf = openssl_def' /etc/ssl/openssl.cnf
  - afterwards ssh login attempts fail (existing session are unaffected):
     $ ssh ubuntu@localhost
     The authenticity of host 'localhost (::1)' can't be established.
     ECDSA key fingerprint is 
SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
     Are you sure you want to continue connecting (yes/no)? yes
     Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
     ubuntu@localhost's password:
     packet_write_wait: Connection to ::1 port 22: Broken pipe

  [94629.032586] User process fault: interruption code 003b ilc:2 in 
libpthread-2.29.so[3ff7d48+1c000]
  [94629.032597] Failing address:  TEID: 0800
  [94629.032598] Fault in primary space mode while using user ASCE.
  [94629.032601] AS:0007450281c7 R3:0024
  [94629.032606] CPU: 0 PID: 8183 Comm: sshd Not tainted 5.0.0-7-generic 
#8-Ubuntu
  [94629.032607] Hardware name: IBM 2964 N63 400 (LPAR)
  [94629.032608] User PSW : 070520018000 03ff7d48e954
  [94629.032610]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
RI:0 EA:3
  [94629.032611] User GPRS:    
03ff7e0085c8
  [94629.032612]03ff7e510108 03ff7db1c3a8  
03fff857eea0
  [94629.032613]03ff7e525040 02aa3f5ec090 03ff7e4916f0 
03ff7e4921a8
  [94629.032614]03ff7db17c18 0002 03ff7e07238a 
03fff857ea20
  [94629.032622] User Code: 03ff7d48e946: b9040012  lgr %r1,%r2
    03ff7d48e94a: e3f0ff60ff71  lay 
%r15,-160(%r15)
   #03ff7d48e950: 4700  bc  0,0
   >03ff7d48e954: 58202018  l   
%r2,24(%r2)
    03ff7d48e958: b24f00b0  ear %r11,%a0
    03ff7d48e95c: ebbb002d  sllg
%r11,%r11,32
    03ff7d48e962: b24f00b1  ear %r11,%a1
    03ff7d48e966: 5920b0d0  c   
%r2,208(%r11)
  [94629.032634] Last Breaking-Event-Address:
  [94629.032638]  [<03ff7df773b4>] 0x3ff7df773b4

  For more details see attachments ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: s390x
  DistroRelease: Ubuntu 19.04
  Package: openssh-server 1:7.9p1-9
  PackageArchitecture: s390x
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code -11:
  Tags:  disco
  Uname: Linux 5.0.0-7-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: pkcs11
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1819487/+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 1819487] Re: sshd crashed on s390x with hw crypto enabled

2019-03-18 Thread Dimitri John Ledkov

This cannot be reproduced on 18.10, as on 18.10 openssh uses libssl1.0.0
package, yet openssl-ibmca is provided for libssl1.1 only.

In disco (19.04), openssh has been upgraded to use libssl1.1 with a
matching openssl-ibmca for libssl1.1.

If you want to reproduce this on 18.10, do add 'disco' repository in
/etc/apt/sources.list and upgrade to disco's version of openssh-server.

(note that 19.04 uses newer openssl-ibmca too 2.0.2 vs 2.0.0 which was
in 18.10).

** Also affects: openssl-ibmca (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  sshd crashed on s390x with hw crypto enabled

Status in Ubuntu on IBM z Systems:
  Triaged
Status in openssh package in Ubuntu:
  New
Status in openssl-ibmca package in Ubuntu:
  New

Bug description:
  While using today's daily image of disco (either in z/VM or on LPAR)
  and enabling s309x hardware crypto support in openssh, sshd crashes
  with the following messages:

  $ ssh ubuntu@localhost
  The authenticity of host 'localhost (::1)' can't be established.
  ECDSA key fingerprint is SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
  ubuntu@localhost's password:
  packet_write_wait: Connection to ::1 port 22: Broken pipe
  (local session is sufficient to reproduce)

  Steps to reproduce - on disco daily:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  Codename: disco
  $ uname -a
  Linux zlin42 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:25:21 UTC 2019 s390x 
s390x s390x GNU/Linux

  - enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  - sudo apt-get install openssl-ibmca libica-utils libica3
  - sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  - sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' 
/etc/ssl/openssl.cnf
  - sudo sed -i '10i openssl_conf = openssl_def' /etc/ssl/openssl.cnf
  - afterwards ssh login attempts fail (existing session are unaffected):
     $ ssh ubuntu@localhost
     The authenticity of host 'localhost (::1)' can't be established.
     ECDSA key fingerprint is 
SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
     Are you sure you want to continue connecting (yes/no)? yes
     Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
     ubuntu@localhost's password:
     packet_write_wait: Connection to ::1 port 22: Broken pipe

  [94629.032586] User process fault: interruption code 003b ilc:2 in 
libpthread-2.29.so[3ff7d48+1c000]
  [94629.032597] Failing address:  TEID: 0800
  [94629.032598] Fault in primary space mode while using user ASCE.
  [94629.032601] AS:0007450281c7 R3:0024
  [94629.032606] CPU: 0 PID: 8183 Comm: sshd Not tainted 5.0.0-7-generic 
#8-Ubuntu
  [94629.032607] Hardware name: IBM 2964 N63 400 (LPAR)
  [94629.032608] User PSW : 070520018000 03ff7d48e954
  [94629.032610]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
RI:0 EA:3
  [94629.032611] User GPRS:    
03ff7e0085c8
  [94629.032612]03ff7e510108 03ff7db1c3a8  
03fff857eea0
  [94629.032613]03ff7e525040 02aa3f5ec090 03ff7e4916f0 
03ff7e4921a8
  [94629.032614]03ff7db17c18 0002 03ff7e07238a 
03fff857ea20
  [94629.032622] User Code: 03ff7d48e946: b9040012  lgr %r1,%r2
    03ff7d48e94a: e3f0ff60ff71  lay 
%r15,-160(%r15)
   #03ff7d48e950: 4700  bc  0,0
   >03ff7d48e954: 58202018  l   
%r2,24(%r2)
    03ff7d48e958: b24f00b0  ear %r11,%a0
    03ff7d48e95c: ebbb002d  sllg
%r11,%r11,32
    03ff7d48e962: b24f00b1  ear %r11,%a1
    03ff7d48e966: 5920b0d0  c   
%r2,208(%r11)
  [94629.032634] Last Breaking-Event-Address:
  [94629.032638]  [<03ff7df773b4>] 0x3ff7df773b4

  For more details see attachments ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: s390x
  DistroRelease: Ubuntu 19.04
  Package: openssh-server 1:7.9p1-9
  PackageArchitecture: s390x
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code -11:
  Tags:  disco
  Uname: Linux 5.0.0-7-generic s390x
  UpgradeStatus: No upgrade log present

[Touch-packages] [Bug 1820509] Re: Avoid use-after-free in _XimProtoSetIMValues()

2019-03-18 Thread Matthias Dieter Wallnöfer

Unfortunately I just stumbled over this commit by accident since I
checked the commit log of libX11. So for a reproduction we would need to
contact the original reporter Sami Farin
(https://bugs.freedesktop.org/show_bug.cgi?id=93186) but I do not find
any valid email address from him.

** Bug watch added: freedesktop.org Bugzilla #93186
   https://bugs.freedesktop.org/show_bug.cgi?id=93186

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

Title:
  Avoid use-after-free in _XimProtoSetIMValues()

Status in libx11 package in Ubuntu:
  New

Bug description:
  I think that the patch
  
https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad
  (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49)
  should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04
  LTS Bionic.

  Although it didn't get an explicit CVS, use-after-free scenarios
  should not get underestimated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1820509/+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 1820614] Re: Mail notification's headlines do not mention autoremovals

The fix is also in the next update in xenial-proposed:

https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
/autopkgtest-xenial/xenial/amd64/u/unattended-
upgrades/20190228_150449_11313@/log.gz

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

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Fix Released

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

Title:
  Mail notification's headlines do not mention autoremovals

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades package in Debian:
  Unknown

Bug description:
  We run unattended-upgrades happily with 'Unattended-Upgrade::Mail'
  active and 'Unattended-Upgrade::Remove-Unused-Dependencies'

  Sometimes a UU run would not install nor hold anything, but only
  autoremove packages that have become obsolete, typically old kernels.
  In such cases, UU's mail notification reads:

  """
   Unattended upgrade returned: True
   
   Warning: A reboot is required to complete this upgrade.

   Packages that were upgraded:
   
   Package installation log:
   [...]
  """

  Which is quite irritating.

  It would be very helpful if it also contained a line "Packages that
  were (auto-)removed:"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1820614/+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 1819487] Re: sshd crashed on s390x with hw crypto enabled

2019-03-18 Thread Frank Heimes

$ sudo lszcrypt -b
ap_domain=0xc
ap_max_domain_id=0x54
ap_interrupts are enabled
config_time=30 (seconds)
poll_thread is disabled
poll_timeout=25 (nanoseconds)

$ sudo lszcrypt -V
CARD.DOMAIN TYPE  MODESTATUS  REQUESTS  PENDING HWTYPE QDEPTH FUNCTIONS 
 DRIVER 

00  CEX5C CCA-Coproc  online1000160 11 08 S--D--N-- 
 cex4card   
00.000c CEX5C CCA-Coproc  online1000160 11 08 S--D--N-- 
 cex4queue

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

Title:
  sshd crashed on s390x with hw crypto enabled

Status in Ubuntu on IBM z Systems:
  Triaged
Status in openssh package in Ubuntu:
  New
Status in openssl-ibmca package in Ubuntu:
  New

Bug description:
  While using today's daily image of disco (either in z/VM or on LPAR)
  and enabling s309x hardware crypto support in openssh, sshd crashes
  with the following messages:

  $ ssh ubuntu@localhost
  The authenticity of host 'localhost (::1)' can't be established.
  ECDSA key fingerprint is SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
  ubuntu@localhost's password:
  packet_write_wait: Connection to ::1 port 22: Broken pipe
  (local session is sufficient to reproduce)

  Steps to reproduce - on disco daily:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  Codename: disco
  $ uname -a
  Linux zlin42 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:25:21 UTC 2019 s390x 
s390x s390x GNU/Linux

  - enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  - sudo apt-get install openssl-ibmca libica-utils libica3
  - sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  - sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' 
/etc/ssl/openssl.cnf
  - sudo sed -i '10i openssl_conf = openssl_def' /etc/ssl/openssl.cnf
  - afterwards ssh login attempts fail (existing session are unaffected):
     $ ssh ubuntu@localhost
     The authenticity of host 'localhost (::1)' can't be established.
     ECDSA key fingerprint is 
SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
     Are you sure you want to continue connecting (yes/no)? yes
     Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
     ubuntu@localhost's password:
     packet_write_wait: Connection to ::1 port 22: Broken pipe

  [94629.032586] User process fault: interruption code 003b ilc:2 in 
libpthread-2.29.so[3ff7d48+1c000]
  [94629.032597] Failing address:  TEID: 0800
  [94629.032598] Fault in primary space mode while using user ASCE.
  [94629.032601] AS:0007450281c7 R3:0024
  [94629.032606] CPU: 0 PID: 8183 Comm: sshd Not tainted 5.0.0-7-generic 
#8-Ubuntu
  [94629.032607] Hardware name: IBM 2964 N63 400 (LPAR)
  [94629.032608] User PSW : 070520018000 03ff7d48e954
  [94629.032610]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
RI:0 EA:3
  [94629.032611] User GPRS:    
03ff7e0085c8
  [94629.032612]03ff7e510108 03ff7db1c3a8  
03fff857eea0
  [94629.032613]03ff7e525040 02aa3f5ec090 03ff7e4916f0 
03ff7e4921a8
  [94629.032614]03ff7db17c18 0002 03ff7e07238a 
03fff857ea20
  [94629.032622] User Code: 03ff7d48e946: b9040012  lgr %r1,%r2
    03ff7d48e94a: e3f0ff60ff71  lay 
%r15,-160(%r15)
   #03ff7d48e950: 4700  bc  0,0
   >03ff7d48e954: 58202018  l   
%r2,24(%r2)
    03ff7d48e958: b24f00b0  ear %r11,%a0
    03ff7d48e95c: ebbb002d  sllg
%r11,%r11,32
    03ff7d48e962: b24f00b1  ear %r11,%a1
    03ff7d48e966: 5920b0d0  c   
%r2,208(%r11)
  [94629.032634] Last Breaking-Event-Address:
  [94629.032638]  [<03ff7df773b4>] 0x3ff7df773b4

  For more details see attachments ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: s390x
  DistroRelease: Ubuntu 19.04
  Package: openssh-server 1:7.9p1-9
  PackageArchitecture: s390x
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code -11:
  Tags:  disco
  Uname: Linux 5.0.0-7-generic s390x
  UpgradeStatus: No upgrade log

[Touch-packages] [Bug 1789642] Re: Nautilus highlights new filename without focusing input field.

Thanks, that's not a bug then. When you click navigate the directories,
the focus ring around the filename entry is removed which indicates well
that the focus has been moved away to the disk navifation part of the
dialog. The filename remains selected because it makes sense to keep the
state for when you focus that wideget again. There is nothing here not
working as intended, that's not a bug

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

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

Title:
  Nautilus highlights new filename without focusing input field.

Status in gtk+3.0 package in Ubuntu:
  Invalid

Bug description:
  Opening nautilus in order to save picture from e.g. browser does so
  the name of the new file is highlighted but the focus is not on the
  input field. I expect when the name is highlighted that it is also
  focused.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 14:18:08 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'931x720+331+141'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'false'
  InstallationDate: Installed on 2018-03-08 (173 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (123 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1789642/+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 1819487] Comment bridged from LTC Bugzilla

2019-03-18 Thread bugproxy

--- Comment From fre...@de.ibm.com 2019-03-18 10:31 EDT---
I am unable to recreate this on Ubuntu 18.10. However, I reviewed the 
destructor code in ibmca and found some code which could be the reason.
So I'll give you a patch for checking - just a shot in the dark...

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

Title:
  sshd crashed on s390x with hw crypto enabled

Status in Ubuntu on IBM z Systems:
  Triaged
Status in openssh package in Ubuntu:
  New

Bug description:
  While using today's daily image of disco (either in z/VM or on LPAR)
  and enabling s309x hardware crypto support in openssh, sshd crashes
  with the following messages:

  $ ssh ubuntu@localhost
  The authenticity of host 'localhost (::1)' can't be established.
  ECDSA key fingerprint is SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
  ubuntu@localhost's password:
  packet_write_wait: Connection to ::1 port 22: Broken pipe
  (local session is sufficient to reproduce)

  Steps to reproduce - on disco daily:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  Codename: disco
  $ uname -a
  Linux zlin42 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:25:21 UTC 2019 s390x 
s390x s390x GNU/Linux

  - enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  - sudo apt-get install openssl-ibmca libica-utils libica3
  - sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  - sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' 
/etc/ssl/openssl.cnf
  - sudo sed -i '10i openssl_conf = openssl_def' /etc/ssl/openssl.cnf
  - afterwards ssh login attempts fail (existing session are unaffected):
     $ ssh ubuntu@localhost
     The authenticity of host 'localhost (::1)' can't be established.
     ECDSA key fingerprint is 
SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
     Are you sure you want to continue connecting (yes/no)? yes
     Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
     ubuntu@localhost's password:
     packet_write_wait: Connection to ::1 port 22: Broken pipe

  [94629.032586] User process fault: interruption code 003b ilc:2 in 
libpthread-2.29.so[3ff7d48+1c000]
  [94629.032597] Failing address:  TEID: 0800
  [94629.032598] Fault in primary space mode while using user ASCE.
  [94629.032601] AS:0007450281c7 R3:0024
  [94629.032606] CPU: 0 PID: 8183 Comm: sshd Not tainted 5.0.0-7-generic 
#8-Ubuntu
  [94629.032607] Hardware name: IBM 2964 N63 400 (LPAR)
  [94629.032608] User PSW : 070520018000 03ff7d48e954
  [94629.032610]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
RI:0 EA:3
  [94629.032611] User GPRS:    
03ff7e0085c8
  [94629.032612]03ff7e510108 03ff7db1c3a8  
03fff857eea0
  [94629.032613]03ff7e525040 02aa3f5ec090 03ff7e4916f0 
03ff7e4921a8
  [94629.032614]03ff7db17c18 0002 03ff7e07238a 
03fff857ea20
  [94629.032622] User Code: 03ff7d48e946: b9040012  lgr %r1,%r2
    03ff7d48e94a: e3f0ff60ff71  lay 
%r15,-160(%r15)
   #03ff7d48e950: 4700  bc  0,0
   >03ff7d48e954: 58202018  l   
%r2,24(%r2)
    03ff7d48e958: b24f00b0  ear %r11,%a0
    03ff7d48e95c: ebbb002d  sllg
%r11,%r11,32
    03ff7d48e962: b24f00b1  ear %r11,%a1
    03ff7d48e966: 5920b0d0  c   
%r2,208(%r11)
  [94629.032634] Last Breaking-Event-Address:
  [94629.032638]  [<03ff7df773b4>] 0x3ff7df773b4

  For more details see attachments ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: s390x
  DistroRelease: Ubuntu 19.04
  Package: openssh-server 1:7.9p1-9
  PackageArchitecture: s390x
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code -11:
  Tags:  disco
  Uname: Linux 5.0.0-7-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: pkcs11
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1819487/+subscriptions

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

[Touch-packages] [Bug 1819487] ibmca rework on error string init and exit

2019-03-18 Thread bugproxy

--- Comment on attachment From fre...@de.ibm.com 2019-03-18 10:34 EDT---


Here is an attempt to maybe fix the issue.
Can you please apply this on top of the ibmca code, build and test ?

Btw. some info about your crypto config would also help me to try to
recreate this. Just an lszcrypt -V output would be fine.

Thanks
Harald Freudenberger

** Attachment added: "ibmca rework on error string init and exit"
   
https://bugs.launchpad.net/bugs/1819487/+attachment/5247283/+files/0001-ibmca-rework-on-error-string-init-and-exit.patch

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

Title:
  sshd crashed on s390x with hw crypto enabled

Status in Ubuntu on IBM z Systems:
  Triaged
Status in openssh package in Ubuntu:
  New

Bug description:
  While using today's daily image of disco (either in z/VM or on LPAR)
  and enabling s309x hardware crypto support in openssh, sshd crashes
  with the following messages:

  $ ssh ubuntu@localhost
  The authenticity of host 'localhost (::1)' can't be established.
  ECDSA key fingerprint is SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
  Are you sure you want to continue connecting (yes/no)? yes
  Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
  ubuntu@localhost's password:
  packet_write_wait: Connection to ::1 port 22: Broken pipe
  (local session is sufficient to reproduce)

  Steps to reproduce - on disco daily:

  $ lsb_release -a
  No LSB modules are available.
  Distributor ID:   Ubuntu
  Description:  Ubuntu Disco Dingo (development branch)
  Release:  19.04
  Codename: disco
  $ uname -a
  Linux zlin42 5.0.0-7-generic #8-Ubuntu SMP Mon Mar 4 16:25:21 UTC 2019 s390x 
s390x s390x GNU/Linux

  - enable z hw crypto support for openssh on an Ubuntu host (zlin42) on s390x 
like this:
  - sudo apt-get install openssl-ibmca libica-utils libica3
  - sudo tee -a /etc/ssl/openssl.cnf < 
/usr/share/doc/openssl-ibmca/examples/openssl.cnf.sample
  - sudo sed -i 's/^\(openssl_conf = openssl_def.*$\)/# \1/g' 
/etc/ssl/openssl.cnf
  - sudo sed -i '10i openssl_conf = openssl_def' /etc/ssl/openssl.cnf
  - afterwards ssh login attempts fail (existing session are unaffected):
     $ ssh ubuntu@localhost
     The authenticity of host 'localhost (::1)' can't be established.
     ECDSA key fingerprint is 
SHA256:KoTYC0jCQPtmsOMmBW9DrCiBbkrKTL0leQ/zoIaInNw.
     Are you sure you want to continue connecting (yes/no)? yes
     Warning: Permanently added 'localhost' (ECDSA) to the list of known hosts.
     ubuntu@localhost's password:
     packet_write_wait: Connection to ::1 port 22: Broken pipe

  [94629.032586] User process fault: interruption code 003b ilc:2 in 
libpthread-2.29.so[3ff7d48+1c000]
  [94629.032597] Failing address:  TEID: 0800
  [94629.032598] Fault in primary space mode while using user ASCE.
  [94629.032601] AS:0007450281c7 R3:0024
  [94629.032606] CPU: 0 PID: 8183 Comm: sshd Not tainted 5.0.0-7-generic 
#8-Ubuntu
  [94629.032607] Hardware name: IBM 2964 N63 400 (LPAR)
  [94629.032608] User PSW : 070520018000 03ff7d48e954
  [94629.032610]R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:1 AS:0 CC:2 PM:0 
RI:0 EA:3
  [94629.032611] User GPRS:    
03ff7e0085c8
  [94629.032612]03ff7e510108 03ff7db1c3a8  
03fff857eea0
  [94629.032613]03ff7e525040 02aa3f5ec090 03ff7e4916f0 
03ff7e4921a8
  [94629.032614]03ff7db17c18 0002 03ff7e07238a 
03fff857ea20
  [94629.032622] User Code: 03ff7d48e946: b9040012  lgr %r1,%r2
    03ff7d48e94a: e3f0ff60ff71  lay 
%r15,-160(%r15)
   #03ff7d48e950: 4700  bc  0,0
   >03ff7d48e954: 58202018  l   
%r2,24(%r2)
    03ff7d48e958: b24f00b0  ear %r11,%a0
    03ff7d48e95c: ebbb002d  sllg
%r11,%r11,32
    03ff7d48e962: b24f00b1  ear %r11,%a1
    03ff7d48e966: 5920b0d0  c   
%r2,208(%r11)
  [94629.032634] Last Breaking-Event-Address:
  [94629.032638]  [<03ff7df773b4>] 0x3ff7df773b4

  For more details see attachments ...
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: s390x
  DistroRelease: Ubuntu 19.04
  Package: openssh-server 1:7.9p1-9
  PackageArchitecture: s390x
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code -11:
  Tags:  disco
  Uname: Linux 5.0.0-7-generic s390x
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: pkcs11

[Touch-packages] [Bug 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove

@mk-uone This crash was reported only 2 times last month on
errors.ubuntu.com thus while I agree that this is a bug, it is not hit
very often and systems seem to recover run u-u fine next time and
continue installing updates.

The overall effect seems to be installing security updates one day later
in some rare cases.

The fix could certainly be backported, but there are other issues with
bigger impact thus those have higher priority.


** Changed in: unattended-upgrades (Ubuntu Bionic)
   Importance: Undecided => Critical

** Changed in: unattended-upgrades (Ubuntu Bionic)
   Importance: Critical => Low

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

Title:
  /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-
  upgrade@1991:main:do_auto_remove

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Confirmed

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.1ubuntu1.18.04.5, the problem page at 
https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e 
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/1795696/+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 1820608] Re: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-03-18 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.8
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Mar 18 13:38:42 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2019-01-21 (56 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1820608/+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 1820614] Re: Mail notification's headlines do not mention autoremovals

2019-03-18 Thread Nils Toedtmann

FYI this is unattended-upgrades 0.90ubuntu0.10 on Ubuntu 16.04.4 LTS

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

Title:
  Mail notification's headlines do not mention autoremovals

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  We run unattended-upgrades happily with 'Unattended-Upgrade::Mail'
  active and 'Unattended-Upgrade::Remove-Unused-Dependencies'

  Sometimes a UU run would not install nor hold anything, but only
  autoremove packages that have become obsolete, typically old kernels.
  In such cases, UU's mail notification reads:

  """
   Unattended upgrade returned: True
   
   Warning: A reboot is required to complete this upgrade.

   Packages that were upgraded:
   
   Package installation log:
   [...]
  """

  Which is quite irritating.

  It would be very helpful if it also contained a line "Packages that
  were (auto-)removed:"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1820614/+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 1809132] Re: Updated bionic to the current 1.10 stable version

Now after 3 months time for testing and no complaints coming up, Ken
VanDine, Will Cooke, Olivier Tilloy, and me agreed on considering this
SRU as verified. So I have marked this bug report appropriately.

Thanks to everyone who has tested this.

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

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

Title:
  Updated bionic to the current 1.10 stable version

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  The updates in the stable serie include several fixes for
  misbehaviour, segfaults and security issues, those are the sort of
  improvements that should be in the LTS

  The detail of the changes can be seen in the NEWS entry
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS

  * Test case

  There is no specific test case for the update, the changelog includes
  some specific bugs which have their own test case, otherwise it's
  important to get testing/feedback from users on desktop & server,
  using IPv4, IPv6, VPN, wifi, eth connections, etc.

  * Regression potential

  The update is non trivial, there are several changes are IPv6 and DNS
  (especially in the context of VPNs) handling so it would be good to
  give those extra testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809132/+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 1819943] Re: intel video driver not installed by default in ubuntu 19.04 (Disco)

2019-03-18 Thread Timo Aaltonen

Please test xserver from ppa:canonical-x/x-staging

It has a patch where the server should fall back to using fb instead of
crashing. You need to uninstall x-x-v-intel and then log out and back
in, before seeing if it works or not.

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

Title:
  intel video driver not installed by default in ubuntu 19.04 (Disco)

Status in xorg package in Ubuntu:
  In Progress
Status in xorg-server package in Ubuntu:
  Triaged

Bug description:
  I am running intel core2duo cpu and ubuntu 18.10 is running fine. I installed 
GRML , copied Ubuntu 19.04 iso to the grml folder in boot directory and then 
updated grub. Restarted the computer and on booting the ISO no login screen 
appeared. However,after pressing alt + ctrl + F2, logging in at command 
prompt,updating apt and installing "xserver-xorg-video-intel, lightdm, and 
unity" I was able to get to the desktop by running the command 'sudo service 
lightdm start'.  Command 'startx and X" gave xorg error saying server could not 
be connected. Command "sudo service gdm(3) start' went back to command prompt 
($).  
   This was also observed in Kubuntu and Xubuntu. In Xubuntu after installing 
intel video driver and running startx command i was able to get to the desktop.
  Whether, "xserver-xorg-video-intel" package is not being installed by default 
in ubuntu or support for "intel core2duo processor" has been withdrawn.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1819943/+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 1795696] Re: /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-upgrade@1991:main:do_auto_remove

Imho this is a mild security issue. For instance, we have a number of
managed clients that rely on unattended-upgrades to install security
patches every day. This bugs prevents those daily updates to run and it
has the potential to be overlooked in automated environments like ours.

Bionic desperately needs the the patch from https://github.com/mvo5
/unattended-upgrades/commit/72cf879db2ccc21cb8f0885ce4d9cb82f70fedaf
#diff-6c85bf717c6bff92cf4c9076f32c3f16L1529

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

Title:
  /usr/bin/unattended-upgrade:UnboundLocalError:/usr/bin/unattended-
  upgrade@1991:main:do_auto_remove

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Bionic:
  Confirmed

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.1ubuntu1.18.04.5, the problem page at 
https://errors.ubuntu.com/problem/651a7b7a070dd794d8cf2f5ea8e974614fdedb8e 
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/1795696/+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 1820614] [NEW] Mail notification's headlines do not mention autoremovals

2019-03-18 Thread Nils Toedtmann

Public bug reported:

We run unattended-upgrades happily with 'Unattended-Upgrade::Mail'
active and 'Unattended-Upgrade::Remove-Unused-Dependencies'

Sometimes a UU run would not install nor hold anything, but only
autoremove packages that have become obsolete, typically old kernels. In
such cases, UU's mail notification reads:

"""
 Unattended upgrade returned: True
 
 Warning: A reboot is required to complete this upgrade.

 Packages that were upgraded:
 
 Package installation log:
 [...]
"""

Which is quite irritating.

It would be very helpful if it also contained a line "Packages that were
(auto-)removed:"

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

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

Title:
  Mail notification's headlines do not mention autoremovals

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  We run unattended-upgrades happily with 'Unattended-Upgrade::Mail'
  active and 'Unattended-Upgrade::Remove-Unused-Dependencies'

  Sometimes a UU run would not install nor hold anything, but only
  autoremove packages that have become obsolete, typically old kernels.
  In such cases, UU's mail notification reads:

  """
   Unattended upgrade returned: True
   
   Warning: A reboot is required to complete this upgrade.

   Packages that were upgraded:
   
   Package installation log:
   [...]
  """

  Which is quite irritating.

  It would be very helpful if it also contained a line "Packages that
  were (auto-)removed:"

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1820614/+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 1820608] [NEW] package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-03-18 Thread Jeffrey Suchomel

Public bug reported:

.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: openssh-server 1:7.2p2-4ubuntu2.8
ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-46-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
Architecture: amd64
Date: Mon Mar 18 13:38:42 2019
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2019-01-21 (56 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.5
 apt  1.2.29ubuntu0.1
SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
Missing privilege separation directory: /var/run/sshd
SourcePackage: openssh
Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


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

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  New

Bug description:
  .

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.8
  ProcVersionSignature: Ubuntu 4.15.0-46.49~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-46-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Mon Mar 18 13:38:42 2019
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2019-01-21 (56 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.5
   apt  1.2.29ubuntu0.1
  SSHDConfig: Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 
255: Missing privilege separation directory: /var/run/sshd
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.8 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1820608/+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 1789642] Re: Nautilus highlights new filename without focusing input field.

2019-03-18 Thread Kaj Printz Madsen

Actually I made it trigger like so:
 - open firefox
 - hit ctrl+s
 - navigate to new folder(filename remains highlighted)
 - type (now searching folder)

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

Title:
  Nautilus highlights new filename without focusing input field.

Status in gtk+3.0 package in Ubuntu:
  Incomplete

Bug description:
  Opening nautilus in order to save picture from e.g. browser does so
  the name of the new file is highlighted but the focus is not on the
  input field. I expect when the name is highlighted that it is also
  focused.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18
  Uname: Linux 4.15.0-33-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Aug 29 14:18:08 2018
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'196'
   b'org.gnome.nautilus.window-state' b'geometry' b"'931x720+331+141'"
   b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'"
   b'org.gnome.nautilus.desktop' b'trash-icon-visible' b'false'
   b'org.gnome.nautilus.desktop' b'volumes-visible' b'false'
  InstallationDate: Installed on 2018-03-08 (173 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to bionic on 2018-04-27 (123 days ago)
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1789642/+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 1820319] Re: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No sound at all

2019-03-18 Thread nicola

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

 No It isn't One Is foto the Blue Port One for green one
Il lunedì 18 marzo 2019, 04:25:37 CET, Daniel van Vugt 
 ha scritto:  
 
 *** This bug is a duplicate of bug 1820314 ***
    https://bugs.launchpad.net/bugs/1820314

Thank you for taking the time to report this bug and helping to make
Ubuntu better. This particular bug has already been reported and is a
duplicate of bug 1820314, so it is being marked as such. Please look at
the other bug report to see if there is any missing information that you
can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report. Feel free to continue to report any other bugs you may
find.


** This bug has been marked a duplicate of bug 1820314
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, Rear] No sound 
at all

-- 
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1820319

Title:
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  even under xubuntu 16.04 my rear output did not work with headphones or Trust 
usb powered 2 way speaker even the front jack of my case does not work.
  the problem persist even if I have upgraded from 16.04 to 18.04 both lts

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC1:  hp        1709 F pulseaudio
  /dev/snd/controlC0:  hp        1709 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Mar 15 17:39:40 2019
  InstallationDate: Installed on 2016-09-07 (918 days ago)
  InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  ProcEnviron:
  LANGUAGE=it
  PATH=(custom, no user)
  XDG_RUNTIME_DIR=
  LANG=it_IT.UTF-8
  SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaRecordingTest: ALSA recording test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_DevicesInUse:
  USER        PID ACCESS COMMAND
  /dev/snd/controlC1:  hp        1709 F pulseaudio
  /dev/snd/controlC0:  hp        1709 F pulseaudio
  /dev/snd/seq:        timidity  1238 F timidity
  Symptom_Jack: Blue Line In, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P2.70
  dmi.board.name: FM2A75M-DGS
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP2.70:bd12/01/2016:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A75M-DGS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  modified.conffile..etc.modprobe.d.alsa-base.conf: options snd-hda-intel 
model=auto
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-14T16:54:28.355882

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

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

Title:
  [To Be Filled By O.E.M., Realtek ALC662 rev1, Blue Line In, Rear] No
  sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  even under xubuntu 16.04 my rear output did not work with headphones or Trust 
usb powered 2 way speaker even the front jack of my case does not work.
  the problem persist even if I have upgraded from 16.04 to 18.04 both lts

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1709 F pulseaudio
   /dev/snd/controlC0:  hp 1709 F pulseaudio
  CurrentDesktop: XFCE
  Date: Fri Mar 15 17:39:40 2019
  InstallationDate: Installed on 2016-09-07 (918 days ago)

[Touch-packages] [Bug 1745032] Re: AC adapter status not detected on Asus ZenBook UX410UAK

2019-03-18 Thread Treviño

Since no regression shell-side has been reported so far and verification
has beend done with a matching kernel, I think we can safely verify this
SRU (also coming as part of GNOME upstream changes) unblocking it from
the queue.

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

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

Title:
  AC adapter status not detected on Asus ZenBook UX410UAK

Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in gnome-shell package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Bionic:
  Fix Committed
Status in gnome-shell source package in Bionic:
  Fix Committed
Status in linux source package in Bionic:
  Fix Committed
Status in upower source package in Bionic:
  Fix Committed
Status in gnome-control-center source package in Cosmic:
  Fix Released
Status in gnome-shell source package in Cosmic:
  Fix Released
Status in linux source package in Cosmic:
  Fix Released
Status in upower source package in Cosmic:
  Fix Released

Bug description:
  === SRU Justification ===
  [Impact]
  Some Asus laptops report "discharging" when the battery is full and AC
  is plugged

  [Test]
  Charge battery to full, the issue appears.
  Users report with the patch the behaviour is correct.

  [Fix]
  The discharge rate is 0 on those machines. Use that to detect the wrong
  status report.

  [Regression Potential]
  Low. The quirk uses strict DMI to match affected systems.

  === Original Bug Report ===
  The AC adapter status is incorrectly reported when the battery is fully 
charged. It always shows as if the adapter is not plugged in. If the battery is 
drained for a while, the adapter status is shown correctly (both connects and 
disconnects are shown).

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: linux-image-4.13.0-31-generic 4.13.0-31.34
  ProcVersionSignature: Ubuntu 4.13.0-31.34-generic 4.13.13
  Uname: Linux 4.13.0-31-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  abarto 1388 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 23 18:26:18 2018
  InstallationDate: Installed on 2018-01-23 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp.
   Bus 001 Device 003: ID 04f2:b57a Chicony Electronics Co., Ltd
   Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. UX410UAK
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-31-generic.efi.signed 
root=UUID=58ea0561-3f74-4566-9332-5e7021275160 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-4.13.0-31-generic N/A
   linux-backports-modules-4.13.0-31-generic  N/A
   linux-firmware 1.169.2
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/08/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: UX410UAK.306
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: UX410UAK
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrUX410UAK.306:bd08/08/2017:svnASUSTeKCOMPUTERINC.:pnUX410UAK:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX410UAK:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: UX
  dmi.product.name: UX410UAK
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1745032/+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 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Ian, could you perhaps apply the patch of comment #13 and see whether
you get your problem fully solved (no need of setting AuthType Default
for /)?

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
  seems to be acting more like AuthInfoRequired username,password i.e.
  it prompts for a password when printing rather than using the
  available Kerberos credentials.

  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:

  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
  -o printer-error-policy=abort-job -o auth-info-required=negotiate -m
  "CIS/hp-officejet_pro_476_576_series-ps.ppd"

  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
  as it's blocked by default) and the permissions on this file changed
  to 700 (owner root) as per manpage instructions.

  When using lp -d printer /tmp/test.txt I get the following response:

  Password for myuid on localhost?

  Typing my password gets the job accepted to the queue but it does
  spool to the Windows Print Server and in the error_log file I can see

  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)

  Any ideas how to fix this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1820509] Re: Avoid use-after-free in _XimProtoSetIMValues()

Thank you for your bug report. That eems indeed worth fixing, it's a bit
difficult to know how sensitive the problem is without details though.
Could you provide a bit more context on the bug, maybe a way to trigger
it?

** Changed in: libx11 (Ubuntu)
   Importance: Undecided => High

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

Title:
  Avoid use-after-free in _XimProtoSetIMValues()

Status in libx11 package in Ubuntu:
  New

Bug description:
  I think that the patch
  
https://gitlab.freedesktop.org/xorg/lib/libx11/commit/003e30a66a249f5c70b30d1c187385124cd4cdad
  (issue: https://gitlab.freedesktop.org/xorg/lib/libx11/issues/49)
  should be backported to both Ubuntu 16.04 LTS Xenial and Ubuntu 18.04
  LTS Bionic.

  Although it didn't get an explicit CVS, use-after-free scenarios
  should not get underestimated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libx11/+bug/1820509/+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 1624644] Re: By default settings unattended-upgrade does not automatically remove kernel packages that become unused in conjunction with updating by other software

2019-03-18 Thread Jarno Suni

** Description changed:

  [Impact]
  
   * Update-manager and unattended-upgrades install many kernel packages during 
the lifetime of a release but does not remove them automatically leading to 
those packages filling disk space potentially completely filling /boot and 
making the system unable to install updates or even boot.
   * Stable release users are impacted by this bug for years and their systems 
already collected many autoremovable unused kernel packages, thus they would 
benefit from backporting the fix greatly.
   * The bug is fixed by removing autoremovable (not currently booted) kernel 
packages when running unattended-upgrades or update-manager. Update manager 
offers the kernel removals when there are other updates to be installed.
  
  [Test Case]
  
+ Note: test either update-manager or unattended-upgrades, not both at the
+ same time. If you remove unused kernels by the former, you can not test
+ the function in the latter.
+ 
   1. Install kernel packages to be removed, mark them auto-installed and
- run apt's kernel hook script to make apt consider them autoremovable:
+ run apt's kernel hook script to make apt consider them autoremovable and
+ simulate apt autoremove to get list of autoremovable packages:
  
    sudo apt install -y linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo apt-mark auto linux-image-extra-4.4.0-92-generic 
linux-image-extra-4.4.0-93-generic
    sudo /etc/kernel/postinst.d/apt-auto-removal
+   apt autoremove --simulate
  
-  2. Also downgrade a package to be upgraded:
+  2. (for update-manager; add something for it to update as update-
+ manager will not show removable packages, if there is not something to
+ update, right?) Downgrade a package to be upgraded:
  
     sudo apt-get install -y --allow-downgrades ca-
  certificates=20160104ubuntu1
  
   3. (update-manager). Run update-manager and observe that kernel
  packages are offered for removal in Details of updates.
  
    sudo update-manager
  
   4. (update-manager) Click on Install Now and observe that the kernel
  packages are removed.
  
-  3. (unattended-upgrades, the fix comes in an update of u-u) Run
+  2. (unattended-upgrades, the fix comes in an update of u-u) Run
  unattended-upgrades manually and observe the removal of the
  autoremovable kernel packages:
  
    sudo unattended-upgrade -v
  
  [Regression Potential]
  
   The change may cause update-manager or unattanded-upgrades to remove
  used kernel packages or fail to install other package updates.
  
  [Other Info]
  
  The unattended-upgrades fix is uploaded with many other fixes and those
  may cause regressions in other areas in unattended-upgrades.
  
  [Original bug text]
  
  When using default settings for unattended-upgrade i.e.
  Unattended-Upgrade::Remove-Unused-Dependencies "false";
  # default "false"
  Unattended-Upgrade::Remove-New-Unused-Dependencies "true";
  # default "true"
  in configuration file /etc/apt/apt.conf.d/50unattended-upgrades,
  unattended-upgrade is unable to remove packages that become unused in 
conjunction with updating by other software such as update-manager or apt 
full-upgrade. This is because unattended-upgrade compares the list of unneeded 
packages before and after it upgrades packages to detect which packages are new 
unused ones.
  
  Consequently, if user installs new kernels using e.g. update-manager,
  the excessive kernels will not be removed by unattended-upgrade, and
  eventually (small) /boot will become full.
  
  Expected behavior: handle removing of unused packages differently at
  least until other package management software installed by default can
  handle removing of new unused packages.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  CurrentDesktop: XFCE
  Date: Sat Sep 17 11:28:44 2016
  InstallationDate: Installed on 2016-09-05 (11 days ago)
  InstallationMedia: Mythbuntu 16.04.1 LTS "Xenial Xerus" - Release i386 
(20160719)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  By default settings unattended-upgrade does not automatically remove
  kernel packages that become unused in conjunction with updating by
  other software

Status in unattended-upgrades package in Ubuntu:
  Fix Released
Status in update-manager package in Ubuntu:
  Fix Released
Status in unattended-upgrades source package in Xenial:
  Fix Committed
Status in update-manager source package in Xenial:
  Fix Released
Status in unattended-upgrades source package in Artful:
  Won't Fix
Status in update-manager source

[Touch-packages] [Bug 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

2019-03-18 Thread Ian Gordon

@sil2100 it works for me as long as I set AuthType Default for / (which
I didn't have to set before but I'm happy to set it now)

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
  seems to be acting more like AuthInfoRequired username,password i.e.
  it prompts for a password when printing rather than using the
  available Kerberos credentials.

  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:

  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
  -o printer-error-policy=abort-job -o auth-info-required=negotiate -m
  "CIS/hp-officejet_pro_476_576_series-ps.ppd"

  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
  as it's blocked by default) and the permissions on this file changed
  to 700 (owner root) as per manpage instructions.

  When using lp -d printer /tmp/test.txt I get the following response:

  Password for myuid on localhost?

  Typing my password gets the job accepted to the queue but it does
  spool to the Windows Print Server and in the error_log file I can see

  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)

  Any ideas how to fix this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1809132] Re: Updated bionic to the current 1.10 stable version

Also on the Bionic VM on my main laptop I have updated network-manager
to 1.10.14 and there are no issues.

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

Title:
  Updated bionic to the current 1.10 stable version

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  The updates in the stable serie include several fixes for
  misbehaviour, segfaults and security issues, those are the sort of
  improvements that should be in the LTS

  The detail of the changes can be seen in the NEWS entry
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS

  * Test case

  There is no specific test case for the update, the changelog includes
  some specific bugs which have their own test case, otherwise it's
  important to get testing/feedback from users on desktop & server,
  using IPv4, IPv6, VPN, wifi, eth connections, etc.

  * Regression potential

  The update is non trivial, there are several changes are IPv6 and DNS
  (especially in the context of VPNs) handling so it would be good to
  give those extra testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809132/+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 1624644] Re: By default settings unattended-upgrade does not automatically remove kernel packages that become unused in conjunction with updating by other software

2019-03-18 Thread Jarno Suni

@rbalint about your test case: I wonder why linux-image-4.8.0-53-generic
was not removed by u-u? Was it the booted kernel? You also did not run
'sudo /etc/kernel/postinst.d/apt-auto-removal' before running u-u. Your
test case does not show how the kernels were installed.

In the following, I show the extraction of terminal output of a more
complete test case for u-u. It installs linux-image-
extra-4.4.0-141-generic by apt. Output of 'apt autoremove --simulate'
shows it would remove the kernel, and one unneeded package that is not a
kernel related. Whereas u-u just removes the kernel (which may be the
expected behavior).

$ set -x; sudo apt install -y unattended-upgrades/xenial-proposed 
linux-image-extra-4.4.0-141-generic;  sudo apt-mark auto 
linux-image-extra-4.4.0-141-generic;  sudo 
/etc/kernel/postinst.d/apt-auto-removal;  apt autoremove --simulate;  sudo 
unattended-upgrade -v;  set +x
+ sudo apt install -y unattended-upgrades/xenial-proposed 
linux-image-extra-4.4.0-141-generic
Reading package lists... Done
Building dependency tree   
Reading state information... Done
unattended-upgrades is already the newest version (1.1ubuntu1.18.04.7~16.04.2).
Selected version '1.1ubuntu1.18.04.7~16.04.2' (Ubuntu:16.04/xenial-proposed 
[all]) for 'unattended-upgrades'
The following package was automatically installed and is no longer required:
  xscreensaver-data
Use 'sudo apt autoremove' to remove it.
Suggested packages:
  fdutils linux-doc-4.4.0 | linux-source-4.4.0 linux-tools 
linux-headers-4.4.0-141-generic
The following NEW packages will be installed:
  linux-image-4.4.0-141-generic linux-image-extra-4.4.0-141-generic
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 58,7 MB of archives.
After this operation, 224 MB of additional disk space will be used.
Get:1 http://ubuntu.mirror.true.nl/ubuntu xenial-updates/main amd64 
linux-image-4.4.0-141-generic amd64 4.4.0-141.167 [22,2 MB]
Get:2 http://ubuntu.mirror.true.nl/ubuntu xenial-updates/main amd64 
linux-image-extra-4.4.0-141-generic amd64 4.4.0-141.167 [36,5 MB]
Fetched 58,7 MB in 26s (2 233 kB/s) 
 
Selecting previously unselected package linux-image-4.4.0-141-generic.
(Reading database ... 332942 files and directories currently installed.)
Preparing to unpack .../linux-image-4.4.0-141-generic_4.4.0-141.167_amd64.deb 
...
Examining /etc/kernel/preinst.d/
run-parts: executing /etc/kernel/preinst.d/intel-microcode 4.4.0-141-generic 
/boot/vmlinuz-4.4.0-141-generic
Done.
Unpacking linux-image-4.4.0-141-generic (4.4.0-141.167) ...
Selecting previously unselected package linux-image-extra-4.4.0-141-generic.
Preparing to unpack 
.../linux-image-extra-4.4.0-141-generic_4.4.0-141.167_amd64.deb ...
Unpacking linux-image-extra-4.4.0-141-generic (4.4.0-141.167) ...
Setting up linux-image-4.4.0-141-generic (4.4.0-141.167) ...
Running depmod.
update-initramfs: deferring update (hook will be called later)
Examining /etc/kernel/postinst.d.
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-141-generic 
/boot/vmlinuz-4.4.0-141-generic
run-parts: executing /etc/kernel/postinst.d/dkms 4.4.0-141-generic 
/boot/vmlinuz-4.4.0-141-generic
Error! Your kernel headers for kernel 4.4.0-141-generic cannot be found.
Please install the linux-headers-4.4.0-141-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located
Error! Your kernel headers for kernel 4.4.0-141-generic cannot be found.
Please install the linux-headers-4.4.0-141-generic package,
or use the --kernelsourcedir option to tell DKMS where it's located
run-parts: executing /etc/kernel/postinst.d/initramfs-tools 4.4.0-141-generic 
/boot/vmlinuz-4.4.0-141-generic
update-initramfs: Generating /boot/initrd.img-4.4.0-141-generic
run-parts: executing /etc/kernel/postinst.d/pm-utils 4.4.0-141-generic 
/boot/vmlinuz-4.4.0-141-generic
run-parts: executing /etc/kernel/postinst.d/unattended-upgrades 
4.4.0-141-generic /boot/vmlinuz-4.4.0-141-generic
run-parts: executing /etc/kernel/postinst.d/update-notifier 4.4.0-141-generic 
/boot/vmlinuz-4.4.0-141-generic
run-parts: executing /etc/kernel/postinst.d/zz-update-grub 4.4.0-141-generic 
/boot/vmlinuz-4.4.0-141-generic
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.15.0-46-generic
Found initrd image: /boot/initrd.img-4.15.0-46-generic
Found linux image: /boot/vmlinuz-4.4.0-143-generic
Found initrd image: /boot/initrd.img-4.4.0-143-generic
Found linux image: /boot/vmlinuz-4.4.0-141-generic
Found initrd image: /boot/initrd.img-4.4.0-141-generic
Found memtest86+ image: /memtest86+.elf
Found memtest86+ image: /memtest86+.bin
Found Ubuntu 16.04.1 LTS (16.04) on /dev/sdc2
done
Setting up linux-image-extra-4.4.0-141-generic (4.4.0-141.167) ...
run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 4.4.0-141-generic 
/boot/vmlinuz-4.4.0-141-generic
run-parts: executing /etc/kernel/postinst.d/dkms

[Touch-packages] [Bug 1689833] Re: OpenVPN server does not start properly on boot

Do you have a pointer to the upstream discussion?

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

Title:
  OpenVPN server does not start properly on boot

Status in openvpn package in Ubuntu:
  Triaged
Status in systemd package in Ubuntu:
  Invalid

Bug description:
  OpenVPN intermittently fails to bind to local address during boot on
  Ubuntu Server 16.04.2 LTS. Sometimes it succeeds, sometimes it does
  not.

  /var/log/openvpn.log
  Wed May 10 15:42:02 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] 
[LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb  2 2016
  Wed May 10 15:42:02 2017 library versions: OpenSSL 1.0.2g  1 Mar 2016, LZO 
2.08
  Wed May 10 15:42:02 2017 Diffie-Hellman initialized with 2048 bit key
  Wed May 10 15:42:02 2017 Control Channel Authentication: using 
'./easy-rsa/keys/ta.key' as a OpenVPN static key file
  Wed May 10 15:42:02 2017 Outgoing Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:02 2017 Incoming Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:02 2017 Socket Buffers: R=[212992->212992] S=[212992->212992]
  Wed May 10 15:42:02 2017 TCP/UDP: Socket bind failed on local address 
[AF_INET]192.168.4.254:1194: Cannot assign requested address
  Wed May 10 15:42:02 2017 Exiting due to fatal error

  In case it does not start, running 'sudo service openvpn start' fixes
  that problem.

  /var/log/openvpn.log
  Wed May 10 15:42:43 2017 OpenVPN 2.3.10 x86_64-pc-linux-gnu [SSL (OpenSSL)] 
[LZO] [EPOLL] [PKCS11] [MH] [IPv6] built on Feb  2 2016
  Wed May 10 15:42:43 2017 library versions: OpenSSL 1.0.2g  1 Mar 2016, LZO 
2.08
  Wed May 10 15:42:43 2017 Diffie-Hellman initialized with 2048 bit key
  Wed May 10 15:42:43 2017 Control Channel Authentication: using 
'./easy-rsa/keys/ta.key' as a OpenVPN static key file
  Wed May 10 15:42:43 2017 Outgoing Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:43 2017 Incoming Control Channel Authentication: Using 160 
bit message hash 'SHA1' for HMAC authentication
  Wed May 10 15:42:43 2017 Socket Buffers: R=[212992->212992] S=[212992->212992]
  Wed May 10 15:42:43 2017 ROUTE_GATEWAY 192.168.4.1/255.255.255.0 IFACE=ens4 
HWADDR=52:54:00:f0:26:0c
  Wed May 10 15:42:43 2017 TUN/TAP device tun0 opened
  Wed May 10 15:42:43 2017 TUN/TAP TX queue length set to 100
  Wed May 10 15:42:43 2017 do_ifconfig, tt->ipv6=0, 
tt->did_ifconfig_ipv6_setup=0
  Wed May 10 15:42:43 2017 /sbin/ip link set dev tun0 up mtu 1500
  Wed May 10 15:42:43 2017 /sbin/ip addr add dev tun0 local 172.16.1.1 peer 
172.16.1.2
  Wed May 10 15:42:43 2017 /sbin/ip route add 172.16.1.0/24 via 172.16.1.2
  Wed May 10 15:42:43 2017 GID set to nogroup
  Wed May 10 15:42:43 2017 UID set to nobody
  Wed May 10 15:42:43 2017 UDPv4 link local (bound): [AF_INET]192.168.4.254:1194
  Wed May 10 15:42:43 2017 UDPv4 link remote: [undef]
  Wed May 10 15:42:43 2017 MULTI: multi_init called, r=256 v=256
  Wed May 10 15:42:43 2017 IFCONFIG POOL: base=172.16.1.4 size=62, ipv6=0
  Wed May 10 15:42:43 2017 IFCONFIG POOL LIST
  Wed May 10 15:42:43 2017 Initialization Sequence Completed

  My guess is that systemd starts OpenVPN too early before the network
  is brought up sufficiently. Running 'sudo systemctl edit --full
  openvpn' and adding 'Wants=network-online.target' does not change that
  behaviour.

  user@server:~$ sudo systemd-analyze critical-chain
  graphical.target @2.160s
  └─multi-user.target @2.159s
    └─ntp.service @2.054s +104ms
  └─remote-fs.target @2.052s
    └─remote-fs-pre.target @2.052s
  └─open-iscsi.service @1.993s +57ms
    └─iscsid.service @1.942s +47ms
  └─network-online.target @1.941s
    └─network.target @1.929s
  └─networking.service @1.793s +134ms
    └─apparmor.service @1.140s +395ms
  └─local-fs.target @1.140s
    └─local-fs-pre.target @1.139s
  └─lvm2-monitor.service @602ms +536ms
    └─lvm2-lvmetad.service @773ms
  └─systemd-journald.socket @574ms
    └─-.slice @500ms

  The boot time is quite short. Clean install with the additional
  packages ntp and openssh-server. This happens both on bare metal and
  as a Virtual Machine (KVM) as well.

  /etc/openvpn/server.conf
  local 192.168.4.254
  port 1194
  proto udp
  dev tun
  ca ./easy-rsa/keys/ca.crt
  cert ./easy-rsa/keys/crt.crt
  key ./easy-rsa/keys/key.key
  dh ./easy-rsa/keys/dh2048.pem
  tls-auth ./easy-rsa/keys/ta.key 0
  server 172.16.1.0 255.255.255.0
  ifconfig-pool-persist ipp.txt
  push "route 192.168.0.0 255.255.255.0"
  push "route 192.168.4.0 255.255.255.0"

[Touch-packages] [Bug 1820510] Re: Build errors against recent valac

There is a merge request on 
https://code.launchpad.net/~ricotz/libunity/syntax-fixes/+merge/362923 but it 
fails to build now with a dee 
https://launchpadlibrarian.net/415297335/buildlog_ubuntu-disco-amd64.libunity_7.1.4+19.04.20190315.5-0ubuntu1_BUILDING.txt.gz

** Changed in: libunity (Ubuntu)
   Importance: Undecided => High

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

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

Title:
  Build errors against recent valac

Status in libunity:
  New
Status in libunity package in Ubuntu:
  In Progress

Bug description:
  I'd like to build Geary with support for Unity indicators in the Geary
  Flatpak package, but it's failing to build against recent valac:

  mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ vala 
--version
  Vala 0.44.0
  mjog@blanchefort:~/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig$ make
  make  all-recursive
  make[1]: Entering directory 
'/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig'
  Making all in data
  make[2]: Entering directory 
'/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data'
ITMRG  com.canonical.Unity.Lenses.gschema.xml
GEN  com.canonical.Unity.Lenses.gschema.valid
  make[2]: Leaving directory 
'/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/data'
  Making all in protocol
  make[2]: Entering directory 
'/home/mjog/Projects/GNOME/libunity_7.1.4+16.04.20180209.1.orig/protocol'
GEN  libunity_protocol_private_la_vala.stamp
  Command-line option `--thread` is deprecated and will be ignored
  protocol-scope-discovery.vala:24.3-24.40: warning: the modifier `static' is 
not applicable to constants
private static const string SCOPES_DIR = "unity/scopes";
^^
  protocol-scope-discovery.vala:190.5-190.43: warning: the modifier `static' is 
not applicable to constants
  private static const string SCOPE_GROUP = "Scope";
  ^^^
  protocol-scope-discovery.vala:191.5-191.45: warning: the modifier `static' is 
not applicable to constants
  private static const string DESKTOP_GROUP = "Desktop Entry";
  ^
  protocol-scope-discovery.vala:902.5-902.49: warning: the modifier `static' is 
not applicable to constants
  private static const string SCOPE_GROUP_GROUP = "Scope Group";
  ^
  protocol-preview-player.vala:41.3-41.46: warning: the modifier `static' is 
not applicable to constants
static const string PREVIEW_PLAYER_DBUS_NAME = 
"com.canonical.Unity.Lens.Music.PreviewPlayer";

  protocol-preview-player.vala:42.3-42.46: warning: the modifier `static' is 
not applicable to constants
static const string PREVIEW_PLAYER_DBUS_PATH = 
"/com/canonical/Unity/Lens/Music/PreviewPlayer";

  protocol-scope-interface.vala:117.3-117.51: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async ActivationReplyRaw activate (
^
  protocol-scope-interface.vala:124.3-124.57: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async HashTable search (
^^^
  protocol-scope-interface.vala:134.7-134.46: error: Synchronous out-parameters 
are not supported in async methods
out HashTable out_hints,

  protocol-scope-interface.vala:130.3-130.43: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async string open_channel (
^
  protocol-scope-interface.vala:137.3-137.42: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void close_channel (

  protocol-scope-interface.vala:142.3-142.63: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async HashTable push_results (
^
  protocol-scope-interface.vala:151.3-151.42: warning: DBus methods are 
recommended to throw at least `GLib.Error' or `GLib.DBusError, GLib.IOError'
public abstract async void set_view_type (uint view_type) throws IOError;

  unity-scope-proxy-remote.vala:379.12-379.21: error: The name `channel_id' 
does not exist in the context of

[Touch-packages] [Bug 1815742] Re: latest network-manager segfaults in disco

Thanks!

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

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  Triaged

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

This bug was fixed in the package qtbase-opensource-src - 5.9.5+dfsg-
0ubuntu2

---
qtbase-opensource-src (5.9.5+dfsg-0ubuntu2) bionic; urgency=medium

  * Backport two upstream commits to fix duplex printing (LP: #1776173).
Thanks to Robert Bredereck for the initial patch!

 -- Dmitry Shachnev   Wed, 06 Feb 2019 10:47:55
+0300

** Changed in: qtbase-opensource-src (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Released
Status in qtbase-opensource-src source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  All kde applications shipped with ubuntu and particularly kubuntu bionic 
print via the qt print dialog, that, unfortunately, does not seem to respect 
the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  [Test Case]
  1) Install a printer that can duplex and configure it to do duplex with 
long-edge binding from the printer setup dialog.

  2) Open a PDF with okular, and open the print dialog. Select the
  printer above.

  3) Press the "Options" button to enlarge the dialog to also present
  the options. Select the "options" tab, right of "copies". Verify that
  Duplex Printing is preset to "None"

  This is wrong, because the printer was configured to do duplex with
  long-edge binding.

  4) Print and close okular.

  5) Reopen okular (with the same or another PDF file). Open again the
  print dialog and select the same printer.

  6) Redo 3). Again see that Duplex Printing is preset to "None",
  instead of being at the default or at the previously used setup.

  [Regression Potential]
  The proposed patch only changes the default settings. The regression 
potential may be that the values are wrong, although they are already wrong.

  In case there is some bug it may lead to crashes. But this code is in
  the latest stable Qt release and I am not aware of any such crashes
  reported.

  [Other Info]
  The proposed patch is a backport of the following upstream commits:
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e

  [Original Description]
  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1818201] Re: packagekitd crashed with SIGSEGV in __memmove_{sse2, avx}_unaligned_erms() from std::char_traits::copy() from ... from show_errors (errorCode=PK_ERROR_ENUM_CAN

This bug was fixed in the package packagekit - 1.1.9-1ubuntu2.18.04.5

---
packagekit (1.1.9-1ubuntu2.18.04.5) bionic; urgency=medium

  * 03_aptcc-use-correct-return-type-in-function.patch: Cherry pick upstream
fix for show_errors crashes (LP: #1818201)

 -- Julian Andres Klode   Mon, 04 Mar 2019 16:42:18
+0100

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

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

Title:
  packagekitd crashed with SIGSEGV in
  __memmove_{sse2,avx}_unaligned_erms() from
  std::char_traits::copy() from ... from show_errors
  (errorCode=PK_ERROR_ENUM_CANNOT_FETCH_SOURCES)

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  Won't Fix
Status in packagekit source package in Bionic:
  Fix Released
Status in packagekit source package in Cosmic:
  Fix Released
Status in packagekit source package in Disco:
  Fix Released

Bug description:
  [Impact]
  packagekit (sometimes) crashes when there are errors.

  https://errors.ubuntu.com/problem/1bdc3e539949aa164d276979f62ca0282a54fcbd
  https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034

  [Test case]
  Check that there are no further cases on the error tracker with the proposed 
version.

  [Regression potential]
  Given that this just changes the return type of a function only used in 
calls, and the code compiles, there should be no possibility for a regression. 
Of course, if there were, it'd be segfaults or stuff.

  [Original info]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
packagekit.  This problem was most recently seen with package version 
1.1.12-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034 
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/packagekit/+bug/1818201/+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 1818201] Re: packagekitd crashed with SIGSEGV in __memmove_{sse2, avx}_unaligned_erms() from std::char_traits::copy() from ... from show_errors (errorCode=PK_ERROR_ENUM_CAN

This bug was fixed in the package packagekit - 1.1.10-1ubuntu7.1

---
packagekit (1.1.10-1ubuntu7.1) cosmic; urgency=medium

  * 03_aptcc-use-correct-return-type-in-function.patch: Cherry pick upstream
fix for show_errors crashes (LP: #1818201)

 -- Julian Andres Klode   Mon, 04 Mar 2019 16:29:55
+0100

** Changed in: packagekit (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  packagekitd crashed with SIGSEGV in
  __memmove_{sse2,avx}_unaligned_erms() from
  std::char_traits::copy() from ... from show_errors
  (errorCode=PK_ERROR_ENUM_CANNOT_FETCH_SOURCES)

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  Won't Fix
Status in packagekit source package in Bionic:
  Fix Committed
Status in packagekit source package in Cosmic:
  Fix Released
Status in packagekit source package in Disco:
  Fix Released

Bug description:
  [Impact]
  packagekit (sometimes) crashes when there are errors.

  https://errors.ubuntu.com/problem/1bdc3e539949aa164d276979f62ca0282a54fcbd
  https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034

  [Test case]
  Check that there are no further cases on the error tracker with the proposed 
version.

  [Regression potential]
  Given that this just changes the return type of a function only used in 
calls, and the code compiles, there should be no possibility for a regression. 
Of course, if there were, it'd be segfaults or stuff.

  [Original info]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
packagekit.  This problem was most recently seen with package version 
1.1.12-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034 
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/packagekit/+bug/1818201/+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 1783298] Update Released

The verification of the Stable Release Update for cups has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
  seems to be acting more like AuthInfoRequired username,password i.e.
  it prompts for a password when printing rather than using the
  available Kerberos credentials.

  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:

  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
  -o printer-error-policy=abort-job -o auth-info-required=negotiate -m
  "CIS/hp-officejet_pro_476_576_series-ps.ppd"

  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
  as it's blocked by default) and the permissions on this file changed
  to 700 (owner root) as per manpage instructions.

  When using lp -d printer /tmp/test.txt I get the following response:

  Password for myuid on localhost?

  Typing my password gets the job accepted to the queue but it does
  spool to the Windows Print Server and in the error_log file I can see

  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)

  Any ideas how to fix this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01

[Touch-packages] [Bug 1776173] Re: qt print dialog shipped with bionic ignores printer defaults

This bug was fixed in the package qtbase-opensource-src - 5.11.1+dfsg-
7ubuntu3

---
qtbase-opensource-src (5.11.1+dfsg-7ubuntu3) cosmic; urgency=medium

  * Backport upstream commit to fix duplex printing (LP: #1776173).
Thanks to Robert Bredereck for the initial patch!

 -- Dmitry Shachnev   Thu, 28 Feb 2019 13:26:39
+0300

** Changed in: qtbase-opensource-src (Ubuntu Cosmic)
   Status: Fix Committed => Fix Released

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  All kde applications shipped with ubuntu and particularly kubuntu bionic 
print via the qt print dialog, that, unfortunately, does not seem to respect 
the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  [Test Case]
  1) Install a printer that can duplex and configure it to do duplex with 
long-edge binding from the printer setup dialog.

  2) Open a PDF with okular, and open the print dialog. Select the
  printer above.

  3) Press the "Options" button to enlarge the dialog to also present
  the options. Select the "options" tab, right of "copies". Verify that
  Duplex Printing is preset to "None"

  This is wrong, because the printer was configured to do duplex with
  long-edge binding.

  4) Print and close okular.

  5) Reopen okular (with the same or another PDF file). Open again the
  print dialog and select the same printer.

  6) Redo 3). Again see that Duplex Printing is preset to "None",
  instead of being at the default or at the previously used setup.

  [Regression Potential]
  The proposed patch only changes the default settings. The regression 
potential may be that the values are wrong, although they are already wrong.

  In case there is some bug it may lead to crashes. But this code is in
  the latest stable Qt release and I am not aware of any such crashes
  reported.

  [Other Info]
  The proposed patch is a backport of the following upstream commits:
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e

  [Original Description]
  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

This bug was fixed in the package cups - 2.2.7-1ubuntu2.4

---
cups (2.2.7-1ubuntu2.4) bionic; urgency=medium

  * fix-a-parsing-bug-in-the-new-authentication-code.patch,
fix-cups-auth-find-for-schemes-without-parameters.patch: Backported
authentication fixes from upstream (LP: #1783298).

 -- Till Kamppeter   Sun,  3 Mar 2019 12:28:01
+0100

** Changed in: cups (Ubuntu Bionic)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
  Fix Released
Status in cups package in Ubuntu:
  Fix Released
Status in cups source package in Bionic:
  Fix Released
Status in cups source package in Cosmic:
  Fix Released
Status in cups source package in Disco:
  Fix Released

Bug description:
  [Impact]

  If a print queue is set up with "auth-info-required=negotiate" because
  the server requires authentication (for example Kerberos) the user is
  asked for user name and password on every join, instead of the
  authentication working automatically. This worked correctly in 14.04
  and 16.04.

  Also setting "AuthType Default" for "/" in cupsd.conf leads to be
  prompted for a password on commands like "lpatat -a", even for root.
  Works correctly in Xenial and Cosmic.

  [Test Case]

  Set up a queue pointing to a Kerberos-authenticated Windows server
  with "lpadmin ... -o auth-info-required=negotiate ..." OR set
  "AuthType Default" for "/" in cupsd.conf. When printing or running
  other commands accessing your print queue you will get prompted for
  credentials. With the fix the authentication will get automatic again.

  [Regression Potential]

  Low, as the fix are simple one-line corrections taken from upstream.

  [Original report]

  Hi,

  We have our printers configured to print to a Windows print server. In
  Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
  seems to be acting more like AuthInfoRequired username,password i.e.
  it prompts for a password when printing rather than using the
  available Kerberos credentials.

  We are using an unaltered cupsd.conf file and are adding printers with
  the following command:

  lpadmin -p "printer" -D "Printer" -L "room" -v
  "smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
  -o printer-error-policy=abort-job -o auth-info-required=negotiate -m
  "CIS/hp-officejet_pro_476_576_series-ps.ppd"

  the smb backend has been linked to /usr/lib/x86_64-linux-
  gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
  as it's blocked by default) and the permissions on this file changed
  to 700 (owner root) as per manpage instructions.

  When using lp -d printer /tmp/test.txt I get the following response:

  Password for myuid on localhost?

  Typing my password gets the job accepted to the queue but it does
  spool to the Windows Print Server and in the error_log file I can see

  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - 
AUTH_INFO_REQUIRED=negotiate
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
  D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

  As I said earlier this all works perfectly on Xenial and Trusty.
  (A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS 
10.13)

  Any ideas how to fix this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: cups 2.2.7-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
  Uname: Linux 4.15.0-29-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  Date: Tue Jul 24 10:03:57 2018
  InstallationDate: Installed on 2018-06-22 (31 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical 
Mouse
   Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. OptiPlex 790
  Papersize: a4
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro 
quiet splash
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/28/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0HY9JP
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 790
  dmi.product.version: 01
  dmi.sys.vendor:

[Touch-packages] [Bug 1776173] Update Released

The verification of the Stable Release Update for qtbase-opensource-src
has completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  qt print dialog shipped with bionic ignores printer defaults

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src source package in Bionic:
  Fix Committed
Status in qtbase-opensource-src source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  All kde applications shipped with ubuntu and particularly kubuntu bionic 
print via the qt print dialog, that, unfortunately, does not seem to respect 
the defaults set for the printer.

  Specifically, every time one starts to print the "duplex" option gets
  reset to "none" even for those printers that were configured for "long
  edge" duplex by default.

  This may lead to a huge *waste of paper*: people print, expecting the
  duplex, do not get it, throw away the printout and reprint, for a
  total of 3 times the paper usage if the print dialog respected the
  default.

  [Test Case]
  1) Install a printer that can duplex and configure it to do duplex with 
long-edge binding from the printer setup dialog.

  2) Open a PDF with okular, and open the print dialog. Select the
  printer above.

  3) Press the "Options" button to enlarge the dialog to also present
  the options. Select the "options" tab, right of "copies". Verify that
  Duplex Printing is preset to "None"

  This is wrong, because the printer was configured to do duplex with
  long-edge binding.

  4) Print and close okular.

  5) Reopen okular (with the same or another PDF file). Open again the
  print dialog and select the same printer.

  6) Redo 3). Again see that Duplex Printing is preset to "None",
  instead of being at the default or at the previously used setup.

  [Regression Potential]
  The proposed patch only changes the default settings. The regression 
potential may be that the values are wrong, although they are already wrong.

  In case there is some bug it may lead to crashes. But this code is in
  the latest stable Qt release and I am not aware of any such crashes
  reported.

  [Other Info]
  The proposed patch is a backport of the following upstream commits:
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f6fd3f18d301cde3
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=fa854f214a3c812e

  [Original Description]
  See also https://bugs.kde.org/show_bug.cgi?id=395150

  As a final comment and in general, I think that Bionic should be
  updated to use the QT 5.11 print subsystem (from 5.9.5) as soon as
  possible (at least via a kubuntu ppa). The QT 5 print dialog has
  always been extremely poor, with no possibility to provide information
  about things like print quality and resolution, paper type, stapling
  (for printers supporting it), etc. Now, QT 5.11 has finally a better
  print dialog and it would be great if the bionic users could use it.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1776173/+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 1783298] Re: [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

@ian-gordon does this mean the fix does not work for you? I'll release
it into bionic-updates since it seems to work for others and not
introduce any regressions, but if you are still encountering issues
please open a new bug.

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

Title:
[SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work

Status in CUPS:
Fix Released
Status in cups package in Ubuntu:
Fix Released
Status in cups source package in Bionic:
Fix Released
Status in cups source package in Cosmic:
Fix Released
Status in cups source package in Disco:
Fix Released

Bug description:
[Impact]

If a print queue is set up with "auth-info-required=negotiate" because
the server requires authentication (for example Kerberos) the user is
asked for user name and password on every join, instead of the
authentication working automatically. This worked correctly in 14.04
and 16.04.

Also setting "AuthType Default" for "/" in cupsd.conf leads to be
prompted for a password on commands like "lpatat -a", even for root.
Works correctly in Xenial and Cosmic.

[Test Case]

Set up a queue pointing to a Kerberos-authenticated Windows server
with "lpadmin ... -o auth-info-required=negotiate ..." OR set
"AuthType Default" for "/" in cupsd.conf. When printing or running
other commands accessing your print queue you will get prompted for
credentials. With the fix the authentication will get automatic again.

[Regression Potential]

Low, as the fix are simple one-line corrections taken from upstream.

[Original report]

Hi,

We have our printers configured to print to a Windows print server. In
Ubuntu 14.04 and 16.04 our setup works fine but in 18.04 our setup
seems to be acting more like AuthInfoRequired username,password i.e.
it prompts for a password when printing rather than using the
available Kerberos credentials.

We are using an unaltered cupsd.conf file and are adding printers with
the following command:

lpadmin -p "printer" -D "Printer" -L "room" -v
"smb://printers.cis.strath.ac.uk/printers" -o Media=A4 -o PageSize=A4
-o printer-error-policy=abort-job -o auth-info-required=negotiate -m
"CIS/hp-officejet_pro_476_576_series-ps.ppd"

the smb backend has been linked to /usr/lib/x86_64-linux-
gnu/samba/smbspool_krb5_wrapper (I've added this the apparmor profile
as it's blocked by default) and the permissions on this file changed
to 700 (owner root) as per manpage instructions.

When using lp -d printer /tmp/test.txt I get the following response:

Password for myuid on localhost?

Typing my password gets the job accepted to the queue but it does
spool to the Windows Print Server and in the error_log file I can see

D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 -
AUTH_INFO_REQUIRED=negotiate
D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - Started with uid=0
D [24/Jul/2018:10:33:00 +0100] [Job 45] SMBSPOOL_KRB5 - AUTH_UID is not set

As I said earlier this all works perfectly on Xenial and Trusty.
(A similar AuthInfoRequired negotiate setup also works in cups 2.2.5 on MacOS
10.13)

Any ideas how to fix this?

Thanks,

Ian.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: cups 2.2.7-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.15.0-29.31-generic 4.15.18
Uname: Linux 4.15.0-29-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
Date: Tue Jul 24 10:03:57 2018
InstallationDate: Installed on 2018-06-22 (31 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
Lsusb:
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 0461:4d81 Primax Electronics, Ltd Dell N889 Optical
Mouse
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. OptiPlex 790
Papersize: a4
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=/dev/mapper/pd--ig--vg-root ro
quiet splash
SourcePackage: cups
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/28/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A05
dmi.board.name: 0HY9JP
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvrA05:bd05/28/2011:svnDellInc.:pnOptiPlex790:pvr01:rvnDellInc.:rn0HY9JP:rvrA00:cvnDellInc.:ct6:cvr:
dmi.product.name: OptiPlex 790
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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

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

[Touch-packages] [Bug 1818201] Update Released

The verification of the Stable Release Update for packagekit has
completed successfully and the package has now been released to
-updates.  Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  packagekitd crashed with SIGSEGV in
  __memmove_{sse2,avx}_unaligned_erms() from
  std::char_traits::copy() from ... from show_errors
  (errorCode=PK_ERROR_ENUM_CANNOT_FETCH_SOURCES)

Status in packagekit package in Ubuntu:
  Fix Released
Status in packagekit source package in Xenial:
  Won't Fix
Status in packagekit source package in Bionic:
  Fix Committed
Status in packagekit source package in Cosmic:
  Fix Committed
Status in packagekit source package in Disco:
  Fix Released

Bug description:
  [Impact]
  packagekit (sometimes) crashes when there are errors.

  https://errors.ubuntu.com/problem/1bdc3e539949aa164d276979f62ca0282a54fcbd
  https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034

  [Test case]
  Check that there are no further cases on the error tracker with the proposed 
version.

  [Regression potential]
  Given that this just changes the return type of a function only used in 
calls, and the code compiles, there should be no possibility for a regression. 
Of course, if there were, it'd be segfaults or stuff.

  [Original info]
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
packagekit.  This problem was most recently seen with package version 
1.1.12-1ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/e9af46c2ad01a15f968379c434fe0bfbf924d034 
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/packagekit/+bug/1818201/+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 1799279] Re: kernel update hangs inside update-secureboot-policy

2019-03-18 Thread Guillaume Charmetant

Hello,

This just happened to me as well.

Like Jérémie Roquet (arkanosis), I run Kubuntu 16.04 and never had this
issue in the previous years when asked about secure boot during an
upgrade.

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

Title:
  kernel update hangs inside update-secureboot-policy

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  I just ran `apt-get --auto-remove dist-upgrade` on 18.04.

  It is hung on update-secureboot-policy waiting for confirmation from
  whiptail.

  apt-get --auto-remove dist-upgrade
  |
  -/usr/bin/dpkg --status-fd 80 --configure --pending
   |
   -/bin/sh /var/lib/dpkg/info/linux-headers-4.15.0-38-generic.postinst 
configure
    |
    -run-parts --report --exit-on-error --arg=4.15.0-38-generic 
/etc/kernel/header_postinst.d
     |
     -/bin/sh /usr/lib/dkms/dkms_autoinstaller start 4.15.0-38-generic
  |
  -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
   |
   -/bin/bash /usr/sbin/dkms autoinstall --kernelver 4.15.0-38-generic
    |
    -/usr/bin/perl -w /usr/share/debconf/frontend 
/usr/sbin/update-secureboot-policy --enroll-key
     |
     -/bin/sh /usr/sbin/update-secureboot-policy --enroll-key
     -whiptail --backtitle Package configuration --title Configuring Secure 
Boot --output-fd 12 --nocancel --msgbox Your system has UEFI Secure Boot 
enabled.  UEFI Secure Boot requires additional configuration to work with  
third-party drivers.  The system will assist you in configuring UEFI Secure 
Boot. To permit  the use of third-party drivers, a new Machine-Owner Key (MOK) 
has been  generated. This key now needs to be enrolled in your system's 
firmware.  To ensure that this change is being made by you as an authorized 
user,  and not by an attacker, you must choose a password now and then confirm  
the change after reboot using the same password, in both the "Enroll  MOK" and 
"Change Secure Boot state" menus that will be presented to you  when this 
system reboots.  If you proceed but do not confirm the password upon reboot, 
Ubuntu will  still be able to boot on your system but any hardware that 
requires  third-party drivers to work correctly may not be usable. --scrolltext 
20 77

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apt 1.6.3ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18
  Uname: Linux 4.15.0-36-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Oct 22 15:15:56 2018
  InstallationDate: Installed on 2018-09-27 (25 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: apt
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1799279/+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 1809132] Re: Updated bionic to the current 1.10 stable version

Now my Bionic test box is running for the whole weekend and it does not
show any irregularities. No crash reports. The new network-manager seems
to work fine on Bionic.

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

Title:
  Updated bionic to the current 1.10 stable version

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Bionic:
  Fix Committed

Bug description:
  * Impact

  The updates in the stable serie include several fixes for
  misbehaviour, segfaults and security issues, those are the sort of
  improvements that should be in the LTS

  The detail of the changes can be seen in the NEWS entry
  https://gitlab.freedesktop.org/NetworkManager/NetworkManager/blob/nm-1-10/NEWS

  * Test case

  There is no specific test case for the update, the changelog includes
  some specific bugs which have their own test case, otherwise it's
  important to get testing/feedback from users on desktop & server,
  using IPv4, IPv6, VPN, wifi, eth connections, etc.

  * Regression potential

  The update is non trivial, there are several changes are IPv6 and DNS
  (especially in the context of VPNs) handling so it would be good to
  give those extra testing

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1809132/+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 1820420] Re: package libldap-2.4-2 2.4.46+dfsg-5ubuntu1.1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libldap-2.4-2/changelog.Debian.gz', which is diffe

2019-03-18 Thread Karl Stenerud

Hi dierre,

I'm seeing the following error message in the logs:

error processing archive 
/tmp/apt-dpkg-install-EPmbpq/114-libldap-2.4-2_2.4.46+dfsg-5ubuntu1.1_i386.deb 
(--unpack):
 trying to overwrite shared '/usr/share/doc/libldap-2.4-2/changelog.Debian.gz', 
which is different from other instances of package libldap-2.4-2:i386

Generally, this happens when you've installed a different version from a
non-ubuntu archive (perhaps manually built?), and it hasn't been fully
uninstalled yet. Check to make sure you don't have an existing ldap
installation. Ultimately, if you can't manage to fix it with apt, you
can always manually delete /usr/share/doc/libldap-2.4-2.

I'm marking this as invalid since it's a system configuration issue, but
if you feel there's more to it, please give more info about the problem
and change the status back to "new".


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

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

Title:
  package libldap-2.4-2 2.4.46+dfsg-5ubuntu1.1 failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libldap-2.4-2/changelog.Debian.gz', which is different
  from other instances of package libldap-2.4-2:i386

Status in openldap package in Ubuntu:
  Invalid

Bug description:
  See attached log

  ProblemType: Package
  DistroRelease: Ubuntu 18.10
  Package: libldap-2.4-2 2.4.46+dfsg-5ubuntu1.1
  Uname: Linux 4.19.0-041900rc8-lowlatency x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  Date: Wed Mar 13 20:39:09 2019
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libldap-2.4-2/changelog.Debian.gz', which is different from 
other instances of package libldap-2.4-2:i386
  InstallationDate: Installed on 2018-12-22 (84 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Python3Details: /usr/bin/python3.6, Python 3.6.7rc1, python3-minimal, 
3.6.7-1~18.10
  PythonDetails: /usr/bin/python2.7, Python 2.7.15+, python-minimal, 2.7.15-3
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu5
   apt  1.7.2
  SourcePackage: openldap
  Title: package libldap-2.4-2 2.4.46+dfsg-5ubuntu1.1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libldap-2.4-2/changelog.Debian.gz', which is different from 
other instances of package libldap-2.4-2:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1820420/+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 1815742] Re: latest network-manager segfaults in disco

2019-03-18 Thread Bas Zoetekouw

The problem still occurs with the .91 version from disco-proposed.
I'll attach the requested files to the upstream report.

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

Title:
  latest network-manager segfaults in disco

Status in network-manager package in Ubuntu:
  Incomplete

Bug description:
  When I updated to the latest version of networkmanager in disco dingo
  (1.15.2-0ubuntu1), it started segfaulting.  Reverting to the version
  in cosmic (1.12.4-1ubuntu1.2) solved the problem.

  Syslog shows the following (will attach a more complete log):

  feb 13 10:39:45 regan NetworkManager[2315]: 
NetworkManager:ERROR:src/settings/nm-settings-plugin.c:147:_nm_settings_plugin_emit_signal_connection_added:
 assertion failed: __extension__ ({ GTypeInstance *__inst = 
(GTypeInstance*) ((sett_conn)); GType __t = ((nm_settings_connection_get_type 
())); gboolean __r; if (!__inst) __r = (0); else if (__inst->g_class && 
__inst->g_class->g_type == __t) __r = (!(0)); else __r = 
g_type_check_instance_is_a (__inst, __t); __r; })
  feb 13 10:39:45 regan NetworkManager[2315]:   [1550050785.3612] 
ifupdown: management mode: managed
  feb 13 10:39:45 regan NetworkManager[2315]: invalid uninstantiatable type 
'(null)' in cast to 'NMSettingsConnection'
  feb 13 10:39:45 regan systemd[1]: NetworkManager.service: Main process 
exited, code=dumped, status=6/ABRT
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.10-0ubuntu20
  Architecture: amd64
  CurrentDesktop: GNOME
  DistroRelease: Ubuntu 19.04
  InstallationDate: Installed on 2016-12-22 (782 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  Package: network-manager 1.12.4-1ubuntu1.2
  PackageArchitecture: amd64
  Tags:  disco
  Uname: Linux 4.19.0-1-amd64 x86_64
  UpgradeStatus: Upgraded to disco on 2017-09-18 (512 days ago)
  UserGroups: adm cdrom dialout dip docker libvirt lp lpadmin lxd plugdev 
sambashare scanner src sudo tss wireshark
  _MarkForUpload: True
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2018-06-01T16:38:44.962715
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.12.4   connected  started  full  enabled enabled  
enabled  enabled  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1815742/+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 1819728] Re: Please backport "fix race between daemon-reload and other commands #8803" to 16.04 (for UC16) and 18.04 (for UC18)

2019-03-18 Thread Michael Vogt

** Patch added: "updated debdiff with updated PR#11121"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1819728/+attachment/5247198/+files/systemd_237-3ubuntu10.17.debdiff

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

** Description changed:

  [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".
+ 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]
- Low, this change is already in the systemd upstream and in use cosmic and 
later.
+ 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
- Full spread run with the fixed systemd in the "core" snap and a regression 
test: https://github.com/snapcore/snapd/pull/6595
+ The upstream fix is https://github.com/systemd/systemd/pull/8803 and
+ https://github.com/systemd/systemd/pull/11121

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

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 1819240] Re: Many sites will not connect. Very slow. Some siezing.

It sounds like you might be having Internet problems. Are you having any
problems with a particular app or browser?

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

** Changed in: ubuntu
   Status: New => Incomplete

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

Title:
  Many sites will not connect. Very slow. Some siezing.

Status in Ubuntu:
  Incomplete

Bug description:
  N/A

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-142.168-generic 4.4.167
  Uname: Linux 4.4.0-142-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Mar  8 19:20:55 2019
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RS880 [Radeon HD 4200] [1002:9710] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RS880 [Radeon HD 4200] [103c:2ab1]
  InstallationDate: Installed on 2016-09-11 (908 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: Hewlett-Packard p6710f
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-142-generic 
root=UUID=03dbc475-0f36-4145-a3a0-9293828af31a ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/04/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 6.07
  dmi.board.name: 2AB1
  dmi.board.vendor: FOXCONN
  dmi.board.version: 1.00
  dmi.chassis.asset.tag: 4CE0480TV4
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.07:bd05/04/2011:svnHewlett-Packard:pnp6710f:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: p6710f
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.91-2~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Fri Mar  8 18:28:14 2019
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 8
   inputCHICONY HP USB Multimedia Keyboard KEYBOARD, id 9
   inputLogitech USB Optical Mouse MOUSE, id 10
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.8
  xserver.video_driver: radeon

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1819240/+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 1820569] Re: !!