[Touch-packages] [Bug 1809174] Re: apt doesn't detect file corruption in /var/lib/apt/lists

[Charles Brian Quinn]

Just saw this on some field units that are iOT type devices and
sometimes get shutdown non-cleanly.  We run apt-update on startup and we
noticed one machine would not update and had no knowledge of any
packages in one of the repos in the sources.list.

We noticed the Packages file has 0 size, and no amount of apt update or
apt-cache clean could fix it besides deleting/removing the corrupt file.

Deleting it resolved the issue:

```
$ ls -lat /var/lib/apt/lists/
total 71252
drwx-- 2 _apt root 4096 Apr 23 16:18 partial
drwxr-xr-x 5 root root 4096 Apr 23 15:40 ..
drwxr-xr-x 4 root root 4096 Apr 22 21:13 .
-rw-r--r-- 1 root root 4342 Apr 22 20:12 
[redacted-package-server]-experimental_dists_focal_InRelease
-rw-r--r-- 1 root root0 Apr 22 20:12 
[redacted-package-server]-experimental_dists_focal_main_binary-amd64_Packages
-rw-r--r-- 1 root root 4362 Jan 27  2023 
[redacted-package-server]-ubuntu-experimental_dists_focal_InRelease
```

Note the 0 file size on the `[redacted-package-
server]-experimental_dists_focal_main_binary-amd64_Packages` file.

During this time, it would not Get any new information from the package
server.  Even with updates pushed to the package server.

After removing the file, it does a `Get` and now can see all the
packages again:

$ sudo mv 
/var/lib/apt/lists/[redacted-package-server]-experimental_dists_focal_main_binary-amd64_Packages
$ sudo apt update
Hit:1 [redacted-server]-experimental focal InRelease
Hit:2 [redacted-server]-ubuntu-experimental focal InRelease
Get:3 [redacted-server]-experimental focal/main amd64 Packages [3524 kB]
Fetched 3524 kB in 6s (571 kB/s)
 
Reading package lists... Done
Building dependency tree   
Reading state information... Done
27 packages can be upgraded. Run 'apt list --upgradable' to see them.
```

Server software is aptly.  apt version is `apt 2.0.6 (amd64)`

Happy to track this down and submit a patch for checking the file size
of 0, or the algorithm as suggested above.

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

Title:
  apt doesn't detect file corruption in /var/lib/apt/lists

Status in apt package in Ubuntu:
  Triaged

Bug description:
  The Problem
  ==

  /var/lib/apt/lists contains the repository index caches or similar;
  I'm not sure what the correct  apt-terminology is.

  I've installed Chrome on my laptop, so I have:

  smacdonald@L247:/var/lib/apt/lists$ dir *goog*
  -rw-r--r-- 1 root root  943 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_Release
  -rw-r--r-- 1 root root  819 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_Release.gpg
  -rw-r--r-- 1 root root 4457 Dec 19 14:02 
dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages

  for example.

  
  dl.google.com_linux_chrome_deb_dists_stable_Release contains checksums for 
the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages file:

  smacdonald@L247:/var/lib/apt/lists$ cat 
dl.google.com_linux_chrome_deb_dists_stable_Release
  Origin: Google LLC
  Label: Google
  Suite: stable
  Codename: stable
  Version: 1.0
  Date: Wed, 19 Dec 2018 18:51:54 UTC
  Architectures: amd64
  Components: main
  Description: Google chrome-linux software repository
  MD5Sum:
   9e0d0ad6a4f5ccf8e3971c32e9bb22d3 4457 main/binary-amd64/Packages
   a17f6de0ef487b82af58ccd91df52d04 1109 main/binary-amd64/Packages.gz
   156e5ea7a0c6bed5973a68a45e546dc9 151 main/binary-amd64/Release
  SHA1:
   4c2cde4f71476d7881262d9a07e33cf4506232a7 4457 main/binary-amd64/Packages
   e002924c9ddfe41ee2033594ec768ed9e4545909 1109 main/binary-amd64/Packages.gz
   0f4348c2d4d7cc1f8e59b5934d87f1ca872f6e34 151 main/binary-amd64/Release
  SHA256:
   fb0e586c2b5ec5afa17965d0bbc6bd46c2071336f75e2b0f0c7f3e7b090a7844 4457 
main/binary-amd64/Packages
   2462cff732765679a56373a7ca9a5b8b029fdb445e707b1aba10d01fbdb853b3 1109 
main/binary-amd64/Packages.gz
   c1e3c9318381862306adcdc4fd4fe2d85be8aa4c4f3dcbb40fce80413f588286 151 
main/binary-amd64/Release

  
  If the dl.google.com_linux_chrome_deb_dists_stable_main_binary-amd64_Packages 
file has become corrupt in the specific manner of being 0 bytes in length, apt 
does not detect this, and the repository is effectively unreachable until one 
of two things occurs: a) the repository has an update causing apt to re-fetch 
the repository information and accidentally fix-by-over-writing the corrupt 0 
byte file, or, b) the user removes the corrupt 0-byte file and does an apt 
update to refetch the repository information.

  
  The Context
  ==

  Our IoT devices run Ubuntu 16.04, and their main storage is eMMC.
  Sometimes there are catastrophic

[Touch-packages] [Bug 2056217] Re: nmcli regression: can't set IPV6 token

[Charles Hedrick]

** Tags added: regression-release

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

Title:
  nmcli regression: can't set IPV6 token

Status in network-manager package in Ubuntu:
  New

Bug description:
  24.04 nightly, downloaded Mar 5.

  network-manager 1.45.90-1ubuntu1

  In network manager, if you try to set ipv6.token, when you save it
  says

  Error: connection verification failed: ipv6.token: only makes sense
  with EUI64 address generation mode

  This is the same as under 22.04. However under 22.04 the solution is
  setipv6.addr-gen-mode eui64 along with the token. In 24.04 when you
  save you get

  Error: Failed to save 'netplan-enp3s0'
  (6effa1b1-280b-3785-9b52-c723b445fb3e) connection: failed to update
  connection: netplan: YAML translation failed: Error in network
  definition: enp3s0: ipv6-address-generation and ipv6-address-token are
  mutually exclusive

  There doesn't seem to be any combination involving the token that
  works.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Mar  5 14:14:01 2024
  InstallationDate: Installed on 2024-03-05 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240305)
  IpRoute:
   default via 128.6.60.1 dev enp3s0 proto dhcp src 128.6.60.252 metric 100 
   128.6.60.0/24 dev enp3s0 proto kernel scope link src 128.6.60.252 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE   IP4-CONNECTIVITY  IP6-CONNECTIVITY 
 DBUS-PATH  CONNECTION  CON-UUID
  CON-PATH   
   enp3s0  ethernet  connected   full  limited  
 /org/freedesktop/NetworkManager/Devices/2  netplan-enp3s0  
6effa1b1-280b-3785-9b52-c723b445fb3e  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   lo  loopback  connected (externally)  unknown   unknown  
 /org/freedesktop/NetworkManager/Devices/1  lo  
b04a6583-06fa-4685-bbd9-05171997cf93  
/org/freedesktop/NetworkManager/ActiveConnection/1
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.45.90  connected  started  full  enabled missing  
enabled  missing  enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/2056217/+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 2056217] [NEW] nmcli regression: can't set IPV6 token

[Charles Hedrick]

Public bug reported:

24.04 nightly, downloaded Mar 5.

network-manager 1.45.90-1ubuntu1

In network manager, if you try to set ipv6.token, when you save it says

Error: connection verification failed: ipv6.token: only makes sense with
EUI64 address generation mode

This is the same as under 22.04. However under 22.04 the solution is
setipv6.addr-gen-mode eui64 along with the token. In 24.04 when you save
you get

Error: Failed to save 'netplan-enp3s0'
(6effa1b1-280b-3785-9b52-c723b445fb3e) connection: failed to update
connection: netplan: YAML translation failed: Error in network
definition: enp3s0: ipv6-address-generation and ipv6-address-token are
mutually exclusive

There doesn't seem to be any combination involving the token that works.

ProblemType: Bug
DistroRelease: Ubuntu 24.04
Package: network-manager 1.45.90-1ubuntu1
ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
Uname: Linux 6.8.0-11-generic x86_64
ApportVersion: 2.28.0-0ubuntu1
Architecture: amd64
CRDA: N/A
CasperMD5CheckResult: pass
Date: Tue Mar  5 14:14:01 2024
InstallationDate: Installed on 2024-03-05 (0 days ago)
InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240305)
IpRoute:
 default via 128.6.60.1 dev enp3s0 proto dhcp src 128.6.60.252 metric 100 
 128.6.60.0/24 dev enp3s0 proto kernel scope link src 128.6.60.252 metric 100
IwConfig:
 lono wireless extensions.
 
 enp3s0no wireless extensions.
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=true
RfKill:
 
SourcePackage: network-manager
UpgradeStatus: No upgrade log present (probably fresh install)
nmcli-dev:
 DEVICE  TYPE  STATE   IP4-CONNECTIVITY  IP6-CONNECTIVITY  
DBUS-PATH  CONNECTION  CON-UUID 
 CON-PATH   
 enp3s0  ethernet  connected   full  limited   
/org/freedesktop/NetworkManager/Devices/2  netplan-enp3s0  
6effa1b1-280b-3785-9b52-c723b445fb3e  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 lo  loopback  connected (externally)  unknown   unknown   
/org/freedesktop/NetworkManager/Devices/1  lo  
b04a6583-06fa-4685-bbd9-05171997cf93  
/org/freedesktop/NetworkManager/ActiveConnection/1
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN
 running  1.45.90  connected  started  full  enabled missing  
enabled  missing  enabled

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


** Tags: amd64 apport-bug noble

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

Title:
  nmcli regression: can't set IPV6 token

Status in network-manager package in Ubuntu:
  New

Bug description:
  24.04 nightly, downloaded Mar 5.

  network-manager 1.45.90-1ubuntu1

  In network manager, if you try to set ipv6.token, when you save it
  says

  Error: connection verification failed: ipv6.token: only makes sense
  with EUI64 address generation mode

  This is the same as under 22.04. However under 22.04 the solution is
  setipv6.addr-gen-mode eui64 along with the token. In 24.04 when you
  save you get

  Error: Failed to save 'netplan-enp3s0'
  (6effa1b1-280b-3785-9b52-c723b445fb3e) connection: failed to update
  connection: netplan: YAML translation failed: Error in network
  definition: enp3s0: ipv6-address-generation and ipv6-address-token are
  mutually exclusive

  There doesn't seem to be any combination involving the token that
  works.

  ProblemType: Bug
  DistroRelease: Ubuntu 24.04
  Package: network-manager 1.45.90-1ubuntu1
  ProcVersionSignature: Ubuntu 6.8.0-11.11-generic 6.8.0-rc4
  Uname: Linux 6.8.0-11-generic x86_64
  ApportVersion: 2.28.0-0ubuntu1
  Architecture: amd64
  CRDA: N/A
  CasperMD5CheckResult: pass
  Date: Tue Mar  5 14:14:01 2024
  InstallationDate: Installed on 2024-03-05 (0 days ago)
  InstallationMedia: Ubuntu 24.04 LTS "Noble Numbat" - Daily amd64 (20240305)
  IpRoute:
   default via 128.6.60.1 dev enp3s0 proto dhcp src 128.6.60.252 metric 100 
   128.6.60.0/24 dev enp3s0 proto kernel scope link src 128.6.60.252 metric 100
  IwConfig:
   lono wireless extensions.
   
   enp3s0no wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE   IP4-CONNECTIVITY  IP6-CONNECTIVITY 
 DBUS-PATH  CONNECTION  CON-UUID
  CON-PATH   
   enp3s0  ethernet  connected   full  limited  
 /org/fre

[Touch-packages] [Bug 2040019] [NEW] Bash environment gets corrupted

[Charles Evans]

Public bug reported:

bash 5.1-6ubuntu1 (jammy)
After loading about 1000 aliases totaling 50kB
Setting 200 vars totaling 20kB (half from default profile)
And 1200 functions totaling 400kB (~100/72kB default completions) 
After running the occasional basic (but lengthy) scripts with no recursion, 
runtimes under 1 minute, all under 1 second CPU time in bash,
10-20 times a day for less than a month,

bash starts losing functions and variables and aliases.

Nothing in dmesg or syslog
System is otherwise stable:
-Memtest runs multiple passes ok
-Several GB of apt updates all verify no errors
-Checkrestart did not show any copies of bash needing restarts
-no suspends, no remote shell
-weekly apt updates run in this bash shell

kernel 6.2.0-32 generic
libc6 2.35-0ubuntu3.4

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

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

Title:
  Bash environment gets corrupted

Status in bash package in Ubuntu:
  New

Bug description:
  bash 5.1-6ubuntu1 (jammy)
  After loading about 1000 aliases totaling 50kB
  Setting 200 vars totaling 20kB (half from default profile)
  And 1200 functions totaling 400kB (~100/72kB default completions) 
  After running the occasional basic (but lengthy) scripts with no recursion, 
runtimes under 1 minute, all under 1 second CPU time in bash,
  10-20 times a day for less than a month,

  bash starts losing functions and variables and aliases.

  Nothing in dmesg or syslog
  System is otherwise stable:
  -Memtest runs multiple passes ok
  -Several GB of apt updates all verify no errors
  -Checkrestart did not show any copies of bash needing restarts
  -no suspends, no remote shell
  -weekly apt updates run in this bash shell

  kernel 6.2.0-32 generic
  libc6 2.35-0ubuntu3.4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/2040019/+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 2038590] [NEW] Wget --rejected-log=file never logs anything

[Charles Evans]

Public bug reported:

Wget jammy 1.21.2-2ubuntu1
404 errors etc. are not written to log file
File is never created.

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

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

Title:
  Wget --rejected-log=file  never logs anything

Status in wget package in Ubuntu:
  New

Bug description:
  Wget jammy 1.21.2-2ubuntu1
  404 errors etc. are not written to log file
  File is never created.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/wget/+bug/2038590/+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 1283309] Re: bash built-in read timeout (-t) doesn't work

[Charles Evans]

System time consistently falls behind, so hwclock -s is advancing the
system clock.

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

Title:
  bash built-in read timeout (-t) doesn't work

Status in bash package in Ubuntu:
  Expired

Bug description:
  This should timeout after 2 seconds (based on bash man page) but it doesn't:
  #read -t 2 test
  (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..)

  bash --version:
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)

  Installed bash package version:
  4.2-2ubuntu2.1

  $ lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1283309] Re: bash built-in read timeout (-t) doesn't work

[Charles Evans]

Hwclock -s is run on the system at least weekly as system time drifts.
Adjtime is not installed.

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

Title:
  bash built-in read timeout (-t) doesn't work

Status in bash package in Ubuntu:
  Expired

Bug description:
  This should timeout after 2 seconds (based on bash man page) but it doesn't:
  #read -t 2 test
  (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..)

  bash --version:
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)

  Installed bash package version:
  4.2-2ubuntu2.1

  $ lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1283309] Re: bash built-in read timeout (-t) doesn't work

[Charles Evans]

With multiple bash scripts running for over a month,
I now have random read fails at least once an hour PER SCRIPT. 
Restarting the script did not help.
Restarting bash helps for a while.

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

Title:
  bash built-in read timeout (-t) doesn't work

Status in bash package in Ubuntu:
  Expired

Bug description:
  This should timeout after 2 seconds (based on bash man page) but it doesn't:
  #read -t 2 test
  (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..)

  bash --version:
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)

  Installed bash package version:
  4.2-2ubuntu2.1

  $ lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1817052] Re: bug with ls command, doesn't list only a single directory.

[Charles Evans]

Did you mean ls -1?
ls -l is long listing,
does not start with filename,
Example can't work as written

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

Title:
  bug with ls command, doesn't list only a single directory.

Status in bash package in Ubuntu:
  New

Bug description:
  If is the only one which starts with an specified letter, won't show
  it with grep. Example: if there is only a directory starting with 'w',
  ls -l | grep ^[w] won't show it. With ls -l w* happens the same
  problem. I think you should check.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bash 4.4.18-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18
  Uname: Linux 4.15.0-43-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Feb 21 12:37:04 2019
  ExecutablePath: /bin/bash
  InstallationDate: Installed on 2019-01-13 (38 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  ProcEnviron:
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
  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/1817052/+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 1283309] Re: bash built-in read timeout (-t) doesn't work

[Charles Evans]

Also failing in 
Bash 5.0.6ubuntu1.2
In focal 20.04.5 LTS

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

Title:
  bash built-in read timeout (-t) doesn't work

Status in bash package in Ubuntu:
  Expired

Bug description:
  This should timeout after 2 seconds (based on bash man page) but it doesn't:
  #read -t 2 test
  (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..)

  bash --version:
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)

  Installed bash package version:
  4.2-2ubuntu2.1

  $ lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1283309] Re: bash built-in read timeout (-t) doesn't work

[Charles Evans]

While date
Do
Read -t 60 x
Done

In another terminal, adjust the system clock by a few seconds
Repeat hourly until the read hangs.
Sometimes it hangs immediately after setting clock, 
Sometimes it runs for hours.
I have seen hangs semi regularly for the last 5, maybe 10+ years. 
It often hangs with no apparent system clock changes,
But more often when a cron job runs ntp 
No VM involved. 
Hangs on multiple AMD systems.

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

Title:
  bash built-in read timeout (-t) doesn't work

Status in bash package in Ubuntu:
  Incomplete

Bug description:
  This should timeout after 2 seconds (based on bash man page) but it doesn't:
  #read -t 2 test
  (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..)

  bash --version:
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)

  Installed bash package version:
  4.2-2ubuntu2.1

  $ lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1283309] Re: bash built-in read timeout (-t) doesn't work

[Charles Evans]

Still fails randomly 
@ jammy bash 5.1-6ubuntu1
Read -t 60 failure can often be triggered by changing the system clock 
slightly. It often fails if waiting when ntp runs.

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

Title:
  bash built-in read timeout (-t) doesn't work

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  This should timeout after 2 seconds (based on bash man page) but it doesn't:
  #read -t 2 test
  (waits infinitely, only terminates after pressing [enter] or ctrl-C, etc..)

  bash --version:
  GNU bash, version 4.2.25(1)-release (x86_64-pc-linux-gnu)

  Installed bash package version:
  4.2-2ubuntu2.1

  $ lsb_release -rd
  Description:  Ubuntu 12.04.4 LTS
  Release:  12.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bash/+bug/1283309/+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 1988548] Re: Missing fix for CVE-2022-37434 in zlib1g in focal and jammy

[Charles Evans]

I manually installed the fixed zlib from kinetic.
So far it is working.
Could someone put it in proposed for focal and jammy so it will be on the 
livecd's?

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

Title:
  Missing fix for CVE-2022-37434 in zlib1g in focal and jammy

Status in zlib package in Ubuntu:
  Confirmed

Bug description:
  There is a crictical security issue with zlib tracked here [1]

  The newest version in bionic [2] already has a security patch for it
  but the one in the focal [3] (and jammy) does not. As can be seen from
  their respective changelogs in the right hand side panel.

  Since zlib is loaded by lots of software, e.g. the apache weg server,
  this could be a problem. It seems that focal, jammy and bionic use the
  same base zlib version (1.2.11), so maybe the patch there could be
  recycled?

  I was asked to create a bug here after asking it as question here [4].
  Thank you very much for your hard work!

  [1] CVE: https://nvd.nist.gov/vuln/detail/CVE-2022-37434
  [2] Bionic Package: https://packages.ubuntu.com/bionic/zlib1g
  [3] Focal Package: https://packages.ubuntu.com/focal/zlib1g
  [4] Original Question: 
https://answers.launchpad.net/ubuntu/+source/zlib/+question/703010

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zlib/+bug/1988548/+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 1970050] Re: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all because of upgrade from 20.04 LTS to 22.04

[Charles Wright]

I have an Intel Nuc, Product Name: D34010WYK, i3-4010U, its hooked up a
Samsung TV via hdmi.   The sound defaults to HDMI/DisplayPort - Built-in
Audio, Digital Stereo (HDMI) Output but that doesn't work.   If I flip
it to Digital Surround it works but since the TV only has a left/right
speaker I would think stereo should work and doesn't.   I confirmed the
issue is the same if I boot off the desktop ISO and "Try Ubuntu", since
I upgraded my system I thought maybe something wasn't right because of
that.

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

Title:
  [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
  because of upgrade from 20.04 LTS to 22.04

Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  After upgrading today from 20.04 LTS to 22.04
  HDMI Audio does not work at all.
  Audio from speakers from a headphone jack works fine.

  ProblemType: Bug
  DistroRelease: Ubuntu 22.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu7
  ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
  Uname: Linux 5.15.0-25-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu82
  Architecture: amd64
  CasperMD5CheckResult: unknown
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 23 21:13:23 2022
  InstallationDate: Installed on 2020-04-24 (729 days ago)
  InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 
(20200203.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:HDMI failed
  Symptom_Card: Built-in Audio - HDA Intel HDMI
  Symptom_Jack: Digital Out, HDMI
  Symptom_Type: No sound at all
  Title: [H97M-HD3, Intel Haswell HDMI, Digital Out, HDMI] No sound at all
  UpgradeStatus: Upgraded to jammy on 2022-04-23 (0 days ago)
  dmi.bios.date: 04/21/2015
  dmi.bios.release: 4.6
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: F7
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H97M-HD3
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF7:bd04/21/2015:br4.6:svnGigabyteTechnologyCo.,Ltd.:pnH97M-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH97M-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:skuTobefilledbyO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H97M-HD3
  dmi.product.sku: To be filled by O.E.M.
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1970050/+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 1609750]

[Mutatina Charles Mwombeki]

solved the bug already i cleared some things and made an update

On Sun, Sep 26, 2021, 05:40 ian <1609...@bugs.launchpad.net> wrote:

> Any update on this?  Having issues with sound working for some time,
> than suddenly stopping with a buzzing sound.  Will attempt to modify
> patch for most recent kernel, but my understanding is the kernel should
> already be patched. Works fine on galliumos, but not with any other
> distro or most recent kernel
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1803810).
> https://bugs.launchpad.net/bugs/1609750
>
> Title:
>   Audio not working on Acer Chromebook R11
>
> Status in linux:
>   Confirmed
> Status in linux package in Ubuntu:
>   In Progress
> Status in pulseaudio package in Ubuntu:
>   Invalid
>
> Bug description:
>   Audio is not working at all on Acer Chromebook R11 (codename CYAN).
>   It's a Intel Braswell platform. snd_hda_intel messages seem normal,
>   but Pulseaudio does not detect sound hardware.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: pulseaudio 1:9.0-1.1ubuntu1
>   ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
>   Uname: Linux 4.4.0-33-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu2
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p',
> '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: Unity
>   Date: Thu Aug  4 14:12:03 2016
>   InstallationDate: Installed on 2016-07-22 (13 days ago)
>   InstallationMedia:
>
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   SourcePackage: pulseaudio
>   Symptom: audio
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/20/2016
>   dmi.bios.vendor: coreboot
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: GOOGLE
>   dmi.modalias:
> dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
>   dmi.product.name: Cyan
>   dmi.product.version: 1.0
>   dmi.sys.vendor: GOOGLE
>   ---
>   ApportVersion: 2.20.3-0ubuntu2
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p',
> '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: Unity
>   DistroRelease: Ubuntu 16.10
>   HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
>   InstallationDate: Installed on 2016-07-22 (13 days ago)
>   InstallationMedia:
>
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 8087:0a2a Intel Corp.
>Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: GOOGLE Cyan
>   Package: linux-image-4.4.0-33-generic 4.4.0-33.52
>   PackageArchitecture: amd64
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic
> root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-4.4.0-33-generic N/A
>linux-backports-modules-4.4.0-33-generic  N/A
>linux-firmware1.159
>   Tags:  yakkety
>   Uname: Linux 4.4.0-33-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 05/20/2016
>   dmi.bios.vendor: coreboot
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: GOOGLE
>   dmi.modalias:
> dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
>   dmi.product.name: Cyan
>   dmi.product.version: 1.0
>   dmi.sys.vendor: GOOGLE
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions
>
>

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

Title:
  Audio not working on Acer Chromebook R11

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 

[Touch-packages] [Bug 1941938] [NEW] systemd trying to unmount non-existent file system

[Charles Meo]

Public bug reported:

This output is copied from here: https://github.com/systemd/systemd/issues/20516
because I have not been able to capture the error messages. However what I am 
seeing is identical.

sd-umoun[2406]: Failed to unmount /oldroot: Device or resource busy
 sd-umoun[2407]: Failed to unmount /oldroot/dev/pts: Device or resource busy
 sd-umoun[2408]: Failed to unmount /oldroot/dev: Device or resource busy
 shutdown[1]: Failed to finalize  file systems, ignoring

This has happened consistently since I upgraded to Ubuntu 20.04 two
weeks ago, and is really annoying. Is there an actual problem or is it
just noise that can be safely ignored?

The only other thing referencing oldroot in its config was snap, which I
have completely uninstalled to isolate the problem.

/lib/systemd/systemd-shutdown also contains this string:
# strings systemd-shutdown |grep old
/oldroot
sigprocmask(SIG_BLOCK, &mask, &oldmask) == 0
sigprocmask(SIG_SETMASK, &oldmask, NULL) == 0

I have never had an /oldroot mount and there isn't one now. I gather it
is something the upgrade process might create, or it could perhaps be
something broken in finalrd.

Bin Li, who posted the above error to the systemd bug portal, got short
shrift there and was told to contact the distro. So I am, as my version
of systemd is 245, same as his. This problem is 100% repeateable and I
see it every time I shutdown or restart.

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: systemd 245.4-4ubuntu3.11
ProcVersionSignature: Ubuntu 5.4.0-81.91-generic 5.4.128
Uname: Linux 5.4.0-81-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: Unity:Unity7:ubuntu
Date: Sat Aug 28 14:28:03 2021
InstallationDate: Installed on 2017-05-26 (1554 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 5986:0708 Acer, Inc Integrated Camera
 Bus 001 Device 002: ID 046d:c077 Logitech, Inc. M105 Optical Mouse
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Lsusb-t:
 /:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
 /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M
 |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
 |__ Port 7: Dev 4, If 0, Class=Video, Driver=uvcvideo, 480M
 |__ Port 7: Dev 4, If 1, Class=Video, Driver=uvcvideo, 480M
MachineType: LENOVO 20EVCTO1WW
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-81-generic 
root=UUID=3be3-50c9-41cc-94b5-eab06cff1d17 ro quiet splash
SourcePackage: systemd
UpgradeStatus: Upgraded to focal on 2021-08-05 (22 days ago)
dmi.bios.date: 12/01/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R00ET49W (1.24 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20EVCTO1WW
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40709 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR00ET49W(1.24):bd12/01/2016:svnLENOVO:pn20EVCTO1WW:pvrThinkPadE560:rvnLENOVO:rn20EVCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad E560
dmi.product.name: 20EVCTO1WW
dmi.product.sku: LENOVO_MT_20EV_BU_Think_FM_ThinkPad E560
dmi.product.version: ThinkPad E560
dmi.sys.vendor: LENOVO

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

Title:
  systemd trying to unmount non-existent file system

Status in systemd package in Ubuntu:
  New

Bug description:
  This output is copied from here: 
https://github.com/systemd/systemd/issues/20516
  because I have not been able to capture the error messages. However what I am 
seeing is identical.

  sd-umoun[2406]: Failed to unmount /oldroot: Device or resource busy
   sd-umoun[2407]: Failed to unmount /oldroot/dev/pts: Device or resource busy
   sd-umoun[2408]: Failed to unmount /oldroot/dev: Device or resource busy
   shutdown[1]: Failed to finalize  file systems, ignoring

  This has happened consistently since I upgraded to Ubuntu 20.04 two
  weeks ago, and is really annoying. Is there an actual problem or is it
  just noise that can be safely ignored?

  The only other thing referencing oldroot in its config was snap, which
  I have completely uninstalled to isolate the problem.

  /lib/systemd/systemd-shutdown also contains this string:
  # strings systemd-shutdown |grep old
  /oldroot
  sigprocmask(SIG_BLOCK, &mask, &oldmask) == 0
  sigprocmask(SIG_SETMASK, &oldmask, NULL) == 0

  I have never had an /oldroot mount and there isn't one now. I gather
  it is something the upgrade process might create, or it could perhaps
  be something broken in finalrd.

  Bin Li

[Touch-packages] [Bug 1920047] [NEW] sanlock global lock creation fail

[Charles KOPROWSKI]

Public bug reported:

Hello,

Running Ubuntu server 20.04, I cannot create a shared VG using sanlock :

# vgcreate --shared foo /dev/mapper/vol
  Enabling sanlock global lock
  Skipping global lock: lockspace not found or started
  Logical volume "lvmlock" created.
  VG foo init failed: -28
  Failed to initialize lock args for lock type sanlock
  Volume group "foo" successfully removed

Messages in /var/log/syslog

lvmlockd[446807]: 1616089866 WARNING: mixed block sizes physical 4096 logical 
512 (using 4096) for /dev/mapper/foo-lvmlock
lvmlockd[446807]: 1616089866 S lvm_foo init_vg_san write_resource gl error -28 
/dev/mapper/foo-lvmlock

# lsb_release -rd
Description:Ubuntu 20.04.2 LTS
Release:20.04

# dpkg -l | grep lvm
ii  liblvm2cmd2.03:amd64 2.03.07-1ubuntu1  
amd64LVM2 command library
ii  lvm2 2.03.07-1ubuntu1  
amd64Linux Logical Volume Manager
ii  lvm2-lockd   2.03.07-1ubuntu1  
amd64LVM locking daemon

A similar bug report from RHEL8 :
https://bugzilla.redhat.com/show_bug.cgi?id=1833837

Bug has been fixed upstream :
https://sourceware.org/git/?p=lvm2.git;a=commit;h=2d1fe38d84d499011d13ae1ea11535398528fc87

It seems to be included in version 2.03.10 :
https://sourceware.org/git/?p=lvm2.git;a=shortlog;h=refs/tags/v2_03_10

How can we get this patch included in Ubuntu 20.04 ?

King Regards,

Charles

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

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

Title:
  sanlock global lock creation fail

Status in lvm2 package in Ubuntu:
  New

Bug description:
  Hello,

  Running Ubuntu server 20.04, I cannot create a shared VG using sanlock
  :

  # vgcreate --shared foo /dev/mapper/vol
Enabling sanlock global lock
Skipping global lock: lockspace not found or started
Logical volume "lvmlock" created.
VG foo init failed: -28
Failed to initialize lock args for lock type sanlock
Volume group "foo" successfully removed

  Messages in /var/log/syslog

  lvmlockd[446807]: 1616089866 WARNING: mixed block sizes physical 4096 logical 
512 (using 4096) for /dev/mapper/foo-lvmlock
  lvmlockd[446807]: 1616089866 S lvm_foo init_vg_san write_resource gl error 
-28 /dev/mapper/foo-lvmlock

  # lsb_release -rd
  Description:Ubuntu 20.04.2 LTS
  Release:20.04

  # dpkg -l | grep lvm
  ii  liblvm2cmd2.03:amd64 2.03.07-1ubuntu1 
 amd64LVM2 command library
  ii  lvm2 2.03.07-1ubuntu1 
 amd64Linux Logical Volume Manager
  ii  lvm2-lockd   2.03.07-1ubuntu1 
 amd64LVM locking daemon

  A similar bug report from RHEL8 :
  https://bugzilla.redhat.com/show_bug.cgi?id=1833837

  Bug has been fixed upstream :
  
https://sourceware.org/git/?p=lvm2.git;a=commit;h=2d1fe38d84d499011d13ae1ea11535398528fc87

  It seems to be included in version 2.03.10 :
  https://sourceware.org/git/?p=lvm2.git;a=shortlog;h=refs/tags/v2_03_10

  How can we get this patch included in Ubuntu 20.04 ?

  King Regards,

  Charles

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/1920047/+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 1903323] [NEW] trying to get apps to show on gnome store returns error code

[charles]

Public bug reported:

when I try the sudo apt-get update command to fix apps not showing in
the gnome-software center it produces the following error

E: The repository 'http://ppa.launchpad.net/ehoover/compholio/ubuntu
hirsute Release' does not have a Release file.

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

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

Title:
  trying to get apps to show on gnome store returns error code

Status in apt package in Ubuntu:
  New

Bug description:
  when I try the sudo apt-get update command to fix apps not showing in
  the gnome-software center it produces the following error

  E: The repository 'http://ppa.launchpad.net/ehoover/compholio/ubuntu
  hirsute Release' does not have a Release file.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apt/+bug/1903323/+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 1889021] [NEW] package python3-software-properties 0.98.9 failed to install/upgrade: dpkg-deb --fsys-tarfile subprocess returned error exit status 2

[Charles Hodge]

Public bug reported:

Check if you are using third party repositories. If so disable them, since they 
are a common source of problems.
Furthermore run the following command in a Terminal: apt-get install -f
Transaction failed: The package system is broken
 The following packages have unmet dependencies:

software-properties-gtk: Depends: gir1.2-goa-1.0 (>= 3.27.92-1ubuntu1) but 
3.36.0-1ubuntu1 is installed
 Depends: gir1.2-snapd-1 (>= 1.42) but 1.57-0ubuntu3 is 
installed
 Depends: python3-software-properties (= 0.98.9.1) but 
0.98.9 is installed
 Depends: ubuntu-drivers-common (>= 1:0.2.75) but 
1:0.8.1.1 is installed
 Depends: python3:any but it is a virtual package

ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: python3-software-properties 0.98.9
ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
Uname: Linux 5.4.0-42-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu27.4
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Jul 26 21:03:14 2020
ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
InstallationDate: Installed on 2020-07-27 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
PackageArchitecture: all
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
PythonDetails: N/A
RelatedPackageVersions:
 dpkg 1.19.7ubuntu3
 apt  2.0.2ubuntu0.1
SourcePackage: software-properties
Title: package python3-software-properties 0.98.9 failed to install/upgrade: 
dpkg-deb --fsys-tarfile subprocess returned error exit status 2
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/1889021

Title:
  package python3-software-properties 0.98.9 failed to install/upgrade:
  dpkg-deb --fsys-tarfile subprocess returned error exit status 2

Status in software-properties package in Ubuntu:
  New

Bug description:
  Check if you are using third party repositories. If so disable them, since 
they are a common source of problems.
  Furthermore run the following command in a Terminal: apt-get install -f
  Transaction failed: The package system is broken
   The following packages have unmet dependencies:

  software-properties-gtk: Depends: gir1.2-goa-1.0 (>= 3.27.92-1ubuntu1) but 
3.36.0-1ubuntu1 is installed
   Depends: gir1.2-snapd-1 (>= 1.42) but 1.57-0ubuntu3 
is installed
   Depends: python3-software-properties (= 0.98.9.1) 
but 0.98.9 is installed
   Depends: ubuntu-drivers-common (>= 1:0.2.75) but 
1:0.8.1.1 is installed
   Depends: python3:any but it is a virtual package

  ProblemType: Package
  DistroRelease: Ubuntu 20.04
  Package: python3-software-properties 0.98.9
  ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44
  Uname: Linux 5.4.0-42-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27.4
  Architecture: amd64
  CasperMD5CheckResult: skip
  Date: Sun Jul 26 21:03:14 2020
  ErrorMessage: dpkg-deb --fsys-tarfile subprocess returned error exit status 2
  InstallationDate: Installed on 2020-07-27 (0 days ago)
  InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 
3.8.2-0ubuntu2
  PythonDetails: N/A
  RelatedPackageVersions:
   dpkg 1.19.7ubuntu3
   apt  2.0.2ubuntu0.1
  SourcePackage: software-properties
  Title: package python3-software-properties 0.98.9 failed to install/upgrade: 
dpkg-deb --fsys-tarfile 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/software-properties/+bug/1889021/+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 1884536] Re: Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04

[Charles Brittain]

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

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

Title:
  Multiple-monitor Set Up Makes Mouse-pointer Jump About in 20.04

Status in gpm package in Ubuntu:
  New

Bug description:
  I have relatively recently loaded Ubuntu 20.04 to dual-boot on a
  Packard Bell with Windows 10 Home 64-bit already installed. The mouse-
  pointer moves and clicks perfectly when the PC has a single-monitor.
  However, for work as a developer, I should like to use a dual-monitor
  setup.

  The problem I have is, if I plug in to the PC tower a second monitor
  and follow the steps to Connect Another Monitor To My Computer
  (https://help.ubuntu.com/stable/ubuntu-help/display-dual-
  monitors.html), and after I confirm "join Display", the mouse-pointer
  jumps about and a second stationary mouse-pointer appears in the
  bottom right of my primary screen. This behaviour stops immediately I
  confirm "Single Display", but now the second screen is now turned
  blank.

  $ xinput
  ⎡ Virtual core pointer  id=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
  ⎜   ↳ USB Wired Keyboard Consumer Control   id=12   [slave  pointer  (2)]
  ⎜   ↳ PixArt USB Optical Mouse  id=13   [slave  pointer  (2)]
  ⎣ Virtual core keyboard id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
  ↳ Power Button  id=6[slave  keyboard (3)]
  ↳ Video Bus id=7[slave  keyboard (3)]
  ↳ Power Button  id=8[slave  keyboard (3)]
  ↳ Sleep Button  id=9[slave  keyboard (3)]
  ↳ USB Wired Keyboardid=10   [slave  keyboard (3)]
  ↳ USB Wired Keyboard System Control id=11   [slave  keyboard (3)]
  ↳ USB Wired Keyboard Consumer Control   id=14   [slave  keyboard (3)]

  $ sudo dmidecode -t 1
  # dmidecode 3.2
  Getting SMBIOS data from sysfs.
  SMBIOS 2.8 present.

  Handle 0x0001, DMI type 1, 27 bytes
  System Information
  Manufacturer: Packard Bell
  Product Name: iMedia S2984
  Version: 
  Serial Number: DTU96EK00360103D0F3000
  UUID: 84edd4a2-b457-11e5-9b1f-98eecb2ca5dd
  Wake-up Type: Power Switch
  SKU Number:  
  Family: Packard Bell Desktop

  $ lsb_release -a; uname -a; lsusb
  No LSB modules are available.
  Distributor ID: Ubuntu
  Description:Ubuntu 20.04 LTS
  Release:20.04
  Codename:   focal
  Linux charlesb2t-iMedia-S2984 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 
18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 001 Device 004: ID 0bda:0153 Realtek Semiconductor Corp. 3-in-1 
(SD/SDHC/SDXC) Card Reader
  Bus 001 Device 003: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse
  Bus 001 Device 002: ID 0461:4e6f Primax Electronics, Ltd Acer Wired Keyboard 
Model KBAY211
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  I am reporting this as a bug because I am unable to fix it and I have
  asked around, but no joy. I do need a dual-monitor set p for work.
  Currently, I can use Windows10 with dual-monitors, on the same
  machine, without a glitch.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gpm/+bug/1884536/+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 1880775] [NEW] HP Envy 4524 All In One - Device communication error - code 5012;

[Charles Vine]

Public bug reported:

Situation:
Ubuntu 20.04 LTS after fresh install, NOT upgrade on desktop (had 16.04 LTS 
before). Printer was attached during fresh install of 20.04 LTS and internet 
connection, third party downloads ticked.

Bug description:
USB connected HP Envy 4524 All In One is recognized multiple times as printer 
but does not print, scans occasionally but unreliable in getting recognized by 
20.04 LTS.

Additional Information:
HP Envy 4524 All In One works flawless with Ubuntu 18.04 LTS on Laptop. Worked 
flawless with Ubuntu 16.04 LTS on the desktop used above.

Steps taken so far:
De-installed/purged hplip 3.20.3 as sudo hp-check -i showed multiple errors and 
missing dependencies. 
Installed hplip 3.20.5 from the HPLIP site and ran the script which resulted in 
compiling and installing the printer with nil errors running sudo hp-check -i. 
However, after reboot Device communication error - code 5012 re-occured 
(current hp-check log attached). 


 Log ___

administrator@office-server:~$ sudo hp-check -i
[sudo] password for administrator: 
/usr/bin/hp-check:685: SyntaxWarning: "is not" with a literal. Did you mean 
"!="?
  if 'getfacl' not in g and '' is not g and 'file' not in g:
Saving output in log file: /home/administrator/hp-check.log

HP Linux Imaging and Printing System (ver. 3.20.5)
Dependency/Version Check Utility ver. 15.1

Copyright (c) 2001-18 HP Development Company, LP
This software comes with ABSOLUTELY NO WARRANTY.
This is free software, and you are welcome to distribute it
under certain conditions. See COPYING file for more details.

Note: hp-check can be run in three modes:
1. Compile-time check mode (-c or --compile): Use this mode before compiling 
the HPLIP supplied tarball (.tar.gz or .run) to determine if the proper 
dependencies are installed to
successfully compile HPLIP. 

  
2. Run-time check mode (-r or --run): Use this mode to determine if a distro 
supplied package (.deb, .rpm, etc) or an already built HPLIP supplied tarball 
has the proper dependencies
installed to successfully run.  

  
3. Both compile- and run-time check mode (-b or --both) (Default): This mode 
will check both of the above cases (both compile- and run-time dependencies).   
 

Check types:

  
a. EXTERNALDEP - External Dependencies  

  
b. GENERALDEP - General Dependencies (required both at compile and run time)

  
c. COMPILEDEP - Compile time Dependencies   

  
d. [All are run-time checks]

  
PYEXT SCANCONF QUEUES PERMISSION

  

Status Types:
OK
MISSING   - Missing Dependency or Permission or Plug-in
INCOMPAT  - Incompatible dependency-version or Plugin-version

|Gtk-Message: 09:51:18.656: Failed to load module "canberra-gtk-module"
 
---
| SYSTEM INFO |
---

 Kernel: 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 GNU/Linux
 Host: office-server
 Proc: 5.4.0-31-generic #35-Ubuntu SMP Thu May 7 20:20:34 UTC 2020 GNU/Linux
 Distribution: 12 20.04
 Bitness: 64 bit


---
| HPLIP CONFIGURATION |
---

HPLIP-Version: HPLIP 3.20.5
HPLIP-Home: /usr/share/hplip
HPLIP-Installation: Auto installation is supported for ubuntu distro  20.04 
version 

Current contents of '/etc/hp/hplip.conf' file:
# hplip.conf.  Generated from hplip.conf.in by configure.

[hplip]
version=3.20.5

[dirs]
home=/usr/share/hplip
run=/var/run
ppd=/usr/share/ppd/HP
ppdbase=/usr/share/ppd
doc=/usr/share/doc/hplip-3.20.5
html=/usr/share/doc/hplip-3.20.5
icon=/usr/share/applications
cupsbackend=/usr/lib/cups/backend
cupsfilter=/usr/lib/cups/filter
drv=/usr/share/cups/drv/hp
bin=/usr/bin
apparmor=/etc/apparmor.d
# Following values are determined at configure time and cannot be changed.
[configure]
network-b

[Touch-packages] [Bug 1878617] Re: Apple pages file type should be added to MIME types

[Charles Plessy]

Hello,

You can add `application/vnd.apple.pages pages` in `/etc/mime.types` on
your system, and I will do it in a future update of the `mime-support`
package, but it will not effect the output of the `file` command, which
uses a different database.

You can open a bug on the `file` package to request it, but please have
a look if you can at <https://github.com/file/file/tree/master/magic>
before: as you will see, unless you can provide a “magic number” for
that format (a proprietary format from a proprietary software, if I may
comment), it may not be possible to detect it.

You can also have a look at the `shared-mime-info` package for another
way to associate the `.pages` file suffix to the
`application/vnd.apple.pages` media type.

Have a nice day,

Charles Plessy

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

Title:
  Apple pages file type should be added to MIME types

Status in mime-support package in Ubuntu:
  New

Bug description:
  LibreOffice can open .pages files (from Apple pages). However, the
  mime type for these files is incorrectly just application/zip:

  $ file --mime-type example.pages
  example.pages: application/zip

  Instead, it should be application/vnd.apple.pages .

  This would allow the user to associate LibreOffice Writer with these
  types of files, and use it to open this file. (LibreOffice Writer can
  open .pages files)

  Apple Keynote files should have this MIME type:
  application/vnd.apple.keynote

  Apple Numbers files should have this MIME type:
  application/vnd.apple.numbers

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: mime-support 3.64ubuntu1
  ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
  Uname: Linux 5.4.0-29-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  CasperMD5CheckResult: skip
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 14 14:46:40 2020
  InstallationDate: Installed on 2018-11-11 (550 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  PackageArchitecture: all
  SourcePackage: mime-support
  UpgradeStatus: Upgraded to focal on 2020-04-18 (25 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mime-support/+bug/1878617/+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 1876046] Re: [XPS L501X, Realtek ALC665, Speaker, Internal]

[Charles Bruce]

I have a Dell XPS L501X with exactly the same problem. The fix above:

> volume control -> configuration to Analog Stereo Duplex (unplugged)

I the only thing that has worked for me.

I've tried multiple other suggestions on other sites, include renaming
.config/pulse folder then reboot, force-reload of alsa, removing the
pulse-audio and alsa-base packages from the system, and reinstalling
them, and reviewing all settings in alsa mixer.

Ubuntu works perfectly on this laptop. I had 19.04 previously, and sound
worked fine. An upgrade to 20.04 didn't work as selecting the nVidia
video driver nvidia-driver-390 would not let the OS boot into the GUI.
What is strange is a complete wipe and reinstall of 20.04 from scratch
worked fine, and that video driver was selected automatically.

I'm so glad I found this post, as I now have sound again. For now I'm
content changing the setting by hand after a reboot.

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

Title:
  [XPS L501X, Realtek ALC665, Speaker, Internal]

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 19.04 to 20.04 sound did not work. "Analog Stereo" and 
"Build-in speaker" appears "unplugged/unavaiable". I can change it in volume 
control -> configuration to Analog Stereo Duplex (unplugged)(unavaiable) and 
sound does play, but after each reboot computer changes to Digital Stereo 
IEC985 and do not play sound until changed again.
  I did reinstall of alsa and pulse according to some forums but this didn't 
work.
  Before upgrade everything always worked out of the box since 2009 on this 
computer. I know it's a little old but it works excellent! Please help.

  ProblemType: Bug
  DistroRelease: Ubuntu 20.04
  Package: pulseaudio 1:13.99.1-1ubuntu3
  ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30
  Uname: Linux 5.4.0-28-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.11-0ubuntu27
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kwiatek1472 F pulseaudio
   /dev/snd/controlC0:  kwiatek1472 F pulseaudio
   /dev/snd/pcmC0D0c:   kwiatek1472 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kwiatek1472 F...m pulseaudio
  CasperMD5CheckResult: skip
  CurrentDesktop: XFCE
  Date: Thu Apr 30 09:25:27 2020
  InstallationDate: Installed on 2020-02-25 (64 days ago)
  InstallationMedia: Xubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:MID successful
  Symptom_Card: Built-in Audio - HDA Intel MID
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  kwiatek1472 F pulseaudio
   /dev/snd/controlC0:  kwiatek1472 F pulseaudio
   /dev/snd/pcmC0D0c:   kwiatek1472 F...m pulseaudio
   /dev/snd/pcmC0D0p:   kwiatek1472 F...m pulseaudio
  Symptom_Jack: Speaker, Internal
  Symptom_PulsePlaybackTest: PulseAudio playback test failed
  Symptom_Type: No sound at all
  Title: [XPS L501X, Realtek ALC665, Speaker, Internal] No sound at all
  UpgradeStatus: Upgraded to focal on 2020-04-25 (4 days ago)
  dmi.bios.date: 07/26/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A08
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A08
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: A08
  dmi.modalias: 
dmi:bvnDellInc.:bvrA08:bd07/26/2011:svnDellInc.:pnXPSL501X:pvrA08:rvnDellInc.:rn:rvrA08:cvnDellInc.:ct8:cvrA08:
  dmi.product.name: XPS L501X
  dmi.product.version: A08
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1876046/+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 1766503] Re: ibus-* randomly use high CPU

[Charles Lohr]

New note.  As commented here:
https://github.com/linuxmint/xed/issues/237 you can make it happen by
pressing control key is pressed in rapid succession.

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

Title:
  ibus-* randomly use high CPU

Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 1766503] Re: ibus-* randomly use high CPU

[Charles Lohr]

I have observed this is happening Mint Mate 19.3 but also only when
using Xed.  I have been unable to track down this problem any further.

** Bug watch added: github.com/linuxmint/xed/issues #237
   https://github.com/linuxmint/xed/issues/237

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

Title:
  ibus-* randomly use high CPU

Status in The Ubuntu Power Consumption Project:
  Confirmed
Status in ibus package in Ubuntu:
  Confirmed

Bug description:
  ibus-* randomly use high CPU in Ubuntu 18.04

  In fact, I think it's now using more CPU overall than the shell itself
  is to redraw a 4K screen:

PID USER  PR  NIVIRTRESSHR S  %CPU %MEM TIME+ COMMAND   
  
   3308 dan   20   0 4009804 192676  84804 R  45.7  2.4   1:13.65 
gnome-shell 
   3352 dan   20   0  384364  26796  20552 S  13.9  0.3   0:22.81 ibus-x11  
  
   3372 dan   20   0  217944  10620   7764 S  10.9  0.1   0:16.20 
ibus-engin+ 
   3350 dan   20   0  293828  10384   7516 R  10.6  0.1   0:16.54 
ibus-dconf  
   3346 dan   20   0  374572  11944   8268 S  10.3  0.1   0:15.93 
ibus-daemon

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: ibus 1.5.17-3ubuntu4
  ProcVersionSignature: Ubuntu 4.15.0-19.20-generic 4.15.17
  Uname: Linux 4.15.0-19-generic x86_64
  ApportVersion: 2.20.9-0ubuntu6
  Architecture: amd64
  Date: Tue Apr 24 15:29:07 2018
  InstallationDate: Installed on 2017-12-12 (133 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: ibus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1766503/+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 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)

[Charles Wilkins]

Some additional information and observations.

What I am currently seeing with this issue on 3 systems running Ubuntu
18.04 that did not occur on the same systems that previously ran 16.04
is that the actual screen blanking in 18.04, aside from default settings
or overrides, fails to turn off the monitor using DPMS as it did in
16.04, but only with nvidia binary drivers installed and only in 18.04,
and only with the console blanking code in its current state.

In 18.04 without the nvidia binary driver, console blanking seems to
work, as expected, with the consoleblank=n. This includes a correct
power down.

In 18.04 with the nvidia binary driver 340.107, console blanking only
blanks the screen, but fails to power down the monitor- yet a call to
vbetool dpms off does work, as do any similar calls in X for those
systems that have X installed. So if vbetool dpms works with the nvidia
binary driver and the console blanking code no longer does, I am half
way to an assumption that the dpms code in the console blanking has
changed, with some reservation that possibly the latest nvidia binary
driver doesn't like the way the call is coming from the newly changed
console blanking code.

This problem did not exist in 16.04, on any of our systems to my
knowledge, with or without a graphical desktop installed and with or
without a binary driver installed.

>From my perspective, this isn't an issue of default blanking behaviour,
but rather an issue with a broken dpms call in 18.04 to a system with
the nvidia binary driver. Other calls, such as vbetool dpms off work as
do those within graphical desktop systems such as those like the one
that xscreensaver uses.

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

Title:
  Ubuntu server enables screenblanking, concealing crashdumps (DPMS is
  not used)

Status in kbd package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in kbd source package in Zesty:
  Invalid
Status in linux source package in Zesty:
  Fix Released
Status in kbd package in Debian:
  Fix Released

Bug description:
  James Rice of Jump Networks noticed that there is a screen-blanker
  enabled on Ubuntu Server.

  James notes that this blanking is not enabling DPMS power saving
  (thereby negating any power-saving benefit), and is simply turning the
  screen content blank.   This means that the crash output is invisible
  which is unhelpful on a server (virtual or otherwise).

  Ideally the screen should (at a minimum) be turned on and unblanked at
  the point of an OOPs/crash being printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+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 869017] Re: Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)

[Charles Wilkins]

To Robie Basak, specifically #22,

You said, "I don't see how we created another problem. We changed the default,
that's all."

You seem to have concluded that merely a change of default functionally
was made at some point.

Perhaps that is the case. If so, what specifically was the default
setting that was changed? For example, was it a kernel compilation time
option? If so, can you please specify what setting can be changed back
in order to re-enable Console blanking using DPMS (console display in
power saving mode) for Ubuntu server 18.04?

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

Title:
  Ubuntu server enables screenblanking, concealing crashdumps (DPMS is
  not used)

Status in kbd package in Ubuntu:
  Invalid
Status in linux package in Ubuntu:
  Fix Released
Status in kbd source package in Zesty:
  Invalid
Status in linux source package in Zesty:
  Fix Released
Status in kbd package in Debian:
  Fix Released

Bug description:
  James Rice of Jump Networks noticed that there is a screen-blanker
  enabled on Ubuntu Server.

  James notes that this blanking is not enabling DPMS power saving
  (thereby negating any power-saving benefit), and is simply turning the
  screen content blank.   This means that the crash output is invisible
  which is unhelpful on a server (virtual or otherwise).

  Ideally the screen should (at a minimum) be turned on and unblanked at
  the point of an OOPs/crash being printed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/kbd/+bug/869017/+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 1853065] [NEW] package resolvconf 1.78ubuntu7 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[charles spitzer]

Public bug reported:

i was upgrading my windows 10 from 14 to 16 using sudo do-release-
upgrade, which failed about an hour into the process

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: resolvconf 1.78ubuntu7
Uname: Linux 3.4.0+ x86_64
ApportVersion: 2.20.1-0ubuntu2.21
Architecture: amd64
Date: Mon Nov 18 15:58:15 2019
Dmesg:
 
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.6
 apt  1.2.32
SourcePackage: resolvconf
Title: package resolvconf 1.78ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2019-11-18 (0 days ago)

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


** Tags: amd64 apport-package uec-images xenial

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

Title:
  package resolvconf 1.78ubuntu7 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in resolvconf package in Ubuntu:
  New

Bug description:
  i was upgrading my windows 10 from 14 to 16 using sudo do-release-
  upgrade, which failed about an hour into the process

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: resolvconf 1.78ubuntu7
  Uname: Linux 3.4.0+ x86_64
  ApportVersion: 2.20.1-0ubuntu2.21
  Architecture: amd64
  Date: Mon Nov 18 15:58:15 2019
  Dmesg:
   
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.6
   apt  1.2.32
  SourcePackage: resolvconf
  Title: package resolvconf 1.78ubuntu7 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2019-11-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/resolvconf/+bug/1853065/+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 1609750] Re: Audio not working on Acer Chromebook R11

[Mutatina Charles Mwombeki]

thanks for the feedback

On Thu, Sep 26, 2019, 09:55 daniel primo stuart <1609...@bugs.launchpad.net>
wrote:

> Kernel needs this patch for maxim98090 to work on cyan and some baytrail
> chromebooks:
>
> https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f
>
> As it didn't make to 5.3 on time, would be nice if it were backported by
> ubuntu devs
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1803810).
> https://bugs.launchpad.net/bugs/1609750
>
> Title:
>   Audio not working on Acer Chromebook R11
>
> Status in linux:
>   Confirmed
> Status in linux package in Ubuntu:
>   In Progress
> Status in pulseaudio package in Ubuntu:
>   Invalid
>
> Bug description:
>   Audio is not working at all on Acer Chromebook R11 (codename CYAN).
>   It's a Intel Braswell platform. snd_hda_intel messages seem normal,
>   but Pulseaudio does not detect sound hardware.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.10
>   Package: pulseaudio 1:9.0-1.1ubuntu1
>   ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
>   Uname: Linux 4.4.0-33-generic x86_64
>   ApportVersion: 2.20.3-0ubuntu2
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p',
> '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: Unity
>   Date: Thu Aug  4 14:12:03 2016
>   InstallationDate: Installed on 2016-07-22 (13 days ago)
>   InstallationMedia:
>
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   SourcePackage: pulseaudio
>   Symptom: audio
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/20/2016
>   dmi.bios.vendor: coreboot
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: GOOGLE
>   dmi.modalias:
> dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
>   dmi.product.name: Cyan
>   dmi.product.version: 1.0
>   dmi.sys.vendor: GOOGLE
>   ---
>   ApportVersion: 2.20.3-0ubuntu2
>   Architecture: amd64
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p',
> '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: Unity
>   DistroRelease: Ubuntu 16.10
>   HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08
>   InstallationDate: Installed on 2016-07-22 (13 days ago)
>   InstallationMedia:
>
>   Lsusb:
>Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
>Bus 001 Device 003: ID 8087:0a2a Intel Corp.
>Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp.
>Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
>   MachineType: GOOGLE Cyan
>   Package: linux-image-4.4.0-33-generic 4.4.0-33.52
>   PackageArchitecture: amd64
>   ProcFB: 0 inteldrmfb
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic
> root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7
>   ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   RelatedPackageVersions:
>linux-restricted-modules-4.4.0-33-generic N/A
>linux-backports-modules-4.4.0-33-generic  N/A
>linux-firmware1.159
>   Tags:  yakkety
>   Uname: Linux 4.4.0-33-generic x86_64
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
>   _MarkForUpload: True
>   dmi.bios.date: 05/20/2016
>   dmi.bios.vendor: coreboot
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: GOOGLE
>   dmi.modalias:
> dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr:
>   dmi.product.name: Cyan
>   dmi.product.version: 1.0
>   dmi.sys.vendor: GOOGLE
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions
>

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

Title:
  Audio not working on Acer Chromebook R11

Status in linux:
  Confirmed
Status in linux package in Ubuntu:
  In Progress
Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Audio is not working at all on Acer Chromebook R11 (codename CYAN).
  It's a Intel Braswell platform. snd_hda_intel messages seem normal,
  but Pulseaudio does not detect sound hardware.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: pulseaudio 1:9.0-1.1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.3-0ubunt

Re: [Touch-packages] [Bug 1841659] Re: shaky, unreadable screens; orig. prog seems to be over written??

[charles marshall]

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

I fumbled around and got it fixed.

On Tue, Aug 27, 2019 at 8:45 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> *** This bug is a duplicate of bug 1841318 ***
> https://bugs.launchpad.net/bugs/1841318
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. This particular bug has already been reported and is a
> duplicate of bug 1841318, so it is being marked as such. Please look at
> the other bug report to see if there is any missing information that you
> can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report. Feel free to continue to report any other bugs you may
> find.
>
>
> ** This bug has been marked a duplicate of bug 1841318
>Shaky display on GM965 [X3100] (Core 2 Duo L7500)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1841659
>
> Title:
>   shaky, unreadable screens; orig. prog seems to be over written??
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   I apologize that I cannot explain clearly what happened to end up with
>   this problem. The machine works when I get into firefox, but I really
>   don't have much. My orig. sys. did not have a "dash"? but I had top
>   and bottom options. I just do not know what occurred, but I would like
>   to get rid of the shaky pages either with this or my original
>   settings.
>
>   This problem occurred when I was trying to fix or change something. I
>   do not think this is a bug but it is probably my fault somehow.
>
>   Is there a chance this can be fixed? If not I'll have to re-install
>   after I save all my documents and stuff. It is a dual boot win 7/
>   Uuntu system.
>
>   Is there a step by step guide to help me get this fixed?
>
>   Is there any chance you all can help?
>
>   Does my explanation of this problem make any sense?
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: xorg 1:7.7+19ubuntu12
>   ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
>   Uname: Linux 5.0.0-25-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.10-0ubuntu27.1
>   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:Unity7:ubuntu
>   Date: Tue Aug 27 14:04:31 2019
>   DistUpgraded: Fresh install
>   DistroCodename: disco
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller
> (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
>  Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
>  Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
>   InstallationDate: Installed on 2015-09-10 (1447 days ago)
>   InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64
> (20150422.1)
>   MachineType: LENOVO 7763CU8
>   PccardctlIdent:
>Socket 0:
>  no product info available
>   PccardctlStatus:
>Socket 0:
>  no card
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic
> root=UUID=125478c5-8ad6-45c1-b162-78e61507b85c ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/12/2009
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 7SET38WW (1.24 )
>   dmi.board.name: 7763CU8
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Available
>   dmi.chassis.asset.tag: 2075960
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias:
> dmi:bvnLENOVO:bvr7SET38WW(1.24):bd10/12/2009:svnLENOVO:pn7763CU8:pvrThinkPadX61Tablet:rvnLENOVO:rn7763CU8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.family: ThinkPad X61 Tablet
>   dmi.product.name: 7763CU8
>   dmi.product.version: ThinkPad X61 Tablet
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
>   version.libdrm2: libdrm2 2.4.97-1ubuntu1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20180925-2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net

Re: [Touch-packages] [Bug 1841659] Re: shaky, unreadable screens; orig. prog seems to be over written??

[charles marshall]

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

How can it be repaired?

On Tue, Aug 27, 2019 at 8:45 PM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:

> *** This bug is a duplicate of bug 1841318 ***
> https://bugs.launchpad.net/bugs/1841318
>
> Thank you for taking the time to report this bug and helping to make
> Ubuntu better. This particular bug has already been reported and is a
> duplicate of bug 1841318, so it is being marked as such. Please look at
> the other bug report to see if there is any missing information that you
> can provide, or to see if there is a workaround for the bug.
> Additionally, any further discussion regarding the bug should occur in
> the other report. Feel free to continue to report any other bugs you may
> find.
>
>
> ** This bug has been marked a duplicate of bug 1841318
>Shaky display on GM965 [X3100] (Core 2 Duo L7500)
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1841659
>
> Title:
>   shaky, unreadable screens; orig. prog seems to be over written??
>
> Status in xorg package in Ubuntu:
>   New
>
> Bug description:
>   I apologize that I cannot explain clearly what happened to end up with
>   this problem. The machine works when I get into firefox, but I really
>   don't have much. My orig. sys. did not have a "dash"? but I had top
>   and bottom options. I just do not know what occurred, but I would like
>   to get rid of the shaky pages either with this or my original
>   settings.
>
>   This problem occurred when I was trying to fix or change something. I
>   do not think this is a bug but it is probably my fault somehow.
>
>   Is there a chance this can be fixed? If not I'll have to re-install
>   after I save all my documents and stuff. It is a dual boot win 7/
>   Uuntu system.
>
>   Is there a step by step guide to help me get this fixed?
>
>   Is there any chance you all can help?
>
>   Does my explanation of this problem make any sense?
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 19.04
>   Package: xorg 1:7.7+19ubuntu12
>   ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
>   Uname: Linux 5.0.0-25-generic x86_64
>   .tmp.unity_support_test.0:
>
>   ApportVersion: 2.20.10-0ubuntu27.1
>   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:Unity7:ubuntu
>   Date: Tue Aug 27 14:04:31 2019
>   DistUpgraded: Fresh install
>   DistroCodename: disco
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, if not too technical
>   GraphicsCard:
>Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller
> (primary) [8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
>  Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
>  Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
>   InstallationDate: Installed on 2015-09-10 (1447 days ago)
>   InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64
> (20150422.1)
>   MachineType: LENOVO 7763CU8
>   PccardctlIdent:
>Socket 0:
>  no product info available
>   PccardctlStatus:
>Socket 0:
>  no card
>   ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic
> root=UUID=125478c5-8ad6-45c1-b162-78e61507b85c ro quiet splash vt.handoff=1
>   SourcePackage: xorg
>   Symptom: display
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 10/12/2009
>   dmi.bios.vendor: LENOVO
>   dmi.bios.version: 7SET38WW (1.24 )
>   dmi.board.name: 7763CU8
>   dmi.board.vendor: LENOVO
>   dmi.board.version: Not Available
>   dmi.chassis.asset.tag: 2075960
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: LENOVO
>   dmi.chassis.version: Not Available
>   dmi.modalias:
> dmi:bvnLENOVO:bvr7SET38WW(1.24):bd10/12/2009:svnLENOVO:pn7763CU8:pvrThinkPadX61Tablet:rvnLENOVO:rn7763CU8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
>   dmi.product.family: ThinkPad X61 Tablet
>   dmi.product.name: 7763CU8
>   dmi.product.version: ThinkPad X61 Tablet
>   dmi.sys.vendor: LENOVO
>   version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
>   version.libdrm2: libdrm2 2.4.97-1ubuntu1
>   version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
>   version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
>   version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
>   version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
>   version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-0ubuntu1
>   version.xserver-xorg-video-intel: xserver-xorg-video-intel
> 2:2.99.917+git20180925-2
>   version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+so

[Touch-packages] [Bug 1841659] [NEW] shaky, unreadable screens; orig. prog seems to be over written??

[charles marshall]

Public bug reported:

I apologize that I cannot explain clearly what happened to end up with
this problem. The machine works when I get into firefox, but I really
don't have much. My orig. sys. did not have a "dash"? but I had top and
bottom options. I just do not know what occurred, but I would like to
get rid of the shaky pages either with this or my original settings.

This problem occurred when I was trying to fix or change something. I do
not think this is a bug but it is probably my fault somehow.

Is there a chance this can be fixed? If not I'll have to re-install
after I save all my documents and stuff. It is a dual boot win 7/ Uuntu
system.

Is there a step by step guide to help me get this fixed?

Is there any chance you all can help?

Does my explanation of this problem make any sense?

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu27.1
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:Unity7:ubuntu
Date: Tue Aug 27 14:04:31 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
   Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
InstallationDate: Installed on 2015-09-10 (1447 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
MachineType: LENOVO 7763CU8
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=125478c5-8ad6-45c1-b162-78e61507b85c ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7SET38WW (1.24 )
dmi.board.name: 7763CU8
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: 2075960
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7SET38WW(1.24):bd10/12/2009:svnLENOVO:pn7763CU8:pvrThinkPadX61Tablet:rvnLENOVO:rn7763CU8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X61 Tablet
dmi.product.name: 7763CU8
dmi.product.version: ThinkPad X61 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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 compiz-0.9 corruption 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/1841659

Title:
  shaky, unreadable screens; orig. prog seems to be over written??

Status in xorg package in Ubuntu:
  New

Bug description:
  I apologize that I cannot explain clearly what happened to end up with
  this problem. The machine works when I get into firefox, but I really
  don't have much. My orig. sys. did not have a "dash"? but I had top
  and bottom options. I just do not know what occurred, but I would like
  to get rid of the shaky pages either with this or my original
  settings.

  This problem occurred when I was trying to fix or change something. I
  do not think this is a bug but it is probably my fault somehow.

  Is there a chance this can be fixed? If not I'll have to re-install
  after I save all my documents and stuff. It is a dual boot win 7/
  Uuntu system.

  Is there a step by step guide to help me get this fixed?

  Is there any chance you all can help?

  Does my explanation of this problem make any sense?

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
  Uname: Linux 5.0.0-25-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz

[Touch-packages] [Bug 1841318] [NEW] some crash rest to a "dash" on left, old system ???

[charles marshall]

Public bug reported:

I have a dual boot system that somehow got corrupted on the ubuntu side.
What causes it I do not have a clue. There are two very shaky, blurred
screens. Pressing the firefox icon open up browser fine and all seems to
work. The display is different from what I gotten use to, but it seems
ok. If I close, I get the shaky, very annoying display.

I wish I could give you more helpful info. I tried some stuff on the
terminal that I got readying internet. I think I must have had another
"display" stuffed on top of my original. I don't know how so I am just
guessing. I did not have the "dash"??? on the left before. Now, I do.

I am 78 years old and I choose Ubuntu because I like it. I do not do a
lot of "programing" type of stuff. Ubutnu Mate is what I was using, I
think.

Hope there is something that helps you. Thank you so much for your help.
Ubuntu is a good system.

Thanx, Charlie

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-25.26-generic 5.0.18
Uname: Linux 5.0.0-25-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu27.1
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:Unity7:ubuntu
Date: Sat Aug 24 11:53:20 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation Mobile GM965/GL960 Integrated Graphics Controller (primary) 
[8086:2a02] (rev 0c) (prog-if 00 [VGA controller])
   Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
   Subsystem: Lenovo GM965 [X3100] on ThinkPad T61/R61 [17aa:20b5]
InstallationDate: Installed on 2015-09-10 (1444 days ago)
InstallationMedia: Ubuntu-MATE 15.04 "Vivid Vervet" - Release amd64 (20150422.1)
LightdmDisplayLog: (EE) Wacom Serial Penabled Pen eraser: Error reading wacom 
device : No such device
MachineType: LENOVO 7763CU8
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-25-generic 
root=UUID=125478c5-8ad6-45c1-b162-78e61507b85c ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/12/2009
dmi.bios.vendor: LENOVO
dmi.bios.version: 7SET38WW (1.24 )
dmi.board.name: 7763CU8
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: 2075960
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr7SET38WW(1.24):bd10/12/2009:svnLENOVO:pn7763CU8:pvrThinkPadX61Tablet:rvnLENOVO:rn7763CU8:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad X61 Tablet
dmi.product.name: 7763CU8
dmi.product.version: ThinkPad X61 Tablet
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
version.libdrm2: libdrm2 2.4.97-1ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 19.0.8-0ubuntu0~19.04.1
version.libgl1-mesa-glx: libgl1-mesa-glx 19.0.8-0ubuntu0~19.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.4-1ubuntu3
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1
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 compiz-0.9 corruption 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/1841318

Title:
  some crash rest to a "dash" on left, old system ???

Status in xorg package in Ubuntu:
  New

Bug description:
  I have a dual boot system that somehow got corrupted on the ubuntu
  side. What causes it I do not have a clue. There are two very shaky,
  blurred screens. Pressing the firefox icon open up browser fine and
  all seems to work. The display is different from what I gotten use to,
  but it seems ok. If I close, I get the shaky, very annoying display.

  I wish I could give you more helpful info. I tried some stuff on the
  terminal that I got readying internet. I think I must have had another
  "display" stuffed on top of my original. I don't know how so I am just
  guessing. I did not have the "dash"??? on the left before. Now, I do.

  I am 78 years old and I choose Ubuntu because I like it. I do not do a
  lot of "programing" type of stuff. Ubutnu Mate is what I was using, I
  think.

  Hope there is something that helps you. Thank you so much for your
  help. Ubuntu is a good system.

  Thanx, Charlie

  ProblemType: Bug

[Touch-packages] [Bug 1610944] Re: GNOME Online Accounts breaks if you log out (until you reboot)

[charles r.]

I also encountered that bug in 19.04

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

Title:
  GNOME Online Accounts breaks if you log out (until you reboot)

Status in gnome-online-accounts:
  Confirmed
Status in Ubuntu GNOME:
  Fix Released
Status in gnome-online-accounts package in Ubuntu:
  Fix Released
Status in gnome-session package in Ubuntu:
  Fix Released
Status in gnome-online-accounts source package in Yakkety:
  Won't Fix
Status in gnome-session source package in Yakkety:
  Won't Fix
Status in gnome-online-accounts source package in Zesty:
  Won't Fix
Status in gnome-session source package in Zesty:
  Won't Fix

Bug description:
  Impact
  ==
  After logging out, GNOME Online Accounts doesn't work the next time you log 
in.

  This bug was a Release Blocker for Fedora 26. (Fedora 26 will be
  released in July).

  gnome-session is the only package updated in this update (not gnome-
  online-accounts).

  Test Case
  =
  From Ubuntu GNOME, click Settings>Online Accounts and add your Google 
account. Install Evolution if it's not installed. Verified that your Google 
account has synced.

  Log out. Log in. It may help to reproduce the bug log in to a
  different session (GNOME on Wayland instead of GNOME, or the other way
  around).

  Open Evolution. Verify that no errors are reported and that your
  Google account is still syncing.

  After installing the gnome-session update, I recommend rebooting once
  to clear any old lingering GNOME Online Accounts processes from
  previous sessions.

  Regression Potential
  
  This fix is the same as was accepted into Fedora 26. It is a workaround by 
killing all the user's D-Bus sessions when the user logs out. This fix has been 
backported from gnome-session 3.25.3. It has not been applied to the 3.24 git 
branch upstream.

  Since 16.10 has almost reached its end of life (July), I am not
  proposing this fix there. I believe 16.10 is the first release
  affected since Ubuntu moved many more services to systemd user
  sessions in that release.

  The patch tries to only kill the D-Bus sessions if the session being
  logged out is the final remaining session for the user.

  The workaround makes sense to me. It seems similar to the
  KillUserProcesses option that was pushed into systemd to fix this kind
  of problem but it's more limited than the systemd method so hopefully
  it won't be as controversial.

  Original Bug Report
  ===
  Can't add any online accounts in after opened Online accounts + mark is 
faded, can't click.
  After reinstalled gnome-online-accounts still has same problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.20.3-1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Budgie:GNOME
  Date: Mon Aug  8 15:33:45 2016
  SourcePackage: gnome-online-accounts
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-online-accounts/+bug/1610944/+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 1838352] [NEW] package python3 3.7.3-1 failed to install/upgrade: installed python3 package post-installation script subprocess returned error exit status 4

[Charles Shellenbarger]

Public bug reported:

trying to upgrade

ProblemType: Package
DistroRelease: Ubuntu 19.04
Package: python3 3.7.3-1
ProcVersionSignature: Ubuntu 4.18.0-1024.25~18.04.1-azure 4.18.20
Uname: Linux 4.18.0-1024-azure x86_64
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
Date: Mon Jul 29 19:44:42 2019
ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
RelatedPackageVersions:
 dpkg 1.19.6ubuntu1
 apt  1.8.1
SourcePackage: python3-defaults
Title: package python3 3.7.3-1 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
UpgradeStatus: Upgraded to disco on 2019-07-29 (0 days ago)

** Affects: python3-defaults (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package disco need-duplicate-check uec-images

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

Title:
  package python3 3.7.3-1 failed to install/upgrade: installed python3
  package post-installation script subprocess returned error exit status
  4

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  trying to upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 19.04
  Package: python3 3.7.3-1
  ProcVersionSignature: Ubuntu 4.18.0-1024.25~18.04.1-azure 4.18.20
  Uname: Linux 4.18.0-1024-azure x86_64
  ApportVersion: 2.20.9-0ubuntu7.7
  Architecture: amd64
  Date: Mon Jul 29 19:44:42 2019
  ErrorMessage: installed python3 package post-installation script subprocess 
returned error exit status 4
  Python3Details: /usr/bin/python3.7, Python 3.7.3, python3-minimal, 3.7.3-1
  PythonDetails: /usr/bin/python2.7, Python 2.7.16, python-minimal, 2.7.16-1
  RelatedPackageVersions:
   dpkg 1.19.6ubuntu1
   apt  1.8.1
  SourcePackage: python3-defaults
  Title: package python3 3.7.3-1 failed to install/upgrade: installed python3 
package post-installation script subprocess returned error exit status 4
  UpgradeStatus: Upgraded to disco on 2019-07-29 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/python3-defaults/+bug/1838352/+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 1831264] Re: Sun keyboard Front key not accepted by gnome-control-center

[Charles Lindsey]

Although reported to gitlab.freedesktop.org (see above), there is no sign 
whatsoever of activity in that quarter.
In the meantime, I have just downloaded the latest batch of 18.04 updates, and 
the situation has got immeasurably worse.

The relevant part of the xmodmap -pk output has now changed to:

136 0xffc8 (F11)0xffc8 (F11)0xffc8 (F11)0xffc8 (F11)
0xff69 (Cancel) 0x (NoSymbol)   0xff69 (Cancel) 
137 0xffc9 (F12)0xffc9 (F12)0xffc9 (F12)0xffc9 (F12)
0xff66 (Redo)   0x (NoSymbol)   0xff66 (Redo)   
138 0xffca (F13)0xffca (F13)0xffca (F13)0xffca (F13)
0x1005ff70 (SunProps)   0x (NoSymbol)   0x1005ff70 (SunProps)   
139 0xffcb (F14)0xffcb (F14)0xffcb (F14)0xffcb (F14)
0xff65 (Undo)   0x (NoSymbol)   0xff65 (Undo)   
140 0xffcc (F15)0xffcc (F15)0xffcc (F15)0xffcc (F15)
0x1005ff71 (SunFront)   0x (NoSymbol)   0x1005ff71 (SunFront)   
141 0xffcd (F16)0xffcd (F16)0xffcd (F16)0xffcd (F16)
0x1005ff72 (SunCopy)0x (NoSymbol)   0x1005ff72 (SunCopy)
142 0xffce (F17)0xffce (F17)0xffce (F17)0xffce (F17)
0x1005ff73 (SunOpen)0x (NoSymbol)   0x1005ff73 (SunOpen)
143 0xffcf (F18)0xffcf (F18)0xffcf (F18)0xffcf (F18)
0x1005ff74 (SunPaste)   0x (NoSymbol)   0x1005ff74 (SunPaste)   
144 0xffd0 (F19)0xffd0 (F19)0xffd0 (F19)0xffd0 (F19)
0xff68 (Find)   0x (NoSymbol)   0xff68 (Find)   
145 0xffd1 (F20)0xffd1 (F20)0xffd1 (F20)0xffd1 (F20)
0x1005ff75 (SunCut) 0x (NoSymbol)   0x1005ff75 (SunCut) 
146 0xff6a (Help)   0x (NoSymbol)   0xff6a (Help)   

i.e. the keysyms mapped to keycodes 141, 142, 143, and 145 have all
changed, and unpteen things which were working fine this morning are
suddenly broken (in addition to gedit, which I can fix, my Opera Browser
is affected' libreoffice and firefox seem to have survived, but every
application whatsoever, when you press keycode 145, produces an ugly
popup concerning my "rear microphone" - which does not even exist).

What is going on?

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

Title:
  Sun keyboard Front key not accepted by gnome-control-center

Status in xkeyboard-config:
  New
Status in xkeyboard-config package in Ubuntu:
  Triaged

Bug description:
  A Sun keyboards is recognized by the hardware detector with no
  problem. xmodmap -pk gives the following for the relevant keys:

  136   0xff69 (Cancel) 0x (NoSymbol)   0xff69 (Cancel) 
  137   0xff66 (Redo)   0x (NoSymbol)   0xff66 (Redo)   
  138   0x1005ff70 (SunProps)   0x (NoSymbol)   0x1005ff70 
(SunProps)   
  139   0xff65 (Undo)   0x (NoSymbol)   0xff65 (Undo)   
  140   0x1005ff71 (SunFront)   0x (NoSymbol)   0x1005ff71 
(SunFront)   
  141   0x1008ff57 (XF86Copy)   0x (NoSymbol)   0x1008ff57 
(XF86Copy)   
  142   0x1008ff6b (XF86Open)   0x (NoSymbol)   0x1008ff6b 
(XF86Open)   
  143   0x1008ff6d (XF86Paste)  0x (NoSymbol)   0x1008ff6d 
(XF86Paste)  
  144   0xff68 (Find)   0x (NoSymbol)   0xff68 (Find)   
  145   0x1008ff58 (XF86Cut)0x (NoSymbol)   0x1008ff58 
(XF86Cut)
  146   0xff6a (Help)   0x (NoSymbol)   0xff6a (Help)   

  Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71
  are SUN specials, not in the XF86 set. Pressing either of these using
  xev behaves as expected:

  KeyPress event, serial 37, synthetic NO, window 0x361,
  root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168),
  state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x361,
  root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168),
  state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES,
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  I tried binding "Lower window below other windows" to the SunFront
  using the Settings app, but it did not work.(Note that back in the
  days of 14.04 where you uses CCSM to make this setting, it worked
  fine.)

  After this I did
  $ dconf dump /org/gnome/desktop/wm/keybindings/
  [/]
  lower=['0x1005ff71']
  switch-to-workspace-1=['1']
  move-to-workspace-1=@as []
  switch-to-workspace-2=['2']
  switch-to-workspace-3=['3']
  switch-to-workspace-4=['4']
  move-to-monitor-down=@as []
  move-to-monitor-up=@as []

  So it had reco

[Touch-packages] [Bug 1831264] Re: Sun keyboard Front key not accepted by gnome-control-center

[Charles Lindsey]

See also https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-
config/issues/172

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

Title:
  Sun keyboard Front key not accepted by gnome-control-center

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  A Sun keyboards is recognized by the hardware detector with no
  problem. xmodmap -pk gives the following for the relevant keys:

  136   0xff69 (Cancel) 0x (NoSymbol)   0xff69 (Cancel) 
  137   0xff66 (Redo)   0x (NoSymbol)   0xff66 (Redo)   
  138   0x1005ff70 (SunProps)   0x (NoSymbol)   0x1005ff70 
(SunProps)   
  139   0xff65 (Undo)   0x (NoSymbol)   0xff65 (Undo)   
  140   0x1005ff71 (SunFront)   0x (NoSymbol)   0x1005ff71 
(SunFront)   
  141   0x1008ff57 (XF86Copy)   0x (NoSymbol)   0x1008ff57 
(XF86Copy)   
  142   0x1008ff6b (XF86Open)   0x (NoSymbol)   0x1008ff6b 
(XF86Open)   
  143   0x1008ff6d (XF86Paste)  0x (NoSymbol)   0x1008ff6d 
(XF86Paste)  
  144   0xff68 (Find)   0x (NoSymbol)   0xff68 (Find)   
  145   0x1008ff58 (XF86Cut)0x (NoSymbol)   0x1008ff58 
(XF86Cut)
  146   0xff6a (Help)   0x (NoSymbol)   0xff6a (Help)   

  Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71
  are SUN specials, not in the XF86 set. Pressing either of these using
  xev behaves as expected:

  KeyPress event, serial 37, synthetic NO, window 0x361,
  root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168),
  state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x361,
  root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168),
  state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES,
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  I tried binding "Lower window below other windows" to the SunFront
  using the Settings app, but it did not work.(Note that back in the
  days of 14.04 where you uses CCSM to make this setting, it worked
  fine.)

  After this I did
  $ dconf dump /org/gnome/desktop/wm/keybindings/
  [/]
  lower=['0x1005ff71']
  switch-to-workspace-1=['1']
  move-to-workspace-1=@as []
  switch-to-workspace-2=['2']
  switch-to-workspace-3=['3']
  switch-to-workspace-4=['4']
  move-to-monitor-down=@as []
  move-to-monitor-up=@as []

  So it had recognized the correct keysym, but does not know that the
  name of that keysym is SunFront.

  So far so bad. It works fine with keysyms with known names (e.g. the
  CANCEL key), and it should not be hard to construct a workaround my
  modifying the keyboard tables to map that key to some better-named
  keysym, so it might be argued that this bug is of Low Priority.

  BUT

  there is a serious side effect. With that dconf setting in place: the
  Left Arrow key on the keyboard no longer works (for example, I made
  that change whilst composing this report, and I cannot now move the
  cursor backwards with the Left Arrow key, though fortunately the Left
  Arrow on the numeric keypad still behaves). All applications seem to
  be affected (e.g. Firefox, Terminal, Gedit). Left and
  Left still work, except that if you engage Num Lock,
  Left now stops working.

  Using xev to see what happens when Left Arrow is pressed yields:

  FocusOut event, serial 37, synthetic NO, window 0x361,
  mode NotifyGrab, detail NotifyAncestor

  FocusOut event, serial 37, synthetic NO, window 0x361,
  mode NotifyUngrab, detail NotifyPointer

  FocusIn event, serial 37, synthetic NO, window 0x361,
  mode NotifyUngrab, detail NotifyAncestor

  KeymapNotify event, serial 37, synthetic NO, window 0x0,
  keys:  2   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   
 0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   0   

  which is crazy! You should not be surprised that I spent a whole day
  gradually removing all the changes I had made until finally I narrowed
  it down to dconf, and then to that particular setting. Changing the
  binding back to CANCEL removes the problem (except that you have to
  restart each application affected, so I have just restarted Terminal,
  but I cannot restart Firefox while I am still typing this report).

  My main worry is that there may be some other keybinding errors that cause 
the same side effect, and therefor the Priority of fixing this bug needs to be 
much higher. Moreover, this problem seems to have been around for a long time. 
see:
  
https://unix.stackexchange.com/questions/231307/key-for-the-letter-o-stopped-working-works-

[Touch-packages] [Bug 1831264] Re: Sun keyboard Front key not accepted by gnome-control-center

[Charles Lindsey]

On 03/06/2019 16:05, Gunnar Hjalmarsson wrote:
> Thanks for your report!
> 
> The issues you describe are upstream in nature, and it would be great if
> you could file an upstream issue as well:

See https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-
config/issues/172

> 
> https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues
> 
> If you do, please post the URL to it here for tracking purposes.
> 

-- 
Charles H. Lindsey -At my New Home, still doing my own thing--
Tel: +44 161 488 1845Web: http://www.cs.man.ac.uk/~chl
Email: c...@clerew.man.ac.uk  Snail-mail: Apt 40, SK8 5BF, U.K.
PGP: 2C15F1A9 Fingerprint: 73 6D C2 51 93 A0 01 E7 65 E8 64 7E 14 A4 AB A5


** Bug watch added: 
gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues #172
   https://gitlab.freedesktop.org/xkeyboard-config/xkeyboard-config/issues/172

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

Title:
  Sun keyboard Front key not accepted by gnome-control-center

Status in xkeyboard-config package in Ubuntu:
  New

Bug description:
  A Sun keyboards is recognized by the hardware detector with no
  problem. xmodmap -pk gives the following for the relevant keys:

  136   0xff69 (Cancel) 0x (NoSymbol)   0xff69 (Cancel) 
  137   0xff66 (Redo)   0x (NoSymbol)   0xff66 (Redo)   
  138   0x1005ff70 (SunProps)   0x (NoSymbol)   0x1005ff70 
(SunProps)   
  139   0xff65 (Undo)   0x (NoSymbol)   0xff65 (Undo)   
  140   0x1005ff71 (SunFront)   0x (NoSymbol)   0x1005ff71 
(SunFront)   
  141   0x1008ff57 (XF86Copy)   0x (NoSymbol)   0x1008ff57 
(XF86Copy)   
  142   0x1008ff6b (XF86Open)   0x (NoSymbol)   0x1008ff6b 
(XF86Open)   
  143   0x1008ff6d (XF86Paste)  0x (NoSymbol)   0x1008ff6d 
(XF86Paste)  
  144   0xff68 (Find)   0x (NoSymbol)   0xff68 (Find)   
  145   0x1008ff58 (XF86Cut)0x (NoSymbol)   0x1008ff58 
(XF86Cut)
  146   0xff6a (Help)   0x (NoSymbol)   0xff6a (Help)   

  Observe that the names of the two keysyms 0x1005ff70 and 0x1005ff71
  are SUN specials, not in the XF86 set. Pressing either of these using
  xev behaves as expected:

  KeyPress event, serial 37, synthetic NO, window 0x361,
  root 0x4fe, subw 0x0, time 3071686, (118,83), root:(1365,168),
  state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES,
  XLookupString gives 0 bytes: 
  XmbLookupString gives 0 bytes: 
  XFilterEvent returns: False

  KeyRelease event, serial 37, synthetic NO, window 0x361,
  root 0x4fe, subw 0x0, time 3071688, (118,83), root:(1365,168),
  state 0x0, keycode 140 (keysym 0x1005ff71, SunFront), same_screen YES,
  XLookupString gives 0 bytes: 
  XFilterEvent returns: False

  I tried binding "Lower window below other windows" to the SunFront
  using the Settings app, but it did not work.(Note that back in the
  days of 14.04 where you uses CCSM to make this setting, it worked
  fine.)

  After this I did
  $ dconf dump /org/gnome/desktop/wm/keybindings/
  [/]
  lower=['0x1005ff71']
  switch-to-workspace-1=['1']
  move-to-workspace-1=@as []
  switch-to-workspace-2=['2']
  switch-to-workspace-3=['3']
  switch-to-workspace-4=['4']
  move-to-monitor-down=@as []
  move-to-monitor-up=@as []

  So it had recognized the correct keysym, but does not know that the
  name of that keysym is SunFront.

  So far so bad. It works fine with keysyms with known names (e.g. the
  CANCEL key), and it should not be hard to construct a workaround my
  modifying the keyboard tables to map that key to some better-named
  keysym, so it might be argued that this bug is of Low Priority.

  BUT

  there is a serious side effect. With that dconf setting in place: the
  Left Arrow key on the keyboard no longer works (for example, I made
  that change whilst composing this report, and I cannot now move the
  cursor backwards with the Left Arrow key, though fortunately the Left
  Arrow on the numeric keypad still behaves). All applications seem to
  be affected (e.g. Firefox, Terminal, Gedit). Left and
  Left still work, except that if you engage Num Lock,
  Left now stops working.

  Using xev to see what happens when Left Arrow is pressed yields:

  FocusOut event, serial 37, synthetic NO, window 0x361,
  mode NotifyGrab, detail NotifyAncestor

  FocusOut event, serial 37, synthetic NO, window 0x361,
  mode NotifyUngrab, detail NotifyPointer

  FocusIn event, serial 37, synthetic NO, window 0x361,
  mode NotifyUngrab, detail NotifyAncestor

  KeymapNotify event, serial 37, synthetic NO, window 0x0,
  keys:  2   

[Touch-packages] [Bug 1830318] [NEW] intel graphics issues

[charles kamonde]

Public bug reported:

my computer is behaving a though there arent any graphics drivers
installed

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg (not installed)
ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-20-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri May 24 08:03:57 2019
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

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

Title:
  intel graphics issues

Status in xorg package in Ubuntu:
  New

Bug description:
  my computer is behaving a though there arent any graphics drivers
  installed

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.18.0-20.21~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri May 24 08:03:57 2019
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1830318/+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 1829533] [NEW] Doubled desktop icons

[Charles B Kramer]

Public bug reported:

I customized my icons by changing the folder image.  That worked fine in
Ubuntu 18.04.

When I upgraded to 19.04 my customized icons no longer showed the new
image, and to fix that I did... something.  Install Nemo deskop, I
think, but I can't find a configuration or uninstall option for it.

Then the old icons with the customized images worked fine... but now the
folders have a doubles that are "dummies" (not working -- not customized
-- don't respond to being clicked).

In the Gnome Tweak Took Desktop icons is "off" but the toggle for
"Desktop Icons Switch" has an ! meaning can't be turned on or off.

I'm moderately techy in Windows, but still pretty stupid about Linux,
sorry.  But I can probably run tests, find logs, paste commands into
Terminal Window or whatever.

THANKS!!!

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xorg 1:7.7+19ubuntu12
ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
Uname: Linux 5.0.0-15-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Fri May 17 09:27:05 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: Lenovo ThinkPad T520 [17aa:21cf]
Lsusb:
 Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 001 Device 003: ID 147e:2016 Upek Biometric Touchchip/Touchstrip 
Fingerprint Sensor
 Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 4243AV5
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-15-generic 
root=UUID=a8ac701e-a37a-41b7-aa12-0816bd937e33 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/11/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8AET49WW (1.29 )
dmi.board.asset.tag: Not Available
dmi.board.name: 4243AV5
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: 
dmi:bvnLENOVO:bvr8AET49WW(1.29):bd07/11/2011:svnLENOVO:pn4243AV5:pvrThinkPadT520:rvnLENOVO:rn4243AV5:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.family: ThinkPad T520
dmi.product.name: 4243AV5
dmi.product.version: ThinkPad T520
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.14.0+19.04.20190223.1-0ubuntu1
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 19.0.2-1ubuntu1
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/1829533

Title:
  Doubled desktop icons

Status in xorg package in Ubuntu:
  New

Bug description:
  I customized my icons by changing the folder image.  That worked fine
  in Ubuntu 18.04.

  When I upgraded to 19.04 my customized icons no longer showed the new
  image, and to fix that I did... something.  Install Nemo deskop, I
  think, but I can't find a configuration or uninstall option for it.

  Then the old icons with the customized images worked fine... but now
  the folders have a doubles that are "dummies" (not working -- not
  customized -- don't respond to being clicked).

  In the Gnome Tweak Took Desktop icons is "off" but the toggle for
  "Desktop Icons Switch" has an ! meaning can't be turned on or off.

  I'm moderately techy in Windows, but still pretty stupid about Linux,
  sorry.  But I can probably run tests, find logs, paste commands into
  Terminal Window or whatever.

  THANKS!!!

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: xorg 1:7.7+19ubuntu12
  ProcVersionSignature: Ubuntu 5.0.0-15.16-generic 5.0.6
  Uname: Linux 5.0.0-15-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.10-0ubuntu27
  Architect

[Touch-packages] [Bug 1827263] [NEW] mod_brotli missing in Apache Web Server 2.4.29

[Charles J. C. Elling]

Public bug reported:

Apache Module mod_brotli
Description:Compress content via Brotli before it is delivered to the client
Status: Extension
Module Identifier:  brotli_module
Source File:mod_brotli.c
Compatibility:  Available in version 2.4.26 and later.
See https://httpd.apache.org/docs/2.4/mod/mod_brotli.html

> lsb_release -rd
Description:Ubuntu 18.04.2 LTS
Release:18.04

> apt-cache policy apache2
apache2:
  Installed: 2.4.29-1ubuntu4.6
  Candidate: 2.4.29-1ubuntu4.6
  Version table:
 *** 2.4.29-1ubuntu4.6 500
500 http://apt.dreamcompute.com bionic-updates/main amd64 Packages
500 http://apt.dreamcompute.com bionic-security/main amd64 Packages
100 /var/lib/dpkg/status
 2.4.29-1ubuntu4 500
500 http://apt.dreamcompute.com bionic/main amd64 Packages

It was expected to have de following files:
/usr/lib/apache2/modules/mod_brotli.so
/etc/apache2/mods-available/brotli.load
/etc/apache2/mods-available/brotli.conf

But the files are missing and the package does not depend in  libbrotli1
or libbrotli-dev.

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

** Description changed:

  Apache Module mod_brotli
  Description:  Compress content via Brotli before it is delivered to the client
  Status:   Extension
  Module Identifier:brotli_module
  Source File:  mod_brotli.c
  Compatibility:Available in version 2.4.26 and later.
  See https://httpd.apache.org/docs/2.4/mod/mod_brotli.html
  
- 
  > lsb_release -rd
  Description:Ubuntu 18.04.2 LTS
  Release:18.04
  
  > apt-cache policy apache2
  apache2:
-   Installed: 2.4.29-1ubuntu4.6
-   Candidate: 2.4.29-1ubuntu4.6
-   Version table:
-  *** 2.4.29-1ubuntu4.6 500
- 500 http://apt.dreamcompute.com bionic-updates/main amd64 Packages
- 500 http://apt.dreamcompute.com bionic-security/main amd64 Packages
- 100 /var/lib/dpkg/status
-  2.4.29-1ubuntu4 500
- 500 http://apt.dreamcompute.com bionic/main amd64 Packages
- 
- It was expected to have
+   Installed: 2.4.29-1ubuntu4.6
+   Candidate: 2.4.29-1ubuntu4.6
+   Version table:
+  *** 2.4.29-1ubuntu4.6 500
+ 500 http://apt.dreamcompute.com bionic-updates/main amd64 Packages
+ 500 http://apt.dreamcompute.com bionic-security/main amd64 Packages
+ 100 /var/lib/dpkg/status
+  2.4.29-1ubuntu4 500
+ 500 http://apt.dreamcompute.com bionic/main amd64 Packages
  
  It was expected to have de following files:
  /usr/lib/apache2/modules/mod_brotli.so
  /etc/apache2/mods-available/brotli.load
  /etc/apache2/mods-available/brotli.conf
  
  But the files are missing and the package does not depend in  libbrotli1
  or libbrotli-dev.

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

Title:
  mod_brotli missing in Apache Web Server 2.4.29

Status in curl package in Ubuntu:
  New

Bug description:
  Apache Module mod_brotli
  Description:  Compress content via Brotli before it is delivered to the client
  Status:   Extension
  Module Identifier:brotli_module
  Source File:  mod_brotli.c
  Compatibility:Available in version 2.4.26 and later.
  See https://httpd.apache.org/docs/2.4/mod/mod_brotli.html

  > lsb_release -rd
  Description:Ubuntu 18.04.2 LTS
  Release:18.04

  > apt-cache policy apache2
  apache2:
    Installed: 2.4.29-1ubuntu4.6
    Candidate: 2.4.29-1ubuntu4.6
    Version table:
   *** 2.4.29-1ubuntu4.6 500
  500 http://apt.dreamcompute.com bionic-updates/main amd64 Packages
  500 http://apt.dreamcompute.com bionic-security/main amd64 Packages
  100 /var/lib/dpkg/status
   2.4.29-1ubuntu4 500
  500 http://apt.dreamcompute.com bionic/main amd64 Packages

  It was expected to have de following files:
  /usr/lib/apache2/modules/mod_brotli.so
  /etc/apache2/mods-available/brotli.load
  /etc/apache2/mods-available/brotli.conf

  But the files are missing and the package does not depend in
  libbrotli1 or libbrotli-dev.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/curl/+bug/1827263/+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 1825771] [NEW] Screen doesn't go out

[Charles Fonseca de Oliveira Júnior]

Public bug reported:

that screen doesn't work and it doesn't quit

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] Permissão negada: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sun Apr 21 23:57:42 2019
DistUpgraded: Fresh install
DistroCodename: disco
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
   Subsystem: Samsung Electronics Co Ltd HD Graphics 620 [144d:c804]
MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=92ba0814-64ef-4817-a375-a436c2815444 ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 10/16/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P03REP.034.181016.ZW
dmi.board.asset.tag: No Asset Tag
dmi.board.name: NP350XAA-JD1BR
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03REP.034.181016.ZW:bd10/16/2018:svnSAMSUNGELECTRONICSCO.,LTD.:pn340XAA/350XAA/550XAA:pvrP03REP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350XAA-JD1BR:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
dmi.product.family: Notebook 3 Series
dmi.product.name: 340XAA/350XAA/550XAA
dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREP
dmi.product.version: P03REP
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
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

** Attachment added: "that "Autenticação necessária" pop up into scrren after 
log in"
   
https://bugs.launchpad.net/bugs/1825771/+attachment/5257766/+files/Captura%20de%20tela%20de%202019-04-21%2023-56-12.png

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

Title:
  Screen doesn't go out

Status in xorg package in Ubuntu:
  New

Bug description:
  that screen doesn't work and it doesn't quit

  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] Permissão negada: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Apr 21 23:57:42 2019
  DistUpgraded: Fresh install
  DistroCodename: disco
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation HD Graphics 620 [8086:5916] (rev 02) (prog-if 00 [VGA 
controller])
 Subsystem: Samsung Electronics Co Ltd HD Graphics 620 [144d:c804]
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 340XAA/350XAA/550XAA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-13-generic 
root=UUID=92ba0814-64ef-4817-a375-a436c2815444 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/16/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P03REP.034.181016.ZW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: NP350XAA-JD1BR
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: SGLFREEDOS-C00-R000-S+1.0.
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP03REP.034.181016.ZW:bd10/16/2018:svnSAMSUNGELECTRONICSCO.,LTD.:pn340XAA/350XAA/550XAA:pvrP03REP:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP350XAA-JD1BR:rvrSGLFREEDOS-C00-R000-S+1.0.:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:
  dmi.product.family: Notebook 3 Series
  dmi.product.name: 340XAA/350XAA/550XAA
  dmi.product.sku: SCAI-A5A5-A5A5-A5A5-PREP
  dmi.product.version: P03REP
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  versi

Re: [Touch-packages] [Bug 1803810] Re: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card

[Mutatina Charles Mwombeki]

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

thank you for your reply


On Mon, 19 Nov 2018 at 06:15, Daniel van Vugt 
wrote:

> Can you please try headphones, to see if the problem is just with the
> speakers?
>
> Please also run this command:
>
>   dpkg -l > allpackages.txt
>
> and send us the resulting 'allpackages.txt'.
>
>
> ** Changed in: pulseaudio (Ubuntu)
>Status: New => Incomplete
>
> ** Summary changed:
>
> - [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card
> + [chtmax98090 - chtmax98090, playback] Cannot get sound at all
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1803810
>
> Title:
>   [chtmax98090 - chtmax98090, playback] Cannot get sound at all
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   just downloaded and upgraded to ubuntu 18.04 and now i cannot get
>   sound at all im using acer chromebook cb3-111 bay trail with intel
>   processor
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 18.04
>   Package: pulseaudio 1:11.1-1ubuntu7.1
>   ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
>   Uname: Linux 4.15.0-39-generic x86_64
>   ApportVersion: 2.20.9-0ubuntu7.5
>   Architecture: amd64
>   AudioDevicesInUse:
>USERPID ACCESS COMMAND
>/dev/snd/controlC1:  mutta255   1262 F pulseaudio
>   CurrentDesktop: ubuntu:GNOME
>   Date: Sat Nov 17 11:39:20 2018
>   InstallationDate: Installed on 2018-11-16 (0 days ago)
>   InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64
> (20180725)
>   SourcePackage: pulseaudio
>   Symptom: audio
>   Symptom_Card: Built-in Audio - HDA Intel PCH
>   Title: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect
> card
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 12/03/2017
>   dmi.bios.vendor: coreboot
>   dmi.chassis.type: 3
>   dmi.chassis.vendor: GOOGLE
>   dmi.modalias:
> dmi:bvncoreboot:bvr:bd12/03/2017:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
>   dmi.product.name: Gnawty
>   dmi.product.version: 1.0
>   dmi.sys.vendor: GOOGLE
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803810/+subscriptions
>

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

Title:
  [chtmax98090 - chtmax98090, playback] Cannot get sound at all

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  just downloaded and upgraded to ubuntu 18.04 and now i cannot get
  sound at all im using acer chromebook cb3-111 bay trail with intel
  processor

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mutta255   1262 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 11:39:20 2018
  InstallationDate: Installed on 2018-11-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Title: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2017
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd12/03/2017:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803810/+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 1814098] [NEW] Favorites cant be added or removed

[Charles Tyrwhitt]

Public bug reported:

Apps randomly stay on the sidebar even tho they are not added to
favorites, also favorites cant be removed.

Video:

https://www.youtube.com/watch?v=5LUx3ljV83I

Recreation:

i cant, but restarting the system allways fixes it.

Also the sidebar appears on the lockscreen

ProblemType: Bug
DistroRelease: Ubuntu 18.10
Package: xorg 1:7.7+19ubuntu8
ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
Uname: Linux 4.18.0-13-generic x86_64
ApportVersion: 2.20.10-0ubuntu13.1
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Thu Jan 31 11:43:49 2019
DistUpgraded: Fresh install
DistroCodename: cosmic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GraphicsCard:
 Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
   Subsystem: Lenovo UHD Graphics 620 [17aa:39fa]
InstallationDate: Installed on 2018-12-01 (60 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. 
 Bus 001 Device 002: ID 04f2:b5d9 Chicony Electronics Co., Ltd 
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 81BL
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/12/2017
dmi.bios.vendor: LENOVO
dmi.bios.version: 4QCN41WW(V2.05)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad 520S-14IKB
dmi.modalias: 
dmi:bvnLENOVO:bvr4QCN41WW(V2.05):bd12/12/2017:svnLENOVO:pn81BL:pvrLenovoideapad520S-14IKB:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad520S-14IKB:
dmi.product.family: ideapad 520S-14IKB
dmi.product.name: 81BL
dmi.product.sku: LENOVO_MT_81BL_BU_idea_FM_ideapad 520S-14IKB
dmi.product.version: Lenovo ideapad 520S-14IKB
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.95-1
version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.2-0ubuntu1
version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.2-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3

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


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

Title:
  Favorites cant be added or removed

Status in xorg package in Ubuntu:
  New

Bug description:
  Apps randomly stay on the sidebar even tho they are not added to
  favorites, also favorites cant be removed.

  Video:

  https://www.youtube.com/watch?v=5LUx3ljV83I

  Recreation:

  i cant, but restarting the system allways fixes it.

  Also the sidebar appears on the lockscreen

  ProblemType: Bug
  DistroRelease: Ubuntu 18.10
  Package: xorg 1:7.7+19ubuntu8
  ProcVersionSignature: Ubuntu 4.18.0-13.14-generic 4.18.17
  Uname: Linux 4.18.0-13-generic x86_64
  ApportVersion: 2.20.10-0ubuntu13.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Jan 31 11:43:49 2019
  DistUpgraded: Fresh install
  DistroCodename: cosmic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Lenovo UHD Graphics 620 [17aa:39fa]
  InstallationDate: Installed on 2018-12-01 (60 days ago)
  InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 
(20181017.3)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0cf3:e500 Atheros Communications, Inc. 
   Bus 001 Device 002: ID 04f2:b5d9 Chicony Electronics Co., Ltd 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: LENOVO 81BL
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic 
root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/12/2017
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 4QCN41WW(V2.05)
  dmi.board.asset.tag: NO Asset Tag
  dmi.board.name: LNVNB161216
  dmi.bo

[Touch-packages] [Bug 1813000] [NEW] package ca-certificates 20180409 failed to install/upgrade: installed ca-certificates package post-installation script subprocess returned error exit status 43

[Charles Gillanders]

Public bug reported:

error occurred when running do-release-upgrade

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: ca-certificates 20180409
ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
Uname: Linux 4.4.0-141-generic i686
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: i386
Date: Wed Jan 23 11:27:51 2019
ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 43
InstallationDate: Installed on 2013-08-24 (1978 days ago)
InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release i386 
(20120424.1)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 3.6.7-1~18.04
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2.1
 apt  1.6.6ubuntu0.1
SourcePackage: ca-certificates
Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 43
UpgradeStatus: Upgraded to bionic on 2019-01-23 (0 days ago)

** Affects: ca-certificates (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package bionic i386

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

Title:
  package ca-certificates 20180409 failed to install/upgrade: installed
  ca-certificates package post-installation script subprocess returned
  error exit status 43

Status in ca-certificates package in Ubuntu:
  New

Bug description:
  error occurred when running do-release-upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.4.0-141.167-generic 4.4.162
  Uname: Linux 4.4.0-141-generic i686
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: i386
  Date: Wed Jan 23 11:27:51 2019
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 43
  InstallationDate: Installed on 2013-08-24 (1978 days ago)
  InstallationMedia: Ubuntu-Server 12.04 LTS "Precise Pangolin" - Release i386 
(20120424.1)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.7, python3-minimal, 
3.6.7-1~18.04
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2.1
   apt  1.6.6ubuntu0.1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 43
  UpgradeStatus: Upgraded to bionic on 2019-01-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1813000/+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 1804330] Re: seccomp preventing package installs

[Charles Baillie]

This was fixed by removing microsoft scep software. Nothing to do with
seccomp in the end.

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

Title:
  seccomp preventing package installs

Status in libseccomp package in Ubuntu:
  New

Bug description:
  I'm not sure exactly what the problem is but on our 18.04 server installing 
packages has become an issue. For apt packages the workaround is:
  sudo MAN_DISABLE_SECCOMP=1 apt install 

  But I recently tried to install rstudio server with and without
  passing the seccomp environment:

  sudo MAN_DISABLE_SECCOMP=1 gdebi rstudio-server-1.1.463-amd64.deb

  and keep getting this error:

   error[4e0c]: Cannot connect to /tmp/scep.sock: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1804330/+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 1806088] [NEW] disco livecd still has insecure version 15 days after 10.4 bugfix hit proposed

[Charles Evans]

Public bug reported:

This applies to disco only.
Ref: symlink exploit fixed in 10.4 release

Systemd restart is masked.
Debian lists this update as high priority.
Any easy get-root bug should be critical, 
not medium priority as listed in the usn. 
Updating while running the livecd  is not securing anything.
Please prioritize release of proposed security updates to disco,
and all future current livecd versions.
At least push out those updates that require substantial knowledge to activate
(libc6, dbus, systemd, and their dependencies, etc )
and packages needed to do updates (apt, networkmanager, their dependencies, etc)


Is there a way to override the mask and restart systemd?
Can I use apparmor to prevent the symlink exploit? How?


Should I file this elsewhere?

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

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

Title:
  disco livecd still has insecure version 15 days after 10.4 bugfix hit
  proposed

Status in systemd package in Ubuntu:
  New

Bug description:
  This applies to disco only.
  Ref: symlink exploit fixed in 10.4 release

  Systemd restart is masked.
  Debian lists this update as high priority.
  Any easy get-root bug should be critical, 
  not medium priority as listed in the usn. 
  Updating while running the livecd  is not securing anything.
  Please prioritize release of proposed security updates to disco,
  and all future current livecd versions.
  At least push out those updates that require substantial knowledge to activate
  (libc6, dbus, systemd, and their dependencies, etc )
  and packages needed to do updates (apt, networkmanager, their dependencies, 
etc)

  
  Is there a way to override the mask and restart systemd?
  Can I use apparmor to prevent the symlink exploit? How?

  
  Should I file this elsewhere?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1806088/+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 1787824] Re: "rfkill: input handler disabled" boot time 11 seconds.

[Charles Wright]

I was watching a video over the network from my x1 system when it went
offline.

My system had been up over a day at the time,

Later it came back online and I found this pattern in the logs.

Nov 24 22:08:38 x1 kernel: [ 4491.984774] rfkill: input handler enabled
Nov 24 22:45:15 x1 kernel: [ 6689.350749] r8169 :04:00.0 eth0: link down
Nov 24 22:45:18 x1 kernel: [ 6692.350653] r8169 :04:00.0 eth0: link up
...
Nov 24 23:28:51 x1 kernel: [ 9305.191129] perf: interrupt took too long (2514 > 
2500), lowering kernel.perf_event_max_sample_rate to 79500
Nov 24 23:44:36 x1 kernel: [10250.105921] r8169 :04:00.0 eth0: link down
Nov 24 23:44:39 x1 kernel: [10253.137255] r8169 :04:00.0 eth0: link up
Nov 24 23:44:41 x1 kernel: [10254.820174] r8169 :04:00.0 eth0: link down
Nov 24 23:44:53 x1 kernel: [10267.308766] r8169 :04:00.0 eth0: link down
Nov 24 23:44:57 x1 kernel: [10270.416767] r8169 :04:00.0 eth0: link up
Nov 24 23:45:05 x1 kernel: [10278.366294] r8169 :04:00.0 eth0: link down
Nov 24 23:45:08 x1 kernel: [10281.415489] r8169 :04:00.0 eth0: link up
Nov 24 23:45:56 x1 kernel: [10329.333933] r8169 :04:00.0 eth0: link down
Nov 24 23:46:04 x1 kernel: [10337.815700] r8169 :04:00.0 eth0: link down
Nov 24 23:46:11 x1 kernel: [10344.998667] r8169 :04:00.0 eth0: link up
Nov 24 23:46:13 x1 kernel: [10346.873959] r8169 :04:00.0 eth0: link down
Nov 24 23:46:16 x1 kernel: [10350.226690] r8169 :04:00.0 eth0: link up
Nov 24 23:46:18 x1 kernel: [10352.318011] r8169 :04:00.0 eth0: link down
Nov 24 23:46:21 x1 kernel: [10355.245040] r8169 :04:00.0 eth0: link up

Nov 26 21:14:23 x1 kernel: [129787.573891] rfkill: input handler enabled
Nov 26 21:23:30 x1 kernel: [130334.427437] r8169 :03:00.0 eth0: link down
Nov 26 21:23:33 x1 kernel: [130337.443076] r8169 :03:00.0 eth0: link up
Nov 26 21:23:57 x1 kernel: [130361.790251] r8169 :03:00.0 eth0: link down
Nov 26 21:24:00 x1 kernel: [130364.790674] r8169 :03:00.0 eth0: link up
Nov 26 21:41:58 x1 kernel: [131442.193462] r8169 :03:00.0 eth0: link down
Nov 26 21:42:01 x1 kernel: [131445.332817] r8169 :03:00.0 eth0: link up
Nov 26 21:42:14 x1 kernel: [131458.567170] rfkill: input handler disabled
Nov 26 21:42:16 x1 kernel: [131460.513607] r8169 :03:00.0 eth0: link down
Nov 26 21:42:19 x1 kernel: [131464.056605] r8169 :03:00.0 eth0: link up
Nov 26 21:42:23 x1 kernel: [131467.593377] r8169 :03:00.0 eth0: link down
Nov 26 21:42:30 x1 kernel: [131474.613404] r8169 :03:00.0 eth0: link up
Nov 26 21:42:41 x1 kernel: [131485.133432] r8169 :03:00.0 eth0: link down
Nov 26 21:42:49 x1 kernel: [131493.199224] rfkill: input handler enabled
Nov 26 21:42:52 x1 kernel: [131496.274226] r8169 :03:00.0 eth0: link up
Nov 26 21:42:53 x1 kernel: [131497.548189] r8169 :03:00.0 eth0: link down
Nov 26 21:42:56 x1 kernel: [131500.994252] r8169 :03:00.0 eth0: link up
Nov 26 21:42:57 x1 kernel: [131501.750754] r8169 :03:00.0 eth0: link down
Nov 26 21:43:04 x1 kernel: [131508.486113] r8169 :03:00.0 eth0: link up


root@x1:/var/log# uname -a
Linux x1 4.15.0-39-generic #42-Ubuntu SMP Tue Oct 23 15:48:01 UTC 2018 x86_64 
x86_64 x86_64 GNU/Linux

root@x1:/var/log# cat /etc/lsb-release 
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=18.04
DISTRIB_CODENAME=bionic
DISTRIB_DESCRIPTION="Ubuntu 18.04.1 LTS"

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

Title:
  "rfkill: input handler disabled" boot time 11 seconds.

Status in util-linux package in Ubuntu:
  Incomplete

Bug description:
  My computer is slowly opening, I looked at the output of dmesg and at 11th I 
get this post.
  What i need to do? thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: rfkill 2.31.1-0.4ubuntu3.1
  ProcVersionSignature: Ubuntu 4.15.0-32.35-generic 4.15.18
  Uname: Linux 4.15.0-32-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.2
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Aug 19 19:44:21 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libsmartcols1 2.31.1-0.4ubuntu3.1
  InstallationDate: Installed on 2018-08-18 (1 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: util-linux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1787824/+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 1804330] [NEW] seccomp preventing package installs

[Charles Baillie]

Public bug reported:

I'm not sure exactly what the problem is but on our 18.04 server installing 
packages has become an issue. For apt packages the workaround is:
sudo MAN_DISABLE_SECCOMP=1 apt install 

But I recently tried to install rstudio server with and without passing
the seccomp environment:

sudo MAN_DISABLE_SECCOMP=1 gdebi rstudio-server-1.1.463-amd64.deb

and keep getting this error:

 error[4e0c]: Cannot connect to /tmp/scep.sock: Permission denied

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

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

Title:
  seccomp preventing package installs

Status in libseccomp package in Ubuntu:
  New

Bug description:
  I'm not sure exactly what the problem is but on our 18.04 server installing 
packages has become an issue. For apt packages the workaround is:
  sudo MAN_DISABLE_SECCOMP=1 apt install 

  But I recently tried to install rstudio server with and without
  passing the seccomp environment:

  sudo MAN_DISABLE_SECCOMP=1 gdebi rstudio-server-1.1.463-amd64.deb

  and keep getting this error:

   error[4e0c]: Cannot connect to /tmp/scep.sock: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1804330/+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 1804330] Re: seccomp preventing package installs

[Charles Baillie]

sorry, I  should add that the apt workaround mentioned is to ensure that
man-db specifically doesn't freak out and end up in core dump loop.

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

Title:
  seccomp preventing package installs

Status in libseccomp package in Ubuntu:
  New

Bug description:
  I'm not sure exactly what the problem is but on our 18.04 server installing 
packages has become an issue. For apt packages the workaround is:
  sudo MAN_DISABLE_SECCOMP=1 apt install 

  But I recently tried to install rstudio server with and without
  passing the seccomp environment:

  sudo MAN_DISABLE_SECCOMP=1 gdebi rstudio-server-1.1.463-amd64.deb

  and keep getting this error:

   error[4e0c]: Cannot connect to /tmp/scep.sock: Permission denied

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libseccomp/+bug/1804330/+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 1803992] [NEW] Lock screen, notifications panel crashes

[Charles Birk]

Public bug reported:

Multiple issues:
1) Lock screen crashes revealing the desktop after sleep/wake

2) Notification panel crashes constantly (with ubuntu-mate)

3) Ability to send report fails for whatever reason

Pics attached here: https://imgur.com/a/dtUaXQF

Happy to work with anyone to get this resolved.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: xorg 1:7.7+19ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
 GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CompositorRunning: None
CurrentDesktop: MATE
Date: Mon Nov 19 08:40:53 2018
DistUpgraded: Fresh install
DistroCodename: bionic
DistroVariant: ubuntu
DkmsStatus:
 nvidia, 390.87, 4.15.0-38-generic, x86_64: installed
 nvidia, 390.87, 4.15.0-39-generic, x86_64: installed
ExtraDebuggingInterest: Yes, including running git bisection searches
GraphicsCard:
 NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 
00 [VGA controller])
   Subsystem: eVga.com. Corp. GP106 [GeForce GTX 1060 6GB] [3842:6161]
LightdmLog:
 [+119931.86s] DEBUG: Seat seat0 changes active session to 
 [+119934.82s] DEBUG: Seat seat0 changes active session to c2
 [+119934.82s] DEBUG: Session c2 is already active
MachineType: Gigabyte Technology Co., Ltd. Z170X-Designare
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-39-generic 
root=/dev/mapper/hostname--vg-root ro initrd=initrd.gz text
SourcePackage: xorg
Symptom: display
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/09/2018
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: F23g
dmi.board.asset.tag: Default string
dmi.board.name: Z170X-Designare-CF
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrF23g:bd03/09/2018:svnGigabyteTechnologyCo.,Ltd.:pnZ170X-Designare:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnZ170X-Designare-CF:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:
dmi.product.family: Default string
dmi.product.name: Z170X-Designare
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
version.compiz: compiz N/A
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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.2
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

** Affects: xorg (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/1803992

Title:
  Lock screen, notifications panel crashes

Status in xorg package in Ubuntu:
  New

Bug description:
  Multiple issues:
  1) Lock screen crashes revealing the desktop after sleep/wake

  2) Notification panel crashes constantly (with ubuntu-mate)

  3) Ability to send report fails for whatever reason

  Pics attached here: https://imgur.com/a/dtUaXQF

  Happy to work with anyone to get this resolved.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.87  Tue Aug 21 12:33:05 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-27ubuntu1~18.04)
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: MATE
  Date: Mon Nov 19 08:40:53 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.87, 4.15.0-38-generic, x86_64: installed
   nvidia, 390.87, 4.15.0-39-generic, x86

[Touch-packages] [Bug 1803810] [NEW] [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card

[Mutatina Charles Mwombeki]

Public bug reported:

just downloaded and upgraded to ubuntu 18.04 and now i cannot get sound
at all im using acer chromebook cb3-111 bay trail with intel processor

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: pulseaudio 1:11.1-1ubuntu7.1
ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
Uname: Linux 4.15.0-39-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC1:  mutta255   1262 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 17 11:39:20 2018
InstallationDate: Installed on 2018-11-16 (0 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
SourcePackage: pulseaudio
Symptom: audio
Symptom_Card: Built-in Audio - HDA Intel PCH
Title: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/03/2017
dmi.bios.vendor: coreboot
dmi.chassis.type: 3
dmi.chassis.vendor: GOOGLE
dmi.modalias: 
dmi:bvncoreboot:bvr:bd12/03/2017:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
dmi.product.name: Gnawty
dmi.product.version: 1.0
dmi.sys.vendor: GOOGLE

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


** Tags: amd64 apport-bug bionic

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

Title:
  [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  just downloaded and upgraded to ubuntu 18.04 and now i cannot get
  sound at all im using acer chromebook cb3-111 bay trail with intel
  processor

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: pulseaudio 1:11.1-1ubuntu7.1
  ProcVersionSignature: Ubuntu 4.15.0-39.42-generic 4.15.18
  Uname: Linux 4.15.0-39-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  mutta255   1262 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Nov 17 11:39:20 2018
  InstallationDate: Installed on 2018-11-16 (0 days ago)
  InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 
(20180725)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Title: [chtmax98090 - chtmax98090, playback] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/03/2017
  dmi.bios.vendor: coreboot
  dmi.chassis.type: 3
  dmi.chassis.vendor: GOOGLE
  dmi.modalias: 
dmi:bvncoreboot:bvr:bd12/03/2017:svnGOOGLE:pnGnawty:pvr1.0:cvnGOOGLE:ct3:cvr:
  dmi.product.name: Gnawty
  dmi.product.version: 1.0
  dmi.sys.vendor: GOOGLE

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1803810/+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 1795081] [NEW] I'm not sure. Earlier today the computer didn't waken up as usual, when I clicked the mouse, but revived when I pressed the ppwer button. It revived, but displaye

[Charles Ronald McMillan]

Public bug reported:

Nothing to add.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tzdata 2018e-0ubuntu0.16.04
ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18
Uname: Linux 4.15.0-34-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.18
AptOrdering:
 tzdata: Install
 tzdata: Configure
 NULL: ConfigurePending
Architecture: amd64
Date: Fri Sep 28 23:29:35 2018
ErrorMessage: subprocess installed post-installation script returned error exit 
status 128
InstallationDate: Installed on 2018-07-29 (61 days ago)
InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.4
 apt  1.2.27
SourcePackage: tzdata
Title: package tzdata 2018e-0ubuntu0.16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  I'm not sure.  Earlier today the computer didn't waken up as usual,
  when I clicked the mouse, but revived when I pressed the ppwer button.
  It revived, but displayed a message saying that there was a system
  problem, and asked me if I wished to report it.

Status in tzdata package in Ubuntu:
  New

Bug description:
  Nothing to add.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tzdata 2018e-0ubuntu0.16.04
  ProcVersionSignature: Ubuntu 4.15.0-34.37~16.04.1-generic 4.15.18
  Uname: Linux 4.15.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  AptOrdering:
   tzdata: Install
   tzdata: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Sep 28 23:29:35 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 128
  InstallationDate: Installed on 2018-07-29 (61 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.27
  SourcePackage: tzdata
  Title: package tzdata 2018e-0ubuntu0.16.04 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 128
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tzdata/+bug/1795081/+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 1760714] [NEW] getlogin_r is performing NSS lookups when loginid isn't set

[Charles F. Stephens]

Public bug reported:

This the eglibc duplicate of
https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1760713 (which is
for glibc)

For configurations that use networked naming services for passwd (in
particular LDAP), processes that have no login UID, there are excessive
delays when getlogin_r() is called.

For such processes, /proc/self/loginid is set to a sentinel value (-1),
when files is the only backend, or if nscd is running this returns
quickly. However if ldap is configured as a backend for passwd, and nscd
isn't being used (which for various political and economic reasons is
not always feasible) network requests to the configured LDAP servers
will occur which can slow down process creation enough to cause timeouts
in parent processes in certain contexts.

Good news, however, as this was recently fixed upstream by:

https://sourceware.org/git/?p=glibc.git;a=commit;h=cc8a1620eb97ccddd337d157263c13c57b39ab71

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

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

Title:
  getlogin_r is performing NSS lookups when loginid isn't set

Status in eglibc package in Ubuntu:
  New

Bug description:
  This the eglibc duplicate of
  https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1760713 (which is
  for glibc)

  For configurations that use networked naming services for passwd (in
  particular LDAP), processes that have no login UID, there are
  excessive delays when getlogin_r() is called.

  For such processes, /proc/self/loginid is set to a sentinel value
  (-1), when files is the only backend, or if nscd is running this
  returns quickly. However if ldap is configured as a backend for
  passwd, and nscd isn't being used (which for various political and
  economic reasons is not always feasible) network requests to the
  configured LDAP servers will occur which can slow down process
  creation enough to cause timeouts in parent processes in certain
  contexts.

  Good news, however, as this was recently fixed upstream by:

  
https://sourceware.org/git/?p=glibc.git;a=commit;h=cc8a1620eb97ccddd337d157263c13c57b39ab71

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1760714/+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 1371250] Re: LightDM fails to switch to greeter on logout if allow-user-switching=false

[Charles Wright]

Hello,

I'm using multiseat under ubuntu lts 16.04

I found a description of what is happening here:
https://lists.launchpad.net/ubuntu-multiseat/msg00505.html

In short, seat-1 lock/switch user doesn't work and generates tons of
error logs

[+763003.64s] DEBUG: Launching process 27821: /usr/bin/X :1 -s seat-1 :2 
-config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 
-nolisten tcp
[+763003.69s] DEBUG: Launching process 27822: /usr/bin/X :1 -s seat-1 :2 
-config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 
-nolisten tcp
[+763003.74s] DEBUG: Launching process 27823: /usr/bin/X :1 -s seat-1 :2 
-config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 
-nolisten tcp
[+763003.79s] DEBUG: Launching process 27824: /usr/bin/X :1 -s seat-1 :2 
-config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 
-nolisten tcp
[+763003.84s] DEBUG: Launching process 27825: /usr/bin/X :1 -s seat-1 :2 
-config /etc/X11/xorg.conf.nvidia -seat seat-1 -auth /var/run/lightdm/root/:2 
-nolisten tcp


I configured allow-user-switching=false so that my logs won't fill up.

[Seat:seat-1]
xserver-command=/usr/bin/X :1 -s seat-1
xserver-config=/etc/X11/xorg.conf.nvidia
# This kept constant respawn of X from filling up logs, but only allows one 
login - greeter fails to start
allow-user-switching=false

Now what happens, just as reported in this bug is that I can start
lightdm, and someone can login once to seat-1, but once they log out
there is no greeter respawned.

I think this bug should be updated to include Xenial as well.

Anyways I'm sure multiseat is a rare thing but I wanted someone to know
it matters to me.

I'm so close to having it work!

Is there anything else I can try to work around?

I see the question above:

"Should we adopt the following solution for this bug?"

I vote yes to that.

Thanks.

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

Title:
  LightDM fails to switch to greeter on logout if allow-user-
  switching=false

Status in Light Display Manager:
  Triaged
Status in Light Display Manager 1.10 series:
  Triaged
Status in Light Display Manager 1.12 series:
  Won't Fix
Status in lightdm package in Ubuntu:
  Triaged
Status in lightdm source package in Trusty:
  Triaged
Status in lightdm source package in Utopic:
  Won't Fix

Bug description:
  In my multiseat system, if I logout on a non-seat0 seat (which has
  allow-user-switching=false by default), lightdm fails to start a
  greeter on that seat:

  DEBUG: Seat: Display server stopped
  DEBUG: Seat: Active display server stopped, starting greeter
  DEBUG: Seat: Stopping; failed to start a greeter
  DEBUG: Seat: Stopping
  DEBUG: Seat: Stopped

  I guess the problem is related to seat_switch_to_greeter() calls in
  session_stopped or display_server_stopped callbacks in seat.c. Switch
  to greeter should be always allowed on logout.

  NOTE: This was observed in LightDM 1.10.2 on Ubuntu 14.04, but I guess
  it also happens on trunk series.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1371250/+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 1278223] Re: Mouse Flickering after adding 3rd Monitor

[D. Charles Pyle]

I had the latest DisplayLink driver and it still did the same thing to
me.  And it gets worse than that.  No errors are generated but the speed
is so slow it is almost unbearable whenever the DisplayLink device is in
use.  I could click the icon for Files to launch Nautilus from the Unity
favorites bar, and it would not appear for almost two whole minutes!
Disconnect the device and reboot, and all was fine with the world--
except that it wasn't.  I could not use my third monitor to do editing
work.

Unfortunately, it became easier just to remove Ubuntu from my system and
move to another distribution that does work with DisplayLink devices.
There were serious problems with power saving, too.  Suspend would crash
the machine rather than suspend to memory, and this was on a system that
I purchased because it was certified for Ubuntu!

In Fedora, the distribution I now am using exclusively, I still see
flickering when the mouse is moved to the top of the screen but the
flickering is bearable compared to the ungodly slowness on the screen
with that flickering, in Ubuntu 16.04.2.  I do not know what the problem
is on Ubuntu with DisplayLink devices but it was too unbearable, and
that is unfortunate because I really liked working in Ubuntu, with Unity
being my chosen interface.  But I hear that even Unity will be going
away.

I hope that one day the display bugs involving DisplayLink displays will
be fixed.  Until then, if I want to get work done, and not have to spend
time waiting between mouse clicks and app launches, I have to go
elsewhere for at least the time being.

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

Title:
  Mouse Flickering after adding 3rd Monitor

Status in X.Org X server:
  New
Status in xorg package in Ubuntu:
  Incomplete
Status in xorg package in Fedora:
  Unknown

Bug description:
  My issues is, after adding a 3rd monitor to Ubuntu 14.04, the mouse
  flickers (or blinks) when the cursor is on monitors one or two, but
  not 3.

  Monitor 1: 1440 x 900 - Laptop's Native Monitor
  Monitor 2: 1920 x 1080 - Laptop's HDMI Port's External Monitor
  Monitor 3: 1024 x 768 - SIIG USB 2.0 to VGA Pro Monitor

  Here's the video card that feeds my laptop's native monitor, monitor 2
  (hdmi).

  lspci | grep 'VGA\|Display'
  00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)
  00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset 
Integrated Graphics Controller (rev 07)

  The 3rd Monitor is powered through a Display Link certified SIIG USB
  2.0 to VGA Pro adapter (A2H1320X1374 - not sure what this number, but
  it is a sticker on back of the device):

  lsusb -tv
  /:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/6p, 480M
  |__ Port 6: Dev 2, If 0, Class=Video, Driver=uvcvideo, 480M
  |__ Port 6: Dev 2, If 1, Class=Video, Driver=uvcvideo, 480M

  dmesg
  [1.688343] usb 2-1: New USB device found, idVendor=17e9, idProduct=02ee
  [1.688348] usb 2-1: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [1.688351] usb 2-1: Product: VGA Display Adapter
  [1.688353] usb 2-1: Manufacturer: DisplayLink
  [1.688356] usb 2-1: SerialNumber: 119785

  Additionally, unity-control-center crashes sometimes after I "Restore
  previous settings", after selecting a resolution too high. This
  freezed my laptop, requiring a hard reboot.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity-control-center 14.04.1-0ubuntu5
  ProcVersionSignature: Ubuntu 3.13.0-8.27-generic 3.13.2
  Uname: Linux 3.13.0-8-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sun Feb  9 18:43:13 2014
  InstallationDate: Installed on 2014-02-02 (7 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Alpha amd64 (20140202)
  SourcePackage: unity-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1278223/+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 1712221] [NEW] package libgtk2.0-bin 2.24.31-1ubuntu1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

[Charles Allen]

Public bug reported:

Not sure where the bug is. Not sure where to begin. I will work on trying to 
provide more technical information on how to report bugs that can actually help 
DevOps. I was trying to update the OS, however it is something that always pops 
up after initial boot/startup.
Thanks

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: libgtk2.0-bin 2.24.31-1ubuntu1
ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
Uname: Linux 4.10.0-32-generic x86_64
ApportVersion: 2.20.4-0ubuntu4.5
AptOrdering:
 net-tools:amd64: Install
 NULL: ConfigurePending
Architecture: amd64
Date: Thu Aug 17 19:45:16 2017
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2017-04-22 (121 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: gtk+2.0
Title: package libgtk2.0-bin 2.24.31-1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk+2.0 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package zesty

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

Title:
  package libgtk2.0-bin 2.24.31-1ubuntu1 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in gtk+2.0 package in Ubuntu:
  New

Bug description:
  Not sure where the bug is. Not sure where to begin. I will work on trying to 
provide more technical information on how to report bugs that can actually help 
DevOps. I was trying to update the OS, however it is something that always pops 
up after initial boot/startup.
  Thanks

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: libgtk2.0-bin 2.24.31-1ubuntu1
  ProcVersionSignature: Ubuntu 4.10.0-32.36-generic 4.10.17
  Uname: Linux 4.10.0-32-generic x86_64
  ApportVersion: 2.20.4-0ubuntu4.5
  AptOrdering:
   net-tools:amd64: Install
   NULL: ConfigurePending
  Architecture: amd64
  Date: Thu Aug 17 19:45:16 2017
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2017-04-22 (121 days ago)
  InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: gtk+2.0
  Title: package libgtk2.0-bin 2.24.31-1ubuntu1 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtk+2.0/+bug/1712221/+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 1691556] Re: Can't send audio to Amazon Echo via Bluetooth

[Charles Inwald]

** Also affects: bluez
   Importance: Undecided
   Status: New

** No longer affects: bluez

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

Title:
  Can't send audio to Amazon Echo via Bluetooth

Status in bluez package in Ubuntu:
  Confirmed

Bug description:
  Pairing and coupling to Amazon Echo works, but no sound is heard.

  I believe the issue is related to the fact that Amazon Echo is paired
  as a handset (i.e., speaker + microphone) rather than just as a
  speaker.  I believe the critical error is found in a dmesg line such
  as:

  Feb 28 10:59:05 n1 bluetoothd[1025]: a2dp-source profile connect
  failed for 50:F5:DA:A6:3F:EA: Device or resource busy

  as I describe in the askubuntu.com discussion at:

  https://askubuntu.com/questions/871630/cant-send-audio-to-amazon-echo-
  via-bluetooth

  I have clarified there my thinking and the steps I've taken thus far
  on this issue, which includes trying debug bluetooth per the Ubuntu
  wiki page which describes how to do so.

  This is probably an upstream issue, as Mike H-R has commented there
  that the problem also occurs on ArchLinux.

  I and a few others would like to get this resolved, and I am happy to
  help (I'm a software developer).  However, at this point, I'm not sure
  how to proceed without some assistance.  I suppose I could report it
  to Debain, but I've only ever used Debain vis a vis Ubuntu, so I
  thought it best to start here.

  Thanks.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: bluez 5.37-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-72.93-generic 4.4.49
  Uname: Linux 4.4.0-72-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed May 17 22:27:59 2017
  InstallationDate: Installed on 2015-12-26 (507 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  InterestingModules: rfcomm bnep btusb bluetooth
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-72-generic 
root=UUID=5950fbba-cde1-49ac-a918-04e517894c57 ro quiet splash vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: Upgraded to xenial on 2017-02-28 (78 days ago)
  dmi.bios.date: 01/18/2017
  dmi.bios.vendor: Intel Corporation
  dmi.bios.version: RYBDWi35.86A.0362.2017.0118.0940
  dmi.board.name: NUC5i5RYB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: H40999-504
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorporation:bvrRYBDWi35.86A.0362.2017.0118.0940:bd01/18/2017:svn:pn:pvr:rvnIntelCorporation:rnNUC5i5RYB:rvrH40999-504:cvn:ct3:cvr:
  hciconfig:
   hci0:Type: BR/EDR  Bus: USB
    BD Address: DC:53:60:97:55:17  ACL MTU: 1021:5  SCO MTU: 96:6
    UP RUNNING PSCAN
    RX bytes:13547334 acl:58 sco:0 events:1935087 errors:0
    TX bytes:1652407651 acl:1934967 sco:0 commands:76 errors:0
  mtime.conffile..etc.bluetooth.main.conf: 2015-12-29T07:24:08.439240

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1691556/+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 1710531] [NEW] package linux-image-4.4.0-91-generic 4.4.0-91.114 failed to install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with return code 2

[Charles Henrique Martins Sobrinho]

Public bug reported:

package linux-image-4.4.0-91-generic 4.4.0-91.114 failed to
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
exited with return code 2

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-91-generic 4.4.0-91.114
ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
Uname: Linux 4.4.0-89-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.10
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  ra059746   2176 F pulseaudio
Date: Sun Aug 13 23:30:30 2017
ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
HibernationDevice: RESUME=UUID=26cb4e4c-de55-4871-a29e-e47c9cf17400
InstallationDate: Installed on 2016-04-22 (478 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Houter Oro PC
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-89-generic root=/dev/sda8 ro quiet 
splash vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
RfKill:
 0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
SourcePackage: apt
Title: package linux-image-4.4.0-91-generic 4.4.0-91.114 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/15/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.02
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: Oro PC
dmi.board.vendor: Houter
dmi.board.version: To be filled by O.E.M.
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 10
dmi.chassis.vendor: Houter
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd12/15/2010:svnHouter:pnOroPC:pvrTobefilledbyO.E.M.:rvnHouter:rnOroPC:rvrTobefilledbyO.E.M.:cvnHouter:ct10:cvrToBeFilledByO.E.M.:
dmi.product.name: Oro PC
dmi.product.version: To be filled by O.E.M.
dmi.sys.vendor: Houter

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

Title:
  package linux-image-4.4.0-91-generic 4.4.0-91.114 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 2

Status in apt package in Ubuntu:
  New

Bug description:
  package linux-image-4.4.0-91-generic 4.4.0-91.114 failed to
  install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal
  exited with return code 2

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-91-generic 4.4.0-91.114
  ProcVersionSignature: Ubuntu 4.4.0-89.112-generic 4.4.76
  Uname: Linux 4.4.0-89-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  ra059746   2176 F pulseaudio
  Date: Sun Aug 13 23:30:30 2017
  ErrorMessage: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  HibernationDevice: RESUME=UUID=26cb4e4c-de55-4871-a29e-e47c9cf17400
  InstallationDate: Installed on 2016-04-22 (478 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Houter Oro PC
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-89-generic root=/dev/sda8 ro 
quiet splash vt.handoff=7
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  RelatedPackageVersions: grub-pc 2.02~beta2-36ubuntu3.12
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: yes
  SourcePackage: apt
  Title: package linux-image-4.4.0-91-generic 4.4.0-91.114 failed to 
install/upgrade: run-parts: /etc/kernel/postinst.d/apt-auto-removal exited with 
return code 2
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/15/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.02
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: Oro PC
  dmi.board.vendor: Houter
  dmi.board.version: To be filled by O.E.M.
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 10
  dmi.chassis.vendor: Houter
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.02:bd12/15/2010:svnHouter:pnOroPC:pvrTobefilledbyO.E.M.:rvnHouter:rnOroPC:rvrTobefilledbyO.E.M.:cvnHouter:ct10:cvrToBeFilledByO.E.M.:
  dmi.product.name: Oro PC
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Houter

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

[Touch-packages] [Bug 1365375] Re: package libc6-dev-i386 (not installed) failed to install/upgrade: trying to overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 2.19-0ubuntu6.3

[Charles McColm]

I second Ben's comment, we're almost 3 years on with a severe bug and
it's still in Ubuntu 16.04.

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

Title:
  package libc6-dev-i386 (not installed) failed to install/upgrade:
  trying to overwrite '/usr/include/gnu', which is also in package libc6
  -dev-amd64 2.19-0ubuntu6.3

Status in eglibc package in Ubuntu:
  Confirmed

Bug description:
  apt-get install gcc-multilib broke it!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libc6-dev-i386 (not installed)
  ProcVersionSignature: Ubuntu 3.13.0-35.62-generic 3.13.11.6
  Uname: Linux 3.13.0-35-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.3
  Architecture: amd64
  Date: Thu Sep  4 08:50:46 2014
  DpkgTerminalLog:
   Preparing to unpack .../libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb ...
   Unpacking libc6-dev-i386 (2.19-0ubuntu6.3) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libc6-dev-i386_2.19-0ubuntu6.3_amd64.deb (--unpack):
    trying to overwrite '/usr/include/gnu', which is also in package 
libc6-dev-amd64 2.19-0ubuntu6.3
  DuplicateSignature: package:libc6-dev-i386:(not installed):trying to 
overwrite '/usr/include/gnu', which is also in package libc6-dev-amd64 
2.19-0ubuntu6.3
  ErrorMessage: trying to overwrite '/usr/include/gnu', which is also in 
package libc6-dev-amd64 2.19-0ubuntu6.3
  SourcePackage: eglibc
  Title: package libc6-dev-i386 (not installed) failed to install/upgrade: 
trying to overwrite '/usr/include/gnu', which is also in package 
libc6-dev-amd64 2.19-0ubuntu6.3
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1365375/+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 1612779] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  just updated ubuntu 16.04 to 16.10

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu5
  Architecture: amd64
  Date: Fri Aug 12 18:21:37 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-05-18 (85 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~pre3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-08-12 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1612779/+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 1615052] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Fri Aug 19 21:09:53 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-19 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu2
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-08-19 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1615052/+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 1605950] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  Confirmed

Bug description:
  A failure with triggers left unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 23 20:03:27 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-07-19 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~exp1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1605950/+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 1607167] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Testing on the Yakkety Sax (Yak) branch

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Wed Jul 27 23:53:29 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-05-30 (58 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~exp1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1607167/+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 1605896] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  Varios errores durante la actualización a 16.04 a 16.0.1

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  Date: Sat Jul 23 11:09:19 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-04-26 (87 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.9ubuntu2
   apt  1.3~exp1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-07-23 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1605896/+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 1619948] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  after upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  Uname: Linux 4.7.2-040702-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Sep  3 14:51:07 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-28 (6 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc4ubuntu1
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-09-03 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1619948/+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 1617611] Re: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems - leaving triggers unprocessed

[charles r.]

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

** This bug is no longer a duplicate of bug 1605950
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed
** This bug has been marked a duplicate of bug 1551623
   package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency problems 
- leaving triggers unprocessed

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

Title:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in gconf package in Ubuntu:
  New

Bug description:
  package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

  ProblemType: Package
  DistroRelease: Ubuntu 16.10
  Package: gconf2 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-36.55-generic 4.4.16
  Uname: Linux 4.4.0-36-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  Date: Sat Aug 27 12:28:39 2016
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2016-08-21 (6 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu1
   apt  1.3~rc2ubuntu3
  SourcePackage: gconf
  Title: package gconf2 3.2.6-3ubuntu6 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to yakkety on 2016-08-27 (0 days ago)
  mtime.conffile..etc.xdg.autostart.gsettings-data-convert.desktop: 
2016-08-23T20:57:41.165020

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gconf/+bug/1617611/+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 1701963] [NEW] package libjpeg-turbo8-dev (not installed) failed to install/upgrade: a tentar sobre-escrever '/usr/include/turbojpeg.h', que também está no pacote libjpeg-turbo:i

[Charles]

Public bug reported:

install alegro sound

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libjpeg-turbo8-dev (not installed)
ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
Uname: Linux 4.4.0-78-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.6
Architecture: amd64
Date: Sun Jul  2 18:03:26 2017
ErrorMessage: a tentar sobre-escrever '/usr/include/turbojpeg.h', que também 
está no pacote libjpeg-turbo:i386 1.0.1-20100909
InstallationDate: Installed on 2017-01-15 (168 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.20
SourcePackage: libjpeg-turbo
Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: a 
tentar sobre-escrever '/usr/include/turbojpeg.h', que também está no pacote 
libjpeg-turbo:i386 1.0.1-20100909
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  package libjpeg-turbo8-dev (not installed) failed to install/upgrade:
  a tentar sobre-escrever '/usr/include/turbojpeg.h', que também está no
  pacote libjpeg-turbo:i386 1.0.1-20100909

Status in libjpeg-turbo package in Ubuntu:
  New

Bug description:
  install alegro sound

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libjpeg-turbo8-dev (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-78.99-generic 4.4.62
  Uname: Linux 4.4.0-78-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Sun Jul  2 18:03:26 2017
  ErrorMessage: a tentar sobre-escrever '/usr/include/turbojpeg.h', que também 
está no pacote libjpeg-turbo:i386 1.0.1-20100909
  InstallationDate: Installed on 2017-01-15 (168 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: libjpeg-turbo
  Title: package libjpeg-turbo8-dev (not installed) failed to install/upgrade: 
a tentar sobre-escrever '/usr/include/turbojpeg.h', que também está no pacote 
libjpeg-turbo:i386 1.0.1-20100909
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1701963/+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 1700670] [NEW] package systemd 229-4ubuntu4 failed to install/upgrade: unable to make backup link of './bin/journalctl' before installing new version: Input/output error

[Charles Frank]

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

Public bug reported:

internal system error

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu4
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
CasperVersion: 1.376
Date: Mon Jun 26 22:58:19 2017
DpkgTerminalLog:
 Preparing to unpack .../systemd_229-4ubuntu17_amd64.deb ...
 Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
 dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu17_amd64.deb (--unpack):
  unable to make backup link of './bin/journalctl' before installing new 
version: Input/output error
DuplicateSignature:
 Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
 dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu17_amd64.deb (--unpack):
  unable to make backup link of './bin/journalctl' before installing new 
version: Input/output error
ErrorMessage: unable to make backup link of './bin/journalctl' before 
installing new version: Input/output error
JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', 
'--lines=1000'] failed with exit code -7:
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard p6719c
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.10ubuntu1
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 
 3 overridden configuration files found.
Title: package systemd 229-4ubuntu4 failed to install/upgrade: unable to make 
backup link of './bin/journalctl' before installing new version: Input/output 
error
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/28/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6.11
dmi.board.name: 2AB1
dmi.board.vendor: FOXCONN
dmi.board.version: 1.00
dmi.chassis.asset.tag: MXX1070J1T
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6719c:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: p6719c
dmi.sys.vendor: Hewlett-Packard

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

Title:
  package systemd 229-4ubuntu4 failed to install/upgrade: unable to make
  backup link of './bin/journalctl' before installing new version:
  Input/output error

Status in systemd package in Ubuntu:
  New

Bug description:
  internal system error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  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
  CasperVersion: 1.376
  Date: Mon Jun 26 22:58:19 2017
  DpkgTerminalLog:
   Preparing to unpack .../systemd_229-4ubuntu17_amd64.deb ...
   Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu17_amd64.deb (--unpack):
unable to make backup link of './bin/journalctl' before installing new 
version: Input/output error
  DuplicateSignature:
   Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu17_amd64.deb (--unpack):
unable to make backup link of './bin/journalctl' before installing new 
version: Input/output error
  ErrorMessage: unable to make backup link of './bin/journalctl' before 
installing new version: Input/output error
  JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', 
'--lines=1000'] failed with exit code -7:
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: Hewlett-Packard p6719c
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/syste

[Touch-packages] [Bug 1700282] [NEW] package systemd 229-4ubuntu4 failed to install/upgrade: unable to make backup link of './bin/journalctl' before installing new version: Input/output error

[Charles Frank]

Public bug reported:

tried upgrading to 16.04.2 got system error during upgrade

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: systemd 229-4ubuntu4
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
CasperVersion: 1.376
Date: Sat Jun 24 17:43:55 2017
DpkgTerminalLog:
 Preparing to unpack .../systemd_229-4ubuntu17_amd64.deb ...
 Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
 dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu17_amd64.deb (--unpack):
  unable to make backup link of './bin/journalctl' before installing new 
version: Input/output error
DuplicateSignature:
 Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
 dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu17_amd64.deb (--unpack):
  unable to make backup link of './bin/journalctl' before installing new 
version: Input/output error
ErrorMessage: unable to make backup link of './bin/journalctl' before 
installing new version: Input/output error
JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', 
'--lines=1000'] failed with exit code -7:
LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: Hewlett-Packard p6719c
ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.2
 apt  1.2.10ubuntu1
SourcePackage: systemd
SystemdDelta:
 [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
 [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debian.conf
 [EXTENDED]   /etc/systemd/system/display-manager.service → 
/lib/systemd/system/display-manager.service.d/xdiagnose.conf
 
 3 overridden configuration files found.
Title: package systemd 229-4ubuntu4 failed to install/upgrade: unable to make 
backup link of './bin/journalctl' before installing new version: Input/output 
error
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/28/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 6.11
dmi.board.name: 2AB1
dmi.board.vendor: FOXCONN
dmi.board.version: 1.00
dmi.chassis.asset.tag: MXX1070J1T
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr6.11:bd12/28/2011:svnHewlett-Packard:pnp6719c:pvr:rvnFOXCONN:rn2AB1:rvr1.00:cvnHewlett-Packard:ct3:cvr:
dmi.product.name: p6719c
dmi.sys.vendor: Hewlett-Packard

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

Title:
  package systemd 229-4ubuntu4 failed to install/upgrade: unable to make
  backup link of './bin/journalctl' before installing new version:
  Input/output error

Status in systemd package in Ubuntu:
  New

Bug description:
  tried upgrading to 16.04.2 got system error during upgrade

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-4ubuntu4
  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
  CasperVersion: 1.376
  Date: Sat Jun 24 17:43:55 2017
  DpkgTerminalLog:
   Preparing to unpack .../systemd_229-4ubuntu17_amd64.deb ...
   Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu17_amd64.deb (--unpack):
unable to make backup link of './bin/journalctl' before installing new 
version: Input/output error
  DuplicateSignature:
   Unpacking systemd (229-4ubuntu17) over (229-4ubuntu4) ...
   dpkg: error processing archive 
/var/cache/apt/archives/systemd_229-4ubuntu17_amd64.deb (--unpack):
unable to make backup link of './bin/journalctl' before installing new 
version: Input/output error
  ErrorMessage: unable to make backup link of './bin/journalctl' before 
installing new version: Input/output error
  JournalErrors: Error: command ['journalctl', '-b', '--priority=warning', 
'--lines=1000'] failed with exit code -7:
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  MachineType: Hewlett-Packard p6719c
  ProcKernelCmdLine: file=/cdrom/preseed/hostname.seed boot=casper 
initrd=/casper/initrd.lz quiet splash --- maybe-ubiquity
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.10ubuntu1
  SourcePackage: systemd
  SystemdDelta:
   [EXTENDED]   /lib/systemd/system/systemd-timesyncd.service → 
/lib/systemd/system/systemd-timesyncd.service.d/disable-with-time-daemon.conf
   [EXTENDED]   /lib/systemd/system/rc-local.service → 
/lib/systemd/system/rc-local.service.d/debi

[Touch-packages] [Bug 1695752] [NEW] package shared-mime-info 1.8-1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 139

[Charles Gilley]

Public bug reported:

This is from the 17.04 32 bit ISO.  All of the suggested bugs are from
2011.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: shared-mime-info 1.8-1
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic i686
ApportVersion: 2.20.4-0ubuntu4
Architecture: i386
Date: Sun Jun  4 11:40:39 2017
ErrorMessage: subprocess installed post-installation script returned error exit 
status 139
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: shared-mime-info
Title: package shared-mime-info 1.8-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: shared-mime-info (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 zesty

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

Title:
  package shared-mime-info 1.8-1 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 139

Status in shared-mime-info package in Ubuntu:
  New

Bug description:
  This is from the 17.04 32 bit ISO.  All of the suggested bugs are from
  2011.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: shared-mime-info 1.8-1
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  Date: Sun Jun  4 11:40:39 2017
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 139
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: shared-mime-info
  Title: package shared-mime-info 1.8-1 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 139
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/shared-mime-info/+bug/1695752/+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 1695750] [NEW] package dictionaries-common 1.27.2 failed to install/upgrade: subprocess installed post-installation script was killed by signal (Aborted), core dumped

[Charles Gilley]

Public bug reported:

Well, no real idea if this is a bug or not, but Ubuntu sent me here.

I'm trying to resurrect and older system that had Ubuntu 14 on it.
Started with 17.04 64 bit and consistently ran into hangs during the
upgrade and updates.  Saw a relevant post - so I decided to try the
32bit ISO.  Here I am.  Reported some sort of unpleasantness during the
install with languages.

No warm Penguin fuzzies yet.

ProblemType: Package
DistroRelease: Ubuntu 17.04
Package: dictionaries-common 1.27.2
ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
Uname: Linux 4.10.0-19-generic i686
ApportVersion: 2.20.4-0ubuntu4
Architecture: i386
Date: Sun Jun  4 11:40:23 2017
ErrorMessage: subprocess installed post-installation script was killed by 
signal (Aborted), core dumped
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.10ubuntu2
 apt  1.4
SourcePackage: dictionaries-common
Title: package dictionaries-common 1.27.2 failed to install/upgrade: subprocess 
installed post-installation script was killed by signal (Aborted), core dumped
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: dictionaries-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 zesty

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

Title:
  package dictionaries-common 1.27.2 failed to install/upgrade:
  subprocess installed post-installation script was killed by signal
  (Aborted), core dumped

Status in dictionaries-common package in Ubuntu:
  New

Bug description:
  Well, no real idea if this is a bug or not, but Ubuntu sent me here.

  I'm trying to resurrect and older system that had Ubuntu 14 on it.
  Started with 17.04 64 bit and consistently ran into hangs during the
  upgrade and updates.  Saw a relevant post - so I decided to try the
  32bit ISO.  Here I am.  Reported some sort of unpleasantness during
  the install with languages.

  No warm Penguin fuzzies yet.

  ProblemType: Package
  DistroRelease: Ubuntu 17.04
  Package: dictionaries-common 1.27.2
  ProcVersionSignature: Ubuntu 4.10.0-19.21-generic 4.10.8
  Uname: Linux 4.10.0-19-generic i686
  ApportVersion: 2.20.4-0ubuntu4
  Architecture: i386
  Date: Sun Jun  4 11:40:23 2017
  ErrorMessage: subprocess installed post-installation script was killed by 
signal (Aborted), core dumped
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.10ubuntu2
   apt  1.4
  SourcePackage: dictionaries-common
  Title: package dictionaries-common 1.27.2 failed to install/upgrade: 
subprocess installed post-installation script was killed by signal (Aborted), 
core dumped
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dictionaries-common/+bug/1695750/+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 1100546] Re: Power indicator favours 'not present' mouse over laptop battery level

[Charles Kerr]

** Changed in: indicator-power (Ubuntu)
 Assignee: Charles Kerr (charlesk) => (unassigned)

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

Title:
  Power indicator favours 'not present' mouse over laptop battery level

Status in indicator-power package in Ubuntu:
  Fix Released
Status in indicator-power source package in Xenial:
  New

Bug description:
  [Impact]

   * It's very annoying to see the mouse battery instead of the system
  battery on indicator bar.

  [Test Case]

   * Using Logitech Wireless Mouse M325 or other wireless mouse can see
  this issue.

  [Regression Potential]

   * No regression as I know.

  [Other Info]
   
   * This is a SRU request for Ubuntu 16.04 (xenial).

  The power indicator shows the battery level for cordless mice and
  keyboards, even when it cannot identify the battery level. This is a
  problem as it seems to favour showing a "not present" mouse status
  over the laptop battery level in the top bar.

  I haven't done a good job of explaining it, so check out the
  screenshot - it will explain all :)

  Basically, the laptop battery should be shown in the top bar if the 
mouse/keyboard is "not present".
  Also hiding the mouse and keyboard when the battery level is unknown would 
also be useful too :)

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: indicator-power 12.10.6daily12.11.21.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-0.3-generic 3.8.0-rc3
  Uname: Linux 3.8.0-0-generic x86_64
  ApportVersion: 2.8-0ubuntu1
  Architecture: amd64
  Date: Thu Jan 17 10:11:16 2013
  InstallationDate: Installed on 2012-12-14 (33 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121214)
  MarkForUpload: True
  SourcePackage: indicator-power
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-power/+bug/1100546/+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 1674389] Re: Session Indicator's "Suspend" button has no effect in Unity 8

[Charles Kerr]

Might be a two-parter bug.

On the indicator-session side, we need to handle "challenge" as a
response to CanSuspend / CanHibernate calls and, when calling
suspend/hibernate, allow interactivity. This is in the fix-suspend-on-u8
branch.

Even after this is done, u8's challenge prompt is the lockscreen, so the 
unintuitive UX is that you have to (appear to) unlock in order to suspend. So 
in u8,
1. we should consider whether a password prompt should be necessary for 
suspend, and
2. if prompt is necessary, Calls to login1.Suspend(interactive=True) should 
probably be handled more elegantly than showing the lockscreen prompt


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

** Also affects: unity8 (Ubuntu)
   Importance: Undecided
   Status: New

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

Title:
  Session Indicator's "Suspend" button has no effect in Unity 8

Status in indicator-session package in Ubuntu:
  Confirmed
Status in unity8 package in Ubuntu:
  New

Bug description:
  Testing Unity 8 from a Zesty nightly iso install on March 17 2017.

  When clicking on the "Suspend" button in the session indicator,
  nothing happens.

  This may or may not be an indicator-session issue. I need to triage
  this and see where the breakage is, e.g. does it work in Unity 7 on
  Zesty, and are there are any DBus signatures that have changed in
  Zesty that would cause this

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1674389/+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 1664426] Re: Can no longer play wma files with Ubuntu 16.04

[Charles Mikesell]

Thanks for fixing. Ran update today on all units and am very pleased to
be playing wma files again!!!

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

Title:
  Can no longer play wma files with Ubuntu 16.04

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Multiple (7) computers were working just fine until a recent update
  apparently removed the plug-in.

  Perhaps you could provide us with an update to put the plug-in back in
  place.(?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1664426/+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 1650961] Re: ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS endpoint with error -106

[Charles de Bueger]

I got this weird messages on a terminal today. Ubuntu had been acting
strangely, (a zombie process, everything grinding to a halt). The
messages just appeared - nothing else was running in the terminal:

776:3815:0216/221717.542851:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -118
[3776:3815:0216/222049.474716:ERROR:socket_stream.cc(101)] Socket was 
disconnected, closing input stream
[3776:3815:0216/222049.474737:ERROR:socket_stream.cc(210)] Closing stream with 
result -100
[3776:3815:0216/57.894857:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -118
[3776:3815:0216/223017.423604:ERROR:connection_handler_impl.cc(402)] Received 
message of invalid type 84
[3776:3815:0216/223225.830859:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -118
[1:1:0216/223733.894859:ERROR:KeyboardEventManager.cpp(424)] Not implemented 
reached in static bool blink::KeyboardEventManager::currentCapsLockState()
[1:1:0216/223734.619503:ERROR:KeyboardEventManager.cpp(424)] Not implemented 
reached in static bool blink::KeyboardEventManager::currentCapsLockState()
[1:1:0216/223738.335086:ERROR:KeyboardEventManager.cpp(424)] Not implemented 
reached in static bool blink::KeyboardEventManager::currentCapsLockState()
[1:1:0216/223738.338407:ERROR:KeyboardEventManager.cpp(424)] Not implemented 
reached in static bool blink::KeyboardEventManager::currentCapsLockState()

I have never seen the capslock thing before either - not sure if it's
related. I am on Ubuntu 16.04

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

Title:
  ERROR:connection_factory_impl.cc(367)] Failed to connect to MCS
  endpoint with error -106

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux
  caravena@caravena-530U3C-530U4C:~$ 
[12375:12409:1218/134054:ERROR:nss_util.cc(809)] After loading Root Certs, 
loaded==false: NSS error code: -8018
  Se creó una nueva ventana en la sesión existente del navegador.
  [7185:7220:1218/142107:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -106
  [7185:7318:1218/142111:ERROR:get_updates_processor.cc(242)] 
PostClientToServerMessage() failed during GetUpdates
  [7185:7318:1218/142115:ERROR:get_updates_processor.cc(242)] 
PostClientToServerMessage() failed during GetUpdates
  [7185:7220:1218/142117:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -105
  [7185:7220:1218/143613:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -106
  [7185:7318:1218/144540:ERROR:get_updates_processor.cc(242)] 
PostClientToServerMessage() failed during GetUpdates
  [7185:7220:1218/145430:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -106
  [7185:7318:1218/162533:ERROR:get_updates_processor.cc(242)] 
PostClientToServerMessage() failed during GetUpdates
  [7185:7220:1218/162540:ERROR:connection_factory_impl.cc(367)] Failed to 
connect to MCS endpoint with error -21
  [7185:7318:1218/162540:ERROR:get_updates_processor.cc(242)] 
PostClientToServerMessage() failed during GetUpdates
  caravena@caravena-530U3C-530U4C:~$ ubuntu-bug linux
  caravena@caravena-530U3C-530U4C:~$ 
[18327:18362:1218/165822:ERROR:nss_util.cc(809)] After loading Root Certs, 
loaded==false: NSS error code: -8018

  ProblemType: Bug
  DistroRelease: Ubuntu 17.04
  Package: apport 2.20.4-0ubuntu1
  ProcVersionSignature: Ubuntu 4.9.0-11.12-generic 4.9.0
  Uname: Linux 4.9.0-11-generic x86_64
  ApportVersion: 2.20.4-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Sun Dec 18 17:32:53 2016
  InstallationDate: Installed on 2015-07-26 (511 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha amd64 (20150723)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: Upgraded to zesty on 2016-10-29 (50 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/apport/+bug/1650961/+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 1633319] Re: memory leak in indicator-datetime

[Julien-Charles Lévesque]

Killed my computer as soon as I activated my google online account.

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1664426] [NEW] Can no longer play wma files with Ubuntu 16.04

[Charles Mikesell]

Public bug reported:

Multiple (7) computers were working just fine until a recent update
apparently removed the plug-in.

Perhaps you could provide us with an update to put the plug-in back in
place.(?)

** Affects: gstreamer1.0 (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Can no longer play wma files with Ubuntu 16.04

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Multiple (7) computers were working just fine until a recent update
  apparently removed the plug-in.

  Perhaps you could provide us with an update to put the plug-in back in
  place.(?)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gstreamer1.0/+bug/1664426/+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 1635360] Re: res_query.c:262: __libc_res_nquery: Assertion

[Charles F. Stephens]

Ping: has anyone looked at this ticket yet?  It seems like a trivial fix
to incorporate into eglibc.  Thanks.

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

Title:
  res_query.c:262: __libc_res_nquery: Assertion

Status in eglibc package in Ubuntu:
  New

Bug description:
  Debian report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816669
  Upstream report https://sourceware.org/bugzilla/show_bug.cgi?id=19791

  Whenever, in resolv.conf, there are both IPv6 and IPv4 server entries
  and either protocol is not routable on a system, resolv throws an
  assertion:

  res_query.c:262: __libc_res_nquery: Assertion `(hp != ((void *)0)) &&
  (hp2 != ((void *)0))' failed.

  This problem was introduced as a side-effect of patching
  CVE-2015-7547.

  There is a fix upstream:

  commit 10d268070a8aa9a878668e7f060e92ed668de146
  Author: Florian Weimer 
  Date:   Fri Mar 25 11:49:51 2016 +0100

  resolv: Always set *resplen2 out parameter in send_dg [BZ #19791]
  
  Since commit 44d20bca52ace85850012b0ead37b360e3ecd96e (Implement
  second fallback mode for DNS requests), there is a code path which
  returns early, before *resplen2 is initialized.  This happens if the
  name server address is immediately recognized as invalid (because of
  lack of protocol support, or if it is a broadcast address such
  255.255.255.255, or another invalid address).
  
  If this happens and *resplen2 was non-zero (which is the case if a
  previous query resulted in a failure), __libc_res_nquery would reuse
  an existing second answer buffer.  This answer has been previously
  identified as unusable (for example, it could be an NXDOMAIN
  response).  Due to the presence of a second answer, no name server
  switching will occur.  The result is a name resolution failure,
  although a successful resolution would have been possible if name
  servers have been switched and queries had proceeded along the search
  path.
  
  The above paragraph still simplifies the situation.  Before glibc
  2.23, if the second answer needed malloc, the stub resolver would
  still attempt to reuse the second answer, but this is not possible
  because __libc_res_nsearch has freed it, after the unsuccessful call
  to __libc_res_nquerydomain, and set the buffer pointer to NULL.  This
  eventually leads to an assertion failure in __libc_res_nquery:
  
/* Make sure both hp and hp2 are defined */
assert((hp != NULL) && (hp2 != NULL));
  
  If assertions are disabled, the consequence is a NULL pointer
  dereference on the next line.
  
  Starting with glibc 2.23, as a result of commit
  e9db92d3acfe1822d56d11abcea5bfc4c41cf6ca (CVE-2015-7547: getaddrinfo()
  stack-based buffer overflow (Bug 18665)), the second answer is always
  allocated with malloc.  This means that the assertion failure happens
  with small responses as well because there is no buffer to reuse, as
  soon as there is a name resolution failure which triggers a search for
  an answer along the search path.
  
  This commit addresses the issue by ensuring that *resplen2 is
  initialized before the send_dg function returns.
  
  This commit also addresses a bug where an invalid second reply is
  incorrectly returned as a valid to the caller.
  
  (cherry picked from commit b66d837bb5398795c6b0f651bd5a5d66091d8577)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/eglibc/+bug/1635360/+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 1530807] Re: Bluetooth cannot be activated on several devices

[Charles Kerr]

Reopening for workitem found by dobey to see if
https://code.launchpad.net/~morphis/indicator-bluetooth/fix-
lp1530807/+merge/290022 should still be landed

** Changed in: indicator-bluetooth (Ubuntu)
   Status: Fix Committed => Triaged

** Changed in: indicator-bluetooth (Ubuntu)
 Assignee: Charles Kerr (charlesk) => Rodney Dawes (dobey)

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

Title:
  Bluetooth cannot be activated on several devices

Status in The Avila project:
  Fix Committed
Status in Canonical System Image:
  Fix Committed
Status in Canonical Pocket Desktop:
  Fix Committed
Status in indicator-bluetooth package in Ubuntu:
  Triaged
Status in ubuntu-system-settings package in Ubuntu:
  Confirmed

Bug description:
  Using RC proposed 04/01/2016 bluetooth cannot be enabled.

  Tested on a nexus 7.

  Expected behavior:
  Bluetooth slider is moved to on
  Bluetooth activates
  Available devices appear in the list

  Experienced behavior: 
  Bluetooth slider is moved to on
  Activity spinners appear 
  Bluetooth slider moves to off.

To manage notifications about this bug go to:
https://bugs.launchpad.net/avila/+bug/1530807/+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 1646530] [NEW] network-manager dns-search

[Charles]

Public bug reported:

NetworkManager is ignoring the ipv4.dns-search when using VPN.

This was not the case with 14.04 LTS.

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

Title:
  network-manager dns-search

Status in network-manager package in Ubuntu:
  New

Bug description:
  NetworkManager is ignoring the ipv4.dns-search when using VPN.

  This was not the case with 14.04 LTS.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1646530/+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 1642989] [NEW] indicators should use 'com.canonical.indicators.link' type for Settings links

[Charles Kerr]

Public bug reported:

http://bazaar.launchpad.net/~unity-
team/unity8/trunk/view/head:/qml/Panel/Indicators/MenuItemFactory.qml
has this code:

> if (modelData.action !== undefined && modelData.action.indexOf("settings") > 
> -1) {
>   // FIXME : At the moment, the indicators aren't using
>   // com.canonical.indicators.link for settings menu. Need to fudge it.
>   return linkMenu;
> }

We should set the type of settings menuitems to
'com.canonical.indicators.link' so that this hack can be removed.

** Affects: indicator-bluetooth (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: indicator-datetime (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: indicator-location (Ubuntu)
 Importance: Undecided
 Status: New

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

** Affects: indicator-power (Ubuntu)
 Importance: Undecided
 Status: New

** Affects: indicator-session (Ubuntu)
 Importance: Medium
 Status: Triaged

** Affects: indicator-sound (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

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

** Also affects: indicator-location (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/1642989

Title:
  indicators should use 'com.canonical.indicators.link' type for
  Settings links

Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  Triaged
Status in indicator-sound package in Ubuntu:
  New

Bug description:
  http://bazaar.launchpad.net/~unity-
  team/unity8/trunk/view/head:/qml/Panel/Indicators/MenuItemFactory.qml
  has this code:

  > if (modelData.action !== undefined && modelData.action.indexOf("settings") 
> -1) {
  >   // FIXME : At the moment, the indicators aren't using
  >   // com.canonical.indicators.link for settings menu. Need to fudge it.
  >   return linkMenu;
  > }

  We should set the type of settings menuitems to
  'com.canonical.indicators.link' so that this hack can be removed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1642989/+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 1611466] Re: Calendar crashes on ESC typing.

[Charles Kerr]

I'm marking this bug as closed due to your last comment on no longer
being able to reproduce it, either through an update or some other
reason. If the problem reappears for you in the future, please submit a
backtrace using the method linked to by seb128 in the comment above.
Thank you again for taking the time to report this bug and helping to
make Ubuntu better. Please submit any future bugs you may find.

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Calendar crashes on ESC typing.

Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  When you click on date, it opens the calendar, if you type the ESC
  button on keyboard, the graphical interface crashes and in a few
  seconds it restart. During this few seconds or a minute, all the
  system stay frozen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1611466/+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 1639472] Re: Alarm should provide GAction for toggling them

[Charles Kerr]

Marco, could you explain more what you're asking for here? A way to
toggle on/off whether alarms will go off?

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

Title:
  Alarm should provide GAction for toggling them

Status in indicator-datetime package in Ubuntu:
  Triaged

Bug description:
  Indicator-datetime should provide a GAaction for toggling the
  activation of alarms.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1639472/+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 1638708] Re: Hardcoded paths in data/*.desktop.in need Snappy prefixing

[Charles Kerr]

** Description changed:

- Noticed and reported by mterry in https://code.launchpad.net/~mterry
- /indicator-sound/snap-root/+merge/308125:
+ Noticed and reported by mterry in several indicator patches, e.g.
+ :
  
  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  > I think it makes more sense to update the code that reads those
  > files to do the prefixing.

** Summary changed:

- Hardcoded paths in data/*.desktop.in need Snappy prefixing
+ Hardcoded paths in desktop files need to be processed need $SNAP prefixing

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

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

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

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

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

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

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

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

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

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

** Description changed:

  Noticed and reported by mterry in several indicator patches, e.g.
  :
  
  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  > I think it makes more sense to update the code that reads those
  > files to do the prefixing.
+ 
+ There is also an umbrella ticket for hardcoded paths in the u8 snap:
+ 

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

Title:
  Hardcoded paths in desktop files need to be processed need $SNAP
  prefixing

Status in indicator-application package in Ubuntu:
  New
Status in indicator-bluetooth package in Ubuntu:
  New
Status in indicator-datetime package in Ubuntu:
  New
Status in indicator-location package in Ubuntu:
  New
Status in indicator-messages package in Ubuntu:
  New
Status in indicator-network package in Ubuntu:
  New
Status in indicator-power package in Ubuntu:
  New
Status in indicator-printers package in Ubuntu:
  New
Status in indicator-session package in Ubuntu:
  New
Status in indicator-sound package in Ubuntu:
  Triaged
Status in indicator-transfer package in Ubuntu:
  New

Bug description:
  Noticed and reported by mterry in several indicator patches, e.g.
  :

  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  > I think it makes more sense to update the code that reads those
  > files to do the prefixing.

  There is also an umbrella ticket for hardcoded paths in the u8 snap:
  

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-application/+bug/1638708/+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 1638710] Re: Hardcoded paths need Snappy prefixing

[Charles Kerr]

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

D'oh, user error. This is the same as bug #1638708

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

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

** No longer affects: indicator-transfer (Ubuntu)

** No longer affects: indicator-printers (Ubuntu)

** No longer affects: indicator-power (Ubuntu)

** Tags removed: unity8-snap

** This bug has been marked a duplicate of bug 1638708
   Hardcoded paths in desktop files need to be processed need $SNAP prefixing

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

Title:
  Hardcoded paths need Snappy prefixing

Status in indicator-session package in Ubuntu:
  New

Bug description:
  Noticed and reported by mterry in https://code.launchpad.net/~mterry
  /indicator-transfer/snap-root/+merge/308128:

  > There are also two hardcoded paths in the data/*.desktop.in files.
  > But that's a static desktop file, so $SNAP isn't appropriate.
  >
  > I'm not sure what the best solution for those is, but presumably
  > it would lie in whichever component consumes the desktop file
  > not this package.

  As mterry points out this is probably not an issue for indicator-
  transfer to fix, this ticket is being filed so that we track the issue
  & see if there's anything that can be done locally or to reassign to
  proper owner

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-session/+bug/1638710/+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 1443203] Re: GUFW blocks all incoming VNC connections even if rules allow

[D. Charles Pyle]

Unfortunately, I have ceased using Windows XP, and the computer from
which I used VNC connections also has ceased to function.  I am now
using a DisplayLink device to give me a third screen rather than using
VNC to access a virtual machine from another machine to do it.

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

Title:
  GUFW blocks all incoming VNC connections even if rules allow

Status in ufw package in Ubuntu:
  Incomplete

Bug description:
  I am having a problem with GUFW.  I have it set to block incoming
  connections from everything.  I then set rules to allow incoming
  connections from a VNC client on my local network to a VMWare Player
  VNC setup but no matter what I do with those rules, I cannot connect
  to the VNC server on my machine unless I change the setting for my
  profile to Allow for everything.  Making and applying rules has no
  effect if the "Incoming" setting at the top of the application is set
  to Deny or Reject.

  The only other option is to turn off the firewall entirely for a
  moment for the VNC client to connect, and then turn it back on again
  once a connection is established.  Allowing all incoming connections
  for even a few moments just to use VNC on one port is a security risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ufw/+bug/1443203/+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 1623666] Re: iOS10 will not connect to Ubuntu

[Charles]

Also appears to affect Ubuntu 14.04 Trust Tahr.  I was previously able
to connect my iPhone 5S and browse the file system, now it gives the
error message "Unable to access """ Unhandled Lockdown error (-16).

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

Title:
  iOS10 will not connect to Ubuntu

Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libimobiledevice/+bug/1623666/+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 1635360] [NEW] res_query.c:262: __libc_res_nquery: Assertion

[Charles F. Stephens]

Public bug reported:

Debian report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816669
Upstream report https://sourceware.org/bugzilla/show_bug.cgi?id=19791

Whenever, in resolv.conf, there are both IPv6 and IPv4 server entries
and either protocol is not routable on a system, resolv throws an
assertion:

res_query.c:262: __libc_res_nquery: Assertion `(hp != ((void *)0)) &&
(hp2 != ((void *)0))' failed.

This problem was introduced as a side-effect of patching CVE-2015-7547.

There is a fix upstream:

commit 10d268070a8aa9a878668e7f060e92ed668de146
Author: Florian Weimer 
Date:   Fri Mar 25 11:49:51 2016 +0100

resolv: Always set *resplen2 out parameter in send_dg [BZ #19791]

Since commit 44d20bca52ace85850012b0ead37b360e3ecd96e (Implement
second fallback mode for DNS requests), there is a code path which
returns early, before *resplen2 is initialized.  This happens if the
name server address is immediately recognized as invalid (because of
lack of protocol support, or if it is a broadcast address such
255.255.255.255, or another invalid address).

If this happens and *resplen2 was non-zero (which is the case if a
previous query resulted in a failure), __libc_res_nquery would reuse
an existing second answer buffer.  This answer has been previously
identified as unusable (for example, it could be an NXDOMAIN
response).  Due to the presence of a second answer, no name server
switching will occur.  The result is a name resolution failure,
although a successful resolution would have been possible if name
servers have been switched and queries had proceeded along the search
path.

The above paragraph still simplifies the situation.  Before glibc
2.23, if the second answer needed malloc, the stub resolver would
still attempt to reuse the second answer, but this is not possible
because __libc_res_nsearch has freed it, after the unsuccessful call
to __libc_res_nquerydomain, and set the buffer pointer to NULL.  This
eventually leads to an assertion failure in __libc_res_nquery:

/* Make sure both hp and hp2 are defined */
assert((hp != NULL) && (hp2 != NULL));

If assertions are disabled, the consequence is a NULL pointer
dereference on the next line.

Starting with glibc 2.23, as a result of commit
e9db92d3acfe1822d56d11abcea5bfc4c41cf6ca (CVE-2015-7547: getaddrinfo()
stack-based buffer overflow (Bug 18665)), the second answer is always
allocated with malloc.  This means that the assertion failure happens
with small responses as well because there is no buffer to reuse, as
soon as there is a name resolution failure which triggers a search for
an answer along the search path.

This commit addresses the issue by ensuring that *resplen2 is
initialized before the send_dg function returns.

This commit also addresses a bug where an invalid second reply is
incorrectly returned as a valid to the caller.

(cherry picked from commit b66d837bb5398795c6b0f651bd5a5d66091d8577)

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

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

Title:
  res_query.c:262: __libc_res_nquery: Assertion

Status in eglibc package in Ubuntu:
  New

Bug description:
  Debian report https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=816669
  Upstream report https://sourceware.org/bugzilla/show_bug.cgi?id=19791

  Whenever, in resolv.conf, there are both IPv6 and IPv4 server entries
  and either protocol is not routable on a system, resolv throws an
  assertion:

  res_query.c:262: __libc_res_nquery: Assertion `(hp != ((void *)0)) &&
  (hp2 != ((void *)0))' failed.

  This problem was introduced as a side-effect of patching
  CVE-2015-7547.

  There is a fix upstream:

  commit 10d268070a8aa9a878668e7f060e92ed668de146
  Author: Florian Weimer 
  Date:   Fri Mar 25 11:49:51 2016 +0100

  resolv: Always set *resplen2 out parameter in send_dg [BZ #19791]
  
  Since commit 44d20bca52ace85850012b0ead37b360e3ecd96e (Implement
  second fallback mode for DNS requests), there is a code path which
  returns early, before *resplen2 is initialized.  This happens if the
  name server address is immediately recognized as invalid (because of
  lack of protocol support, or if it is a broadcast address such
  255.255.255.255, or another invalid address).
  
  If this happens and *resplen2 was non-zero (which is the case if a
  previous query resulted in a failure), __libc_res_nquery would reuse
  an existing second answer buffer.  This answer has been previously
  identified as unusable (for example, it could be an NXDOMAIN
  response).  Due to the presence of a second answer, no name server
  switching will o

[Touch-packages] [Bug 1626767] Re: Tests should be re-enabled / fixed

[Charles Kerr]

Looks like there's still general test failure as of 13 Oct, see
https://code.launchpad.net/~pete-woods/indicator-network/lp1632275-fix-
memory-corruption/+merge/308379/comments/798923

CI is not productive on indicator-network until this is fixed...

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

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

Title:
  Tests should be re-enabled / fixed

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  we have multiple arches currently disabled for testing due to their
  flakyness. Investigate and re-enable.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1626767/+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 1634059] Re: indicator-datetime-service devours memory rendering system useless

[Charles Kerr]

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

** This bug is no longer a duplicate of bug 1633319
   memory leak in indicator-datetime
** This bug has been marked a duplicate of bug 1342123
   evolution-calendar-factory always running with high memory usage

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

Title:
  indicator-datetime-service devours memory rendering system useless

Status in indicator-datetime package in Ubuntu:
  New

Bug description:
  Upon upgrading to 16.10, yakkety yak, I cannot load Unity because the
  indicator-datetime-service devours memory at an incredible pace before
  being automatically killed, and restarting to devour all over again!

  The workaround I found is to open a virtual terminal 
  and then log into unity while quickly switching back to the the F1
  terminal.  I then repeatedly do "killall -KILL indicator-datetime-
  service" until it stops coming back.

  This is a major bug in that it renders the entire system unusable.  It
  happened on both my laptop and my desktop after upgrade to 16.10.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 17 11:02:54 2016
  InstallationDate: Installed on 2014-10-13 (735 days ago)
  InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923)
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1634059/+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 1633319] Re: memory leak in indicator-datetime

[Charles Kerr]

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

>From Jonathan's insights in comment 9, this sounds like a duplicate of
bug #1342123.

** This bug has been marked a duplicate of bug 1342123
   evolution-calendar-factory always running with high memory usage

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

Title:
  memory leak in indicator-datetime

Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  After upgrading from 16.04 to 16.10 on the System76 Serval WS
  indicator-datetime-service is consuming all the system memory from
  3.7GB up to 32 GB in 30 seconds. The system kills the indicator-
  datetime-service process and indicator-datetime-service restarts and
  memory consumption repeats until killed again. All swap memory is
  consumed in this pattern.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: indicator-datetime 15.10+16.10.20160820.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Uname: Linux 4.8.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Fri Oct 14 00:12:00 2016
  EcryptfsInUse: Yes
  SourcePackage: indicator-datetime
  UpgradeStatus: Upgraded to yakkety on 2016-10-14 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1633319/+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 1593924] Re: systemd-shim was not installed in 16.10 and now cannot purge or remove

[Julien-Charles Lévesque]

To me this seems to be the problem :

dpkg-divert: error: rename involves overwriting 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service' with
  different file 
'/usr/share/dbus-1/system-services/org.freedesktop.systemd1.service.systemd', 
not allowed

Why does the package try to do this if it is not allowed?

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

Title:
  systemd-shim was not installed in 16.10 and now cannot purge or remove

Status in libjpeg-turbo package in Ubuntu:
  Invalid

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libjpeg-turbo/+bug/1593924/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked

[Charles Kerr]

After looking through the code, Pat's thoughts in comment 14 seem right
to me.

For indicator-datetime's part, it can pass the system bus into the
object constructor instead of making an asynchronous call to fetch it.
This narrows the dangerous interval in datetime between wakeup and
calling requestSysState -- though, NB, I'm not able to reproduce this
bug in testing and so I'm not able to determine how much this change
ameliorates it.

Outside of indicator-datetime, this might be a question for repowerd wrt
ensuring that, after system wakeup, apps have a chance to respond to the
wakeup before the system goes back to sleep.

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1588526] Re: [mako] Alarm doesn't ring when screen locked

[Charles Kerr]

** Branch linked: lp:~charlesk/indicator-datetime/lp-1588526-remember-
system-bus

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

Title:
  [mako] Alarm doesn't ring when screen locked

Status in Canonical System Image:
  Incomplete
Status in Ubuntu Clock App:
  Confirmed
Status in indicator-datetime package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I noticed couple of time, difficult to reproduce that the alarm does
  not ring at the correct time but ring as soon the screen is on.

  Mako Rc-proposed bq-aquaris R324.

  Regards

  Edit : to make ring the phone i just need to wake up the phone and the
  alarm start to ring.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588526/+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 1630551] Re: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

[Charles Kerr]

** Information type changed from Private to Public

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

Title:
  indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()

Status in indicator-network package in Ubuntu:
  New

Bug description:
  Crash on startup

  ProblemType: Crash
  DistroRelease: Ubuntu 16.10
  Package: indicator-network 0.8.0+16.10.20160930.5-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic i686
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: i386
  Date: Wed Oct  5 12:38:48 2016
  ExecutablePath: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ProcCmdline: 
/usr/lib/i386-linux-gnu/indicator-network/indicator-network-secret-agent
  ProcEnviron:
   PATH=(custom, no user)
   LANGUAGE=en_GB:en
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/false
  SegvAnalysis:
   Segfault happened at: 0xb779beba :   mov0x4(%eax),%ebx
   PC (0xb779beba) ok
   source "0x4(%eax)" (0x0074) not located in a known VMA region (needed 
readable region)!
   destination "%ebx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: indicator-network
  Stacktrace:
   #0  do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfaa21eb, ref=0x0, 
result=0x4cd, scope=0x70, i=3807944636, version=0xb779c529 , 
flags=5, skip=0x1, type_class=-1226319944, undef_map=0xd62) at dl-lookup.c:361
   n = 
   list = 
   #1  0x in ?? ()
   No symbol table info available.
  StacktraceTop:
   do_lookup_x (undef_name=0x0, new_hash=1, old_hash=0xbfaa21eb, ref=0x0, 
result=0x4cd, scope=0x70, i=3807944636, version=0xb779c529 , 
flags=5, skip=0x1, type_class=-1226319944, undef_map=0xd62) at dl-lookup.c:361
   ?? ()
  Title: indicator-network-secret-agent crashed with SIGSEGV in do_lookup_x()
  UpgradeStatus: Upgraded to yakkety on 2016-09-26 (8 days ago)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1630551/+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 1554504] Re: Calendar reminder does not wake phone when airplane mode is enabled

[Charles Kerr]

Pat, yes we use the com.canonical.powerd interface's requestWakeup
method to wakeup the phone when a clock alarm or calendar event needs a
notification.

indicator-datetime doesn't have any airplane mode logic in it at all, so
I'm not sure what's going on there.

I'm not able to reproduce this on a n4 running 15.04 (r531) by turning
on airplane mode and trying calendar events and a clock-app alarm. Is
this issue reproducible for anyone?

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

** Changed in: indicator-datetime (Ubuntu)
   Status: Confirmed => Incomplete

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

Title:
  Calendar reminder does not wake phone when airplane mode is enabled

Status in Canonical System Image:
  Incomplete
Status in indicator-datetime package in Ubuntu:
  Incomplete

Bug description:
  If airplane mode is enabled, the phone seems to go into a deep sleep
  where it doesn't wake up for a calendar reminder. The reminder does
  not sound until the power button is pressed to wake the phone, in some
  cases this has been more than an hour after the reminder was scheduled
  for.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1554504/+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 1384354] Re: Should ellipsize events names

[Charles Kerr]

This should be handled in the rendering, rather than in the strings we
pass across the bus to Unity

** Package changed: indicator-datetime (Ubuntu) => unity8 (Ubuntu)

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

Title:
  Should ellipsize events names

Status in unity8 package in Ubuntu:
  Confirmed

Bug description:
  Using utopic, if you calendar contains an event with a long name the
  indicator menu is stretched to contain it which looks weird,
  ellipsizing those would be nice

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1384354/+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 1613561] Re: [MIR] thumbnailer

[Charles Kerr]

FWIW, I'm seeing very similar issues on indicator-network. It too uses
qdbus, and I'm seeing a high volume of test regressions on yakkety arm64
and ppc64el: https://bugs.launchpad.net/ubuntu/+source/indicator-
network/+bug/1626767

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

Title:
  [MIR] thumbnailer

Status in thumbnailer package in Ubuntu:
  Incomplete

Bug description:
  [Availability]
   * Available in universe

  [Rationale]
   * This package is required by many Ubuntu Touch applications and scopes, 
such as gallery app, music app, today scope, music scope, etc.

  [Security]
   * No known security issues at this time. It has been reviewed by security in 
the past for use on the phone.

  [Quality assurance]
   * This package has unit tests.

  [Dependencies]
   Most dependencies are already in main with the exception of the following:
   * libboost-filesystem-dev
   * libunity-api-dev (Bug #1613563)
   * persistent-cache-cpp-dev (Bug #1613560)

   Note that the package has other dependencies that are not in main,
  but these are used only for the tests and are not runtime
  dependencies.

  [Standards compliance]
   * This package uses cmake.

  [Maintenance]
   * This package is maintained by Canonical and actively in use on the phone 
images.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1613561/+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 1626767] Re: Tests should be re-enabled / fixed

[Charles Kerr]

Thumbnailer seems to be having similar issues:
https://bugs.launchpad.net/ubuntu/+source/thumbnailer/+bug/1613561

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

Title:
  Tests should be re-enabled / fixed

Status in indicator-network package in Ubuntu:
  Confirmed

Bug description:
  https://code.launchpad.net/~charlesk/indicator-network/flight-mode-
  handle-missing-urfkill disables all tests because of multiple (eleven,
  by my count) separate failing tests.

  Nearly all the failures occurred on Yakkety + arm64 or ppc64el, so
  it's possible that this is some issue in Yakkety and the test fails
  will resolve themselves when the distro is fixed. Or maybe these
  really are lots of real bugs that need to be addressed.

  What I'm sure of, though: they're *not* all related to this three-line
  change that needs to land. So I'm making this separate ticket to track
  it separately.

  Sample list of test failures:

  WpaPsk/TestSecretAgentGetSecrets.ProvidesPasswordForWpaPsk/0
  
https://launchpadlibrarian.net/286072925/buildlog_ubuntu-xenial-armhf.indicator-network_0.8.0+16.04.20160922.5-0ubuntu1_BUILDING.txt.gz

  TestIndicator.UnlockSIM2_IncorrectPin
  
https://launchpadlibrarian.net/286052502/buildlog_ubuntu-yakkety-i386.indicator-network_0.8.0+16.10.20160922.3-0ubuntu1_BUILDING.txt.gz

  TestIndicator.OneDisconnectedAccessPointAtStartup
  
https://launchpadlibrarian.net/286051922/buildlog_ubuntu-yakkety-amd64.indicator-network_0.8.0+16.10.20160922.3-0ubuntu1_BUILDING.txt.gz

  TestIndicator.UnlockSIM_CancelFirstUnlockSecond
  
https://launchpadlibrarian.net/286065695/buildlog_ubuntu-vivid-ppc64el.indicator-network_0.8.0+15.04.20160922.4-0ubuntu1_BUILDING.txt.gz

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