date:20190401

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

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 1583801, 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 1583801
   No sound via headphones (headset) when Ubuntu boots with them plugged in

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

Title:
  [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at
  all if headphones are plugged in before boot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This is only an issue if the headphones are plugged in before boot. If
  I unplug/plug the headphone jack the audio works just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  strassek   1732 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 21:53:00 2019
  InstallationDate: Installed on 2018-05-12 (324 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1309 F pulseaudio
strassek   1732 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0YT4WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0YT4WT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822716/+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 1822716] [NEW] [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at all if headphones are plugged in before boot

2019-04-01 Thread Kevin Strasser

Public bug reported:

This is only an issue if the headphones are plugged in before boot. If I
unplug/plug the headphone jack the audio works just fine.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
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
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  strassek   1732 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 21:53:00 2019
InstallationDate: Installed on 2018-05-12 (324 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  gdm1309 F pulseaudio
  strassek   1732 F pulseaudio
Symptom_Jack: Black Headphone Out, Front
Symptom_Type: No sound at all
Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at 
all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/01/2016
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.3
dmi.board.name: 0YT4WT
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0YT4WT:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9350
dmi.sys.vendor: Dell Inc.

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

Title:
  [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at
  all if headphones are plugged in before boot

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  This is only an issue if the headphones are plugged in before boot. If
  I unplug/plug the headphone jack the audio works just fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  strassek   1732 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 21:53:00 2019
  InstallationDate: Installed on 2018-05-12 (324 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  gdm1309 F pulseaudio
strassek   1732 F pulseaudio
  Symptom_Jack: Black Headphone Out, Front
  Symptom_Type: No sound at all
  Title: [XPS 13 9350, Realtek ALC3246, Black Headphone Out, Front] No sound at 
all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/01/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.3.3
  dmi.board.name: 0YT4WT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.3.3:bd03/01/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0YT4WT:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822716/+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 1819961] Re: binutils: Bug 23465 - wrongly scale non-8-bit x86 displacements

2019-04-01 Thread Matthias Klose

xenial is using 2.26.

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

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

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

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

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

Title:
  binutils: Bug 23465 - wrongly scale non-8-bit x86 displacements

Status in binutils package in Ubuntu:
  Fix Released
Status in binutils source package in Bionic:
  New
Status in binutils source package in Cosmic:
  Fix Released

Bug description:
  Due to following bug in binutils - gnu assembler
  compiled code optimised for AVX512 will not work correctly.

  binutils: Bug 23465 - wrongly scale non-8-bit x86 displacements

  https://sourceware.org/bugzilla/show_bug.cgi?id=23465

  it is fixed in binutils 2.31 but bug exist in 2.30 which is release
  used in xenial. Please consider backporting this bugfix to xenial.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/binutils/+bug/1819961/+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 1687478] Re: "properties" -> "open with" - defective statemachine

[Expired for gtk+3.0 (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  "properties" -> "open with" - defective statemachine

Status in gtk+3.0 package in Ubuntu:
  Expired

Bug description:
  On Ubuntu 16.04.2: The statemachine of the "Open With" dialogue in is
  defective. To open this dialogue reightclick a file, click
  "properties" and select "Open With" tab.

  The behaviour of the button "Set as default" is correct. After
  clicking that button, the behaviour of the "Add" button is also
  correct.

  But clicking only the button "Add" after opening the dialogue without
  click "Set as default", it shows the wrong behavior. Clicking "add"
  does always the same like clicking "Set as Default". Clicking "Set as
  default" one time repairs that behavior.

  Why that? There are two problems.

  Clicking "Add" does have the behaviour like clicking "Set as default"
  to have one "Default Application" set, if no "Default Application" is
  set. That is correct.

  1st problem: This dialogue starts in state believing no default
  application is set. But the already set default application is listed
  as "Default Application". That means, clicking "Add" does the same
  like "Set as default", when it should not.

  2nd related problem: Clicking "Add" to set the "Default Application"
  the first time, does not set the state that the "Default Application"
  is set like clicking "Set as default" does. So the 1st problem is
  repeated.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon May  1 23:09:06 2017
  GsettingsChanges:
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'253'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x522+1030+530'"
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1687478/+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 1796251] Re: gnome-shell crashed with SIGSEGV in __strlen_avx2() from real_save_png() from gdk_pixbuf__png_image_save_to_callback() from gdk_pixbuf_real_save_to_callback() from g

** Bug watch added: gitlab.gnome.org/GNOME/gdk-pixbuf/issues #113
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/113

** Also affects: gdk-pixbuf via
   https://gitlab.gnome.org/GNOME/gdk-pixbuf/issues/113
   Importance: Unknown
   Status: Unknown

** Also affects: gdk-pixbuf (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gdk-pixbuf (Ubuntu)
   Status: New => Confirmed

** Changed in: gdk-pixbuf (Ubuntu)
   Importance: Undecided => High

** Changed in: gnome-shell (Ubuntu)
   Importance: Undecided => High

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

Title:
  gnome-shell crashed with SIGSEGV in __strlen_avx2() from
  real_save_png() from gdk_pixbuf__png_image_save_to_callback() from
  gdk_pixbuf_real_save_to_callback() from gdk_pixbuf_save_to_callbackv()

Status in gdk-pixbuf:
  Unknown
Status in gdk-pixbuf package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-shell.  This problem was most recently seen with package version 
3.30.0-3ubuntu1, the problem page at 
https://errors.ubuntu.com/problem/1473c291c70d181ad72605561ac28f3b860445d5 
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/gdk-pixbuf/+bug/1796251/+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 1822699] Re: System appears to use wayland despite my having Wayland Enable set to false in the .conf file in the gdm3 folder.

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

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 1822527, 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 1822527
   System appears to use wayland despite my having Wayland Enable set to false.

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

Title:
  System appears to use wayland despite my having Wayland Enable set to
  false in the .conf file in the gdm3 folder.

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Ubuntu 18.10
  2. xorg:
Installed: 1:7.7+19ubuntu8
  Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  Basically, when I rebooted the computer, the graphics were scrambled and the 
system behaved as it did when wayland was enabled despite the .conf file saying 
"WaylandEnabled=False", and that line being uncommented.
  Steps to Reproduce:
  1. Edit the .conf file to uncomment "WaylandEnabled"
  2. Reboot the machine
  3. Wait 2 days before booting it back up
  4. Notice the machine is using Wayland despite the conf file specifying 
otherwise.
  Expected Results:
  Machine runs with the behavior of Xorg.
  Actual Results:
  Machine appears to run Wayland.
  Workaround: Edit the conf file again, and then reboot.
  In respect to the diagnostics taken, this issue occurred before I took the 
diagnostics and was able to use Firefox to write this report. This at around 
9:56 PM, EDT on March 31, 2019.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Mon Apr  1 22:00:43 2019
  DistUpgraded: 2018-11-20 23:52:16,217 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
  InstallationDate: Installed on 2018-10-07 (176 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=4c74a6f6-2050-43cf-96aa-f3d050456a3d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-11-21 (131 days ago)
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822699/+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 1822639] Re: Login screen doesn't react to key pressings prior to entering the password

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

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


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

** This bug has been marked a duplicate of bug 1822072
   User selector doesn't have focus from login screen after screen turned off

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

Title:
  Login screen doesn't react to key pressings prior to entering the
  password

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Before the screen when you enter the password, where the clock is
  shown, if a key is pressed, it does not retract the screen upwards, as
  it used to. Now I have to manually use my mouse to drag the screen up.
  Not sure if it is the way it was intended to be used, but I am
  submitting a bug report to be sure.

  I apologise if this is a bug with GNOME, but please do tell me so I
  can send a bug report to them.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
   GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 18:23:16 2019
  DistUpgraded: 2019-03-29 19:19:33,105 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 418.56, 4.18.0-16-generic, x86_64: installed
   nvidia, 418.56, 5.0.0-7-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 530 [17aa:380a]
 Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
  InstallationDate: Installed on 2018-12-31 (91 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 003: ID 5986:0670 Acer, Inc 
   Bus 001 Device 002: ID 17ef:60b2 Lenovo 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 80RU
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=a2f33991-8e13-4dbe-bfae-4a0a1edd71b9 ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to disco on 2019-03-29 (2 days ago)
  XorgConf:
   Section "Extensions"
   Option "XVideo" "Disable"
   EndSection
  dmi.bios.date: 02/15/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: E5CN58WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lenovo ideapad 700-15ISK
  dmi.board.vendor: LENOVO
  dmi.board.version: NO DPK
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 700-15ISK
  dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN58WW:bd02/15/2017:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80RU
  dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
  dmi.product.version: Lenovo ideapad 700-15ISK
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel:

[Touch-packages] [Bug 1822633] Re: Pairing failure with BLE 4.0

The first thing I would try is to wait for a fix for bug 1822533 in case
that helps.

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version:

[Touch-packages] [Bug 1822634] Re: grub boot fail

Could you please explain in more detail what problem you are
experiencing?

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

Title:
  grub boot fail

Status in Ubuntu:
  Incomplete

Bug description:
  no linux file found  16.04 GMT

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 17:04:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company C67 [GeForce 7000M / nForce 610M] 
[103c:30ea]
  InstallationDate: Installed on 2019-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 002: ID 064e:a102 Suyin Corp. Acer/Lenovo Webcam [CN0316]
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=6bf08b7f-515d-43b6-865e-0ea3b9f55772 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd03/22/2011:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family: 103C_5335KV
  dmi.product.name: Compaq Presario F700 Notebook PC
  dmi.product.sku: KW336EA#ABU
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1822634/+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 1822699] Re: System appears to use wayland despite my having Wayland Enable set to false in the .conf file in the gdm3 folder.

2019-04-01 Thread Seija Kijin

Correction: This issue occurred at around 9:55 PM, EDT on April 1, 2019,
not March 31, 2019.

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

Title:
  System appears to use wayland despite my having Wayland Enable set to
  false in the .conf file in the gdm3 folder.

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Ubuntu 18.10
  2. xorg:
Installed: 1:7.7+19ubuntu8
  Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  Basically, when I rebooted the computer, the graphics were scrambled and the 
system behaved as it did when wayland was enabled despite the .conf file saying 
"WaylandEnabled=False", and that line being uncommented.
  Steps to Reproduce:
  1. Edit the .conf file to uncomment "WaylandEnabled"
  2. Reboot the machine
  3. Wait 2 days before booting it back up
  4. Notice the machine is using Wayland despite the conf file specifying 
otherwise.
  Expected Results:
  Machine runs with the behavior of Xorg.
  Actual Results:
  Machine appears to run Wayland.
  Workaround: Edit the conf file again, and then reboot.
  In respect to the diagnostics taken, this issue occurred before I took the 
diagnostics and was able to use Firefox to write this report. This at around 
9:56 PM, EDT on March 31, 2019.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  Date: Mon Apr  1 22:00:43 2019
  DistUpgraded: 2018-11-20 23:52:16,217 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: cosmic
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
  InstallationDate: Installed on 2018-10-07 (176 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  MachineType: Gateway DX4860
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=4c74a6f6-2050-43cf-96aa-f3d050456a3d ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to cosmic on 2018-11-21 (131 days ago)
  dmi.bios.date: 08/01/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P02-A1
  dmi.board.name: IPISB-VR
  dmi.board.vendor: Gateway
  dmi.board.version: 1.01
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gateway
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
  dmi.product.family: Gateway Desktop
  dmi.product.name: DX4860
  dmi.sys.vendor: Gateway
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1822699/+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 1822699] [NEW] System appears to use wayland despite my having Wayland Enable set to false in the .conf file in the gdm3 folder.

2019-04-01 Thread Seija Kijin

Public bug reported:

1. Ubuntu 18.10
2. xorg:
  Installed: 1:7.7+19ubuntu8
Version table:
 *** 1:7.7+19ubuntu8 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
100 /var/lib/dpkg/status
Basically, when I rebooted the computer, the graphics were scrambled and the 
system behaved as it did when wayland was enabled despite the .conf file saying 
"WaylandEnabled=False", and that line being uncommented.
Steps to Reproduce:
1. Edit the .conf file to uncomment "WaylandEnabled"
2. Reboot the machine
3. Wait 2 days before booting it back up
4. Notice the machine is using Wayland despite the conf file specifying 
otherwise.
Expected Results:
Machine runs with the behavior of Xorg.
Actual Results:
Machine appears to run Wayland.
Workaround: Edit the conf file again, and then reboot.
In respect to the diagnostics taken, this issue occurred before I took the 
diagnostics and was able to use Firefox to write this report. This at around 
9:56 PM, EDT on March 31, 2019.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
Date: Mon Apr  1 22:00:43 2019
DistUpgraded: 2018-11-20 23:52:16,217 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
DistroCodename: cosmic
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
   Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:3207]
InstallationDate: Installed on 2018-10-07 (176 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
MachineType: Gateway DX4860
ProcEnviron:
 TERM=linux
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=4c74a6f6-2050-43cf-96aa-f3d050456a3d ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to cosmic on 2018-11-21 (131 days ago)
dmi.bios.date: 08/01/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P02-A1
dmi.board.name: IPISB-VR
dmi.board.vendor: Gateway
dmi.board.version: 1.01
dmi.chassis.type: 3
dmi.chassis.vendor: Gateway
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP02-A1:bd08/01/2011:svnGateway:pnDX4860:pvr:rvnGateway:rnIPISB-VR:rvr1.01:cvnGateway:ct3:cvr:
dmi.product.family: Gateway Desktop
dmi.product.name: DX4860
dmi.sys.vendor: Gateway
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.10.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.10.2
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


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

Title:
  System appears to use wayland despite my having Wayland Enable set to
  false in the .conf file in the gdm3 folder.

Status in xorg package in Ubuntu:
  New

Bug description:
  1. Ubuntu 18.10
  2. xorg:
Installed: 1:7.7+19ubuntu8
  Version table:
   *** 1:7.7+19ubuntu8 500
  500 http://us.archive.ubuntu.com/ubuntu cosmic/main amd64 Packages
  100 /var/lib/dpkg/status
  Basically, when I rebooted the computer, the graphics were scrambled and the 
system behaved as it did when wayland was enabled despite the .conf file saying 
"WaylandEnabled=False", and that line being uncommented.
  Steps to Reproduce:
  1. Edit the .conf file to uncomment "WaylandEnabled"
  2. Reboot the machine
  3. Wait 2 days before booting it back up
  4. Notice the machine is using Wayland despite the conf file specifying 
otherwise.
  Expected Results:
  Machine runs with the behavior of Xorg.
  Actual Results:
  Machine appears to run Wayland.
  Workaround: Edit the conf file again, and then reboot.
  In respect to the diagnostics taken, this issue occurred before I took the 
diagnostics and was able to use Firefox to write this report. This at around 
9:56 PM, EDT on March 31, 2019.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic

[Touch-packages] [Bug 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

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

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

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

Title:
  lightdm login screen briefly appears and then blanks out on Intel(R)
  Core(TM)2 Duo CPU T5870

Status in lightdm package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  Okay the has happened recently at least since march 18, 2019 iso and
  march 22, 2019 iso are both effected very similar to one of my
  previously reported bugs .. which was related to xorg not being
  installed ..

  
  back ground .. PC is lenovo sl 500 with evo860 SSD drive

  3 partions contain installs of disco sda1 -- main working system -- I
  usually install grub from here as master ..

  sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
  03-22-2019 repectively

  
  on the test installs as long as the iso is using the grub boot loader 
installed from that install the system will boot normally .. the display manger 
tends to flicker on and off but does final start and login can proceed. 

  but if another install re-installs grub as master  the display manager
  fails to stay active or even come-up  for sda6 or sda7 only if their
  own grubs are reinstalled will they work normally

  sda1 display manager/xorg login works always no matter which "grub-
  source" is in control.

  if I use rescue boot from any grub as master I can get the displays to work 
by running dpkg fix which does nothing .. and then resuming the boot .. then 
things work normally..
  if the "non-rescue" boots are used the screen/computer locks and only a power 
down and reboot gives access. (sometime requiring radical depowering .. 
unpluging and removing battery)

  now the is a message that appears that RCs??? level is missing.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu11
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Mon Mar 25 11:25:58 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GpuHangFrequency: Several times a day
  GpuHangReproducibility: Yes, I can easily reproduce it
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
 Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller 
[17aa:20e4]
  InstallationDate: Installed on 2019-03-23 (1 days ago)
  InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
  MachineType: LENOVO 2746CTO
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2010
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 6AET64WW
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: 2746CTO
  dmi.board.vendor: LENOVO
  dmi.board.version: LENOVO 6AET64WW
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: LENOVO 6AET64WW
  dmi.modalias: 
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
  dmi.product.name: 2746CTO
  dmi.product.version: ThinkPad SL500
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1821609/+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 1236749] Re: Gnome shell extensions disabled at every startup

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

This bug is closed as a duplicate of bug 1385572 which is also closed.

If you have any problems in 19.04 then please open a new bug.

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

Title:
  Gnome shell extensions disabled at every startup

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Since gnome-shell 3.10, my extensions are disabled by default at every boot.
  I need to launch Tweak Tool to enable theme by hand every time.

  Both pre-installed extensions ( AlternateTab) and user-installed ones
  (top-icons)

  Step to reproduce :
  Enable an extension in Tweak Tool ( Alternate Tab for example)
  reboot computer,
  open Tweak Tool : Alternate tab is disabled.

  Running on Ubuntu 13.10
  GNOME Shell 3.10.0.1
  gnome-tweak-tool 3.10..0-0ubuntu1-saucy1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1236749/+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 1820132] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:gdb_command

** Branch linked: lp:~ubuntu-core-dev/ubuntu/disco/apport/ubuntu

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  all@162:collect_info:process_report:add_gdb_info:gdb_command

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Disco:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu23, the problem page at 
https://errors.ubuntu.com/problem/4a48673e60f08b7d2b9067d1b47766a57f7e693e 
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/apport/+bug/1820132/+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 1822688] [NEW] it does not print on printer

2019-04-01 Thread VijayPatel

Public bug reported:

os: ubuntu 18.04.2  ,trying to print with Canon Imageclass MF 6530
.message says: printing completed, but it does not print the
document.dell computer xps 8930

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: vim (not installed)
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 15:50:56 2019
InstallationDate: Installed on 2019-03-29 (3 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 LANG=en_US.UTF-8
 TERM=xterm-256color
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=
 PATH=(custom, no user)
SourcePackage: vim
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  it does not print on printer

Status in vim package in Ubuntu:
  New

Bug description:
  os: ubuntu 18.04.2  ,trying to print with Canon Imageclass MF 6530
  .message says: printing completed, but it does not print the
  document.dell computer xps 8930

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vim (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 15:50:56 2019
  InstallationDate: Installed on 2019-03-29 (3 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   LANG=en_US.UTF-8
   TERM=xterm-256color
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   PATH=(custom, no user)
  SourcePackage: vim
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/vim/+bug/1822688/+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 1794629] Re: CVE-2018-15473 - User enumeration vulnerability

2019-04-01 Thread Seth Arnold

Root, version 1:7.6p1-4ubuntu0.1 included the fix for CVE-2018-15473.

Version 1:7.6p1-4ubuntu0.2 is included in the disc image ubuntu-18.04.2
-server-amd64:

$ sha256sum ubuntu-18.04.2-server-amd64.iso 
a2cb36dc010d98ad9253ea5ad5a07fd6b409e3412c48f1860536970b073c98f5  
ubuntu-18.04.2-server-amd64.iso
$ bsdtar tf ubuntu-18.04.2-server-amd64.iso | grep openssh
pool/main/o/openssh
pool/main/o/openssh/openssh-client-udeb_7.6p1-4ubuntu0.2_amd64.udeb
pool/main/o/openssh/openssh-client_7.6p1-4ubuntu0.2_amd64.deb
pool/main/o/openssh/openssh-server-udeb_7.6p1-4ubuntu0.2_amd64.udeb
pool/main/o/openssh/openssh-server_7.6p1-4ubuntu0.2_amd64.deb
pool/main/o/openssh/openssh-sftp-server_7.6p1-4ubuntu0.2_amd64.deb
pool/main/o/openssh/ssh_7.6p1-4ubuntu0.2_all.deb

1:7.6p1-4ubuntu0.2 includes the fix from 1:7.6p1-4ubuntu0.1 and fixes three 
more CVEs:
- CVE-2018-20685
- CVE-2019-6109
- CVE-2019-6111

During the install, you have the option of downloading and installing updates. 
These additional updates include openssh version 1:7.6p1-4ubuntu0.3 which 
includes addition fixes for one CVE:
- CVE-2019-6111

Thanks

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2018-20685

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-6109

** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2019-6111

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

Title:
  CVE-2018-15473 - User enumeration vulnerability

Status in openssh package in Ubuntu:
  Fix Released
Status in openssh source package in Trusty:
  Fix Released
Status in openssh source package in Xenial:
  Fix Released
Status in openssh source package in Bionic:
  Fix Released
Status in openssh source package in Cosmic:
  Fix Released

Bug description:
  https://nvd.nist.gov/vuln/detail/CVE-2018-15473

  OpenSSH through 7.7 is prone to a user enumeration vulnerability due
  to not delaying bailout for an invalid authenticating user until after
  the packet containing the request has been fully parsed, related to
  auth2-gss.c, auth2-hostbased.c, and auth2-pubkey.c.

  Fixed in Debian: https://www.debian.org/security/2018/dsa-4280

  Currently pending triage? https://people.canonical.com/~ubuntu-
  security/cve/2018/CVE-2018-15473.html

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1794629/+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 1396160] Re: /usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info

** Branch linked: lp:~ubuntu-core-dev/ubuntu/disco/apport/ubuntu

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

Title:
  
/usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Disco:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.14.7-0ubuntu10, the problem page at
  https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c
  contains more details.

  More Buckets:
  https://errors.ubuntu.com/problem/2a97a88118a1d8746cff239205a4cd9eb3d0357d
  https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462

  
  Other reference:
  bug 1394919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1396160/+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 1396160] Re: /usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info

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

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

Title:
  
/usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Disco:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.14.7-0ubuntu10, the problem page at
  https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c
  contains more details.

  More Buckets:
  https://errors.ubuntu.com/problem/2a97a88118a1d8746cff239205a4cd9eb3d0357d
  https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462

  
  Other reference:
  bug 1394919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1396160/+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 1396160] Re: /usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info

** Branch linked: lp:apport

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

Title:
  
/usr/share/apport/recoverable_problem:PermissionError:/usr/share/apport/recoverable_problem@75:main:add_proc_info

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Disco:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.14.7-0ubuntu10, the problem page at
  https://errors.ubuntu.com/problem/9a1df90760a88c9b4e5e7e3b4ef450f6b5669c7c
  contains more details.

  More Buckets:
  https://errors.ubuntu.com/problem/2a97a88118a1d8746cff239205a4cd9eb3d0357d
  https://errors.ubuntu.com/problem/72c621876cfe04b51b37f8f3ef08c3da0460b462

  
  Other reference:
  bug 1394919

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1396160/+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 1809247] Re: SetReportCrashes to true dbus call failed

** Branch linked: lp:~ubuntu-core-dev/ubuntu/disco/apport/ubuntu

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

Title:
  SetReportCrashes to true dbus call failed

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Disco:
  In Progress

Bug description:
  The following copied from screenshot 2018-12-20 11-50-53
  Saving crash reporting state failed, Can't set auto auto or never 
  reporting mode.

  Command '['/usr/bin/gdbus','call','-y','-d',
  'com.ubuntu.WhoopsiePreferences','-o','/com/ubuntu/
  WhoopsiePreferences','-m',
  'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']'
  returned non-zero exit status 1.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-43 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  Date: Thu Dec 20 11:22:53 2018
  Dependencies:
   
  DuplicateSignature:
   package:linux-headers-4.15.0-43:4.15.0-43.46
   Unpacking linux-modules-extra-4.15.0-43-generic (4.15.0-43.46) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-OeaFpG/04-linux-modules-extra-4.15.0-43-generic_4.15.0-43.46_i386.deb
 (--unpack):
unable to open 
'/lib/modules/4.15.0-43-generic/kernel/drivers/infiniband/hw/cxgb4/iw_cxgb4.ko.dpkg-new':
 Operation not permitted
  ErrorMessage: unable to create new file 
'/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted
  InstallationDate: Installed on 2017-12-03 (382 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: linux
  Title: package linux-headers-4.15.0-43 4.15.0-43.46 failed to 
install/upgrade: unable to create new file 
'/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted
  UpgradeStatus: Upgraded to bionic on 2018-09-18 (92 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1809247/+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 1820132] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:gdb_command

** Changed in: apport (Ubuntu Disco)
   Status: Triaged => In Progress

** Changed in: apport (Ubuntu Disco)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  all@162:collect_info:process_report:add_gdb_info:gdb_command

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Disco:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu23, the problem page at 
https://errors.ubuntu.com/problem/4a48673e60f08b7d2b9067d1b47766a57f7e693e 
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/apport/+bug/1820132/+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 1809247] Re: SetReportCrashes to true dbus call failed

** Changed in: apport (Ubuntu Disco)
   Status: Triaged => In Progress

** Changed in: apport (Ubuntu Disco)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  SetReportCrashes to true dbus call failed

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Disco:
  In Progress

Bug description:
  The following copied from screenshot 2018-12-20 11-50-53
  Saving crash reporting state failed, Can't set auto auto or never 
  reporting mode.

  Command '['/usr/bin/gdbus','call','-y','-d',
  'com.ubuntu.WhoopsiePreferences','-o','/com/ubuntu/
  WhoopsiePreferences','-m',
  'com.ubuntu.WhoopsiePreferences.SetReportCrashes', 'true']'
  returned non-zero exit status 1.

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: linux-headers-4.15.0-43 4.15.0-43.46
  ProcVersionSignature: Ubuntu 4.15.0-42.45-generic 4.15.18
  Uname: Linux 4.15.0-42-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  Date: Thu Dec 20 11:22:53 2018
  Dependencies:
   
  DuplicateSignature:
   package:linux-headers-4.15.0-43:4.15.0-43.46
   Unpacking linux-modules-extra-4.15.0-43-generic (4.15.0-43.46) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-OeaFpG/04-linux-modules-extra-4.15.0-43-generic_4.15.0-43.46_i386.deb
 (--unpack):
unable to open 
'/lib/modules/4.15.0-43-generic/kernel/drivers/infiniband/hw/cxgb4/iw_cxgb4.ko.dpkg-new':
 Operation not permitted
  ErrorMessage: unable to create new file 
'/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted
  InstallationDate: Installed on 2017-12-03 (382 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20171017.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6
  SourcePackage: linux
  Title: package linux-headers-4.15.0-43 4.15.0-43.46 failed to 
install/upgrade: unable to create new file 
'/var/lib/dpkg/info/linux-headers-4.15.0-43.list-new': Operation not permitted
  UpgradeStatus: Upgraded to bionic on 2018-09-18 (92 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1809247/+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 1820132] Re: /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport/whoopsie-upload-all@162:collect_info:process_report:add_gdb_info:gdb_command

** Branch linked: lp:apport

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

Title:
  /usr/share/apport/whoopsie-upload-all:AssertionError:/usr/share/apport
  /whoopsie-upload-
  all@162:collect_info:process_report:add_gdb_info:gdb_command

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Disco:
  Triaged

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu23, the problem page at 
https://errors.ubuntu.com/problem/4a48673e60f08b7d2b9067d1b47766a57f7e693e 
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/apport/+bug/1820132/+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 1658188] Re: /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

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

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

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

Title:
  /usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-
  gtk@597:run_argv:run_crashes

Status in apport package in Ubuntu:
  Fix Released
Status in apport source package in Xenial:
  Fix Released
Status in apport source package in Bionic:
  New
Status in apport source package in Cosmic:
  New

Bug description:
  [Test Case]
  Check Error Tracker bucket and make sure version from -proposed doesn't show 
up there. Given that this happens a whole bunch we should know pretty quick if 
its fixed.

  [Regression Potential]
  The test being modified is designed to not report crashes that happen during 
logout. It's possible that some reports don't have a Date in them but in that 
case we couldn't compare the logind_session information to the Date anyway so 
those crashes would have been reported anyway. Regardless, the potential is 
that we'll have some more crashes reported about things crashing on logout 
which is better than the hundreds of crashes we get like this one.

  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.3-0ubuntu8.2, the problem page at 
https://errors.ubuntu.com/problem/65cb22d7c29a308dad9368b971e1b8d6384c9089 
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 you can request it at 
http://forms.canonical.com/reports/.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1658188/+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 1822681] Re: /usr/share/apport/apport-kde:TypeError:/usr/share/apport/apport-kde@532:run_argv:run_crashes

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

** This bug has been marked a duplicate of bug 1658188
   
/usr/share/apport/apport-gtk:TypeError:/usr/share/apport/apport-gtk@597:run_argv:run_crashes

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

Title:
  /usr/share/apport/apport-kde:TypeError:/usr/share/apport/apport-
  kde@532:run_argv:run_crashes

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu14, the problem page at 
https://errors.ubuntu.com/problem/04befe96ffc67d2d1c0d66cefbc9b3539df59b19 
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/apport/+bug/1822681/+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 1822681] [NEW] /usr/share/apport/apport-kde:TypeError:/usr/share/apport/apport-kde@532:run_argv:run_crashes

2019-04-01 Thread errors.ubuntu.com bug bridge

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

Public bug reported:

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

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


** Tags: artful bionic cosmic disco zesty

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

Title:
  /usr/share/apport/apport-kde:TypeError:/usr/share/apport/apport-
  kde@532:run_argv:run_crashes

Status in apport package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
apport.  This problem was most recently seen with package version 
2.20.10-0ubuntu14, the problem page at 
https://errors.ubuntu.com/problem/04befe96ffc67d2d1c0d66cefbc9b3539df59b19 
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/apport/+bug/1822681/+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 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

2019-04-01 Thread Steve Langasek

FFe approved.

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

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1442512] Re: Apport-kde crash when reporting bugs

** Changed in: apport (Ubuntu Vivid)
   Status: Confirmed => Won't Fix

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

Title:
  Apport-kde crash when reporting bugs

Status in Apport:
  Confirmed
Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Vivid:
  Won't Fix

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding apport.  This problem was most recently seen with version
  2.17-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/1b2e1c9cdac684074f5f97db85ae78c1b8a2b3ac
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/apport/+bug/1442512/+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 1774768] Re: systemd-udevd eats cpu in infinite loop when nvidia card is not plugged

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

Title:
  systemd-udevd eats cpu in infinite loop  when nvidia card is not
  plugged

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  i have a roaming ssd disk ubuntu 18.04 with proprietaty nvidia drivers
  installed from ubuntu thid party repository:

  ii  nvidia-cuda-dev  9.1.85-3ubuntu1amd64
NVIDIA CUDA development files
  ii  nvidia-cuda-doc  9.1.85-3ubuntu1all  
NVIDIA CUDA and OpenCL documentation
  ii  nvidia-cuda-gdb  9.1.85-3ubuntu1amd64
NVIDIA CUDA Debugger (GDB)
  ii  nvidia-cuda-toolkit  9.1.85-3ubuntu1amd64
NVIDIA CUDA development toolkit
  ii  nvidia-dkms-396  396.24-0ubuntu0~gpu18.04.1 amd64
NVIDIA DKMS package
  ii  nvidia-kernel-common-396 396.24-0ubuntu0~gpu18.04.1 amd64
Shared files used with the kernel module
  ii  nvidia-kernel-source-396 396.24-0ubuntu0~gpu18.04.1 amd64
NVIDIA kernel source package
  ii  nvidia-profiler  9.1.85-3ubuntu1amd64
NVIDIA Profiler for CUDA and OpenCL
  ii  nvidia-settings  396.24-0ubuntu0~gpu18.04.1 amd64
Tool for configuring the NVIDIA graphics driver
  ii  nvidia-visual-profiler   9.1.85-3ubuntu1amd64
NVIDIA Visual Profiler for CUDA and OpenCL
  r

  When i boot on my nvidia system , no problem.

  when i boot on other system , with other card, systemd-udevd eats lots
  cpu (nearby 100% or little more) and in logs i see infinite loop
  logging:

  Jun  2 11:23:16 localhost [19963]: failed to execute '/usr/bin/nvidia-smi' 
'/usr/bin/nvidia-smi': No such file or directory
  Jun  2 11:23:16 localhost systemd-udevd[492]: Process '/usr/bin/nvidia-smi' 
failed with exit code 2.
  Jun  2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Start 
request repeated too quickly.
  Jun  2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Failed 
with result 'exit-code'.
  Jun  2 11:23:16 localhost systemd[1]: Failed to start NVIDIA Persistence 
Daemon.
  Jun  2 11:23:16 localhost kernel: [ 2227.682538] nvidia-nvlink: Nvlink Core 
is being initialized, major device number 241
  Jun  2 11:23:16 localhost kernel: [ 2227.682917] NVRM: No NVIDIA graphics 
adapter found!
  Jun  2 11:23:16 localhost kernel: [ 2227.683149] nvidia-nvlink: Unregistered 
the Nvlink Core, major device number 241
  Jun  2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe 
nvidia-modeset' failed with exit code 1.
  Jun  2 11:23:16 localhost kernel: [ 2227.756646] nvidia-nvlink: Nvlink Core 
is being initialized, major device number 241
  Jun  2 11:23:16 localhost kernel: [ 2227.756971] NVRM: No NVIDIA graphics 
adapter found!
  Jun  2 11:23:16 localhost kernel: [ 2227.757149] nvidia-nvlink: Unregistered 
the Nvlink Core, major device number 241
  Jun  2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe 
nvidia-drm' failed with exit code 1.
  Jun  2 11:23:16 localhost kernel: [ 2227.824072] nvidia-nvlink: Nvlink Core 
is being initialized, major device number 241
  Jun  2 11:23:16 localhost kernel: [ 2227.824383] NVRM: No NVIDIA graphics 
adapter found!
  Jun  2 11:23:16 localhost kernel: [ 2227.824596] nvidia-nvlink: Unregistered 
the Nvlink Core, major device number 241
  Jun  2 11:23:16 localhost systemd-udevd[492]: Process '/sbin/modprobe 
nvidia-uvm' failed with exit code 1.
  Jun  2 11:23:16 localhost [19972]: failed to execute '/usr/bin/nvidia-smi' 
'/usr/bin/nvidia-smi': No such file or directory
  Jun  2 11:23:16 localhost systemd-udevd[492]: Process '/usr/bin/nvidia-smi' 
failed with exit code 2.
  Jun  2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Start 
request repeated too quickly.
  Jun  2 11:23:16 localhost systemd[1]: nvidia-persistenced.service: Failed 
with result 'exit-code'.
  Jun  2 11:23:16 localhost systemd[1]: Failed to start NVIDIA Persistence 
Daemon.

  the nvidia-uvm module is listed in /etc/modules.

  # /etc/modules: kernel modules to load at boot time.
  #
  # This file contains the names of kernel modules that should be loaded
  # at boot time, one per line. Lines beginning with "#" are ignored.
  nvidia-uvm

  it should just fail at boot time and do nothing else.

  
  when stopping systemd-udevd and starting it again, the problem disappear.


  
  i hadn't this problem with ubuntu 16.X/17.X.
   it may be a nvidia driver/software pb too, so i will do a bug report on 
nvidia driver too.

  Regards

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: udev 237-3ubuntu10
  ProcVersionSignature:

[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

** Description changed:

  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not in
  a non-graphical one.
+ 
+ N.B. you first need to create a /var/log/plymouth-debug.log file for the
+ plymouth apport package hook to actually trigger this.
  
  ubuntu@disco:~$ ubuntu-bug plymouth
  
  *** Collecting problem information
  
  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized
  
  This incident has been reported.
  
  Subsequently, bug reports from servers will contain less information.

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  N.B. you first need to create a /var/log/plymouth-debug.log file for
  the plymouth apport package hook to actually trigger this.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1822633] Re: Pairing failure with BLE 4.0

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

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2017
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 2.0.7

[Touch-packages] [Bug 1822633] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1822633/+attachment/5251761/+files/Lspci.txt

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2017

[Touch-packages] [Bug 1820317] Re: The firewalld autopackage tests fail due to iptables

This bug was fixed in the package firewalld - 0.6.3-5ubuntu4

---
firewalld (0.6.3-5ubuntu4) disco; urgency=medium

  * Re-add Recommends for ebtables and remove the iptables dependency on 1.8
for now until iptables 1.8.3 is available (LP: #1820317 and also see Debian
bug 914694)

 -- Jamie Strandboge   Mon, 25 Mar 2019 13:12:46 +

** Changed in: firewalld (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 iptables in Ubuntu.
https://bugs.launchpad.net/bugs/1820317

Title:
  The firewalld autopackage tests fail due to iptables

Status in firewalld package in Ubuntu:
  Fix Released
Status in iptables package in Ubuntu:
  Won't Fix
Status in iptables package in Debian:
  Fix Committed

Bug description:
  The firewalld autopkgtest fail in disco on what looks like an iptables
  issue

  
https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac
  /autopkgtest-
  disco/disco/amd64/f/firewalld/20190315_154203_ef4d6@/log.gz

  'Mar 15 15:41:39 autopkgtest firewalld[1691]: ERROR: 
'/usr/sbin/iptables-restore -w -n' failed: iptables-restore v1.8.2 (nf_tables): 
   line 4: RULE_REPLACE failed (No 
such file or directory): rule in chain INPUT
   line 4: RULE_REPLACE failed (No 
such file or directory): rule in chain OUTPUT'

  That looks like the issue reported on 
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=914694 which is fixed in 
upstream iptables
  https://git.netfilter.org/iptables/commit/?id=947c51c95

  That fix seems to depends on git master changes from libnftnl
  https://git.netfilter.org/libnftnl/log/
  ('chain: Support per chain rules list' and following commits)

  Unsure at this point what's best disco, if we should start looking at
  backporting those changes?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firewalld/+bug/1820317/+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 1822633] syslog.txt

apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1822633/+attachment/5251770/+files/syslog.txt

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2017

[Touch-packages] [Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch

2019-04-01 Thread Sergio Cazzolato

Validation completed. No errors detected on:

bionic: 237-3ubuntu10.17
core18: systemd 237

** 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1778936

Title:
  please re-add Support-system-image-read-only-etc.patch

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

Bug description:
  [Impact]

   * core18 systems fail to update hostname
   * this happens due to /etc/hostname actually being a symlink to a file under 
/etc/writable/, adjust hostnamed to take that into account when trying to 
update /etc/hostname

  [Test Case]

   * run a core18 system, check that dhcp acquire hostname is correctly
  updated in /etc/writable/hostname

  [Regression Potential]

   * This is cherrypick of code that has gone missing since xenial.
   * There is no change of behaviour for the classic systems.
   * Currently, core18 systems simply fail to update hostname/machine-info 
files, thus the worst case is that they will still fail to do so.

  [Other Info]
   
   * original bug report

  The 16.04 version of systemd had a patch to support the read-only etc.
  For core18 we will also need this change because core18 is still not
  on a fully writable etc.

  I will attach a debdiff against the current bionic version of systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+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 1822633] rfkill.txt

apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1822633/+attachment/5251769/+files/rfkill.txt

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2017

[Touch-packages] [Bug 1822633] getfacl.txt

apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1822633/+attachment/5251768/+files/getfacl.txt

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date:

[Touch-packages] [Bug 1822633] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1822633/+attachment/5251762/+files/Lsusb.txt

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2017

[Touch-packages] [Bug 1822633] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1822633/+attachment/5251767/+files/UdevDb.txt

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 05/24/2017

[Touch-packages] [Bug 1822633] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1822633/+attachment/5251764/+files/ProcCpuinfoMinimal.txt

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

[Touch-packages] [Bug 1822633] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1822633/+attachment/5251766/+files/ProcModules.txt

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date:

[Touch-packages] [Bug 1822633] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1822633/+attachment/5251765/+files/ProcInterrupts.txt

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

[Touch-packages] [Bug 1822633] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1822633/+attachment/5251763/+files/ProcCpuinfo.txt

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date:

[Touch-packages] [Bug 1822633] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1822633/+attachment/5251760/+files/Dependencies.txt

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2019-01-21 (70 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  InterestingModules: bnep btusb bluetooth
  MachineType: Dell Inc. XPS 13 9360
  Package: linux
  PackageArchitecture: amd64
  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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
  Tags: third-party-packages bionic
  Uname: Linux 4.15.0-46-generic x86_64
  UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

[Touch-packages] [Bug 1822633] Re: Pairing failure with BLE 4.0

apport information

** Tags added: apport-collected bionic third-party-packages

** Description changed:

  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.
  
  Here is the FW from Jason.
  
  Details:
  
  ===
  
  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:
  
  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5
  
  When I try to pair the PN557W, however, I only get the following:
  
  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...
  
  The "allowed" value is a bitmap, so 0024 means that only event code
  2 and 5 are allowed. The "smp_sig_channel()" function does allow code 11
  ("SMP_CMD_SECURITY_REQ") to be sent from the device at the beginning of
  the connection but *only* if the "smp" variable hasn't been set yet. It
  looks like the host starts the pairing process and initializes the "smp"
  variable, which then prevents code 11 from being allowed.
  
  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.
  
  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the AuthReq
  flags. All zero would seem to indicate that no security is requested,
  and I'm not sure if the kernel enforces a minimum security level or
  something.
  
- Finally, I also tried the suggestion at
- https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the
- assumption that maybe this is an issue caused by LE communication rather
- than classic BR/EDR communication. Alas, my computer wasn't even able to
- start the pairing process after making the change.
+ Finally, I also tried the suggestion at 
https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the assumption 
that maybe this is an issue caused by LE communication rather than classic 
BR/EDR communication. Alas, my computer wasn't even able to start the pairing 
process after making the change.
+ --- 
+ ProblemType: Bug
+ ApportVersion: 2.20.9-0ubuntu7.6
+ Architecture: amd64
+ CurrentDesktop: ubuntu:GNOME
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2019-01-21 (70 days ago)
+ InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
+ InterestingModules: bnep btusb bluetooth
+ MachineType: Dell Inc. XPS 13 9360
+ Package: linux
+ PackageArchitecture: amd64
+ 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=c045330d-1b98-41ff-99cb-26bf69b59fd3 ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-46.49-generic 4.15.18
+ Tags: third-party-packages bionic
+ Uname: Linux 4.15.0-46-generic x86_64
+ UnreportableReason: This is not an official Ubuntu package. Please remove any 
third party package and try again.
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 05/24/2017
+ dmi.bios.vendor:

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

2019-04-01 Thread Sergio Cazzolato

Validation completed. No errors detected on:

xenial: 229-4ubuntu21.19
bionic: 237-3ubuntu10.17
core18: systemd 237


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

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

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

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
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 1816547] Re: SRU 2.56.4 to bionic

2019-04-01 Thread Treviño

As per GNOME MRE, package hit properly proposed.

** 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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1816547

Title:
  SRU 2.56.4 to bionic

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  New upstream bug fix microrelease

  * Various buffer overflow fixes in GMarkup/GVariant/GDBus (#1582)

  * Bug fixes:
   #1588 Moving a bookmark item to the same URI causes a crash
   #1582 Backport GMarkup/GVariant/GDBus fixes to glib-2-58 and glib-2-56

  Plus fix for LP: #1760569

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Test various parts of the desktop.

    - Logging in
    - Shutting down
    - Starting a variety of apps and checking that they work
  + rhythmbox (play a song using gstreamer)
  + cheese (look at yourself with your webcam using gstreamer)
  + network-manager
  + epiphany (web stuff works)

  Monitor the error tracker for any increases.

  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1816547/+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 1236749] Re: Gnome shell extensions disabled at every startup

2019-04-01 Thread Xosé

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

Confirming this on 19.04-development, not only after every new boot but
also after suspend.

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

Title:
  Gnome shell extensions disabled at every startup

Status in Ubuntu GNOME:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in upstart package in Ubuntu:
  Confirmed

Bug description:
  Since gnome-shell 3.10, my extensions are disabled by default at every boot.
  I need to launch Tweak Tool to enable theme by hand every time.

  Both pre-installed extensions ( AlternateTab) and user-installed ones
  (top-icons)

  Step to reproduce :
  Enable an extension in Tweak Tool ( Alternate Tab for example)
  reboot computer,
  open Tweak Tool : Alternate tab is disabled.

  Running on Ubuntu 13.10
  GNOME Shell 3.10.0.1
  gnome-tweak-tool 3.10..0-0ubuntu1-saucy1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1236749/+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 1822633] Missing required logs.

2019-04-01 Thread Ubuntu Kernel Bot

This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:

apport-collect 1822633

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.

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

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at
  https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the
  assumption that maybe this is an issue caused by LE communication
  rather than classic BR/EDR communication. Alas, my computer wasn't
  even able to start the pairing process after making the change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1822633/+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 1822633] Re: Pairing failure with BLE 4.0

2019-04-01 Thread Mario Limonciello

** Project changed: snappy-hwe-snaps => linux (Ubuntu)

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at
  https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the
  assumption that maybe this is an issue caused by LE communication
  rather than classic BR/EDR communication. Alas, my computer wasn't
  even able to start the pairing process after making the change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1822633/+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 1822633] Re: Pairing failure with BLE 4.0

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

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

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at
  https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the
  assumption that maybe this is an issue caused by LE communication
  rather than classic BR/EDR communication. Alas, my computer wasn't
  even able to start the pairing process after making the change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1822633/+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 1822633] Re: Pairing failure with BLE 4.0

2019-04-01 Thread Mario Limonciello

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

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

Title:
  Pairing failure with BLE 4.0

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

Bug description:
  When attempting to pair a BLE 4.0 pen using Bluez, we receive
  authentication errors.

  Here is the FW from Jason.

  Details:

  ===

  I added a few debug statements (patch attached) to the kernel's
  net/bluetooth/smp.c:smp_sig_channel() function
  (https://github.com/torvalds/linux/blob/v5.0/net/bluetooth/smp.c#L2883).
  When I try to pair the PN579X, I get the following logs:

  [ 5653.563048] DBG: Received code 2 (allowed = 0024) with 6 bytes
  [ 5653.563053] DBG: Processing code...
  [ 5653.709572] DBG: Received code 3 (allowed = 0028) with 16 bytes
  [ 5653.709577] DBG: Processing code...
  [ 5653.807085] DBG: Received code 4 (allowed = 0030) with 16 bytes
  [ 5653.807089] DBG: Processing code...
  [ 5654.148553] DBG: Received code 6 (allowed = 0060) with 16 bytes
  [ 5654.148557] DBG: Processing code...
  [ 5654.197024] DBG: Received code 7 (allowed = 00a0) with 10 bytes
  [ 5654.197027] DBG: Processing code...
  [ 5654.245824] DBG: Received code 8 (allowed = 0120) with 16 bytes
  [ 5654.245828] DBG: Processing code...
  [ 5654.246178] DBG: Received code 9 (allowed = 0220) with 7 bytes
  [ 5654.246182] DBG: Processing code...
  [ 5657.610656] input: Dell Active Pen PN579X Keyboard as 
/devices/virtual/misc/uhid/0005:413C:81D5.0004/input/input23
  [ 5657.610997] hid-generic 0005:413C:81D5.0004: input,hidraw0: BLUETOOTH HID 
vf.08 Keyboard [Dell Active Pen PN579X] on 18:56:80:18:6A:E5

  When I try to pair the PN557W, however, I only get the following:

  [   64.924901] DBG: Received code 11 (allowed = 0024) with 1 bytes
  [   64.924906] DBG: AuthReq = 00
  [   64.924907] ERR: Code not allowed on existing connection
  [   64.924943] Bluetooth: hci0: unexpected SMP command 0x0b from 
bc:82:5d:fa:5e:b7
  [   64.940314] NET: Registered protocol family 38
  [   65.022326] DBG: Received code 5 (allowed = 0024) with 1 bytes
  [   65.022331] DBG: Processing code...

  The "allowed" value is a bitmap, so 0024 means that only event
  code 2 and 5 are allowed. The "smp_sig_channel()" function does allow
  code 11 ("SMP_CMD_SECURITY_REQ") to be sent from the device at the
  beginning of the connection but *only* if the "smp" variable hasn't
  been set yet. It looks like the host starts the pairing process and
  initializes the "smp" variable, which then prevents code 11 from being
  allowed.

  I did try to force the code to allow code 11 at any time, but this
  didn't seem to help the situation any. The device still sent code 5
  ("SMP_CMD_PAIRING_FAIL") immediately afterwards, just like it does in
  the trace above. Worse, the kernel logs a general protection fault
  several seconds afterwards, so it clearly doesn't like the workaround.

  I also find it odd that the "AuthReq = 00". I found a copy of the core
  Bluetooth spec at https://www.bluetooth.com/specifications/bluetooth-
  core-specification and Vol. 3 Part H Chapter 3.6.7 describes the
  AuthReq flags. All zero would seem to indicate that no security is
  requested, and I'm not sure if the kernel enforces a minimum security
  level or something.

  Finally, I also tried the suggestion at
  https://www.raymondjdouglas.com/blog/2019/airpods-on-arch/  on the
  assumption that maybe this is an issue caused by LE communication
  rather than classic BR/EDR communication. Alas, my computer wasn't
  even able to start the pairing process after making the change.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1822633/+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 1816642] Re: SRU of LXC 2.0.11

2019-04-01 Thread Adam Conrad

Hello Stéphane, or anyone else affected,

Accepted lxc into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/lxc/2.0.11-0ubuntu1~16.04.1 in a
few hours, and then in the -proposed repository.

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

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

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

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

** Changed in: lxc (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

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

Title:
  SRU of LXC 2.0.11

Status in lxc package in Ubuntu:
  Fix Released
Status in lxc source package in Trusty:
  Triaged
Status in lxc source package in Xenial:
  Fix Committed

Bug description:
  LXC upstream has released a new bugfix release for the LXC 2.0 LTS branch.
  This is version 2.0.10. Ubuntu never received 2.0.9 as an SRU, so the 
changelog for both of them can be found below:

  LXC 2.0.11:
   - autotools: handle getgrgid_r on bionic
   - autotools: add memory_utils.h to Makefile.am
   - change version to 2.0.11 in configure.ac

  LXC 2.0.10:
   - tools: allow lxc-attach to undefined containers
   - utils: move memfd_create() definition
   - utils: add lxc_cloexec()
   - utils: add lxc_make_tmpfile()
   - utils: add lxc_getpagesize()
   - utils: add lxc_safe_long_long()
   - utils: parse_byte_size_string()
   - utils: add lxc_find_next_power2()
   - namespace: use lxc_getpagesize()
   - lxc-debian: allow creating `testing` and `unstable`
   - Call lxc_config_define_load from lxc_execute again
   - Fix typo in lxc-net script
   - Add missing lxc_container_put
   - lxc-debian: don't write C.* locales to /etc/locale.gen
   - attach: correctly handle namespace inheritance
   - cgfsng: fix cgroup2 detection
   - cgroups: enable container without CAP_SYS_ADMIN
   - lxc-start: remove unnecessary checks
   - start: close non-needed file descriptors
   - handler: make name argument const
   - start: close data socket in parent
   - monitor: do not log useless warnings
   - network: reap child in all cases
   - conf: reap child in all cases
   - storage: switch to ext4 as default filesystem
   - tools: fix help output of lxc-create
   - attach: handle namespace inheritance
   - cgroups/cgfsng: keep mountpoint intact
   - cgroups/cgfsng: cgfsns_chown() -> cgfsng_chown()
   - cgroups/cgfsng: support MS_READONLY with cgroup ns
   - log: check for i/o error with vsnprintf()
   - cgroupfs/cgfsng: tweak logging
   - cgroups/cgfsng: remove is_lxcfs()
   - cgroups/cgfsng: fix get_controllers() for cgroup2
   - cgroupfs/cgfsng: improve cgroup2 handling
   - config: remove SIGRTMIN+14 as lxc.signal.stop
   - commands: non-functional changes
   - console: non-functional changes
   - console: non-functional changes
   - lxc-test-unpriv: fix the overlayfs mount error
   - attach: allow attach with empty conf
   - tools/lxc_attach: removed api logging
   - console: fix console info message
   - Add missing dependency libunistring
   - cgroups/cgfsng: adapt to new cgroup2 delegation
   - console: report detach message on demand
   - lxccontainer: enable daemonized app containers
   - console: use correct escape sequence check
   - console: prepare for generic signal handler
   - console: exit mainloop on SIGTERM
   - commands: non-functional changes
   - lxccontainer: non-functional changes
   - commands: fix state socket implementation
   - lxc_init: set the control terminal in the child session
   - lxc-test-unpriv: check user existence before removing it
   - Fixed typo on lxc.spec.in
   - conf: move CAP_SYS_* definitions to utils.h
   - start.c: always switch uid and gid
   - Use AX_PTHREAD config script to detect pthread api
   - utils.h: Avoid duplicated sethostname implementation
   - tools/lxc_cgroup: remove internal logging
   - tools/lxc_autostart: remove internal logging
   - tools/lxc_clone: remove internal logging
   - tools/lxc_console: remove internal logging
   - tools/lxc_create: remove

[Touch-packages] [Bug 1810129] Re: blake2b512 / sha3-512 invalid digest type

2019-04-01 Thread Dimitri John Ledkov

Not sure if blake support is in TLS certificates.

I see many more constants for sha3, than for blake:
https://paste.ubuntu.com/p/gjzTwVTCBX/

did you try to use sha3-512 and did that work?

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

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

Title:
  blake2b512 / sha3-512 invalid digest type

Status in openssl package in Ubuntu:
  Incomplete

Bug description:
  cosmic | openssl 1.1.1-1

  Since 1.1.1.a-1 provides support for blake2b512 / sha3-512 it would be
  expected such to work when generating certificates which however does
  not.

  OpenSSL> list -digest-commands
  blake2b512 blake2s256 gost md4
  md5 mdc2 rmd160 sha1
  sha224 sha256 sha3-224 sha3-256
  sha3-384 sha3-512 sha384 sha512
  sha512-224 sha512-256 shake128 shake256
  sm3

  OpenSSL> list -digest-algorithms
  ...
  BLAKE2b512
  ...
  SHA3-512
  ...

  

  Steps to reproduce:

  in openssl_ca.conf set 'default_md = blake2b512' or 'default_md =
  sha3-512'

  generating a certificate ends with

  'error:100C508A:elliptic curve routines:pkey_ec_ctrl:invalid digest
  type:crypto/ec/ec_pmeth.c:327:'

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1810129/+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 1821091] Re: [FFe] Qt 5.12.2 update

2019-04-01 Thread Dmitry Shachnev

Hi, I have three things to mention:

1) We now have successfully rebuilt all reverse dependencies in the PPA.

2) I have checked whether Qt WebEngine 5.12 builds fine against Qt 5.11
and the answer is no. So I was wrong, and the only way to get Qt
WebEngine security updates is updating all of Qt.

3) PyQt5 WebEngine module was split into a separate module upstream, so
we have a new source package: pyqt5webengine. There are no functional
changes, just packaging change. See
https://www.riverbankcomputing.com/news/pyqt-512.

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

Title:
  [FFe] Qt 5.12.2 update

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

Bug description:
  Dear Release Team,

  I would like to update Qt in disco from 5.11.3 to 5.12.2.

  The reasons are the following:

  1) The 5.11 branch is EOL and no longer receiving any fixes. The 5.12
  branch is LTS and will be supported for three years.

  2) New versions of Plasma are going to require Qt 5.12, and the
  Kubuntu team would like to be able to package them in their backports
  PPA for disco.

  3) In Qt 5.12, the memory usage of the QML Engine is reduced by up to
  30 %.

  4) Finally we will be able to sync all packages from Debian. I have
  managed to drop the delta in qtbase, qtmultimedia and qtwebkit.

  Why we haven’t packaged it early: we did not want to package 5.12.1
  because it had some known bugs. And 5.12.2 was released upstream later
  than it was originally planned.

  Changelog: https://wiki.qt.io/New_Features_in_Qt_5.12

  The packages are being prepared in https://launchpad.net/~ci-train-
  ppa-service/+archive/ubuntu/3680/+packages, but these will be replaced
  with syncs from Debian when qtbase and qtdeclarative get accepted from
  Debian’s NEW queue.

  This transition will require syncs of all Qt packages, and no-change
  rebuilds of packages that build-depend on qtbase5-private-dev or
  qtdeclarative5-private-dev.

  All Qt modules are in universe.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1821091/+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 1822642] [NEW] Suspend with pm-suspend (or any other way) stops working after a few cycles

2019-04-01 Thread debasish ray chawdhuri

Public bug reported:

I had a fresh installation of Ubuntu-18.04. From the beginning suspend
was failing spuriously. When I looked up in Google, I was suggested to
upgrade my kernel as the provided kernel 4.15 was buggy. So I compiled
the kernel from source and upgraded to 5.04. The problem still
persisted. Having GRUB_CMDLINE_LINUX_DEFAULT="acpi_sleep=nonvs" in the
file /etc/default/grub and running sudo update-grub does not change
anything. Finally I have narrowed down the problem to calling sudo pm-
suspend directly. The command works perfectly fine until a few suspend-
wakeup cycles have passed. After a few cycle, the screen blanks out and
the system does not go to sleep. Nothing responds and I have to do a
hard reboot after which everything works the same.

Release: Description:   Ubuntu 18.04.2 LTS
Release:18.04

pm-utils:
  Installed: 1.4.1-17
  Candidate: 1.4.1-17
  Version table:
 *** 1.4.1-17 500
500 http://in.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
500 http://in.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
100 /var/lib/dpkg/status

Expected pm-suspend to work every time. Instead, pm-suspend fails to put
the system to sleep after a few cycles.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pm-utils 1.4.1-17
Uname: Linux 5.0.4 x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 21:20:39 2019
InstallationDate: Installed on 2019-02-13 (47 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
PackageArchitecture: all
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_IN
 SHELL=/bin/bash
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Suspend with pm-suspend (or any other way) stops working after a few
  cycles

Status in pm-utils package in Ubuntu:
  New

Bug description:
  I had a fresh installation of Ubuntu-18.04. From the beginning suspend
  was failing spuriously. When I looked up in Google, I was suggested to
  upgrade my kernel as the provided kernel 4.15 was buggy. So I compiled
  the kernel from source and upgraded to 5.04. The problem still
  persisted. Having GRUB_CMDLINE_LINUX_DEFAULT="acpi_sleep=nonvs" in the
  file /etc/default/grub and running sudo update-grub does not change
  anything. Finally I have narrowed down the problem to calling sudo pm-
  suspend directly. The command works perfectly fine until a few
  suspend-wakeup cycles have passed. After a few cycle, the screen
  blanks out and the system does not go to sleep. Nothing responds and I
  have to do a hard reboot after which everything works the same.

  Release: Description: Ubuntu 18.04.2 LTS
  Release:  18.04

  pm-utils:
Installed: 1.4.1-17
Candidate: 1.4.1-17
Version table:
   *** 1.4.1-17 500
  500 http://in.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages
  500 http://in.archive.ubuntu.com/ubuntu bionic/universe i386 Packages
  100 /var/lib/dpkg/status

  Expected pm-suspend to work every time. Instead, pm-suspend fails to
  put the system to sleep after a few cycles.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pm-utils 1.4.1-17
  Uname: Linux 5.0.4 x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 21:20:39 2019
  InstallationDate: Installed on 2019-02-13 (47 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 701856] Re: Brother's printer/scanner drivers awkward to find and install

2019-04-01 Thread Colan Schwartz

I gave up on Brother after having to fiddle with the config on every OS
upgrade, and I recommend that everyone else do the same.  I tried
opening a support ticket the last time, and they said Linux support is
only available in the forums, which tells me they don't actively support
it any more (if they ever did).

So as suggested in comment #26, I ran out and bought an HP, and never
looked back.  I got everything working fairly quickly, and it hasn't
broken since.

They actually work with the open-source community so I'll keep
supporting them.  I'm never buying a Brother again.

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

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

Status in cups package in Ubuntu:
  Opinion

Bug description:
  Binary package hint: cupsys

  Hello,

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

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

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

  - Printer BROTHER DCP-7030 :

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

  After that printer works

  
  - SCANNING :

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

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

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

  Now Simple Scan works, Brother-DCP is seen.

  But... big problem !

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

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

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

  Thanks in advance for your help. Best regards,

  Xavier

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

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

[Touch-packages] [Bug 1797386] Re: [SRU] OpenSSL 1.1.1 to 18.04 LTS

2019-04-01 Thread Dimitri John Ledkov

** Changed in: openssl (Ubuntu)
 Assignee: (unassigned) => Steve Langasek (vorlon)

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

Title:
  [SRU] OpenSSL 1.1.1 to 18.04 LTS

Status in openssl package in Ubuntu:
  In Progress
Status in libio-socket-ssl-perl source package in Bionic:
  New
Status in libnet-ssleay-perl source package in Bionic:
  New
Status in nova source package in Bionic:
  New
Status in openssl source package in Bionic:
  Confirmed
Status in python-cryptography source package in Bionic:
  New
Status in python2.7 source package in Bionic:
  New
Status in python3.6 source package in Bionic:
  New
Status in python3.7 source package in Bionic:
  New
Status in r-cran-openssl source package in Bionic:
  Fix Committed
Status in ruby-openssl source package in Bionic:
  Fix Committed
Status in ruby2.5 source package in Bionic:
  New

Bug description:
  [Impact]

   * OpenSSL 1.1.1 is an LTS release upstream, which will continue to
  receive security support for much longer than 1.1.0 series will.

   * OpenSSL 1.1.1 comes with support for TLS v1.3 which is expected to
  be rapidly adopted due to increased set of supported hashes & algoes,
  as well as improved handshake [re-]negotiation.

   * OpenSSL 1.1.1 comes with improved hw-acceleration capabilities.

   * OpenSSL 1.1.1 is ABI/API compatible with 1.1.0, however some
  software is sensitive to the negotiation handshake and may either need
  patches/improvements or clamp-down to maximum v1.2.

  [Test Case]

   * Rebuild all reverse dependencies

   * Execute autopkg tests for all of them

   * Clamp down to TLS v1.2 software that does not support TLS v1.3
  (e.g. mongodb)

   * Backport TLS v1.3 support patches, where applicable

  [Regression Potential]

   * Connectivity interop is the biggest issues which will be
  unavoidable with introducing TLS v1.3. However, tests on cosmic
  demonstrate that curl/nginx/google-chrome/mozilla-firefox connect and
  negotiate TLS v1.3 without issues.

   * Mitigation of discovered connectivity issues will be possible by
  clamping down to TLS v1.2 in either server-side or client-side
  software or by backporting relevant support fixes

   * Notable changes are listed here
  https://wiki.openssl.org/index.php/TLS1.3

   * Most common connectivity issues so far:
     - client verifies SNI in TLSv1.3 mode, yet client doesn't set hostname. 
Solution is client change to set hostname, or to clamp down the client to 
TLSv1.2.

     - session negotiation is different in TLSv1.3, existing client code
  may fail to create/negotiate/resume session. Clients need to learn how
  to use session callback.

   * This update bundles python 3.6 and 3.7 point releases

   * Following the change in Cosmic and up, this SRU also includes a
  distro patch that lowers OPENSSL_TLS_SECURITY_LEVEL from 1 to 0, to
  allow for establishing client->server server->client connections with
  lower grade security settings (e.g. sub-80bits keys, MD5/SHA1
  certificate checksums, and other crap like that). This is to continue
  allow bionic clients to connect to servers operating with older 1.0.x
  based openssl, as typically clients are at no mercy to reject servers
  that do not have any better certs/keys/signatures. Thus potentially
  weak-security connections that previously would fail to establish
  to/from bionic, may now be accepted. Some may view this as a
  regression. In that case adjust openssl.cnf to a higher
  TLS_SECURITY_LEVEL, or use the openssl ctx APIs to set a higher TLS
  security level. See further comments in this bug report as to when we
  will be raising this LEVEL up (currently timeline is to raise to 2, in
  20.04 LTS).

  [Other Info]

   * Previous FFe for OpenSSL in 18.10 is at
     https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1793092

   * TLS v1.3 support in NSS is expected to make it to 18.04 via
  security updates

   * TLS v1.3 support in GnuTLS is expected to be available in 19.04

   * Test OpenSSL is being prepared in
     https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3473

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1797386/+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 1820314] Re: [ASRock FM2A75M-DGS] No sound at all

Performing 
sudo apt-get -y --reinstall install linux-sound-base alsa-base alsa-utils 
lightdm ubuntu-desktop linux-image-`uname -r` libasound2
On fresh install 18.04 partition on a different partition did not dolce the 
problem. Is there any step by step

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

Title:
  [ASRock FM2A75M-DGS] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  cannot hear any sound even with headphones from any of 2 rear output
  port (green and blue) of my asrock fm2a75m-dgs or the front unique
  one.

  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
  CurrentDesktop: XFCE
  Date: Fri Mar 15 17:32:51 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_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, 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/1820314/+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 1822639] [NEW] Login screen doesn't react to key pressings prior to entering the password

2019-04-01 Thread Adrian

Public bug reported:

Before the screen when you enter the password, where the clock is shown,
if a key is pressed, it does not retract the screen upwards, as it used
to. Now I have to manually use my mouse to drag the screen up. Not sure
if it is the way it was intended to be used, but I am submitting a bug
report to be sure.

I apologise if this is a bug with GNOME, but please do tell me so I can
send a bug report to them.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  418.56  Fri Mar 15 12:59:26 
CDT 2019
 GCC version:  gcc version 8.3.0 (Ubuntu 8.3.0-3ubuntu1)
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 18:23:16 2019
DistUpgraded: 2019-03-29 19:19:33,105 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 418.56, 4.18.0-16-generic, x86_64: installed
 nvidia, 418.56, 5.0.0-7-generic, x86_64: installed
DpkgLog:
 
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Intel Corporation HD Graphics 530 [8086:191b] (rev 06) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 530 [17aa:380a]
   Subsystem: Lenovo GM107M [GeForce GTX 950M] [17aa:380b]
InstallationDate: Installed on 2018-12-31 (91 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2a Intel Corp. 
 Bus 001 Device 003: ID 5986:0670 Acer, Inc 
 Bus 001 Device 002: ID 17ef:60b2 Lenovo 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80RU
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic 
root=UUID=a2f33991-8e13-4dbe-bfae-4a0a1edd71b9 ro quiet splash vt.handoff=1
Renderer: Software
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to disco on 2019-03-29 (2 days ago)
XorgConf:
 Section "Extensions"
 Option "XVideo" "Disable"
 EndSection
dmi.bios.date: 02/15/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: E5CN58WW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: Lenovo ideapad 700-15ISK
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 700-15ISK
dmi.modalias: 
dmi:bvnLENOVO:bvrE5CN58WW:bd02/15/2017:svnLENOVO:pn80RU:pvrLenovoideapad700-15ISK:rvnLENOVO:rnLenovoideapad700-15ISK:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapad700-15ISK:
dmi.product.family: IDEAPAD
dmi.product.name: 80RU
dmi.product.sku: LENOVO_MT_80RU_BU_idea_FM_Lenovo ideapad 700-15ISK
dmi.product.version: Lenovo ideapad 700-15ISK
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.1-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.1-1ubuntu1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco possible-manual-nvidia-install 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/1822639

Title:
  Login screen doesn't react to key pressings prior to entering the
  password

Status in xorg package in Ubuntu:
  New

Bug description:
  Before the screen when you enter the password, where the clock is
  shown, if a key is pressed, it does not retract the screen upwards, as
  it used to. Now I have to manually use my mouse to drag the screen up.
  Not sure if it is the way it was intended to be used, but I am
  submitting a bug report to be sure.

  I apologise if this is a bug with GNOME, but please do tell me so I
  can send a bug report to them.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
  Uname: Linux 5.0.0-7-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia

Re: [Touch-packages] [Bug 1822370] Re: 19.04 beta openssh-client broken pipe

2019-04-01 Thread FranksMCB

Thanks for the responses Christian.

This client does indeed run in VMware, VMware Player 15

Running it using /ssh -o IPQoS=throughput user@host /and it functions
correctly on multiple hosts.

On 4/1/19 4:30 AM, Christian Ehrhardt  wrote:
> Interesting and maybe related
>
> https://communities.vmware.com/thread/590825
> https://github.com/vmware/open-vm-tools/issues/287
> https://bugzilla.redhat.com/show_bug.cgi?id=1624437
>
> The TL;DR of those is that VMWare would have issues with the AF21 QoS flag.
> Does your client run in VMWare by chance?
>
>
> Even if not it might be another part of the network setup between your client 
> and server that reacts to the same change.
>
> Please give the:
>   $ ssh -o IPQoS=throughput user@host
> a check (older default) if that resolves the issue.
>
>
> I checked for the reason of this default change and found:
> I found that the man page has this update about the defaults between 
> cosmic/disco.
> The upstream change is:
>   
> https://anongit.mindrot.org/openssh.git/commit/?id=5ee8448ad7c306f05a9f56769f95336a8269f379
>
> There as no follow on change to that yet as far as I can tell from git.
>
> I'd appreciate if you could do the testing with the QoS options (which
> can also be set in /etc/ssh/ssh_config if you want to make them
> permanent. Maybe the world isn't ready for the new defaults yet and we
> might have to hold them back a release?
>
> ** Bug watch added: github.com/vmware/open-vm-tools/issues #287
>https://github.com/vmware/open-vm-tools/issues/287
>
> ** Bug watch added: Red Hat Bugzilla #1624437
>https://bugzilla.redhat.com/show_bug.cgi?id=1624437
>

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

Title:
  19.04 beta openssh-client broken pipe

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Upgrade to Xubuntu 19.04 beta from 18.10

  openssh-client

  when trying to ssh into another system, following error:

  packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  Problem is consistent on trying to connect to various systems.

  Can confirm was able to ssh prior to upgrade and can ssh into these
  systems from other systems.

  Can use putty on this system to ssh into these boxes as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openssh-client 1:7.9p1-9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 29 13:36:38 2019
  InstallationDate: Installed on 2018-11-14 (135 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b  26 Feb 2019
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1822466] Re: [FM2A75M-DGS., Realtek ALC662 rev1, Green Line Out, Rear] No sound at all

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

In this bug report I include case specs and alsamixer image with front
panel with audio jack

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

Title:
  [FM2A75M-DGS., Realtek ALC662 rev1, Green Line Out, Rear] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Alsamixer with my http://it.thermaltake.com/products-model.aspx?id=C_2559 
front panel audio extension, usb powered 
https://www.trust.com/it/product/20943-polo-compact-2-0-speaker-set connected 
to rear green port
  https://imgur.com/nM1gzEC

  pavucontrol option all analog device seems unplugged even if they are plugged 
in
  https://streamable.com/ix2ob

  Need a fix

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1776 F pulseaudio
   /dev/snd/controlC0:  hp 1776 F pulseaudio
hp16340 F alsamixer
  CurrentDesktop: XFCE
  Date: Sun Mar 31 13:29:12 2019
  InstallationDate: Installed on 2016-09-07 (934 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_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  hp 1776 F pulseaudio
   /dev/snd/controlC0:  hp 1776 F pulseaudio
hp16340 F alsamixer
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, 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.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.sku: 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.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2019-03-30T08:08:19.492099

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1822466/+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 1822634] [NEW] grub boot fail

2019-04-01 Thread Ray Newton

Public bug reported:

no linux file found  16.04 GMT

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 17:04:05 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company C67 [GeForce 7000M / nForce 610M] 
[103c:30ea]
InstallationDate: Installed on 2019-04-01 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 002: ID 064e:a102 Suyin Corp. Acer/Lenovo Webcam [CN0316]
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=6bf08b7f-515d-43b6-865e-0ea3b9f55772 ro recovery nomodeset
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/22/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.0A
dmi.board.name: 30EA
dmi.board.vendor: Quanta
dmi.board.version: 86.09
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd03/22/2011:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: Compaq Presario F700 Notebook PC
dmi.product.sku: KW336EA#ABU
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


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

Title:
  grub boot fail

Status in xorg package in Ubuntu:
  New

Bug description:
  no linux file found  16.04 GMT

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 17:04:05 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company C67 [GeForce 7000M / nForce 610M] 
[103c:30ea]
  InstallationDate: Installed on 2019-04-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 002: ID 064e:a102 Suyin Corp. Acer/Lenovo Webcam [CN0316]
   Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: Hewlett-Packard Compaq Presario F700 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-15-generic 
root=UUID=6bf08b7f-515d-43b6-865e-0ea3b9f55772 ro recovery nomodeset
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/22/2011
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.0A
  dmi.board.name: 30EA
  dmi.board.vendor: Quanta
  dmi.board.version: 86.09
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.0A:bd03/22/2011:svnHewlett-Packard:pnCompaqPresarioF700NotebookPC:pvrRev1:rvnQuanta:rn30EA:rvr86.09:cvnQuanta:ct10:cvrN/A:
  dmi.product.family:

[Touch-packages] [Bug 1760569] Re: Nautilus crashes in g_free -> g_bookmark_file_move_item -> gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

2019-04-01 Thread Treviño

Run test for test_move_item inside glib 2.56.4-0ubuntu0.18.04.2 and it
works as expected.

** 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 glib2.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1760569

Title:
  Nautilus crashes in g_free -> g_bookmark_file_move_item ->
  gtk_recent_manager_move_item -> nautilus_recent_update_file_moved

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Bionic:
  Fix Committed
Status in nautilus source package in Bionic:
  Invalid

Bug description:
  [ Description ]

  A crasher when using nautilus. No clear reproducer.

  [ QA ]

  Under the GNOME MRE, believe all bugs that upstream says are fixed are
  really fixed without explicitly verifying them.

  https://wiki.ubuntu.com/StableReleaseUpdates/GNOME

  Make sure nautilus works, and that the error tracker buckets listed
  below at least don't increase more rapidly (but hopefully tail off
  with the new version)

  
  [ Regression potential ]

  It's GLib. A regression could break the whole desktop, or any part of
  it... Our QA should help us have confidence that the update is at
  least not that bad.

  [ Original description ]

  Happens when there's a "rename" to a file to its same value, no known
  reproducer though.

  Upstream fix: https://gitlab.gnome.org/GNOME/glib/merge_requests/456

  https://errors.ubuntu.com/problem/1aa40f9ef3a1f77a05e71d0a69351c2ae5a7fb45
  https://errors.ubuntu.com/problem/9f0f3a1aee06700bc4ac107754f909801c4641b9

  ProblemType: CrashDistroRelease: Ubuntu 18.04
  Package: nautilus 1:3.26.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  AssertionMessage: munmap_chunk(): invalid pointer
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  2 09:04:45 2018
  ExecutablePath: /usr/bin/nautilus
  GsettingsChanges:
   b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'"
   b'org.gnome.nautilus.window-state' b'sidebar-width' b'223'
   b'org.gnome.nautilus.window-state' b'geometry' b"'890x550+117+77'"
   b'org.gnome.nautilus.window-state' b'maximized' b'true'
  InstallationDate: Installed on 2018-03-31 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180329)
  ProcCmdline: /usr/bin/nautilus --gapplication-service
  ProcEnviron:
   XDG_RUNTIME_DIR=
   SHELL=/bin/bash
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   LANG=en_GB.UTF-8Signal: 6SourcePackage: nautilus
  StacktraceTop:
   __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7f1a46fcfb9a 
"%s\n") at ../sysdeps/posix/libc_fatal.c:181
   malloc_printerr (str=str@entry=0x7f1a46fd17a8 "munmap_chunk(): invalid 
pointer") at malloc.c:5350
   munmap_chunk (p=0x55f2e55b71f0) at malloc.c:2846
   __GI___libc_free (mem=0x55f2e55b7200) at malloc.c:3117
   g_bookmark_file_move_item () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
  Title: nautilus assert failure: munmap_chunk(): invalid pointer
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  usr_lib_nautilus:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1760569/+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 1818953] Re: mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by executing perl script, multiple architectures

Great. Thanks Dimitri. We'd missed that upload.

-- 
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:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818953/+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 1778844] Re: nvme multipath does not report path relationships

Hi Thadeu, thanks for the update.

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  In Progress
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in initramfs-tools source package in Disco:
  In Progress
Status in linux source package in Disco:
  Invalid

Bug description:
  [Impact]
  initramfs created with MODULES=dep or kdump initrd won't boot a system with 
root filesystem on a multipath nvme.

  [Test case]
  Systems with nvme multipath were able to boot with the created initramfs. 
Also tested on systems with non-multipath nvme, and non nvme systems.

  [Regression potential]
  A system could fail to boot because the generated initramfs was broken. The 
code should just add modules, which is safer than removing modules or doing any 
other changes. In any case, it was tested to boot on multipath nvme, non 
multipath nvme and non nvme systems.


  -

  
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004
  [   73.058099] CFAR: c07f3564 DAR:  DSISR: 4200

[Touch-packages] [Bug 1818953] Re: mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by executing perl script, multiple architectures

2019-04-01 Thread Dimitri John Ledkov

@manjo as you can see from launchpad and proposed-updates report it has
been synced 17h ago, built and stuck in disco-proposed with autopkgtest
regressions, and awaiting results for many more.

-- 
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:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818953/+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 1764628] Re: incorrect hypervisor and virtualization type reported in compat mode guest

** Changed in: ubuntu-power-systems
   Status: Triaged => Incomplete

** Changed in: util-linux (Ubuntu)
   Status: New => Incomplete

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

Title:
  incorrect hypervisor and virtualization type reported in compat mode
  guest

Status in The Ubuntu-power-systems project:
  Incomplete
Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  ---uname output---
  Linux guest 4.15.0-13-generic #14~16.04.1-Ubuntu SMP Sat Mar 17 03:03:53 UTC 
2018 ppc64le ppc64le ppc64le GNU/Linux
   
  Machine Type = boston-LC 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   Incorrect hypervisor and virtualization type reported in ubuntu 16.04.04 
guest running in P8compat mode on P9 boston-LC:

  root@guest:/tmp# lscpu
  Architecture:  ppc64le
  Byte Order:Little Endian
  CPU(s):2
  On-line CPU(s) list:   0,1
  Thread(s) per core:2
  Core(s) per socket:1
  Socket(s): 1
  NUMA node(s):  1
  Model: 2.2 (pvr 004e 1202)
  Model name:POWER8 (architected), altivec supported
  >> Hypervisor vendor: horizontal
  >> Virtualization type:   full
  L1d cache: 32K
  L1i cache: 32K
  NUMA node0 CPU(s): 0,1


   
  Stack trace output:
   no
   
  Oops output:
   no
   

  
  We test what is coming along with distro. If you are not able to see issue 
with : https://launchpad.net/ubuntu/+source/util-linux/2.27.1-6ubuntu3.5 .. can 
we get this included in 16.04.x train ?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1764628/+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 1821308] Update Released

2019-04-01 Thread Łukasz Zemczak

The verification of the Stable Release Update for apt 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 apt in Ubuntu.
https://bugs.launchpad.net/bugs/1821308

Title:
  apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Pinning on local-only package versions is ignored, causing them to be 
upgraded.

  [Test case]
  The integration tests run in autopkgtest include an automated test case that 
contains a package called coolstuff in three versions. We are specifying a Pin 
for the installed one, set to 1000.

  The bug caused 1.0 to become the candidate, as the existing pin was
  ignored. The test checks that 2.0~bpo1 to remains the candidate, that
  is, apt-cache policy looks like this:

  coolstuff:
    Installed: 2.0~bpo1
    Candidate: 2.0~bpo1
    Package pin: 2.0~bpo1
    Version table:
   2.0~bpo2 1000
  100 file:${tmppath}/aptarchive/ backports/main i386 Packages
   *** 2.0~bpo1 1000
  100 ${tmppath}/rootdir/var/lib/dpkg/status
   1.0 1000
  500 file:${tmppath}/aptarchive/ stable/main i386 Packages

  On the output of the autopkgtest we'll see:

  Check that local-only versions can be pinned correctly (LP: #1821308) 

  Test for successful execution of apt-cache policy coolstuff … PASS
 
  Test for correctness of file testsuccess.output … PASS  

  [Regression potential]
  Other weird pinning bugs.

  [Original bug report]

  I have updated apt this morning:

  Start-Date: 2019-03-22  09:36:18
  Commandline: apt-get dist-upgrade
  Upgrade: apt:amd64 (1.0.1ubuntu2.20, 1.0.1ubuntu2.22), ...

  Afterwards, apt-get ignores my pinning preferences:

  # apt-get --dry-run upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be DOWNGRADED:
    burp
  0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
  Inst burp [2.0.54-1] (1.3.48-4 Ubuntu:14.04/trusty [amd64])
  Conf burp (1.3.48-4 Ubuntu:14.04/trusty [amd64])

  # cat /etc/apt/preferences.d/burp.pref
  Package: burp
  Pin: version 2.0.54*
  Pin-Priority: 1000

  This might be caused by bug 1814727 as it's the only thing I can see
  in the changelog regarding apt/pinning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821308/+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 1821308] Re: apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

This bug was fixed in the package apt - 1.0.1ubuntu2.23

---
apt (1.0.1ubuntu2.23) trusty; urgency=medium

  * Fix regression in pinning of local-only package versions (LP:
#1821308)

 -- Julian Andres Klode   Mon, 25 Mar 2019 11:22:42
+0100

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

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

Title:
  apt-get upgrade ignores pinning preferences since 1.0.1ubuntu2.22

Status in apt package in Ubuntu:
  Invalid
Status in apt source package in Trusty:
  Fix Released

Bug description:
  [Impact]
  Pinning on local-only package versions is ignored, causing them to be 
upgraded.

  [Test case]
  The integration tests run in autopkgtest include an automated test case that 
contains a package called coolstuff in three versions. We are specifying a Pin 
for the installed one, set to 1000.

  The bug caused 1.0 to become the candidate, as the existing pin was
  ignored. The test checks that 2.0~bpo1 to remains the candidate, that
  is, apt-cache policy looks like this:

  coolstuff:
    Installed: 2.0~bpo1
    Candidate: 2.0~bpo1
    Package pin: 2.0~bpo1
    Version table:
   2.0~bpo2 1000
  100 file:${tmppath}/aptarchive/ backports/main i386 Packages
   *** 2.0~bpo1 1000
  100 ${tmppath}/rootdir/var/lib/dpkg/status
   1.0 1000
  500 file:${tmppath}/aptarchive/ stable/main i386 Packages

  On the output of the autopkgtest we'll see:

  Check that local-only versions can be pinned correctly (LP: #1821308) 

  Test for successful execution of apt-cache policy coolstuff … PASS
 
  Test for correctness of file testsuccess.output … PASS  

  [Regression potential]
  Other weird pinning bugs.

  [Original bug report]

  I have updated apt this morning:

  Start-Date: 2019-03-22  09:36:18
  Commandline: apt-get dist-upgrade
  Upgrade: apt:amd64 (1.0.1ubuntu2.20, 1.0.1ubuntu2.22), ...

  Afterwards, apt-get ignores my pinning preferences:

  # apt-get --dry-run upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be DOWNGRADED:
    burp
  0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded.
  Inst burp [2.0.54-1] (1.3.48-4 Ubuntu:14.04/trusty [amd64])
  Conf burp (1.3.48-4 Ubuntu:14.04/trusty [amd64])

  # cat /etc/apt/preferences.d/burp.pref
  Package: burp
  Pin: version 2.0.54*
  Pin-Priority: 1000

  This might be caused by bug 1814727 as it's the only thing I can see
  in the changelog regarding apt/pinning.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1821308/+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 1778844] Re: nvme multipath does not report path relationships

2019-04-01 Thread Thadeu Lima de Souza Cascardo

Hi, Andrew, with the debdiff attached and ubuntu sponsors team
subscribed, now we should wait for someone on that team to sponsor that
update. With the SRU template attached, the only thing blocking that
sponsorship now is that disco is now on freeze, so the sponsor is the
one who would decide whether this warrants an upload during the freeze.

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  In Progress
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in initramfs-tools source package in Disco:
  In Progress
Status in linux source package in Disco:
  Invalid

Bug description:
  [Impact]
  initramfs created with MODULES=dep or kdump initrd won't boot a system with 
root filesystem on a multipath nvme.

  [Test case]
  Systems with nvme multipath were able to boot with the created initramfs. 
Also tested on systems with non-multipath nvme, and non nvme systems.

  [Regression potential]
  A system could fail to boot because the generated initramfs was broken. The 
code should just add modules, which is safer than removing modules or doing any 
other changes. In any case, it was tested to boot on multipath nvme, non 
multipath nvme and non nvme systems.


  -

  
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:

[Touch-packages] [Bug 1821582] Update Released

2019-04-01 Thread Łukasz Zemczak

The verification of the Stable Release Update for rsyslog 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 rsyslog in Ubuntu.
https://bugs.launchpad.net/bugs/1821582

Title:
  Don't rely on SysV init script in logrotate config

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Xenial:
  Fix Released

Bug description:
  [IMPACT]

  Xenial uses systemd as default now, debian salsa 
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
  taking advantage of systemctl directly if systemd is active by still keeping 
Sysv init script as fallback only.

  While there is no 'real' impact, I think it make total sense for a
  systemd Xenial system, to use the systemctl approach for log rotation

  It has been brought to my attention by a Ubuntu user that:

  "Xenial logrotate is not able to perform full log rotation on a LXC
  container without the 'sys_ptrace' capability[1] using the Sysv
  approach, invoke-rc.d just fails"

  I have created a test pkg for this user, and the same user was able to
  conclude that it was working as expected with the systemd approach
  (systemctl) when sys_ptrace is disable inside the container.

  [1] - lxc config set  raw.lxc lxc.cap.drop=sys_ptrace

  [TEST CASE]

  ==
  [1] - On a Xenial active systemd system:
  ==
  Determine the script pick the right decision (systemd approach).
  # bash -vx /usr/lib/rsyslog/rsyslog-rotate

  Run logrotate which contains 'include /etc/logrotate.d', thus will use the 
rsyslog log rotation information, now using '/usr/lib/rsyslog/rsyslog-rotate' 
helper.
  # logrotate -vdf /etc/logrotate.conf

  Check if logs rotation happened in /var/log.
  # ls -altr /var/log

  ==
  [2] - On a Xenial active upstart system:
  ==
  Determine the script pick the right decision (non-systemd approach).
  # bash -vx /usr/lib/rsyslog/rsyslog-rotate

  Run logrotate which contains 'include /etc/logrotate.d', thus will use the 
rsyslog log rotation information, now using '/usr/lib/rsyslog/rsyslog-rotate' 
helper.
  # logrotate -vdf /etc/logrotate.conf

  Check if logs rotation happened in /var/log.
  # ls -altr /var/log

  [POTENTIAL REGRESSION

  * None, this commit introduced a new shell script (rsyslog-rotate)
  which uses systemctl directly if systemd is active (default in Xenial)
  but keeps the original Sysv init script as fallback only. Meaning no
  behaviour change for users who decided not to use systemd on their
  Xenial system.

  * I don't see any reported bug about this new helper for Bionic/Cosmic
  which has it since their released.

  /usr/lib/rsyslog/rsyslog-rotate:

  1) Check if existence of systemd, if yes:
     systemctl kill -s HUP rsyslog.service

  2) Check if existence of systemd, if no:
     invoke-rc.d rsyslog rotate > /dev/null

  [OTHER INFO]

  * Salsa rsyslog repository:
  
https://salsa.debian.org/debian/rsyslog/commit/4a49edf26d405726041bee12a42d6f064145c87e

  * First introduced:
  git describe --contains 4a49edf26d405726041bee12a42d6f064145c87e
  debian/8.27.0-4~1

  * rmadison:
  =>   rsyslog | 8.16.0-1ubuntu3  | xenial
  rsyslog | 8.32.0-1ubuntu4  | bionic
  rsyslog | 8.32.0-1ubuntu5  | cosmic
  rsyslog | 8.32.0-1ubuntu7  | disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1821582/+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 1821582] Re: Don't rely on SysV init script in logrotate config

This bug was fixed in the package rsyslog - 8.16.0-1ubuntu3.1

---
rsyslog (8.16.0-1ubuntu3.1) xenial; urgency=medium

  * Add d/rsyslog-rotate
  * Modify d/rsyslog.install & d/rsyslog.logrotate
Don't rely on SysV init script in logrotate config

Add a small helper to send SIGHUP to rsyslogd to close open log files.
Use systemctl directly if systemd is the active PID 1. Keep the SysV
init script as fallback only. (LP: #1821582)

 -- Eric Desrochers   Tue, 19 Mar 2019
22:09:50 -0400

** Changed in: rsyslog (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  Don't rely on SysV init script in logrotate config

Status in rsyslog package in Ubuntu:
  Fix Released
Status in rsyslog source package in Xenial:
  Fix Released

Bug description:
  [IMPACT]

  Xenial uses systemd as default now, debian salsa 
4a49edf26d405726041bee12a42d6f064145c87e, introduce a shell script,
  taking advantage of systemctl directly if systemd is active by still keeping 
Sysv init script as fallback only.

  While there is no 'real' impact, I think it make total sense for a
  systemd Xenial system, to use the systemctl approach for log rotation

  It has been brought to my attention by a Ubuntu user that:

  "Xenial logrotate is not able to perform full log rotation on a LXC
  container without the 'sys_ptrace' capability[1] using the Sysv
  approach, invoke-rc.d just fails"

  I have created a test pkg for this user, and the same user was able to
  conclude that it was working as expected with the systemd approach
  (systemctl) when sys_ptrace is disable inside the container.

  [1] - lxc config set  raw.lxc lxc.cap.drop=sys_ptrace

  [TEST CASE]

  ==
  [1] - On a Xenial active systemd system:
  ==
  Determine the script pick the right decision (systemd approach).
  # bash -vx /usr/lib/rsyslog/rsyslog-rotate

  Run logrotate which contains 'include /etc/logrotate.d', thus will use the 
rsyslog log rotation information, now using '/usr/lib/rsyslog/rsyslog-rotate' 
helper.
  # logrotate -vdf /etc/logrotate.conf

  Check if logs rotation happened in /var/log.
  # ls -altr /var/log

  ==
  [2] - On a Xenial active upstart system:
  ==
  Determine the script pick the right decision (non-systemd approach).
  # bash -vx /usr/lib/rsyslog/rsyslog-rotate

  Run logrotate which contains 'include /etc/logrotate.d', thus will use the 
rsyslog log rotation information, now using '/usr/lib/rsyslog/rsyslog-rotate' 
helper.
  # logrotate -vdf /etc/logrotate.conf

  Check if logs rotation happened in /var/log.
  # ls -altr /var/log

  [POTENTIAL REGRESSION

  * None, this commit introduced a new shell script (rsyslog-rotate)
  which uses systemctl directly if systemd is active (default in Xenial)
  but keeps the original Sysv init script as fallback only. Meaning no
  behaviour change for users who decided not to use systemd on their
  Xenial system.

  * I don't see any reported bug about this new helper for Bionic/Cosmic
  which has it since their released.

  /usr/lib/rsyslog/rsyslog-rotate:

  1) Check if existence of systemd, if yes:
     systemctl kill -s HUP rsyslog.service

  2) Check if existence of systemd, if no:
     invoke-rc.d rsyslog rotate > /dev/null

  [OTHER INFO]

  * Salsa rsyslog repository:
  
https://salsa.debian.org/debian/rsyslog/commit/4a49edf26d405726041bee12a42d6f064145c87e

  * First introduced:
  git describe --contains 4a49edf26d405726041bee12a42d6f064145c87e
  debian/8.27.0-4~1

  * rmadison:
  =>   rsyslog | 8.16.0-1ubuntu3  | xenial
  rsyslog | 8.32.0-1ubuntu4  | bionic
  rsyslog | 8.32.0-1ubuntu5  | cosmic
  rsyslog | 8.32.0-1ubuntu7  | disco

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rsyslog/+bug/1821582/+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 1778844] Re: nvme multipath does not report path relationships

Next step: Thadeu to propose the diff described in comment #53 into the archive.
(If this incorrect, please flag.)

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

Title:
  nvme multipath does not report path relationships

Status in The Ubuntu-power-systems project:
  In Progress
Status in initramfs-tools package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Bionic:
  In Progress
Status in linux source package in Bionic:
  Invalid
Status in initramfs-tools source package in Cosmic:
  In Progress
Status in linux source package in Cosmic:
  Invalid
Status in initramfs-tools source package in Disco:
  In Progress
Status in linux source package in Disco:
  Invalid

Bug description:
  [Impact]
  initramfs created with MODULES=dep or kdump initrd won't boot a system with 
root filesystem on a multipath nvme.

  [Test case]
  Systems with nvme multipath were able to boot with the created initramfs. 
Also tested on systems with non-multipath nvme, and non nvme systems.

  [Regression potential]
  A system could fail to boot because the generated initramfs was broken. The 
code should just add modules, which is safer than removing modules or doing any 
other changes. In any case, it was tested to boot on multipath nvme, non 
multipath nvme and non nvme systems.


  -

  
  Problem Description:
  ===
  After triggering crash ,kdump is not working & system enters into initramfs 
state

  Steps to re-create:
  ==

  >. woo is installed ubuntu180401 kernel

  root@woo:~# uname -a
  Linux woo 4.15.0-23-generic #25-Ubuntu SMP Wed May 23 17:59:00 UTC 2018 
ppc64le ppc64le ppc64le GNU/Linux
  root@woo:~#

  >. Crashkernel value as below

  root@woo:~# free -h
    totalusedfree  shared  buff/cache   
available
  Mem:   503G2.0G501G 13M279M
499G
  Swap:  2.0G  0B2.0G

  root@woo:~# cat /proc/cmdline
  root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
crashkernel=8192M

  >  kdump status

  root@woo:~#  kdump-config status
  current state   : ready to kdump

  root@woo:~#  kdump-config show
  DUMP_MODE:kdump
  USE_KDUMP:1
  KDUMP_SYSCTL: kernel.panic_on_oops=1
  KDUMP_COREDIR:/var/crash
  crashkernel addr:
     /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinux-4.15.0-23-generic
  kdump initrd:
     /var/lib/kdump/initrd.img: symbolic link to 
/var/lib/kdump/initrd.img-4.15.0-23-generic
  current state:ready to kdump

  kexec command:
    /sbin/kexec -p 
--command-line="root=UUID=45bb7eb2-4c61-425d-8bf9-4e6f16829ddb ro splash quiet 
nr_cpus=1 systemd.unit=kdump-tools.service irqpoll noirqdistrib nousb" 
--initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz

  root@woo:~# dmesg | grep Reser
  [0.00] Reserving 8192MB of memory at 128MB for crashkernel (System 
RAM: 524288MB)
  [0.00] cma: Reserved 26224 MiB at 0x20399500
  [3.545490] Copyright (C) 2017-2018 Broadcom. All Rights Reserved. The 
term "Broadcom" refers to Broadcom Limited and/or its subsidiaries.

  > Triggered crash

  root@woo:~# echo 1 > /proc/sys/kernel/sysrq
  root@woo:~# echo c > /proc/sysrq-trigger
  [   73.056308] sysrq: SysRq : Trigger a crash
  [   73.056357] Unable to handle kernel paging request for data at address 
0x
  [   73.056459] Faulting instruction address: 0xc07f24c8
  [   73.056543] Oops: Kernel access of bad area, sig: 11 [#1]
  [   73.056609] LE SMP NR_CPUS=2048 NUMA PowerNV
  [   73.056668] Modules linked in: rdma_ucm(OE) ib_ucm(OE) rdma_cm(OE) 
iw_cm(OE) ib_ipoib(OE) ib_cm(OE) ib_uverbs(OE) ib_umad(OE) esp6_offload esp6 
esp4_offload esp4 xfrm_algo mlx5_fpga_tools(OE) mlx4_en(OE) mlx4_ib(OE) 
mlx4_core(OE) rpcsec_gss_krb5 nfsv4 nfs fscache binfmt_misc idt_89hpesx 
vmx_crypto crct10dif_vpmsum ofpart cmdlinepart ipmi_powernv ipmi_devintf at24 
powernv_flash ipmi_msghandler ibmpowernv mtd opal_prd uio_pdrv_genirq uio nfsd 
auth_rpcgss nfs_acl lockd sch_fq_codel grace sunrpc knem(OE) ip_tables x_tables 
autofs4 btrfs xor zstd_compress raid6_pq mlx5_ib(OE) ib_core(OE) nouveau lpfc 
ast i2c_algo_bit ttm mlx5_core(OE) drm_kms_helper mlxfw(OE) nvmet_fc devlink 
syscopyarea nvmet mlx_compat(OE) sysfillrect cxl nvme_fc sysimgblt fb_sys_fops 
nvme_fabrics nvme ahci crc32c_vpmsum drm scsi_transport_fc
  [   73.057601]  tg3 libahci nvme_core pnv_php
  [   73.057652] CPU: 44 PID: 4626 Comm: bash Tainted: G   OE
4.15.0-23-generic #25-Ubuntu
  [   73.057767] NIP:  c07f24c8 LR: c07f3568 CTR: 
c07f24a0
  [   73.057868] REGS: c03f8269f9f0 TRAP: 0300   Tainted: G   OE
 (4.15.0-23-generic)
  [   73.057986] MSR:  90009033   CR: 2822 
 XER: 2004

[Touch-packages] [Bug 1818953] Re: mblen() failing in Perl / Perl core dumping core on UBUNTU 19.04 by executing perl script, multiple architectures

2019-04-01 Thread Manoj Iyer

@steve, look like its now fixed in Debian 5.28.1-6 and we are close to
beta freeze, are we going to cherry-pick this one?

-- 
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:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1818953/+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 802942] Re: printing PDFs (and other complex documents) from GTK applications fails

2019-04-01 Thread Carl-Daniel Hailfinger

See https://bugs.launchpad.net/ubuntu/+source/foomatic-
db/+bug/1306849/comments/42 for a workaround for the broken Firefox

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

Title:
  printing PDFs (and other complex documents) from GTK applications
  fails

Status in Mozilla Firefox:
  New
Status in cups package in Ubuntu:
  Invalid
Status in cups-filters package in Ubuntu:
  Invalid
Status in firefox package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I'm discovering a bug when printing complex PDFs or other complex
  documents from GTK applications. Printing complex PDFs from evince, or
  sometimes even printing comples webpages from firefox result in one
  error page being printed instead of the document content:

  +-+
  | ERROR NAME;|
  | undefined|
  | COMMAND; |
  | Q|
  | OPERAND STACK;  |
  +-+

  My printer is a Brother HL 5270DN. It doesn't matter whether the
  printer is connected via USB or as network printer. In both cases the
  described bug does happen. The PPD I use is "Brother HL-5270DN BR-
  Script3", similar to the one at
  http://www.openprinting.org/download/PPD/Brother/BR5270_2_GPL.ppd

  I discovered this bug in up-to-date Debian unstable for several years
  already. Now I switched one of my laptops to Ubuntu Natty (fresh
  installation), and unfortunately discovered the same bug there as
  well.

  I'm pretty sure that this bug is related to bug #419143, and not
  really in CUPS, but rather in some library (poppler or cairo) used by
  GTK applications. The same PDFs that produce the described error in
  evince, print fine in okular.

  I attach an example PDF that doesn't print in evince, but prints fine
  in okular. It's sufficient to (try to) print page 1 of the document.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.04
  Package: cups 1.4.6-5ubuntu1.2
  ProcVersionSignature: Ubuntu 2.6.39-0.5~20110427-generic 2.6.39-rc5
  Uname: Linux 2.6.39-0-generic x86_64
  Architecture: amd64
  CupsErrorLog:
   
  Date: Tue Jun 28 13:13:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110426)
  Lpstat: device for Brother-HL-5270DN: lpd://192.168.1.75/PASSTHRU
  MachineType: LENOVO 4180W1H
  Papersize: a4
  PpdFiles: Brother-HL-5270DN: Brother HL-5270DN BR-Script3
  ProcEnviron:
   LANGUAGE=de:en
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-2.6.39-0-generic 
root=/dev/mapper/vgsys-root ro quiet splash vt.handoff=7
  SourcePackage: cups
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/13/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 83ET56WW (1.26 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 4180W1H
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr83ET56WW(1.26):bd05/13/2011:svnLENOVO:pn4180W1H:pvrThinkPadT420:rvnLENOVO:rn4180W1H:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 4180W1H
  dmi.product.version: ThinkPad T420
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/802942/+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 1795857] Re: enable CONFIG_DRM_BOCHS

2019-04-01 Thread Thadeu Lima de Souza Cascardo

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: Incomplete

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

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

Title:
  enable CONFIG_DRM_BOCHS

Status in kmod package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Incomplete
Status in kmod source package in Disco:
  New
Status in linux source package in Disco:
  Incomplete

Bug description:
  CONFIG_DRM_BOCHS got disabled for
  https://bugs.launchpad.net/ubuntu/+source/kmod/+bug/1378648

  but doing so regressed running qemu with the 'std' VGA driver, where
  it'd fail to start X after install, as mentioned on bug 1794280

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

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

[Touch-packages] [Bug 1821863] Re: Need to add Intel CML related pci-id's

2019-04-01 Thread Thadeu Lima de Souza Cascardo

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

** Also affects: libdrm (Ubuntu Disco)
   Importance: Undecided
   Status: Fix Released

** Also affects: xorg-server (Ubuntu Disco)
   Importance: Undecided
   Status: New

** Also affects: linux (Ubuntu Disco)
   Importance: Undecided
   Status: Incomplete

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

** Changed in: linux-oem (Ubuntu Disco)
   Status: New => Fix Committed

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

Title:
  Need to add Intel CML related pci-id's

Status in libdrm package in Ubuntu:
  Fix Released
Status in linux package in Ubuntu:
  Incomplete
Status in linux-oem package in Ubuntu:
  Fix Committed
Status in mesa package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New
Status in libdrm source package in Bionic:
  New
Status in linux source package in Bionic:
  Invalid
Status in linux-oem source package in Bionic:
  New
Status in mesa source package in Bionic:
  New
Status in xorg-server source package in Bionic:
  New
Status in libdrm source package in Disco:
  Fix Released
Status in linux source package in Disco:
  Incomplete
Status in linux-oem source package in Disco:
  Fix Committed
Status in mesa source package in Disco:
  New
Status in xorg-server source package in Disco:
  New

Bug description:
  [Impact]

  Please make it happen in the coming oem-kernel as there will be a
  flood of Intel Comet Lake (CML) platforms that would need it. Thank
  you.

  The same is needed for the rest of the stack.

  CML is basically another iteration of Skylake/Kabylake/Coffee Lake,
  and doesn't need other changes than pci-id's and support for the PCH
  (similar to Cannon point, already supported by the kernel).

  [Test case]

  Test that i915 graphics works on CML.

  [Regression potential]

  None really, these only add a bunch of new pci-id's across the stack.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/1821863/+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 1822587] [NEW] wifi service stops occasionally.

2019-04-01 Thread Justin Hall

Public bug reported:

wifi service stops occasionally: ('?' in the top right icon). an old bug
that disappeared a few updates back, back now after yesterday's update.
'service network-manager restart' gets it working again. annoying as i
thought it gone.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: network-manager 1.12.4-1ubuntu1.2
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr  1 14:50:50 2019
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-07-30 (975 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
 169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
 192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
ProcEnviron:
 LANGUAGE=en_ZA:en
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_ZA.UTF-8
 SHELL=/bin/bash
SourcePackage: network-manager
UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
nmcli-dev:
 DEVICE TYPE  STATE DBUS-PATH   
   CONNECTIONCON-UUID  CON-PATH 
  
 wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
 1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
 enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   -- 
 lo loopback  unmanaged 
/org/freedesktop/NetworkManager/Devices/1  ---- 
   --
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  disabled

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


** Tags: amd64 apport-bug cosmic

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

Title:
  wifi service stops occasionally.

Status in network-manager package in Ubuntu:
  New

Bug description:
  wifi service stops occasionally: ('?' in the top right icon). an old
  bug that disappeared a few updates back, back now after yesterday's
  update.  'service network-manager restart' gets it working again.
  annoying as i thought it gone.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: network-manager 1.12.4-1ubuntu1.2
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  1 14:50:50 2019
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-07-30 (975 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.8.1 dev wlp3s0f0 proto dhcp metric 600 
   169.254.0.0/16 dev wlp3s0f0 scope link metric 1000 
   192.168.8.0/24 dev wlp3s0f0 proto kernel scope link src 192.168.8.100 metric 
600
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  ProcEnviron:
   LANGUAGE=en_ZA:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_ZA.UTF-8
   SHELL=/bin/bash
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to cosmic on 2018-12-06 (116 days ago)
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 CONNECTIONCON-UUID  CON-PATH   

   wlp3s0f0   wifi  connected 
/org/freedesktop/NetworkManager/Devices/3  HUAWEI-B315-D7CD  
01a82e09-44b7-4509-af07-4bf05f76759a  
/org/freedesktop/NetworkManager/ActiveConnection/1 
   1C:AF:05:F7:CE:56  btdisconnected  
/org/freedesktop/NetworkManager/Devices/4  ---- 
   -- 
   enp2s0f1   ethernet  unavailable   
/org/freedesktop/NetworkManager/Devices/2  ---- 
   --

[Touch-packages] [Bug 1778936] Re: please re-add Support-system-image-read-only-etc.patch

2019-04-01 Thread Michael Vogt

This is tested via spread in https://github.com/snapcore/snapd/pull/6667

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

Title:
  please re-add Support-system-image-read-only-etc.patch

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

Bug description:
  [Impact]

   * core18 systems fail to update hostname
   * this happens due to /etc/hostname actually being a symlink to a file under 
/etc/writable/, adjust hostnamed to take that into account when trying to 
update /etc/hostname

  [Test Case]

   * run a core18 system, check that dhcp acquire hostname is correctly
  updated in /etc/writable/hostname

  [Regression Potential]

   * This is cherrypick of code that has gone missing since xenial.
   * There is no change of behaviour for the classic systems.
   * Currently, core18 systems simply fail to update hostname/machine-info 
files, thus the worst case is that they will still fail to do so.

  [Other Info]
   
   * original bug report

  The 16.04 version of systemd had a patch to support the read-only etc.
  For core18 we will also need this change because core18 is still not
  on a fully writable etc.

  I will attach a debdiff against the current bionic version of systemd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1778936/+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 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

This bug was fixed in the package resolvconf - 1.79ubuntu10.18.04.3

---
resolvconf (1.79ubuntu10.18.04.3) bionic; urgency=medium

  * d/resolvconf.resolvconf-pull-resolved.service
Hack out the 'edns0' option that systemd-resolved has
recently added to its stub-resolv.conf. (LP: #1817903)

 -- Dan Streetman   Thu, 14 Mar 2019 17:35:23
-0400

** Changed in: resolvconf (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1817903

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in resolvconf source package in Trusty:
  Invalid
Status in systemd source package in Trusty:
  Invalid
Status in resolvconf source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in resolvconf source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Invalid
Status in resolvconf source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Invalid
Status in resolvconf source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Invalid

Bug description:
  [impact]

  systems upgraded from pre-Bionic releases to Bionic or later will
  continue to use ifupdown/resolvconf for network conf and management,
  but resolvconf has a new systemd service in Bionic and later that
  pulls systemd-resolved stub-resolv.conf into its local configuration.
  With the recent addition of edns0 option to the stub resolver conf in
  systemd to fix bug 1811471, this means resolvconf now sets up the
  /etc/resolv.conf file to include upstream servers but also use edns.
  For any systems where the upstream resolver(s) don't support edns, dns
  lookups will break.

  [test case]

  == upgrade from pre-bionic (e.g. xenial) to bionic or later ==

  1) create a xenial system with ifupdown/resolvconf.  The ifupdown
  config needs to include an upstream name server (must be static).  At
  this point, once the network is configured and up, the resolvconf
  should have put the upstream name server(s) and search domain into the
  /etc/resolv.conf.  As is usual for pre-systemd releases, there should
  be no local dns resolver in /etc/resolv.conf (i.e. 127.0.0.53 should
  not be included) at this point.

  2) upgrade the system to bionic (alternately it should be possible to install 
bionic, then remove netplan and install/configure ifupdown and resolvconf, but 
I have not specifically tested this).  The upgrade will retain the 
ifupdown/resolvconf configuration, and will not change to 
netplan/systemd-networkd.  After upgrade is finished, the /etc/resolv.conf will 
contain:
    a) the upstream name server(s)
    b) options edns0
    c) the local stub resolver (127.0.0.53)
    d) search domain

  the fixed resolvconf will remove (b).

  As mentioned, this case also should cover the situation of a native
  Bionic install, where netplan is removed and ifupdown/resolvconf is
  manually installed.

  == bionic or later install ==

  with a bionic install, ifupdown is not installed, instead netplan
  /systemd-networkd handle networking.  In this case, systemd-networkd
  manages the /etc/resolv.conf, and symlinks it to networkd's stub-
  resolv.conf which always contains only the local stub resolver
  (127.0.0.53) and (recently) options edns0, and local search domain.

  If resolvconf is installed while systemd-networkd is managing the
  network, then currently the resolv.conf contents will remain
  completely unchanged, still pointing to the local stub resolver.

  This resolvconf change will alter that, to remove 'options edns0'.  No
  other changes will be made from the stub-resolv.conf.

  [regression potential]

  Regressions due to this change would likely be seen in dns query
  failures with other system configurations.

  This will cause systems with resolvconf installed to lose the fix from
  bug 1811471, and again experience that bug.

  [other info]

  This affects only Bionic and later; in Xenial and earlier, systemd
  does not handle dns, and the 'edns0' option was not added to that
  systemd-resolved anyway.

  This also does not affect Debian, as it does not include the
  'resolvconf-pull-resolved' service either.

  original description:

  --

  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...

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

2019-04-01 Thread Michael Vogt

We validated the fix via spread in
https://github.com/snapcore/snapd/pull/6595 (both xenial and bionic).

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

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

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Xenial:
  Fix Committed
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 1822581] [NEW] HP 1030 G3 fn-keys not working

2019-04-01 Thread Marcel Munce

Public bug reported:

Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn key 
combinations are only working partially. 
What works: Volume up/down/mute, Airplane mode
What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator lights

I already tried solutions regarding editing the Kernel Parameter
acpi_osi in the grub config but can not get the keys to work. In case of
screen brightness changing it using the desktop slider works.

But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
Running showkey -k results in a keycode 465 pressed and released event for all 
three key combinations.

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: udev 239-7ubuntu10.10
ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.2
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
CustomUdevRuleFiles: 70-snap.core.rules
Date: Mon Apr  1 14:22:47 2019
InstallationDate: Installed on 2019-03-30 (1 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
MachineType: HP HP EliteBook x360 1030 G3
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
SourcePackage: systemd
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/04/2019
dmi.bios.vendor: HP
dmi.bios.version: Q90 Ver. 01.06.00
dmi.board.name: 8438
dmi.board.vendor: HP
dmi.board.version: KBC Version 14.38.00
dmi.chassis.asset.tag: 5CD8427YK5
dmi.chassis.type: 31
dmi.chassis.vendor: HP
dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
dmi.product.family: 103C_5336AN HP EliteBook x360
dmi.product.name: HP EliteBook x360 1030 G3
dmi.product.sku: 4QZ13ES#ABD
dmi.sys.vendor: HP

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


** Tags: amd64 apport-bug cosmic

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

Title:
  HP 1030 G3 fn-keys not working

Status in systemd package in Ubuntu:
  New

Bug description:
  Running Ubuntu 18.10 on my HP Elitebook x360 1030 G3 I noticed, that the fn 
key combinations are only working partially. 
  What works: Volume up/down/mute, Airplane mode
  What doesn't work: Brigtness up/down, microphone mute, fn-Keys indicator 
lights

  I already tried solutions regarding editing the Kernel Parameter
  acpi_osi in the grub config but can not get the keys to work. In case
  of screen brightness changing it using the desktop slider works.

  But it seems, that the keypress isn't recognized at all. Neither xev nor 
acpi_listen are showing events for screen brightness (fn+f3/f4) or microphone 
muting (fn+f8).
  Running showkey -k results in a keycode 465 pressed and released event for 
all three key combinations.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: udev 239-7ubuntu10.10
  ProcVersionSignature: Ubuntu 4.18.0-16.17-generic 4.18.20
  Uname: Linux 4.18.0-16-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  CustomUdevRuleFiles: 70-snap.core.rules
  Date: Mon Apr  1 14:22:47 2019
  InstallationDate: Installed on 2019-03-30 (1 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  MachineType: HP HP EliteBook x360 1030 G3
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-16-generic 
root=UUID=db6a8def-2553-4696-b160-f79e8865b17e ro quiet splash vt.handoff=1
  SourcePackage: systemd
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/04/2019
  dmi.bios.vendor: HP
  dmi.bios.version: Q90 Ver. 01.06.00
  dmi.board.name: 8438
  dmi.board.vendor: HP
  dmi.board.version: KBC Version 14.38.00
  dmi.chassis.asset.tag: 5CD8427YK5
  dmi.chassis.type: 31
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnHP:bvrQ90Ver.01.06.00:bd01/04/2019:svnHP:pnHPEliteBookx3601030G3:pvr:rvnHP:rn8438:rvrKBCVersion14.38.00:cvnHP:ct31:cvr:
  dmi.product.family: 103C_5336AN HP EliteBook x360
  dmi.product.name: HP EliteBook x360 1030 G3
  dmi.product.sku: 4QZ13ES#ABD
  dmi.sys.vendor: HP

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1822581/+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 1759014] Re: Netplan has no way to control DHCP client

2019-04-01 Thread Michael Steffens

Applied

https://github.com/systemd/systemd/commit/223932c786ada7f758a7b7878a6ad2dae0d1e5fb

to systemd 237-3ubuntu10.15 on Bionic. It does indeed fix the issue in
https://bugs.launchpad.net/netplan/+bug/1759014/comments/48 and
https://bugs.launchpad.net/netplan/+bug/1776228/comments/14.

Should I log a separate request to get this included in Bionic systemd?
Or will this be picked up from here?

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

Title:
  Netplan has no way to control DHCP client

Status in netplan:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Confirmed
Status in netplan.io source package in Cosmic:
  Fix Committed
Status in systemd source package in Cosmic:
  Confirmed
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Confirmed

Bug description:
  [Impact]
  DHCP configurations where custom settings (routes, nameservers, etc.) need to 
be applied.

  [Test case]
  1) Configure netplan for the particulars of the network by configuring an 
appropriate dhcp{4,6}-override stanza:

  network:
version: 2
ethernets:
  engreen:
dhcp4: true
dhcp4-overrides:
  use-dns: false
  use-routes: false
  route-metric: 

  Additionally, if so required, add a custom DNS / routes to the
  configuration. e.g.

nameservers:
  search: [lab, kitchen]
  addresses: [8.8.8.8]

  (See https://netplan.io/reference#dhcp-overrides for the available
  options)

  2) Run 'netplan apply' or reboot to have the configuration applied.
  3) Validate that the routes / DNS are properly ignored and/or replaced by the 
defined values.

  [Regression potential]
  Minimal; this adds new values to the configuration generated for networkd or 
NetworkManager. Existing configurations will remain unchanged, but new 
configurations using the dhcp{4,6}-overrides fields will benefit from 
additional flexibility.

  
  ---

  
  Currently DHCP appears to be an all or nothing boolean, which is insufficient 
for many network configurations.

  Ideally all of the DHCP configuration options supported by systemd would also 
be supported in netplan:
  
https://www.freedesktop.org/software/systemd/man/systemd.network.html#%5BDHCP%5D%20Section%20Options

  As an example, consider the following netplan configuration:

  network:
    version: 2
    renderer: networkd
    ethernets:
  enp0s3:
    dhcp4: yes
    nameservers: [8.8.8.8,8.8.4.4]

  After running netplan apply I check the nameservers with systemd-
  resolve --status and it shows:

  DNS Servers: 8.8.8.8
   8.8.4.4
   192.168.1.1

  Here, "192.168.1.1" was provided by my DHCP server.  On this
  particular node, I only want the manually configured DNS servers, but
  netplan has no way to indicate this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/netplan/+bug/1759014/+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 1821609] Re: lightdm login screen briefly appears and then blanks out on Intel(R) Core(TM)2 Duo CPU T5870

2019-04-01 Thread Derk Willem te Bokkel

xubuntu iso for daily april 1, 2019 .. no change

installed iso reboots into the install partition everything works as normal..
reboot into sda1 .. grub-install /dev/sda then update-grub then reboot .. back
into the fresh install partition ..

same behaviours as before .. red flash no visible plymouth .. brief
lightdm login screen appearance .. then brief cursor .. then blank
screen .. all after changing grub back to sda1 as master after
installing iso to freshly blanked test partition sda7 or sda6

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

Title:
lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870

Status in xorg package in Ubuntu:
New

Bug description:
Okay the has happened recently at least since march 18, 2019 iso and
march 22, 2019 iso are both effected very similar to one of my
previously reported bugs .. which was related to xorg not being
installed ..

back ground .. PC is lenovo sl 500 with evo860 SSD drive

3 partions contain installs of disco sda1 -- main working system -- I
usually install grub from here as master ..

sda6 and sda7 are test installs of disco daily iso's 03-18-2019,
03-22-2019 repectively

on the test installs as long as the iso is using the grub boot loader
installed from that install the system will boot normally .. the display manger
tends to flicker on and off but does final start and login can proceed.

but if another install re-installs grub as master the display manager
fails to stay active or even come-up for sda6 or sda7 only if their
own grubs are reinstalled will they work normally

sda1 display manager/xorg login works always no matter which "grub-
source" is in control.

if I use rescue boot from any grub as master I can get the displays to work
by running dpkg fix which does nothing .. and then resuming the boot .. then
things work normally..
if the "non-rescue" boots are used the screen/computer locks and only a power
down and reboot gives access. (sometime requiring radical depowering ..
unpluging and removing battery)

now the is a message that appears that RCs??? level is missing.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu11
ProcVersionSignature: Ubuntu 5.0.0-7.8-generic 5.0.0
Uname: Linux 5.0.0-7-generic x86_64
ApportVersion: 2.20.10-0ubuntu23
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Mon Mar 25 11:25:58 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GpuHangFrequency: Several times a day
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller
[17aa:20e4]
Subsystem: Lenovo Mobile 4 Series Chipset Integrated Graphics Controller
[17aa:20e4]
InstallationDate: Installed on 2019-03-23 (1 days ago)
InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190322)
MachineType: LENOVO 2746CTO
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-7-generic
root=UUID=1d61086d-275b-4537-bed5-f2d3080670eb ro recovery nomodeset
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6AET64WW
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: 2746CTO
dmi.board.vendor: LENOVO
dmi.board.version: LENOVO 6AET64WW
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: LENOVO 6AET64WW
dmi.modalias:
dmi:bvnLENOVO:bvr6AET64WW:bd12/01/2010:svnLENOVO:pn2746CTO:pvrThinkPadSL500:rvnLENOVO:rn2746CTO:rvrLENOVO6AET64WW:cvnLENOVO:ct10:cvrLENOVO6AET64WW:
dmi.product.name: 2746CTO
dmi.product.version: ThinkPad SL500
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.0-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1821415] Re: pkexec fails in a non-graphical environment

2019-04-01 Thread Andrea Azzarone

I proposed a fix upstream [1]. A workaround can be added to apport to
workaroud this while polkit is fixed upstream: we could for example
spawn pkttyagent manually (a similar approach is used by systemd).

[1] https://gitlab.freedesktop.org/polkit/polkit/merge_requests/28

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

Title:
  pkexec fails in a non-graphical environment

Status in PolicyKit:
  New
Status in policykit-1 package in Ubuntu:
  New

Bug description:
  The plymouth apport source package hooks wants to gather log files as
  the root user and apport provides a policy kit policy for collecting
  that information. This works fine in a graphical environment but not
  in a non-graphical one.

  ubuntu@disco:~$ ubuntu-bug plymouth

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .. AUTHENTICATING FOR com.ubuntu.apport.root-info ===
  Authentication is required to collect system information for this problem 
report
  Authenticating as: Ubuntu (ubuntu)
  Password: 
  polkit-agent-helper-1: error response to PolicyKit daemon: 
GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: No session for cookie
   AUTHENTICATION FAILED ===
  Error executing command as another user: Not authorized

  This incident has been reported.

  Subsequently, bug reports from servers will contain less information.

To manage notifications about this bug go to:
https://bugs.launchpad.net/policykit-1/+bug/1821415/+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 1817903] Re: systemd-resolve appends "options edns0" to resolv.conf

This bug was fixed in the package resolvconf - 1.79ubuntu10.18.10.3

---
resolvconf (1.79ubuntu10.18.10.3) cosmic; urgency=medium

  * d/resolvconf.resolvconf-pull-resolved.service
Hack out the 'edns0' option that systemd-resolved has
recently added to its stub-resolv.conf. (LP: #1817903)

 -- Dan Streetman   Thu, 14 Mar 2019 17:33:24
-0400

** Changed in: resolvconf (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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1817903

Title:
  systemd-resolve appends "options edns0" to resolv.conf

Status in resolvconf package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in resolvconf source package in Trusty:
  Invalid
Status in systemd source package in Trusty:
  Invalid
Status in resolvconf source package in Xenial:
  Invalid
Status in systemd source package in Xenial:
  Invalid
Status in resolvconf source package in Bionic:
  Fix Committed
Status in systemd source package in Bionic:
  Invalid
Status in resolvconf source package in Cosmic:
  Fix Released
Status in systemd source package in Cosmic:
  Invalid
Status in resolvconf source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Invalid

Bug description:
  [impact]

  systems upgraded from pre-Bionic releases to Bionic or later will
  continue to use ifupdown/resolvconf for network conf and management,
  but resolvconf has a new systemd service in Bionic and later that
  pulls systemd-resolved stub-resolv.conf into its local configuration.
  With the recent addition of edns0 option to the stub resolver conf in
  systemd to fix bug 1811471, this means resolvconf now sets up the
  /etc/resolv.conf file to include upstream servers but also use edns.
  For any systems where the upstream resolver(s) don't support edns, dns
  lookups will break.

  [test case]

  == upgrade from pre-bionic (e.g. xenial) to bionic or later ==

  1) create a xenial system with ifupdown/resolvconf.  The ifupdown
  config needs to include an upstream name server (must be static).  At
  this point, once the network is configured and up, the resolvconf
  should have put the upstream name server(s) and search domain into the
  /etc/resolv.conf.  As is usual for pre-systemd releases, there should
  be no local dns resolver in /etc/resolv.conf (i.e. 127.0.0.53 should
  not be included) at this point.

  2) upgrade the system to bionic (alternately it should be possible to install 
bionic, then remove netplan and install/configure ifupdown and resolvconf, but 
I have not specifically tested this).  The upgrade will retain the 
ifupdown/resolvconf configuration, and will not change to 
netplan/systemd-networkd.  After upgrade is finished, the /etc/resolv.conf will 
contain:
    a) the upstream name server(s)
    b) options edns0
    c) the local stub resolver (127.0.0.53)
    d) search domain

  the fixed resolvconf will remove (b).

  As mentioned, this case also should cover the situation of a native
  Bionic install, where netplan is removed and ifupdown/resolvconf is
  manually installed.

  == bionic or later install ==

  with a bionic install, ifupdown is not installed, instead netplan
  /systemd-networkd handle networking.  In this case, systemd-networkd
  manages the /etc/resolv.conf, and symlinks it to networkd's stub-
  resolv.conf which always contains only the local stub resolver
  (127.0.0.53) and (recently) options edns0, and local search domain.

  If resolvconf is installed while systemd-networkd is managing the
  network, then currently the resolv.conf contents will remain
  completely unchanged, still pointing to the local stub resolver.

  This resolvconf change will alter that, to remove 'options edns0'.  No
  other changes will be made from the stub-resolv.conf.

  [regression potential]

  Regressions due to this change would likely be seen in dns query
  failures with other system configurations.

  This will cause systems with resolvconf installed to lose the fix from
  bug 1811471, and again experience that bug.

  [other info]

  This affects only Bionic and later; in Xenial and earlier, systemd
  does not handle dns, and the 'edns0' option was not added to that
  systemd-resolved anyway.

  This also does not affect Debian, as it does not include the
  'resolvconf-pull-resolved' service either.

  original description:

  --

  Mint 19 (Ubuntu 18.04)

  Following latest mint update done on 24/02/2019, DNS is broken

  nslookup and dig of certain domain names work as expected, ping does
  not (ip works but not domain name)

  After a day of trial and error, testing I found that the problem lies
  with the presence of

  "options edns0"

  in /run/resolvconf/resolv.conf (link to by /etc/resolv.conf)

  With option present many dns lookups fail with both FF and chrome browswers 
and thunderbird...

[Touch-packages] [Bug 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

2019-04-01 Thread Balint Reczey

Fixed, still handcrafted patch.

** Patch added: "ubuntu-meta_1.431.patch"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+attachment/5251566/+files/ubuntu-meta_1.431.patch

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1820314] Re: [ASRock FM2A75M-DGS] No sound at all

asrock-mobo from live 19.04 live, sudo alsa force-reloading, pulseaudio
-k. Did not work

** Attachment added: "alsa-info.txt.1BjH77KqBS"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820314/+attachment/5251562/+files/alsa-info.txt.1BjH77KqBS

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

Title:
  [ASRock FM2A75M-DGS] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  cannot hear any sound even with headphones from any of 2 rear output
  port (green and blue) of my asrock fm2a75m-dgs or the front unique
  one.

  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
  CurrentDesktop: XFCE
  Date: Fri Mar 15 17:32:51 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_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, 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/1820314/+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 1820314] Re: [ASRock FM2A75M-DGS] No sound at all

xubuntu@xubuntu:~$ sudo alsa force-reload
Unloading ALSA sound driver modules: snd-seq-midi snd-seq-midi-event snd-seq 
snd-rawmidi snd-seq-device snd-hda-codec-hdmi snd-hda-codec-realtek 
snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep 
snd-pcm snd-timer (failed: modules still loaded: snd-hda-codec-hdmi 
snd-hda-codec-realtek snd-hda-codec-generic snd-hda-intel snd-hda-codec 
snd-hda-core snd-hwdep snd-pcm snd-timer).
Loading ALSA sound driver modules: snd-seq-midi snd-seq-midi-event snd-seq 
snd-rawmidi snd-seq-device snd-hda-codec-hdmi snd-hda-codec-realtek 
snd-hda-codec-generic snd-hda-intel snd-hda-codec snd-hda-core snd-hwdep 
snd-pcm snd-timer.
xubuntu@xubuntu:~$ alsamixer -V all
xubuntu@xubuntu:~$ pulseaudio -k
xubuntu@xubuntu:~$ sudo apt remove timidity
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
Il pacchetto "timidity" non è installato e quindi non è stato rimosso
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.


** Attachment added: "alsa-info.txt.O6vc7UB6bt"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1820314/+attachment/5251563/+files/alsa-info.txt.O6vc7UB6bt

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

Title:
  [ASRock FM2A75M-DGS] No sound at all

Status in alsa-driver package in Ubuntu:
  Incomplete

Bug description:
  cannot hear any sound even with headphones from any of 2 rear output
  port (green and blue) of my asrock fm2a75m-dgs or the front unique
  one.

  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
  CurrentDesktop: XFCE
  Date: Fri Mar 15 17:32:51 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_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed
  Symptom_Card: Audio interno - HD-Audio Generic
  Symptom_Jack: Green Line Out, Rear
  Symptom_Type: No sound at all
  Title: [To Be Filled By O.E.M., Realtek ALC662 rev1, Green Line Out, 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/1820314/+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 1822341] Re: [FFE][SRU] Please add ubuntu-wsl binary package

2019-04-01 Thread Balint Reczey

@adconrad Thank, I update the seed changes and the package accordingly.
Can the refresh and the ubuntu-wsl metapackage depending only on wslu get the 
ffe?

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

Title:
  [FFE][SRU] Please add ubuntu-wsl binary package

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  [Impact]
  * The newly added wsl seed includes the packages to be installed by default 
on Ubuntu running in the Windows Subsystem for Linux. In addition to the 
packages in ubuntu-minimal the added ubuntu-wsl metapackage depends on on 
utilities useful only in the WSL environment.

  [Test Case]
  * The package is a new metapackage, just try installing it

  [Fix]
  * The change add the new package and also adds the wsl seed to watch.

  [Regression potential]
  * Nothing, it is a new meta package, with no breaks, etc.

  [Other Info]
  * Please consider accepting this new binary package to Disco, because it 
needs to be SRU-d to all supported releases. The ubuntu-wsl metapackage will 
allow adding new packages for WSL installations only when more integration 
utilities become available.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1822341/+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 1822370] Re: 19.04 beta openssh-client broken pipe

2019-04-01 Thread Christian Ehrhardt 

@cjwatson - I subscribed you as you usually look after ssh(d) - have you
heard about that issue before or have any special recommendation
already?

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

Title:
  19.04 beta openssh-client broken pipe

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Upgrade to Xubuntu 19.04 beta from 18.10

  openssh-client

  when trying to ssh into another system, following error:

  packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  Problem is consistent on trying to connect to various systems.

  Can confirm was able to ssh prior to upgrade and can ssh into these
  systems from other systems.

  Can use putty on this system to ssh into these boxes as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openssh-client 1:7.9p1-9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 29 13:36:38 2019
  InstallationDate: Installed on 2018-11-14 (135 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b  26 Feb 2019
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1822370] Re: 19.04 beta openssh-client broken pipe

2019-04-01 Thread Christian Ehrhardt 

Interesting and maybe related

https://communities.vmware.com/thread/590825
https://github.com/vmware/open-vm-tools/issues/287
https://bugzilla.redhat.com/show_bug.cgi?id=1624437

The TL;DR of those is that VMWare would have issues with the AF21 QoS flag.
Does your client run in VMWare by chance?


Even if not it might be another part of the network setup between your client 
and server that reacts to the same change.

Please give the:
  $ ssh -o IPQoS=throughput user@host
a check (older default) if that resolves the issue.


I checked for the reason of this default change and found:
I found that the man page has this update about the defaults between 
cosmic/disco.
The upstream change is:
  
https://anongit.mindrot.org/openssh.git/commit/?id=5ee8448ad7c306f05a9f56769f95336a8269f379

There as no follow on change to that yet as far as I can tell from git.

I'd appreciate if you could do the testing with the QoS options (which
can also be set in /etc/ssh/ssh_config if you want to make them
permanent. Maybe the world isn't ready for the new defaults yet and we
might have to hold them back a release?

** Bug watch added: github.com/vmware/open-vm-tools/issues #287
   https://github.com/vmware/open-vm-tools/issues/287

** Bug watch added: Red Hat Bugzilla #1624437
   https://bugzilla.redhat.com/show_bug.cgi?id=1624437

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

Title:
  19.04 beta openssh-client broken pipe

Status in openssh package in Ubuntu:
  Incomplete

Bug description:
  Upgrade to Xubuntu 19.04 beta from 18.10

  openssh-client

  when trying to ssh into another system, following error:

  packet_write_wait: Connection to x.x.x.x port 22: Broken pipe

  Problem is consistent on trying to connect to various systems.

  Can confirm was able to ssh prior to upgrade and can ssh into these
  systems from other systems.

  Can use putty on this system to ssh into these boxes as well.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: openssh-client 1:7.9p1-9
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu23
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Mar 29 13:36:38 2019
  InstallationDate: Installed on 2018-11-14 (135 days ago)
  InstallationMedia: Xubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.2)
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome N/A
  SSHClientVersion: OpenSSH_7.9p1 Ubuntu-9, OpenSSL 1.1.1b  26 Feb 2019
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-03-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1822370/+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 1820314] Re: [ASRock FM2A75M-DGS] No sound at all