date:20180415

[Touch-packages] [Bug 1764216] Re: [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 2.56.1-2ubuntu1

2018-04-15 Thread Daniel van Vugt

** Package changed: gjs (Ubuntu) => glib2.0 (Ubuntu)

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

Title:
  [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and
  glib 2.56.1-2ubuntu1

Status in glib2.0 package in Ubuntu:
  Won't Fix

Bug description:
  Since Ubuntu updated to gjs 1.52.1-1, our bug tracking systems are
  unable to automatically retrace crashes. This has created a sudden
  wave of crash reports that we can't automatically classify.

  For example, this is what LP: #1748450/LP: #1505409 looks like now:

  #0  raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:51
  set = {__val = {0, 538, 539, 540, 541, 542, 543, 544, 545, 546, 547, 
548, 549, 550, 551, 552}}
  pid = 
  tid = 
  ret = 
  #1  0x558168af3a6b in dump_gjs_stack_on_signal_handler (signo=5) at 
../src/main.c:367
  sa = {__sigaction_handler = {sa_handler = 0x558168af3aa0 
, sa_sigaction = 0x558168af3aa0 
}, sa_mask = {__val = {0 }}, 
sa_flags = 0, sa_restorer = 0x0}
  i = 65
  #2  
  No locals.
  #3  0x7f1d3e2bdc41 in ?? ()
  No symbol table info available.
  #4  0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  No symbol table info available.
  #5  0x7f1d3e2bec7c in ?? ()
  No symbol table info available.
  #6  0x7f1d3e30a51f in ?? ()
  No symbol table info available.
  #7  0x7f1d3e35fe32 in ?? ()
  No symbol table info available.
  #8  0x in ?? ()
  No symbol table info available.
  #9  0x7f1d3e30a451 in ?? ()
  No symbol table info available.
  #10 0x5581697262f0 in ?? ()
  No symbol table info available.
  #11 0x in ?? ()
  No symbol table info available.
  #12 0x7f1d3e30a464 in ?? ()
  No symbol table info available.
  #13 0x7f1d3e30a2f9 in ?? ()
  No symbol table info available.
  #14 0x in ?? ()
  No symbol table info available.
  #15 0x7f1d3e30a4be in ?? ()
  No symbol table info available.
  #16 0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  No symbol table info available.
  #17 0x in ?? ()
  No symbol table info available.
  #18 0x5581697262f0 in ?? ()
  No symbol table info available.
  #19 0x4cae2c7f65c95f00 in ?? ()
  No symbol table info available.
  #20 0x0006 in ?? ()
  No symbol table info available.
  #21 0x558168af3b45 in default_log_handler (log_domain=0x1 , log_level=6, message=0x5581697262f0 "Connection 
to xwayland lost", data=0x0) at ../src/main.c:310
  now = {tv_sec = 1523717020, tv_usec = 986744}
  #22 0x7f1d3e2bef0d in ?? ()
  No symbol table info available.
  #23 0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
  No symbol table info available.
  #24 0x5581697262f0 in ?? ()
  No symbol table info available.
  #25 0x0001 in ?? ()
  No symbol table info available.
  #26 0x558168af3af0 in ?? () at ../src/main.c:337

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1764216/+subscriptions

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

[Touch-packages] [Bug 1764216] [NEW] [regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 2.56.1-2ubuntu1

2018-04-15 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

Since Ubuntu updated to gjs 1.52.1-1, our bug tracking systems are
unable to automatically retrace crashes. This has created a sudden wave
of crash reports that we can't automatically classify.

For example, this is what LP: #1748450/LP: #1505409 looks like now:

#0  raise (sig=) at ../sysdeps/unix/sysv/linux/raise.c:51
set = {__val = {0, 538, 539, 540, 541, 542, 543, 544, 545, 546, 547, 
548, 549, 550, 551, 552}}
pid = 
tid = 
ret = 
#1  0x558168af3a6b in dump_gjs_stack_on_signal_handler (signo=5) at 
../src/main.c:367
sa = {__sigaction_handler = {sa_handler = 0x558168af3aa0 
, sa_sigaction = 0x558168af3aa0 
}, sa_mask = {__val = {0 }}, 
sa_flags = 0, sa_restorer = 0x0}
i = 65
#2  
No locals.
#3  0x7f1d3e2bdc41 in ?? ()
No symbol table info available.
#4  0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
No symbol table info available.
#5  0x7f1d3e2bec7c in ?? ()
No symbol table info available.
#6  0x7f1d3e30a51f in ?? ()
No symbol table info available.
#7  0x7f1d3e35fe32 in ?? ()
No symbol table info available.
#8  0x in ?? ()
No symbol table info available.
#9  0x7f1d3e30a451 in ?? ()
No symbol table info available.
#10 0x5581697262f0 in ?? ()
No symbol table info available.
#11 0x in ?? ()
No symbol table info available.
#12 0x7f1d3e30a464 in ?? ()
No symbol table info available.
#13 0x7f1d3e30a2f9 in ?? ()
No symbol table info available.
#14 0x in ?? ()
No symbol table info available.
#15 0x7f1d3e30a4be in ?? ()
No symbol table info available.
#16 0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
No symbol table info available.
#17 0x in ?? ()
No symbol table info available.
#18 0x5581697262f0 in ?? ()
No symbol table info available.
#19 0x4cae2c7f65c95f00 in ?? ()
No symbol table info available.
#20 0x0006 in ?? ()
No symbol table info available.
#21 0x558168af3b45 in default_log_handler (log_domain=0x1 , log_level=6, message=0x5581697262f0 "Connection 
to xwayland lost", data=0x0) at ../src/main.c:310
now = {tv_sec = 1523717020, tv_usec = 986744}
#22 0x7f1d3e2bef0d in ?? ()
No symbol table info available.
#23 0x7f1d3c854b4d in ?? () from 
/tmp/apport_sandbox_2dl0glnw/usr/lib/x86_64-linux-gnu/libmutter-2.so.0
No symbol table info available.
#24 0x5581697262f0 in ?? ()
No symbol table info available.
#25 0x0001 in ?? ()
No symbol table info available.
#26 0x558168af3af0 in ?? () at ../src/main.c:337

** Affects: glib2.0 (Ubuntu)
 Importance: High
 Status: Won't Fix


** Tags: regression-update
-- 
[regression] Unreadable stack traces since upgrading to gjs 1.52.1 and glib 
2.56.1-2ubuntu1
https://bugs.launchpad.net/bugs/1764216
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to glib2.0 in Ubuntu.

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

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

2018-04-15 Thread Jean-Baptiste Lallement

** Tags removed: rls-bb-incoming

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

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

Status in ca-certificates package in Ubuntu:
  Triaged

Bug description:
  upgrading ca-certificates fails with:
  Updating certificates in /etc/ssl/certs...
  rehash: skipping duplicate certificate in Go_Daddy_Class_2_CA.pem
  dpkg: error processing package ca-certificates (--configure):
   installed ca-certificates package post-installation script subprocess 
returned error exit status 1

  or

  rehash: skipping duplicate certificate in UbuntuOne-Go_Daddy_Class_2_CA.pem
  dpkg: error processing package ca-certificates (--configure):
   installed ca-certificates package post-installation script subprocess 
returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: ca-certificates 20180409
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Sun Apr 15 08:32:40 2018
  ErrorMessage: installed ca-certificates package post-installation script 
subprocess returned error exit status 1
  InstallationDate: Installed on 2015-03-19 (1122 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-2
  PythonDetails: /usr/bin/python2.7, Python 2.7.14+, python-minimal, 2.7.14-4
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu1
   apt  1.6~beta1
  SourcePackage: ca-certificates
  Title: package ca-certificates 20180409 failed to install/upgrade: installed 
ca-certificates package post-installation script subprocess returned error exit 
status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ca-certificates/+bug/1764060/+subscriptions

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

[Touch-packages] [Bug 1764252] Re: X-KDE-SubstituteUID=true / root can't be used in wayland

2018-04-15 Thread Daniel van Vugt

** Package changed: wayland (Ubuntu) => kwin (Ubuntu)

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

Title:
  X-KDE-SubstituteUID=true / root can't be used in wayland

Status in kwin package in Ubuntu:
  New

Bug description:
  Hello,

  kubuntu 18.04 beta 1

  I often use :

  X-KDE-SubstituteUID=true
  X-KDE-Username=root

  in the file ".desktop" for applications who may have root id.

  Example, luckybackup, system-config-samba

  No bug in a plasma session.

  With wayland, using the same desktop, the application asked for passwd
  and then stop.

  I understood that is for security reasons. That's means all the
  "graphics" applications needing root id are prohibited.

  Sorry, english is not my native langage.

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

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

[Touch-packages] [Bug 1764252] Re: X-KDE-SubstituteUID=true / root can't be used in wayland

2018-04-15 Thread trotosa

** Description changed:

  Hello,
  
  kubuntu 18.04 beta 1
  
  I often use :
  
  X-KDE-SubstituteUID=true
  X-KDE-Username=root
  
  in the file ".desktop" for applications who may have root id.
  
  Example, luckybackup, system-config-samba
  
  No bug in a plasma session.
  
  With wayland, using the same desktop, the application asked for passwd
  and then stop.
  
+ I understood that is for security reasons. That's means all the
+ "graphics" applications needing root id are prohibited.
+ 
  Sorry, english is not my native langage.

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

Title:
  X-KDE-SubstituteUID=true / root can't be used in wayland

Status in kwin package in Ubuntu:
  New

Bug description:
  Hello,

  kubuntu 18.04 beta 1

  I often use :

  X-KDE-SubstituteUID=true
  X-KDE-Username=root

  in the file ".desktop" for applications who may have root id.

  Example, luckybackup, system-config-samba

  No bug in a plasma session.

  With wayland, using the same desktop, the application asked for passwd
  and then stop.

  I understood that is for security reasons. That's means all the
  "graphics" applications needing root id are prohibited.

  Sorry, english is not my native langage.

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

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

[Touch-packages] [Bug 1716900] Re: apt-get: order of the dependencies ends in a diffrent result

2018-04-15 Thread Matthias Klumpp

** Package changed: appstream (Ubuntu) => apt (Ubuntu)

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

Title:
  apt-get: order of the dependencies ends in a diffrent result

Status in apt package in Ubuntu:
  New

Bug description:
  While trying to use the php installation delivered by
  https://launchpad.net/%7Eondrej/+archive/ubuntu/php, we found out,
  that the order within apt-get install change the solved packages.

  Which means if we do:
  apt-get install php-apcu php7.1-cli => installs newest php and 7.1
  apt-get install php7.1-cli php-apcu) => > installs only 7.1

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

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

[Touch-packages] [Bug 1764252] [NEW] X-KDE-SubstituteUID=true / root can't be used in wayland

2018-04-15 Thread trotosa

Public bug reported:

Hello,

kubuntu 18.04 beta 1

I often use :

X-KDE-SubstituteUID=true
X-KDE-Username=root

in the file ".desktop" for applications who may have root id.

Example, luckybackup, system-config-samba

No bug in a plasma session.

With wayland, using the same desktop, the application asked for passwd
and then stop.

I understood that is for security reasons. That's means all the
"graphics" applications needing root id are prohibited.

Sorry, english is not my native langage.

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

** Description changed:

  Hello,
  
  kubuntu 18.04 beta 1
  
  I often use :
  
  X-KDE-SubstituteUID=true
  X-KDE-Username=root
  
- in the file ".desktop" for applications who me have root id.
+ in the file ".desktop" for applications who may have root id.
  
  Example, luckybackup, system-config-samba
  
  No bug in a plasma session.
  
- 
- With wayland, using the same desktop, the application asked for passwd and 
then stop.
- 
+ With wayland, using the same desktop, the application asked for passwd
+ and then stop.
  
  Sorry, english is not my native langage.

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

Title:
  X-KDE-SubstituteUID=true / root can't be used in wayland

Status in wayland package in Ubuntu:
  New

Bug description:
  Hello,

  kubuntu 18.04 beta 1

  I often use :

  X-KDE-SubstituteUID=true
  X-KDE-Username=root

  in the file ".desktop" for applications who may have root id.

  Example, luckybackup, system-config-samba

  No bug in a plasma session.

  With wayland, using the same desktop, the application asked for passwd
  and then stop.

  I understood that is for security reasons. That's means all the
  "graphics" applications needing root id are prohibited.

  Sorry, english is not my native langage.

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

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

[Touch-packages] [Bug 1716900] [NEW] apt-get: order of the dependencies ends in a diffrent result

2018-04-15 Thread Launchpad Bug Tracker

You have been subscribed to a public bug:

While trying to use the php installation delivered by
https://launchpad.net/%7Eondrej/+archive/ubuntu/php, we found out, that
the order within apt-get install change the solved packages.

Which means if we do:
apt-get install php-apcu php7.1-cli => installs newest php and 7.1
apt-get install php7.1-cli php-apcu) => > installs only 7.1

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

-- 
apt-get: order of the dependencies ends in a diffrent result
https://bugs.launchpad.net/bugs/1716900
You received this bug notification because you are a member of Ubuntu Touch 
seeded packages, which is subscribed to apt in Ubuntu.

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

[Touch-packages] [Bug 1749101] Re: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-04-15 Thread Launchpad Bug Tracker

[Expired for openssh (Ubuntu) because there has been no activity for 60
days.]

** Changed in: openssh (Ubuntu)
   Status: Incomplete => Expired

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

Title:
  package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in openssh package in Ubuntu:
  Expired

Bug description:
  package openssh-server 1:7.2p2-4ubuntu2.4 failed

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: openssh-server 1:7.2p2-4ubuntu2.4
  ProcVersionSignature: Ubuntu 4.4.0-112.135-generic 4.4.98
  Uname: Linux 4.4.0-112-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  Date: Tue Feb 13 08:32:25 2018
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-09-27 (503 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.24
  SSHDConfig:
   Error: command ['/usr/sbin/sshd', '-T'] failed with exit code 255: 
/etc/ssh/sshd_config: line 89: Bad configuration option: OD
   /etc/ssh/sshd_config: terminating, 1 bad configuration options
  SourcePackage: openssh
  Title: package openssh-server 1:7.2p2-4ubuntu2.4 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

2018-04-15 Thread Trent Lloyd

** Patch added: "lp1752411-avahi-host-timeout.diff"
   
https://bugs.launchpad.net/ubuntu/+source/avahi/+bug/1752411/+attachment/5117372/+files/lp1752411-avahi-host-timeout.diff

** Changed in: avahi (Ubuntu)
 Assignee: (unassigned) => Trent Lloyd (lathiat)

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Confirmed
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid

Bug description:
  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago)

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

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

[Touch-packages] [Bug 1752411] Re: bind9-host, avahi-daemon-check-dns.sh hang forever causes network connections to get stuck

2018-04-15 Thread Trent Lloyd

With host -d I simply get

> Trying "local"

When it works normally I get;

Trying "local"
Host local. not found: 3(NXDOMAIN)
Received 98 bytes from 10.48.134.6#53 in 1 ms
Received 98 bytes from 10.48.134.6#53 in 1 ms

The system I am hitting this issue on is an upgraded system (rather than
a fresh install which wouldn't use ifupdown)

Because this is a serious issue for bionic upgraders I am attaching a
debdiff to use 'timeout' to fix the issue for now because release is
imminent.  Core issue with 'host' probably still needs to be
investigated (as this may add 5s delays to boot-up) however the timeout
is probably a good backup anyway.  In some ways potentially the entire
check-dns script should probably be launched under timeout.

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

Title:
  bind9-host, avahi-daemon-check-dns.sh hang forever causes network
  connections to get stuck

Status in avahi package in Ubuntu:
  Confirmed
Status in bind9 package in Ubuntu:
  Confirmed
Status in openconnect package in Ubuntu:
  Invalid

Bug description:
  On 18.04 Openconnect connects successfully to any of multiple VPN
  concentrators but network traffic does not flow across the VPN tunnel
  connection. When testing on 16.04 this works flawlessly. This also
  worked on this system when it was on 17.10.

  I have tried reducing the mtu of the tun0 network device but this has
  not resulted in me being able to successfully ping the IP address.

  Example showing ping attempt to the IP of DNS server:

  ~$ cat /etc/resolv.conf 
  # Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
  # DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
  # 127.0.0.53 is the systemd-resolved stub resolver.
  # run "systemd-resolve --status" to see details about the actual nameservers.

  nameserver 172.29.88.11
  nameserver 127.0.0.53

  liam@liam-lat:~$ netstat -nr
  Kernel IP routing table
  Destination Gateway Genmask Flags   MSS Window  irtt Iface
  0.0.0.0 192.168.1.1 0.0.0.0 UG0 0  0 
wlp2s0
  105.27.198.106  192.168.1.1 255.255.255.255 UGH   0 0  0 
wlp2s0
  169.254.0.0 0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.17.0.0  0.0.0.0 255.255.0.0 U 0 0  0 
docker0
  172.29.0.0  0.0.0.0 255.255.0.0 U 0 0  0 tun0
  172.29.88.110.0.0.0 255.255.255.255 UH0 0  0 tun0
  192.168.1.0 0.0.0.0 255.255.255.0   U 0 0  0 
wlp2s0
  liam@liam-lat:~$ ping 172.29.88.11
  PING 172.29.88.11 (172.29.88.11) 56(84) bytes of data.
  ^C
  --- 172.29.88.11 ping statistics ---
  4 packets transmitted, 0 received, 100% packet loss, time 3054ms

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: openconnect 7.08-3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
  Uname: Linux 4.15.0-10-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 28 22:11:33 2018
  InstallationDate: Installed on 2017-06-15 (258 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: openconnect
  UpgradeStatus: Upgraded to bionic on 2018-02-22 (6 days ago)

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

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

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

While logged in via ssh to the machine with the "hung" Xorg (screen
blank, no way to recover except Alt-SysRq-k), I dumped the output of
Alt-SysRq-t into the syslog -- see attached file. Not sure this is much
use, however. Just trying to be complete while I'm on-site with a hung
machine.

** Attachment added: "syslog with output from Alt-SysRq-t in ssh session"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117347/+files/syslog

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

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Bug description:
I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
LTS and 16.04. As we have gradually transitioned them to 16.04, we
have noticed that the machines running 16.04.1 now regularly exhibit
problems restoring from the blank screen which appears after a period
of inactivity.

This only occurs on the machines where we've installed 16.04. All of
the 16.04.1 installations are "fresh", that is, complete re-installs
from scratch, and we install all security and other updates on a
regular basis. This problem has persisted right from the beginning
when we started using 16.04.

Following a period of user inactivity, the screen goes blank; this is,
of course, expected. When the user tries to restore the session by
typing a key or moving the mouse, one of three outcomes occurs.

Sometimes, the session restores normally. Other times, the screen
remains blank regardless of all normal keyboard input, until a magic
SysRq sequence is performed. After Alt-SysRq-k, either the virtual
console resets to a login screen (as expected after this SysRq
sequence), or we get a kernel panic text screen (see attached screen
photo) and can only restore via a hard power-cycle reboot.

I will continue to try to capture a better trace output from one of
these conditions, perhaps from /var/log/kern.log or by installing
linux-crashdump (although these old machines may not have enough
memory for the stock package). But in the meantime, I'm attaching a
photo of the kernel panic we see, which suggests a problem may reside
in the Radeon driver ... which would seem possible, given the general
blank-screen no-resume problem on these systems.

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

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

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

Further debugging today while I'm on-site with the kiosks.  The system
froze, as usual, after normal idle screen blanking.  I was able to login
via ssh and retrieve some details.

First, it appears that the basic screen blanking problem is somehow
related to the Radeon driver.  I will attach the Xorg.0.log file and a
gdb backtrace on the running but non-responsive Xorg process.  No
keyboard or mouse activity will un-blank the screen.

Here's the output from lspci | grep VGA:

01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV516 
[Radeon X1300/X1550 Series]

I'll also attach the PCI ROM dump from the /sys/devices rom file for
this device.

This suggests that when we use Alt-SysRq-k to restore the system,
sometimes we trigger *another* bug in the driver which results in the
overall system crash.  See the attached apr1.full.kern.log file for what
details I could recover from the crash on April 1st; that corresponds to
the screen photo I took that day (the radeon_kernel_panic1.jpg
attachment).

The Xorg "hang" bug which precedes this appears similar, but not
identical, to what is documented in #1664979:

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1664979

I will continue to try to study the live Xorg process to see if I can
determine where its hung, but I may not have time this evening.  Let me
know if there are specific further debugging steps I can take to examine
either the Xorg hang or the subsequent crash which (sometimes) follows
on attempting to recover with Alt-SysRq-k.  (And note that I'll copy in
the files apport-bug generated from #1764211 later tonight, using my
"cdarroch" personal account, and then I'll try to close that extra bug
report.)

Thanks very much,
Chris.

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

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

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

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

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

** Attachment added: "Xorg.0.log"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117322/+files/Xorg.0.log

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

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

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

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

** Attachment added: "gdb-Xorg.txt"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117324/+files/gdb-Xorg.txt

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

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

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

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

** Attachment added: "rom.vga.bin"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117323/+files/rom.vga.bin

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

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

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

[Touch-packages] [Bug 1764229] Re: dbus-send crashed with SIGABRT during GUI login process

2018-04-15 Thread Apport retracing service

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

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

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

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

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

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

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

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

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

** This bug has been marked a duplicate of private bug 1751483

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

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

Title:
  dbus-send crashed with SIGABRT during GUI login process

Status in dbus package in Ubuntu:
  New

Bug description:
  I dunno - this happened after I rebooted and logged in

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: dbus 1.12.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  Date: Mon Apr 16 08:43:15 2018
  ExecutablePath: /usr/bin/dbus-send
  InstallationDate: Installed on 2018-04-13 (2 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409)
  ProcCmdline: dbus-send --system --print-reply 
--dest=org.freedesktop.NetworkManager 
/org/freedesktop/NetworkManager/IP4Config/0 org Get
  ProcEnviron:
   LANG=en_NZ.UTF-8
   SHELL=/bin/bash
   TERM=xterm-256color
   LANGUAGE=en_NZ:en
   PATH=(custom, user)
  Signal: 6
  SourcePackage: dbus
  StacktraceTop:
   _dbus_abort () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   _dbus_warn_check_failed () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   dbus_message_new_method_call () from /lib/x86_64-linux-gnu/libdbus-1.so.3
   ?? ()
   __libc_start_main (main=0x5f8c6d10, argc=6, argv=0x7fff3ecc3f98, 
init=, fini=, rtld_fini=, 
stack_end=0x7fff3ecc3f88) at ../csu/libc-start.c:310
  Title: dbus-send crashed with SIGABRT in _dbus_abort()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

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

[Touch-packages] [Bug 1301607] Re: Ambiance Combo box - dark highlighted text and scroll arrows

2018-04-15 Thread Daniel van Vugt

** Summary changed:

- Ambiance Combo box - black highlighted text and scroll arrows
+ Ambiance Combo box - dark highlighted text and scroll arrows

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

Title:
  Ambiance Combo box - dark highlighted text and scroll arrows

Status in One Hundred Papercuts:
  Triaged
Status in Ubuntu theme:
  Confirmed
Status in ubuntu-themes package in Ubuntu:
  Triaged

Bug description:
  To reproduce:
  Open files
  Right-click on any file or folder and select properties
  On permissions, open any combobox

  The highlighted item has black text over orange background, but I'm pretty 
sure should be white over orange.
  Also, scroll arrows (when the box reaches the top or bottom of the screen) 
are black over dark gray, barely visibles.

  I'm pretty sure this is not by design, and also could be an usability
  issue due to the lack of contrast.

  Screenshot attached.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: unity 7.1.2+14.04.20140321-0ubuntu1
  ProcVersionSignature: Ubuntu 3.13.0-19.40-generic 3.13.6
  Uname: Linux 3.13.0-19-generic i686
  ApportVersion: 2.13.3-0ubuntu1
  Architecture: i386
  CasperVersion: 1.339
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CurrentDesktop: Unity
  Date: Wed Apr  2 20:33:10 2014
  LiveMediaBuild: Ubuntu 14.04 LTS "Trusty Tahr" - Beta i386 (20140326)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: unity
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1764049] Re: [ALC256] [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card

2018-04-15 Thread Daniel van Vugt

** Summary changed:

- [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card
+ [ALC256] [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card

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

Title:
  [ALC256] [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to
  detect card

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Audio is very glitchy through speakers while using any application.
  Have tried a lot of different things, and configured my audio, but
  still can not get audio to not skip. I'm using Ubuntu 16.04

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   chuck  1786 F...m pulseaudio
   /dev/snd/controlC0:  chuck  1786 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 14 22:31:49 2018
  InstallationDate: Installed on 2018-03-12 (33 days ago)
  InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 
(20180228)
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: HDA-Intel - HDA Intel PCH
  Title: [HDA-Intel - HDA Intel PCH, playback] Pulseaudio fails to detect card
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/20/2017
  dmi.bios.vendor: AMI
  dmi.bios.version: F.36
  dmi.board.asset.tag: 8CC7460L0N
  dmi.board.name: 81BB
  dmi.board.vendor: HP
  dmi.board.version: 
  dmi.chassis.asset.tag: 8CC7460L0N
  dmi.chassis.type: 13
  dmi.chassis.vendor: HP
  dmi.modalias: 
dmi:bvnAMI:bvrF.36:bd07/20/2017:svnHP:pn20-c013w:pvr:rvnHP:rn81BB:rvr:cvnHP:ct13:cvr:
  dmi.product.family: 103C_53316J HP Desktop
  dmi.product.name: 20-c013w
  dmi.sys.vendor: HP
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.pulse.default.pa: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2018-04-04T21:49:05.382211
  mtime.conffile..etc.pulse.default.pa: 2018-04-14T20:03:46.503451

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

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

[Touch-packages] [Bug 1763764] Re: Context menu up & down arrows are not themed

2018-04-15 Thread Daniel van Vugt

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

Looks like a continuation of bug 1301607.

** This bug has been marked a duplicate of bug 1301607
   Ambiance Combo box - black highlighted text and scroll arrows

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

Title:
  Context menu up & down arrows are not themed

Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  When you press right-click to bring up the context menu of a
  selection, if the menu is too tall, you will see up and down arrows to
  be able to see all menu items.

  In Ambiance, those arrows are not themed.

  Steps:

  1. Install and launch synaptic
  2. Search for libreoffice
  3. Right-click on libreoffice
  4. Go to "Mark Suggested for Installation"
  5. A very tall menu will appear
  6. Up & down arrows are not themed

  This bug exists in all context menus, not only in Synaptic.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 13 17:31:01 2018
  InstallationDate: Installed on 2017-10-02 (192 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (16 days ago)

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

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

[Touch-packages] [Bug 1763940] Re: Pressing Print Screen in keyboard makes Rhythmbox go to sleep

2018-04-15 Thread Daniel van Vugt

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

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

Title:
  Pressing Print Screen in keyboard makes Rhythmbox go to sleep

Status in pulseaudio package in Ubuntu:
  New
Status in rhythmbox package in Ubuntu:
  New

Bug description:
  Steps:

  1. Start Rhythmbox and play music
  2. Press Print Screen in keyboard
  3. Music stops and cannot be played again in Rhythmbox
  4. If the music does not stop from the first time try step 2 again and again 
until it stops

  I can navigate the UI of Rhythmbox, but I cannot play music. I have to
  kill the sleeping process in order to play music.

  I can reproduce this bug in Totem and Clementine too.

  Clementine and Totem present this error:

  pa_stream_writable_size() failed: Connection terminated

  This bug affects Bionic too.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.8
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  amr9438 F pulseaudio
  CurrentDesktop: Unity
  Date: Sat Apr 14 14:42:55 2018
  InstallationDate: Installed on 2017-06-21 (296 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: pulseaudio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/08/2011
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F2
  dmi.board.name: GA-78LMT-S2P
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF2:bd04/08/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-78LMT-S2P:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-78LMT-S2P:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: GA-78LMT-S2P
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  modified.conffile..etc.pulse.daemon.conf: [modified]
  modified.conffile..etc.xdg.autostart.pulseaudio.desktop: [modified]
  mtime.conffile..etc.pulse.daemon.conf: 2017-07-04T15:49:08
  mtime.conffile..etc.xdg.autostart.pulseaudio.desktop: 2017-06-22T13:08:09

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

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

[Touch-packages] [Bug 1762545] Re: No dashed line to indicate that more content is scrollable

2018-04-15 Thread Daniel van Vugt

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

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

Title:
  No dashed line to indicate that more content is scrollable

Status in Ubuntu theme:
  New
Status in ubuntu-themes package in Ubuntu:
  New

Bug description:
  Ambiance does not show a dashed line to indicate that more content is
  scrollable. I have been using another theme than Ambiance for some
  time and I find the dashed line very helpful.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: light-themes 16.10+18.04.20180328-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Apr  9 22:25:00 2018
  InstallationDate: Installed on 2017-10-02 (189 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Beta amd64 (20170930)
  PackageArchitecture: all
  SourcePackage: ubuntu-themes
  UpgradeStatus: Upgraded to bionic on 2018-03-27 (13 days ago)

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

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

[Touch-packages] [Bug 1759628] Re: bluez regression: Bluetooth audio fails to reconnect after resume

2018-04-15 Thread Daniel van Vugt

"Mature" means it hasn't changed in a while and we know what bugs it
contains. "Mature" does not mean zero bugs, but at least by not changing
it at the last minute we don't risk introducing bigger bugs. And this
bug is not big at all.

As an example, just today the "gjs" package has blown up with lots of
new crashes that didn't exist last week. This was caused by an
unnecessary upgrade of a previously mature package, and it looks like it
may risk the whole 18.04 release. That is why you shouldn't change
things late in the release cycle.

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

Title:
   bluez regression: Bluetooth audio fails to reconnect after resume

Status in bluez package in Ubuntu:
  Triaged
Status in bluez package in Fedora:
  Fix Released
Status in Suse:
  Fix Released

Bug description:
  STEPS TO REPRODUCE:
  1. Connect to Bluetooth audio device
  2. Suspend & Resume
  3. Reconnect to Bluetooth device.

  This regression in bluez 5.48 has already been identified and fixed
  upstream. Report is here  and patch is here
  
.

  Syslog reports messages as follows when this issue is happening (I have 
replaced my device's MAC address with [MAC]):
  Mar 28 12:34:29 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:29 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Mar 28 12:34:33 cue pulseaudio[1859]: [pulseaudio] bluez5-util.c: Information 
about device /org/bluez/hci0/dev_[MAC] is invalid
  Mar 28 12:34:33 cue bluetoothd[984]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments

  Workaround is to run sudo systemctl restart bluetooth after resume.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: bluez 5.48-0ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7
  Uname: Linux 4.15.0-12-generic x86_64
  ApportVersion: 2.20.9-0ubuntu1
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Mar 28 12:37:11 2018
  InstallationDate: Installed on 2018-03-23 (5 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 
(20180306.1)
  InterestingModules: rfcomm bnep btusb bluetooth
  MachineType: Hewlett-Packard HP ProBook 640 G1
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-12-generic 
root=/dev/mapper/internal-root ro quiet splash vt.handoff=1
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/25/2018
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: L78 Ver. 01.43
  dmi.board.name: 2101
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 16.3C
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvrL78Ver.01.43:bd01/25/2018:svnHewlett-Packard:pnHPProBook640G1:pvrA3009DD10303:rvnHewlett-Packard:rn2101:rvrKBCVersion16.3C:cvnHewlett-Packard:ct10:cvr:
  dmi.product.family: 103C_5336AN G=N L=BUS B=HP S=PRO
  dmi.product.name: HP ProBook 640 G1
  dmi.product.version: A3009DD10303
  dmi.sys.vendor: Hewlett-Packard
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 80:00:0B:C7:4D:1C  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:5025 acl:32 sco:0 events:202 errors:0
TX bytes:5785 acl:32 sco:0 commands:103 errors:0

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

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

[Touch-packages] [Bug 1763975] Re: DP1.2 daisy-chain flickering

2018-04-15 Thread Stuart

@update. Started occurring even when bypassing the Avocent.

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

Title:
  DP1.2 daisy-chain flickering

Status in xorg package in Ubuntu:
  New

Bug description:
  Hi all,

  I have a NUC7i7BNH with the latest BIOS (0062) running Ubuntu 18.04
  (uname -r = 4.15.0-15-generic). I have the NUC connected via USB-C to
  DisplayPort, to an Avocent SV340D KVM, then to a Dell U2415 which has
  DP1.2 enabled and is daisy-chainged to another Dell U2415 (DP1.2
  disabled on the second monitor as per Dell instructions).

  I am getting flickering whereby randomly display1 or display2 turn
  black and then back on again. When I disable DP1.2 on the display1,
  and therefore get a duplicate display (as opposed to extended) on
  display2, I get no flickering at all.

  The same setup yields no flickering when running from a Windows 10
  box, so don't think it is the monitors.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu6
  ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
  Uname: Linux 4.15.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu4
  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: Sat Apr 14 12:52:24 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Device [8086:5927] (rev 06) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:2068]
  InstallationDate: Installed on 2018-04-01 (12 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180401)
  MachineType: Intel Corporation NUC7i7BNH
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-15-generic.efi.signed 
root=/dev/mapper/ubuntu--vg-root ro quiet splash
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/22/2018
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BNKBL357.86A.0062.2018.0222.1644
  dmi.board.name: NUC7i7BNB
  dmi.board.vendor: Intel Corporation
  dmi.board.version: J31145-307
  dmi.chassis.type: 3
  dmi.chassis.vendor: Intel Corporation
  dmi.chassis.version: 2
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBNKBL357.86A.0062.2018.0222.1644:bd02/22/2018:svnIntelCorporation:pnNUC7i7BNH:pvrJ31153-308:rvnIntelCorporation:rnNUC7i7BNB:rvrJ31145-307:cvnIntelCorporation:ct3:cvr2:
  dmi.product.family: Intel NUC
  dmi.product.name: NUC7i7BNH
  dmi.product.version: J31153-308
  dmi.sys.vendor: Intel Corporation
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu3
  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

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

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

[Touch-packages] [Bug 1549163] Re: Bluetooth headset HSP/HFP mode not working in Xenial

2018-04-15 Thread Daniel van Vugt

if you have any ongoing issues then open a new bug.

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

Title:
  Bluetooth headset HSP/HFP mode not working in Xenial

Status in HWE Next:
  Fix Released
Status in pulseaudio package in Ubuntu:
  Fix Released

Bug description:
  Using the 2/14 Xenial daily build, paired bluetooth headsets' do not
  work in HSP/HFP mode.

  [Steps to reproduce]
  1. Pair a bluetooth headset with laptop installed with Xenial 2/14 daily build
  2. In the laptop, go to sound settings > output tab > try switching mode to 
HSP/HFP mode
  3. Press the "test sound" button and try playing sound
  4. Go to the input tab and check if bluetooth headset mic is listed

  [Expected result]
  After step 3, a window for mono audio test should pop up
  After step 4, the input tab should list a bluetooth headset mic device

  [Actual result]
  After step 3, the window that pops up is for stereo (A2DP) audio test
  After step 4, the input tab does not list any bluetooth headset mic

  [Details]
  BT wireless module:
   * Intel 3160
  BT headset:
   * Jabra CLI
  Xenial: 2/14 daily build:
   * Kernel: 4.4.0-6
   * bluez: 5.36-0ubuntu1
   * gstreamer1.0-pulseaudio:amd64: 1.7.2-1ubuntu1
   * pulseaudio: 1:8.0-0ubuntu2
   * pulseaudio-module-bluetooth: 1:8.0-0ubuntu2

  [Note]
  Also double checked with same set of hardware, but with 15.10 installed.
  Bluetooth headset HSP/HFP mode worked correctly in 15.10.

  15.10 details:
   * kernel: 4.2.0-19
   * bluez: 5.35-0ubuntu2
   * gstreamer1.0-pulseaudio:amd64: 1.6.0-1ubuntu1
   * pulseaudio: 1:6.0-0ubuntu13
   * pulseaudio-module-bluetooth: 1:6.0-0ubuntu13

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1549163/+subscriptions

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

[Touch-packages] [Bug 1763839] Re: [FFe] apt 1.6~rc1, zstd & hook support

2018-04-15 Thread Balint Reczey

** Description changed:

- As discussed previously, we want to have zstd support in 16.04 to evaluate 
and potentially enable it in later releases. We also want to add hooks for
+ As discussed previously, we want to have zstd support in 18.04 to evaluate 
and potentially enable it in later releases. We also want to add hooks for
  snap integration to apt, this release is supposed to add them too.
  
  The new features are not invasive - they are new code with a few places
  too hook them in. If no zstd is used, or if no hooks are registered,
  then there will be basically no change in behavior (or code paths).
  
  # FEATURE: zstd
  The zstd support adds a dependency on libzstd1 to libapt-pkg5.0. This should 
not have any effect on live images, since libzstd1 is part of the various live 
tasks, as btrfs-progs need it. For installed systems, this might be a new 
dependency (if they do not use btrfs, tor, or some other tools), so an increase 
of ~520 KB, as that's the size of the library and the library only depends on 
libc6.
  
  This also depends on the zstd patch in dpkg being uploaded. If this
  unexpectedly does not happen, and I upload apt first, I'd revert it
  later before the release.
  
  # FEATURE: hooks
  The concrete code is still undergoing review, some option names might change 
for the hooks before release (e.g. pre-download might become 
pre-install-prompt, and the AptCli::Hooks config section only gets Install and 
Search lists for hooks to register, rather than individual pre-, post-, and 
fail- lists).
  
  # other changes
  We disable the seccomp sandbox for methods for the release, as it turns out 
there are still too many failure cases for it to be worthwhile to enable (NSS 
modules, weird libc functions calling weird syscalls, etc). People can 
re-enable it with a config option.
  
  the rest is bug fixes. some change translatable strings in
  documentation, but fix up the translation too. A few additional strings
  are added to the sources.list man page ("mention mirror method in
  sources.list (Closes: 679580)", but I'm happy to back them out.
  
  There are also some CI fixes, and the major cache version is bumped so
  we can issue updates independently for 1.5 and 1.6 apt release series.
  
  The attached patch is thus preliminary but should be fairly identical to
  the final result.

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

Title:
  [FFe] apt 1.6~rc1, zstd & hook support

Status in apt package in Ubuntu:
  New

Bug description:
  As discussed previously, we want to have zstd support in 18.04 to evaluate 
and potentially enable it in later releases. We also want to add hooks for
  snap integration to apt, this release is supposed to add them too.

  The new features are not invasive - they are new code with a few
  places too hook them in. If no zstd is used, or if no hooks are
  registered, then there will be basically no change in behavior (or
  code paths).

  # FEATURE: zstd
  The zstd support adds a dependency on libzstd1 to libapt-pkg5.0. This should 
not have any effect on live images, since libzstd1 is part of the various live 
tasks, as btrfs-progs need it. For installed systems, this might be a new 
dependency (if they do not use btrfs, tor, or some other tools), so an increase 
of ~520 KB, as that's the size of the library and the library only depends on 
libc6.

  This also depends on the zstd patch in dpkg being uploaded. If this
  unexpectedly does not happen, and I upload apt first, I'd revert it
  later before the release.

  # FEATURE: hooks
  The concrete code is still undergoing review, some option names might change 
for the hooks before release (e.g. pre-download might become 
pre-install-prompt, and the AptCli::Hooks config section only gets Install and 
Search lists for hooks to register, rather than individual pre-, post-, and 
fail- lists).

  # other changes
  We disable the seccomp sandbox for methods for the release, as it turns out 
there are still too many failure cases for it to be worthwhile to enable (NSS 
modules, weird libc functions calling weird syscalls, etc). People can 
re-enable it with a config option.

  the rest is bug fixes. some change translatable strings in
  documentation, but fix up the translation too. A few additional
  strings are added to the sources.list man page ("mention mirror method
  in sources.list (Closes: 679580)", but I'm happy to back them out.

  There are also some CI fixes, and the major cache version is bumped so
  we can issue updates independently for 1.5 and 1.6 apt release series.

  The attached patch is thus preliminary but should be fairly identical
  to the final result.

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

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

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

Further details from apport-bug are in #1764211; I'll copy them into
this account using my "cdarroch" personal Launchpad account in a few
hours, when I get home.

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

Title:
  kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
  Incomplete
Status in xorg package in Ubuntu:
  New

Bug description:
  I maintain a set of older kiosks running a mix of stock Ubuntu 14.04
  LTS and 16.04.  As we have gradually transitioned them to 16.04, we
  have noticed that the machines running 16.04.1 now regularly exhibit
  problems restoring from the blank screen which appears after a period
  of inactivity.

  This only occurs on the machines where we've installed 16.04.  All of
  the 16.04.1 installations are "fresh", that is, complete re-installs
  from scratch, and we install all security and other updates on a
  regular basis.  This problem has persisted right from the beginning
  when we started using 16.04.

  Following a period of user inactivity, the screen goes blank; this is,
  of course, expected.  When the user tries to restore the session by
  typing a key or moving the mouse, one of three outcomes occurs.

  Sometimes, the session restores normally.  Other times, the screen
  remains blank regardless of all normal keyboard input, until a magic
  SysRq  sequence is performed.  After Alt-SysRq-k, either the virtual
  console resets to a login screen (as expected after this SysRq
  sequence), or we get a kernel panic text screen (see attached screen
  photo) and can only restore via a hard power-cycle reboot.

  I will continue to try to capture a better trace output from one of
  these conditions, perhaps from /var/log/kern.log or by installing
  linux-crashdump (although these old machines may not have enough
  memory for the stock package).  But in the meantime, I'm attaching a
  photo of the kernel panic we see, which suggests a problem may reside
  in the Radeon driver ... which would seem possible, given the general
  blank-screen no-resume problem on these systems.

  Any advice on how to further capture any other needed details would be
  appreciated.  Thanks very much!

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

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

[Touch-packages] [Bug 1763892] Re: 144Hz/120Hz monitor but Wayland sessions seem to cap rendering at 60FPS

2018-04-15 Thread Daniel van Vugt

Thanks for the bug report. It's been a known issue for a while:
https://bugzilla.gnome.org/show_bug.cgi?id=781296

** Bug watch added: GNOME Bug Tracker #781296
   https://bugzilla.gnome.org/show_bug.cgi?id=781296

** Package changed: wayland (Ubuntu) => mutter (Ubuntu)

** Also affects: mutter via
   https://bugzilla.gnome.org/show_bug.cgi?id=781296
   Importance: Unknown
   Status: Unknown

** Changed in: mutter (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

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

Title:
  144Hz/120Hz monitor but Wayland sessions seem to cap rendering at
  60FPS

Status in Mutter:
  Unknown
Status in mutter package in Ubuntu:
  Confirmed

Bug description:
  Monitor is set to 144hz, but on Wayland it visually fails to go above
  60Hz.  On XOrg it  runs higher and feels much smoother.  I have
  confirmed the monitor is running at 144Hz during the Wayland session,
  and that is also the setting in the Settings control panel.

  Using the additional NVidia drivers installed using the Ubuntu
  software control panel.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: libwayland-bin (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-38.43-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.8
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Apr 14 08:43:29 2018
  DistUpgraded: Fresh install
  DistroCodename: artful
  DistroVariant: ubuntu
  GraphicsCard:
   NVIDIA Corporation GP104 [GeForce GTX 1070] [10de:1b81] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] GP104 [GeForce GTX 
1070] [1462:3301]
  InstallationDate: Installed on 2018-03-30 (14 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=4f8fe8e2-8445-4034-bae3-dc8afb789c64 ro quiet splash vt.handoff=7
  SourcePackage: wayland
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/11/2018
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0610
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME Z370-P
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0610:bd01/11/2018:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEZ370-P:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.83-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~17.10.1
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~17.10.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.5-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.10.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20170309-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

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

[Touch-packages] [Bug 1764211] Re: apport bug details for #1763273 (radeon crash while screen blank)

2018-04-15 Thread RBL Admin

When I get home I'll copy these attachments and data into the original
bug report under my personal Launchpad account.

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

Title:
  apport bug details for #1763273 (radeon crash while screen blank)

Status in xorg package in Ubuntu:
  New

Bug description:
  Unfortunately, I had to create a second bug report because apport-
  collect will not accept a different set of Launchpad user credentials
  from those I used to create the original bug report (#1763273).  My
  apologies, but I had to use a different Launchpad account to run
  apport-bug, so this is the result.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr 15 18:28:07 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7187] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] [174b:e020]
 Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] (Secondary) [174b:e021]
  InstallationDate: Installed on 2017-07-24 (265 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  ProcEnviron:
   LANGUAGE=en_CA:en
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_CA.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=fe381ac7-304a-4c28-b497-bdefa6602251 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/24/2007
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 2JKT30AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.modalias: 
dmi:bvnLENOVO:bvr2JKT30AUS:bd01/24/2007:svnLENOVO:pn8811BJ8:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvr:cvnLENOVO:ct7:cvr:
  dmi.product.name: 8811BJ8
  dmi.product.version: ThinkCentre M55
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Sun Apr 15 17:45:51 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputDell Dell USB Keyboard KEYBOARD, id 8
   inputUSB Optical MouseMOUSE, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7
  xserver.video_driver: radeon

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

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

[Touch-packages] [Bug 1764211] [NEW] apport bug details for #1763273 (radeon crash while screen blank)

2018-04-15 Thread RBL Admin

Public bug reported:

Unfortunately, I had to create a second bug report because apport-
collect will not accept a different set of Launchpad user credentials
from those I used to create the original bug report (#1763273).  My
apologies, but I had to use a different Launchpad account to run apport-
bug, so this is the result.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
Uname: Linux 4.4.0-119-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.15
Architecture: amd64
BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
Date: Sun Apr 15 18:28:07 2018
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] RV516 [Radeon X1300/X1550 Series] 
[1002:7187] (prog-if 00 [VGA controller])
   Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] [174b:e020]
   Subsystem: PC Partner Limited / Sapphire Technology RV516 [Radeon 
X1300/X1550 Series] (Secondary) [174b:e021]
InstallationDate: Installed on 2017-07-24 (265 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 LANGUAGE=en_CA:en
 TERM=xterm-256color
 PATH=(custom, no user)
 LANG=en_CA.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-119-generic 
root=UUID=fe381ac7-304a-4c28-b497-bdefa6602251 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/24/2007
dmi.bios.vendor: LENOVO
dmi.bios.version: 2JKT30AUS
dmi.board.name: LENOVO
dmi.chassis.vendor: LENOVO
dmi.modalias: 
dmi:bvnLENOVO:bvr2JKT30AUS:bd01/24/2007:svnLENOVO:pn8811BJ8:pvrThinkCentreM55:rvnLENOVO:rnLENOVO:rvr:cvnLENOVO:ct7:cvr:
dmi.product.name: 8811BJ8
dmi.product.version: ThinkCentre M55
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.83-1~16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Sun Apr 15 17:45:51 2018
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputDell Dell USB Keyboard KEYBOARD, id 8
 inputUSB Optical MouseMOUSE, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.7
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 freeze ubuntu xenial

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

Title:
  apport bug details for #1763273 (radeon crash while screen blank)

Status in xorg package in Ubuntu:
  New

Bug description:
  Unfortunately, I had to create a second bug report because apport-
  collect will not accept a different set of Launchpad user credentials
  from those I used to create the original bug report (#1763273).  My
  apologies, but I had to use a different Launchpad account to run
  apport-bug, so this is the result.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-119.143-generic 4.4.114
  Uname: Linux 4.4.0-119-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  BootLog: /dev/sda1: clean, 257395/9510912 files, 1925432/38014720 blocks
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sun Apr 15 18:28:07 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes

[Touch-packages] [Bug 1763273] Re: kernel panic in Radeon driver while screen blank

2018-04-15 Thread RBL Admin

** Attachment added: "Full kern.log from April 1 crash"

https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1763273/+attachment/5117229/+files/apr1.full.kern.log

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

Title:
kernel panic in Radeon driver while screen blank

Status in linux package in Ubuntu:
Incomplete
Status in xorg package in Ubuntu:
New

Any advice on how to further capture any other needed details would be
appreciated. Thanks very much!

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

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

82 matches

Mail list logo