[Touch-packages] [Bug 1773921] Re: merge ntp 1:4.2.8p11+dfsg-1 for cosmic

2018-06-05 Thread Launchpad Bug Tracker
This bug was fixed in the package ntp - 1:4.2.8p11+dfsg-1ubuntu1

---
ntp (1:4.2.8p11+dfsg-1ubuntu1) cosmic; urgency=medium

  * Merge with Debian unstable (LP: #1773921). Remaining changes:
- d/ntp.conf, d/ntpdate.default: Change default server to ntp.ubuntu.com.
- Add PPS support (LP 1512980):
  + debian/README.Debian: Add a PPS section to the README.Debian
  + debian/ntp.conf: Add some PPS configuration examples from the offical
documentation.
- d/ntp.dhcp add support for parsing systemd networkd lease files LP 1717983
  * Dropped Changes (accepted in Debian)
- d/ntp-systemd-wrapper protect systemd service startup from concurrent
  ntpdate processes the same way it was protected on sysv-init (LP 1706818)
- debian/apparmor-profile: add attach_disconnected which is needed in some
  cases to let ntp report its log messages (LP 1727202).
- debian/apparmor-profile: avoid denies to to arg checks (LP 1741227)
- fix apparmor denial when checking for running ntpdate (LP 1749389)

ntp (1:4.2.8p11+dfsg-1) unstable; urgency=medium

  * New upstream version 4.2.8p11+dfsg (Closes: #851096)
- Refresh patches
- Drop ntpd-increase-stack-size included upstream
- CVE-2018-7185: Unauthenticated packet can reset authenticated
  interleaved association (LOW/MED)
- CVE-2018-7184: Interleaved symmetric mode cannot recover from bad state
  (LOW/MED)
- CVE-2018-7170 / CVE-2016-1549: Provide a way to prevent authenticated
  symmetric passive peering (LOW)
- CVE-2018-7183: decodearr() can write beyond its 'buf' limits (Medium)
- CVE-2018-7182: ctl_getitem(): buffer read overrun leads to undefined
  behavior and information leak (Info/Medium)
- CVE-2016-1549: Sybil vulnerability: ephemeral association attack
  (mitigated in 4.2.8p7)
  * convert dfsg.sh into mk-origtargz script
  * Run wrap-and-sort
  * Sync AppArmor profile changes from Ubuntu, including a fix for a
harmless AppArmor denial in /usr/local (Closes: #883022)
  * Don't chown in postinst recursively.
Thanks to Daniel Kahn Gillmor (Closes: #889488)
  * Build sntp against system libevent
  * Drop versioned build-deps already fulfilled by oldoldstable

ntp (1:4.2.8p10+dfsg-6) unstable; urgency=medium

  * Make sntp KoD path FHS-compliant.
Thanks to Aaron Smith (Closes: #863873)
  * Drop historic Breaks/Pre-Depends
  * Drop historic conffile handling from pre-jessie
  * Adjust ntpdate description stating that it is deprecated
  * Move Vcs-* to salsa
  * Bump Standards-Version to 4.1.3.0, no changes necessary
  * Cherry-pick patch from upstream to increase stack size.
Thanks to Frederic Endner-Dühr for testing (Closes: #887385)
  * Temporarily add ntpdate lock for systemd wrapper.
Thanks to Christian Ehrhardt (Closes: #874540)
  * Add note about AppArmor tunable in README.Debian (Closes: #883949)

 -- Christian Ehrhardt   Tue, 29 May
2018 10:34:11 +0200

** Changed in: ntp (Ubuntu)
   Status: In Progress => Fix Released

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

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

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

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

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

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

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

Title:
  merge ntp 1:4.2.8p11+dfsg-1 for cosmic

Status in ntp package in Ubuntu:
  Fix Released

Bug description:
  Debian has picked many of our Apparmor changes whcih simplifies Delta.
  Also the newer Upstream version is good to have.

  I have marked a few bugs to retest with this new build, but need the
  merge build first.

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

-- 
Mailing list: https://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 1717983] Re: replacement of isc-dhcp-client with with systemd-networkd for dhclient needs integration

2018-06-05 Thread Launchpad Bug Tracker
** Merge proposal linked:
   https://code.launchpad.net/~paelzer/ubuntu/+source/ntp/+git/ntp/+merge/347033

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

Title:
  replacement of isc-dhcp-client with with systemd-networkd for dhclient
  needs integration

Status in avahi package in Ubuntu:
  Invalid
Status in cloud-init package in Ubuntu:
  In Progress
Status in controlaula package in Ubuntu:
  Invalid
Status in ddclient package in Ubuntu:
  Triaged
Status in maas package in Ubuntu:
  Invalid
Status in madwimax package in Ubuntu:
  Triaged
Status in ntp package in Ubuntu:
  Fix Released
Status in openresolv package in Ubuntu:
  Won't Fix
Status in resolvconf package in Ubuntu:
  Won't Fix
Status in samba package in Ubuntu:
  Triaged
Status in sendmail package in Ubuntu:
  Invalid
Status in ubuntu-meta package in Ubuntu:
  Triaged

Bug description:
  dhclient has been used as the dhcp client in Ubuntu and debian for
  many years. Over time, many packages have integrated with dhclient.
  The list below is of packages that have declared a dependency and
  those that have shipped hooks to be invoked by dhclient.

  As we move to systemd-networkd these will have to be addressed.

  # ./get-rdeps isc-dhcp-client | sort -u
  breaks - initramfs-tools (initramfs-tools)
  depends - dracut (dracut-network)
  depends - isc-dhcp (isc-dhcp-client-ddns)
  depends - libguestfs (libguestfs0)
  depends - maas (python3-maas-provisioningserver)
  depends - netscript-2.4 (netscript-2.4)
  depends - network-manager (network-manager)
  depends - ubuntu-meta (ubuntu-minimal)
  depends - walinuxagent (walinuxagent)
  depends - whereami (whereami)
  depends - wicd (wicd-daemon)
  depends - wifi-radar (wifi-radar)
  enhances - resolvconf (resolvconf)
  recommends - avahi (avahi-autoipd)
  recommends - ifupdown (ifupdown)
  recommends - ifupdown2 (ifupdown2)
  recommends - madwimax (madwimax)

  $ apt-file search '/etc/dhcp/' | grep 'hooks.d/' | sed 's,:.*,,' | sort -u
  avahi-autoipd
  cloud-init
  controlaula
  ddclient
  isc-dhcp-client
  ntp
  ntpdate
  openresolv
  resolvconf
  samba-common
  sendmail-base
  systemd
  whereami

  Another possible integration point that is not likely listed in the package
  dependencies is reading of the leases file for additional information.
  As an example, Azure advertises the location of its http based metadata
  service as an option in a dhclient response.  cloud-init will read the
  lease files to find the correct address.

  Related bugs:
   * bug 1713803: replacement of resolvconf with systemd needs integration 

  
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: isc-dhcp-client 4.3.5-3ubuntu1
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.7-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Mon Sep 18 12:46:31 2017
  DhclientLeases:

  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-07-23 (788 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: isc-dhcp
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1712866] Re: icons from qt applications disappear after screen lock/sleep

2018-06-05 Thread Mihai
I can confirm this happening to me in 18.04 Bionic.
The icons disappear after lock/sleep.
Restarting with Alt+F2 + r makes them reappear.

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

Title:
  icons from qt applications disappear after screen lock/sleep

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Indicators of some Qt apps are not showing after unlocking the screen
  or shell restart.

  
  [Test case]

  - Login to 17.10
  - launch dropbox (if not already launched)
  - Launch telegram (snap version or without libappindicator support)
  - Observe icons in taskbar
  - Lock screen with Super+L
  - Unlock screen
  - Icons should still be there

  
  [Possible regressions]

  Icons that should be hidden could be visible instead

  The fix doesn't apply to snapped applications

  In the Ubuntu Xorg session, with the Ubuntu Appindicator extension
  enabled, the tray icons for QT apps (in my case, both owncloud-client
  from the Ubuntu repos and enpass, from their own repo) show up after
  first logging in. But once the screen has been left idle long enough
  to be put to sleep, and is then woken up (I don't actually have screen
  *lock* enabled, but it still goes comes back to the clock screen and a
  further gesture is needed to scroll that up to get the desktop), then
  the icons for those QT apps are gone. Non-QT apps (eg: in my case
  hexchat, from the ubuntu repos) remain.

  For a while and due to inattention it seemed more random than that,
  but I'm fairly sure now it's just the display sleep/wake thing that
  kills it.

  The applications are still running in the background (so for instance
  enpass is still available via the browser extension), and can be seen
  in the process list. It's just the icons that have disappeared. If I
  then kill those apps (from the commandline with 'kill [pid]' because
  there's no other interface to do it from) and relaunch them, they
  reappear back in the appindicator area.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 24 17:12:43 2017
  Dependencies:

  InstallationDate: Installed on 2017-07-30 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to artful on 2017-08-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+subscriptions

-- 
Mailing list: https://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 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

2018-06-05 Thread Suho Meso
Hi,

this package fixes our slapd replication bug.

we tested following version:

# dpkg -l | grep 'slapd\|libldap'
ii  libldap-2.4-2:amd64 2.4.42+dfsg-2ubuntu3.3  
   amd64OpenLDAP libraries
ii  slapd   2.4.42+dfsg-2ubuntu3.3  
   amd64OpenLDAP server (slapd)

Thanks!

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap:
  Fix Released
Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Concurrent SASL authentications could trigger a segfault. This was observed 
by the bug reporter during replication from a master to a slave, and can be 
reproduced with a test program.

  The fix is applied upstream, see comment #13.

  [Test Case]
  * Create a fresh xenial VM or container and login. Update the apt 
repositories:
  sudo apt update

  * Create a local directory and cd into it:
  mkdir test && cd test

  * Download the test attachments from this bug: Makefile, sasltest.c and 
testscript:
  wget 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript

  * Build with
$ apt install libsasl2-dev libldap2-dev
$ make

  * Execute the testscript with sudo once. It shall fail at the very end with a 
core dump:
  sudo sh ./testscript
  (...)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Export this var:
  export LDAPSASL_SECPROPS=none

  * Run the actual test script a few more times to confirm the crasH:
  $ ./sasltest
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Install the updated packages from proposed

  * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported:
  $ echo $LDAPSASL_SECPROPS
  none

  $ ./sasltest
  $

  This time the test completes without crashing.

  [Regression Potential]
  This is SASL authentication, and with kerberos nonetheless (in the case of 
the bug reporter). I suspect not many people deploy this due to its complexity. 
The ones that have such a setup, however, tend to know what they are doing, so 
if they say the problem is fixed for them, I believe it is.

  About this particular change, it's committed upstream and also in
  debian, and @rtandy was kind enough to provide a sample test script
  that exhibits the problem.

  [Other Info]
  Since the fix is applied upstream and in Debian, there shouldn't be 
additional surprises here.

  [Original description]

  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not occuring.

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $
   
buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" 

[Touch-packages] [Bug 1688575] Re: Segmentation fault on a slave slapd (sync replication with kerberos authentication)

2018-06-05 Thread Suho Meso
** Tags removed: verification-needed-xenial
** Tags added: verification-done-xenial

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

Title:
  Segmentation fault on a slave slapd (sync replication with kerberos
  authentication)

Status in openldap:
  Fix Released
Status in openldap package in Ubuntu:
  Fix Released
Status in openldap source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Concurrent SASL authentications could trigger a segfault. This was observed 
by the bug reporter during replication from a master to a slave, and can be 
reproduced with a test program.

  The fix is applied upstream, see comment #13.

  [Test Case]
  * Create a fresh xenial VM or container and login. Update the apt 
repositories:
  sudo apt update

  * Create a local directory and cd into it:
  mkdir test && cd test

  * Download the test attachments from this bug: Makefile, sasltest.c and 
testscript:
  wget 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139678/+files/Makefile
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139679/+files/sasltest.c
 
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1688575/+attachment/5139680/+files/testscript

  * Build with
$ apt install libsasl2-dev libldap2-dev
$ make

  * Execute the testscript with sudo once. It shall fail at the very end with a 
core dump:
  sudo sh ./testscript
  (...)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Export this var:
  export LDAPSASL_SECPROPS=none

  * Run the actual test script a few more times to confirm the crasH:
  $ ./sasltest
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  rc = -6 (Unknown authentication method)
  sasltest: sasltest.c:70: bind_thread: Assertion `rc == LDAP_SUCCESS' failed.
  Aborted (core dumped)

  * Install the updated packages from proposed

  * Run ./sasltest again. Make sure the LDAPSASL_SECPROPS var is still exported:
  $ echo $LDAPSASL_SECPROPS
  none

  $ ./sasltest
  $

  This time the test completes without crashing.

  [Regression Potential]
  This is SASL authentication, and with kerberos nonetheless (in the case of 
the bug reporter). I suspect not many people deploy this due to its complexity. 
The ones that have such a setup, however, tend to know what they are doing, so 
if they say the problem is fixed for them, I believe it is.

  About this particular change, it's committed upstream and also in
  debian, and @rtandy was kind enough to provide a sample test script
  that exhibits the problem.

  [Other Info]
  Since the fix is applied upstream and in Debian, there shouldn't be 
additional surprises here.

  [Original description]

  I have a slapd problem on a freshly installed 16.04 machine:

  slapd[17107]: segfault at 1a ip 7f3c12c79f55 sp 7f3c03c2d080
  error 4 in libsasl2.so.2.0.25[7f3c12c72000+19000]

  I'm using the server as Slave LDAP-Server and sync replication with kerberos 
authentication.
  The service either starts and runs successfully or it fails with segmentation 
fault or 100% CPU.
  Maybe an useful info, I'm replicating two databases. When I deactivate 
syncrepl for one of them (doesn't matter which one) the problem is not occuring.

  Linux xxx 4.4.0-75-generic #96-Ubuntu SMP Thu Apr 20 09:56:33 UTC 2017 x86_64 
x86_64 x86_64 GNU/Linux
  slapd 2.4.42+dfsg-2ubuntu3.1
  libsasl2-2:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules:amd64 2.1.26.dfsg1-14build1
  libsasl2-modules-gssapi-mit:amd64 2.1.26.dfsg1-14build1

  GDB debug:

  Starting program: /usr/sbin/slapd -h "ldap:/// ldaps:/// ldapi:///" -u 
openldap -g openldap -f /etc/ldap/slapd.conf -d 256
  [Thread debugging using libthread_db enabled]
  Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
  590c82ab @(#) $OpenLDAP: slapd  (Ubuntu) (May 11 2016 16:12:05) $
   
buildd@lgw01-10:/build/openldap-mF7Kfq/openldap-2.4.42+dfsg/debian/build/servers/slapd
  590c82ab slapd starting
  [New Thread 0x7f2e96b7b700 (LWP 42139)]
  [New Thread 0x7f2e9637a700 (LWP 42140)]
  [New Thread 0x7f2e95b79700 (LWP 42141)]
  [New Thread 0x7f2e95378700 (LWP 42142)]
  [New Thread 0x7f2e94b77700 (LWP 42143)]
  590c82ba slap_client_connect: URI=ldap://xxx ldap_sasl_interactive_bind_s 
failed (-6)
  590c82ba do_syncrepl: rid=132 rc -6 retrying (9 retries left)

  Thread 4 "slapd" received signal SIGSEGV, Segmentation fault.
  [Switching to Thread 0x7f2e95b79700 (LWP 42141)]
  0x7f2ea53035b5 in sasl_client_add_plugin () from 
/usr/lib/x86_64-linux-gnu/libsasl2.so.2

  (gdb) thr apply all bt

  Thread 6 (Thread 0x7f2e94b77700 (LWP 42143)):
  #0  

[Touch-packages] [Bug 992971] Re: libavformat53 Mismatching header version

2018-06-05 Thread ablaszczyk
Once a while...

libavformat version 58.5.100 (external)
Mismatching header version 56.40.101
libavformat file format detected.

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

Title:
  libavformat53 Mismatching header version

Status in libav package in Ubuntu:
  Opinion
Status in mplayer package in Ubuntu:
  Confirmed
Status in libav package in Arch Linux:
  New

Bug description:
  Version details should be in the auto-loaded Apport file.

  $ mplayer blah_blah.mov
  MPlayer svn r34540 (Ubuntu), built with gcc-4.6 (C) 2000-2012 MPlayer Team

  Playing blah_blah.mov.
  libavformat version 53.21.0 (external)
  Mismatching header version 53.19.0
  libavformat file format detected.
  [snip]

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libavformat53 4:0.8.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
  Uname: Linux 3.2.0-24-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Tue May  1 20:24:45 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Release amd64 
(20120425)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: libav
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1755863] Re: netbooting the bionic live CD over NFS goes straight to maintenance mode :

2018-06-05 Thread Woodrow Shen
"toram" option only affected desktop with casper.

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

Title:
  netbooting the bionic live CD over NFS goes straight to maintenance
  mode :

Status in casper package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  netbooting the bionic live CD[1] over NFS goes straight to maintenance
  mode :

  [1] http://cdimage.ubuntu.com/daily-live/current/

  # casper.log
  Begin: Adding live session user... ... dbus-daemon[568]: [session uid=999 
pid=568] Activating service name='org.gtk.vfs.Daemon' requested by ':1.0' 
(uid=999 pid=569 comm="" label="unconfined")
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Daemon'
  dbus-daemon[568]: [session uid=999 pid=568] Activating service 
name='org.gtk.vfs.Metadata' requested by ':1.0' (uid=999 pid=569 comm="" 
label="unconfined")
  fuse: device not found, try 'modprobe fuse' first
  dbus-daemon[568]: [session uid=999 pid=568] Successfully activated service 
'org.gtk.vfs.Metadata'

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270:
  g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)'
  failed

  (gvfsd-metadata:580): GUdev-CRITICAL **: 16:28:56.270: 
g_udev_device_has_property: assertion 'G_UDEV_IS_DEVICE (device)' failed
  A connection to the bus can't be made
  done.
  Begin: Setting up init... ... done.

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

-- 
Mailing list: https://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 1767795] Re: Error Message

2018-06-05 Thread Philipp Batram
[] Reloading apparmor configuration (via systemctl): 
apparmor.serviceapparmor.service is not active, cannot reload.
  failed!


Am 04.06.2018 um 23:35 schrieb Seth Arnold:
> Hrm, I thought the logged information would include status on which
> profile failed to start. Bummer.
>
> If you run:  sudo /etc/init.d/apparmor reload
> do you get any error messages there? Please paste the output here.
>
> Thanks
>

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

Title:
  Error Message

Status in apparmor package in Ubuntu:
  New

Bug description:
  By starting the system in the long list of terms it shows one FAILED.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-38.43~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-38-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Apr 29 14:34:52 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: No
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company Broadwell-U Integrated Graphics 
[103c:81ef]
  InstallationDate: Installed on 2017-07-31 (271 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 04f2:b52d Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 8087:0a2a Intel Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: HP HP 250 G5 Notebook PC
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-38-generic.efi.signed 
root=UUID=90f2bd5c-bf2f-4aa9-866a-dcaf60f182d2 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/27/2016
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.21
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 81EF
  dmi.board.vendor: HP
  dmi.board.version: 63.38
  dmi.chassis.type: 10
  dmi.chassis.vendor: HP
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.21:bd10/27/2016:svnHP:pnHP250G5NotebookPC:pvrType1ProductConfigId:rvnHP:rn81EF:rvr63.38:cvnHP:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5336AN G=N L=SMB B=HP S=250
  dmi.product.name: HP 250 G5 Notebook PC
  dmi.product.version: Type1ProductConfigId
  dmi.sys.vendor: HP
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sun Apr 29 13:38:51 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset
  --- 
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CurrentDesktop: MATE
  DistroRelease: Ubuntu 16.04
  InstallationDate: Installed on 2017-07-31 (307 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  Package: apparmor 2.10.95-0ubuntu2.9
  PackageArchitecture: amd64
  ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=90f2bd5c-bf2f-4aa9-866a-dcaf60f182d2 ro drm.debug=0xe plymouth:debug
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Syslog:
   
  Tags:  xenial
  Uname: Linux 4.13.0-43-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/apparmor/+bug/1767795/+subscriptions

-- 
Mailing list: https://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 1759961] Re: Update to 5.50 (mostly bug-fix release)

2018-06-05 Thread Daniel van Vugt
Sorry for the delay. I have updated the PPA to BlueZ version 5.50 today.
If nobody finds any problems then that will be proposed as the version
for cosmic.

https://launchpad.net/~bluetooth/+archive/ubuntu/bluez

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

Title:
  Update to 5.50 (mostly bug-fix release)

Status in bluez package in Ubuntu:
  In Progress

Bug description:
  From upstream:
  http://www.bluez.org/release-of-bluez-5-49/

  Release of BlueZ 5.49

  This is mostly a bug fix release, with fixes to features such as
  AVCTP, OBEX, GATT and Mesh. There are however some notable new
  features also, such as improved heartbeat management support in
  meshctl as well as a new experimental ConnectDevice D-Bus method on
  the Adapter interface, which can be used for quick device object
  creation for testing purpose or when information about the device has
  been received over some Out-of-Band channel.

  Upstream changelog:
  https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog

  ver 5.49:
Fix issue with configuring discoverable advertising flag.
Fix issue with bearer selection and single mode controllers.
Fix issue with Connect and ConnectProfile returning in progress.
Fix issue with missing Paired property change when not bonded.
Fix issue with storage for controllers without public address.
Fix issue with handling AVCTP disconnecting the channel queue.
Fix issue with not clearing connectable setting on power off.
Fix issue with creating multiple mgmt socket instances.
Fix issue with GATT server and BR/EDR only devices.
Fix issue with InterfaceAdded event ordering.
Add support for generic ConnectDevice method call.
Add support for Mesh heartbeat client functionality.

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

-- 
Mailing list: https://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 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Daniel van Vugt
** Also affects: mesa (Ubuntu)
   Importance: Undecided
   Status: New

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

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC 
Controller (rev 05)
Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC 
Controller
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family 6 port SATA 

[Touch-packages] [Bug 1774962] Re: frequent hanging

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  frequent hanging

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  frequent hanging and slow download speed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Mon Jun  4 14:42:17 2018
  DistUpgraded: 2018-03-14 21:54:16,375 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   ndiswrapper, 1.60, 3.13.0-143-generic, x86_64: installed
   ndiswrapper, 1.60, 4.4.0-124-generic, x86_64: installed
   ndiswrapper, 1.60, 4.4.0-127-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd 82945G/GZ Integrated Graphics 
Controller [1458:d000]
  InstallationDate: Installed on 2016-06-29 (704 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Gigabyte Technology Co., Ltd. 945GCM-S2L
  ProcEnviron:
   LANGUAGE=en_IN:en
   PATH=(custom, no user)
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=da9a2669-c301-4637-9543-3c60bae76695 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: Upgraded to xenial on 2018-03-14 (81 days ago)
  dmi.bios.date: 12/27/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: F5
  dmi.board.name: 945GCM-S2L
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd12/27/2007:svnGigabyteTechnologyCo.,Ltd.:pn945GCM-S2L:pvr:rvnGigabyteTechnologyCo.,Ltd.:rn945GCM-S2L:rvr:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr:
  dmi.product.name: 945GCM-S2L
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Mon Jun  4 13:04:17 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputUSB Optical MouseMOUSE, id 8
   inputAT Translated Set 2 keyboard KEYBOARD, id 9
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id 739 
   vendor SAM
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://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 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Tracy
I don't see any changes in vainfo from before the change to the BIOS to
after. I have posted both versions here, in case I missed something.

I haven't yet tried removing the mesa drivers or the i965 driver - I
will try that later today, as time permits.

vainfo from before any changes (as posted under the "call for testing")

tracy@tracy-hp:~$ vainfo
libva info: VA-API version 1.1.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_1
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.1 (libva 2.1.0)
vainfo: Driver version: Intel i965 driver for Intel® Sandybridge Mobile - 2.1.0
vainfo: Supported profile and entrypoints
VAProfileMPEG2Simple : VAEntrypointVLD
VAProfileMPEG2Main : VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointVLD
VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
VAProfileH264Main : VAEntrypointVLD
VAProfileH264Main : VAEntrypointEncSlice
VAProfileH264High : VAEntrypointVLD
VAProfileH264High : VAEntrypointEncSlice
VAProfileH264StereoHigh : VAEntrypointVLD
VAProfileVC1Simple : VAEntrypointVLD
VAProfileVC1Main : VAEntrypointVLD
VAProfileVC1Advanced : VAEntrypointVLD
VAProfileNone : VAEntrypointVideoProc

vainfo after changing BIOS setting:

tracy@tracy-hp:~$ vainfo
libva info: VA-API version 1.1.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_1
libva info: va_openDriver() returns 0
vainfo: VA-API version: 1.1 (libva 2.1.0)
vainfo: Driver version: Intel i965 driver for Intel(R) Sandybridge Mobile - 
2.1.0
vainfo: Supported profile and entrypoints
  VAProfileMPEG2Simple: VAEntrypointVLD
  VAProfileMPEG2Main  : VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointVLD
  VAProfileH264ConstrainedBaseline: VAEntrypointEncSlice
  VAProfileH264Main   : VAEntrypointVLD
  VAProfileH264Main   : VAEntrypointEncSlice
  VAProfileH264High   : VAEntrypointVLD
  VAProfileH264High   : VAEntrypointEncSlice
  VAProfileH264StereoHigh : VAEntrypointVLD
  VAProfileVC1Simple  : VAEntrypointVLD
  VAProfileVC1Main: VAEntrypointVLD
  VAProfileVC1Advanced: VAEntrypointVLD
  VAProfileNone   : VAEntrypointVideoProc

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)

[Touch-packages] [Bug 1774170] Re: Applications block on eglswapBuffers due to buggy mesa version

2018-06-05 Thread Mohamed Sharaf-El-Deen
Problem is fixed. Thanks for your support.
Tested mesa package version: 18.0.5-0ubuntu0~18.04.1

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

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

Title:
  Applications block on eglswapBuffers due to buggy mesa version

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Bionic:
  Fix Committed

Bug description:
  [Impact]
  The mesa version that is available after installing packages has a bug that 
leads to wayland applications blocking on eglSwapBuffers if egl swap interval 
is set to Zero.

  Ubuntu version: 18.04 LTS
  Currently available mesa version for installation: 18.0.0~rc5

  Versions where the bug is fixed:
  17.3.8, 18.0.2, 18.1.0, or later

  [Test case]
  More details about the bug, how to reproduce it and the right mesa versions 
to use in here:
  https://bugs.freedesktop.org/show_bug.cgi?id=106719

  Would be so good if it is possible to provide one of the mesa versions
  where the problem does not exist as a package for installation.

  Thanks

  Output from running:
  apt-cache policy libegl-mesa0

  libegl-mesa0:
    Installed: 18.0.0~rc5-1ubuntu1
    Candidate: 18.0.0~rc5-1ubuntu1
    Version table:
   *** 18.0.0~rc5-1ubuntu1 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  [Regression potential]
  none known, and we're SRUing 18.0.5 which is the last one of the series so 
shouldn't have regressions caused by earlier bugfixes..

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

-- 
Mailing list: https://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 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Daniel van Vugt
Ah! Your kernel log mentions the AMD video decoder here:

[ 1223.799908] [drm] UVD initialized successfully.

So it's possible that's the cause of the main problem. Can you please
reintroduce the bug and run 'vainfo'? Does 'vainfo' report different
information after you switch your BIOS?

If that is the problem then the workaround should be:

  sudo apt remove mesa-va-drivers

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC 
Controller (rev 05)
  

[Touch-packages] [Bug 1770321] Re: help

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  help

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  me

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 10 11:16:32 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Acer Incorporated [ALI] Skylake GT2 [HD Graphics 520] 
[1025:110f]
  InstallationDate: Installed on 2018-05-09 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 04f2:b573 Chicony Electronics Co., Ltd 
   Bus 001 Device 002: ID 04ca:3015 Lite-On Technology Corp. 
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Acer Aspire E5-475
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=65ab738c-e1f4-4212-91c7-fc8d3d4df889 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/29/2016
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: AntMan_SK
  dmi.board.vendor: Acer
  dmi.board.version: V1.01
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01:bd03/29/2016:svnAcer:pnAspireE5-475:pvrV1.01:rvnAcer:rnAntMan_SK:rvrV1.01:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.family: SKL
  dmi.product.name: Aspire E5-475
  dmi.product.version: V1.01
  dmi.sys.vendor: Acer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://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 1770092] Re: error

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  error

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  when I downloading apps some errors and when working OS working so
  slowy

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May  9 15:43:57 2018
  DistUpgraded: 2018-05-02 06:58:57,163 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   virtualbox, 5.2.10, 4.13.0-39-generic, x86_64: installed
   virtualbox, 5.2.10, 4.15.0-20-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GconfCompiz:
   /apps/compiz-1/general:
 /apps/compiz-1/general/screen0:
  /apps/compiz-1/general/screen0/options:
   active_plugins = 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus]
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Samsung Electronics Co Ltd 3rd Gen Core processor Graphics 
Controller [144d:c652]
   NVIDIA Corporation GF119M [GeForce 610M] [10de:1058] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Samsung Electronics Co Ltd GF119M [GeForce 610M] [144d:c652]
  InstallationDate: Installed on 2017-01-31 (462 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: SAMSUNG ELECTRONICS CO., LTD. 300E4C/300E5C/300E7C
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=e8f1d7ee-2740-4158-977c-6250f43f5995 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-01 (7 days ago)
  dmi.bios.date: 02/20/2013
  dmi.bios.vendor: Phoenix Technologies Ltd.
  dmi.bios.version: P07RAC
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: SAMSUNG_NP1234567890
  dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.board.version: FAB1
  dmi.chassis.asset.tag: Asset Tag
  dmi.chassis.type: 9
  dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
  dmi.chassis.version: 0.1
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLtd.:bvrP07RAC:bd02/20/2013:svnSAMSUNGELECTRONICSCO.,LTD.:pn300E4C/300E5C/300E7C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnSAMSUNG_NP1234567890:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1:
  dmi.product.family: ChiefRiver System
  dmi.product.name: 300E4C/300E5C/300E7C
  dmi.product.version: 0.1
  dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Tue Apr 10 08:59:09 2018
  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.
  

[Touch-packages] [Bug 1771628] Re: Grpahic Drivers

2018-06-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1766137 ***
https://bugs.launchpad.net/bugs/1766137

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


** This bug has been marked a duplicate of bug 1766137
   [regression] Password accepted but login fails (blank purple screen and 
mouse pointer only)

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

Title:
  Grpahic Drivers

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Hi,

  I'm getting a purple blank screen after putting my creadentials when
  the computer is starting.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 16 19:05:08 2018
  DistUpgraded: 2018-05-16 16:54:13,314 DEBUG icon theme changed, re-reading
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation HD Graphics 520 [8086:1916] (rev 07) (prog-if 00 [VGA 
controller])
 Subsystem: Dell Skylake GT2 [HD Graphics 520] [1028:0704]
  InstallationDate: Installed on 2016-11-01 (560 days ago)
  InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 003: ID 0c45:670c Microdia 
   Bus 001 Device 002: ID 0a5c:6412 Broadcom Corp. 
   Bus 001 Device 004: ID 0781:5567 SanDisk Corp. Cruzer Blade
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: Dell Inc. XPS 13 9350
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=it_IT.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=247af43d-40d7-48c1-8502-e54796f36b07 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-16 (0 days ago)
  dmi.bios.date: 06/14/2016
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.4.4
  dmi.board.vendor: Dell Inc.
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.4.4:bd06/14/2016:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://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 1774979] Re: no input and output devices detected in sound definitions

2018-06-05 Thread Paulo Jorge Costa Ricardo Barroso
I wanna thank you for the time you spent with this.

What I did was a fresh install of the Ubuntu because I needed the laptop
urgently. Everything went back to normal.

Thank you once again for your support. I want to say that I' m very pleased
with Ubuntu.

A Ter, 5/06/2018, 03:11, Daniel van Vugt 
escreveu:

> When experiencing the problem please also run:
>
>   ps auxw | grep pulse
>
> and send us the output.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1774979
>
> Title:
>   no input and output devices detected in sound definitions
>
> Status in pulseaudio package in Ubuntu:
>   Incomplete
>
> Bug description:
>   After installing pulse audio equalizer, it worked good. everything was
>   detected in Sound Definitions and there was sound in the headphone
>   out.
>
>   In the day after, every input and output devices were gone in Sound
>   Definition. I uninstalled pulse audio equalizer but nothing happened
>   in Sound Definitions, everything was gone.
>
>   I rebooted the system and nothing. No sound.
>
>   ProblemType: Bug
>   DistroRelease: Ubuntu 16.04
>   Package: pulseaudio 1:8.0-0ubuntu3.10
>   ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
>   Uname: Linux 4.13.0-43-generic i686
>   ApportVersion: 2.20.1-0ubuntu2.18
>   Architecture: i386
>   AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path',
> '/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c',
> '/dev/snd/pcmC0D6p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c',
> '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/seq',
> '/dev/snd/timer'] failed with exit code 1:
>   CurrentDesktop: Unity
>   Date: Mon Jun  4 12:35:32 2018
>   InstallationDate: Installed on 2018-01-04 (150 days ago)
>   InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386
> (20170801)
>   ProcEnviron:
>LANGUAGE=pt:pt_BR:en
>PATH=(custom, no user)
>XDG_RUNTIME_DIR=
>LANG=pt_PT.UTF-8
>SHELL=/bin/bash
>   PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No
> PulseAudio daemon running, or not running as session daemon.
>   SourcePackage: pulseaudio
>   Symptom: audio
>   UpgradeStatus: No upgrade log present (probably fresh install)
>   dmi.bios.date: 05/15/2006
>   dmi.bios.vendor: American Megatrends Inc.
>   dmi.bios.version: A6FAS.212
>   dmi.board.asset.tag: To Be Filled By O.E.M.
>   dmi.board.name: A6F
>   dmi.board.vendor: ASUSTeK Computer Inc.
>   dmi.board.version: 1.0
>   dmi.chassis.type: 10
>   dmi.chassis.vendor: ASUSTeK Computer Inc.
>   dmi.modalias:
> dmi:bvnAmericanMegatrendsInc.:bvrA6FAS.212:bd05/15/2006:svnASUSTeKComputerInc.:pnA6F:pvr1.0:rvnASUSTeKComputerInc.:rnA6F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
>   dmi.product.family: To Be Filled By O.E.M.
>   dmi.product.name: A6F
>   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/pulseaudio/+bug/1774979/+subscriptions
>

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

Title:
  no input and output devices detected in sound definitions

Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  After installing pulse audio equalizer, it worked good. everything was
  detected in Sound Definitions and there was sound in the headphone
  out.

  In the day after, every input and output devices were gone in Sound
  Definition. I uninstalled pulse audio equalizer but nothing happened
  in Sound Definitions, everything was gone.

  I rebooted the system and nothing. No sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.10
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun  4 12:35:32 2018
  InstallationDate: Installed on 2018-01-04 (150 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A6FAS.212
  

[Touch-packages] [Bug 1768232] Re: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing

2018-06-05 Thread d a i s y
Shane Semanek

I've tried disabling Wayland in GDM3.

sudo vi /etc/gdm3/custom.conf

Change #WaylandEnable=false to WaylandEnable=false and reboot

It worked !

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

Title:
  [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while
  booting after installing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My system stuck at ubuntu logo while booting. This issue occurred only
  after installing it, not when I choose 'Try without Installing'. This
  doesn't happen in 16.04.4.

  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  WORKAROUND: Using the following kernel boot parameter allows me to boot but 
the maximum resolution is limited to 1024x768:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://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 1768232] Re: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing

2018-06-05 Thread d a i s y
Christopher M. Penalver

1. I've tried debugging kernel boot option other than nomodeset but it did not 
work, it shows started all the services and then pause there, no process after 
then.
2. I've installed kernel 4.16 and 4.17 but it also didn't work and I have to 
boot up with nomodeset option.

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

Title:
  [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while
  booting after installing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My system stuck at ubuntu logo while booting. This issue occurred only
  after installing it, not when I choose 'Try without Installing'. This
  doesn't happen in 16.04.4.

  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  WORKAROUND: Using the following kernel boot parameter allows me to boot but 
the maximum resolution is limited to 1024x768:
  nomodeset

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://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 1774462] Re: nividi drivers

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  nividi drivers

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  nvidia drivers fuck up total bullshit noting woks in laptop that was
  purchestwit ubunt 14.04 simple sudo apt full-upgrade distrosit

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  NonfreeKernelModules: bbswitch nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  396.24  Thu Apr 26 00:10:09 
PDT 2018
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.4)
  ApportVersion: 2.14.1-0ubuntu3.28
  Architecture: amd64
  Date: Thu May 31 19:04:47 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06ae]
 Subsystem: Dell Device [1028:06ae]
  InstallationDate: Installed on 2015-07-22 (1044 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5558
  ProcEnviron:
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=704f2fc5-97f6-46db-8498-c4dc3400a4e2 ro drm.debug=0xe plymouth:debug 
quiet splash radeon.modeset=0 nouveau.modeset=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 086DKN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/14/2015:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn086DKN:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Thu May 31 18:58:57 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.devices:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.15.1-0ubuntu2.11

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

-- 
Mailing list: https://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 1774204] Re: asdf

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  asdf

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  adsf

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Wed May 30 08:41:14 2018
  DistUpgraded: 2018-05-21 13:20:06,969 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process 
“./xorg_fix_proprietary.py” (No such file or directory) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   amdgpu, 18.20-579836, 4.15.0-20-generic, x86_64: installed
   amdgpu, 18.20-579836, 4.15.0-22-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-20-generic, x86_64: installed
   bcmwl, 6.30.223.271+bdcom, 4.15.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Dell 4th Gen Core Processor Integrated Graphics Controller 
[1028:05cc]
   Advanced Micro Devices, Inc. [AMD/ATI] Venus XT [Radeon HD 8870M / R9 
M270X/M370X] [1002:6821] (prog-if 00 [VGA controller])
 Subsystem: Dell FirePro M5100 [1028:05cc]
  InstallationDate: Installed on 2018-05-21 (8 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20180105.1)
  MachineType: Dell Inc. Precision M4800
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=ffa4c69d-899f-4e51-ae7e-bae9d551b398 ro quiet splash vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-21 (8 days ago)
  dmi.bios.date: 05/19/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A14
  dmi.board.name: 0V5GVY
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA14:bd05/19/2015:svnDellInc.:pnPrecisionM4800:pvr01:rvnDellInc.:rn0V5GVY:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Precision M4800
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://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 1774860] Re: Dudnt work mane

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  Dudnt work mane

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  whatever it is I am sure it is something I have done to it in the last
  24 hrs. It was working without glitch es until I started into it. I
  had hoped for more with adding the card. I am not sure If the gpu with
  the intel chip wasn't doing better or if I can turn it off somehow.
  The firmware with the ATI is not what I had hoped either. I would like
  for everything to not lcok up or cause something else to not quite
  work right such as the mouse or just trying to navigate or scroll a
  window. I am sure I have to many things running sometimes and I am
  still getting the hang of just how the structure works with it all.
  For example this go around and there have been several in the last 9
  months, all with a smile though. Installed several packages with
  several different methods such appimaage, snapd, flatpack, git, built
  them from source code, etc... and The appimages are just frustrating
  sometimes depending on wether I built them, used ocs-url, open desktop
  , or the new one can't remember, it put them every where and then they
  just wern't recoginized by  something else, so then there were 2, and
  sometimes Root, User, and usr all had there own but no one had
  everything and of course it is just My best friends ME, myself, and I
  that are using this machine. All in All hve put 10 different versions
  of linux and windows on this machine all in a multiboot working
  correctly twice now. There is however not a really reason to have
  asmany now. It has all been to learn, and use something I had not
  before and see which ones did what. I think i should have started with
  the structure of the basic kernel and worked my way up, but it does
  appear sometimes different distros still put what they want where they
  want, also. Hope you are havung a day with just enough stress to cause
  you to learn something new and share it with someone else someday.
  Thank you for your time in reading not only this, but what I am sure
  is so so so many other reports.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Sun Jun  3 04:35:51 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Subsystem: Dell Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller 
[1028:0581]
   Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 
230 OEM] [1002:6779] (prog-if 00 [VGA controller])
 Subsystem: XFX Pine Group Inc. Caicos [Radeon HD 6450/7450/8450 / R5 230 
OEM] [1682:5230]
  InstallationDate: Installed on 2018-05-05 (28 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Release amd64 
(20180426)
  MachineType: Dell Inc. Inspiron 660
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: \\boot\vmlinuz-4.15.0-22-generic ro 
root=UUID=2aa28c28-b34b-4409-bd58-293233105d72 
initrd=boot\initrd.img-4.15.0-22-generic
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 03/20/2018
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A12
  dmi.board.name: 0XR1GT
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 3
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA12:bd03/20/2018:svnDellInc.:pnInspiron660:pvr:rvnDellInc.:rn0XR1GT:rvrA00:cvnDellInc.:ct3:cvr:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: Inspiron 660
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  

[Touch-packages] [Bug 1712866] Re: icons from qt applications disappear after screen lock/sleep

2018-06-05 Thread Rachel Greenham
FWIW I have *not* seen this since upgrading to Bionic. It was probably
fixed sooner, when they said it was, but at some point I gave up on
Artful because of various gnome-shell problems including this, went back
to Mac, and tried again with a fresh Bionic install, where they almost
all seem to have been fixed.

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

Title:
  icons from qt applications disappear after screen lock/sleep

Status in gnome-shell-extension-appindicator package in Ubuntu:
  Fix Released
Status in qtbase-opensource-src package in Ubuntu:
  Fix Released
Status in gnome-shell-extension-appindicator source package in Artful:
  Fix Released

Bug description:
  [Impact]

  Indicators of some Qt apps are not showing after unlocking the screen
  or shell restart.

  
  [Test case]

  - Login to 17.10
  - launch dropbox (if not already launched)
  - Launch telegram (snap version or without libappindicator support)
  - Observe icons in taskbar
  - Lock screen with Super+L
  - Unlock screen
  - Icons should still be there

  
  [Possible regressions]

  Icons that should be hidden could be visible instead

  The fix doesn't apply to snapped applications

  In the Ubuntu Xorg session, with the Ubuntu Appindicator extension
  enabled, the tray icons for QT apps (in my case, both owncloud-client
  from the Ubuntu repos and enpass, from their own repo) show up after
  first logging in. But once the screen has been left idle long enough
  to be put to sleep, and is then woken up (I don't actually have screen
  *lock* enabled, but it still goes comes back to the clock screen and a
  further gesture is needed to scroll that up to get the desktop), then
  the icons for those QT apps are gone. Non-QT apps (eg: in my case
  hexchat, from the ubuntu repos) remain.

  For a while and due to inattention it seemed more random than that,
  but I'm fairly sure now it's just the display sleep/wake thing that
  kills it.

  The applications are still running in the background (so for instance
  enpass is still available via the browser extension), and can be seen
  in the process list. It's just the icons that have disappeared. If I
  then kill those apps (from the commandline with 'kill [pid]' because
  there's no other interface to do it from) and relaunch them, they
  reappear back in the appindicator area.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-shell-extension-appindicator 17.10
  ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
  Uname: Linux 4.12.0-11-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.6-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Thu Aug 24 17:12:43 2017
  Dependencies:

  InstallationDate: Installed on 2017-07-30 (24 days ago)
  InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: gnome-shell-extension-appindicator
  UpgradeStatus: Upgraded to artful on 2017-08-22 (2 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-appindicator/+bug/1712866/+subscriptions

-- 
Mailing list: https://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 1774450] Re: bug

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  bug

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  look at summary

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..22.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/proc/driver/nvidia/gpus/:22:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.48  Thu Mar 22 00:42:57 
PDT 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 31 17:55:44 2018
  DistUpgraded: 2018-05-11 18:46:23,230 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (g-exec-error-quark: Kindprozess 
»./xorg_fix_proprietary.py« konnte nicht ausgeführt werden (Datei oder 
Verzeichnis nicht gefunden) (8))
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia, 390.48, 4.15.0-22-generic, x86_64: installed
   nvidia, 390.48, 4.15.0-23-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: ASUSTeK Computer Inc. GK106 [GeForce GTX 660] [1043:8422]
  InstallationDate: Installed on 2018-02-22 (97 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  MachineType: System manufacturer System Product Name
  ProcEnviron:
   PATH=(custom, no user)
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-23-generic 
root=UUID=3487a6bb-a3c6-47ed-93c6-4c469f004ca6 ro drm.debug=0xe plymouth:debug
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-05-11 (19 days ago)
  dmi.bios.date: 03/20/2017
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 0513
  dmi.board.asset.tag: Default string
  dmi.board.name: PRIME B350-PLUS
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: Rev X.0x
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: Default string
  dmi.chassis.version: Default string
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr0513:bd03/20/2017:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEB350-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May 31 17:52:56 2018
  xserver.configfile: default
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   
  xserver.version: 2:1.19.6-1ubuntu4

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

-- 
Mailing list: https://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 1774640] syslog.txt

2018-06-05 Thread SpiderQED
apport information

** Attachment added: "syslog.txt"
   https://bugs.launchpad.net/bugs/1774640/+attachment/5148901/+files/syslog.txt

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774751] Re: mouse

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  mouse

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  my mouse is malfunctioning

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  Date: Sat Jun  2 01:09:52 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 4th Gen Core Processor Integrated Graphics Controller 
[8086:0416] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 4th Gen Core Processor Integrated 
Graphics Controller [103c:1962]
  InstallationDate: Installed on 2018-04-18 (44 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  MachineType: Hewlett-Packard HP ENVY 15 Notebook PC
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-43-generic.efi.signed 
root=UUID=8f0b1c00-fce6-4eb9-af73-8b962be4d947 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/22/2015
  dmi.bios.vendor: Insyde
  dmi.bios.version: F.66
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: 1962
  dmi.board.vendor: Hewlett-Packard
  dmi.board.version: KBC Version 93.52
  dmi.chassis.asset.tag: 5CG414D6R1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Hewlett-Packard
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY15NotebookPC:pvr098211405E032:rvnHewlett-Packard:rn1962:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion:
  dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV
  dmi.product.name: HP ENVY 15 Notebook PC
  dmi.product.version: 098211405E032
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.83-1~16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 17.2.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.xserver-xorg-core: xserver-xorg-core N/A
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A
  version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A
  xserver.bootTime: Sat Jun  2 01:05:34 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.5-0ubuntu2~16.04.1
  xserver.video_driver: modeset

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

-- 
Mailing list: https://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 1774657] Re: I945G don't load

2018-06-05 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => xorg-server (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/1774657

Title:
  I945G don't load

Status in xorg-server package in Ubuntu:
  New

Bug description:
  After upgrade, the video card not load properly

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18
  Uname: Linux 4.15.0-23-generic i686
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  Date: Thu May 31 17:11:21 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
 Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:3011]
  MachineType: Hewlett-Packard HP Compaq dc7600 Small Form Factor
  ProcEnviron:
   LANGUAGE=es_ES:en
   PATH=(custom, no user)
   LANG=es_ES.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-23-generic 
root=UUID=a9e49865-59bc-44ce-818f-6b5b2e1c89fe ro quiet splash drm.debug=0xe 
nomodeset
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2005
  dmi.bios.vendor: Hewlett-Packard
  dmi.bios.version: 786D1 v01.03
  dmi.board.name: 09F8h
  dmi.board.vendor: Hewlett-Packard
  dmi.chassis.asset.tag: Thor
  dmi.chassis.type: 4
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnHewlett-Packard:bvr786D1v01.03:bd05/18/2005:svnHewlett-Packard:pnHPCompaqdc7600SmallFormFactor:pvr:rvnHewlett-Packard:rn09F8h:rvr:cvnHewlett-Packard:ct4:cvr:
  dmi.product.family: 103C_53307F
  dmi.product.name: HP Compaq dc7600 Small Form Factor
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.4-0ubuntu0~18.04.1~ppa1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.4-0ubuntu0~18.04.1~ppa1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Thu May 31 16:13:00 2018
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputAT Translated Set 2 keyboard KEYBOARD, id 8
   inputImPS/2 Logitech Wheel Mouse MOUSE, id 9
   inputHP WMI hotkeys   KEYBOARD, id 10
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.19.6-1ubuntu4

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

-- 
Mailing list: https://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 1774640] ProcCpuinfo.txt

2018-06-05 Thread SpiderQED
apport information

** Attachment added: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/bugs/1774640/+attachment/5148893/+files/ProcCpuinfo.txt

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774640] rfkill.txt

2018-06-05 Thread SpiderQED
apport information

** Attachment added: "rfkill.txt"
   https://bugs.launchpad.net/bugs/1774640/+attachment/5148900/+files/rfkill.txt

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774486] Re: graphic chip

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  graphic chip

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  i didnt know how to install my intel chip 3000 hd

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Thu May 31 21:05:34 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics 
Controller [8086:0402] (rev 06) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Xeon E3-1200 v3/4th Gen Core 
Processor Integrated Graphics Controller [1458:d000]
  InstallationDate: Installed on 2018-05-24 (7 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Gigabyte Technology Co., Ltd. H81M-S2PH
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=91ec5cbc-f46b-4c99-9d84-78001db6db6b ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 11/10/2014
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: FC
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: H81M-S2PH
  dmi.board.vendor: Gigabyte Technology Co., Ltd.
  dmi.board.version: x.x
  dmi.chassis.asset.tag: To Be Filled By O.E.M.
  dmi.chassis.type: 3
  dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
  dmi.chassis.version: To Be Filled By O.E.M.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrFC:bd11/10/2014:svnGigabyteTechnologyCo.,Ltd.:pnH81M-S2PH:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnH81M-S2PH:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.:
  dmi.product.family: To be filled by O.E.M.
  dmi.product.name: H81M-S2PH
  dmi.product.version: To be filled by O.E.M.
  dmi.sys.vendor: Gigabyte Technology Co., Ltd.
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://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 1774640] UdevDb.txt

2018-06-05 Thread SpiderQED
apport information

** Attachment added: "UdevDb.txt"
   https://bugs.launchpad.net/bugs/1774640/+attachment/5148898/+files/UdevDb.txt

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774856] Re: nividi drivers

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Unfortunately, we cannot work on this bug because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html. We'd be grateful
if you would then provide a more complete description of the problem.

We have instructions on debugging some types of problems at
http://wiki.ubuntu.com/DebuggingProcedures.

At a minimum, we need:
1. The specific steps or actions you took that caused you to encounter the 
problem.
2. The behavior you expected. 
3. The behavior you actually encountered (in as much detail as possible).
Thanks!

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

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

Title:
  nividi drivers

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  Drivers nvidia fuck up

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8.1
  ProcVersionSignature: Ubuntu 3.13.0-149.199-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-149-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  390.59  Wed May  9 22:33:42 
PDT 2018
   GCC version:  gcc version 4.8.4 (Ubuntu 4.8.4-2ubuntu1~14.04.4)
  ApportVersion: 2.14.1-0ubuntu3.28
  Architecture: amd64
  Date: Sun Jun  3 12:52:30 2018
  DistUpgraded: Fresh install
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-20140620-0
  DistroCodename: trusty
  DistroVariant: ubuntu
  GraphicsCard:
   Intel Corporation Broadwell-U Integrated Graphics [8086:1616] (rev 09) 
(prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:06ae]
 Subsystem: Dell Device [1028:06ae]
  InstallationDate: Installed on 2015-07-22 (1047 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20140620-04:25
  MachineType: Dell Inc. Inspiron 5558
  ProcEnviron:
   LANGUAGE=pl
   PATH=(custom, no user)
   LANG=pl_PL.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-149-generic 
root=UUID=704f2fc5-97f6-46db-8498-c4dc3400a4e2 ro drm.debug=0xe plymouth:debug 
quiet splash radeon.modeset=0 nouveau.modeset=0
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A03
  dmi.board.name: 086DKN
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA03:bd07/14/2015:svnDellInc.:pnInspiron5558:pvr01:rvnDellInc.:rn086DKN:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: Inspiron 5558
  dmi.product.version: 01
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11.3+14.04.20160425-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.14.04.2
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.3-0ubuntu0.6
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.3-0ubuntu0.6
  version.nvidia-graphics-drivers: nvidia-graphics-drivers N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2.11
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3.1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.910-0ubuntu1.7
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Sun Jun  3 12:19:40 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   No devices detected.
   [drm] KMS not enabled
   Failed to initialize GLX extension (Compatible NVIDIA X driver not found)
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id1583 
   vendor BOE
  xserver.version: 2:1.15.1-0ubuntu2.11

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

-- 
Mailing list: https://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 1775018] Re: Fix for openssl 1.0.2 backport

2018-06-05 Thread Francis Ginther
** Tags added: id-5b1570c1ed92da52a894618c

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

Title:
  Fix for openssl 1.0.2 backport

Status in Ubuntu on IBM z Systems:
  Triaged
Status in openssl package in Ubuntu:
  New

Bug description:
  This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and
  upstream code are not affected ).

  Original LP ticket : 
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+subscriptions

-- 
Mailing list: https://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 1751593] Re: Weird black border flickres around windows.

2018-06-05 Thread Daniel van Vugt
** Package changed: xorg (Ubuntu) => gnome-shell (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/1751593

Title:
  Weird black border flickres around windows.

Status in gnome-shell package in Ubuntu:
  New

Bug description:
  Whenever I open any new window, a black border around the window
  appears for a fraction of a second (like a flicker).

  Although this doesn't happen very frequently, happens around 3-4 times
  out of 10. This is most noticeable when I right click on Desktop and
  click on "Open terminal". I can replicate this bug every time when I
  open terminal this way.

  Also, when I open terminal by pressing Control+Alt+T, the caption
  buttons kind of grey out after the flicker and are un-clickable. They
  look as if the window is not at focus. Workaround is to switch to
  another window (Alt+Tab) and then switch back to terminal.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: xorg (not installed)
  ProcVersionSignature: Ubuntu 4.13.0-36.40-generic 4.13.13
  Uname: Linux 4.13.0-36-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Feb 25 19:58:24 2018
  InstallationDate: Installed on 2018-02-13 (11 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1774151] Re: Xorg crashed with SIGABRT in RSetChanged()

2018-06-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1249551 ***
https://bugs.launchpad.net/bugs/1249551

** Package changed: xorg (Ubuntu) => xorg-server (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/1774151

Title:
  Xorg crashed with SIGABRT in RSetChanged()

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I guess it happens because I made and update of my nvidia drivers
  using apt-get dist-upgrade while gnome was up and running. Because
  during the update gnome freezes and restarts itself after a while.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-127.153-generic 4.4.128
  Uname: Linux 4.4.0-127-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Ist ein Verzeichnis: 
'/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.130  Wed Mar 21 03:37:26 
PDT 2018
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.9)
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed May 30 10:34:15 2018
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Lenovo 3rd Gen Core processor Graphics Controller [17aa:21f5]
   NVIDIA Corporation GK107GLM [Quadro K2000M] [10de:0ffb] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: Lenovo GK107GLM [Quadro K2000M] [17aa:21f5]
  InstallationDate: Installed on 2014-04-18 (1502 days ago)
  InstallationMedia: Ubuntu-GNOME 14.04 LTS "Trusty Tahr" - Release amd64 
(20140416.2)
  MachineType: LENOVO 24474GG
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-127-generic 
root=UUID=b44fee51-1765-4794-b840-a8e5272c94c7 ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/13/2013
  dmi.bios.vendor: LENOVO
  dmi.bios.version: G5ET95WW (2.55 )
  dmi.board.asset.tag: Not Available
  dmi.board.name: 24474GG
  dmi.board.vendor: LENOVO
  dmi.board.version: Win8 Pro DPK TPG
  dmi.chassis.asset.tag: No Asset Information
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Not Available
  dmi.modalias: 
dmi:bvnLENOVO:bvrG5ET95WW(2.55):bd09/13/2013:svnLENOVO:pn24474GG:pvrThinkPadW530:rvnLENOVO:rn24474GG:rvrWin8ProDPKTPG:cvnLENOVO:ct10:cvrNotAvailable:
  dmi.product.name: 24474GG
  dmi.product.version: ThinkPad W530
  dmi.sys.vendor: LENOVO
  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.8-0ubuntu0~16.04.1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 17.2.8-0ubuntu0~16.04.1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.7
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.1-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160325-1ubuntu1.2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed May 30 10:11:32 2018
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://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 1774782] Re: Horizontal stripes flickering

2018-06-05 Thread Daniel van Vugt
1. Can you please take a photo of the problem and attach it here?

2. Does logging into 'Ubuntu on Wayland' fix the problem?

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

** Package changed: xorg (Ubuntu) => xorg-server (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/1774782

Title:
  Horizontal stripes flickering

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I've go horizontal stripes flickering on my laptop screen. It's really
  annoying and I couldn't concentrate on my work.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Sat Jun  2 15:44:32 2018
  DistUpgraded: 2018-06-02 14:32:32,469 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 0b) (prog-if 00 [VGA controller])
 Subsystem: Lenovo Haswell-ULT Integrated Graphics Controller [17aa:380d]
  InstallationDate: Installed on 2016-04-20 (773 days ago)
  InstallationMedia: Ubuntu 14.04.4 LTS "Trusty Tahr" - Release amd64 
(20160217.1)
  MachineType: LENOVO 20354
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=cs_CZ.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=14857e5e-1fd5-4571-b7e9-c3394bee4e34 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  UpgradeStatus: Upgraded to bionic on 2018-06-02 (0 days ago)
  dmi.bios.date: 10/20/2014
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 9BCN29WW
  dmi.board.asset.tag: No Asset Tag
  dmi.board.name: Lancer 5A5
  dmi.board.vendor: LENOVO
  dmi.board.version: 31900058WIN
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: Lenovo Z50-70
  dmi.modalias: 
dmi:bvnLENOVO:bvr9BCN29WW:bd10/20/2014:svnLENOVO:pn20354:pvrLenovoZ50-70:rvnLENOVO:rnLancer5A5:rvr31900058WIN:cvnLENOVO:ct10:cvrLenovoZ50-70:
  dmi.product.family: IDEAPAD
  dmi.product.name: 20354
  dmi.product.version: Lenovo Z50-70
  dmi.sys.vendor: LENOVO
  version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
  xserver.bootTime: Sat Jun  2 12:35:03 2018
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5579 
   vendor CMN
  xserver.version: 2:1.18.4-0ubuntu0.7

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

-- 
Mailing list: https://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 1774640] ProcCpuinfoMinimal.txt

2018-06-05 Thread SpiderQED
apport information

** Attachment added: "ProcCpuinfoMinimal.txt"
   
https://bugs.launchpad.net/bugs/1774640/+attachment/5148894/+files/ProcCpuinfoMinimal.txt

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774640] Dependencies.txt

2018-06-05 Thread SpiderQED
apport information

** Attachment added: "Dependencies.txt"
   
https://bugs.launchpad.net/bugs/1774640/+attachment/5148891/+files/Dependencies.txt

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774640] ProcInterrupts.txt

2018-06-05 Thread SpiderQED
apport information

** Attachment added: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/bugs/1774640/+attachment/5148896/+files/ProcInterrupts.txt

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774640] getfacl.txt

2018-06-05 Thread SpiderQED
apport information

** Attachment added: "getfacl.txt"
   
https://bugs.launchpad.net/bugs/1774640/+attachment/5148899/+files/getfacl.txt

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774640] Lspci.txt

2018-06-05 Thread SpiderQED
apport information

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

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774640] Re: Bluetooth turns off automatically Ubuntu 18.04 LTS

2018-06-05 Thread SpiderQED
I am able to turn Bluetooth on, but after a few seconds it turns off
automatically again. Only after a reboot of my laptop I am able turn
Bluetooth on without any problems. I've run 'apport-collect 1774640'.

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774640] ProcModules.txt

2018-06-05 Thread SpiderQED
apport information

** Attachment added: "ProcModules.txt"
   
https://bugs.launchpad.net/bugs/1774640/+attachment/5148897/+files/ProcModules.txt

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774640] ProcEnviron.txt

2018-06-05 Thread SpiderQED
apport information

** Attachment added: "ProcEnviron.txt"
   
https://bugs.launchpad.net/bugs/1774640/+attachment/5148895/+files/ProcEnviron.txt

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1774640] Re: Bluetooth turns off automatically Ubuntu 18.04 LTS

2018-06-05 Thread SpiderQED
apport information

** Tags added: apport-collected bionic

** Description changed:

- Whenever I start up my laptop and connect my JBL-speaker, the device
- stays connected. However, when I turn de speaker off, and try to
- reconnect to the speaker, the Bluetooth automatically turns off. I then
- need to restart my laptop and then only Bluetooth works again.
+ Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
+ --- 
+ ApportVersion: 2.20.9-0ubuntu7.1
+ Architecture: amd64
+ CurrentDesktop: Unity:Unity7:ubuntu
+ DistroRelease: Ubuntu 18.04
+ InstallationDate: Installed on 2018-04-27 (39 days ago)
+ InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
+ InterestingModules: rfcomm bnep btusb bluetooth
+ Lsusb:
+  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
+  Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
+  Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
+  Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
+  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
+ MachineType: ASUSTeK COMPUTER INC. X555LAB
+ Package: bluez 5.48-0ubuntu3
+ PackageArchitecture: amd64
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
+ ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
+ Tags:  bionic
+ Uname: Linux 4.15.0-22-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
+ _MarkForUpload: True
+ dmi.bios.date: 08/04/2015
+ dmi.bios.vendor: American Megatrends Inc.
+ dmi.bios.version: X555LAB.503
+ dmi.board.asset.tag: ATN12345678901234567
+ dmi.board.name: X555LAB
+ dmi.board.vendor: ASUSTeK COMPUTER INC.
+ dmi.board.version: 1.0
+ dmi.chassis.asset.tag: ATN12345678901234567
+ dmi.chassis.type: 10
+ dmi.chassis.vendor: ASUSTeK COMPUTER INC.
+ dmi.chassis.version: 1.0
+ dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
+ dmi.product.family: X
+ dmi.product.name: X555LAB
+ dmi.product.version: 1.0
+ dmi.sys.vendor: ASUSTeK COMPUTER INC.
+ hciconfig:
+  hci0:Type: Primary  Bus: USB
+   BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
+   UP RUNNING PSCAN 
+   RX bytes:55347 acl:67 sco:0 events:7591 errors:0
+   TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

** Attachment added: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/bugs/1774640/+attachment/5148890/+files/CurrentDmesg.txt

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 

[Touch-packages] [Bug 1775064] Re: Xorg freeze

2018-06-05 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1765261 ***
https://bugs.launchpad.net/bugs/1765261

The freeze with a violet background is bug 1766137.

Needing to log in two times is bug 1765261.


** This bug has been marked a duplicate of bug 1765261
   [regression] Ubuntu 18.04 login screen rejects a valid password on first 
attempt (if starting with Shift key). Usually works on the second attempt

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  Yesterday my PC shutdown for a voltage issue. Today I power on it but after 
the login the screen it freezes with a violet background. For repair this 
problem I put this one in StandBy using the power button. After the standby 
resume I can be able to login and use the OS.
  Sometime happen that after the standby I need to login two times for use the 
PC.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  340.106  Tue Jan  9 15:10:23 
PST 2018
   GCC version:  gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)
  .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.9-0ubuntu7.1
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Jun  4 21:29:39 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  DkmsStatus:
   nvidia-340, 340.106, 4.15.0-20-generic, x86_64: installed
   nvidia-340, 340.106, 4.15.0-22-generic, x86_64: installed
  DpkgLog:
   
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: This is the first time
  GraphicsCard:
   NVIDIA Corporation GT218 [GeForce 310] [10de:0a66] (rev a2) (prog-if 00 [VGA 
controller])
 Subsystem: PC Partner Limited / Sapphire Technology GT218 [GeForce 310] 
[174b:3100]
  InstallationDate: Installed on 2018-05-02 (33 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Packard Bell imedia S3800
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=a804f163-b3e6-486b-9852-424a8b051616 ro quiet splash vt.handoff=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 04/03/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: P01-B1
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: FIH57
  dmi.board.vendor: Packard Bell
  dmi.chassis.type: 3
  dmi.chassis.vendor: Packard Bell
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrP01-B1:bd04/03/2010:svnPackardBell:pnimediaS3800:pvr:rvnPackardBell:rnFIH57:rvr:cvnPackardBell:ct3:cvr:
  dmi.product.family: Packard Bell Desktop
  dmi.product.name: imedia S3800
  dmi.sys.vendor: Packard Bell
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91-2
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.0.0~rc5-1ubuntu1
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.0.0~rc5-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://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 1773213] Re: U1 login dialog missing link to the privacy policy

2018-06-05 Thread Iain Lane
Hey, I think this should get the privacy policy URL from /etc/os-
release, do you agree?

** Also affects: gnome-online-accounts (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Changed in: gnome-online-accounts (Ubuntu)
 Assignee: Andrea Azzarone (azzar1) => Ken VanDine (ken-vandine)

** Changed in: gnome-online-accounts (Ubuntu Bionic)
 Assignee: (unassigned) => Ken VanDine (ken-vandine)

** Tags removed: rls-bb-incoming

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

Title:
  U1 login dialog missing link to the privacy policy

Status in gnome-online-accounts package in Ubuntu:
  In Progress
Status in gnome-online-accounts source package in Bionic:
  New

Bug description:
  The U1 login for g-o-a is missing a link to the privacy policy.

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

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


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

2018-06-05 Thread Arun Soman
Thanks Stephen.
As per your note I removed the /usr/share/python/rekall-forensic  folder then 
it is worked for me 2 days I spend for finding out a solution thanks for your 
help...

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

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

Status in python-defaults package in Ubuntu:
  Confirmed

Bug description:
  There seems to be a dependency snarl:

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

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

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

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

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


[Touch-packages] [Bug 1706939] Re: A live session can't be shut down due to "[ *** ] (2 of 2) A start job is running for ... (22s / no limit)"

2018-06-05 Thread Iain Lane
hi xnox, is this the same as casper 1.394 - i.e. a failure to properly
cache everything that casper needs?

If so, I don't think this is a gdm3 bug itself. I just assigned this to
nudge you on it; feel free to move on as you see fit.

(Making Invalid for gdm3 to get this off our rls-bb-tracking list.)

** Changed in: casper (Ubuntu)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

** Changed in: casper (Ubuntu Bionic)
 Assignee: (unassigned) => Dimitri John Ledkov (xnox)

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

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

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

Title:
  A live session can't be shut down due to "[ ***  ] (2 of 2) A start
  job is running for ... (22s / no limit)"

Status in Release Notes for Ubuntu:
  Fix Released
Status in casper package in Ubuntu:
  New
Status in gdm3 package in Ubuntu:
  Invalid
Status in systemd package in Ubuntu:
  Confirmed
Status in casper source package in Bionic:
  New
Status in gdm3 source package in Bionic:
  Invalid

Bug description:
  Test case:
  Boot to live session using current or recent image
  Attempt to restart, shutdown or even log out.
  Hangs basically forever with:

  [ ***  ] (2 of 2) A start job is running for Hold until boot process
  finishes up (21s / no limit)

  or

  [ *** ] (2 of 2) A start job is running for Wait for Network to be
  Configured (21s / no limit)

  ---
  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gdm3 3.24.2-1ubuntu9
  ProcVersionSignature: Ubuntu 4.11.0-10.15-generic 4.11.8
  Uname: Linux 4.11.0-10-generic x86_64
  ApportVersion: 2.20.6-0ubuntu4
  Architecture: amd64
  CasperVersion: 1.384
  CurrentDesktop: GNOME
  Date: Thu Jul 27 10:15:57 2017
  LiveMediaBuild: Ubuntu 17.10 "Artful Aardvark" - Alpha amd64 (20170723)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2017-07-27T10:13:04.127685

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1706939/+subscriptions

-- 
Mailing list: https://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 611835] Re: Incorrect detect size of surface for subtitle rendering when playback anamorph video

2018-06-05 Thread Bug Watch Updater
** Changed in: gstreamer
   Status: Expired => Confirmed

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

Title:
  Incorrect detect size of surface for subtitle rendering when playback
  anamorph video

Status in GStreamer:
  Confirmed
Status in gstreamer0.10 package in Ubuntu:
  Triaged

Bug description:
  Look at attached screenshots. I get incorrect rendering in Totem player. 
Correct rendering - it's mplayer.
  Sample: http://sharebee.com/65fa39aa
  When aspect ratio of video stream not equal with aspect ratio in properties 
of this video stream in media contatiner (anamorph video) rendering ass 
subtitles always incorrect. For example real size of video in this sample file 
is 1440x1080, but it's playback like 1920x1080.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: libgstreamer0.10-0 0.10.30-1
  ProcVersionSignature: Ubuntu 2.6.35-11.16-generic 2.6.35-rc5
  Uname: Linux 2.6.35-11-generic x86_64
  Architecture: amd64
  Date: Sat Jul 31 04:47:55 2010
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
  ProcEnviron:
   LANG=ru_RU.UTF-8
   SHELL=/bin/bash
  SourcePackage: gstreamer0.10

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

-- 
Mailing list: https://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 1760349] Re: Cannot log in to public open Wifi connection because not being redirected to login site

2018-06-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: network-manager (Ubuntu)
   Status: New => Confirmed

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

Title:
  Cannot log in to public open Wifi connection because not being
  redirected to login site

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  I have noticed that Kubuntu 18.04 (Bionic Beaver) does not login to
  public Wifi hotspots without wifi security, that require login through
  a web page. I don't know if this is reproducible on arbitrary public
  networks, or only on the few I tried.

  The solution was as follows:
  - Create file /etc/NetworkManager/conf.d/20-connectivity-debian.conf (you'll 
need root or sudo).
  - Add the following lines as recommended by Guruprasad 
(https://www.lguruprasad.in/blog/2015/07/21/enabling-captive-portal-detection-in-gnome-3-14-on-debian-jessie/):

  [connectivity]
  uri=http://network-test.debian.org/nm
  response=NetworkManager is online
  interval=300

  - Restart the network manager with service network-manager restart
  (will need sudo or root again).

  This is a very annoying and unnecessary default behavior it seems.
  Maybe a good idea to fix it.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: network-manager 1.10.6-2ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Mar 31 22:48:21 2018
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2018-02-18 (41 days ago)
  InstallationMedia: Kubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180218)
  IpRoute:
   default via 10.129.249.1 dev wlp1s0 proto dhcp metric 600 
   10.129.249.0/24 dev wlp1s0 proto kernel scope link src 10.129.249.35 metric 
600 
   169.254.0.0/16 dev wlp1s0 scope link metric 1000
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
  ProcEnviron:
   LANGUAGE=
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  RfKill:
   0: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-dev:
   DEVICE  TYPE  STATE  DBUS-PATH  
CONNECTION   CON-UUID  CON-PATH 
  
   wlp1s0  wifi  connected  /org/freedesktop/NetworkManager/Devices/2  
SuedtirolSpot_1  c4464785-b548-4655-b06b-48a0aec06a87  
/org/freedesktop/NetworkManager/ActiveConnection/3 
   lo  loopback  unmanaged  /org/freedesktop/NetworkManager/Devices/1  --   
----
  nmcli-nm:
   RUNNING  VERSION  STATE  STARTUP  CONNECTIVITY  NETWORKING  WIFI-HW  
WIFI WWAN-HW  WWAN
   running  1.10.6   connected  started  full  enabled enabled  
enabled  enabled  enabled

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

-- 
Mailing list: https://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 1775187] [NEW] bluetooth headset gets imitatively disconnected

2018-06-05 Thread Jan Katins
Public bug reported:

I upgraded from artful to bionic (just run apt update && apt upgrade and
rebooted before testing the below) and since then my sennheiser pxc550
was immediately disconnected after a connect.

Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete 
(0x0f)
Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: Device 
doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8
Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with an 
error: org.bluez.Error.InvalidArguments, Unable to handle new connection
Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: 
Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid
Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 
matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 
comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") 
interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" 
destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " 
label="unconfined")
Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: 
Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid
Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 
matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 
comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") 
interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" 
destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " 
label="unconfined")
Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete 
(0x0f)
Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete 
(0x0f)
Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd complete 
(0x0f)
[...same message a few more time until I had a new version installed ...]


I since then applied the patch from 
https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> 
https://marc.info/?l=linux-bluetooth=151801178209679=raw to bluez (apt 
source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now 
my headset works again.

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

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

Title:
  bluetooth headset gets imitatively disconnected

Status in bluez package in Ubuntu:
  New

Bug description:
  I upgraded from artful to bionic (just run apt update && apt upgrade
  and rebooted before testing the below) and since then my sennheiser
  pxc550 was immediately disconnected after a connect.

  Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)
  Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: 
Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8
  Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with 
an error: org.bluez.Error.InvalidArguments, Unable to handle new connection
  Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: 
Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid
  Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 
matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 
comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") 
interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" 
destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " 
label="unconfined")
  Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: 
Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid
  Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 
matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 
comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") 
interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" 
destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " 
label="unconfined")
  Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)
  Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)
  Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last 

[Touch-packages] [Bug 1775215] [NEW] /etc/resolvconf/resolv.conf.d/head contains misleading references to systemd-resolved

2018-06-05 Thread Michael
Public bug reported:

References to systemd-resolved, systemd-resolve, or 127.0.0.53 are
obviously incorrect and misleading on machines configured to not use
systemd-resolve(d).

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: resolvconf 1.79ubuntu10
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
Date: Tue Jun  5 23:59:33 2018
InstallationDate: Installed on 2017-08-01 (308 days ago)
InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
PackageArchitecture: all
SourcePackage: resolvconf
UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  /etc/resolvconf/resolv.conf.d/head contains misleading references to
  systemd-resolved

Status in resolvconf package in Ubuntu:
  New

Bug description:
  References to systemd-resolved, systemd-resolve, or 127.0.0.53 are
  obviously incorrect and misleading on machines configured to not use
  systemd-resolve(d).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  Date: Tue Jun  5 23:59:33 2018
  InstallationDate: Installed on 2017-08-01 (308 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1703100] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

2018-06-05 Thread Victor Marin
Thanks for your responses.

I not longer had this problem in Kubuntu 18.04.

 Original Message 
Subject: [Bug 1703100] Re: package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed 
to install/upgrade: el subproceso instalado el script post-installation 
devolvió el código de salida de error 1
From:  Christian Ehrhardt  <1703...@bugs.launchpad.net>
To: 
Date: 29/05/18 09:48
> And I beg your pardon to come by so late, I was looking at ntp bugs in
> general today and found this. If I'd have known I could have explained
> earlier :-/
>
> ** Changed in: ntp (Ubuntu)
> Status: New => Incomplete
>

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

Title:
  package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in ntp package in Ubuntu:
  Incomplete

Bug description:
  Trying to install the updates along with audacity through Synaptic, it
  had problems and didn't install.

  I didn't copy the error message but it was something related to: util-
  linux

  And I think the error message was something related to that "it can't be 
true!" and it included a message like this:
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  Thereafter I couldn't install nor uninstall anything.

  In http://www.ubuntu-es.org/node/157198#.WWCyvydLfrc they advised to
  go to /var/lib/dpkg/info as root, then to remove all files including
  util-linux on its names.

  Then, I could uninstall util-linux and everything seems Ok now.

  But, I just did a # apt-get -f install, and it returns that:

  Leyendo lista de paquetes... Hecho
  Creando árbol de dependencias   
  Leyendo la información de estado... Hecho
  Los paquetes indicados a continuación se instalaron de forma automática y ya 
no son necesarios.
linux-headers-4.4.0-78 linux-headers-4.4.0-78-generic
linux-image-4.4.0-78-generic linux-image-extra-4.4.0-78-generic
linux-signed-image-4.4.0-78-generic
  Utilice «sudo apt autoremove» para eliminarlos.
  0 actualizados, 0 nuevos se instalarán, 0 para eliminar y 43 no actualizados.
  1 no instalados del todo o eliminados.
  Se utilizarán 0 B de espacio de disco adicional después de esta operación.
  Configurando ntp (1:4.2.8p4+dfsg-3ubuntu5.5) ...
  insserv: warning: script 'K01smfpd' missing LSB tags and overrides
  insserv: warning: script 'smfpd' missing LSB tags and overrides
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: There is a loop between service smfpd and grub-common if started
  insserv:  loop involving service grub-common at depth 7
  insserv:  loop involving service smfpd at depth 1
  insserv: Starting smfpd depends on grub-common and therefore on system 
facility `$all' which can not be true!
  insserv: exiting now without changing boot order!
  update-rc.d: error: insserv rejected the script header
  dpkg: error al procesar el paquete ntp (--configure):
   el subproceso instalado el script post-installation devolvió el código de 
salida de error 1
  Se encontraron errores al procesar:
   ntp
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  
  Perhaps, Synaptic tried to install at its own some updates that it were 
retained by Ubuntu, But I don't know.

  I am fulfilling this bug because Ubuntu so requested me to do on the
  next time I have started the OS.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ntp 1:4.2.8p4+dfsg-3ubuntu5.5
  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: Sat Jul  8 11:05:11 2017
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2017-05-23 (45 days ago)
  InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  NtpStatus: ntpq: read: Connection refused
  ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-4.4.0-79-generic.efi.signed 
root=UUID=090c6807-97c0-4b04-b1b5-1080d8ae1ddf ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.2
   apt  1.2.20
  SourcePackage: ntp
  Title: package ntp 1:4.2.8p4+dfsg-3ubuntu5.5 failed to install/upgrade: el 
subproceso instalado el script post-installation devolvió el código de salida 
de error 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go 

[Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-06-05 Thread Julian Andres Klode
I could not reproduce this with that file in my lxd testing setup
either. It might depend on PPA packages changing the order. That said,
fixing the trigger to be noawait is definitely the right thing to do-

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

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  In Progress

Bug description:
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

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

-- 
Mailing list: https://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 1775215] Re: /etc/resolvconf/resolv.conf.d/head contains misleading references to systemd-resolved

2018-06-05 Thread Dimitri John Ledkov
The comment is in a conffile /etc/resolvconf/resolv.conf.d/head and is
correct for the unmodified systems.

Feel free to update that conffile on your system to match the local
configuration.

** Changed in: resolvconf (Ubuntu)
   Status: New => Opinion

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

Title:
  /etc/resolvconf/resolv.conf.d/head contains misleading references to
  systemd-resolved

Status in resolvconf package in Ubuntu:
  Opinion

Bug description:
  References to systemd-resolved, systemd-resolve, or 127.0.0.53 are
  obviously incorrect and misleading on machines configured to not use
  systemd-resolve(d).

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: resolvconf 1.79ubuntu10
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  Date: Tue Jun  5 23:59:33 2018
  InstallationDate: Installed on 2017-08-01 (308 days ago)
  InstallationMedia: Xubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412)
  PackageArchitecture: all
  SourcePackage: resolvconf
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1774651] Re: Ubuntu 18.04: click: install updates before shutdown, enter disk password

2018-06-05 Thread Balint Reczey
It is a bit confusing to have another parallel way of upgrading packages
with Gnome Software, I opened LP: #1775226 about it.

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

Title:
  Ubuntu 18.04: click: install updates before shutdown, enter disk
  password

Status in packagekit package in Ubuntu:
  New

Bug description:
  Ubuntu 18.04 with disk-encryption, when (security) updates are
  available but not installed, then the shutdown- menu gives the option
  to "install updates before shutdown" selecting this option takes you
  to the disk-encrytion password screen before installing updates and
  shutdown.

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

-- 
Mailing list: https://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 1766969] Re: DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

2018-06-05 Thread Dimitri John Ledkov
** Changed in: systemd (Ubuntu Bionic)
   Status: Fix Released => Fix Committed

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

Title:
  DNS cannot be resolved in Public / Hotel / Starbucks WiFi Hotspot

Status in systemd package in Ubuntu:
  Fix Committed
Status in systemd source package in Artful:
  Confirmed
Status in systemd source package in Bionic:
  Fix Committed
Status in systemd source package in Cosmic:
  Fix Committed

Bug description:
  [Impact]

   * More captive portals have been discovered that do not handle DNS requests 
with D0 set.
   * Thus extend previous aruba-networks fix from 
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 by retrying all 
NXDOMAIN results with lower feature levels just in case.

  [Test Case]

   * systemd-resolved something-nonexistant.ubuntu.com
   * monitor the logs, and check that the transaction has been downgraded 
multiple times and tried at least once at a feature level below D0. There 
should be a downgrade message in the log.
   * Note, it will be cached, thus one may need to call $ systemd-resolved 
--flush-caches

  [Regression Potential]

   * Legitimate NXDOMAIN queries will now take longer, as they will be
  retried multiple times with different features sets until an answer is
  found. At that point the query will be cached and will return quickly.
  This is needed to work-around bad captive portals that do not support
  dns queries with D0. Post-captive portal, the feature level can
  usually be cranked back up and it does after a grace period.

  [Other Info]
   
   * Original bug report

  I was asked to create a new bug for this in
  https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1727237 as it
  seems to be a different issue.

  I have installed the nightly image of Kubuntu Bionic from 25th of
  April.

  There systemd is in version 237-3ubuntu10.

  When connecting to the wifi hotspot in my hotel (Quality Hotel
  Augsburg) I cannot open the hotspot landing page that should give me
  access to the WIFI. With Windows and on an Iphone it's working.

  For the following distributions I can confirm it not working:
  Kubuntu 17.10
  Kubuntu 18.04 (nightly image 25th of April 2018)

  The logs were taken on 18.04.

  Workaround:
  sudo systemctl disable systemd-resolved.service
  sudo service systemd-resolved stop
  sudo rm /etc/resolv.conf
  sudo nano /etc/NetworkManager/NetworkManager.conf
    >> add "dns=default" under [main]
  sudo service network-manager restart

  Then I can connect to the WIFI and I see the login page in Firefox.

  To capture some data I did the following:
   - connect to Hotspot
   - enter golem.de

  Case 1: Fresh default Kubuntu install
  With a default Kubuntu install it does not work. I can connect to the WIFI 
and get IP and DNS from DHCP but I cannot resolve any hostname. When trying  to 
open the router ip directly in the browser it forwards to hotsplots.de which 
cannot be resolved.

  Case 2: With aforementioned Workaround
  I connect to the wifi, I open firefox and the login page shows up (if I 
havent been connected yet. In the capture I already was able to connect to the 
hotspot which allows immediately to connect to the webpage)

  PS: I'll be in this hotel till Friday 27th if more information are
  required.

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

-- 
Mailing list: https://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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-06-05 Thread Julian Andres Klode
** Description changed:

+ [Impact]
+ Breaks some upgrades, depending on install order.
+ 
+ [Test case]
+ N/A. After consultation with the dpkg maintainer and investigating the 
situation, it's reasonably safe to assume that noawait is the right thing to do:
+ 
+ * the intended use for the trigger is to run _after_ packages with .menu 
+ files are configured, not before; therefore
+ * the file trigger is triggered manually from the postinst again, discussion 
has been that the file trigger is not actually needed.
+ 
+ [Regression potential]
+ Menu might not be updated correctly
+ 
+ [Original bug report]
  I get this error when I update to 18.04
  
  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 16:51:28 2018
  Dependencies:
-  gcc-8-base 8-20180414-1ubuntu2
-  libc6 2.27-3ubuntu1
-  libgcc1 1:8-20180414-1ubuntu2
-  libstdc++6 8-20180414-1ubuntu2
+  gcc-8-base 8-20180414-1ubuntu2
+  libc6 2.27-3ubuntu1
+  libgcc1 1:8-20180414-1ubuntu2
+  libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
-  dpkg 1.19.0.5ubuntu2
-  apt  1.6.1
+  dpkg 1.19.0.5ubuntu2
+  apt  1.6.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Fix Committed
Status in apt source package in Xenial:
  New
Status in menu source package in Xenial:
  New
Status in apt source package in Artful:
  New
Status in menu source package in Artful:
  New
Status in apt source package in Bionic:
  New
Status in menu source package in Bionic:
  New

Bug description:
  [Impact]
  Breaks some upgrades, depending on install order.

  [Test case]
  N/A. After consultation with the dpkg maintainer and investigating the 
situation, it's reasonably safe to assume that noawait is the right thing to do:

  * the intended use for the trigger is to run _after_ packages with .menu 
  files are configured, not before; therefore
  * the file trigger is triggered manually from the postinst again, discussion 
has been that the file trigger is not actually needed.

  [Regression potential]
  Menu might not be updated correctly

  [Original bug report]
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

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

-- 
Mailing list: https://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 1775219] [NEW] incorrectly reports package as unsupported if apt cache is empty

2018-06-05 Thread Robert C Jennings
Public bug reported:

Cloud images ship with empty /var/lib/apt/lists/ to save on size.
Running 'ubuntu-bug ' will erroneously report that
the package is unsupported:

  $ ubuntu-bug coreutils

  *** Collecting problem information

  The collected information can be sent to the developers to improve the
  application. This might take a few minutes.
  .

  *** Problem in coreutils

  The problem cannot be reported:

  This is not an official Ubuntu package. Please remove any third party
package and try again.

A simpler recreate is:

$ python3 -c 'import 
apport;print(apport.packaging.is_distro_package("coreutils"))'
False
$ sudo apt update -qq
All packages are up to date.
$ python3 -c 'import 
apport;print(apport.packaging.is_distro_package("coreutils"))'
True

Desired result:

The message should instruct the user to run 'apt update' as root if they
think this is in error.   That would improve usability and avoid false
reports about apport incorrectly flagging a package as unsupported.

Additionally, if the user is root (and optionally if the set of package
candidates only contains a 'now' component) self._cache.update();
self._cache.open() could be called to download lists.

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

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

Title:
  incorrectly reports package as unsupported if apt cache is empty

Status in apport package in Ubuntu:
  New

Bug description:
  Cloud images ship with empty /var/lib/apt/lists/ to save on size.
  Running 'ubuntu-bug ' will erroneously report that
  the package is unsupported:

$ ubuntu-bug coreutils

*** Collecting problem information

The collected information can be sent to the developers to improve the
application. This might take a few minutes.
.

*** Problem in coreutils

The problem cannot be reported:

This is not an official Ubuntu package. Please remove any third
  party package and try again.

  A simpler recreate is:

  $ python3 -c 'import 
apport;print(apport.packaging.is_distro_package("coreutils"))'
  False
  $ sudo apt update -qq
  All packages are up to date.
  $ python3 -c 'import 
apport;print(apport.packaging.is_distro_package("coreutils"))'
  True

  Desired result:

  The message should instruct the user to run 'apt update' as root if
  they think this is in error.   That would improve usability and avoid
  false reports about apport incorrectly flagging a package as
  unsupported.

  Additionally, if the user is root (and optionally if the set of
  package candidates only contains a 'now' component)
  self._cache.update(); self._cache.open() could be called to download
  lists.

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

-- 
Mailing list: https://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 1755250] Re: backport statx syscall whitelist fix

2018-06-05 Thread Felix Abecassis
Tianon is right, runc silently discards syscalls it doesn't know about:
https://github.com/opencontainers/runc/blob/ecd55a4135e0a26de884ce436442914f945b1e76/libcontainer/seccomp/seccomp_linux.go#L168-L173

This affects other syscalls, like preadv2:
https://github.com/opencontainers/runtime-spec/issues/972

Failing to whitelist a syscall than the kernel does support is safe, but
failing to *blacklist* a syscall could be more problematic. But failing
to whitelist could also impact functionality/performance compared to a
non-containerized application.

I couldn't find if anything is backported in "2.3.1-2.1ubuntu4", but the
upstream "2.3.1" limits us to syscalls up to Linux 4.5-rc4.

Summoning Christian to help in bumping the priority of this issue.

** Bug watch added: github.com/opencontainers/runtime-spec/issues #972
   https://github.com/opencontainers/runtime-spec/issues/972

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

Title:
  backport statx syscall whitelist fix

Status in docker.io package in Ubuntu:
  New
Status in libseccomp package in Ubuntu:
  New

Bug description:
  Hello maintainer,

  The docker version 17.03 (bionic) in ubuntu doesn't allow the statx syscall 
which is needed to build qt >=5.10 applications:
  https://github.com/docker/for-linux/issues/208#issuecomment-372400859

  Could this fix be backported in the ubuntu package ?
  https://github.com/moby/moby/pull/36417

  regards,
  xan.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/docker.io/+bug/1755250/+subscriptions

-- 
Mailing list: https://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 1775230] [NEW] TP-LINK TL-WN722N causes 100% CPU usage due to trace logging

2018-06-05 Thread Nando
Public bug reported:

Hello.

Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK TL-
WN722N into the USB port, the CPU usage goes to 100%, and there are
multiple reports of "stack traces" in dmesg.

The attached snippet repeats multiple consecutive times in the dmesg
output (albeit with a different trace id).

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


** Tags: tp-link usb wireless

** Attachment added: "tplink-trace-dmesg.txt"
   
https://bugs.launchpad.net/bugs/1775230/+attachment/5149056/+files/tplink-trace-dmesg.txt

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

Title:
  TP-LINK TL-WN722N causes 100% CPU usage due to  trace logging

Status in network-manager package in Ubuntu:
  New

Bug description:
  Hello.

  Running Ubuntu 18.04 (4.15.0-22-generic), after plugging my TP-LINK
  TL-WN722N into the USB port, the CPU usage goes to 100%, and there are
  multiple reports of "stack traces" in dmesg.

  The attached snippet repeats multiple consecutive times in the dmesg
  output (albeit with a different trace id).

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

-- 
Mailing list: https://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 1775018] Re: Fix for openssl 1.0.2 backport

2018-06-05 Thread Dimitri John Ledkov
The change looks obvious.

Is this upstreamed already? What is the upstream commit id?

Can you please provide the following info:

[Impact]

 * An explanation of the effects of the bug on users and

 * justification for backporting the fix to the stable release.

 * In addition, it is helpful, but not required, to include an
   explanation of how the upload fixes this bug.

[Test Case]

 * detailed instructions how to reproduce the bug

 * these should allow someone who is not familiar with the affected
   package to reproduce the bug and verify that the updated package fixes
   the problem.

[Regression Potential]

 * discussion of how regressions are most likely to manifest as a result
of this change.

 * It is assumed that any SRU candidate patch is well-tested before
   upload and has a low overall risk of regression, but it's important
   to make the effort to think about what ''could'' happen in the
   event of a regression.

 * This both shows the SRU team that the risks have been considered,
   and provides guidance to testers in regression-testing the SRU.


It should be fairly straightforward for you to explain above I hope. 
Specifically how to test/excercise this code path?

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

Title:
  Fix for openssl 1.0.2 backport

Status in Ubuntu on IBM z Systems:
  Triaged
Status in openssl package in Ubuntu:
  New

Bug description:
  This is a fix for this feature's backport to openssl 1.0.2 ( 1.1.0 and
  upstream code are not affected ).

  Original LP ticket : 
  https://bugs.launchpad.net/ubuntu/+source/openssl/+bug/1743750

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-z-systems/+bug/1775018/+subscriptions

-- 
Mailing list: https://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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-06-05 Thread Julian Andres Klode
Adding tasks for down to xenial, but not sure what we want to do. I
don't foresee any trouble with that change, but we can't test it, and
even if we get a failing upgrade, we can only test for that release.

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

** Also affects: apt (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: menu (Ubuntu Xenial)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: menu (Ubuntu Bionic)
   Importance: Undecided
   Status: New

** Also affects: apt (Ubuntu Artful)
   Importance: Undecided
   Status: New

** Also affects: menu (Ubuntu Artful)
   Importance: Undecided
   Status: New

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Fix Committed
Status in apt source package in Xenial:
  New
Status in menu source package in Xenial:
  New
Status in apt source package in Artful:
  New
Status in menu source package in Artful:
  New
Status in apt source package in Bionic:
  New
Status in menu source package in Bionic:
  New

Bug description:
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

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

-- 
Mailing list: https://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 1773213] Re: U1 login dialog missing link to the privacy policy

2018-06-05 Thread Andrea Azzarone
Done.

** Patch added: "goa.debdiff"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/1773213/+attachment/5149078/+files/goa.debdiff

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

Title:
  U1 login dialog missing link to the privacy policy

Status in gnome-online-accounts package in Ubuntu:
  In Progress
Status in gnome-online-accounts source package in Bionic:
  New

Bug description:
  The U1 login for g-o-a is missing a link to the privacy policy.

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

-- 
Mailing list: https://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 1775280] [NEW] The second user cannot start their session, login screen has low resolution

2018-06-05 Thread Gabor Czibula
Public bug reported:

The first user can start their session successfully with autologin. When
I try to switch to the second user, the login screen has very low
resolution and it cannot start the secondary user session. I tried to
change the value of the autologin user, than the other user session
start well, but the original user session failed. That's why I think
this is not a user related error, always the second user session fail,
does not matter which one is the first user. The only differences
between the default settings that passwordless login switch on the pam
config and use nvidia-340 driver instead of noveau. The strange thing
that this lightdm config works well with noveau driver, the problem with
noveau driver that the video playing freeze the computer. Previously
lightdm and nvidia driver work well on 16.04. This is a clean install
not an upgrade from 16.04. I think the problem somewhere virtual X
terminals handled by ligthDm.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.9-0ubuntu7.1
Architecture: amd64
CurrentDesktop: X-Cinnamon
Date: Tue Jun  5 23:07:11 2018
EcryptfsInUse: Yes
InstallationDate: Installed on 2018-05-27 (9 days ago)
InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.pam.d.lightdm: 2018-05-27T21:23:23.664631

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

Title:
  The second user cannot start their session, login screen has low
  resolution

Status in lightdm package in Ubuntu:
  New

Bug description:
  The first user can start their session successfully with autologin.
  When I try to switch to the second user, the login screen has very low
  resolution and it cannot start the secondary user session. I tried to
  change the value of the autologin user, than the other user session
  start well, but the original user session failed. That's why I think
  this is not a user related error, always the second user session fail,
  does not matter which one is the first user. The only differences
  between the default settings that passwordless login switch on the pam
  config and use nvidia-340 driver instead of noveau. The strange thing
  that this lightdm config works well with noveau driver, the problem
  with noveau driver that the video playing freeze the computer.
  Previously lightdm and nvidia driver work well on 16.04. This is a
  clean install not an upgrade from 16.04. I think the problem somewhere
  virtual X terminals handled by ligthDm.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: lightdm 1.26.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: X-Cinnamon
  Date: Tue Jun  5 23:07:11 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2018-05-27 (9 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.pam.d.lightdm: 2018-05-27T21:23:23.664631

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

-- 
Mailing list: https://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 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

2018-06-05 Thread Roger Davis
Today, with Xdiagnose unused, I again had an error message "Running in
Low Graphics Mode", after about a dozen starts with no problem.

I again engaged Xdiagnose, checked the top 3 boxes about functions, and
also engaged "Disable bootloader graphics".

Back to checking results...

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

Title:
  message - Low Graphics mode - about 2/3 of startups - not all

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it
  offers, and get by it, after which things look and work normally until
  a reboot, which may or may not occur correctly.

  I also usually get "System error detected, Report? at the same time,
  so I agree to report it.

  Please note that I'm using 16.04 (fully updated), Gnome Flashback
  Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7
  250E] . This problem shows up no matter which of the above I'm using,
  or Unity.

  roger@roger-desktop:~$ uname -a
  Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux

  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348

  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000

  I have found a WORK-AROUND. Using x-diagnose, I selected all options
  under both Debug and Workarounds.  After this, all works normally
  every time.  However, I take this as a crutch, not a fix, and think
  other action should be taken

  Selecting "View Errors" shows no errors, so I never tried reporting
  from that point.

  This gives me a presumption that there is a bug in coding that
  interacts badly with my system and a few others like it, which I
  encountered in my search for a solution.

  Also, if I simply go to 18.04 (I don't really want to just yet.) will
  it likely fix this or might this block or damage the upgrade?

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
  roger@roger-desktop:~$ lsb_release -rd
  Description:  Ubuntu 16.04.4 LTS
  Release:  16.04

  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
  roger@roger-desktop:~$ apt-cache policy pkgname
  N: Unable to locate package pkgname
  ALSO - I'm unable to locate this information in Software Center

  3) What you expected to happen
  Normal boot, no errors or problems

  4) What happened instead
  "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
 Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1413 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug drm.debug=0xe 
nopat vesafb.invalid=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (519 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: 

[Touch-packages] [Bug 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-06-05 Thread Julian Andres Klode
** Bug watch added: Debian Bug tracker #900838
   https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900838

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

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Fix Committed
Status in apt source package in Xenial:
  New
Status in menu source package in Xenial:
  New
Status in apt source package in Artful:
  New
Status in menu source package in Artful:
  New
Status in apt source package in Bionic:
  New
Status in menu source package in Bionic:
  New
Status in menu package in Debian:
  Unknown

Bug description:
  [Impact]
  Breaks some upgrades, depending on install order.

  [Test case]
  N/A. After consultation with the dpkg maintainer and investigating the 
situation, it's reasonably safe to assume that noawait is the right thing to do:

  * the intended use for the trigger is to run _after_ packages with .menu 
  files are configured, not before; therefore
  * the file trigger is triggered manually from the postinst again, discussion 
has been that the file trigger is not actually needed.

  [Regression potential]
  Menu might not be updated correctly

  [Original bug report]
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

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

-- 
Mailing list: https://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 1719038] Re: X Server crashes during log in VM since 16.04.2

2018-06-05 Thread Gannet
Moved from freedesktop to GitLab: https://gitlab.freedesktop.org/spice
/spice-gtk/issues/66

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

Title:
  X Server crashes during log in VM since 16.04.2

Status in X.Org X server:
  In Progress
Status in qemu package in Ubuntu:
  New
Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  If I change screen resolution in my VM with Kubuntu 16.04.3 and then
  make log off and then log on X server is crashes doesn't able me to
  log in.

  Please, look in Xorg.0.log.old for backtrace.

  Also the appropriate report on freedesktop.org:
  https://bugs.freedesktop.org/show_bug.cgi?id=102554

  Host:
  Kubuntu 17.04
  Linux 4.13.2
  libvirt-bin 3.6.0
  qemu 2.10

  
  Guest:
  Kubuntu 16.04.3
  Linux 4.10.0-35-generic
  xserver-xorg-video-qxl 0.1.4-3ubuntu3
  xserver-common 1.18.4-0ubuntu0.3

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xserver-xorg (not installed)
  ProcVersionSignature: Ubuntu 4.10.0-35.39~16.04.1-generic 4.10.17
  Uname: Linux 4.10.0-35-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.10
  Architecture: amd64
  CurrentDesktop: KDE
  Date: Sat Sep 23 01:27:49 2017
  InstallationDate: Installed on 2016-09-16 (371 days ago)
  InstallationMedia: Kubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   Error: command ['journalctl', '-b', '--priority=warning', '--lines=1000'] 
failed with exit code 1: Hint: You are currently not seeing messages from other 
users and the system.
 Users in the 'systemd-journal' group can see all messages. Pass -q to
 turn off this notice.
   No journal files were opened due to insufficient permissions.
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1719038/+subscriptions

-- 
Mailing list: https://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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-06-05 Thread Julian Andres Klode
** Changed in: menu (Ubuntu Xenial)
   Status: New => In Progress

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Fix Committed
Status in apt source package in Xenial:
  New
Status in menu source package in Xenial:
  In Progress
Status in apt source package in Artful:
  New
Status in menu source package in Artful:
  New
Status in apt source package in Bionic:
  New
Status in menu source package in Bionic:
  New
Status in menu package in Debian:
  Unknown

Bug description:
  [Impact]
  Breaks some upgrades, depending on install order.

  [Test case]
  N/A. After consultation with the dpkg maintainer and investigating the 
situation, it's reasonably safe to assume that noawait is the right thing to do:

  * the intended use for the trigger is to run _after_ packages with .menu 
  files are configured, not before; therefore
  * the file trigger is triggered manually from the postinst again, discussion 
has been that the file trigger is not actually needed.

  [Regression potential]
  Menu might not be updated correctly

  [Original bug report]
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

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

-- 
Mailing list: https://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 1768905] Re: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency problems - leaving triggers unprocessed

2018-06-05 Thread Launchpad Bug Tracker
This bug was fixed in the package menu - 2.1.47ubuntu3

---
menu (2.1.47ubuntu3) cosmic; urgency=medium

  * Switch triggers to use noawait (LP: #1768905)

 -- Julian Andres Klode   Tue, 05 Jun 2018 10:48:23
-0700

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

Title:
  package menu 2.1.47ubuntu2 failed to install/upgrade: dependency
  problems - leaving triggers unprocessed

Status in apt package in Ubuntu:
  Incomplete
Status in menu package in Ubuntu:
  Fix Released
Status in apt source package in Xenial:
  New
Status in menu source package in Xenial:
  In Progress
Status in apt source package in Artful:
  New
Status in menu source package in Artful:
  New
Status in apt source package in Bionic:
  New
Status in menu source package in Bionic:
  New
Status in menu package in Debian:
  Unknown

Bug description:
  [Impact]
  Breaks some upgrades, depending on install order.

  [Test case]
  N/A. After consultation with the dpkg maintainer and investigating the 
situation, it's reasonably safe to assume that noawait is the right thing to do:

  * the intended use for the trigger is to run _after_ packages with .menu 
  files are configured, not before; therefore
  * the file trigger is triggered manually from the postinst again, discussion 
has been that the file trigger is not actually needed.

  [Regression potential]
  Menu might not be updated correctly

  [Original bug report]
  I get this error when I update to 18.04

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: menu 2.1.47ubuntu2
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  Date: Thu May  3 16:51:28 2018
  Dependencies:
   gcc-8-base 8-20180414-1ubuntu2
   libc6 2.27-3ubuntu1
   libgcc1 1:8-20180414-1ubuntu2
   libstdc++6 8-20180414-1ubuntu2
  ErrorMessage: dependency problems - leaving triggers unprocessed
  InstallationDate: Installed on 2018-04-11 (22 days ago)
  InstallationMedia: Ubuntu-MATE 17.10 "Artful Aardvark" - Release amd64 
(20180106)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: menu
  Title: package menu 2.1.47ubuntu2 failed to install/upgrade: dependency 
problems - leaving triggers unprocessed
  UpgradeStatus: Upgraded to bionic on 2018-05-03 (0 days ago)

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

-- 
Mailing list: https://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 1767331] Re: package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O pacote está num mau estado de inconsistência; deve reinstala-lo antes de tentar configura-lo.

2018-06-05 Thread Phillip Susi
** Package changed: util-linux (Ubuntu) => glib2.0 (Ubuntu)

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

Title:
  package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O
  pacote está num mau estado de inconsistência; deve  reinstala-lo antes
  de tentar configura-lo.

Status in glib2.0 package in Ubuntu:
  New

Bug description:
  i dont know

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: uuid-runtime 2.31.1-0.4ubuntu3
  ProcVersionSignature: Ubuntu 4.15.0-13.14-generic 4.15.10
  Uname: Linux 4.15.0-13-generic x86_64
  ApportVersion: 2.20.9-0ubuntu2
  Architecture: amd64
  Date: Fri Apr 27 07:46:33 2018
  ErrorMessage: O pacote está num mau estado de inconsistência; deve  
reinstala-lo antes de tentar configura-lo.
  InstallationDate: Installed on 2018-03-15 (43 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180314)
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /root/Error: command ['which', 'python'] failed with exit code 
1:, Error: [Errno 2] Arquivo ou diretório inexistente: "/root/Error: command 
['which', 'python'] failed with exit code 1:": "/root/Error: command ['which', 
'python'] failed with exit code 1:", unpackaged
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: util-linux
  Title: package uuid-runtime 2.31.1-0.4ubuntu3 failed to install/upgrade: O 
pacote está num mau estado de inconsistência; deve  reinstala-lo antes de 
tentar configura-lo.
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1768232] Re: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing

2018-06-05 Thread Christopher M. Penalver
** Description changed:

  My system stuck at ubuntu logo while booting. This issue occurred only
  after installing it, not when I choose 'Try without Installing'. This
  doesn't happen in 16.04.4.
  
  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*
  
  Output of sudo lshw -c display
  
  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d
  
  WORKAROUND: Using the following kernel boot parameter allows me to boot but 
the maximum resolution is limited to 1024x768:
  nomodeset
+ 
+ WORKAROUND: Edit the file /etc/gdm3/custom.conf and change:
+ #WaylandEnable=false
+ 
+ to:
+ WaylandEnable=false
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

Title:
  [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while
  booting after installing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My system stuck at ubuntu logo while booting. This issue occurred only
  after installing it, not when I choose 'Try without Installing'. This
  doesn't happen in 16.04.4.

  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     

[Touch-packages] [Bug 1768232] Re: [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while booting after installing

2018-06-05 Thread Christopher M. Penalver
d a i s y, to advise, the boot options in
https://wiki.ubuntu.com/DebuggingKernelBoot are so that you can provide
a screencast and/or log of a bad boot to root cause.

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

Title:
  [HP Compaq dx2080 Microtower PC] Stuck at Ubuntu 18.04 logo while
  booting after installing

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  My system stuck at ubuntu logo while booting. This issue occurred only
  after installing it, not when I choose 'Try without Installing'. This
  doesn't happen in 16.04.4.

  xrandr
  xrandr: Failed to get size of gamma for output default
  Screen 0: minimum 1024 x 768, current 1024 x 768, maximum 1024 x 768
  default connected primary 1024x768+0+0 0mm x 0mm
     1024x768  76.00*

  Output of sudo lshw -c display

  *-display UNCLAIMED
     description: VGA compatible controller
     product: 82945G/GZ Integrated Graphics Controller
     vendor: Intel Corporation
     physical id: 2
     bus info: pci@:00:02.0
     version: 02
     width: 32 bits
     clock: 33MHz
     capabilities: msi pm vga_controller bus_master cap_list
     configuration: latency=0
     resources: memory:e200-e207 ioport:c000(size=8) 
memory:d000-dfff memory:e208-e20b memory:c-d

  WORKAROUND: Using the following kernel boot parameter allows me to boot but 
the maximum resolution is limited to 1024x768:
  nomodeset

  WORKAROUND: Edit the file /etc/gdm3/custom.conf and change:
  #WaylandEnable=false

  to:
  WaylandEnable=false

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: xorg 1:7.7+19ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17
  Uname: Linux 4.15.0-20-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7
  Architecture: amd64
  BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
  CompositorRunning: None
  CurrentDesktop: ubuntu:GNOME
  Date: Tue May  1 17:16:20 2018
  DistUpgraded: Fresh install
  DistroCodename: bionic
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
     Subsystem: Hewlett-Packard Company 82945G/GZ Integrated Graphics 
Controller [103c:302a]
  InstallationDate: Installed on 2018-05-01 (0 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  MachineType: Hewlett-Packard HP dx2080 MT(KS826PA)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_IN
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic 
root=UUID=7ec4f610-9b62-44f3-867d-01abd93de14d ro quiet splash nomodeset 
vt.handoff=1
  Renderer: Software
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  XorgConf:
   Section "Device"
    Identifier "Intel Graphics"
    Driver "intel"
    Option "AccelMethod" "uxa"
   EndSection
  dmi.bios.date: 11/28/2007
  dmi.bios.vendor: Award Software International, Inc.
  dmi.bios.version: V1.03
  dmi.board.name: 0AD8h
  dmi.board.vendor: Board Manufacturer
  dmi.chassis.asset.tag: INA8100LFY
  dmi.chassis.type: 3
  dmi.chassis.vendor: Hewlett-Packard
  dmi.modalias: 
dmi:bvnAwardSoftwareInternational,Inc.:bvrV1.03:bd11/28/2007:svnHewlett-Packard:pnHPdx2080MT(KS826PA):pvr:rvnBoardManufacturer:rn0AD8h:rvr:cvnHewlett-Packard:ct3:cvr:
  dmi.product.name: HP dx2080 MT(KS826PA)
  dmi.sys.vendor: Hewlett-Packard
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.91+git1804271336.50426f~oibaf~b
  version.libgl1-mesa-dri: libgl1-mesa-dri 18.2~git1804301930.1c5f4f~oibaf~b
  version.libgl1-mesa-glx: libgl1-mesa-glx 18.2~git1804301930.1c5f4f~oibaf~b
  version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20171229-1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2

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

-- 
Mailing list: https://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 1767143] Re: package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2018-06-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package ifupdown 0.8.10ubuntu1.3 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in ifupdown package in Ubuntu:
  Confirmed

Bug description:
  error

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: ifupdown 0.8.10ubuntu1.3
  ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-lowlatency 4.13.16
  Uname: Linux 4.13.0-39-lowlatency x86_64
  ApportVersion: 2.20.1-0ubuntu2.16
  Architecture: amd64
  Date: Thu Apr 26 17:27:57 2018
  DuplicateSignature:
   package:ifupdown:0.8.10ubuntu1.3
   Setting up ubuntu-make (17.03~xenial1) ...
   /var/lib/dpkg/info/ubuntu-make.postinst: 6: 
/var/lib/dpkg/info/ubuntu-make.postinst: register-python-argcomplete3: not found
   dpkg: error processing package ubuntu-make (--configure):
subprocess installed post-installation script returned error exit status 127
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2018-04-01 (24 days ago)
  InstallationMedia: Ubuntu-Studio 16.04.3 LTS "Xenial Xerus" - Release amd64 
(20170801)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: ifupdown
  Title: package ifupdown 0.8.10ubuntu1.3 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/ifupdown/+bug/1767143/+subscriptions

-- 
Mailing list: https://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 1772386] Re: message - Low Graphics mode - about 2/3 of startups - not all

2018-06-05 Thread Christopher M. Penalver
Roger Davis, could you please provide undo the WORKAROUND, and provide
the missing information from https://wiki.ubuntu.com/DebuggingKernelBoot
?

** Description changed:

  After a recent update (kernel?), I have begun to occasionally receive
  the message "Running in Low Graphics Mode" at boot (maybe half the
  time). I can tell it to use Default setting from the options it offers,
  and get by it, after which things look and work normally until a reboot,
  which may or may not occur correctly.
  
  I also usually get "System error detected, Report? at the same time, so
  I agree to report it.
  
- Please note that I'm using 16.04 (fully updated), Gnome Flashback
- Metacity, with [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / R7 250E]
- . This problem shows up no matter which of the above I'm using, or
- Unity.
- 
- roger@roger-desktop:~$ uname -a
- Linux roger-desktop 4.4.0-124-generic #148-Ubuntu SMP Wed May 2 13:00:18 UTC 
2018 x86_64 x86_64 x86_64 GNU/Linux
+ This problem shows up using GNOME Flashback or Unity.
  
  roger@roger-desktop:~$ free -m
  total used free shared buff/cache available
  Mem: 16013 3880 10410 363 1722 11443
  Swap: 16348 0 16348
  
  roger@roger-desktop:~$ df -h
  Filesystem Size Used Avail Use% Mounted on
  udev 7.8G 0 7.8G 0% /dev
  tmpfs 1.6G 9.6M 1.6G 1% /run
  /dev/sda1 902G 77G 779G 9% /
  tmpfs 7.9G 127M 7.7G 2% /dev/shm
  tmpfs 5.0M 4.0K 5.0M 1% /run/lock
  tmpfs 7.9G 0 7.9G 0% /sys/fs/cgroup
  cgmfs 100K 0 100K 0% /run/cgmanager/fs
  tmpfs 1.6G 52K 1.6G 1% /run/user/1000
  
- I have found a WORK-AROUND. Using x-diagnose, I selected all options
- under both Debug and Workarounds.  After this, all works normally every
- time.  However, I take this as a crutch, not a fix, and think other
- action should be taken
- 
- Selecting "View Errors" shows no errors, so I never tried reporting from
- that point.
- 
- This gives me a presumption that there is a bug in coding that interacts
- badly with my system and a few others like it, which I encountered in my
- search for a solution.
- 
- Also, if I simply go to 18.04 (I don't really want to just yet.) will it
- likely fix this or might this block or damage the upgrade?
- 
- 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> 
About Ubuntu
- roger@roger-desktop:~$ lsb_release -rd
- Description:  Ubuntu 16.04.4 LTS
- Release:  16.04
- 
- 2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center
- roger@roger-desktop:~$ apt-cache policy pkgname
- N: Unable to locate package pkgname
- ALSO - I'm unable to locate this information in Software Center
- 
- 3) What you expected to happen
- Normal boot, no errors or problems
- 
- 4) What happened instead
- "Running in Low Graphics Mode" displayed, along with subsequent "System Error 
Detected" messages
+ WORKAROUND: Using x-diagnose, I selected all options under both Debug
+ and Workarounds.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-124.148-generic 4.4.117
  Uname: Linux 4.4.0-124-generic x86_64
  .tmp.unity_support_test.0:
-  
+ 
  ApportVersion: 2.20.1-0ubuntu2.17
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon May 21 01:56:23 2018
  DistUpgraded: 2016-12-17 18:57:41,412 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
-  Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
-Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
+  Advanced Micro Devices, Inc. [AMD/ATI] Cape Verde PRO [Radeon HD 7750/8740 / 
R7 250E] [1002:683f] (prog-if 00 [VGA controller])
+    Subsystem: PC Partner Limited / Sapphire Technology Cape Verde PRO [Radeon 
HD 7750/8740 / R7 250E] [174b:e213]
  InstallationDate: Installed on 2014-07-07 (1413 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-124-generic 
root=UUID=3d311d21-7c70-432e-a4ac-d9dd4986a2b5 ro plymouth:debug drm.debug=0xe 
nopat vesafb.invalid=1
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: Upgraded to xenial on 2016-12-18 (519 days ago)
  dmi.bios.date: 02/08/2012
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: BHZ7710H.86A.0057.2012.0208.1904
  dmi.board.name: DZ77BH-55K
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAG39008-400
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrBHZ7710H.86A.0057.2012.0208.1904:bd02/08/2012:svn:pn:pvr:rvnIntelCorporation:rnDZ77BH-55K:rvrAAG39008-400:cvn:ct3:cvr:
  version.compiz: compiz 1:0.9.12.3+16.04.20180221-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  

[Touch-packages] [Bug 1775307] [NEW] Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1 version

2018-06-05 Thread Balint Reczey
Public bug reported:

...
adjusting candidate version: zfs-initramfs=0.7.5-1ubuntu15
adjusting candidate version: zfs-test=0.7.5-1ubuntu15
adjusting candidate version: zfs-zed=0.7.5-1ubuntu15
adjusting candidate version: zfsutils-linux=0.7.5-1ubuntu15
Traceback (most recent call last):
  File "/usr/bin/unattended-upgrade", line 1928, in 
sys.exit(main(options))
  File "/usr/bin/unattended-upgrade", line 1554, in main
allowed_origins=allowed_origins)
  File "/usr/bin/unattended-upgrade", line 122, in __init__
apt.Cache.__init__(self, rootdir=rootdir)
  File "/usr/lib/python3/dist-packages/apt/cache.py", line 130, in __init__
self.open(progress)
  File "/usr/bin/unattended-upgrade", line 152, in open
self.adjust_candidates()
  File "/usr/bin/unattended-upgrade", line 161, in adjust_candidates
for pkgname, candidate in self._get_candidates_to_adjust():
ValueError: too many values to unpack (expected 2)

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

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

Title:
  Unattended-upgrades crashes in adjusting candidates in 1.2ubuntu1
  version

Status in unattended-upgrades package in Ubuntu:
  New

Bug description:
  ...
  adjusting candidate version: zfs-initramfs=0.7.5-1ubuntu15
  adjusting candidate version: zfs-test=0.7.5-1ubuntu15
  adjusting candidate version: zfs-zed=0.7.5-1ubuntu15
  adjusting candidate version: zfsutils-linux=0.7.5-1ubuntu15
  Traceback (most recent call last):
File "/usr/bin/unattended-upgrade", line 1928, in 
  sys.exit(main(options))
File "/usr/bin/unattended-upgrade", line 1554, in main
  allowed_origins=allowed_origins)
File "/usr/bin/unattended-upgrade", line 122, in __init__
  apt.Cache.__init__(self, rootdir=rootdir)
File "/usr/lib/python3/dist-packages/apt/cache.py", line 130, in __init__
  self.open(progress)
File "/usr/bin/unattended-upgrade", line 152, in open
  self.adjust_candidates()
File "/usr/bin/unattended-upgrade", line 161, in adjust_candidates
  for pkgname, candidate in self._get_candidates_to_adjust():
  ValueError: too many values to unpack (expected 2)

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

-- 
Mailing list: https://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 1769682] Re: NFS-based remote root hangs when running 'netplan apply'

2018-06-05 Thread Launchpad Bug Tracker
This bug was fixed in the package nplan - 0.32~17.10.4

---
nplan (0.32~17.10.4) artful; urgency=medium

  * bond/bridge: Support suffixes for time-based values so things like
"mii-monitor-interval" can support milliseconds. (LP: #1745597)
  * debian/postinst: Write breadcrumbs on disk in /etc/network/interfaces to
denote the migration to using netplan. (LP: #1756742)
  * DHCPv4: add a "dhcp-identifier: mac" field that can be set to fix interop
with Windows Server-based DHCP servers which don't support RFC 4361.
(LP: #1738998)
  * IPv6: accept-ra should default to being unset, so that the kernel default
can be used. (LP: #1732002)
  * doc/netplan.md: Clarify the behavior for time-based values for bonds
and bridges. (LP: #1756587)
  * critical: provide a way to set "CriticalConnection=true" on a networkd
connection, especially for remote-fs scenarios. (LP: #1769682)
  * networkd: don't wipe out /run/netplan on generate: we do want to keep any
YAML configurations in that directory, we just need to remove generated
wpasupplicant configs. (LP: #1764869)

 -- Mathieu Trudel-Lapierre   Tue, 08 May 2018
11:04:30 -0400

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

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

Title:
  NFS-based remote root hangs when running 'netplan apply'

Status in initramfs-tools package in Ubuntu:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Invalid
Status in initramfs-tools source package in Xenial:
  Confirmed
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Released
Status in initramfs-tools source package in Artful:
  Confirmed
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Fix Released
Status in initramfs-tools source package in Bionic:
  Confirmed
Status in netplan.io source package in Bionic:
  Fix Committed
Status in nplan source package in Bionic:
  Invalid

Bug description:
  [Impact]
  Netboot users with a remote filesystem over NFS (possibly over other 
networked filesystems).

  [Test cases]
  1) Boot a system with its root filesystem over NFS.
  2) Run 'sudo netplan apply'
  3) Validate that the system remains responsive and keeps connectivity over 
the same IP address  as it had.

  [Regression potential]
  This SRU changes network properties, and enforces that networkd does not 
release and re-request an IP address from DHCP when it is restarted. 
Environments relying on the IP release/renew behavior may find themselves 
staying on the previous IP address, which might negatively impact connectivity. 
Changes in connectivity on a system running netplan should be investigated as a 
potential regression from this SRU. Other regression possibilities would 
include failure to get a new IP address over time (usually seen as losing 
connectivity) or possible IP conflicts on a network.

  ---

  With a system booted on the network, with its remote root fs on NFS:

  Running 'netplan apply' restarts systemd-networkd, which releases the
  IP received from DHCP. With no IP (and and IP potentially changing),
  the NFS server can't be reached so the system hangs.

  'netplan apply' or restarting systemd-networkd should not affect teh
  system, it should continue working normally despite "changing" network
  states, as long as the effective IP remains the same.

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

-- 
Mailing list: https://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 1756322] Re: 'netplan apply' fails when trying to activate another interface on another QETH device ...

2018-06-05 Thread Launchpad Bug Tracker
This bug was fixed in the package nplan - 0.32~16.04.5

---
nplan (0.32~16.04.5) xenial; urgency=medium

  * bond/bridge: Support suffixes for time-based values so things like
"mii-monitor-interval" can support milliseconds. (LP: #1745597)
  * Do not attempt to rebind driver 'qeth'. (LP: #1756322)
  * Allow setting ClientIdentifier=mac for networkd-renderered devices
(LP: #1738998)
  * IPv6: accept-ra should default to being unset, so that the kernel default
can be used. (LP: #1732002)
  * doc/netplan.md: Clarify the behavior for time-based values for bonds
and bridges. (LP: #1756587)
  * critical: provide a way to set "CriticalConnection=true" on a networkd
connection, especially for remote-fs scenarios. (LP: #1769682)
  * networkd: don't wipe out /run/netplan on generate: we do want to keep any
YAML configurations in that directory, we just need to remove generated
wpasupplicant configs. (LP: #1764869)

 -- Mathieu Trudel-Lapierre   Tue, 08 May 2018
10:36:24 -0400

** Changed in: nplan (Ubuntu Xenial)
   Status: Fix Committed => 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/1756322

Title:
  'netplan apply' fails when trying to activate another interface on
  another QETH device ...

Status in netplan:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Won't Fix
Status in systemd source package in Artful:
  Invalid

Bug description:
  [Impact]
  Server users on s390x configuring qeth devices.

  [Test case]
  1) Reconfigure an interface for a QETH device
  2) Verify that 'netplan apply' completes successfully, without error.

  [Regression potential]
  This change has minimal potential for regression, and it only skip qeth-based 
devices from "replugging", which "disconnects" them by unbinding and rebinding 
the driver. Potential issues would be limited to failure to rename interfaces 
without a reboot, for configurations that depend on this (but it already would 
not have worked due to netplan apply failing to rebind the device).

  ---

  When trying to add another interface for a QETH device on a s390x
  system netplan apply fails:

  sudo netplan apply
  Cannot replug encc003: [Errno 19] No such device
  Traceback (most recent call last):
    File "/usr/sbin/netplan", line 23, in 
  netplan.main()
    File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 40, in run
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 87, in 
command_apply
  stdout=fd, stderr=fd)
    File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 
'net_setup_link', '/sys/class/net/encc003']' returned non-zero exit status 4.

  It seems like rebinding of qeth devices is not allowed.
  With qeth devices, I guess one needs to "offline & online" them...
  Or like unbind a whole group of them, as there are three of them per 
interface.

  ubuntu@s1lp14:/sys/class/net/encc006/device$ ls -latr
  total 0
  drwxr-xr-x 5 root root0 Mar 16 02:06 ..
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 uevent
  drwxr-xr-x 6 root root0 Mar 16 13:44 .
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 online
  lrwxrwxrwx 1 root root0 Mar 16 13:44 subsystem -> ../../../bus/ccwgroup
  lrwxrwxrwx 1 root root0 Mar 16 13:44 driver -> 
../../../bus/ccwgroup/drivers/qeth
  drwxr-xr-x 2 root root0 Mar 16 13:44 vnicc
  --w--- 1 root root 4096 Mar 16 13:44 recover
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 priority_queueing
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portno
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portname
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 performance_stats
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 layer2
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 isolation
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 hw_trap
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev2 -> ../../css0/0.0.0bb4/0.0.c008
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev1 -> ../../css0/0.0.0bb3/0.0.c007
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev0 -> ../../css0/0.0.0bb2/0.0.c006
  -rw-r--r-- 

[Touch-packages] [Bug 1756322] Update Released

2018-06-05 Thread Chris Halse Rogers
The verification of the Stable Release Update for nplan has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  'netplan apply' fails when trying to activate another interface on
  another QETH device ...

Status in netplan:
  Fix Released
Status in Ubuntu on IBM z Systems:
  Fix Released
Status in netplan.io package in Ubuntu:
  Fix Released
Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  Invalid
Status in netplan.io source package in Xenial:
  Invalid
Status in nplan source package in Xenial:
  Fix Released
Status in systemd source package in Xenial:
  Invalid
Status in netplan.io source package in Artful:
  Invalid
Status in nplan source package in Artful:
  Won't Fix
Status in systemd source package in Artful:
  Invalid

Bug description:
  [Impact]
  Server users on s390x configuring qeth devices.

  [Test case]
  1) Reconfigure an interface for a QETH device
  2) Verify that 'netplan apply' completes successfully, without error.

  [Regression potential]
  This change has minimal potential for regression, and it only skip qeth-based 
devices from "replugging", which "disconnects" them by unbinding and rebinding 
the driver. Potential issues would be limited to failure to rename interfaces 
without a reboot, for configurations that depend on this (but it already would 
not have worked due to netplan apply failing to rebind the device).

  ---

  When trying to add another interface for a QETH device on a s390x
  system netplan apply fails:

  sudo netplan apply
  Cannot replug encc003: [Errno 19] No such device
  Traceback (most recent call last):
    File "/usr/sbin/netplan", line 23, in 
  netplan.main()
    File "/usr/share/netplan/netplan/cli/core.py", line 50, in main
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 40, in run
  self.run_command()
    File "/usr/share/netplan/netplan/cli/utils.py", line 110, in run_command
  self.func()
    File "/usr/share/netplan/netplan/cli/commands/apply.py", line 87, in 
command_apply
  stdout=fd, stderr=fd)
    File "/usr/lib/python3.6/subprocess.py", line 291, in check_call
  raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['udevadm', 'test-builtin', 
'net_setup_link', '/sys/class/net/encc003']' returned non-zero exit status 4.

  It seems like rebinding of qeth devices is not allowed.
  With qeth devices, I guess one needs to "offline & online" them...
  Or like unbind a whole group of them, as there are three of them per 
interface.

  ubuntu@s1lp14:/sys/class/net/encc006/device$ ls -latr
  total 0
  drwxr-xr-x 5 root root0 Mar 16 02:06 ..
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 uevent
  drwxr-xr-x 6 root root0 Mar 16 13:44 .
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 online
  lrwxrwxrwx 1 root root0 Mar 16 13:44 subsystem -> ../../../bus/ccwgroup
  lrwxrwxrwx 1 root root0 Mar 16 13:44 driver -> 
../../../bus/ccwgroup/drivers/qeth
  drwxr-xr-x 2 root root0 Mar 16 13:44 vnicc
  --w--- 1 root root 4096 Mar 16 13:44 recover
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 priority_queueing
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portno
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 portname
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 performance_stats
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 layer2
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 isolation
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 hw_trap
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev2 -> ../../css0/0.0.0bb4/0.0.c008
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev1 -> ../../css0/0.0.0bb3/0.0.c007
  lrwxrwxrwx 1 root root0 Mar 16 13:44 cdev0 -> ../../css0/0.0.0bb2/0.0.c006
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 buffer_count
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_role
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_reflect_promisc
  -rw-r--r-- 1 root root 4096 Mar 16 13:44 bridge_hostnotify
  --w--- 1 root root 4096 Mar 16 13:50 ungroup
  -r--r--r-- 1 root root 4096 Mar 16 13:50 switch_attrs
  -r--r--r-- 1 root root 4096 Mar 16 13:50 state
  drwxr-xr-x 2 root root0 Mar 16 13:50 power
  -r--r--r-- 1 root root 4096 Mar 16 13:50 inbuf_size
  -r--r--r-- 1 root root 4096 Mar 16 13:50 if_name
  -r--r--r-- 1 root root 4096 Mar 16 13:50 chpid
  -r--r--r-- 1 root root 4096 Mar 16 13:50 card_type
  

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

2018-06-05 Thread Launchpad Bug Tracker
This bug was fixed in the package nplan - 0.32~17.10.4

---
nplan (0.32~17.10.4) artful; urgency=medium

  * bond/bridge: Support suffixes for time-based values so things like
"mii-monitor-interval" can support milliseconds. (LP: #1745597)
  * debian/postinst: Write breadcrumbs on disk in /etc/network/interfaces to
denote the migration to using netplan. (LP: #1756742)
  * DHCPv4: add a "dhcp-identifier: mac" field that can be set to fix interop
with Windows Server-based DHCP servers which don't support RFC 4361.
(LP: #1738998)
  * IPv6: accept-ra should default to being unset, so that the kernel default
can be used. (LP: #1732002)
  * doc/netplan.md: Clarify the behavior for time-based values for bonds
and bridges. (LP: #1756587)
  * critical: provide a way to set "CriticalConnection=true" on a networkd
connection, especially for remote-fs scenarios. (LP: #1769682)
  * networkd: don't wipe out /run/netplan on generate: we do want to keep any
YAML configurations in that directory, we just need to remove generated
wpasupplicant configs. (LP: #1764869)

 -- Mathieu Trudel-Lapierre   Tue, 08 May 2018
11:04:30 -0400

** Changed in: nplan (Ubuntu Artful)
   Status: Fix Committed => 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/1732002

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in nplan source package in Xenial:
  Fix Released
Status in nplan source package in Artful:
  Fix Released

Bug description:
  [Impact]
  All users of netplan.

  [Test case]

  == LXD containers ==
  1) Start an LXD container (artful or bionic)
  2) Verify that an IPv6 address is present
  3) Verify that the system is brought up in a reasonable time (does not wait 2 
minutes to be reachable).

  == servers / cloud instances ==
  1) Start a bionic system, with no IPv6 connectivity (no router to advertise a 
prefix)
  2) Verify that the system boots quickly (does not wait 2 minutes to be 
reachable).

  [Regression potential]
  Since this changes default IPv6 behavior, care should be taken to validate 
that systems are maintaining IPv6 connectivity when it is available, and 
similarly that systems where no IPv6 connectivity is available on the network 
are behaving correctly: there should not be long boot delays, and no extra IPv6 
addresses aside from link-local addresses generated by the kernel.

  --

  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
     lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
    name: eth0
    subnets:
    - type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
    

[Touch-packages] [Bug 1732002] Update Released

2018-06-05 Thread Chris Halse Rogers
The verification of the Stable Release Update for nplan has completed
successfully and the package has now been released to -updates.
Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report.  In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.

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

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in nplan source package in Xenial:
  Fix Released
Status in nplan source package in Artful:
  Fix Released

Bug description:
  [Impact]
  All users of netplan.

  [Test case]

  == LXD containers ==
  1) Start an LXD container (artful or bionic)
  2) Verify that an IPv6 address is present
  3) Verify that the system is brought up in a reasonable time (does not wait 2 
minutes to be reachable).

  == servers / cloud instances ==
  1) Start a bionic system, with no IPv6 connectivity (no router to advertise a 
prefix)
  2) Verify that the system boots quickly (does not wait 2 minutes to be 
reachable).

  [Regression potential]
  Since this changes default IPv6 behavior, care should be taken to validate 
that systems are maintaining IPv6 connectivity when it is available, and 
similarly that systems where no IPv6 connectivity is available on the network 
are behaving correctly: there should not be long boot delays, and no extra IPv6 
addresses aside from link-local addresses generated by the kernel.

  --

  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
     lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
    name: eth0
    subnets:
    - type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  [Match]
  Name=eth0

  [Network]
  DHCP=ipv4

  [DHCP]
  UseMTU=true
  RouteMetric=100

  $ lxc exec bionic-demo  -- systemctl status --no-pager --full systemd-networkd
  ● systemd-networkd.service - Network Service
     Loaded: loaded (/lib/systemd/system/systemd-networkd.service; enabled; 
vendor preset: enabled)
     Active: active (running) since Mon 2017-11-13 18:37:34 UTC; 8min ago
   Docs: man:systemd-networkd.service(8)
   Main PID: 118 (systemd-network)
     Status: "Processing requests..."
  Tasks: 1 (limit: 4915)
     Memory: 2.0M
    CPU: 19ms
     CGroup: /system.slice/systemd-networkd.service
     └─118 

[Touch-packages] [Bug 1732002] Re: cloud images in lxc get ipv6 address

2018-06-05 Thread Launchpad Bug Tracker
This bug was fixed in the package nplan - 0.32~16.04.5

---
nplan (0.32~16.04.5) xenial; urgency=medium

  * bond/bridge: Support suffixes for time-based values so things like
"mii-monitor-interval" can support milliseconds. (LP: #1745597)
  * Do not attempt to rebind driver 'qeth'. (LP: #1756322)
  * Allow setting ClientIdentifier=mac for networkd-renderered devices
(LP: #1738998)
  * IPv6: accept-ra should default to being unset, so that the kernel default
can be used. (LP: #1732002)
  * doc/netplan.md: Clarify the behavior for time-based values for bonds
and bridges. (LP: #1756587)
  * critical: provide a way to set "CriticalConnection=true" on a networkd
connection, especially for remote-fs scenarios. (LP: #1769682)
  * networkd: don't wipe out /run/netplan on generate: we do want to keep any
YAML configurations in that directory, we just need to remove generated
wpasupplicant configs. (LP: #1764869)

 -- Mathieu Trudel-Lapierre   Tue, 08 May 2018
10:36:24 -0400

** Changed in: nplan (Ubuntu Xenial)
   Status: Fix Committed => 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/1732002

Title:
  cloud images in lxc get ipv6 address

Status in nplan package in Ubuntu:
  Fix Released
Status in systemd package in Ubuntu:
  New
Status in nplan source package in Xenial:
  Fix Released
Status in nplan source package in Artful:
  Fix Released

Bug description:
  [Impact]
  All users of netplan.

  [Test case]

  == LXD containers ==
  1) Start an LXD container (artful or bionic)
  2) Verify that an IPv6 address is present
  3) Verify that the system is brought up in a reasonable time (does not wait 2 
minutes to be reachable).

  == servers / cloud instances ==
  1) Start a bionic system, with no IPv6 connectivity (no router to advertise a 
prefix)
  2) Verify that the system boots quickly (does not wait 2 minutes to be 
reachable).

  [Regression potential]
  Since this changes default IPv6 behavior, care should be taken to validate 
that systems are maintaining IPv6 connectivity when it is available, and 
similarly that systems where no IPv6 connectivity is available on the network 
are behaving correctly: there should not be long boot delays, and no extra IPv6 
addresses aside from link-local addresses generated by the kernel.

  --

  I noticed that lxd (lxc list) reports that an lxc container has an
  ipv6 address in artful or bionic.  It does not list this in xenial or
  zesty.  I suspect this change occurred in the switch over to
  netplan/networkd.

  This may at first seem harmless or even desired, but note that the
  user configuration did not request ipv6 config, so its presence is a
  bug.

  $ for rel in xenial zesty artful bionic; do
     lxc launch ubuntu-daily:$rel $rel-demo; done
  Creating xenial-demo
  Starting xenial-demo
  ..
  Creating bionic-demo
  Starting bionic-demo

  $ sleep 10
  $ lxc list
  $ lxc list
  
+-+-+--+++---+
  |NAME |  STATE  | IPV4 |  IPV6
  |TYPE| SNAPSHOTS |
  
+-+-+--+++---+
  | artful-demo | RUNNING | 10.75.205.208 (eth0) | 
fd42:eee5:7c43:3d62:3a42:611c:3f6f:1184 (eth0) | PERSISTENT | 0 |
  
+-+-+--+++---+
  | bionic-demo | RUNNING | 10.75.205.187 (eth0) | 
fd42:eee5:7c43:3d62:6f4:155b:39cc:fc3d (eth0)  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | xenial-demo | RUNNING | 10.75.205.143 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+
  | zesty-demo  | RUNNING | 10.75.205.123 (eth0) |  
  | PERSISTENT | 0 |
  
+-+-+--+++---+

  ## Here is the config that was provided by lxd
  $ lxc exec bionic-demo cat /var/lib/cloud/seed/nocloud-net/network-config
  version: 1
  config:
  - type: physical
    name: eth0
    subnets:
    - type: dhcp
  control: auto

  ## Here is the config that cloud-init rendered.
  $ lxc exec bionic-demo -- grep -v '^#' /etc/netplan/50-cloud-init.yaml
  network:
  version: 2
  ethernets:
  eth0:
  dhcp4: true

  $ lxc exec bionic-demo cat /run/systemd/network/10-netplan-eth0.network
  

[Touch-packages] [Bug 1774979] Re: no input and output devices detected in sound definitions

2018-06-05 Thread Daniel van Vugt
** Changed in: pulseaudio (Ubuntu)
   Status: Incomplete => Invalid

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

Title:
  no input and output devices detected in sound definitions

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  After installing pulse audio equalizer, it worked good. everything was
  detected in Sound Definitions and there was sound in the headphone
  out.

  In the day after, every input and output devices were gone in Sound
  Definition. I uninstalled pulse audio equalizer but nothing happened
  in Sound Definitions, everything was gone.

  I rebooted the system and nothing. No sound.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.10
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic i686
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: i386
  AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', 
'/dev/snd/hwC0D1', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D6c', '/dev/snd/pcmC0D6p', 
'/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', 
'/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1:
  CurrentDesktop: Unity
  Date: Mon Jun  4 12:35:32 2018
  InstallationDate: Installed on 2018-01-04 (150 days ago)
  InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release i386 (20170801)
  ProcEnviron:
   LANGUAGE=pt:pt_BR:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=pt_PT.UTF-8
   SHELL=/bin/bash
  PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No 
PulseAudio daemon running, or not running as session daemon.
  SourcePackage: pulseaudio
  Symptom: audio
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/15/2006
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: A6FAS.212
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: A6F
  dmi.board.vendor: ASUSTeK Computer Inc.
  dmi.board.version: 1.0
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK Computer Inc.
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrA6FAS.212:bd05/15/2006:svnASUSTeKComputerInc.:pnA6F:pvr1.0:rvnASUSTeKComputerInc.:rnA6F:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr:
  dmi.product.family: To Be Filled By O.E.M.
  dmi.product.name: A6F
  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/pulseaudio/+bug/1774979/+subscriptions

-- 
Mailing list: https://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 1774640] Re: Bluetooth turns off automatically Ubuntu 18.04 LTS

2018-06-05 Thread Daniel van Vugt
** Changed in: bluez (Ubuntu)
   Status: Incomplete => New

** Tags added: a2dp

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

Title:
  Bluetooth turns off automatically Ubuntu 18.04 LTS

Status in bluez package in Ubuntu:
  New

Bug description:
  Whenever I start up my laptop and connect my JBL-speaker, the device stays 
connected. However, when I turn de speaker off, and try to reconnect to the 
speaker, the Bluetooth automatically turns off. I then need to restart my 
laptop and then only Bluetooth works again.
  --- 
  ApportVersion: 2.20.9-0ubuntu7.1
  Architecture: amd64
  CurrentDesktop: Unity:Unity7:ubuntu
  DistroRelease: Ubuntu 18.04
  InstallationDate: Installed on 2018-04-27 (39 days ago)
  InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426)
  InterestingModules: rfcomm bnep btusb bluetooth
  Lsusb:
   Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
   Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card 
Reader Controller
   Bus 001 Device 003: ID 0bda:57b5 Realtek Semiconductor Corp. 
   Bus 001 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth 
Dongle (HCI mode)
   Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  MachineType: ASUSTeK COMPUTER INC. X555LAB
  Package: bluez 5.48-0ubuntu3
  PackageArchitecture: amd64
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-22-generic 
root=UUID=2c696fdd-83b4-4daf-b864-3c9a68f8c2dc ro quiet splash vt.handoff=1
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Tags:  bionic
  Uname: Linux 4.15.0-22-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 08/04/2015
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: X555LAB.503
  dmi.board.asset.tag: ATN12345678901234567
  dmi.board.name: X555LAB
  dmi.board.vendor: ASUSTeK COMPUTER INC.
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: ATN12345678901234567
  dmi.chassis.type: 10
  dmi.chassis.vendor: ASUSTeK COMPUTER INC.
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrX555LAB.503:bd08/04/2015:svnASUSTeKCOMPUTERINC.:pnX555LAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX555LAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:
  dmi.product.family: X
  dmi.product.name: X555LAB
  dmi.product.version: 1.0
  dmi.sys.vendor: ASUSTeK COMPUTER INC.
  hciconfig:
   hci0:Type: Primary  Bus: USB
BD Address: 00:1A:7D:DA:71:0A  ACL MTU: 310:10  SCO MTU: 64:8
UP RUNNING PSCAN 
RX bytes:55347 acl:67 sco:0 events:7591 errors:0
TX bytes:4599486 acl:14880 sco:0 commands:100 errors:0

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

-- 
Mailing list: https://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 1772542] Re: after waking from sleep i get text radeon error message then return login screen

2018-06-05 Thread Christopher M. Penalver
Chris Guiver, to confirm a WORKAROUND, if you uninstall both light-
locker and caffeine simultaneously, is a crash still reproducible?

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

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

Title:
  after waking from sleep i get text radeon error message then return
  login screen

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  my box is 18.04 (was 17.10 installed; standard Ubuntu with MATE & XFCE
  desktops added)

  I sleep my XFCE (xubuntu) machine rather than turning it off at night.

  Today as with yesterday morning, instead of getting the locker-screen
  after hitting the power-button to wake my machine, i get a blank
  screen with a RADEON two-line text message top left on screen which
  appear only momentarily as screen is erased and I get the
  login/greeter screen.

  (it's happened 4-5 times, but does NOT happen every time)

  I can login fine, but my xfce session is new.

  I have grep'd for the message I see (yesterday & today), but can't
  find it as i usually recall little but the radeon word...

  sudo lshw -C video
    *-display
     description: VGA compatible controller
     product: Cedar [Radeon HD 5000/6000/7350/8350 Series]
     vendor: Advanced Micro Devices, Inc. [AMD/ATI]
     physical id: 0
     bus info: pci@:01:00.0
     version: 00
     width: 64 bits
     clock: 33MHz
     capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
     configuration: driver=radeon latency=0
     resources: irq:30 memory:e000-efff memory:f7de-f7df 
ioport:dc00(size=256) memory:c-d

  guiverc@d960-ubu2:/var/crash$   pwd
  /var/crash
  guiverc@d960-ubu2:/var/crash$   ls -la
  total 35332
  drwxrwsrwt  2 rootwhoopsie 4096 May 22 09:41 .
  drwxr-xr-x 15 rootroot 4096 Nov 16  2017 ..
  -rw-r-  1 guiverc whoopsie50003 May 21 10:32 
_usr_bin_caffeine.1000.crash
  -rw-r-  1 guiverc whoopsie   880121 May 21 10:33 
_usr_bin_light-locker.1000.crash
  -rw-rw-r--  1 guiverc whoopsie0 May 21 10:33 
_usr_bin_light-locker.1000.upload
  -rw-r-  1 guiverc whoopsie 35234566 May 21 10:32 
_usr_lib_xorg_Xorg.1000.crash
  (these files are dated yesteday - i didn't find anything for today)

  extract of /var/log/auth.log  (copied from `view` hence line numbers)
  // last-night
   48 May 21 19:35:10 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   49 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   50 May 21 19:55:52 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   51 May 21 19:56:16 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
  // overnight
   52 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
opened for user root by (uid=0)
   53 May 21 20:17:01 d960-ubu2 CRON[31879]: pam_unix(cron:session): session 
closed for user root
   54 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   55 May 21 20:34:20 d960-ubu2 gnome-keyring-daemon[16355]: asked to register 
item /org/freedesktop/secrets/collection/login/1, but it's already registered
   56 May 21 20:34:45 d960-ubu2 dbus-daemon[1112]: [system] Failed to activate 
service 'org.bluez': timed out (service_start_timeout=25000ms)
   57 May 22 09:36:23 d960-ubu2 systemd-logind[1108]: Operation 'sleep' 
finished.
   58 May 22 09:36:24 d960-ubu2 gdm-password]: pam_unix(gdm-password:session): 
session closed for user guiverc
   59 May 22 09:36:24 d960-ubu2 sudo: pam_unix(sudo:session): session closed 
for user root
   60 May 22 09:36:26 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   61 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   62 May 22 09:36:26 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   63 May 22 09:36:26 d960-ubu2 dbus-daemon[1112]: [system] Rejected send 
message, 2 matched rules; type="method_call", sender=":1.1659" (uid=1000 
pid=5442 comm="/usr/bin/pulseaudio --start --log-target=syslog " 
label="unconfined") interface="org.freedesktop.DBus.ObjectManager" 
member="GetManagedObjects" error name="(unset)" requested_reply="0" 
destination="org.bluez" (bus)
   64 May 22 09:36:27 d960-ubu2 sshd[1276]: Received SIGHUP; restarting.
   65 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on 0.0.0.0 port 22.
   66 May 22 09:36:27 d960-ubu2 sshd[1276]: Server listening on :: port 22.
   67 May 22 09:36:29 d960-ubu2 

[Touch-packages] [Bug 1775187] Re: bluetooth headset gets imitatively disconnected

2018-06-05 Thread Daniel van Vugt
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please execute the following command only once, as it
will automatically gather debugging information, in a terminal:

apport-collect 1775187

When reporting bugs in the future please use apport by using 'ubuntu-
bug' and the name of the package affected. You can learn more about this
functionality at https://wiki.ubuntu.com/ReportingBugs.

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

** Tags added: a2dp

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

Title:
  bluetooth headset gets imitatively disconnected

Status in bluez package in Ubuntu:
  Incomplete

Bug description:
  I upgraded from artful to bionic (just run apt update && apt upgrade
  and rebooted before testing the below) and since then my sennheiser
  pxc550 was immediately disconnected after a connect.

  Jun 05 15:18:49 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)
  Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] backend-native.c: 
Device doesnt exist for /org/bluez/hci0/dev_00_16_94_22_21_D8
  Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Headset Voice gateway replied with 
an error: org.bluez.Error.InvalidArguments, Unable to handle new connection
  Jun 05 15:18:50 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: 
Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid
  Jun 05 15:18:50 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Jun 05 15:18:52 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 
matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 
comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") 
interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" 
destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " 
label="unconfined")
  Jun 05 15:18:53 PC-SUJ pulseaudio[2773]: [pulseaudio] bluez5-util.c: 
Information about device /org/bluez/hci0/dev_00_16_94_22_21_D8 is invalid
  Jun 05 15:18:53 PC-SUJ bluetoothd[1033]: Endpoint replied with an error: 
org.bluez.Error.InvalidArguments
  Jun 05 15:18:55 PC-SUJ dbus-daemon[889]: [system] Rejected send message, 1 
matched rules; type="method_return", sender=":1.108" (uid=1000 pid=2773 
comm="/usr/bin/pulseaudio --start --log-target=syslog " label="unconfined") 
interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" 
destination=":1.23" (uid=0 pid=1033 comm="/usr/lib/bluetooth/bluetoothd " 
label="unconfined")
  Jun 05 15:19:07 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)
  Jun 05 15:19:23 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)
  Jun 05 15:19:39 PC-SUJ kernel: Bluetooth: hci0: last event is not cmd 
complete (0x0f)
  [...same message a few more time until I had a new version installed ...]

  
  I since then applied the patch from 
https://bugzilla.redhat.com/show_bug.cgi?id=1534857 -> 
https://marc.info/?l=linux-bluetooth=151801178209679=raw to bluez (apt 
source bluez -> patch -> dpkg-buildpackage ... > sudo dpkg -i ../*.deb) and now 
my headset works again.

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

-- 
Mailing list: https://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 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Daniel van Vugt
Yes, please do reinstall:
  sudo apt install i965-va-driver
That will restore hardware-accelerated video decoding, and keep the system 
cooler :)

It now sounds like you have a general graphics/CPU/disk performance
problem and this bug is not really specific to video playback. I assume
this is a real and not virtual machine...

Next please benchmark the disk you are playing from. You can do that in
the 'Disks' app, or on the command line by running:

  sudo hdparm -t /dev/sda   # or whatever the device is

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller

[Touch-packages] [Bug 1677276] Re: package libreadline-gplv2-dev 5.2+dfsg-3build1 failed to install/upgrade: trying to overwrite shared '/usr/share/doc/libreadline5/examples/Makefile', which is differ

2018-06-05 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package libreadline-gplv2-dev 5.2+dfsg-3build1 failed to
  install/upgrade: trying to overwrite shared
  '/usr/share/doc/libreadline5/examples/Makefile', which is different
  from other instances of package libreadline-gplv2-dev:i386

Status in readline5 package in Ubuntu:
  Confirmed

Bug description:
  I am trying to install the following package but i get an error from the 
system, pipe is broken. 
   sudo apt-get install libreadline-gplv2-dev:i386 libreadline-gplv2-dev

  
  More specifically
  Unpacking libreadline-gplv2-dev:i386 (5.2+dfsg-3build1) ...
  dpkg: error processing archive 
/var/cache/apt/archives/libreadline-gplv2-dev_5.2+dfsg-3build1_i386.deb 
(--unpack):
   trying to overwrite shared '/usr/share/doc/libreadline5/examples/Makefile', 
which is different from other instances of package libreadline-gplv2-dev:i386
  dpkg-deb: error: subprocess paste was killed by signal (Broken pipe)
  Processing triggers for libc-bin (2.23-0ubuntu7) ...
  Errors were encountered while processing:
   /var/cache/apt/archives/libreadline-gplv2-dev_5.2+dfsg-3build1_i386.deb
  E: Sub-process /usr/bin/dpkg returned an error code(1)

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libreadline-gplv2-dev 5.2+dfsg-3build1
  ProcVersionSignature: Ubuntu 4.4.0-66.87-generic 4.4.44
  Uname: Linux 4.4.0-66-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Mar 29 16:58:51 2017
  DuplicateSignature:
   package:libreadline-gplv2-dev:5.2+dfsg-3build1
   Unpacking libreadline-gplv2-dev:i386 (5.2+dfsg-3build1) ...
   dpkg: error processing archive 
/var/cache/apt/archives/libreadline-gplv2-dev_5.2+dfsg-3build1_i386.deb 
(--unpack):
trying to overwrite shared '/usr/share/doc/libreadline5/examples/Makefile', 
which is different from other instances of package libreadline-gplv2-dev:i386
  ErrorMessage: trying to overwrite shared 
'/usr/share/doc/libreadline5/examples/Makefile', which is different from other 
instances of package libreadline-gplv2-dev:i386
  InstallationDate: Installed on 2016-11-18 (130 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.19
  SourcePackage: readline5
  Title: package libreadline-gplv2-dev 5.2+dfsg-3build1 failed to 
install/upgrade: trying to overwrite shared 
'/usr/share/doc/libreadline5/examples/Makefile', which is different from other 
instances of package libreadline-gplv2-dev:i386
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Tracy
CPU benchmarking

tracy@tracy-hp:~$ sysbench --test=cpu run
WARNING: the --test option is deprecated. You can pass a script name or path on 
the command line without any options.
sysbench 1.0.11 (using system LuaJIT 2.1.0-beta3)

Running the test with following options:
Number of threads: 1
Initializing random number generator from current time


Prime numbers limit: 1

Initializing worker threads...

Threads started!

CPU speed:
events per second:   861.57

General statistics:
total time:  10.0012s
total number of events:  8620

Latency (ms):
 min:  1.14
 avg:  1.16
 max:  3.55
 95th percentile:  1.21
 sum:   .07

Threads fairness:
events (avg/stddev):   8620./0.00
execution time (avg/stddev):   9.9991/0.00

tracy@tracy-hp:~$ sysbench --test=cpu --num-threads=16 run
WARNING: the --test option is deprecated. You can pass a script name or path on 
the command line without any options.
WARNING: --num-threads is deprecated, use --threads instead
sysbench 1.0.11 (using system LuaJIT 2.1.0-beta3)

Running the test with following options:
Number of threads: 16
Initializing random number generator from current time


Prime numbers limit: 1

Initializing worker threads...

Threads started!

CPU speed:
events per second:  4668.70

General statistics:
total time:  10.0023s
total number of events:  46707

Latency (ms):
 min:  1.55
 avg:  3.42
 max: 49.71
 95th percentile: 17.63
 sum: 159900.51

Threads fairness:
events (avg/stddev):   2919.1875/110.55
execution time (avg/stddev):   9.9938/0.01

tracy@tracy-hp:~$ sysbench --test=cpu --num-threads=16 --cpu-max-prime=10 
run
WARNING: the --test option is deprecated. You can pass a script name or path on 
the command line without any options.
WARNING: --num-threads is deprecated, use --threads instead
sysbench 1.0.11 (using system LuaJIT 2.1.0-beta3)

Running the test with following options:
Number of threads: 16
Initializing random number generator from current time


Prime numbers limit: 10

Initializing worker threads...

Threads started!

CPU speed:
events per second:   199.77

General statistics:
total time:  10.0494s
total number of events:  2008

Latency (ms):
 min: 39.76
 avg: 79.86
 max:156.43
 95th percentile: 92.42
 sum: 160358.07

Threads fairness:
events (avg/stddev):   125.5000/1.94
execution time (avg/stddev):   10.0224/0.01

tracy@tracy-hp:~$

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include 

[Touch-packages] [Bug 1775317] [NEW] package apport 2.20.9-0ubuntu7 failed to install/upgrade: El paquete está en un estado grave de inconsistencia - debe reinstalarlo antes de intentar su configurac

2018-06-05 Thread Geancarlo Murillo
Public bug reported:

Trying to install or update something

ProblemType: Package
DistroRelease: Ubuntu 18.04
Package: apport 2.20.9-0ubuntu7
ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
Uname: Linux 4.15.0-22-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportLog:
 
ApportVersion: 2.20.9-0ubuntu7
AptOrdering: NULL: ConfigurePending
Architecture: amd64
CrashReports: 600:0:116:82123:2018-06-05 21:56:22.171656847 -0500:2018-06-05 
21:56:23.171656847 -0500:/var/crash/apport.0.crash
Date: Tue Jun  5 21:56:22 2018
DpkgTerminalLog:
 dpkg: error al procesar el paquete apport (--configure):
  El paquete está en un estado grave de inconsistencia - debe reinstalarlo
  antes de intentar su configuración.
ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
InstallationDate: Installed on 2017-05-02 (399 days ago)
InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
PackageArchitecture: all
Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
RelatedPackageVersions:
 dpkg 1.19.0.5ubuntu2
 apt  1.6.1
SourcePackage: apport
Title: package apport 2.20.9-0ubuntu7 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
UpgradeStatus: Upgraded to bionic on 2018-05-07 (30 days ago)

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


** Tags: amd64 apport-package bionic

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

Title:
  package apport 2.20.9-0ubuntu7 failed to install/upgrade: El paquete
  está en un estado grave de inconsistencia - debe reinstalarlo  antes
  de intentar su configuración.

Status in apport package in Ubuntu:
  New

Bug description:
  Trying to install or update something

  ProblemType: Package
  DistroRelease: Ubuntu 18.04
  Package: apport 2.20.9-0ubuntu7
  ProcVersionSignature: Ubuntu 4.15.0-22.24-generic 4.15.17
  Uname: Linux 4.15.0-22-generic x86_64
  NonfreeKernelModules: nvidia_modeset nvidia
  ApportLog:
   
  ApportVersion: 2.20.9-0ubuntu7
  AptOrdering: NULL: ConfigurePending
  Architecture: amd64
  CrashReports: 600:0:116:82123:2018-06-05 21:56:22.171656847 -0500:2018-06-05 
21:56:23.171656847 -0500:/var/crash/apport.0.crash
  Date: Tue Jun  5 21:56:22 2018
  DpkgTerminalLog:
   dpkg: error al procesar el paquete apport (--configure):
El paquete está en un estado grave de inconsistencia - debe reinstalarlo
antes de intentar su configuración.
  ErrorMessage: El paquete está en un estado grave de inconsistencia - debe 
reinstalarlo  antes de intentar su configuración.
  InstallationDate: Installed on 2017-05-02 (399 days ago)
  InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 
(20170215.2)
  PackageArchitecture: all
  Python3Details: /usr/bin/python3.6, Python 3.6.5, python3-minimal, 3.6.5-3
  PythonDetails: /usr/bin/python2.7, Python 2.7.15rc1, python-minimal, 
2.7.15~rc1-1
  RelatedPackageVersions:
   dpkg 1.19.0.5ubuntu2
   apt  1.6.1
  SourcePackage: apport
  Title: package apport 2.20.9-0ubuntu7 failed to install/upgrade: El paquete 
está en un estado grave de inconsistencia - debe reinstalarlo  antes de 
intentar su configuración.
  UpgradeStatus: Upgraded to bionic on 2018-05-07 (30 days ago)

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

-- 
Mailing list: https://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 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Tracy
Totem and gnome-shell both are running between 10% and 30% each (they
bounce back and forth during playback). The next highest usage
(according to top) is 8% and under. Is there a way to capture CPU usage
during playback that will be representative of actual usage?

My video resolution is 1920 x 1080 - it is the default resolution for
this screen (17" laptop LCD - no touchscreen capabilities).

I should note that I get this problem regardless of whether I run totem
full screen or in a small (320 x 200) window... (I realize that the size
of the window isn't the determining factor, but I would think that a
smaller window would be less likely to show the problem than a full
screen - but that doesn't seem to be the case here.)

tracy@tracy-hp:~$ xrandr
Screen 0: minimum 320 x 200, current 1920 x 1080, maximum 8192 x 8192
LVDS-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y 
axis) 381mm x 214mm
   1920x1080 60.06*+  60.0159.9759.9659.93  
   1680x1050 59.9559.88  
   1600x1024 60.17  
   1400x1050 59.98  
   1600x900  59.9959.9459.9559.82  
   1280x1024 60.02  
   1440x900  59.89  
   1400x900  59.9659.88  
   1280x960  60.00  
   1440x810  60.0059.97  
   1368x768  59.8859.85  
   1360x768  59.8059.96  
   1280x800  59.9959.9759.8159.91  
   1152x864  60.00  
   1280x720  60.0059.9959.8659.74  
   1024x768  60.0460.00  
   960x720   60.00  
   928x696   60.05  
   896x672   60.01  
   1024x576  59.9559.9659.9059.82  
   960x600   59.9360.00  
   960x540   59.9659.9959.6359.82  
   800x600   60.0060.3256.25  
   840x525   60.0159.88  
   864x486   59.9259.57  
   800x512   60.17  
   700x525   59.98  
   800x450   59.9559.82  
   640x512   60.02  
   720x450   59.89  
   700x450   59.9659.88  
   640x480   60.0059.94  
   720x405   59.5158.99  
   684x384   59.8859.85  
   680x384   59.8059.96  
   640x400   59.8859.98  
   576x432   60.06  
   640x360   59.8659.8359.8459.32  
   512x384   60.00  
   512x288   60.0059.92  
   480x270   59.6359.82  
   400x300   60.3256.34  
   432x243   59.9259.57  
   320x240   60.05  
   360x202   59.5159.13  
   320x180   59.8459.32  
VGA-1 disconnected (normal left inverted right x axis y axis)
HDMI-1 disconnected (normal left inverted right x axis y axis)
DP-1 disconnected (normal left inverted right x axis y axis)
tracy@tracy-hp:~$

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver 

[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Daniel van Vugt
Thanks.

If the pauses are now very brief with your BIOS in "fixed" mode, and if
mpv is performing slightly better than totem, then I suggest this is now
a duplicate of bug 1698270. Bug 1698270 is not fully resolved and
requires more investigation.

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC 
Controller (rev 05)
Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC 
Controller
Kernel driver in use: lpc_ich
Kernel 

[Touch-packages] [Bug 1775325] Re: package python3 3.5.1-3 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2018-06-05 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 python3-defaults in
Ubuntu.
https://bugs.launchpad.net/bugs/1775325

Title:
  package python3 3.5.1-3 failed to install/upgrade: package is in a
  very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in python3-defaults package in Ubuntu:
  New

Bug description:
  When my PC starts, it occurs this error.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3 3.5.1-3
  ProcVersionSignature: Ubuntu 4.13.0-43.48~16.04.1-generic 4.13.16
  Uname: Linux 4.13.0-43-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.18
  Architecture: amd64
  Date: Wed Jun  6 06:42:44 2018
  DpkgHistoryLog:
   Start-Date: 2018-06-06  06:41:46
   Commandline: /usr/bin/unattended-upgrade
   Upgrade: git-man:amd64 (1:2.7.4-0ubuntu1.3, 1:2.7.4-0ubuntu1.4), 
liblouis9:amd64 (2.6.4-2ubuntu0.1, 2.6.4-2ubuntu0.2), libelf1:amd64 
(0.165-3ubuntu1, 0.165-3ubuntu1.1), libelf1:i386 (0.165-3ubuntu1, 
0.165-3ubuntu1.1), git:amd64 (1:2.7.4-0ubuntu1.3, 1:2.7.4-0ubuntu1.4), 
python3-louis:amd64 (2.6.4-2ubuntu0.1, 2.6.4-2ubuntu0.2), libexempi3:amd64 
(2.2.2-2, 2.2.2-2ubuntu0.1), apport:amd64 (2.20.1-0ubuntu2.17, 
2.20.1-0ubuntu2.18), python3-apport:amd64 (2.20.1-0ubuntu2.17, 
2.20.1-0ubuntu2.18), apport-gtk:amd64 (2.20.1-0ubuntu2.17, 2.20.1-0ubuntu2.18), 
liblouis-data:amd64 (2.6.4-2ubuntu0.1, 2.6.4-2ubuntu0.2), 
python3-problem-report:amd64 (2.20.1-0ubuntu2.17, 2.20.1-0ubuntu2.18)
  DuplicateSignature:
   package:python3:3.5.1-3
   Processing triggers for mime-support (3.59ubuntu1) ...
   dpkg: error processing package python3 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-07-06 (1065 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150705)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.4
   apt  1.2.26
  SourcePackage: python3-defaults
  Title: package python3 3.5.1-3 failed to install/upgrade: package is in a 
very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: Upgraded to xenial on 2018-05-26 (11 days ago)

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

-- 
Mailing list: https://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 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Tracy
I reinstalled the i965-va-driver.

Here is the output of the hdparm command for the drive that currently
houses the video file:

tracy@tracy-hp:~$ sudo hdparm -t /dev/sdb
[sudo] password for tracy: 

/dev/sdb:
 Timing buffered disk reads: 352 MB in  3.01 seconds = 117.06 MB/sec

I moved the video file to a different drive, and tried it in totem
again. Same problem. Here's the hdparm output for that drive:

tracy@tracy-hp:~$ sudo hdparm -t /dev/sda

/dev/sda:
 Timing buffered disk reads: 1198 MB in  3.00 seconds = 399.32 MB/sec

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced 

[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Tracy
Most of that info doesn't mean much to me, but hopefully it will help
narrow things down and at least let you point me in the right
direction

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC 
Controller (rev 05)
Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC 
Controller
Kernel driver in use: lpc_ich
Kernel modules: lpc_ich
  00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset 
Family 6 

[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Tracy
tracy@tracy-hp:~$ glmark2
===
glmark2 2014.03+git20150611.fa71af2d
===
OpenGL Information
GL_VENDOR: Intel Open Source Technology Center
GL_RENDERER:   Mesa DRI Intel(R) Sandybridge Mobile 
GL_VERSION:3.0 Mesa 18.0.0-rc5
===
[build] use-vbo=false: FPS: 1893 FrameTime: 0.528 ms
[build] use-vbo=true: FPS: 1793 FrameTime: 0.558 ms
[texture] texture-filter=nearest: FPS: 1735 FrameTime: 0.576 ms
[texture] texture-filter=linear: FPS: 1720 FrameTime: 0.581 ms
[texture] texture-filter=mipmap: FPS: 1772 FrameTime: 0.564 ms
[shading] shading=gouraud: FPS: 1576 FrameTime: 0.635 ms
[shading] shading=blinn-phong-inf: FPS: 1570 FrameTime: 0.637 ms
[shading] shading=phong: FPS: 1400 FrameTime: 0.714 ms
[shading] shading=cel: FPS: 1341 FrameTime: 0.746 ms
[bump] bump-render=high-poly: FPS: 882 FrameTime: 1.134 ms
[bump] bump-render=normals: FPS: 1796 FrameTime: 0.557 ms
[bump] bump-render=height: FPS: 1670 FrameTime: 0.599 ms
[effect2d] kernel=0,1,0;1,-4,1;0,1,0;: FPS: 857 FrameTime: 1.167 ms
[effect2d] kernel=1,1,1,1,1;1,1,1,1,1;1,1,1,1,1;: FPS: 370 FrameTime: 2.703 ms
[pulsar] light=false:quads=5:texture=false: FPS: 1580 FrameTime: 0.633 ms
[desktop] blur-radius=5:effect=blur:passes=1:separable=true:windows=4: FPS: 416 
FrameTime: 2.404 ms
[desktop] effect=shadow:windows=4: FPS: 835 FrameTime: 1.198 ms
[buffer] 
columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=map:
 FPS: 658 FrameTime: 1.520 ms
[buffer] 
columns=200:interleave=false:update-dispersion=0.9:update-fraction=0.5:update-method=subdata:
 FPS: 676 FrameTime: 1.479 ms
[buffer] 
columns=200:interleave=true:update-dispersion=0.9:update-fraction=0.5:update-method=map:
 FPS: 719 FrameTime: 1.391 ms
[ideas] speed=duration: FPS: 1014 FrameTime: 0.986 ms
[jellyfish] : FPS: 881 FrameTime: 1.135 ms
[terrain] : FPS: 95 FrameTime: 10.526 ms
[shadow] : FPS: 674 FrameTime: 1.484 ms
[refract] : FPS: 238 FrameTime: 4.202 ms
[conditionals] fragment-steps=0:vertex-steps=0: FPS: 1663 FrameTime: 0.601 ms
[conditionals] fragment-steps=5:vertex-steps=0: FPS: 1473 FrameTime: 0.679 ms
[conditionals] fragment-steps=0:vertex-steps=5: FPS: 1654 FrameTime: 0.605 ms
[function] fragment-complexity=low:fragment-steps=5: FPS: 1644 FrameTime: 0.608 
ms
[function] fragment-complexity=medium:fragment-steps=5: FPS: 1435 FrameTime: 
0.697 ms
[loop] fragment-loop=false:fragment-steps=5:vertex-steps=5: FPS: 1368 
FrameTime: 0.731 ms
[loop] fragment-steps=5:fragment-uniform=false:vertex-steps=5: FPS: 1621 
FrameTime: 0.617 ms
[loop] fragment-steps=5:fragment-uniform=true:vertex-steps=5: FPS: 1465 
FrameTime: 0.683 ms
===
  glmark2 Score: 1226 
===
tracy@tracy-hp:~$

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core 

[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Daniel van Vugt
Thanks, but there's no need to benchmark the CPU itself. We already know
the CPU model. What does concern me about CPU usage is whether gnome-
shell or some other process is using considerable CPU during playback.
Do you find that?

Also, please run 'xrandr' and send us the output. Gnome Shell is
unfortunately not very efficient at drawing high resolution yet (using
standard GPUs like that in the i7-2630QM). So if your screen is greater
than 1920x1080 then that could also be a problem.

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: 

[Touch-packages] [Bug 1774915] Re: Video freezes and stutters when using totem (audio continues fine)

2018-06-05 Thread Tracy
The pauses are very brief using mpv - using totem I still get pauses in
excess of 5 seconds at random points during playback. However I am
willing to accept that this would constitute a duplicate of 1698270, and
will wait for any updates there.

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

Title:
  Video freezes and stutters when using totem (audio continues fine)

Status in gnome-shell package in Ubuntu:
  Incomplete
Status in gstreamer1.0 package in Ubuntu:
  Incomplete
Status in mesa package in Ubuntu:
  Incomplete

Bug description:
  Advised to file a bug report after posting on "Call for testing: Video
  playback in 18.04".

  Running 18.04 LTS as fresh install (not upgraded from previous version
  - older version still installed in separate partition). Xorg session.

  System: HP Pavillion DV7 (lm726av) - Intel Core i7 2630 processor,
  integrated Intel video

  Playing any local video file (regardless of video format - flv, mp4,
  avi), the video will randomly lag in playback. Audio is not affected,
  it plays back correctly. Very occasional lags in browsers (Firefox and
  Chrome) on pages with a lot of active graphics (flash or HTML5).
  Browser lags significantly improved after installing synaptic driver
  for touchpad operation (I have no idea why this would affect video
  playback - I simply note that it happened).

  I can pick a random video on YouTube and watch it in Firefox or Chrome
  without lag (even full-screen). However, if I grab a local copy of the
  video (using, for instance, Clipgrab) and play it using Totem, I get
  lag.

  I was also advised to try using mpv - I still get lag in mpv, although
  not as pronounced.

  tracy@tracy-hp:~$ sudo apt-cache policy totem
  [sudo] password for tracy: 
  totem:
Installed: 3.26.0-0ubuntu6
Candidate: 3.26.0-0ubuntu6
Version table:
   *** 3.26.0-0ubuntu6 500
  500 http://us.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
  100 /var/lib/dpkg/status

  I was also asked to include output of lspci -k - shown below:

  tracy@tracy-hp:~$ lspci -k
  00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family 
DRAM Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
DRAM Controller
  00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core 
Processor Family PCI Express Root Port (rev 09)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core 
Processor Family Integrated Graphics Controller (rev 09)
Subsystem: Hewlett-Packard Company 2nd Generation Core Processor Family 
Integrated Graphics Controller
Kernel driver in use: i915
Kernel modules: i915
  00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series 
Chipset Family MEI Controller #1 (rev 04)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
MEI Controller
Kernel driver in use: mei_me
Kernel modules: mei_me
  00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #2 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family 
High Definition Audio Controller (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
High Definition Audio Controller
Kernel driver in use: snd_hda_intel
Kernel modules: snd_hda_intel
  00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 1 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 2 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.2 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 3 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI 
Express Root Port 4 (rev b5)
Kernel driver in use: pcieport
Kernel modules: shpchp
  00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller #1 (rev 05)
Subsystem: Hewlett-Packard Company 6 Series/C200 Series Chipset Family 
USB Enhanced Host Controller
Kernel driver in use: ehci-pci
  00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC 
Controller (rev 05)
Subsystem: Hewlett-Packard Company HM65 Express Chipset Family LPC 
Controller
Kernel driver in use: lpc_ich
Kernel 

  1   2   >