[Touch-packages] [Bug 1996946] Re: Memory leak on every frame when reading GIF animations

[Alejandro]

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

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

Title:
  Memory leak on every frame when reading GIF animations

Status in gdk-pixbuf package in Ubuntu:
  Confirmed

Bug description:
  There is a big memory leak when reading GIF animations.

  The issue was identified and fixed in gdk-pixbuf two (2) years ago,
  but it was released in a version grater that the available in Ubuntu
  20.04.

  At first glance, the leak appears only when a static image is
  requested, but this function is used by pixbuf's upload functions and
  calls this function internally. So the leak happens every time a GIF
  is loaded.

  Here is the commit with the fix released in version 2.41:

  https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827

  A patch is attached to this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+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 1989731] Re: Non-root user unable to change own password if pam_pwhistory is used

[Alejandro Santoyo Gonzalez]

The CIS recommendations containing the fix for this issue have been
already released [1][2].

The next step would be to fix the CIS/USG tooling so that it follows the
new guidelines.

[1] https://workbench.cisecurity.org/benchmarks/11909
[2] https://workbench.cisecurity.org/sections/1668741/recommendations/2682696

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

Title:
  Non-root user unable to change own password if pam_pwhistory is used

Status in Ubuntu Security Guide:
  In Progress
Status in pam package in Ubuntu:
  New

Bug description:
  When pam_pwhistory is in use non-root users are unable to change their
  passwords. In fact, they are able to change it but the system spits
  out an error even though the password was indeed changed.

  Reproducer:
  ---

  1. created an Ubuntu/Focal VM
  2. added a user 'test'

  sudo adduser test # used passwd '123'
  su test

  3. changed the password using 'passwd' logged in as the user 'test'

  passwd test # used passwd '1qaz2wsx'

  4. logged out from 'test' and executed

  echo 'password required pam_pwhistory.so remember=5' | sudo tee -a
  /etc/pam.d/common-password

  5. tried again to follow step 3 as user 'test' but the following
  happens:

  passwd test # used passwd '3edc4rfv' (1)
  Changing password for test.
  Current password:
  New password:
  Retype new password:
  Password has been already used. Choose another.
  passwd: Have exhausted maximum number of retries for service
  passwd: password unchanged

  However, I'm now able to log in as 'test' using the password in
  (1) (the one that was supposedly not set up due to having been
  already used) instead of the old one (the one that should be in
  place since the change process returned an error).

  6. if I comment out 'password required pam_pwhistory.so remember=5'
  then I can log in as 'test' and change the password without issues

  This behavior has been verified with the below package versioning:

  ii  libpam-cap:amd641:2.32-1  
amd64POSIX 1003.1e capabilities (PAM module)
  ii  libpam-modules:amd641.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM
  ii  libpam-modules-bin  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM - helper binaries
  ii  libpam-runtime  1.3.1-5ubuntu4.3  all 
 Runtime support for the PAM library
  ii  libpam-systemd:amd64245.4-4ubuntu3.15 
amd64system and service manager - PAM module
  ii  libpam0g:amd64  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules library

To manage notifications about this bug go to:
https://bugs.launchpad.net/usg/+bug/1989731/+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 1989731] Re: Non-root user unable to change own password if pam_pwhistory is used

[Alejandro Santoyo Gonzalez]

It seems like if the line:

'password required pam_pwhistory.so remember=5'

is added before the pam_unix line in /etc/pam.d/common-password
everything works as expected because the new password now won't match the "old" 
password that was already in the shadow file (which is what happens if 
pam_pwhistory line is set after pam_unix). 

The problem is that the CIS tooling for Ubuntu seems to be adding this line at 
the end of the file
hence causing the issue. Do we need to modify this bug in any way to ensure the 
CIS implementation is amended/fixed as needed?

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

Title:
  Non-root user unable to change own password if pam_pwhistory is used

Status in Ubuntu Security Guide:
  In Progress
Status in pam package in Ubuntu:
  New

Bug description:
  When pam_pwhistory is in use non-root users are unable to change their
  passwords. In fact, they are able to change it but the system spits
  out an error even though the password was indeed changed.

  Reproducer:
  ---

  1. created an Ubuntu/Focal VM
  2. added a user 'test'

  sudo adduser test # used passwd '123'
  su test

  3. changed the password using 'passwd' logged in as the user 'test'

  passwd test # used passwd '1qaz2wsx'

  4. logged out from 'test' and executed

  echo 'password required pam_pwhistory.so remember=5' | sudo tee -a
  /etc/pam.d/common-password

  5. tried again to follow step 3 as user 'test' but the following
  happens:

  passwd test # used passwd '3edc4rfv' (1)
  Changing password for test.
  Current password:
  New password:
  Retype new password:
  Password has been already used. Choose another.
  passwd: Have exhausted maximum number of retries for service
  passwd: password unchanged

  However, I'm now able to log in as 'test' using the password in
  (1) (the one that was supposedly not set up due to having been
  already used) instead of the old one (the one that should be in
  place since the change process returned an error).

  6. if I comment out 'password required pam_pwhistory.so remember=5'
  then I can log in as 'test' and change the password without issues

  This behavior has been verified with the below package versioning:

  ii  libpam-cap:amd641:2.32-1  
amd64POSIX 1003.1e capabilities (PAM module)
  ii  libpam-modules:amd641.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM
  ii  libpam-modules-bin  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM - helper binaries
  ii  libpam-runtime  1.3.1-5ubuntu4.3  all 
 Runtime support for the PAM library
  ii  libpam-systemd:amd64245.4-4ubuntu3.15 
amd64system and service manager - PAM module
  ii  libpam0g:amd64  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules library

To manage notifications about this bug go to:
https://bugs.launchpad.net/usg/+bug/1989731/+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 1996946] Re: Memory leak on every frame when reading GIF animations

[Alejandro]

** Description changed:

  There is a big memory leak when reading GIF animations.
  
  The issue was identified and fixed in gdk-pixbuf two (2) years ago, but
  it was released in a version grater that the available in Ubuntu 20.04.
  
  At first glance, the leak appears only when a static image is requested,
  but this function is used by pixbuf's upload functions and calls this
  function internally. So the leak happens every time a GIF is loaded.
  
- Here is the commit with the fix releases in version 2.41:
+ Here is the commit with the fix released in version 2.41:
  
  https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827
  
  A patch is attached to this message.

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

Title:
  Memory leak on every frame when reading GIF animations

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a big memory leak when reading GIF animations.

  The issue was identified and fixed in gdk-pixbuf two (2) years ago,
  but it was released in a version grater that the available in Ubuntu
  20.04.

  At first glance, the leak appears only when a static image is
  requested, but this function is used by pixbuf's upload functions and
  calls this function internally. So the leak happens every time a GIF
  is loaded.

  Here is the commit with the fix released in version 2.41:

  https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827

  A patch is attached to this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+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 1996946] [NEW] Memory leak on every frame when reading GIF animations

[Alejandro]

Public bug reported:

There is a big memory leak when reading GIF animations.

The issue was identified and fixed in gdk-pixbuf two (2) years ago, but
it was released in a version grater that the available in Ubuntu 20.04.

At first glance, the leak appears only when a static image is requested,
but this function is used by pixbuf's upload functions and calls this
function internally. So the leak happens every time a GIF is loaded.

Here is the commit with the fix releases in version 2.41:

https://gitlab.gnome.org/GNOME/gdk-
pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827

A patch is attached to this message.

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

** Patch added: "Fix memory leak"
   
https://bugs.launchpad.net/bugs/1996946/+attachment/5631282/+files/fix-animation-iterator-leak.patch

** Summary changed:

- Memory leak on every frmae when reading GIF animations
+ Memory leak on every frame when reading GIF animations

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

Title:
  Memory leak on every frame when reading GIF animations

Status in gdk-pixbuf package in Ubuntu:
  New

Bug description:
  There is a big memory leak when reading GIF animations.

  The issue was identified and fixed in gdk-pixbuf two (2) years ago,
  but it was released in a version grater that the available in Ubuntu
  20.04.

  At first glance, the leak appears only when a static image is
  requested, but this function is used by pixbuf's upload functions and
  calls this function internally. So the leak happens every time a GIF
  is loaded.

  Here is the commit with the fix releases in version 2.41:

  https://gitlab.gnome.org/GNOME/gdk-
  pixbuf/-/commit/dd3aa9ed64a0a370c8150f98e849ffc6e73da827

  A patch is attached to this message.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdk-pixbuf/+bug/1996946/+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 1989731] Re: Non-root user unable to change own password if pam_pwhistory is used

[Alejandro Santoyo Gonzalez]

** Also affects: ubuntu-security-certifications
   Importance: Undecided
   Status: New

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

Title:
  Non-root user unable to change own password if pam_pwhistory is used

Status in Ubuntu Security Certifications:
  New
Status in pam package in Ubuntu:
  New

Bug description:
  When pam_pwhistory is in use non-root users are unable to change their
  passwords. In fact, they are able to change it but the system spits
  out an error even though the password was indeed changed.

  Reproducer:
  ---

  1. created an Ubuntu/Focal VM
  2. added a user 'test'

  sudo adduser test # used passwd '123'
  su test

  3. changed the password using 'passwd' logged in as the user 'test'

  passwd test # used passwd '1qaz2wsx'

  4. logged out from 'test' and executed

  echo 'password required pam_pwhistory.so remember=5' | sudo tee -a
  /etc/pam.d/common-password

  5. tried again to follow step 3 as user 'test' but the following
  happens:

  passwd test # used passwd '3edc4rfv' (1)
  Changing password for test.
  Current password:
  New password:
  Retype new password:
  Password has been already used. Choose another.
  passwd: Have exhausted maximum number of retries for service
  passwd: password unchanged

  However, I'm now able to log in as 'test' using the password in
  (1) (the one that was supposedly not set up due to having been
  already used) instead of the old one (the one that should be in
  place since the change process returned an error).

  6. if I comment out 'password required pam_pwhistory.so remember=5'
  then I can log in as 'test' and change the password without issues

  This behavior has been verified with the below package versioning:

  ii  libpam-cap:amd641:2.32-1  
amd64POSIX 1003.1e capabilities (PAM module)
  ii  libpam-modules:amd641.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM
  ii  libpam-modules-bin  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM - helper binaries
  ii  libpam-runtime  1.3.1-5ubuntu4.3  all 
 Runtime support for the PAM library
  ii  libpam-systemd:amd64245.4-4ubuntu3.15 
amd64system and service manager - PAM module
  ii  libpam0g:amd64  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules library

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-security-certifications/+bug/1989731/+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 1989731] [NEW] Non-root user unable to change own password if pam_pwhistory is used

[Alejandro Santoyo Gonzalez]

Public bug reported:

When pam_pwhistory is in use non-root users are unable to change their
passwords. In fact, they are able to change it but the system spits out
an error even though the password was indeed changed.

Reproducer:
---

1. created an Ubuntu/Focal VM
2. added a user 'test'

sudo adduser test # used passwd '123'
su test

3. changed the password using 'passwd' logged in as the user 'test'

passwd test # used passwd '1qaz2wsx'

4. logged out from 'test' and executed

echo 'password required pam_pwhistory.so remember=5' | sudo tee -a
/etc/pam.d/common-password

5. tried again to follow step 3 as user 'test' but the following
happens:

passwd test # used passwd '3edc4rfv' (1)
Changing password for test.
Current password:
New password:
Retype new password:
Password has been already used. Choose another.
passwd: Have exhausted maximum number of retries for service
passwd: password unchanged

However, I'm now able to log in as 'test' using the password in
(1) (the one that was supposedly not set up due to having been
already used) instead of the old one (the one that should be in
place since the change process returned an error).

6. if I comment out 'password required pam_pwhistory.so remember=5'
then I can log in as 'test' and change the password without issues

This behavior has been verified with the below package versioning:

ii  libpam-cap:amd641:2.32-1  amd64 
   POSIX 1003.1e capabilities (PAM module)
ii  libpam-modules:amd641.3.1-5ubuntu4.3  amd64 
   Pluggable Authentication Modules for PAM
ii  libpam-modules-bin  1.3.1-5ubuntu4.3  amd64 
   Pluggable Authentication Modules for PAM - helper binaries
ii  libpam-runtime  1.3.1-5ubuntu4.3  all   
   Runtime support for the PAM library
ii  libpam-systemd:amd64245.4-4ubuntu3.15 amd64 
   system and service manager - PAM module
ii  libpam0g:amd64  1.3.1-5ubuntu4.3  amd64 
   Pluggable Authentication Modules library

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

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

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

Title:
  Non-root user unable to change own password if pam_pwhistory is used

Status in pam package in Ubuntu:
  New

Bug description:
  When pam_pwhistory is in use non-root users are unable to change their
  passwords. In fact, they are able to change it but the system spits
  out an error even though the password was indeed changed.

  Reproducer:
  ---

  1. created an Ubuntu/Focal VM
  2. added a user 'test'

  sudo adduser test # used passwd '123'
  su test

  3. changed the password using 'passwd' logged in as the user 'test'

  passwd test # used passwd '1qaz2wsx'

  4. logged out from 'test' and executed

  echo 'password required pam_pwhistory.so remember=5' | sudo tee -a
  /etc/pam.d/common-password

  5. tried again to follow step 3 as user 'test' but the following
  happens:

  passwd test # used passwd '3edc4rfv' (1)
  Changing password for test.
  Current password:
  New password:
  Retype new password:
  Password has been already used. Choose another.
  passwd: Have exhausted maximum number of retries for service
  passwd: password unchanged

  However, I'm now able to log in as 'test' using the password in
  (1) (the one that was supposedly not set up due to having been
  already used) instead of the old one (the one that should be in
  place since the change process returned an error).

  6. if I comment out 'password required pam_pwhistory.so remember=5'
  then I can log in as 'test' and change the password without issues

  This behavior has been verified with the below package versioning:

  ii  libpam-cap:amd641:2.32-1  
amd64POSIX 1003.1e capabilities (PAM module)
  ii  libpam-modules:amd641.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM
  ii  libpam-modules-bin  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules for PAM - helper binaries
  ii  libpam-runtime  1.3.1-5ubuntu4.3  all 
 Runtime support for the PAM library
  ii  libpam-systemd:amd64245.4-4ubuntu3.15 
amd64system and service manager - PAM module
  ii  libpam0g:amd64  1.3.1-5ubuntu4.3  
amd64Pluggable Authentication Modules library

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


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

[Touch-packages] [Bug 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs

[Alejandro Santoyo Gonzalez]

Tested 249.11-0ubuntu3.3 and DuplicateAddressDetection is now honored as
expected. No other issues were observed.

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

Title:
  Setting DuplicateAddressDetection=none doesn't disable DAD for link-
  local IPs

Status in systemd:
  Fix Released
Status in systemd package in Ubuntu:
  Fix Released
Status in systemd source package in Jammy:
  Fix Committed
Status in systemd source package in Kinetic:
  Fix Released

Bug description:
  [impact]

  manual disabling of ipv4 DAD (IACD) for static link-local address does
  not work in jammy

  [test case]

  see 'Reproducer' in original description below

  [regression potential]

  failure to disable DAD, or incorrect disabling of DAD, or networkd
  issues around parsing of DAD config parsing

  [scope]

  this is needed for j and k

  introduced upstream by commit
  1cf4ed142d6c1e2b9dc6a0bc74b6a83ae30b0f8e, first included in v249, so
  this bug does not affect impish or earlier

  fixed upstream by commit 2859932bd64d61a89f85fa027762bc16961fcf53

  [original description]

  A customer reported network disconnections on their storage
  servers when running 'netplan apply'. The culprit was that
  they have link-local addresses configured and the Duplicate
  Address Detection (DAD) mechanism was delaying the interfaces
  from coming back up.

  As a workaround we tried to disable DAD for the interfaces
  but that's not working in Ubuntu 22.04:

  I've noticed that setting DuplicateAddressDetection=none for an
  interface with a link-local address (e.g., 169.254.*) via a
  .network file added to /etc/systemd/network/ doesn't really
  disable Duplicate Address Detection.

  OS and package versions:
  
   - Description:   Ubuntu Jammy Jellyfish (development branch). Release: 
22.04
   - systemd 249.5-2ubuntu4

  Reproducer:
  ---
  1- Set up Ubuntu 22.04 VM
  2- Increase systemlog level:

    mkdir -p /etc/systemd/system/systemd-networkd.service.d/
    cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf 

[Touch-packages] [Bug 1971916] [NEW] error in the system

[Alejandro Chavez Rodriguez]

Public bug reported:

I get several messages when I start the UBUNTU OS

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3.1
ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-142-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.30
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: Thu May  5 21:42:12 2022
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3410/3430] [1002:95c2] (prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 3410/3430] 
[103c:30e9]
InstallationDate: Installed on 2022-05-02 (3 days ago)
InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 (20190227.1)
MachineType: Hewlett-Packard HP Compaq 6830s (FR883LA#ABM)
ProcEnviron:
 LANGUAGE=es_MX:es
 PATH=(custom, no user)
 LANG=es_MX.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-142-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/24/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PZD Ver. F.0F
dmi.board.name: 30E9
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 95.1D
dmi.chassis.asset.tag: CNU8504GHF
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnHewlett-Packard:bvr68PZDVer.F.0F:bd06/24/2009:svnHewlett-Packard:pnHPCompaq6830s(FR883LA#ABM):pvrF.0F:rvnHewlett-Packard:rn30E9:rvrKBCVersion95.1D:cvnHewlett-Packard:ct10:cvr:
dmi.product.family: 103C_5336AN
dmi.product.name: HP Compaq 6830s (FR883LA#ABM)
dmi.product.version: F.0F
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 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
xserver.bootTime: Thu May  5 21:31:49 2022
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs: OutputLVDS   VGA-0
xserver.version: 2:1.19.6-1ubuntu4.1~16.04.6
xserver.video_driver: radeon

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


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

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

Title:
  error in the system

Status in xorg package in Ubuntu:
  New

Bug description:
  I get several messages when I start the UBUNTU OS

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-142.146~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-142-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.30
  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: Thu May  5 21:42:12 2022
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV620/M82 [Mobility Radeon HD 
3410/3430] [1002:95c2] (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company RV620/M82 [Mobility Radeon HD 
3410/3430] [103c:30e9]
  InstallationDate: Installed on 2022-05-02 (3 days ago)
  InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release i386 
(20190227.1)
  MachineType: Hewlett-Packard HP Compaq 6830s (FR883LA#ABM)
  ProcEnviron:
   LANGUAGE=es_MX:es
   PATH=(custom, no user)
   LANG=es_MX.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-142-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/24/2009
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 68PZD Ver. F.0F
  dmi.board.name: 30E9
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Ve

[Touch-packages] [Bug 1969959] Re: Weird colors after startup (Ubuntu 22.04)

[Alejandro R. Mosteo]

Same here, trying the first stable live release of 22.04. I get a
weirdly saturated green-lime combo. Picture attached.

VGA: Intel HD Graphics 530
Monitor: HP LE2201w


** Attachment added: "Picture of screen"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969959/+attachment/5582878/+files/20220423_194416.jpg

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

Title:
  Weird colors after startup (Ubuntu 22.04)

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  I started Ubuntu 22.04 from a live pen drive. Everything seems fine,
  the usual screen with the options to "Try Ubuntu" or "Install" Ubuntu
  appears. When hitting "Try Ubuntu", the screen turns black for a
  couple of seconds and then re-appears in yellow and brown colors,
  feels like a 4 color display (white, black, yellow and orange) and I
  can hardly see anything - sending this bug report from that live
  system right after starting it up.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: xorg 1:7.7+23ubuntu2
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CasperMD5CheckResult: pass
  CasperVersion: 1.470
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 22 15:54:05 2022
  DistUpgraded: Fresh install
  DistroCodename: jammy
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation TU117 [GeForce GTX 1650] [10de:1f82]
   Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d9) (prog-if 
00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636]
  LiveMediaBuild: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419)
  MachineType: Micro-Star International Co., Ltd. MS-7C56
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz 
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/30/2020
  dmi.bios.release: 5.17
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A.40
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: B550-A PRO (MS-7C56)
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: To be filled by O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Micro-Star International Co., Ltd.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA.40:bd10/30/2020:br5.17:svnMicro-StarInternationalCo.,Ltd.:pnMS-7C56:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB550-APRO(MS-7C56):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: MS-7C56
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: 1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.110-1ubuntu1
  version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.1-1ubuntu2
  version.libgl1-mesa-glx: libgl1-mesa-glx N/A
  version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20210115-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.17-2build1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1969959/+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 1964494] Re: Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs

[Alejandro Santoyo Gonzalez]

I agree, a user-configured setting should be honored. Another thing to
consider is that according to the Jammy systemd.network man page, the 
default should be 'ipv6' so one would expect that to be a global 
default, but it gets overridden for link-local IPs due to this commit.  


[1] https://manpages.ubuntu.com/manpages/jammy/man5/systemd.network.5.html

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

Title:
  Setting DuplicateAddressDetection=none doesn't disable DAD for link-
  local IPs

Status in systemd package in Ubuntu:
  New

Bug description:
  A customer reported network disconnections on their storage 
  servers when running 'netplan apply'. The culprit was that
  they have link-local addresses configured and the Duplicate 
  Address Detection (DAD) mechanism was delaying the interfaces 
  from coming back up. 

  As a workaround we tried to disable DAD for the interfaces 
  but that's not working in Ubuntu 22.04:

  I've noticed that setting DuplicateAddressDetection=none for an
  interface with a link-local address (e.g., 169.254.*) via a 
  .network file added to /etc/systemd/network/ doesn't really 
  disable Duplicate Address Detection.

  OS and package versions:
  
   - Description:   Ubuntu Jammy Jellyfish (development branch). Release: 
22.04
   - systemd 249.5-2ubuntu4

  Reproducer:
  ---
  1- Set up Ubuntu 22.04 VM
  2- Increase systemlog level:

mkdir -p /etc/systemd/system/systemd-networkd.service.d/
cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf 

[Touch-packages] [Bug 1964494] [NEW] Setting DuplicateAddressDetection=none doesn't disable DAD for link-local IPs

[Alejandro Santoyo Gonzalez]

Public bug reported:

A customer reported network disconnections on their storage 
servers when running 'netplan apply'. The culprit was that
they have link-local addresses configured and the Duplicate 
Address Detection (DAD) mechanism was delaying the interfaces 
from coming back up. 

As a workaround we tried to disable DAD for the interfaces 
but that's not working in Ubuntu 22.04:

I've noticed that setting DuplicateAddressDetection=none for an
interface with a link-local address (e.g., 169.254.*) via a 
.network file added to /etc/systemd/network/ doesn't really 
disable Duplicate Address Detection.

OS and package versions:

 - Description: Ubuntu Jammy Jellyfish (development branch). Release: 22.04
 - systemd 249.5-2ubuntu4

Reproducer:
---
1- Set up Ubuntu 22.04 VM
2- Increase systemlog level:

  mkdir -p /etc/systemd/system/systemd-networkd.service.d/
  cat > /etc/systemd/system/systemd-networkd.service.d/10-debug.conf  /etc/systemd/system/systemd-networkd.service.d/10-debug.conf 

[Touch-packages] [Bug 1960647] [NEW] sound problem on Dell Vostro 3405

[Alejandro Arcos]

Public bug reported:

>From install xubuntu not sound on my laptop, i following
https://help.ubuntu.com/community/SoundTroubleshootingProcedure

I found with BIOS nro 146 not show features (microfone for example) and
my system show Dummy outputs devices.

After upgrade BIOS 149 this features appears!! But not sounds... attach
file with info!!!

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162
Uname: Linux 5.4.0-99-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  melange1188 F pulseaudio
 /dev/snd/controlC0:  melange1188 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Fri Feb 11 12:42:33 2022
InstallationDate: Installed on 2021-11-19 (83 days ago)
InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  melange1188 F pulseaudio
 /dev/snd/controlC0:  melange1188 F pulseaudio
Symptom_Jack: Speaker, Internal
Symptom_Type: No sound at all
Title: [Vostro 3405, Cirrus Logic Generic, Speaker, Internal] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2021
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.4.9
dmi.board.asset.tag: not specified
dmi.board.name: 0Y6PDY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 1.4.9
dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.9:bd10/12/2021:svnDellInc.:pnVostro3405:pvr1.4.9:rvnDellInc.:rn0Y6PDY:rvrA00:cvnDellInc.:ct10:cvr1.4.9:
dmi.product.family: Vostro
dmi.product.name: Vostro 3405
dmi.product.sku: 0A11
dmi.product.version: 1.4.9
dmi.sys.vendor: Dell Inc.
mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-02-11T11:47:02.161792

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug focal

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

Title:
   sound problem on Dell Vostro 3405

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  From install xubuntu not sound on my laptop, i following
  https://help.ubuntu.com/community/SoundTroubleshootingProcedure

  I found with BIOS nro 146 not show features (microfone for example)
  and my system show Dummy outputs devices.

  After upgrade BIOS 149 this features appears!! But not sounds...
  attach file with info!!!

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-99.112-generic 5.4.162
  Uname: Linux 5.4.0-99-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  melange1188 F pulseaudio
   /dev/snd/controlC0:  melange1188 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Feb 11 12:42:33 2022
  InstallationDate: Installed on 2021-11-19 (83 days ago)
  InstallationMedia: Xubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 
(20200731)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic_1 failed
  Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio 
Generic
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  melange1188 F pulseaudio
   /dev/snd/controlC0:  melange1188 F pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_Type: No sound at all
  Title: [Vostro 3405, Cirrus Logic Generic, Speaker, Internal] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/12/2021
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.9
  dmi.board.asset.tag: not specified
  dmi.board.name: 0Y6PDY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 1.4.9
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.9:bd10/12/2021:svnDellInc.:pnVostro3405:pvr1.4.9:rvnDellInc.:rn0Y6PDY:rvrA00:cvnDellInc.:ct10:cvr1.4.9:
  dmi.product.family: Vostro
  dmi.product.name: Vostro 3405
  dmi.product.sku: 0A11
  dmi.product.version: 1.4.9
  dmi.sys.vendor: Dell Inc.
  mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-02-11T11:47:02.161792

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


-- 
Mailing list: https://launchpad.net/~touch-p

[Touch-packages] [Bug 1890572] Re: USB backend never ends if the printer is not connected

[Alejandro]

Hi Till,

the issue was reported in the Apple repository:

https://github.com/apple/cups/issues/5817

I will check whether this was already fixed in OpenPrinting or not.

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  Fix Released

Bug description:
  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```

  It's also easy to test by invoking the backend by hand:

  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take hours to complete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+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 1890572] Re: USB backend never ends if the printer is not connected

[Alejandro]

Hi Sebastian,

the patch set the job state to backend error.

I don't think openprinting is the right error here. The problem is in
the backend (the USB backend) when it's not possible to communicate with
a USB printer. This usually means that the printer is not connected.

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```

  It's also easy to test by invoking the backend by hand:

  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take hours to complete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+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 1883798] Re: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different f

[Alejandro Jesus Huamantuma Anco]

Hi. I installed packettracer. Is there any solution?

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

Title:
  package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade:
  trying to overwrite shared '/usr/share/doc/libjpeg-
  turbo8/changelog.Debian.gz', which is different from other instances
  of package libjpeg-turbo8:amd64

Status in libjpeg-turbo package in Ubuntu:
  Confirmed

Bug description:
  not install file !!! packettracer

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: libjpeg-turbo8 2.0.3-0ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  AptOrdering:
   libjpeg-turbo8:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Wed Jun 17 03:37:01 2020
  DpkgTerminalLog:
   Preparing to unpack .../libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb ...
   Unpacking libjpeg-turbo8:amd64 (2.0.3-0ubuntu1.20.04.1) over 
(2.0.3-0ubuntu1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libjpeg-turbo8_2.0.3-0ubuntu1.20.04.1_amd64.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', which is different from 
other instances of package libjpeg-turbo8:amd64
  InstallationDate: Installed on 2020-06-16 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8 2.0.3-0ubuntu1 failed to install/upgrade: 
trying to overwrite shared '/usr/share/doc/libjpeg-turbo8/changelog.Debian.gz', 
which is different from other instances of package libjpeg-turbo8:amd64
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1883798/+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 1895757] Re: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

[Alejandro Santoyo Gonzalez]

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

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

Title:
  Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

Status in sudo package in Ubuntu:
  New
Status in sudo source package in Bionic:
  New

Bug description:
  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs
  running a command using 'sudo' when 'use_pty' is set in /etc/sudoers.

  Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):

  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
  3) Execute the following (test 'sudo' command):
  for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal hangs and the following backtrace is obtained:

  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
  #2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) 
at ../../../lib/util/event_poll.c:155
  #3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
  #4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
  #5  0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at 
../../src/exec_pty.c:697
  #6  exec_pty (details=details@entry=0x55d01591e0e0 , 
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
  #7  0x55d015701178 in sudo_execute (details=0x55d01591e0e0 
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
  #8  0x55d01570e15b in run_command (details=0x55d01591e0e0 
) at ../../src/sudo.c:968
  #9  0x55d0156ff9a0 in main (argc=, argv=, 
envp=) at ../../src/sudo.c:294

  A similar (most likely the same) bug has been reported here
  https://access.redhat.com/solutions/3404401.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1895757/+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 1895757] Re: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

[Alejandro Santoyo Gonzalez]

** Description changed:

  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
  a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
  
  Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
  
  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
- 3) Execute the following:
+ 3) Execute the following (test 'sudo' command):
  for i in {1..10}; do sudo -- cat /var/log/syslog; done
  
  The terminal hangs and the following backtrace is obtained:
  
  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
  #2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) 
at ../../../lib/util/event_poll.c:155
  #3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
  #4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
  #5  0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at 
../../src/exec_pty.c:697
  #6  exec_pty (details=details@entry=0x55d01591e0e0 , 
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
  #7  0x55d015701178 in sudo_execute (details=0x55d01591e0e0 
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
  #8  0x55d01570e15b in run_command (details=0x55d01591e0e0 
) at ../../src/sudo.c:968
  #9  0x55d0156ff9a0 in main (argc=, argv=, 
envp=) at ../../src/sudo.c:294
  
  A similar (most likely the same) bug has been reported here
  https://access.redhat.com/solutions/3404401.

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

Title:
  Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

Status in sudo package in Ubuntu:
  New

Bug description:
  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs
  running a command using 'sudo' when 'use_pty' is set in /etc/sudoers.

  Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):

  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
  3) Execute the following (test 'sudo' command):
  for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal hangs and the following backtrace is obtained:

  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
  #2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) 
at ../../../lib/util/event_poll.c:155
  #3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
  #4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
  #5  0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at 
../../src/exec_pty.c:697
  #6  exec_pty (details=details@entry=0x55d01591e0e0 , 
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
  #7  0x55d015701178 in sudo_execute (details=0x55d01591e0e0 
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
  #8  0x55d01570e15b in run_command (details=0x55d01591e0e0 
) at ../../src/sudo.c:968
  #9  0x55d0156ff9a0 in main (argc=, argv=, 
envp=) at ../../src/sudo.c:294

  A similar (most likely the same) bug has been reported here
  https://access.redhat.com/solutions/3404401.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1895757/+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 1895757] Re: Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

[Alejandro Santoyo Gonzalez]

** Description changed:

  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
  a command using 'sudo' when 'use_pty' is set in /etc/sudoers.
  
- Steps to reproduce:
+ Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):
  
  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
  3) Execute the following:
  for i in {1..10}; do sudo -- cat /var/log/syslog; done
  
  The terminal hangs and the following backtrace is obtained:
  
  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
  #2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) 
at ../../../lib/util/event_poll.c:155
  #3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
  #4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
  #5  0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at 
../../src/exec_pty.c:697
  #6  exec_pty (details=details@entry=0x55d01591e0e0 , 
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
  #7  0x55d015701178 in sudo_execute (details=0x55d01591e0e0 
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
  #8  0x55d01570e15b in run_command (details=0x55d01591e0e0 
) at ../../src/sudo.c:968
  #9  0x55d0156ff9a0 in main (argc=, argv=, 
envp=) at ../../src/sudo.c:294
  
  A similar (most likely the same) bug has been reported here
  https://access.redhat.com/solutions/3404401.

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

Title:
  Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

Status in sudo package in Ubuntu:
  New

Bug description:
  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs
  running a command using 'sudo' when 'use_pty' is set in /etc/sudoers.

  Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):

  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
  3) Execute the following:
  for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal hangs and the following backtrace is obtained:

  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
  #2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) 
at ../../../lib/util/event_poll.c:155
  #3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
  #4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
  #5  0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at 
../../src/exec_pty.c:697
  #6  exec_pty (details=details@entry=0x55d01591e0e0 , 
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
  #7  0x55d015701178 in sudo_execute (details=0x55d01591e0e0 
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
  #8  0x55d01570e15b in run_command (details=0x55d01591e0e0 
) at ../../src/sudo.c:968
  #9  0x55d0156ff9a0 in main (argc=, argv=, 
envp=) at ../../src/sudo.c:294

  A similar (most likely the same) bug has been reported here
  https://access.redhat.com/solutions/3404401.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1895757/+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 1895757] [NEW] Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

[Alejandro Santoyo Gonzalez]

Public bug reported:

An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs running
a command using 'sudo' when 'use_pty' is set in /etc/sudoers.

Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):

1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
Defaultsuse_pty
3) Execute the following:
for i in {1..10}; do sudo -- cat /var/log/syslog; done

The terminal hangs and the following backtrace is obtained:

(gdb) bt
#0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, timeout=-1) 
at ../sysdeps/unix/sysv/linux/poll.c:29
#1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
#2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) at 
../../../lib/util/event_poll.c:155
#3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
#4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
#5  0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at 
../../src/exec_pty.c:697
#6  exec_pty (details=details@entry=0x55d01591e0e0 , 
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
#7  0x55d015701178 in sudo_execute (details=0x55d01591e0e0 
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
#8  0x55d01570e15b in run_command (details=0x55d01591e0e0 
) at ../../src/sudo.c:968
#9  0x55d0156ff9a0 in main (argc=, argv=, 
envp=) at ../../src/sudo.c:294

A similar (most likely the same) bug has been reported here
https://access.redhat.com/solutions/3404401.

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

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

Title:
  Terminal hangs running sudo when "use_pty" is set in /etc/sudoers

Status in sudo package in Ubuntu:
  New

Bug description:
  An SSH terminal into an Ubuntu server (tested on 18.04.5) hangs
  running a command using 'sudo' when 'use_pty' is set in /etc/sudoers.

  Steps to reproduce ('sudo' version --> 1.8.21p2-3ubuntu1.2):

  1) Log in into an Ubuntu server (tested on 18.04.5 using SSH)
  2) Ensure that /etc/sudoers has the following line (add this line if not 
present)
  Defaults  use_pty
  3) Execute the following:
  for i in {1..10}; do sudo -- cat /var/log/syslog; done

  The terminal hangs and the following backtrace is obtained:

  (gdb) bt
  #0  0x7f751d5c8cc4 in __GI___poll (fds=0x55d0159917b0, nfds=1, 
timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29
  #1  0x7f751d8b146a in poll (__timeout=, __nfds=, __fds=) at /usr/include/x86_64-linux-gnu/bits/poll2.h:46
  #2  sudo_ev_scan_impl (base=base@entry=0x55d015990dc0, flags=flags@entry=0) 
at ../../../lib/util/event_poll.c:155
  #3  0x7f751d8aa74d in sudo_ev_loop_v1 (base=base@entry=0x55d015990dc0, 
flags=flags@entry=0) at ../../../lib/util/event.c:617
  #4  0x55d01570597a in del_io_events (nonblocking=nonblocking@entry=false) 
at ../../src/exec_pty.c:1537
  #5  0x55d015707b97 in pty_close (cstat=0x7ffd074d6110) at 
../../src/exec_pty.c:697
  #6  exec_pty (details=details@entry=0x55d01591e0e0 , 
cstat=cstat@entry=0x7ffd074d6110) at ../../src/exec_pty.c:1412
  #7  0x55d015701178 in sudo_execute (details=0x55d01591e0e0 
, cstat=0x7ffd074d6110) at ../../src/exec.c:391
  #8  0x55d01570e15b in run_command (details=0x55d01591e0e0 
) at ../../src/sudo.c:968
  #9  0x55d0156ff9a0 in main (argc=, argv=, 
envp=) at ../../src/sudo.c:294

  A similar (most likely the same) bug has been reported here
  https://access.redhat.com/solutions/3404401.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sudo/+bug/1895757/+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 1890572] Re: USB backend never ends if the printer is not connected

[Alejandro Claro]

We have prepared a patch for the package in Ubuntu 18.04 (CUPS 2.2.7).
We would like to request to include a solution like this for at least
Ubuntu 18.04.

We also made a pull request in the official CUPS repository:

https://github.com/apple/cups/issues/5817
https://github.com/apple/cups/pull/5818

However, we don't have plans to upgrade or change the distribution we
use (Ubuntu 18.04), and this issue is affecting us considerably.

** Bug watch added: github.com/apple/cups/issues #5817
   https://github.com/apple/cups/issues/5817

** Patch added: "usb-libusb.c.patch"
   
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+attachment/5399506/+files/usb-libusb.c.patch

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```

  It's also easy to test by invoking the backend by hand:

  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take hours to complete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+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 1890572] Re: USB backend never ends if the printer is not connected

[Alejandro Claro]

** Description changed:

- USB backend never ends if the printer is not connected. we have been
+ USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
-   fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
-   while ((g.printer = find_device(print_cb, uri)) == NULL)
-   {
- _cupsLangPrintFilter(stderr, "INFO",
-_("Waiting for printer to become available."));
- sleep(5);
-   }
+   fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
+   while ((g.printer = find_device(print_cb, uri)) == NULL)
+   {
+ _cupsLangPrintFilter(stderr, "INFO",
+ _("Waiting for printer to become available."));
+ sleep(5);
+   }
  ```
  
  It's also easy to test by invoking the backend by hand:
- 
  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file
  
  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...
  
  ```
  
- Setting a job timeout policy or stopping the job by hand are not options
- for us. We can have job that take up to an hour to complete.
+ Setting a work timeout policy or manually stopping work are not options
+ for us. We may have jobs that take up to an hour to complete.

** Description changed:

  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```
  
  It's also easy to test by invoking the backend by hand:
  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file
  
  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
- DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
+ DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...
  
  ```
  
  Setting a work timeout policy or manually stopping work are not options
  for us. We may have jobs that take up to an hour to complete.

** Description changed:

  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.printer = find_device(print_cb, uri)) == NULL)
    {
  _cupsLangPrintFilter(stderr, "INFO",
  _("Waiting for printer to become available."));
  sleep(5);
    }
  ```
  
  It's also easy to test by invoking the backend by hand:
  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file
  
  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Printer/Model?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
- 
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...
  
  ```
  
- Setting a work timeout policy or manually stopping work are not options
+ Setting a job timeout policy or manually stopping work are not options
  for us. We may have jobs that take up to an hour to complete.

** Description changed:

  USB backend never ends if the printer is not connected. We have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:
  
  ```
    fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
    while ((g.p

[Touch-packages] [Bug 1890572] [NEW] USB backend never ends if the printer is not connected

[Alejandro Claro]

Public bug reported:

USB backend never ends if the printer is not connected. we have been
able to identify a infinity loop in print_device function in usb-
libusb.c file:

```
  fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
  while ((g.printer = find_device(print_cb, uri)) == NULL)
  {
_cupsLangPrintFilter(stderr, "INFO",
 _("Waiting for printer to become available."));
sleep(5);
  }
```

It's also easy to test by invoking the backend by hand:


```
# export DEVICE_URI='usb://Printer/Model?serial=?'
# /usr/lib/cups/backend/usb 0 root title 1 '' data.file

DEBUG: Loading USB quirks from "/usr/share/cups/usb".
DEBUG: Loaded 159 quirks.
DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.

DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
DEBUG: libusb_get_device_list=6
INFO: Waiting for printer to become available.
...

```

Setting a job timeout policy or stopping the job by hand are not options
for us. We can have job that take up to an hour to complete.

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

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

Title:
  USB backend never ends if the printer is not connected

Status in cups package in Ubuntu:
  New

Bug description:
  USB backend never ends if the printer is not connected. we have been
  able to identify a infinity loop in print_device function in usb-
  libusb.c file:

  ```
fprintf(stderr, "DEBUG: Printing on printer with URI: %s\n", uri);
while ((g.printer = find_device(print_cb, uri)) == NULL)
{
  _cupsLangPrintFilter(stderr, "INFO",
 _("Waiting for printer to become available."));
  sleep(5);
}
  ```

  It's also easy to test by invoking the backend by hand:

  
  ```
  # export DEVICE_URI='usb://Printer/Model?serial=?'
  # /usr/lib/cups/backend/usb 0 root title 1 '' data.file

  DEBUG: Loading USB quirks from "/usr/share/cups/usb".
  DEBUG: Loaded 159 quirks.
  DEBUG: Printing on printer with URI: usb://Brother/PJ-773?serial=?
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.

  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  DEBUG: libusb_get_device_list=6
  INFO: Waiting for printer to become available.
  ...

  ```

  Setting a job timeout policy or stopping the job by hand are not
  options for us. We can have job that take up to an hour to complete.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1890572/+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 1883408] [NEW] package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new':

[Alejandro]

Public bug reported:

no deja de molesrae

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cups-client 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jun 13 06:32:25 2020
ErrorMessage: no se pudieron copiar los datos extraídos de 
'./usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de 
flujo inesperado
InstallationDate: Installed on 2020-06-13 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Dell Inc. Latitude E6400
Papersize: letter
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: cups
Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se 
pudieron copiar los datos extraídos de './usr/bin/lpoptions' a 
'/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A34
dmi.board.name: 0G866N
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0G866N:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package focal

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

Title:
  package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se
  pudieron copiar los datos extraídos de './usr/bin/lpoptions' a
  '/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado

Status in cups package in Ubuntu:
  New

Bug description:
  no deja de molesrae

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: cups-client 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jun 13 06:32:25 2020
  ErrorMessage: no se pudieron copiar los datos extraídos de 
'./usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de 
flujo inesperado
  InstallationDate: Installed on 2020-06-13 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude E6400
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: cups
  Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se 
pudieron copiar los datos extraídos de './usr/bin/lpoptions' a 
'/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A34
  dmi.board.name: 0G866N
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0G866N:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6400
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1883408/+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 1883409] [NEW] package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se pudieron copiar los datos extraídos de './usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new':

[Alejandro]

Public bug reported:

no deja de molesrae

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: cups-client 2.3.1-9ubuntu1.1
ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
Uname: Linux 5.4.0-37-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.2
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sat Jun 13 06:32:25 2020
ErrorMessage: no se pudieron copiar los datos extraídos de 
'./usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de 
flujo inesperado
InstallationDate: Installed on 2020-06-13 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
MachineType: Dell Inc. Latitude E6400
Papersize: letter
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: cups
Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se 
pudieron copiar los datos extraídos de './usr/bin/lpoptions' a 
'/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 06/04/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A34
dmi.board.name: 0G866N
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0G866N:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude E6400
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package focal

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

Title:
  package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se
  pudieron copiar los datos extraídos de './usr/bin/lpoptions' a
  '/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado

Status in cups package in Ubuntu:
  New

Bug description:
  no deja de molesrae

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: cups-client 2.3.1-9ubuntu1.1
  ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41
  Uname: Linux 5.4.0-37-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.2
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sat Jun 13 06:32:25 2020
  ErrorMessage: no se pudieron copiar los datos extraídos de 
'./usr/bin/lpoptions' a '/usr/bin/lpoptions.dpkg-new': fin de fichero o de 
flujo inesperado
  InstallationDate: Installed on 2020-06-13 (1 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  Lpstat: Error: command ['lpstat', '-v'] failed with exit code 1: lpstat: No 
destinations added.
  MachineType: Dell Inc. Latitude E6400
  Papersize: letter
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic 
root=UUID=1bcab7a8-d4a0-4bae-adfc-3e1e7fa36a9c ro quiet splash vt.handoff=7
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: cups
  Title: package cups-client 2.3.1-9ubuntu1.1 failed to install/upgrade: no se 
pudieron copiar los datos extraídos de './usr/bin/lpoptions' a 
'/usr/bin/lpoptions.dpkg-new': fin de fichero o de flujo inesperado
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 06/04/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A34
  dmi.board.name: 0G866N
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA34:bd06/04/2013:svnDellInc.:pnLatitudeE6400:pvr:rvnDellInc.:rn0G866N:rvr:cvnDellInc.:ct8:cvr:
  dmi.product.name: Latitude E6400
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1883409/+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

[F. Alejandro Osso]

Just to thank you all.  I just hit this problem, solved it and in the
process learned something about apparmor.

-- 
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 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

[Alejandro Claro]

Good morning Murray,

we performed some test and everything looks fine.

Thank you very much.

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

Title:
  Errors when extracting ZIP files. It can not differentiate between
  files and directories

Status in libarchive package in Ubuntu:
  Fix Released
Status in libarchive source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  The bionic version has a known problem when reading file entries in ZIP 
files, where it incorrectly identifies directories and files entries.

  * Test case
  $ wget 
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+attachment/5268728/+files/example.zip
  $ bsdtar -vxf example.zip
  $ ls -l

  The 'ABCD_1234' and 'empty' entries should be directories

  * Regression potential
  Check that extracting zips from bsdtar or nautilus work without issue

  

  It has been confirmed that the previous and following versions
  (3.3.1+) do not have this problem and the library handles the ZIP
  files correctly.

  Is it possible to include a newer version of libarchive (3.3.1+) in
  Bionic?

  This problem is seriously affecting some of our systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+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 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

[Alejandro Claro]

Thank you Brian,

We are going to be testing it during this week. I will let you know the
results.

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

Title:
  Errors when extracting ZIP files. It can not differentiate between
  files and directories

Status in libarchive package in Ubuntu:
  Fix Released
Status in libarchive source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  The bionic version has a known problem when reading file entries in ZIP 
files, where it incorrectly identifies directories and files entries.

  * Test case
  $ wget 
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+attachment/5268728/+files/example.zip
  $ bsdtar -vxf example.zip
  $ ls -l

  The 'ABCD_1234' and 'empty' entries should be directories

  * Regression potential
  Check that extracting zips from bsdtar or nautilus work without issue

  

  It has been confirmed that the previous and following versions
  (3.3.1+) do not have this problem and the library handles the ZIP
  files correctly.

  Is it possible to include a newer version of libarchive (3.3.1+) in
  Bionic?

  This problem is seriously affecting some of our systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+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 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

[Alejandro Claro]

HI Sebastien,

Sure. Here is a zip file that it's very easy to use to reproduce the
defect. The defect s not in the bsdtar, it's in libarchive. However,
since bsdtar depends on libarchive, this can be used to demonstrate the
problem as someone reports in the GitHub issue report:

https://github.com/libarchive/libarchive/issues/822

If you try to extract the content with bsdtar:

#  bsdtar -vxf example.zip

You will see and error, and if you look to the result in the filesystem,
that 'ABCD_1234' and 'empty' are created as files instead of
directories. If you try the same operation using unzip in other
directory (or after cleaning the previous operation):

# unzip example.zip

You will see the right result (ABCD_1234 and empty directories).

Thanks for take care of this,
Alejandro


** Attachment added: "example.zip"
   
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+attachment/5268728/+files/example.zip

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

Title:
  Errors when extracting ZIP files. It can not differentiate between
  files and directories

Status in libarchive package in Ubuntu:
  New

Bug description:
  The specific version included in Ubuntu 18.04 (libarchive 3.2.2) is
  the only version that presents the problem. This version has a known
  problem when reading file entries in ZIP files, where it incorrectly
  identifies directories and files entries.

  It has been confirmed that the previous and following versions
  (3.3.1+) do not have this problem and the library handles the ZIP
  files correctly.

  Is it possible to include a newer version of libarchive (3.3.1+) in
  Bionic?

  This problem is seriously affecting some of our systems.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libarchive/+bug/1830629/+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 1830629] Re: Errors when extracting ZIP files. It can not differentiate between files and directories

[Alejandro Claro]

One important note here,

The defect is only present in version 3.2.2 (Bionic official version
now). Previous and next version do work properly.

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

Title:
  Errors when extracting ZIP files. It can not differentiate between
  files and directories

Status in libarchive package in Ubuntu:
  New

Bug description:
  The specific version included in Ubuntu 18.04 (libarchive 3.2.2) is
  the only version that presents the problem. This version has a known
  problem when reading file entries in ZIP files, where it incorrectly
  identifies directories and files entries.

  It has been confirmed that the previous and following versions
  (3.3.1+) do not have this problem and the library handles the ZIP
  files correctly.

  Is it possible to include a newer version of libarchive (3.3.1+) in
  Bionic?

  This problem is seriously affecting some of our systems.

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

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

Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

[Alejandro]

I ended up uninstalling everything and installing the 18.04 from
sctratch.Thanks for your help


On Thursday, April 11, 2019, 12:26:08 PM GMT-3, José Enrique 
<1773...@bugs.launchpad.net> wrote:  
 
 Hola creo recordar que utilicé estos comandos:
sudo mv / usr / share / dbus-1 / system- servicios / org.freedesktop
.systemd1. servicio / usr / share / dbus-1 / system- servicios /
org.freedesktop .systemd1. Servicio. bak
sudo apt-get install -f
sudo apt dist-upgrade
sudo apt autoremove

A mi me funcionó correctamente, pero no lo almacené.
Puede ser otro problema con el mismo resultado.
Otra solución, que apliqué en un laptop fue sacar un back-up de los
archivos de usuario, documentos, descargas...
Y reinstalar la nueva versión desde 0
Sañudos

El jue., 11 abr. 2019 0:45, loluchayjose <1773...@bugs.launchpad.net>
escribió:

> Bueno, ninguna de las soluciones aquí está muy clara. Una de ellas es
> "sudo apt purge gdm etc."... "etc." que?
>
> Varios dicen "borrar"... borrar como?
>
> Tu dijiste: "I solved problem sttoping services and erasing systemd-shim
> upon console.
> After I could updating my pc, also, from console"... Qué servicios
> paraste, y como? Tengo que hacerlo en Safe Mode?
>
> Uno de los últimos dice: "The upload of systemd that was purported to
> fix this bug report was superseded by a security update of systemd so
> the fix is no longer available." Así que por lo que se ve, esa solucion
> ya no sirve.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1792241).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
>  upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
>  Fix Released
> Status in systemd-shim package in Ubuntu:
>  Won't Fix
> Status in systemd source package in Bionic:
>  Triaged
> Status in systemd-shim source package in Bionic:
>  Won't Fix
> Status in systemd source package in Cosmic:
>  Fix Released
> Status in systemd-shim source package in Cosmic:
>  Won't Fix
>
> Bug description:
>  [Impact]
>
>    * Some systems fail to upgrade due to conflicts between systemd and
>  the (now removed from the archive) systemd-shim / upstart.
>
>    * Instead of trying to work out what's the problem in ordering /
>  removal of diverts, ensure that systemd is never unpacked whilst
>  systemd-shim/upstart are still on disk. Thus declare conflicts against
>  systemd-shim/upstart packages in systemd package.
>
>  [Test Case]
>
>    * monitor drop-off of upgrades with below reported problem
>
>    * Check that it is possible to upgrade to bionic's libpam-systemd
>  from xenial with systemd-shim installed on xenial, ie.
>
>  lxc launch ubuntu-daily:xenial test-shim-upgrade
>  lxc exec test-shim-upgrade
>  apt update
>  apt install systemd-shim
>  wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
>  apt install ./systemd-shim_10-3_amd64.deb
>  sed 's/xenial/bionic/' -i /etc/apt/sources.list
>  apt update
>  apt install systemd
>
>  this currently passes, however, systemd-shim remains installed. It
>  should be removed instead. Apt install systemd should have lines like
>  this:
>
>  The following packages will be REMOVED:
>    systemd-shim
>  ...
>  Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>  ...
>
>
>  [Regression Potential]
>
>    * systemd-shim/upstart are both removed and not supported in bionic,
>  thus forcing their removal via conflicts should bring the system into
>  an expected state.
>
>  [Other Info]
>
>    * original bug report
>
>  $ sudo apt upgrade
>  Reading package lists... Done
>  Building dependency tree
>  Reading state information... Done
>  Calculating upgrade... Done
>  The following packages will be REMOVED:
>    systemd-shim
>  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
>  1 not fully installed or removed.
>  After this operation, 71.7 kB disk space will be freed.
>  Do you want to continue? [Y/n] y
>  (Reading database ... 63 files and directories currently installed.)
>  Removing systemd-shim (9-1bzr4ubuntu1) ...
>  Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>  dpkg-divert: error: rename involves overwriting
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
>    different file
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd',
> not allowed
>  dpkg: error processing package systemd-shim (--remove):
>    subprocess installed post-removal script returned error exit status 2
>  Errors were encountered while processing:
>    systemd-shim
>  E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>  Commenting out the dpkg-divert in systemd-shim's postrm solved this
>  for me and I was about to conti

[Touch-packages] [Bug 1814481] Re: bluetooth keyboard not working

[Alejandro Mery]

I can confirm it works out of the box using the latest Ubuntu "disco"
live stick.

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

Title:
  bluetooth keyboard not working

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~

[Touch-packages] [Bug 1814481] Re: bluetooth keyboard not working

[Alejandro Mery]

I did test with bluez ppa and didn't change anything.

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

Title:
  bluetooth keyboard not working

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  I recently got a nice mechanical bluetooth keyboard to use on my
  thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04
  live, but on my installed xubuntu 18.04, 18.04 live and 18.10 live it
  only works after calling `sudo evtest /dev/input/eventN`.

  Xorg.0.log shows it is detected fine, and I can't see anything there
  after temporarily getting it to work using the evtest trick.

  18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
  [18.515] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.515] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.515] (**) Keychron K1: always reports core events
  [18.515] (**) Option "Device" "/dev/input/event23"
  [18.515] (**) Option "_source" "server/udev"
  [18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.516] (II) event23 - Keychron K1: device is a keyboard
  [18.516] (II) event23 - Keychron K1: device removed
  [18.524] (II) libinput: Keychron K1: needs a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
  [18.524] (**) Option "AccelerationScheme" "none"
  [18.524] (**) Keychron K1: (accel) selected scheme none/0
  [18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
  [18.524] (**) Keychron K1: (accel) acceleration threshold: 4
  [18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
  [18.524] (II) event23 - Keychron K1: device is a keyboard
  [18.524] (**) Keychron K1: Applying InputClass "libinput keyboard 
catchall"
  [18.524] (II) Using input driver 'libinput' for 'Keychron K1'
  [18.524] (**) Keychron K1: always reports core events
  [18.524] (**) Option "Device" "/dev/input/event23"
  [18.524] (**) Option "_source" "_driver/libinput"
  [18.524] (II) libinput: Keychron K1: is a virtual subdevice
  [18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
  [18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
  [18.524] (**) Option "xkb_model" "pc105"
  [18.524] (**) Option "xkb_layout" "us"
  [18.524] (**) Option "xkb_variant" "altgr-intl"
  [18.524] (WW) Option "xkb_options" requires a string value

  I've also tried using the latest 4.20.6 from mainline-ppa and the
  latest bluetooth/bluz ppa without success.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
  Uname: Linux 4.15.0-45-lowlatency x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Sun Feb  3 23:51:29 2019
  DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo HD Graphics 620 [17aa:224b]
  InstallationDate: Installed on 2017-07-24 (559 days ago)
  InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215)
  MachineType: LENOVO 20HFCTO1WW
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
  dmi.bios.date: 09/14/2018
  dmi.bios.vendor: LENOVO
  dmi.bios.version: N1WET51W (1.30 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20HFCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40709 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T470s
  dmi.product.name: 20HFCTO1WW
  dmi.product.version: ThinkPad T470s
  dmi.sys.vendor: LENOVO
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.95-1~18.04.1
  version.libgl1-mesa

[Touch-packages] [Bug 1814481] [NEW] bluetooth keyboard not working

[Alejandro Mery]

Public bug reported:

I recently got a nice mechanical bluetooth keyboard to use on my
thinkpad. It works fine with Android, Windows 10 and Xubuntu 19.04 live,
but on my installed xubuntu 18.04, 18.04 live and 18.10 live it only
works after calling `sudo evtest /dev/input/eventN`.

Xorg.0.log shows it is detected fine, and I can't see anything there
after temporarily getting it to work using the evtest trick.

18.515] (II) config/udev: Adding input device Keychron K1 
(/dev/input/event23)
[18.515] (**) Keychron K1: Applying InputClass "libinput keyboard catchall"
[18.515] (II) Using input driver 'libinput' for 'Keychron K1'
[18.515] (**) Keychron K1: always reports core events
[18.515] (**) Option "Device" "/dev/input/event23"
[18.515] (**) Option "_source" "server/udev"
[18.516] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
[18.516] (II) event23 - Keychron K1: device is a keyboard
[18.516] (II) event23 - Keychron K1: device removed
[18.524] (II) libinput: Keychron K1: needs a virtual subdevice
[18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
[18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
MOUSE, id 20)
[18.524] (**) Option "AccelerationScheme" "none"
[18.524] (**) Keychron K1: (accel) selected scheme none/0
[18.524] (**) Keychron K1: (accel) acceleration factor: 2.000
[18.524] (**) Keychron K1: (accel) acceleration threshold: 4
[18.524] (II) event23 - Keychron K1: is tagged by udev as: Keyboard
[18.524] (II) event23 - Keychron K1: device is a keyboard
[18.524] (**) Keychron K1: Applying InputClass "libinput keyboard catchall"
[18.524] (II) Using input driver 'libinput' for 'Keychron K1'
[18.524] (**) Keychron K1: always reports core events
[18.524] (**) Option "Device" "/dev/input/event23"
[18.524] (**) Option "_source" "_driver/libinput"
[18.524] (II) libinput: Keychron K1: is a virtual subdevice
[18.524] (**) Option "config_info" 
"udev:/sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:0255.0007/input/input24/event23"
[18.524] (II) XINPUT: Adding extended input device "Keychron K1" (type: 
KEYBOARD, id 21)
[18.524] (**) Option "xkb_model" "pc105"
[18.524] (**) Option "xkb_layout" "us"
[18.524] (**) Option "xkb_variant" "altgr-intl"
[18.524] (WW) Option "xkb_options" requires a string value

I've also tried using the latest 4.20.6 from mainline-ppa and the latest
bluetooth/bluz ppa without success.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-45.48-lowlatency 4.15.18
Uname: Linux 4.15.0-45-lowlatency x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
Date: Sun Feb  3 23:51:29 2019
DistUpgraded: 2019-02-03 21:49:33,752 DEBUG /openCache(), new cache size 92675
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.2.18, 4.15.0-45-lowlatency, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo HD Graphics 620 [17aa:224b]
InstallationDate: Installed on 2017-07-24 (559 days ago)
InstallationMedia: Xubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215)
MachineType: LENOVO 20HFCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-lowlatency 
root=UUID=8f8366ae-4d29-44cf-9b85-f83f1771eab1 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2019-02-03 (0 days ago)
dmi.bios.date: 09/14/2018
dmi.bios.vendor: LENOVO
dmi.bios.version: N1WET51W (1.30 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20HFCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrN1WET51W(1.30):bd09/14/2018:svnLENOVO:pn20HFCTO1WW:pvrThinkPadT470s:rvnLENOVO:rn20HFCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T470s
dmi.product.name: 20HFCTO1WW
dmi.product.version: ThinkPad T470s
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1~18.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
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

** Affects: xorg (U

Re: [Touch-packages] [Bug 1773859] Please test proposed package

[Alejandro]

José Enrique,disculpa y gracias por contestarme.Quería pedirte si me puedes 
contar brevemente ¿cómo pudiste borrar el systemd-shim package?No se cómo 
accederloMuchas graciasAlejandro   
  -   
  -  
 -  


  -  
 - -
José Enrique <1773...@bugs.launchpad.net>
   
  - 
  - Nov 19 at 2:01 PM

   
   - To avertaness...@yahoo.com
  - 

Message body
Thanks a lot for your help. I resolved my problem erasing systemd-shim and
updating.
I'll try new solution in another pc.
Kind regards


  From: José Enrique <1773...@bugs.launchpad.net>
 To: avertaness...@yahoo.com 
 Sent: Tuesday, November 27, 2018 3:01 PM
 Subject: Re: [Bug 1773859] Please test proposed package
   
Lo siento Alejandro, no soy Lucas
 Saludos

El mar., 27 nov. 2018 18:51, Alejandro <1773...@bugs.launchpad.net>
escribió:

> Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make
> this test in the last weeks I will make them as soon as
> possibleRegardsAlejandro
>
>      From: Łukasz Zemczak <1773...@bugs.launchpad.net>
>  To: avertaness...@yahoo.com
>  Sent: Tuesday, November 20, 2018 9:21 AM
>  Subject: [Bug 1773859] Please test proposed package
>
> Hello Kees, or anyone else affected,
>
> Accepted systemd into bionic-proposed. The package will build now and be
> available at
> https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few
> hours, and then in the -proposed repository.
>
> Please help us by testing this new package.  See
> https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
> to enable and use -proposed.  Your feedback will aid us getting this
> update out to other Ubuntu users.
>
> If this package fixes the bug for you, please add a comment to this bug,
> mentioning the version of the package you tested and change the tag from
> verification-needed-bionic to verification-done-bionic. If it does not
> fix the bug for you, please add a comment stating that, and change the
> tag to verification-failed-bionic. In either case, without details of
> your testing we will not be able to proceed.
>
> Further information regarding the verification process can be found at
> https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
> advance for helping!
>
> N.B. The updated package will be released to -updates after the bug(s)
> fixed by this package have been verified and the package has been in
> -proposed for a minimum of 7 days.
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1796221).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
>  upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
>  Fix Released
> Status in systemd-shim package in Ubuntu:
>  Won't Fix
> Status in systemd source package in Bionic:
>  Fix Committed
> Status in systemd-shim source package in Bionic:
>  Won't Fix
> Status in systemd source package in Cosmic:
>  Fix Released
> Status in systemd-shim source package in Cosmic:
>  Won't Fix
>
> Bug description:
>  [Impact]
>
>    * Some systems fail to upgrade due to conflicts between systemd and
>  the (now removed from the archive) systemd-shim / upstart.
>
>    * Instead of trying to work out what's the problem in ordering /
>  removal of diverts, ensure that systemd is never unpacked whilst
>  systemd-shim/upstart are still on disk. Thus declare conflicts against
>  systemd-shim/upstart packages in systemd package.
>
>  [Test Case]
>
>    * monitor drop-off of upgrades with below reported problem
>
>    * Check that it is possible to upgrade to bionic's libpam-systemd
>  from xenial with systemd-shim installed on xenial, ie.
>
>  lxc launch ubuntu-daily:xenial test-shim-upgrade
>  lxc exec test-shim-upgrade
>  apt update
>  apt install systemd-shim
>  wget
> https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
>  apt install ./systemd-shim_10-3_amd64.deb
>  sed 's/xenial/bionic/' -i /etc/apt/sources.list
>  apt update
>  apt install systemd
>
>  this currently passes, however, systemd-shim remains installed. It
>  should be removed instead. Apt install systemd should have lines like
>  this:
>
>  The following packages will be REMOVED:
>    systemd-shim
>  ...
>  Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>  ...
>
>
>  [Regression Potential]
>
>    * systemd-shim/upstart are both removed and not supported in bionic,
>  thus forcing thei

Re: [Touch-packages] [Bug 1773859] Please test proposed package

[Alejandro]

Dear Łukasz ZemczakThank you for all your replies.Sorry I couldn't make
this test in the last weeks I will make them as soon as
possibleRegardsAlejandro

  From: Łukasz Zemczak <1773...@bugs.launchpad.net>
 To: avertaness...@yahoo.com 
 Sent: Tuesday, November 20, 2018 9:21 AM
 Subject: [Bug 1773859] Please test proposed package
   
Hello Kees, or anyone else affected,

Accepted systemd into bionic-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/systemd/237-3ubuntu10.10 in a few
hours, and then in the -proposed repository.

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

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

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

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

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1796221).
https://bugs.launchpad.net/bugs/1773859

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

   * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

   * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

   * monitor drop-off of upgrades with below reported problem

   * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial, ie.

  lxc launch ubuntu-daily:xenial test-shim-upgrade
  lxc exec test-shim-upgrade
  apt update
  apt install systemd-shim
  wget 
https://deb.debian.org/debian/pool/main/s/systemd-shim/systemd-shim_10-3_amd64.deb
  apt install ./systemd-shim_10-3_amd64.deb 
  sed 's/xenial/bionic/' -i /etc/apt/sources.list
  apt update
  apt install systemd

  this currently passes, however, systemd-shim remains installed. It
  should be removed instead. Apt install systemd should have lines like
  this:

  The following packages will be REMOVED:
    systemd-shim
  ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  ...

  
  [Regression Potential]

   * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]

   * original bug report

  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packages will be REMOVED:
    systemd-shim
  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
  1 not fully installed or removed.
  After this operation, 71.7 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 63 files and directories currently installed.)
  Removing systemd-shim (9-1bzr4ubuntu1) ...
  Removing 'diversion of 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to 
/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd by 
systemd-shim'
  dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
    different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed
  dpkg: error processing package systemd-shim (--remove):
   subprocess installed post-removal script returned error exit status 2
  Errors were encountered while processing:
   systemd-shim
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Commenting out the dpkg-divert in systemd-shim's postrm solved this
  for me and I was about to continue th

[Touch-packages] [Bug 1769299] Re: universal access zoom unusable

[Alejandro Fabre]

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

Have the same problem.

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

Title:
  universal access zoom unusable

Status in gnome-shell package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  New

Bug description:
  
  Filed by mark on behalf of low vision user Ken.   Ken is able to read 56 
point type without magnification at normal reading distance and can barely read 
the universal access "large text" from a distance of about 2.5 inches from a 
26inch monitor at 1360x768.   So he really needs magnification and a lot more 
than the 2x default I used here for testing.   We do not live in the same town 
so providing additional details would be slow.

  Turned on zoom from the universal access button on top panel.
  Default settings were used including Zoom = 2.0, screen part = full

  Several areas are corrupted.  These zoom and scroll separately from
  the rest of the screen and in a way that severely impairs use as
  portions may not ever be visible.   Portions of these subwindows
  cannot be used because you have to move the mouse off them to be able
  see them so you can either see or click but not both.

  These areas are:
- The top panel
- The left panel (launcher)  (intermittently)
- pull down menus, particularly the universal access pull down from the top 
panel

  
  Also, the zoom randomly every couple seconds. jumps to a different position 
without the user's consent.   This appeared to be because text was printed by a 
program running in the terminal window (long apt-get install) but continued to 
happen even when that window was minimized and even when that program stopped 
printing.

  These problems persisted with all the other zoom modes.   One mode,
  however, created new bugs.  With "magnifier extends outside of
  screen", you lose the ability to see the top and left panels at all;
  you can pan over where they would be but they are not drawn.   Can't
  open the pulldown menu since there is no icon, so who knows how it
  would be rendered.

  These bugs made it very difficult to get screenshots, especially with
  the defective screenshot program gnome-screenshot which ships with
  system.   Also, the bug-reporting program did not permitted attaching
  additional screenshots once spectacle was installed.

  Ubuntu 18.04, fresh install, only a few added packages (ham radio
  related, chrome).  Not using wayland, though a wayland session runs
  concurrently with X11 even though no one has logged in with wayland.

  Another problem in making the bug report is the irresponsible practice
  of failing to identify the software being used.   The accessability
  man in circle menu does not have a heading to tell you what program is
  run for the accessability menu or any of the functions thus invoked.
  Nor does the settings.  And there is no tooltip, popup, or about menu
  item to convey this information to the user.   And running a diff on
  ps doesn't show any new processes started when zoom is turned on.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat May  5 00:04:35 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation G98 [GeForce 8400 GS Rev. 2] [10de:06e4] (rev a1) 
(prog-if 00 [VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] G98 [GeForce 8400 GS 
Rev. 2] [1462:1163]
  InstallationDate: Installed on 2018-05-05 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Dell Inc. OptiPlex 760
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=6a7e27f6-5135-461e-9e6b-fea68756ed37 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/29/2009
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0M858N
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 6
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd04/29/2009:svnDellInc.:pnOptiPlex760:pvr:rvnDellInc.:rn0M858N:rvrA01:cvnDellInc.:ct6:cvr:
  dmi.product.name: OptiPlex 760
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-m

Re: [Touch-packages] [Bug 1773859] Re: upgrades to 18.04 fail

[Alejandro]

Histill having the same problem  with the "systemd-shim"I don't know how
to fix it May be I will format everything and reinstall Ubuntu 18
againgreetings

  From: José Enrique <1773...@bugs.launchpad.net>
 To: avertaness...@yahoo.com 
 Sent: Thursday, October 18, 2018 3:10 AM
 Subject: Re: [Bug 1773859] Re: upgrades to 18.04 fail
   
Hy, in this moment I can't update my laptop or install any package or
program
Greetings

El mié., 17 oct. 2018 23:11, Brian Murray  escribió:

> ** Tags added: bugpattern-written
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1792241).
> https://bugs.launchpad.net/bugs/1773859
>
> Title:
>  upgrades to 18.04 fail
>
> Status in systemd package in Ubuntu:
>  Fix Released
> Status in systemd-shim package in Ubuntu:
>  Won't Fix
> Status in systemd source package in Bionic:
>  In Progress
> Status in systemd-shim source package in Bionic:
>  Won't Fix
> Status in systemd source package in Cosmic:
>  Fix Released
> Status in systemd-shim source package in Cosmic:
>  Won't Fix
>
> Bug description:
>  [Impact]
>
>    * Some systems fail to upgrade due to conflicts between systemd and
>  the (now removed from the archive) systemd-shim / upstart.
>
>    * Instead of trying to work out what's the problem in ordering /
>  removal of diverts, ensure that systemd is never unpacked whilst
>  systemd-shim/upstart are still on disk. Thus declare conflicts against
>  systemd-shim/upstart packages in systemd package.
>
>  [Test Case]
>
>    * monitor drop-off of upgrades with below reported problem
>
>    * Check that it is possible to upgrade to bionic's libpam-systemd
>  from xenial with systemd-shim installed on xenial.
>
>  [Regression Potential]
>
>    * systemd-shim/upstart are both removed and not supported in bionic,
>  thus forcing their removal via conflicts should bring the system into
>  an expected state.
>
>  [Other Info]
>
>    * original bug report
>
>
>  $ sudo apt upgrade
>  Reading package lists... Done
>  Building dependency tree
>  Reading state information... Done
>  Calculating upgrade... Done
>  The following packages will be REMOVED:
>    systemd-shim
>  0 upgraded, 0 newly installed, 1 to remove and 0 not upgraded.
>  1 not fully installed or removed.
>  After this operation, 71.7 kB disk space will be freed.
>  Do you want to continue? [Y/n] y
>  (Reading database ... 63 files and directories currently installed.)
>  Removing systemd-shim (9-1bzr4ubuntu1) ...
>  Removing 'diversion of
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service to
> /usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd
> by systemd-shim'
>  dpkg-divert: error: rename involves overwriting
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
>    different file
> '/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd',
> not allowed
>  dpkg: error processing package systemd-shim (--remove):
>    subprocess installed post-removal script returned error exit status 2
>  Errors were encountered while processing:
>    systemd-shim
>  E: Sub-process /usr/bin/dpkg returned an error code (1)
>
>  Commenting out the dpkg-divert in systemd-shim's postrm solved this
>  for me and I was about to continue the upgrade.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1773859/+subscriptions
>

-- 
You received this bug notification because you are subscribed to a
duplicate bug report (1796221).
https://bugs.launchpad.net/bugs/1773859

Title:
  upgrades to 18.04 fail

Status in systemd package in Ubuntu:
  Fix Released
Status in systemd-shim package in Ubuntu:
  Won't Fix
Status in systemd source package in Bionic:
  In Progress
Status in systemd-shim source package in Bionic:
  Won't Fix
Status in systemd source package in Cosmic:
  Fix Released
Status in systemd-shim source package in Cosmic:
  Won't Fix

Bug description:
  [Impact]

  * Some systems fail to upgrade due to conflicts between systemd and
  the (now removed from the archive) systemd-shim / upstart.

  * Instead of trying to work out what's the problem in ordering /
  removal of diverts, ensure that systemd is never unpacked whilst
  systemd-shim/upstart are still on disk. Thus declare conflicts against
  systemd-shim/upstart packages in systemd package.

  [Test Case]

  * monitor drop-off of upgrades with below reported problem

  * Check that it is possible to upgrade to bionic's libpam-systemd
  from xenial with systemd-shim installed on xenial.

  [Regression Potential]

  * systemd-shim/upstart are both removed and not supported in bionic,
  thus forcing their removal via conflicts should bring the system into
  an expected state.

  [Other Info]
  
  * original bug report

  
  $ sudo apt upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following packa

[Touch-packages] [Bug 1756846] Re: bridge-utils incompatible with ifupdown on bionic

[Alejandro Mery]

I had to install ifupdown manually, and got 0.8.17ubuntu1. everything
fine now, but shouldn't this package be pulled in automatically somehow?

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in ifupdown package in Ubuntu:
  Fix Released

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 0 B/30.1 kB of archives.
  After this operation, 119 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 251318 files and directories currently installed.)
  Removing ifupdown (0.8.16ubuntu2) ...
  Selecting previously unselected package bridge-utils.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
  Unpacking bridge-utils (1.5-15ubuntu1) ...
  Setting up bridge-utils (1.5-15ubuntu1) ...
  Processing triggers for man-db (2.8.2-1) ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ifupdown/+bug/1756846/+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 1756846] Re: bridge-utils incompatible with ifupdown on bionic

[Alejandro Mery]

thanks @albrt, I didn't know that one

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in bridge-utils package in Ubuntu:
  Confirmed

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 0 B/30.1 kB of archives.
  After this operation, 119 kB disk space will be freed.
  Do you want to continue? [Y/n] y
  (Reading database ... 251318 files and directories currently installed.)
  Removing ifupdown (0.8.16ubuntu2) ...
  Selecting previously unselected package bridge-utils.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
  Unpacking bridge-utils (1.5-15ubuntu1) ...
  Setting up bridge-utils (1.5-15ubuntu1) ...
  Processing triggers for man-db (2.8.2-1) ...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bridge-utils/+bug/1756846/+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 1756846] [NEW] bridge-utils incompatible with ifupdown on bionic

[Alejandro Mery]

Public bug reported:

$ apt-cache policy ifupdown bridge-utils
ifupdown:
  Installed: (none)
  Candidate: 0.8.16ubuntu2
  Version table:
 0.8.16ubuntu2 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
bridge-utils:
  Installed: 1.5-15ubuntu1
  Candidate: 1.5-15ubuntu1
  Version table:
 *** 1.5-15ubuntu1 500
500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status

$ sudo apt-get install ifupdown
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  rdnssd
The following packages will be REMOVED
  bridge-utils
The following NEW packages will be installed
  ifupdown
0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
Need to get 55.2 kB of archives.
After this operation, 119 kB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
Fetched 55.2 kB in 0s (1,280 kB/s)  
(Reading database ... 251311 files and directories currently installed.)
Removing bridge-utils (1.5-15ubuntu1) ...
Selecting previously unselected package ifupdown.
(Reading database ... 251286 files and directories currently installed.)
Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
Unpacking ifupdown (0.8.16ubuntu2) ...
Setting up ifupdown (0.8.16ubuntu2) ...
Processing triggers for ureadahead (0.100.0-20) ...
ureadahead will be reprofiled on next reboot
Processing triggers for systemd (237-3ubuntu4) ...
Processing triggers for man-db (2.8.2-1) ...

$ sudo apt-get install bridge-utils
Reading package lists... Done
Building dependency tree   
Reading state information... Done
Suggested packages:
  ifupdown
The following packages will be REMOVED
  ifupdown
The following NEW packages will be installed
  bridge-utils
0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
Need to get 0 B/30.1 kB of archives.
After this operation, 119 kB disk space will be freed.
Do you want to continue? [Y/n] y
(Reading database ... 251318 files and directories currently installed.)
Removing ifupdown (0.8.16ubuntu2) ...
Selecting previously unselected package bridge-utils.
(Reading database ... 251286 files and directories currently installed.)
Preparing to unpack .../bridge-utils_1.5-15ubuntu1_amd64.deb ...
Unpacking bridge-utils (1.5-15ubuntu1) ...
Setting up bridge-utils (1.5-15ubuntu1) ...
Processing triggers for man-db (2.8.2-1) ...

** Affects: bridge-utils (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  bridge-utils incompatible with ifupdown on bionic

Status in bridge-utils package in Ubuntu:
  New

Bug description:
  $ apt-cache policy ifupdown bridge-utils
  ifupdown:
Installed: (none)
Candidate: 0.8.16ubuntu2
Version table:
   0.8.16ubuntu2 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  bridge-utils:
Installed: 1.5-15ubuntu1
Candidate: 1.5-15ubuntu1
Version table:
   *** 1.5-15ubuntu1 500
  500 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ sudo apt-get install ifupdown
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
rdnssd
  The following packages will be REMOVED
bridge-utils
  The following NEW packages will be installed
ifupdown
  0 to upgrade, 1 to newly install, 1 to remove and 0 not to upgrade.
  Need to get 55.2 kB of archives.
  After this operation, 119 kB of additional disk space will be used.
  Do you want to continue? [Y/n] y
  Get:1 http://gb.archive.ubuntu.com/ubuntu bionic/main amd64 ifupdown amd64 
0.8.16ubuntu2 [55.2 kB]
  Fetched 55.2 kB in 0s (1,280 kB/s)  
  (Reading database ... 251311 files and directories currently installed.)
  Removing bridge-utils (1.5-15ubuntu1) ...
  Selecting previously unselected package ifupdown.
  (Reading database ... 251286 files and directories currently installed.)
  Preparing to unpack .../ifupdown_0.8.16ubuntu2_amd64.deb ...
  Unpacking ifupdown (0.8.16ubuntu2) ...
  Setting up ifupdown (0.8.16ubuntu2) ...
  Processing triggers for ureadahead (0.100.0-20) ...
  ureadahead will be reprofiled on next reboot
  Processing triggers for systemd (237-3ubuntu4) ...
  Processing triggers for man-db (2.8.2-1) ...

  $ sudo apt-get install bridge-utils
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Suggested packages:
ifupdown
  The following packages will be REMOVED
ifupdown
  The following NEW packages will be installed
bridge-utils
  0 to upgrade, 1 to n

[Touch-packages] [Bug 1733332] [NEW] package linux-image-4.4.0-101-generic 4.4.0-101.124 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Alejandro Rivosecchi]

Public bug reported:

Description:Ubuntu 16.04.3 LTS
Release:16.04

linux-image-4.4.0-101-generic:
  Installed: 4.4.0-101.124
  Candidate: 4.4.0-101.124
  Version table:
 *** 4.4.0-101.124 500
500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages
500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 Packages
100 /var/lib/dpkg/status

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-101-generic 4.4.0-101.124
ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
Uname: Linux 4.4.0-98-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.12
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  murdoxix   1717 F pulseaudio
 /dev/snd/controlC1:  murdoxix   1717 F pulseaudio
 /dev/snd/seq:timidity   1034 F timidity
Date: Mon Nov 20 11:36:10 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=5826ccbf-827f-4c93-8d27-f65bb8332b78
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
MachineType: Gigabyte Technology Co., Ltd. H61M-S2P-B3
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=cec7b457-0ea2-47ae-ab3c-8ac4874b082a ro quiet splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
RfKill:
 
SourcePackage: initramfs-tools
Title: package linux-image-4.4.0-101-generic 4.4.0-101.124 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/27/2012
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F6
dmi.board.name: H61M-S2P-B3
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF6:bd03/27/2012:svnGigabyteTechnologyCo.,Ltd.:pnH61M-S2P-B3:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnH61M-S2P-B3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: H61M-S2P-B3
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


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

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

Title:
  package linux-image-4.4.0-101-generic 4.4.0-101.124 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Description:  Ubuntu 16.04.3 LTS
  Release:  16.04

  linux-image-4.4.0-101-generic:
Installed: 4.4.0-101.124
Candidate: 4.4.0-101.124
Version table:
   *** 4.4.0-101.124 500
  500 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://archive.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-101-generic 4.4.0-101.124
  ProcVersionSignature: Ubuntu 4.4.0-98.121-generic 4.4.90
  Uname: Linux 4.4.0-98-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.12
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  murdoxix   1717 F pulseaudio
   /dev/snd/controlC1:  murdoxix   1717 F pulseaudio
   /dev/snd/seq:timidity   1034 F timidity
  Date: Mon Nov 20 11:36:10 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=5826ccbf-827f-4c93-8d27-f65bb8332b78
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  MachineType: Gigabyte Technology Co., Ltd. H61M-S2P-B3
  ProcFB: 0 radeondrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-98-generic 
root=UUID=cec7b457-0ea2-47ae-ab3c-8ac4874b082a ro quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.14
  RfKill:
   
  SourcePackage: initramfs-tools
  Title: package linux-image-4.4.0-101-generic 4.4.0-101.124 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/27/2012
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F6
  dmi.board.name: H61M-S2P-B3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.ve

[Touch-packages] [Bug 1716848] [NEW] package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Alejandro]

Public bug reported:

Bluetooth no working in my laptop. Therefore, it's not possible to
detect other devices or transfer archives.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: bluez 5.37-0ubuntu5.1
ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
Uname: Linux 4.4.0-93-generic i686
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: i386
Date: Wed Sep 13 08:01:25 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-04-10 (520 days ago)
InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 (20160217.1)
InterestingModules: bnep bluetooth
MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-93-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.24
SourcePackage: bluez
Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-12-03 (283 days ago)
dmi.bios.date: 08/17/2007
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.22
dmi.board.name: 30CC
dmi.board.vendor: Quanta
dmi.board.version: 79.1D
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd08/17/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.1D:cvnQuanta:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv6500 Notebook PC
dmi.product.version: Rev 1
dmi.sys.vendor: Hewlett-Packard
hciconfig:

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


** Tags: apport-package i386 xenial

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

Title:
  package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in bluez package in Ubuntu:
  New

Bug description:
  Bluetooth no working in my laptop. Therefore, it's not possible to
  detect other devices or transfer archives.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5.1
  ProcVersionSignature: Ubuntu 4.4.0-93.116-generic 4.4.79
  Uname: Linux 4.4.0-93-generic i686
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: i386
  Date: Wed Sep 13 08:01:25 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-04-10 (520 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release i386 
(20160217.1)
  InterestingModules: bnep bluetooth
  MachineType: Hewlett-Packard HP Pavilion dv6500 Notebook PC
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-93-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SourcePackage: bluez
  Title: package bluez 5.37-0ubuntu5.1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-12-03 (283 days ago)
  dmi.bios.date: 08/17/2007
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: F.22
  dmi.board.name: 30CC
  dmi.board.vendor: Quanta
  dmi.board.version: 79.1D
  dmi.chassis.type: 10
  dmi.chassis.vendor: Quanta
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrF.22:bd08/17/2007:svnHewlett-Packard:pnHPPaviliondv6500NotebookPC:pvrRev1:rvnQuanta:rn30CC:rvr79.1D:cvnQuanta:ct10:cvrN/A:
  dmi.product.name: HP Pavilion dv6500 Notebook PC
  dmi.product.version: Rev 1
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1716848/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04

[Alejandro R. Mosteo]

#27, just to add to my previous post a few months ago, removing xserver-
xorg-input-libinput AND installing xserver-xorg-input-evdev fixed it for
me in several machines. What I additionally found is that the latter
package does not come preinstalled and just removing libinput will leave
you mouse/keyboardless in X.

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

Title:
  Mouse acceleration significantly reduced after upgrade to 17.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My external Logitech USB mouse was behaving nicely under 16.10 but
  after upgrade to 17.04 it has slowed down to a crawl. Settings
  slidebars are set at the maximum acceleration, but it only affects the
  touch pad, the mouse is extremely slow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1638301] Re: systemctl start auto-completion shows error

[Alejandro Comisario]

Still happening on ubuntu 16.04 systemd 229-4ubuntu19, any workaround ?

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

Title:
  systemctl start  auto-completion shows error

Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  When i try to auto-complete the "systemctl start " the
  following error message is shown in bash:

  Unit org.freedesktop.network1.busname could not be found.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: systemd 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-26.28-generic 4.8.0
  Uname: Linux 4.8.0-26-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Nov  1 10:42:37 2016
  InstallationDate: Installed on 2015-06-20 (499 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. Dell System Vostro 3450
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-26-generic 
root=UUID=7468e7be-a2e1-48dd-ba72-244c33698364 ro cgroup_enable=memory 
swapaccount=1 quiet splash vt.handoff=7
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (12 days ago)
  dmi.bios.date: 07/22/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A06
  dmi.board.name: 0GG0VM
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnDellInc.:bvrA06:bd07/22/2011:svnDellInc.:pnDellSystemVostro3450:pvr:rvnDellInc.:rn0GG0VM:rvrA01:cvnDellInc.:ct8:cvr0.1:
  dmi.product.name: Dell System Vostro 3450
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1638301/+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 1706305] [NEW] package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Alejandro Martínez ballesteros]

Public bug reported:

I don't know what is the problem. I only have read the notification
telling me I have a problem in ubuntu.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1
ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
Uname: Linux 4.10.0-28-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
Architecture: amd64
Date: Tue Jul 25 12:18:43 2017
Dependencies:
 gcc-6-base 6.3.0-12ubuntu2
 libc6 2.24-9ubuntu2.2
 libgcc1 1:6.3.0-12ubuntu2
 libnl-3-200 3.2.29-0ubuntu2.1
DuplicateSignature:
 package:libnl-genl-3-200:amd64:3.2.29-0ubuntu2.1
 Setting up mythes-en-au (2.1-5.4) ...
 dpkg: error processing package libnl-genl-3-200:amd64 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-07-24 (0 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: libnl3
Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-package zesty

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

Title:
  package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting configuration

Status in libnl3 package in Ubuntu:
  New

Bug description:
  I don't know what is the problem. I only have read the notification
  telling me I have a problem in ubuntu.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1
  ProcVersionSignature: Ubuntu 4.10.0-28.32-generic 4.10.17
  Uname: Linux 4.10.0-28-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  Architecture: amd64
  Date: Tue Jul 25 12:18:43 2017
  Dependencies:
   gcc-6-base 6.3.0-12ubuntu2
   libc6 2.24-9ubuntu2.2
   libgcc1 1:6.3.0-12ubuntu2
   libnl-3-200 3.2.29-0ubuntu2.1
  DuplicateSignature:
   package:libnl-genl-3-200:amd64:3.2.29-0ubuntu2.1
   Setting up mythes-en-au (2.1-5.4) ...
   dpkg: error processing package libnl-genl-3-200:amd64 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-07-24 (0 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: libnl3
  Title: package libnl-genl-3-200:amd64 3.2.29-0ubuntu2.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1706305/+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 1692671] Re: intel driver fails to reenable display

[Alejandro Mery]

** Attachment added: "dmesg"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881545/+files/dmesg.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+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 1692671] Re: intel driver fails to reenable display

[Alejandro Mery]

** Attachment added: "lspci -v"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881544/+files/lspci.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+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 1692671] Re: intel driver fails to reenable display

[Alejandro Mery]

** Attachment added: "sudo get-edid | parse-edid"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+attachment/4881543/+files/edid.txt

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+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 1692671] [NEW] intel driver fails to reenable display

[Alejandro Mery]

Public bug reported:

if the display is sent to sleep it won't wake up. If I go to tty1 or
tty2 I'm pulled back to tty7 (?) within seconds.

sometimes if I ctrl-alt-del I'm sent back to the login screen and from
there I can resume the session.

everything was working fine with my previous (1920x1080) display, but
since I switched to a 3840x2160 display the only reliable solution to
get the computer back from blanking is pressing the power button. I can
then see the shutdown "splash" and after powering it back again
everything is back to normal. until it blanks the screen again obviusly

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Mon May 22 19:16:43 2017
InstallationDate: Installed on 2015-12-27 (512 days ago)
InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: xorg
UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

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


** Tags: amd64 apport-bug xenial

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

Title:
  intel driver fails to reenable display

Status in xorg package in Ubuntu:
  New

Bug description:
  if the display is sent to sleep it won't wake up. If I go to tty1 or
  tty2 I'm pulled back to tty7 (?) within seconds.

  sometimes if I ctrl-alt-del I'm sent back to the login screen and from
  there I can resume the session.

  everything was working fine with my previous (1920x1080) display, but
  since I switched to a 3840x2160 display the only reliable solution to
  get the computer back from blanking is pressing the power button. I
  can then see the shutdown "splash" and after powering it back again
  everything is back to normal. until it blanks the screen again
  obviusly

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Mon May 22 19:16:43 2017
  InstallationDate: Installed on 2015-12-27 (512 days ago)
  InstallationMedia: Xubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (389 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1692671/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04

[Alejandro R. Mosteo]

Just to confirm that removing xserver-xorg-input-libinput solved the
issue without [immediately evident] side effects. I had to reconfigure
the mouse speed in the GUI.

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

Title:
  Mouse acceleration significantly reduced after upgrade to 17.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My external Logitech USB mouse was behaving nicely under 16.10 but
  after upgrade to 17.04 it has slowed down to a crawl. Settings
  slidebars are set at the maximum acceleration, but it only affects the
  touch pad, the mouse is extremely slow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1682193] Re: Mouse acceleration significantly reduced after upgrade to 17.04

[Alejandro R. Mosteo]

@loplop, surprisingly in my default installation the only mouse option
related to our problem in settings is labeled as "Mouse Speed" (Below
System Settings -> Mouse & Touchpad). Whatever it does behind the scenes
I can't but guess; in my duplicate bug #1683435 I reported seeing "Accel
Speed" in the capabilities listed by xinput. I too am used to being able
to differentiate between acceleration and precision somehow in other
desktops/OSs.

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

Title:
  Mouse acceleration significantly reduced after upgrade to 17.04

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  My external Logitech USB mouse was behaving nicely under 16.10 but
  after upgrade to 17.04 it has slowed down to a crawl. Settings
  slidebars are set at the maximum acceleration, but it only affects the
  touch pad, the mouse is extremely slow.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1682193/+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 1685443] [NEW] package pulseaudio-module-bluetooth 1:9.0-2ubuntu2.1 failed to install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è consigliato install

[Alejandro Figliolia]

Public bug reported:


alejandro@alejandro-HP-Pavilion-15-Notebook-PC:~$ sudo apt-get remove 
pulseaudio-module-bluetooth
[sudo] password di alejandro: 
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
I seguenti pacchetti saranno RIMOSSI:
  pulseaudio-module-bluetooth
0 aggiornati, 0 installati, 1 da rimuovere e 0 non aggiornati.
1 non completamente installati o rimossi.
Dopo quest'operazione, verranno liberati 285 kB di spazio su disco.
Continuare? [S/n] s
dpkg: errore nell'elaborare il pacchetto pulseaudio-module-bluetooth (--remove):
 il pacchetto si trova in uno stato di inconsistenza grave:
 è necessario installarlo nuovamente prima di rimuoverlo
Si sono verificati degli errori nell'elaborazione:
 pulseaudio-module-bluetooth
E: Sub-process /usr/bin/dpkg returned an error code (1)
alejandro@alejandro-HP-Pavilion-15-Notebook-PC:~$ sudo apt-get install 
pulseaudio-module-bluetooth
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
pulseaudio-module-bluetooth is already the newest version (1:9.0-2ubuntu2.1).
0 aggiornati, 0 installati, 0 da rimuovere e 0 non aggiornati.
1 non completamente installati o rimossi.
È necessario scaricare 0 B/56,5 kB di archivi.
Dopo quest'operazione, verranno occupati 0 B di spazio su disco.
Continuare? [S/n] s
dpkg: errore nell'elaborare il pacchetto pulseaudio-module-bluetooth 
(--configure):
 il pacchetto si trova in uno stato di inconsistenza critico: è consigliato
 installarlo nuovamente prima di tentare la configurazione.
Si sono verificati degli errori nell'elaborazione:
 pulseaudio-module-bluetooth
E: Sub-process /usr/bin/dpkg returned an error code (1)
alejandro@alejandro-HP-Pavilion-15-Notebook-PC:~$ sudo apt-get purge 
pulseaudio-module-bluetooth
Lettura elenco dei pacchetti... Fatto
Generazione albero delle dipendenze   
Lettura informazioni sullo stato... Fatto
I seguenti pacchetti saranno RIMOSSI:
  pulseaudio-module-bluetooth*
0 aggiornati, 0 installati, 1 da rimuovere e 0 non aggiornati.
1 non completamente installati o rimossi.
Dopo quest'operazione, verranno liberati 285 kB di spazio su disco.
Continuare? [S/n] s
dpkg: errore nell'elaborare il pacchetto pulseaudio-module-bluetooth (--remove):
 il pacchetto si trova in uno stato di inconsistenza grave:
 è necessario installarlo nuovamente prima di rimuoverlo
Si sono verificati degli errori nell'elaborazione:
 pulseaudio-module-bluetooth
E: Sub-process /usr/bin/dpkg returned an error code (1)

ProblemType: Package
DistroRelease: Ubuntu 16.10
Package: pulseaudio-module-bluetooth 1:9.0-2ubuntu2.1
ProcVersionSignature: Ubuntu 4.8.0-46.49-generic 4.8.17
Uname: Linux 4.8.0-46-generic x86_64
ApportVersion: 2.20.3-0ubuntu8.2
AptOrdering: NULL: ConfigurePending
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  alejandro   2009 F.... pulseaudio
 /dev/snd/controlC0:  alejandro   2009 F pulseaudio
Date: Sat Apr 22 08:09:48 2017
DpkgTerminalLog:
 dpkg: errore nell'elaborare il pacchetto pulseaudio-module-bluetooth 
(--configure):
  il pacchetto si trova in uno stato di inconsistenza critico: è consigliato
  installarlo nuovamente prima di tentare la configurazione.
ErrorMessage: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
InstallationDate: Installed on 2017-04-13 (8 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 dpkg 1.18.10ubuntu1
 apt  1.3.4
SourcePackage: pulseaudio
Title: package pulseaudio-module-bluetooth 1:9.0-2ubuntu2.1 failed to 
install/upgrade: il pacchetto si trova in uno stato di inconsistenza critico: è 
consigliato  installarlo nuovamente prima di tentare la configurazione.
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/26/2014
dmi.bios.vendor: Insyde
dmi.bios.version: F.67
dmi.board.asset.tag: Type2 - Board Asset Tag
dmi.board.name: 2166
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 29.42
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.67:bd11/26/2014:svnHewlett-Packard:pnHPPavilion15NotebookPC:pvr08961030410620100:rvnHewlett-Packard:rn2166:rvr29.42:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion 15 Notebook PC
dmi.product.version: 08961030410620100
dmi.sys.vendor: Hewlett-Packard

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


** Tags: amd64 apport-package yakkety

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded p

[Touch-packages] [Bug 1683435] [NEW] Mouse speed/acceleration ignored in 17.04

[Alejandro R. Mosteo]

Public bug reported:

After upgrading to 17.04 my mouse (a plain Logitech USB-PS/2 Optical
Mouse) is much slower and nothing I do changes its speed.

Tried through the settings GUI, using xset and using xinput. Nothing
seems to do anything. The only thing that offers some feedback is
xinput, that complaints about a value out of range:

$ xinput --set-prop 8 289 2
X Error of failed request:  BadValue (integer parameter out of range for 
operation)
  Major opcode of failed request:  131 (XInputExtension)
  Minor opcode of failed request:  57 ()
  Value in failed request:  0x121
  Serial number of failed request:  19
  Current serial number in output stream:  20
where 8 is the device id, 289 is the "libinput Accel Speed", and 2 is the 
desired multiplier:

$ xinput --list --short
⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Logitech USB-PS/2 Optical Mouse   id=8[slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ Media Center Ed. eHome Infrared Remote Transceiver (185b:3020)id=9
[slave  keyboard (3)]
↳ LITEON Technology USB Multimedia Keyboard id=10   [slave  keyboard (3)]
↳ Nuvoton w836x7hg Infrared Remote Transceiver  id=11   [slave  
keyboard (3)]

Basically I can set that value in the range 0..1, with no effect
(although it is reported correctly by xinput --list-props), or outside
and getting the error. Likewise, changing values with xset shows them as
changed, but the mouse is oblivious to it.


Finally, I tried in a live USB and at least via the settings GUI there's no 
noticeable difference between either extreme setting of the slider.

ProblemType: Bug
DistroRelease: Ubuntu 17.04
Package: xorg 1:7.7+16ubuntu3
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  375.39  Tue Jan 31 20:47:00 
PST 2017
 GCC version:  gcc version 6.3.0 20170406 (Ubuntu 6.3.0-12ubuntu2)
.proc.driver.nvidia.warnings.fbdev:
 Your system is not currently configured to drive a VGA console
 on the primary VGA device. The NVIDIA Linux graphics driver
 requires the use of a text-mode VGA console. Use of other console
 drivers including, but not limited to, vesafb, may result in
 corruption and stability problems, and is not supported.
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.4-0ubuntu4
Architecture: amd64
BootLog: root: clean, 577548/2097152 files, 6029465/8388608 blocks
CompizPlugins: 
[core,bailer,detection,composite,opengl,decor,compiztoolbox,resize,regex,mousepoll,move,grid,vpswitch,animation,wall,gnomecompat,imgpng,place,snap,expo,unitymtgrabhandles,workarounds,fade,session,ezoom,scale,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop:
 
Date: Mon Apr 17 19:06:07 2017
DistUpgraded: 2017-04-17 14:10:56,823 DEBUG icon theme changed, re-reading
DistroCodename: zesty
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 NVIDIA Corporation GK208 [GeForce GT 730] [10de:1287] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 730] [1043:8525]
InstallationDate: Installed on 2014-03-13 (1130 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Tranquil PC IXLs
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-19-generic 
root=UUID=bb84f1b8-0976-403f-a1da-0a4d0b7de950 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: Upgraded to zesty on 2017-04-17 (0 days ago)
dmi.bios.date: 10/07/2011
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BLH6710H.86A.0132.2011.1007.1505
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DH67CF
dmi.board.vendor: Intel Corporation
dmi.board.version: AAG10215-204
dmi.chassis.type: 3
dmi.chassis.vendor: Tranquil PC
dmi.modalias: 
dmi:bvnIntelCorp.:bvrBLH6710H.86A.0132.2011.1007.1505:bd10/07/2011:svnTranquilPC:pnIXLs:pvr:rvnIntelCorporation:rnDH67CF:rvrAAG10215-204:cvnTranquilPC:ct3:cvr:
dmi.product.name: IXLs
dmi.sys.vendor: Tranquil PC
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.76-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.3-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl

[Touch-packages] [Bug 1677667] [NEW] package linux-image-extra-4.4.0-64-generic 4.4.0-64.85 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Alejandro Arcos]

Public bug reported:

the problem appears after reboot system

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-extra-4.4.0-64-generic 4.4.0-64.85
ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
Uname: Linux 4.4.0-71-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
AudioDevicesInUse:
 ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
  USERPID ACCESS COMMAND
 /dev/snd/controlC0:  administrador   1594 F pulseaudio
Date: Thu Mar 30 12:41:47 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=f2970602-8d5d-4112-811b-547f53012e43
PccardctlIdent: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload 
cannot be preloaded (cannot open shared object file): ignored.
PccardctlStatus: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload 
cannot be preloaded (cannot open shared object file): ignored.
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=646bc068-284c-4372-9187-99883ca0face ro quiet splash vt.handoff=7
PulseList:
 Error: command ['pacmd', 'list'] failed with exit code 1: ERROR: ld.so: object 
'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot open 
shared object file): ignored.
 No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
RfKill: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot 
be preloaded (cannot open shared object file): ignored.
SourcePackage: initramfs-tools
Title: package linux-image-extra-4.4.0-64-generic 4.4.0-64.85 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/15/2009
dmi.bios.vendor: Intel Corp.
dmi.bios.version: DPP3510J.86A.0572.2009.0715.2346
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: DP35DP
dmi.board.vendor: Intel Corporation
dmi.board.version: AAD81073-205
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrDPP3510J.86A.0572.2009.0715.2346:bd07/15/2009:svn:pn:pvr:rvnIntelCorporation:rnDP35DP:rvrAAD81073-205:cvn:ct3:cvr:

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


** Tags: amd64 apport-package xenial

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

Title:
  package linux-image-extra-4.4.0-64-generic 4.4.0-64.85 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools
  exited with return code 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  the problem appears after reboot system

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-extra-4.4.0-64-generic 4.4.0-64.85
  ProcVersionSignature: Ubuntu 4.4.0-71.92-generic 4.4.49
  Uname: Linux 4.4.0-71-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  AudioDevicesInUse:
   ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot be 
preloaded (cannot open shared object file): ignored.
USERPID ACCESS COMMAND
   /dev/snd/controlC0:  administrador   1594 F pulseaudio
  Date: Thu Mar 30 12:41:47 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=f2970602-8d5d-4112-811b-547f53012e43
  PccardctlIdent: ERROR: ld.so: object 'libesets_pac.so' from 
/etc/ld.so.preload cannot be preloaded (cannot open shared object file): 
ignored.
  PccardctlStatus: ERROR: ld.so: object 'libesets_pac.so' from 
/etc/ld.so.preload cannot be preloaded (cannot open shared object file): 
ignored.
  ProcFB: 0 nouveaufb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-71-generic 
root=UUID=646bc068-284c-4372-9187-99883ca0face ro quiet splash vt.handoff=7
  PulseList:
   Error: command ['pacmd', 'list'] failed with exit code 1: ERROR: ld.so: 
object 'libesets_pac.so' from /etc/ld.so.preload cannot be preloaded (cannot 
open shared object file): ignored.
   No PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.8
  RfKill: ERROR: ld.so: object 'libesets_pac.so' from /etc/ld.so.preload cannot 
be preloaded (cannot open shared object file): ignored.
  SourcePackage: initramfs-tools
  Title: package linux-image-extra-4.4.0-64-generic 4.4.0-64.85 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/15/2009
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: DPP3510J.86A.0572.2009.0715.2346
  dmi.board.asset.tag: Base Board Asset Ta

[Touch-packages] [Bug 1672401] Re: Screen is black for too long during login to Unity8

[Alejandro J. Cura]

@saviq: I'm not convinced the unity8-greeter should be the "real" login
experience for unity8 on classic.

When we start shipping u8 as the default we would still want to keep u7
installed as a fallback, but we can't if we install u8-greeter.

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

Title:
  Screen is black for too long during login to Unity8

Status in Canonical System Image:
  Triaged
Status in Unity System Compositor:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  This makes me worry there's something gone wrong on every login.

  It's only this slow on a cold boot. It's somewhat faster on a second
  login.

  It'd be nice for there to be something like:

  * Splash screen
  * Progress bar
  * User's wallpaper (blurred?)

  during this time.

  Maybe it's faster on bare metal, but I'm waiting a while in a Qemu VM.

  == Note ==

  The experience might differ depending on whether you use unity-greeter
  (X11-based, default in 17.04) or unity8-greeter (not installed by
  default yet), which is better suited for this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672401/+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 1672392] Re: Install an app from Ubuntu Terminal and it doesn't show up in the app drawer

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Changed in: canonical-devices-system-image
Milestone: None => u8c-2

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

Title:
  Install an app from Ubuntu Terminal and it doesn't show up in the app
  drawer

Status in Canonical System Image:
  Triaged
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  On a fresh Zesty Qemu VM, I installed dconf-editor from the archive
  using the terminal.

    sudo apt install dconf-editor

  and it didn't show up in the app drawer, either in the scrollable list
  or searching by name.

  After a reboot (can't logout due to bug #1670657) dconf-editor is
  there.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1672392/+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 1628589] Re: Need better session management for apps

[Alejandro J. Cura]

** Changed in: ubuntu-app-launch (Ubuntu)
 Assignee: (unassigned) => Ted Gould (ted)

** Changed in: ubuntu-app-launch (Ubuntu)
   Importance: Medium => High

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

Title:
  Need better session management for apps

Status in Canonical System Image:
  Triaged
Status in Libertine:
  Triaged
Status in Libertine devel series:
  Triaged
Status in Libertine trunk series:
  Triaged
Status in libertine package in Ubuntu:
  Triaged
Status in ubuntu-app-launch package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  This is the master bug for better session management for apps.  All
  other bugs affected by this will be dup'ed to this bug.

  Currently, if a user closes an app using the 'X' button on the window,
  many bad things can happen including data loss.

  If a user is editing a document and accidentally hits the X while the
  data is not saved, the user will not be prompted to save and the data
  will be lost.

  Another example is Libertine helper apps can crash when Xmir is
  killed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1628589/+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 1669314] Re: unity8 crashed with SIGABRT: LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate registration of tracepoint probes having the same name is not allow

[Alejandro J. Cura]

** Changed in: ubuntu-app-launch (Ubuntu)
 Assignee: (unassigned) => Ted Gould (ted)

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

Title:
  unity8 crashed with SIGABRT: LTTng-UST: Error (-17) while registering
  tracepoint probe. Duplicate registration of tracepoint probes having
  the same name is not allowed.

Status in ubuntu-app-launch package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  With the most recent libubuntu-app-launch4:

  $ apt policy libubuntu-app-launch4
  libubuntu-app-launch4:
Installed: 0.10+17.04.20170215.1-0ubuntu1
Candidate: 0.10+17.04.20170215.1-0ubuntu1
Version table:
   *** 0.10+17.04.20170215.1-0ubuntu1 400
  400 http://archive.ubuntu.com/ubuntu zesty-proposed/main amd64 
Packages
  100 /var/lib/dpkg/status

  Unity8 aborts on startup with:

  > LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate
  registration of tracepoint probes having the same name is not allowed.

  ProblemType: Crash
  DistroRelease: Ubuntu 17.04
  Package: unity8 8.15+17.04.20170301.2-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-2481]
  ProcVersionSignature: Ubuntu 4.10.0-8.10-generic 4.10.0-rc8
  Uname: Linux 4.10.0-8-generic x86_64
  ApportVersion: 2.20.4-0ubuntu2
  Architecture: amd64
  Date: Thu Mar  2 09:51:45 2017
  ExecutablePath: /usr/bin/unity8
  ExecutableTimestamp: 1488389347
  InstallationDate: Installed on 2016-05-06 (299 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcCmdline: /usr/bin/unity8 --mode=greeter
  ProcCwd: /var/lib/lightdm
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pl_PL.UTF-8
   SHELL=/bin/false
  Signal: 6
  SourcePackage: unity8
  StacktraceTop:
   __lttng_events_init__ubuntu_app_launch () at 
/usr/include/lttng/ust-tracepoint-event.h:1011
   call_init (l=, argc=argc@entry=2, 
argv=argv@entry=0x7ffc9ad667a8, env=env@entry=0x5570b3998740) at dl-init.c:72
   call_init (env=0x5570b3998740, argv=0x7ffc9ad667a8, argc=2, l=) at dl-init.c:30
   _dl_init (main_map=main_map@entry=0x7f70500ad630, argc=2, 
argv=0x7ffc9ad667a8, env=0x5570b3998740) at dl-init.c:120
   dl_open_worker (a=a@entry=0x7f707cff76c0) at dl-open.c:575
  Title: unity8 crashed with SIGABRT
  UpgradeStatus: Upgraded to zesty on 2016-11-22 (99 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-app-launch/+bug/1669314/+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 1014992] Re: Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission denied.

[Alejandro Romero Herrera]

Writing a udev rule to ignore device by ModemManager worked for me:

/etc/udev/rules.d/55-bluetooth-drone-NoModem.rules
KERNEL=="rfcomm*", ATTR{address}=="xx:d3:xx:00:xx:xx", 
ENV{ID_MM_DEVICE_IGNORE}="1"

And reloading rules:
sudo udevadm control --reload-rules

So I connect to device as root
sudo rfcomm connect hic0 XX:D3:XX:00:XX:XX

and then I am able to use it as regular user from dialout group

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

Title:
  Ubuntu 12.04, i386, cannot use rfcomm as regular user. Permission
  denied.

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  After updating from 8.04 to 12.04 I cannot use rfcomm without sudo.

  I've already added the user  to group 'dialout' .

  Temporary I tried to change udev.rules (KERNEL=="rfcomm[0-9]*", 
GROUP="dialout", MODE="666")  but this doesn't
  solve the problem so I removed it again.

  Here the commands I used :

  burki@orion:/$ hcitool scan
  Scanning ...
   00:12:6F:08:98:FFGEO LE-71 1

  burki@orion:/$ rfcomm connect 1 00:12:6F:08:98:FF
  Can't open RFCOMM device: Permission denied

  burki@orion:/$ ls -l /dev/rfcomm1
  ls: cannot access /dev/rfcomm1: No such file or directory

  burki@orion:/$ groups
  burki adm dialout fax cdrom floppy tape sudo audio dip video plugdev fuse 
scanner lpadmin netdev sambashare

  burki@orion:/$ sudo rfcomm connect 1 00:12:6F:08:98:FF
  Connected /dev/rfcomm1 to 00:12:6F:08:98:FF on channel 1
  Press CTRL-C for hangup

  In another terminal while connection is running ...

  burki@orion:/$ ls -l /dev/rfcomm1
  crw-rw 1 root dialout 216, 1 Jun 19 09:01 /dev/rfcomm1

  burki@orion:/$ UDEV_LOG=debug udevadm test $(udevadm info -q path -n rfcomm1)
  (I've stolen this command from another bug report #570692.  Output is very 
long. Please see attachment)

  WORKAROUND: sudo chmod u+s /usr/bin/rfcomm

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: linux-image-3.2.0-25-generic-pae 3.2.0-25.40
  ProcVersionSignature: Ubuntu 3.2.0-25.40-generic-pae 3.2.18
  Uname: Linux 3.2.0-25-generic-pae i686
  AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
  ApportVersion: 2.0.1-0ubuntu8
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  burki  1730 F pulseaudio
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Card0.Amixer.info:
   Card hw:0 'PCH'/'HDA Intel PCH at 0xfe50 irq 56'
     Mixer name : 'Intel CougarPoint HDMI'
     Components : 'HDA:10ec0887,10438444,00100302 
HDA:80862805,80862805,0010'
     Controls  : 49
     Simple ctrls  : 21
  Date: Tue Jun 19 09:15:54 2012
  HibernationDevice: RESUME=UUID=f3e3a302-4042-4fcd-86c5-756ae88e15b8
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release i386 
(20120423)
  IwConfig:
   lono wireless extensions.

   eth0  no wireless extensions.
  MachineType: System manufacturer System Product Name
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-25-generic-pae 
root=UUID=f791f2d4-8966-47d3-a19d-9b0b649e63ea ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.2.0-25-generic-pae N/A
   linux-backports-modules-3.2.0-25-generic-pae  N/A
   linux-firmware1.79
  RfKill:
   0: hci0: Bluetooth
    Soft blocked: no
    Hard blocked: no
  SourcePackage: linux
  StagingDrivers: mei
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/21/2011
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0703
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: P8Z68-V LX
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0703:bd10/21/2011:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLX:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1014992/+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 1652890] [NEW] Keyboard Layout indicator is not translated into Spanish

[Alejandro Morales Lepe]

Public bug reported:

See attached screenshot.

Keyboard Layout indicator is not properly translated into Spanish.

"Orientación", "Archivos" and "Ubicación" have working translation,
meanwhile Keyboard Layout is still in English.

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

** Attachment added: "Screenshot of the untranslated indicator."
   
https://bugs.launchpad.net/bugs/1652890/+attachment/4797414/+files/screenshot20161227_224058303.png

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

Title:
  Keyboard Layout indicator is not translated into Spanish

Status in unity8 package in Ubuntu:
  New

Bug description:
  See attached screenshot.

  Keyboard Layout indicator is not properly translated into Spanish.

  "Orientación", "Archivos" and "Ubicación" have working translation,
  meanwhile Keyboard Layout is still in English.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1652890/+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 1615474] Re: Network Indicator / Connectivity-API is not accessible

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
   Status: Confirmed => Triaged

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

Title:
  Network Indicator / Connectivity-API is not accessible

Status in Canonical System Image:
  Triaged
Status in indicator-network package in Ubuntu:
  In Progress

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

  -

  Per the comments the .config/connectivity-service/config.ini file
  seems to hold bad or outdated info and needs to be manually deleted
  and then recreated by the service.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+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 1607291] Re: Dual SIM devices show "No SIM" icon in indicators if there is only one SIM installed

[Alejandro J. Cura]

** Also affects: ubuntu-ux
   Importance: Undecided
   Status: New

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

Title:
  Dual SIM devices show "No SIM" icon in indicators if there is only one
  SIM installed

Status in Ubuntu UX:
  New
Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  rc-proposed, since about a week I have 2 SIM icons in the indicators
  panel. One that shows the signal strength for the installed SIM card
  (which is fine), and then a second one which shows the "no SIM card"
  icon.

  When there is a SIM card installed, the indicator should not show a
  "no SIM installed" icon, even though there would be a second free slot
  available.

  See attached screenshot.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-ux/+bug/1607291/+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 1619183] Re: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras instan

[Alejandro Sánchez Marín]

I solve the issue making a

apt-get -f install

and redo

apt-get install skype

Becauses I tried to install skype on my ubuntu amd64 system and skype
needs i386 dependencies.

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

Title:
  package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade:
  intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que
  es distinto de otras instancias del paquetes libqtcore4:i386

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  Trying to install skype with i386 support, breaks.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep  1 10:47:14 2016
  ErrorMessage: intentando sobreescribir el compartido 
`/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes 
libqtcore4:i386
  InstallationDate: Installed on 2016-07-06 (57 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: 
intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es 
distinto de otras instancias del paquetes libqtcore4:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1619183/+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 1619183] [NEW] package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es distinto de otras inst

[Alejandro Sánchez Marín]

Public bug reported:

Trying to install skype with i386 support, breaks.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
Date: Thu Sep  1 10:47:14 2016
ErrorMessage: intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', 
que es distinto de otras instancias del paquetes libqtcore4:i386
InstallationDate: Installed on 2016-07-06 (57 days ago)
InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: qt4-x11
Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: 
intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es 
distinto de otras instancias del paquetes libqtcore4:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: qt4-x11 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package xenial

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

Title:
  package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade:
  intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que
  es distinto de otras instancias del paquetes libqtcore4:i386

Status in qt4-x11 package in Ubuntu:
  New

Bug description:
  Trying to install skype with i386 support, breaks.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libqtcore4 4:4.8.7+dfsg-5ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Sep  1 10:47:14 2016
  ErrorMessage: intentando sobreescribir el compartido 
`/etc/xdg/Trolltech.conf', que es distinto de otras instancias del paquetes 
libqtcore4:i386
  InstallationDate: Installed on 2016-07-06 (57 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04 LTS "Xenial Xerus" - Release amd64 
(20160421)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: qt4-x11
  Title: package libqtcore4 4:4.8.7+dfsg-5ubuntu2 failed to install/upgrade: 
intentando sobreescribir el compartido `/etc/xdg/Trolltech.conf', que es 
distinto de otras instancias del paquetes libqtcore4:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/1619183/+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 1615474] Re: Wifi networking no longer possible, network indicator broken

[Alejandro J. Cura]

Hi Matthew, sorry to hear about this breakage, and that USB is not
working for you.

Can you please let us know if the process "indicator-network" process is
still running? Please paste the output of this: ps -ax | grep indicator-
network

Also, please paste any indicator-network logs you may find in
~/.cache/upstart

If you need wifi to get those things out of the phone, you may try using
the command line, as explained in http://askubuntu.com/questions/138472
/how-do-i-connect-to-a-wpa-wifi-network-using-the-command-line

That might help you also upgrade to a newer OTA, to see if things get
fixed, or to backup your data in case you want to try doing a full
device reset.

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

Title:
  Wifi networking no longer possible, network indicator broken

Status in Canonical System Image:
  Incomplete
Status in indicator-network package in Ubuntu:
  New

Bug description:
  Sometime in the last few days my phone lost the ability to connect to
  wifi networks and the network indicator at the top has stopped
  working.

  Currently between "Bluetooth" and "Sound" I have a gear icon and the
  caption "indicator-network".  When I select it, the rest of the screen
  is blank.  There are no settings available and no way to connect to a
  wifi network.

  On the System Settings app, if I tap on the "Wi-Fi" icon, I can see
  "Previous networks".  But below that the page is just white, there is
  no way to select a wifi network.

  Rebooting the phone doesn't seem to fix the problem.

  Given that this is an MX4 and therefore the USB port doesn't work, and
  there's no SD card slot, there's vanishingly few ways to get data in
  and out of this phone now.  If there's a solution to the problem, it's
  going to have to involve something other than updating system
  software.

  Current system software is Ubuntu 15.05 (OTA-12).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1615474/+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 1612334] [NEW] package libglapi-mesa:i386 11.2.0-1ubuntu2.1 failed to install/upgrade: package libglapi-mesa:i386 is already installed and configured

[Alejandro Lemus]

Public bug reported:

mmnb ,mn

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libglapi-mesa:i386 11.2.0-1ubuntu2.1
ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
Uname: Linux 4.4.0-34-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Fri Aug  5 00:00:04 2016
Dependencies:
 gcc-6-base 6.0.1-0ubuntu1
 libc6 2.23-0ubuntu3
 libgcc1 1:6.0.1-0ubuntu1
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.24, 3.13.0-91-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-31-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-34-generic, x86_64: installed
DuplicateSignature:
 package:libglapi-mesa:i386:11.2.0-1ubuntu2.1
 Setting up ure (5.1.4-0ubuntu1) ...
 dpkg: error processing package libreoffice-style-breeze (--configure):
  no package named 'libreoffice-style-breeze' is installed, cannot configure
ErrorMessage: package libglapi-mesa:i386 is already installed and configured
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo 2nd Generation Core Processor Family Integrated Graphics 
Controller [17aa:3975]
InstallationDate: Installed on 2014-04-10 (854 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
MachineType: LENOVO HuronRiver Platform
PackageArchitecture: i386
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-34-generic 
root=UUID=4e98a8b3-1dd5-495c-92ab-fe0cff0ef38c ro quiet splash vt.handoff=7
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: mesa
Title: package libglapi-mesa:i386 11.2.0-1ubuntu2.1 failed to install/upgrade: 
package libglapi-mesa:i386 is already installed and configured
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/27/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 44CN43WW
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: Emerald Lake
dmi.board.vendor: LENOVO
dmi.board.version: FAB1
dmi.chassis.asset.tag: Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnLENOVO:bvr44CN43WW:bd10/27/2011:svnLENOVO:pnHuronRiverPlatform:pvr0.1:rvnLENOVO:rnEmeraldLake:rvrFAB1:cvnLENOVO:ct10:cvr0.1:
dmi.product.name: HuronRiver Platform
dmi.product.version: 0.1
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Thu Aug 11 12:00:46 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id 732 
 vendor LGD
xserver.version: 2:1.18.3-1ubuntu2.3

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


** Tags: already-installed apport-package compiz-0.9 i386 ubuntu xenial

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

Title:
  package libglapi-mesa:i386 11.2.0-1ubuntu2.1 failed to
  install/upgrade: package libglapi-mesa:i386 is already installed and
  configured

Status in mesa package in Ubuntu:
  New

Bug description:
  mmnb ,mn

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libglapi-mesa:i386 11.2.0-1ubuntu2.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  AptdaemonVersion: 1.1.1+bzr982-0ubuntu14
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Fri Aug  5 00:00:04 2016
  Dependencies:
   gcc-6-base 6.0.1-0ubuntu1
   libc6 2.23-0ubuntu3
   libgcc1 1:6.0.1-0ubuntu1
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   virtualb

[Touch-packages] [Bug 1607799] Re: Dash freezes after U1 login

[Alejandro J. Cura]

I can confirm that the silo mentioned in #9 fixes the issue for me
(frieza, rc-proposed r161).

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

Title:
  Dash freezes after U1 login

Status in Canonical System Image:
  In Progress
Status in libsignon-glib package in Ubuntu:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  Incomplete
Status in unity-scopes-shell package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Test case.
  - Without U1 account, go to Ubuntu Store.
  - Tap on an app.
  - Tap on the install button.
  - Introduce credentials.

  Expected result.
  - After credentials, the app is installed.

  Actual result.
  - Dash is frozen. Cannot go back to the scopes. Launcher and indicators do 
work, though. There is no crash.

  current build number: 389
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607799/+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 1606808] Re: scope freezes after login

[Alejandro J. Cura]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
Milestone: None => 13

** Changed in: unity-scopes-shell (Ubuntu)
   Importance: Undecided => Critical

** Changed in: canonical-devices-system-image
   Status: New => Confirmed

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

** Changed in: unity-scopes-shell (Ubuntu)
 Assignee: (unassigned) => Paweł Stołowski (stolowski)

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

Title:
  scope freezes after login

Status in Canonical System Image:
  Confirmed
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  scopes which have online-account integrated freezes after login.
  To reproduce this issue
  1. flashing latest image, my image information as following
  current build number: 394
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-07-27 12:20:38
  version version: 394
  version ubuntu: 20160727
  version device: 20160606-ab415b2
  version custom: 20160701-981-38-14 
  2. launching youtube scope, click "Log-in" to youtube
  3. login with google account and back to youtube scope.
  4. scope freezes, there's nothing else I can do with the running scope now.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1606808/+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 1607079] Re: Cellular Option immediately crashes [OTA-12]

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
 Assignee: John McAleely (john.mcaleely) => Alejandro J. Cura (alecu)

** Also affects: indicator-network (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Antti Kaijanmäki (kaijanmaki)

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
   Status: New => In Progress

** Changed in: canonical-devices-system-image
   Importance: Undecided => High

** Changed in: canonical-devices-system-image
Milestone: None => 13

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

Title:
  Cellular Option immediately crashes [OTA-12]

Status in Canonical System Image:
  In Progress
Status in indicator-network package in Ubuntu:
  New
Status in ofono package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to OTA-12 today, everything seemed to work perfectly.
  But after rebooting the first time, I was not asked for a SIM PIN
  number. I had to deactivate/activate the SIM card so I could use the
  phone again.

  Due to the fact that the indicator-network is empty, I tried to
  activate the 3G connection by using the cellular option in the system
  settings.

  The cellular data option immediately crashes when selecting it.

  Edit:
  After rebooting a few times and deactivate/activate the SIM card again I 
could use this option. But I cannot activate/deactivate the cellular data 
option. My carrier is shown correctly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607079/+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 1606946] [NEW] AppArmor denied opening /dev/shm/lttng-ust-wait*

[Alejandro J. Cura]

Public bug reported:

When running under the Unity8 desktop session, the kernel log is spammed
with apparmor messages coming from the webbrowser app profile, the same
four lines every 5 seconds:

$ dmesg -w
[...]
[85560.662068] audit: type=1400 audit(1469629097.571:50068): apparmor="DENIED" 
operation="open" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-6-1000" 
pid=17206 comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
[85560.662124] audit: type=1400 audit(1469629097.571:50069): apparmor="DENIED" 
operation="open" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-6" 
pid=17205 comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=119
[85560.662173] audit: type=1400 audit(1469629097.571:50070): apparmor="DENIED" 
operation="open" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-6-1000" 
pid=17206 comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=1000
[85560.662221] audit: type=1400 audit(1469629097.571:50071): apparmor="DENIED" 
operation="open" profile="webbrowser-app" name="/dev/shm/lttng-ust-wait-6" 
pid=17205 comm="QQmlThread" requested_mask="r" denied_mask="r" fsuid=1000 
ouid=119

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  AppArmor denied opening /dev/shm/lttng-ust-wait*

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  When running under the Unity8 desktop session, the kernel log is
  spammed with apparmor messages coming from the webbrowser app profile,
  the same four lines every 5 seconds:

  $ dmesg -w
  [...]
  [85560.662068] audit: type=1400 audit(1469629097.571:50068): 
apparmor="DENIED" operation="open" profile="webbrowser-app" 
name="/dev/shm/lttng-ust-wait-6-1000" pid=17206 comm="QQmlThread" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  [85560.662124] audit: type=1400 audit(1469629097.571:50069): 
apparmor="DENIED" operation="open" profile="webbrowser-app" 
name="/dev/shm/lttng-ust-wait-6" pid=17205 comm="QQmlThread" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=119
  [85560.662173] audit: type=1400 audit(1469629097.571:50070): 
apparmor="DENIED" operation="open" profile="webbrowser-app" 
name="/dev/shm/lttng-ust-wait-6-1000" pid=17206 comm="QQmlThread" 
requested_mask="r" denied_mask="r" fsuid=1000 ouid=1000
  [85560.662221] audit: type=1400 audit(1469629097.571:50071): 
apparmor="DENIED" operation="open" profile="webbrowser-app" 
name="/dev/shm/lttng-ust-wait-6" pid=17205 comm="QQmlThread" requested_mask="r" 
denied_mask="r" fsuid=1000 ouid=119

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/webbrowser-app/+bug/1606946/+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 1595113] Re: Icons in scope filters look pixelated

[Alejandro J. Cura]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Michał Sawicz (saviq)

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

Title:
  Icons in scope filters look pixelated

Status in Canonical System Image:
  New
Status in unity8 package in Ubuntu:
  In Progress

Bug description:
  bq M10 FHD rc-proposed with Libertine/X-Apps scope installed.

  Steps to reproduce:
  1. Open XApps scope
  2. Click "search" icon
  3. Click "filters" icon
  4. Click "down" icon to expand the list
  5. Click any list item to see "tick" icon

  Expected result:
  All icons are nice and smooth 

  What happens instead:
  Icons: "down", "up" and "tick" look pixelated

  Screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595113/+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 1598010] Re: cellular data switch disabled until SIM selected in settings

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
   Importance: High => Critical

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

Title:
  cellular data switch disabled until SIM selected in settings

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  
  Cellular data switch is disabled on nexus 4. 

  rc_proposed: r476
  Ubuntu Image Part: 20160701

  Mobile data cannot be activated on this device (possibly others) as
  the cellular data switch in settings and in the indicator are
  disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598010/+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 1598010] Re: cellular data switch disabled until SIM selected in settings

[Alejandro J. Cura]

** Changed in: indicator-network (Ubuntu)
 Assignee: Pete Woods (pete-woods) => Antti Kaijanmäki (kaijanmaki)

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => Critical

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

Title:
  cellular data switch disabled until SIM selected in settings

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  
  Cellular data switch is disabled on nexus 4. 

  rc_proposed: r476
  Ubuntu Image Part: 20160701

  Mobile data cannot be activated on this device (possibly others) as
  the cellular data switch in settings and in the indicator are
  disabled.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598010/+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 1460458] Re: [system settings] Dual Sim; no possibility to switch on or off each sim card completely.

[Alejandro J. Cura]

** Also affects: indicator-network (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Antti Kaijanmäki (kaijanmaki)

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

Title:
  [system settings] Dual Sim; no possibility to switch on or off each
  sim card completely.

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  Triaged
Status in indicator-network package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  If two sim cards is used there is no possibility to switch each sim card on 
or off completely
  (to completely activate or deactivate sim 1 and sim 2 separately).

  Sim 1 and sim 2 inside:
  Often I do not want to use both sim cards at the same time.
  Sometimes it's needed that only sim 1 is active.
  Sometimes it's needed that only sim 2 is active.
  Sometimes it's needed that sim 1 and sim 2 is active.

  So there should be the possibility to completely activate/deactivate sim 1 
and sim 2 separately.
  Would be nice in the context menu of the network indicator,
  an on/off switch for sim1 and sim2.
  Or at least in systemsettings.

  Bq Aquaris E4.5
  Ubuntu 14.10 (r22)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1460458/+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 1599754] Re: Dash restarts in the middle while refreshing or navigating

[Alejandro J. Cura]

** Changed in: unity-scopes-shell (Ubuntu)
 Assignee: (unassigned) => Pawel Stolowski (stolowski)

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

Title:
  Dash restarts in the middle while refreshing or navigating

Status in Canonical System Image:
  Confirmed
Status in frieza:
  New
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  current build number: 15
  device name: frieza
  channel: ubuntu-touch/rc/bq-aquaris-pd.en
  last update: 2016-07-04 18:00:02
  version version: 15
  version ubuntu: 20160629
  version tag: OTA-12-rc
  version device: 20160622.0
  version custom: 20160624--41-15-vivid

  Steps:
  1.Find a scope which asking a location service, like: nearby scope, news scope
  2.Change to different filters to reload the content
  3.Pull down to refresh the page repeatedly

  actual:
  Sometimes, scopes hangs in refreshing state for ~3 minutes, then dash restarts

  expected:
  no hang and dash restart

  First image this happens on: frieza ubuntu-touch/rc/bq-aquaris-
  pd.en@126

  The upgrade that breaks it:

   unity-plugin-scopes:armhf
     from 0.5.7+15.04.20160617.1-0ubuntu1
   to 0.5.7+15.04.20160624.2-0ubuntu1

  The offending landing:
  https://requests.ci-train.ubuntu.com/#/ticket/1587

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1599754/+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 1598584] Re: M10 wifi slows to a crawl when bluetooth is enabled

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

** Changed in: indicator-network (Ubuntu)
   Status: New => Invalid

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

Title:
  M10 wifi slows to a crawl when bluetooth is enabled

Status in Canonical System Image:
  New
Status in indicator-network package in Ubuntu:
  Invalid

Bug description:
  I am having serious wifi performance issues on my Aquaris M10 (running
  rc-proposed r133). When measuring the wifi speed, I get download
  speeds of less than 1/20 compared to my Pro 5 at the same distance
  from the wifi router. This seems to be consistent through reboots. I
  had similar wifi performance also before recently upgrading to rc-
  proposed, which I thought would have fixed the issue.

  I am in the same place testing 3 different ubuntu devices and these are the 
readings of the wifi download speed:
  Laptop: 4 MB/s
  Pro 5: 3.5 MB/s
  Aquaris M10: 0.16 MB/s

  However, upload speed is about the same on all three devices.

  Turning bluetooth off gets Aquaris M10 wifi speed back to sort of
  normal, 2.5-3.4 MB/s. Bluetooth on, again 0.1-0.2 MB/s. Seems the two
  wireless technologies interfere with each other on the M10, while the
  Pro 5 doesn't have that problem.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1598584/+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 1597681] Re: [CTA] Enable WAPI support

[Alejandro J. Cura]

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => High

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

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

Title:
  [CTA] Enable WAPI support

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  The phone does not currently support WAPI [1]

  It should do so. As part of this, support for the SMS4 [2] cipher is
  also required.

  
  [1] 
https://en.wikipedia.org/wiki/WLAN_Authentication_and_Privacy_Infrastructure
  [2]: https://en.wikipedia.org/wiki/SMS4

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597681/+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 1597615] Re: The cellular data option in network indicator is disabled after turning on and turning off the flight mode.

[Alejandro J. Cura]

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => High

** Changed in: indicator-network (Ubuntu)
   Status: New => Triaged

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

Title:
  The cellular data option in network indicator is disabled after
  turning on and turning off the flight mode.

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Triaged

Bug description:
  Information:
  current build number: 371
  device name: krillin
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-06-29 05:04:34
  version version: 371
  version ubuntu: 20160629
  version device: 20160606-ab415b2
  version custom: 2

  Precondition:
  SIM card is inserted and Cellular data is open.

  Steps:
  1.Pull down the network indicator,and turn on flight mode toggle.
  2.After a few seconds turn  off the flight mode and check the cellular data 
option.

  Actual result:
  The state is on but option bar is disable and cannot be tapping. Go to 
cellular settings page, it works fine there.

  Expected result:
  The cellular data option should be still enabled after turn on and turning 
off the flight mode.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597615/+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 1597683] Re: Cellular data switch visible on M10 tablet

[Alejandro J. Cura]

** Changed in: indicator-network (Ubuntu)
   Importance: Undecided => High

** Changed in: indicator-network (Ubuntu)
 Assignee: (unassigned) => Pete Woods (pete-woods)

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

Title:
  Cellular data switch visible on M10 tablet

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  New

Bug description:
  M10 FHD with rc-proposed (r130)

  When I pull down the indicators panel I can see greyed out 'Cellular data' 
and a switch next to it.
  Screenshot attached.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1597683/+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 1595569] Re: Indicators panel doesn't close when turning screen off

[Alejandro J. Cura]

Weird thing is that sometimes the indicator stays still:
https://goo.gl/photos/cdsEc4k2fhPfhKUZ9

and sometimes it closes on its own:
http://people.canonical.com/~davmor2/vids/video20160629_201128513.mp4

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

Title:
  Indicators panel doesn't close when turning screen off

Status in Canonical System Image:
  Confirmed
Status in unity8 package in Ubuntu:
  Triaged

Bug description:
  Steps:
  * open indicators
  * press power button to turn the screen off
  * press power button to turn the screen on

  Expected:
  * greeter shown

  Current:
  * indicators panel shown

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity8 8.12+16.04.20160617-0ubuntu1 [origin: 
LP-PPA-ci-train-ppa-service-stable-phone-overlay]
  ProcVersionSignature: Ubuntu 4.4.0-24.43-generic 4.4.10
  Uname: Linux 4.4.0-24-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jun 23 10:17:32 2016
  InstallationDate: Installed on 2016-05-06 (47 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1595569/+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 1492252] Re: Allow direct linking to a Preview via uri

[Alejandro J. Cura]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  Allow direct linking to a Preview via uri

Status in Client Developer Experience:
  New
Status in Canonical System Image:
  New
Status in unity-scopes-api package in Ubuntu:
  Invalid
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  I can already link to a scopes search via the scope:// protocol but it
  would be great to be able to link directly to a preview page via a
  scope:// uri. This would be especially helpful for uApp Explorer to
  link directly to an app in the official store (rather than the search
  page like it does now).

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1492252/+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 1388931] Re: Support 12h or 24h time display format

[Alejandro J. Cura]

** Changed in: indicator-datetime (Ubuntu)
 Assignee: Charles Kerr (charlesk) => Renato Araujo Oliveira Filho 
(renatofilho)

** Changed in: canonical-devices-system-image
 Assignee: Pat McGowan (pat-mcgowan) => Bill Filler (bfiller)

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

Title:
  Support 12h or 24h time display format

Status in Canonical System Image:
  Confirmed
Status in Ubuntu Clock App:
  Confirmed
Status in Ubuntu UX:
  Won't Fix
Status in indicator-datetime package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Updating this bug based on the comments and dupes.

  There should be a setting in the Time & Date settings control panel to
  select 12 or 24 hour display format. This should be honored in the
  indicator, greeter and clock app.

  gsetting com.canonical.indicator.datetime time-format controls this

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1388931/+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 1591246] Re: Wrong icon in notification of missed alarms and events

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
 Assignee: Alejandro J. Cura (alecu) => Bill Filler (bfiller)

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

Title:
  Wrong icon in notification of missed alarms and events

Status in Canonical System Image:
  Confirmed
Status in Ubuntu UX:
  New
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  The new implemented notifications (Released in OTA-11; see Bug
  #1440111) for missed alarms and events is using wrong icons.

  1) If an alarm has been missed, the notification should use the icon of the 
clock app instead of the calendar app's.
  2) A missed alarm should use the clock-icon on the right instead of an icon 
showing a number.
  3) A missed event should use the new event-icon without a number.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591246/+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 1594880] Re: Location settings missing in scope until reboot

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

** Changed in: canonical-devices-system-image
   Status: New => In Progress

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Changed in: canonical-devices-system-image
Milestone: None => 12

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

Title:
  Location settings missing in scope until reboot

Status in Canonical System Image:
  In Progress
Status in unity-scopes-shell package in Ubuntu:
  Confirmed

Bug description:
  On this system [1], installed with --bootstrap, I allowed all location
  related bits as prompted.

  But, when I looked in a scope (for example NearBy), I found that the
  scope did not have a location and that the Enable Location settings
  normally present in scopes was not present.

  On reboot, everything worked as expected.

  [1] phablet@ubuntu-phablet:~$ system-image-cli -i
  current build number: 338
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-06-21 09:59:59
  version version: 338
  version ubuntu: 20160621
  version device: 20160401.1
  version custom: 20160504-2-vivid

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1594880/+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 1579837] Re: Issue after wizard with policykit

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
Milestone: 12 => backlog

** Changed in: canonical-devices-system-image
   Importance: High => Medium

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

Title:
  Issue after wizard with policykit

Status in Canonical System Image:
  In Progress
Status in accountsservice package in Ubuntu:
  Fix Released
Status in policykit-unity8 package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete

Bug description:
  STEPS:
  1. Bootstrap flash a fresh image to a device
  2. Run through the wizard selecting pin for authentication
  3. Tap on the get started button
  4. Phone freezes for a while
  5. At some point it unfreezes and you see the dash
  6. Reboot and get password login instead of pin login

  EXPECTED:
  I expect no freeze (possibly due to apport) and pin dialogue on reboot

  ACTUAL:
  I get a long freeze and on reboot instead of getting the pin dialogue to 
unlock the phone I get the password dialogue and full osk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1579837/+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 1586379] Re: Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu 16.04

[Alejandro Comisario]

anyone ?

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

Title:
  Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu
  16.04

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a Macbook pro 15 (version 8.2) with Xubuntu 14.04 the mic
  worked out of the box, with xubuntu 16.04

  * upgraded from 14.04
  * fresh install

  The mic does'nt get any signal, i have tried these:
  
http://askubuntu.com/questions/482626/microphone-not-working-on-ubuntu-14-04-on-macbookpro10-2

  with no luck.

  the output of the command:
  wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh

  is here:
  http://www.alsa-project.org/db/?f=1a18a2a3188be0c68d960ae4e6d8ec2ccacb994d

  if please can anyone help me ? 
  not being able to use the microphone is killing me.

  thank you !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1586379/+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 1586379] Re: Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu 16.04

[Alejandro Comisario]

thank god, hope someone take it asap

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

Title:
  Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu
  16.04

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I have a Macbook pro 15 (version 8.2) with Xubuntu 14.04 the mic
  worked out of the box, with xubuntu 16.04

  * upgraded from 14.04
  * fresh install

  The mic does'nt get any signal, i have tried these:
  
http://askubuntu.com/questions/482626/microphone-not-working-on-ubuntu-14-04-on-macbookpro10-2

  with no luck.

  the output of the command:
  wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh

  is here:
  http://www.alsa-project.org/db/?f=1a18a2a3188be0c68d960ae4e6d8ec2ccacb994d

  if please can anyone help me ? 
  not being able to use the microphone is killing me.

  thank you !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1586379/+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 1586379] Re: Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu 16.04

[Alejandro Comisario]

Hi, any help ?

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

Title:
  Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu
  16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a Macbook pro 15 (version 8.2) with Xubuntu 14.04 the mic
  worked out of the box, with xubuntu 16.04

  * upgraded from 14.04
  * fresh install

  The mic does'nt get any signal, i have tried these:
  
http://askubuntu.com/questions/482626/microphone-not-working-on-ubuntu-14-04-on-macbookpro10-2

  with no luck.

  the output of the command:
  wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh

  is here:
  http://www.alsa-project.org/db/?f=1a18a2a3188be0c68d960ae4e6d8ec2ccacb994d

  if please can anyone help me ? 
  not being able to use the microphone is killing me.

  thank you !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1586379/+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 1552371] Re: Unexpected display on

[Alejandro J. Cura]

The "home" button accidentally turning the screen on is confirmed in
this thread:
https://plus.google.com/u/0/108188125572924200710/posts/aBuWYcnSyQt?cfem=1

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

Title:
  Unexpected display on

Status in Canonical System Image:
  Confirmed
Status in Mir:
  New
Status in Unity System Compositor:
  New
Status in bluez package in Ubuntu:
  Confirmed
Status in mir package in Ubuntu:
  Confirmed
Status in unity-system-compositor package in Ubuntu:
  Confirmed

Bug description:
  NOTE: kgunn suggests this bug be about 1) not 2) here

  1)
  I have been noticing my phone and tablet occasionally turning on without 
interaction. Several times with my phone in my pocket I found it in the 
emergency call UI
  I also see the tablet display turn on while lying idle on the desk. Freiza & 
Arale

  2)
  I have reproduced one case such that turning on a BT device (headset) causes 
the phone to light up and display the volume slider. Similarly turning on the 
BT keyboard while the tablet screen is off caused the display to turn on.These 
may be as intended.

  I suspect other BT events can similarly resume the device and/or turn on the 
display if it happens to be awake due to the 5 min polling timer.
  The proximity sensor is also not honored when this happens, if its covered 
the screen still comes on.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1552371/+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 1580908] Re: Sim lock screen doesn't appear after restarting the device

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => John McAleely (john.mcaleely)

** Changed in: ofono (Ubuntu)
 Assignee: (unassigned) => Alfonso Sanchez-Beato (alfonsosanchezbeato)

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

Title:
   Sim lock screen doesn't appear after restarting the device

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  From https://bugs.launchpad.net/zhongshan/+bug/1572886

  current build number: 4
  device name: turbo
  channel: ubuntu-touch/rc/meizu.en
  last update: 2016-04-19 10:38:50
  version version: 4
  version ubuntu: 20160418
  version device: 20160412-d272a77
  version custom: 20160324-945-18-69

  Steps:
  1.turn on sim pin lock
  2.reboot the device
  3.swipe to dismiss the greeter

  Actual result:
  phone lock screen is displayed

  Expected result:
  sim lock screen should appear before the phone lock screen

  It also happens sometimes on arale without any pattern to reproduce,
  just random on reboot.

  =

  After debugging it seems that this is caused by ofono removing the
  modems in the middle of the unlock process. You can see the difference
  for Turbo and Krillin below.

  Log for Turbo: http://paste.ubuntu.com/1147/

  Log for Krillin: http://paste.ubuntu.com/16675431/

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1580908/+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 1586379] [NEW] Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu 16.04

[Alejandro Comisario]

Public bug reported:

I have a Macbook pro 15 (version 8.2) with Xubuntu 14.04 the mic worked
out of the box, with xubuntu 16.04

* upgraded from 14.04
* fresh install

The mic does'nt get any signal, i have tried these:
http://askubuntu.com/questions/482626/microphone-not-working-on-ubuntu-14-04-on-macbookpro10-2

with no luck.

the output of the command:
wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh

is here:
http://www.alsa-project.org/db/?f=1a18a2a3188be0c68d960ae4e6d8ec2ccacb994d

if please can anyone help me ? 
not being able to use the microphone is killing me.

thank you !

** Affects: alsa-driver (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Microphone not working on MacBookpro 15 (version 8.2) and Xubuntu
  16.04

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  I have a Macbook pro 15 (version 8.2) with Xubuntu 14.04 the mic
  worked out of the box, with xubuntu 16.04

  * upgraded from 14.04
  * fresh install

  The mic does'nt get any signal, i have tried these:
  
http://askubuntu.com/questions/482626/microphone-not-working-on-ubuntu-14-04-on-macbookpro10-2

  with no luck.

  the output of the command:
  wget -O alsa-info.sh http://www.alsa-project.org/alsa-info.sh && chmod +x 
./alsa-info.sh && ./alsa-info.sh

  is here:
  http://www.alsa-project.org/db/?f=1a18a2a3188be0c68d960ae4e6d8ec2ccacb994d

  if please can anyone help me ? 
  not being able to use the microphone is killing me.

  thank you !

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1586379/+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 1235300] Re: Location menu doesn't list apps that recently used location

[Alejandro J. Cura]

** Changed in: indicator-location (Ubuntu)
   Importance: High => Low

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

Title:
  Location menu doesn't list apps that recently used location

Status in platform-api:
  Invalid
Status in indicator-location package in Ubuntu:
  Triaged

Bug description:
  Ubuntu Touch 2013-10-03

  1. In the Location menu, turn on "Location detection" and "GPS" if they are 
not on already.
  2. In the Weather app's toolbar, choose "Edit" [sic], then "Scan for 
location".
  3. Open the Location menu again.

  What happens The Weather app is not listed in the menu.

  What should happen: The Weather app is listed in the menu.

  (This bug might be obscured by location detection not working at all.
  On reopening the Location menu, "Location detection" and "GPS" are
  once more unchecked.)

To manage notifications about this bug go to:
https://bugs.launchpad.net/platform-api/+bug/1235300/+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 1407921] Re: Indicator should give feedback when location-service is in use by apps

[Alejandro J. Cura]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Changed in: canonical-devices-system-image
 Assignee: (unassigned) => Alejandro J. Cura (alecu)

** Changed in: canonical-devices-system-image
Milestone: None => 12

** Changed in: canonical-devices-system-image
   Importance: Undecided => Critical

** Changed in: canonical-devices-system-image
   Status: New => Triaged

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

Title:
  Indicator should give feedback when location-service is in use by apps

Status in Canonical System Image:
  Triaged
Status in Indicator Location:
  New
Status in Ubuntu theme:
  In Progress
Status in Ubuntu UX:
  Triaged
Status in indicator-location package in Ubuntu:
  In Progress

Bug description:
  The only information the location indicator icon conveys currently is
  whether location detection is enabled at all, when more data could be
  interesting. Especially acquiring a GPS lock is often interesting, as
  this greatly impacts the location accuracy.

  Maybe the location icon should be dimmed when nothing is using it and
  blink when GPS lock is being acquired, bright when the lock is fine?

  The current spec is @ https://wiki.ubuntu.com/Location

  == Bug revision by charlesk 2016-01-24:

  The Location spec has been revised in this regard. The new text reads:

  > The indicator should appear in the status bar
  > whenever an app has accessed your location in
  > the past five minutes. It should list all apps
  > that have accessed your location in the past
  > five minutes, most recent first. Choosing any
  > app should switch to that app, so that you may
  > control whichever functions in that app are
  > accessing location. “Location Settings…” should
  > navigate to the “Location” screen of System
  > Settings.

  This bug is about the first part of that spec -- making the indicator
  visible when it's active -- and is (currently) blocked on location-
  service bug #1536774.

  The recent apps list component of the spec is covered in sibling bug
  #1235300.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1407921/+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 1536774] Re: Service state should distinguish between enabled/disabled and active/inactive

[Alejandro J. Cura]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  Service state should distinguish between enabled/disabled and
  active/inactive

Status in Canonical System Image:
  New
Status in location-service package in Ubuntu:
  Confirmed

Bug description:
  Service state should distinguish between enabled/disabled and
  active/inactive

  To make usage of that solution I would like to propose new icons which are 
added in bug report:
  https://bugs.launchpad.net/ubuntu/+source/indicator-location/+bug/1407921

  GPS Disabled: No icon displayed
  GPS Enabled, GPS active: Display 
https://launchpadlibrarian.net/210299143/gps-enabled-connected.svg
  GPS Enabled, GPS inactive: Display 
https://launchpadlibrarian.net/210299156/gps-enabled-not-connected.svg

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1536774/+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 1317860] Re: the phone should switch itself off before completely draining battery

[Alejandro J. Cura]

** Also affects: livecd-rootfs (Ubuntu)
   Importance: Undecided
   Status: New

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

** Changed in: livecd-rootfs (Ubuntu)
   Status: New => Fix Released

** Changed in: livecd-rootfs (Ubuntu)
 Assignee: (unassigned) => Xavi Garcia (xavi-garcia-mena)

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Invalid
Status in livecd-rootfs package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Invalid

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+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 1317860] Re: the phone should switch itself off before completely draining battery

[Alejandro J. Cura]

** Changed in: canonical-devices-system-image
   Status: In Progress => Fix Committed

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

Title:
  the phone should switch itself off before completely draining battery

Status in Canonical System Image:
  Fix Committed
Status in Ubuntu UX:
  Fix Committed
Status in indicator-power package in Ubuntu:
  Invalid
Status in upower package in Ubuntu:
  Confirmed

Bug description:
  the phone should switch itself off at around ~5% remaining battery.

  This is to preserve a little battery for use cases such as:

  * turn it back on once or twice for urgent short phone calls
  * prevent the battery from going into a state where it can't be charged any 
more
  * have enough power to turn itself on again and trigger an alarm

  : "The device should hibernate
  (PC) or power off (phone/tablet) if both of these things are true: *
  there is less than 2% battery remaining * there has been more than 3%
  battery remaining at some point since the last time the device
  hibernated or powered off."

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1317860/+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 1577351] Re: OptionSelector: selectedIndex should be updated before onTriggered and onDelegateClicked

[Alejandro J. Cura]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  OptionSelector: selectedIndex should be updated before onTriggered and
  onDelegateClicked

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  OptionSelector {
  onSelectedIndexChanged: {
  console.log("SelectedIndex Changed")
  }
  onTriggered:  {
  console.log("On Triggered")
  }
  onDelegateClicked: {
  console.log("Delegate Clicked: " + index)
  }

  
  With this example we see that onTriggered and onDelegateClicked are being 
fired before selectedIndex has been updated. This makes the onTriggered quite 
useless, as the important info of which is the selectedIndex is not there yet. 
onDelegateClicked suffers from the same problem, although it's index argument 
allows to workaround this bug.

  IMHO having the selectedIndex updated before triggering these signals
  is a justifiable and sane behavior.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1577351/+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 1577359] Re: OptionSelectorDelegate: Renders empty if enabled: false

[Alejandro J. Cura]

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

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

Title:
  OptionSelectorDelegate: Renders empty if enabled: false

Status in Canonical System Image:
  New
Status in ubuntu-ui-toolkit package in Ubuntu:
  New

Bug description:
  import QtQuick 2.0
  import Ubuntu.Components 1.3

  Column {
  spacing: units.gu(3)

  OptionSelector {
  text: i18n.tr("Label")
  model: customModel
  expanded: true
  colourImage: true
  delegate: selectorDelegate
  }
  Component {
  id: selectorDelegate
  OptionSelectorDelegate { text: name; subText: description; enabled: 
isenabled }
  }
  ListModel {
  id: customModel
  ListElement { name: "Name 1"; description: "Description 1"; 
isenabled: true }
  ListElement { name: "Name 2"; description: "Description 2"; 
isenabled: false }
  ListElement { name: "Name 3"; description: "Description 3"; 
isenabled: true }
  ListElement { name: "Name 4"; description: "Description 4"; 
isenabled: false }
  }
  }

  
  

  Above example renders the second and fourth element completely empty.

  Expected:
  Show the contents of the element grayed out.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1577359/+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 1554079] Re: The icon does not change for active VPN connection

[Alejandro J. Cura]

Marking as Incomplete, because I would like some comments from design on
this, and some icons if this needs to be changed.

** Changed in: canonical-devices-system-image
   Status: Confirmed => Incomplete

** Changed in: indicator-network (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  The icon does not change for active VPN connection

Status in Canonical System Image:
  Incomplete
Status in Ubuntu UX:
  New
Status in indicator-network package in Ubuntu:
  Incomplete

Bug description:
  Reproduce:
  Activate VPN connection, i.e. make sure switch for VPN is on

  What happens:
  No indication besides the switch, which you have to pull down to see

  What should happen:
  Like on desktop (nm-applet) the indicator should indicate with a lock icon 
that VPN is active.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554079/+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