[Touch-packages] [Bug 1971538] Re: My machine has Wi-Fi Hotspot broken after upgrade to 22.04

[Samuel Rossille]

** Summary changed:

- My machine as Wi-Fi Hotspot broken after upgrade to 22.04
+ My machine has Wi-Fi Hotspot broken after upgrade to 22.04

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

Title:
  My machine has Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1971538] Re: My machine as Wi-Fi Hotspot broken after upgrade to 22.04

[Samuel Rossille]

I have a similar issue.
Here is what happens : I can connect to the hotspot just fine, but the 
connected devices don't have access to internet (tested with an android device 
and a windows device).
I tried all the wifi security options one by one, and there is the same 
behavior with each of them.
The hotspot worked fine with Ubuntu 21.10.
Hope this helps and sorry for the noise if it's unrelated.

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

Title:
  My machine as Wi-Fi Hotspot broken after upgrade to 22.04

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  * Impact
  The hotspot feature fails to forward the data to the clients

  * Test case
  - log into an Ubuntu or GNOME session
  - connect the machine to an eth cable for internet
  - go to gnome-control-center -> wifi
  - enable the hotspot from the menu in the headerbar
  - connect another device to the wifi created
  -> the client should connect and access to internet work correctly

  Upon updating to 22.04, none of my machines can use the connection.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1971538/+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 1089389] Re: juju bootstrap fail behind a proxy when a gpg key must be imported

[Samuel]

Thanks to all of you for sharing your experience. As I was facing the
same issue due to which we have opened our  https://gtavicecityapk.com/
from the last 2 weeks. And now the issue get fixed so I opened it after
2 weeks. The knowledge shared here is such awesome and brief.

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

Title:
  juju bootstrap fail behind a proxy when a gpg key must be imported

Status in software-properties package in Ubuntu:
  Triaged

Bug description:
  This is related to a Maas environment hosted behind a proxy.

  I'm trying to use
  juju 0.6.0.1+bzr603-0juju1~precise1

  ubuntu@maas:~$ cat .juju/environments.yaml
  environments:
    mymaas:
  type: maas
  maas-server: 'http://192.168.124.2:80/MAAS'
  maas-oauth: 
'UP5Qay8Nsku8K98fqn:LjhnStY2HjfCeKfvmg:BxA586DWVNPKrT9ASNj9QasMvSPdgavt'
  admin-secret: 'nothing'
  default-series: precise
  juju-origin: ppa

  When juju boostrap, things do not behave as expected on the zookeeper
  node.

  Excerpt from the cloud-init-output.log:

  W: GPG error: http://ppa.launchpad.net precise Release: The following
  signatures couldn't be verified because the public key is not
  available: NO_PUBKEY 376A290EC8068B11

  On the zookeeper node, if i try to apt-add-repository , the needed gpg
  key is not injected, but the scrpit does not return any error code:

  ubuntu@zookeeper:/var/log$ sudo mv 
/etc/apt/sources.list.d/juju-pkgs-precise.list /tmp/
  ubuntu@zookeeper:/var/log$ sudo ls /etc/apt/sources.list.d/
  ubuntu@zookeeper:/var/log$ sudo apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmpmlP7VA/secring.gpg' created
  gpg: keyring `/tmp/tmpmlP7VA/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpgkeys: key A2EB2DEC0BD7519B7B38BE38376A290EC8068B11 not found on keyserver
  gpg: no valid OpenPGP data found.
  gpg: Total number processed: 0
  recv failed
  ubuntu@zookeeper:/var/log$ echo $?
  0

  Trying to inject key while setting the http_proxy environment variable works 
better:
  ubuntu@zookeeper:/var/log$ sudo http_proxy=http://91.189.90.174:3128/ 
apt-add-repository ppa:juju/pkgs --yes
  gpg: keyring `/tmp/tmp1pAd6X/secring.gpg' created
  gpg: keyring `/tmp/tmp1pAd6X/pubring.gpg' created
  gpg: requesting key C8068B11 from hkp server keyserver.ubuntu.com
  gpg: /tmp/tmp1pAd6X/trustdb.gpg: trustdb created
  gpg: key C8068B11: public key "Launchpad Ensemble PPA" imported
  gpg: Total number processed: 1
  gpg: imported: 1 (RSA: 1)
  OK
  ubuntu@zookeeper:/var/log$ echo $?
  0

  On the zookeeper node, python-software-properties is version 0.82.7.3

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: python-software-properties 0.82.7.3
  ProcVersionSignature: Ubuntu 3.2.0-34.53-generic 3.2.33
  Uname: Linux 3.2.0-34-generic x86_64
  ApportVersion: 2.0.1-0ubuntu15
  Architecture: amd64
  Date: Wed Dec 12 14:40:21 2012
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: Upgraded to precise on 2012-05-14 (212 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1089389/+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 1970011] [NEW] pulseaudio running but can't hear any sound

[Samuel Siaw]

Public bug reported:

...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: pulseaudio 1:13.99.1-1ubuntu3.13
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.23
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Sat Apr 23 00:50:09 2022
InstallationDate: Installed on 2022-04-06 (16 days ago)
InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2021
dmi.bios.release: 4.14
dmi.bios.vendor: coreboot
dmi.bios.version: MrChromebox-4.14
dmi.board.name: Banon
dmi.board.vendor: GOOGLE
dmi.board.version: 1.0
dmi.chassis.type: 9
dmi.chassis.vendor: GOOGLE
dmi.ec.firmware.release: 0.0
dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku:
dmi.product.family: Intel_Strago
dmi.product.name: Banon
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE
modified.conffile..etc.pulse.default.pa: [modified]
mtime.conffile..etc.pulse.default.pa: 2022-04-23T00:30:09.974603

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

Title:
  pulseaudio running but can't hear any sound

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  ...

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.13
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.23
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Sat Apr 23 00:50:09 2022
  InstallationDate: Installed on 2022-04-06 (16 days ago)
  InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2021
  dmi.bios.release: 4.14
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.14
  dmi.board.name: Banon
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku:
  dmi.product.family: Intel_Strago
  dmi.product.name: Banon
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.default.pa: 2022-04-23T00:30:09.974603

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1970011/+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 1968385] [NEW] [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all

[Samuel Siaw]

Public bug reported:

Can't hear any sound on my inbuilt speaker (but it works with lubuntu).
Currently using xubuntu.

Also cannot hear any sound in my headphones when plugged in, although
volume control recognizes that headphones have been plugged in.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
Uname: Linux 5.13.0-39-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: XFCE
Date: Fri Apr  8 18:54:56 2022
InstallationDate: Installed on 2022-04-06 (2 days ago)
InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2021
dmi.bios.release: 4.14
dmi.bios.vendor: coreboot
dmi.bios.version: MrChromebox-4.14
dmi.board.name: Banon
dmi.board.vendor: GOOGLE
dmi.board.version: 1.0
dmi.chassis.type: 9
dmi.chassis.vendor: GOOGLE
dmi.ec.firmware.release: 0.0
dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku:
dmi.product.family: Intel_Strago
dmi.product.name: Banon
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

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

Title:
  [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Can't hear any sound on my inbuilt speaker (but it works with
  lubuntu). Currently using xubuntu.

  Also cannot hear any sound in my headphones when plugged in, although
  volume control recognizes that headphones have been plugged in.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.13.0-39.44~20.04.1-generic 5.13.19
  Uname: Linux 5.13.0-39-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Fri Apr  8 18:54:56 2022
  InstallationDate: Installed on 2022-04-06 (2 days ago)
  InstallationMedia: Xubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 
(20220223)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH failed
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [Banon, Intel Braswell HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/25/2021
  dmi.bios.release: 4.14
  dmi.bios.vendor: coreboot
  dmi.bios.version: MrChromebox-4.14
  dmi.board.name: Banon
  dmi.board.vendor: GOOGLE
  dmi.board.version: 1.0
  dmi.chassis.type: 9
  dmi.chassis.vendor: GOOGLE
  dmi.ec.firmware.release: 0.0
  dmi.modalias: 
dmi:bvncoreboot:bvrMrChromebox-4.14:bd07/25/2021:br4.14:efr0.0:svnGOOGLE:pnBanon:pvr1.0:rvnGOOGLE:rnBanon:rvr1.0:cvnGOOGLE:ct9:cvr:sku:
  dmi.product.family: Intel_Strago
  dmi.product.name: Banon
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1968385/+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 1968337] [NEW] package python-apt 2.0.0ubuntu0.20.04.7 failed to install/upgrade: installed python-apt package post-installation script subprocess returned error exit status 2

[Samuel Raker]

Public bug reported:

my computer froze & i rebooted it and got this error

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python-apt 2.0.0ubuntu0.20.04.7
Uname: Linux 5.16.11-76051611-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
AptOrdering:
 python-apt:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Apr  4 12:38:40 2022
ErrorMessage: installed python-apt package post-installation script subprocess 
returned error exit status 2
Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: python-apt
Title: package python-apt 2.0.0ubuntu0.20.04.7 failed to install/upgrade: 
installed python-apt package post-installation script subprocess returned error 
exit status 2
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package python-apt 2.0.0ubuntu0.20.04.7 failed to install/upgrade:
  installed python-apt package post-installation script subprocess
  returned error exit status 2

Status in python-apt package in Ubuntu:
  New

Bug description:
  my computer froze & i rebooted it and got this error

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python-apt 2.0.0ubuntu0.20.04.7
  Uname: Linux 5.16.11-76051611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   python-apt:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr  4 12:38:40 2022
  ErrorMessage: installed python-apt package post-installation script 
subprocess returned error exit status 2
  Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: python-apt
  Title: package python-apt 2.0.0ubuntu0.20.04.7 failed to install/upgrade: 
installed python-apt package post-installation script subprocess returned error 
exit status 2
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1968337/+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 1968338] [NEW] package software-properties-common 0.99.9.8 failed to install/upgrade: new software-properties-common package pre-removal script subprocess returned error exit sta

[Samuel Raker]

Public bug reported:

my computer froze, i rebooted, and got this error

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: software-properties-common 0.99.9.8
Uname: Linux 5.16.11-76051611-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.21
AptOrdering:
 software-properties-common:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Mon Apr  4 13:07:14 2022
ErrorMessage: new software-properties-common package pre-removal script 
subprocess returned error exit status 127
PackageArchitecture: all
Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.6
SourcePackage: software-properties
Title: package software-properties-common 0.99.9.8 failed to install/upgrade: 
new software-properties-common package pre-removal script subprocess returned 
error exit status 127
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package software-properties-common 0.99.9.8 failed to install/upgrade:
  new software-properties-common package pre-removal script subprocess
  returned error exit status 127

Status in software-properties package in Ubuntu:
  New

Bug description:
  my computer froze, i rebooted, and got this error

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: software-properties-common 0.99.9.8
  Uname: Linux 5.16.11-76051611-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.21
  AptOrdering:
   software-properties-common:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Mon Apr  4 13:07:14 2022
  ErrorMessage: new software-properties-common package pre-removal script 
subprocess returned error exit status 127
  PackageArchitecture: all
  Python3Details: /usr/local/bin/python3.10, Python 3.10.3, unpackaged
  PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.6
  SourcePackage: software-properties
  Title: package software-properties-common 0.99.9.8 failed to install/upgrade: 
new software-properties-common package pre-removal script subprocess returned 
error exit status 127
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968338/+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 1968109] Re: "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources

[Samuel Santaella]

Forgot to add: the date in the screen record file is not correct because
this laptop doesn't have a battery (that's on me; I'm working on that).
I don't remember exactly when I took the screen record itself, but the
recorded "last modified" time is April 2, 2022 at 7:33 PM. I transferred
it to my smartphone offline (via cable) before transferring it to
another computer (again via cable; it was the easy option for me) to
send this bug report. This is the Ubuntu Studio 22.04 "beta" ISO, not a
daily release.

In Ubuntu Studio 21.10, I can get the correct time after I connect to
the Internet, *because* I can do so.

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

Title:
  "Apply changes" button remains disabled after selecting Wi-Fi driver
  in Software Sources

Status in software-properties package in Ubuntu:
  New

Bug description:
  I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009
  MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of
  the box.

  What I expect to happen is something I can do successfully in Ubuntu
  Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that
  version. In KDE Settings I click on "Driver Manager", which
  automatically opens Software Sources (that's the only way I know how
  to get there). It finds and shows my [proprietary Broadcom] Wi-Fi
  driver; I click on it, then the "Apply Changes" button is enabled
  after a second or two. I click that, wait about half a minute with a
  progress bar in action below, and then the Wi-Fi options appear the
  notification area, allowing me to connect.

  I attached a screen record of what actually happens in Ubuntu Studio
  22.04 beta (thankfully this distro comes with screen recording
  software out of the box). When I click on "Driver Manager", a "xterm"
  window (version 372-1ubuntu1 I think?) opens unexpectedly with some
  code showing up in it (the code is in the screen record), shortly
  before Software Sources (version 0.99.20) opens as expected. The same
  driver still appears on the list. When I click on the driver, it seems
  to still take that second or two to transition, with some more code
  appearing in "xterm", but the "Apply Changes" button never enables
  itself. It remains disabled so I can't click it. The "revert" button
  directly next to it is also disabled. Thus, I can't connect my
  computer to Wi-Fi in 22.04 beta.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-qt 0.99.20
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: KDE
  Date: Fri Mar 18 17:00:53 2022
  LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1968109/+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 1968109] [NEW] "Apply changes" button remains disabled after selecting Wi-Fi driver in Software Sources

[Samuel Santaella]

Public bug reported:

I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009
MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of
the box.

What I expect to happen is something I can do successfully in Ubuntu
Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that
version. In KDE Settings I click on "Driver Manager", which
automatically opens Software Sources (that's the only way I know how to
get there). It finds and shows my [proprietary Broadcom] Wi-Fi driver; I
click on it, then the "Apply Changes" button is enabled after a second
or two. I click that, wait about half a minute with a progress bar in
action below, and then the Wi-Fi options appear the notification area,
allowing me to connect.

I attached a screen record of what actually happens in Ubuntu Studio
22.04 beta (thankfully this distro comes with screen recording software
out of the box). When I click on "Driver Manager", a "xterm" window
(version 372-1ubuntu1 I think?) opens unexpectedly with some code
showing up in it (the code is in the screen record), shortly before
Software Sources (version 0.99.20) opens as expected. The same driver
still appears on the list. When I click on the driver, it seems to still
take that second or two to transition, with some more code appearing in
"xterm", but the "Apply Changes" button never enables itself. It remains
disabled so I can't click it. The "revert" button directly next to it is
also disabled. Thus, I can't connect my computer to Wi-Fi in 22.04 beta.

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: software-properties-qt 0.99.20
ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
Uname: Linux 5.15.0-22-lowlatency x86_64
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: pass
CasperVersion: 1.468
CurrentDesktop: KDE
Date: Fri Mar 18 17:00:53 2022
LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
PackageArchitecture: all
SourcePackage: software-properties
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: software-properties (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug jammy

** Attachment added: "Screen record of the process I do in Ubuntu Studio 21.10 
to get my Wi-Fi driver working, but fails in 22.04."
   
https://bugs.launchpad.net/bugs/1968109/+attachment/5577783/+files/vokoscreenNG-2022-03-18_16-35-55.mp4

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

Title:
  "Apply changes" button remains disabled after selecting Wi-Fi driver
  in Software Sources

Status in software-properties package in Ubuntu:
  New

Bug description:
  I'm testing the live USB of Ubuntu Studio 22.04 beta on a mid-2009
  MacBook Pro. (Can't do a full install yet.) Wi-Fi doesn't work out of
  the box.

  What I expect to happen is something I can do successfully in Ubuntu
  Studio 21.10 (live USB). Wi-Fi also didn't work out of the box in that
  version. In KDE Settings I click on "Driver Manager", which
  automatically opens Software Sources (that's the only way I know how
  to get there). It finds and shows my [proprietary Broadcom] Wi-Fi
  driver; I click on it, then the "Apply Changes" button is enabled
  after a second or two. I click that, wait about half a minute with a
  progress bar in action below, and then the Wi-Fi options appear the
  notification area, allowing me to connect.

  I attached a screen record of what actually happens in Ubuntu Studio
  22.04 beta (thankfully this distro comes with screen recording
  software out of the box). When I click on "Driver Manager", a "xterm"
  window (version 372-1ubuntu1 I think?) opens unexpectedly with some
  code showing up in it (the code is in the screen record), shortly
  before Software Sources (version 0.99.20) opens as expected. The same
  driver still appears on the list. When I click on the driver, it seems
  to still take that second or two to transition, with some more code
  appearing in "xterm", but the "Apply Changes" button never enables
  itself. It remains disabled so I can't click it. The "revert" button
  directly next to it is also disabled. Thus, I can't connect my
  computer to Wi-Fi in 22.04 beta.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: software-properties-qt 0.99.20
  ProcVersionSignature: Ubuntu 5.15.0-22.22-lowlatency 5.15.19
  Uname: Linux 5.15.0-22-lowlatency x86_64
  ApportVersion: 2.20.11-0ubuntu79
  Architecture: amd64
  CasperMD5CheckResult: pass
  CasperVersion: 1.468
  CurrentDesktop: KDE
  Date: Fri Mar 18 17:00:53 2022
  LiveMediaBuild: Ubuntu-Studio 22.04 LTS "Jammy Jellyfish" - Beta amd64 
(20220329.1)
  PackageArchitecture: all
  SourcePackage: software-properties
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:

[Touch-packages] [Bug 1964808] [NEW] Wifi keeps disconnecting

[Samuel Hangouët]

Public bug reported:

I have a box with 802-11n and I run into a problem with my Lenovo laptop :
- when I change the wifi password, it connects immediately and works well
- the next time (for example after switching the airplane mode on and off), it 
fails and the network manager keeps asking me the password again and again

Please notice that I have no problem with other wifi access points (when
going in other places with my laptop), and my box works well with every
other devices (ubuntu laptops, android phones) but mine !

My laptop runs an updated 20.04.4, but the problem first came when I was
on 21.04. I then made a fresh install of 21.10 and then a fresh install
on 20.04 just to make sure the kernel was not involved. Even tried the
last Intel Clear Linux without success.

As a workaround, I tried to stop and restart wpa_supplicant:

sudo systemctl disable --now wpa_supplicant.service
sudo systemctl enable --now wpa_supplicant.service

but this did not solve the problem.
I also contacted the support of my ISP and they made a clear reset of my box 
without success.

Here is what I see in dmesg :

[ 4203.366374] wlp4s0: authenticate with e4:9e:12:8c:8e:1a
[ 4203.374010] wlp4s0: send auth to e4:9e:12:8c:8e:1a (try 1/3)
[ 4203.378464] wlp4s0: authenticated
[ 4203.383534] wlp4s0: associate with e4:9e:12:8c:8e:1a (try 1/3)
[ 4203.387408] wlp4s0: RX AssocResp from e4:9e:12:8c:8e:1a (capab=0x1411 
status=0 aid=6)
[ 4203.391628] wlp4s0: associated
[ 4203.399358] wlp4s0: deauthenticating from e4:9e:12:8c:8e:1a by local choice 
(Reason: 17=IE_DIFFERENT)


And here is the restult of lspci :

00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v6/7th Gen Core Processor 
Host Bridge/DRAM Registers (rev 02)
00:02.0 VGA compatible controller: Intel Corporation HD Graphics 620 (rev 02)
00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 
6th/7th/8th Gen Core Processor Gaussian Mixture Model
00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI 
Controller (rev 21)
00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP 
Thermal subsystem (rev 21)
00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI 
#1 (rev 21)
00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #1 
(rev f1)
00:1c.2 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 
(rev f1)
00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 
(rev f1)
00:1d.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #9 
(rev f1)
00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21)
00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21)
00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21)
00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21)
00:1f.6 Ethernet controller: Intel Corporation Ethernet Connection (4) I219-V 
(rev 21)
02:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. RTS525A PCI 
Express Card Reader (rev 01)
04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 88)
05:00.0 Non-Volatile memory controller: Samsung Electronics Co Ltd NVMe SSD 
Controller SM961/PM961

** Affects: network-manager (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Wifi keeps disconnecting

Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a box with 802-11n and I run into a problem with my Lenovo laptop :
  - when I change the wifi password, it connects immediately and works well
  - the next time (for example after switching the airplane mode on and off), 
it fails and the network manager keeps asking me the password again and again

  Please notice that I have no problem with other wifi access points
  (when going in other places with my laptop), and my box works well
  with every other devices (ubuntu laptops, android phones) but mine !

  My laptop runs an updated 20.04.4, but the problem first came when I
  was on 21.04. I then made a fresh install of 21.10 and then a fresh
  install on 20.04 just to make sure the kernel was not involved. Even
  tried the last Intel Clear Linux without success.

  As a workaround, I tried to stop and restart wpa_supplicant:

  sudo systemctl disable --now wpa_supplicant.service
  sudo systemctl enable --now wpa_supplicant.service

  but this did not solve the problem.
  I also contacted the support of my ISP and they made a clear reset of my box 
without success.

  Here is what I see in dmesg :

  [ 4203.366374] wlp4s0: authenticate with e4:9e:12:8c:8e:1a
  [ 4203.374010] wlp4s0: send auth to e4:9e:12:8c:8e:1a (try 1/3)
  [ 4203.378464] wlp4s0: authenticated
  [ 4203.383534] wlp4s0: associate with e4:9e:12:8c:8e:1a (try 1/3)
  [ 

[Touch-packages] [Bug 1930584] Re: InstallProgress is not being used as a context manager

[Samuel]

Ok, thanks Julian.

For future reference, which was the proper place to report this bug?
Here or over at bugs.debian?

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

Title:
  InstallProgress is not being used as a context manager

Status in python-apt package in Ubuntu:
  Won't Fix

Bug description:
  Package: python3-apt
  Version: 2.2.0

  As can be seen in the constructor, InstallProgress is designed to be
  used in a 'with' in order to properly close write_stream and
  status_stream:

  https://git.launchpad.net/python-apt/tree/apt/progress/base.py#n163

  This commit added support for using InstallProgress as a context
  manager:

  https://git.launchpad.net/python-
  apt/commit/?id=462c05b39eae5a0fa2270d329b03d4711742f20d

  It also modified a test, but didn't change the way InstallProgress is
  used by cache.py.

  This causes Python 3 to complain that InstallProgress's constructor
  leaves unclosed files:

  > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file 
<_io.TextIOWrapper name=4 mode='r' encoding='UTF-8'>
  >   with os.scandir(dirname) as it:
  > Object allocated at (most recent call last):
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", 
lineno 33
  > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 88
  > self . _aptcallback = i1Ii1i ( self )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 31
  > super ( ) . __init__ ( )
  >   File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 164
  > self.status_stream = os.fdopen(self.statusfd, "r")  # type: 
io.TextIOBase # noqa
  >   File "/usr/lib/python3.9/os.py", lineno 1023
  > return io.open(fd, *args, **kwargs)
  > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file 
<_io.TextIOWrapper name=5 mode='w' encoding='UTF-8'>
  >   with os.scandir(dirname) as it:
  > Object allocated at (most recent call last):
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", 
lineno 33
  > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 88
  > self . _aptcallback = i1Ii1i ( self )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 31
  > super ( ) . __init__ ( )
  >   File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 163
  > self.write_stream = os.fdopen(self.writefd, "w")  # type: io.TextIOBase
  >   File "/usr/lib/python3.9/os.py", lineno 1023
  > return io.open(fd, *args, **kwargs)

  
  The issue was identified on Ubuntu 21.04:

  > Linux ubuntu2104 5.11.0-17-generic #18-Ubuntu SMP Thu May 6 20:10:11
  > UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1930584/+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 1930584] Re: InstallProgress is not being used as a context manager

[Samuel]

Also reported to debian:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989389

** Bug watch added: Debian Bug tracker #989389
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=989389

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

Title:
  InstallProgress is not being used as a context manager

Status in python-apt package in Ubuntu:
  New

Bug description:
  Package: python3-apt
  Version: 2.2.0

  As can be seen in the constructor, InstallProgress is designed to be
  used in a 'with' in order to properly close write_stream and
  status_stream:

  https://git.launchpad.net/python-apt/tree/apt/progress/base.py#n163

  This commit added support for using InstallProgress as a context
  manager:

  https://git.launchpad.net/python-
  apt/commit/?id=462c05b39eae5a0fa2270d329b03d4711742f20d

  It also modified a test, but didn't change the way InstallProgress is
  used by cache.py.

  This causes Python 3 to complain that InstallProgress's constructor
  leaves unclosed files:

  > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file 
<_io.TextIOWrapper name=4 mode='r' encoding='UTF-8'>
  >   with os.scandir(dirname) as it:
  > Object allocated at (most recent call last):
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", 
lineno 33
  > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 88
  > self . _aptcallback = i1Ii1i ( self )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 31
  > super ( ) . __init__ ( )
  >   File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 164
  > self.status_stream = os.fdopen(self.statusfd, "r")  # type: 
io.TextIOBase # noqa
  >   File "/usr/lib/python3.9/os.py", lineno 1023
  > return io.open(fd, *args, **kwargs)
  > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file 
<_io.TextIOWrapper name=5 mode='w' encoding='UTF-8'>
  >   with os.scandir(dirname) as it:
  > Object allocated at (most recent call last):
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", 
lineno 33
  > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 88
  > self . _aptcallback = i1Ii1i ( self )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 31
  > super ( ) . __init__ ( )
  >   File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 163
  > self.write_stream = os.fdopen(self.writefd, "w")  # type: io.TextIOBase
  >   File "/usr/lib/python3.9/os.py", lineno 1023
  > return io.open(fd, *args, **kwargs)

  
  The issue was identified on Ubuntu 21.04:

  > Linux ubuntu2104 5.11.0-17-generic #18-Ubuntu SMP Thu May 6 20:10:11
  > UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-apt/+bug/1930584/+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 1930584] [NEW] InstallProgress is not being used as a context manager

[Samuel]

Public bug reported:

Package: python3-apt
Version: 2.2.0

As can be seen in the constructor, InstallProgress is designed to be
used in a 'with' in order to properly close write_stream and
status_stream:

https://git.launchpad.net/python-apt/tree/apt/progress/base.py#n163

This commit added support for using InstallProgress as a context
manager:

https://git.launchpad.net/python-
apt/commit/?id=462c05b39eae5a0fa2270d329b03d4711742f20d

It also modified a test, but didn't change the way InstallProgress is
used by cache.py.

This causes Python 3 to complain that InstallProgress's constructor
leaves unclosed files:

> /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file 
> <_io.TextIOWrapper name=4 mode='r' encoding='UTF-8'>
>   with os.scandir(dirname) as it:
> Object allocated at (most recent call last):
>   File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno 
> 33
> OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( )
>   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
> lineno 88
> self . _aptcallback = i1Ii1i ( self )
>   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
> lineno 31
> super ( ) . __init__ ( )
>   File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 164
> self.status_stream = os.fdopen(self.statusfd, "r")  # type: io.TextIOBase 
> # noqa
>   File "/usr/lib/python3.9/os.py", lineno 1023
> return io.open(fd, *args, **kwargs)
> /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file 
> <_io.TextIOWrapper name=5 mode='w' encoding='UTF-8'>
>   with os.scandir(dirname) as it:
> Object allocated at (most recent call last):
>   File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", lineno 
> 33
> OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( )
>   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
> lineno 88
> self . _aptcallback = i1Ii1i ( self )
>   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
> lineno 31
> super ( ) . __init__ ( )
>   File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 163
> self.write_stream = os.fdopen(self.writefd, "w")  # type: io.TextIOBase
>   File "/usr/lib/python3.9/os.py", lineno 1023
> return io.open(fd, *args, **kwargs)


The issue was identified on Ubuntu 21.04:

> Linux ubuntu2104 5.11.0-17-generic #18-Ubuntu SMP Thu May 6 20:10:11
> UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

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

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

Title:
  InstallProgress is not being used as a context manager

Status in python-apt package in Ubuntu:
  New

Bug description:
  Package: python3-apt
  Version: 2.2.0

  As can be seen in the constructor, InstallProgress is designed to be
  used in a 'with' in order to properly close write_stream and
  status_stream:

  https://git.launchpad.net/python-apt/tree/apt/progress/base.py#n163

  This commit added support for using InstallProgress as a context
  manager:

  https://git.launchpad.net/python-
  apt/commit/?id=462c05b39eae5a0fa2270d329b03d4711742f20d

  It also modified a test, but didn't change the way InstallProgress is
  used by cache.py.

  This causes Python 3 to complain that InstallProgress's constructor
  leaves unclosed files:

  > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file 
<_io.TextIOWrapper name=4 mode='r' encoding='UTF-8'>
  >   with os.scandir(dirname) as it:
  > Object allocated at (most recent call last):
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", 
lineno 33
  > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 88
  > self . _aptcallback = i1Ii1i ( self )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 31
  > super ( ) . __init__ ( )
  >   File "/usr/lib/python3/dist-packages/apt/progress/base.py", lineno 164
  > self.status_stream = os.fdopen(self.statusfd, "r")  # type: 
io.TextIOBase # noqa
  >   File "/usr/lib/python3.9/os.py", lineno 1023
  > return io.open(fd, *args, **kwargs)
  > /usr/lib/python3.9/glob.py:123: ResourceWarning: unclosed file 
<_io.TextIOWrapper name=5 mode='w' encoding='UTF-8'>
  >   with os.scandir(dirname) as it:
  > Object allocated at (most recent call last):
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/__init__.py", 
lineno 33
  > OOO0o000 = globals ( ) [ IIi1i111IiII ] . Backend ( )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 88
  > self . _aptcallback = i1Ii1i ( self )
  >   File "/opt/thinlinc/modules/thinlinc/packageinstaller/aptbackend.py", 
lineno 31
  > super ( ) . __init__ ( )
  >   File 

[Touch-packages] [Bug 1928996] Re: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend

[Samuel Ainsworth]

Just woke up from a suspend once again and still getting this issue. The
most recent log lines are

May 19 17:30:18 skainswo-X58A-UD3R systemd[1798]: Starting Sound Service...
May 19 17:30:18 skainswo-X58A-UD3R systemd[1798]: Started Sound Service.
May 19 17:30:27 skainswo-X58A-UD3R pulseaudio[1811]: GetManagedObjects() 
failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 
'org.bluez': timed out (service_start_timeout=25000ms)
May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: ALSA woke us up to write 
new data to the device, but there was actually nothing to write.
May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: Most likely this is a bug 
in the ALSA driver 'snd_hda_intel'. Please report this issue to the ALSA 
developers.
May 19 17:33:38 skainswo-X58A-UD3R pulseaudio[1811]: We were woken up with 
POLLOUT set -- however a subsequent snd_pcm_avail() returned 0 or another value 
< min_avail.

But these logs are from two days ago...

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

Title:
  [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all
  after resuming from suspend

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound works fine after an initial boot up, but fails after resuming
  from a suspend. Going to the "Sound" section in the Settings app, I no
  longer see the HDMI device presented as an output option when this
  occurs.

  I suspect this is due to issues with pulseaudio. At least, running
  `pulseaudio -k && pulseaudio --start`, then restarting apps seems to
  fix the issue. In particular I've found that the pulseaudio systemd
  service has failed after resuming from suspend. After scanning through
  journalctl, there are a few suspect sections. I've attached the logs
  in their entirety, and an abbreviated log with only sections that I
  found interesting. I cannot be sure which are at fault, but hopefully
  it helps narrow the search.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  skainswo  2282708 F pulseaudio
   /dev/snd/controlC0:  skainswo  2282708 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 19 16:08:41 2021
  InstallationDate: Installed on 2020-05-15 (369 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/home/username/.nix-profile/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  skainswo  2282708 F pulseaudio
   /dev/snd/controlC0:  skainswo  2282708 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-08-08 (284 days ago)
  dmi.bios.date: 04/20/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: X58A-UD3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: X58A-UD3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928996/+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 1928996] Re: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend

[Samuel Ainsworth]

As a quick update, I managed to kill all of the spurious pulseaudio
processes that had been lying around as a result of `pulseaudio -k &&
pulseaudio --start` and got the systemd pulseaudio process back on its
feet. Then I confirmed that the audio worked, suspended my system, and
woke it up again and the audio still works!

Therefore I suspect that pulseaudio processes started by the user in
terminal sessions (daemonized) do not survive the suspend/resume cycle
for some reason(?). How the systemd pulseaudio process failed to begin
with remains the larger issue, however.

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

Title:
  [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all
  after resuming from suspend

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound works fine after an initial boot up, but fails after resuming
  from a suspend. Going to the "Sound" section in the Settings app, I no
  longer see the HDMI device presented as an output option when this
  occurs.

  I suspect this is due to issues with pulseaudio. At least, running
  `pulseaudio -k && pulseaudio --start`, then restarting apps seems to
  fix the issue. In particular I've found that the pulseaudio systemd
  service has failed after resuming from suspend. After scanning through
  journalctl, there are a few suspect sections. I've attached the logs
  in their entirety, and an abbreviated log with only sections that I
  found interesting. I cannot be sure which are at fault, but hopefully
  it helps narrow the search.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  skainswo  2282708 F pulseaudio
   /dev/snd/controlC0:  skainswo  2282708 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 19 16:08:41 2021
  InstallationDate: Installed on 2020-05-15 (369 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/home/username/.nix-profile/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
  Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  skainswo  2282708 F pulseaudio
   /dev/snd/controlC0:  skainswo  2282708 F pulseaudio
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-08-08 (284 days ago)
  dmi.bios.date: 04/20/2010
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: FA
  dmi.board.name: X58A-UD3R
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: X58A-UD3R
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1928996/+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 1928996] [NEW] [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all after resuming from suspend

[Samuel A]

Public bug reported:

Sound works fine after an initial boot up, but fails after resuming from
a suspend. Going to the "Sound" section in the Settings app, I no longer
see the HDMI device presented as an output option when this occurs.

I suspect this is due to issues with pulseaudio. At least, running
`pulseaudio -k && pulseaudio --start`, then restarting apps seems to fix
the issue. In particular I've found that the pulseaudio systemd service
has failed after resuming from suspend. After scanning through
journalctl, there are a few suspect sections. I've attached the logs in
their entirety, and an abbreviated log with only sections that I found
interesting. I cannot be sure which are at fault, but hopefully it helps
narrow the search.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
Uname: Linux 5.4.0-73-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.17
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  skainswo  2282708 F pulseaudio
 /dev/snd/controlC0:  skainswo  2282708 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed May 19 16:08:41 2021
InstallationDate: Installed on 2020-05-15 (369 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
PackageArchitecture: all
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/home/username/.nix-profile/bin/zsh
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed
Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  skainswo  2282708 F pulseaudio
 /dev/snd/controlC0:  skainswo  2282708 F pulseaudio
Symptom_Jack: Digital Out, HDMI
Symptom_Type: No sound at all
Title: [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all
UpgradeStatus: Upgraded to focal on 2020-08-08 (284 days ago)
dmi.bios.date: 04/20/2010
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: FA
dmi.board.name: X58A-UD3R
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrFA:bd04/20/2010:svnGigabyteTechnologyCo.,Ltd.:pnX58A-UD3R:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnX58A-UD3R:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
dmi.product.name: X58A-UD3R
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

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


** Tags: amd64 apport-bug focal third-party-packages

** Attachment added: "pulseaudio-logs.zip"
   
https://bugs.launchpad.net/bugs/1928996/+attachment/5498825/+files/pulseaudio-logs.zip

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

Title:
  [X58A-UD3R, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] No sound at all
  after resuming from suspend

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  Sound works fine after an initial boot up, but fails after resuming
  from a suspend. Going to the "Sound" section in the Settings app, I no
  longer see the HDMI device presented as an output option when this
  occurs.

  I suspect this is due to issues with pulseaudio. At least, running
  `pulseaudio -k && pulseaudio --start`, then restarting apps seems to
  fix the issue. In particular I've found that the pulseaudio systemd
  service has failed after resuming from suspend. After scanning through
  journalctl, there are a few suspect sections. I've attached the logs
  in their entirety, and an abbreviated log with only sections that I
  found interesting. I cannot be sure which are at fault, but hopefully
  it helps narrow the search.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 5.4.0-73.82-generic 5.4.106
  Uname: Linux 5.4.0-73-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.17
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  skainswo  2282708 F pulseaudio
   /dev/snd/controlC0:  skainswo  2282708 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 19 16:08:41 2021
  InstallationDate: Installed on 2020-05-15 (369 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/home/username/.nix-profile/bin/zsh
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA 

[Touch-packages] [Bug 1889416] Re: pulseaudio.service: Start request repeated too quickly.

[Samuel PHAN]

As a workaround, you can try to edit the systemd file
"/usr/lib/systemd/user/pulseaudio.service" and add the line:

```
RestartSec=2s
```

Your [Service] section would look like to this:

```
[Service]
ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal
LockPersonality=yes
MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
Restart=on-failure
RestartSec=2s
RestrictNamespaces=yes
SystemCallArchitectures=native
SystemCallFilter=@system-service
# Note that notify will only work if --daemonize=no
Type=notify
UMask=0077
```

Samuel

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

Title:
  pulseaudio.service: Start request repeated too quickly.

Status in fscrypt package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  PA doesn't start on it's own after the latest update.

  ```
  nafallo@wendigo:~$ systemctl --user status pulseaudio
  ● pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: failed (Result: exit-code) since Wed 2020-07-29 14:59:19 CEST; 
11min ago
  TriggeredBy: ● pulseaudio.socket
  Process: 2774 ExecStart=/usr/bin/pulseaudio --daemonize=no 
--log-target=journal (code=exited, status=1/FAILURE)
 Main PID: 2774 (code=exited, status=1/FAILURE)

  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Scheduled restart 
job, restart counter is at 5.
  Jul 29 14:59:19 wendigo systemd[2664]: Stopped Sound Service.
  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Start request 
repeated too quickly.
  Jul 29 14:59:19 wendigo systemd[2664]: pulseaudio.service: Failed with result 
'exit-code'.
  Jul 29 14:59:19 wendigo systemd[2664]: Failed to start Sound Service.
  Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Start request 
repeated too quickly.
  Jul 29 14:59:20 wendigo systemd[2664]: pulseaudio.service: Failed with result 
'exit-code'.
  Jul 29 14:59:20 wendigo systemd[2664]: Failed to start Sound Service.
  ```

  But works after starting it manually.

  ```
  nafallo@wendigo:~$ systemctl --user start pulseaudio
  nafallo@wendigo:~$ systemctl --user status pulseaudio
  ● pulseaudio.service - Sound Service
   Loaded: loaded (/usr/lib/systemd/user/pulseaudio.service; enabled; 
vendor preset: enabled)
   Active: active (running) since Wed 2020-07-29 15:11:14 CEST; 5min ago
  TriggeredBy: ● pulseaudio.socket
 Main PID: 5675 (pulseaudio)
   CGroup: /user.slice/user-1000.slice/user@1000.service/pulseaudio.service
   └─5675 /usr/bin/pulseaudio --daemonize=no --log-target=journal

  Jul 29 15:11:13 wendigo systemd[2664]: Starting Sound Service...
  Jul 29 15:11:14 wendigo systemd[2664]: Started Sound Service.
  ```

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3.5
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  nafallo5675 F pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Jul 29 15:11:28 2020
  InstallationDate: Installed on 2018-06-27 (763 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/11/2019
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.12.1
  dmi.board.name: 0W970W
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A03
  dmi.chassis.type: 10
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.12.1:bd12/11/2019:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0W970W:rvrA03:cvnDellInc.:ct10:cvr:
  dmi.product.family: XPS
  dmi.product.name: XPS 13 9370
  dmi.product.sku: 07E6
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fscrypt/+bug/1889416/+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 1916722] Re: Pulseaudio fails to start after reboot if home partition is encrypted

[Samuel PHAN]

Hi Anton,

As a workaround, you can try to edit the systemd file
"/usr/lib/systemd/user/pulseaudio.service" and add the line:

```
RestartSec=2s
```

Your [Service] section would look like to this:

```
[Service]
ExecStart=/usr/bin/pulseaudio --daemonize=no --log-target=journal
LockPersonality=yes
MemoryDenyWriteExecute=yes
NoNewPrivileges=yes
Restart=on-failure
RestartSec=2s
RestrictNamespaces=yes
SystemCallArchitectures=native
SystemCallFilter=@system-service
# Note that notify will only work if --daemonize=no
Type=notify
UMask=0077
```

Samuel

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

Title:
  Pulseaudio fails to start after reboot if home partition is encrypted

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  It seems that with Ubuntu 20.10, Pulseaudio now tries to start as main
  user too early, before user logs in and the home partition is
  decrypted. Probably pulseaudio should not start as main user before
  login of this user.

  Starting pulseaudio manually after login works.

  grep 'pulseaudio' /var/log/syslog
  Feb 24 10:52:31 aziber systemd[1451]: Not generating service for XDG 
autostart app-pulseaudio-autostart.service, startup phases are not supported.
  Feb 24 10:52:31 aziber dbus-daemon[972]: [system] Activating via systemd: 
service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' 
requested by ':1.30' (uid=123 pid=1497 comm="/usr/bin/pulseaudio --daemonize=no 
--log-target=jo" label="unconfined")
  Feb 24 10:52:38 aziber systemd[3631]: Not generating service for XDG 
autostart app-pulseaudio-autostart.service, startup phases are not supported.
  Feb 24 10:52:38 aziber pulseaudio[3690]: Failed to create secure directory 
(/home/anton/.config/pulse): No such file or directory
  Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
  Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Scheduled restart 
job, restart counter is at 1.
  Feb 24 10:52:38 aziber pulseaudio[3899]: Failed to create secure directory 
(/home/anton/.config/pulse): No such file or directory
  Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 24 10:52:38 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart 
job, restart counter is at 2.
  Feb 24 10:52:39 aziber pulseaudio[4128]: Failed to create secure directory 
(/home/anton/.config/pulse): No such file or directory
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart 
job, restart counter is at 3.
  Feb 24 10:52:39 aziber pulseaudio[4311]: Failed to create secure directory 
(/home/anton/.config/pulse): No such file or directory
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart 
job, restart counter is at 4.
  Feb 24 10:52:39 aziber pulseaudio[4493]: Failed to create secure directory 
(/home/anton/.config/pulse): No such file or directory
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Main process 
exited, code=exited, status=1/FAILURE
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Scheduled restart 
job, restart counter is at 5.
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Start request 
repeated too quickly.
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.service: Failed with result 
'exit-code'.
  Feb 24 10:52:39 aziber systemd[3609]: pulseaudio.socket: Failed with result 
'service-start-limit-hit'.
  Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: Connection failure: 
Connection refused
  Feb 24 10:52:42 aziber pulseaudio.desktop[5720]: pa_context_connect() failed: 
Connection refused
  Feb 24 10:52:42 aziber gnome-session[5663]: gnome-session-binary[5663]: 
WARNING: App 'pulseaudio.desktop' exited with code 1
  Feb 24 10:52:42 aziber gnome-session-binary[5663]: WARNING: App 
'pulseaudio.desktop' exited with code 1
  Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed 
to add PIDs to scope's control group: No such process
  Feb 24 10:52:42 aziber systemd[3609]: app-gnome-pulseaudio-5715.scope: Failed 
with result 'resources'.
  

[Touch-packages] [Bug 520546] Re: [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Samuel thibault]

It seems I have to insist again: patch
https://launchpadlibrarian.net/405256420/patch should definitely really
really be applied. As explained in
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1508146/comments/73 that script should really *not* pass
--force to setupcon. There is no reason for that except that it was
copy/pasted from the Debian installer, where it is needed due to the use
of bterm. On Ubuntu it should really not be used.

Can somebody at last apply that patch that has been waiting for 2 years?

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

Title:
  [SRU]Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Fix Released
Status in kbd package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid
Status in console-setup source package in Lucid:
  New
Status in kbd source package in Lucid:
  New
Status in xorg-server source package in Lucid:
  New
Status in console-setup source package in Maverick:
  New
Status in kbd source package in Maverick:
  New
Status in xorg-server source package in Maverick:
  New
Status in console-setup source package in Xenial:
  Confirmed
Status in kbd source package in Xenial:
  Won't Fix
Status in xorg-server source package in Xenial:
  Confirmed
Status in console-setup source package in Bionic:
  Fix Released
Status in kbd source package in Bionic:
  Won't Fix
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Invalid
Status in console-setup source package in Cosmic:
  Fix Released
Status in kbd source package in Cosmic:
  Won't Fix
Status in linux source package in Cosmic:
  Won't Fix
Status in xorg-server source package in Cosmic:
  Invalid
Status in console-setup source package in Disco:
  Fix Released
Status in kbd source package in Disco:
  Won't Fix
Status in linux source package in Disco:
  Won't Fix
Status in xorg-server source package in Disco:
  Invalid
Status in console-setup source package in Eoan:
  Fix Released
Status in kbd source package in Eoan:
  Fix Released
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Invalid

Bug description:
  (kbd)
  [Impact]

   * kbd_mode -u is documented to break keyboards in modes other than xlate and 
unicode, while it is still called by some scripts. Those scripts are called 
transitively by maintainer scripts such as the one already fixed in 
console-setup. 
   * To avoid accidentally breaking keyboards a -f option is added to force 
such breaking mode changes. Without -f only the safe mode changes are performed 
and an error is printed when the requested mode change is not safe. Next 
upstream version will also exit with error, but the cherry-picked fix makes 
kbd_mode return success even when the mode switch is not performed to avoid 
regressions of scripts.

  [Test case]

   * Verify that safe mode switches work and dangerous ones are skipped
  without -f. Please note that the test will temporarily break the
  system's keyboard and it is recommended to run the test in a VM.

  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4; echo $?
  The keyboard is in Unicode (UTF-8) mode
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -a -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in xlate (8-bit) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty4; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty4
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in some unknown mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -f -u -C /dev/tty0; echo $?
  0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in Unicode (UTF-8) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -s -C /dev/tty0
  rbalint@MacBookAir-test:~$ sudo kbd_mode -C /dev/tty0
  The keyboard is in raw (scancode) mode
  rbalint@MacBookAir-test:~$ sudo kbd_mode -u -C /dev/tty0; echo $?
  The keyboard is in raw (scancode) mode
  Changing to the requested mode may make your keyboard unusable, please use -f 
to force the change.
  0

  [Regression Potential]

   * kbd_mode stops performing breaking mode switches and this may make
  scripts ineffective when trying to perform a breaking change. This is
  the intention of the change and the emitter error helps in finding the
  offending script.

  The following packages found to call kbd_mode directly:
  console-setup
  xinit
  console-cyrillic
  initramfs-tools
  dracut
  console-tools
  xview
  ubiquity's embedded 

[Touch-packages] [Bug 1905194] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Lucien SAMUEL]

Upgrading from 18.04 to 20.04 (LTS)

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading from 18.04 to 20.04 (LTS)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18
  Uname: Linux 4.15.0-125-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 12:04:13 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-08-20 (1190 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1905194/+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 1905194] Re: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status 1

[Lucien SAMUEL]

Upgrading from 18.04 to 20.04 (LTS)

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading from 18.04 to 20.04 (LTS)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18
  Uname: Linux 4.15.0-125-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 12:04:13 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-08-20 (1190 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1905194/+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 1905194] [NEW] package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: installed initramfs-tools package post-installation script subprocess returned error exit status

[Lucien SAMUEL]

Public bug reported:

Upgrading from 18.04 to 20.04 (LTS)

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: initramfs-tools 0.136ubuntu6.3
ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18
Uname: Linux 4.15.0-125-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.13
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Nov 22 12:04:13 2020
ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
InstallationDate: Installed on 2017-08-20 (1190 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: initramfs-tools
Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade:
  installed initramfs-tools package post-installation script subprocess
  returned error exit status 1

Status in initramfs-tools package in Ubuntu:
  New

Bug description:
  Upgrading from 18.04 to 20.04 (LTS)

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: initramfs-tools 0.136ubuntu6.3
  ProcVersionSignature: Ubuntu 4.15.0-125.128-generic 4.15.18
  Uname: Linux 4.15.0-125-generic x86_64
  ApportVersion: 2.20.11-0ubuntu27.13
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Nov 22 12:04:13 2020
  ErrorMessage: installed initramfs-tools package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2017-08-20 (1190 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: initramfs-tools
  Title: package initramfs-tools 0.136ubuntu6.3 failed to install/upgrade: 
installed initramfs-tools package post-installation script subprocess returned 
error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1905194/+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 483928] Re: ssh-keyscan(1) exits prematurely on some non-fatal errors

[Samuel]

8 years later, we saw this on one of our customer's systems. Looking at
the status of this entry, it looks like it's still unresolved?

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

Title:
  ssh-keyscan(1) exits prematurely on some non-fatal errors

Status in portable OpenSSH:
  Confirmed
Status in openssh package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: openssh-client

  This concerns openssh-client 1:5.1p1-5ubuntu1 in Karmic.

  I am using ssh-keyscan(1) for its intended purpose: building an
  ssh_known_hosts file for a large network. Most of the hosts on this
  network are well-maintained systems, with properly-functioning SSH
  servers, and present no difficulty to the program.

  However, a handful of hosts are barely alive, with SSH servers that
  are not exactly in good working order. ssh-keyscan(1) currently will
  scan these systems, encounter some form of error, and then---right
  here is the problem---exit in the middle of the scan. The last bit of
  stderr output may look like

# A.B.C.D SSH-2.0-OpenSSH_4.3
# A.B.C.E SSH-2.0-OpenSSH_4.3
# A.B.C.F SSH-1.99-OpenSSH_3.7p1
Connection closed by A.B.C.F

  or

# A.B.C.D SSH-2.0-OpenSSH_4.1
# A.B.C.E SSH-2.0-OpenSSH_4.1
# A.B.C.F SSH-2.0-mpSSH_0.1.0
Received disconnect from A.B.C.F: 10:  Protocol error

  or

# A.B.C.D SSH-2.0-OpenSSH_4.4p1
# A.B.C.E SSH-2.0-OpenSSH_5.0p1
# A.B.C.F SSH-2.0-mpSSH_0.1.0
Received disconnect from A.B.C.F: 11:  SSH Disabled

  (These are the different failure modes I've observed to date)

  ssh-keyscan(1) needs to be robust to these kinds of errors---simply
  make a note of them, and continue on with the scan. I don't want to
  have to find out which systems are misbehaving by running and re-
  running the scan (each run yields at most one bad host, obviously),
  nor manually edit out the few bad apples from the input list of hosts
  (especially considering that this particular subset can change over
  time). Neither is feasible when the number of hosts being scanned is
  very large.

To manage notifications about this bug go to:
https://bugs.launchpad.net/openssh/+bug/483928/+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 1882966] Re: Recent updates to some packages make it impossible to build an Orca Master in Ubuntu-MATE 20.04

[Samuel thibault]

I guess this is due to the following change in at-spi2-atk:

* Meson: don't hard-code shared_library (!19).

which made meson emit a lot of new libraries in Requires.private of atk-
bridge-2.0.pc, and thus the -dev package now has to add them in Depends.

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

Title:
  Recent updates to some packages make it impossible to build an Orca
  Master in Ubuntu-MATE 20.04

Status in at-spi2-atk package in Ubuntu:
  Confirmed

Bug description:
  The recent update of the libatk-bridge2.0-0 libatk-bridge2.0-dev and
  libatk-adapter packages makes it impossible to build Orca Master in
  Ubuntu-MATE 20.04. Reproduction steps:

  1. You need to have Ubuntu-MATE 20.04 with the latest updates;

  2. Install the following packages:

  git autoconf autopoint yelp-tools libgstreamer1.0-dev python-gi-dev
  libatspi2.0-dev libatk-bridge2.0-dev

  3. Clone the Orca repository:

  git clone https://gitlab.gnome.org/GNOME/orca.git

  4. Navigate to the cloned repository:

  cd orca

  5. Run the command:

  ./autogen.sh

  The command output ends with the following lines:

  checking for ATKBRIDGE... no
  configure: error: Package requirements (atk-bridge-2.0 >= 2.26) were not met:
  Package 'atk', required by 'atk-bridge-2.0', not found
  Consider adjusting the PKG_CONFIG_PATH environment variable if you
  installed software in a non-standard prefix.
  Alternatively, you may set the environment variables ATKBRIDGE_CFLAGS
  and ATKBRIDGE_LIBS to avoid the need to call pkg-config.
  See the pkg-config man page for more details.

  If libatk-bridge2.0-0 libatk-bridge2.0-dev and libatk-adapter are
  forcibly downgraded to version 2.34.1-3, this error disappears.

  Many thanks for fixing this issues.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1882966/+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 1638842] Re: network-manager does not manage ethernet and bluetooth interfaces when Ubuntu 16.10 is installed using chroot/netboot method

[Samuel Alves Gonçalves]

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

New Install from netboot method ubuntu 20.04 focal same error, I did
everything, but nothing worked

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

Title:
  network-manager does not manage ethernet and bluetooth interfaces when
  Ubuntu 16.10 is installed using chroot/netboot method

Status in network-manager package in Ubuntu:
  Won't Fix

Bug description:
  Hello,

  I installed Ubuntu 16.10 using a chroot. I use network-manager to
  manage connections. My system is up-to-date (so I use network-manager
  1.2.4-0ubuntu1).

  Wifi works perfectly but I cannot connect to wired networks and using
  my phone's Bluetooth connection. Corresponding devices are said to be
  unmanaged by network-manager. nmcli dev outputs:

  DEVICETYPE  STATE CONNECTION 
  enp1s0ethernet  unmanaged -- 
  wlp2s0wifi  disconnected  --
  6C:9B:02:2C:EE:2C btunmanaged -- 
  hfp/org/bluez/hci0/dev_6C_9B_02_2C_EE_2C  gsm   unmanaged -- 
  loloopback  unmanaged -- 

  The following command has no effect:
  sudo nmcli dev set enp1s0 managed yes

  I can connect to a wired connection by doing:
  ifconfig enp1s0 up
  dhclient enp1s0

  There is nothing in the file /etc/network/interfaces.

  Everything works perfectly if I downgrade network-manager to this
  version: network-manager_1.2.2-0ubuntu0.16.04.3_amd64.deb
  (http://packages.ubuntu.com/xenial-updates/amd64/network-
  manager/download). I had to install libreadline6 and downgrade nplan
  to meet dependencies.

  I don't know what to join to this bug report so please ask in case
  anything is needed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1638842/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Samuel Kennedy]

Have the same issue on a lot of laptop in my company, we have a webteam
that work with Ubuntu and i update all machines for the last version
19.10, after this update all laptops don't have a internal micro.

Model: HP 830 G6

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1840725] Re: Microphone not working in Ubuntu 18.04.3 LTS on new hp-spectre-x360-convertible-15 laptop

[Samuel Kennedy]

Have the same issue on a lot of laptop in my companie, we hame a webteam
that work with Ubuntu and i update all machines for the last version
19.10, after this update all laptops don't have a internal micro.

Model: HP 830 G6

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

Title:
  Microphone not working in Ubuntu 18.04.3 LTS on new hp-
  spectre-x360-convertible-15 laptop

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  Internal Microphone does not work in Ubuntu 18.04.3 LTS in a new hp-
  spectre-x360-convertible-15 laptop. The microphone works perfectly on
  Windows 10 (present in Dual boot mode).

  Initially, Internal Microphone was not even detected but installing
  alsa-tools-gui and overriding pin 0x12 to the Internal Microphone
  fixed that issue. [Pin 0x13 does not work and causes static in a
  headphone if it is plugged in.]

  Microphone is not able to pick up any sound. I changed levels/settings in 
alsamixer, pavucontrol without any success:
  In alsamixer: Experimented with levels ranging from very low to very high for 
Internal Mic, Capture, etc.
  In pavucontrol: Set the Internal Mic as a fallback device, unlocked the 
channels for the mic, experimented with reducing the level for one of the 
channels (reduced right mic level to Silence while keeping the left mic level 
normal/high and vice versa).

  alsa-info:
  http://alsa-project.org/db/?f=cf6d3ccc6372f955da7d99df07afbcb31d5a6c7f

  arecord -l
   List of CAPTURE Hardware Devices 
  card 0: PCH [HDA Intel PCH], device 0: ALC285 Analog [ALC285 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1840725/+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 1826944] [NEW] green bars in ubuntu videos

[Samuel Comeau]

Public bug reported:

When I try to play a .mp4 video in Ubuntu Video, I get a screen with
green bars all over. The problem does not occur when I switch to my
nvidia graphics card.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
Uname: Linux 5.0.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 29 19:02:44 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590]
   Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] 
[1043:1590]
InstallationDate: Installed on 2019-04-28 (1 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
MachineType: ASUSTeK COMPUTER INC. GL753VE
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=0e415d44-e0a5-4ad3-8d86-ebc66f155d5e ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/16/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: GL753VE.307
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: GL753VE
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No  Asset  Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL753VE.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: ROG
dmi.product.name: GL753VE
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.2-1ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20180925-2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1

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


** Tags: amd64 apport-bug disco ubuntu

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

Title:
  green bars in ubuntu videos

Status in xorg package in Ubuntu:
  New

Bug description:
  When I try to play a .mp4 video in Ubuntu Video, I get a screen with
  green bars all over. The problem does not occur when I switch to my
  nvidia graphics card.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6
  Uname: Linux 5.0.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr 29 19:02:44 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  DkmsStatus: nvidia, 418.56, 5.0.0-13-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 630 [8086:591b] (rev 04) (prog-if 00 [VGA 
controller])
 Subsystem: ASUSTeK Computer Inc. HD Graphics 630 [1043:1590]
 Subsystem: ASUSTeK Computer Inc. GP107M [GeForce GTX 1050 Ti Mobile] 
[1043:1590]
  InstallationDate: Installed on 2019-04-28 (1 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  MachineType: ASUSTeK COMPUTER INC. GL753VE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=0e415d44-e0a5-4ad3-8d86-ebc66f155d5e ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: GL753VE.307
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: GL753VE
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No  Asset  Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrGL753VE.307:bd04/16/2018:svnASUSTeKCOMPUTERINC.:pnGL753VE:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL753VE:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: ROG
  dmi.product.name: GL753VE
  dmi.product.version: 1.0
  dmi.sys.vendor: 

[Touch-packages] [Bug 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Samuel thibault]

But scripts changing between scancode and ascii/unicode (such as for
some terminal emulation, dosbox, etc.) would break. I'm not saying they
are widespread, but I have seen this kind of use, and requiring such
flag will suddenly break them.

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Confirmed
Status in kbd package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in console-setup source package in Bionic:
  Confirmed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Confirmed
Status in console-setup source package in Cosmic:
  Confirmed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Confirmed
Status in console-setup source package in Disco:
  In Progress
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Confirmed
Status in console-setup source package in Eoan:
  Confirmed
Status in kbd source package in Eoan:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Confirmed

Bug description:
  
  (console-setup)
  [Impact]

   * keyboard-configuration's postinst changes keyboard mode breaking X
  keys.

  [Test Case]

   * Ssh to a system or open a terminal and unset DISPLAY

  $ echo $DISPLAY
  
  $

   * Check kbd mode, should be raw (set by kbd_mode -s) or unknown:
 $ sudo kbd_mode
 The keyboard is in some unknown mode
 $ sudo kbd_mode
 The keyboard is in raw (scancode) mode
 $

   * Install or reinstall kbd-configuration

 $ sudo apt install --reinstall keyboard-configuration 
 ...
 Setting up keyboard-configuration (1.178ubuntu11) ...
 Your console font configuration will be updated the next time your system
 boots. If you want to update it now, run 'setupcon' from a virtual console.
 ...

   * With the fixed package you should see the note above and the kbd
  mode must stay the same:

 $ sudo kbd_mode
 The keyboard is in raw (scancode) mode
 $

   * The unfixed package sets the kbd mode to unicode:

 $  sudo kbd_mode
 The keyboard is in Unicode (UTF-8) mode
 $

  [Regression Potential]

   * The change may break debian-installer changing the keyboard mode, this 
should also be tested.
   * In general changing the postinst script may make the package unable to 
install, but this is tested in generic environment and the change to the 
postinst script is very small.

  [Original Bug Text]
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Samuel thibault]

How will kbd_mode know whether it's safe or not?

Adding a -f option to kbd_mode will at best break some *other* existing
scripts, while this very script should really definitely *NOT* pass -f
to setupcon. That is the nonsense which needs to be fixed.

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Confirmed
Status in kbd package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in console-setup source package in Bionic:
  Confirmed
Status in kbd source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Confirmed
Status in console-setup source package in Cosmic:
  Confirmed
Status in kbd source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Confirmed
Status in console-setup source package in Disco:
  In Progress
Status in kbd source package in Disco:
  Confirmed
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Confirmed
Status in console-setup source package in Eoan:
  Confirmed
Status in kbd source package in Eoan:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Confirmed

Bug description:
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Samuel thibault]

That is when updating the console-setup package, yes. As mentioned on
https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1508146/comments/73 that's because its config script passes
--force to setupcon, it really shouldn't, as mentioned there

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed
Status in console-setup source package in Bionic:
  Confirmed
Status in linux source package in Bionic:
  Confirmed
Status in xorg-server source package in Bionic:
  Confirmed
Status in console-setup source package in Cosmic:
  Confirmed
Status in linux source package in Cosmic:
  Confirmed
Status in xorg-server source package in Cosmic:
  Confirmed
Status in console-setup source package in Disco:
  In Progress
Status in linux source package in Disco:
  Confirmed
Status in xorg-server source package in Disco:
  Confirmed
Status in console-setup source package in Eoan:
  Confirmed
Status in linux source package in Eoan:
  Confirmed
Status in xorg-server source package in Eoan:
  Confirmed

Bug description:
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT switch from Alt+Left/Right

[Samuel thibault]

Xorg can't do anything about intercepting Alt-key, it's the kernel which
takes the shortcut away.

Again, as mentioned on https://bugs.launchpad.net/ubuntu/+source
/console-setup/+bug/520546/comments/66

«
proposed fix: 
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attachment/5227480/+files/patch

As mentioned in 
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146 , Ubuntu 
probably wants to apply the attached patch.
»

Can somebody with t he proper rights do something about this? That patch
exists since months now...

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY, and/or unwanted VT
  switch from Alt+Left/Right

Status in console-setup package in Ubuntu:
  Confirmed
Status in linux package in Ubuntu:
  Confirmed
Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  WORKAROUND:

  sudo kbd_mode -s

  ORIGINAL DESCRIPTION:

  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1812095] Re: console login loop after entering username followed by RETURN

[SAMUEL TEIXEIRA SANTOS]

I'm have the same problem.
Not even the update to linux-image-4.15.0-45-generic solved this.

Like @lokkoze, I'm still using (choosing) linux-image-4.15.0-43-generic
where the problem  not exist

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

Title:
  console login loop after entering username followed by RETURN

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
   login: 
  password:

  Just do nothing. About two seconds later ...

  login:
  password:

  login:
  password:

  login:
  password:

  After this being displayed three times:

  "Too many failure" or so and login is restarting.

  You cant login at all. Only solution: clear the password for the
  account you want to login with.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: login 1:4.5-1ubuntu1
  ProcVersionSignature: Ubuntu 4.18.0-14.15-generic 4.18.20
  Uname: Linux 4.18.0-14-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 16 19:34:30 2019
  InstallationDate: Installed on 2011-10-19 (2645 days ago)
  InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
  SourcePackage: shadow
  UpgradeStatus: Upgraded to cosmic on 2018-11-03 (74 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shadow/+bug/1812095/+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 1508146] Re: Alt+left/right arrows switch between tty consoles (Gnome Shell vanishes), cannot disable

[Samuel thibault]

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

Is there really any reason why keyboard-configuration.postinst passes
--force to setupcon?

In Debian we do this in the Debian installer because it is running
within a bterm and thus can't detect it's running on the Linux console.
But we never do this for an installed system. Apparently Ubuntu took
that code snipped and dropped the check for being running within the
Debian installer, and thus erroneously run with --force when DISPLAY is
empty (typically from unattended upgrades and such), with the resulting
observed effects of this bug report.

I guess Ubuntu wants to apply the attached patch

** Attachment added: "proposed fix"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1508146/+attachment/5227479/+files/patch

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

Title:
  Alt+left/right arrows switch between tty consoles (Gnome Shell
  vanishes), cannot disable

Status in console-setup package in Ubuntu:
  Confirmed
Status in gdm3 package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in kubuntu-meta package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  I'm used to using alt+left/right arrow to navigate back and forward in
  web browsers and elsewhere (nautilus)...  But on this fresh install of
  Ubuntu Gnome 15.10 beta, it seems to try and switch me between tty
  consoles (the ctrl+alt+f1 ones).  But it's not listed as one of the
  shortcuts in the "keyboard" menu, so I don't know how to disable it...

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/1508146/+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 520546] Re: Alt+KEY incorrectly behaves like Ctrl+Alt+KEY

[Samuel thibault]

As mentioned in https://bugs.launchpad.net/ubuntu/+source/gnome-
shell/+bug/1508146 , Ubuntu probably wants to apply the attached patch.

** Attachment added: "proposed fix"
   
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+attachment/5227480/+files/patch

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

Title:
  Alt+KEY incorrectly behaves like Ctrl+Alt+KEY

Status in console-setup package in Ubuntu:
  Confirmed

Bug description:
  I'm running Ubuntu Lucid development branch.

  Pressing alt-f2 switches the screen to the second virtual terminal.
  Alt-f3 does the same to the third and so on. I expected alt-f2 to open
  the run dialog.

  I'm pretty sure that my keyboard is not malfunctioning as I can use
  all my applications normally. (Pressing O and Ctrl-O do not have the
  same effect.)

  I'm not sure which package I should file this bug against. I'll
  happily do an apport-collect once I know.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/console-setup/+bug/520546/+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 1792820] [NEW] help you me

[Samuel B de H]

Public bug reported:

I don#t know what i am doing. How can I help you? help you me

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.9-0ubuntu7.2
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
Date: Sun Sep 16 22:33:39 2018
DistUpgraded: 2018-09-04 07:33:08,269 DEBUG icon theme changed, re-reading
DistroCodename: bionic
DistroVariant: ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8180] [1002:9839] 
(prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. Kabini [Radeon HD 8180] [1043:141d]
InstallationDate: Installed on 2016-10-16 (700 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
MachineType: ASUSTeK COMPUTER INC. X102BA
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=UUID=b4b46cc3-3ea0-41d0-8266-15beb0306075 ro quiet splash vt.handoff=1
SourcePackage: xorg
UpgradeStatus: Upgraded to bionic on 2018-09-04 (12 days ago)
dmi.bios.date: 12/31/2013
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: X102BA.219
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: X102BA
dmi.board.vendor: ASUSTeK COMPUTER INC.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK COMPUTER INC.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX102BA.219:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnX102BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX102BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
dmi.product.family: X
dmi.product.name: X102BA
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK COMPUTER INC.
version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
version.libdrm2: libdrm2 2.4.91-2
version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.5-0ubuntu0~18.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.5-0ubuntu0~18.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
xserver.bootTime: Mon Sep  3 23:15:32 2018
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.8
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug bionic ubuntu

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

Title:
  help you me

Status in xorg package in Ubuntu:
  New

Bug description:
  I don#t know what i am doing. How can I help you? help you me

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Sep 16 22:33:39 2018
  DistUpgraded: 2018-09-04 07:33:08,269 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Kabini [Radeon HD 8180] [1002:9839] 
(prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Kabini [Radeon HD 8180] [1043:141d]
  InstallationDate: Installed on 2016-10-16 (700 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: ASUSTeK COMPUTER INC. X102BA
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-34-generic 
root=UUID=b4b46cc3-3ea0-41d0-8266-15beb0306075 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-09-04 (12 days ago)
  dmi.bios.date: 12/31/2013
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X102BA.219
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X102BA
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX102BA.219:bd12/31/2013:svnASUSTeKCOMPUTERINC.:pnX102BA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX102BA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X102BA
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  

[Touch-packages] [Bug 1575078] Re: [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a while

[Aidan Samuel]

Dell XPS 15 9560
Ubuntu 18.04.1
4.15.0-32-generic

Speakers work fine. Headphones are detected when plugged in and sound no
longer plays from the speakers, but no sound comes through the
headphones.

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

Title:
  [XPS 15 9550, Realtek ALC3266] Headphone jack stops working after a
  while

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  I'm experiencing a strange behavior with a headphone jack on my
  laptop.

  I have an external audio speaker connected to it. When I disconnect the 
speaker and reconnect it again it stops working.
  Even more, laptop audio stops working too. And after the reboot, I don't even 
see any of the audio devices.

  I've googled a lot and tried different fixes from forums with no luck.
  After a while, I've accidentally discovered that putting the laptop to
  the sleep mode and rebooting system after brings audio back to live.
  Even more, if speakers were attached during this sleep-reboot
  procedure, they are starting to work as well.

  However, after the next reboot speakers are not working again. And if
  I will plug them out and in - problem with completely missing audio
  returns.

  P.S. I'm using laptop-mode-tools package on my laptop. Recovery after
  hibernation made me believe that it's somehow related. But after
  uninstalling this package nothing really changed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   kop3224 F...m pulseaudio
   /dev/snd/controlC0:  kop3224 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Apr 26 12:17:03 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-04-22 (3 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_Card: Встроенное аудио - HDA Intel PCH
  Symptom_Jack: Black Headphone Out, Left
  Symptom_Type: Sound works for a while, then breaks
  Title: [XPS 15 9550, Realtek ALC3266, Black Headphone Out, Left] fails after 
a while
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/07/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 01.02.00
  dmi.board.name: 0N7TVV
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr01.02.00:bd04/07/2016:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 15 9550
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1575078/+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 1782320] Re: Braille display inoperable in GUI since polkit-update

[Samuel thibault]

>From the upstream policykit bug entry, it is actually a misuse of the
policykit API from brltty. I have uploaded a fix in Debian's brltty
5.6-5.

Ubuntu should definitely include the policykit-fix patch contained in
that 5.6-5 version as an update to ubuntu 18.04, otherwise all blind
users will have the issue, thus unable to use the graphical desktop.

** Package changed: policykit-1 (Ubuntu) => brltty (Ubuntu)

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

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

Title:
  Braille display inoperable in GUI since polkit-update

Status in brltty package in Ubuntu:
  Confirmed

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy brltty
  brltty:
Installed: 5.5-4ubuntu2
Candidate: 5.5-4ubuntu2
Version table:
   *** 5.5-4ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy policykit-1-gnome 
  policykit-1-gnome:
Installed: (none)
Candidate: 0.105-6ubuntu2
Version table:
   0.105-6ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Expected behavior:
  After a system upgrade, the braille display should function as before the 
upgrade.

  Actual behavior:
  Since the upgrade, the braille display only works in console mode 
(Ctrl+Alt+F3, -F4, etc.)
  In GUI mode, the display reads "Screen not in text mode".
  Restarting Orca (screenreader) has no effect. Restarting the system has no 
effect.

  This is the upgrade command, taken from /var/log/apt/history.log:
  Start-Date: 2018-07-17  07:47:02
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 
(0.105-20, 0.105-20ubuntu0.18.04.1)
  End-Date: 2018-07-17  07:47:04

  These are the error messages taken from /var/log/syslog:
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: brltty 5.5-4ubuntu2
  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.2
  Architecture: amd64
  Date: Wed Jul 18 11:03:27 2018
  ExecutablePath: /bin/brltty
  InstallationDate: Installed on 2018-05-15 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 
/usr/local/lib/libgcrypt.so.20.2.2
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1782320/+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 1782320] Re: Braille display inoperable in GUI since polkit-update

[Samuel thibault]

Yes, disabling that patch fixes the issue.

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

Title:
  Braille display inoperable in GUI since polkit-update

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy brltty
  brltty:
Installed: 5.5-4ubuntu2
Candidate: 5.5-4ubuntu2
Version table:
   *** 5.5-4ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy policykit-1-gnome 
  policykit-1-gnome:
Installed: (none)
Candidate: 0.105-6ubuntu2
Version table:
   0.105-6ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Expected behavior:
  After a system upgrade, the braille display should function as before the 
upgrade.

  Actual behavior:
  Since the upgrade, the braille display only works in console mode 
(Ctrl+Alt+F3, -F4, etc.)
  In GUI mode, the display reads "Screen not in text mode".
  Restarting Orca (screenreader) has no effect. Restarting the system has no 
effect.

  This is the upgrade command, taken from /var/log/apt/history.log:
  Start-Date: 2018-07-17  07:47:02
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 
(0.105-20, 0.105-20ubuntu0.18.04.1)
  End-Date: 2018-07-17  07:47:04

  These are the error messages taken from /var/log/syslog:
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: brltty 5.5-4ubuntu2
  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.2
  Architecture: amd64
  Date: Wed Jul 18 11:03:27 2018
  ExecutablePath: /bin/brltty
  InstallationDate: Installed on 2018-05-15 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 
/usr/local/lib/libgcrypt.so.20.2.2
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+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 1782320] Re: Braille display inoperable in GUI since polkit-update

[Samuel thibault]

I can confirm the same issue on Debian: upgrading from version 0.105-20
to version 0.105-21 brings the same issue.

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

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

Title:
  Braille display inoperable in GUI since polkit-update

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy brltty
  brltty:
Installed: 5.5-4ubuntu2
Candidate: 5.5-4ubuntu2
Version table:
   *** 5.5-4ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy policykit-1-gnome 
  policykit-1-gnome:
Installed: (none)
Candidate: 0.105-6ubuntu2
Version table:
   0.105-6ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Expected behavior:
  After a system upgrade, the braille display should function as before the 
upgrade.

  Actual behavior:
  Since the upgrade, the braille display only works in console mode 
(Ctrl+Alt+F3, -F4, etc.)
  In GUI mode, the display reads "Screen not in text mode".
  Restarting Orca (screenreader) has no effect. Restarting the system has no 
effect.

  This is the upgrade command, taken from /var/log/apt/history.log:
  Start-Date: 2018-07-17  07:47:02
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 
(0.105-20, 0.105-20ubuntu0.18.04.1)
  End-Date: 2018-07-17  07:47:04

  These are the error messages taken from /var/log/syslog:
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: brltty 5.5-4ubuntu2
  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.2
  Architecture: amd64
  Date: Wed Jul 18 11:03:27 2018
  ExecutablePath: /bin/brltty
  InstallationDate: Installed on 2018-05-15 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 
/usr/local/lib/libgcrypt.so.20.2.2
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+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 1782320] Re: Braille display inoperable in GUI since polkit-update

[Samuel thibault]

This is most probably due to the introduction of Fix-CVE-2018-1116
-Trusting-client-supplied-UID.patch

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

Title:
  Braille display inoperable in GUI since polkit-update

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy brltty
  brltty:
Installed: 5.5-4ubuntu2
Candidate: 5.5-4ubuntu2
Version table:
   *** 5.5-4ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy policykit-1-gnome 
  policykit-1-gnome:
Installed: (none)
Candidate: 0.105-6ubuntu2
Version table:
   0.105-6ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Expected behavior:
  After a system upgrade, the braille display should function as before the 
upgrade.

  Actual behavior:
  Since the upgrade, the braille display only works in console mode 
(Ctrl+Alt+F3, -F4, etc.)
  In GUI mode, the display reads "Screen not in text mode".
  Restarting Orca (screenreader) has no effect. Restarting the system has no 
effect.

  This is the upgrade command, taken from /var/log/apt/history.log:
  Start-Date: 2018-07-17  07:47:02
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 
(0.105-20, 0.105-20ubuntu0.18.04.1)
  End-Date: 2018-07-17  07:47:04

  These are the error messages taken from /var/log/syslog:
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: brltty 5.5-4ubuntu2
  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.2
  Architecture: amd64
  Date: Wed Jul 18 11:03:27 2018
  ExecutablePath: /bin/brltty
  InstallationDate: Installed on 2018-05-15 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 
/usr/local/lib/libgcrypt.so.20.2.2
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+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 1782320] Re: Braille display inoperable in GUI since polkit-update

[Samuel thibault]

This seems to be an issue within policykit itself. Printing the actual
error shows:

GDBus.Error:org.freedesktop.PolicyKit1.Error.Failed: process with PID
12570 has been replaced

>From reading the source code, it seems that policykit is checking the
start time of the program and finds a mismatch. It happens that orca is
run as a Python script, so I thought that might be due to the script
startup procedure, but starting a C brlapi client gives the same issue.
At any rate, really looks like not an issue in brltty itself.

** Package changed: brltty (Ubuntu) => policykit-1 (Ubuntu)

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

Title:
  Braille display inoperable in GUI since polkit-update

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy brltty
  brltty:
Installed: 5.5-4ubuntu2
Candidate: 5.5-4ubuntu2
Version table:
   *** 5.5-4ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy policykit-1-gnome 
  policykit-1-gnome:
Installed: (none)
Candidate: 0.105-6ubuntu2
Version table:
   0.105-6ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Expected behavior:
  After a system upgrade, the braille display should function as before the 
upgrade.

  Actual behavior:
  Since the upgrade, the braille display only works in console mode 
(Ctrl+Alt+F3, -F4, etc.)
  In GUI mode, the display reads "Screen not in text mode".
  Restarting Orca (screenreader) has no effect. Restarting the system has no 
effect.

  This is the upgrade command, taken from /var/log/apt/history.log:
  Start-Date: 2018-07-17  07:47:02
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 
(0.105-20, 0.105-20ubuntu0.18.04.1)
  End-Date: 2018-07-17  07:47:04

  These are the error messages taken from /var/log/syslog:
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: brltty 5.5-4ubuntu2
  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.2
  Architecture: amd64
  Date: Wed Jul 18 11:03:27 2018
  ExecutablePath: /bin/brltty
  InstallationDate: Installed on 2018-05-15 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 
/usr/local/lib/libgcrypt.so.20.2.2
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+subscriptions

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

[Touch-packages] [Bug 1782320] Re: Braille display inoperable in GUI since polkit-update

[Samuel thibault]

Note: to reproduce the issue, one just needs to install an Ubuntu 18.04
system, start brltty by hand as root with:

  sudo brltty -b no

then try to connect to it as normal logged-in user through brlapi:

  python3
  >>> import brlapi
  >>> b = brlapi.Connection()

which shouldn't raise an exception. Logs can be seen in /var/log/syslog
(unfortunately the current package source code only prints errno instead
of the GError).

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

Title:
  Braille display inoperable in GUI since polkit-update

Status in policykit-1 package in Ubuntu:
  New

Bug description:
  $ lsb_release -rd
  Description:  Ubuntu 18.04 LTS
  Release:  18.04

  $ apt-cache policy brltty
  brltty:
Installed: 5.5-4ubuntu2
Candidate: 5.5-4ubuntu2
Version table:
   *** 5.5-4ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  $ apt-cache policy policykit-1-gnome 
  policykit-1-gnome:
Installed: (none)
Candidate: 0.105-6ubuntu2
Version table:
   0.105-6ubuntu2 500
  500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages

  Expected behavior:
  After a system upgrade, the braille display should function as before the 
upgrade.

  Actual behavior:
  Since the upgrade, the braille display only works in console mode 
(Ctrl+Alt+F3, -F4, etc.)
  In GUI mode, the display reads "Screen not in text mode".
  Restarting Orca (screenreader) has no effect. Restarting the system has no 
effect.

  This is the upgrade command, taken from /var/log/apt/history.log:
  Start-Date: 2018-07-17  07:47:02
  Commandline: /usr/bin/unattended-upgrade
  Upgrade: libpolkit-gobject-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-agent-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
libpolkit-backend-1-0:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), 
policykit-1:amd64 (0.105-20, 0.105-20ubuntu0.18.04.1), gir1.2-polkit-1.0:amd64 
(0.105-20, 0.105-20ubuntu0.18.04.1)
  End-Date: 2018-07-17  07:47:04

  These are the error messages taken from /var/log/syslog:
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: BrlAPI connection fd=22 accepted: 
local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: BrlAPI connection fd=22 
accepted: local 
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.
  Jul 18 10:55:34 WaanzinsPC2 brltty[2635]: brltty: 
polkit_authority_check_authorization_sync error 11: Resource temporarily 
unavailable.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: brltty 5.5-4ubuntu2
  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.2
  Architecture: amd64
  Date: Wed Jul 18 11:03:27 2018
  ExecutablePath: /bin/brltty
  InstallationDate: Installed on 2018-05-15 (63 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  LocalLibraries: /usr/local/lib/libgpg-error.so.0.24.2 
/usr/local/lib/libgcrypt.so.20.2.2
  SourcePackage: brltty
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.brltty.conf: 2018-05-16T09:36:35.497752

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1/+bug/1782320/+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 1140716]

[Samuel Rakitničan]

I doesn't seem to be getting mentioned Gnome crashes on my sandybridge
anymore with mainline kernels, that is currently 4.11 and I think even
with 4.10 I was not getting any issues, with mainline longterm 4.4.61
and default centos 7 kernels I am definitely getting very frequent GPU
crashes that brings down Gnome.

So it is either fixed for good, or it become much rarer. The issue I
am/was experiencing happens when Gnome is running, it does not happen
when only GDM is loaded. System load seems to not have effect on the bug
triggering, seems to happen any time, on idle, or when machine is
loaded.

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

Title:
  [regression] 3.5.0-26-generic and  3.2.0-39-generic GPU hangs on
  Sandybridge

Status in DRI:
  Won't Fix
Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in mesa source package in Precise:
  Triaged
Status in linux source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux source package in Raring:
  Invalid
Status in linux-lts-quantal source package in Raring:
  Invalid
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Won't Fix

Bug description:
  I'm getting errors about GPU hangs every minute or so (usually only
  when using FF and scrolling a webpage or something). I also get an
  annoying ubuntu dialog saying there is a "system error".

  This didn't happen with 3.5.0-24-generic.

  Here is the dmesg:
  [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.658405] [ cut here ]
  [26285.658472] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26285.658474] Hardware name: SATELLITE Z830
  [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm 
arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel 
snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep 
iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi 
rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer 
snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap 
soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei 
video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc 
lp parport e1000e ahci libahci [last unloaded: sdhci]
  [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic 
#40-Ubuntu
  [26285.658539] Call Trace:
  [26285.658549]  [] warn_slowpath_common+0x7f/0xc0
  [26285.658553]  [] warn_slowpath_null+0x1a/0x20
  [26285.658569]  [] gen6_enable_rps+0x706/0x710 [i915]
  [26285.658584]  [] intel_modeset_init_hw+0x66/0xa0 [i915]
  [26285.658595]  [] i915_reset+0x1a4/0x6e0 [i915]
  [26285.658601]  [] ? __switch_to+0x12b/0x420
  [26285.658612]  [] i915_error_work_func+0xc3/0x110 [i915]
  [26285.658618]  [] process_one_work+0x12a/0x420
  [26285.658629]  [] ? gen6_pm_rps_work+0xe0/0xe0 [i915]
  [26285.658632]  [] worker_thread+0x12e/0x2f0
  [26285.658636]  [] ? manage_workers.isra.26+0x200/0x200
  [26285.658640]  [] kthread+0x93/0xa0
  [26285.658644]  [] kernel_thread_helper+0x4/0x10
  [26285.658649]  [] ? kthread_freezable_should_stop+0x70/0x70
  [26285.658652]  [] ? gs_change+0x13/0x13
  [26285.658654] ---[ end trace 59c6162fdfcbffee ]---
  [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26766.014093] [drm:i915_hangcheck_hung] *ERROR* 

[Touch-packages] [Bug 1751252] Re: [regression] ubiquity crashed in debconf.py:104 with ValueError: invalid literal for int() with base 10: ''

[Samuel Bancal]

Hi,

I do confirm proposed worked also for me on a Dell XPS 15 9530.

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

Title:
  [regression] ubiquity crashed in debconf.py:104 with ValueError:
  invalid literal for int() with base 10: ''

Status in cairo:
  Confirmed
Status in OEM Priority Project:
  Triaged
Status in cairo package in Ubuntu:
  In Progress
Status in ubiquity package in Ubuntu:
  Fix Released
Status in cairo source package in Bionic:
  In Progress
Status in ubiquity source package in Bionic:
  Fix Committed

Bug description:
  * Impact
  The Ubuntu installer crashes on some machines (seems more often on hiDPI 
machines (QHD/UHD etc)).

  * Test case
  Try installing Ubuntu on an hidpi machine, it should complete installation 
instead of crashing.

  * Regression potential
  The fix in ubiquity touches the code handle uid drop/privilege, that can have 
unexpected side effects so we need proper/complete testing of the installer

  --

  Update: Actually the crash occurs on slow-ish systems due to a race
  condition. It's not strictly only hi-DPI machines - that's just the
  most common place it is experienced.

  ---

  https://errors.ubuntu.com/problem/82f7f7e7923663c7b2123c7f1f49af29f6ff4d77
  https://errors.ubuntu.com/problem/735a2b847e0eeab6c8a7b954de5110e43889be15
  https://errors.ubuntu.com/problem/dcd4c9da5ee0cc6d36324446e0e49d39705c90b7
  https://errors.ubuntu.com/problem/cb82f70f9ede07369e8104da9ddf87e28b42257d
  https://errors.ubuntu.com/problem/84a5563af3d2b85f098da832ece4cb8450bfd524

  ---

  WORKAROUND:

  1. Boot into the live session.
  2. Settings > Devices > Displays > Scale = 100%
  3. Click Apply.
  4. Proceed with installation: Click "Install Ubuntu 18.04 LTS".

  ---

  Crashed in a VM in the middle of installation. The host is Bionic up
  to date.

  From the journal
  Feb 23 12:52:27 ubuntu kernel: traps: ubiquity[2646] trap int3 
ip:7f5a76936961 sp:7ffde5090c50 error:0 in 
libglib-2.0.so.0.5400.1[7f5a768e6000+111000]
  Feb 23 12:52:41 ubuntu /install.py[6858]: Exception during installation:
  Feb 23 12:52:41 ubuntu /install.py[6858]: Traceback (most recent call last):
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 757, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: install.run()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 135, in run
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.copy_all()
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/share/ubiquity/install.py", line 505, in copy_all
  Feb 23 12:52:41 ubuntu /install.py[6858]: self.db.progress('SET', 10 + 
copy_progress)
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 83, in 
  Feb 23 12:52:41 ubuntu /install.py[6858]: lambda *args, **kw: 
self.command(command, *args, **kw))
  Feb 23 12:52:41 ubuntu /install.py[6858]:   File 
"/usr/lib/python3/dist-packages/debconf.py", line 104, in command
  Feb 23 12:52:41 ubuntu /install.py[6858]: status = int(status)
  Feb 23 12:52:41 ubuntu /install.py[6858]: ValueError: invalid literal for 
int() with base 10: ''

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: ubiquity 18.04.1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CasperVersion: 1.388
  Date: Fri Feb 23 12:52:28 2018
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  InstallCmdLine: file=/cdrom/preseed/ubuntu.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- keyboard-configuration/layoutcode=fr 
keyboard-configuration/variantcode=oss
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180222)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity -d
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.4+, python3-minimal, 3.6.4-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  Signal: 5
  SourcePackage: ubiquity
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   _XEventsQueued () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   XPending () from /usr/lib/x86_64-linux-gnu/libX11.so.6
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: ubiquity crashed with signal 5 in _XEventsQueued()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1766951] [NEW] package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to install/upgrade:

[Samuel Guay]

Public bug reported:

I was trying to update Ubuntu and it wouldnt stop crashing.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
Uname: Linux 4.13.0-38-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.16
Architecture: amd64
Date: Wed Apr 25 14:45:00 2018
DuplicateSignature:
 package:libgstreamer-plugins-base0.10-0:0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
 Unpacking libgstreamer0.10-0:i386 (0.10.36-1.5ubuntu1) over (0.10.36-1.5) ...
 dpkg: error processing archive 
/var/cache/apt/archives/libgstreamer0.10-0_0.10.36-1.5ubuntu1_i386.deb 
(--unpack):
  trying to overwrite shared 
'/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different 
from other instances of package libgstreamer0.10-0:i386
ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:i386
InstallationDate: Installed on 2018-04-12 (13 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.26
SourcePackage: gst-plugins-base0.10
Title: package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:i386
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gst-plugins-base0.10 (Ubuntu)
 Importance: Undecided
 Status: New


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

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

Title:
  package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified:
  usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
  failed to install/upgrade: trying to overwrite shared '/usr/share/doc
  /libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is
  different from other instances of package libgstreamer-plugins-
  base0.10-0:i386

Status in gst-plugins-base0.10 package in Ubuntu:
  New

Bug description:
  I was trying to update Ubuntu and it wouldnt stop crashing.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Wed Apr 25 14:45:00 2018
  DuplicateSignature:
   package:libgstreamer-plugins-base0.10-0:0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz]
   Unpacking libgstreamer0.10-0:i386 (0.10.36-1.5ubuntu1) over (0.10.36-1.5) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libgstreamer0.10-0_0.10.36-1.5ubuntu1_i386.deb 
(--unpack):
trying to overwrite shared 
'/usr/share/doc/libgstreamer0.10-0/changelog.Debian.gz', which is different 
from other instances of package libgstreamer0.10-0:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:i386
  InstallationDate: Installed on 2018-04-12 (13 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: gst-plugins-base0.10
  Title: package libgstreamer-plugins-base0.10-0 0.10.36-2ubuntu0.1 [modified: 
usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz] failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libgstreamer-plugins-base0.10-0/changelog.Debian.gz', which is 
different from other instances of package libgstreamer-plugins-base0.10-0:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gst-plugins-base0.10/+bug/1766951/+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 1563945] Re: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 1

[Ermias samuel]

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

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

Title:
  package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to
  install/upgrade: subprocess installed pre-removal script returned
  error exit status 1

Status in avahi package in Ubuntu:
  Fix Released

Bug description:
  interesting issues while updating packages this morning...

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Wed Mar 30 09:33:28 2016
  DpkgTerminalLog:
   Removing avahi-discover (0.6.32~rc+dfsg-1ubuntu2) ...
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--remove):
subprocess installed pre-removal script returned error exit status 1
  DuplicateSignature:
   Removing avahi-dnsconfd (0.6.32~rc+dfsg-1ubuntu2) ...
   Job for avahi-daemon.socket canceled.
   dpkg: error processing package avahi-dnsconfd (--remove):
subprocess installed pre-removal script returned error exit status 1
  ErrorMessage: subprocess installed pre-removal script returned error exit 
status 1
  InstallationDate: Installed on 2016-01-06 (83 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.9
  SourcePackage: avahi
  Title: package avahi-dnsconfd 0.6.32~rc+dfsg-1ubuntu2 failed to 
install/upgrade: subprocess installed pre-removal script returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1563945/+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 1759009] [NEW] software bug

[Samuel T Cardinal]

Public bug reported:

I ran the installed x diagnosis software. The software found the bug. I
have no idea what the problem is. My Ubuntu Apps application will not
work. I tried removing and reinstall the application but it still will
not work. I installed gnome-software as a work around but that doesn't
seem to work either. I believe my Ubuntu 16.04 lts original installation
is faulty.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
Uname: Linux 4.13.0-37-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
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: Mon Mar 26 12:02:22 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] (rev 
09) (prog-if 00 [VGA controller])
   Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:053e]
 NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: Dell GK107GLM [Quadro K2000M] [1028:153e]
InstallationDate: Installed on 2018-03-23 (3 days ago)
InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801)
MachineType: Dell Inc. Precision M4700
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-37-generic 
root=UUID=6126fabd-0eaf-4345-ac41-42b5013ac682 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 05/09/2017
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A17
dmi.board.name: 082H3V
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA17:bd05/09/2017:svnDellInc.:pnPrecisionM4700:pvr01:rvnDellInc.:rn082H3V:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: Precision M4700
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-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

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


** Tags: amd64 apport-bug compiz-0.9 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/1759009

Title:
  software bug

Status in xorg package in Ubuntu:
  New

Bug description:
  I ran the installed x diagnosis software. The software found the bug.
  I have no idea what the problem is. My Ubuntu Apps application will
  not work. I tried removing and reinstall the application but it still
  will not work. I installed gnome-software as a work around but that
  doesn't seem to work either. I believe my Ubuntu 16.04 lts original
  installation is faulty.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-37.42~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-37-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  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: Mon Mar 26 12:02:22 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell 3rd Gen Core processor Graphics Controller [1028:053e]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Dell GK107GLM [Quadro K2000M] [1028:153e]
  InstallationDate: Installed on 2018-03-23 (3 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Dell Inc. Precision M4700
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  

[Touch-packages] [Bug 1750586] Re: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Stephan Samuel]

Thanks, Stephen.

I had the same results as Mattias, mine was datapulley instead of
rekall-forensic. Your direction of running the compile without the
redirect so I could see the output was what got me there.

FWIW, datapulley seemed to be the only package in that folder. Is yours
the same? (Mattias, same question for you.) Considering how much...
uh... stuff I have installed and how integral Python is to Ubuntu it
would seem to me that there would be more; maybe some folks didn't take
a hint that they should be doing a thing a certain way. Perhaps this is
somewhat more systemic? I don't know enough about Python or its package
management to even start diagnosing something like this.

I'm filing with datapulley, which broke my apt.

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

Title:
  package python-minimal 2.7.12-1~16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-defaults package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a dependency snarl:

  python-minimal is already the newest version (2.7.12-1~16.04).
  python-minimal set to manually installed.
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   python : PreDepends: python-minimal (= 2.7.11-1) but 2.7.12-1~16.04 is to be 
installed
   python-all : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
   python-all-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-all-dev (= 2.7.12-1~16.04) but 2.7.11-1 
is to be installed
   python-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
  E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify 
a solution).

  apt-get -f install tries to set up python-minimal (2.7.12-1~16.04) and
  returns 1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.12-1~16.04
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb 20 08:48:01 2018
  DuplicateSignature:
   package:python-minimal:2.7.12-1~16.04
   Setting up python-minimal (2.7.12-1~16.04) ...
   dpkg: error processing package python-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-23 (484 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1750586/+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 1750586] [NEW] package python-minimal 2.7.12-1~16.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Stephan Samuel]

Public bug reported:

There seems to be a dependency snarl:

python-minimal is already the newest version (2.7.12-1~16.04).
python-minimal set to manually installed.
You might want to run 'apt-get -f install' to correct these:
The following packages have unmet dependencies:
 python : PreDepends: python-minimal (= 2.7.11-1) but 2.7.12-1~16.04 is to be 
installed
 python-all : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed
 python-all-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
  Depends: libpython-all-dev (= 2.7.12-1~16.04) but 2.7.11-1 is 
to be installed
 python-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be installed
  Depends: libpython-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify a 
solution).

apt-get -f install tries to set up python-minimal (2.7.12-1~16.04) and
returns 1.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python-minimal 2.7.12-1~16.04
ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
Uname: Linux 4.4.0-109-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
Date: Tue Feb 20 08:48:01 2018
DuplicateSignature:
 package:python-minimal:2.7.12-1~16.04
 Setting up python-minimal (2.7.12-1~16.04) ...
 dpkg: error processing package python-minimal (--configure):
  subprocess installed post-installation script returned error exit status 1
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2016-10-23 (484 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.2.25
SourcePackage: python-defaults
Title: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package python-minimal 2.7.12-1~16.04 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in python-defaults package in Ubuntu:
  New

Bug description:
  There seems to be a dependency snarl:

  python-minimal is already the newest version (2.7.12-1~16.04).
  python-minimal set to manually installed.
  You might want to run 'apt-get -f install' to correct these:
  The following packages have unmet dependencies:
   python : PreDepends: python-minimal (= 2.7.11-1) but 2.7.12-1~16.04 is to be 
installed
   python-all : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
   python-all-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-all-dev (= 2.7.12-1~16.04) but 2.7.11-1 
is to be installed
   python-dev : Depends: python (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
Depends: libpython-dev (= 2.7.12-1~16.04) but 2.7.11-1 is to be 
installed
  E: Unmet dependencies. Try 'apt-get -f install' with no packages (or specify 
a solution).

  apt-get -f install tries to set up python-minimal (2.7.12-1~16.04) and
  returns 1.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python-minimal 2.7.12-1~16.04
  ProcVersionSignature: Ubuntu 4.4.0-109.132-generic 4.4.98
  Uname: Linux 4.4.0-109-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb 20 08:48:01 2018
  DuplicateSignature:
   package:python-minimal:2.7.12-1~16.04
   Setting up python-minimal (2.7.12-1~16.04) ...
   dpkg: error processing package python-minimal (--configure):
subprocess installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-10-23 (484 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.2.25
  SourcePackage: python-defaults
  Title: package python-minimal 2.7.12-1~16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python-defaults/+bug/1750586/+subscriptions

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

[Touch-packages] [Bug 1735987] [NEW] Where I execute eclipse IDE

[samuel porras de la flor]

Public bug reported:

When I execute eclipse IDE I get this error: ** (java:5218): WARNING **:
Couldn't connect to accessibility bus: Failed to connect to socket /tmp
/dbus-I2WWf3Uz2u: Conection refused

ProblemType: Bug
DistroRelease: elementary 0.4.1
Package: dbus 1.10.6-1ubuntu3.3 [origin: Ubuntu]
ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
Uname: Linux 4.4.0-101-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.13
Architecture: amd64
CurrentDesktop: Pantheon
Date: Sun Dec  3 12:17:53 2017
InstallationDate: Installed on 2017-04-13 (234 days ago)
InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
SourcePackage: dbus
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug loki third-party-packages

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

Title:
  Where I execute eclipse IDE

Status in dbus package in Ubuntu:
  New

Bug description:
  When I execute eclipse IDE I get this error: ** (java:5218): WARNING
  **: Couldn't connect to accessibility bus: Failed to connect to socket
  /tmp/dbus-I2WWf3Uz2u: Conection refused

  ProblemType: Bug
  DistroRelease: elementary 0.4.1
  Package: dbus 1.10.6-1ubuntu3.3 [origin: Ubuntu]
  ProcVersionSignature: Ubuntu 4.4.0-101.124-generic 4.4.95
  Uname: Linux 4.4.0-101-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.13
  Architecture: amd64
  CurrentDesktop: Pantheon
  Date: Sun Dec  3 12:17:53 2017
  InstallationDate: Installed on 2017-04-13 (234 days ago)
  InstallationMedia: elementary OS 0.4 "Loki" - Stable amd64 (20160921)
  SourcePackage: dbus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1735987/+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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Samuel Ballé]

I followed Julien Scordia #83 and upgraded to 17 loosing the LTS.
Problem solved with this version, no issue in two month.

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+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 1697692] [NEW] package libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting

[Samuel Ranz Castañeda]

Public bug reported:

I have no further details since I don't know the precise thing that has
failed. I hope the logs are enough for you, sorry not to be more
helpful.

Thank you a lot!

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1
ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
Uname: Linux 4.8.0-54-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Tue Jun 13 14:23:13 2017
DpkgTerminalLog:
 dpkg: error processing package libpoppler-qt5-1:amd64 (--remove):
  package is in a very bad inconsistent state; you should
  reinstall it before attempting a removal
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
InstallationDate: Installed on 2017-06-01 (11 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: poppler
Title: package libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 failed to
  install/upgrade: package is in a very bad inconsistent state; you
  should  reinstall it before attempting a removal

Status in poppler package in Ubuntu:
  New

Bug description:
  I have no further details since I don't know the precise thing that
  has failed. I hope the logs are enough for you, sorry not to be more
  helpful.

  Thank you a lot!

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1
  ProcVersionSignature: Ubuntu 4.8.0-54.57~16.04.1-generic 4.8.17
  Uname: Linux 4.8.0-54-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Tue Jun 13 14:23:13 2017
  DpkgTerminalLog:
   dpkg: error processing package libpoppler-qt5-1:amd64 (--remove):
package is in a very bad inconsistent state; you should
reinstall it before attempting a removal
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  InstallationDate: Installed on 2017-06-01 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: poppler
  Title: package libpoppler-qt5-1:amd64 0.41.0-0ubuntu1.1 failed to 
install/upgrade: package is in a very bad inconsistent state; you should  
reinstall it before attempting a removal
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/poppler/+bug/1697692/+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 1444656] Re: GnuTLS TLS 1.2 handshake failure

[Samuel Leslie]

Hi Seth,

I've attached a debdiff which is generated off the latest gnutls26
package: 2.12.23-12ubuntu2.7. That said, no changes to my earlier patch
were required to apply cleanly. Hopefully this is what you're after?

I should also add that this patch should ideally be reviewed by someone
knowledgeable about GnuTLS and C, as I don't consider myself to meet
either of those requirements! Particularly given this is a security
library.

Cheers,
-SDL

** Patch added: "gnutls26_2.12.23-12ubuntu2.8.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1444656/+attachment/4841301/+files/gnutls26_2.12.23-12ubuntu2.8.debdiff

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

Title:
  GnuTLS TLS 1.2 handshake failure

Status in gnutls26 package in Ubuntu:
  Invalid
Status in gnutls26 source package in Trusty:
  Triaged

Bug description:
  I'm experiencing the same issue as here:

  http://comments.gmane.org/gmane.network.gnutls.general/3713

  
  I came across a SSL handshake problem with gnutls-cli when connecting to 
  some websites, see below. It is somehow specific to gnutls as 
  openssl/Chrome/Firefox can connect fine. 

  Is this is a bug in gnutls or do you have any ideas how to
  troubleshoot it?

  $ gnutls-cli --version
  gnutls-cli (GnuTLS) 2.12.23
  Packaged by Debian (2.12.23-12ubuntu2.1)

  $ gnutls-cli www.openlearning.com
  Resolving 'www.openlearning.com'...
  Connecting to '119.9.9.205:443'...
  *** Fatal error: A TLS fatal alert has been received.
  *** Received alert [40]: Handshake failed
  *** Handshake has failed
  GnuTLS error: A TLS fatal alert has been received.

  $ gnutls-cli sequencewiz.com
  Resolving 'sequencewiz.com'...
  Connecting to '50.112.144.117:443'...
  *** Fatal error: A TLS packet with unexpected length was received.
  *** Handshake has failed
  GnuTLS error: A TLS packet with unexpected length was received.

  Thank you,

  
  Please back port the latest GnuTLS to Trusty as it is an LTS release and 
clearly GnuTLS 2.12 is an old branch.

  I've also attached packet captures of this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1444656/+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 1574667] Re: Mouse pointer occasionally jumps to the bottom-left corner

[Samuel Holmes]

Hi,

I was having the same issue, but the fix suggested by Juan Hernandez at
#32 seems to have worked!

I had to install xserver-xorg-core before I could install xserver-xorg-
input-libinput, but it seems to work now!

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

Title:
  Mouse pointer occasionally jumps to the bottom-left corner

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  Sometimes the mouse pointer jumps directly to the bottom-left corner
  of the screen, which results in opening the trash window when
  clicking.

  This seems to be related: https://ubuntu-mate.community/t/mouse-
  pointer-jumps-on-clicking-touchpad/2932.

  Thanks,
  MZ

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog: /dev/sda6: clean, 276587/40779776 files, 15261626/163117056 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Mon Apr 25 15:55:54 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:06b2]
  InstallationDate: Installed on 2016-04-23 (2 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 8087:07dc Intel Corp. 
   Bus 001 Device 003: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 002: ID 064e:920b Suyin Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. Inspiron 5559
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic.efi.signed 
root=UUID=c5bc0a1d-3fe9-4ae5-81e9-de7d141b419c ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.5
  dmi.board.name: 06CMH7
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.5:bd12/21/2015:svnDellInc.:pnInspiron5559:pvr:rvnDellInc.:rn06CMH7:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5559
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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: Mon Apr 25 13:43:44 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1156 
   vendor LGD
  xserver.version: 2:1.18.3-1ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1574667/+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 1657440] Re: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated

[Samuel Matzek]

I setup a test environment to re-run the recreation script I attached
above while using the fix from xenial-proposed.

What I found was that the fix helps but is not perfect.

While the UCA repo is in the hourly update time window, the apt-get
update can still leave the user in the error case where you have the
Release file but not the Release.gpg file.  However, WITH this fix a
subsequent apt-get update resolves the issue and will pull down the
Release.gpg file.  This is in contrast to WITHOUT the fix no amount of
apt-get update calls would fix the issue until after the next hourly UCA
update.

So my verdict is that this fix should go through as it allows automated
tooling to simply do apt-get update retries and self-resolve the missing
gpg issue.

Any further changes are probably required in the Ubuntu Cloud Archive
itself to close the "partially updated" window that is part of the error
case trigger.

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

Title:
  apt won't redownload Release.gpg after inconsistent cache updates made
  while UCA is being updated

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Fix Committed
Status in apt source package in Yakkety:
  In Progress

Bug description:
  # apt --version
  apt 1.2.18 (amd64)

  xenial

  I got myself into a situation where a repository has a Release and a
  Release.gpg file, but apt is just ignoring the gpg one and won't
  download it via apt update for some reason:

  The repository in question is http://ubuntu-
  cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
  how locally I have just the Release file:

  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
  -rw-r--r-- 1 root root 100K Jan 15 18:03 
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
  -rw-r--r-- 1 root root 242K Apr 21  2016 
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
  -rw-r--r-- 1 root root 7.7K Jan 18 11:45 
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release

  Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a 
"Get:":
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease
  Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
InRelease
  Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
  Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release
  Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release.gpg [543 B]
  Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
  Fetched 205 kB in 0s (395 kB/s)
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  8 packages can be upgraded. Run 'apt list --upgradable' to see them.

  And I can't install packages:
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
    python3-setuptools
  The following packages will be upgraded:
    dh-python dnsmasq-base python-pkg-resources python-setuptools 
python3-cryptography python3-pkg-resources python3-requests python3-urllib3
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,193 kB of archives.
  After this operation, 808 kB of additional disk space will be used.
  Do you want to continue? [Y/n]
  WARNING: The following packages cannot be authenticated!
    dh-python dnsmasq-base python-setuptools python-pkg-resources 
python3-pkg-resources python3-setuptools python3-cryptography python3-requests 
python3-urllib3
  Install these packages without verification? [y/N] n
  E: Some packages could not be authenticated
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists#

  Somehow apt is thinking it has the Release.gpg file, but it doesn't?

  This server is behind a squid proxy.


  [Impact]
  An apt update of an apt repository that does not use InRelease during the 
time it is being updated can cause the gpg file to not be downloaded and 
updated. This makes the packages from the repository be unable to be 
authenticated.

  The Ubuntu Cloud Archive is one of the archives that meets this
  criteria.

  The impact to downstream automation deployment code is that if they
  are adding the UCA repo to a system and calling apt update during the
  time the UCA is being updated by Canonical, the repo can get into a

[Touch-packages] [Bug 1444656] Re: GnuTLS TLS 1.2 handshake failure

[Samuel D. Leslie]

We encountered this bug today and it has the potential to be pretty
nasty if you're unfortunate enough to hit it. In our case we have
several systems which perform authentication against a Windows domain
using LDAPS. We recently updated the TLS certificate on those systems
and all the services which perform LDAPS authentication starting failing
with the symptoms described earlier in this bug.

The new TLS certificate we installed had the same key size and hash
algorithm, but it turned out the root CA & intermediate certificate were
using SHA384 as the signature hash. This in turn caused the LDAPS
connections to stop working. Given the CA's certificates were using
SHA384 reissuing the certificate wasn't going to help and downgrading
the TLS version was not at all desirable given the potential security
implications.

I've backported the commit referenced by Marc and confirmed it resolves
the problem for us. In my view it'd be wise to push this out to 14.04
users as this issue is going to presumably become more prominent as more
certificates start using stronger hash algorithms and TLS 1.2 becomes
more prevalent.

** Patch added: "fix-tls12-handshake.diff"
   
https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1444656/+attachment/4837425/+files/fix-tls12-handshake.diff

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

Title:
  GnuTLS TLS 1.2 handshake failure

Status in gnutls26 package in Ubuntu:
  Invalid
Status in gnutls26 source package in Trusty:
  Triaged

Bug description:
  I'm experiencing the same issue as here:

  http://comments.gmane.org/gmane.network.gnutls.general/3713

  
  I came across a SSL handshake problem with gnutls-cli when connecting to 
  some websites, see below. It is somehow specific to gnutls as 
  openssl/Chrome/Firefox can connect fine. 

  Is this is a bug in gnutls or do you have any ideas how to
  troubleshoot it?

  $ gnutls-cli --version
  gnutls-cli (GnuTLS) 2.12.23
  Packaged by Debian (2.12.23-12ubuntu2.1)

  $ gnutls-cli www.openlearning.com
  Resolving 'www.openlearning.com'...
  Connecting to '119.9.9.205:443'...
  *** Fatal error: A TLS fatal alert has been received.
  *** Received alert [40]: Handshake failed
  *** Handshake has failed
  GnuTLS error: A TLS fatal alert has been received.

  $ gnutls-cli sequencewiz.com
  Resolving 'sequencewiz.com'...
  Connecting to '50.112.144.117:443'...
  *** Fatal error: A TLS packet with unexpected length was received.
  *** Handshake has failed
  GnuTLS error: A TLS packet with unexpected length was received.

  Thank you,

  
  Please back port the latest GnuTLS to Trusty as it is an LTS release and 
clearly GnuTLS 2.12 is an old branch.

  I've also attached packet captures of this.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnutls26/+bug/1444656/+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 1657440] Re: apt won't redownload Release.gpg after inconsistent cache updates made while UCA is being updated

[Samuel Matzek]

[Impact] 
An apt update of an apt repository that does not use InRelease during the time 
it is being updated can cause the gpg file to not be downloaded and updated.  
This makes the packages from the repository be unable to be authenticated.

The Ubuntu Cloud Archive is one of the archives that meets this
criteria.

The impact to downstream automation deployment code is that if they are
adding the UCA repo to a system and calling apt update during the time
the UCA is being updated by Canonical, the repo can get into a state
where the Release.gpg file is not there and all package installs will
fail due to "unauthenticated packages" error.


[Test Case]
A detailed python script was attached.

To reproduce this outside that script you would want to:
1. Add the UCA repo
2. Do the following in a loop starting at 43 minutes after the hour and run it 
until 55 minutes after the hour:
2.1 Remove these files to simulate the UCA repo being added the first time.
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release.gpg
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_main_binary*Packages

2.2 apt-get update
3. Check the state of the 3 files you deleted.  If you have the _Release file 
but not the _Release.gpg you have recreated the issue.
4. If you have not recreated the issue, continue GOTO 2 and continue to loop.

[Regression Potential] 
Unknown

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

Title:
  apt won't redownload Release.gpg after inconsistent cache updates made
  while UCA is being updated

Status in APT:
  Fix Released
Status in apt package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  Triaged
Status in apt source package in Yakkety:
  Triaged

Bug description:
  # apt --version
  apt 1.2.18 (amd64)

  xenial

  
  I got myself into a situation where a repository has a Release and a 
Release.gpg file, but apt is just ignoring the gpg one and won't download it 
via apt update for some reason:

  The repository in question is http://ubuntu-
  cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
  how locally I have just the Release file:

  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
  -rw-r--r-- 1 root root 100K Jan 15 18:03 
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
  -rw-r--r-- 1 root root 242K Apr 21  2016 
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
  -rw-r--r-- 1 root root 7.7K Jan 18 11:45 
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release

  
  Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a 
"Get:":
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease   
 
  Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
InRelease
  Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
  Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release
  Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release.gpg [543 B]
  Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
  Fetched 205 kB in 0s (395 kB/s)   
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  8 packages can be upgraded. Run 'apt list --upgradable' to see them.

  
  And I can't install packages:
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
python3-setuptools
  The following packages will be upgraded:
dh-python dnsmasq-base python-pkg-resources python-setuptools 
python3-cryptography python3-pkg-resources python3-requests python3-urllib3
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,193 kB of archives.
  After this operation, 808 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  WARNING: The following packages cannot be authenticated!
dh-python dnsmasq-base python-setuptools python-pkg-resources 
python3-pkg-resources python3-setuptools python3-cryptography python3-requests 
python3-urllib3
  Install these packages without verification? [y/N] n
  E: Some packages could not be authenticated
  

[Touch-packages] [Bug 1657440] Re: apt won't redownload Release.gpg

[Samuel Matzek]

This upstream patch needs to be backported to the 1.2 series for Xenial.
If left unfixed in Xenial it opens a timing window every hour with
Ubuntu Cloud Archive where users can fall into the "Some packages could
not be authenticated" state without Release.gpg that is described in the
description.  This state will not self correct until an hour has passed
an another apt-get update is run.  This really impacts automated
deployment technologies such as Juju and Ansible because if they hit
this hourly window with UCA their fallback retries on apt-get update
will not work and the automated deployments fail. The noted upstream
Debian bug is specifically about trying to do an apt-get update without
adding the keys first. The timing window that users can hit will occur
even if you add the keys first.

Now for background information to explain the assertions above. Ubuntu
Cloud Archive updates its files, and more importantly the timestamps on
its files including the Release and Release.gpg file every hour. The
timestamps are updated to be 45 minutes past the hour. The UCA servers
start to reflect these changes around 50 minutes after the hour with a
rolling update of the Packages and then the Release.* files.  They are
not updated as an atomic unit as seen from an HTTP client.

So the order of events is:
1. User or automation adds keys by installing the 'ubuntu-cloud-keyring' apt 
pacakge.
2. User adds the UCA repo using the Ansible apt_repository or other technique, 
possilbly just adding the repo to a sources list file under 
/etc/apt/sources/sources.list.d.
3. Either the tooling (apt_repository module) or the user triggers an apt-get 
update or other apt cache update trigger.  If this cache update hits the timing 
window when UCA is being updated you can get into the state where you have the 
Release file but not the Release.gpg file without triggering a cache or apt-get 
update failure.  A recreation Python main which uses straight python-apt can 
show this.  I will attach my recreation program and output showing the error 
case.
4. At this point, as shown in the original description no further apt-get 
updates will fix the situation and any package installs from UCA will fail with 
"Some packages could not be authenticated".

While the timing window may seem small, probably a minute each hour,
with complex multi-node OpenStack deployments using Ansible we are
seeing this occur fairly frequently. Given the 'juju' in the host name
in the original description I suspect that multi-node orchestrated Juju
charm deployments using UCA are also hitting this often.

The bug is particularly harmful to automated deploy tooling because
while the deploy tooling normally has apt-get update retries or periodic
updates throughout the process, once this error state is entered the
apt-get updates do not work to correct it until after an hour has passed
and UCA has updated itself.  The deployment tooling normally times and
fails much sooner than an hour of retries.

Here is the annotated log output of the recreation script:
#
# In this snippet we see apt update not pulling down the Release.gpg that was 
deleted right before the update to test
# its ability to pull down a new copy.
#
Before update 2017-02-06 22:50:01.915
After update 2017-02-06 22:50:03.044
ctime changed for file 
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release:
 1486421402.8
Path does not exist 
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release.gpg
Before update 2017-02-06 22:50:03.045
After update 2017-02-06 22:50:06.387
ctime changed for file 
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release:
 1486421404.05
mtime changed for file 
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release:
 1486421112.0
Path does not exist 
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release.gpg

#
# In this iteration of the loop we see that the apt update has removed the 
Release file as well as not pulling down the Release.gpg.
# UCA's hourly update is in progress.
#
Before update 2017-02-06 22:50:06.387
After update 2017-02-06 22:50:07.536
Path does not exist 
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release
Path does not exist 
/var/lib/apt/lists/ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release.gpg

#
# In this iteration of the loop we see that the apt update has updates the 
packages file and recreated the Release file.
# However, it did NOT pull down the Release.gpg file.  If an automated tool 
were to hit this window they enter the bug state
# where no amount of updates will fix this until after the next hourly UCA 
update.
#
Before update 2017-02-06 22:50:07.536
After update 2017-02-06 22:50:09.966
ctime changed for file 

[Touch-packages] [Bug 1657440] Re: apt won't redownload Release.gpg

[Samuel Matzek]

** Attachment added: "Recreation script"
   
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657440/+attachment/4814822/+files/recreate.py

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

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

Title:
  apt won't redownload Release.gpg

Status in apt package in Ubuntu:
  Confirmed

Bug description:
  # apt --version
  apt 1.2.18 (amd64)

  xenial

  
  I got myself into a situation where a repository has a Release and a 
Release.gpg file, but apt is just ignoring the gpg one and won't download it 
via apt update for some reason:

  The repository in question is http://ubuntu-
  cloud.archive.canonical.com/ubuntu/dists/xenial-updates/newton/. See
  how locally I have just the Release file:

  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# l *Release*
  -rw-r--r-- 1 root root 100K Jan 15 18:03 
archive.ubuntu.com_ubuntu_dists_xenial-backports_InRelease
  -rw-r--r-- 1 root root 242K Apr 21  2016 
archive.ubuntu.com_ubuntu_dists_xenial_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
archive.ubuntu.com_ubuntu_dists_xenial-updates_InRelease
  -rw-r--r-- 1 root root 100K Jan 18 11:42 
security.ubuntu.com_ubuntu_dists_xenial-security_InRelease
  -rw-r--r-- 1 root root 7.7K Jan 18 11:45 
ubuntu-cloud.archive.canonical.com_ubuntu_dists_xenial-updates_newton_Release

  
  Now I try an update. See how the Release.gpg file gets a "Hit:" instead of a 
"Get:":
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt update
  Get:1 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]
  Hit:2 http://archive.ubuntu.com/ubuntu xenial InRelease   
 
  Ign:3 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
InRelease
  Get:4 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB]
  Hit:5 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release
  Get:6 http://ubuntu-cloud.archive.canonical.com/ubuntu xenial-updates/newton 
Release.gpg [543 B]
  Hit:7 http://archive.ubuntu.com/ubuntu xenial-backports InRelease
  Fetched 205 kB in 0s (395 kB/s)   
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  8 packages can be upgraded. Run 'apt list --upgradable' to see them.

  
  And I can't install packages:
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# apt dist-upgrade
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  The following NEW packages will be installed:
python3-setuptools
  The following packages will be upgraded:
dh-python dnsmasq-base python-pkg-resources python-setuptools 
python3-cryptography python3-pkg-resources python3-requests python3-urllib3
  8 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
  Need to get 1,193 kB of archives.
  After this operation, 808 kB of additional disk space will be used.
  Do you want to continue? [Y/n] 
  WARNING: The following packages cannot be authenticated!
dh-python dnsmasq-base python-setuptools python-pkg-resources 
python3-pkg-resources python3-setuptools python3-cryptography python3-requests 
python3-urllib3
  Install these packages without verification? [y/N] n
  E: Some packages could not be authenticated
  root@juju-cb14ed-0-lxd-3:/var/lib/apt/lists# 

  Somehow apt is thinking it has the Release.gpg file, but it doesn't?

  
  This server is behind a squid proxy.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1657440/+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 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

[Samuel Walladge]

This can probably be closed. After receiving my tablet back from BQ with
the s/n, mac addresses, etc. reset, I haven't had this problem since.

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

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

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Samuel Ballé]

Hello, I have the same issue.
I reported a bug and made it duplicate of this one, including full ubuntu-bug 
xorg data.
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626288

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+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 1626288] Re: X fonts and widgets disappear after suspend/resume cycle

[Samuel Ballé]

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

I wanted to add my report to an existing bug : 
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351
using exactly the same title and based on 
https://help.ubuntu.com/community/ReportingBugs info, I expected the launchpad 
to propose me to add to it instead of creating a new one.

** This bug has been marked a duplicate of bug 1434351
   X fonts and widgets disappear after suspend/resume cycle

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

Title:
   X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  New

Bug description:
  not all the time, but at some suspend/resume operations fonts disapear from 
gnome terminal, nm-applet and soffice which then show spaces and underscore 
placeholders instead of characters.
  google chrome, thunderbird, firefox, virtualbox are not affected.
  As it happens not at each suspend resume I find it hard to diagnose what is 
going wrong.
  next time I will launch more apps to see wich ones are affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   /dev/sdb1: clean, 505825/14589952 files, 3844900/58349824 blocks
   [FAILED] Failed to start Automatically refresh installed snaps.
   See 'systemctl status snapd.refresh.service' for details.
   [  OK  ] Started Detect the available GPUs and deal with any 
system changes.
Starting Light Display Manager...
  CompizPlugins:
   (gconftool-2:18460): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
   Failed to connect to socket /tmp/dbus-NG2bGyKMRZ: Connection refused
   Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
  CompositorRunning: None
  CurrentDesktop: i3
  Date: Wed Sep 21 23:41:50 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:6504]
  InstallationDate: Installed on 2016-07-27 (56 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Notebook W65_67SZ
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ef4d32b1-8cd0-4f61-9e8e-a0a191b86e14 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/26/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.05SB.02
  dmi.board.asset.tag: Tag 12345
  dmi.board.name: W65_67SZ
  dmi.board.vendor: Notebook
  dmi.board.version: Not Applicable
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: Notebook
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05SB.02:bd08/26/2015:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
  dmi.product.name: W65_67SZ
  dmi.product.version: Not Applicable
  dmi.sys.vendor: Notebook
  version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
  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.1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Sep 21 23:08:03 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5941 
   vendor CMN
  xserver.version: 2:1.18.3-1ubuntu2.3

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1626288/+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 1626288] [NEW] X fonts and widgets disappear after suspend/resume cycle

[Samuel Ballé]

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

Public bug reported:

not all the time, but at some suspend/resume operations fonts disapear from 
gnome terminal, nm-applet and soffice which then show spaces and underscore 
placeholders instead of characters.
google chrome, thunderbird, firefox, virtualbox are not affected.
As it happens not at each suspend resume I find it hard to diagnose what is 
going wrong.
next time I will launch more apps to see wich ones are affected.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
Uname: Linux 4.4.0-36-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
BootLog:
 /dev/sdb1: clean, 505825/14589952 files, 3844900/58349824 blocks
 [FAILED] Failed to start Automatically refresh installed snaps.
 See 'systemctl status snapd.refresh.service' for details.
 [  OK  ] Started Detect the available GPUs and deal with any system 
changes.
  Starting Light Display Manager...
CompizPlugins:
 (gconftool-2:18460): GConf-WARNING **: Client failed to connect to the D-BUS 
daemon:
 Failed to connect to socket /tmp/dbus-NG2bGyKMRZ: Connection refused
 Failed to get value for 
`/apps/compiz-1/general/screen0/options/active_plugins': No D-BUS daemon running
CompositorRunning: None
CurrentDesktop: i3
Date: Wed Sep 21 23:41:50 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
   Subsystem: CLEVO/KAPOK Computer 4th Gen Core Processor Integrated Graphics 
Controller [1558:6504]
InstallationDate: Installed on 2016-07-27 (56 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Notebook W65_67SZ
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-36-generic 
root=UUID=ef4d32b1-8cd0-4f61-9e8e-a0a191b86e14 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/26/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05SB.02
dmi.board.asset.tag: Tag 12345
dmi.board.name: W65_67SZ
dmi.board.vendor: Notebook
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 9
dmi.chassis.vendor: Notebook
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.05SB.02:bd08/26/2015:svnNotebook:pnW65_67SZ:pvrNotApplicable:rvnNotebook:rnW65_67SZ:rvrNotApplicable:cvnNotebook:ct9:cvrN/A:
dmi.product.name: W65_67SZ
dmi.product.version: Not Applicable
dmi.sys.vendor: Notebook
version.compiz: compiz 1:0.9.12.2+16.04.20160801.3-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
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.1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Wed Sep 21 23:08:03 2016
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id5941 
 vendor CMN
xserver.version: 2:1.18.3-1ubuntu2.3

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


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

Title:
   X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  New

Bug description:
  not all the time, but at some suspend/resume operations fonts disapear from 
gnome terminal, nm-applet and soffice which then show spaces and underscore 
placeholders instead of characters.
  google chrome, thunderbird, firefox, virtualbox are not affected.
  As it happens not at each suspend resume I find it hard to diagnose what is 
going wrong.
  next time I will launch more apps to see wich ones are affected.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  BootLog:
   /dev/sdb1: clean, 505825/14589952 files, 3844900/58349824 blocks
   [FAILED] 

[Touch-packages] [Bug 1030022] Re: Port from legacy Xlib to modern XCB

[Samuel Henrique]

See discussion at:
https://github.com/joewing/jwm/issues/194

** Bug watch added: github.com/joewing/jwm/issues #194
   https://github.com/joewing/jwm/issues/194

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

** Changed in: jwm (Ubuntu)
 Assignee: (unassigned) => Samuel Henrique (samueloph)

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

Title:
  Port from legacy Xlib to modern XCB

Status in Compiz:
  Triaged
Status in 9wm package in Ubuntu:
  New
Status in aewm package in Ubuntu:
  New
Status in aewm++ package in Ubuntu:
  New
Status in afterstep package in Ubuntu:
  New
Status in amiwm package in Ubuntu:
  New
Status in blackbox package in Ubuntu:
  New
Status in cairo package in Ubuntu:
  New
Status in compiz package in Ubuntu:
  Triaged
Status in ctwm package in Ubuntu:
  New
Status in dwm package in Ubuntu:
  Opinion
Status in enlightenment package in Ubuntu:
  New
Status in fvwm package in Ubuntu:
  New
Status in fvwm1 package in Ubuntu:
  New
Status in gtk+3.0 package in Ubuntu:
  New
Status in icewm package in Ubuntu:
  New
Status in jwm package in Ubuntu:
  Invalid
Status in larswm package in Ubuntu:
  New
Status in lwm package in Ubuntu:
  New
Status in matchbox-window-manager package in Ubuntu:
  New
Status in metacity package in Ubuntu:
  Invalid
Status in miwm package in Ubuntu:
  New
Status in muffin package in Ubuntu:
  New
Status in mutter package in Ubuntu:
  New
Status in pekwm package in Ubuntu:
  New
Status in ratpoison package in Ubuntu:
  New
Status in sapphire package in Ubuntu:
  New
Status in sawfish package in Ubuntu:
  New
Status in spectrwm package in Ubuntu:
  Fix Released
Status in tinywm package in Ubuntu:
  New
Status in tritium package in Ubuntu:
  New
Status in twm package in Ubuntu:
  New
Status in vtwm package in Ubuntu:
  New
Status in w9wm package in Ubuntu:
  New
Status in windowlab package in Ubuntu:
  New
Status in wm2 package in Ubuntu:
  New
Status in wmaker package in Ubuntu:
  New
Status in xmonad package in Ubuntu:
  New

Bug description:
  Port/rewrite the window manager to use the modern XCB (X C Binding)
  library instead of the old legacy Xlib.

To manage notifications about this bug go to:
https://bugs.launchpad.net/compiz/+bug/1030022/+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 1609134] [NEW] ice when compiling included lambda pattern (internal compiler error: in is_base_type, at dwarf2out.c:9968)

[Samuel Just]

Public bug reported:

When compiling the attached repro.cc without the -g flag, g++ succeeds:

~/gcc_bug [deepthought●] » g++ -std=c++11 repro.cc

With the -g flag, g++ hits an internal compiler error:

~/gcc_bug [deepthought●] » g++ -std=c++11 repro.cc -g
repro.cc: In instantiation of ‘struct lambda_visitor’:
repro.cc:10:8:   required from ‘struct lambda_visitor’
repro.cc:49:62:   required from here
repro.cc:22:8: internal compiler error: in is_base_type, at dwarf2out.c:9968
 struct lambda_visitor 
^
Please submit a full bug report,
with preprocessed source if appropriate.
See  for instructions.
Preprocessed source stored into /tmp/cclEDzyl.out file, please attach this to 
your bugreport.

g++ -v:

~/gcc_bug [deepthought●] » g++ -v
Using built-in specs.
COLLECT_GCC=g++
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
4.8.4-2ubuntu1~14.04.3' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs 
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.8 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls 
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap 
--enable-plugin --with-system-zlib --disable-browser-plugin 
--enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 
--with-jvm-jar-dir=/usr/lib/jvm-exports/java-1.5.0-gcj-4.8-amd64 
--with-arch-directory=amd64 --with-ecj-jar=/usr/share/java/eclipse-ecj.jar 
--enable-objc-gc --enable-multiarch --disable-werror --with-arch-32=i686 
--with-abi=m64 --with-multilib-list=m32,m64,mx32 --with-tune=generic 
--enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu 
--target=x86_64-linux-gnu
Thread model: posix
gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.3) 

ice.tgz is attached with
- error.out has the above output
- repro.cc has the source which triggers the ice
- preprocessed_source.cc has the preprocessed source
- the crash file

I reported the bug upstream:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=72779

It seems to be fixed by 5.3.1.

** Affects: gcc-4.8 (Ubuntu)
 Importance: Undecided
 Status: New

** Attachment added: "ice-shorter-reproducer.tgz"
   
https://bugs.launchpad.net/bugs/1609134/+attachment/4712615/+files/ice-shorter-reproducer.tgz

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

Title:
  ice when compiling included lambda pattern (internal compiler error:
  in is_base_type, at dwarf2out.c:9968)

Status in gcc-4.8 package in Ubuntu:
  New

Bug description:
  When compiling the attached repro.cc without the -g flag, g++
  succeeds:

  ~/gcc_bug [deepthought●] » g++ -std=c++11 repro.cc

  With the -g flag, g++ hits an internal compiler error:

  ~/gcc_bug [deepthought●] » g++ -std=c++11 repro.cc -g
  repro.cc: In instantiation of ‘struct lambda_visitor’:
  repro.cc:10:8:   required from ‘struct lambda_visitor’
  repro.cc:49:62:   required from here
  repro.cc:22:8: internal compiler error: in is_base_type, at dwarf2out.c:9968
   struct lambda_visitor 
  ^
  Please submit a full bug report,
  with preprocessed source if appropriate.
  See  for instructions.
  Preprocessed source stored into /tmp/cclEDzyl.out file, please attach this to 
your bugreport.

  g++ -v:

  ~/gcc_bug [deepthought●] » g++ -v
  Using built-in specs.
  COLLECT_GCC=g++
  COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.8/lto-wrapper
  Target: x86_64-linux-gnu
  Configured with: ../src/configure -v --with-pkgversion='Ubuntu 
4.8.4-2ubuntu1~14.04.3' --with-bugurl=file:///usr/share/doc/gcc-4.8/README.Bugs 
--enable-languages=c,c++,java,go,d,fortran,objc,obj-c++ --prefix=/usr 
--program-suffix=-4.8 --enable-shared --enable-linker-build-id 
--libexecdir=/usr/lib --without-included-gettext --enable-threads=posix 
--with-gxx-include-dir=/usr/include/c++/4.8 --libdir=/usr/lib --enable-nls 
--with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug 
--enable-libstdcxx-time=yes --enable-gnu-unique-object --disable-libmudflap 
--enable-plugin --with-system-zlib --disable-browser-plugin 
--enable-java-awt=gtk --enable-gtk-cairo 
--with-java-home=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64/jre --enable-java-home 
--with-jvm-root-dir=/usr/lib/jvm/java-1.5.0-gcj-4.8-amd64 

[Touch-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

[Samuel Walladge]

Ok.

"You will have lost your S/N, MAC addresses, and some key
material the HDMI software expects to find (but does not use)."

What partition(s) keep that data? 
(Asking because I'm trying to gather data for discussing with BQ.)

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

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

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+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 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

[Samuel Walladge]

Ouch. What a way to learn about imei...

Is this then a fault with the flash tool I used? (I mean an official
tool from the manufacturer isn't supposed to destroy the device...)

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

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

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+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 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

[Samuel Walladge]

Also, probably related, I just discovered through an irc conversation on
#ubuntu-touch (thanks Mister_Q) that using the bq flash tool (which I did to 
fix an unbootable
system) and selecting 'format and download' (which I also did), would have
deleted the imei partition.

Quite possible, seeing as the serial number displayed in the 'about' section
shows "0123456789ABCDEF".

Apparently it could also cause my other problem of the tablet not recognizing
or outputting to HDMI monitors via a micro-hdmi to hdmi cable.

Although... that doesn't explain why the wifi problem has been seen before, or
why there's plenty of other reports of the M10 not outputting to displays (at
least not reliably). - see
http://askubuntu.com/questions/762148/bq-m10-ubuntu-touch-micro-hdmi-not-outputting-to-tv
for example.

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

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

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+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 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

[Samuel Walladge]

- syslog is attached
- wifi access point is set up as following: 2.4Ghz, channel 11, 20MHz width, AU 
region, WPA2 PSK security, wps disabled.

** Attachment added: "syslog"
   
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+attachment/4709989/+files/syslog

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

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

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+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 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Samuel W]

I can confirm that this also happens when toggling the radio killswitch
on my x230 with Xenial:

Jul 26 09:48:19 Host NetworkManager[2979]:   [1469540899.8669] manager: 
WiFi now enabled by radio killswitch
Jul 26 09:48:19 Host kernel: [71025.599893] IPv6: ADDRCONF(NETDEV_UP): wlan0: 
link is not ready
Jul 26 09:48:19 Host wpa_supplicant[3344]: dbus: 
wpa_dbus_get_object_properties: failed to get object properties: (none) none
Jul 26 09:48:19 Host wpa_supplicant[3344]: dbus: Failed to construct signal
Jul 26 09:48:19 Host NetworkManager[2979]:   [1469540899.9049] device 
(wlan0): supplicant interface state: starting -> ready
Jul 26 09:48:19 Host NetworkManager[2979]:   [1469540899.9050] device 
(wlan0): state change: unavailable -> disconnected (reason 
'supplicant-available') [20 30 42]
Jul 26 09:48:19 Host kernel: [71025.639368] IPv6: ADDRCONF(NETDEV_UP): wlan0: 
link is not ready

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1585863/+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 1584087] [NEW] package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[Samuel Montes]

Public bug reported:

No tengo ni idea dónde está el error y debido a qué.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: click 0.4.43+16.04.20160203-0ubuntu2
ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
Uname: Linux 4.4.0-22-generic x86_64
ApportVersion: 2.20.1-0ubuntu2
Architecture: amd64
Date: Fri May 20 16:38:16 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2016-05-06 (13 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.10ubuntu1
SourcePackage: click
Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to install/upgrade: 
el subproceso instalado el script post-installation devolvió el código de 
salida de error 1
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package click 0.4.43+16.04.20160203-0ubuntu2 failed to
  install/upgrade: el subproceso instalado el script post-installation
  devolvió el código de salida de error 1

Status in click package in Ubuntu:
  New

Bug description:
  No tengo ni idea dónde está el error y debido a qué.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: click 0.4.43+16.04.20160203-0ubuntu2
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  Date: Fri May 20 16:38:16 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2016-05-06 (13 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.10ubuntu1
  SourcePackage: click
  Title: package click 0.4.43+16.04.20160203-0ubuntu2 failed to 
install/upgrade: el subproceso instalado el script post-installation devolvió 
el código de salida de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/click/+bug/1584087/+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 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

[Samuel]

After 40 hours of trying, I bought a DVD reader and reinstalled Ubuntu. 
I encourage to implement: when we accept proposed updates, a warning appears 
explaining the risks.
Reason: many of us can not understand what is suggested here or elsewhere in 
Internet related with Terminal -no further than copy even if we have an 
extra computer to read online the suggestions -Network Manager was broken- and 
try to solve this problem for days, we still can not repair this bugs. 
PS: move/copy this suggestion if you think of a better place for implementation.

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

Title:
  network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Trusty:
  Fix Committed

Bug description:
  [Triage Notes]

  This regression is caused by a libnl proposed update tracked in bug
  1511735. It has not been released as an update, only proposed as an
  update for early testing. If you volunteered to test proposed updates,
  then thank you. Your care and attention will stop this regression from
  hitting ordinary users, and we appreciate your contribution to Ubuntu.

  If you are not aware that you volunteered to test proposed updates,
  then please be aware that your system is configured to do so. In this
  case, you probably should turn this off. I'd appreciate if someone
  could explain how to do this in the comments.

  [Impact]

   * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200
     libnl-route-3-200) and when libnl is updated to proposed
     3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM
     validation packets.

     This affects the 0.98 release of NetworkManager and has already
     been fixed in newer releases.

   * Backporting fixes from upstream release is required to prevent
     NetworkManager from faulting which breaks networking on most
     Desktop releases.

   * All patches applied are already accepted upstream and newer Ubuntu
     releases are not affected.

   * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating
     libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing.

  [Test Case]

   * Reproduce crash test:
  1. Download 14.04.03 Desktop iso, amd64
  2. Launched in a VM, run from iso
  3. In terminal, enable proposed
  4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
  5. sudo restart network-manager
  #  note the nm-applet disappears as NM has now crashed, no network
     conn.
  6. dmesg to confirm network-manager crash
  7. sudo dpkg --install 
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb 
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
  8. sudo start network-manager
  #  nm-applet reappears, network connectivity restored

   * Successful upgrade test:
     1. Download 14.04.03 Desktop iso, amd64
     2. Launched in a VM, run from iso
     3. In a terminal, sudo dpkg --install 
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb 
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
     4. sudo restart network-manager  # NM still runs, no crash, net up
     5. enable trusty-proposed in /etc/apt/sources.list
     6. sudo apt-get update
     7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
     8. sudo restart network-manager  # NM still runs, no crash, net up.

  [Regression Potential]

   * NetworkManager is a highly visible package, so testing NetworkManager
     functionality is critical.  The patch does address the crash specificly
     introduced by the updated libnl SRU.

   * We need to ensure that users have installed this NetworkManager
     update before installing libnl3 update (special phasing needed).

  [Original Description]
  Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98.

  After installing updated libnl3 and restarting networkmanager, NM
  crashes with:

  /var/log/syslog shows:
  init: network-manager main process (1057) killed by SEGV signal
  init: network-manager main process ended, respawning
  init: network-manager main process (1065) killed by SEGV signal
  init: network-manager respawning too fast, stopped

  The bug has been fixed in upstream 0.98 with these patches:

  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

To manage notifications about this bug go to:

[Touch-packages] [Bug 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

[Samuel]

How did you fix it? I assume that I have to go to 
"https://launchpad.net/ubuntu/+source/network-manager/0.9.8.8-0ubuntu7.3; and 
to "Downloads" where there are 2 folders and one file. If that is right, what 
should I do with those and how can I install them? 
Thank you!

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

Title:
  network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Trusty:
  Fix Committed

Bug description:
  [Triage Notes]

  This regression is caused by a libnl proposed update tracked in bug
  1511735. It has not been released as an update, only proposed as an
  update for early testing. If you volunteered to test proposed updates,
  then thank you. Your care and attention will stop this regression from
  hitting ordinary users, and we appreciate your contribution to Ubuntu.

  If you are not aware that you volunteered to test proposed updates,
  then please be aware that your system is configured to do so. In this
  case, you probably should turn this off. I'd appreciate if someone
  could explain how to do this in the comments.

  [Impact]

   * NetworkManager depends on libnl (libnl-3-200 libnl-genl-3-200
     libnl-route-3-200) and when libnl is updated to proposed
     3.2.21-1ubuntu1 NM segfaults due to libnl exposing a bug in NM
     validation packets.

     This affects the 0.98 release of NetworkManager and has already
     been fixed in newer releases.

   * Backporting fixes from upstream release is required to prevent
     NetworkManager from faulting which breaks networking on most
     Desktop releases.

   * All patches applied are already accepted upstream and newer Ubuntu
     releases are not affected.

   * Upgrading NetworkManager to 0.9.8.8-0ubuntu7.3 prior to updating
     libnl-3.2.21-1ubuntu1 is required to prevent NetworkManager crashing.

  [Test Case]

   * Reproduce crash test:
  1. Download 14.04.03 Desktop iso, amd64
  2. Launched in a VM, run from iso
  3. In terminal, enable proposed
  4. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
  5. sudo restart network-manager
  #  note the nm-applet disappears as NM has now crashed, no network
     conn.
  6. dmesg to confirm network-manager crash
  7. sudo dpkg --install 
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb 
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
  8. sudo start network-manager
  #  nm-applet reappears, network connectivity restored

   * Successful upgrade test:
     1. Download 14.04.03 Desktop iso, amd64
     2. Launched in a VM, run from iso
     3. In a terminal, sudo dpkg --install 
gir1.2-networkmanager-1.0_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib4_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-glib-vpn1_0.9.8.8-0ubuntu7.3_amd64.deb 
libnm-util2_0.9.8.8-0ubuntu7.3_amd64.deb 
network-manager_0.9.8.8-0ubuntu7.3_amd64.deb
     4. sudo restart network-manager  # NM still runs, no crash, net up
     5. enable trusty-proposed in /etc/apt/sources.list
     6. sudo apt-get update
     7. sudo apt-get install libnl-3-200 libnl-genl-3-200 libnl-route-3-200
     8. sudo restart network-manager  # NM still runs, no crash, net up.

  [Regression Potential]

   * NetworkManager is a highly visible package, so testing NetworkManager
     functionality is critical.  The patch does address the crash specificly
     introduced by the updated libnl SRU.

   * We need to ensure that users have installed this NetworkManager
     update before installing libnl3 update (special phasing needed).

  [Original Description]
  Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98.

  After installing updated libnl3 and restarting networkmanager, NM
  crashes with:

  /var/log/syslog shows:
  init: network-manager main process (1057) killed by SEGV signal
  init: network-manager main process ended, respawning
  init: network-manager main process (1065) killed by SEGV signal
  init: network-manager respawning too fast, stopped

  The bug has been fixed in upstream 0.98 with these patches:

  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+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 1539634] Re: network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

[Samuel]

Downgrading using the terminal needs internet in our machine. And if we
paste the previous libnl with a USB stick and click, Ubuntu Software
Center says -Error. A later version is already installed-. I tried
desperate many more things. Provably only a new repaired libnl UPDATE
which we can open by clicking might really solve this for everyone. I
believe there are more people affected but reporting this bug requires
internet.

Thank you.

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

Title:
  network-manager crashes when using libnl-3-200-3.21.1-1ubuntu1

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Trusty:
  Triaged

Bug description:
  Testing out proposed libnl-3 package[1] exposed a bug in NM 0.98.

  After installing updated libnl3 and restarting networkmanager, NM
  crashes with:

  /var/log/syslog shows:
  init: network-manager main process (1057) killed by SEGV signal
  init: network-manager main process ended, respawning
  init: network-manager main process (1065) killed by SEGV signal
  init: network-manager respawning too fast, stopped

  The bug has been fixed in upstream 0.98 with these patches:

  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=8e4576b9fdb5c888d20a13aa2cc198df790dba54
  
http://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=65981edb9f562c07e78815c98093da67c50bfdcf

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1539634/+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 1267059] Re: "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

[Samuel Reed]

This is causing us issues left and right. Has the backport come through
yet? We are still seeing servers fill up disks because of this bug.

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

Title:
  "Unattended-Upgrade::Remove-Unused-Dependencies" does not work

Status in unattended-upgrades package in Ubuntu:
  Fix Released

Bug description:
  I have a system that runs unattended-upgrades just fine. Now i want to
  automate removal of old kernels and kernel header packages that are
  accumulating otherwise. So i set 'Unattended-Upgrade::Remove-Unused-
  Dependencies "true";'. But it doesn't work.

  
  Details: Lots of stuff pending autoremoval:

  $ apt-get --assume-no autoremove 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following packages will be REMOVED
linux-headers-3.2.0-38 linux-headers-3.2.0-38-generic 
linux-headers-3.2.0-39 linux-headers-3.2.0-39-generic linux-headers-3.2.0-40 
linux-headers-3.2.0-40-generic linux-headers-3.2.0-41 
linux-headers-3.2.0-41-generic linux-headers-3.2.0-43 
linux-headers-3.2.0-43-generic linux-headers-3.2.0-44 
linux-headers-3.2.0-44-generic linux-headers-3.2.0-45 
linux-headers-3.2.0-45-generic linux-headers-3.2.0-48 
linux-headers-3.2.0-48-generic linux-headers-3.2.0-51 
linux-headers-3.2.0-51-generic linux-headers-3.2.0-52 
linux-headers-3.2.0-52-generic linux-headers-3.2.0-53 
linux-headers-3.2.0-53-generic linux-headers-3.2.0-54 
linux-headers-3.2.0-54-generic linux-headers-3.2.0-55 
linux-headers-3.2.0-55-generic linux-headers-3.2.0-56 
linux-headers-3.2.0-56-generic linux-image-3.2.0-39-generic 
linux-image-3.2.0-40-generic linux-image-3.2.0-41-generic 
linux-image-3.2.0-43-generic linux-image-3.2.0-44-generic 
linux-image-3.2.0-45-generic linux-image-3.2.0-48-generic 
linux-image-3.2.0-51-generic linux-
 image-3.2.0-52-generic linux-image-3.2.0-53-generic 
linux-image-3.2.0-54-generic linux-image-3.2.0-55-generic 
linux-image-3.2.0-56-generic
  0 upgraded, 0 newly installed, 41 to remove and 13 not upgraded.
  After this operation, 2,893 MB disk space will be freed.
  Do you want to continue [Y/n]? N
  Abort.

  Note that the majority of these packages have been installed by
  unattended-upgrades from precise-security.

  According to the comments within/etc/apt/apt.conf.d/50unattended-
  upgrades, this should automate autoremoval:

// Do automatic removal of new unused dependencies after the upgrade
// (equivalent to apt-get autoremove)
Unattended-Upgrade::Remove-Unused-Dependencies "true";

  but nothing happens (note the line "Packages that are auto removed: ''
  ":

  $ unattended-upgrades --debug --dry-run
  Initial blacklisted packages: 
  Starting unattended upgrades script
  Allowed origins are: ['o=Ubuntu,a=precise-security']
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  adjusting candidate version: ''
  Checking: bc ([""])
  Checking: grub-common ([""])
  Checking: grub-pc ([""])
  Checking: grub-pc-bin ([""])
  Checking: grub2-common ([""])
  Checking: iproute ([""])
  Checking: landscape-common ([""])
  pkgs that look like they should be upgraded: 
  Fetched 0 B in 0s (0 B/s) 

 
  blacklist: []
  Packages that are auto removed: ''
  InstCount=0 DelCount=0 BrokenCout=0
  No packages found that can be upgraded unattended

  
  
  I am using unattended-upgrades-0.76ubuntu1 on Ubuntu 12.04.3 LTS

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1267059/+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 1140716]

[Samuel Rakitničan]

(In reply to Chris Wilson from comment #192)
> (In reply to comment #191)
> > What information is most useful for these repeating issues, as it just
> > happened again:
> > 
> >  Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139690] [drm] stuck on
> > render ring
> >  Sep 16 08:32:59 arrowsmithlap1 kernel: [1182242.139699] [drm] stuck on
> > blitter ring
> 
> So long as it is the same event, there is no more information we need other
> than testing feedback for an eventual workaround.

Is this the same bug?

$ journalctl -p 3 -b -1
Ruj 25 02:13:01 crnigrom kernel: [drm:fw_domains_get [i915]] *ERROR* render: 
timed out waiting for forcewake ack request.
Ruj 25 02:13:01 crnigrom kernel: [drm:__gen6_gt_wait_for_thread_c0.isra.16 
[i915]] *ERROR* GT thread status wait timed out
... [ repeated messages ] ...
Ruj 25 02:13:33 crnigrom kernel: [drm:fw_domains_get [i915]] *ERROR* render: 
timed out waiting for forcewake ack request.
Ruj 25 02:13:33 crnigrom kernel: [drm:__gen6_gt_wait_for_thread_c0.isra.16 
[i915]] *ERROR* GT thread status wait timed out
Ruj 25 02:13:34 crnigrom kernel: [drm:stop_ring [i915]] *ERROR* render ring : 
timed out trying to stop ring
Ruj 25 02:13:34 crnigrom kernel: [drm:init_ring_common [i915]] *ERROR* render 
ring initialization failed ctl  (valid? 0) head  tail  
start  [expected ]
Ruj 25 02:13:34 crnigrom kernel: [drm:i915_reset [i915]] *ERROR* Failed hw init 
on reset -5
Ruj 25 02:13:34 crnigrom gnome-session[1823]: Unrecoverable failure in required 
component gnome-shell.desktop

After which gnome crashes with "Oh No Something Is Wrong" screen

$ uname -r
4.1.7-200.fc22.x86_64

Hardware i3-2100 CPU/GPU

This bug is going on already for a long long time, but at least computer
is not hard freezing anymore, although gnome is crashing so any gtk
applications running doing something stalls.

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

Title:
  [regression] 3.5.0-26-generic and  3.2.0-39-generic GPU hangs on
  Sandybridge

Status in DRI:
  In Progress
Status in Mesa:
  Unknown
Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Fix Committed
Status in linux-lts-quantal source package in Precise:
  Fix Committed
Status in linux-lts-raring source package in Precise:
  Invalid
Status in mesa source package in Precise:
  Triaged
Status in linux source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux source package in Raring:
  Invalid
Status in linux-lts-quantal source package in Raring:
  Invalid
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  I'm getting errors about GPU hangs every minute or so (usually only
  when using FF and scrolling a webpage or something). I also get an
  annoying ubuntu dialog saying there is a "system error".

  This didn't happen with 3.5.0-24-generic.

  Here is the dmesg:
  [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.658405] [ cut here ]
  [26285.658472] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26285.658474] Hardware name: SATELLITE Z830
  [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm 
arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel 
snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep 
iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi 
rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer 
snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap 
soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei 
video mac_hid lpc_ich 

[Touch-packages] [Bug 1463332] Re: zeitgeist-datahub.vala:229: Unable to get name org.gnome.zeitgeist.datahub on the bus!

[Samuel Suther]

Same here for Kubuntu (KDE-Desktop)

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

Title:
   zeitgeist-datahub.vala:229: Unable to get name
  org.gnome.zeitgeist.datahub on the bus!

Status in zeitgeist package in Ubuntu:
  Confirmed

Bug description:
  get that error logged into journalctl:

  org.gnome.zeitgeist.Engine[1675]: ** (zeitgeist-datahub:2083): WARNING
  **: zeitgeist-datahub.vala:229: Unable to get name
  org.gnome.zeitgeist.datahub on the bus!

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: zeitgeist-datahub 0.9.14-2.2ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-20.20-generic 3.19.8
  Uname: Linux 3.19.0-20-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.17.3-0ubuntu4
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Jun  9 11:32:35 2015
  SourcePackage: zeitgeist
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zeitgeist/+bug/1463332/+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 1469167] [NEW] package linux-image-3.16.0-41-generic 3.16.0-41.57 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1

[Samuel]

Public bug reported:

I got the error while running apt-get upgrade.

ProblemType: Package
DistroRelease: Ubuntu 14.10
Package: linux-image-3.16.0-41-generic 3.16.0-41.57
ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
Uname: Linux 3.13.0-55-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.14.7-0ubuntu8.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  samuel19558 F pulseaudio
 /dev/snd/controlC0:  samuel19558 F pulseaudio
Date: Fri Jun 26 14:46:22 2015
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-trusty-amd64-20140620-0
DuplicateSignature: 
package:linux-image-3.16.0-41-generic:3.16.0-41.57:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
HibernationDevice: RESUME=UUID=5663324b-b453-451b-abaa-70a6518f0556
InstallationDate: Installed on 2015-05-22 (35 days ago)
InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20140620-04:25
MachineType: Dell Inc. XPS 13 9343
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic 
root=UUID=41e92da2-5f16-4db8-a47b-2f7d60b0caaa ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc N/A
SourcePackage: initramfs-tools
Title: package linux-image-3.16.0-41-generic 3.16.0-41.57 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
UpgradeStatus: Upgraded to utopic on 2015-06-26 (0 days ago)
dmi.bios.date: 03/25/2015
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A03
dmi.board.name: 0TM99H
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd03/25/2015:svnDellInc.:pnXPS139343:pvr01:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
dmi.product.name: XPS 13 9343
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

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


** Tags: amd64 apport-package dist-upgrade utopic

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

Title:
  package linux-image-3.16.0-41-generic 3.16.0-41.57 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:
  I got the error while running apt-get upgrade.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: linux-image-3.16.0-41-generic 3.16.0-41.57
  ProcVersionSignature: Ubuntu 3.13.0-55.94-generic 3.13.11-ckt20
  Uname: Linux 3.13.0-55-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.14.7-0ubuntu8.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  samuel19558 F pulseaudio
   /dev/snd/controlC0:  samuel19558 F pulseaudio
  Date: Fri Jun 26 14:46:22 2015
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DuplicateSignature: 
package:linux-image-3.16.0-41-generic:3.16.0-41.57:run-parts: 
/etc/kernel/postinst.d/initramfs-tools exited with return code 1
  ErrorMessage: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  HibernationDevice: RESUME=UUID=5663324b-b453-451b-abaa-70a6518f0556
  InstallationDate: Installed on 2015-05-22 (35 days ago)
  InstallationMedia: Ubuntu 14.04 Trusty - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. XPS 13 9343
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-55-generic 
root=UUID=41e92da2-5f16-4db8-a47b-2f7d60b0caaa ro quiet splash pcie_aspm=force 
radeon.modeset=0 nouveau.modeset=0 video.use_native_backlight=1
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc N/A
  SourcePackage: initramfs-tools
  Title: package linux-image-3.16.0-41-generic 3.16.0-41.57 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/initramfs-tools exited with 
return code 1
  UpgradeStatus: Upgraded to utopic on 2015-06-26 (0 days ago)
  dmi.bios.date: 03/25/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc

[Touch-packages] [Bug 1453597] [NEW] Builtins don't have help (-h or --help) option

[John Samuel]

Public bug reported:

Bash builtins like doesn't have -h (or --help) option.

$ alias -h
bash: alias: -h: invalid option
alias: usage: alias [-p] [name[=value] ... ]

$ builtin -h
bash: builtin: -h: invalid option
builtin: usage: builtin [shell-builtin [arg ...]]


$ apt-cache policy bash
bash:
  Installed: 4.3-11ubuntu2
  Candidate: 4.3-11ubuntu2
  Version table:
 *** 4.3-11ubuntu2 0
500 http://fr.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
100 /var/lib/dpkg/status
$ lsb_release -rd
Description:Ubuntu 15.04
Release:15.04

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

** Summary changed:

- Builtins doesn't have help (-h or --help) option
+ Builtins don't have help (-h or --help) option

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

Title:
  Builtins don't have help (-h or --help) option

Status in bash package in Ubuntu:
  New

Bug description:
  Bash builtins like doesn't have -h (or --help) option.

  $ alias -h
  bash: alias: -h: invalid option
  alias: usage: alias [-p] [name[=value] ... ]

  $ builtin -h
  bash: builtin: -h: invalid option
  builtin: usage: builtin [shell-builtin [arg ...]]

  
  $ apt-cache policy bash
  bash:
Installed: 4.3-11ubuntu2
Candidate: 4.3-11ubuntu2
Version table:
   *** 4.3-11ubuntu2 0
  500 http://fr.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages
  100 /var/lib/dpkg/status
  $ lsb_release -rd
  Description:  Ubuntu 15.04
  Release:  15.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1453597/+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 1405478] Re: invokation with -h doesn't correpond to usage instructions

[John Samuel]

This feature is desirable for all other builtins. It looks like builtins
only use the short versions of options and not the long versions.

Reference:  https://sources.debian.net/src/bash/4.3-12/builtins/jobs.def/#L242

while ((opt = internal_getopt (list, ahr)) != -1)
{
  switch (opt)


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

Title:
  invokation with -h doesn't correpond to usage instructions

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Invoking `disown --help` displays usage instructions

  $ disown --help
  bash: disown: --: invalid option
  disown: usage: disown [-h] [-ar] [jobspec ...]

  but invocation of `disown -h` displays

  bash: disown: current: no such job

  which is inconsistent.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: bash 4.3-11ubuntu1
  Uname: Linux 3.19.0-031900rc1-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Dec 24 20:35:20 2014
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1405478/+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 1449621] Re: Connecting to external display turns off laptop screen

[Samuel]

Thanks, my laptop is Hewlett-Packard HP Pavilion m6 -1035dx . Here is the
exact model on hp:
http://support.hp.com/us-en/document/c03383025
Thank you.

On Sat, May 2, 2015 at 9:00 AM Christopher M. Penalver 
christopher.m.penal...@gmail.com wrote:

 Samuel, thank you for reporting this and helping make Ubuntu better.
 Could you please provide the full computer model as noted on the sticker
 of the computer itself (not from the Bug Description)?

 ** Changed in: xorg (Ubuntu)
Importance: Undecided = Low

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

 --
 You received this bug notification because you are subscribed to the bug
 report.
 https://bugs.launchpad.net/bugs/1449621

 Title:
   Connecting to external display turns off laptop screen

 Status in xorg package in Ubuntu:
   Incomplete

 Bug description:
   I'm using HP Pavilion m6 laptop with AMD A10. Connecting to external
   monitor using normal VGA cable causes laptop monitor to turn off
   permanently. disconnecting external display does not do anything.

   ProblemType: Bug
   DistroRelease: Ubuntu 14.04
   Package: xorg 1:7.7+1ubuntu8.1
   ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
   Uname: Linux 3.16.0-33-generic x86_64
   .tmp.unity.support.test.0:

   ApportVersion: 2.14.1-0ubuntu3.8
   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
   CurrentDesktop: Unity
   Date: Tue Apr 28 08:16:50 2015
   DistUpgraded: Fresh install
   DistroCodename: trusty
   DistroVariant: ubuntu
   DpkgLog:

   ExtraDebuggingInterest: Yes, if not too technical
   GraphicsCard:
Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660G]
 [1002:9900] (prog-if 00 [VGA controller])
  Subsystem: Hewlett-Packard Company Device [103c:18a6]
   InstallationDate: Installed on 2015-03-30 (28 days ago)
   InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64
 (20150218.1)
   MachineType: Hewlett-Packard HP Pavilion m6 Notebook PC
   ProcEnviron:
LANGUAGE=en_US
PATH=(custom, no user)
XDG_RUNTIME_DIR=set
LANG=en_US.UTF-8
SHELL=/bin/bash
   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic
 root=UUID=0694a3e0-7768-4daa-837f-17aa85fc5462 ro quiet splash vt.handoff=7
   SourcePackage: xorg
   Symptom: display
   UpgradeStatus: No upgrade log present (probably fresh install)
   dmi.bios.date: 09/23/2013
   dmi.bios.vendor: Insyde
   dmi.bios.version: F.35
   dmi.board.asset.tag: Base Board Asset Tag
   dmi.board.name: 18A6
   dmi.board.vendor: Hewlett-Packard
   dmi.board.version: 74.80
   dmi.chassis.asset.tag: Chassis Asset Tag
   dmi.chassis.type: 10
   dmi.chassis.vendor: Hewlett-Packard
   dmi.chassis.version: Chassis Version
   dmi.modalias:
 dmi:bvnInsyde:bvrF.35:bd09/23/2013:svnHewlett-Packard:pnHPPavilionm6NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn18A6:rvr74.80:cvnHewlett-Packard:ct10:cvrChassisVersion:
   dmi.product.name: HP Pavilion m6 Notebook PC
   dmi.product.version: 07911020561620100
   dmi.sys.vendor: Hewlett-Packard
   version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
   version.ia32-libs: ia32-libs N/A
   version.libdrm2: libdrm2 2.4.56-1~ubuntu2
   version.libgl1-mesa-dri: libgl1-mesa-dri N/A
   version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
   version.libgl1-mesa-glx: libgl1-mesa-glx N/A
   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: Tue Apr 28 08:02:11 2015
   xserver.configfile: default
   xserver.errors:

   xserver.logfile: /var/log/Xorg.0.log
   xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
   xserver.video_driver: radeon

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


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

Title:
  Connecting to external display turns off laptop screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm using HP Pavilion m6 laptop with AMD A10. Connecting to external
  monitor using normal VGA cable causes laptop monitor to turn off
  permanently. disconnecting external display does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.8
  Architecture

[Touch-packages] [Bug 1449621] [NEW] Connecting to external display turns off laptop screen

[Samuel]

Public bug reported:

I'm using HP Pavilion m6 laptop with AMD A10. Connecting to external
monitor using normal VGA cable causes laptop monitor to turn off
permanently. disconnecting external display does not do anything.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: xorg 1:7.7+1ubuntu8.1
ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
Uname: Linux 3.16.0-33-generic x86_64
.tmp.unity.support.test.0:
 
ApportVersion: 2.14.1-0ubuntu3.8
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
CurrentDesktop: Unity
Date: Tue Apr 28 08:16:50 2015
DistUpgraded: Fresh install
DistroCodename: trusty
DistroVariant: ubuntu
DpkgLog:
 
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660G] [1002:9900] 
(prog-if 00 [VGA controller])
   Subsystem: Hewlett-Packard Company Device [103c:18a6]
InstallationDate: Installed on 2015-03-30 (28 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 (20150218.1)
MachineType: Hewlett-Packard HP Pavilion m6 Notebook PC
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic 
root=UUID=0694a3e0-7768-4daa-837f-17aa85fc5462 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/23/2013
dmi.bios.vendor: Insyde
dmi.bios.version: F.35
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 18A6
dmi.board.vendor: Hewlett-Packard
dmi.board.version: 74.80
dmi.chassis.asset.tag: Chassis Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: 
dmi:bvnInsyde:bvrF.35:bd09/23/2013:svnHewlett-Packard:pnHPPavilionm6NotebookPC:pvr07911020561620100:rvnHewlett-Packard:rn18A6:rvr74.80:cvnHewlett-Packard:ct10:cvrChassisVersion:
dmi.product.name: HP Pavilion m6 Notebook PC
dmi.product.version: 07911020561620100
dmi.sys.vendor: Hewlett-Packard
version.compiz: compiz 1:0.9.11.3+14.04.20150122-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.56-1~ubuntu2
version.libgl1-mesa-dri: libgl1-mesa-dri N/A
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx N/A
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: Tue Apr 28 08:02:11 2015
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.16.0-1ubuntu1.2~trusty2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 trusty ubuntu

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

Title:
  Connecting to external display turns off laptop screen

Status in xorg package in Ubuntu:
  New

Bug description:
  I'm using HP Pavilion m6 laptop with AMD A10. Connecting to external
  monitor using normal VGA cable causes laptop monitor to turn off
  permanently. disconnecting external display does not do anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.16.0-33.44~14.04.1-generic 3.16.7-ckt7
  Uname: Linux 3.16.0-33-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3.8
  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
  CurrentDesktop: Unity
  Date: Tue Apr 28 08:16:50 2015
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  DpkgLog:
   
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Trinity [Radeon HD 7660G] [1002:9900] 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Device [103c:18a6]
  InstallationDate: Installed on 2015-03-30 (28 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS Trusty Tahr - Release amd64 
(20150218.1)
  MachineType: Hewlett-Packard HP Pavilion m6 Notebook PC
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-33-generic 

[Touch-packages] [Bug 1433155] Re: bash kill -l builtin gives wrong numbers for SIGRTMIN+n signals

[John Samuel]

On executing the following command

$ grep SIGRTMIN /usr/include/ -r
/usr/include/asm-generic/signal.h:#define SIGRTMIN  32
/usr/include/x86_64-linux-gnu/asm/signal.h:#define SIGRTMIN 32
/usr/include/x86_64-linux-gnu/bits/signum.h:#define SIGRTMIN
(__libc_current_sigrtmin ())
/usr/include/x86_64-linux-gnu/bits/signum.h:#define __SIGRTMIN  32

and checking the source code of glibc-2.19/signal/allocrtsig.c
...
/* Return number of available real-time signal with highest priority.  */
int
__libc_current_sigrtmin (void)
{
#ifdef __SIGRTMIN
  if (!initialized)
init ();
#endif
  return current_rtmin;
}
...

It seems that bash uses the value of current_rtmin

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

Title:
  bash kill -l builtin gives wrong numbers for SIGRTMIN+n signals

Status in bash package in Ubuntu:
  New

Bug description:
  The command grep SIGRTMIN /usr/include/ -r gives me

  /usr/include/asm/signal.h:#define SIGRTMIN  32

  and a bunch of other defines with the same value. But if I ask bash's
  kill builtin via kill -l, I get 34) SIGRTMIN. What's
  interesting, there's actually no number 32 listed at all. Number 34
  goes right after 31, where the right 32 should appear. The other names
  defined via SIGRTMIN are also wrong.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: bash 4.2-2ubuntu2.6
  ProcVersionSignature: Ubuntu 3.2.0-76.111-generic 3.2.66
  Uname: Linux 3.2.0-76-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.6
  Architecture: amd64
  Date: Tue Mar 17 18:34:25 2015
  InstallationMedia: Kubuntu 12.04 LTS Precise Pangolin - Release amd64 
(20120423)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: bash
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1433155/+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 445333] Re: remember password on printing to windows printers does not work

[Samuel Bancal]

** Attachment added: print_step2.png
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4344090/+files/print_step2.png

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

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

Title:
  remember password on printing to windows printers does not work

Status in GTK+ GUI Toolkit:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Trusty:
  Fix Committed
Status in gtk+3.0 source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * Passwords for printers are not stored and the users are required
 to retype it with every print job for password protected printers

  [Test Case]

   * Configure a remote (shared via SMB), password-protected printer.

   * Request a print job.

   * Each subsequent job will require retyping the password.

  [Regression Potential]

   * Cherry-pick from upstream (present in Gtk+3.13.8).

   * Minor conflict resolution needed (line numbers changed)

  [Other Info]
   
   * Original bug description:
  i am printing from my ubuntu karmic to a windows box. everytime i print i get 
asked to input username and password to windows box, then the document gets 
printed. there is a remember password checkbox, but it keeps asking me when 
printing the next document.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/445333/+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 445333] Re: remember password on printing to windows printers does not work

[Samuel Bancal]

** Attachment added: print_step1.png
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333/+attachment/4344089/+files/print_step1.png

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

Title:
  remember password on printing to windows printers does not work

Status in GTK+ GUI Toolkit:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Trusty:
  Fix Committed
Status in gtk+3.0 source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * Passwords for printers are not stored and the users are required
 to retype it with every print job for password protected printers

  [Test Case]

   * Configure a remote (shared via SMB), password-protected printer.

   * Request a print job.

   * Each subsequent job will require retyping the password.

  [Regression Potential]

   * Cherry-pick from upstream (present in Gtk+3.13.8).

   * Minor conflict resolution needed (line numbers changed)

  [Other Info]
   
   * Original bug description:
  i am printing from my ubuntu karmic to a windows box. everytime i print i get 
asked to input username and password to windows box, then the document gets 
printed. there is a remember password checkbox, but it keeps asking me when 
printing the next document.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/445333/+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 445333] Re: remember password on printing to windows printers does not work

[Samuel Bancal]

sudo vi /etc/apt/sources.list
# snip
# Trusty Proposed - test GTK2 patch 
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/445333
deb http://archive.ubuntu.com/ubuntu/ trusty-proposed restricted main 
multiverse universe
# snap

sudo apt-get update
sudo apt-get install libgail-common libgail18 libgtk2.0-common libgtk2.0-bin 
libgtk2.0-0
Reading package lists... Done
Building dependency tree   
Reading state information... Done
The following packages will be upgraded:
  libgail-common libgail18 libgtk2.0-0 libgtk2.0-bin libgtk2.0-common
5 upgraded, 0 newly installed, 0 to remove and 209 not upgraded.
Need to get 1'994 kB of archives.
After this operation, 13.3 kB of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libgail-common 
amd64 2.24.23-0ubuntu1.2 [110 kB]
Get:2 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libgtk2.0-common 
all 2.24.23-0ubuntu1.2 [121 kB]
Get:3 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libgtk2.0-bin 
amd64 2.24.23-0ubuntu1.2 [9'798 B]
Get:4 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libgail18 amd64 
2.24.23-0ubuntu1.2 [14.1 kB]
Get:5 http://archive.ubuntu.com/ubuntu/ trusty-proposed/main libgtk2.0-0 amd64 
2.24.23-0ubuntu1.2 [1'739 kB]
Fetched 1'994 kB in 0s (4'148 kB/s)
[...]

I run the following test steps :

Initial status : Gnome keyring is empty

Step #1 :
 print from Firefox
 Nothing asked, new printer icon on top right of the screen. Click - Job#1 is 
Held for authentication
 Right-click  Authenticate
 I Give the credentials and check the Remember password. (attached 
print_step1.png)
 Job is printed
 Gnome keyring gets a Network password entry 
domain\usern...@printserver.epfl.ch (smb)
 
Step #2 :
 print from Firefox
 A dialog opens ans ask for authentication Authentication is required to print 
document Title on printer printername.
 I Give the credentials and check the Remember password. (attached 
print_step2.png)
 Job is printed
 Gnome keyring gets a second Password or secret entry 
ipp://localhost:631/printers/printername

Step #3 and following :
 print from Firefox
 No dialog comes to the user
 Job is printed
 Gnome keyring has no more entries than the 2 said before.

To me this is the acceptable behaviour.
Ideal would even be to have step #1 asking interactively for credentials, step 
#2 skipped so that we get immediately step #3. But this is outside the scope of 
this bug report I think.

Thanks!
Samuel

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

Title:
  remember password on printing to windows printers does not work

Status in GTK+ GUI Toolkit:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Fix Released
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Trusty:
  Fix Committed
Status in gtk+3.0 source package in Trusty:
  Fix Released

Bug description:
  [Impact]

   * Passwords for printers are not stored and the users are required
 to retype it with every print job for password protected printers

  [Test Case]

   * Configure a remote (shared via SMB), password-protected printer.

   * Request a print job.

   * Each subsequent job will require retyping the password.

  [Regression Potential]

   * Cherry-pick from upstream (present in Gtk+3.13.8).

   * Minor conflict resolution needed (line numbers changed)

  [Other Info]
   
   * Original bug description:
  i am printing from my ubuntu karmic to a windows box. everytime i print i get 
asked to input username and password to windows box, then the document gets 
printed. there is a remember password checkbox, but it keeps asking me when 
printing the next document.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/445333/+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 1140716]

[Samuel Rakitničan]

*** Bug 88626 has been marked as a duplicate of this bug. ***

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

Title:
  [regression] 3.5.0-26-generic and  3.2.0-39-generic GPU hangs on
  Sandybridge

Status in Direct Rendering Infrastructure:
  In Progress
Status in The Linux Kernel:
  Invalid
Status in linux package in Ubuntu:
  Invalid
Status in linux-lts-quantal package in Ubuntu:
  Invalid
Status in linux-lts-raring package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Triaged
Status in linux source package in Precise:
  Invalid
Status in linux-lts-quantal source package in Precise:
  Invalid
Status in linux-lts-raring source package in Precise:
  Invalid
Status in mesa source package in Precise:
  Triaged
Status in linux source package in Quantal:
  Invalid
Status in linux-lts-quantal source package in Quantal:
  Invalid
Status in linux source package in Raring:
  Invalid
Status in linux-lts-quantal source package in Raring:
  Invalid
Status in linux package in Debian:
  New
Status in linux package in Fedora:
  Unknown

Bug description:
  I'm getting errors about GPU hangs every minute or so (usually only
  when using FF and scrolling a webpage or something). I also get an
  annoying ubuntu dialog saying there is a system error.

  This didn't happen with 3.5.0-24-generic.

  Here is the dmesg:
  [15169.033709] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15169.034517] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15628.480216] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15628.480570] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [15844.231372] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [15844.231773] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [20173.232593] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [20173.233211] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.650393] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26285.650980] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26285.658405] [ cut here ]
  [26285.658472] WARNING: at 
/build/buildd/linux-3.5.0/drivers/gpu/drm/i915/intel_pm.c:2505 
gen6_enable_rps+0x706/0x710 [i915]()
  [26285.658474] Hardware name: SATELLITE Z830
  [26285.658476] Modules linked in: sdhci_pci sdhci btrfs zlib_deflate 
libcrc32c ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs reiserfs ext2 
snd_hda_codec_hdmi snd_hda_codec_realtek joydev btusb coretemp kvm_intel kvm 
arc4 ghash_clmulni_intel aesni_intel cryptd aes_x86_64 snd_hda_intel 
snd_hda_codec snd_hwdep uvcvideo snd_pcm videobuf2_core microcode videodev bnep 
iwlwifi videobuf2_vmalloc snd_seq_midi psmouse videobuf2_memops snd_rawmidi 
rfcomm pcspkr snd_seq_midi_event serio_raw snd_seq bluetooth mac80211 snd_timer 
snd_seq_device i915 drm_kms_helper cfg80211 drm toshiba_acpi snd sparse_keymap 
soundcore wmi i2c_algo_bit toshiba_bluetooth snd_page_alloc parport_pc mei 
video mac_hid lpc_ich ppdev nfsd nfs lockd fscache auth_rpcgss nfs_acl sunrpc 
lp parport e1000e ahci libahci [last unloaded: sdhci]
  [26285.658537] Pid: 23433, comm: kworker/u:0 Not tainted 3.5.0-26-generic 
#40-Ubuntu
  [26285.658539] Call Trace:
  [26285.658549]  [81051bef] warn_slowpath_common+0x7f/0xc0
  [26285.658553]  [81051c4a] warn_slowpath_null+0x1a/0x20
  [26285.658569]  [a02d32e6] gen6_enable_rps+0x706/0x710 [i915]
  [26285.658584]  [a02bf3f6] intel_modeset_init_hw+0x66/0xa0 [i915]
  [26285.658595]  [a02954b4] i915_reset+0x1a4/0x6e0 [i915]
  [26285.658601]  [8101257b] ? __switch_to+0x12b/0x420
  [26285.658612]  [a029a943] i915_error_work_func+0xc3/0x110 [i915]
  [26285.658618]  [8107097a] process_one_work+0x12a/0x420
  [26285.658629]  [a029a880] ? gen6_pm_rps_work+0xe0/0xe0 [i915]
  [26285.658632]  [8107152e] worker_thread+0x12e/0x2f0
  [26285.658636]  [81071400] ? manage_workers.isra.26+0x200/0x200
  [26285.658640]  [81076023] kthread+0x93/0xa0
  [26285.658644]  [8168a3e4] kernel_thread_helper+0x4/0x10
  [26285.658649]  [81075f90] ? kthread_freezable_should_stop+0x70/0x70
  [26285.658652]  [8168a3e0] ? gs_change+0x13/0x13
  [26285.658654] ---[ end trace 59c6162fdfcbffee ]---
  [26756.021167] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26756.021426] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26766.014093] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26766.014397] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  [26932.376233] [drm:i915_hangcheck_hung] *ERROR* Hangcheck timer elapsed... 
GPU hung
  [26932.376544] [drm] Enabling RC6 states: RC6 on, RC6p off, RC6pp off
  

[Touch-packages] [Bug 531208]

[Samuel Suther]

+ 10 for the implementation of this UNICODE-FEATURE.

At the moment I'm coding on a Keyboard-Firmware (ErgoDox). Problem is
that I can send UNICODE-Chars easy and nice with the GNOME-Method :
CTRL+Shift+digits, but there is no way to send them to QT-Based
Programms.

So keep calm and implement the Shortcut which is still implemented in
Gnome (and please, please, please don't choose another one like CTRL+
META or such different Stuff...) Keep things easy and implement like it
still works in Gnome.

BTW: Thanks a lot for all your work. I love KDE.

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

Title:
  Need way to insert arbitrary unicode characters in Kubuntu

Status in X.Org X server:
  Confirmed
Status in xorg package in Ubuntu:
  Won't Fix

Bug description:
  KDE, Qt, and Xorg are in disagreement about who should implement ISO 14755, 
which would facilitate the input of arbitrary unicode characters. This is the 
original KDE bug:
  https://bugs.kde.org/show_bug.cgi?id=103788

  It was pushed upstream to Qt:
  http://bugreports.qt.nokia.com/browse/QTBUG-8

  From there it was pushed further upstream to Xorg:
  https://bugs.freedesktop.org/show_bug.cgi?id=26747

  Xorg pushes the bug downstream, back to either Qt or KDE to implement,
  just as Gnome implemented the fix themselves. An Xorg developer who
  does not want to be named says that if KDE won't implement it then my
  distro should. So here I file that request.

  Note that in KDE 3 one could use the Kcharselect applet to enter arbitrary 
unicode characters, however that has been disabled in KDE 4:
  https://bugs.kde.org/show_bug.cgi?id=190776

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/531208/+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 445333] Re: remember password on printing to windows printers does not work

[Samuel Bancal]

Hello,

I upgraded from trusty-proposed:
- libgail-3-0:amd64 3.10.8-0ubuntu1.3
- libgtk-3-0:amd64 3.10.8-0ubuntu1.3

Here is my test scenario (using gedit):

Nothing in gnome keyring
Print text1
A dialog asked for credentials (I fill and check remember)
job is printed  credentials appear in gnome keyring

Print text2
no dialog appear, job is printed

Print text3
no dialog appear, job is printed

Then I deleted the credentials in gnome keyring
Print text4
A dialog asked again for credentials.

The new packages looks perfect to me! :)

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

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

Title:
  remember password on printing to windows printers does not work

Status in GTK+ GUI Toolkit:
  Fix Released
Status in gtk+2.0 package in Ubuntu:
  Triaged
Status in gtk+3.0 package in Ubuntu:
  Fix Released
Status in gtk+2.0 source package in Trusty:
  Triaged
Status in gtk+3.0 source package in Trusty:
  Fix Committed

Bug description:
  [Impact]

   * Passwords for printers are not stored and the users are required
 to retype it with every print job for password protected printers

  [Test Case]

   * Configure a remote (shared via SMB), password-protected printer.

   * Request a print job.

   * Each subsequent job will require retyping the password.

  [Regression Potential]

   * Cherry-pick from upstream (present in Gtk+3.13.8).

   * Minor conflict resolution needed (line numbers changed)

  [Other Info]
   
   * Original bug description:
  i am printing from my ubuntu karmic to a windows box. everytime i print i get 
asked to input username and password to windows box, then the document gets 
printed. there is a remember password checkbox, but it keeps asking me when 
printing the next document.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/445333/+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 1317449] Re: sqlite3 version 3.8.2 breaks digikam

[Chris Samuel]

I applied the patch that b3nmore mentions in comment #126 to sqlite3
from Trusty and built my own packages which I installed but sadly
Digikam still crashes with that applied. :-(

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

Title:
  sqlite3 version 3.8.2 breaks digikam

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in “digikam” package in Ubuntu:
  Fix Released
Status in “sqlite3” package in Ubuntu:
  Fix Released
Status in “digikam” source package in Trusty:
  Confirmed
Status in “sqlite3” source package in Trusty:
  Incomplete
Status in “digikam” source package in Utopic:
  Fix Released
Status in “sqlite3” source package in Utopic:
  Fix Released

Bug description:
  Please update sqlite to a version  3.8.2.

  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. Several reports confirm, that versions  3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

  Workaround:
  Install sqlite3  3.8.2, e.g. you can manually install the corresponding deb 
packages from either utopic or debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/digikam/+bug/1317449/+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 1317449] Re: sqlite3 version 3.8.2 breaks digikam

[Chris Samuel]

I can confirm that Tim Edwards suggestion of installing the sqlite3
packages from Utopic in comment #117 does indeed seem to resolve this
issue.

Before Digikam could crash every few minutes whilst cycling through
photos with just normal viewing.

After Digikam does not crash.

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

Title:
  sqlite3 version 3.8.2 breaks digikam

Status in digiKam - digital photo management:
  Won't Fix
Status in SQLite:
  Won't Fix
Status in “digikam” package in Ubuntu:
  Fix Released
Status in “sqlite3” package in Ubuntu:
  Fix Released
Status in “digikam” source package in Trusty:
  Confirmed
Status in “sqlite3” source package in Trusty:
  Incomplete
Status in “digikam” source package in Utopic:
  Fix Released
Status in “sqlite3” source package in Utopic:
  Fix Released

Bug description:
  Please update sqlite to a version  3.8.2.

  According to https://bugs.kde.org/show_bug.cgi?id=329697 sqlite3 version 
3.8.2 causes crashes in digikam (and possibly other software) in various 
situations. Several reports confirm, that versions  3.8.2 fix the issue.
  I'm using the 3.8.4.3 package from debian testing right now and can't trigger 
crashes anymore.

  Workaround:
  Install sqlite3  3.8.2, e.g. you can manually install the corresponding deb 
packages from either utopic or debian.

To manage notifications about this bug go to:
https://bugs.launchpad.net/digikam/+bug/1317449/+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 794315] Re: lightdm forgets to source /etc/profile and ~/.profile

[Samuel Bronson]

** Bug watch added: Debian Bug tracker #636108
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636108

** Also affects: lightdm (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=636108
   Importance: Unknown
   Status: Unknown

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

Title:
  lightdm forgets to source /etc/profile and ~/.profile

Status in Light Display Manager:
  Fix Released
Status in “lightdm” package in Ubuntu:
  Fix Released
Status in “lightdm” package in Debian:
  Unknown

Bug description:
  Binary package hint: lightdm

  /etc/gdm/Xsession had this code:
# First read /etc/profile and .profile
test -f /etc/profile  . /etc/profile
test -f $HOME/.profile  . $HOME/.profile
# Second read /etc/xprofile and .xprofile for X specific setup
test -f /etc/xprofile  . /etc/xprofile
test -f $HOME/.xprofile  . $HOME/.xprofile
  so that, for example, ~/bin gets added to the path (by the default 
~/.profile), and any user-customized environment setup gets run.

  After switching from gdm to lightdm, this no longer happens.  This is
  going to be a regression now that lightdm is becoming the default
  display manager.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.3.7-0ubuntu1
  ProcVersionSignature: Ubuntu 2.6.39-3.10-generic 2.6.39
  Uname: Linux 2.6.39-3-generic x86_64
  NonfreeKernelModules: openafs
  Architecture: amd64
  Date: Tue Jun  7 19:27:11 2011
  EcryptfsInUse: Yes
  InstallationMedia: Ubuntu 11.04 Natty Narwhal - Alpha amd64 (20101202)
  ProcEnviron:
   LANGUAGE=en_US:en
   PATH=(custom, no user)
   LANG=en_US.utf8
   LC_MESSAGES=en_US.utf8
   SHELL=/bin/bash
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/794315/+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 1357897] Re: Wrong date abbreviating in Date Indicator

[Samuel Dolt]

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

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

Title:
  Wrong date abbreviating in Date Indicator

Status in elementary OS:
  Incomplete
Status in “indicator-datetime” package in Ubuntu:
  New

Bug description:
  In French with local fr_CH (Switzerland), août (august) should not
  be abbreviating. Also, abbreviating must be ended with a dot.

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