[Touch-packages] [Bug 1370953] Re: layout switch is delayed

2019-06-08 Thread Alexey
Hello!

The problem is still here. In 17.10, 18.04, 18.10, 19.04 releases...

I found out that all standard layout switches are with that stupid delay. 
But somehow the alternative switching on LShift+RShift works instantly!

I spent few hours to find the place where this action is stored to move
it to standard keybindings like Shfit+Alt, but failed.

May be someone can suggest the way how to find action on key binding in
Ubuntu to do this?

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

Title:
  layout switch is delayed

Status in console-setup package in Ubuntu:
  Confirmed
Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  I have two layouts configured En and Ru with Ctrl-Shift as layout
  switch combo.

  When I start typing in wrong layout I notice it, hit Ctrl-Shift and type 
again, but more often than not it is wrong layout again.
  I repeat the action, but there is no luck. On the third attemt it usually 
either works OR the first letter is still in wrong layout, but the second is in 
correct one - i.e. layout switches as I type.

  The explanation for this is that layout switch takes very unreasonable
  time - much longer than it is needed to move your fingers from  one
  key to the other. Each time I encounter the error I retry slower so on
  the third attempt it is slow enough to actually recognize that layout
  switch is happening, but with a delay.

  This is extremely annoying and unacceptable. If someone knows how to
  work around it - please post your suggestions here. It would be nice
  to have a solution for 3+ layouts setup as well.

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

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


[Touch-packages] [Bug 1785629] Re: [MIR] gupnp-av

2019-06-08 Thread Launchpad Bug Tracker
[Expired for gupnp-av (Ubuntu) because there has been no activity for 60
days.]

** Changed in: gupnp-av (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  [MIR] gupnp-av

Status in gupnp-av package in Ubuntu:
  Expired

Bug description:
  * Availability

  Builds on all supported architectures in Ubuntu and on sync from
  Debian

  * Rationale

  We would like to enable dlna sharing of media files, which is a GNOME
  upstream feature and relying on rygel which depends on the gupnp
  libraries, including the gupnp-dlna one

  * Security

  No CVE/known security issue

  * Quality assurance

  - the desktop-packages team is subscribed to the package
  - the bug lists in upstream, the Debian PTS and launchpad are empty
  - upstream has a testsuit which is not being used during build, we are going 
to look at changing that

  * Dependendies

  The package uses standard desktop libraries that are already in main
  (gstreamer, glib)

  * Standards compliance

  the package is using standard packaging (dh10), the standards-version
  is 3.9.8, the package is in sync from Debian

  * Maintainance

  Upstream is active and the desktop team is going to look after the
  package in ubuntu

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gupnp-av/+bug/1785629/+subscriptions

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


[Touch-packages] [Bug 1823573] Re: Bluetooth headset not available as output device

2019-06-08 Thread Launchpad Bug Tracker
[Expired for alsa-driver (Ubuntu) because there has been no activity for
60 days.]

** Changed in: alsa-driver (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  Bluetooth headset not available as output device

Status in alsa-driver package in Ubuntu:
  Expired

Bug description:
  Connecting my Bluetooth headset (Beoplay H8) appears to be working,
  and everything looks correct in the Bluetooth settings: However, the
  headset is not listed under "Output devices" in the sound menu after
  connecting, and all sounds are channeled through the built-in
  speakers.

  Media buttons on the headset are also rendered useless, not that there
  would be much use for them without sound anyways. Still worth noting,
  as everything including media buttons worked perfectly in 18.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu25
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  stein  2603 F pulseaudio
   /dev/snd/pcmC0D0c:   stein  2603 F...m pulseaudio
   /dev/snd/pcmC0D0p:   stein  2603 F...m pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr  7 23:00:38 2019
  InstallationDate: Installed on 2018-05-09 (332 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  PackageArchitecture: all
  ProcEnviron:
   LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=nb_NO.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Title: Bluetooth sound card not detected
  UpgradeStatus: Upgraded to disco on 2019-04-03 (4 days ago)
  dmi.bios.date: 10/14/2016
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 3PCN16WW(V2.00)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: Lenovo ideapad 510S-13IKB
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: NO Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo ideapad 510S-13IKB
  dmi.modalias: 
dmi:bvnLENOVO:bvr3PCN16WW(V2.00):bd10/14/2016:svnLENOVO:pn80V0:pvrLenovoideapad510S-13IKB:rvnLENOVO:rnLenovoideapad510S-13IKB:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoideapad510S-13IKB:
  dmi.product.family: IDEAPAD
  dmi.product.name: 80V0
  dmi.product.sku: LENOVO_MT_80V0_BU_idea_FM_Lenovo ideapad 510S-13IKB
  dmi.product.version: Lenovo ideapad 510S-13IKB
  dmi.sys.vendor: LENOVO

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

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


[Touch-packages] [Bug 458476] Re: /etc/init.d/ssh gives OK status even if daemon fails to launch

2019-06-08 Thread Luke A. Perkins
Did you check for the existence of the /run/sshd directory? Is
UsePrivilegeSeparation set to yes?

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

Title:
  /etc/init.d/ssh gives OK status even if daemon fails to launch

Status in lsb package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New

Bug description:
  Binary package hint: lsb

  lsb-base: /lib/lsb/init-functions appears to let the script
  /etc/init.d/ssh, from package openssh-server, continue with status OK
  even if the daemon fails to launch.

  I can run the script, but no sshd is launched:

  $ sudo /etc/init.d/ssh start
   * Starting OpenBSD Secure Shell server sshd  
[ OK ]
  $ pgrep -l sshd || echo Not There
  Not There

  If I launch sshd manually, it gives me a proper error message:
  sudo   /usr/sbin/sshd -Dd
  debug1: sshd version OpenSSH_5.1p1 Debian-6ubuntu1
  [snip]
  debug1: Bind to port 22 on 192.168.0.5.
  Bind to port 22 on 192.168.0.5 failed: Cannot assign requested address.

  I expect that in such a situation  /etc/init.d/ssh should show an error, 
something like this:
  $ sudo /etc/init.d/ssh start
   * Starting OpenBSD Secure Shell server sshd  
[ FAIL]
   Starting sshd failed : Bind to port 22 on 192.168.0.5 failed: Cannot assign 
requested address.

  $ apt-cache policy lsb-base
  lsb-base:
Installed: 4.0-0ubuntu5
Candidate: 4.0-0ubuntu5
Version table:
   *** 4.0-0ubuntu5 0
  500 http://fi.archive.ubuntu.com karmic/main Packages
  100 /var/lib/dpkg/status

  $  lsb_release -rd
  Description:Ubuntu 9.10
  Release:9.10

  If someone misconfigures the server and then uses /etc/init.d/ssh to
  restart the server.  They will get locked out (aka denial of service)
  if they did not plan carefully enough to test which processes are
  running, that's not something your average sysadmin should be expected
  to do.  The script should work...

  ProblemType: Bug
  Architecture: i386
  Date: Thu Oct 22 22:21:28 2009
  DistroRelease: Ubuntu 9.10
  Package: lsb-base 4.0-0ubuntu5
  PackageArchitecture: all
  ProcEnviron:
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   LANGUAGE=
  ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
  SourcePackage: lsb
  Uname: Linux 2.6.31-14-generic i686
  XsessionErrors: (polkit-gnome-authentication-agent-1:2635): GLib-CRITICAL **: 
g_once_init_leave: assertion `initialization_value != 0' failed

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

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


[Touch-packages] [Bug 1832111] Re: package systemd 237-3ubuntu10 failed to install/upgrade: unable to stat './var/lib/polkit-1/localauthority' (which I was about to install): Bad message

2019-06-08 Thread Ubuntu Foundations Team Bug Bot
Thank you for taking the time to report this bug and helping to make
Ubuntu better.  Reviewing your dmesg attachment in this bug report it
seems that there is a problem with your hardware.  I recommend
performing a back up and then investigating the situation.  Measures you
might take include checking cable connections and using software tools
to investigate the health of your hardware.  In the event that is is not
in fact an error with your hardware please set the bug's status back to
New.  Thanks and good luck!

[This is an automated message.  I apologize if it reached you
inappropriately; please just reply to this message indicating so.]

** Tags added: hardware-error

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

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

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

Title:
  package systemd 237-3ubuntu10 failed to install/upgrade: unable to
  stat './var/lib/polkit-1/localauthority' (which I was about to
  install): Bad message

Status in systemd package in Ubuntu:
  Invalid

Bug description:
  while rebooting it gui is not appearing only linux terminal is showing
  not resetting into graphical mode

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency i686
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: i386
  Date: Sun Jun  9 06:37:13 2019
  DuplicateSignature:
   package:systemd:237-3ubuntu10
   Unpacking systemd (237-3ubuntu10.21) over (237-3ubuntu10) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-FLSGvw/4-systemd_237-3ubuntu10.21_i386.deb (--unpack):
unable to stat './var/lib/polkit-1/localauthority' (which I was about to 
install): Bad message
  ErrorMessage: unable to stat './var/lib/polkit-1/localauthority' (which I was 
about to install): Bad message
  InstallationDate: Installed on 2019-06-09 (0 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f82399f9-2a5d-483d-8dc3-cb178026d113 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 237-3ubuntu10 failed to install/upgrade: unable to 
stat './var/lib/polkit-1/localauthority' (which I was about to install): Bad 
message
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH61HO
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG62445-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr:

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

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


[Touch-packages] [Bug 1832111] Re: package systemd 237-3ubuntu10 failed to install/upgrade: unable to stat './var/lib/polkit-1/localauthority' (which I was about to install): Bad message

2019-06-08 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 systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1832111

Title:
  package systemd 237-3ubuntu10 failed to install/upgrade: unable to
  stat './var/lib/polkit-1/localauthority' (which I was about to
  install): Bad message

Status in systemd package in Ubuntu:
  New

Bug description:
  while rebooting it gui is not appearing only linux terminal is showing
  not resetting into graphical mode

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency i686
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: i386
  Date: Sun Jun  9 06:37:13 2019
  DuplicateSignature:
   package:systemd:237-3ubuntu10
   Unpacking systemd (237-3ubuntu10.21) over (237-3ubuntu10) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-FLSGvw/4-systemd_237-3ubuntu10.21_i386.deb (--unpack):
unable to stat './var/lib/polkit-1/localauthority' (which I was about to 
install): Bad message
  ErrorMessage: unable to stat './var/lib/polkit-1/localauthority' (which I was 
about to install): Bad message
  InstallationDate: Installed on 2019-06-09 (0 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f82399f9-2a5d-483d-8dc3-cb178026d113 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 237-3ubuntu10 failed to install/upgrade: unable to 
stat './var/lib/polkit-1/localauthority' (which I was about to install): Bad 
message
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH61HO
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG62445-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr:

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

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


[Touch-packages] [Bug 1832111] [NEW] package systemd 237-3ubuntu10 failed to install/upgrade: unable to stat './var/lib/polkit-1/localauthority' (which I was about to install): Bad message

2019-06-08 Thread venugopal
Public bug reported:

while rebooting it gui is not appearing only linux terminal is showing
not resetting into graphical mode

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: systemd 237-3ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
Uname: Linux 4.15.0-20-lowlatency i686
ApportVersion: 2.20.9-0ubuntu7
Architecture: i386
Date: Sun Jun  9 06:37:13 2019
DuplicateSignature:
 package:systemd:237-3ubuntu10
 Unpacking systemd (237-3ubuntu10.21) over (237-3ubuntu10) ...
 dpkg: error processing archive 
/tmp/apt-dpkg-install-FLSGvw/4-systemd_237-3ubuntu10.21_i386.deb (--unpack):
  unable to stat './var/lib/polkit-1/localauthority' (which I was about to 
install): Bad message
ErrorMessage: unable to stat './var/lib/polkit-1/localauthority' (which I was 
about to install): Bad message
InstallationDate: Installed on 2019-06-09 (0 days ago)
InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f82399f9-2a5d-483d-8dc3-cb178026d113 ro quiet splash vt.handoff=1
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.1
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
 
 2 overridden configuration files found.
Title: package systemd 237-3ubuntu10 failed to install/upgrade: unable to stat 
'./var/lib/polkit-1/localauthority' (which I was about to install): Bad message
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/24/2012
dmi.bios.vendor: Intel Corp.
dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH61HO
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG62445-102
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pvr:rvnIntelCorporation:rnDH61HO:rvrAAG62445-102:cvn:ct3:cvr:

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


** Tags: apport-package bionic i386

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

Title:
  package systemd 237-3ubuntu10 failed to install/upgrade: unable to
  stat './var/lib/polkit-1/localauthority' (which I was about to
  install): Bad message

Status in systemd package in Ubuntu:
  New

Bug description:
  while rebooting it gui is not appearing only linux terminal is showing
  not resetting into graphical mode

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-3ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-20.21-lowlatency 4.15.17
  Uname: Linux 4.15.0-20-lowlatency i686
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: i386
  Date: Sun Jun  9 06:37:13 2019
  DuplicateSignature:
   package:systemd:237-3ubuntu10
   Unpacking systemd (237-3ubuntu10.21) over (237-3ubuntu10) ...
   dpkg: error processing archive 
/tmp/apt-dpkg-install-FLSGvw/4-systemd_237-3ubuntu10.21_i386.deb (--unpack):
unable to stat './var/lib/polkit-1/localauthority' (which I was about to 
install): Bad message
  ErrorMessage: unable to stat './var/lib/polkit-1/localauthority' (which I was 
about to install): Bad message
  InstallationDate: Installed on 2019-06-09 (0 days ago)
  InstallationMedia: Ubuntu-Studio 18.04 LTS "Bionic Beaver" - Release i386 
(20180426)
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-20-lowlatency 
root=UUID=f82399f9-2a5d-483d-8dc3-cb178026d113 ro quiet splash vt.handoff=1
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
   [EXTENDED]   /lib/systemd/system/user@.service → 
/lib/systemd/system/user@.service.d/timeout.conf
   
   2 overridden configuration files found.
  Title: package systemd 237-3ubuntu10 failed to install/upgrade: unable to 
stat './var/lib/polkit-1/localauthority' (which I was about to install): Bad 
message
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/24/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: HOH6110H.86A.0010.2012.0424.1632
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DH61HO
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG62445-102
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrHOH6110H.86A.0010.2012.0424.1632:bd04/24/2012:svn:pn:pv

[Touch-packages] [Bug 1690485] Re: openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

2019-06-08 Thread Luke A. Perkins
See also Ticket #1831765 and #1832110 regarding the path of the
privilege separation directory (aka: /run/sshd).

This path is hard-coded into sshd and there is no means of changing its
location. I have found that if the directory is missing, all ssh
communication unceremoniously stops (iff UsePrivilegeSeparation yes).
The original OpenSSH 7.6p1 assigns the privilege separation directory to
"/var/empty" (see man sshd at openssh.com). When Ubuntu changed to
systemd from Upstart, the privilege separation directory was changed
from "/var/empty" to "/run/sshd". This is also supported by reviewing
the value of /lib/systemd/system/ssh.service and look at the
RuntimeDirectory=sshd.

My work-around is to create a service that does nothing other than
create the "/run/sshd" directory and define the
RuntimeDirectory=(anything but sshd) in your .service file.

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

Title:
  openssh-server SIGSYS with 'UsePrivilegeSeparation sandbox'

Status in openssh package in Ubuntu:
  New

Bug description:
  The 'sshd' process gets 'authentication failure' and refuses to allow
  any login.

  dmesg indicates that the problem is SIGSYS on a call to 'socket'
  (syscall #41, signal #31).

  On a hunch, I decided to test whether the problem is related to
  'seccomp' and changed /etc/ssh/sshd_config from the default

  # UsePrivilegeSeparation sandbox

  to the former standard value

  UsePrivilegeSeparation yes

  and logins started to work again.

  Obviously, I'd like to have the additional protection that sandboxing
  would give me.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: openssh-server 1:7.4p1-10
  ProcVersionSignature: Ubuntu 4.10.0-20.22-generic 4.10.8
  Uname: Linux 4.10.0-20-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri May 12 21:06:20 2017
  InstallationDate: Installed on 2017-04-08 (35 days ago)
  InstallationMedia:
   
  SourcePackage: openssh
  UpgradeStatus: Upgraded to zesty on 2017-04-24 (19 days ago)

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

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


[Touch-packages] [Bug 1832110] [NEW] Resource Sharing with multiple sshd services

2019-06-08 Thread Luke A. Perkins
Public bug reported:

Ubuntu: 18.04.2 LTS
OpenSSH: 7.6p1

I am having a problem starting multiple sshd processes. The default
location of the sshd privilege separation directory is hard-coded to
/run/sshd (see man page). If I want to have 2 sshd services using
systemd, I need to write 2 service files, let's call them
sshd_wan.service ans sshd_lan.service. Both of these services need to
have their own "RuntimeDirectory=sshd_wan" and
"RuntimeDirectory=sshd_lan". If you do not have separate
RuntimeDirectory definitions for the 2 services, then when one service
is killed/faults/restarts/stops/etc. the systemd (or init) process
deletes the RuntimeDirectory and causes the other service to crash since
a RuntimeDirectory does not exist.

The problem is the hard-coding of the sshd Privilege Separation
Directory. We need to modify the OpenBSD/OpenSSH sshd code to provision
command line assignment of the privilege separation directory.

I have attempted to contact the OpenSSH team (i.e. OpenSSH.com) and they
say it is a Ubuntu problem. I reported this in Ubuntu bug #1831765 and
Ubuntu (e.g. Paride Legovini, June 6, 2019 @ 2:55AM PDT) rejected it
because I described the problem using the init.d example.

I know how to modify the sshd.c file in OpenSSH 7.6p1, the problem is
getting Ubuntu and OpenSSH to admit there is a problem and it needs to
be fixed.

The problem is still there regardless if you are using Upstart (i.e.
init.d) or systemd.

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

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

Title:
  Resource Sharing with multiple sshd services

Status in openssh package in Ubuntu:
  New

Bug description:
  Ubuntu: 18.04.2 LTS
  OpenSSH: 7.6p1

  I am having a problem starting multiple sshd processes. The default
  location of the sshd privilege separation directory is hard-coded to
  /run/sshd (see man page). If I want to have 2 sshd services using
  systemd, I need to write 2 service files, let's call them
  sshd_wan.service ans sshd_lan.service. Both of these services need to
  have their own "RuntimeDirectory=sshd_wan" and
  "RuntimeDirectory=sshd_lan". If you do not have separate
  RuntimeDirectory definitions for the 2 services, then when one service
  is killed/faults/restarts/stops/etc. the systemd (or init) process
  deletes the RuntimeDirectory and causes the other service to crash
  since a RuntimeDirectory does not exist.

  The problem is the hard-coding of the sshd Privilege Separation
  Directory. We need to modify the OpenBSD/OpenSSH sshd code to
  provision command line assignment of the privilege separation
  directory.

  I have attempted to contact the OpenSSH team (i.e. OpenSSH.com) and
  they say it is a Ubuntu problem. I reported this in Ubuntu bug
  #1831765 and Ubuntu (e.g. Paride Legovini, June 6, 2019 @ 2:55AM PDT)
  rejected it because I described the problem using the init.d example.

  I know how to modify the sshd.c file in OpenSSH 7.6p1, the problem is
  getting Ubuntu and OpenSSH to admit there is a problem and it needs to
  be fixed.

  The problem is still there regardless if you are using Upstart (i.e.
  init.d) or systemd.

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

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


[Touch-packages] [Bug 1832108] [NEW] unmkinitramfs fails with lz4 compressed initrds

2019-06-08 Thread Dimitri John Ledkov
Public bug reported:

unmkinitramfs fails with lz4 compressed initrds

Note:

$ lz4cat -t unmkinitramfs_Cz6Yl9
File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process 
file: unmkinitramfs_Cz6Yl9


And

$ lsinitramfs /boot/initrd.img
kernel
kernel/x86
kernel/x86/microcode
kernel/x86/microcode/.enuineIntel.align.0123456789abc
kernel/x86/microcode/GenuineIntel.bin
cpio: premature end of archive

** Affects: initramfs-tools (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  unmkinitramfs fails with lz4 compressed initrds

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  unmkinitramfs fails with lz4 compressed initrds

  Note:

  $ lz4cat -t unmkinitramfs_Cz6Yl9
  File extension doesn't match expected LZ4_EXTENSION (.lz4); will not process 
file: unmkinitramfs_Cz6Yl9

  
  And

  $ lsinitramfs /boot/initrd.img
  kernel
  kernel/x86
  kernel/x86/microcode
  kernel/x86/microcode/.enuineIntel.align.0123456789abc
  kernel/x86/microcode/GenuineIntel.bin
  cpio: premature end of archive

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1832108/+subscriptions

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


[Touch-packages] [Bug 1832106] [NEW] Some packages could not be installed

2019-06-08 Thread Max Emerling
Public bug reported:

sudo apt-get install xserver-xorg-video-intel

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-21-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Jun  8 12:10:54 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
   Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc]
InstallationDate: Installed on 2019-06-06 (1 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
 Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
 Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp. 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Latitude E7470
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=4c3f6446-77d8-4152-8446-dbda7f591ea6 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/20/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.21.6
dmi.board.name: 0T6HHJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.6:bd05/20/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude E7470
dmi.product.sku: 06DC
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core N/A
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  Some packages could not be installed

Status in xorg package in Ubuntu:
  New

Bug description:
  sudo apt-get install xserver-xorg-video-intel

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.18.0-21.22~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-21-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  8 12:10:54 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:06dc]
  InstallationDate: Installed on 2019-06-06 (1 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
   Bus 001 Device 003: ID 0a5c:5832 Broadcom Corp. 
   Bus 001 Device 002: ID 0bda:5686 Realtek Semiconductor Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Latitude E7470
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-21-generic 
root=UUID=4c3f6446-77d8-4152-8446-dbda7f591ea6 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/20/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.21.6
  dmi.board.name: 0T6HHJ
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.21.6:bd05/20/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.family: Latitude
  dmi.product.name: Latitude E7470
  dmi.product.sku: 06DC
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2

[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892

2019-06-08 Thread Luca Mastromatteo
https://bugzilla.kernel.org/show_bug.cgi?id=195303

This bug tracker is more updated

** Summary changed:

- Microphone distorted sound on ALC892
+ Microphone distorted sound on ALC892/1220 on AMD chipsets

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

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

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

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

  alsa-info on the attachments

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

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


[Touch-packages] [Bug 1801540] Re: Microphone distorted sound on ALC892

2019-06-08 Thread Luca Mastromatteo
Some info regarding this, looks like a common problem with also other
different codecs and the only thing in common is the AMD chipset.

The same codecs on Intel looks to play just fine

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

Title:
  Microphone distorted sound on ALC892/1220 on AMD chipsets

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

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

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

  alsa-info on the attachments

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

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


[Touch-packages] [Bug 1832078] [NEW] two start need

2019-06-08 Thread Roch Desjardins
Public bug reported:

i don't speak english

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
Uname: Linux 4.15.0-51-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sat Jun  8 05:09:13 2019
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:144b]
 Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 / 
6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Mobility Radeon HD 5650 [103c:144b]
InstallationDate: Installed on 2019-05-11 (28 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=ce1ae318-35fe-47bc-8fb6-7a2662550abd ro quiet splash radeon.audio=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/21/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.23
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 144B
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 65.35
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.23:bd10/21/2010:svnHewlett-Packard:pnHPPaviliondv7NotebookPC:pvr058911242B20010020100:rvnHewlett-Packard:rn144B:rvr65.35:cvnHewlett-Packard:ct10:cvrN/A:
dmi.product.family: 103C_5335KV
dmi.product.name: HP Pavilion dv7 Notebook PC
dmi.product.version: 058911242B20010020100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.8-0ubuntu0~18.04.2
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.8-0ubuntu0~18.04.2
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Sat Jun  8 04:55:57 2019
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.6-1ubuntu4.2
xserver.video_driver: modeset

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


** Tags: apport-bug bionic compiz-0.9 i386 ubuntu

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

Title:
  two start need

Status in xorg package in Ubuntu:
  New

Bug description:
  i don't speak english

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-51.55-generic 4.15.18
  Uname: Linux 4.15.0-51-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jun  8 05:09:13 2019
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Core Processor Integrated Graphics Controller [8086:0046] 
(rev 02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Core Processor Integrated Graphics 
Controller [103c:144b]
   Advanced Micro Devices, Inc. [AMD/ATI] Madison [Mobility Radeon HD 5650/5750 
/ 6530M/6550M] [1002:68c1] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Mobility Radeon HD 5650 [103c:144b]
  InstallationDate: Installed on 2019-05-11 (28 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  MachineType: Hewlett-Packard HP Pavilion dv7 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-51-generic 
root=UUID=ce1ae318-35fe-47bc-8fb6-7a2662550abd ro quiet splash radeon.audio=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2010
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.23
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: 144B
  dmi.board.vendor: Hewlett-Packard
  dmi.board.versio

[Touch-packages] [Bug 1832060] Re: Backport "add an option that allows rewinds to be disabled"

2019-06-08 Thread Ubuntu Foundations Team Bug Bot
The attachment "0001-Backport-add-an-option-that-allows-rewinds-to-be-
dis.patch" seems to be a patch.  If it isn't, please remove the "patch"
flag from the attachment, remove the "patch" tag, and if you are a
member of the ~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  Backport "add an option that allows rewinds to be disabled"

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  PulseAudio git master added an option that allows rewinds to be
  disabled. I backported it to v12.2, the patch is here:
  https://gitlab.com/nixtux-packaging/pulseaudio-
  ubuntu/blob/master/pulseaudio-12.2/debian/patches/0001-Backport-add-
  an-option-that-allows-rewinds-to-be-dis.patch

  This will help PulseEffects that is being packaged in
  https://bugs.launchpad.net/ubuntu/+bug/1832059 by fixing crackling
  sound when changing the volume level.

  It would be good to have this patches applied in Eoan if PulseAudio
  13.0 does not get to it.

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

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


[Touch-packages] [Bug 1832074] [NEW] base-files '/etc/update-motd.d/50-motd-news' reports system use to Ubuntu

2019-06-08 Thread Justin Fletcher
Public bug reported:

System information::

root@here $ lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04

root@here$ dpkg -l base-files | tail -1
ii  base-files 10.1ubuntu2.4 amd64Debian base system miscellaneous 
files


What I expect to happen::

Logins to my machine should not be communicated to anyone else, and
should not provide anyone else of information about my machine.


What does happen::

Logins to my machine report that a login occurred, and provide details
about the installed system, to Ubuntu.


Report::

I've just upgraded fromt Trusty to Bionic, and found that on login I get
a message telling me something about Ubuntu's Kubernetes. I don't want
advertising presented to me when I log in to MY system, so I began to
investigate where this is happening - assuming that /etc/update-
motd.d/10-help-text or 00-header had been updated during the upgrade and
recreated with this content.

Instead, I discover that there is another script that has been added -
/etc/update-motd.d/50-motd-news - which adds this junk text to the
login. Not only that, but the script comminucates with Ubuntu, to fetch
that information. Not only that, but it provides information about the
system that is running as part of the request.

During the upgrade, I was not asked about whether it was ok for the
system to call home every time I login (or every 12 hours, whichever is
sooner, but at least a minute after you boot), and it absolutely would
not be my expectation that this be the default. When I log in to my
machine, I do not expect that the event would be reported to any off-
site system, and I suspect that most other users would be surprised if
not horrified to find that the fact that a system is in use was being
reported to Ubuntu.

The service can be disabled by changing a setting in /etc/defaults/motd-
news from ENABLED=1 to ENABLED=0, but this almost certainly should be
defaulting to 0 - tracking disabled by default, not tracking enabled by
default.

For example, on my system this provides a user agent containing:

```
curl/7.58.0-2ubuntu3.7 Ubuntu/18.04.2/LTS GNU/Linux/4.15.0-50-generic/x86_64 
Intel(R)/Xeon(R)/CPU/X5675/@/3.07GHz uptime/580915.35/4598709.84
```

This means that every time the user logs in (or after 12 hours from the
prior log in, whichever is longer) Ubuntu receives:

* The IP address of a system that is in use (which might be behind NAT, but 
it's still a report).
* The Distribution version details.
* The Kernel version details
* The CPU type
* The uptime

Knowing where a machine is, that it is active, exactly what type of
system it is an how often it is restarted, would be an awesome dataset
for any attacker to obtain - ideally (for them) it tells them the
location of systems that are alive, how they might be attacked - from
the distribution version, the kernel and the CPU information, you can
determine a set of vulnerabilities to attack - and the uptime, which
will indicate how likely the system is to be patched.

The only thing that might be worse might be to include a cookie-jar on
the curl command, which would allow tracking of individual systems,
rather than aggregating them behind NAT using the IP (although it's
still possible that the data reported in the user agent may be able to
make that information individually usable). That said, the root user
could (unintentionally) enable a cookie jar in their .curlrc and thus
enable individual system tracking without realising.

Whilst there may be legitimate reasons for reporting this information
(say for reporting to the user that their system has updates available
or that the system is vulnerable!), an advertising tool which reports
the system's information regularly back to home does not seem
appropriate for a 'base-files' package.

The surprise at having my logins recorded on a remote site pales in
comparison to the horror of recording a database of systems that might
be abused.

The Privacy and potential Security concerns of this feature hugely
outweigh any perceived benefit to the user, and I believe that the right
course of action is to remove this script entirely from the
distribution. At the very least the script's operation should default to
being disabled.

** Affects: base-files (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: privacy

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

Title:
  base-files '/etc/update-motd.d/50-motd-news' reports system use to
  Ubuntu

Status in base-files package in Ubuntu:
  New

Bug description:
  System information::

  root@here $ lsb_release -rd
  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  root@here$ dpkg -l base-files | tail -1
  ii  base-files 10.1ubuntu2.4 amd64Debian base system 
miscellaneous files

  
  What I expect to happen::

  Logins to my machine should not be communicate

[Touch-packages] [Bug 1831505] Re: Qt5 incorrectly interpret keypresses from remote VNC keyboard

2019-06-08 Thread Dmitry Shachnev
** Description changed:

- Steps to reproduce:
+ [Impact]
+ Qt applications incorrectly interpret keyboard input when running over some 
VNC clients such as TightVNC.
+ 
+ [Test Case]
  1. Have Ubuntu 18.04 LTS installed with VNC server
  2. Connect to Ubuntu 18.04 LTS from other machine with VNC client
  3. Launch any Qt5 based application such as `assistant`, `kate` or `retext`
  4. Press keyboard combination on VNC client
  
  Expected results:
  all keypresses are recognized successfully
  
  Actual results:
  *  produces `1`
  *  produces `5`
  * <`> produces `p`
  *  and  are not working
  * all letters are messed
  
+ [Proposed Fix]
+ The proposed fix is a backport of two upstream commits: the second being the 
actual fix, the first one is some refactoring of the code to make it easier to 
write the second. The commits are:
  
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f8b164e1c37ca901
+ - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=3edcd9420e3ad661
+ 
+ [Regression Potential]
+ Most of the new code is triggered only when the keymap is missing rules, 
models, or layout (i.e. rmlvo_is_incomplete == true). This minimizes the risk 
of regressions when working with simple X11 server. In any case, the potential 
regressions will be related to input handling.
+ 
+ [Other Info]
  Note:
  only Qt applications are affected, the GTK-based work as expected (including 
Chromium from which I write this bug-report)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qt5-assistant 5.9.5-0ubuntu1
  Uname: Linux 4.4.78-perf+ aarch64
  NonfreeKernelModules: wlan exfat
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: armhf
  CurrentDesktop: MATE
  Date: Tue Jun  4 00:46:55 2019
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: qttools-opensource-src
  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 qtbase-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1831505

Title:
  Qt5 incorrectly interpret keypresses from remote VNC keyboard

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

Bug description:
  [Impact]
  Qt applications incorrectly interpret keyboard input when running over some 
VNC clients such as TightVNC.

  [Test Case]
  1. Have Ubuntu 18.04 LTS installed with VNC server
  2. Connect to Ubuntu 18.04 LTS from other machine with VNC client
  3. Launch any Qt5 based application such as `assistant`, `kate` or `retext`
  4. Press keyboard combination on VNC client

  Expected results:
  all keypresses are recognized successfully

  Actual results:
  *  produces `1`
  *  produces `5`
  * <`> produces `p`
  *  and  are not working
  * all letters are messed

  [Proposed Fix]
  The proposed fix is a backport of two upstream commits: the second being the 
actual fix, the first one is some refactoring of the code to make it easier to 
write the second. The commits are:

  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=f8b164e1c37ca901
  - https://code.qt.io/cgit/qt/qtbase.git/commit/?id=3edcd9420e3ad661

  [Regression Potential]
  Most of the new code is triggered only when the keymap is missing rules, 
models, or layout (i.e. rmlvo_is_incomplete == true). This minimizes the risk 
of regressions when working with simple X11 server. In any case, the potential 
regressions will be related to input handling.

  [Other Info]
  Note:
  only Qt applications are affected, the GTK-based work as expected (including 
Chromium from which I write this bug-report)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: qt5-assistant 5.9.5-0ubuntu1
  Uname: Linux 4.4.78-perf+ aarch64
  NonfreeKernelModules: wlan exfat
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: armhf
  CurrentDesktop: MATE
  Date: Tue Jun  4 00:46:55 2019
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: qttools-opensource-src
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1831505/+subscriptions

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


[Touch-packages] [Bug 1810346] Re: VLC interface not displayed correctly

2019-06-08 Thread Dmitry Shachnev
Can one of you please check if the issue still exists with Ubuntu 19.04
(which has Qt 5.12)?

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

Title:
  VLC interface not displayed correctly

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

Bug description:
  I use vlc on a Dell E-5530 laptop seated on its docking station.
  The laptop display cover is closed, the output is sent on an external LG TV 
with 1920x1080.
  This system has been working flawlessly for many years, resp. under late 
14.04 and 16.04.
  After recently upgrading to 18.04, I noticed VLC wouldn't display correctly - 
see attachment.
  This only occurs on the external display ; if I open the cover and use the 
internal display, there is no problem - except I cannot work on the internal 
display.
  regards,
  J.-Luc

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: vlc-bin 3.0.4-1ubuntu0.2
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jan  2 23:38:36 2019
  ExecutablePath: /usr/bin/vlc
  InstallationDate: Installed on 2018-12-19 (14 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   PATH=(custom, user)
   XDG_RUNTIME_DIR=
   LANG=fr_FR.UTF-8
   SHELL=/bin/bash
  SourcePackage: vlc
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1810346/+subscriptions

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


[Touch-packages] [Bug 1795358] Re: FTBFS with MySQL 8.0

2019-06-08 Thread Dmitry Shachnev
Ubuntu 19.04 release has Qt 5.12, so marking this as fixed.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => 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/1795358

Title:
  FTBFS with MySQL 8.0

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  MySQL 8.0 removes the my_bool symbol, and it should simply be replaced
  with int or bool (this is also backwards-compatible with older
  versions of MySQL)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1795358/+subscriptions

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


[Touch-packages] [Bug 1811678] Re: Inconsistent OpenGL support across architectures

2019-06-08 Thread Dmitry Shachnev
Sorry for the delay, for some reason I have not received a mail about
this bug.

Starting with Ubuntu 19.04 release, there is no difference between
Debian and Ubuntu: both use OpenGL ES on armel/armhf, and desktop OpenGL
on the other architectures. Initially I wanted to add arm64 to that list
too, but after the discussion in https://lists.debian.org/debian-
devel/2018/11/msg00457.html the plan was changed.

The reason for using OpenGL ES on armel/armhf is that the majority of
devices with that architecture are mobile devices that have video chips
supporting only OpenGL ES natively.

It looks like v4l-utils currently builds fine on all supported Ubuntu
releases, but if you have problems with supporting OpenGL ES versions,
please let me know.

** Changed in: qtbase-opensource-src (Ubuntu)
   Status: New => 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/1811678

Title:
  Inconsistent OpenGL support across architectures

Status in qtbase-opensource-src package in Ubuntu:
  Fix Released

Bug description:
  Hello,

  today I noticed build failures of v4l-utils on arm64 hosts:
  
https://launchpadlibrarian.net/406083796/buildlog_ubuntu-bionic-arm64.v4l-utils_1.17.1-201901131615~ubuntu18.04.1_BUILDING.txt.gz

  This is due to the OpenGLES2 feature is enabled on arm64 (but this
  feature is not enabled for amd64):

  > /usr/include/x86_64-linux-gnu/qt5/QtGui# grep -i opengl qtgui-config.h
  > #define QT_FEATURE_opengles2 -1
  > #define QT_FEATURE_opengl 1
  > #define QT_FEATURE_opengles3 -1
  > #define QT_FEATURE_opengles31 -1

  vs:

  > /usr/include/aarch64-linux-gnu/qt5/QtGui$ grep -i opengl qtgui-config.h
  > #define QT_FEATURE_opengles2 1
  > #define QT_OPENGL_ES true
  > #define QT_OPENGL_ES_2 true
  > #define QT_FEATURE_opengl 1
  > #define QT_FEATURE_opengles3 1
  > #define QT_OPENGL_ES_3 true
  > #define QT_FEATURE_opengles31 1
  > #define QT_OPENGL_ES_3_1 true 

  Is the inconsistent feature setting intentional? The Debian Qt
  packages seem to select Desktop OpenGL across architectures.

  Thanks,
  Gregor

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qtbase-opensource-src/+bug/1811678/+subscriptions

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


[Touch-packages] [Bug 1829366] Re: [SRU] Bugfix release 1.14.4

2019-06-08 Thread Steve Langasek
Hello Iain, or anyone else affected,

Accepted gstreamer1.0 into bionic-proposed. The package will build now
and be available at
https://launchpad.net/ubuntu/+source/gstreamer1.0/1.14.4-1~ubuntu18.04.1
in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested and change the tag from
verification-needed-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.

** Changed in: gstreamer1.0 (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  [SRU]  Bugfix release 1.14.4

Status in gst-libav1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-bad1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-base1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-good1.0 package in Ubuntu:
  Fix Released
Status in gst-plugins-ugly1.0 package in Ubuntu:
  Fix Released
Status in gst-python1.0 package in Ubuntu:
  Fix Released
Status in gst-rtsp-server1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-editing-services1.0 package in Ubuntu:
  Fix Released
Status in gstreamer-vaapi package in Ubuntu:
  Fix Released
Status in gstreamer1.0 package in Ubuntu:
  Fix Released
Status in gst-libav1.0 source package in Bionic:
  In Progress
Status in gst-plugins-bad1.0 source package in Bionic:
  In Progress
Status in gst-plugins-base1.0 source package in Bionic:
  In Progress
Status in gst-plugins-good1.0 source package in Bionic:
  In Progress
Status in gst-plugins-ugly1.0 source package in Bionic:
  In Progress
Status in gst-python1.0 source package in Bionic:
  In Progress
Status in gst-rtsp-server1.0 source package in Bionic:
  Fix Committed
Status in gstreamer-editing-services1.0 source package in Bionic:
  In Progress
Status in gstreamer-vaapi source package in Bionic:
  In Progress
Status in gstreamer1.0 source package in Bionic:
  Fix Committed

Bug description:
  [ Description ]

  We should keep up with GStreamer's bugfix releases in the 1.14 series
  that 18.04 shipped with.

  [ QA and testing ]

  Play a range of videos in Totem. Play a range of audio tracks in
  Rhythmbox. Try to stream audio and/or video. Try to install a missing
  codec.

  In all cases, make sure that everything which worked before still
  works.

  [ Regression potential ]

  If one of the fixes is bad then it might break video or audio
  playback, or could crash any application that tries to use gstreamer.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-libav1.0/+bug/1829366/+subscriptions

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