[Touch-packages] [Bug 1652486] Re: mesa gpu lockup

[Ubuntu Foundations Team Bug Bot]

The attachment "mesa source package patch" seems to be a debdiff.  The
ubuntu-sponsors team has been subscribed to the bug report so that they
can review and hopefully sponsor the debdiff.  If the attachment isn't a
patch, please remove the "patch" flag from the attachment, remove the
"patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe
the team.

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

** Tags added: patch

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

Title:
  mesa gpu lockup

Status in mesa package in Ubuntu:
  New

Bug description:
  package: mesa
  version: 11.2.0-1ubuntu2.2
  release: 16.04.1 / "Xenial"

  references:
  * https://bugs.freedesktop.org/show_bug.cgi?id=93649
  * https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3

  symptoms:
  1. kernel reports "GPU lockup"
  2. kernel reports "GPU softreset"
  3. immediately frozen display
  4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 
seconds."
  5. computer hanging on system reboot requiring a forced power off

  Symptoms occur when playing Team Fortress 2.

  Attachments:
  1. mesa source package patch
  2. lspci output for video card (ie Radeon HD 7750)
  3. kernel log

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

-- 
Mailing list: https://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 1652491] [NEW] Sync elfutils 0.166-2.2 (main) from Debian unstable (main)

[Jeremy Bicha]

Public bug reported:

Please sync elfutils 0.166-2.2 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Don't run the run-backtrace-native-biarch test.

The test was fixed in -2.2. I confirmed that the package builds
successfully on all normal PPA architectures.

Changelog entries since current zesty version 0.166-2ubuntu1:

elfutils (0.166-2.2) unstable; urgency=medium

  * Non-maintainer upload.
  * testsuite-amd64-fix-backtrace-native.patch: Backport upstream
patch to fix FTBFS on amd64 (Closes: #841124)

 -- James Clarke   Tue, 18 Oct 2016 08:13:34 +0100

elfutils (0.166-2.1) unstable; urgency=medium

  * Non-maintainer upload.
  * Build-Depend on gcc-multilib and libc6-dbg on sparc64 (Closes: #832584)

 -- James Clarke   Fri, 07 Oct 2016 15:16:09 +0100

** Affects: elfutils (Ubuntu)
 Importance: Wishlist
 Status: New

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

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

Title:
  Sync elfutils 0.166-2.2 (main) from Debian unstable (main)

Status in elfutils package in Ubuntu:
  New

Bug description:
  Please sync elfutils 0.166-2.2 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Don't run the run-backtrace-native-biarch test.

  The test was fixed in -2.2. I confirmed that the package builds
  successfully on all normal PPA architectures.

  Changelog entries since current zesty version 0.166-2ubuntu1:

  elfutils (0.166-2.2) unstable; urgency=medium

* Non-maintainer upload.
* testsuite-amd64-fix-backtrace-native.patch: Backport upstream
  patch to fix FTBFS on amd64 (Closes: #841124)

   -- James Clarke   Tue, 18 Oct 2016 08:13:34 +0100

  elfutils (0.166-2.1) unstable; urgency=medium

* Non-maintainer upload.
* Build-Depend on gcc-multilib and libc6-dbg on sparc64 (Closes: #832584)

   -- James Clarke   Fri, 07 Oct 2016 15:16:09 +0100

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

-- 
Mailing list: https://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 1633390] Re: unity 8 login stalls

[Launchpad Bug Tracker]

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

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

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

Title:
  unity 8 login stalls

Status in Canonical System Image:
  Incomplete
Status in unity8 package in Ubuntu:
  Expired

Bug description:
  Contrary to other login problems with Unity 8 (as installed by default
  in Ubuntu 16.10), I'm not getting a black screen when trying to log
  in. After entering my password the login screen just sort of hangs;
  I'm left with the login GUI (which is frozen) and the top panel (which
  I can use) to display the suspend / restart options. I left it running
  for quite a while, but nothing happened. I can log in to the default
  environment easily.

  I'm running a System 76 Meerkat, having upgraded from Ubuntu 16.04 without 
wiping my system drive.
  --- 
  ApportVersion: 2.20.3-0ubuntu8
  Architecture: amd64
  CurrentDesktop: Unity
  DistroRelease: Ubuntu 16.10
  InstallationDate: Installed on 2016-10-01 (18 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  Package: unity8 8.14+16.10.20160922-0ubuntu2
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-22.24-generic 4.8.0
  Tags: third-party-packages yakkety
  Uname: Linux 4.8.0-22-generic x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (6 days ago)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
  _MarkForUpload: True

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1633390/+subscriptions

-- 
Mailing list: https://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 1636631] Re: DISC SPACE NONE LEFT

[Launchpad Bug Tracker]

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

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

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

Title:
  DISC SPACE NONE LEFT

Status in xorg package in Ubuntu:
  Expired

Bug description:
  DISC NOT ENOUGH SPACE

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-27.29-generic 4.8.1
  Uname: Linux 4.8.0-27-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.3-0ubuntu8
  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: Tue Oct 25 17:40:32 2016
  DistUpgraded: 2016-10-13 13:22:55,920 DEBUG running apport_crash()
  DistroCodename: yakkety
  DistroVariant: ubuntu
  ExtraDebuggingInterest: I just need to know a workaround
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
 Subsystem: Toshiba America Info Systems Mobile 4 Series Chipset Integrated 
Graphics Controller [1179:fde0]
  InstallationDate: Installed on 2016-09-13 (42 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  MachineType: TOSHIBA Satellite C655
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-27-generic 
root=/dev/mapper/ubuntu--vg-root ro splash quiet
  SourcePackage: xorg
  UpgradeStatus: Upgraded to yakkety on 2016-10-13 (12 days ago)
  dmi.bios.date: 07/07/2011
  dmi.bios.vendor: INSYDE
  dmi.bios.version: 1.70
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: Portable PC
  dmi.board.vendor: TOSHIBA
  dmi.board.version: Base Board Version
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnINSYDE:bvr1.70:bd07/07/2011:svnTOSHIBA:pnSatelliteC655:pvrPSC08U-03C01K:rvnTOSHIBA:rnPortablePC:rvrBaseBoardVersion:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: Satellite C655
  dmi.product.version: PSC08U-03C01K
  dmi.sys.vendor: TOSHIBA
  version.compiz: compiz 1:0.9.13.0+16.10.20160818.2-0ubuntu2
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.3-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.3-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu6
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2
  xserver.bootTime: Tue Oct 25 14:26:13 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-1ubuntu6
  xserver.video_driver: modeset

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

-- 
Mailing list: https://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 1652486] Re: mesa gpu lockup

[undefined]

** Attachment added: "video card lspci output"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1652486/+attachment/4796224/+files/lspci.log

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

Title:
  mesa gpu lockup

Status in mesa package in Ubuntu:
  New

Bug description:
  package: mesa
  version: 11.2.0-1ubuntu2.2
  release: 16.04.1 / "Xenial"

  references:
  * https://bugs.freedesktop.org/show_bug.cgi?id=93649
  * https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3

  symptoms:
  1. kernel reports "GPU lockup"
  2. kernel reports "GPU softreset"
  3. immediately frozen display
  4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 
seconds."
  5. computer hanging on system reboot requiring a forced power off

  Symptoms occur when playing Team Fortress 2.

  Attachments:
  1. mesa source package patch
  2. lspci output for video card (ie Radeon HD 7750)
  3. kernel log

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

-- 
Mailing list: https://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 1652486] Re: mesa gpu lockup

[undefined]

** Attachment added: "kernel log of GPU lockup, GPU soft reset, and blocked 
tasks"
   
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1652486/+attachment/4796223/+files/gpu_hang.log

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

Title:
  mesa gpu lockup

Status in mesa package in Ubuntu:
  New

Bug description:
  package: mesa
  version: 11.2.0-1ubuntu2.2
  release: 16.04.1 / "Xenial"

  references:
  * https://bugs.freedesktop.org/show_bug.cgi?id=93649
  * https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3

  symptoms:
  1. kernel reports "GPU lockup"
  2. kernel reports "GPU softreset"
  3. immediately frozen display
  4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 
seconds."
  5. computer hanging on system reboot requiring a forced power off

  Symptoms occur when playing Team Fortress 2.

  Attachments:
  1. mesa source package patch
  2. lspci output for video card (ie Radeon HD 7750)
  3. kernel log

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

-- 
Mailing list: https://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 1652486] [NEW] mesa gpu lockup

[undefined]

Public bug reported:

package: mesa
version: 11.2.0-1ubuntu2.2
release: 16.04.1 / "Xenial"

references:
* https://bugs.freedesktop.org/show_bug.cgi?id=93649
* https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3

symptoms:
1. kernel reports "GPU lockup"
2. kernel reports "GPU softreset"
3. immediately frozen display
4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 
seconds."
5. computer hanging on system reboot requiring a forced power off

Symptoms occur when playing Team Fortress 2.

Attachments:
1. mesa source package patch
2. lspci output for video card (ie Radeon HD 7750)
3. kernel log

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

** Patch added: "mesa source package patch"
   
https://bugs.launchpad.net/bugs/1652486/+attachment/4796222/+files/mesa_11.2.0-1ubuntu2.2+udo1604+1.patch

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

Title:
  mesa gpu lockup

Status in mesa package in Ubuntu:
  New

Bug description:
  package: mesa
  version: 11.2.0-1ubuntu2.2
  release: 16.04.1 / "Xenial"

  references:
  * https://bugs.freedesktop.org/show_bug.cgi?id=93649
  * https://cgit.freedesktop.org/mesa/mesa/commit/?id=6dc96de3

  symptoms:
  1. kernel reports "GPU lockup"
  2. kernel reports "GPU softreset"
  3. immediately frozen display
  4. eventual "INFO: task (kworker|Xorg)[/:0-9]+ blocked for more than 120 
seconds."
  5. computer hanging on system reboot requiring a forced power off

  Symptoms occur when playing Team Fortress 2.

  Attachments:
  1. mesa source package patch
  2. lspci output for video card (ie Radeon HD 7750)
  3. kernel log

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

-- 
Mailing list: https://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 1652477] [NEW] Sync cpio 2.11+dfsg-6 (main) from Debian unstable (main)

[Jeremy Bicha]

Public bug reported:

Please sync cpio 2.11+dfsg-6 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * Resynchronise with Debian. Remaining changes:
- Don't build a cpio-win32 package since mingw-w64 is in universe.

cpio-win32 does not have any dependencies on universe packages:
https://packages.debian.org/unstable/cpio-win32

Changelog entries since current zesty version 2.11+dfsg-5ubuntu1:

cpio (2.11+dfsg-6) unstable; urgency=medium

  * Man page for "mt" describes how to "fast erase"
Patch by Kees Cook
Add fix.mt-erase.manpage.patch
Closes: #770198
  * Backport "New options to create device and inode-independent
archives." from cpio 2.12
Patch by Chris Lamb
Add reproducible.patch
See #804063
  * Standards-Version: 3.9.8
  * Refresh patches

 -- Anibal Monsalve Salazar   Tue, 29 Nov 2016
12:31:53 +

** Affects: cpio (Ubuntu)
 Importance: Wishlist
 Status: New

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

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

Title:
  Sync cpio 2.11+dfsg-6 (main) from Debian unstable (main)

Status in cpio package in Ubuntu:
  New

Bug description:
  Please sync cpio 2.11+dfsg-6 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* Resynchronise with Debian. Remaining changes:
  - Don't build a cpio-win32 package since mingw-w64 is in universe.

  cpio-win32 does not have any dependencies on universe packages:
  https://packages.debian.org/unstable/cpio-win32

  Changelog entries since current zesty version 2.11+dfsg-5ubuntu1:

  cpio (2.11+dfsg-6) unstable; urgency=medium

* Man page for "mt" describes how to "fast erase"
  Patch by Kees Cook
  Add fix.mt-erase.manpage.patch
  Closes: #770198
* Backport "New options to create device and inode-independent
  archives." from cpio 2.12
  Patch by Chris Lamb
  Add reproducible.patch
  See #804063
* Standards-Version: 3.9.8
* Refresh patches

   -- Anibal Monsalve Salazar   Tue, 29 Nov 2016
  12:31:53 +

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

-- 
Mailing list: https://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 1652478] [NEW] Sync json-c 0.12.1-1.1 (main) from Debian unstable (main)

[Jeremy Bicha]

Public bug reported:

Please sync json-c 0.12.1-1.1 (main) from Debian unstable (main)

Explanation of the Ubuntu delta and why it can be dropped:
  * debian/libjson-c-dev.links: Fix library symlinks to not collide between
/lib/ and /usr/lib/. (Closes: #843145, LP: #1629552)

That change was applied in Debian

Changelog entries since current zesty version 0.12.1-1ubuntu1:

json-c (0.12.1-1.1) unstable; urgency=medium

  * Non-maintainer upload.
  * debian/control: Fix Vcs-Browser URL
  * debian/libjson-c-dev.links: Fix library symlinks to not collide between
/lib/ and /usr/lib/ (Closes: #843145, LP: #1629552)

 -- Martin Pitt   Mon, 14 Nov 2016 11:33:17 +0100

** Affects: json-c (Ubuntu)
 Importance: Wishlist
 Status: New

** Changed in: json-c (Ubuntu)
   Importance: Undecided => Wishlist

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

Title:
  Sync json-c 0.12.1-1.1 (main) from Debian unstable (main)

Status in json-c package in Ubuntu:
  New

Bug description:
  Please sync json-c 0.12.1-1.1 (main) from Debian unstable (main)

  Explanation of the Ubuntu delta and why it can be dropped:
* debian/libjson-c-dev.links: Fix library symlinks to not collide between
  /lib/ and /usr/lib/. (Closes: #843145, LP: #1629552)

  That change was applied in Debian

  Changelog entries since current zesty version 0.12.1-1ubuntu1:

  json-c (0.12.1-1.1) unstable; urgency=medium

* Non-maintainer upload.
* debian/control: Fix Vcs-Browser URL
* debian/libjson-c-dev.links: Fix library symlinks to not collide between
  /lib/ and /usr/lib/ (Closes: #843145, LP: #1629552)

   -- Martin Pitt   Mon, 14 Nov 2016 11:33:17 +0100

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

-- 
Mailing list: https://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 1638245] Re: Files in the root of a folder on another partition symlinked to user's home cannot be moved to trash because of a patch in this package

[Svivi]

Hi,

Does anybody know when will be the updated glib2.0 included in
xenial(-proposed)?

Thanks in advance!

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

Title:
  Files in the root of a folder on another partition symlinked to user's
  home cannot be moved to trash because of a patch in this package

Status in glib2.0 package in Ubuntu:
  Fix Released
Status in glib2.0 source package in Xenial:
  Confirmed
Status in glib2.0 source package in Yakkety:
  Fix Committed

Bug description:
  [ Description ]

  Can't trash files if the directory they are in is a symlink to another
  device

  [ QA ]

  Steps:
  1. Install system and partition disk into root and data partitions
  2. create ~/Data folder, and mount data partition on it
  3. create symlinks for ~/whatever/ to ~/Data/something/
  4. delete files directly inside ~/whatever/

  What happen:
  Then Nautilus says: "File can't be put in the trash. Do you want to delete it 
immediately?".

  What should happen:
  The files moved into Trash.

  [ Regression potential ]

  The proposed fix uses g_stat instead of g_stat to follow symlinks, so
  we know where to place the trash (you can't rename() across
  filesystems). If that is wrong, then it could regress trashing other
  kinds of files.

  [ Original ]

  I'm on Ubuntu 16.10 64-bit with libglib2.0-0 version 2.50.0-1.

  I've reported this bug (or marked as "it affects me") in a couple of
  other places before I've finally discovered that this is the package
  that's causing this problem, which unfortunately has been around for a
  couple of years now.

  This bug has been reported upstream as well, but it's just taking very
  very long to arrive at a decision and take action it seems.

  Apparently one of the patches
  (https://sources.debian.net/patches/glib2.0/2.50.1-1/0001-Fix-
  trashing-on-overlayfs.patch/) which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0-1.debian.tar.xz)
  to the original package which is here
  
(https://launchpad.net/ubuntu/+archive/primary/+files/glib2.0_2.50.0.orig.tar.xz)
  is the root cause of this annoying problem.

  As I prefer keeping one patition for the root filesystem (/), one
  partition for user settings (/home) and one partition for user data
  (Documents, Downloads, Drive, Music, Pictures, Public, Videos) which
  are simply symlinked to my home folder for ease of use, I cannot move
  any file to the trash in the root of these folders when I access them
  from my home folder or nautilus sidebar.

  This problem doesn't affect folders at all, nor any other files in
  subfolders, etc.

  So I was wondering if Ubuntu devs can leave out that particular patch
  when building this package for Ubuntu - if it doesn't cause more harm,
  which I doubt.

  Otherwise, I would appreciate if I could learn how to do it myself:
  how can I (as an end-user) compile the contents of
  "glib2.0_2.50.0.orig.tar.xz" with all the patches, etc. in
  "glib2.0_2.50.0-1.debian.tar.xz" except "0001-Fix-trashing-on-
  overlayfs.patch"?

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

-- 
Mailing list: https://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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Mark Leigh]

I should add, one inhibitor listed was multiple displays, but I don't
have that, nor have I attached any additional displays since the clean
install of 16.04.

I tested the workaround suggest above (HandleLidSwitchDocked=suspend)
and it (sort of) works.  It takes 12-14 seconds after closing the lid
before suspend starts. However, it also makes the system unstable. It
now locks up during boot sometimes, and sometimes crashes and reboots
during suspend.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

-- 
Mailing list: https://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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Mark Leigh]

I should add, even though it says I have multiple displays attached, I
don't and I haven't since I installed 16.04.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

-- 
Mailing list: https://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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Mark Leigh]

Although if I do the following steps, it will suspend

1: Close the lid
2: Open the lid (presented with unlock screen)
3: Close the lid
4: Wait 10s and notebook suspends...

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

-- 
Mailing list: https://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 1574120] Re: Notebook doesn't suspend when lid is closed after update to 16.04

[Mark Leigh]

Same bug on Lenovo Thinkpad T510.

 Who: NetworkManager (UID 0/root, PID 1042/NetworkManager)
What: sleep
 Why: NetworkManager needs to turn off networks
Mode: delay

 Who: bob (UID 1000/bob, PID 3529/cinnamon-settin)
What: handle-power-key:handle-suspend-key:handle-hibernate-key
 Why: Cinnamon handling keypresses
Mode: block

 Who: bob (UID 1000/bob, PID 3529/cinnamon-settin)
What: sleep
 Why: Cinnamon needs to lock the screen
Mode: delay

 Who: bob (UID 1000/bob, PID 3529/cinnamon-settin)
What: handle-lid-switch
 Why: Multiple displays attached
Mode: block

4 inhibitors listed.

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

Title:
  Notebook doesn't suspend when lid is closed after update to 16.04

Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  My notebook does not suspend after upgrading from 15.10 to 16.04.

  According to system settings the notebook should suspend when lid is
  closed but actually this does not happen. Instead it continues to run
  as if nothing had happened.

  With the previous versions of ubuntu (14.04-15.10) everything worked
  fine.

  My System: HP Pavilion dv7.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: acpi (not installed)
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Apr 23 23:11:15 2016
  InstallationDate: Installed on 2015-10-29 (176 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: acpi
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)

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

-- 
Mailing list: https://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 1652471] [NEW] package dbus 1.10.6-1ubuntu3.2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 1

[miguel]

Public bug reported:

i don't know

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: dbus 1.10.6-1ubuntu3.2
ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
Uname: Linux 3.13.0-86-generic i686
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: i386
Date: Fri Dec 16 17:45:36 2016
ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
InstallationDate: Installed on 2010-02-21 (2498 days ago)
InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.18
SourcePackage: dbus
Title: package dbus 1.10.6-1ubuntu3.2 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)

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


** Tags: apport-package i386 package-from-proposed xenial

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

Title:
  package dbus 1.10.6-1ubuntu3.2 failed to install/upgrade: el
  subproceso instalado el script post-installation devolvió el código de
  salida de error 1

Status in dbus package in Ubuntu:
  New

Bug description:
  i don't know

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: dbus 1.10.6-1ubuntu3.2
  ProcVersionSignature: Ubuntu 3.13.0-86.130-generic 3.13.11-ckt39
  Uname: Linux 3.13.0-86-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  Date: Fri Dec 16 17:45:36 2016
  ErrorMessage: el subproceso instalado el script post-installation devolvió el 
código de salida de error 1
  InstallationDate: Installed on 2010-02-21 (2498 days ago)
  InstallationMedia: Kubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.18
  SourcePackage: dbus
  Title: package dbus 1.10.6-1ubuntu3.2 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 to:
https://bugs.launchpad.net/ubuntu/+source/dbus/+bug/1652471/+subscriptions

-- 
Mailing list: https://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 1652469] [NEW] Boot partition too small, apt-get upgrade fails

[Harald Rudell]

Public bug reported:

PROBLEM:
On install, the boot partition has the size 244.0 MiB or 499,712 sectors

SYMPTOM:
This causes apt-get upgrade to fail at a later time with messages like:

apt-get --yes dist-upgrade
…
update-initramfs: Generating /boot/initrd.img-4.4.0-57-generic
gzip: stdout: No space left on device
E: mkinitramfs failure cpio 141 gzip 1
update-initramfs: failed for /boot/initrd.img-4.4.0-57-generic with 1.
run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
dpkg: error processing package linux-image-extra-4.4.0-57-generic (--configure):
 subprocess installed post-installation script returned error exit status 1
dpkg: dependency problems prevent configuration of linux-image-generic:
 linux-image-generic depends on linux-image-extra-4.4.0-57-generic; however:
  Package linux-image-extra-4.4.0-57-generic is not configured yet.
…
Errors were encountered while processing:
 linux-image-extra-4.4.0-57-generic
 linux-image-generic
 linux-generic
 linux-signed-image-generic
 linux-signed-generic
E: Sub-process /usr/bin/dpkg returned an error code (1)
- status code: 100

FIX:
usually want multiple of 2,048 sectors / 1 MiB
One kernel revision is 56 MiB
Miscellaneous files is 28 MiB
File system overhead is 11 MiB
Typically there are 3 kernels: is the running, the latest and the second to 
latest
56 * 3 + 28 = 196 MiB
A system upgrade requires 120 MiB free
So /boot should be at least 196 + 11 + 120 = 327 MiB in 1 MiB increments
A power of 2 would be 512 MiB or 1,048,576 sectors

** Affects: debian-installer (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Boot partition too small, apt-get upgrade fails

Status in debian-installer package in Ubuntu:
  New

Bug description:
  PROBLEM:
  On install, the boot partition has the size 244.0 MiB or 499,712 sectors

  SYMPTOM:
  This causes apt-get upgrade to fail at a later time with messages like:

  apt-get --yes dist-upgrade
  …
  update-initramfs: Generating /boot/initrd.img-4.4.0-57-generic
  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-57-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: error processing package linux-image-extra-4.4.0-57-generic 
(--configure):
   subprocess installed post-installation script returned error exit status 1
  dpkg: dependency problems prevent configuration of linux-image-generic:
   linux-image-generic depends on linux-image-extra-4.4.0-57-generic; however:
Package linux-image-extra-4.4.0-57-generic is not configured yet.
  …
  Errors were encountered while processing:
   linux-image-extra-4.4.0-57-generic
   linux-image-generic
   linux-generic
   linux-signed-image-generic
   linux-signed-generic
  E: Sub-process /usr/bin/dpkg returned an error code (1)
  - status code: 100

  FIX:
  usually want multiple of 2,048 sectors / 1 MiB
  One kernel revision is 56 MiB
  Miscellaneous files is 28 MiB
  File system overhead is 11 MiB
  Typically there are 3 kernels: is the running, the latest and the second to 
latest
  56 * 3 + 28 = 196 MiB
  A system upgrade requires 120 MiB free
  So /boot should be at least 196 + 11 + 120 = 327 MiB in 1 MiB increments
  A power of 2 would be 512 MiB or 1,048,576 sectors

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

-- 
Mailing list: https://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 1652469] Re: Boot partition too small, apt-get upgrade fails

[Harald Rudell]

GETAROUND
Run the following script before any apt-upgrade
It ensures only two kernels are installed

#!/bin/bash -eu
# ~/bin/auto-remove-kernels
# Remove kernels except the currently running and the latest
# © 2016 Harald Rudell  (http://haraldrudell.com) 
Licence: ISC.

MASTERSTART="$(date +%s%N)"

run() {
  getRunningKernelRelease || return
  echo "Running kernel: $KERNEL_RELEASE"
  MSG="Running: $KERNEL_RELEASE"

  getInstalledKernelReleases || return
  LATEST_RELEASE="${INSTALLED_RELEASES[$((INSTALLED_RELEASES_COUNT-1))]}"
  echo "Latest installed release: $LATEST_RELEASE"
  MSG+=" latest: $LATEST_RELEASE"

  getRemovableReleases "$KERNEL_RELEASE" "${INSTALLED_RELEASES[@]}" || return
  if [ ${#REMOVABLE_RELEASES[@]} -gt 0 ]; then
getPackagesToRemove "${REMOVABLE_RELEASES[@]}" || return
if [ ${#PACKAGES[@]} -eq 0 ]; then
  echo >&2 "Failed to determine what packages to remove"
  return 1
fi
echo "$MSG"
"${LOGGER[@]}" "$MSG" || return

CMD=(sudo apt-get remove --yes ${PACKAGES[@]})
echo "${CMD[*]}"
"${LOGGER[@]}" "${CMD[*]}" || return

"${CMD[@]}" || return

MSG="Package removal ok"
  else MSG+=" no more releases: ok"
  fi

  MSG+=" in $(getDuration "$MASTERSTART") s."
  echo "$MSG"
  "${LOGGER[@]}" "$MSG" || return
}

parseOptions() { # 160301
  SCRIPTNAME="$(basename "${BASH_SOURCE[0]}")"
  LOGGER=(logger --priority local1.info --tag "$SCRIPTNAME[$$]" --)
  NAME="$(hostname):$SCRIPTNAME:$$"
  displayGreeting

  "${LOGGER[@]}" "$NAME: Starting…" || return
}

getRunningKernelRelease() {
  KERNEL_RELEASE="$(doCmd uname --kernel-release)" || return
  KERNEL_RELEASE="$(sed --silent 
's/^\([0-9]\+\.[0-9]\+\.[0-9]\+-[0-9]\+\).*/\1/p' <<<"$KERNEL_RELEASE")"
  if [ ! "$KERNEL_RELEASE" ]; then
echo >&2 "Failed to determine kernel release"
return 1
  fi
}

getInstalledKernelReleases() {
  getLinuxPackages || return
  INSTALLED_RELEASES=($(sed --silent 's/^ii  
linux-[^-]\+-\([0-9]\+\.[0-9]\+\.[0-9]\+-[0-9]\+\).*/\1/p' <<<"$LINUX_PACKAGES" 
| sort --version-sort | uniq))
  INSTALLED_RELEASES_COUNT=${#INSTALLED_RELEASES[@]}
  if [ $INSTALLED_RELEASES_COUNT -lt 1 ]; then
echo >&2 "Failed to determine installed kernel releases"
return 1
  fi
}

getRemovableReleases() { # running-version installed-version…
  local RUNNING="$1"; shift

  REMOVABLE_RELEASES=()
  while [ $# -gt 1 ]; do # skip last
if [ "$1" != "$RUNNING" ]; then
  REMOVABLE_RELEASES+=("$1")
fi
shift
  done
}

getPackagesToRemove() { # releases…
  PACKAGES=()
  while [ $# -ge 1 ]; do
PACKAGES+=($(cut --delimiter=" " --fields=3 <<<"$LINUX_PACKAGES" | fgrep 
"$1" | cat))
shift
  done
}

getLinuxPackages() {
  # LINUX_PACKAGES: string with newlines
  LINUX_PACKAGES="$(doCmd dpkg --list "linux-*")" || return
  LINUX_PACKAGES="$(egrep ^ii <<<"$LINUX_PACKAGES")" || :
}

doCmd() { # [-p] command… 160311
  # echoes command unless first argument is -p
  local AA; local X

  if [ "${1-}" = "-p" ]; then shift
  else echo "$*"
  fi

  AA="$("$@" 2>&1)" && X=0 || X=$?

  if [ $X != 0 ]; then
echo >&2 -e "Status code: $X\nCommand: $*\nOutput: $AA"
return $X
  fi

  [ "$AA" ] && echo "$AA" || :
}

displayGreeting() { # 160301
  echo -e "\n\n===  $NAME $(date --date=@${MASTERSTART:0:-9} 
--rfc-3339=seconds)"
}

getDuration() { # 160223
  # duration in s with .1 s resolution rounded down
  local T0; local T1;
  local DT; local DT_LENGTH
  local RESULT

  if [ $# -eq 0 ]; then RESULT="$(date +%s%N)" # time since 1970-01-01, 
intereger, ns resolution
  else
T0="$1"
T1="$(date +%s%N)"
DT=$((T1 - T0)) # difference in ns
DT_LENGTH=${#DT}
if [ $DT_LENGTH -lt 9 ]; then RESULT="0.0" # less than .1 s
elif [ $DT_LENGTH -eq 9 ]; then RESULT="0.${DT:0:1}" # less than 1 s
else RESULT="${DT:0:$DT_LENGTH-9}.${DT:$DT_LENGTH-9:1}"
fi
  fi

  echo "$RESULT"
}

parseOptions "$@" && run && X=0 || X=$?
if [ $X -ne 0 ]; then
  MSG="$SCRIPTNAME status code: $X"
  echo >&2 "$MSG" || :
  "${LOGGER[@]}" "$MSG" || :
  exit $X
fi


** Package changed: network-manager (Ubuntu) => debian-installer (Ubuntu)

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

Title:
  Boot partition too small, apt-get upgrade fails

Status in debian-installer package in Ubuntu:
  New

Bug description:
  PROBLEM:
  On install, the boot partition has the size 244.0 MiB or 499,712 sectors

  SYMPTOM:
  This causes apt-get upgrade to fail at a later time with messages like:

  apt-get --yes dist-upgrade
  …
  update-initramfs: Generating /boot/initrd.img-4.4.0-57-generic
  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-4.4.0-57-generic with 1.
  run-parts: /etc/kernel/postinst.d/initramfs-tools exited with return code 1
  dpkg: error processing package 

[Touch-packages] [Bug 1651575] Re: goa-daemon starts broken

[Richard]

It appear to not be the same as those two bugs, although the getaround
is the same: restart the daemon

In this case, evolution is attempting to authenticate against a locally
hosted plain password login wrapped in https (off-the-mill php)

Evolution does not offer to store the credentials somewhere, it accepts
them and the next time you start evolution, it says authentication
failed. I could not authenticate until I realized goa-daemon needs a
restart. I had no idea there was a goa-daemon before it broke.

** This bug is no longer a duplicate of bug 1649995
   Replace Google API key used by GNOME services

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

Title:
  goa-daemon starts broken

Status in gnome-online-accounts package in Ubuntu:
  New
Status in gnome-online-accounts package in Fedora:
  Unknown

Bug description:
  goa-daemon, that is started with GNOME Shell/Wayland on login, on
  16.10 launches in a corrupt state where all authentication fails.

  This can be seen by launching Evolution which fails to use credential
  from goa.

  GETAROUND
  restart goa

  killall goa-daemon

  - goa-daemon retarts by itself
  - authentication now works

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.22.2-1~ubuntu16.10.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 20 12:17:37 2016
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (34 days ago)

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

-- 
Mailing list: https://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 798414] Re: update-initramfs should produce a more helpful error when there isn't enough free space

[Jarno Suni]

"a more helpful error" that the title of this bug report calls for would
not free you from the need to remove kernels manually.

I made a script called linux-purge to make it easy to remove extra
kernels even in tricky conditions:
https://www.bountysource.com/issues/38300038-feature-request-the-
command-should-work-like-this (It is designed to handle dependency
problems and even problem running out of inodes - that may occur when
installing a kernel - when using --fix option.)

As for preventing system from getting full of kernels automatically, 
unattended-upgrades provides an adequate solution for most cases. You can 
configure it in Ubuntu 16.04 like this:
Add line 

Unattended-Upgrade::Remove-Unused-Dependencies "true";

in /etc/apt/apt.conf.d/50unattended-upgrades

(since unattended-upgrades is enabled by default in 16.04; the
configuration acts as if running "apt-get autoremove" periodically.)

The default setting in 16.04 is

Unattended-Upgrade::Remove-New-Unused-Dependencies "true";

but that does not work in some cases (Bug #1624644); the former setting
overrides it.

Alternatively, putting "linux-purge --yes --keep 1" as a cron job or alike 
could do automatic kernel purging, (if no other process has locked dpkg at the 
time of calling it).
It has some differences to the unattended-upgrades way:
- It works in 12.04 and 14.04, too. (unattended-upgrades cannot remove manually 
installed kernels that will be around, if user installs kernel using e.g. 
update-manager; Bug #1439769.)
- The number of kernels to keep is configurable. It keeps the given number of 
nearest older kernels of each installed kernel update series, e.g. 
linux-generic and linux-generic-lts-xenial, not necessarily the installed 
kernels with greatest versions. (You could use --auto-only to keep
manually installed kernels, too, but you probably would not want to use it in 
12.04 and 14.04.)
- Current kernel will never be removed. (Bug #1615381)
- It removes configuration files, too. (i.e. it purges)
- It only removes versioned kernel packages whose name start by linux-.

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

Title:
  update-initramfs should produce a more helpful error when there isn't
  enough  free space

Status in initramfs-tools:
  Confirmed
Status in initramfs-tools package in Ubuntu:
  In Progress

Bug description:
  Binary package hint: initramfs-tools

  When generating a new initramfs there is no check for available free
  space, subsequently its possible for update-initramfs to fail due to a
  lack of free space.  This is resulting in package installation
  failures for initramfs-tools.  For example:

  Setting up initramfs-tools (0.98.8ubuntu3) ...
  update-initramfs: deferring update (trigger activated)
  Processing triggers for initramfs-tools ...
  update-initramfs: Generating /boot/initrd.img-2.6.38-8-generic

  gzip: stdout: No space left on device
  E: mkinitramfs failure cpio 141 gzip 1
  update-initramfs: failed for /boot/initrd.img-2.6.38-8-generic
  dpkg: error processing initramfs-tools (--configure):
   subprocess installed post-installation script returned error exit status 1

  WORKAROUND:

  Remove unused kernels using computer janitor (not in repositories for
  14.04 or later) or manually free space on your partition containing
  the /boot file system.

  See instructions here
  https://help.ubuntu.com/community/RemoveOldKernels

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

-- 
Mailing list: https://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 1614943] Re: No ringtone on incoming calls

[Cesar Herrera]

At least tree times the BQ E4.5 didn't ring.

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

Title:
  No ringtone on incoming calls

Status in Canonical System Image:
  Confirmed
Status in telephony-service package in Ubuntu:
  Confirmed

Bug description:
  current build number: 405
  device name: arale
  channel: ubuntu-touch/rc-proposed/meizu.en

  Regularly on incoming calls, there is no ringtone or just a click.
  Apart from that, the notification is displayed, I can answer the call
  normally.

  Phone is not muted, sound is close to the max, and if I reboot it
  works again.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1614943/+subscriptions

-- 
Mailing list: https://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 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

[Stefan Heijnen]

I have exactly the same issue on 16.04:

[172512.094995] audit: type=1400 audit(1482614869.625:1439):
apparmor="DENIED" operation="change_onexec" info="no new privs" error=-1
namespace="root//lxd-torelay_" profile="unconfined"
name="system_tor" pid=128522 comm="(tor)" target="system_tor"

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

Title:
  tor in lxd: apparmor="DENIED" operation="change_onexec"
  namespace="root//CONTAINERNAME_" profile="unconfined"
  name="system_tor"

Status in apparmor package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  

  Distribution: ubuntu
  Distribution version: 16.10
  lxc info:
  apiextensions:

  storage_zfs_remove_snapshots
  container_host_shutdown_timeout
  container_syscall_filtering
  auth_pki
  container_last_used_at
  etag
  patch
  usb_devices
  https_allowed_credentials
  image_compression_algorithm
  directory_manipulation
  container_cpu_time
  storage_zfs_use_refquota
  storage_lvm_mount_options
  network
  profile_usedby
  container_push
  apistatus: stable
  apiversion: "1.0"
  auth: trusted
  environment:
  addresses:
  163.172.48.149:8443
  172.20.10.1:8443
  172.20.11.1:8443
  172.20.12.1:8443
  172.20.22.1:8443
  172.20.21.1:8443
  10.8.0.1:8443
  architectures:
  x86_64
  i686
  certificate: |
  -BEGIN CERTIFICATE-
  -END CERTIFICATE-
  certificatefingerprint: 
3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b
  driver: lxc
  driverversion: 2.0.5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.8.0-27-generic
  server: lxd
  serverpid: 32694
  serverversion: 2.4.1
  storage: btrfs
  storageversion: 4.7.3
  config:
  core.https_address: '[::]:8443'
  core.trust_password: true

  Container: ubuntu 16.10

  
  Issue description
  --

  
  tor can't start in a non privileged container

  
  Logs from the container:
  -

  Dec 7 15:03:00 anonymous tor[302]: Configuration was valid
  Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process 
exited, code=exited, status=231/APPARMOR
  Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay 
network for TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed 
state.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 
'exit-code'.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off 
time over, scheduling restart.
  Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for 
TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset 
devices.list: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to 
set devices.allow on /system.slice/system-tor.slice/tor@default.service: 
Operation not permitted]
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/chr
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/blk
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted


  Logs from the host
  

  audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" 
  pid=12164 comm="(tor)"

  
  Steps to reproduce
  -

  install ubuntu container 16.10 on a ubuntu 16.10 host
  install tor in the container
  Launch tor

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

-- 
Mailing list: https://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 1652381] Re: systematic way to refresh the random-seed again and again

[John Denker]

Here's an even simpler argument why random-seed-load and random-seed-save should
be seen as two separate stateless services, not as the "start" and "stop" of 
some
single long-lived service.

Suppose that during boot-up, random-seed-load fails for some reason.  There are
definitely ways this could happen.  (OTOH there are a surprising number of 
things
that could go wrong that systemd-random-seed save does /not/ report as an error
... but that is a topic for another day.)

Now suppose that in the minutes, hours, or days that follow, the problem is 
resolved.
Desired behavior:  We really want the 'save' service to be performed at 
shutdown.

The currently-observed behavior is that if 'load' failed then 'save' will never 
be
performed.  This is a Bad Thing from the security point of view.

Splitting the services as discussed above makes this issue (among
others) go away.

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

Title:
  systematic way to refresh the random-seed again and again

Status in systemd package in Ubuntu:
  New

Bug description:
  Background and rationale:  There ought to be a nice systematic way to
  refresh the random-seed again and again, while the system is running
  normally, not just at boot time or at shutdown time.

  Sometimes a system may crash without carrying out an orderly shutdown.
  Indeed some systems never carry out an orderly shutdown;  they run
  until they die.  Therefore all the reasons why it is important to
  refresh the random-seed during shutdown are also good reasons for
  refreshing it from time to time during normal operations ... not just
  at startup.

  Desired behavior:  The logical, systematic, traditional, and expected
  way to refresh the seed would be either "systemctl start systemd-
  random-seed" or equivalently "/etc/init.d/urandom start".  The command
  should happily run as many times as desired, and should refresh the
  random-seed each time.

  Observed behavior:  "systemctl start systemd-random-seed" doesn't have
  the desired effect.  Apparently systemd considers the previous
  instance of systemd-random-seed.service to be still active, so
  additional starts don't do any good.  Furthermore,
  "/etc/init.d/urandom start" has been re-implemented in terms of
  "systemctl start systemd-random-seed", so that doesn't work either.

  This is a significant regression relative to the pre-systemd behavior.

  Constructive suggestion.  See attached patch.  Recipe:
   :; systemctl start systemd-random-seed
   -- Observe that /var/lib/systemd/random-seed does not get refreshed.
   :; systemctl stop systemd-random-seed
   -- Apply the patch.
   :; systemctl daemon-reload
   :; systemctl start systemd-random-seed
   :; sleep 60
   :; systemctl start systemd-random-seed
   -- observe that the seed now does get refreshed.

  There may be other ways of dealing with the issue, but this seems nice
  and simple.

  Tangent:  In a non-essential way, this might touch on decisions about
  how best to address https://bugs.launchpad.net/bugs/1651947

  Digression:  There is a policy question as to how often to refresh the
  seed during normal operations.  That is a question for another day.

  ---
  Observed on
  :; lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  :; apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu13
Candidate: 229-4ubuntu13
Version table:
   *** 229-4ubuntu13 500
  500 http://ubuntu.cs.utah.edu/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages

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

-- 
Mailing list: https://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 1652466] [NEW] [Xenial] mesa-va-drivers should be as alternative to Depends of va-driver-all, otherwise, Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium gra

[Amr Ibrahim]

Public bug reported:

What is the problem:
Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium graphics 
in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.

Here is the dependency chain in Xenial:
gstreamer1.0-vaapi Depends on libva1
libva1 Recommends va-driver-all
va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers!)

Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and no 
mesa-va-drivers):
:~$ totem
Stream with high frequencies VQ coding
libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
libva info: va_openDriver() returns -1
libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0
libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
libva info: va_openDriver() returns -1
libva info: VA-API version 0.39.0
libva info: va_getDriverName() returns 0

When mesa-va-drivers is installed, Totem plays videos just fine.

This is fixed in version 1.7.0-2 in Debian and Yakkety.
libva (1.7.0-2) unstable; urgency=medium

  * debian/control:
- Add mesa-va-drivers as alternative to Depends of va-driver-all.
- Bump Standards-Versions.

 -- Sebastian Ramacher   Wed, 11 May 2016 17:32:06
+0200

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: va-driver-all 1.7.0-1
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Sat Dec 24 21:54:20 2016
InstallationDate: Installed on 2016-04-26 (242 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
SourcePackage: libva
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

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

Title:
  [Xenial] mesa-va-drivers should be as alternative to Depends of va-
  driver-all, otherwise, Totem can't play videos if gstreamer1.0-vaapi
  is installed on Gallium graphics

Status in libva package in Ubuntu:
  New

Bug description:
  What is the problem:
  Totem can't play videos if gstreamer1.0-vaapi is installed on Gallium 
graphics in Xenial because mesa-va-drivers is not installed as a dependency of 
va-driver-all.

  Here is the dependency chain in Xenial:
  gstreamer1.0-vaapi Depends on libva1
  libva1 Recommends va-driver-all
  va-driver-all Depends on i965-va-driver vdpau-va-driver (no mesa-va-drivers!)

  Here is the terminal output of Totem (with gstreamer1.0-vaapi installed and 
no mesa-va-drivers):
  :~$ totem
  Stream with high frequencies VQ coding
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/radeonsi_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0
  libva info: Trying to open /usr/lib/x86_64-linux-gnu/dri/gallium_drv_video.so
  libva info: va_openDriver() returns -1
  libva info: VA-API version 0.39.0
  libva info: va_getDriverName() returns 0

  When mesa-va-drivers is installed, Totem plays videos just fine.

  This is fixed in version 1.7.0-2 in Debian and Yakkety.
  libva (1.7.0-2) unstable; urgency=medium

* debian/control:
  - Add mesa-va-drivers as alternative to Depends of va-driver-all.
  - Bump Standards-Versions.

   -- Sebastian Ramacher   Wed, 11 May 2016
  17:32:06 +0200

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: va-driver-all 1.7.0-1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Sat Dec 24 21:54:20 2016
  InstallationDate: Installed on 2016-04-26 (242 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: libva
  UpgradeStatus: No upgrade log present (probably fresh install)

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

-- 
Mailing list: https://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 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  tor in lxd: apparmor="DENIED" operation="change_onexec"
  namespace="root//CONTAINERNAME_" profile="unconfined"
  name="system_tor"

Status in apparmor package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  

  Distribution: ubuntu
  Distribution version: 16.10
  lxc info:
  apiextensions:

  storage_zfs_remove_snapshots
  container_host_shutdown_timeout
  container_syscall_filtering
  auth_pki
  container_last_used_at
  etag
  patch
  usb_devices
  https_allowed_credentials
  image_compression_algorithm
  directory_manipulation
  container_cpu_time
  storage_zfs_use_refquota
  storage_lvm_mount_options
  network
  profile_usedby
  container_push
  apistatus: stable
  apiversion: "1.0"
  auth: trusted
  environment:
  addresses:
  163.172.48.149:8443
  172.20.10.1:8443
  172.20.11.1:8443
  172.20.12.1:8443
  172.20.22.1:8443
  172.20.21.1:8443
  10.8.0.1:8443
  architectures:
  x86_64
  i686
  certificate: |
  -BEGIN CERTIFICATE-
  -END CERTIFICATE-
  certificatefingerprint: 
3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b
  driver: lxc
  driverversion: 2.0.5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.8.0-27-generic
  server: lxd
  serverpid: 32694
  serverversion: 2.4.1
  storage: btrfs
  storageversion: 4.7.3
  config:
  core.https_address: '[::]:8443'
  core.trust_password: true

  Container: ubuntu 16.10

  
  Issue description
  --

  
  tor can't start in a non privileged container

  
  Logs from the container:
  -

  Dec 7 15:03:00 anonymous tor[302]: Configuration was valid
  Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process 
exited, code=exited, status=231/APPARMOR
  Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay 
network for TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed 
state.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 
'exit-code'.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off 
time over, scheduling restart.
  Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for 
TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset 
devices.list: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to 
set devices.allow on /system.slice/system-tor.slice/tor@default.service: 
Operation not permitted]
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/chr
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/blk
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted


  Logs from the host
  

  audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" 
  pid=12164 comm="(tor)"

  
  Steps to reproduce
  -

  install ubuntu container 16.10 on a ubuntu 16.10 host
  install tor in the container
  Launch tor

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

-- 
Mailing list: https://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 1648143] Re: tor in lxd: apparmor="DENIED" operation="change_onexec" namespace="root//CONTAINERNAME_" profile="unconfined" name="system_tor"

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  tor in lxd: apparmor="DENIED" operation="change_onexec"
  namespace="root//CONTAINERNAME_" profile="unconfined"
  name="system_tor"

Status in apparmor package in Ubuntu:
  Confirmed
Status in tor package in Ubuntu:
  Confirmed

Bug description:
  Environment:
  

  Distribution: ubuntu
  Distribution version: 16.10
  lxc info:
  apiextensions:

  storage_zfs_remove_snapshots
  container_host_shutdown_timeout
  container_syscall_filtering
  auth_pki
  container_last_used_at
  etag
  patch
  usb_devices
  https_allowed_credentials
  image_compression_algorithm
  directory_manipulation
  container_cpu_time
  storage_zfs_use_refquota
  storage_lvm_mount_options
  network
  profile_usedby
  container_push
  apistatus: stable
  apiversion: "1.0"
  auth: trusted
  environment:
  addresses:
  163.172.48.149:8443
  172.20.10.1:8443
  172.20.11.1:8443
  172.20.12.1:8443
  172.20.22.1:8443
  172.20.21.1:8443
  10.8.0.1:8443
  architectures:
  x86_64
  i686
  certificate: |
  -BEGIN CERTIFICATE-
  -END CERTIFICATE-
  certificatefingerprint: 
3048baa9f20d316f60a6c602452b58409a6d9e2c3218897e8de7c7c72af0179b
  driver: lxc
  driverversion: 2.0.5
  kernel: Linux
  kernelarchitecture: x86_64
  kernelversion: 4.8.0-27-generic
  server: lxd
  serverpid: 32694
  serverversion: 2.4.1
  storage: btrfs
  storageversion: 4.7.3
  config:
  core.https_address: '[::]:8443'
  core.trust_password: true

  Container: ubuntu 16.10

  
  Issue description
  --

  
  tor can't start in a non privileged container

  
  Logs from the container:
  -

  Dec 7 15:03:00 anonymous tor[302]: Configuration was valid
  Dec 7 15:03:00 anonymous systemd[303]: tor@default.service: Failed at step 
APPARMOR spawning /usr/bin/tor: No such file or directory
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Main process 
exited, code=exited, status=231/APPARMOR
  Dec 7 15:03:00 anonymous systemd[1]: Failed to start Anonymizing overlay 
network for TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Unit entered failed 
state.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed with result 
'exit-code'.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Service hold-off 
time over, scheduling restart.
  Dec 7 15:03:00 anonymous systemd[1]: Stopped Anonymizing overlay network for 
TCP.
  Dec 7 15:03:00 anonymous systemd[1]: tor@default.service: Failed to reset 
devices.list: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted
  Dec 7 15:03:00 anonymous systemd[1]: message repeated 6 times: [ Failed to 
set devices.allow on /system.slice/system-tor.slice/tor@default.service: 
Operation not permitted]
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/chr
  Dec 7 15:03:00 anonymous systemd[1]: Couldn't stat device 
/run/systemd/inaccessible/blk
  Dec 7 15:03:00 anonymous systemd[1]: Failed to set devices.allow on 
/system.slice/system-tor.slice/tor@default.service: Operation not permitted


  Logs from the host
  

  audit: type=1400 audit(1481119378.856:6950): apparmor="DENIED" 
operation="change_onexec" info="label not found" error=-2 
namespace="root//lxd-anonymous_" profile="unconfined" name="system_tor" 
  pid=12164 comm="(tor)"

  
  Steps to reproduce
  -

  install ubuntu container 16.10 on a ubuntu 16.10 host
  install tor in the container
  Launch tor

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

-- 
Mailing list: https://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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[scarline]

*but I can't get any output from them with headphone or HIFI-profile*

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

Title:
  pulseaudio crashes when connecting to bluetooth headphones (due to
  ubuntu changes?)

Status in pulseaudio package in Ubuntu:
  Fix Released
Status in pulseaudio source package in Xenial:
  Fix Released
Status in pulseaudio source package in Yakkety:
  Fix Released

Bug description:
  Impact:

  A patch we carry for Ubuntu touch introduced a change that originally
  was required to make sure PulseAudio did not crash. This patch was
  ported to PulseAudio 8 in Xenial, but the patch author's bluetooth
  hardware that was to hand at the time worked so was assumed to be ok.
  However, the opposite is now happening, i.e PulseAudio is crashing
  with a subset of Bluetooth hardware.

  Regression potential:

  Very low to none. As can be read in this report, much debugging and
  testing has been done to find the problem, and the eventual fix.
  Moreover the change is the removal of a patch hunk that removed a line
  of code originally present in PulseAudio.

  Test case:

  NOTE that this test case applies to bluetooth hardware that is
  identified as not working in this bug report.

  1. Install, or upgrade to Xenial or yakkety.
  2. Pair your bluetooth device in the bluetooth settings in the relevant 
settings application for your desktop environment.
  3. Once paired, you will notice that sound stops working, as pulseaudio has 
thrown an assertion error.
  4. You do not have to remove your audio device from the paired device list, 
but it may be easier to do so for the next part of the testing.
  5. Update to the version of PulseAudio in xenial-proposed which is 
1:8.0-0ubuntu3.1, or in yakkety-proposed, which is 1:9.0-2ubuntu2.1.
  6. Re-pair your device. Audio should continue to work, and you should be able 
to switch to your bluetooth device and use it.

  
  Original bug report:

  When I attempt to connect my Jaybird Bluebuds X to Ubuntu 16.04
  pulseaudio crashes, this does *NOT* happen with a Jambox which leads
  me to believe it's an intermittent problem with some hardware. This
  did not happen on Ubuntu 15.10 (which was an upgrade of 15.04).

  Ubuntu Release:

  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  Pulseaudio Version:

  pulseaudio:
    Installed: 1:8.0-0ubuntu3
    Candidate: 1:8.0-0ubuntu3
    Version table:
   *** 1:8.0-0ubuntu3 500
  500 http://gb.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

  Device info:

  [bluetooth]# info 44:5E:F3:B4:07:29
  Device 44:5E:F3:B4:07:29
   Name: BlueBuds X
   Alias: BlueBuds X
   Class: 0x240404
   Icon: audio-card
   Paired: yes
   Trusted: yes
   Blocked: no
   Connected: no
   LegacyPairing: no
   UUID: Headset   (1108--1000-8000-00805f9b34fb)
   UUID: Audio Sink(110b--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control Target (110c--1000-8000-00805f9b34fb)
   UUID: A/V Remote Control(110e--1000-8000-00805f9b34fb)
   UUID: Handsfree (111e--1000-8000-00805f9b34fb)
   UUID: Unknown   (80ff--1000-8000-00805f9b34fb)

  I have also attached a debug dump of Pulseaudio when attempting to
  connect to the headphones.

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

-- 
Mailing list: https://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 1574324] Re: pulseaudio crashes when connecting to bluetooth headphones (due to ubuntu changes?)

[scarline]

On Xubuntu 16.04, 4.4.0-57-generic jaybird x2 does not work via
bluetooh.

user@user-pc:~$ grep pulse /var/log/syslog*
/var/log/syslog:Dec 24 00:08:38 user-pc pulseaudio[1938]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
/var/log/syslog:Dec 24 00:08:38 user-pc pulseaudio[1938]: [pulseaudio] 
bluez5-util.c: Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_44_5E_F3_C0_BD_E6/fd3 (Operation Not Authorized)
/var/log/syslog:Dec 24 00:19:09 user-pc pulseaudio[1938]: [pulseaudio] 
module.c: Module "module-bluetooth-discover" should be loaded once at most. 
Refusing to load.
/var/log/syslog:Dec 24 00:22:19 user-pc pulseaudio[1938]: [pulseaudio] 
bluez5-util.c: Transport Acquire() failed for transport 
/org/bluez/hci0/dev_44_5E_F3_C0_BD_E6/fd3 (Operation Not Authorized)
/var/log/syslog:Dec 24 03:19:57 user-pc pulseaudio[8105]: [pulseaudio] 
backend-ofono.c: Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
/var/log/syslog:Dec 24 13:39:00 user-pc pulseaudio[8820]: [pulseaudio] 
backend-ofono.c: Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
/var/log/syslog:Dec 24 14:13:17 user-pc pulseaudio[9286]: [pulseaudio] 
backend-ofono.c: Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
/var/log/syslog:Dec 24 15:06:48 user-pc pulseaudio[10012]: [pulseaudio] 
backend-ofono.c: Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
/var/log/syslog:Dec 24 16:18:08 user-pc pulseaudio[1938]: [alsa-sink-ALC668 
Analog] alsa-sink.c: ALSA woke us up to write new data to the device, but there 
was actually nothing to write.
/var/log/syslog:Dec 24 16:18:08 user-pc pulseaudio[1938]: [alsa-sink-ALC668 
Analog] alsa-sink.c: Most likely this is a bug in the ALSA driver 
'snd_hda_intel'. Please report this issue to the ALSA developers.
/var/log/syslog:Dec 24 16:18:08 user-pc pulseaudio[1938]: [alsa-sink-ALC668 
Analog] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent 
snd_pcm_avail() returned 0 or another value < min_avail.
/var/log/syslog:Dec 24 17:01:41 user-pc pulseaudio[10995]: [pulseaudio] 
backend-ofono.c: Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
/var/log/syslog:Dec 24 18:55:36 user-pc pulseaudio[12243]: [pulseaudio] 
backend-ofono.c: Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
/var/log/syslog.1:Dec 23 18:00:30 user-pc pulseaudio[1960]: [alsa-sink-ALC668 
Analog] alsa-sink.c: ALSA woke us up to write new data to the device, but there 
was actually nothing to write.
/var/log/syslog.1:Dec 23 18:00:30 user-pc pulseaudio[1960]: [alsa-sink-ALC668 
Analog] alsa-sink.c: Most likely this is a bug in the ALSA driver 
'snd_hda_intel'. Please report this issue to the ALSA developers.
/var/log/syslog.1:Dec 23 18:00:30 user-pc pulseaudio[1960]: [alsa-sink-ALC668 
Analog] alsa-sink.c: We were woken up with POLLOUT set -- however a subsequent 
snd_pcm_avail() returned 0 or another value < min_avail.
/var/log/syslog.1:Dec 23 20:17:11 user-pc pulseaudio[5693]: [pulseaudio] 
backend-ofono.c: Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
/var/log/syslog.1:Dec 23 21:39:33 user-pc pulseaudio[14506]: [pulseaudio] 
backend-ofono.c: Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
/var/log/syslog.1:Dec 23 22:21:54 user-pc pulseaudio[1960]: [pulseaudio] 
backend-native.c: connect(): Die angeforderte Funktion ist nicht implementiert
/var/log/syslog.1:Dec 23 22:35:58 user-pc pulseaudio[2022]: [pulseaudio] pid.c: 
Daemon already running.
/var/log/syslog.1:Dec 23 22:35:58 user-pc pulseaudio[1967]: [pulseaudio] 
backend-ofono.c: Failed to register as a handsfree audio agent with ofono: 
org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided 
by any .service files
/var/log/syslog.1:Dec 23 22:37:08 user-pc pulseaudio[1967]: [pulseaudio] 
backend-native.c: connect(): Die angeforderte Funktion ist nicht implementiert
/var/log/syslog.1:Dec 23 22:39:09 user-pc pulseaudio[1967]: [pulseaudio] 
backend-native.c: connect(): Die angeforderte Funktion ist nicht implementiert
/var/log/syslog.1:Dec 23 22:42:20 user-pc pulseaudio[1967]: [pulseaudio] 
module.c: Module 

[Touch-packages] [Bug 1652457] [NEW] cannot disable whoopsie via systemd & polkit authentication

[Reverend Homer]

Public bug reported:

Hi,
today I wanted to disable whoopsie service on boot but could not do it via 
Polkit authentication in systemd. So command "systemctl disable whoopsie" 
worked properly only with sudo.

I'm using Ubuntu 16.04.1 LTS and whoopsie-0.2.52.2. Here is some console
log:

ecko@insomnia:~$ systemctl disable whoopsie
Synchronizing state of whoopsie.service with SysV init with 
/lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install disable whoopsie
insserv: fopen(.depend.stop): Permission denied
 AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
Authentication is required to reload the systemd state.
Authenticating as: Reverend Homer,,, (ecko)
Password:
 AUTHENTICATION COMPLETE ===
update-rc.d: error: unable to write /etc/init/whoopsie.override
ecko@insomnia:~$ sudo !!
sudo systemctl disable whoopsie
Synchronizing state of whoopsie.service with SysV init with 
/lib/systemd/systemd-sysv-install...
Executing /lib/systemd/systemd-sysv-install disable whoopsie
insserv: warning: current start runlevel(s) (empty) of script `whoopsie' 
overrides LSB defaults (2 3 4 5).
insserv: warning: current stop runlevel(s) (1 2 3 4 5) of script `whoopsie' 
overrides LSB defaults (1).
ecko@insomnia:~$

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: whoopsie 0.2.52.2
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
Date: Sat Dec 24 21:48:44 2016
InstallationDate: Installed on 2016-10-20 (65 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
JournalErrors:
 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.
 -- Logs begin at Sat 2016-12-24 21:48:19 MSK, end at Sat 2016-12-24 21:48:19 
MSK. --
 Dec 24 21:48:19 hostname org.freedesktop.Notifications[1533]: ** 
(notify-osd:4325): WARNING **: dnd_is_idle_inhibited(): got error "The name 
org.gnome.SessionManager was not provided by any .service files"
RelatedPackageVersions: apport-noui N/A
SourcePackage: whoopsie
UpgradeStatus: No upgrade log present (probably fresh install)
upstart.whoopsie.override: manual

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


** Tags: amd64 apport-bug autoreport-false xenial

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

Title:
  cannot disable whoopsie via systemd & polkit authentication

Status in whoopsie package in Ubuntu:
  New

Bug description:
  Hi,
  today I wanted to disable whoopsie service on boot but could not do it via 
Polkit authentication in systemd. So command "systemctl disable whoopsie" 
worked properly only with sudo.

  I'm using Ubuntu 16.04.1 LTS and whoopsie-0.2.52.2. Here is some
  console log:

  ecko@insomnia:~$ systemctl disable whoopsie
  Synchronizing state of whoopsie.service with SysV init with 
/lib/systemd/systemd-sysv-install...
  Executing /lib/systemd/systemd-sysv-install disable whoopsie
  insserv: fopen(.depend.stop): Permission denied
   AUTHENTICATING FOR org.freedesktop.systemd1.reload-daemon ===
  Authentication is required to reload the systemd state.
  Authenticating as: Reverend Homer,,, (ecko)
  Password:
   AUTHENTICATION COMPLETE ===
  update-rc.d: error: unable to write /etc/init/whoopsie.override
  ecko@insomnia:~$ sudo !!
  sudo systemctl disable whoopsie
  Synchronizing state of whoopsie.service with SysV init with 
/lib/systemd/systemd-sysv-install...
  Executing /lib/systemd/systemd-sysv-install disable whoopsie
  insserv: warning: current start runlevel(s) (empty) of script `whoopsie' 
overrides LSB defaults (2 3 4 5).
  insserv: warning: current stop runlevel(s) (1 2 3 4 5) of script `whoopsie' 
overrides LSB defaults (1).
  ecko@insomnia:~$

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: whoopsie 0.2.52.2
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Sat Dec 24 21:48:44 2016
  InstallationDate: Installed on 2016-10-20 (65 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  JournalErrors:
   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.
   -- Logs begin at Sat 2016-12-24 21:48:19 MSK, end at Sat 2016-12-24 21:48:19 
MSK. --
   Dec 24 21:48:19 hostname org.freedesktop.Notifications[1533]: ** 
(notify-osd:4325): WARNING **: dnd_is_idle_inhibited(): got error "The name 
org.gnome.SessionManager was not provided by any .service files"
  RelatedPackageVersions: apport-noui N/A
  

[Touch-packages] [Bug 1652456] [NEW] video problem

[tom larson]

Public bug reported:

occasionally the screen will darken and just do nothing for a while..
then lighten up and everything is fine.   Also, occasionally the screen
will go into a spasm with multiple colors all across, (with previous
screen barely visable behind it.  I push cont alt del and when the
shutdown window appears, I cancel it and usually screen returns to
normal.  I have upgraded from Ubuntu 15.10 to 16.? LTS and it has
happened a couple more times, maybe not as much.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35
Uname: Linux 4.4.0-58-generic i686
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: i386
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 Dec 24 13:32:28 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) (prog-if 00 [VGA controller])
   Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01ad]
   Subsystem: Dell 82945G/GZ Integrated Graphics Controller [1028:01ad]
InstallationDate: Installed on 2013-06-17 (1286 days ago)
InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release i386 
(20130213)
MachineType: Dell Inc. OptiPlex GX520
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-58-generic 
root=UUID=f5e3dfb6-7bed-4d2c-95fb-38bd30e99447 ro quiet splash vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 11/30/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A11
dmi.board.name: 0XG312
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA11:bd11/30/2006:svnDellInc.:pnOptiPlexGX520:pvr:rvnDellInc.:rn0XG312:rvr:cvnDellInc.:ct3:cvr:
dmi.product.name: OptiPlex GX520
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
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: Sat Dec 24 11:43:54 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputUSB Optical MouseMOUSE, id 8
 inputDell Dell USB Keyboard KEYBOARD, id 9
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id  19 
 vendor HSP
xserver.version: 2:1.18.4-0ubuntu0.2

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


** Tags: apport-bug compiz-0.9 i386 ubuntu xenial

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

Title:
  video problem

Status in xorg package in Ubuntu:
  New

Bug description:
  occasionally the screen will darken and just do nothing for a while..
  then lighten up and everything is fine.   Also, occasionally the
  screen will go into a spasm with multiple colors all across, (with
  previous screen barely visable behind it.  I push cont alt del and
  when the shutdown window appears, I cancel it and usually screen
  returns to normal.  I have upgraded from Ubuntu 15.10 to 16.? LTS and
  it has happened a couple more times, maybe not as much.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-58.79-generic 4.4.35
  Uname: Linux 4.4.0-58-generic i686
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  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 Dec 24 13:32:28 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 82945G/GZ Integrated Graphics Controller [8086:2772] (rev 
02) 

[Touch-packages] [Bug 1652381] Re: systematic way to refresh the random-seed again and again

[John Denker]

OK, I implemented approach (2) from the previous comment.
The work consists of six steps, in two groups of three:

++ create system/systemd-random-seed-load.service
++ create system/systemd-random-seed-save.service
-- get rid of the old system/systemd-random-seed.service

++ create system/sysinit.target.wants/systemd-random-seed-load.service
++ create system/shutdown.target.wants/systemd-random-seed-save.service
-- get rid of the old system/sysinit.target.wants/systemd-random-seed.service

The two new .service files are simple and straightforward.  See attached
patch.

I retract my previous speculation about reimplementing the old
systemd-random-seed.service because AFAICT it was only invoked from
sysinit.target ... and anybody else who tried it almost certainly wasn't
getting acceptable results.

We must drop the whole idea of a systemd-random-seed "service" with an active
state bookended by a single start-event and a single stop-event.  That might
have seemed elegant at first glance, but it did not capture the right semantics.
It did not meet the security needs.

Implementing two separate one-shot services does what is needed.  It is
close to the longstanding init.d/urandom behavior.


** Patch added: "two separate one-shot random-seed services"
   
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1652381/+attachment/4796118/+files/random-seed.patch

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

Title:
  systematic way to refresh the random-seed again and again

Status in systemd package in Ubuntu:
  New

Bug description:
  Background and rationale:  There ought to be a nice systematic way to
  refresh the random-seed again and again, while the system is running
  normally, not just at boot time or at shutdown time.

  Sometimes a system may crash without carrying out an orderly shutdown.
  Indeed some systems never carry out an orderly shutdown;  they run
  until they die.  Therefore all the reasons why it is important to
  refresh the random-seed during shutdown are also good reasons for
  refreshing it from time to time during normal operations ... not just
  at startup.

  Desired behavior:  The logical, systematic, traditional, and expected
  way to refresh the seed would be either "systemctl start systemd-
  random-seed" or equivalently "/etc/init.d/urandom start".  The command
  should happily run as many times as desired, and should refresh the
  random-seed each time.

  Observed behavior:  "systemctl start systemd-random-seed" doesn't have
  the desired effect.  Apparently systemd considers the previous
  instance of systemd-random-seed.service to be still active, so
  additional starts don't do any good.  Furthermore,
  "/etc/init.d/urandom start" has been re-implemented in terms of
  "systemctl start systemd-random-seed", so that doesn't work either.

  This is a significant regression relative to the pre-systemd behavior.

  Constructive suggestion.  See attached patch.  Recipe:
   :; systemctl start systemd-random-seed
   -- Observe that /var/lib/systemd/random-seed does not get refreshed.
   :; systemctl stop systemd-random-seed
   -- Apply the patch.
   :; systemctl daemon-reload
   :; systemctl start systemd-random-seed
   :; sleep 60
   :; systemctl start systemd-random-seed
   -- observe that the seed now does get refreshed.

  There may be other ways of dealing with the issue, but this seems nice
  and simple.

  Tangent:  In a non-essential way, this might touch on decisions about
  how best to address https://bugs.launchpad.net/bugs/1651947

  Digression:  There is a policy question as to how often to refresh the
  seed during normal operations.  That is a question for another day.

  ---
  Observed on
  :; lsb_release -rd
  Description:Ubuntu 16.04.1 LTS
  Release:16.04

  :; apt-cache policy systemd
  systemd:
Installed: 229-4ubuntu13
Candidate: 229-4ubuntu13
Version table:
   *** 229-4ubuntu13 500
  500 http://ubuntu.cs.utah.edu/ubuntu xenial-updates/main amd64 
Packages
  100 /var/lib/dpkg/status
   229-4ubuntu10 500
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
   229-4ubuntu4 500
  500 http://ubuntu.cs.utah.edu/ubuntu xenial/main amd64 Packages

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

-- 
Mailing list: https://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 1551982] Re: uncleared pch fifo underrun on pch transcoder A

[Christopher M. Penalver]

Scott Stensland, to clarify, if you boot into a kernel from 14.04, is
this issue still reproducible?

** Changed in: xorg (Ubuntu)
   Status: Confirmed => 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/1551982

Title:
  uncleared pch fifo underrun on pch transcoder A

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After upgrading from 14.04 to 16.04, the following appears in dmesg and for a 
short while on black ascii screen during login sequence:
  [2.214317] [drm:intel_set_pch_fifo_underrun_reporting [i915]] *ERROR* 
uncleared pch fifo underrun on pch transcoder A
  [2.214339] [drm:intel_pch_fifo_underrun_irq_handler [i915]] *ERROR* PCH 
transcoder A FIFO underrun

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-9.24-generic 4.4.3
  Uname: Linux 4.4.0-9-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  355.00.26  Sun Feb 14 
16:11:36 PST 2016
   GCC version:  gcc version 5.3.1 20160225 (Ubuntu 5.3.1-10ubuntu2)
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Mar  1 16:55:32 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-8-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-9-generic, x86_64: installed
   nvidia-355, 355.00.26, 4.4.0-8-generic, x86_64: installed
   nvidia-355, 355.00.26, 4.4.0-9-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] 3rd Gen Core processor 
Graphics Controller [1462:10b8]
   NVIDIA Corporation GK107M [GeForce GT 645M] [10de:0fd9] (rev a1) (prog-if 00 
[VGA controller])
     Subsystem: Micro-Star International Co., Ltd. [MSI] GK107M [GeForce GT 
645M] [1462:10b8]
  InstallationDate: Installed on 2016-02-29 (1 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160228)
  MachineType: Micro-Star International Co., Ltd. CX61 0NC/CX61 0ND/CX61 
0NF/CX61 0NE
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9-generic 
root=UUID=7ffdb95a-c39d-4d4a-964a-eebefe28f75b ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 10/10/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: E16GBIMS.406
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: MS-16GB
  dmi.board.vendor: Micro-Star International Co., Ltd.
  dmi.board.version: REV:1.0
  dmi.chassis.asset.tag: No Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: CX61 0NC/CX61 0ND/CX61 0NF/CX61 0NE
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrE16GBIMS.406:bd10/10/2012:svnMicro-StarInternationalCo.,Ltd.:pnCX610NC/CX610ND/CX610NF/CX610NE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16GB:rvrREV1.0:cvnCX610NC/CX610ND/CX610NF/CX610NE:ct10:cvrN/A:
  dmi.product.name: CX61 0NC/CX61 0ND/CX61 0NF/CX61 0NE
  dmi.product.version: REV:1.0
  dmi.sys.vendor: Micro-Star International Co., Ltd.
  version.compiz: compiz 1:0.9.12.2+16.04.20160209-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.1.2-1ubuntu1
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.1.2-1ubuntu1
  version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.3-2ubuntu4
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.6.1-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160218-1ubuntu2
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1
  xserver.bootTime: Tue Mar  1 16:33:17 2016
  xserver.configfile: /etc/X11/xorg.conf
  xserver.errors: systemd-logind: failed to get session: PID 931 does not 
belong to any known session
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.17.3-2ubuntu4

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

-- 
Mailing list: https://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 1652455] [NEW] ALSA driver works on login screen but not in desktop

[Artyom Bolshagin]

Public bug reported:

Model is Acer Aspire One D255. Sound not work, but then i add string
options snd-hda-intel model=acer-aspire position_fix=1 enable=yes (found in 
forum)
it begin work in login screen (i hear a sound like a glass crashing), but then 
i login sound settings program show no found sound cards. (aplay -l show this:
LANG= aplay -l
 List of PLAYBACK Hardware Devices 
card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
  Subdevices: 0/1
  Subdevice #0: subdevice #0
)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pulseaudio 1:8.0-0ubuntu3.1
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Uname: Linux 4.4.0-57-generic i686
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: i386
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   artem  2549 F...m firefox
 /dev/snd/controlC0:  artem  2549 F firefox
 /dev/snd/timer:  artem  2549 f firefox
CurrentDesktop: Unity
Date: Sat Dec 24 22:49:05 2016
InstallationDate: Installed on 2016-08-26 (120 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
ProcEnviron:
 LANGUAGE=ru
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=ru_RU.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: 04/22/2011
dmi.bios.vendor: Acer
dmi.bios.version: V3.16(DDR2)
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: JE02_PT
dmi.board.vendor: Acer
dmi.board.version: V3.16(DDR2)
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: V3.16(DDR2)
dmi.modalias: 
dmi:bvnAcer:bvrV3.16(DDR2):bd04/22/2011:svnAcer:pnAOD255:pvrV3.16(DDR2):rvnAcer:rnJE02_PT:rvrV3.16(DDR2):cvnAcer:ct10:cvrV3.16(DDR2):
dmi.product.name: AOD255
dmi.product.version: V3.16(DDR2)
dmi.sys.vendor: Acer

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


** Tags: apport-bug i386 xenial

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

Title:
  ALSA driver works on login screen but not in desktop

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  Model is Acer Aspire One D255. Sound not work, but then i add string
  options snd-hda-intel model=acer-aspire position_fix=1 enable=yes (found in 
forum)
  it begin work in login screen (i hear a sound like a glass crashing), but 
then i login sound settings program show no found sound cards. (aplay -l show 
this:
  LANG= aplay -l
   List of PLAYBACK Hardware Devices 
  card 0: Intel [HDA Intel], device 0: ALC272X Analog [ALC272X Analog]
Subdevices: 0/1
Subdevice #0: subdevice #0
  )

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pulseaudio 1:8.0-0ubuntu3.1
  ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
  Uname: Linux 4.4.0-57-generic i686
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: i386
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   artem  2549 F...m firefox
   /dev/snd/controlC0:  artem  2549 F firefox
   /dev/snd/timer:  artem  2549 f firefox
  CurrentDesktop: Unity
  Date: Sat Dec 24 22:49:05 2016
  InstallationDate: Installed on 2016-08-26 (120 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release i386 (20160719)
  ProcEnviron:
   LANGUAGE=ru
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=ru_RU.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: 04/22/2011
  dmi.bios.vendor: Acer
  dmi.bios.version: V3.16(DDR2)
  dmi.board.asset.tag: Base Board Asset Tag
  dmi.board.name: JE02_PT
  dmi.board.vendor: Acer
  dmi.board.version: V3.16(DDR2)
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: V3.16(DDR2)
  dmi.modalias: 
dmi:bvnAcer:bvrV3.16(DDR2):bd04/22/2011:svnAcer:pnAOD255:pvrV3.16(DDR2):rvnAcer:rnJE02_PT:rvrV3.16(DDR2):cvnAcer:ct10:cvrV3.16(DDR2):
  dmi.product.name: AOD255
  dmi.product.version: V3.16(DDR2)
  dmi.sys.vendor: Acer

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

-- 
Mailing list: https://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 1652449] [NEW] dnsmasq requires restart randomly now and then in order to access random URLs

[Sadi Yumuşak]

Public bug reported:

I use dnsmasq along with a long list of domains blocked in order to
prevent spyware, malware, etc. on my personal computer.

I've begun having frequent DNS problems after upgrading my Ubuntu (64
bit) system from 16.04 to 16.10.

>From time to time a random URL address suddenly becomes unreachable with
varying error messages, most common one that I remember is some sort of
a DNS ERROR.

I've found that the only remedy is this "sudo /etc/init.d/dnsmasq restart".
After that, the problem disappears - for some time.

Such URL addresses cannot be accessed system-wide until dnsmasq service
is restarted, but they can be accessed via Tor Browser only, which
bypasses dnsmasq I guess.

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

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

Title:
  dnsmasq requires restart randomly now and then in order to access
  random URLs

Status in dnsmasq package in Ubuntu:
  New

Bug description:
  I use dnsmasq along with a long list of domains blocked in order to
  prevent spyware, malware, etc. on my personal computer.

  I've begun having frequent DNS problems after upgrading my Ubuntu (64
  bit) system from 16.04 to 16.10.

  From time to time a random URL address suddenly becomes unreachable
  with varying error messages, most common one that I remember is some
  sort of a DNS ERROR.

  I've found that the only remedy is this "sudo /etc/init.d/dnsmasq restart".
  After that, the problem disappears - for some time.

  Such URL addresses cannot be accessed system-wide until dnsmasq
  service is restarted, but they can be accessed via Tor Browser only,
  which bypasses dnsmasq I guess.

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

-- 
Mailing list: https://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 1652448] Re: sound is not working at all

[Tabalot]

I'm trying output the sound by the analog way (desktop speakers)

mteresa@mteresa-PC:~$ cat 
/proc/asound/{version,cards,devices,hwdep,pcm,seq/clients}; sudo rm 
/etc/asound.conf; sudo rm -r ~/.pulse ~/.asound* ;sudo rm ~/.pulse-cookie; sudo 
apt-get update; sudo apt-get install aptitude; sudo aptitude install paman 
gnome-alsamixer libasound2-plugins padevchooser libsdl1.2debian-pulseaudio; 
sudo lshw -short;ls -lart /dev/snd; find /lib/modules/`uname -r` | grep snd 
;cat /dev/sndstat; lspci -nn; lsusb; sudo which alsactl; sudo fuser -v /dev/dsp 
/dev/snd/* ; dpkg -S bin/slmodemd; dmesg | egrep 
'EMU|probe|emu|ALSA|alsa|ac97|udi|snd|ound|irmware'; sudo 
/etc/init.d/sl-modem-daemon status; sudo grep model /etc/modprobe.d/* ; sudo 
dmidecode|egrep 'anufact|roduct|erial|elease'; lsmod | egrep 
'snd|usb|midi|udio'; pacmd list-sinks; aplay -l; sudo alsa force-reload;  
ubuntu-support-status ; sudo lshw -C sound
Advanced Linux Sound Architecture Driver Version k3.19.0-78-generic.
 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xf7d1 irq 30
  1:: sequencer
  2: [ 0]   : control
  3: [ 0- 0]: digital audio playback
  4: [ 0- 0]: digital audio capture
  5: [ 0- 1]: digital audio playback
  6: [ 0- 2]: digital audio capture
  7: [ 0- 0]: hardware dependent
 33:: timer
00-00: HDA Codec 0
00-00: ALC887-VD Analog : ALC887-VD Analog : playback 1 : capture 1
00-01: ALC887-VD Digital : ALC887-VD Digital : playback 1
00-02: ALC887-VD Alt Analog : ALC887-VD Alt Analog : capture 1
Client info
  cur  clients : 1
  peak clients : 1
  max  clients : 192

Client   0 : "System" [Kernel]
  Port   0 : "Timer" (Rwe-)
  Port   1 : "Announce" (R-e-)
Client  14 : "Midi Through" [Kernel]
  Port   0 : "Midi Through Port-0" (RWe-)
[sudo] password for mteresa: 
rm: no s’ha pogut eliminar «/etc/asound.conf»: El fitxer o directori no existeix
rm: no s’ha pogut eliminar «/home/mteresa/.pulse»: El fitxer o directori no 
existeix
rm: no s’ha pogut eliminar «/home/mteresa/.asound*»: El fitxer o directori no 
existeix
rm: no s’ha pogut eliminar «/home/mteresa/.pulse-cookie»: El fitxer o directori 
no existeix
Obj http://archive.canonical.com vivid InRelease
Obj http://es.archive.ubuntu.com vivid InRelease   
Obj http://es.archive.ubuntu.com vivid-updates InRelease   
Obj http://security.ubuntu.com vivid-security InRelease
Obj http://archive.canonical.com vivid/partner Sources 
Obj http://es.archive.ubuntu.com vivid/main Sources
Obj http://archive.canonical.com vivid/partner amd64 Packages  
Obj http://es.archive.ubuntu.com vivid/restricted Sources  
Obj http://archive.canonical.com vivid/partner i386 Packages   
Obj http://es.archive.ubuntu.com vivid/universe Sources   
Obj http://archive.canonical.com vivid/partner Translation-en  
Obj http://es.archive.ubuntu.com vivid/multiverse Sources  
Obj http://es.archive.ubuntu.com vivid/main amd64 Packages 
Obj http://es.archive.ubuntu.com vivid/restricted amd64 Packages   
Obj http://security.ubuntu.com vivid-security/main Sources
Obj http://es.archive.ubuntu.com vivid/universe amd64 Packages
Obj http://es.archive.ubuntu.com vivid/multiverse amd64 Packages
Obj http://security.ubuntu.com vivid-security/restricted Sources
Obj http://es.archive.ubuntu.com vivid/main i386 Packages
Obj http://es.archive.ubuntu.com vivid/restricted i386 Packages
Obj http://es.archive.ubuntu.com vivid/universe i386 Packages  
Obj http://security.ubuntu.com vivid-security/universe Sources
Obj http://es.archive.ubuntu.com vivid/multiverse i386 Packages
Obj http://es.archive.ubuntu.com vivid/main Translation-ca
Obj http://security.ubuntu.com vivid-security/multiverse Sources
Obj http://es.archive.ubuntu.com vivid/main Translation-en 
Obj http://es.archive.ubuntu.com vivid/multiverse Translation-ca   
Obj http://es.archive.ubuntu.com vivid/multiverse Translation-en
Obj http://security.ubuntu.com vivid-security/main amd64 Packages
Obj http://security.ubuntu.com vivid-security/restricted amd64 Packages
Obj http://es.archive.ubuntu.com vivid/restricted Translation-ca   
Obj http://es.archive.ubuntu.com vivid/restricted Translation-en   
Obj http://es.archive.ubuntu.com vivid/universe Translation-ca 
Obj http://security.ubuntu.com vivid-security/universe amd64 Packages
Obj http://es.archive.ubuntu.com vivid/universe Translation-en 
Obj http://es.archive.ubuntu.com vivid-updates/main Sources
Obj http://security.ubuntu.com vivid-security/multiverse amd64 Packages
Obj http://es.archive.ubuntu.com vivid-updates/restricted Sources
Obj http://es.archive.ubuntu.com 

[Touch-packages] [Bug 1651082] Re: package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package procps 2:3.3.10-4ubuntu2.3 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in procps package in Ubuntu:
  Confirmed

Bug description:
  "there was an error installing package" that is the massage i receive
  every time i install a package using terminal.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: procps 2:3.3.10-4ubuntu2.3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-generic 4.4.13
  Uname: Linux 4.4.0-28-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  Date: Mon Dec 19 13:13:39 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2016-06-15 (186 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.15ubuntu0.2
  SourcePackage: procps
  Title: package procps 2:3.3.10-4ubuntu2.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/procps/+bug/1651082/+subscriptions

-- 
Mailing list: https://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 1652448] [NEW] sound is not working at all

[Tabalot]

Public bug reported:

upload=true=true=
!!
!!ALSA Information Script v 0.4.64
!!

!!Script ran on: Sat Dec 24 16:28:32 UTC 2016


!!Linux Distribution
!!--

Ubuntu 15.04 \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 15.04"
NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 15.04"
HOME_URL="http://www.ubuntu.com/; SUPPORT_URL="http://help.ubuntu.com/;
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/;


!!DMI Information
!!---

Manufacturer:  ASUS
Product Name:  All Series
Product Version:   System Version
Firmware Version:  1002


!!Kernel Information
!!--

Kernel release:3.19.0-78-generic
Operating System:  GNU/Linux
Architecture:  x86_64
Processor: x86_64
SMP Enabled:   Yes


!!ALSA Version
!!

Driver version: k3.19.0-78-generic
Library version:1.0.28
Utilities version:  1.0.28


!!Loaded ALSA modules
!!---

snd_hda_intel


!!Sound Servers on this system
!!

Pulseaudio:
  Installed - Yes (/usr/bin/pulseaudio)
  Running - Yes


!!Soundcards recognised by ALSA
!!-

 0 [PCH]: HDA-Intel - HDA Intel PCH
  HDA Intel PCH at 0xf7d1 irq 30


!!PCI Soundcards installed in the system
!!--

00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset
High Definition Audio Controller (rev 05)


!!Advanced information - PCI Vendor/Device/Subsystem ID's
!!---

00:02.0 0300: 8086:0402 (rev 06) (prog-if 00 [VGA controller])
Subsystem: 1043:8534
--
00:1b.0 0403: 8086:8c20 (rev 05)
Subsystem: 1043:8576


!!Modprobe options (Sound related)
!!

snd_atiixp_modem: index=-2
snd_intel8x0m: index=-2
snd_via82xx_modem: index=-2
snd_usb_audio: index=-2
snd_usb_caiaq: index=-2
snd_usb_ua101: index=-2
snd_usb_us122l: index=-2
snd_usb_usx2y: index=-2
snd_cmipci: mpu_port=0x330 fm_port=0x388
snd_pcsp: index=-2
snd_usb_audio: index=-2


!!Loaded sound module options
!!---

!!Module: snd_hda_intel
align_buffer_size : -1
bdl_pos_adj : 
1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
beep_mode : 
N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N
enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y
enable_msi : -1
id : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
index : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
jackpoll_ms : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
model : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
patch : 
(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null)
position_fix : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
power_save : 0
power_save_controller : Y
probe_mask : 
-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1
probe_only : 
0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
single_cmd : N
snoop : -1


!!HDA-Intel Codec information
!!---
--startcollapse--

Codec: Realtek ALC887-VD
Address: 0
AFG Function Id: 0x1 (unsol 1)
Vendor Id: 0x10ec0887
Subsystem Id: 0x10438576
Revision Id: 0x100302
No Modem Function Group found
Default PCM:
rates [0x5f0]: 32000 44100 48000 88200 96000 192000
bits [0xe]: 16 20 24
formats [0x1]: PCM
Default Amp-In caps: N/A
Default Amp-Out caps: N/A
State of AFG node 0x01:
  Power states:  D0 D1 D2 D3 CLKSTOP EPSS
  Power: setting=D0, actual=D0
GPIO: io=2, o=0, i=0, unsolicited=1, wake=0
  IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
  IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0
Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out
  Control: name="Front Playback Volume", index=0, device=0
ControlAmp: chs=3, dir=Out, idx=0, ofs=0
  Device: name="ALC887-VD Analog", type="Audio", device=0
  Amp-Out caps: ofs=0x40, nsteps=0x40, stepsize=0x03, mute=0
  Amp-Out vals:  [0x3e 0x3e]
  Converter: stream=0, channel=0
  PCM:
rates [0x560]: 44100 48000 96000 192000
 

[Touch-packages] [Bug 1651575] Re: goa-daemon starts broken

[Jeremy Bicha]

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

Your problem is just with Google accounts, right? This is because of a
bug in evolution-data-server that is being worked on.

The bugs tracking this issue are:
https://launchpad.net/bugs/1639926
https://launchpad.net/bugs/1649995

Therefore, I'm marking this bug as a duplicate.

** This bug has been marked a duplicate of bug 1649995
   Replace Google API key used by GNOME services

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

Title:
  goa-daemon starts broken

Status in gnome-online-accounts package in Ubuntu:
  New
Status in gnome-online-accounts package in Fedora:
  Unknown

Bug description:
  goa-daemon, that is started with GNOME Shell/Wayland on login, on
  16.10 launches in a corrupt state where all authentication fails.

  This can be seen by launching Evolution which fails to use credential
  from goa.

  GETAROUND
  restart goa

  killall goa-daemon

  - goa-daemon retarts by itself
  - authentication now works

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: gnome-online-accounts 3.22.2-1~ubuntu16.10.1 [origin: 
LP-PPA-gnome3-team-gnome3-staging]
  ProcVersionSignature: Ubuntu 4.8.0-30.32-generic 4.8.6
  Uname: Linux 4.8.0-30-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Dec 20 12:17:37 2016
  SourcePackage: gnome-online-accounts
  UpgradeStatus: Upgraded to yakkety on 2016-11-16 (34 days ago)

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

-- 
Mailing list: https://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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Christopher M. Penalver]

Kai Blin, it will help immensely if you filed a new report with Ubuntu by 
ensuring you have the package xdiagnose installed, and that you click the Yes 
button for attaching additional debugging information running the following 
from a terminal:
ubuntu-bug xorg

Also, please feel free to subscribe me to it.

For more on why this is helpful, please see
https://wiki.ubuntu.com/ReportingBugs.

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

** Tags removed: apport-collected ubuntu

** Attachment removed: "CurrentDmesg.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796023/+files/CurrentDmesg.txt

** Attachment removed: "BootLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796022/+files/BootLog.txt

** Attachment removed: "Dependencies.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796024/+files/Dependencies.txt

** Attachment removed: "LightdmLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796027/+files/LightdmLog.txt

** Attachment removed: "Lsusb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796029/+files/Lsusb.txt

** Attachment removed: "ProcCpuinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796030/+files/ProcCpuinfo.txt

** Attachment removed: "Lspci.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796028/+files/Lspci.txt

** Attachment removed: "JournalErrors.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796026/+files/JournalErrors.txt

** Attachment removed: "ProcEnviron.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796031/+files/ProcEnviron.txt

** Attachment removed: "ProcModules.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796033/+files/ProcModules.txt

** Attachment removed: "UdevDb.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796034/+files/UdevDb.txt

** Attachment removed: "XorgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796035/+files/XorgLog.txt

** Attachment removed: "XorgLogOld.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796036/+files/XorgLogOld.txt

** Attachment removed: "ProcInterrupts.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796032/+files/ProcInterrupts.txt

** Attachment removed: "Xrandr.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796037/+files/Xrandr.txt

** Attachment removed: "xdpyinfo.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796038/+files/xdpyinfo.txt

** Attachment removed: "DpkgLog.txt"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4796025/+files/DpkgLog.txt

** Attachment removed: "Screenshot.png"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1434351/+attachment/4545751/+files/Screenshot.png

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

-- 
Mailing list: https://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 1637950] Re: nano HEAD is stuck in the year 2006

[faissaloo]

The GNU Nano package seriously needs updating as numerous important
changes have been introduced and I'm sick of needing to compile from
source on every machine I own.

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

Title:
  nano HEAD is stuck in the year 2006

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  On https://launchpad.net/nano/head both the timeline and the Downloads
  say that the last release of nano is 1.9.99pre3 from October 2006.
  But the last release is 2.7.1 from a few days ago.  Please adjust
  things so that the timeline and the Downloads show also the most
  recent versions.

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

-- 
Mailing list: https://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 1637950] Re: nano HEAD is stuck in the year 2006

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  nano HEAD is stuck in the year 2006

Status in nano package in Ubuntu:
  Confirmed

Bug description:
  On https://launchpad.net/nano/head both the timeline and the Downloads
  say that the last release of nano is 1.9.99pre3 from October 2006.
  But the last release is 2.7.1 from a few days ago.  Please adjust
  things so that the timeline and the Downloads show also the most
  recent versions.

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

-- 
Mailing list: https://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 1652443] [NEW] Wrong time format of html elements

[Frindli]

Public bug reported:

The default control of the video elements show the duration always in minutes. 
If a time value is heigher than 59 minutes, it not show - for example - 
02:20:13 (2-hour 20-minutes 13-secs), BUT it show 140:13. OOps..
I experience this mistake since the appearance of video control changed (to 
white-blue colors).

** Affects: webbrowser-app (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: media video

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

Title:
  Wrong time format of html  elements

Status in webbrowser-app package in Ubuntu:
  New

Bug description:
  The default control of the video elements show the duration always in 
minutes. If a time value is heigher than 59 minutes, it not show - for example 
- 02:20:13 (2-hour 20-minutes 13-secs), BUT it show 140:13. OOps..
  I experience this mistake since the appearance of video control changed (to 
white-blue colors).

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

-- 
Mailing list: https://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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Kai Blin]

It looks like for me the workaround from comment #5 causes even more
immediate rendering issues. E.g. terminal windows being overlapped by
elements from another window below. Now trying the workaround from
comment #7.

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

-- 
Mailing list: https://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 1591418] Re: Network doesn't switch from 3G to 2G when low connectivity

[Launchpad Bug Tracker]

Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  Network doesn't switch from 3G to 2G when low connectivity

Status in indicator-network package in Ubuntu:
  Confirmed
Status in ofono package in Ubuntu:
  Confirmed

Bug description:
  Hello,

  I've noticed in my flat loosing the network connection to my provider.

  I've tested to move in the same room with android and ubuntu.
  - ubuntu (in 3G) stays in 3G and lost the phone network connectivity,
  - Android (in 3G) switch to 2G and keeps some connectivity.
  - Ubuntu (in 2G) keeps some connectivity.

  Is it a bug or not developed the automatic switch ?

  root@ubuntu-phablet:/home/phablet# system-image-cli -i
  current build number: 330
  device name: mako
  channel: ubuntu-touch/rc-proposed/bq-aquaris.en
  last update: 2016-06-09 23:20:58
  version version: 330
  version ubuntu: 20160610
  version device: 20160401.1
  version custom: 20160504-2-vivid

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

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

[Kai Blin]

apport information

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

** Attachment added: "xdpyinfo.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4796038/+files/xdpyinfo.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

** Attachment added: "LightdmLog.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4796027/+files/LightdmLog.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

** Attachment added: "Xrandr.txt"
   https://bugs.launchpad.net/bugs/1434351/+attachment/4796037/+files/Xrandr.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

** Attachment added: "XorgLogOld.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4796036/+files/XorgLogOld.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

-- 
Mailing list: https://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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Kai Blin]

I managed to get through the unreadable pop-ups by clicking on random
buttons until it worked. Please note that the xorg.conf reported above
is one I just added to try the workaround mentioned in comment #5, I did
not have any xorg.conf set up at the time the bug appeared. I just
thought I'd give reporting the error another try before rebooting to get
a useable system back.

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

** Attachment added: "XorgLog.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4796035/+files/XorgLog.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

** Attachment added: "Lsusb.txt"
   https://bugs.launchpad.net/bugs/1434351/+attachment/4796029/+files/Lsusb.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

** Attachment added: "JournalErrors.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4796026/+files/JournalErrors.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

** Attachment added: "BootLog.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4796022/+files/BootLog.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

** Attachment added: "DpkgLog.txt"
   
https://bugs.launchpad.net/bugs/1434351/+attachment/4796025/+files/DpkgLog.txt

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Kai Blin]

apport information

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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

-- 
Mailing list: https://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 1434351] apport information

[Kai Blin]

ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: XFCE
DistUpgraded: 2016-07-31 00:23:07,940 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
DistroCodename: xenial
DistroRelease: Ubuntu 16.04
DistroVariant: ubuntu
DkmsStatus:
 virtualbox, 5.0.24, 4.4.0-53-generic, x86_64: installed
 virtualbox, 5.0.24, 4.4.0-57-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] (rev 
0b) (prog-if 00 [VGA controller])
   Subsystem: Dell Haswell-ULT Integrated Graphics Controller [1028:060a]
InstallationDate: Installed on 2015-02-11 (681 days ago)
InstallationMedia: Xubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140723)
LightdmDisplayLog:
 (II) AIGLX: Suspending AIGLX clients for VT switch
 (II) AIGLX: Suspending AIGLX clients for VT switch
LightdmGreeterLogOld:
 ** (lightdm-gtk-greeter:1644): WARNING **: Failed to load user image: Failed 
to open file '/home/kai/.face': No such file or directory
 init: indicator-power main process (1677) killed by TERM signal
 init: indicator-application main process (1682) killed by TERM signal
MachineType: Dell Inc. XPS13 9333
Package: xorg 1:7.7+13ubuntu3
PackageArchitecture: amd64
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-57-generic 
root=/dev/mapper/ubuntu-root ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 4.4.0-57.78-generic 4.4.35
Tags:  xenial ubuntu
Uname: Linux 4.4.0-57-generic x86_64
UpgradeStatus: Upgraded to xenial on 2016-07-30 (146 days ago)
UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo
XorgConf:
 Section "Device"
 Identifier "intel"
 Driver "intel"
 Option "AccelMethod" "none"
 EndSection
_MarkForUpload: True
dmi.bios.date: 03/19/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A04
dmi.board.name: 0D13CR
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: 
dmi:bvnDellInc.:bvrA04:bd03/19/2014:svnDellInc.:pnXPS139333:pvr:rvnDellInc.:rn0D13CR:rvrA00:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: XPS13 9333
dmi.sys.vendor: Dell Inc.
version.compiz: compiz N/A
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.2
version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2.2
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2.2
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-0ubuntu0.2
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

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

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

-- 
Mailing list: https://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 1434351] Re: X fonts and widgets disappear after suspend/resume cycle

[Kai Blin]

This still happens. Unfortunately, calling `apport-collect -p xorg
1434351` fails with a popup that is unreadable because fonts are not
rendering, so I have no idea what it is complaining about.

** Changed in: xorg (Ubuntu)
   Status: Expired => Confirmed

** Tags added: apport-collected 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/1434351

Title:
  X fonts and widgets disappear after suspend/resume cycle

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  After a suspend/resume cycle, the screen comes up normally, but every
  time I move my mouse over a piece of text, button, widget, etc, the
  text vanishes and it's replaced by a plain rectangle.

  This does not affect xterm, but it does affect any GTK apps, firefox,
  etc.

  xfce-panel vanishes, although it's still responding to mouse-clicks.
  Newly opened menus are grey rectangles.

  The lines underlining menu hotkeys do NOT disappear.

  In the attached screenshot, you can clearly see which buttons I have
  waved the mouse over, and which I have not.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-intel 2:2.99.917-1~exp1ubuntu2build1
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Thu Mar 19 19:51:37 2015
  InstallationDate: Installed on 2015-03-05 (14 days ago)
  InstallationMedia: Xubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  SourcePackage: xserver-xorg-video-intel
  UpgradeStatus: Upgraded to vivid on 2015-03-19 (0 days ago)

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

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

[Touch-packages] [Bug 1623666] Re: iOS10 will not connect to Ubuntu

[Ulf Mehlig]

same here with Ubuntu 16.10 and iOS 10.2 (14C92). The ppa cited above
does not install on yakkety.

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

Title:
  iOS10 will not connect to Ubuntu

Status in gnutls28 package in Ubuntu:
  Confirmed
Status in libimobiledevice package in Ubuntu:
  Confirmed

Bug description:
  Plug in iOS10 device, and it doesn't show the documents on it.

  Please package the recent fix in libimobiledevice:

  https://github.com/libimobiledevice/libimobiledevice/issues/327

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

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