date:20180214

** Changed in: apparmor (Ubuntu Xenial)
   Importance: Undecided => High

** Changed in: tor (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Confirmed
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

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

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

[Touch-packages] [Bug 1749247] Re: Spurious SEGV running inside kvm

Ok, this is just at the memcopy above.
I see in this trace that the AC_MEMCPY got mapped to __memmove_ssse3 of 
../sysdeps/x86_64/multiarch/memcpy-ssse3.S

Lets assume (for the sake of trying something until you have a simplified 
reproducer) that sse3 might be broken in KVM on your system.
I'd expect that the compile time detection switched to memmove and the runtime 
feature detection found sse3 and used that.
We could do two things to try here:
1. we could modify your guest to not expose sse3 and retest in there (-cpu 
qemu64/qemu32 will be without sse3 and without a lot other special HW features 
- if you run with -cpu host you can do "-enable-kvm -cpu host,-sse3" to just 
kill this feature). How do you start your KVM guest (commandline, libvirt, 
other - so we know how to help you modify?
2. we could try to influence the build to not use memmove but memcpy or bcopy 
instead and check if that makes it work.

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

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501 new->bv_val = NULL;
  502 new->bv_len = 0;
  503 return new;
  504 }
  (gdb) 
  505
  506 if(( new->bv_val = ber_memalloc_x( src->bv_len + 1, ctx )) == 
NULL ) {
  507 if ( !dst )
  508 ber_memfree_x( new, ctx );
  509 return NULL;
  510 }
  511
  512 AC_MEMCPY( new->bv_val, src->bv_val, src->bv_len );
  513 new->bv_val[src->bv_len] = '\0';
  514 new->bv_len = src->bv_len;
  (gdb) p *new
  $1 = {bv_len = 0, bv_val = 0x0}
  (gdb) p *src
  $2 = {bv_len = 36, bv_val = 0x7f268ccc7bee }
  (gdb) 

  
  At line 506 we allocate some memory and check for a failure (returning NULL) 
and leave the function at line 509 if there was a failure. The allocation is 
for 37 bytes of memory and a memcpy into that memory succeeds on line 512. The 
SEGV occurs at line 513 and the pointer that was just returned from the 
allocator is NULL at this point. There are no other active threads that could 
be stomping on memory, there's no stack overrun or any other misbehavior that 
can account for it. Also, the identical test sequence completes without 
incident when running on the host OS instead of under kvm.
  (The src->bv_val pointer points to valid data at the time of the crash; it's 
just residing in a mmap'd file and that mapping isn't preserved in the 
coredump. So ignore gdb's error there.)

  Something in kvm is writing zeroes over a field of memory after we
  already checked that it was non-zero.

  This is on 
  Linux anvil1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Both the host and the guest VM are on identical

[Touch-packages] [Bug 1729357] Re: unprivileged user can drop supplementary groups

2018-02-14 Thread Aleksa Sarai

I had a preliminary patch written, but it was getting quite complicated
(shadow's codebase is much more complicated than I expected -- and the
/etc/subgid parsing code is intertwined with the parsing code for all of
the other /etc/... files). I am working on it though.

I've also email the SUSE Security team about getting a CVE assigned,
though I'm not sure if it's better that we get it assigned or that the
Ubuntu folks get it assigned.

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

Title:
  unprivileged user can drop supplementary groups

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04.3 LTS
  Kernel: 4.4.0-97-generic
  uidmap package version: 1:4.2-3.1ubuntu5.3

  The newgidmap setuid executable allows any user to write a single
  mapping line to the gid_map of a process whose identity is the same as
  the calling process, as long as that mapping line maps the process's
  own GID outside of the user namespace to GID 0 inside the user
  namespace.

  Newgidmap will write the mapping regardless of the content of
  /proc/$process_being_mapped/setgroups, which will initially contain
  the string "allow". After this mapping is performed, and also after
  the process' uid_map is written with newuidmap, the process in the
  user namespace will be able to use the setgroups system call to drop
  supplementary groups.

  This is possible even if there is no entry for the user in
  /etc/subgid, because no subordinate GIDs are actually being used.

  This allows any user to circumvent the use of supplementary groups as
  blacklists, e.g. for some file owned by root:blacklist with permission
  bits 0604 (octal). Normally any process whose identity included the
  group "blacklist" in its supplementary groups would not be able to
  read that file. By performing this exploit using newgidmap, they can
  drop all supplementary groups and read that file.

  If newgidmap was not available, unprivileged users would not be able
  to write a process's gid_map until writing "deny" to
  /proc/$pid/setgroups. A fix for this might be for newgidmap to check
  the content of /proc/$process_being_mapped/setgroups is "deny", but we
  have not tried to patch this ourselves.

  An example using 2 login shells for a user named "someone" on Ubuntu
  Xenial, with the uidmap package installed:

  Shell 1

  someone@ubuntu-xenial:~$ id
  uid=1001(someone) gid=1001(someone) groups=1001(someone),1002(restricted)

  someone@ubuntu-xenial:~$ ls -al /tmp/should_restrict
  -rwr-- 1 root restricted 8 Nov  1 12:23 /tmp/should_restrict

  someone@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  someone@ubuntu-xenial:~$ unshare -U --setgroups allow #
  /proc/self/setgroups already contains 'allow', but let's be explicit

  nobody@ubuntu-xenial:~$ echo $$
  1878

  Shell 2

  someone@ubuntu-xenial:~$ cat /etc/subuid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  someone@ubuntu-xenial:~$ cat /etc/subgid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  # There are no entries in /etc/sub{u,g}id for someone, but this
  doesn't matter that much as subordinate IDs are not being requested.

  someone@ubuntu-xenial:~$ newuidmap 1878 0 1001 1

  someone@ubuntu-xenial:~$ newgidmap 1878 0 1001 1

  Back to shell 1

  nobody@ubuntu-xenial:~$ id
  uid=0(root) gid=0(root) groups=0(root),65534(nogroup)

  # The presence of the "nogroup" supplementary group indicates that
  some unmapped GIDs are present as supplementary GIDs. The kernel knows
  that this process still has "restricted" in its supplementary groups,
  so it can't read the restricted file yet.

  nobody@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  # The process has gained CAP_SETGID in its user namespace by becoming
  UID 0. /proc/$pid/setgroups contains "allow", so it can call
  setgroups(2). By su-ing to root (itself, in the user namespace), it
  can drop the supplementary groups. It can't read /root/.bashrc as that
  file is owned by UID 0 in the initial user namespace, which creates
  some distracting error output but doesn't matter in this case.

  nobody@ubuntu-xenial:~$ su root
  su: Authentication failure
  (Ignored)
  bash: /root/.bashrc: Permission denied

  # Supplementary groups have been dropped

  root@ubuntu-xenial:~# id
  uid=0(root) gid=0(root) groups=0(root)

  # It can read the restricted file

  root@ubuntu-xenial:~# cat /tmp/should_restrict
  content

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

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

[Touch-packages] [Bug 1729357] Re: unprivileged user can drop supplementary groups

2018-02-14 Thread Akihiro Suda

@cyphar

Did you submit patch/CVE?

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

Title:
  unprivileged user can drop supplementary groups

Status in shadow package in Ubuntu:
  Confirmed

Bug description:
  Distribution: Ubuntu 16.04.3 LTS
  Kernel: 4.4.0-97-generic
  uidmap package version: 1:4.2-3.1ubuntu5.3

  The newgidmap setuid executable allows any user to write a single
  mapping line to the gid_map of a process whose identity is the same as
  the calling process, as long as that mapping line maps the process's
  own GID outside of the user namespace to GID 0 inside the user
  namespace.

  Newgidmap will write the mapping regardless of the content of
  /proc/$process_being_mapped/setgroups, which will initially contain
  the string "allow". After this mapping is performed, and also after
  the process' uid_map is written with newuidmap, the process in the
  user namespace will be able to use the setgroups system call to drop
  supplementary groups.

  This is possible even if there is no entry for the user in
  /etc/subgid, because no subordinate GIDs are actually being used.

  This allows any user to circumvent the use of supplementary groups as
  blacklists, e.g. for some file owned by root:blacklist with permission
  bits 0604 (octal). Normally any process whose identity included the
  group "blacklist" in its supplementary groups would not be able to
  read that file. By performing this exploit using newgidmap, they can
  drop all supplementary groups and read that file.

  If newgidmap was not available, unprivileged users would not be able
  to write a process's gid_map until writing "deny" to
  /proc/$pid/setgroups. A fix for this might be for newgidmap to check
  the content of /proc/$process_being_mapped/setgroups is "deny", but we
  have not tried to patch this ourselves.

  An example using 2 login shells for a user named "someone" on Ubuntu
  Xenial, with the uidmap package installed:

  Shell 1

  someone@ubuntu-xenial:~$ id
  uid=1001(someone) gid=1001(someone) groups=1001(someone),1002(restricted)

  someone@ubuntu-xenial:~$ ls -al /tmp/should_restrict
  -rwr-- 1 root restricted 8 Nov  1 12:23 /tmp/should_restrict

  someone@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  someone@ubuntu-xenial:~$ unshare -U --setgroups allow #
  /proc/self/setgroups already contains 'allow', but let's be explicit

  nobody@ubuntu-xenial:~$ echo $$
  1878

  Shell 2

  someone@ubuntu-xenial:~$ cat /etc/subuid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  someone@ubuntu-xenial:~$ cat /etc/subgid
  lxd:10:65536
  root:10:65536
  ubuntu:165536:65536

  # There are no entries in /etc/sub{u,g}id for someone, but this
  doesn't matter that much as subordinate IDs are not being requested.

  someone@ubuntu-xenial:~$ newuidmap 1878 0 1001 1

  someone@ubuntu-xenial:~$ newgidmap 1878 0 1001 1

  Back to shell 1

  nobody@ubuntu-xenial:~$ id
  uid=0(root) gid=0(root) groups=0(root),65534(nogroup)

  # The presence of the "nogroup" supplementary group indicates that
  some unmapped GIDs are present as supplementary GIDs. The kernel knows
  that this process still has "restricted" in its supplementary groups,
  so it can't read the restricted file yet.

  nobody@ubuntu-xenial:~$ cat /tmp/should_restrict
  cat: /tmp/should_restrict: Permission denied

  # The process has gained CAP_SETGID in its user namespace by becoming
  UID 0. /proc/$pid/setgroups contains "allow", so it can call
  setgroups(2). By su-ing to root (itself, in the user namespace), it
  can drop the supplementary groups. It can't read /root/.bashrc as that
  file is owned by UID 0 in the initial user namespace, which creates
  some distracting error output but doesn't matter in this case.

  nobody@ubuntu-xenial:~$ su root
  su: Authentication failure
  (Ignored)
  bash: /root/.bashrc: Permission denied

  # Supplementary groups have been dropped

  root@ubuntu-xenial:~# id
  uid=0(root) gid=0(root) groups=0(root)

  # It can read the restricted file

  root@ubuntu-xenial:~# cat /tmp/should_restrict
  content

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

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

[Touch-packages] [Bug 1749630] Re: package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade: 10.4193:subprocess installed post-installation script returned error exit status 1

2018-02-14 Thread Apport retracing service

** Tags removed: need-duplicate-check

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

Title:
  package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade:
  10.4193:subprocess installed post-installation script returned error
  exit status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  An error occurred while upgrading to a new version of Bash on Ubuntu
  on Windows. Report was given and I decided to send the report.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libuuid1 2.27.1-6ubuntu3.4
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Wed Feb 14 21:05:15 2018
  DuplicateSignature: package:libuuid1:2.27.1-6ubuntu3.4:10.4193:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: 10.4193:subprocess installed post-installation script returned 
error exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.0.1ubuntu2.17
  SourcePackage: util-linux
  Title: package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade: 
10.4193:subprocess installed post-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to xenial on 2018-02-15 (0 days ago)

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

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

[Touch-packages] [Bug 1749630] [NEW] package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade: 10.4193:subprocess installed post-installation script returned error exit status 1

2018-02-14 Thread Ricardo I Soto

Public bug reported:

An error occurred while upgrading to a new version of Bash on Ubuntu on
Windows. Report was given and I decided to send the report.

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libuuid1 2.27.1-6ubuntu3.4
ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
Uname: Linux 4.4.0-43-Microsoft x86_64
ApportVersion: 2.14.1-0ubuntu3.23
Architecture: amd64
Date: Wed Feb 14 21:05:15 2018
DuplicateSignature: package:libuuid1:2.27.1-6ubuntu3.4:10.4193:subprocess 
installed post-installation script returned error exit status 1
ErrorMessage: 10.4193:subprocess installed post-installation script returned 
error exit status 1
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.3
 apt  1.0.1ubuntu2.17
SourcePackage: util-linux
Title: package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade: 
10.4193:subprocess installed post-installation script returned error exit 
status 1
UpgradeStatus: Upgraded to xenial on 2018-02-15 (0 days ago)

** Affects: util-linux (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-package dist-upgrade third-party-packages uec-images 
xenial

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

Title:
  package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade:
  10.4193:subprocess installed post-installation script returned error
  exit status 1

Status in util-linux package in Ubuntu:
  New

Bug description:
  An error occurred while upgrading to a new version of Bash on Ubuntu
  on Windows. Report was given and I decided to send the report.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libuuid1 2.27.1-6ubuntu3.4
  ProcVersionSignature: Microsoft 4.4.0-43-Microsoft 4.4.35
  Uname: Linux 4.4.0-43-Microsoft x86_64
  ApportVersion: 2.14.1-0ubuntu3.23
  Architecture: amd64
  Date: Wed Feb 14 21:05:15 2018
  DuplicateSignature: package:libuuid1:2.27.1-6ubuntu3.4:10.4193:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: 10.4193:subprocess installed post-installation script returned 
error exit status 1
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.3
   apt  1.0.1ubuntu2.17
  SourcePackage: util-linux
  Title: package libuuid1 2.27.1-6ubuntu3.4 failed to install/upgrade: 
10.4193:subprocess installed post-installation script returned error exit 
status 1
  UpgradeStatus: Upgraded to xenial on 2018-02-15 (0 days ago)

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

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

[Touch-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

2018-02-14 Thread Bug Watch Updater

** Changed in: gnome-bluetooth
   Status: Unknown => Confirmed

** Changed in: gnome-bluetooth
   Importance: Unknown => Low

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions

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

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

** Changed in: apport (Ubuntu Bionic)
   Status: Fix Committed => In Progress

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Bionic:
  In Progress

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1595695] Re: Bluetooth indicator disappears every time bluetooth is being turned off

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

** Changed in: gnome-bluetooth (Ubuntu)
   Status: New => Confirmed

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

Title:
  Bluetooth indicator disappears every time bluetooth is being turned
  off

Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed
Status in indicator-bluetooth package in Ubuntu:
  Confirmed

Bug description:
  In Ubuntu 16.04, every time I turn off bluetooth, the indicator icon 
disappears from the top panel.
  Each time I have to re-enable it by system setting or via dash.

  I expect it to behave in a same way as network indicator instead of
  disappearing.

  Here is the link with some info which could be helpful 
  https://bugs.launchpad.net/ubuntu/+source/indicator-bluetooth/+bug/1126108

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

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

[Touch-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

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

** Also affects: gnome-bluetooth via
   https://bugzilla.gnome.org/show_bug.cgi?id=775376
   Importance: Unknown
   Status: Unknown

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

** Changed in: gnome-bluetooth (Ubuntu)
   Status: New => Confirmed

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in GNOME Bluetooth:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-bluetooth package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-bluetooth/+bug/1738838/+subscriptions

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

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

There are some test failures we need to sort out here though.

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1699033] Re: Two-finger right click does not work in gnome-shell

Thanks.

Although to refer to clickpads as a "Mac" feature that's new to Windows
laptops is probably a bit outdated. Most laptops, for many years of
late, fall into this category.

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

Title:
  Two-finger right click does not work in gnome-shell

Status in GSettings Desktop Schemas:
  Fix Released
Status in gsettings-desktop-schemas package in Ubuntu:
  Fix Released

Bug description:
  Using two fingers on the clickpad to right click does not work in
  gnome-shell.

  It seems to be defaulting to the old-style single finger click in the
  bottom right corner to do a right click.

  Workaround:
  gnome-tweak-tool > Keyboard & Mouse > Touchpad > Click Method = Fingers

  Gsettings diff:
  < org.gnome.desktop.peripherals.touchpad click-method 'default'
  ---
  > org.gnome.desktop.peripherals.touchpad click-method 'fingers'

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell 3.24.2-0ubuntu6
  ProcVersionSignature: Ubuntu 4.11.0-7.12-generic 4.11.6
  Uname: Linux 4.11.0-7-generic x86_64
  ApportVersion: 2.20.5-0ubuntu4
  Architecture: amd64
  Date: Tue Jun 20 14:50:10 2017
  DisplayManager: lightdm
  GsettingsChanges: b'org.gnome.desktop.interface' b'gtk-im-module' 
b"'gtk-im-context-simple'"
  InstallationDate: Installed on 2017-06-20 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170613)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gsettings-desktop-schemas/+bug/1699033/+subscriptions

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

[Touch-packages] [Bug 1738838] Re: Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

** Summary changed:

- bluetooth does not turn on; settings interfaces are nonsensical
+ Bluetooth icon shows "Off" and the only option given below it is "Turn Off"

** Changed in: bluez (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: gnome-control-center (Ubuntu)
   Status: Incomplete => Confirmed

** Changed in: gnome-shell (Ubuntu)
   Status: Incomplete => Confirmed

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

Title:
  Bluetooth icon shows "Off" and the only option given below it is "Turn
  Off"

Status in bluez package in Ubuntu:
  Confirmed
Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in gnome-shell package in Ubuntu:
  Confirmed

Bug description:
  See video. I have installed bluetooth, blueman, bluez but it makes no
  difference to a broken interface to control bluetooth under Gnome
  17.10, as shown in the attached video.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: bluetooth 5.46-0ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Dec 17 22:32:30 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2017-11-18 (30 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  InterestingModules: bnep btusb bluetooth
  MachineType: LENOVO 20BXCTO1WW
  PackageArchitecture: all
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-19-generic.efi.signed 
root=UUID=02bd5120-a925-442c-a0dd-1cce59920632 ro quiet splash 
psmouse.synaptics_intertouch=0 vt.handoff=7
  SourcePackage: bluez
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/06/2015
  dmi.bios.vendor: LENOVO
  dmi.bios.version: JBET54WW (1.19 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 20BXCTO1WW
  dmi.board.vendor: LENOVO
  dmi.board.version: SDK0J40697 WIN
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: None
  dmi.modalias: 
dmi:bvnLENOVO:bvrJBET54WW(1.19):bd11/06/2015:svnLENOVO:pn20BXCTO1WW:pvrThinkPadT450s:rvnLENOVO:rn20BXCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:
  dmi.product.family: ThinkPad T450s
  dmi.product.name: 20BXCTO1WW
  dmi.product.version: ThinkPad T450s
  dmi.sys.vendor: LENOVO
  hciconfig:

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

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

[Touch-packages] [Bug 1681513] Re: Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi adapters from working (MAC Address Randomization issue)

2018-02-14 Thread Walttheboss

Just installed 17.10.1 on 64 bit system.

Same issues as described above.  The aformentioned line (wifi.scan . . .
) was already there.  So someone is paying attention.

BUT WiFi will not connect unless you go through the KDE Wallet System.
I tried for hours.  Finally enabled the wallet and it connects just
fine.

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

Title:
  Ubuntu 17.04/17.10: New feature in NetworkManager stops several WiFi
  adapters from working (MAC Address Randomization issue)

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

Bug description:
  According to 
  
https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-networkmanager-1-4-0/
  there is a new privacy feature in the new version of NetworkManager.
  This privacy feature can cause some USB WiFi adapters to stop working
  while they used to work with older versions of NetworkManager (Ubuntu 16.10 
or older).

  The purpose of this privacy feature is to get your computer to report a new 
random MAC address whenever you connect to a WiFi network.
  This privacy feature is especially useful when you connect to public WiFi 
networks, so that the operators cannot identify you when you connect multiple 
times.

  The downside of this privacy feature is that some USB WiFi adapters misbehave 
when NetworkManager tries to change their MAC address repeatedly. 
  The result is that those USB WiFi adapters cannot connect anymore to the WiFi 
 network.

  Original report follows:

  My Panda USB wi-fi adapter works just fine on 16.10, but when I try to
  connect to my wi-fi router in 17.04, GNOME network manager reports
  "Connection failed." I did some tinkering, and noticed that my MAC
  address for my wifi adapter, according to GNOME, is DIFFERENT every
  time I make it forget my wifi settings and try to reconnect. Weird,
  right? Any leads on a possible fix or work-around?

  I'm running the latest beta of Ubuntu GNOME 17.04, kernel
  4.10.0-19-generic, GNOME 3.24.0.

  https://blogs.gnome.org/thaller/2016/08/26/mac-address-spoofing-in-
  networkmanager-1-4-0/

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

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

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

Fix committed to lp:apport at revision 3186.

** Changed in: apport (Ubuntu Bionic)
   Status: In Progress => Fix Committed

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Fix Committed
Status in apport source package in Bionic:
  Fix Committed

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11

Please don't close the totem task. It is there to help other people find
this bug while it's open. That's all.

** Changed in: totem (Ubuntu)
   Status: Invalid => Confirmed

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1746419] Re: bond parameters are not changed by 'netplan apply'

2018-02-14 Thread Daniel Axtens

Right, so netplan should tell networkd to tear down the bond first?

On Thu, Feb 15, 2018 at 7:06 AM, Dimitri John Ledkov
 wrote:
> I believe this is systemd intentional to not change bond parameters if
> the bond already exists. It is assumed that something else has already
> created the bond, and thus networkd should not be "updating" the params.
> Despite networkd creating the bond in the first place...
>
> ** Changed in: systemd (Ubuntu)
>Status: New => Won't Fix
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1746419
>
> Title:
>   bond parameters are not changed by 'netplan apply'
>
> Status in nplan package in Ubuntu:
>   New
> Status in systemd package in Ubuntu:
>   Won't Fix
>
> Bug description:
>   I have a yaml file as follows:
>
>   network:
>   version: 2
>   ethernets:
>   bonddevs:
>   match:
>   name: ens[78]
>   bonds:
>   bond0:
>   interfaces: [bonddevs]
>   parameters:
>   mode: active-backup
>   mii-monitor-interval: 1
>   addresses:
>   - 10.10.10.1/24
>
>
>   Say I decide that 1s is too frequent for the MII interval, and I want to 
> change the interval to 2s.
>
>   If I change that in the yaml, then run
>   # netplan generate
>   # netplan apply
>   # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
>   MII Polling Interval (ms): 1000
>
>   In other words, the change has not been applied.
>
>   Running netplan --debug apply prints:
>   DEBUG:device bond0 operstate is up, not replugging
>
>   So I wondered if bringing the bond down would help. It does not:
>   # ip link set dev bond0 down
>   # netplan apply
>   # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
>   MII Polling Interval (ms): 1000
>
>   However, deleting the link works:
>   # ip link del dev bond0
>   # netplan apply
>   # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
>   MII Polling Interval (ms): 2000
>
>   This is counter-intuitive behaviour.
>   Ideally, I would like a regular netplan apply to work without deleting the 
> bond.
>   However, a changed to the docs to make this clear would be OK.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 17.10
>   Package: nplan 0.32~17.10.1
>   ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13
>   Uname: Linux 4.13.0-32-generic x86_64
>   ApportVersion: 2.20.7-0ubuntu3.7
>   Architecture: amd64
>   Date: Wed Jan 31 05:47:42 2018
>   ProcEnviron:
>TERM=xterm-256color
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=C.UTF-8
>SHELL=/bin/bash
>   SourcePackage: nplan
>   UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/nplan/+bug/1746419/+subscriptions

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

Title:
  bond parameters are not changed by 'netplan apply'

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I have a yaml file as follows:

  network:
  version: 2
  ethernets:
  bonddevs:
  match:
  name: ens[78]
  bonds:
  bond0:
  interfaces: [bonddevs]
  parameters:
  mode: active-backup
  mii-monitor-interval: 1
  addresses:
  - 10.10.10.1/24

  
  Say I decide that 1s is too frequent for the MII interval, and I want to 
change the interval to 2s.

  If I change that in the yaml, then run
  # netplan generate
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 1000

  In other words, the change has not been applied.

  Running netplan --debug apply prints:
  DEBUG:device bond0 operstate is up, not replugging

  So I wondered if bringing the bond down would help. It does not:
  # ip link set dev bond0 down
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 1000

  However, deleting the link works:
  # ip link del dev bond0
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 2000

  This is counter-intuitive behaviour.
  Ideally, I would like a regular netplan apply to work without deleting the 
bond.
  However, a changed to the docs to make this clear would be OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nplan 0.32~17.10.1
  ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Jan 31 05:47:42 2018
  ProcEnviron:

[Touch-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts

2018-02-14 Thread Crashbit

I have a problem with tinc and netplan.

I've using Ubuntu 17.10 server. When I try to start tincd daemon with systemd, 
it doesn't start. 
When start tinc daemon without systemd, it runs correct. 

Fail:
crashbit@sun:~$ sudo systemctl start tinc
crashbit@sun:~$ sudo systemctl status tinc
● tinc.service - Tinc VPN
   Loaded: loaded (/lib/systemd/system/tinc.service; enabled; vendor preset: 
enabled)
   Active: active (exited) since Thu 2018-02-15 00:58:30 CET; 20s ago
  Process: 26868 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 26868 (code=exited, status=0/SUCCESS)
  CPU: 1ms

feb 15 00:58:30 sun systemd[1]: Starting Tinc VPN...
feb 15 00:58:30 sun systemd[1]: Started Tinc VPN.

crashbit@sun:~$ ifconfig | grep cephnet
crashbit@sun:~$ 



Succes:

crashbit@sun:~$ sudo tincd -c /etc/tinc/cephnet/ -n cephnet
Both netname and configuration directory given, using the latter...
crashbit@sun:~$ ifconfig | grep cephnet
cephnet: flags=4305  mtu 1500
crashbit@sun:~$ 

---

crashbit@sun:/etc/netplan$ cat 01-netcfg.yaml 
# This file describes the network interfaces available on your system
# For more information, see netplan(5).
network:
  version: 2
  renderer: networkd
  ethernets:
enp129s0f0:
dhcp4: false

  bridges:
lxdbr0:
interfaces: [enp129s0f0]
addresses: [172.26.0.2/24]
gateway4: 172.26.0.1
parameters:
stp: false
forward-delay: 0
nameservers:
addresses: [172.26.0.5]   
crashbit@sun:/etc/netplan$

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

Title:
  replacement of ifupdown with netplan needs integration for
  /etc/network/if{up,down}.d scripts

Status in aiccu package in Ubuntu:
  Invalid
Status in aoetools package in Ubuntu:
  New
Status in avahi package in Ubuntu:
  New
Status in bind9 package in Ubuntu:
  New
Status in chrony package in Ubuntu:
  Confirmed
Status in clamav package in Ubuntu:
  New
Status in controlaula package in Ubuntu:
  New
Status in epoptes package in Ubuntu:
  New
Status in ethtool package in Ubuntu:
  New
Status in guidedog package in Ubuntu:
  New
Status in htpdate package in Ubuntu:
  New
Status in ifenslave package in Ubuntu:
  New
Status in ifmetric package in Ubuntu:
  New
Status in ifupdown-multi package in Ubuntu:
  New
Status in ifupdown-scripts-zg2 package in Ubuntu:
  New
Status in isatapd package in Ubuntu:
  New
Status in lprng package in Ubuntu:
  New
Status in miredo package in Ubuntu:
  New
Status in mythtv package in Ubuntu:
  New
Status in nplan package in Ubuntu:
  New
Status in nss-pam-ldapd package in Ubuntu:
  New
Status in ntp package in Ubuntu:
  New
Status in openntpd package in Ubuntu:
  New
Status in openresolv package in Ubuntu:
  New
Status in openssh package in Ubuntu:
  New
Status in openvpn package in Ubuntu:
  New
Status in postfix package in Ubuntu:
  New
Status in quicktun package in Ubuntu:
  New
Status in resolvconf package in Ubuntu:
  New
Status in sendmail package in Ubuntu:
  New
Status in shorewall-init package in Ubuntu:
  New
Status in sidedoor package in Ubuntu:
  New
Status in slrn package in Ubuntu:
  New
Status in tinc package in Ubuntu:
  New
Status in ubuntu-fan package in Ubuntu:
  Fix Committed
Status in ucarp package in Ubuntu:
  New
Status in uml-utilities package in Ubuntu:
  New
Status in uruk package in Ubuntu:
  New
Status in vlan package in Ubuntu:
  New
Status in vzctl package in Ubuntu:
  New
Status in wide-dhcpv6 package in Ubuntu:
  New
Status in wpa package in Ubuntu:
  New

Bug description:
  when network is configured with ifupdown, scripts in
  /etc/network/ifup.d/ were called on network being brought up and
  /etc/network/ifdown.d were called on network being brought down.

  Any packages that shipped these hooks need to be verified to have the
  same functionality under a netplan configured system.

  # binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
  # for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u

  aiccu
  aoetools
  avahi
  bind9
  chrony
  clamav
  controlaula
  epoptes
  ethtool
  guidedog
  htpdate
  ifenslave
  ifmetric
  ifupdown-extra
  ifupdown-multi
  ifupdown-scripts-zg2
  isatapd
  lprng
  miredo
  mythtv-backend
  nss-pam-ldapd
  ntp
  openntpd
  openresolv
  openssh
  openvpn
  postfix
  quicktun
  resolvconf
  sendmail
  shorewall-init
  sidedoor
  slrn
  tinc
  ubuntu-fan
  ucarp
  uml-utilities
  uruk
  vlan
  vzctl
  wide-dhcpv6
  wpa

  
  Related bugs:
   * bug 1718227: replacement of ifupdown with netplan needs integration for 
/etc/network/if{up,down}.d scripts 
   * bug

[Touch-packages] [Bug 1724224] Re: ubiquity crashed with FileNotFoundError in _execute_child(): [Errno 2] No such file or directory: 'sensible-browser': 'sensible-browser'

** Changed in: ubuntu-release-upgrader (Ubuntu)
   Status: Triaged => In Progress

** Changed in: ubuntu-release-upgrader (Ubuntu)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  ubiquity crashed with FileNotFoundError in _execute_child(): [Errno 2]
  No such file or directory: 'sensible-browser': 'sensible-browser'

Status in ubiquity package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-release-upgrader package in Ubuntu:
  In Progress

Bug description:
  Test Case
  1. Boot to the live session
  2. Start the installer
  3. Click on the release notes link.

  Expected result
  A webbrowser opens with the release notes

  Actual result
  This crash

  ProblemType: Crash
  DistroRelease: Ubuntu 17.10
  Package: ubiquity 17.10.10
  ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4
  Uname: Linux 4.13.0-16-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3
  Architecture: amd64
  CasperVersion: 1.387
  Date: Tue Oct 17 11:36:00 2017
  ExecutablePath: /usr/lib/ubiquity/bin/ubiquity
  ExecutableTimestamp: 1507903384
  InterpreterPath: /usr/bin/python3.6
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017)
  ProcCmdline: /usr/bin/python3 /usr/lib/ubiquity/bin/ubiquity gtk_ui
  ProcCwd: /home/ubuntu
  ProcEnviron:
   TERM=unknown
   PATH=(custom, no user)
   LANG=C.UTF-8
   SHELL=/bin/bash
  Python3Details: /usr/bin/python3.6, Python 3.6.3, python3-minimal, 
3.6.3-0ubuntu2
  PythonArgs: ['/usr/lib/ubiquity/bin/ubiquity', 'gtk_ui']
  PythonDetails: /usr/bin/python2.7, Python 2.7.14, python-minimal, 
2.7.14-2ubuntu1
  SourcePackage: ubiquity
  Title: ubiquity crashed with FileNotFoundError in _execute_child(): [Errno 2] 
No such file or directory: 'sensible-browser': 'sensible-browser'
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

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

-- 
Mailing list: https://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 1749086] Re: (X)Ubuntu 16.04.3 LTS: sleep on boot

Thank you for your detailed response. Will do my best tomorrow.

On 14 Feb 2018 20:21, "Christopher M. Penalver" <
christopher.m.penal...@gmail.com> wrote:

> Steve Bainton:
>
> 1) To advise, you don't have to apport-collect further unless
> specifically requested to do so.
>
> 2) Regarding your BIOS, it is not the latest as per your motherboard
> vendor:
> http://www.asrock.com/mb/AMD/770%20Extreme3/#BIOS
>
> 3) Did this issue start to happen after an update? If so, which?
>
> 4) As per your log
> https://launchpadlibrarian.net/357032471/CurrentDmesg.txt the computer
> is suffering from kernel crashes that are correlated to the boot delay.
>
> Hence, in order to allow additional upstream mainline kernel developers to
> examine the issue, at your earliest convenience, could you please test the
> latest mainline kernel available from http://kernel.ubuntu.com/~
> kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
> 1) The one to test is at the very top line at the top of the page (not the
> daily folder).
> 2) The release names are irrelevant.
> 3) The folder time stamps aren't indicative of when the kernel actually
> was released upstream.
> 4) Install instructions are available at https://wiki.ubuntu.com/
> Kernel/MainlineBuilds .
>
> If testing on your main install would be inconvenient, one may:
> 1) Install Ubuntu to a different partition and then test this there.
> 2) Backup, or clone the primary install.
>
> If the latest kernel did not allow you to test to the issue (ex. you
> couldn't boot into the OS) please make a comment in your report about this,
> and continue to test the next most recent kernel version until you can test
> to the issue. Once you've tested the mainline kernel, please comment on
> which kernel version specifically you tested. If this issue is not
> reproducible in the mainline kernel, please add the following tags by
> clicking on the yellow circle with a black pencil icon, next to the word
> Tags, located at the bottom of the report description:
> kernel-fixed-upstream
> kernel-fixed-upstream-X.Y-rcZ
>
> Where X, and Y are the first two numbers of the kernel version, and Z is
> the release candidate number if it exists.
>
> If the issue is reproducible with the mainline kernel, please add the
> following tags:
> kernel-bug-exists-upstream
> kernel-bug-exists-upstream-X.Y-rcZ
>
> Please note, an error to install the kernel does not fit the criteria of
> kernel-bug-exists-upstream.
>
> Also, you don't need to apport-collect further unless specifically
> requested to do so.
>
> It is most helpful that after testing of the latest mainline kernel is
> complete, you mark this report Status Confirmed.
>
> Lastly, to keep this issue relevant to upstream, please continue to test
> the latest mainline kernel as it becomes available.
>
> Thank you for your help.
>
> ** Description changed:
>
> - Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
> - probably the same), the screen turns off a few seconds after choosing
> - ubuntu in grub2 menu, after about 5 minutes it comes back to life and
> - login screen is presented and from that point on everything seems to
> - work as normal. (Might have sth to do with Radeon drivers?) Please tell
> - me what other info you need.
> + Newly installed Xubuntu or Kubuntu the screen turns off a few seconds
> + after choosing Ubuntu in grub2 menu, and after about 5 minutes the login
> + screen is presented and from that point on everything seems to work as
> + normal.
>
> - ProblemType: Bug
> - DistroRelease: Ubuntu 16.04
> - Package: xorg 1:7.7+13ubuntu3
> - ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
> - Uname: Linux 4.13.0-32-generic x86_64
> - ApportVersion: 2.20.1-0ubuntu2.15
> - Architecture: amd64
> - CurrentDesktop: XFCE
> - Date: Tue Feb 13 07:37:53 2018
> - InstallationDate: Installed on 2018-02-11 (1 days ago)
> - InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
> (20170801)
> - ProcEnviron:
> -  LANGUAGE=en_GB:en
> -  PATH=(custom, no user)
> -  XDG_RUNTIME_DIR=
> -  LANG=en_GB.UTF-8
> -  SHELL=/bin/bash
> - SourcePackage: xorg
> - Symptom: display
> - UpgradeStatus: No upgrade log present (probably fresh install)
> - ---
>   ApportVersion: 2.20.1-0ubuntu2.15
>   Architecture: amd64
>   CompizPlugins: No value set for `/apps/compiz-1/general/
> screen0/options/active_plugins'
>   CompositorRunning: None
>   CurrentDesktop: XFCE
>   DistUpgraded: Fresh install
>   DistroCodename: xenial
>   DistroRelease: Ubuntu 16.04
>   DistroVariant: ubuntu
>   ExtraDebuggingInterest: Yes, including running git bisection searches
>   GraphicsCard:
> -  Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770]
> [1002:68b8] (prog-if 00 [VGA controller])
> -Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770]
> [1043:03b6]
> - InstallationDate: Installed on 2018-02-11 (2 days ago)
> - InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64
>

[Touch-packages] [Bug 1749597] Re: [aarch64] gas: Error: non-constant expression in ".if" statement

2018-02-14 Thread Bug Watch Updater

** Changed in: binutils
   Status: Unknown => Fix Released

** Changed in: binutils
   Importance: Unknown => Medium

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

Title:
  [aarch64] gas: Error: non-constant expression in ".if" statement

Status in binutils:
  Fix Released
Status in binutils package in Ubuntu:
  New

Bug description:
  gas in binutils 2.26 contains a bug that prevents compilation of ARM
  Trusted Firmware in particular, or any code that references the "."
  symbol following a .align statement that specifies explicit padding
  data.

  ATF bug report: https://github.com/ARM-software/tf-issues/issues/401
  binutils bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=20364

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

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

[Touch-packages] [Bug 1727237] Re: systemd-resolved is not finding a domain

I can't seem to find where you sent me logs?

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

Title:
  systemd-resolved is not finding a domain

Status in systemd package in Ubuntu:
  Triaged
Status in systemd source package in Xenial:
  Triaged
Status in systemd source package in Zesty:
  Won't Fix
Status in systemd source package in Artful:
  Triaged
Status in systemd source package in Bionic:
  Triaged

Bug description:
  I have an odd network situation that I have so far managed to narrow
  down to the inability to resolve a domain via systemd-resolved which
  is resolvable with nslookup. If I use nslookup against the two
  nameservers on this network I get answers for the domain, but ping
  says it is unable to resolve the same domain (as do browsers and
  crucially the captive portal mechanism).

  Here are details:

  NSLOOKUP:

  ~$ nslookup securelogin.arubanetworks.com 208.67.220.220
  Server:   208.67.220.220
  Address:  208.67.220.220#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  ~$ nslookup securelogin.arubanetworks.com 208.67.222.222
  Server:   208.67.222.222
  Address:  208.67.222.222#53

  Non-authoritative answer:
  Name: securelogin.arubanetworks.com
  Address: 172.22.240.242

  
  PING:

  ~$ ping securelogin.arubanetworks.com
  ping: securelogin.arubanetworks.com: Name or service not known
  mark@mark-X1Y2:~$ 

  
  DIG:

  ~$ dig @208.67.222.222 securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> @208.67.222.222 securelogin.arubanetworks.com
  ; (1 server found)
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 9416
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 4096
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; AUTHORITY SECTION:
  arubanetworks.com.1991IN  SOA dns5.arubanetworks.com. 
hostmaster.arubanetworks.com. 1323935888 3600 200 1209600 86400

  ;; Query time: 34 msec
  ;; SERVER: 208.67.222.222#53(208.67.222.222)
  ;; WHEN: Wed Oct 25 10:31:10 CEST 2017
  ;; MSG SIZE  rcvd: 144

  
  MORE DIG:

  ~$ dig securelogin.arubanetworks.com

  ; <<>> DiG 9.10.3-P4-Ubuntu <<>> securelogin.arubanetworks.com
  ;; global options: +cmd
  ;; Got answer:
  ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 3924
  ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

  ;; OPT PSEUDOSECTION:
  ; EDNS: version: 0, flags:; udp: 65494
  ;; QUESTION SECTION:
  ;securelogin.arubanetworks.com.   IN  A

  ;; Query time: 0 msec
  ;; SERVER: 127.0.0.53#53(127.0.0.53)
  ;; WHEN: Wed Oct 25 10:34:01 CEST 2017
  ;; MSG SIZE  rcvd: 58

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

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

[Touch-packages] [Bug 1749597] [NEW] [aarch64] gas: Error: non-constant expression in ".if" statement

2018-02-14 Thread Stephen Warren

Public bug reported:

gas in binutils 2.26 contains a bug that prevents compilation of ARM
Trusted Firmware in particular, or any code that references the "."
symbol following a .align statement that specifies explicit padding
data.

ATF bug report: https://github.com/ARM-software/tf-issues/issues/401
binutils bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=20364

** Affects: binutils
 Importance: Unknown
 Status: Unknown

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

** Bug watch added: Sourceware.org Bugzilla #20364
   https://sourceware.org/bugzilla/show_bug.cgi?id=20364

** Also affects: binutils via
   https://sourceware.org/bugzilla/show_bug.cgi?id=20364
   Importance: Unknown
   Status: Unknown

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

Title:
  [aarch64] gas: Error: non-constant expression in ".if" statement

Status in binutils:
  Unknown
Status in binutils package in Ubuntu:
  New

Bug description:
  gas in binutils 2.26 contains a bug that prevents compilation of ARM
  Trusted Firmware in particular, or any code that references the "."
  symbol following a .align statement that specifies explicit padding
  data.

  ATF bug report: https://github.com/ARM-software/tf-issues/issues/401
  binutils bug report: https://sourceware.org/bugzilla/show_bug.cgi?id=20364

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-14 Thread Gunnar Hjalmarsson

The good news is that is doesn't matter much as long as upstream hasn't
dropped the translations from the .policy files and added gettext-
domain="systemd" ...

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

Title:
  systemd translations are not synced with upstream

Status in systemd:
  New
Status in Ubuntu Translations:
  New
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 1749595] [NEW] No window, wrong size

2018-02-14 Thread swatkins

Public bug reported:

Since Ubuntu 17, I have had the following bug, I assumed it would be
fixed without my input but has not.

When opening some package, sometimes the icon appears on the left, but
no window will appear.  This occurs most often with any pdf software,
but also Libre, but also shot-well, cheese or mainly graphics programs.
The problem goes away if the software is closed and restarted, but
sometimes this requires several attempts.  This also occurs sometimes
(the most annoying) if the software is iconized and then re-enlarged.
Also, the default window size, only for graphics software and pdf, opens
windows that occupy 2 or three work spaces.  If the internal defaults
are corrected, the same window size opens regardless.  This makes it
difficult to size a window every time it is opened.  As this occurs
across several programs, I do not know how to collect the proper bug
information.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: xorg 1:7.7+19ubuntu3
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 14 22:28:01 2018
DistUpgraded: 2017-11-18 00:35:25,829 DEBUG icon theme changed, re-reading
DistroCodename: artful
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.1.30, 4.13.0-21-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-25-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-31-generic, x86_64: installed
 virtualbox, 5.1.30, 4.13.0-32-generic, x86_64: installed
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics 
Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASUSTeK Computer Inc. 2nd Generation Core Processor Family 
Integrated Graphics Controller [1043:1652]
 NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 [VGA 
controller])
   Subsystem: ASUSTeK Computer Inc. GeForce GT 610M [1043:1652]
InstallationDate: Installed on 2015-10-31 (837 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
MachineType: ASUSTeK Computer Inc. K53SD
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=56e03b17-341b-4643-8ec1-7b9bd282d821 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
UpgradeStatus: Upgraded to artful on 2017-11-17 (88 days ago)
dmi.bios.date: 01/17/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K53SD.204
dmi.board.asset.tag: ATN12345678901234567
dmi.board.name: K53SD
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.version: 1.0
dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrK53SD.204:bd01/17/2012:svnASUSTeKComputerInc.:pnK53SD:pvr1.0:rvnASUSTeKComputerInc.:rnK53SD:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0:
dmi.product.family: K
dmi.product.name: K53SD
dmi.product.version: 1.0
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.13.1+17.10.20170901-0ubuntu1
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 1:2.10.5-1ubuntu1
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
xserver.bootTime: Thu Nov 16 20:37:16 2017
xserver.configfile: default
xserver.errors:
 Failed to load module "nvidia" (module does not exist, 0)
 Failed to load module "nvidia" (module does not exist, 0)
 NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.19.3-1ubuntu1.3
xserver.video_driver: modeset

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


** Tags: amd64 apport-bug artful ubuntu

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

Title:
  No window, wrong size

Status in xorg package in Ubuntu:
  New

Bug description:
  Since Ubuntu 17, I have had the following bug, I assumed it would be
  fixed without my input but has not.

  When opening some package, sometimes the icon appears on the left, but
  no window will appear.  This occurs most often with any pdf software,
  but also Libre, but also shot-well, cheese or mainly graphics
  programs.  The problem goes away if the software is closed and
  restarted, but sometimes this requires several attempts.  This also
  occurs sometimes (the

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-14 Thread Gunnar Hjalmarsson

@Martin: That's disappointing. At least it was imported, as a result of
the name change. :\

I just built 237-2ubuntu1 locally. No such warnings, and:

$ ls -l build-deb/po/systemd.pot
-rw-r--r-- 1 gunnar gunnar 16268 feb 14 22:07 build-deb/po/systemd.pot

i.e. systemd.pot includes the messages from the .policy files (the size
of the one which LP imported is 1700 bytes).

Why does it work for me? Can it be that I have something installed which
ought to be a builddep? The attached file shows some of my installed
gettext related packages. Does it possibly ring a bell?

** Attachment added: "gettext-packages-gunnar.txt"

https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1707898/+attachment/5055484/+files/gettext-packages-gunnar.txt

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

Title:
systemd translations are not synced with upstream

Status in systemd:
New
Status in Ubuntu Translations:
New
Status in systemd package in Ubuntu:
In Progress

Bug description:
Translations for systemd are outdated because they do not seem to be
synced with the upstream ones.

For example the Czech one:
Launchpad:
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
- 0% translated
Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100%
translated

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

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

[Touch-packages] [Bug 1749432] Re: cryptsetup open hangs waiting for udev cookied

** Tags removed: block-proposed

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

Title:
  cryptsetup open hangs waiting for udev cookied

Status in cryptsetup package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  systemd has a testcase to setup, open and close a luks1 volume.

  this test case has started to fail with udev 237 & cryptsetup2

  this appears to be reproducible with straight up "cryptsetup open"
  call which seems to hang in device mapper library, e.g.:

  # cryptsetup open --type luks UUID=fd41c9ba-4286-415d-95e4-960fd28b5e>
  # cryptsetup 2.0.1 processing "cryptsetup open --type luks 
UUID=fd41c9ba-4286-415d-95e4-960fd28b5e43 varcrypt --key-file /etc/varkey 
--debug --verbose"
  # Running command open.
  # Locking memory.
  # Installing SIGINT/SIGTERM handler.
  # Unblocking interruption on signal.
  # Allocating context for crypt device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
  # Trying to open and read device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43 with direct-io.
  # Initialising device-mapper backend library.
  # Trying to load any crypt type from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
  # Crypto backend (gcrypt 1.8.1) initialized in cryptsetup library version 
2.0.1.
  # Detected kernel Linux 4.13.0-32-generic x86_64.
  # PBKDF pbkdf2, hash sha256, time_ms 2000 (iterations 0), max_memory_kb 0, 
parallel_threads 0.
  # Reading LUKS header of size 1024 from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43
  # Key length 32, device size 18432 sectors, header size 2050 sectors.
  # Activating volume varcrypt using token -1.
  # File descriptor passphrase entry requested.
  # Activating volume varcrypt [keyslot -1] using passphrase.
  # dm version   [ opencount flush ]   [16384] (*1)
  # dm versions   [ opencount flush ]   [16384] (*1)
  # Detected dm-ioctl version 4.37.0.
  # Detected dm-crypt version 1.18.0.
  # Device-mapper backend running with UDEV support enabled.
  # dm status varcrypt  [ opencount flush ]   [16384] (*1)
  # Trying to open key slot 0 [ACTIVE_LAST].
  # Reading key slot 0 area.
  # Using userspace crypto wrapper to access keyslot area.
  Key slot 0 unlocked.
  # Calculated device size is 14336 sectors (RW), offset 4096.
  # DM-UUID is CRYPT-LUKS1-fd41c9ba4286415d95e4960fd28b5e43-varcrypt
  # Udev cookie 0xd4d4a7f (semid 65538) created
  # Udev cookie 0xd4d4a7f (semid 65538) incremented to 1
  # Udev cookie 0xd4d4a7f (semid 65538) incremented to 2
  # Udev cookie 0xd4d4a7f (semid 65538) assigned to CREATE task(0) with flags 
DISABLE_LIBRARY_FALLBACK (0x20)
  # dm create varcrypt CRYPT-LUKS1-fd41c9ba4286415d95e4960fd28b5e43-varcrypt [ 
opencount flush ]   [16384] (*1)
  # dm reload varcrypt  [ opencount flush securedata ]   [16384] (*1)
  # dm resume varcrypt  [ opencount flush securedata ]   [16384] (*1)
  # varcrypt: Stacking NODE_ADD (253,0) 0:6 0660 [trust_udev]
  # varcrypt: Stacking NODE_READ_AHEAD 256 (flags=1)
  # Udev cookie 0xd4d4a7f (semid 65538) decremented to 1
  # Udev cookie 0xd4d4a7f (semid 65538) waiting for zero

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

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

[Touch-packages] [Bug 1748692] Re: warning symbol overlaps Ubuntu logo

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

** Changed in: apport (Ubuntu)
   Importance: Undecided => Low

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

Title:
  warning symbol overlaps Ubuntu logo

Status in apport package in Ubuntu:
  Confirmed

Bug description:
  I noticed this while reporting another bug.  The ⛔ warning symbol
  covers most of the Ubuntu logo.  See attached screenshot.

  Description:  Ubuntu Bionic Beaver (development branch)
  Release:  18.04

  Linux 4.13.0-32-generic x86_64

  apport-gtk: 2.20.8-0ubuntu8

  1920x1080 display

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport-gtk 2.20.8-0ubuntu8
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 11 12:51:06 2018
  InstallationDate: Installed on 2018-02-05 (5 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  PackageArchitecture: all
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749432] Re: cryptsetup open hangs waiting for udev cookied

Thank you!

This does appear to be the problem, that 95-dm-notify.rules are now
shipped in the package, but were not copied in the test harness.

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

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

** Changed in: systemd (Ubuntu)
   Status: New => In Progress

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

Title:
  cryptsetup open hangs waiting for udev cookied

Status in cryptsetup package in Ubuntu:
  Invalid
Status in lvm2 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  systemd has a testcase to setup, open and close a luks1 volume.

  this test case has started to fail with udev 237 & cryptsetup2

  this appears to be reproducible with straight up "cryptsetup open"
  call which seems to hang in device mapper library, e.g.:

  # cryptsetup open --type luks UUID=fd41c9ba-4286-415d-95e4-960fd28b5e>
  # cryptsetup 2.0.1 processing "cryptsetup open --type luks 
UUID=fd41c9ba-4286-415d-95e4-960fd28b5e43 varcrypt --key-file /etc/varkey 
--debug --verbose"
  # Running command open.
  # Locking memory.
  # Installing SIGINT/SIGTERM handler.
  # Unblocking interruption on signal.
  # Allocating context for crypt device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
  # Trying to open and read device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43 with direct-io.
  # Initialising device-mapper backend library.
  # Trying to load any crypt type from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43.
  # Crypto backend (gcrypt 1.8.1) initialized in cryptsetup library version 
2.0.1.
  # Detected kernel Linux 4.13.0-32-generic x86_64.
  # PBKDF pbkdf2, hash sha256, time_ms 2000 (iterations 0), max_memory_kb 0, 
parallel_threads 0.
  # Reading LUKS header of size 1024 from device 
/dev/disk/by-uuid/fd41c9ba-4286-415d-95e4-960fd28b5e43
  # Key length 32, device size 18432 sectors, header size 2050 sectors.
  # Activating volume varcrypt using token -1.
  # File descriptor passphrase entry requested.
  # Activating volume varcrypt [keyslot -1] using passphrase.
  # dm version   [ opencount flush ]   [16384] (*1)
  # dm versions   [ opencount flush ]   [16384] (*1)
  # Detected dm-ioctl version 4.37.0.
  # Detected dm-crypt version 1.18.0.
  # Device-mapper backend running with UDEV support enabled.
  # dm status varcrypt  [ opencount flush ]   [16384] (*1)
  # Trying to open key slot 0 [ACTIVE_LAST].
  # Reading key slot 0 area.
  # Using userspace crypto wrapper to access keyslot area.
  Key slot 0 unlocked.
  # Calculated device size is 14336 sectors (RW), offset 4096.
  # DM-UUID is CRYPT-LUKS1-fd41c9ba4286415d95e4960fd28b5e43-varcrypt
  # Udev cookie 0xd4d4a7f (semid 65538) created
  # Udev cookie 0xd4d4a7f (semid 65538) incremented to 1
  # Udev cookie 0xd4d4a7f (semid 65538) incremented to 2
  # Udev cookie 0xd4d4a7f (semid 65538) assigned to CREATE task(0) with flags 
DISABLE_LIBRARY_FALLBACK (0x20)
  # dm create varcrypt CRYPT-LUKS1-fd41c9ba4286415d95e4960fd28b5e43-varcrypt [ 
opencount flush ]   [16384] (*1)
  # dm reload varcrypt  [ opencount flush securedata ]   [16384] (*1)
  # dm resume varcrypt  [ opencount flush securedata ]   [16384] (*1)
  # varcrypt: Stacking NODE_ADD (253,0) 0:6 0660 [trust_udev]
  # varcrypt: Stacking NODE_READ_AHEAD 256 (flags=1)
  # Udev cookie 0xd4d4a7f (semid 65538) decremented to 1
  # Udev cookie 0xd4d4a7f (semid 65538) waiting for zero

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

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

[Touch-packages] [Bug 1707898] Re: systemd translations are not synced with upstream

2018-02-14 Thread Martin Pitt

@Gunnar: This patch does not actually work:

❱❱❱ xgettext -f "po/POTFILES.in" -o "build-deb/po/systemd.pot" --join-existing
xgettext: warning: file 'src/core/org.freedesktop.systemd1.policy.in.in' 
extension 'policy' is unknown; will try C
xgettext: warning: file 'src/hostname/org.freedesktop.hostname1.policy.in' 
extension 'policy' is unknown; will try C
xgettext: warning: file 'src/import/org.freedesktop.import1.policy.in' 
extension 'policy' is unknown; will try C
xgettext: warning: file 'src/locale/org.freedesktop.locale1.policy.in' 
extension 'policy' is unknown; will try C
xgettext: warning: file 'src/login/org.freedesktop.login1.policy.in' extension 
'policy' is unknown; will try C
xgettext: warning: file 'src/machine/org.freedesktop.machine1.policy.in' 
extension 'policy' is unknown; will try C
xgettext: warning: file 'src/timedate/org.freedesktop.timedate1.policy.in' 
extension 'policy' is unknown; will try C

And systemd.pot is unchanged.

I now committed https://salsa.debian.org/systemd-
team/systemd/commit/09c6423728319 to simplify the .pot generation, but
it has the exact same issue.

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

Title:
  systemd translations are not synced with upstream

Status in systemd:
  New
Status in Ubuntu Translations:
  New
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  Translations for systemd are outdated because they do not seem to be
  synced with the upstream ones.

  For example the Czech one:
  Launchpad: 
https://translations.launchpad.net/ubuntu/artful/+source/systemd/+pots/systemd/cs/+translate
 - 0% translated
  Upstream: https://github.com/systemd/systemd/blob/master/po/cs.po - 100% 
translated

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

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

[Touch-packages] [Bug 1746419] Re: bond parameters are not changed by 'netplan apply'

I believe this is systemd intentional to not change bond parameters if
the bond already exists. It is assumed that something else has already
created the bond, and thus networkd should not be "updating" the params.
Despite networkd creating the bond in the first place...

** Changed in: systemd (Ubuntu)
   Status: New => Won't Fix

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

Title:
  bond parameters are not changed by 'netplan apply'

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  Won't Fix

Bug description:
  I have a yaml file as follows:

  network:
  version: 2
  ethernets:
  bonddevs:
  match:
  name: ens[78]
  bonds:
  bond0:
  interfaces: [bonddevs]
  parameters:
  mode: active-backup
  mii-monitor-interval: 1
  addresses:
  - 10.10.10.1/24

  
  Say I decide that 1s is too frequent for the MII interval, and I want to 
change the interval to 2s.

  If I change that in the yaml, then run
  # netplan generate
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 1000

  In other words, the change has not been applied.

  Running netplan --debug apply prints:
  DEBUG:device bond0 operstate is up, not replugging

  So I wondered if bringing the bond down would help. It does not:
  # ip link set dev bond0 down
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 1000

  However, deleting the link works:
  # ip link del dev bond0
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 2000

  This is counter-intuitive behaviour.
  Ideally, I would like a regular netplan apply to work without deleting the 
bond.
  However, a changed to the docs to make this clear would be OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nplan 0.32~17.10.1
  ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Jan 31 05:47:42 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: nplan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749579] Re: systemd-journald crashed with SIGABRT in __pthread_join()

2018-02-14 Thread Apport retracing service

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

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 #1747829, 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/1749579/+attachment/5055389/+files/CoreDump.gz

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

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

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

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

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

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

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

** Information type changed from Private to Public

** Tags removed: need-i386-retrace

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

Title:
  systemd-journald crashed with SIGABRT in __pthread_join()

Status in systemd package in Ubuntu:
  New

Bug description:
  error

  ProblemType: Crash
  DistroRelease: Ubuntu 18.04
  Package: systemd 237-1ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-10.11-lowlatency 4.15.3
  Uname: Linux 4.15.0-10-lowlatency i686
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: i386
  Date: Thu Feb 15 02:30:53 2018
  ExecutablePath: /lib/systemd/systemd-journald
  InstallationDate: Installed on 2018-02-07 (7 days ago)
  InstallationMedia: Lubuntu 17.10 "Artful Aardvark" - Release i386 (20180105)
  MachineType: LENOVO 170644A
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcCmdline: /lib/systemd/systemd-journald
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-10-lowlatency 
root=UUID=ad4d620f-f517-4d3f-be86-85911df83ff8 ro recovery nomodeset
  Signal: 6
  SourcePackage: systemd
  StacktraceTop:
   __pthread_join (threadid=2873850688, thread_return=0x0) at pthread_join.c:90
   ?? () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
   journal_file_append_object () from /lib/systemd/libsystemd-shared-237.so
   ?? () from /lib/systemd/libsystemd-shared-237.so
  Title: systemd-journald crashed with SIGABRT in __pthread_join()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:
   
  dmi.bios.date: 03/31/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 7BETD8WW (2.19 )
  dmi.board.name: 170644A
  dmi.board.vendor: LENOVO
  dmi.board.version: Not Available
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvr7BETD8WW(2.19):bd03/31/2011:svnLENOVO:pn170644A:pvrThinkPadX60:rvnLENOVO:rn170644A:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.family: ThinkPad X60
  dmi.product.name: 170644A
  dmi.product.version: ThinkPad X60
  dmi.sys.vendor: LENOVO
  mtime.conffile..etc.systemd.resolved.conf: 2018-02-13T12:05:23.566776
  mtime.conffile..etc.systemd.system.conf: 2018-02-14T22:21:32.539671

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

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

[Touch-packages] [Bug 1749086] Re: (X)Ubuntu 16.04.3 LTS: sleep on boot

Steve Bainton:

1) To advise, you don't have to apport-collect further unless
specifically requested to do so.

2) Regarding your BIOS, it is not the latest as per your motherboard vendor:
http://www.asrock.com/mb/AMD/770%20Extreme3/#BIOS

3) Did this issue start to happen after an update? If so, which?

4) As per your log
https://launchpadlibrarian.net/357032471/CurrentDmesg.txt the computer
is suffering from kernel crashes that are correlated to the boot delay.

Hence, in order to allow additional upstream mainline kernel developers to 
examine the issue, at your earliest convenience, could you please test the 
latest mainline kernel available from 
http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind 
the following:
1) The one to test is at the very top line at the top of the page (not the 
daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was 
released upstream.
4) Install instructions are available at 
https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel did not allow you to test to the issue (ex. you couldn't 
boot into the OS) please make a comment in your report about this, and continue 
to test the next most recent kernel version until you can test to the issue. 
Once you've tested the mainline kernel, please comment on which kernel version 
specifically you tested. If this issue is not reproducible in the mainline 
kernel, please add the following tags by clicking on the yellow circle with a 
black pencil icon, next to the word Tags, located at the bottom of the report 
description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is
the release candidate number if it exists.

If the issue is reproducible with the mainline kernel, please add the following 
tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of
kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically
requested to do so.

It is most helpful that after testing of the latest mainline kernel is
complete, you mark this report Status Confirmed.

Lastly, to keep this issue relevant to upstream, please continue to test
the latest mainline kernel as it becomes available.

Thank you for your help.

** Description changed:

- Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
- probably the same), the screen turns off a few seconds after choosing
- ubuntu in grub2 menu, after about 5 minutes it comes back to life and
- login screen is presented and from that point on everything seems to
- work as normal. (Might have sth to do with Radeon drivers?) Please tell
- me what other info you need.
+ Newly installed Xubuntu or Kubuntu the screen turns off a few seconds
+ after choosing Ubuntu in grub2 menu, and after about 5 minutes the login
+ screen is presented and from that point on everything seems to work as
+ normal.
  
- ProblemType: Bug
- DistroRelease: Ubuntu 16.04
- Package: xorg 1:7.7+13ubuntu3
- ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
- Uname: Linux 4.13.0-32-generic x86_64
- ApportVersion: 2.20.1-0ubuntu2.15
- Architecture: amd64
- CurrentDesktop: XFCE
- Date: Tue Feb 13 07:37:53 2018
- InstallationDate: Installed on 2018-02-11 (1 days ago)
- InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
- ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
- SourcePackage: xorg
- Symptom: display
- UpgradeStatus: No upgrade log present (probably fresh install)
- --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
-Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
- InstallationDate: Installed on 2018-02-11 (2 days ago)
- InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
- MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
- Package: xorg 1:7.7+13ubuntu3
- PackageArchitecture: amd64
- ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
- ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
- Tags:  xenial

Re: [Touch-packages] [Bug 1749247] Re: Spurious SEGV running inside kvm

2018-02-14 Thread Quanah

It can also die with the following backtrace:
(gdb) bt
#0  __memmove_ssse3 () at ../sysdeps/x86_64/multiarch/memcpy-ssse3.S:2331
#1  0x7f570da4a14e in ber_dupbv_x (dst=0x25f55e8, src=0x7f2ee8001200,
ctx=0x0) at
/home/build/git/sold-2445/openldap/libraries/liblber/memory.c:512
#2  0x7f570da4a19f in ber_dupbv (dst=0x25f55e8, src=0x7f2ee8001200) at
/home/build/git/sold-2445/openldap/libraries/liblber/memory.c:523
#3  0x7f57091a07b4 in accesslog_op_mod (op=0x7f2f0518e780,
rs=0x7f2f0518e030) at
/home/build/git/sold-2445/openldap/servers/slapd/overlays/accesslog.c:2031
#4  0x004d9be5 in overlay_op_walk (op=0x7f2f0518e780,
rs=0x7f2f0518e030, which=op_modify, oi=0x25eb720, on=0x25f53c0)
at /home/build/git/sold-2445/openldap/servers/slapd/backover.c:661
#5  0x004d9ee1 in over_op_func (op=0x7f2f0518e780,
rs=0x7f2f0518e030, which=op_modify) at
/home/build/git/sold-2445/openldap/servers/slapd/backover.c:730
#6  0x004da044 in over_op_modify (op=0x7f2f0518e780,
rs=0x7f2f0518e030) at
/home/build/git/sold-2445/openldap/servers/slapd/backover.c:769
#7  0x004cc061 in syncrepl_updateCookie (si=0x26499f0,
op=0x7f2f0518e780, syncCookie=0x7f2f0518e290) at
/home/build/git/sold-2445/openldap/servers/slapd/syncrepl.c:3982
#8  0x004c0bd5 in do_syncrep2 (op=0x7f2f0518e780, si=0x26499f0) at
/home/build/git/sold-2445/openldap/servers/slapd/syncrepl.c:1019
#9  0x004c2ea6 in do_syncrepl (ctx=0x7f2f0518ec30, arg=0x25ebb40)
at /home/build/git/sold-2445/openldap/servers/slapd/syncrepl.c:1567
#10 0x0043dbed in connection_read_thread (ctx=0x7f2f0518ec30,
argv=0x11) at
/home/build/git/sold-2445/openldap/servers/slapd/connection.c:1296
#11 0x7f570dc6a909 in ldap_int_thread_pool_wrapper (xpool=0x24e8500) at
/home/build/git/sold-2445/openldap/libraries/libldap_r/tpool.c:963
#12 0x7f570d8276ba in start_thread (arg=0x7f2f0518f700) at
pthread_create.c:333
#13 0x7f570c86f41d in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:109

On Wed, Feb 14, 2018 at 6:45 AM, Howard Chu  wrote:

> Will try to come up with a minimal reproducer. Currently it takes
> several hours to run the complete test, and a few hours before the SEGV
> occurs. But the stack trace is always identical when it happens. In
> multiple runs, it always succeeds on the host and always fails in the
> VM.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1749247
>
> Title:
>   Spurious SEGV running inside kvm
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/
> 1749247/+subscriptions
>

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

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501

[Touch-packages] [Bug 1749562] Re: openvpn tls-crypt not working

2018-02-14 Thread Tuxist

seems upstream already fixed
https://git.gnome.org/browse/network-manager-openvpn/commit/?id=d90cf9105e33fd4f646adf4f1ef8b9f95afc737b

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

Title:
  openvpn tls-crypt not working

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  if i try to connect to my openvpn 2.4 server i got this error on
  serverside:

  Feb 14 18:42:22 fenrir openvpn[58665]: tls-crypt unwrap error: packet too 
short
  Feb 14 18:42:22 fenrir openvpn[58665]: TLS Error: tls-crypt unwrapping failed 
from [AF_INET6]:::91.33.41.15:51754 (via :::192.168.2.2%igb0)

  my server conf:
  dev ovpns1
  verb 1
  dev-type tun
  dev-node /dev/tun1
  writepid /var/run/openvpn_server1.pid
  #user nobody
  #group nobody
  script-security 3
  daemon
  keepalive 10 60
  ping-timer-rem
  persist-tun
  persist-key
  proto udp
  cipher AES-256-CBC
  auth SHA512
  up /usr/local/sbin/ovpn-linkup
  down /usr/local/sbin/ovpn-linkdown
  client-connect /usr/local/sbin/openvpn.attributes.sh
  client-disconnect /usr/local/sbin/openvpn.attributes.sh
  multihome
  engine cryptodev
  tls-server
  server 10.4.0.0 255.255.0.0
  client-config-dir /var/etc/openvpn-csc/server1
  username-as-common-name
  auth-user-pass-verify "/usr/local/sbin/ovpn_auth_verify user ZmVucmly false 
server1 1194" via-env
  tls-verify "/usr/local/sbin/ovpn_auth_verify tls 'domain.local' 1"
  lport 1194
  management /var/etc/openvpn/server1.sock unix
  ca /var/etc/openvpn/server1.ca 
  cert /var/etc/openvpn/server1.cert 
  key /var/etc/openvpn/server1.key 
  dh /etc/dh-parameters.4096
  tls-crypt /var/etc/openvpn/server1.tls-crypt 
  ncp-ciphers AES-256-CBC
  persist-remote-ip
  float
  topology subnet

  my client config:

  dev tun
  persist-tun
  persist-key
  cipher AES-256-CBC
  ncp-ciphers AES-256-CBC
  auth SHA512
  tls-client
  client
  resolv-retry infinite
  remote tuxist.ddns.net 1194 udp
  verify-x509-name "domain.local" name
  auth-user-pass
  remote-cert-tls server

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.8.4-1ubuntu4
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Wed Feb 14 18:46:29 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2016-08-13 (550 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 10.3.0.1 dev wlp3s0 proto static metric 600 
   10.3.0.0/16 dev wlp3s0 proto kernel scope link src 10.3.141.174 metric 600 
   169.254.0.0/16 dev wlp3s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=false
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to bionic on 2018-02-12 (1 days ago)
  nmcli-dev:
   DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
   wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
gameofgods  404f7dfd-a05c-4271-9a7f-6e18bc31e0cf  
/org/freedesktop/NetworkManager/ActiveConnection/2 
   eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  -- 
 ----   
  
   lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  -- 
 ----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN 
   running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  disabled

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

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

[Touch-packages] [Bug 1698159] Re: linux-cloud-tools version specific packages are being removed by unattended-upgrade's Remove-Unused-Dependencies

2018-02-14 Thread Balint Reczey

Yes, indeed, the packages should be kept but 01autoremove-kernels is generated 
by /etc/kernel/postinst.d/apt-auto-removal which is shipped by apt.
Reassigning to apt.

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

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

** Package changed: unattended-upgrades (Ubuntu) => apt (Ubuntu)

** Also affects: unattended-upgrades (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  linux-cloud-tools version specific packages are being removed by
  unattended-upgrade's  Remove-Unused-Dependencies

Status in apt package in Ubuntu:
  Triaged
Status in unattended-upgrades package in Ubuntu:
  Triaged

Bug description:
  When running kernel version 4.4.0-78 (for example) and the unattended-
  upgrade packages installs a new kernel 4.4.0-79 (for example) the
  linux-cloud-tools-4.4.0-78 and linux-cloud-tools-4.4.0-78-generic
  packages are removed by the Remove-Unused-Dependencies rule, because
  unlike "normal" kernel packages they are not excluded by
  /etc/apt/apt.conf.d/01autoremove-kernels.

  The linux-cloud-tools package has the hyper-v integration services
  daemons in it, so it's deletion leaves some of the integration not
  working.

  Could /etc/apt/apt.conf.d/01autoremove-kernels be updated so other
  hyper-v users aren't caught out by this?

  Thanks,

  Ian.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unattended-upgrades 0.90ubuntu0.6
  ProcVersionSignature: Ubuntu 4.4.0-79.100-generic 4.4.67
  Uname: Linux 4.4.0-79-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.6
  Architecture: amd64
  Date: Thu Jun 15 15:27:35 2017
  InstallationDate: Installed on 2016-04-25 (415 days ago)
  InstallationMedia: Ubuntu-Server 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.3)
  PackageArchitecture: all
  SourcePackage: unattended-upgrades
  UpgradeStatus: No upgrade log present (probably fresh install)
  modified.conffile..etc.apt.apt.conf.d.10periodic: [modified]
  modified.conffile..etc.update-motd.d.90-updates-available: [deleted]
  modified.conffile..etc.update-motd.d.98-fsck-at-reboot: [deleted]
  modified.conffile..etc.update-motd.d.98-reboot-required: [deleted]
  mtime.conffile..etc.apt.apt.conf.d.10periodic: 2016-04-25T16:28:36.64

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

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

[Touch-packages] [Bug 1749086] XorgLogOld.txt

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055356/+files/XorgLogOld.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] XorgLog.txt

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055355/+files/XorgLog.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] Lspci.txt

apport information

** Attachment added: "Lspci.txt"
   https://bugs.launchpad.net/bugs/1749086/+attachment/5055347/+files/Lspci.txt

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

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] Lsusb.txt

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1749086/+attachment/5055348/+files/Lsusb.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] Xrandr.txt

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1749086/+attachment/5055357/+files/Xrandr.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] xdpyinfo.txt

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055358/+files/xdpyinfo.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

** Changed in: apport (Ubuntu Bionic)
   Status: Triaged => In Progress

** Changed in: apport (Ubuntu Bionic)
 Assignee: (unassigned) => Brian Murray (brian-murray)

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  In Progress
Status in apport source package in Bionic:
  In Progress

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1749086] ProcInterrupts.txt

apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055352/+files/ProcInterrupts.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] ProcModules.txt

apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055353/+files/ProcModules.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] UdevDb.txt

apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1749086/+attachment/5055354/+files/UdevDb.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] ProcEnviron.txt

apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055351/+files/ProcEnviron.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] ProcCpuinfo.txt

apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055349/+files/ProcCpuinfo.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] ProcCpuinfoMinimal.txt

apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055350/+files/ProcCpuinfoMinimal.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] DpkgLog.txt

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055343/+files/DpkgLog.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] Dependencies.txt

apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055342/+files/Dependencies.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] LightdmDisplayLog.txt

apport information

** Attachment added: "LightdmDisplayLog.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055345/+files/LightdmDisplayLog.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] JournalErrors.txt

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055344/+files/JournalErrors.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] LightdmLog.txt

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055346/+files/LightdmLog.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] CurrentDmesg.txt

apport information

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1749086/+attachment/5055341/+files/CurrentDmesg.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/1749086

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (3 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine:

[Touch-packages] [Bug 1749086] Re: (X)Ubuntu 16.04.3 LTS: sleep on boot

Oops, just realized my BIOS version is most recent for this MOBO.
Sending report.

** Description changed:

  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please tell
  me what other info you need.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
+ --- 
+ ApportVersion: 2.20.1-0ubuntu2.15
+ Architecture: amd64
+ CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
+ CompositorRunning: None
+ CurrentDesktop: XFCE
+ DistUpgraded: Fresh install
+ DistroCodename: xenial
+ DistroRelease: Ubuntu 16.04
+ DistroVariant: ubuntu
+ ExtraDebuggingInterest: Yes, including running git bisection searches
+ GraphicsCard:
+  Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
+Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
+ InstallationDate: Installed on 2018-02-11 (3 days ago)
+ InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
+ MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
+ Package: xorg 1:7.7+13ubuntu3
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
+ ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
+ Tags:  xenial ubuntu
+ Uname: Linux 4.13.0-32-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

2018-02-14 Thread Launchpad Bug Tracker

** Branch linked: lp:apport

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1731505] Re: boot into link down state

I'm working on this in systemd upstream; should get it working soon.

** Changed in: netplan
   Status: Triaged => In Progress

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

** Changed in: systemd (Ubuntu)
   Status: New => In Progress

** Changed in: systemd (Ubuntu)
   Importance: Undecided => Wishlist

** Changed in: netplan
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: systemd (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

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

Title:
  boot into link down state

Status in netplan:
  In Progress
Status in systemd package in Ubuntu:
  In Progress

Bug description:
  I have multiple NICs in my Ubuntu 17.10 server, and i want at least
  one of them to be configured but not brought UP on boot. I want it to
  boot into link state DOWN. I'd also prefer the link to be / stay down
  during boot-up.

  My use case requires manual 'ip link set enp2s0f3 up', or 'ifup
  enp2s0f3' as it were. When the interface is being brought up manually,
  it should already be configured. I'm looking for a link state toggle,
  like a hardware switch on a Cat6 cable.

  My request is intended to reproduce the behaviour of the old
  ifupdown's /etc/network/interfaces, without enabling 'auto' or 'allow-
  hotplug'.

  #auto enp2s0f3
  #allow-hotplug enp2s0f3
  iface enp2s0f3 inet static
  address 10.10.1.10
  netmask 255.255.255.0
  network 10.10.1.0
  broadcast 10.10.1.255
  gateway 10.10.1.1
  dns-nameservers 10.10.1.1

  It seems neither systemd, nor NetworkManager "have any way to specify
  you want a configured device to stay down". -- i'm quoting cyphermox
  from the freenode/netplan IRC

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

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

[Touch-packages] [Bug 1746419] Re: bond parameters are not changed by 'netplan apply'

Sounds like this is a bug in systemd, since it's what will deal with the
actual devices.

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

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

Title:
  bond parameters are not changed by 'netplan apply'

Status in nplan package in Ubuntu:
  New
Status in systemd package in Ubuntu:
  New

Bug description:
  I have a yaml file as follows:

  network:
  version: 2
  ethernets:
  bonddevs:
  match:
  name: ens[78]
  bonds:
  bond0:
  interfaces: [bonddevs]
  parameters:
  mode: active-backup
  mii-monitor-interval: 1
  addresses:
  - 10.10.10.1/24

  
  Say I decide that 1s is too frequent for the MII interval, and I want to 
change the interval to 2s.

  If I change that in the yaml, then run
  # netplan generate
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 1000

  In other words, the change has not been applied.

  Running netplan --debug apply prints:
  DEBUG:device bond0 operstate is up, not replugging

  So I wondered if bringing the bond down would help. It does not:
  # ip link set dev bond0 down
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 1000

  However, deleting the link works:
  # ip link del dev bond0
  # netplan apply
  # cat /proc/net/bonding/bond0|grep "MII Polling Interval (ms)"
  MII Polling Interval (ms): 2000

  This is counter-intuitive behaviour.
  Ideally, I would like a regular netplan apply to work without deleting the 
bond.
  However, a changed to the docs to make this clear would be OK.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: nplan 0.32~17.10.1
  ProcVersionSignature: User Name 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  Date: Wed Jan 31 05:47:42 2018
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=C.UTF-8
   SHELL=/bin/bash
  SourcePackage: nplan
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749086] Re: (X)Ubuntu 16.04.3 LTS: sleep on boot

The problem is back. Gonna update BIOS tomorrow and send the automated
report.

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

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1749562] [NEW] openvpn tls-crypt not working

2018-02-14 Thread Tuxist

Public bug reported:

Hi,

if i try to connect to my openvpn 2.4 server i got this error on
serverside:

Feb 14 18:42:22 fenrir openvpn[58665]: tls-crypt unwrap error: packet too short
Feb 14 18:42:22 fenrir openvpn[58665]: TLS Error: tls-crypt unwrapping failed 
from [AF_INET6]:::91.33.41.15:51754 (via :::192.168.2.2%igb0)

my server conf:
dev ovpns1
verb 1
dev-type tun
dev-node /dev/tun1
writepid /var/run/openvpn_server1.pid
#user nobody
#group nobody
script-security 3
daemon
keepalive 10 60
ping-timer-rem
persist-tun
persist-key
proto udp
cipher AES-256-CBC
auth SHA512
up /usr/local/sbin/ovpn-linkup
down /usr/local/sbin/ovpn-linkdown
client-connect /usr/local/sbin/openvpn.attributes.sh
client-disconnect /usr/local/sbin/openvpn.attributes.sh
multihome
engine cryptodev
tls-server
server 10.4.0.0 255.255.0.0
client-config-dir /var/etc/openvpn-csc/server1
username-as-common-name
auth-user-pass-verify "/usr/local/sbin/ovpn_auth_verify user ZmVucmly false 
server1 1194" via-env
tls-verify "/usr/local/sbin/ovpn_auth_verify tls 'domain.local' 1"
lport 1194
management /var/etc/openvpn/server1.sock unix
ca /var/etc/openvpn/server1.ca 
cert /var/etc/openvpn/server1.cert 
key /var/etc/openvpn/server1.key 
dh /etc/dh-parameters.4096
tls-crypt /var/etc/openvpn/server1.tls-crypt 
ncp-ciphers AES-256-CBC
persist-remote-ip
float
topology subnet

my client config:

dev tun
persist-tun
persist-key
cipher AES-256-CBC
ncp-ciphers AES-256-CBC
auth SHA512
tls-client
client
resolv-retry infinite
remote tuxist.ddns.net 1194 udp
verify-x509-name "domain.local" name
auth-user-pass
remote-cert-tls server

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: network-manager 1.8.4-1ubuntu4
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia
ApportVersion: 2.20.8-0ubuntu8
Architecture: amd64
CurrentDesktop: KDE
Date: Wed Feb 14 18:46:29 2018
IfupdownConfig:
 # interfaces(5) file used by ifup(8) and ifdown(8)
 auto lo
 iface lo inet loopback
InstallationDate: Installed on 2016-08-13 (550 days ago)
InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
IpRoute:
 default via 10.3.0.1 dev wlp3s0 proto static metric 600 
 10.3.0.0/16 dev wlp3s0 proto kernel scope link src 10.3.141.174 metric 600 
 169.254.0.0/16 dev wlp3s0 scope link metric 1000
NetworkManager.state:
 [main]
 NetworkingEnabled=true
 WirelessEnabled=true
 WWANEnabled=false
SourcePackage: network-manager
UpgradeStatus: Upgraded to bionic on 2018-02-12 (1 days ago)
nmcli-dev:
 DEVICE  TYPE  STATEDBUS-PATH  
CONNECTION  CON-UUID  CON-PATH  
 
 wlp3s0  wifi  connected/org/freedesktop/NetworkManager/Devices/3  
gameofgods  404f7dfd-a05c-4271-9a7f-6e18bc31e0cf  
/org/freedesktop/NetworkManager/ActiveConnection/2 
 eno1ethernet  unavailable  /org/freedesktop/NetworkManager/Devices/2  --   
   ---- 

 lo  loopback  unmanaged/org/freedesktop/NetworkManager/Devices/1  --   
   ----
nmcli-nm:
 RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  WIFI  
   WWAN-HW  WWAN 
 running  1.8.4connected  started  full  enabled enabled  
enabled  enabled  disabled

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


** Tags: amd64 apport-bug bionic

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

Title:
  openvpn tls-crypt not working

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hi,

  if i try to connect to my openvpn 2.4 server i got this error on
  serverside:

  Feb 14 18:42:22 fenrir openvpn[58665]: tls-crypt unwrap error: packet too 
short
  Feb 14 18:42:22 fenrir openvpn[58665]: TLS Error: tls-crypt unwrapping failed 
from [AF_INET6]:::91.33.41.15:51754 (via :::192.168.2.2%igb0)

  my server conf:
  dev ovpns1
  verb 1
  dev-type tun
  dev-node /dev/tun1
  writepid /var/run/openvpn_server1.pid
  #user nobody
  #group nobody
  script-security 3
  daemon
  keepalive 10 60
  ping-timer-rem
  persist-tun
  persist-key
  proto udp
  cipher AES-256-CBC
  auth SHA512
  up /usr/local/sbin/ovpn-linkup
  down /usr/local/sbin/ovpn-linkdown
  client-connect /usr/local/sbin/openvpn.attributes.sh
  client-disconnect /usr/local/sbin/openvpn.attributes.sh
  multihome
  engine cryptodev
  tls-server
  server 10.4.0.0 255.255.0.0
  client-config-dir /var/etc/openvpn-csc/server1
  username-as-common-name
  auth-user-pass-verify "/usr/local/sbin/ovpn_auth_verify user ZmVucmly false 
server1 1194" via-env
  tls-verify "/usr/local/sbin/ovpn_auth_verify tls 'domain.local' 1"
  lport 1194

[Touch-packages] [Bug 1377653] Re: HDMI sound output not detected / NVIDIA optimus laptop

2018-02-14 Thread Pete

I can confirm that #19 works, as well. Also applied the suggestions in #24.
Ubuntu 17.10 on a Lenovo Ideapad Y910-17ISK with a GTX 1070.
I don't notice any flicker or any problem. The audio device has just appeared, 
and everything works fine now :-) 
Thanks a lot!!

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

Title:
  HDMI sound output not detected / NVIDIA optimus laptop

Status in alsa-driver package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  not sure if this is an alsa or nvidia/nouveau bug.
  HDMI audio output doesn't appear in sound settings output panel.
  Audio works well on internal speakers, but it seems there is no way to make 
it output to hdmi...

  The laptop has optimus NVIDIA+Intel.
  The behaviour is the same with nouveau or nvidia proprietary driver.

  Please let me know if further testing is required

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu4
  ProcVersionSignature: Ubuntu 3.13.0-36.63-generic 3.13.11.6
  Uname: Linux 3.13.0-36-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  sam2295 F pulseaudio
  CurrentDesktop: Unity
  CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order 
/var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission 
denied
  Date: Sun Oct  5 17:05:35 2014
  InstallationDate: Installed on 2014-04-21 (166 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Title: PCI/internal sound card not detected
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/02/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: N56VZ.215
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: N56VZ
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrN56VZ.215:bd11/02/2012:svnASUSTeKCOMPUTERINC.:pnN56VZ:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnN56VZ:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.name: N56VZ
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.

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

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

[Touch-packages] [Bug 1619258] Re: netplan should allow NICs to be disconnected and not stall the boot

In progress; we got optional: true for that and systemd has a
corresponding "RequiredForOnline=false".

** Changed in: nplan (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: nplan (Ubuntu)
   Importance: Undecided => High

** Changed in: nplan (Ubuntu)
 Assignee: (unassigned) => Mathieu Trudel-Lapierre (cyphermox)

** Changed in: systemd (Ubuntu)
   Status: New => Fix Released

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

Title:
  netplan should allow NICs to be disconnected and not stall the boot

Status in Snappy:
  Confirmed
Status in nplan package in Ubuntu:
  In Progress
Status in systemd package in Ubuntu:
  Fix Released

Bug description:
  in older snappy image we used to set "allow-hotplug" in
  /etc/network/interfaces.d/ when configuring a NIC to avoid the boot to
  completely stall or to be stuck for 5min when trying to find an
  internet connection.

  with recent versions of netplan the configuration seems to be back to
  require a network to be up before moving on with them boot so that
  booting takes forever until the network connection times out.

  netplan should make the system check the physical link status when
  trying to bring up a network device instead of stalling the boot.

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

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

[Touch-packages] [Bug 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications

2018-02-14 Thread Timo Aaltonen

oh it's a qt bug not mesa, got it

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

Title:
  mesa 18.0.0 will cause rendering errors in Qt applications

Status in mesa package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  From: https://bugreports.qt.io/browse/QTBUG-66348

  ** extract **

  The `QOpenGLShaderProgram` class in Qt can be used to compile and link
  OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is
  available, it can cache those shaders on disk
  (~/.cache/qtshadercache). The i965 driver in Mesa supports this
  extension since version 18.0.0.

  When the shader is loaded using the `glProgramBinary` function, OpenGL
  can refuse it if for example some hardware or software component
  changed. Mesa refuses binaries that were created by any other build of
  Mesa (using among other things the build_id of the library).

  If the shader is refused, Qt should fallback to compiling it from
  sources, but it incorrectly calls glLinkProgram first. The
  glLinkProgram succeeds, because it actually links 0 shaders together.
  That is allowed in OpenGL compatibility profile and the resulting
  program works as a fixed pipeline. Which of course does not render as
  expected.

  This causes rendering errors in Qt applications every time Mesa is
  updated since version 18.0.0. For example white screen in sddm.

  This issue was originally reported in openSUSE
  (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578).

  ** end extract **

  As this potentially effects Qt applications, and could even render
  display manager login unusable, this should be a blocking bug in mesa
  and Qt until Qt mitigations patches pass codereview and can be
  included in Qtbase for 18.04.

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

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

[Touch-packages] [Bug 1749279] Re: Still using problematic adobe-flashplayer

I don't see how this is an apport issue, that's likely just a message
from your browser.

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

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

Title:
  Still using problematic adobe-flashplayer

Status in Ubuntu:
  New

Bug description:
  Output when running apport-collect:

   apport-collect ***
  The authorization page:
   
(https://launchpad.net/+authorize-token?oauth_token=LqxC5SPg3jmN2S9BJVKl_permission=DESKTOP_INTEGRATION)
  should be opening in your browser. Use your browser to authorize
  this program to access Launchpad on your behalf.
  Waiting to hear from Launchpad about your decision...
  Using PPAPI flash.
   --ppapi-flash-path=/usr/lib/adobe-flashplugin/libpepflashplayer.so 
--ppapi-flash-version=

  

  What is the need to still use that closed/deprecated player, when this
  is now very rarely installed on systems due to the endless problems
  met. Nowadays browser use html5 instead (if only required by apport-
  collect !!!)

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.8-0ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportLog:
   
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Feb 13 20:28:49 2018
  EcryptfsInUse: Yes
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: apport
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749472] Re: mesa 18.0.0 will cause rendering errors in Qt applications

2018-02-14 Thread Timo Aaltonen

sigh, is this filed upstream?

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

Title:
  mesa 18.0.0 will cause rendering errors in Qt applications

Status in mesa package in Ubuntu:
  New
Status in qtbase-opensource-src package in Ubuntu:
  New
Status in mesa source package in Bionic:
  New
Status in qtbase-opensource-src source package in Bionic:
  New

Bug description:
  From: https://bugreports.qt.io/browse/QTBUG-66348

  ** extract **

  The `QOpenGLShaderProgram` class in Qt can be used to compile and link
  OpenGL shaders. If the `GL_ARB_get_program_binary` OpenGL extension is
  available, it can cache those shaders on disk
  (~/.cache/qtshadercache). The i965 driver in Mesa supports this
  extension since version 18.0.0.

  When the shader is loaded using the `glProgramBinary` function, OpenGL
  can refuse it if for example some hardware or software component
  changed. Mesa refuses binaries that were created by any other build of
  Mesa (using among other things the build_id of the library).

  If the shader is refused, Qt should fallback to compiling it from
  sources, but it incorrectly calls glLinkProgram first. The
  glLinkProgram succeeds, because it actually links 0 shaders together.
  That is allowed in OpenGL compatibility profile and the resulting
  program works as a fixed pipeline. Which of course does not render as
  expected.

  This causes rendering errors in Qt applications every time Mesa is
  updated since version 18.0.0. For example white screen in sddm.

  This issue was originally reported in openSUSE
  (https://bugzilla.opensuse.org/show_bug.cgi?id=1080578).

  ** end extract **

  As this potentially effects Qt applications, and could even render
  display manager login unusable, this should be a blocking bug in mesa
  and Qt until Qt mitigations patches pass codereview and can be
  included in Qtbase for 18.04.

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

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

[Touch-packages] [Bug 1746874] Re: gnome-shell and Xwayland sometimes leave $HOME/core files (should be /var/crash files)

Got it, I missed the difference between 1941 and 1946. Thanks for the
clarification.

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

Title:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files)

Status in apport package in Ubuntu:
  Triaged
Status in apport source package in Bionic:
  Triaged

Bug description:
  gnome-shell and Xwayland sometimes leave $HOME/core files (should be
  /var/crash files). This issue was first mentioned in bug 1746653. But
  then I noticed my machine doing it too...

  This is despite:

  $ grep . /proc/sys/kernel/core_*
  /proc/sys/kernel/core_pattern:|/usr/share/apport/apport %p %s %c %d %P
  /proc/sys/kernel/core_pipe_limit:0
  /proc/sys/kernel/core_uses_pid:0

  So really there are two problems:

  1. ~/core files are created but no /var/crash/ files
  2. Because they all have the same name (core_uses_pid == 0), when gnome-shell 
crashes as a result of an Xwayland crash, you can only get the core from one of 
them at most.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-shell 3.26.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  Date: Fri Feb  2 15:13:52 2018
  DisplayManager:

  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  SourcePackage: gnome-shell
  UpgradeStatus: No upgrade log present (probably fresh install)
  ---
  ApportVersion: 2.20.8-0ubuntu7
  Architecture: amd64
  CrashReports:
   640:1000:118:3122469:2018-01-29 16:25:03.658845409 +0800:2018-02-02 
15:39:18.799970611 +0800:/var/crash/_usr_bin_Xwayland.1000.crash
   640:1000:118:24558024:2018-01-29 16:22:23.127058238 +0800:2018-02-02 
15:39:18.887970685 +0800:/var/crash/_usr_bin_gdb.1000.crash
   640:120:118:23982380:2018-01-29 15:52:09.799486456 +0800:2018-01-29 
15:51:51.467493515 +0800:/var/crash/_usr_bin_gnome-shell.120.crash
   640:1000:118:6315115:2018-01-29 16:18:12.723424671 +0800:2018-01-29 
16:18:10.555428082 +0800:/var/crash/_usr_bin_gnome-shell.1000.crash
   640:120:118:3103046:2018-01-29 15:52:12.923485257 +0800:2018-01-29 
15:52:09.859486433 +0800:/var/crash/_usr_bin_Xwayland.120.crash
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2017-12-12 (52 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171211)
  Package: mutter
  PackageArchitecture: all
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Tags:  bionic
  Uname: Linux 4.13.0-25-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Touch-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11

2018-02-14 Thread Timo Aaltonen

don't jump the gun, mesa hasn't landed in bionic yet and won't land
before nvidia is fixed to work with libglvnd..

** Changed in: mesa (Ubuntu)
   Status: Fix Released => Fix Committed

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Committed
Status in totem package in Ubuntu:
  Invalid

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

Verification of Proposed:
[2020342.769272] audit: type=1400 audit(1518622578.674:4871): apparmor="DENIED" 
operation="open" namespace="root//lxd-artful-test_" 
profile="/usr/sbin/ntpd" name="/usr/local/sbin/" pid=16638 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0
[2020342.769282] audit: type=1400 audit(1518622578.674:4872): apparmor="DENIED" 
operation="open" namespace="root//lxd-artful-test_" 
profile="/usr/sbin/ntpd" name="/usr/local/bin/" pid=16638 comm="ntpd" 
requested_mask="r" denied_mask="r" fsuid=0 ouid=0


After upgrade from proposed:
- 1:4.2.8p10+dfsg-5ubuntu3.2

The messages above are gone - so verified

** Tags removed: verification-needed verification-needed-artful
** Tags added: verification-done verification-done-artful

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1749389] Re: ntpdate lock apparmor deny

Verification of proposed:
xenial/artful as is on restart:
[2020349.483870] audit: type=1400 audit(1518622585.386:4875): apparmor="DENIED" 
operation="file_inherit" 
namespace="root//lxd-xenial-test_" 
profile="/usr/sbin/ntpd" name="/run/lock/ntpdate" pid=16784 comm="ntpd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0
[2020342.768379] audit: type=1400 audit(1518622578.674:4870): apparmor="DENIED" 
operation="file_inherit" 
namespace="root//lxd-artful-test_" 
profile="/usr/sbin/ntpd" name="/run/lock/ntpdate" pid=16638 comm="ntpd" 
requested_mask="w" denied_mask="w" fsuid=0 ouid=0

After upgrade from proposed:
- 1:4.2.8p4+dfsg-3ubuntu5.8
- 1:4.2.8p10+dfsg-5ubuntu3.2

The messages above are gone - so verified

** Tags removed: verification-needed verification-needed-artful 
verification-needed-xenial
** Tags added: verification-done verification-done-artful 
verification-done-xenial

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

Title:
  ntpdate lock apparmor deny

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Fix Committed
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no
     issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
  Note: to not be mislead, on xenial there is a remaining stdout appamor 
  issue which is bug 1670408

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
     changes poses a security risk so regression potential on it's own
     should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would
     e.g. no more be freed up or the action behind the locking would cause
     issues.

  [Other Info]

   * n/a

  On start/restart nto has an error in apparmor due to the locking it
  tries to avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

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

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

[Touch-packages] [Bug 1749150] Re: Spontaneous single window freezing

Valentin Nechayev, please don't apport-collect from different machines. If you 
have an issue with different hardware, it is most helpful to file a new report 
instead via a terminal:
ubuntu-bug xorg

Despite this, this appears correlated to a KDE'ism. Is the issue
reproducible if you use GNOME? One may test a live environment via
http://cdimage.ubuntu.com/daily-live/current/ to confirm.

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a

[Touch-packages] [Bug 1746638] Re: [GeForce 6150SE nForce 430] PC freezes and crashes

2018-02-14 Thread Diogo Gomes

Christopher M. Penalver,

I have not had availability to test version 18.04 on a new disc but I
have more information:

- After updating the packages xorg-serverhwe... I decided to test
the Open Source drivers again and got improvements.

- Due to these improvements and to the system crashing less, I detected
a pattern in the crashes. It may not be related but crashes usually
happen when I adjust the size of a window manually.

I'll let you know as soon as I have more information.

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

Title:
  [GeForce 6150SE nForce 430] PC freezes and crashes

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  When using the nouveau graphics driver my pc freezes and crashes.

  WORKAROUND: Use the proprietary nvidia driver.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  Date: Thu Feb  1 01:36:25 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   NVIDIA Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2) 
(prog-if 00 [VGA controller])
     Subsystem: ASUSTeK Computer Inc. C61 [GeForce 6150SE nForce 430] 
[1043:8234]
  InstallationDate: Installed on 2017-11-23 (69 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  Lsusb:
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
   Bus 002 Device 003: ID 04b8:082f Seiko Epson Corp. PX-A620 [Stylus 
CX3900/DX4000/DX4050]
   Bus 002 Device 002: ID 1241:1166 Belkin MI-2150 Trust Mouse
   Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
  MachineType: System manufacturer System Product Name
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=d7ad7807-5ead-49f7-8978-2e035ab6dd15 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/29/2008
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0602
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: M2N-MX SE Plus
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev x.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0602:bd10/29/2008:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM2N-MXSEPlus:rvrRevx.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  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.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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Thu Feb  1 01:34:53 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputHID 1241:1166MOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   Failed to load module "nvidia" (module does not exist, 0)
   Failed to load module "nvidia" (module does not exist, 0)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: nouveau

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

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

[Touch-packages] [Bug 1749150] Re: Spontaneous single window freezing

** Tags added: bios-outdated-2.50

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

Title:
  Spontaneous single window freezing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Sometimes a window stopped refreshing its contents. Different applications 
affected: known examples include xterm, Firefox, CodeBlocks, KDE lock screen.
  No way found to revive in-time refreshing except full window closing (or 
blind login, in case of KDE lock screen). Keyboard or mouse activity in a such 
window doesn't help.
  A one-shot refresh can be easily caused by switching to another virtual 
desktop and then back. After such switching, a window refresh is active for 
approximately 0.5 seconds, then stops again.
  No relation to host uptime or X session uptime is visible.

  Observed on two different hosts, both carrying Kubuntu 16.04 and
  running XWindow+KDE as desktop environment. KDE is standard Kubuntu
  one. Multiple virtual desktops are used on both hosts.

  The issue started to appear approximately 4-5 months ago but I can't
  specify exact package change that could have caused it. Both hosts are
  regularly updated (no more than 1 week delay).

  The first host has:
  video: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. 
[AMD/ATI] Turks XT [Radeon HD 6670/7670] (prog-if 00 [VGA controller])
  Subsystem: ASUSTeK Computer Inc. Turks XT [Radeon HD 6670/7670]
  Kernel driver in use: radeon
  Kernel modules: radeon
  CPU: AMD FX-8150
  RAM: 16GB
  Installed as Kubuntu 14.04, upgraded to 16.04 via do-release-upgrade.
  current kernel: linux-image-4.4.0-112-generic
  video packages: non-HWE series (e.g. xserver-xorg=1:7.7+13ubuntu3); active 
driver: radeon

  Issue rate on this host is rather tiny (~1 per week).

  The second one has:
  video: 01:00.0 VGA compatible controller: NVIDIA Corporation Device 128b (rev 
a1) (prog-if 00 [VGA controller])
  Subsystem: Micro-Star International Co., Ltd. [MSI] Device 8c93
  Kernel driver in use: nvidia
  Kernel modules: nvidiafb, nouveau, nvidia_384_drm, nvidia_384
  (really this is GeForce GT 740)
  CPU:Intel i3-4170
  RAM: 16GB
  Installed originally as Kubuntu 16.04
  current kernel: linux-image-4.13.0-32-generic (depended on by 
linux-generic-hwe-16.04)
  video packages: HWE series (e.g. 
xserver-xorg-hwe-16.04=1:7.7+16ubuntu3~16.04.1); active driver: nvidia 
(proprietary), but the same issue observed with VESA driver.

  Issue rate on this host is 1-2 per day and was much higher with VESA
  driver in use.

  No respective messages are found in Xorg.*.log or ~/.xsession-errors,
  but the latter has got stream of messages like:

  at host with AMD and Radeon:
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 86 , Name: "HDMI-0" 
) ( "HDMI-0" ) to KScreen::Output(Id: 86 , Name: "HDMI-0" ) ( "HDMI-0" )

  at host with Intel and Nvidia:
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )
  kscreen: Primary output changed from KScreen::Output(Id: 640 , Name: 
"DVI-D-0" ) ( "DVI-D-0" ) to KScreen::Output(Id: 640 , Name: "DVI-D-0" ) ( 
"DVI-D-0" )

  such messages started appearing approximately at the same time, plus-
  minus 1-2 months.

  Additional info can be provided on demand.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg 1:7.7+13ubuntu3
  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
  CurrentDesktop: KDE
  Date: Tue Feb 13 11:47:32 2018
  InstallationDate: Installed on 2014-12-16 (1154 days ago)
  InstallationMedia: Kubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2017-03-29 (321 days ago)
  --- 
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
u'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  384.111  Tue Dec 19 23:51:45 
PST 2017
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.5)
  .proc.driver.nvidia.warnings.fbdev:
   Your system is not currently configured to drive a VGA console
   on the primary VGA device. The NVIDIA Linux graphics driver
   requires the use of a text-mode VGA console. Use of other console
   drivers including, but not limited to, vesafb, may result in
   corruption and stability problems, and is not supported.
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for

[Touch-packages] [Bug 1749086] Re: (X)Ubuntu 16.04.3 LTS: sleep on boot

** Tags added: bios-outdated-1.90

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

Title:
  (X)Ubuntu 16.04.3 LTS: sleep on boot

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Newly installed xubuntu, kubuntu (other flavours I haven't tried, but
  probably the same), the screen turns off a few seconds after choosing
  ubuntu in grub2 menu, after about 5 minutes it comes back to life and
  login screen is presented and from that point on everything seems to
  work as normal. (Might have sth to do with Radeon drivers?) Please
  tell me what other info you need.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Tue Feb 13 07:37:53 2018
  InstallationDate: Installed on 2018-02-11 (1 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.1-0ubuntu2.15
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: XFCE
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroRelease: Ubuntu 16.04
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Juniper XT [Radeon HD 5770] 
[1002:68b8] (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Juniper XT [Radeon HD 5770] [1043:03b6]
  InstallationDate: Installed on 2018-02-11 (2 days ago)
  InstallationMedia: Xubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
  Package: xorg 1:7.7+13ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-32-generic 
root=UUID=7529842e-d871-4641-89dc-3a4980dda2de ro quiet splash vt.handoff=7
  ProcVersionSignature: Ubuntu 4.13.0-32.35~16.04.1-generic 4.13.13
  Tags:  xenial ubuntu
  Uname: Linux 4.13.0-32-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 10/18/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P1.80
  dmi.board.name: 770 Extreme3
  dmi.board.vendor: ASRock
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: To Be Filled By O.E.M.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP1.80:bd10/18/2010:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn770Extreme3:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: To Be Filled By O.E.M.
  dmi.product.version: To Be Filled By O.E.M.
  dmi.sys.vendor: To Be Filled By O.E.M.
  version.compiz: compiz N/A
  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.4-0ubuntu1~16.04.4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.4-0ubuntu1~16.04.4
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A

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

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

[Touch-packages] [Bug 1749540] [NEW] qemu tests should run on more architectures

Public bug reported:

qemu tests should be able to run on more architectures.

adt tests are missing dependencies, to e.g. excercise qemu-only tests on
non-amd64 arches.

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

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

Title:
  qemu tests should run on more architectures

Status in systemd package in Ubuntu:
  New

Bug description:
  qemu tests should be able to run on more architectures.

  adt tests are missing dependencies, to e.g. excercise qemu-only tests
  on non-amd64 arches.

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

-- 
Mailing list: https://launchpad.net/~touch-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-02-14 Thread Joshua Powers

Thanks for filing a bug.

>From your terminal log:
Feb 13 08:32:25 jb2-System-Product-Name sshd[3943]: /etc/ssh/sshd_config: lin...
Feb 13 08:32:25 jb2-System-Product-Name sshd[3943]: /etc/ssh/sshd_config: ter...

I'm willing to bet there is something wrong with your
/etc/ssh/sshd_config.

Try running `sudo /usr/sbin/sshd -t`

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

-- 
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:
  Incomplete

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 1749480] Re: Totem black screen with Sparks

i suppose you hit that lp:1747744 dont you; which is solved by upgrading
to mesa 18 (proposed)

** Changed in: gstreamer1.0 (Ubuntu)
   Status: New => Incomplete

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

Title:
  Totem black screen with Sparks

Status in gstreamer1.0 package in Ubuntu:
  Incomplete

Bug description:
  Try play a video in Ubuntu 18.04 x11, i see a black screen with sparks. Same 
video is played correctly in wayland session.
  corrado@corrado-p9-bb-1221:~$ inxi -SCGx
  System:Host: corrado-p9-bb-1221 Kernel: 4.15.0-9-generic x86_64
 bits: 64 gcc: 7.3.0
 Desktop: Gnome 3.26.2 (Gtk 3.22.26-2ubuntu1)
 Distro: Ubuntu Bionic Beaver (development branch)
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) 
 arch: Skylake rev.9 cache: 3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 800 MHz 2: 800 MHz 3: 804 MHz
 4: 811 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 17.3.3 Direct Render: Yes
  corrado@corrado-p9-bb-1221:~$ apt policy totem
  totem:
Installed: 3.26.0-0ubuntu3
Candidate: 3.26.0-0ubuntu3
Version table:
   *** 3.26.0-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p9-bb-1221:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.12.4-1
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 15:58:07 2018
  InstallationDate: Installed on 2017-12-23 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Touch-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11

Clearly cant blame totem.

** Changed in: totem (Ubuntu)
   Status: Confirmed => Invalid

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Invalid

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 108366] Re: Totem unable to add to playlist after selecting unreadable location

2018-02-14 Thread Bug Watch Updater

** Changed in: gtk
   Status: Unknown => Confirmed

** Changed in: gtk
   Importance: Unknown => Medium

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

Title:
  Totem unable to add to playlist after selecting unreadable location

Status in GTK+:
  Confirmed
Status in Totem:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: totem

  When adding to the playlist using the sidebar interface, totem
  defaults to the directory of the last selected file when prompting for
  a new file.  When that directory is unreadable (e.g.
  http://www.gearwire.com/media/ (after adding
  http://www.gearwire.com/media/seymour-duncan-guitar-
  pickups-1-musikmesse.wmv by pasting into the location control in the
  last add)), totem presents the message "error accessing
  'http://www.gearwire.com/media': Access denied".  If this dialog is
  closed, totem is unable to add new files to the playlist (even when
  pasting the Location) until a readable base location (e.g. the home
  directory) is selected.

  In functional terms:

  Observed Behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Paste another location in the Location control
  10)  Click "Add" to add the location
  11)  Nothing happens (no UI changes (except button blink), no message, etc.

  Expected Behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Paste another location in the Location control
  10)  Click "Add" to add the location
  11)  Totem shows the new file in the playlist

  Alternate acceptable behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Totem defauls to user home directory (or /media, or any known safe 
location)
  10)  Paste another location in the Location control
  11)  Click "Add" to add the location
  12)  Totem shows the new file in the playlist

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

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

[Touch-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11

And totem reads video without problem with mesa 18

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 1749480] [NEW] Totem black screen with Sparks

2018-02-14 Thread corrado venturini

Public bug reported:

Try play a video in Ubuntu 18.04 x11, i see a black screen with sparks. Same 
video is played correctly in wayland session.
corrado@corrado-p9-bb-1221:~$ inxi -SCGx
System:Host: corrado-p9-bb-1221 Kernel: 4.15.0-9-generic x86_64
   bits: 64 gcc: 7.3.0
   Desktop: Gnome 3.26.2 (Gtk 3.22.26-2ubuntu1)
   Distro: Ubuntu Bionic Beaver (development branch)
CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) 
   arch: Skylake rev.9 cache: 3072 KB
   flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
   clock speeds: max: 3900 MHz 1: 800 MHz 2: 800 MHz 3: 804 MHz
   4: 811 MHz
Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
   Display Server: x11 (X.Org 1.19.6 ) driver: i915
   Resolution: 1920x1080@60.00hz
   OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
   version: 4.5 Mesa 17.3.3 Direct Render: Yes
corrado@corrado-p9-bb-1221:~$ apt policy totem
totem:
  Installed: 3.26.0-0ubuntu3
  Candidate: 3.26.0-0ubuntu3
  Version table:
 *** 3.26.0-0ubuntu3 500
500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
100 /var/lib/dpkg/status
corrado@corrado-p9-bb-1221:~$

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: libgstreamer1.0-0 1.12.4-1
ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
Uname: Linux 4.15.0-9-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 14 15:58:07 2018
InstallationDate: Installed on 2017-12-23 (53 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
SourcePackage: gstreamer1.0
UpgradeStatus: No upgrade log present (probably fresh install)
XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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


** Tags: bionic totem x11

** Attachment added: "Screenshot from 2018-02-14 15-54-29.png"
   
https://bugs.launchpad.net/bugs/1749480/+attachment/5055178/+files/Screenshot%20from%202018-02-14%2015-54-29.png

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

Title:
  Totem black screen with Sparks

Status in gstreamer1.0 package in Ubuntu:
  New

Bug description:
  Try play a video in Ubuntu 18.04 x11, i see a black screen with sparks. Same 
video is played correctly in wayland session.
  corrado@corrado-p9-bb-1221:~$ inxi -SCGx
  System:Host: corrado-p9-bb-1221 Kernel: 4.15.0-9-generic x86_64
 bits: 64 gcc: 7.3.0
 Desktop: Gnome 3.26.2 (Gtk 3.22.26-2ubuntu1)
 Distro: Ubuntu Bionic Beaver (development branch)
  CPU:   Dual core Intel Core i3-7100 (-MT-MCP-) 
 arch: Skylake rev.9 cache: 3072 KB
 flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 15648
 clock speeds: max: 3900 MHz 1: 800 MHz 2: 800 MHz 3: 804 MHz
 4: 811 MHz
  Graphics:  Card: Intel HD Graphics 630 bus-ID: 00:02.0
 Display Server: x11 (X.Org 1.19.6 ) driver: i915
 Resolution: 1920x1080@60.00hz
 OpenGL: renderer: Mesa DRI Intel HD Graphics 630 (Kaby Lake GT2)
 version: 4.5 Mesa 17.3.3 Direct Render: Yes
  corrado@corrado-p9-bb-1221:~$ apt policy totem
  totem:
Installed: 3.26.0-0ubuntu3
Candidate: 3.26.0-0ubuntu3
Version table:
   *** 3.26.0-0ubuntu3 500
  500 http://archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status
  corrado@corrado-p9-bb-1221:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: libgstreamer1.0-0 1.12.4-1
  ProcVersionSignature: Ubuntu 4.15.0-9.10-generic 4.15.2
  Uname: Linux 4.15.0-9-generic x86_64
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 15:58:07 2018
  InstallationDate: Installed on 2017-12-23 (53 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221)
  SourcePackage: gstreamer1.0
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgLog: Error: [Errno 2] No such file or directory: '/var/log/Xorg.0.log'

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

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

[Touch-packages] [Bug 1316970] Re: g_dbus memory leak in lrmd

2018-02-14 Thread Sebastien Bacher

the glib change seems buggy, the upstream bug corresponding to the first
patch https://bugzilla.gnome.org/show_bug.cgi?id=758641 states that the
issue was in code commited in 2.45 or trusty has 2.40 so it seems wrong
to try to use it on that codebase (unsure about the other ones)

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

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

Title:
  g_dbus memory leak in lrmd

Status in glib2.0 package in Ubuntu:
  New
Status in pacemaker package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Trusty:
  New
Status in pacemaker source package in Trusty:
  In Progress

Bug description:
  [Impact]
  lrmd daemon with upstart resource has memory leak in Trusty

  affected to pacemaker 1.1.10.
  affected to glib2.0 2.40.2-0ubuntu1

  Please note that patch for pacemaker is created myself.

  [Test Case]

  1. deploy 3 trusty instance.
  2. install corosync, pacemaker, mysql.
  3. setting with below info
  3.1 corosync.conf, proper setting for 3 node
  3.2 crm configure < setup.crm ( which has upstart:mysql setting )
  3.3 monitor lrmd daemon's memory usage

  [Regression]
  Restarting daemon after upgrading this pkg will be needed. this patch added 
NULL check for several parts. prior commit[1] changed file structure. and This 
change makes user changes usage of upstart:mysql to lsb:mysql. So I added free 
function myself. This might affect to system.
  For glib2.0, commit [1] is critical, but [2],[3],[4] is needed for building 
it.

  [Others]

  Related commits.

  [1] commit a7b61e276120184c7586a3217ed3571a982f5017
  Author: Andrew Beekhof 
  Date:   Fri Aug 23 16:25:35 2013 +1000

  Refactor: attrd: Move to its own directory and create a stub for
  attrd-ng

  --
  $ git describe --contains a1a6922e43dfe80b23887a88401cbb93fe3645c0
  Pacemaker-1.1.11-rc3

  $ git describe --contains a7b61e276120184c7586a3217ed3571a982f5017
  Pacemaker-1.1.11-rc1~168

  $ rmadison pacemaker
   pacemaker | 1.1.10+git20130802-1ubuntu2   | trusty
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-security
   pacemaker | 1.1.10+git20130802-1ubuntu2.4 | trusty-updates

   pacemaker | 1.1.14-2ubuntu1   | xenial
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-security
   pacemaker | 1.1.14-2ubuntu1.3 | xenial-update
   pacemaker | 1.1.16-1ubuntu1   | zesty
   pacemaker | 1.1.16-1ubuntu1   | artful
   pacemaker | 1.1.18~rc3-1ubuntu1   | bionic
  --

  For glib
  [1] 
https://github.com/GNOME/glib/commit/db641e32920ee8b553ab6f2d318aafa156e4390c
  [2] 
https://github.com/GNOME/glib/commit/8792609e15394967cab526838b83f90acb401663
  [3] 
https://github.com/GNOME/glib/commit/ec02a1875f29ecb8e46c0d8c1403cd00a0b3a9e4
  [4] 
https://github.com/GNOME/glib/commit/f10b6550ff2ce55d06b92d6dc3e443fc007b2f7a

  [Original Description]

  I'm running Pacemaker 1.1.10+git20130802-1ubuntu1 on Ubuntu Saucy
  (13.10) and have encountered a memory leak in lrmd.

  The details of the bug are covered here in this thread
  (http://oss.clusterlabs.org/pipermail/pacemaker/2014-May/021689.html)
  but to summarise, the Pacemaker developers believe the leak is caused
  by the g_dbus API, the use of which was removed in Pacemaker 1.11.

  I've also attached the Valgrind output from the run that exposed the
  issue.

  Given that this issue affects production stability (a periodic restart
  of Pacemaker is required), will a version of 1.11 be released for
  Trusty? (I'm happy to upgrade the OS to Trusty to get it).

  If not, can you advise which version of the OS will be the first to
  take 1.11 please?

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

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

[Touch-packages] [Bug 1747744] Re: [regression] Video playback in totem is corrupted in X11

Packages landed now, and upgrade is ok (if purging previous shemgp ppa
first, in case of use)

mesa (18.0.0~rc4-1ubuntu1) bionic; urgency=medium

  * Merge with Debian experimental.
  * Stop using alternatives, not needed anymore with libglvnd.
  * patches: Mir patches updated.
  * dri3-reinstate-get_dri_screen-callback.diff: Fix a regression in
accelerated video playback. (LP: #1747744)
  * control: Add nvidia-304/340/384 to libegl-mesa0, libgles2-mesa and
libglx-mesa0 Breaks.

 -- Timo Aaltonen   Tue, 13 Feb 2018 17:56:35 +0200

** Changed in: mesa (Ubuntu)
   Status: Fix Committed => Fix Released

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

Title:
  [regression] Video playback in totem is corrupted in X11

Status in Mesa:
  In Progress
Status in mesa package in Ubuntu:
  Fix Released
Status in totem package in Ubuntu:
  Confirmed

Bug description:
  Test case
  Log inti xorg session
  Install gstreamer1.0-vaapi plugin
  Play a supported video (- h.264/avc in .mp4, .mkv or .mov  would suffice

  Expected: hardware decoded playback
  What happens: totally corrupted screen, see screenshots

  Does work ok in a wayland session

  $ vainfo
  libva info: VA-API version 1.0.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/i965_drv_video.so
  libva info: Found init function __vaDriverInit_1_0
  libva info: va_openDriver() returns 0
  vainfo: VA-API version: 1.0 (libva 2.0.0)
  vainfo: Driver version: Intel i965 driver for Intel(R) Haswell Mobile - 2.0.0
  vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple:   VAEntrypointVLD
VAProfileMPEG2Simple:   VAEntrypointEncSlice
VAProfileMPEG2Main  :   VAEntrypointVLD
VAProfileMPEG2Main  :   VAEntrypointEncSlice
VAProfileH264ConstrainedBaseline:   VAEntrypointVLD
VAProfileH264ConstrainedBaseline:   VAEntrypointEncSlice
VAProfileH264Main   :   VAEntrypointVLD
VAProfileH264Main   :   VAEntrypointEncSlice
VAProfileH264High   :   VAEntrypointVLD
VAProfileH264High   :   VAEntrypointEncSlice
VAProfileH264MultiviewHigh  :   VAEntrypointVLD
VAProfileH264MultiviewHigh  :   VAEntrypointEncSlice
VAProfileH264StereoHigh :   VAEntrypointVLD
VAProfileH264StereoHigh :   VAEntrypointEncSlice
VAProfileVC1Simple  :   VAEntrypointVLD
VAProfileVC1Main:   VAEntrypointVLD
VAProfileVC1Advanced:   VAEntrypointVLD
VAProfileNone   :   VAEntrypointVideoProc
VAProfileJPEGBaseline   :   VAEntrypointVLD

  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gstreamer1.0-vaapi 1.12.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  ApportVersion: 2.20.8-0ubuntu8
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Feb  6 14:43:57 2018
  InstallationDate: Installed on 2018-02-06 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180204)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer-vaapi
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Touch-packages] [Bug 108366] Re: Totem unable to add to playlist after selecting unreadable location

2018-02-14 Thread Sebastien Bacher

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

** Changed in: gtk
   Importance: Low => Unknown

** Changed in: gtk
   Status: Invalid => Unknown

** Changed in: gtk
 Remote watch: GNOME Bug Tracker #432904 => GNOME Bug Tracker #382479

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

Title:
  Totem unable to add to playlist after selecting unreadable location

Status in GTK+:
  Unknown
Status in Totem:
  Invalid
Status in gtk+2.0 package in Ubuntu:
  Triaged

Bug description:
  Binary package hint: totem

  When adding to the playlist using the sidebar interface, totem
  defaults to the directory of the last selected file when prompting for
  a new file.  When that directory is unreadable (e.g.
  http://www.gearwire.com/media/ (after adding
  http://www.gearwire.com/media/seymour-duncan-guitar-
  pickups-1-musikmesse.wmv by pasting into the location control in the
  last add)), totem presents the message "error accessing
  'http://www.gearwire.com/media': Access denied".  If this dialog is
  closed, totem is unable to add new files to the playlist (even when
  pasting the Location) until a readable base location (e.g. the home
  directory) is selected.

  In functional terms:

  Observed Behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Paste another location in the Location control
  10)  Click "Add" to add the location
  11)  Nothing happens (no UI changes (except button blink), no message, etc.

  Expected Behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Paste another location in the Location control
  10)  Click "Add" to add the location
  11)  Totem shows the new file in the playlist

  Alternate acceptable behaviour:
  1)  Totem is open, sidebar is open in Playlist mode
  2)  Click "+" to add a file
  3)  Paste a location in the Location control (public location given above)
  4)  Click "Add" to add the location
  5)  Add interface closes, Totem shows the new file in the playlist
  6)  Click "+" to add another file
  7)  Totem presents dialog with "error accessing 
'http://www.gearwire.com/media': Access denied"
  8)  Close dialog
  9)  Totem defauls to user home directory (or /media, or any known safe 
location)
  10)  Paste another location in the Location control
  11)  Click "Add" to add the location
  12)  Totem shows the new file in the playlist

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

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

[Touch-packages] [Bug 1661295] Re: [vmware] mir 0.26 failing with nested server in protobuf when bringing up NestedDisplay [CHECK failed: (index) >= (0)]

2018-02-14 Thread Gerry Boland

Problem is that the "real" KMS platform is unable to determine the
current mode when running on VMware, leaving the current_mode_index at
an invalid value of UINTMAX, which is being passed through to the nested
platform.

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

Title:
  [vmware] mir 0.26 failing with nested server in protobuf when bringing
  up NestedDisplay [CHECK failed: (index) >= (0)]

Status in Mir:
  New
Status in mir package in Ubuntu:
  New

Bug description:
  Setup:
  1. VMWare 12, with the following line added to ~/.vmware/preferences:
    mks.gl.allowBlacklistedDrivers = "TRUE"
  2. Created a VM with Xenial + Overlay PPA
  3. Installed unity8-desktop-session-mir, rebooted
  4. Tried to log in to a Unity8 session

  Problem: Unity8 fails to start, but is exiting cleanly as opposed to
  crashing. The following is all that is printed of the log:

  [2017-02-02:07:18:21.137] qtmir.screens: ScreensModel::ScreensModel
  [2017-02-02 07:18:21.143261] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:18:21.143413] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:18:21.144063] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  [2017-02-02:07:18:21.165] CHECK failed: (index) >= (0):
  initctl: No such variable: UNITY_MIR_SOCKET

  USC is coming up correctly however.

  If I try to launch miral-shell manually, I get similar error:

  MIR_SOCKET=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_PROMPT_FILE=1 
MIR_SERVER_HOST_SOCKET=/run/mir_socket 
MIR_SERVER_FILE=$XDG_RUNTIME_DIR/mir_socket MIR_SERVER_NAME=session-0 
miral-shell
  [2017-02-02 07:55:56.686669] mirplatform: Found graphics driver: mir:mesa-kms 
(version 0.26.0)
  [2017-02-02 07:55:56.687395] mirplatform: Found graphics driver: mir:mesa-x11 
(version 0.26.0)
  [2017-02-02 07:55:56.689036] mirserver: Starting
  [libprotobuf FATAL /usr/include/google/protobuf/repeated_field.h:885] CHECK 
failed: (index) >= (0):
  ERROR: Dynamic exception type: google::protobuf::FatalException
  std::exception::what: CHECK failed: (index) >= (0):

  I tried to grab a backtrace at the location of the last call to
  /usr/include/google/protobuf/repeated_field.h:885 which might print
  the error:

  http://pastebin.ubuntu.com/23911595/

  Thread 4 "MirServerThread" hit Breakpoint 1, 
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  8417  in 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc
  #0  
mir::protobuf::DisplayOutput::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804f7a0, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:8417
  #1  0x7fffeba5c3e8 in 
mir::protobuf::DisplayConfiguration::SerializeWithCachedSizes(google::protobuf::io::CodedOutputStream*)
 const (this=0x7fffd804b830, output=0x7fffe0848280) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/obj-x86_64-linux-gnu/src/protobuf/mir_protobuf.pb.cc:11436
  #2  0x7fffeb38a615 in 
google::protobuf::MessageLite::SerializeWithCachedSizesToArray(unsigned char*) 
const () from /usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.9
  #3  0x7fffed696798 in mir_blob_from_display_config () from 
/usr/lib/x86_64-linux-gnu/libmirclient.so.9
  #4  0x7fffed1d7ec6 in copy_config (conf=) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:44
  #5  __base_ctor  (other=warning: RTTI symbol not found for class 
'mir::graphics::nested::NestedDisplayConfiguration'
  ..., this=0x7fffd8047300) at 
/build/mir-Hd65rv/mir-0.26.0+16.04.20170126.3/src/server/graphics/nested/nested_display_configuration.cpp:61

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

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

[Touch-packages] [Bug 1749389] Please test proposed package

2018-02-14 Thread Chris J Arges

Hello ChristianEhrhardt, or anyone else affected,

Accepted ntp into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p10+dfsg-
5ubuntu3.2 in a few hours, and then in the -proposed repository.

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

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

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

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

Title:
  ntpdate lock apparmor deny

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Fix Committed
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no
     issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
  Note: to not be mislead, on xenial there is a remaining stdout appamor 
  issue which is bug 1670408

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
     changes poses a security risk so regression potential on it's own
     should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would
     e.g. no more be freed up or the action behind the locking would cause
     issues.

  [Other Info]

   * n/a

  On start/restart nto has an error in apparmor due to the locking it
  tries to avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

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

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

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

2018-02-14 Thread Chris J Arges

Hello ChristianEhrhardt, or anyone else affected,

Accepted ntp into artful-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p10+dfsg-
5ubuntu3.2 in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: ntp (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-artful

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1749389] Re: ntpdate lock apparmor deny

2018-02-14 Thread Chris J Arges

Hello ChristianEhrhardt, or anyone else affected,

Accepted ntp into xenial-proposed. The package will build now and be
available at https://launchpad.net/ubuntu/+source/ntp/1:4.2.8p4+dfsg-
3ubuntu5.8 in a few hours, and then in the -proposed repository.

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

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

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

** Changed in: ntp (Ubuntu Xenial)
   Status: In Progress => Fix Committed

** Tags added: verification-needed verification-needed-xenial

** Changed in: ntp (Ubuntu Artful)
   Status: In Progress => Fix Committed

** Tags added: verification-needed-artful

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

Title:
  ntpdate lock apparmor deny

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Fix Committed
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no
     issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
  Note: to not be mislead, on xenial there is a remaining stdout appamor 
  issue which is bug 1670408

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
     changes poses a security risk so regression potential on it's own
     should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would
     e.g. no more be freed up or the action behind the locking would cause
     issues.

  [Other Info]

   * n/a

  On start/restart nto has an error in apparmor due to the locking it
  tries to avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

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

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

[Touch-packages] [Bug 1616651] Re: gnome-shell assert failure: * Error in `/usr/bin/gnome-shell': free(): invalid pointer: 0x00000000082dcf30 * in g_strfreev() from g_themed_icon_finalize() from g

2018-02-14 Thread chris pollock

Gnome shell crashed while updating these packages:

Start-Date: 2018-02-14  08:14:44
Commandline: apt-get -y install libegl1-mesa libegl1-mesa-dev libgbm-dev 
libgbm1 libgl1-mesa-dev libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa 
libgles2-mesa libgles2-mesa-dev libosmesa6 libwayland-egl1-mesa libxatracker2 
mesa-common-dev mesa-vdpau-drivers
Upgrade: libgles2-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libegl1-mesa-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libglapi-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libglapi-mesa:i386 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), mesa-common-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libxatracker2:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libegl1-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgbm1:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libwayland-egl1-mesa:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgles2-mesa-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgl1-mesa-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgl1-mesa-dri:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgl1-mesa-dri:i386 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libosmesa6:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libosmesa6:i386 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgl1-mesa-glx:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgl1-mesa-glx:i386 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), libgbm-dev:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), mesa-vdpau-drivers:amd64 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1), mesa-vdpau-drivers:i386 (17.2.4-0ubuntu1~16.04.4, 
17.2.8-0ubuntu0~16.04.1)
End-Date: 2018-02-14  08:19:10

Here is a link to output of /var/log/syslog on PasteBin -
https://pastebin.com/q7qsWCKq

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

Title:
  gnome-shell assert failure: *** Error in `/usr/bin/gnome-shell':
  free(): invalid pointer: 0x082dcf30 *** in g_strfreev() from
  g_themed_icon_finalize() from g_object_unref() from
  desktop_entry_unref()

Status in libgweather:
  Fix Released
Status in Ubuntu GNOME:
  Fix Committed
Status in gnome-shell package in Ubuntu:
  Invalid
Status in libgweather package in Ubuntu:
  Fix Released
Status in libgweather source package in Zesty:
  In Progress

Bug description:
  
  [Impact] 
  Backport git patch that fixes memory corruption in libgweather that is 
causing gnome-shell to crash. This is particularly bad on wayland as it causes 
the user to lose their sessions

  I believe this should also fix bug 1688208 and potentially a couple of
  other high ranking crashes on errors.ubuntu.com. I have not however
  found reliable reproducers for those other bugs.

  [Test Case]
  After update of libgweather
  1. Ensure org.gnome.Weather.Application locations is not set (as per default 
setting)
  2. Disable Location Services
  3. gnome-shell should not crash

  [Regression Potential]
  Low, the patch merely fixes a refcounting bug. Given the high impact of this 
bug, this is an important fix.
   
  === original bug report 
  This happened while installing Xfce with Synaptic.

  chris@localhost:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  chris@localhost:~$ apt-cache policy gnome-shell
  gnome-shell:
    Installed: 3.18.5-0ubuntu0.1
    Candidate: 3.18.5-0ubuntu0.1
    Version table:
   *** 3.18.5-0ubuntu0.1 500
  500 http://us.archive.ubuntu.com/ubuntu xenial-updates/universe amd64 
Packages
  100 /var/lib/dpkg/status
   3.18.4-0ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/universe amd64 Packages

  ProblemType: CrashDistroRelease: Ubuntu 16.04
  Package: gnome-shell 3.18.5-0ubuntu0.1
  ProcVersionSignature: Ubuntu 4.4.0-34.53-generic 4.4.15
  Uname: Linux 4.4.0-34-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AssertionMessage: *** Error in `/usr/bin/gnome-shell': free(): invalid 
pointer: 0x082dcf30 ***
  CrashCounter: 1
  CurrentDesktop: GNOME
  Date: Wed Aug 24 16:21:37 2016
  DisplayManager: gdm3
  ExecutablePath: /usr/bin/gnome-shell
  InstallationDate: Installed on 2014-10-24 (670 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcCmdline: /usr/bin/gnome-shell
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  Signal: 6SourcePackage: gnome-shell
  StacktraceTop:
   __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7fabad1e06b0 "*** 
Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
   malloc_printerr (ar_ptr=, ptr=, 
str=0x7fabad1dd48f "free(): invalid

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

Bionic - ok
SRU Template - ok
Debdiff for X/T checked - ok
Tested A upload from ppa - ok.
(This issue in particular doesn't apply to Xenial, so dropping this task)

** No longer affects: ntp (Ubuntu Xenial)

** Changed in: ntp (Ubuntu Artful)
   Status: Triaged => In Progress

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1670408] Re: Missing apparmor rules cause tor to fail to start

** Changed in: ntp (Ubuntu)
   Importance: Undecided => High

** Summary changed:

- Missing apparmor rules cause tor to fail to start
+ apparmor base abstraction needs backport of rev 3658 to fix several denies 
(tor, ntp, ...)

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

Title:
  apparmor base abstraction needs backport of rev 3658 to fix several
  denies (tor, ntp, ...)

Status in apparmor package in Ubuntu:
  Fix Released
Status in ntp package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Invalid
Status in apparmor source package in Xenial:
  Triaged

Bug description:
  Using tor 0.2.9.9-1ubuntu1 with Linux 4.10.0-9-generic on Zesty, tor
  fails to start after installing the tor package. "systemctl status
  tor@default" reports:

  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Main process exited, 
code=killed, status=11/SEGV
  Mar 06 16:04:00 zesty systemd[1]: Failed to start Anonymizing overlay network 
for TCP.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Unit entered failed 
state.
  Mar 06 16:04:00 zesty systemd[1]: tor@default.service: Failed with result 
'signal'.

  There are two AppArmor denials in the kernel log:

  Mar  6 15:53:12 zesty-test kernel: [  102.699647] audit: type=1400
  audit(1488815592.268:35): apparmor="DENIED" operation="file_inherit"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/run/systemd/journal/stdout" pid=3520 comm="tor"
  requested_mask="wr" denied_mask="wr" fsuid=10 ouid=10

  Mar  6 15:53:12 zesty-test kernel: [  102.702418] audit: type=1400
  audit(1488815592.272:37): apparmor="DENIED" operation="file_mmap"
  namespace="root//lxd-zesty_" profile="system_tor"
  name="/usr/bin/tor" pid=3520 comm="tor" requested_mask="m"
  denied_mask="m" fsuid=10 ouid=10

  Workaround: add the following two lines to /etc/apparmor.d/system_tor:

  /usr/bin/tor m,
  /run/systemd/journal/stdout rw,

  I couldn't remember how to that that profile reloaded, so I rebooted,
  and after the reboot tor does start up successfully. "systemctl
  tor@default" reports it as running.

  I haven't checked to see if only one or other rule is actually
  required.

  Importance -> High since this bug makes the package unusable in its
  default configuration on Zesty. Since the AppArmor profile comes from
  Debian's 0.2.9.9-1, this should probably be fixed in Debian.

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

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

[Touch-packages] [Bug 1741227] Re: apparmor denial to several paths to binaries

fix in SRU queue (Artful) for review by the SRU Team

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

Title:
  apparmor denial to several paths to binaries

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to bin directories which the option parsing code 
 of ntp touches.

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r"

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
 changes poses a security risk so regression potential on it's own
 should be close to zero.

   * we discussed if this would be a security risk but came to the 
 conclusion that r-only should be ok (the same content anyone can grab 
 from the archive by installing the packages)

  [Other Info]

   * n/a

  Issue shows up (non fatal) as:
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/sbin/" pid=23933 comm="ntpd" requested_mask="r" 
denied_mask="r" fsuid=0 ouid=0
   apparmor="DENIED" operation="open" profile="/usr/sbin/ntpd" 
name="/usr/local/bin/" pid=23933 comm="ntpd" requested_mask="r" denied_mask="r" 
fsuid=0 ouid=0

  Since non crit this is mostyl about many of us being curious why it
  actually does do it :-)

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

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

[Touch-packages] [Bug 1749247] Re: Spurious SEGV running inside kvm

2018-02-14 Thread Howard Chu

Will try to come up with a minimal reproducer. Currently it takes
several hours to run the complete test, and a few hours before the SEGV
occurs. But the stack trace is always identical when it happens. In
multiple runs, it always succeeds on the host and always fails in the
VM.

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

Title:
  Spurious SEGV running inside kvm

Status in openldap package in Ubuntu:
  Confirmed
Status in qemu package in Ubuntu:
  Incomplete

Bug description:
  Running a continuous stream of operations against OpenLDAP slapd
  eventually causes a SEGV in liblber, in a segment of code that cannot
  fail:

   gdb /opt/symas/lib64/slapd CoreDump 
  GNU gdb (Ubuntu 7.11.1-0ubuntu1~16.5) 7.11.1
  Copyright (C) 2016 Free Software Foundation, Inc.
  License GPLv3+: GNU GPL version 3 or later 
  This is free software: you are free to change and redistribute it.
  There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
  and "show warranty" for details.
  This GDB was configured as "x86_64-linux-gnu".
  Type "show configuration" for configuration details.
  For bug reporting instructions, please see:
  .
  Find the GDB manual and other documentation resources online at:
  .
  For help, type "help".
  Type "apropos word" to search for commands related to "word"...
  Reading symbols from /opt/symas/lib64/slapd...done.
  [New LWP 5472]
  [New LWP 5468]
  [New LWP 5524]
  [New LWP 5471]
  [New LWP 5469]
  [New LWP 5507]
  [New LWP 5510]
  [New LWP 5470]
  [New LWP 5506]
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  Core was generated by `/opt/symas/lib64/slapd -u root -g root -h ldap:///'.
  Program terminated with signal SIGSEGV, Segmentation fault.
  #0  0x7f4e2c9f0160 in ber_dupbv_x (dst=0x196b268, src=0x7f25f8001070, 
ctx=0x0) at /home/build/git/sold-master/openldap/libraries/liblber/memory.c:513
  513 new->bv_val[src->bv_len] = '\0';
  [Current thread is 1 (Thread 0x7f260e242700 (LWP 5472))]
  (gdb) l 500
  495 if(( new = ber_memalloc_x( sizeof(struct berval), ctx 
)) == NULL ) {
  496 return NULL;
  497 }
  498 }
  499
  500 if ( src->bv_val == NULL ) {
  501 new->bv_val = NULL;
  502 new->bv_len = 0;
  503 return new;
  504 }
  (gdb) 
  505
  506 if(( new->bv_val = ber_memalloc_x( src->bv_len + 1, ctx )) == 
NULL ) {
  507 if ( !dst )
  508 ber_memfree_x( new, ctx );
  509 return NULL;
  510 }
  511
  512 AC_MEMCPY( new->bv_val, src->bv_val, src->bv_len );
  513 new->bv_val[src->bv_len] = '\0';
  514 new->bv_len = src->bv_len;
  (gdb) p *new
  $1 = {bv_len = 0, bv_val = 0x0}
  (gdb) p *src
  $2 = {bv_len = 36, bv_val = 0x7f268ccc7bee }
  (gdb) 

  
  At line 506 we allocate some memory and check for a failure (returning NULL) 
and leave the function at line 509 if there was a failure. The allocation is 
for 37 bytes of memory and a memcpy into that memory succeeds on line 512. The 
SEGV occurs at line 513 and the pointer that was just returned from the 
allocator is NULL at this point. There are no other active threads that could 
be stomping on memory, there's no stack overrun or any other misbehavior that 
can account for it. Also, the identical test sequence completes without 
incident when running on the host OS instead of under kvm.
  (The src->bv_val pointer points to valid data at the time of the crash; it's 
just residing in a mmap'd file and that mapping isn't preserved in the 
coredump. So ignore gdb's error there.)

  Something in kvm is writing zeroes over a field of memory after we
  already checked that it was non-zero.

  This is on 
  Linux anvil1 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 
x86_64 x86_64 x86_64 GNU/Linux

  Both the host and the guest VM are on identical OS revision.

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

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

[Touch-packages] [Bug 1749389] Re: ntpdate lock apparmor deny

fix in SRU queue (Atrful/Xenial) for review by the SRU Team

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

Title:
  ntpdate lock apparmor deny

Status in ntp package in Ubuntu:
  Fix Released
Status in ntp source package in Xenial:
  Fix Committed
Status in ntp source package in Artful:
  Fix Committed

Bug description:
  [Impact]

   * Apparmor denies access to lock it shares with ntpdate to ensure no
     issues due to concurrent access

  [Test Case]

   1. get a container of target release
   2. install ntp
  apt install ntp
   3. watch dmesg on container-host
  dmesg -w
   4. restart ntp in container
  systemctl restart ntp
   => see (or no more after fix) apparmor denie:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"
  Note: to not be mislead, on xenial there is a remaining stdout appamor 
  issue which is bug 1670408

  [Regression Potential]

   * we are only slightly opening up the apparmor profile, but none of the
     changes poses a security risk so regression potential on it's own
     should be close to zero.

   * There is a potential issue if the locking (that now can succeed) would
     e.g. no more be freed up or the action behind the locking would cause
     issues.

  [Other Info]

   * n/a

  On start/restart nto has an error in apparmor due to the locking it
  tries to avoid issues running concurrently with ntpdate.

  That looks like:
  apparmor="DENIED" operation="file_inherit" profile="/usr/sbin/ntpd" 
name="/run/lock/ntpdate" pid=30113 comm="ntpd" requested_mask="w" 
denied_mask="w"

  The rule we need is:
  /run/lock/ntpdate wk,

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

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

[Touch-packages] [Bug 1749389] Re: ntpdate lock apparmor deny