date:20200207

For the regression of openjdk-lts/11.0.6+10-1ubuntu1~19.10.1 (armhf), it
is a "jdk  FLAKY timed out"

For the regression of openjdk-lts/blacklisted (arm64), I can't open the
log, it always reports "This package is blacklisted. To get the entry
removed, contact a member of the release team." I guess it is a FLAKY
test too.

And I checked the log of the 1st regression, it has nothing to do with
alsa-lib or libasound2.

If it is OK to enqueue the SRU, please enqueue the debdiff of #10 and
#11.

thx.

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Touch-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected

2020-02-07 Thread Bastian Bittorf

@Goran:
both of mine controllers have a weight of 202 grams...
question: they where working on your machine earlier?

I have an onboard Intel Wireless-AC 9260 (rev 29) with recent firmware.

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

Title:
  Dualshock4 controller doesn't stay connected

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

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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

[Touch-packages] [Bug 1738676] Re: With natural scrolling, horizontal sliders behave backwards

2020-02-07 Thread yoyoma2

With 18.04 LTS, if you login with flashback, the volume slider in the
sound settings as well as the volume slider that drops down when
clicking the speaker indicator behave backwards even when natural
scrolling is off.

With flashback, turning natural scrolling on actually makes both volume
sliders behave as you would expect (up=up, down=down).  Using "natural
scrolling" is too unnatural to keep this setting however.

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

Title:
  With natural scrolling, horizontal sliders behave backwards

Status in GNOME Shell:
  New
Status in gnome-shell package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Confirmed

Bug description:
  When natural-scrolling is enabled, controlling horizontal sliders is
  backwards and counter intuitive.

  The volume control in the top-bar "speaker" icon is backwards.

  You have to...
  - scroll DOWN, to INCREASE the volume
  - scroll UP, to DECREASE the volume

  Expected behavior:

  Enable natural-scrolling and
  - scroll UP, to INCREASE the volume
  - scroll DOWN, to DECREASE the volume
  - scroll UP, to INCREASE the screen brightness
  - scroll DOWN, to DECREASE the screen brightness

  Enable natural-scrolling, hover over a horizontal slider, and...
  - scroll UP, to move the slider to the RIGHT
  - scroll DOWN, to move the slider to the LEFT

  This happens for the OSD volume icon, and for the volume slider in the
  topbar menu.

  This also happens for screen brightness controls.

  This problem occurs for both mouse natural-scrolling and touchpad
  natural scrolling.

  Expected fix:

  When the pointer hovers over the speaker icon in the scroll actions on the 
speaker icon in the top bar should be reversed.
  When the user interacts with a horizontal slider, scrolling to the top should 
always move the slider to the right, and scrolling down should always move the 
slider to the left, even if natural-scrolling is enabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.26.2-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 17 19:23:30 2017
  DisplayManager: gdm3
  GsettingsChanges:
   b'org.gnome.shell' b'command-history' b"['r']"
   b'org.gnome.shell' b'had-bluetooth-devices-setup' b'true'
   b'org.gnome.shell' b'favorite-apps' b"['google-chrome.desktop', 
'chrome-eppojlglocelodeimnohnlnionkobfln-Default.desktop', 'spotify.desktop', 
'org.gnome.Nautilus.desktop', 'org.gnome.Terminal.desktop', 
'org.gnome.gedit.desktop', 'libreoffice-writer.desktop', 
'libreoffice-calc.desktop', 'org.gnome.Software.desktop', 
'gnome-system-monitor.desktop']"
   b'org.gnome.desktop.interface' b'gtk-im-module' b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-12-10 (7 days ago)
  InstallationMedia: Ubuntu 17.10.0 2017.12.10 amd64 "Custom Artful Aardvark"
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1738676/+subscriptions

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

[Touch-packages] [Bug 1859754] Autopkgtest regression report (alsa-lib/1.1.9-0ubuntu1.1)

2020-02-07 Thread Ubuntu SRU Bot

All autopkgtests for the newly accepted alsa-lib (1.1.9-0ubuntu1.1) for eoan 
have finished running.
The following regressions have been reported in tests triggered by the package:

openjdk-lts/11.0.6+10-1ubuntu1~19.10.1 (armhf)
openjdk-lts/blacklisted (arm64)


Please visit the excuses page listed below and investigate the failures, 
proceeding afterwards as per the StableReleaseUpdates policy regarding 
autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-
migration/eoan/update_excuses.html#alsa-lib

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

This is the updated debdiff for bionic (adjust the input volume). thx.


** Patch added: "alsa-lib_1.1.3-5ubuntu0.3.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5326424/+files/alsa-lib_1.1.3-5ubuntu0.3.debdiff

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

This is the updated debdiff for eoan (adjust the input volume). thx.


** Patch added: "alsa-lib_1.1.9-0ubuntu1.1.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+attachment/5326423/+files/alsa-lib_1.1.9-0ubuntu1.1.debdiff

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Touch-packages] [Bug 1862341] Re: Errors thrown at boot: Security

2020-02-07 Thread Rudra Saraswat

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

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

Title:
  Errors thrown at boot: Security

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  DETAILS:

  Version:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

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

  Xorg, at boot, through a couple of errors:

  [ error ] display server started at tty -1

  For 20 seconds, the xorg server went on complaining the same issue. I
  tried to ssh into the virtual machine in VirtualBox, and it simply
  logged in without a password.

  Note:
Automatic Login was disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.438
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  7 11:41:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  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/1862341/+subscriptions

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

[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

Recently some users reported the headset-mic input volume is too low,
after installing the 1.1.9-0ubuntu1.1 on eoan and 1.1.3-5ubuntu0.3 on
bionic, I reproduced the issue of "headset-mic input volume is too low",
so please drop the debdiff of #1 and #2, I will upload new debdiffs
which put the input volume higher.

Verification failed on Eoan (input volume is to low):
On a machine of Lenovo X1 Carbon 7th, I already installed 19.10 (eoan) on it, 
then run sudo apt install libasound2, then the libasound is upgraded to 
1.1.9-0ubuntu1.1, check the /usr/share/alsa/ucm, all expected folders and files 
are there. upgrade the linux-firmware to 1.183.4, put snd_hda_intel and 
snd_soc_skl in the /etc/modporbe.d/blacklist.conf, reboot

now we could see speaker, dmic from gnome-sound-setting, if plug
headset, we could see headphone and headset-mic from UI, if we plug hdmi
monitor with audio capability, we could see hdmi-audio from UI, all
worked as expected.

But there is one issue, for headset-mic, we need to set the input volume
to maximum from UI, otherwise I couldn't record any sound.


Verification failed on Bionic (input volume is to low):
On a machine of Dell vistro 5390, I already installed 18.04 (bionic) on it, 
then run sudo apt install libasound2, then the libasound is upgraded to 
1.1.3-5ubuntu0.3, check the /usr/share/alsa/ucm, all expected folders and files 
are there. upgrade the linux-firmware to 1.173.15, Install the linux-oem-osp1 
kernel, put snd_soc_skl in the /etc/modporbe.d/blacklist.conf, reboot

now we could see speaker, dmic from gnome-sound-setting, if plug
headset, we could see headphone and headset-mic from UI, if we plug hdmi
monitor with audio capability, we could see hdmi-audio from UI, all
worked as expected.

But there is one issue, for headset-mic, we need to set the input volume
to maximum from UI, otherwise I couldn't record any sound.


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

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Touch-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected

Bastian, may I ask you to weight your controller? I suspect mine could
be not a genuine one. I checked online and dualshock4 controllers weight
around 220 grams. Mine weights 200 grams. The only way to understand if
it is really copy is to examine the inner parts but I cannot open it
because it would invalidate the warranty.

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

Title:
  Dualshock4 controller doesn't stay connected

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

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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

[Touch-packages] [Bug 1856811] Re: Systemd warning re moving remaining userspace processes

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

Title:
  Systemd warning re moving remaining userspace processes

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  :~$ dmesg|grep error
  [   49.262644] systemd[1]: Couldn't move remaining userspace processes, 
ignoring: Input/output error
  systemd/focal-proposed,now 244-3ubuntu1 amd64

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

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

[Touch-packages] [Bug 1825499] Re: Touchpad vertical sensitivity is much higher than horizontal sensitivity [HP Pavilion g6]

2020-02-07 Thread Сулейман

Thanks #29! 
Works like a charm on my HP Pavilion g6 2394sr

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

Title:
  Touchpad vertical sensitivity is much higher than horizontal
  sensitivity [HP Pavilion g6]

Status in systemd:
  Fix Released
Status in libinput package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Triaged
Status in libinput package in Fedora:
  Confirmed

Bug description:
  After installing Kubuntu 19.04, I found that vertical sensitivity is much 
higher than horizontal sensitivity.
  Installing xserver-xorg-input-synaptics improved the situation a bit and 
enabled KDE touchpad setting that were disabled.

  It's very annoying.

  Laptop: HP Pavilion g6.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xserver-xorg-input-synaptics 1.9.1-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CurrentDesktop: KDE
  Date: Fri Apr 19 12:00:02 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-13-generic 
root=UUID=e1903286-a666-49b1-8177-cf31dc5c8e9f ro quiet splash vt.handoff=1
  SourcePackage: xserver-xorg-input-synaptics
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/29/2013
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.25
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 183E
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: 56.32
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.25:bd05/29/2013:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088512005D160:rvnHewlett-Packard:rn183E:rvr56.32:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV X=Null
  dmi.product.name: HP Pavilion g6 Notebook PC
  dmi.product.sku: D4Z91EA#ABV
  dmi.product.version: 088512005D160
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.97-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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

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

[Touch-packages] [Bug 1862341] Re: Errors thrown at boot: Security

2020-02-07 Thread Seth Arnold

Hello Rudra, can you please investigate your /var/log/auth.log file to
see how the ssh logins were logged?

Thanks

** Information type changed from Private Security to Public Security

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

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

Title:
  Errors thrown at boot: Security

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  DETAILS:

  Version:  Ubuntu Focal Fossa (development branch)
  Release:  20.04

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

  Xorg, at boot, through a couple of errors:

  [ error ] display server started at tty -1

  For 20 seconds, the xorg server went on complaining the same issue. I
  tried to ssh into the virtual machine in VirtualBox, and it simply
  logged in without a password.

  Note:
Automatic Login was disabled.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: xorg 1:7.7+19ubuntu13
  ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
  Uname: Linux 5.4.0-9-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu15
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperVersion: 1.438
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Feb  7 11:41:03 2020
  DistUpgraded: Fresh install
  DistroCodename: focal
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   VMware SVGA II Adapter [15ad:0405] (prog-if 00 [VGA controller])
 Subsystem: VMware SVGA II Adapter [15ad:0405]
  LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
  Lsusb:
   Bus 001 Device 002: ID 80ee:0021 VirtualBox USB Tablet
   Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  Lsusb-t:
   /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/12p, 12M
   |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
  MachineType: innotek GmbH VirtualBox
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: file=/cdrom/preseed/username.seed initrd=/casper/initrd 
quiet splash --- maybe-ubiquity
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.family: Virtual Machine
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.100-4
  version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.4-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.20.6-1ubuntu1
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20190815-1
  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/1862341/+subscriptions

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

[Touch-packages] [Bug 1861975] Re: libiptc.pc non-functional

This bug was fixed in the package strongswan - 5.8.2-1ubuntu1

---
strongswan (5.8.2-1ubuntu1) focal; urgency=medium

  * Merge with Debian unstable (LP: #1861971). Remaining changes:
- d/control: Transition from strongswan-tnc-* being in extra packages
  to libcharon-extra-plugins (drop after 20.04)
- d/control: Transition from former Ubuntu only libcharon-standard-plugins
  to common libcharon-extauth-plugins (drop after 20.04)
- d/control: strongswan-starter hard-depends on strongswan-charon,
  therefore bump the dependency from Recommends to Depends. At the same
  time avoid a circular dependency by dropping
  strongswan-charon->strongswan-starter from Depends to Recommends as the
  binaries can work without the services but not vice versa.
  * Added Changes
- d/control: build-depend on libiptc-dev to avoid FTBFS (LP: #1861975)
  This is needed due to changes in regard to Debian bug 947176 and 939243
  and can later be dropped again.

strongswan (5.8.2-1) unstable; urgency=medium

  [ Jean-Michel Vourgère ]
  * README.Debian: Fixed typo

  [ Yves-Alexis Perez ]
  * d/control: replace iptables-dev b-dep by libip{4,6}tc-dev (Closes: #946148)
  * d/watch: use uscan special strings
  * New upstream version 5.8.2
  * d/control: update dh compat level to 12
  * strongswan-nm: update path for dbus service file
  * install DRBG plugin to libstrongswan
  * d/control: add ${misc:Pre-Depends} to strongswan-starter

 -- Christian Ehrhardt   Wed, 05 Feb
2020 08:28:30 +0100

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

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

Title:
  libiptc.pc non-functional

Status in iptables package in Ubuntu:
  Invalid
Status in strongswan package in Ubuntu:
  Fix Released

Bug description:
  Hi,
  I found this by trying to merge a newer strongswan which was an FTFBS.
  I wondered what happened and found:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=947176

  This is exactly my issue and we might face FTBFS in strongswan,
  systemd and probably others as well.

  The fix seems to be to merge iptables 1.8.4-2 from Debian.
  Could someone usually looking after iptables do that please?

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

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

[Touch-packages] [Bug 1861446] Re: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts

2020-02-07 Thread Brian Murray

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

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

** Changed in: apport (Ubuntu Focal)
   Importance: Undecided => Medium

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

** Changed in: apport (Ubuntu Focal)
   Importance: Medium => High

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

Title:
  on focal 'ubuntu-bug linux' doesn't automatically collect kernel
  artifacts

Status in apport package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  In Progress
Status in linux source package in Focal:
  Invalid

Bug description:
  Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The
  issue was filed against linux-signed-5.4 (Ubuntu) rather than linux
  (Ubuntu), and none of the logs usually included with kernel bug
  reports were included.

  After the bug was changed from linux-signed-5.4 to linux, I was
  prompted to run apport-collect by the kernel team's triagebot and that
  worked successfully:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity

  My guess is that apport needs to be updated to understand a change in
  kernel packaging.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu16
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CrashReports:
   640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 
03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash
   600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 
20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash
   640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 
20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash
  Date: Thu Jan 30 18:44:47 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)

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

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

[Touch-packages] [Bug 1861446] Re: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts

** Branch linked: lp:~ubuntu-core-dev/ubuntu/focal/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/1861446

Title:
  on focal 'ubuntu-bug linux' doesn't automatically collect kernel
  artifacts

Status in apport package in Ubuntu:
  In Progress
Status in linux package in Ubuntu:
  Invalid
Status in apport source package in Focal:
  In Progress
Status in linux source package in Focal:
  Invalid

Bug description:
  Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The
  issue was filed against linux-signed-5.4 (Ubuntu) rather than linux
  (Ubuntu), and none of the logs usually included with kernel bug
  reports were included.

  After the bug was changed from linux-signed-5.4 to linux, I was
  prompted to run apport-collect by the kernel team's triagebot and that
  worked successfully:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity

  My guess is that apport needs to be updated to understand a change in
  kernel packaging.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu16
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CrashReports:
   640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 
03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash
   600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 
20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash
   640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 
20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash
  Date: Thu Jan 30 18:44:47 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)

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

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

[Touch-packages] [Bug 1671951] Re: networkd should allow configuring IPV6 MTU

2020-02-07 Thread Ryan Harper

Verified Eoan systemd 242-7ubuntu3.7 correctly sets IPv6 MTU
Verified Bionic systemd 237-3ubuntu10.39 correctly sets IPv6 MTU

** Attachment added: "curtin vmtest logs for ipv6 mtu verification"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1671951/+attachment/5326389/+files/bug-1671951-curtin-vmtest-verification-v2.tar.gz

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

Title:
  networkd should allow configuring IPV6 MTU

Status in systemd:
  Unknown
Status in cloud-init package in Ubuntu:
  Confirmed
Status in netplan.io package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in cloud-init source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in cloud-init source package in Disco:
  New
Status in netplan.io source package in Disco:
  Fix Released
Status in systemd source package in Disco:
  Won't Fix
Status in cloud-init source package in Eoan:
  New
Status in netplan.io source package in Eoan:
  Fix Released
Status in systemd source package in Eoan:
  Fix Committed
Status in cloud-init source package in Focal:
  Confirmed
Status in netplan.io source package in Focal:
  Fix Released
Status in systemd source package in Focal:
  Fix Released

Bug description:
  = netplan.io =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]
   * Apply a netplan configuration that specifices ipv6-mtu:

  network:
version: 2
ethernets:
  eth0:
dhcp4: true
dhcp6: true
ipv6-mtu: 6000

   * Check that MTU bytes, is at least IPv6MTUBytes on the interface:

  $ sysctl net.ipv6.conf.eth0.mtu
  net.ipv6.conf.eth0.mtu = 6000

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of netplan.io =

  = systemd =

  [Impact]

   * IPv6 traffic failing to send/receive due to incompatible/low MTU
  setting. Specifically, IPv6 traffic may have higher MTU requirements
  than IPv4 traffic and thus may need to be overridden and/or set to a
  higher value than IPv6 traffic.

  [Test Case]

   * Use IPv6MTUBytes= setting in a .network unit
   * Restart systemd-network
   * Check that there no error messages / warnings about not-recognizing this 
option
   * Check that MTU bytes, is at least IPv6MTUBytes on the interface

  [Regression Potential]

   * This is a future compatible backport of an additional keyword not
  used by default. It may result in MTU change to a higher value, which
  should not cause loss of connectivity.

  [Other Info]

   * Original bug report below

  = end of systemd =

  1) Zesty
  2) systemd-232-19
  3) I need to configure the IPV6 MTU for tunneling by adding an 
IPv6MTUBytes=1480 value in the .network file for an interface with an IPV6 
static address in the [Network] section
  4) networkd does not parse or read the value and does not apply this 
configuration to the interface.

  Upstream has discussed this issue here:

  https://github.com/systemd/systemd/pull/1533

  But it's been closed in favor of only setting via RA.

  However, we know of multiple use-case which are currently supported in
  ifdupdown where we want to retain control over IPV6 MTU values outside
  of PMTU Discovery configurations.

  Some context from those discussions

  >> Client systems that route their ipv6 packets to a 6in4 router also
  >> have to have their ipv6 mtu lowered.  They could lower their link mtu,
  >> so their ipv6 packets are small enough, but that reduces performance
  >> of their ipv4 network.

  Yes.  Anything that creates a PMTUD black hole can result in
  situations where the higher header overhead of IPv6 will cause IPv4 to
  pass but IPv6 traffic to be dropped.

  One example here is egress from an ipsec tunnel wherein the next
  hop MTU is too low for IPv6 datagrams to pass.  Another is VM ->
  whatever -> host bridge -> tunnel ingress.  If the datagram cannot enter
  the tunnel due to size, it is dropped, and an ICMP response uses the
  tunnel address as a source, which may not be routable back to the
  origin.  This one is an issue with IPv4 as well, and is one case where
  manually setting the IPv6 MTU lower than the (also manually set) device
  MTU is of benefit.

  In essence, any of these sort of cases that require an explicit
  setting of the device MTU will likely require a setting of the IPv6 mtu
  as well to account for its

[Touch-packages] [Bug 1846232] Re: networkd pads interface MTU by 4 bytes for vlan even when told not to

2020-02-07 Thread Ryan Harper

Verified VLANs on Eoan using systemd 242-7ubuntu3.7 from -proposed
correctly set the MTU to 1500 when specified in the netplan config.


** Attachment added: "curtin vmtest logs for vlan mtu verification"
   
https://bugs.launchpad.net/curtin/+bug/1846232/+attachment/5326388/+files/bug-1846232-curtin-vmtest-verification-v2.tar.gz

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

Title:
  networkd pads interface MTU by 4 bytes for vlan even when told not to

Status in curtin:
  Invalid
Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Eoan:
  Fix Committed

Bug description:
  [impact]

  vlan interface has wrong mtu, which may cause lost packets due to
  incorrect mtu

  [test case]

  configure a system using the netplan cfg similar to comment 2.

  alternately, networkd config can be used, similar to:

  ubuntu@lp1846232-e:/run/systemd/network$ grep . *
  10-netplan-ens3.2667.netdev:[NetDev]
  10-netplan-ens3.2667.netdev:Name=ens3.2667
  10-netplan-ens3.2667.netdev:MTUBytes=1500
  10-netplan-ens3.2667.netdev:Kind=vlan
  10-netplan-ens3.2667.netdev:[VLAN]
  10-netplan-ens3.2667.netdev:Id=2667
  10-netplan-ens3.2667.network:[Match]
  10-netplan-ens3.2667.network:Name=ens3.2667
  10-netplan-ens3.2667.network:[Network]
  10-netplan-ens3.2667.network:LinkLocalAddressing=ipv6
  10-netplan-ens3.2667.network:Address=1.2.3.4/32
  10-netplan-ens3.2667.network:ConfigureWithoutCarrier=yes
  10-netplan-ens3.link:[Match]
  10-netplan-ens3.link:OriginalName=ens3
  10-netplan-ens3.link:[Link]
  10-netplan-ens3.link:WakeOnLan=off
  10-netplan-ens3.link:MTUBytes=1500
  10-netplan-ens3.network:[Match]
  10-netplan-ens3.network:Name=ens3
  10-netplan-ens3.network:[Network]
  10-netplan-ens3.network:LinkLocalAddressing=ipv6
  10-netplan-ens3.network:VLAN=ens3.2667

  The reboot and check the mtus:

  ubuntu@lp1846232-e:~$ ip l show ens3
  2: ens3:  mtu 1504 qdisc fq_codel state UP 
mode DEFAULT group default qlen 1000
  link/ether 52:54:00:12:99:1b brd ff:ff:ff:ff:ff:ff
  ubuntu@lp1846232-e:~$ ip l show ens3.2667
  3: ens3.2667@ens3:  mtu 1500 qdisc noqueue 
state UP mode DEFAULT group default qlen 1000
  link/ether 52:54:00:12:99:1b brd ff:ff:ff:ff:ff:ff

  The base interface should have a mtu of only 1500.

  [regression potential]

  As this corrects/adjusts the mtu of the interface, regressions would
  likely involve interface(s) being assigned incorrect mtu values, which
  then would lead to dropped packets and/or lowered network performance.

  [scope]

  this is needed only for Eoan.

  disco and earlier don't have the patch that introduces this problem,
  commit 4b151b71320bbee1549afcbad5554a40d90d63b4

  focal already has the patches that fix this, commit
  f6fcc1c2a41eae749467de58453174296b635a69 (and the commit before it)

  see comment 4 for more details

  [other info]

  original description:

  ---

  From https://jenkins.ubuntu.com/server/job/curtin-vmtest-devel-
  amd64/916/console:

  ==
  FAIL: test_ip_output (vmtests.test_network_vlan.EoanTestNetworkVlan)
  --
  Traceback (most recent call last):
    File 
"/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py",
 line 311, in test_ip_output
  routes)
    File 
"/var/lib/jenkins/servers/server/workspace/curtin-vmtest-devel-amd64/curtin-916/tests/vmtests/test_network.py",
 line 337, in check_interface
  int(ipcfg[key]))
  AssertionError: 1500 != 1504
   >> begin captured stdout << -
  parsed ip_a dict:
  interface0:
  broadcast: 10.245.175.255
  group: default
  inet4:
  -   address: 10.245.168.16
  prefixlen: '21'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fec0::d6be:d9ff:fea8:4913
  prefixlen: '64'
  scope: site
  valid_lft: 86256sec
  -   address: fe80::d6be:d9ff:fea8:4913
  prefixlen: '64'
  scope: link
  valid_lft: forever
  interface: interface0
  loopback: false
  lower_up: false
  mac_address: d4:be:d9:a8:49:13
  mtu: '1500'
  multicast: false
  qdisc: fq_codel
  qlen: '1000'
  running: false
  state: UP
  up: false
  interface1:
  broadcast: 10.245.188.255
  group: default
  inet4:
  -   address: 10.245.188.2
  prefixlen: '24'
  scope: global
  valid_lft: forever
  inet6:
  -   address: fec0::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: site
  valid_lft: 86256sec
  -   address: fe80::d6be:d9ff:fea8:4915
  prefixlen: '64'
  scope: link
  valid_lft:

Re: [Touch-packages] [Bug 1862157] [NEW] dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles

2020-02-07 Thread Simon Kelley

tftp-root is a security feature. The tftp protocol is entirely
unauthenticated, and if a request was allowed to go outside the
specified root directory, than that effectively makes all readable files
on the host available for internet-wide access, which is not generally
desirable. If you want TFTP to be able to access any file on the
machine, don't set a tftp-root.


Simon.


On 06/02/2020 11:02, Thomas Schweikle wrote:
> Public bug reported:
> 
> dnsmasq does in all cases prepend "tftp_root" to tftp-files.
> 
> tftp-root=/data/tftp
> dhcp-boot=grub/i386-pc/core.0
> 
> now have some config files for different subnets:
> dhcp-boot=net:172-18-1,grub/i386-pc/core.0,172.18.1.1
> dhcp-boot=net:172-18-8,pxelinux.0,172.18.8.1
> dhcp-boot=net:172-18-7,/var/lib/tftpboot/pxelinux.0,spacewalk-ber.bfs.de
> 
> Now booting clients within subnet 172.18.1.0/24 will boot grub with:
> /data/tftp/grub/i386-pc/core.0
> 
> Booting clients within subnet 172.18.2.0/24 will boot pxelinux.0 with:
> /data/tftp/pxelinux.0
> 
> And in subnet 172.18.7.0/24 clients will boot with:
> /data/tftp/var/lib/tftpboot/pxelinux.0
> 
> and return a "File not found" error.
> 
> I'd expected:
> 172.18.1: grub/i386-pc/core.0   (file found within /data/tftp -- 
> without exposing path)
> 172.18.2: pxelinux.0(file found within /data/tftp -- 
> without exposing path)
> 172.18.3: /pxelinux.0   (file found within /)
> 172.18.7: /var/lib/tftpboot/pxelinux.0  (file found within 
> /var/lib/tftpboot/pxelinux.0)
> 
> or even better: some way to set tftp-root for every subnet-config and
> having only relative paths to access files regardless of giving absolute
> or relative paths.
> 
> ProblemType: Bug
> DistroRelease: Ubuntu 18.04
> Package: dnsmasq 2.79-1
> ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18
> Uname: Linux 4.15.0-87-generic x86_64
> ApportVersion: 2.20.9-0ubuntu7.10
> Architecture: amd64
> Date: Thu Feb  6 11:43:07 2020
> InstallationDate: Installed on 2014-01-31 (2197 days ago)
> InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
> (20131016)
> PackageArchitecture: all
> ProcEnviron:
>  TERM=xterm
>  PATH=(custom, no user)
>  XDG_RUNTIME_DIR=
>  LANG=de_DE.UTF-8
>  SHELL=/bin/bash
> SourcePackage: dnsmasq
> UpgradeStatus: Upgraded to bionic on 2018-11-23 (439 days ago)
> mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595
> mtime.conffile..etc.dnsmasq.conf: 2016-08-17T12:18:41.225353
> 
> ** Affects: dnsmasq (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 dnsmasq in Ubuntu.
https://bugs.launchpad.net/bugs/1862157

Title:
  dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  dnsmasq does in all cases prepend "tftp_root" to tftp-files.

  tftp-root=/data/tftp
  dhcp-boot=grub/i386-pc/core.0

  now have some config files for different subnets:
  dhcp-boot=net:172-18-1,grub/i386-pc/core.0,172.18.1.1
  dhcp-boot=net:172-18-8,pxelinux.0,172.18.8.1
  dhcp-boot=net:172-18-7,/var/lib/tftpboot/pxelinux.0,spacewalk-ber.bfs.de

  Now booting clients within subnet 172.18.1.0/24 will boot grub with:
  /data/tftp/grub/i386-pc/core.0

  Booting clients within subnet 172.18.2.0/24 will boot pxelinux.0 with:
  /data/tftp/pxelinux.0

  And in subnet 172.18.7.0/24 clients will boot with:
  /data/tftp/var/lib/tftpboot/pxelinux.0

  and return a "File not found" error.

  I'd expected:
  172.18.1: grub/i386-pc/core.0   (file found within /data/tftp -- 
without exposing path)
  172.18.2: pxelinux.0(file found within /data/tftp -- 
without exposing path)
  172.18.3: /pxelinux.0   (file found within /)
  172.18.7: /var/lib/tftpboot/pxelinux.0  (file found within 
/var/lib/tftpboot/pxelinux.0)

  or even better: some way to set tftp-root for every subnet-config and
  having only relative paths to access files regardless of giving
  absolute or relative paths.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18
  Uname: Linux 4.15.0-87-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  Date: Thu Feb  6 11:43:07 2020
  InstallationDate: Installed on 2014-01-31 (2197 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to bionic on 2018-11-23 (439 days ago)
  mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595
  mtime.conffile..etc.dnsmasq.conf: 2016-08-17T12:18:41.225353

To manage notifications about this bug go to:

[Touch-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

Related pull request: https://github.com/canonical/lightdm/pull/111

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

Title:
  language-options causes live CD sessions to be untranslated

Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Touch-packages] [Bug 378783] Re: xdg-open *.desktop opens text editor

2020-02-07 Thread Kenneth Hanson

Bug still present in Kubuntu 19.10.

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

Title:
  xdg-open *.desktop opens text editor

Status in GLib:
  New
Status in gvfs:
  New
Status in glib2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: xdg-utils

  In order to reproduce it execute "xdg-open *.desktop" (choose any
  .desktop file, e.g. one from /usr/share/applications). Actually your
  favorite text editor will open the file. Expected result: It'll be
  executed.

  Because of this bug, desktop entries with the new "#!/usr/bin/env xdg-
  open" shebang feature were opened in the text editor when executed
  from command line.

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

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

[Touch-packages] [Bug 1553466] Re: org.gnome.SessionManager was not provided by any .service files

2020-02-07 Thread Jerry Quinn

I'm seeing it after rebooting my 18.04 machine today.

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

Title:
  org.gnome.SessionManager was not provided by any .service files

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  This is logged into journalctl:

   org.gnome.ScreenSaver[1755]: ** (gnome-screensaver:1868): WARNING **:
  Couldn't get presence status: The name org.gnome.SessionManager was
  not provided by any .service files

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar  5 08:37:25 2016
  ExecutablePath: /usr/bin/dbus-daemon
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.dbus.log:
   Activating service name='org.gnome.Terminal'
   Successfully activated service 'org.gnome.Terminal'
   Activating service name='org.gnome.Terminal'
   Successfully activated service 'org.gnome.Terminal'

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

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

[Touch-packages] [Bug 1553466] Re: org.gnome.SessionManager was not provided by any .service files

2020-02-07 Thread Jerry Quinn

Linux smaug 4.15.0-76-generic #86-Ubuntu SMP Fri Jan 17 17:24:28 UTC
2020 x86_64 x86_64 x86_64 GNU/Linux

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

Title:
  org.gnome.SessionManager was not provided by any .service files

Status in dbus package in Ubuntu:
  Confirmed

Bug description:
  This is logged into journalctl:

   org.gnome.ScreenSaver[1755]: ** (gnome-screensaver:1868): WARNING **:
  Couldn't get presence status: The name org.gnome.SessionManager was
  not provided by any .service files

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
  Uname: Linux 4.4.0-10-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sat Mar  5 08:37:25 2016
  ExecutablePath: /usr/bin/dbus-daemon
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)
  upstart.dbus.log:
   Activating service name='org.gnome.Terminal'
   Successfully activated service 'org.gnome.Terminal'
   Activating service name='org.gnome.Terminal'
   Successfully activated service 'org.gnome.Terminal'

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

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

[Touch-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected

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

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

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

Title:
  Dualshock4 controller doesn't stay connected

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

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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

[Touch-packages] [Bug 1861358] Re: tracker search hangs and never returns results

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

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

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

Title:
  tracker search hangs and never returns results

Status in tracker package in Ubuntu:
  Confirmed

Bug description:
  When I run

  $ tracker search -f Bruni

  I see the following output on console
  -
  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot 
register existing type 'TrackerLanguage'

  (tracker search:2): GLib-GObject-WARNING **: 00:31:10.761: cannot
  add private field to invalid (non-instantiatable) type ''

  (tracker search:2): GLib-CRITICAL **: 00:31:10.761:
  g_once_init_leave: assertion 'result != 0' failed

  (tracker search:2): GLib-GObject-CRITICAL **: 00:31:10.761: 
g_object_new_valist: assertion 'G_TYPE_IS_OBJECT (object_type)' failed
  -

  The program hangs and never returns. Sending Control-C brings me back
  to prompt

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.3.0-1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  Date: Thu Jan 30 00:31:59 2020
  ExecutablePath: /usr/bin/tracker
  InstallationDate: Installed on 2016-11-05 (1180 days ago)
  InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2020-01-21 (8 days ago)

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

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

[Touch-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)

2020-02-07 Thread Timo Aaltonen

Hello Hui, or anyone else affected,

Accepted alsa-lib into eoan-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.9-0ubuntu1.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-eoan to verification-done-eoan. If it does not fix
the bug for you, please add a comment stating that, and change the tag
to verification-failed-eoan. 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.

** Also affects: alsa-lib (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Also affects: alsa-lib (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: alsa-lib (Ubuntu Eoan)
   Status: New => Fix Committed

** Tags added: verification-needed verification-needed-eoan

** Changed in: alsa-lib (Ubuntu Bionic)
   Status: New => Fix Committed

** Tags added: verification-needed-bionic

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

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

2020-02-07 Thread Timo Aaltonen

Hello Hui, or anyone else affected,

Accepted alsa-lib into bionic-proposed. The package will build now and
be available at https://launchpad.net/ubuntu/+source/alsa-
lib/1.1.3-5ubuntu0.3 in a few hours, and then in the -proposed
repository.

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

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

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

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

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

Title:
  add ucm to make alsa/sof driver work under PA (variants of Lenovo X1
  Carbon 7th, Dell cnl and cml machines)

Status in alsa-lib package in Ubuntu:
  Fix Committed
Status in alsa-lib source package in Bionic:
  Fix Committed
Status in alsa-lib source package in Eoan:
  Fix Committed

Bug description:
  This ucm is only for Eoan and Bionic, for focal and future versions,
  we plan to integrate the ucm2 instead of this ucm, and the ucm2
  depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under
  developing by the community, is not ready yet.

  [Impact]
  In the oem project, we have a couple of Lenovo and Dell machines which
  connect the digital mic to PCH directly, this design needs the new
  sound driver soc/sof, and this driver can't work under pulseaudio
  automatically, we need to integrate the ucm for the driver, then the
  sof dirver could work under pulseaudio and gnome.

  This ucm is maintained by intel audio team, and it is not upstreamed
  and will not be upstreamed, since the community is developing the ucm2
  which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still
  under developing), for bionic and eoan, we have to integrate this ucm
  since the alsa-lib version is too low. For focal and future version, we
  are going to integrate the ucm2 after the ucm2 is ready.

  This ucm is already verified in the oem project, now it is time to put it
  into the stock ubuntu. 

  [Fix]
  These ucm files are backported from sof_ucm1 branch of
  https://github.com/thesofproject/alsa-ucm-conf.git

  [Test Case]
  Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of
  pulseaudio, the ucm files are loaded successfully, then check the
  gnome-sound-setting, both output and input devices work well.

  [Regression Risk]
  Low, just add some new ucm files, and this will not affect other machines,
  and those new added ucm files are only used by specific machines which enable
  the sof driver.

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

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

[Touch-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected

2020-02-07 Thread Bastian Bittorf

Same issue for me with fresh mainline kernel 5.5.2 on debian.
The controller model (the same) is: CUH-ZCT2U

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

Title:
  Dualshock4 controller doesn't stay connected

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

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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

[Touch-packages] [Bug 1862388] [NEW] makedev installation fails on Docker containers

2020-02-07 Thread phanect

Public bug reported:

On Ubuntu 18.04 on Docker container, makedev installation fails.

I guess this issue is almost the same as 1679727 and 1675163.

Here's the console output:

# apt-get install --yes makedev
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following NEW packages will be installed:
  makedev
0 upgraded, 1 newly installed, 0 to remove and 18 not upgraded.
Need to get 24.4 kB of archives.
After this operation, 98.3 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu bionic/universe amd64 makedev all 
2.3.1-93ubuntu2 [24.4 kB]
Fetched 24.4 kB in 0s (96.0 kB/s)
debconf: delaying package configuration, since apt-utils is not installed
Selecting previously unselected package makedev.
(Reading database ... 4046 files and directories currently installed.)
Preparing to unpack .../makedev_2.3.1-93ubuntu2_all.deb ...
Unpacking makedev (2.3.1-93ubuntu2) ...
Setting up makedev (2.3.1-93ubuntu2) ...
mknod: mem-: Operation not permitted
makedev mem c 1 1 root kmem 0640: failed
mknod: kmem-: Operation not permitted
makedev kmem c 1 2 root kmem 0640: failed
mknod: null-: Operation not permitted
makedev null c 1 3 root root 0666: failed
mknod: port-: Operation not permitted
makedev port c 1 4 root kmem 0640: failed
mknod: zero-: Operation not permitted
makedev zero c 1 5 root root 0666: failed
mknod: full-: Operation not permitted
makedev full c 1 7 root root 0666: failed
mknod: random-: Operation not permitted
makedev random c 1 8 root root 0666: failed
mknod: urandom-: Operation not permitted
makedev urandom c 1 9 root root 0666: failed
mknod: tty-: Operation not permitted
makedev tty c 5 0 root tty 0666: failed
mknod: ram0-: Operation not permitted
makedev ram0 b 1 0 root disk 0660: failed
mknod: ram1-: Operation not permitted
makedev ram1 b 1 1 root disk 0660: failed
mknod: ram2-: Operation not permitted
makedev ram2 b 1 2 root disk 0660: failed
mknod: ram3-: Operation not permitted
makedev ram3 b 1 3 root disk 0660: failed
mknod: ram4-: Operation not permitted
makedev ram4 b 1 4 root disk 0660: failed
mknod: ram5-: Operation not permitted
makedev ram5 b 1 5 root disk 0660: failed
mknod: ram6-: Operation not permitted
makedev ram6 b 1 6 root disk 0660: failed
mknod: ram7-: Operation not permitted
makedev ram7 b 1 7 root disk 0660: failed
mknod: ram8-: Operation not permitted
makedev ram8 b 1 8 root disk 0660: failed
mknod: ram9-: Operation not permitted
makedev ram9 b 1 9 root disk 0660: failed
mknod: ram10-: Operation not permitted
makedev ram10 b 1 10 root disk 0660: failed
mknod: ram11-: Operation not permitted
makedev ram11 b 1 11 root disk 0660: failed
mknod: ram12-: Operation not permitted
makedev ram12 b 1 12 root disk 0660: failed
mknod: ram13-: Operation not permitted
makedev ram13 b 1 13 root disk 0660: failed
mknod: ram14-: Operation not permitted
makedev ram14 b 1 14 root disk 0660: failed
mknod: ram15-: Operation not permitted
makedev ram15 b 1 15 root disk 0660: failed
mknod: ram16-: Operation not permitted
makedev ram16 b 1 16 root disk 0660: failed
mknod: loop0-: Operation not permitted
makedev loop0 b 7 0 root disk 0660: failed
mknod: loop1-: Operation not permitted
makedev loop1 b 7 1 root disk 0660: failed
mknod: loop2-: Operation not permitted
makedev loop2 b 7 2 root disk 0660: failed
mknod: loop3-: Operation not permitted
makedev loop3 b 7 3 root disk 0660: failed
mknod: loop4-: Operation not permitted
makedev loop4 b 7 4 root disk 0660: failed
mknod: loop5-: Operation not permitted
makedev loop5 b 7 5 root disk 0660: failed
mknod: loop6-: Operation not permitted
makedev loop6 b 7 6 root disk 0660: failed
mknod: loop7-: Operation not permitted
makedev loop7 b 7 7 root disk 0660: failed
mknod: tty0-: Operation not permitted
makedev tty0 c 4 0 root tty 0600: failed
mknod: console-: Operation not permitted
makedev console c 5 1 root tty 0600: failed
/sbin/MAKEDEV: don't know how to make device "tty0"
dpkg: error processing package makedev (--configure):
 installed makedev package post-installation script subprocess returned error 
exit status 1
Errors were encountered while processing:
 makedev
E: Sub-process /usr/bin/dpkg returned an error code (1)
Exited with code exit status 100
CircleCI received exit code 100

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

# lsb_release -rd
Description:Ubuntu 18.04.3 LTS
Release:18.04

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

2.3.1-93ubuntu2 as written in the above log

3) What you expected to happen

Installation succeeds without error

4) What happened instead

The above error happens and the installation fails.

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

** Description changed:

  On Ubuntu 18.04 on Docker container, makedev installation fails.
  
  I guess this issue is almost the same as 1679727 and 1675163.

[Touch-packages] [Bug 1862386] Re: package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in package vim-tiny 2:7.4

2020-02-07 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade:
  trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also
  in package vim-tiny 2:7.4.1689-3ubuntu1.3

Status in vim package in Ubuntu:
  New

Bug description:
  PDFCROP 1.38, 2012/11/02 - Copyright (c) 2002-2012 by Heiko Oberdiek.

  kpathsea: Running mktexfmt pdftex.fmt
  mktexfmt: mktexfmt is using the following fmtutil.cnf files (in precedence 
order):
  mktexfmt:   /usr/share/texmf/web2c/fmtutil.cnf
  mktexfmt: mktexfmt is using the following fmtutil.cnf file for writing 
changes:
  mktexfmt:   /home/dprai/.texmf-config/web2c/fmtutil.cnf
  mktexfmt [INFO]: writing formats under /home/dprai/.texmf-var/web2c
  mktexfmt [INFO]: did not find entry for byfmt=pdftex, skipped
  mktexfmt [INFO]: Not selected formats: 2
  mktexfmt [INFO]: Total formats: 2
  mktexfmt [INFO]: exiting with status 0
  !!! Error: pdfTeX run failed with value 1!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: vim-runtime 2:7.4.1689-3ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Fri Feb  7 21:24:31 2020
  DpkgHistoryLog:
   Start-Date: 2020-02-07  21:24:30
   Commandline: apt-get -f install
   Requested-By: dprai (1000)
   Upgrade: vim-runtime:amd64 (2:7.4.1689-3ubuntu1.2, 2:7.4.1689-3ubuntu1.3)
  DpkgTerminalLog:
   Preparing to unpack .../vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb ...
   Unpacking vim-runtime (2:7.4.1689-3ubuntu1.3) over (2:7.4.1689-3ubuntu1.2) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb (--unpack):
trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in 
package vim-tiny 2:7.4.1689-3ubuntu1.3
  DuplicateSignature:
   package:vim-runtime:2:7.4.1689-3ubuntu1.2
   Unpacking vim-runtime (2:7.4.1689-3ubuntu1.3) over (2:7.4.1689-3ubuntu1.2) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb (--unpack):
trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in 
package vim-tiny 2:7.4.1689-3ubuntu1.3
  ErrorMessage: trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which 
is also in package vim-tiny 2:7.4.1689-3ubuntu1.3
  InstallationDate: Installed on 2018-12-24 (410 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: vim
  Title: package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: 
trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in 
package vim-tiny 2:7.4.1689-3ubuntu1.3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

On 2020-02-07 16:41, Alkis Georgopoulos wrote:
> I checked with 20.04 and it appears that recent Ubuntu live CDs
> don't have boot=casper anymore; they do still have
> initrd=/casper/initrd;

I also saw that /proc/cmdline contains BOOT_IMAGE=/casper/..., so the
approach would probably have worked with a minor modification.

> but anyway, ^/cow should be fine (sorry I hadn't noticed the ^ there
> before).

Ok, good, then I keep the debdiff for now, in the hope that some sponsor
will approve and upload it soon.

> Thank you for your work in this.

Thank you for reporting it. The current behavior in live sessions of the
flavors is indeed unintentional and unnecessary.

** No longer affects: accountsservice (Ubuntu)

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

Title:
  language-options causes live CD sessions to be untranslated

Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Touch-packages] [Bug 1587142] Re: Shutdown hangs in md kworker after "Reached target Shutdown."

2020-02-07 Thread Joshua Diamant

I am having this issue using IMSM / VROC 6.2 on Ubuntu 18.04 LTS, Kernel
5.3.0-28, mdadm - v4.1-rc1 - 2018-03-22.

I am running a bcache cache device on one of the RAID 1 IMSM (VROC)
arrays. At the very minimum, every reboot the device needs to resync
(not shutting down clean).

What other information is required to help us debug this issue?

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

Title:
  Shutdown hangs in md kworker after "Reached target Shutdown."

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  I'm booting a fully patched 16.04 from an Intel Rapid Storage
  Technology enterprise RAID1 volume (ThinkServer TS140 with two SATA
  ST1000NM0033-9ZM drives, ext4 root partition, no LVM, UEFI mode).

  If the RAID volume is recovering or resyncing for whatever reason, then `sudo 
systemctl reboot` and `sudo systemctl poweroff` work fine (I had to `sudo 
systemctl --now disable lvm2-lvmetad lvm2-lvmpolld lvm2-monitor` in order to 
consistently get that). However, once the recovery/resync is complete and 
clean, the reboot and poweroff commands above hang forever after "Reached 
target Shutdown.". Note that issuing `sudo swapoff -a` beforehand (suggested in 
the bug #1464917) does not help.
  [EDIT]Actually, the shutdown also hangs from time to time during a resync. 
But I've never seen it succeed once the resync is complete.[/EDIT]

  Then, if the server has been forcibly restarted with the power button,
  the Intel Matrix Storage Manager indicates a "Normal" status for the
  RAID1 volume, but Ubuntu then resyncs the volume anyway:

  [1.223649] md: bind
  [1.228426] md: bind
  [1.230030] md: bind
  [1.230738] md: bind
  [1.232985] usbcore: registered new interface driver usbhid
  [1.233494] usbhid: USB HID core driver
  [1.234022] md: raid1 personality registered for level 1
  [1.234876] md/raid1:md126: not clean -- starting background reconstruction
  [1.234956] input: CHESEN USB Keyboard as 
/devices/pci:00/:00:14.0/usb3/3-10/3-10:1.0/0003:0A81:0101.0001/input/input5
  [1.236273] md/raid1:md126: active with 2 out of 2 mirrors
  [1.236797] md126: detected capacity change from 0 to 1000202043392
  [1.246271] md: md126 switched to read-write mode.
  [1.246834] md: resync of RAID array md126
  [1.247325] md: minimum _guaranteed_  speed: 1000 KB/sec/disk.
  [1.247503]  md126: p1 p2 p3 p4
  [1.248269] md: using maximum available idle IO bandwidth (but not more 
than 20 KB/sec) for resync.
  [1.248774] md: using 128k window, over a total of 976759940k.

  Note that the pain of "resync upon every (re)boot" cannot even be a
  bit relieved thanks to bitmaps because mdadm does not support them for
  IMSM containers:

  $ sudo mdadm --grow --bitmap=internal /dev/md126
  mdadm: Cannot add bitmaps to sub-arrays yet

  I also get this in syslog during boot when the individual drives are
  detected, but this seems to be harmless:

  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/sbin/mdadm --incremental 
/dev/sdb --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[608]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/sbin/mdadm --incremental 
/dev/sda --offroot' failed with exit code 1.
  May 30 17:26:07 wssrv1 systemd-udevd[606]: Process '/lib/udev/hdparm' failed 
with exit code 1.

  During a resync, `sudo sh -c 'echo idle >
  /sys/block/md126/md/sync_action'` actually stops it as expected, but
  it restarts immediately though nothing seems to have triggered it:

  May 30 18:17:02 wssrv1 kernel: [ 3106.826710] md: md126: resync interrupted.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836320] md: checkpointing resync of 
md126.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836623] md: resync of RAID array md126
  May 30 18:17:02 wssrv1 kernel: [ 3106.836625] md: minimum _guaranteed_  
speed: 1000 KB/sec/disk.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836626] md: using maximum available 
idle IO bandwidth (but not more than 20 KB/sec) for resync.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836627] md: using 128k window, over a 
total of 976759940k.
  May 30 18:17:02 wssrv1 kernel: [ 3106.836628] md: resuming resync of md126 
from checkpoint.
  May 30 18:17:02 wssrv1 mdadm[982]: RebuildStarted event detected on md device 
/dev/md/Volume0

  I attach screenshots of the hanging shutdown log after a `sudo sh -c 'echo 8 
> /proc/sys/kernel/printk'`. The second screenshot shows that the kernel has 
deadlocked in md_write_start(). Note that `sudo systemctl start debug-shell` is 
unusable on this machine at this point because Ctrl+Alt+F9 brings tty9 without 
any keyboard.
  [EDIT]But I can still switch back to tty1.[/EDIT]

  I have also tried with much lower values for vm.dirty_background_ratio
  and vm.dirty_ratio,

[Touch-packages] [Bug 1862386] Re: package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in package vim-tiny 2:7.4

2020-02-07 Thread dprai

PDFCROP 1.38, 2012/11/02 - Copyright (c) 2002-2012 by Heiko Oberdiek.

kpathsea: Running mktexfmt pdftex.fmt
mktexfmt: mktexfmt is using the following fmtutil.cnf files (in precedence 
order):
mktexfmt:   /usr/share/texmf/web2c/fmtutil.cnf
mktexfmt: mktexfmt is using the following fmtutil.cnf file for writing changes:
mktexfmt:   /home/dprai/.texmf-config/web2c/fmtutil.cnf
mktexfmt [INFO]: writing formats under /home/dprai/.texmf-var/web2c
mktexfmt [INFO]: did not find entry for byfmt=pdftex, skipped
mktexfmt [INFO]: Not selected formats: 2
mktexfmt [INFO]: Total formats: 2
mktexfmt [INFO]: exiting with status 0
!!! Error: pdfTeX run failed with value 1!

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

Title:
  package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade:
  trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also
  in package vim-tiny 2:7.4.1689-3ubuntu1.3

Status in vim package in Ubuntu:
  New

Bug description:
  PDFCROP 1.38, 2012/11/02 - Copyright (c) 2002-2012 by Heiko Oberdiek.

  kpathsea: Running mktexfmt pdftex.fmt
  mktexfmt: mktexfmt is using the following fmtutil.cnf files (in precedence 
order):
  mktexfmt:   /usr/share/texmf/web2c/fmtutil.cnf
  mktexfmt: mktexfmt is using the following fmtutil.cnf file for writing 
changes:
  mktexfmt:   /home/dprai/.texmf-config/web2c/fmtutil.cnf
  mktexfmt [INFO]: writing formats under /home/dprai/.texmf-var/web2c
  mktexfmt [INFO]: did not find entry for byfmt=pdftex, skipped
  mktexfmt [INFO]: Not selected formats: 2
  mktexfmt [INFO]: Total formats: 2
  mktexfmt [INFO]: exiting with status 0
  !!! Error: pdfTeX run failed with value 1!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: vim-runtime 2:7.4.1689-3ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Fri Feb  7 21:24:31 2020
  DpkgHistoryLog:
   Start-Date: 2020-02-07  21:24:30
   Commandline: apt-get -f install
   Requested-By: dprai (1000)
   Upgrade: vim-runtime:amd64 (2:7.4.1689-3ubuntu1.2, 2:7.4.1689-3ubuntu1.3)
  DpkgTerminalLog:
   Preparing to unpack .../vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb ...
   Unpacking vim-runtime (2:7.4.1689-3ubuntu1.3) over (2:7.4.1689-3ubuntu1.2) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb (--unpack):
trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in 
package vim-tiny 2:7.4.1689-3ubuntu1.3
  DuplicateSignature:
   package:vim-runtime:2:7.4.1689-3ubuntu1.2
   Unpacking vim-runtime (2:7.4.1689-3ubuntu1.3) over (2:7.4.1689-3ubuntu1.2) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb (--unpack):
trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in 
package vim-tiny 2:7.4.1689-3ubuntu1.3
  ErrorMessage: trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which 
is also in package vim-tiny 2:7.4.1689-3ubuntu1.3
  InstallationDate: Installed on 2018-12-24 (410 days ago)
  InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 
(20180731)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: vim
  Title: package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: 
trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in 
package vim-tiny 2:7.4.1689-3ubuntu1.3
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1862386] [NEW] package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in package vim-tiny 2:7

2020-02-07 Thread dprai

Public bug reported:

PDFCROP 1.38, 2012/11/02 - Copyright (c) 2002-2012 by Heiko Oberdiek.

kpathsea: Running mktexfmt pdftex.fmt
mktexfmt: mktexfmt is using the following fmtutil.cnf files (in precedence 
order):
mktexfmt:   /usr/share/texmf/web2c/fmtutil.cnf
mktexfmt: mktexfmt is using the following fmtutil.cnf file for writing changes:
mktexfmt:   /home/dprai/.texmf-config/web2c/fmtutil.cnf
mktexfmt [INFO]: writing formats under /home/dprai/.texmf-var/web2c
mktexfmt [INFO]: did not find entry for byfmt=pdftex, skipped
mktexfmt [INFO]: Not selected formats: 2
mktexfmt [INFO]: Total formats: 2
mktexfmt [INFO]: exiting with status 0
!!! Error: pdfTeX run failed with value 1!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: vim-runtime 2:7.4.1689-3ubuntu1.2
ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
Date: Fri Feb  7 21:24:31 2020
DpkgHistoryLog:
 Start-Date: 2020-02-07  21:24:30
 Commandline: apt-get -f install
 Requested-By: dprai (1000)
 Upgrade: vim-runtime:amd64 (2:7.4.1689-3ubuntu1.2, 2:7.4.1689-3ubuntu1.3)
DpkgTerminalLog:
 Preparing to unpack .../vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb ...
 Unpacking vim-runtime (2:7.4.1689-3ubuntu1.3) over (2:7.4.1689-3ubuntu1.2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb (--unpack):
  trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in 
package vim-tiny 2:7.4.1689-3ubuntu1.3
DuplicateSignature:
 package:vim-runtime:2:7.4.1689-3ubuntu1.2
 Unpacking vim-runtime (2:7.4.1689-3ubuntu1.3) over (2:7.4.1689-3ubuntu1.2) ...
 dpkg: error processing archive 
/var/cache/apt/archives/vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb (--unpack):
  trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in 
package vim-tiny 2:7.4.1689-3ubuntu1.3
ErrorMessage: trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is 
also in package vim-tiny 2:7.4.1689-3ubuntu1.3
InstallationDate: Installed on 2018-12-24 (410 days ago)
InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: vim
Title: package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade: 
trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in 
package vim-tiny 2:7.4.1689-3ubuntu1.3
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package package-conflict xenial

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

Title:
  package vim-runtime 2:7.4.1689-3ubuntu1.2 failed to install/upgrade:
  trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also
  in package vim-tiny 2:7.4.1689-3ubuntu1.3

Status in vim package in Ubuntu:
  New

Bug description:
  PDFCROP 1.38, 2012/11/02 - Copyright (c) 2002-2012 by Heiko Oberdiek.

  kpathsea: Running mktexfmt pdftex.fmt
  mktexfmt: mktexfmt is using the following fmtutil.cnf files (in precedence 
order):
  mktexfmt:   /usr/share/texmf/web2c/fmtutil.cnf
  mktexfmt: mktexfmt is using the following fmtutil.cnf file for writing 
changes:
  mktexfmt:   /home/dprai/.texmf-config/web2c/fmtutil.cnf
  mktexfmt [INFO]: writing formats under /home/dprai/.texmf-var/web2c
  mktexfmt [INFO]: did not find entry for byfmt=pdftex, skipped
  mktexfmt [INFO]: Not selected formats: 2
  mktexfmt [INFO]: Total formats: 2
  mktexfmt [INFO]: exiting with status 0
  !!! Error: pdfTeX run failed with value 1!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: vim-runtime 2:7.4.1689-3ubuntu1.2
  ProcVersionSignature: Ubuntu 4.15.0-50.54~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-50-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Fri Feb  7 21:24:31 2020
  DpkgHistoryLog:
   Start-Date: 2020-02-07  21:24:30
   Commandline: apt-get -f install
   Requested-By: dprai (1000)
   Upgrade: vim-runtime:amd64 (2:7.4.1689-3ubuntu1.2, 2:7.4.1689-3ubuntu1.3)
  DpkgTerminalLog:
   Preparing to unpack .../vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb ...
   Unpacking vim-runtime (2:7.4.1689-3ubuntu1.3) over (2:7.4.1689-3ubuntu1.2) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb (--unpack):
trying to overwrite '/usr/share/vim/vim74/doc/help.txt', which is also in 
package vim-tiny 2:7.4.1689-3ubuntu1.3
  DuplicateSignature:
   package:vim-runtime:2:7.4.1689-3ubuntu1.2
   Unpacking vim-runtime (2:7.4.1689-3ubuntu1.3) over (2:7.4.1689-3ubuntu1.2) 
...
   dpkg: error processing archive 
/var/cache/apt/archives/vim-runtime_2%3a7.4.1689-3ubuntu1.3_all.deb (--unpack):
trying to overwrite

[Touch-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

I checked with 20.04 and it appears that recent Ubuntu live CDs don't
have boot=casper anymore; they do still have initrd=/casper/initrd; but
anyway, ^/cow should be fine (sorry I hadn't noticed the ^ there
before).

Thank you for your work in this.

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

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Touch-packages] [Bug 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1

2020-02-07 Thread Richard Anthony Horan

The kernel parameter "snd-hda-intel.model=dual-codecs" has no effect.

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

Title:
  Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted
  Front speakers 5.1

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

Bug description:
  Ubuntu 18.04.3 LTS
  Kernel 5.5.0
  pulseaudio:
Installed: 1:11.1-1ubuntu7.4
  X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound.

  I have surround 5.1 speakers and the Front Left and Right are Muted.  
  I have to unmute Headphones in alsamixer to hear sound from the front left 
and right speakers is the workaround.

  This step should not be required for speakers 5.1 to work.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard2533 F pulseaudio
   /dev/snd/controlC1:  richard2533 F pulseaudio
   /dev/snd/controlC0:  richard2533 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on 
vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-28-generic N/A
   linux-backports-modules-5.3.0-28-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1825515] Re: Looping login cycle when trying to login to Ubuntu-Gnome (both X and Wayland). But logs in to Ubuntu with Budgie desktop okay.

2020-02-07 Thread Balint Reczey

Do you still observe the issue on 19.10 or later?
I'm reassigning to a package more related to the potential bug.

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

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

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

Title:
  Looping login cycle when trying to login to Ubuntu-Gnome (both X and
  Wayland). But logs in to Ubuntu with Budgie desktop okay.

Status in gnome-shell package in Ubuntu:
  Incomplete

Bug description:
  Bug started immediately after upgrading to Ubuntu 19.04. Have tried
  all the suggested work-arounds I can find on the web but none of them
  has any effect on the problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: login 1:4.5-1.1ubuntu2
  ProcVersionSignature: Ubuntu 4.18.0-17.18-generic 4.18.20
  Uname: Linux 4.18.0-17-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Fri Apr 19 22:39:45 2019
  InstallationDate: Installed on 2018-10-22 (179 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to disco on 2019-04-18 (1 days ago)

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

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

[Touch-packages] [Bug 1822501] Re: chpasswd mishandles --root option

2020-02-07 Thread Balint Reczey

** Changed in: shadow (Ubuntu)
   Importance: Undecided => Low

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

Title:
  chpasswd mishandles --root option

Status in shadow package in Ubuntu:
  New

Bug description:
  I did

echo root:secret | chpasswd --root=/mnt/img

  I expected the password to be changed on the mounted filesystem at /mnt/img
  Instead, it changed the password on the host filesystem.

  Although the chpasswd(1) manual page does not list --root=CHROOT_DIR
  as valid syntax, it is common for programs to accept both --arg param
  and --arg=param as valid syntax (as per gnu getopt_long).  At the very
  least, chpasswd should fail with an error report if unacceptable
  option syntax is used, rather than ignoring it.

  passwd 1:4.5-1ubuntu1 on Ubuntu 18.04.2 LTS

  (though bug tracker seems to think this does not exist in Ubuntu)

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

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

[Touch-packages] [Bug 1862377] [NEW] WXtoimg

2020-02-07 Thread Cees de Melker

Public bug reported:

No information

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
Uname: Linux 4.16.8-xanmod9 x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Fri Feb  7 16:11:25 2020
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: I just need to know a workaround
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:13c7]
InstallationDate: Installed on 2019-08-19 (171 days ago)
InstallationMedia: Skywave Linux 3.1.1 - Release amd64 (20180606)
MachineType: ASUSTeK Computer Inc. K54L
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.8-xanmod9 
root=UUID=4fd4c874-6312-499d-b5b8-a0d6f67182bc ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K54L.208
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K54L
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: ATN12345678901234567
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54L.208:bd09/26/2011:svnASUSTeKComputerInc.:pnK54L:pvr1.0:rvnASUSTeKComputerInc.:rnK54L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.family: K
dmi.product.name: K54L
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.92+git1805251830.c1f2d9~oibaf~x
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1806011930.f00fcf~oibaf~x
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1806011930.f00fcf~oibaf~x
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.8
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:18.0.1+git1805221933.65c9df~oibaf~x
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.15+git1805201934.ac8f7b~oibaf~x
xserver.bootTime: Fri Feb  7 16:04:35 2020
xserver.configfile: default
xserver.errors:
 Failed to load module "intel" (module does not exist, 0)
 Failed to load module "intel" (module does not exist, 0)
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: modeset

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


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

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

Title:
  WXtoimg

Status in xorg package in Ubuntu:
  New

Bug description:
  No information

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  Uname: Linux 4.16.8-xanmod9 x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Fri Feb  7 16:11:25 2020
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:13c7]
  InstallationDate: Installed on 2019-08-19 (171 days ago)
  InstallationMedia: Skywave Linux 3.1.1 - Release amd64 (20180606)
  MachineType: ASUSTeK Computer Inc. K54L
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.16.8-xanmod9 
root=UUID=4fd4c874-6312-499d-b5b8-a0d6f67182bc ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/26/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: K54L.208
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: K54L
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK54L.208:bd09/26/2011:svnASUSTeKComputerInc.:pnK54L:pvr1.0:rvnASUSTeKComputerInc.:rnK54L:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
  dmi.product.family: K
  dmi.product.name: K54L

[Touch-packages] [Bug 1862378] [NEW] libsystemd-shared broken in Multi-Arch

2020-02-07 Thread dann frazier

Public bug reported:

I noticed that systemd-machined was failing to start on an arm64 box.
This box had armhf enabled, and turns out systemd had been cross-graded
over to systemd:armhf[*]. It still had systemd-container:arm64
installed, so now I had an arm64 /lib/systemd/systemd-machine, but an
armhf /lib/systemd/libsystemd-shared-244.so.

libsystemd-shared-244.so is from the systemd package. Since systemd is
marked Multi-Arch: foreign, systemd:armhf was able to incorrectly
satisfy systemd-container:arm64's dependency on systemd.

[*] kudos to Multi-Arch that I simply hadn't noticed

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

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

Title:
  libsystemd-shared broken in Multi-Arch

Status in systemd package in Ubuntu:
  New

Bug description:
  I noticed that systemd-machined was failing to start on an arm64 box.
  This box had armhf enabled, and turns out systemd had been cross-
  graded over to systemd:armhf[*]. It still had systemd-container:arm64
  installed, so now I had an arm64 /lib/systemd/systemd-machine, but an
  armhf /lib/systemd/libsystemd-shared-244.so.

  libsystemd-shared-244.so is from the systemd package. Since systemd is
  marked Multi-Arch: foreign, systemd:armhf was able to incorrectly
  satisfy systemd-container:arm64's dependency on systemd.

  [*] kudos to Multi-Arch that I simply hadn't noticed

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

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

[Touch-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

On 2020-02-07 13:41, Alkis Georgopoulos wrote:
> The "grep cow" approach breaks the LTSP package and other software
> that uses a COW root.

Do those packages cause the file system /cow, listed by the df command,
to be mounted? If yes, I wouldn't mind to modify the debdiff. Please let
me know.

> To check for casper, please `grep -w boot=casper /proc/cmdline` or
> something casper-specific.

Thanks for the tip!

> In schools, we sometimes have students of various nationalities.
> They're not frequent enough to install whole langpacks for them, but
> they are frequent enough to configure locales for them (locale-gen).

It's unclear to me why it's more difficult to install language packs
than generating locales separately.

In any case, I would prefer to consider this aspect to be beyond the
scope of this bug report.

> Of course it's your call.

Yes. :)

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

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Touch-packages] [Bug 1410558] Re: ps doesn't support "thcount" format specifier on Xenial

** Merge proposal linked:
   
https://code.launchpad.net/~halves/ubuntu/+source/procps/+git/procps/+merge/378736

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

Title:
  ps doesn't support "thcount" format specifier on Xenial

Status in procps package in Ubuntu:
  Fix Released
Status in procps source package in Xenial:
  In Progress

Bug description:
  [Impact]
  ps -o thcount doesn't print out an error (error: unknown user-defined format 
specifier "thcount")

  [Description]
  The Xenial version of procps has a bug in the thcount format specifier. ps 
doesn't recognize it, and complains about an unknown user-defined format.
  This is due to the format specifier table in ps/output.c, which is queried 
with a binary search. Since the "thcount" entry appears out of order in Xenial, 
it can't be looked up and the program fails with the "unknown user-defined 
format specifier" error.

  This has been fixed upstream by the commit below:
  - Fix for Bug:1174313 (3a52dfa34027)

  $ git describe --contains 3a52dfa34027
  v3.3.12~58^2

  $ rmadison procps
   procps | 2:3.3.10-4ubuntu2   | xenial  | source, ...
   procps | 2:3.3.10-4ubuntu2.4 | xenial-security | source, ...
   procps | 2:3.3.10-4ubuntu2.4 | xenial-updates  | source, ... <
   procps | 2:3.3.12-3ubuntu1   | bionic  | source, ...
   procps | 2:3.3.12-3ubuntu1.1 | bionic-security | source, ...
   procps | 2:3.3.12-3ubuntu1.2 | bionic-updates  | source, ...

  Releases starting with Bionic already have this fix, so it's only
  needed for Xenial.

  [Test case]
  1. Boot up a Xenial environment with e.g. an lxd container:
  # lxc launch images:ubuntu/xenial xenial

  2. Execute ps with the '-o thcount' options:
  # lxc exec xenial -- ps -o thcount
  error: unknown user-defined format specifier "thcount"

  Usage:
   ps [options]

   Try 'ps --help '
or 'ps --help '
   for additional help text.

  For more details see ps(1).

  [Regression Potential]
  The fix just fixes the order of two entries in the format specifier array, so 
the regression potential is very low. Furthermore, the patch has been present 
and tested in up-to-date versions of procps since Bionic. Any new regressions 
introduced in Xenial will be checked with autopkgtest.

  [Original Description]
  In Ubuntu 12.04.5 LTS (procps 1:3.2.8-11ubuntu6.3), the following worked fine:

  $ export PS_FORMAT=thcount
  $ ps
  THCNT
  1
  1

  In Ubuntu 14.04.1 LTS (procps 1:3.3.9-1ubuntu2), it does not work
  anymore:

  $ export PS_FORMAT=thcount
  $ ps
  warning: $PS_FORMAT ignored. (unknown user-defined format specifier "thcount")
    PID TTY  TIME CMD
   6593 pts/100:00:00 ps
  16633 pts/100:00:00 bash

  Other PS_FORMAT specifiers still work fine (I have tried many, but not
  all).

  In real-life usage, a more complex PS_FORMAT would of course be used,
  such as
  
PS_FORMAT=pid,s,thcount,nice,euser,egroup,etime,cputime,%mem,rssize:6,size:7,vsize:7,command

  Workaround: use nlwp instead of thcount (they are alias to the same
  data, and nlwp works fine in both versions).

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

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

[Touch-packages] [Bug 1859829] Re: server will not boot after updating lvm2 package

2020-02-07 Thread Pablo SEMINARIO

Hi,

Same issue here, after a system upgrade today my computer was not able
to boot anymore. On my

It was stuck with the following message:

WARNING: Failed to connect to lvmetad. Falling back to device scanning.
Volume group "ubuntu-vg" not found Cannot process volume group ubuntu-vg

As workaround I downgraded the package from a chroot mount via an USB
key running:

apt-get install lvm2=2.02.176-4.1ubuntu3
liblvm2app2.2=2.02.176-4.1ubuntu3 liblvm2cmd2.02=2.02.176-4.1ubuntu3

and it was able to boot again.

Here's the output of /var/log/dpkg.log:

2020-02-07 12:20:00 upgrade liblvm2cmd2.02:amd64 2.02.176-4.1ubuntu3.18.04.1 
2.02.176-4.1ubuntu3.18.04.2
2020-02-07 12:20:20 upgrade liblvm2app2.2:amd64 2.02.176-4.1ubuntu3.18.04.1 
2.02.176-4.1ubuntu3.18.04.2
2020-02-07 12:20:36 upgrade lvm2:amd64 2.02.176-4.1ubuntu3.18.04.1 
2.02.176-4.1ubuntu3.18.04.2

2020-02-07 15:07:06 upgrade liblvm2app2.2:amd64 2.02.176-4.1ubuntu3.18.04.2 
2.02.176-4.1ubuntu3
2020-02-07 15:07:07 upgrade liblvm2cmd2.02:amd64 2.02.176-4.1ubuntu3.18.04.2 
2.02.176-4.1ubuntu3
2020-02-07 15:07:07 upgrade lvm2:amd64 2.02.176-4.1ubuntu3.18.04.2 
2.02.176-4.1ubuntu3

Please don't hesitate to ask for more details.

Best,

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

Title:
  server will not boot after updating lvm2 package

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  After updating lvm2 from 2.02.176-4.1ubuntu3.18.04.1 to
  2.02.176-4.1ubuntu3.18.04.2, server will not boot.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

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

  3) What you expected to happen
  I expect the server to boot.

  4) What happened instead
  The server hangs at boot.

  As the server will not boot, I can not provide any logs.  I can only
  provide a screen captures of the boot failure messages.

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

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

[Touch-packages] [Bug 1859829] Re: server will not boot after updating lvm2 package

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

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

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

Title:
  server will not boot after updating lvm2 package

Status in lvm2 package in Ubuntu:
  Confirmed

Bug description:
  After updating lvm2 from 2.02.176-4.1ubuntu3.18.04.1 to
  2.02.176-4.1ubuntu3.18.04.2, server will not boot.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

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

  3) What you expected to happen
  I expect the server to boot.

  4) What happened instead
  The server hangs at boot.

  As the server will not boot, I can not provide any logs.  I can only
  provide a screen captures of the boot failure messages.

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

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

[Touch-packages] [Bug 1815101] Re: [master] Restarting systemd-networkd breaks keepalived, heartbeat, corosync, pacemaker (interface aliases are restarted)

2020-02-07 Thread David Negreira

Can we backport the fixes to 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/1815101

Title:
  [master] Restarting systemd-networkd breaks keepalived, heartbeat,
  corosync, pacemaker (interface aliases are restarted)

Status in Keepalived Charm:
  New
Status in netplan:
  Confirmed
Status in heartbeat package in Ubuntu:
  Won't Fix
Status in keepalived package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  In Progress
Status in keepalived source package in Bionic:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed
Status in keepalived source package in Disco:
  Won't Fix
Status in systemd source package in Disco:
  Won't Fix
Status in keepalived source package in Eoan:
  In Progress
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [impact]

  - ALL related HA software has a small problem if interfaces are being
  managed by systemd-networkd: nic restarts/reconfigs are always going
  to wipe all interfaces aliases when HA software is not expecting it to
  (no coordination between them.

  - keepalived, smb ctdb, pacemaker, all suffer from this. Pacemaker is
  smarter in this case because it has a service monitor that will
  restart the virtual IP resource, in affected node & nic, before
  considering a real failure, but other HA service might consider a real
  failure when it is not.

  [test case]

  - comment #14 is a full test case: to have 3 node pacemaker, in that
  example, and cause a networkd service restart: it will trigger a
  failure for the virtual IP resource monitor.

  - other example is given in the original description for keepalived.
  both suffer from the same issue (and other HA softwares as well).

  [regression potential]

  - this backports KeepConfiguration parameter, which adds some
  significant complexity to networkd's configuration and behavior, which
  could lead to regressions in correctly configuring the network at
  networkd start, or incorrectly maintaining configuration at networkd
  restart, or losing network state at networkd stop.

  - Any regressions are most likely to occur during networkd start,
  restart, or stop, and most likely to involve missing or incorrect ip
  address(es).

  - the change is based in upstream patches adding the exact feature we
  needed to fix this issue & it will be integrated with a netplan change
  to add the needed stanza to systemd nic configuration file
  (KeepConfiguration=)

  [other info]

  original description:
  ---

  Configure netplan for interfaces, for example (a working config with
  IP addresses obfuscated)

  network:
  ethernets:
  eth0:
  addresses: [192.168.0.5/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth2:
  addresses:
    - 12.13.14.18/29
    - 12.13.14.19/29
  gateway4: 12.13.14.17
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth3:
  addresses: [10.22.11.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth4:
  addresses: [10.22.14.6/24]
  dhcp4: false
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  eth7:
  addresses: [9.5.17.34/29]
  dhcp4: false
  optional: true
  nameservers:
    search: [blah.com, other.blah.com, hq.blah.com, cust.blah.com, 
phone.blah.com]
    addresses: [10.22.11.1]
  version: 2

  Configure keepalived (again, a working config with IP addresses
  obfuscated)

  global_defs   # Block id
  {
  notification_email {
  sysadm...@blah.com
  }
  notification_email_from keepali...@system3.hq.blah.com
  smtp_server 10.22.11.7 # IP
  smtp_connect_timeout 30  # integer, seconds
  router_id system3  # string identifying the machine,
   # (doesn't have to be hostname).
  vrrp_mcast_group4 224.0.0.18 # optional, default 224.0.0.18
  vrrp_mcast_group6 ff02::12   # optional, default ff02::12
  enable_traps # enable SNMP traps
  }
  vrrp_sync_group collection {
  group {
  wan
  lan
  phone
  }
  vrrp_instance wan {
  state MASTER

[Touch-packages] [Bug 1862232] Re: Long hostname causes networking setup to fail

2020-02-07 Thread Dan Streetman

** Description changed:

+ [impact]
+ 
+ networkd fails to bring up networking on systems with long hostname
+ 
+ [test case]
+ 
+ setting the hostname:
+ 
+ $ sudo hostnamectl set-hostname
+ asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf
+ 
+ then reboot and check the networking.
+ 
+ [regression potential]
+ 
+ TBD
+ 
+ [scope]
+ 
+ This is reproducable only on Bionic.
+ 
+ [other info]
+ 
+ original description:
+ ---
+ 
+ 
  1) ubuntu version
  # lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04
  
  2) package version
  # apt-cache policy systemd
  systemd:
-   Installed: 237-3ubuntu10.31
-   Candidate: 237-3ubuntu10.31
-   Version table:
-  *** 237-3ubuntu10.31 500
- 500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packag
+   Installed: 237-3ubuntu10.31
+   Candidate: 237-3ubuntu10.31
+   Version table:
+  *** 237-3ubuntu10.31 500
+ 500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packag
  es
- 100 /var/lib/dpkg/status
-  237-3ubuntu10.29 500
- 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages 
-  237-3ubuntu10 500
- 500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages 

+ 100 /var/lib/dpkg/status
+  237-3ubuntu10.29 500
+ 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages
+  237-3ubuntu10 500
+ 500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages
  
- 
- 3) I expect the network to come online correctly regardless of how long the 
hostname is. This is what happens with both 14.0 and 19.0 (I tested the same 
behavior with both of them).
+ 3) I expect the network to come online correctly regardless of how long
+ the hostname is. This is what happens with both 14.0 and 19.0 (I tested
+ the same behavior with both of them).
  
  4) the external network interface fails to be configured and is stuck in
  a (pending) state as reported by networkctl status -a
  
  setting the hostname:
  
  # hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf
  
  after rebooting the machine, it no longer has network access.
  
  # journalctl
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: 
Starting Wait for Network to be Configured...
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: Link state is up-to-date
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: found matching network 
'/run/systemd/network/10-netplan-eth0.network'
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: sd-netlink: callback failed: Invalid argument
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: lo: Link state is up-to-date
  
  # networkctl status -a:
  ● 1: lo
-Link File: /lib/systemd/network/99-default.link
- Network File: n/a
- Type: loopback
-State: carrier (unmanaged)
-  Address: 127.0.0.1
-   ::1
+    Link File: /lib/systemd/network/99-default.link
+ Network File: n/a
+ Type: loopback
+    State: carrier (unmanaged)
+  Address: 127.0.0.1
+   ::1
  
  ● 2: eth0
-Link File: /run/systemd/network/10-netplan-eth0.link
- Network File: /run/systemd/network/10-netplan-eth0.network
- Type: ether
-State: off (pending)
- Path: pci-:00:03.0
-   Driver: virtio_net
-   Vendor: Red Hat, Inc.
-Model: Virtio network device
-   HW Address: ae:4d:91:1c:e8:86
-  DNS: 67.207.67.3
-   67.207.67.2
+    Link File: /run/systemd/network/10-netplan-eth0.link
+ Network File: /run/systemd/network/10-netplan-eth0.network
+ Type: ether
+    State: off (pending)
+ Path: pci-:00:03.0
+   Driver: virtio_net
+   Vendor: Red Hat, Inc.
+    Model: Virtio network device
+   HW Address: ae:4d:91:1c:e8:86
+  DNS: 67.207.67.3
+   67.207.67.2
  
  and to bring up the network correctly, set the hostname to something
  shorter
  
  # hostnamectl set-hostname asdf
  # systemctl restart systemd-networkd
  # networkctl status -a
  ● 1: lo
-Link File: /lib/systemd/network/99-default.link
- Network File: n/a
- Type: loopback
-State: carrier (unmanaged)
-  Address: 127.0.0.1
-   ::1
+    Link File: /lib/systemd/network/99-default.link
+ Network File: n/a
+ Type: loopback
+    State: carrier (unmanaged)
+  Address: 127.0.0.1
+   ::1
  
  ● 2: eth0
-Link File:

[Touch-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected

Done: https://bugzilla.kernel.org/show_bug.cgi?id=206457

** Bug watch added: Linux Kernel Bug Tracker #206457
   https://bugzilla.kernel.org/show_bug.cgi?id=206457

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

Title:
  Dualshock4 controller doesn't stay connected

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

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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

[Touch-packages] [Bug 1861451] Re: apport's cloud-init-specific handling tracebacks on minimal cloud images

2020-02-07 Thread Francis Ginther

** Tags added: id-5e3c4d71dc61a969457f7c09

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

Title:
  apport's cloud-init-specific handling tracebacks on minimal cloud
  images

Status in apport package in Ubuntu:
  New
Status in apport source package in Focal:
  New

Bug description:
  Steps to reproduce:

  1) Install multipass.
  2) `multipass launch 
http://cloud-images.ubuntu.com/minimal/daily/bionic/current/bionic-minimal-cloudimg-amd64.img
 -n reproducer`
  3) `multipass shell reproducer`
  4) `ubuntu-bug cloud-init`

  Expected behaviour:

  Usual bug reporting flow (though, currently, I would really expect to
  see just the issue reported in bug 1861450).

  Actual behaviour:

  ERROR: hook /usr/share/apport/package-hooks/cloud-init.py crashed:
  Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/apport/report.py", line 198, in 
_run_hook
  symb['add_info'](report, ui)
File "/usr/share/apport/package-hooks/cloud-init.py", line 6, in add_info
  return cloudinit_add_info(report, ui)
File "/usr/lib/python3/dist-packages/cloudinit/apport.py", line 123, in 
add_info
  attach_cloud_init_logs(report, ui)
File "/usr/lib/python3/dist-packages/cloudinit/apport.py", line 57, in 
attach_cloud_init_logs
  'cloud-init-output.log.txt': 'cat /var/log/cloud-init-output.log'})
File "/usr/lib/python3/dist-packages/apport/hookutils.py", line 444, in 
attach_root_command_outputs
  sp = subprocess.Popen(_root_command_prefix() + [wrapper_path, 
script_path])
File "/usr/lib/python3.6/subprocess.py", line 729, in __init__
  restore_signals, start_new_session)
File "/usr/lib/python3.6/subprocess.py", line 1364, in _execute_child
  raise child_exception_type(errno_num, err_msg, err_filename)
  FileNotFoundError: [Errno 2] No such file or directory: 'pkexec': 'pkexec'

  (As alluded to above, this also demonstrates bug 1861450 after the
  traceback is emitted.)

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

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

[Touch-packages] [Bug 1861446] Re: on focal 'ubuntu-bug linux' doesn't automatically collect kernel artifacts

2020-02-07 Thread Francis Ginther

** Tags added: id-5e3c4e30994bdb87508721cc

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

Title:
  on focal 'ubuntu-bug linux' doesn't automatically collect kernel
  artifacts

Status in apport package in Ubuntu:
  New
Status in linux package in Ubuntu:
  Confirmed
Status in apport source package in Focal:
  New
Status in linux source package in Focal:
  Confirmed

Bug description:
  Hello, on focal I ran 'ubuntu-bug linux' to report a kernel issue. The
  issue was filed against linux-signed-5.4 (Ubuntu) rather than linux
  (Ubuntu), and none of the logs usually included with kernel bug
  reports were included.

  After the bug was changed from linux-signed-5.4 to linux, I was
  prompted to run apport-collect by the kernel team's triagebot and that
  worked successfully:

  https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861359/+activity

  My guess is that apport needs to be updated to understand a change in
  kernel packaging.

  Thanks

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: apport 2.20.11-0ubuntu16
  ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8
  Uname: Linux 5.4.0-12-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportLog:
   
  ApportVersion: 2.20.11-0ubuntu16
  Architecture: amd64
  CrashReports:
   640:1000:1000:40192:2020-01-30 03:32:41.717296496 +:2020-01-30 
03:32:41.717296496 +:/var/crash/_usr_bin_apport-bug.1000.crash
   600:0:0:467987:2020-01-24 20:40:35.855434497 +:2020-01-24 
20:40:35.819434494 +:/var/crash/zfsutils-linux.0.crash
   640:0:0:386063:2020-01-24 20:42:09.391725398 +:2020-01-24 
20:42:08.887728256 +:/var/crash/_usr_sbin_zfs.0.crash
  Date: Thu Jan 30 18:44:47 2020
  PackageArchitecture: all
  ProcEnviron:
   TERM=rxvt-unicode-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago)

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

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

[Touch-packages] [Bug 1862232] Re: Long hostname causes networking setup to fail

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

Title:
  Long hostname causes networking setup to fail

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  1) ubuntu version
  # lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

  2) package version
  # apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.31
Candidate: 237-3ubuntu10.31
Version table:
   *** 237-3ubuntu10.31 500
  500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packag
  es
  100 /var/lib/dpkg/status
   237-3ubuntu10.29 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages 
   237-3ubuntu10 500
  500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages 


  
  3) I expect the network to come online correctly regardless of how long the 
hostname is. This is what happens with both 14.0 and 19.0 (I tested the same 
behavior with both of them).

  4) the external network interface fails to be configured and is stuck
  in a (pending) state as reported by networkctl status -a

  setting the hostname:

  # hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  after rebooting the machine, it no longer has network access.

  # journalctl
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: 
Starting Wait for Network to be Configured...
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: Link state is up-to-date
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: found matching network 
'/run/systemd/network/10-netplan-eth0.network'
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: sd-netlink: callback failed: Invalid argument
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: lo: Link state is up-to-date

  # networkctl status -a:
  ● 1: lo
 Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
 State: carrier (unmanaged)
   Address: 127.0.0.1
::1

  ● 2: eth0
 Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
 State: off (pending)
  Path: pci-:00:03.0
Driver: virtio_net
Vendor: Red Hat, Inc.
 Model: Virtio network device
HW Address: ae:4d:91:1c:e8:86
   DNS: 67.207.67.3
67.207.67.2

  and to bring up the network correctly, set the hostname to something
  shorter

  # hostnamectl set-hostname asdf
  # systemctl restart systemd-networkd
  # networkctl status -a
  ● 1: lo
 Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
 State: carrier (unmanaged)
   Address: 127.0.0.1
::1

  ● 2: eth0
 Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
 State: routable (configured)
  Path: pci-:00:03.0
Driver: virtio_net
Vendor: Red Hat, Inc.
 Model: Virtio network device
HW Address: ae:4d:91:1c:e8:86
   Address: 10.17.0.5
157.245.210.250
fe80::ac4d:91ff:fe1c:e886
   Gateway: 157.245.208.1 (ICANN, IANA Department)
   DNS: 67.207.67.3
67.207.67.2

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

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

[Touch-packages] [Bug 1862232] Re: Long hostname causes networking setup to fail

2020-02-07 Thread Dan Streetman

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

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

** Changed in: systemd (Ubuntu Bionic)
   Importance: Undecided => Medium

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  Long hostname causes networking setup to fail

Status in systemd package in Ubuntu:
  Confirmed
Status in systemd source package in Bionic:
  Confirmed

Bug description:
  1) ubuntu version
  # lsb_release -rd
  Description:Ubuntu 18.04.3 LTS
  Release:18.04

  2) package version
  # apt-cache policy systemd
  systemd:
Installed: 237-3ubuntu10.31
Candidate: 237-3ubuntu10.31
Version table:
   *** 237-3ubuntu10.31 500
  500 http://mirrors.digitalocean.com/ubuntu bionic-updates/main amd64 
Packag
  es
  100 /var/lib/dpkg/status
   237-3ubuntu10.29 500
  500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 
Packages 
   237-3ubuntu10 500
  500 http://mirrors.digitalocean.com/ubuntu bionic/main amd64 Packages 


  
  3) I expect the network to come online correctly regardless of how long the 
hostname is. This is what happens with both 14.0 and 19.0 (I tested the same 
behavior with both of them).

  4) the external network interface fails to be configured and is stuck
  in a (pending) state as reported by networkctl status -a

  setting the hostname:

  # hostnamectl set-hostname
  asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf

  after rebooting the machine, it no longer has network access.

  # journalctl
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf systemd[1]: 
Starting Wait for Network to be Configured...
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: Link state is up-to-date
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: eth0: found matching network 
'/run/systemd/network/10-netplan-eth0.network'
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: sd-netlink: callback failed: Invalid argument
  Feb 06 19:29:41 
asdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdfasdf 
systemd-networkd[605]: lo: Link state is up-to-date

  # networkctl status -a:
  ● 1: lo
 Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
 State: carrier (unmanaged)
   Address: 127.0.0.1
::1

  ● 2: eth0
 Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
 State: off (pending)
  Path: pci-:00:03.0
Driver: virtio_net
Vendor: Red Hat, Inc.
 Model: Virtio network device
HW Address: ae:4d:91:1c:e8:86
   DNS: 67.207.67.3
67.207.67.2

  and to bring up the network correctly, set the hostname to something
  shorter

  # hostnamectl set-hostname asdf
  # systemctl restart systemd-networkd
  # networkctl status -a
  ● 1: lo
 Link File: /lib/systemd/network/99-default.link
  Network File: n/a
  Type: loopback
 State: carrier (unmanaged)
   Address: 127.0.0.1
::1

  ● 2: eth0
 Link File: /run/systemd/network/10-netplan-eth0.link
  Network File: /run/systemd/network/10-netplan-eth0.network
  Type: ether
 State: routable (configured)
  Path: pci-:00:03.0
Driver: virtio_net
Vendor: Red Hat, Inc.
 Model: Virtio network device
HW Address: ae:4d:91:1c:e8:86
   Address: 10.17.0.5
157.245.210.250
fe80::ac4d:91ff:fe1c:e886
   Gateway: 157.245.208.1 (ICANN, IANA Department)
   DNS: 67.207.67.3
67.207.67.2

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

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

[Touch-packages] [Bug 1862162] Re: Badly working video mode on the greeter

2020-02-07 Thread Jarno Suni

** Description changed:

  In the video mode there are moving stripes on the screen and monitor
  turns off occasionally. (Maybe this is just bad behaving monitor, an old
  Samsung TV) It became got good after I run
  
  xrandr --output HDMI-1 --mode 1920x1080
  
  (and --auto for each other video output) in /usr/local/bin/monitor-
  config.sh and I put
  
  display-setup-script=/usr/local/bin/monitor-config.sh
  
- in lightdm configuration, except that screens partly overlap even if the
+ in LightDM configuration, except that screens partly overlap even if the
  other monitor is right of other. Couldn't they be mirroring each other?
+ Anyway, I can make it work decently as extended desktop if I use --left-
+ of or --right-of.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Feb  6 13:35:12 2020
  InstallationDate: Installed on 2019-12-05 (62 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  LightdmConfig:
   [Seat:*]
   display-setup-script=/usr/local/bin/monitor-config.sh
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Badly working video mode on the greeter

Status in lightdm package in Ubuntu:
  New

Bug description:
  In the video mode there are moving stripes on the screen and monitor
  turns off occasionally. (Maybe this is just bad behaving monitor, an
  old Samsung TV) It became got good after I run

  xrandr --output HDMI-1 --mode 1920x1080

  (and --auto for each other video output) in /usr/local/bin/monitor-
  config.sh and I put

  display-setup-script=/usr/local/bin/monitor-config.sh

  in LightDM configuration, except that screens partly overlap even if
  the other monitor is right of other. Couldn't they be mirroring each
  other? Anyway, I can make it work decently as extended desktop if I
  use --left-of or --right-of.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Feb  6 13:35:12 2020
  InstallationDate: Installed on 2019-12-05 (62 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  LightdmConfig:
   [Seat:*]
   display-setup-script=/usr/local/bin/monitor-config.sh
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1862162] Re: Badly working video mode on the greeter

2020-02-07 Thread Jarno Suni

** Description changed:

  In the video mode there are moving stripes on the screen and monitor
- turns off occasionally. (Maybe this is bad behaving monitor, an old
- Samsung TV) It got good after I run
+ turns off occasionally. (Maybe this is just bad behaving monitor, an old
+ Samsung TV) It became got good after I run
  
- xrandr --output HDMI-1 --auto
+ xrandr --output HDMI-1 --mode 1920x1080
  
- (and similar for each other video output) in /usr/local/bin/monitor-
+ (and --auto for each other video output) in /usr/local/bin/monitor-
  config.sh and I put
  
  display-setup-script=/usr/local/bin/monitor-config.sh
  
- in lightdm configuration.
+ in lightdm configuration, except that screens partly overlap even if the
+ other monitor is right of other. Couldn't they be mirroring each other?
  
  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Feb  6 13:35:12 2020
  InstallationDate: Installed on 2019-12-05 (62 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  LightdmConfig:
-  [Seat:*]
-  display-setup-script=/usr/local/bin/monitor-config.sh
+  [Seat:*]
+  display-setup-script=/usr/local/bin/monitor-config.sh
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Badly working video mode on the greeter

Status in lightdm package in Ubuntu:
  New

Bug description:
  In the video mode there are moving stripes on the screen and monitor
  turns off occasionally. (Maybe this is just bad behaving monitor, an
  old Samsung TV) It became got good after I run

  xrandr --output HDMI-1 --mode 1920x1080

  (and --auto for each other video output) in /usr/local/bin/monitor-
  config.sh and I put

  display-setup-script=/usr/local/bin/monitor-config.sh

  in LightDM configuration, except that screens partly overlap even if
  the other monitor is right of other. Couldn't they be mirroring each
  other? Anyway, I can make it work decently as extended desktop if I
  use --left-of or --right-of.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: lightdm 1.30.0-0ubuntu1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Feb  6 13:35:12 2020
  InstallationDate: Installed on 2019-12-05 (62 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  LightdmConfig:
   [Seat:*]
   display-setup-script=/usr/local/bin/monitor-config.sh
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected

Please file an upstream bug at https://bugzilla.kernel.org/
Product: Drivers
Component: Bluetooth

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

Title:
  Dualshock4 controller doesn't stay connected

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

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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

[Touch-packages] [Bug 1853768] Re: Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show them as normal document icon under Yaru theme

2020-02-07 Thread Dmitry Shachnev

In Focal this is now fixed in yaru-theme 20.04.1.

** No longer affects: qtbase-opensource-src (Ubuntu)

** Also affects: yaru-theme (Ubuntu Eoan)
   Importance: Undecided
   Status: New

** Changed in: yaru-theme (Ubuntu)
   Status: Confirmed => Fix Released

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

Title:
  Qt apps, like kid3-qt, which uses legacy icons "document-*.png", show
  them as normal document icon under Yaru theme

Status in Yaru Theme:
  Fix Released
Status in yaru-theme package in Ubuntu:
  Fix Released
Status in yaru-theme source package in Eoan:
  New

Bug description:
  Qt apps, like kid3-qt, which uses these legacy icons:

  document-open.png
  document-open-recent.png
  document-save.png
  document-save-as.png
  document-revert.png
  document-import.png
  document-export.png

  The icons are all shown as the same normal document icon under Yaru.

  Qt apps only have a problem with legacy icons starting with
  "document-*" and all other legacy icons are inherited from Humanity
  under Yaru.

  Is there a general solution to force Qt apps to choose the closest
  icon name from Yaru or Humanity?

  Should this bug be issued against upstream Qt?

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

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

[Touch-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices

2020-02-07 Thread joes

Can confirm the same behaviour. Using LE-Bose QC35 II on Ubuntu 18.04.4
LTS.

Switching to A2DP stops the "Call from.." prompts on the headphones but
it also then deselects it as an input device. (I think this is correct
for A2DP).

Selecting HSP/HFP or going back and selecting Bose QC35 II as an input
device (which has the effect of selecting HSP/HFP) means the "Call
from.." prompt comes back.

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

Title:
  Annoying "call from" message when connecting Bose devices

Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each
  time I initially connect to listen to an audio or video, I hear an
  annoying "Call from" on my headset. My headset seems to think a
  connection to a phone call is taking place. This is annoying because
  the audio will start to play and after a little while the "call from"
  voice talks over the audio.

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

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

[Touch-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

I commented before I saw the previous reply; I'll reply to that now.

The "grep cow" approach breaks the LTSP package and other software that uses a 
COW root.
To check for casper, please `grep -w boot=casper /proc/cmdline` or something 
casper-specific.

In schools, we sometimes have students of various nationalities. They're
not frequent enough to install whole langpacks for them, but they are
frequent enough to configure locales for them (locale-gen).

I do not see any reason to keep the Ubuntu-specific
04_language_handling.patch, when we know that it's causing issues and we
do not know its benefit. Of course it's your call. :)

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

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Touch-packages] [Bug 1860548] Re: systemd crashes when logging long message

2020-02-07 Thread Ioanna Alifieraki

RE-VERIFICATION ON BIONIC

Installed systemd from -proposed :
# dpkg -l | grep systemd
ii  libnss-systemd:amd64  237-3ubuntu10.39  
  amd64nss module providing dynamic user and group name 
resolution
ii  libpam-systemd:amd64  237-3ubuntu10.39  
  amd64system and service manager - PAM module
ii  libsystemd0:amd64 237-3ubuntu10.39  
  amd64systemd utility library
ii  python3-systemd   234-1build1   
  amd64Python 3 bindings for systemd
ii  systemd   237-3ubuntu10.39  
  amd64system and service manager
ii  systemd-sysv  237-3ubuntu10.39  
  amd64system and service manager - SysV links

Following the reproducer described in the [Test Case] section of the bug
description :

# systemd-run --scope apt-get -q -y -o DPkg::Options::=--force-confold -o 
DPkg::Options::=--force-confdef --allow-unauthenticated install acl adduser 
amd64-microcode apt base-files base-passwd bash bash-completion bind9-host 
binfmt-support binutils-common binutils-x86-64-linux-gnu bsdmainutils bsdutils 
busybox-initramfs busybox-static bzip2 ca-certificates console-setup 
console-setup-linux coreutils cpio cpp cpp-7 crda cron curl dash dbus 
dctrl-tools debconf debconf-i18n debianutils dictionaries-common diffutils 
dirmngr distro-info-data dmeventd dmsetup dnsmasq-base dnsutils dpkg e2fslibs 
e2fsprogs ed eject fakeroot fdisk file findutils friendly-recovery gawk 
gcc-7-base gcc-8-base gettext-base gir1.2-glib-2.0 gnupg gnupg-l10n gnupg-utils 
gpg gpg-agent gpg-wks-client gpg-wks-server gpgconf gpgsm gpgv grep groff-base 
grub-common grub-pc grub-pc-bin grub2-common gzip hostname info init 
init-system-helpers initramfs-tools initramfs-tools-bin initramfs-tools-core 
install-info intel-microcode iproute2 iptables iputils-ping iputils-tracepath 
irqbalance isc-dhcp-client isc-dhcp-common iso-codes iw keyboard-configuration 
keyutils klibc-utils kmod krb5-locales krb5-user language-pack-en 
language-pack-en-base language-pack-gnome-en language-pack-gnome-en-base less 
libaccountsservice0 libacl1 libapparmor1 libargon2-0 libasan4 libasn1-8-heimdal 
libassuan0 libatm1 libatomic1 libattr1 libaudit-common libaudit1 libbinutils 
libblkid1 libbsd0 libbz2-1.0 libc-bin libc-dev-bin libc6 libc6-dev libcap-ng0 
libcap2 libcap2-bin libcc1-0 libcilkrts5 libcom-err2 libcryptsetup12 
libcurl3-gnutls libcurl4 libdb5.3 libdbus-1-3 libdebconfclient0 
libdevmapper-event1.02.1 libdevmapper1.02.1 libdpkg-perl libdrm-common libdrm2 
libdumbnet1 libedit2 libelf1 libestr0 libevent-2.1-6 libexpat1 libexpat1-dev 
libext2fs2 libfakeroot libfastjson4 libfdisk1 libffi6 libfreetype6 libfribidi0 
libfuse2 libgc1c2 libgcc-7-dev libgcc1 libgcrypt20 libgdbm-compat4 libgeoip1 
libgirepository-1.0-1 libglib2.0-0 libglib2.0-data libgmp10 libgnutls30 
libgomp1 libgpg-error0 libgpm2 libgssapi-krb5-2 libgssapi3-heimdal libgssrpc4 
libhcrypto4-heimdal libheimbase1-heimdal libheimntlm0-heimdal libhogweed4 
libhx509-5-heimdal libitm1 libjs-jquery libjs-sphinxdoc libjs-underscore 
libk5crypto3 libkadm5clnt-mit11 libkadm5srv-mit11 libkdb5-9 libkeyutils1 
libkmod2 libkrb5-26-heimdal libkrb5-3 libkrb5support0 libksba8 libldap-2.4-2 
libldap-common liblocale-gettext-perl liblsan0 liblz4-1 liblzma5 libmagic-mgc 
libmagic1 libmnl0 libmount1 libmpc3 libmpdec2 libmpfr6 libmpx2 libmspack0 
libncurses5 libncursesw5 libnetfilter-conntrack3 libnettle6 libnewt0.52 
libnfnetlink0 libnfsidmap2 libnghttp2-14 libnl-3-200 libnl-genl-3-200 libnorm1 
libnpth0 libnss-systemd libnuma1 libp11-kit0 libpam-cap libpam-krb5 
libpam-modules libpam-modules-bin libpam-runtime libpam-systemd libpam0g 
libparted2 libpcap0.8 libpci3 libpcre3 libpgm-5.2-0 libpipeline1 libplymouth4 
libpng16-16 libpolkit-gobject-1-0 libpopt0 libpsl5 libpython-all-dev 
libpython-dev libpython-stdlib libpython2.7 libpython2.7-dev 
libpython2.7-minimal


Command terminates successfully without aborting.


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

Title:
  systemd crashes when logging long message

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Disco:
  Fix Released
Status in systemd source package in Eoan:
  Fix Released

Bug description:
  [Impact]

  Systemd crashes when logging very long messages. This regression was 
introduced with
  upstream commit d054f0a4d451 [1] due to xsprintf.
  Commits e68eedbbdc98 [2] and 574432f889ce [3]

[Touch-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected

I have tried the daily iso and the same things happens. Same error
message as well.

If anybody else is reading this bug report and has the dualshock4 model
CUH-ZCTU2 please try to pair it and post here the result.

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

Title:
  Dualshock4 controller doesn't stay connected

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

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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

[Touch-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

Btw, lightdm doesn't set LANGUAGE at all in Debian; it only sets LANG,
like GDM, and everything works fine.

Gunnar, do you see any issues with just completely dropping your 
04_language_handling.patch?
Or at least this line there:

+session_set_env (session, "LANGUAGE", language);

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

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  In Progress

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Touch-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

Not sure why you would want to uninstall the language packs for a
language you have configured. You are not supposed to do that. Please
use "Language Support" to manage your languages.

This special thing in LightDM is there for a reason (even if I don't
remember the reason exactly). I'm not ready to propose something which
might have adverse side effects.

Attached please find a debdiff which I think fixes it in live sessions.
The real test can be done only after the new version of lightdm has
reached the daily build ISOs. Would appreciate your confirmation when
that happens.

** Patch added: "lightdm_lp1861481.debdiff"

https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1861481/+attachment/5326214/+files/lightdm_lp1861481.debdiff

** Changed in: lightdm (Ubuntu)
Importance: Undecided => Medium

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

** Changed in: lightdm (Ubuntu)
Assignee: (unassigned) => Gunnar Hjalmarsson (gunnarhj)

** Tags added: patch

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

Title:
language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
Confirmed
Status in lightdm package in Ubuntu:
In Progress

Bug description:
Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
MATE and Xubuntu), if a user selects a language in syslinux other than
those with an included langpack, the session is then untranslated.

For example, if one boots Ubuntu MATE 20.04 and selects Greek in
syslinux, he ends up with LANGUAGE=en in the session.

The chain of events is:
LightDM has an Ubuntu-specific patch that makes it call
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
`locale -a` does list el_GR as a supported locale because casper correctly
updated the locales.
But language-options doesn't list el_GR, so it fools LightDM into thinking
that Greek aren't supported; while they're all there, since e.g. MATE doesn't
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

I believe the correct fix would be for language-options to list el_GR
on live CDs (to merge the output of locale -a in its output).

Thanks!

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

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

[Touch-packages] [Bug 1862344] [NEW] Please switch from python-windowmocker to python3-windowmocker

2020-02-07 Thread Dmitry Shachnev

Public bug reported:

The dependency of python3-autopilot-tests should be updated from python-
windowmocker to python3-windowmocker.

In the code, window-mocker should be probably replaced with window-
mocker3, as python3-windowmocker ships /usr/bin/window-mocker3.

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

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

Title:
  Please switch from python-windowmocker to python3-windowmocker

Status in autopilot package in Ubuntu:
  New

Bug description:
  The dependency of python3-autopilot-tests should be updated from
  python-windowmocker to python3-windowmocker.

  In the code, window-mocker should be probably replaced with window-
  mocker3, as python3-windowmocker ships /usr/bin/window-mocker3.

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

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

[Touch-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected

I am waiting for the daily-iso to be downloaded but I suspect it will
not solve the issue because I have already tried with the current kernel
(5.5+) without success. Same issue. So unless this doesn't only involve
the kernel I don't think that the daily iso will make any difference.

Is there any way I can provide more info about this bug?

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

Title:
  Dualshock4 controller doesn't stay connected

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

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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

[Touch-packages] [Bug 1861345] Re: Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted Front speakers 5.1

Can you please try kernel parameter "snd-hda-intel.model=dual-codecs"?

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

Title:
  Gigabyte x570 Aorus Master with ALC1220 and ESS SABRE 9118 DAC Muted
  Front speakers 5.1

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

Bug description:
  Ubuntu 18.04.3 LTS
  Kernel 5.5.0
  pulseaudio:
Installed: 1:11.1-1ubuntu7.4
  X570 Aorus Master Motherboard. ALC1220 ESS Sabre sound.

  I have surround 5.1 speakers and the Front Left and Right are Muted.  
  I have to unmute Headphones in alsamixer to hear sound from the front left 
and right speakers is the workaround.

  This step should not be required for speakers 5.1 to work.
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.9-0ubuntu7.9
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC2:  richard2533 F pulseaudio
   /dev/snd/controlC1:  richard2533 F pulseaudio
   /dev/snd/controlC0:  richard2533 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2020-01-28 (2 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  MachineType: Gigabyte Technology Co., Ltd. X570 AORUS MASTER
  Package: linux (not installed)
  ProcFB:
   
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-28-generic 
root=UUID=51fe9653-53b0-475f-836e-a1662c6d8b79 ro quiet splash amd_iommu=on 
vt.handoff=1
  ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-28-generic N/A
   linux-backports-modules-5.3.0-28-generic  N/A
   linux-firmware1.173.14
  Tags:  bionic
  Uname: Linux 5.3.0-28-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip kvm libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 12/06/2019
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F11
  dmi.board.asset.tag: Default string
  dmi.board.name: X570 AORUS MASTER
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: Default string
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF11:bd12/06/2019:svnGigabyteTechnologyCo.,Ltd.:pnX570AORUSMASTER:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnX570AORUSMASTER:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: Default string
  dmi.product.name: X570 AORUS MASTER
  dmi.product.sku: Default string
  dmi.product.version: -CF
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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

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

[Touch-packages] [Bug 1861289] Re: No virtual terminals and NAutoVTs=6 setting ineffective

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

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

Title:
  No virtual terminals and NAutoVTs=6 setting ineffective

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  This is not the same bug as #1758512 - that bug is about an
  unresponsive key combination, this bug is reproducible without
  pressing any key-combination.

  Reproduce:

  Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by
  uncommenting this:

  [Login]
  NAutoVTs=6
  ReserveVT=6

  According to man logind.conf  this would result 6 virtual terminals
  spawned.

  
  Bug behaviour:

  Reboot and run

  $ sudo fgconsole --next-available
  3

  Expected:

Given I've configured 6 auto virtual terminals this number should be
  higher than 6.

  Bug behaviour

  Reboot and run:
  $ sudo chvt 3

  Got a screen with a black background and a single blinking cursor at
  upper left corner

  Expected:

Seeing a login prompt
  --- 
  ProblemType: Bug
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  weiwu  1703 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  DistroRelease: Ubuntu 19.10
  InstallationDate: Installed on 2019-06-11 (232 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: LENOVO 20KHS1BP00
  Package: linux (not installed)
  ProcFB: 0 i915drmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
  RelatedPackageVersions:
   linux-restricted-modules-5.3.0-26-generic N/A
   linux-backports-modules-5.3.0-26-generic  N/A
   linux-firmware1.183.3
  Tags:  eoan
  Uname: Linux 5.3.0-26-generic x86_64
  UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago)
  UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo
  _MarkForUpload: True
  dmi.bios.date: 06/25/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N23ET50W (1.25 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20KHS1BP00
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 6th
  dmi.product.name: 20KHS1BP00
  dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
  dmi.product.version: ThinkPad X1 Carbon 6th
  dmi.sys.vendor: LENOVO

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

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

[Touch-packages] [Bug 1861289] [NEW] No virtual terminals and NAutoVTs=6 setting ineffective

You have been subscribed to a public bug:

This is not the same bug as #1758512 - that bug is about an unresponsive
key combination, this bug is reproducible without pressing any key-
combination.

Reproduce:

Using Ubuntu 19.10. Manually modified /etc/systemd/logind.conf by
uncommenting this:

[Login]
NAutoVTs=6
ReserveVT=6

According to man logind.conf  this would result 6 virtual terminals
spawned.


Bug behaviour:

Reboot and run

$ sudo fgconsole --next-available
3

Expected:

  Given I've configured 6 auto virtual terminals this number should be
higher than 6.

Bug behaviour

Reboot and run:
$ sudo chvt 3

Got a screen with a black background and a single blinking cursor at
upper left corner

Expected:

  Seeing a login prompt
--- 
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.2
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  weiwu  1703 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2019-06-11 (232 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: LENOVO 20KHS1BP00
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic 
root=UUID=b9df6bda-4eaa-4420-9573-12ab02da707d ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13
RelatedPackageVersions:
 linux-restricted-modules-5.3.0-26-generic N/A
 linux-backports-modules-5.3.0-26-generic  N/A
 linux-firmware1.183.3
Tags:  eoan
Uname: Linux 5.3.0-26-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-11-15 (75 days ago)
UserGroups: adm cdrom dialout dip lp lpadmin plugdev sambashare staff sudo
_MarkForUpload: True
dmi.bios.date: 06/25/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N23ET50W (1.25 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20KHS1BP00
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN23ET50W(1.25):bd06/25/2018:svnLENOVO:pn20KHS1BP00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHS1BP00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad X1 Carbon 6th
dmi.product.name: 20KHS1BP00
dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th
dmi.product.version: ThinkPad X1 Carbon 6th
dmi.sys.vendor: LENOVO

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


** Tags: apport-collected eoan
-- 
No virtual terminals and NAutoVTs=6 setting ineffective
https://bugs.launchpad.net/bugs/1861289
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to systemd in Ubuntu.

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

[Touch-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected

Please try latest daily iso:
http://cdimages.ubuntu.com/daily-live/current/

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

Title:
  Dualshock4 controller doesn't stay connected

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

Bug description:
  Pairing the Dualshock4 controller works somehow, after several
  attempts. I expected this to work out of the box but it does not work
  well at all.

  Once the pairing is completed, if I try to connect it it doesn't stay
  connected.

  I have checked the dmesg and apparently there is a buffer overflow
  somewhere.

  I can pair a bluetooth headset to my laptop and the Dualshock4 pairs
  with my samsung tablet without problems but when I try to pair the
  dualshock4 to the laptop, running Ubuntu 19.10, it does not work.

  Dmesg output:

  
  [4.099796] Bluetooth: Core ver 2.22
  [4.099833] Bluetooth: HCI device and connection manager initialized
  [4.099837] Bluetooth: HCI socket layer initialized
  [4.099839] Bluetooth: L2CAP socket layer initialized
  [4.099842] Bluetooth: SCO socket layer initialized
  [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018
  [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
  [6.855413] Bluetooth: BNEP filters: protocol multicast
  [6.855416] Bluetooth: BNEP socket layer initialized
  [   14.234706] Bluetooth: RFCOMM TTY layer initialized
  [   14.234711] Bluetooth: RFCOMM socket layer initialized
  [   14.234715] Bluetooth: RFCOMM ver 1.11
  [  117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow


  
  Release: 
  Description:  Ubuntu 19.10
  Release:  19.10

  
  Package Info:
  bluez:
Installed: 5.50-0ubuntu4
Candidate: 5.50-0ubuntu4
Version table:
   *** 5.50-0ubuntu4 500
  500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: bluez 5.50-0ubuntu4
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Jan 28 14:11:19 2020
  InstallationDate: Installed on 2019-11-26 (62 days ago)
  InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 
(20190805)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: LENOVO 20FCS33A00
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic 
root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago)
  dmi.bios.date: 03/13/2019
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1FET68W (1.42 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20FCS33A00
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Defined
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad X1 Carbon 4th
  dmi.product.name: 20FCS33A00
  dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th
  dmi.product.version: ThinkPad X1 Carbon 4th
  dmi.sys.vendor: LENOVO
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: E4:A7:A0:C6:7F:AE  ACL MTU: 1021:4  SCO MTU: 96:6
UP RUNNING PSCAN 
RX bytes:8289 acl:41 sco:0 events:268 errors:0
TX bytes:9494 acl:44 sco:0 commands:163 errors:0
  syslog:

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

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

[Touch-packages] [Bug 1862157] Re: dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles

2020-02-07 Thread Christian Ehrhardt 

Thank you for taking the time to report this bug and helping to make
Ubuntu better. I appreciate the quality of this bug report and I'm sure
it'll be helpful to others to find this discussion if they are
experiencing the same issue.

This sounds like an upstream bug to me. I have checked the latest
upstream and there isn't a new option around that topic available that
Ubuntu could add.

The best route to getting it fixed in Ubuntu in this case would be to
file an upstream bug if you're able to do that. Otherwise, I'm not sure
what we can do directly in Ubuntu to fix the problem.

If you do end up filing an upstream bug/discussion, please link to it
from here. Thanks!

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

Title:
  dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  dnsmasq does in all cases prepend "tftp_root" to tftp-files.

  tftp-root=/data/tftp
  dhcp-boot=grub/i386-pc/core.0

  now have some config files for different subnets:
  dhcp-boot=net:172-18-1,grub/i386-pc/core.0,172.18.1.1
  dhcp-boot=net:172-18-8,pxelinux.0,172.18.8.1
  dhcp-boot=net:172-18-7,/var/lib/tftpboot/pxelinux.0,spacewalk-ber.bfs.de

  Now booting clients within subnet 172.18.1.0/24 will boot grub with:
  /data/tftp/grub/i386-pc/core.0

  Booting clients within subnet 172.18.2.0/24 will boot pxelinux.0 with:
  /data/tftp/pxelinux.0

  And in subnet 172.18.7.0/24 clients will boot with:
  /data/tftp/var/lib/tftpboot/pxelinux.0

  and return a "File not found" error.

  I'd expected:
  172.18.1: grub/i386-pc/core.0   (file found within /data/tftp -- 
without exposing path)
  172.18.2: pxelinux.0(file found within /data/tftp -- 
without exposing path)
  172.18.3: /pxelinux.0   (file found within /)
  172.18.7: /var/lib/tftpboot/pxelinux.0  (file found within 
/var/lib/tftpboot/pxelinux.0)

  or even better: some way to set tftp-root for every subnet-config and
  having only relative paths to access files regardless of giving
  absolute or relative paths.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18
  Uname: Linux 4.15.0-87-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  Date: Thu Feb  6 11:43:07 2020
  InstallationDate: Installed on 2014-01-31 (2197 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to bionic on 2018-11-23 (439 days ago)
  mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595
  mtime.conffile..etc.dnsmasq.conf: 2016-08-17T12:18:41.225353

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

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

[Touch-packages] [Bug 1862157] Re: dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles

2020-02-07 Thread Christian Ehrhardt 

Hi Thomas,
as you already described yourself if you set in /etc/dnsmasq.conf
 tftp-root=/
then all paths you provide in per subnet config would work if each of them were 
added as absolute path.
This works as-is without any change to the package.

`tftp-root` is defined as:
--tftp-root=[,]
Look for files to transfer using TFTP relative to the given directory. When 
this is set, TFTP paths which include ".." are rejected, to stop clients  
getting  outside  the specified  root.   Absolute  paths (starting with /) are 
allowed, but they must be within the tftp-root. If the optional interface 
argument is given, the directory is only used for TFTP requests via that 
interface.

Your example violates the "paths starting with / ... must be within the
tftp-root" which is why it won't work. You could also just "not at all"
set `tftp-root` as it is mostly a security feature to not serve
something you'd never want to be served.

You can even do "per IP paths" in between with tftp-root + --tftp-
unique-root - see the manpage for more details.

If all those config options aren't enough this is more a feature request
to dnsmasq than a bug in Ubuntu. Go to [1] for that if you like to do
so.

[1]: http://lists.thekelleys.org.uk/mailman/listinfo/dnsmasq-discuss

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

Title:
  dnsmasq does in all cases prepend "tftp_root" to tftp-bootfiles

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  dnsmasq does in all cases prepend "tftp_root" to tftp-files.

  tftp-root=/data/tftp
  dhcp-boot=grub/i386-pc/core.0

  now have some config files for different subnets:
  dhcp-boot=net:172-18-1,grub/i386-pc/core.0,172.18.1.1
  dhcp-boot=net:172-18-8,pxelinux.0,172.18.8.1
  dhcp-boot=net:172-18-7,/var/lib/tftpboot/pxelinux.0,spacewalk-ber.bfs.de

  Now booting clients within subnet 172.18.1.0/24 will boot grub with:
  /data/tftp/grub/i386-pc/core.0

  Booting clients within subnet 172.18.2.0/24 will boot pxelinux.0 with:
  /data/tftp/pxelinux.0

  And in subnet 172.18.7.0/24 clients will boot with:
  /data/tftp/var/lib/tftpboot/pxelinux.0

  and return a "File not found" error.

  I'd expected:
  172.18.1: grub/i386-pc/core.0   (file found within /data/tftp -- 
without exposing path)
  172.18.2: pxelinux.0(file found within /data/tftp -- 
without exposing path)
  172.18.3: /pxelinux.0   (file found within /)
  172.18.7: /var/lib/tftpboot/pxelinux.0  (file found within 
/var/lib/tftpboot/pxelinux.0)

  or even better: some way to set tftp-root for every subnet-config and
  having only relative paths to access files regardless of giving
  absolute or relative paths.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: dnsmasq 2.79-1
  ProcVersionSignature: Ubuntu 4.15.0-87.87-generic 4.15.18
  Uname: Linux 4.15.0-87-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.10
  Architecture: amd64
  Date: Thu Feb  6 11:43:07 2020
  InstallationDate: Installed on 2014-01-31 (2197 days ago)
  InstallationMedia: Ubuntu-Server 13.10 "Saucy Salamander" - Release amd64 
(20131016)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  SourcePackage: dnsmasq
  UpgradeStatus: Upgraded to bionic on 2018-11-23 (439 days ago)
  mtime.conffile..etc.default.dnsmasq: 2014-02-19T17:19:28.429595
  mtime.conffile..etc.dnsmasq.conf: 2016-08-17T12:18:41.225353

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

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

[Touch-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

2020-02-07 Thread Maciej Borzecki

Nonetheless it isn't clear whether it's a snapd problem or the actual
libraries. Switching to confirmed in snapd, but needs investigation from
desktop team too.

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

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  New
Status in gnome-themes-extra package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions

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

[Touch-packages] [Bug 1861558] Re: Snap 'ed applicaitons have garbage on top of the window Close [x] button

2020-02-07 Thread Maciej Borzecki

I've seen this happen occasionally with snaps on Arch too.

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

Title:
  Snap 'ed applicaitons have garbage on top of the window Close [x]
  button

Status in adwaita-icon-theme package in Ubuntu:
  New
Status in gnome-themes-extra package in Ubuntu:
  New
Status in humanity-icon-theme package in Ubuntu:
  New
Status in snapd package in Ubuntu:
  Confirmed
Status in ubuntu-mono package in Ubuntu:
  New

Bug description:
  Steps to reproduce:
  1. Have Ubuntu 19.10 installed
  2. Install GNOME application as a Snap - for example with

  sudo snap install gedit gnome-calculator

  3. Open GNOME Tweaks -> Appearance tab, then switch Icon set to the
  one of the following:

  * Adwaita
  * DMZ-Black
  * DMZ-White
  * hicolor
  * HighContrast
  * Humanity
  * Humanity-Dark
  * LoginIcons

  For example - Adwaita theme with Adwaita icon set.

  4. Open GNOME Calculator as a Snap application:

 /snap/bin/gnome-calculator

  Expected result:

  * GNOME Calculator looks as any other GTK application

  Actual result:

  * GNOME Calculator has garbage on top of the window Close [x] button

  ---

  Notes: 
  1. Problem was first seen on AskUbuntu - https://askubuntu.com/q/1206868
  2. one can use the script below to check all possible Theme<->Icon 
combinations:

  ```
  #!/bin/bash

  DISPLAY=:0

  for t in $(ls -1 /usr/share/themes/)
  do 
for i in $(ls -1 /usr/share/icons/)
do

  echo -e "\nTheme: $t, Icons: $i\n"

gsettings set org.gnome.desktop.interface gtk-theme "$t"
gsettings set org.gnome.desktop.interface icon-theme "$i"

  /snap/bin/gnome-calculator

#read -r -s -p "Press  for next theme"   
done
  done

  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: snapd 2.41+19.10.1
  ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13
  Uname: Linux 5.3.0-29-generic x86_64
  ApportVersion: 2.20.11-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Feb  1 17:55:09 2020
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: snapd
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/adwaita-icon-theme/+bug/1861558/+subscriptions

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

[Touch-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated

I mean that if, on a normal 20.04 installation, I uninstall the el langpack, 
then
1) If I'm using GDM, universe apps show Greek,
2) If I'm using LightDM, universe apps show English (this one regressed in 
19.10).

If we're modifying LightDM, I suggest to modify LightDM to not set LANGUAGE at 
all, not just in live CDs.
This is what GDM does and it works fine everywhere.

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

Title:
  language-options causes live CD sessions to be untranslated

Status in accountsservice package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  New

Bug description:
  Since Ubuntu 19.10, for all Ubuntu live CDs that use LightDM (e.g.
  MATE and Xubuntu), if a user selects a language in syslinux other than
  those with an included langpack, the session is then untranslated.

  For example, if one boots Ubuntu MATE 20.04 and selects Greek in
  syslinux, he ends up with LANGUAGE=en in the session.

  The chain of events is:
  LightDM has an Ubuntu-specific patch that makes it call 
/usr/share/language-tools/language-options instead of the upstream `locale -a`.
  `locale -a` does list el_GR as a supported locale because casper correctly 
updated the locales.
  But language-options doesn't list el_GR, so it fools LightDM into thinking 
that Greek aren't supported; while they're all there, since e.g. MATE doesn't 
rely on langpacks; mate-panel.mo and mate-calc.mo etc are all there.

  I believe the correct fix would be for language-options to list el_GR
  on live CDs (to merge the output of locale -a in its output).

  Thanks!

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

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

[Touch-packages] [Bug 1861481] Re: language-options causes live CD sessions to be untranslated