[Touch-packages] [Bug 1841915] Re: black screen, unresponsive, after logout from gnome Wayland session

2019-09-08 Thread Daniel van Vugt
Yes, confirmed fixed... somewhere.

** No longer affects: gnome-shell (Ubuntu)

** Changed in: gdm3 (Ubuntu)
   Status: Confirmed => Fix Released

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

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

Title:
  black screen, unresponsive, after logout from gnome Wayland session

Status in gdm3 package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  on logout the screen is black, the system is unresponsive and has to
  be restarted. (Untested by me yet, but I expect ssh-ing in and
  restarting gdm would work.)

  I believe this may be already reported upstream here:
  https://bugzilla.redhat.com/show_bug.cgi?id=1745554 That's why I've
  reported this against gdm3 even though I honestly don't know if it
  might be a gnome-shell, gnome-session or mutter based error. (FWIW
  without the upstream bug to link to I'd maybe suspect gnome-shell
  first.)

  NB: This machine's conf has AutomaticLogin enabled, but another
  machine also on 19.10 does not, and it's showing the same thing. On
  *this* machine I found that the *first* time I logged out, it was OK,
  but not the second time. On the other machine, it fails first time
  too. It's as if the gdm login screen can appear exactly once. That
  (and being on gnome 3.33) is why I don't think this is a dupe of
  #1824588.

  Nothing appears in /var/crash as a result of this.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gdm3 3.33.90-1ubuntu1
  ProcVersionSignature: Ubuntu 5.2.0-13.14-generic 5.2.8
  Uname: Linux 5.2.0-13-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 29 10:51:22 2019
  InstallationDate: Installed on 2018-09-11 (351 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to eoan on 2019-07-16 (43 days ago)
  mtime.conffile..etc.gdm3.custom.conf: 2019-07-17T00:07:04.528641

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

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


[Touch-packages] [Bug 1132446] Re: Bold fonts are converting to normal fonts on scrolling

2019-09-08 Thread Colin Watson
Reassigning to less, then, though it could also be a bug in lxterminal.

** Package changed: man-db (Ubuntu) => less (Ubuntu)

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

Title:
  Bold fonts are converting to normal fonts on scrolling

Status in less package in Ubuntu:
  New

Bug description:
  I'm using Ubuntu 13.04 dev with man-db 2.6.3-3. If I'm reading a
  manpage in the terminal and scrolling down with the keyboard rarely
  some bold fonts are converting to normal fonts.

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

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


[Touch-packages] [Bug 611791] Re: package man-db 2.5.5-1build1 failed to install/upgrade:

2019-09-08 Thread Colin Watson
I suspect at this point it's probably no longer relevant, and there
isn't much to go on here; but "package man-db is already installed and
configured" suggests that apt tried to schedule a dpkg --configure
action on man-db when it shouldn't have done so.

** Package changed: man-db (Ubuntu) => apt (Ubuntu)

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

Title:
  package man-db 2.5.5-1build1 failed to install/upgrade:

Status in apt package in Ubuntu:
  New

Bug description:
  Binary package hint: man-db

  while trying to upgrade system state, was told this upgrade failed

  ProblemType: Package
  Architecture: i386
  DistroRelease: Ubuntu 9.04
  ErrorMessage:
   ErrorMessage: package man-db is already installed and configured
  NonfreeKernelModules: wl
  Package: man-db 2.5.5-1build1
  SourcePackage: man-db
  Title: package man-db 2.5.5-1build1 failed to install/upgrade:
  Uname: Linux 2.6.28-19-generic i686

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

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


[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon

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

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  Port schemas from gnome-settings-daemon-common to com.canonical.unity
  .settings-daemon

Status in indicator-session package in Ubuntu:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Unity-settings-daemon still depends on gnome-settings-daemon schemas.
  It is undesired as it requires to modify code in all unity related
  components when upstream drops some gsettings schemas.

  gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an
  undesired way that it can't easily be reverted. Keyboard & mouse
  schemas are modified and unity-settings-daemon is crashing. So it's
  better unity uses it's own schema as suggested by Laney. We will of-
  course keep using settings migration (org.gnome.settings-daemon->
  org.gnome.desktop) wherever possible.

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768

  Since this is a huge task it can be achieved gradually.

  1) Ubuntu 19.10

  - Port media keys to use com.canonical.unity.settings-daemon

  - u-s-d will still use org.gnome.settings-daemon name in dbus

  - u-s-d will still respects activation toggle in org.gnome.settings-
  daemon

  - everything else remains the same

  2) Ubuntu 20.04

  - Port rest of plugins to use com.canonical.unity.settings-daemon

  - u-s-d will still use org.gnome.settings-daemon name in dbus

  - Activation toggle key will now use com.canonical.unity.settings-
  daemon

  - Everything else will remain the same

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+subscriptions

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


[Touch-packages] [Bug 1842324] Re: Port schemas from gnome-settings-daemon-common to com.canonical.unity.settings-daemon

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

** Changed in: indicator-session (Ubuntu)
   Status: New => Confirmed

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

Title:
  Port schemas from gnome-settings-daemon-common to com.canonical.unity
  .settings-daemon

Status in indicator-session package in Ubuntu:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  Confirmed
Status in unity package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Confirmed
Status in unity-greeter package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  Unity-settings-daemon still depends on gnome-settings-daemon schemas.
  It is undesired as it requires to modify code in all unity related
  components when upstream drops some gsettings schemas.

  gnome-settings-daemon > 3.33 drops/modify media-keys schemas in an
  undesired way that it can't easily be reverted. Keyboard & mouse
  schemas are modified and unity-settings-daemon is crashing. So it's
  better unity uses it's own schema as suggested by Laney. We will of-
  course keep using settings migration (org.gnome.settings-daemon->
  org.gnome.desktop) wherever possible.

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/6dff93a0dfa80db3f481eed5d6ed689bf469aa1b

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/44f53c64c5a2514d2c022bcb1596a9e46f1df51c

  https://gitlab.gnome.org/GNOME/gnome-settings-
  daemon/commit/121a6f89917898b8d05db2e1933dd0ad59c26768

  Since this is a huge task it can be achieved gradually.

  1) Ubuntu 19.10

  - Port media keys to use com.canonical.unity.settings-daemon

  - u-s-d will still use org.gnome.settings-daemon name in dbus

  - u-s-d will still respects activation toggle in org.gnome.settings-
  daemon

  - everything else remains the same

  2) Ubuntu 20.04

  - Port rest of plugins to use com.canonical.unity.settings-daemon

  - u-s-d will still use org.gnome.settings-daemon name in dbus

  - Activation toggle key will now use com.canonical.unity.settings-
  daemon

  - Everything else will remain the same

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1842324/+subscriptions

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


[Touch-packages] [Bug 1132446] [NEW] Bold fonts are converting to normal fonts on scrolling

2019-09-08 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I'm using Ubuntu 13.04 dev with man-db 2.6.3-3. If I'm reading a manpage
in the terminal and scrolling down with the keyboard rarely some bold
fonts are converting to normal fonts.

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

-- 
Bold fonts are converting to normal fonts on scrolling
https://bugs.launchpad.net/bugs/1132446
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to less 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 611791] [NEW] package man-db 2.5.5-1build1 failed to install/upgrade:

2019-09-08 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

Binary package hint: man-db

while trying to upgrade system state, was told this upgrade failed

ProblemType: Package
Architecture: i386
DistroRelease: Ubuntu 9.04
ErrorMessage:
 ErrorMessage: package man-db is already installed and configured
NonfreeKernelModules: wl
Package: man-db 2.5.5-1build1
SourcePackage: man-db
Title: package man-db 2.5.5-1build1 failed to install/upgrade:
Uname: Linux 2.6.28-19-generic i686

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


** Tags: apport-package i386
-- 
package man-db 2.5.5-1build1 failed to install/upgrade:
https://bugs.launchpad.net/bugs/611791
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt 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 1414311] Re: package man-db 2.6.1-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-09-08 Thread Colin Watson
** Package changed: man-db (Ubuntu) => debconf (Ubuntu)

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

Title:
  package man-db 2.6.1-2ubuntu1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in debconf package in Ubuntu:
  Confirmed

Bug description:
  error occured while repairing the boot

  ProblemType: Package
  DistroRelease: Ubuntu 12.04
  Package: man-db 2.6.1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
  Uname: Linux 3.13.0-32-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  CasperVersion: 1.315.1
  Date: Sat Jan 24 20:49:00 2015
  DuplicateSignature: package:man-db:2.6.1-2ubuntu1:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  LiveMediaBuild: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
  MarkForUpload: True
  SourcePackage: man-db
  Title: package man-db 2.6.1-2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1799996] Re: package man-db 2.8.3-2ubuntu0.1 failed to install/upgrade: instalado man-db paquete post-installation guión el subproceso devolvió un error con estado de salida 1

2019-09-08 Thread Colin Watson
** Package changed: man-db (Ubuntu) => debconf (Ubuntu)

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

Title:
  package man-db 2.8.3-2ubuntu0.1 failed to install/upgrade: instalado
  man-db paquete post-installation guión el subproceso devolvió un error
  con estado de salida 1

Status in debconf package in Ubuntu:
  New

Bug description:
  ocurrio posterior mente cuando trate de installar los restrited-extras

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: man-db 2.8.3-2ubuntu0.1
  ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
  Uname: Linux 4.15.0-38-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.4
  Architecture: amd64
  Date: Thu Oct 25 12:26:58 2018
  ErrorMessage: instalado man-db paquete post-installation guión el subproceso 
devolvió un error con estado de salida 1
  InstallationDate: Installed on 2018-10-17 (7 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  Python3Details: /usr/bin/python3.6, Python 3.6.6, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.6
  SourcePackage: man-db
  Title: package man-db 2.8.3-2ubuntu0.1 failed to install/upgrade: instalado 
man-db paquete post-installation guión el subproceso devolvió un error con 
estado de salida 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1483751] Re: Issues traversing a sftp server when files or folders contain the character "]"

2019-09-08 Thread Luke Faraone
Can confirm:

sftp> cd Foo\ \[bar\]
sftp> ls
hello.txt  
sftp> get hello.txt
File "/home/lfaraone/Foo [bar]/hello.txt" not found.
sftp> 


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

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

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

Title:
  Issues traversing a sftp server when files or folders contain the
  character "]"

Status in openssh package in Ubuntu:
  Triaged

Bug description:
  I am unsure if the bug is with openssh sftp client or within openssh-
  sftp-server

  When traversing an sftp server, I encounter issues for files and, in
  particular, directories containing the character "]". Tab completion
  does not escape the character in sftp shell, however, in bash it will
  escape the character for tab completion. If I "cd" into a directory
  that contains the character I cannot get any files with in that
  directory and I have to rename the directory outside of the sftp shell
  to remove the character in order to be able to correctly get files.

  Ex:

  sftp> cd Movie\ \[1080p]/
  sftp> ls
  Movie.1080p.mp4
  sftp> get Movie.1080p.mp4
  File "/home/hitsuji/movies/Movie [1080p]/Movie.1080p.mp4" not found.
  sftp>

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: openssh-client 1:6.6p1-2ubuntu2
  ProcVersionSignature: Ubuntu 3.16.0-45.60~14.04.1-generic 3.16.7-ckt14
  Uname: Linux 3.16.0-45-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.11
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug 11 14:36:00 2015
  InstallationDate: Installed on 2015-05-01 (101 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  RelatedPackageVersions:
   ssh-askpass   N/A
   libpam-sshN/A
   keychain  N/A
   ssh-askpass-gnome 1:6.6p1-2ubuntu2
  SSHClientVersion: OpenSSH_6.6.1p1 Ubuntu-2ubuntu2, OpenSSL 1.0.1f 6 Jan 2014
  SourcePackage: openssh
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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


[Touch-packages] [Bug 1414311] [NEW] package man-db 2.6.1-2ubuntu1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2019-09-08 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

error occured while repairing the boot

ProblemType: Package
DistroRelease: Ubuntu 12.04
Package: man-db 2.6.1-2ubuntu2
ProcVersionSignature: Ubuntu 3.13.0-32.57~precise1-generic 3.13.11.4
Uname: Linux 3.13.0-32-generic x86_64
ApportVersion: 2.0.1-0ubuntu17.6
Architecture: amd64
CasperVersion: 1.315.1
Date: Sat Jan 24 20:49:00 2015
DuplicateSignature: package:man-db:2.6.1-2ubuntu1:subprocess installed 
post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
LiveMediaBuild: Ubuntu 12.04.5 LTS "Precise Pangolin" - Release amd64 
(20140807.1)
MarkForUpload: True
SourcePackage: man-db
Title: package man-db 2.6.1-2ubuntu1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: debconf (Ubuntu)
 Importance: Undecided
 Status: Confirmed


** Tags: amd64 apport-package precise
-- 
package man-db 2.6.1-2ubuntu1 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
https://bugs.launchpad.net/bugs/1414311
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to debconf 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 1799996] [NEW] package man-db 2.8.3-2ubuntu0.1 failed to install/upgrade: instalado man-db paquete post-installation guión el subproceso devolvió un error con estado de salida 1

2019-09-08 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

ocurrio posterior mente cuando trate de installar los restrited-extras

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: man-db 2.8.3-2ubuntu0.1
ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18
Uname: Linux 4.15.0-38-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.4
Architecture: amd64
Date: Thu Oct 25 12:26:58 2018
ErrorMessage: instalado man-db paquete post-installation guión el subproceso 
devolvió un error con estado de salida 1
InstallationDate: Installed on 2018-10-17 (7 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
Python3Details: /usr/bin/python3.6, Python 3.6.6, unpackaged
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, unpackaged
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.6
SourcePackage: man-db
Title: package man-db 2.8.3-2ubuntu0.1 failed to install/upgrade: instalado 
man-db paquete post-installation guión el subproceso devolvió un error con 
estado de salida 1
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package bionic
-- 
package man-db 2.8.3-2ubuntu0.1 failed to install/upgrade: instalado man-db 
paquete post-installation guión el subproceso devolvió un error con estado de 
salida 1
https://bugs.launchpad.net/bugs/176
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to debconf 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 1843201] [NEW] Unity in Wayland prompts for keyboard focus on each run of ssh-askpass-gnome

2019-09-08 Thread Luke Faraone
Public bug reported:

When using a Wayland-based Unity session on Ubuntu 19.04:

1. Have ssh-askpass-gnome as your askpass program.
2. ssh-add -c 
3. `ssh` to a host

Each time, before the ssh-askpass prompt is shown, Unity shows this
dialog:

+-+
| |
| ssh-askpass wants to inhibit shortcuts  |
| |
| You can restore Shortcuts by pressing   |
| Super+Escape.   |
| |
|_|
|   Deny | Allow  |
+-+

This is mildly distracting, and it means that you need to hit ,
answer, , instead of just answer .

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: ssh-askpass-gnome 1:7.9p1-10
ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
Uname: Linux 5.0.0-27-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep  8 15:04:25 2019
DistributionChannelDescriptor:
 # This is the distribution channel descriptor for the OEM CDs
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 
canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1
InstallationDate: Installed on 2019-08-27 (12 days ago)
InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
SourcePackage: openssh
UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago)

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


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

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

Title:
  Unity in Wayland prompts for keyboard focus on each run of ssh-
  askpass-gnome

Status in openssh package in Ubuntu:
  New

Bug description:
  When using a Wayland-based Unity session on Ubuntu 19.04:

  1. Have ssh-askpass-gnome as your askpass program.
  2. ssh-add -c 
  3. `ssh` to a host

  Each time, before the ssh-askpass prompt is shown, Unity shows this
  dialog:

  +-+
  | |
  | ssh-askpass wants to inhibit shortcuts  |
  | |
  | You can restore Shortcuts by pressing   |
  | Super+Escape.   |
  | |
  |_|
  |   Deny | Allow  |
  +-+

  This is mildly distracting, and it means that you need to hit ,
  answer, , instead of just answer .

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ssh-askpass-gnome 1:7.9p1-10
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep  8 15:04:25 2019
  DistributionChannelDescriptor:
   # This is the distribution channel descriptor for the OEM CDs
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   
canonical-oem-somerville-bionic-amd64-20180608-47+tunnels-mlk+X55+tunnels-mlk+X55.1
  InstallationDate: Installed on 2019-08-27 (12 days ago)
  InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 
20180608-09:38
  SourcePackage: openssh
  UpgradeStatus: Upgraded to disco on 2019-08-31 (8 days ago)

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

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


[Touch-packages] [Bug 1843197] Re: Time reported for having downloaded the packages is way off

2019-09-08 Thread Egmont Koblinger
** Also affects: apt (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Time reported for having downloaded the packages is way off

Status in apt package in Ubuntu:
  New
Status in ubuntu-release-upgrader package in Ubuntu:
  New

Bug description:
  It took about 30 minutes for me to download the packages for a distro
  upgrade, yet it reports it took 6 seconds.

  I'm upgrading from Disco to Eoan test version, using the command

sudo do-release-upgrade -d

  Excerpt from the output:

7 packages are going to be removed. 81 new packages are going to be 
installed. 1940 packages are going to be upgraded. 

You have to download a total of 1,964 M. This download will take 
about 4 hours with a 1Mbit DSL connection and about 3 days 4 hours 
with a 56k modem. 

[...]

Fetching
Get:1 http://hu.archive.ubuntu.com/ubuntu eoan/main amd64 locales all 
2.30-0ubuntu1 [3,870 kB]
Get:2 http://hu.archive.ubuntu.com/ubuntu eoan/main amd64 libc6-dbg amd64 
2.30-0ubuntu1 [5,736 kB]
[...]
Get:2020 http://hu.archive.ubuntu.com/ubuntu eoan/universe amd64 
xawtv-plugins amd64 3.106-1 [51.6 kB]
Get:2021 http://hu.archive.ubuntu.com/ubuntu eoan/main amd64 xbrlapi amd64 
5.6-11ubuntu2 [63.0 kB]
Fetched 1,964 MB in 6s (1,094 kB/s)

  The last line is faulty. The actual time was maybe about 30 minutes,
  not 6 seconds :-D

  Note that the two other values shown in the last line, namely the
  overall size and the average download speed seem to be correct, and
  dividing these two indeed gives about 30 minutes.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: ubuntu-release-upgrader-core 1:19.04.16.6
  ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21
  Uname: Linux 5.0.0-27-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity:Unity7:ubuntu
  Date: Sun Sep  8 22:48:32 2019
  InstallationDate: Installed on 2016-11-09 (1032 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to disco on 2019-09-08 (0 days ago)

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

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


[Touch-packages] [Bug 1654448] Re: Dell XPS 13 9350/9360 headphone audio hiss

2019-09-08 Thread caoilte
Weird. I've had an XPS 9360 running ubuntu since November 2017. Last
week I picked up all the updates from August, rebooted and ran straight
into this bug with headphones that had previously been fine. I dual boot
into Windows and that is fine so it isn't a hardware problem.

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

Title:
  Dell XPS 13 9350/9360 headphone audio hiss

Status in Dell Sputnik:
  Confirmed
Status in alsa-driver package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Won't Fix
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pertaining to 16.04 on a dell XPS 13 9360

  ii  alsa-base 1.0.25+dfsg-0ubuntu5

  Advanced Linux Sound Architecture Driver Version k4.4.0-57-generic.

  
  When headphones are plugged in, there is a clearly audible hiss (white 
noise). This is present as soon as the headphones are plugged in, whether 
'headphones' or 'headset' are selected from the pop-up box. 

  Using alsamixer to debug the issue reveals that it is related to
  "Headphone Mic Boost" - the default setting is: dB gain 0.00, 0.00. If
  this is changed to:

  10.00, 10.00 (one notch up) the hiss disappears. 
  20.00, 20.00 cause a louder hiss and 
  30.00, 30.00 causes an even louder hiss with high frequency audio artifacts. 

  When the headphones are removed and plugged back in the Headphone Mic
  Boost setting returns to dB gain 0 and the problem also returns.

  This (problem and workaround) has been reported in the wild:
  https://news.ycombinator.com/item?id=13050843 and
  
https://www.reddit.com/r/Dell/comments/4j1zz4/headphones_have_static_noise_with_ubuntu_1604_on/
  for example

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1654448/+subscriptions

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


[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

2019-09-08 Thread Forest
The systemd patch I posted earlier no longer works in disco, and the
workarounds posted here only partially fix the problem and only for a
subset of use cases. Looks like we're back to needing a proper fix.

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

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

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


[Touch-packages] [Bug 1718658] Re: ecryptfs-mount-private fails to initialize ecryptfs keys

2019-09-08 Thread Forest
Still broken in disco.

** Tags added: disco

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

Title:
  ecryptfs-mount-private fails to initialize ecryptfs keys

Status in ecryptfs-utils package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  ecryptfs-mount-private fails to mount the ecryptfs after the 1st
  reboot after creating the ecryptfs by ecryptfs-setup-private.

  After the unsucessful attempt dmesg contains:

  [ 1265.695388] Could not find key with description: []
  [ 1265.695393] process_request_key_err: No key
  [ 1265.695394] Could not find valid key in user session keyring for sig 
specified in mount option: []
  [ 1265.695395] One or more global auth toks could not properly register; rc = 
[-2]
  [ 1265.695396] Error parsing options; rc = [-2]

  Note: The correct key ID has been replaced in the "".

  I also accidentally found an workaround - just running ecrytpfs-
  manager and then the ecryptfs-mount-private (it does not ask for
  password for the second time and mounts the ecryptfs correctly):

  host:~$ ecryptfs-manager

  eCryptfs key management menu
  ---
1. Add passphrase key to keyring
2. Add public key to keyring
3. Generate new public/private keypair
4. Exit

  Make selection: 4
  host:~$ ls Private/
  Access-Your-Private-Data.desktop  README.txt
  host:~$ ecryptfs-mount-private 
  host:~$ ls Private/
  

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

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


[Touch-packages] [Bug 1842133] Re: findutils shows wrong version number

2019-09-08 Thread Andreas Metzler
> I could submit a bug report against the upstream findutils component.
Should I do so?

No please don't, there is no point.

As noted above less old versions in Debian (and Ubuntu) already report a
more helpful version string.

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

Title:
  findutils shows wrong version number

Status in findutils package in Ubuntu:
  New

Bug description:
  This problem occurs on Ubuntu 18.04.3 LTS (bionic).
  It does not occur on Ubuntu 19.04 (disco)

  The "find" and "xargs" command are provided by a patched version of the
  GNU findutils package. The current version is based on release 4.6.0, but
  the "--version" option shows a version number of "4.7.0-git".

  As you can see, the "/usr/bin/find" executable is dated Nov 5 2017.
  findutils release 4.7.0 was released just yesterday, Aug 29 2017.

  Ubuntu 19.04 has findutils 4.6.0+git+20190209-2, and "find --version"
  shows "find (GNU findutils) 4.6.0.225-235f".

  Expected: "findutils --version" shows a version number based on 4.6.0
  Actual:   "findutils --version" shows a version number based on 4.7.0,
which had not yet been released

  Demonstration:

  $ lsb_release -rd
  Description:Ubuntu 18.04.3 LTS  
  Release:18.04
  $ apt-cache policy findutils
  findutils:
Installed: 4.6.0+git+20170828-2
Candidate: 4.6.0+git+20170828-2
Version table:
   *** 4.6.0+git+20170828-2 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  $ ls -l /usr/bin/find
  -rwxr-xr-x 1 root root 238080 Nov  5  2017 /usr/bin/find
  $ /usr/bin/find --version
  find (GNU findutils) 4.7.0-git
  Copyright (C) 2017 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later .
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.

  Written by Eric B. Decker, James Youngman, and Kevin Dalley.
  Features enabled: D_TYPE O_NOFOLLOW(enabled) LEAF_OPTIMISATION FTS(FTS_CWDFD) 
CBO(level=2)
  $

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

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


[Touch-packages] [Bug 1806263] Re: MariaDB 10.1 server won't start when MySQL 5.7 server has been previously installed

2019-09-08 Thread Thommie Rother
I see no activities here since may 19 and just ran into this bug on two
installations of 18.04.3. This is a major issue preventing the use of
mariadb!

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

Title:
  MariaDB 10.1 server won't start when MySQL 5.7 server has been
  previously installed

Status in apparmor package in Ubuntu:
  Won't Fix
Status in mariadb-10.1 package in Ubuntu:
  Confirmed
Status in mysql-5.7 package in Ubuntu:
  Won't Fix

Bug description:
  If you purge MySQL 5.7 server, then install MariaDB 10.1, that last
  won't start due to wrong AppArmor profile.

  CURRENT RESULT ON mariadb-server-10.1 package installation

  ...
  Job for mariadb.service failed because a timeout was exceeded.
  See "systemctl status mariadb.service" and "journalctl -xe" for details.
  ...

  # LANG=C systemctl status mariadb

  * mariadb.service - MariaDB 10.1.34 database server
 Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor 
preset: enabled)
 Active: failed (Result: timeout) since Sun 2018-12-02 17:26:09 UTC; 59s ago
   Docs: man:mysqld(8)
 https://mariadb.com/kb/en/library/systemd/
   Main PID: 23245 (code=exited, status=0/SUCCESS)

  Dec 02 17:24:37 bionic systemd[1]: Starting MariaDB 10.1.34 database server...
  Dec 02 17:24:37 bionic mysqld[23245]: 2018-12-02 17:24:37 139820621216896 
[Note] /usr/sbin/mysqld (mysqld 10.1.34-MariaDB-0ubuntu0.18.04.1) starting as 
process 23245 ...
  Dec 02 17:26:07 bionic systemd[1]: mariadb.service: Start operation timed 
out. Terminating.
  Dec 02 17:26:09 bionic systemd[1]: mariadb.service: Failed with result 
'timeout'.
  Dec 02 17:26:09 bionic systemd[1]: Failed to start MariaDB 10.1.34 database 
server.

  
  EXPECTED RESULT

  MariaDB 10.1 server starting as expected.

  HOWTO REPRODUCE

  apt-get install mysql-server-5.7 mysql-client-5.7
  apt-get purge mysql-server-5.7 mysql-client-5.7
  apt-get install mariadb-server-10.1 mariadb-client-10.1

  DISCUSSION

  The mysql-server-5.7 package install an
  /etc/apparmor.d/usr.sbin.mysqld APPARMOR(7) profile:

  # dpkg -S /etc/apparmor.d/usr.sbin.mysqld 
  mysql-server-5.7: /etc/apparmor.d/usr.sbin.mysqld

  When purging the mysql-server-5.7 server package get purged, the
  /etc/apparmor.d/usr.sbin.mysqld profile is also removed but, it is
  still loaded:

  # aa-status | grep 'mysqld'
 /usr/sbin/mysqld

  This lead to MariaDB 1.0 server not being able to start due to MySQL
  5.7 APPARMOR(7) profile that is still loaded.

  Furthermore, the mariadb-server-10.1 also comes with an APPARMOR(7)
  profile which as per it header comments is "intensionally empty to
  disable apparmor by default for newer versions of MariaDB".

  This is a big mistake as such a profile is simply wrong in regard of
  APPARMOR_PARSER(8) and as such, won't be unloaded:

  # apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
  # aa-status | grep 'mysqld'
 /usr/sbin/mysqld

  while:

  # echo "/usr/sbin/mysqld { }" > /etc/apparmor.d/usr.sbin.mysqld
  # apparmor_parser -v -R /etc/apparmor.d/usr.sbin.mysqld
  Removal succeeded for "/usr/sbin/mysqld".
  # aa-status | grep 'mysqld'

  FIX PROPOSAL

  1. When mysql-server-5.7 package is being removed/purged, the APPARMOR(7) 
profile should be unloaded and removed ranther than be simply removed.
  2. The profile provided by the mariadb-server-10.1 package should have 
correct syntax in regard of APPARMOR_PARSER(8)
  3. The mariadb-server-10.1 package postinst/postrm maintainer scripts should 
handle apparmor profile (load/unload)

  Env Ubuntu Bionic Beaver (18.04)

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

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


[Touch-packages] [Bug 1843163] Re: tracker-store crashed with SIGSEGV

2019-09-08 Thread Apport retracing service
*** This bug is a duplicate of bug 1843083 ***
https://bugs.launchpad.net/bugs/1843083

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

** Attachment removed: "CoreDump.gz"
   
https://bugs.launchpad.net/bugs/1843163/+attachment/5287297/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   
https://bugs.launchpad.net/bugs/1843163/+attachment/5287299/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   
https://bugs.launchpad.net/bugs/1843163/+attachment/5287302/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   
https://bugs.launchpad.net/bugs/1843163/+attachment/5287303/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   
https://bugs.launchpad.net/bugs/1843163/+attachment/5287304/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   
https://bugs.launchpad.net/bugs/1843163/+attachment/5287305/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   
https://bugs.launchpad.net/bugs/1843163/+attachment/5287306/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1843083
   tracker-store crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  tracker-store crashed with SIGSEGV

Status in tracker package in Ubuntu:
  New

Bug description:
  Don't know about how to help

  ProblemType: Crash
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.2.99.0-1
  ProcVersionSignature: Ubuntu 5.2.0-15.16-generic 5.2.9
  Uname: Linux 5.2.0-15-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: XFCE
  Date: Sun Sep  8 11:27:10 2019
  ExecutablePath: /usr/lib/tracker/tracker-store
  InstallationDate: Installed on 2016-02-29 (1286 days ago)
  InstallationMedia: Xubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  ProcCmdline: /usr/lib/tracker/tracker-store
  ProcEnviron:
   LANG=ca_ES.UTF-8
   PATH=(custom, no user)
   SHELL=/bin/bash
   XDG_RUNTIME_DIR=
   LANGUAGE=ca
  SegvAnalysis:
   Segfault happened at: 0x560133f35c33:cmpq   $0x0,0x8(%rdi)
   PC (0x560133f35c33) ok
   source "$0x0" ok
   destination "0x8(%rdi)" (0x0008) not located in a known VMA region 
(needed writable region)!
   Stack memory exhausted (SP below stack segment)
  SegvReason: writing NULL VMA
  Signal: 11
  SourcePackage: tracker
  StacktraceTop:
   ()
   ()
   tracker_data_commit_transaction () at 
/usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   () at /usr/lib/x86_64-linux-gnu/tracker-2.0/libtracker-data.so
   ()
  Title: tracker-store crashed with SIGSEGV
  UpgradeStatus: Upgraded to eoan on 2019-07-30 (39 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  separator:

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

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


[Touch-packages] [Bug 1839211] Re: Please upgrade to 2.2.1-1(Debian)

2019-09-08 Thread Hans Joachim Desserud
Marking as fixed based on comment above, and the version in Eoan.

** Changed in: tracker (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  Please upgrade to 2.2.1-1(Debian)

Status in tracker package in Ubuntu:
  Fix Released

Bug description:
  I am testing gnome-music [0]night, and request tracker version 2.2.0 or 
higher.
  [0] https://wiki.gnome.org/Apps/Music/Resources

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: tracker 2.1.8-2
  Uname: Linux 5.2.6-050206-generic x86_64
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Aug  6 16:10:43 2019
  InstallationDate: Installed on 2018-12-02 (247 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: tracker
  UpgradeStatus: Upgraded to eoan on 2018-12-02 (247 days ago)

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

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


[Touch-packages] [Bug 1838771] Re: http:Fix Host header in proxied https connections

2019-09-08 Thread Mathew Hodson
** Changed in: apt (Ubuntu)
   Importance: Undecided => Medium

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

Title:
  http:Fix Host header in proxied https connections

Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Bionic:
  Fix Committed
Status in apt source package in Disco:
  Fix Committed

Bug description:
  [Impact]

  Currently CONNECT requests use the name of the proxy as Host value,
  instead of the origin server's name.

  According to RFC 2616 "The Host field value MUST represent the naming
  authority of the origin server or gateway given by the original URL."

  The current implementation causes problems with some proxy vendors. This
  commit[0] fixes this.

  [0] - https://salsa.debian.org/apt-
  
team/apt/commit/86d4d98060f36c7e71c34af20a1193a75496ef72#54d3193c5d10a0032c80c3a6d3f069507265547f

  [Test Case]

  Here's one reproducer an impacted user brought to my attention:

  # /etc/environment
  http_proxy="http://internal:8080;
  https_proxy="http://interal:8080;

  To support application development activities in-house, I had to
  configure Azure CLI APT repository following the instructions from
  "https://docs.microsoft.com/en-us/cli/azure/install-azure-cli-apt?view
  =azure-cli-latest":

  $ sudo apt-get update
  $ sudo apt-get install curl apt-transport-https lsb-release gnupg
  $ curl -sL https://packages.microsoft.com/keys/microsoft.asc | \
  $ gpg --dearmor | \
  $ sudo tee /etc/apt/trusted.gpg.d/microsoft.asc.gpg > /dev/null
  $ AZ_REPO=$(lsb_release -cs)
  $ echo "deb [arch=amd64] https://packages.microsoft.com/repos/azure-cli/ $ $ 
AZ_REPO main" | \
  $ sudo tee /etc/apt/sources.list.d/azure-cli.list
  $ sudo apt update

  In the final "apt update" command, APT respects system-wide network
  proxy variables and successfully fetched Canonical repository data
  over HTTP.

  However, it was unable to fetch the newly added Microsoft packages
  repository served via HTTPS.

  By using Wireshark to examine the HTTPS request made by APT, the
  request body reveals as:

  CONNECT packages.microsoft.com:443 HTTP/1.1\r\n
  Host: internal:8080\r\n
  User-Agent: Debian APT-HTTP/1.3 (1.6.11)\r\n
  ...
  ...

  There also is an automated test case in the package that runs as part
  of autopkgtest that tests a scenario like this, see the commit.

  [Regression Potential]

  * Fix already in debian, and Eoan
  * Has been reviewed/approved by juliank
  * A test package (pre-sru) has been provided to an impacted user, and he 
confirms it solves the situation.

  [Other Info]

  # salsa
  $ git describe --contains 86d4d98060f36c7e71c34af20a1193a75496ef72
  1.9.0~8

  # rmadison apt
  => apt | 1.6.11 | bionic-updates | source, amd64, arm64, armhf, i386, 
ppc64el, s390x
  => apt | 1.8.1 | disco-updates | source, amd64, arm64, armhf, i386, ppc64el, 
s390x
  apt | 1.9.1 | eoan | source, amd64, arm64, armhf, i386, ppc64el, s390x

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

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


[Touch-packages] [Bug 1754671] Re: Full-tunnel VPN DNS leakage regression

2019-09-08 Thread Mathew Hodson
** Bug watch removed: bugzilla.gnome.org/ #766769
   https://bugzilla.gnome.org/show_bug.cgi?id=766769

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

Title:
  Full-tunnel VPN DNS leakage regression

Status in NetworkManager:
  Confirmed
Status in network-manager package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Confirmed
Status in systemd source package in Xenial:
  Invalid
Status in network-manager source package in Bionic:
  In Progress
Status in systemd source package in Bionic:
  Fix Released
Status in network-manager source package in Cosmic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released

Bug description:
  [Impact]
  When using a VPN the DNS requests might still be sent to a DNS server outside 
the VPN when they should not

  [Test case]
  1) Set up a VPN with split tunneling:
a) Configure VPN normally (set up remote host, any ports and options needed 
for the VPN to work)
b) Under the IPv4 tab: enable "Use this connection only for the resources 
on its network".
c) Under the IPv6 tab: enable "Use this connection only for the resources 
on its network".

  2) Connect to the VPN.

  3) Run 'systemd-resolve --status'; note the DNS servers configured:
a) For the VPN; under a separate link (probably tun0), note down the IP of 
the DNS server(s). Also note the name of the interface (link).
b) For the "main" connection; under the link for your ethernet or wireless 
devices (wl*, en*, whatever it may be), note down the IP of the DNS server(s). 
Also note the name of the interface (link).

  4) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  5) In a separate terminal, run 'sudo tcpdump -ni 
  port 53'; let it run.

  6) In yet another terminal, issue name resolution requests using dig:
a) For a name known to be reachable via the public network:
   'dig www.yahoo.com'
b) For a name known to be reachable only via the VPN:
   'dig '

  7) Check the output of each terminal running tcpdump. When requesting
  the public name, traffic can go through either. When requesting the
  "private" name (behind the VPN), traffic should only be going through
  the interface for the VPN. Additionally, ensure the IP receiving the
  requests for the VPN name is indeed the IP address noted above for the
  VPN's DNS server.

  If you see no traffic showing in tcpdump output when requesting a
  name, it may be because it is cached by systemd-resolved. Use a
  different name you have not tried before.

  
  [Regression potential]
  The code change the handling of DNS servers when using a VPN, we should check 
that name resolution still work whne using a VPN in different configurations

  -

  In 16.04 the NetworkManager package used to carry this patch:
  
http://bazaar.launchpad.net/~network-manager/network-manager/ubuntu/view/head:/debian/patches/Filter-DNS-servers-to-add-to-dnsmasq-based-on-availa.patch

  It fixed the DNS setup so that when I'm on the VPN, I am not sending
  unencrypted DNS queries to the (potentially hostile) local
  nameservers.

  This patch disappeared in an update. I think it was present in
  1.2.2-0ubuntu0.16.04.4 but was dropped some time later.

  This security bug exists upstream too: 
https://bugzilla.gnome.org/show_bug.cgi?id=746422
  It's not a *regression* there though, as they didn't fix it yet 
(unfortunately!)

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1754671/+subscriptions

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


[Touch-packages] [Bug 1756595] Re: disk space info inadvertently provides all installed snaps

2019-09-08 Thread Mathew Hodson
** No longer affects: apport (Ubuntu)

** No longer affects: apport (Ubuntu Bionic)

** No longer affects: apport (Ubuntu Disco)

** No longer affects: apport (Ubuntu Eoan)

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

Title:
  disk space info inadvertently provides all installed snaps

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

Bug description:
  [Impact]
  When apport is reporting a crash, it includes the output of the "df" utility, 
to list the free disk space information per mount point.

  That output nowadays will inadvertently include all snaps that the
  user may have installed, including their revision numbers.

  Here is a simple df output:
  andreas@nsn7:~$ df
  Filesystem  1K-blocksUsed Available Use% Mounted on
  udev  8119680   0   8119680   0% /dev
  tmpfs 16301561828   1628328   1% /run
  nsn7/ROOT/ubuntu433084288 2500608 430583680   1% /
  tmpfs 8150776   1   8131888   1% /dev/shm
  tmpfs5120   4  5116   1% /run/lock
  tmpfs 8150776   0   8150776   0% 
/sys/fs/cgroup
  nsn7/var/log430763136  179456 430583680   1% /var/log
  nsn7/var/tmp430583808 128 430583680   1% /var/tmp
  /dev/sda2 1032088  160336871752  16% /boot
  /dev/sda1  5232482720520528   1% /boot/efi
  nsn7/home   430651264   67584 430583680   1% /home
  nsn7/var/cache  430653312   69632 430583680   1% /var/cache
  nsn7/var/mail   430583808 128 430583680   1% /var/mail
  nsn7/var/spool  430583808 128 430583680   1% /var/spool
  tmpfs 1630152  16   1630136   1% /run/user/120
  tmpfs 100   0   100   0% 
/var/lib/lxd/shmounts
  tmpfs 100   0   100   0% 
/var/lib/lxd/devlxd
  tmpfs 1630152  36   1630116   1% 
/run/user/1000
  nsn7/lxd/containers/squid-ds216 431444096  860416 430583680   1% 
/var/lib/lxd/storage-pools/default/containers/squid-ds216
  /dev/loop0  83712   83712 0 100% 
/snap/core/4206
  /dev/loop1 102144  102144 0 100% 
/snap/git-ubuntu/402

  You can see I have the core snap at revision 4206, and git-ubuntu at
  revision 402.

  There are already many bug reports in launchpad where one can see this
  information.

  Granted, the user can review it, refuse to send this data, etc. This
  bug is about the unexpectedness of having that information in the disk
  space data.

  If the user sees a prompt like "Would you like to include disk free
  space information in your report?", or "Would you like to include the
  output of the df(1) command in your report?", that doesn't immediately
  translate to "Would you like to include disk free space information
  and a list of all installed snaps and their revision numbers in your
  report?".

  [Test case]
  Do something that triggers the apport hook and make sure you don't see snaps 
in there.

  For example, install xterm, then add exit 1 to the start of the prerm,
  then run apt remove xterm, and investigate /var/crash/xterm.0.crash
  after that (delete before running apt).

  [Regression potential]
  Fix consists of adding -x squashfs to df output, so might hide other non-snap 
squashfs images.

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

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