[Touch-packages] [Bug 1838176] Re: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, ideapad_laptop: Unknown event: 10

2019-07-27 Thread Kenji
I think I fixed this myself!

I downloaded the latest drivers from amd

https://www.amd.com/en/support/kb/release-notes/rn-amdgpu-unified-navi-
linux

extracted them all

ran

 sudo ./amdgpu-pro-install

and it seemed to work!


** Summary changed:

- Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr,  ideapad_laptop: 
Unknown event: 10
+ Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr,  ideapad_laptop

** Summary changed:

- Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr,  ideapad_laptop
+ Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr

** Summary changed:

- Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr
+ Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login 
screen with cursor

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

Title:
  Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at
  login screen with cursor

Status in systemd package in Ubuntu:
  New

Bug description:
  Was on 4.20, booted fine (with the boot option
  ivrs_ioapic[32]=00:14.0)

  Tried to boot 5.2.3 (but I believe this happened on 5.1.X too)

  It will boot to a certain extent, it does my disk password, i can see
  everything say "ok" when i do no quiet splash. But where it should go
  to the login screen I just see a single cursor

  Setting nomodeset lets me boot, looking at logs:

  Syslog

  Jul 27 21:28:58 kenji-mintop systemd[1]: Startup finished in 41.291s (kernel) 
+ 8.383s (userspace) = 49.675s.
  Jul 27 21:28:59 kenji-mintop kernel: [   50.535066] failed to write reg 1a6f4 
wait reg 1a706
  Jul 27 21:28:59 kenji-mintop NetworkManager[1082]:   [1564288139.7335] 
manager: NetworkManager state is now CONNECTED_GLOBAL
  Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': new 
request (1 scripts)
  Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': 
start running ordered scripts...
  Jul 27 21:29:09 kenji-mintop kernel: [   60.615575] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
  Jul 27 21:29:09 kenji-mintop kernel: [   60.615662] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
  Jul 27 21:29:09 kenji-mintop kernel: [   60.615665] [drm] GPU recovery 
disabled.
  Jul 27 21:29:11 kenji-mintop zerotier-one[1984]: connect: Host is unreachable
  Jul 27 21:29:19 kenji-mintop kernel: [   70.855956] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
  Jul 27 21:29:19 kenji-mintop kernel: [   70.856043] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
  Jul 27 21:29:19 kenji-mintop kernel: [   70.856047] [drm] GPU recovery 
disabled.
  Jul 27 21:29:20 kenji-mintop zerotier-one[1984]: message repeated 3 times: [ 
connect: Host is unreachable]
  Jul 27 21:29:22 kenji-mintop systemd-timesyncd[968]: Synchronized to time 
server 91.189.94.4:123 (ntp.ubuntu.com).
  Jul 27 21:29:23 kenji-mintop zerotier-one[1984]: connect: Host is unreachable
  Jul 27 21:29:29 kenji-mintop kernel: [   81.095310] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
  Jul 27 21:29:29 kenji-mintop kernel: [   81.095397] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
  Jul 27 21:29:29 kenji-mintop kernel: [   81.095401] [drm] GPU recovery 
disabled.
  Jul 27 21:29:40 kenji-mintop kernel: [   91.335557] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
  Jul 27 21:29:40 kenji-mintop kernel: [   91.335645] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
  Jul 27 21:29:40 kenji-mintop kernel: [   91.335648] [drm] GPU recovery 
disabled.
  Jul 27 21:29:41 kenji-mintop zerotier-one[1984]: message repeated 6 times: [ 
connect: Host is unreachable]
  Jul 27 21:29:43 kenji-mintop systemd[1]: Starting Stop ureadahead data 
collection...
  Jul 27 21:29:43 kenji-mintop systemd[1]: Started Stop ureadahead data 
collection.
  Jul 27 21:29:44 kenji-mintop zerotier-one[1984]: connect: Host is unreachable
  Jul 27 21:29:50 kenji-mintop kernel: [  101.575935] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
  Jul 27 21:29:50 kenji-mintop kernel: [  101.576023] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
  Jul 27 21:29:50 kenji-mintop kernel: [  101.576027] [drm] GPU recovery 
disabled.
  Jul 27 21:30:00 kenji-mintop kernel: [  111.815551] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
  Jul 27 21:30:00 kenji-mintop kernel: [  111.815638] 

[Touch-packages] [Bug 1838176] [NEW] Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, ideapad_laptop: Unknown event: 10

2019-07-27 Thread Kenji
Public bug reported:

Was on 4.20, booted fine (with the boot option ivrs_ioapic[32]=00:14.0)

Tried to boot 5.2.3 (but I believe this happened on 5.1.X too)

It will boot to a certain extent, it does my disk password, i can see
everything say "ok" when i do no quiet splash. But where it should go to
the login screen I just see a single cursor

Setting nomodeset lets me boot, looking at logs:

Syslog

Jul 27 21:28:58 kenji-mintop systemd[1]: Startup finished in 41.291s (kernel) + 
8.383s (userspace) = 49.675s.
Jul 27 21:28:59 kenji-mintop kernel: [   50.535066] failed to write reg 1a6f4 
wait reg 1a706
Jul 27 21:28:59 kenji-mintop NetworkManager[1082]:   [1564288139.7335] 
manager: NetworkManager state is now CONNECTED_GLOBAL
Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': new 
request (1 scripts)
Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': start 
running ordered scripts...
Jul 27 21:29:09 kenji-mintop kernel: [   60.615575] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
Jul 27 21:29:09 kenji-mintop kernel: [   60.615662] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
Jul 27 21:29:09 kenji-mintop kernel: [   60.615665] [drm] GPU recovery disabled.
Jul 27 21:29:11 kenji-mintop zerotier-one[1984]: connect: Host is unreachable
Jul 27 21:29:19 kenji-mintop kernel: [   70.855956] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
Jul 27 21:29:19 kenji-mintop kernel: [   70.856043] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
Jul 27 21:29:19 kenji-mintop kernel: [   70.856047] [drm] GPU recovery disabled.
Jul 27 21:29:20 kenji-mintop zerotier-one[1984]: message repeated 3 times: [ 
connect: Host is unreachable]
Jul 27 21:29:22 kenji-mintop systemd-timesyncd[968]: Synchronized to time 
server 91.189.94.4:123 (ntp.ubuntu.com).
Jul 27 21:29:23 kenji-mintop zerotier-one[1984]: connect: Host is unreachable
Jul 27 21:29:29 kenji-mintop kernel: [   81.095310] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
Jul 27 21:29:29 kenji-mintop kernel: [   81.095397] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
Jul 27 21:29:29 kenji-mintop kernel: [   81.095401] [drm] GPU recovery disabled.
Jul 27 21:29:40 kenji-mintop kernel: [   91.335557] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
Jul 27 21:29:40 kenji-mintop kernel: [   91.335645] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
Jul 27 21:29:40 kenji-mintop kernel: [   91.335648] [drm] GPU recovery disabled.
Jul 27 21:29:41 kenji-mintop zerotier-one[1984]: message repeated 6 times: [ 
connect: Host is unreachable]
Jul 27 21:29:43 kenji-mintop systemd[1]: Starting Stop ureadahead data 
collection...
Jul 27 21:29:43 kenji-mintop systemd[1]: Started Stop ureadahead data 
collection.
Jul 27 21:29:44 kenji-mintop zerotier-one[1984]: connect: Host is unreachable
Jul 27 21:29:50 kenji-mintop kernel: [  101.575935] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
Jul 27 21:29:50 kenji-mintop kernel: [  101.576023] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
Jul 27 21:29:50 kenji-mintop kernel: [  101.576027] [drm] GPU recovery disabled.
Jul 27 21:30:00 kenji-mintop kernel: [  111.815551] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
Jul 27 21:30:00 kenji-mintop kernel: [  111.815638] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
Jul 27 21:30:00 kenji-mintop kernel: [  111.815642] [drm] GPU recovery disabled.


Kern.log

Jul 27 21:28:56 kenji-mintop kernel: [   47.231201] failed to write reg 1a6f4 
wait reg 1a706
Jul 27 21:28:57 kenji-mintop kernel: [   48.907343] failed to write reg 28b4 
wait reg 28c6
Jul 27 21:28:58 kenji-mintop kernel: [   49.772880] capability: warning: 
`zerotier-one' uses 32-bit capabilities (legacy support in use)
Jul 27 21:28:59 kenji-mintop kernel: [   50.535066] failed to write reg 1a6f4 
wait reg 1a706
Jul 27 21:29:09 kenji-mintop kernel: [   60.615575] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
Jul 27 21:29:09 kenji-mintop kernel: [   60.615662] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 
pid 1736
Jul 27 21:29:09 kenji-mintop kernel: [   60.615665] [drm] GPU recovery disabled.
Jul 27 21:29:19 kenji-mintop kernel: [   70.855956] [drm:amdgpu_job_timedout 
[amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3
Jul 27 21:29:19 

[Touch-packages] [Bug 1838146] Re: ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on *.ntp.org

2019-07-27 Thread Paul Gear
On which version of Ubuntu did you experience this?  Whilst the latest
LTS (18.04) and non-LTS (19.04) versions have moved the ntp package to
universe, they still ship with a fully working configuration.  Here's an
example from a stock install on an AWS EC2 instance running disco
(19.04):

root@ip-172-31-7-27:~# grep ubuntu /etc/ntp.conf
pool 0.ubuntu.pool.ntp.org iburst
pool 1.ubuntu.pool.ntp.org iburst
pool 2.ubuntu.pool.ntp.org iburst
pool 3.ubuntu.pool.ntp.org iburst
pool ntp.ubuntu.com
root@ip-172-31-7-27:~# awk '/ubuntu/ {print $2}' /etc/ntp.conf | xargs -n1 host
0.ubuntu.pool.ntp.org has address 142.147.92.5
0.ubuntu.pool.ntp.org has address 12.71.198.242
0.ubuntu.pool.ntp.org has address 45.76.244.193
0.ubuntu.pool.ntp.org has address 104.168.88.15
1.ubuntu.pool.ntp.org has address 27.124.125.252
1.ubuntu.pool.ntp.org has address 129.250.35.250
1.ubuntu.pool.ntp.org has address 129.250.35.251
1.ubuntu.pool.ntp.org has address 13.55.50.68
2.ubuntu.pool.ntp.org has address 144.48.166.166
2.ubuntu.pool.ntp.org has address 203.7.149.149
2.ubuntu.pool.ntp.org has address 103.38.120.36
2.ubuntu.pool.ntp.org has address 103.76.40.123
2.ubuntu.pool.ntp.org has IPv6 address 2404:cc80:166::166
2.ubuntu.pool.ntp.org has IPv6 address 2407:f100:4:1::3
2.ubuntu.pool.ntp.org has IPv6 address 2a00:fd80:::::ff2
2.ubuntu.pool.ntp.org has IPv6 address 2001:19f0:5801:1daa:5400:1ff:fe95:cf80
3.ubuntu.pool.ntp.org has address 220.158.215.20
3.ubuntu.pool.ntp.org has address 27.124.125.251
3.ubuntu.pool.ntp.org has address 103.38.120.36
3.ubuntu.pool.ntp.org has address 103.214.220.220
ntp.ubuntu.com has address 91.189.89.198
ntp.ubuntu.com has address 91.189.89.199
ntp.ubuntu.com has address 91.189.91.157
ntp.ubuntu.com has address 91.189.94.4
ntp.ubuntu.com has IPv6 address 2001:67c:1560:8003::c8
ntp.ubuntu.com has IPv6 address 2001:67c:1560:8003::c7

So for the stock configuration on released Ubuntu versions, this is
factually incorrect.  Can you provide any further details to explain how
this is a problem?

** Changed in: ntp (Ubuntu)
   Status: New => Incomplete

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

Title:
  ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on
  *.ntp.org

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  When you install 'ntp' the /etc/ntp.conf it writes refers to the
  following:

   - *.ubuntu.ntp.org

  This hostname name and subdomain doesn't exist, it would be better if
  you just import and write http://ntp.snails.email/v1/ntp.conf
  alternatively make a file that randomly selects the pool and server
  from http://ntp.snails.email/v1/online.json --> so you download the
  .json, and then have somewhere on *.ubuntu.com that has a ntp.conf it
  will and randomly compile alist of pool items from the .json --> this
  will stop chronologistic buffering convulsive environments...

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

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


[Touch-packages] [Bug 1814302] Re: Quasselcore apparmor profile issue in lxd container.

2019-07-27 Thread Robert Pendell
The above workaround isn't enough to totally resolve the issues with
AppArmor and this application inside LXD.  I also had to switch to aa-
complain for PostgreSQL migration so features will have to be thoroughly
tested to identify it.  I'm willing to setup a secondary instance to do
any testing that is necessary but I don't know anything about AppArmor
to fix the profile.

Added note: It seems that migration may be broken in Quassel-Core in
general but I'm reporting that on their tracker as it seems to be a bug
on their end but setting up for PostgreSQL seemed to work in complain
mode.  It is untested in enforce mode.

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

Title:
  Quasselcore apparmor profile issue in lxd container.

Status in AppArmor:
  New
Status in apparmor package in Ubuntu:
  Confirmed
Status in quassel package in Ubuntu:
  Confirmed

Bug description:
  Fresh install of Ubuntu 18.04. lxd installed from snap. Fresh 18.04
  container. Everything up todate via apt.

  Install quassel-core. Service will not start.

  Set "aa-complain /usr/bin/quasselcore" allows quasselcore to start.

  I then added "/usr/bin/quasselcore rm," to
  "/etc/apparmor.d/usr.bin.quasselcore".

  Set "aa-enforce /usr/bin/quasselcore". Restarted main host.

  Quasselcore service now starts and I can connect to it.

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

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


[Touch-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1

2019-07-27 Thread Tom Lake
Oh, I see incoming updates for mesa 19.0.8 in bionic as well. They're
still under final adjustments then, I hope it fix my issue.

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

Title:
  Kodi package crash after the update of libdrm-amdgpu1

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Greetings,

  The last update of libdrm-amdgpu1 caused a bug on Kodi package, making
  it to crash after loading any video or reproduce a black image.

  Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC

libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium

* Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

   -- Timo Aaltonen  Wed, 10 Apr 2019 13:54:06
  +0300

  
  Kodi gives this error:

  #3  0x7f47676c60aa in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  #4  0x7f47676c5dd7 in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

  Repeated several times

  #3  0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1
  #4  0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1

  Team-Kodi stated these errors are in relation to 'Not supported GPU
  drivers', when Kodi can't find these files.

  
  I've found the cause, and a temporary solution:

  This bug was caused after an update for the latest version of libdrm-
  amdgpu1 2.4.97-1ubuntu1~18.04.1

  So I grabbed the previous version from 
  https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/

  installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb

  and now Kodi returns.

  
  I created a bug report, the problem affects multiple users.

  https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828

  
  We have a PointRelease coming soon, would we have time to fix this package?

  Thank you for your assistance.

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

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


[Touch-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1

2019-07-27 Thread Tom Lake
Please ignore the solution I commented, I committed a mistake and had
vdpau disabled.

But there's this update that hasn't been released by the server.

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

Title:
  Kodi package crash after the update of libdrm-amdgpu1

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Greetings,

  The last update of libdrm-amdgpu1 caused a bug on Kodi package, making
  it to crash after loading any video or reproduce a black image.

  Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC

libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium

* Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

   -- Timo Aaltonen  Wed, 10 Apr 2019 13:54:06
  +0300

  
  Kodi gives this error:

  #3  0x7f47676c60aa in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  #4  0x7f47676c5dd7 in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

  Repeated several times

  #3  0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1
  #4  0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1

  Team-Kodi stated these errors are in relation to 'Not supported GPU
  drivers', when Kodi can't find these files.

  
  I've found the cause, and a temporary solution:

  This bug was caused after an update for the latest version of libdrm-
  amdgpu1 2.4.97-1ubuntu1~18.04.1

  So I grabbed the previous version from 
  https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/

  installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb

  and now Kodi returns.

  
  I created a bug report, the problem affects multiple users.

  https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828

  
  We have a PointRelease coming soon, would we have time to fix this package?

  Thank you for your assistance.

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

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


[Touch-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1

2019-07-27 Thread Tom Lake
What's happening here?

Everything I download from this server

http://mirrors.edge.kernel.org/ubuntu/pool/main/u/ubuntu-meta/

Firefox accuses of having a virus or malware and eliminate the files.

It's an official Ubuntu North America server.

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

Title:
  Kodi package crash after the update of libdrm-amdgpu1

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Greetings,

  The last update of libdrm-amdgpu1 caused a bug on Kodi package, making
  it to crash after loading any video or reproduce a black image.

  Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC

libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium

* Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

   -- Timo Aaltonen  Wed, 10 Apr 2019 13:54:06
  +0300

  
  Kodi gives this error:

  #3  0x7f47676c60aa in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  #4  0x7f47676c5dd7 in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

  Repeated several times

  #3  0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1
  #4  0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1

  Team-Kodi stated these errors are in relation to 'Not supported GPU
  drivers', when Kodi can't find these files.

  
  I've found the cause, and a temporary solution:

  This bug was caused after an update for the latest version of libdrm-
  amdgpu1 2.4.97-1ubuntu1~18.04.1

  So I grabbed the previous version from 
  https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/

  installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb

  and now Kodi returns.

  
  I created a bug report, the problem affects multiple users.

  https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828

  
  We have a PointRelease coming soon, would we have time to fix this package?

  Thank you for your assistance.

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

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


[Touch-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1

2019-07-27 Thread Tom Lake
https://lists.ubuntu.com/archives/bionic-changes/2019-July/021427.html

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

Title:
  Kodi package crash after the update of libdrm-amdgpu1

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Greetings,

  The last update of libdrm-amdgpu1 caused a bug on Kodi package, making
  it to crash after loading any video or reproduce a black image.

  Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC

libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium

* Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

   -- Timo Aaltonen  Wed, 10 Apr 2019 13:54:06
  +0300

  
  Kodi gives this error:

  #3  0x7f47676c60aa in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  #4  0x7f47676c5dd7 in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

  Repeated several times

  #3  0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1
  #4  0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1

  Team-Kodi stated these errors are in relation to 'Not supported GPU
  drivers', when Kodi can't find these files.

  
  I've found the cause, and a temporary solution:

  This bug was caused after an update for the latest version of libdrm-
  amdgpu1 2.4.97-1ubuntu1~18.04.1

  So I grabbed the previous version from 
  https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/

  installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb

  and now Kodi returns.

  
  I created a bug report, the problem affects multiple users.

  https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828

  
  We have a PointRelease coming soon, would we have time to fix this package?

  Thank you for your assistance.

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

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


[Touch-packages] [Bug 1837170] Re: Kodi package crash after the update of libdrm-amdgpu1

2019-07-27 Thread Tom Lake
Solution's found:

 ubuntu-meta (1.417.3) bionic; urgency=medium

  * Added dbus-x11 to wsl-recommends (LP: #1837466)

 -- Balint Reczey  Wed, 24 Jul 2019 01:21:39 +0200

I found in the server this latest version of ubuntu-desktop and
installed the .deb file.

Indeed we see a correction for X11/xorg and everything works now.


However, I find odd that this package was uploaded on Thu Jul 25 21:52:21 to be 
sent as an update:

https://lists.ubuntu.com/archives/bionic-changes/2019-July/021433.html
http://mirrors.edge.kernel.org/ubuntu/pool/main/u/ubuntu-meta/

But I received on my system this one

[ubuntu/bionic-updates] ubuntu-meta 1.417.2 (Accepted)

Uploaded on Thu Jul 25 19:44:55 UTC 2019

And probably everyone else!

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

Title:
  Kodi package crash after the update of libdrm-amdgpu1

Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Greetings,

  The last update of libdrm-amdgpu1 caused a bug on Kodi package, making
  it to crash after loading any video or reproduce a black image.

  Version: 2.4.97-1ubuntu1~18.04.12019-07-03 15:07:54 UTC

libdrm (2.4.97-1ubuntu1~18.04.1) bionic; urgency=medium

* Backport to bionic for 18.04.3 HWE stack update. (LP: #1824111)

   -- Timo Aaltonen  Wed, 10 Apr 2019 13:54:06
  +0300

  
  Kodi gives this error:

  #3  0x7f47676c60aa in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so
  #4  0x7f47676c5dd7 in ?? () from 
/usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so

  Repeated several times

  #3  0x7f475ce2c5a6 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1
  #4  0x7f475ce2c425 in ?? () from /usr/lib/x86_64-linux-gnu/libLLVM-8.so.1

  Team-Kodi stated these errors are in relation to 'Not supported GPU
  drivers', when Kodi can't find these files.

  
  I've found the cause, and a temporary solution:

  This bug was caused after an update for the latest version of libdrm-
  amdgpu1 2.4.97-1ubuntu1~18.04.1

  So I grabbed the previous version from 
  https://mirror.transip.net/ubuntu/ubuntu/pool/main/libd/libdrm/

  installed libdrm-amdgpu1_2.4.95-1~18.04.1_amd64.deb

  and now Kodi returns.

  
  I created a bug report, the problem affects multiple users.

  https://bugs.launchpad.net/ubuntu/+source/kodi/+bug/1836828

  
  We have a PointRelease coming soon, would we have time to fix this package?

  Thank you for your assistance.

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

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


[Touch-packages] [Bug 1451286] Re: crontab -r deletes cron entries without asking for confirmation

2019-07-27 Thread Anonymous
I'm glad my initial stubborness is leading to this avalanche of users
echoing me. I feel all your pain, I have been there and it sucks!

I would suggest this update/patch needs to go into not only the new
versions of Ubuntu, but also the LTS distribution repos also, as a
stability bugfix.

I made a ticket in the Mint repos about the bug called systemd and they
insta-banned me, lol. I still run Ubuntu 14.04 because I am not
interesting in running systemd as pid1, or at all. I'll probably be off
to slackware soon.

It's been real, Ubuntu.

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

Title:
  crontab -r deletes cron entries without asking for confirmation

Status in cron package in Ubuntu:
  Confirmed
Status in cron package in Debian:
  New

Bug description:
  type: crontab -r

  Expected use case : should ask user if they really want to delete this
  file, of which there are no backups on the system by default, and may
  take hours to restore by hand, if it's even possible.

  what happens: user's cron entry is deleted with no warning.

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

-- 
Mailing list: https://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 1451286] Re: crontab -r deletes cron entries without asking for confirmation

2019-07-27 Thread Akiva
These are only the ones stubborn enough to.complain. there are so.many
others...

On Sat, Jul 27, 2019, 10:53 PM Terence Eden <1451...@bugs.launchpad.net>
wrote:

> Here's a whole bunch of people who have accidentally run `-r` when they
> meant `e` (including me!)
>
> * https://twitter.com/search?q=crontab%20e%20r=typed_query
> *
> https://stackoverflow.com/questions/37852940/how-recover-deleted-crontab-r-option
> *
> https://www.reddit.com/r/linux/comments/5h1bh5/psa_do_not_type_crontab_r_when_you_mean_crontab_e/
> *
> https://b3z13r.wordpress.com/2011/02/09/how-to-rebuild-crontab-from-scratch-after-accidentally-typing-crontab-r/
>
> Please can someone to implement the attached patch.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1451286
>
> Title:
>   crontab -r deletes cron entries without asking for confirmation
>
> Status in cron package in Ubuntu:
>   Confirmed
> Status in cron package in Debian:
>   New
>
> Bug description:
>   type: crontab -r
>
>   Expected use case : should ask user if they really want to delete this
>   file, of which there are no backups on the system by default, and may
>   take hours to restore by hand, if it's even possible.
>
>   what happens: user's cron entry is deleted with no warning.
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/cron/+bug/1451286/+subscriptions
>

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

Title:
  crontab -r deletes cron entries without asking for confirmation

Status in cron package in Ubuntu:
  Confirmed
Status in cron package in Debian:
  New

Bug description:
  type: crontab -r

  Expected use case : should ask user if they really want to delete this
  file, of which there are no backups on the system by default, and may
  take hours to restore by hand, if it's even possible.

  what happens: user's cron entry is deleted with no warning.

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

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


[Touch-packages] [Bug 1451286] Re: crontab -r deletes cron entries without asking for confirmation

2019-07-27 Thread Terence Eden
Here's a whole bunch of people who have accidentally run `-r` when they
meant `e` (including me!)

* https://twitter.com/search?q=crontab%20e%20r=typed_query
* 
https://stackoverflow.com/questions/37852940/how-recover-deleted-crontab-r-option
* 
https://www.reddit.com/r/linux/comments/5h1bh5/psa_do_not_type_crontab_r_when_you_mean_crontab_e/
* 
https://b3z13r.wordpress.com/2011/02/09/how-to-rebuild-crontab-from-scratch-after-accidentally-typing-crontab-r/

Please can someone to implement the attached patch.

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

Title:
  crontab -r deletes cron entries without asking for confirmation

Status in cron package in Ubuntu:
  Confirmed
Status in cron package in Debian:
  New

Bug description:
  type: crontab -r

  Expected use case : should ask user if they really want to delete this
  file, of which there are no backups on the system by default, and may
  take hours to restore by hand, if it's even possible.

  what happens: user's cron entry is deleted with no warning.

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

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


[Touch-packages] [Bug 1821343] Re: slapd process failure is not detected by systemd

2019-07-27 Thread Launchpad Bug Tracker
** Merge proposal linked:
   
https://code.launchpad.net/~ahasenack/ubuntu/+source/openldap/+git/openldap/+merge/370689

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

Title:
  slapd process failure is not detected by systemd

Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Xenial:
  Fix Released
Status in openldap source package in Bionic:
  Fix Released
Status in openldap source package in Cosmic:
  Fix Released
Status in openldap package in Debian:
  New

Bug description:
  [Impact]
  Systemd service reports slapd as active, even though it may have failed

  [Description]
  The slapd package for OpenLDAP is shipped with a SysV-style init script 
(/etc/init.d/slapd). Systemd automatically converts this to a systemd service 
by generating the unit file using the systemd-sysv-generator(8) utility. The 
generated unit file contains Type=forking and RemainAfterExit=yes directives.

  If the slapd daemon process exits due to some failure (e.g., it
  receives a SIGTERM or SIGKILL), the failure is not detected properly
  by systemd. The service is still reported as active even though the
  child (daemon) process has exited with a signal.

  We can easily fix this by including a proper systemd service file for
  slapd in the openldap package. Since the init.d script already does
  most of the necessary work (parsing configs, setting up PID files,
  etc.), we don't need anything complicated for the systemd unit file.
  Just making sure that RemainAfterExit is set to "no" makes the systemd
  service behave in the expected way.

  [Test Case]
  1) Deploy a disco container
  $ lxc launch images:ubuntu/disco disco

  2) Install slapd
  ubuntu@disco:~$ sudo apt update && sudo apt install slapd -y

  3) Verify that slapd is running with the auto-generated service
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
     Loaded: loaded (/etc/init.d/slapd; generated)
     Active: active (running) since Fri 2019-03-22 11:51:22 UTC; 40min ago
   Docs: man:systemd-sysv-generator(8)
    Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)
  Tasks: 3 (limit: 4915)
     Memory: 712.6M
     CGroup: /system.slice/slapd.service
     └─1109 /usr/sbin/slapd -h ldap:/// ldapi:/// -g openldap -u 
openldap -F /etc/ldap/slapd.d

  4) SIGKILL the slapd process (PID is displayed in systemctl status output)
  ubuntu@disco:~$ sudo kill -9 1109

  5) Check if systemd service lists slapd as still active, even though it was 
terminated
  ubuntu@disco:~$ systemctl status slapd
  ● slapd.service - LSB: OpenLDAP standalone server (Lightweight Directory 
Access Protocol)
     Loaded: loaded (/etc/init.d/slapd; generated)
     Active: active (exited) since Fri 2019-03-22 11:51:22 UTC; 42min ago
   Docs: man:systemd-sysv-generator(8)
    Process: 1103 ExecStart=/etc/init.d/slapd start (code=exited, 
status=0/SUCCESS)

  6) Check if systemd has loaded both
  /run/systemd/generator.late/slapd.service &
  /usr/lib/systemd/system/slapd.service.d/slapd-remain-after-exit.conf

  $ systemctl cat slapd

  [Regression Potential]
  The regression potential for this fix should be very low, if we keep the new 
systemd unit file close to the one generated by systemd-sysv-generator(8). The 
only significant change would be the RemainAfterExit directive, and this should 
make the slapd service behave like a "normal" forking service. Nonetheless, 
we'll perform scripted test runs to make sure no regressions arise.

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

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


[Touch-packages] [Bug 1838151] [NEW] Poor quality audio with modern Bluetooth headsets in HSP/HFP. Missing wide band speech support.

2019-07-27 Thread Jeffrey Nappi
Public bug reported:

Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

Modern Bluetooth headsets (such as the Bose QC series headphones, many
others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding. As
it currently stands, Ubuntu defaults to only supporting HSP headsets
using 8kHz CVSD, and is incapable of supporting HFP 1.6 at this time.

The ChromiumOS team recently tackled this issue -
https://bugs.chromium.org/p/chromium/issues/detail?id=843048

Their efforts may assist in bringing this to Ubuntu, however it appears
that there are quite a lot of differences considering they have
developed their own audio server solution etc.

The Bluetooth Telephony Working Group published the HFP 1.6 spec in May
2011 -
https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

Patches have been proposed in the past for this issue to the kernel and
PulseAudio:

PulseAudio: https://patchwork.freedesktop.org/patch/245272/
Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

It appears that the Chromium OS team applied the same kernel patch:
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: pulseaudio 1:12.2-2ubuntu3
ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
Uname: Linux 5.0.0-20-generic x86_64
ApportVersion: 2.20.10-0ubuntu27.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/controlC0:  jnappi 2777 F pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sat Jul 27 11:08:29 2019
EcryptfsInUse: Yes
InstallationDate: Installed on 2017-11-04 (629 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pulseaudio
UpgradeStatus: Upgraded to disco on 2019-07-18 (9 days ago)
dmi.bios.date: 06/07/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: R07ET67W (2.07 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20FW000TUS
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40705 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.modalias: 
dmi:bvnLENOVO:bvrR07ET67W(2.07):bd06/07/2016:svnLENOVO:pn20FW000TUS:pvrThinkPadT460p:rvnLENOVO:rn20FW000TUS:rvrSDK0J40705WIN:cvnLENOVO:ct10:cvrNone:
dmi.product.family: ThinkPad T460p
dmi.product.name: 20FW000TUS
dmi.product.sku: LENOVO_MT_20FW_BU_Think_FM_ThinkPad T460p
dmi.product.version: ThinkPad T460p
dmi.sys.vendor: LENOVO

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


** Tags: amd64 apport-bug disco

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

Title:
  Poor quality audio with modern Bluetooth headsets in HSP/HFP.  Missing
  wide band speech support.

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Bluetooth HSP/HFP audio quality is poor on Ubuntu comparative to all
  other major platforms (Windows, MacOS, ChromeOS, Android, iOS).

  Modern Bluetooth headsets (such as the Bose QC series headphones, many
  others) are capable of using HFP 1.6 with mSBC 16kHz audio encoding.
  As it currently stands, Ubuntu defaults to only supporting HSP
  headsets using 8kHz CVSD, and is incapable of supporting HFP 1.6 at
  this time.

  The ChromiumOS team recently tackled this issue -
  https://bugs.chromium.org/p/chromium/issues/detail?id=843048

  Their efforts may assist in bringing this to Ubuntu, however it
  appears that there are quite a lot of differences considering they
  have developed their own audio server solution etc.

  The Bluetooth Telephony Working Group published the HFP 1.6 spec in
  May 2011 -
  https://www.bluetooth.org/docman/handlers/downloaddoc.ashx?doc_id=238193

  Patches have been proposed in the past for this issue to the kernel
  and PulseAudio:

  PulseAudio: https://patchwork.freedesktop.org/patch/245272/
  Kernel: https://www.spinics.net/lists/linux-bluetooth/msg76982.html

  It appears that the Chromium OS team applied the same kernel patch:
  
https://chromium.googlesource.com/chromiumos/third_party/kernel/+/77dd0cb94c1713a8a12f6e392955dfa64c430e54

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: pulseaudio 1:12.2-2ubuntu3
  ProcVersionSignature: Ubuntu 5.0.0-20.21-generic 5.0.8
  Uname: Linux 5.0.0-20-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  jnappi 2777 F pulseaudio
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jul 27 11:08:29 2019
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-04 (629 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - 

[Touch-packages] [Bug 1838147] Re: ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on *.ntp.org

2019-07-27 Thread Paul White
*** This bug is a duplicate of bug 1838146 ***
https://bugs.launchpad.net/bugs/1838146

** This bug has been marked a duplicate of bug 1838146
   ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on *.ntp.org

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

Title:
  ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on
  *.ntp.org

Status in ntp package in Ubuntu:
  New

Bug description:
  When you install 'ntp' the /etc/ntp.conf it writes refers to the
  following:

   - *.ubuntu.ntp.org

  This hostname name and subdomain doesn't exist, it would be better if
  you just import and write http://ntp.snails.email/v1/ntp.conf
  alternatively make a file that randomly selects the pool and server
  from http://ntp.snails.email/v1/online.json --> so you download the
  .json, and then have somewhere on *.ubuntu.com that has a ntp.conf it
  will and randomly compile alist of pool items from the .json --> this
  will stop chronologistic buffering convulsive environments...

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

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


[Touch-packages] [Bug 1838147] [NEW] ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on *.ntp.org

2019-07-27 Thread Dr. Simon A. Roberts
Public bug reported:

When you install 'ntp' the /etc/ntp.conf it writes refers to the
following:

 - *.ubuntu.ntp.org

This hostname name and subdomain doesn't exist, it would be better if
you just import and write http://ntp.snails.email/v1/ntp.conf
alternatively make a file that randomly selects the pool and server from
http://ntp.snails.email/v1/online.json --> so you download the .json,
and then have somewhere on *.ubuntu.com that has a ntp.conf it will and
randomly compile alist of pool items from the .json --> this will stop
chronologistic buffering convulsive environments...

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

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

Title:
  ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on
  *.ntp.org

Status in ntp package in Ubuntu:
  New

Bug description:
  When you install 'ntp' the /etc/ntp.conf it writes refers to the
  following:

   - *.ubuntu.ntp.org

  This hostname name and subdomain doesn't exist, it would be better if
  you just import and write http://ntp.snails.email/v1/ntp.conf
  alternatively make a file that randomly selects the pool and server
  from http://ntp.snails.email/v1/online.json --> so you download the
  .json, and then have somewhere on *.ubuntu.com that has a ntp.conf it
  will and randomly compile alist of pool items from the .json --> this
  will stop chronologistic buffering convulsive environments...

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

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


[Touch-packages] [Bug 1838146] [NEW] ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on *.ntp.org

2019-07-27 Thread Dr. Simon A. Roberts
Public bug reported:

When you install 'ntp' the /etc/ntp.conf it writes refers to the
following:

 - *.ubuntu.ntp.org

This hostname name and subdomain doesn't exist, it would be better if
you just import and write http://ntp.snails.email/v1/ntp.conf
alternatively make a file that randomly selects the pool and server from
http://ntp.snails.email/v1/online.json --> so you download the .json,
and then have somewhere on *.ubuntu.com that has a ntp.conf it will and
randomly compile alist of pool items from the .json --> this will stop
chronologistic buffering convulsive environments...

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

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

Title:
  ntpd installation /etc/ntp.conf ~ hostnames listed do not exist on
  *.ntp.org

Status in ntp package in Ubuntu:
  New

Bug description:
  When you install 'ntp' the /etc/ntp.conf it writes refers to the
  following:

   - *.ubuntu.ntp.org

  This hostname name and subdomain doesn't exist, it would be better if
  you just import and write http://ntp.snails.email/v1/ntp.conf
  alternatively make a file that randomly selects the pool and server
  from http://ntp.snails.email/v1/online.json --> so you download the
  .json, and then have somewhere on *.ubuntu.com that has a ntp.conf it
  will and randomly compile alist of pool items from the .json --> this
  will stop chronologistic buffering convulsive environments...

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

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


[Touch-packages] [Bug 1835711] Re: Ubuntu-bug collects bug data but does not upload it

2019-07-27 Thread fcole90
sudo systemctl enable  whoopsie
[sudo] password for x: 
Synchronizing state of whoopsie.service with SysV service script with 
/lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable whoopsie
Created symlink /etc/systemd/system/multi-user.target.wants/whoopsie.service → 
/lib/systemd/system/whoopsie.service.

Now it correctly opens a page to report a bug with ubuntu-bug.

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

Title:
  Ubuntu-bug collects bug data but does not upload it

Status in apport package in Ubuntu:
  New

Bug description:
  I'm trying to report some bugs from a stable release, 18.04. I enabled
  apport reporting as suggested
  
here:https://help.ubuntu.com/community/ReportingBugs#Reporting_a_crash_in_the_stable_release
  and also here: https://www.linuxbabe.com/ubuntu/disable-apport-error-
  reporting-ubuntu-16-04-lts

  I also have whoopsie package installed.

  When I try to report a bug using `ubuntu-bug $package_name` it seem to
  be collecting data, but then it doesn't send them to launchpad.

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

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


[Touch-packages] [Bug 1835711] Re: Ubuntu-bug collects bug data but does not upload it

2019-07-27 Thread fcole90
Hi, in the while I decided to upgrade my system up to current dev
version, so I'm now using eoan.

$ systemctl is-enabled whoopsie
disabled

$ systemctl is-active whoopsie
active

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

Title:
  Ubuntu-bug collects bug data but does not upload it

Status in apport package in Ubuntu:
  New

Bug description:
  I'm trying to report some bugs from a stable release, 18.04. I enabled
  apport reporting as suggested
  
here:https://help.ubuntu.com/community/ReportingBugs#Reporting_a_crash_in_the_stable_release
  and also here: https://www.linuxbabe.com/ubuntu/disable-apport-error-
  reporting-ubuntu-16-04-lts

  I also have whoopsie package installed.

  When I try to report a bug using `ubuntu-bug $package_name` it seem to
  be collecting data, but then it doesn't send them to launchpad.

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

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


[Touch-packages] [Bug 1773682] Re: Skype notification area icon corrupted

2019-07-27 Thread Ubuntu Foundations Team Bug Bot
The attachment "statusicon-create-pixbuf-at-correct-size.patch" seems to
be a patch.  If it isn't, please remove the "patch" flag from the
attachment, remove the "patch" tag, and if you are a member of the
~ubuntu-reviewers, unsubscribe the team.

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

** Tags added: patch

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

Title:
  Skype notification area icon corrupted

Status in Ubuntu MATE:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Debian:
  Unknown

Bug description:
  System Version: Ubuntu MATE 18.04
  Package: mate-panel 1.20.1-3ubuntu1

  How to reproduce:
  - log in with new user profile
  - install Skype from Software Boutique
  - launch Skype

  => icon in nofitication area is corrupted (see screenshot)

  This is already noticeable on default panel size, enlarging the panel
  makes it even more obvious with lots of duplicate Skype icons
  appearing.

  This bug does not appear on the GTK2-based Ubuntu MATE 16.04 running
  the exact same Skype version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1773682/+subscriptions

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


[Touch-packages] [Bug 1828505] Re: sudo apt-get upgrade E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource temporarily unavailable) E: Unable to acquire the dpkg frontend lock (/va

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

** Changed in: unattended-upgrades (Ubuntu)
   Status: New => Confirmed

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

Title:
  sudo apt-get upgrade E: Could not get lock /var/lib/dpkg/lock-frontend
  - open (11: Resource temporarily unavailable) E: Unable to acquire the
  dpkg frontend lock (/var/lib/dpkg/lock-frontend), is another process
  using it?

Status in unattended-upgrades package in Ubuntu:
  Confirmed

Bug description:
  I am having problem in upgarde. terminal showing

  sudo apt-get upgrade
  E: Could not get lock /var/lib/dpkg/lock-frontend - open (11: Resource 
temporarily unavailable)
  E: Unable to acquire the dpkg frontend lock (/var/lib/dpkg/lock-frontend), is 
another process using it?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unattended-upgrades/+bug/1828505/+subscriptions

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


[Touch-packages] [Bug 1566437] Re: Scrolling randomly stops working

2019-07-27 Thread Egmont Koblinger
> I found a hacky workaround - add this to your $PS1:

The workaround of resetting relevant settings from the prompt has
already been mentioned – although without showing a concrete example.

> Given how randomly it happens, I believe there is a real bug in
Terminator

I'm about 99.999% sure that this is _not_ a bug in Terminator (VTE). It
is believed to properly execute the relevant escape sequences it
receives. (Can you reproduce the issue with xterm, urxvt, konsole...? I
bet you can.)

> but if you want to force the broken state, just open 'mc' and run
'pkill mc' from another terminal, your scrolling will be broken.

Yup, in this case mc asks the terminal to switch to a special mode, and
due to getting killed, it does not ask the terminal to leave that mode.
Nothing new here, exactly what has already been concluded in this
thread.

> run e.g 'mc > trace.txt'. Then type 'exit', hit return, and mc will
quit. You will get all the escape sequences from mc in trace.txt to
inspect.

Can you really reproduce the issue this way? Because you don't kill mc
now, but exit it cleanly.

> to report it as a terminator bug

Unless you have firm evidence that this is a terminator (or VTE) bug,
please don't spam its bugtracker with something that's most likely an
issue elsewhere.

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

Title:
  Scrolling randomly stops working

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Usually, scrolling in the terminal window works as expected, which is like 
this:
  - the terminal window has a scrollbar
  - Assuming there are more lines (of commands you have typed + their output) 
than fit in the window, you can scroll up and down both by dragging the 
scrollbar and by using the mouse wheel

  
  However, at random times, the Terminal starts behaving like this:
  1 - the scrollbar's "handle" is as high as the whole scrollbar, as if the 
existing lines didn't exceed the height of the window, even if that is not the 
case
  2 - you can't scroll by dragging the scrollbar (which is consistent with 1)
  3 - the scrollwheel behaves like the up and down arrow keys, that is, it 
scans through previously typed commands in your history.

  
  I have no idea what triggers the nonsense behavior. It seems to start 
happening randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-terminal 3.16.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  5 19:05:18 2016
  InstallationDate: Installed on 2013-10-11 (906 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to wily on 2016-01-18 (78 days ago)

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

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


[Touch-packages] [Bug 1773682] Re: Skype notification area icon corrupted

2019-07-27 Thread Pavel
** Patch added: "statusicon-create-pixbuf-at-correct-size.patch"
   
https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1773682/+attachment/5279534/+files/statusicon-create-pixbuf-at-correct-size.patch

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

Title:
  Skype notification area icon corrupted

Status in Ubuntu MATE:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Debian:
  Unknown

Bug description:
  System Version: Ubuntu MATE 18.04
  Package: mate-panel 1.20.1-3ubuntu1

  How to reproduce:
  - log in with new user profile
  - install Skype from Software Boutique
  - launch Skype

  => icon in nofitication area is corrupted (see screenshot)

  This is already noticeable on default panel size, enlarging the panel
  makes it even more obvious with lots of duplicate Skype icons
  appearing.

  This bug does not appear on the GTK2-based Ubuntu MATE 16.04 running
  the exact same Skype version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1773682/+subscriptions

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


[Touch-packages] [Bug 1773682] Re: Skype notification area icon corrupted

2019-07-27 Thread Pavel
This is a bug in GtkStatusIcon, not in Skype. Here is the patch for
gtk+3.0: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910635#26

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

** Also affects: gtk+3.0 (Debian) via
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=910635
   Importance: Unknown
   Status: Unknown

** Also affects: gtk+3.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 gtk+3.0 in Ubuntu.
https://bugs.launchpad.net/bugs/1773682

Title:
  Skype notification area icon corrupted

Status in Ubuntu MATE:
  Invalid
Status in gtk+3.0 package in Ubuntu:
  New
Status in gtk+3.0 package in Debian:
  Unknown

Bug description:
  System Version: Ubuntu MATE 18.04
  Package: mate-panel 1.20.1-3ubuntu1

  How to reproduce:
  - log in with new user profile
  - install Skype from Software Boutique
  - launch Skype

  => icon in nofitication area is corrupted (see screenshot)

  This is already noticeable on default panel size, enlarging the panel
  makes it even more obvious with lots of duplicate Skype icons
  appearing.

  This bug does not appear on the GTK2-based Ubuntu MATE 16.04 running
  the exact same Skype version.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-mate/+bug/1773682/+subscriptions

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


[Touch-packages] [Bug 1566437] Re: Scrolling randomly stops working

2019-07-27 Thread MightyPork
oops this is a wrong place to report it as a terminator bug, but the
workaround should work anyway ;)

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

Title:
  Scrolling randomly stops working

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Usually, scrolling in the terminal window works as expected, which is like 
this:
  - the terminal window has a scrollbar
  - Assuming there are more lines (of commands you have typed + their output) 
than fit in the window, you can scroll up and down both by dragging the 
scrollbar and by using the mouse wheel

  
  However, at random times, the Terminal starts behaving like this:
  1 - the scrollbar's "handle" is as high as the whole scrollbar, as if the 
existing lines didn't exceed the height of the window, even if that is not the 
case
  2 - you can't scroll by dragging the scrollbar (which is consistent with 1)
  3 - the scrollwheel behaves like the up and down arrow keys, that is, it 
scans through previously typed commands in your history.

  
  I have no idea what triggers the nonsense behavior. It seems to start 
happening randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-terminal 3.16.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  5 19:05:18 2016
  InstallationDate: Installed on 2013-10-11 (906 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to wily on 2016-01-18 (78 days ago)

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

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


[Touch-packages] [Bug 1566437] Re: Scrolling randomly stops working

2019-07-27 Thread MightyPork
Getting this with 1.91 on Arch, it likes to happen during package
updates for some reason.

I found a hacky workaround - add this to your $PS1:

\[\e[?1049l\e[?2004l\e[?1006l\e[?1002l\e[?1001r\e[?1l\]

It'll fix it as soon as you get to a prompt.

Given how randomly it happens, I believe there is a real bug in
Terminator; but if you want to force the broken state, just open 'mc'
and run 'pkill mc' from another terminal, your scrolling will be broken.

A way to debug this kind of thing is to run e.g 'mc > trace.txt'. Then
type 'exit', hit return, and mc will quit. You will get all the escape
sequences from mc in trace.txt to inspect.

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

Title:
  Scrolling randomly stops working

Status in bash package in Ubuntu:
  Confirmed

Bug description:
  Usually, scrolling in the terminal window works as expected, which is like 
this:
  - the terminal window has a scrollbar
  - Assuming there are more lines (of commands you have typed + their output) 
than fit in the window, you can scroll up and down both by dragging the 
scrollbar and by using the mouse wheel

  
  However, at random times, the Terminal starts behaving like this:
  1 - the scrollbar's "handle" is as high as the whole scrollbar, as if the 
existing lines didn't exceed the height of the window, even if that is not the 
case
  2 - you can't scroll by dragging the scrollbar (which is consistent with 1)
  3 - the scrollwheel behaves like the up and down arrow keys, that is, it 
scans through previously typed commands in your history.

  
  I have no idea what triggers the nonsense behavior. It seems to start 
happening randomly.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gnome-terminal 3.16.2-1ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-34.39-generic 4.2.8-ckt4
  Uname: Linux 4.2.0-34-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Apr  5 19:05:18 2016
  InstallationDate: Installed on 2013-10-11 (906 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  SourcePackage: gnome-terminal
  UpgradeStatus: Upgraded to wily on 2016-01-18 (78 days ago)

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

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