date:20170125

You have been subscribed to a public bug:

Binary package hint: gnome-panel

This is not a usability bug, it is an aesthetic bug.

The icons in:
 - notification area
 - quick lounge applet
 - icons added as "application launcher"
are all too large!

Right now they are so tall they basically span from top to bottom of the panel.
And this makes it look ugly and unprofessional.
They need to be scaled down some 25%.

ProblemType: Bug
Architecture: amd64
Date: Wed Oct 14 14:13:22 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelModules: nvidia
Package: gnome-panel 1:2.28.0-0ubuntu4
ProcEnviron:
 LANGUAGE=en_US.UTF-8
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-13.45-generic
SourcePackage: gnome-panel
Uname: Linux 2.6.31-13-generic x86_64

** Affects: gnome-panel (Ubuntu)
 Importance: Wishlist
 Status: New


** Tags: apport-bug gnome-panel icons scale
-- 
Icons in gnome panel are too large
https://bugs.launchpad.net/bugs/451228
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to gnome-panel in Ubuntu.

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

[Desktop-packages] [Bug 1638929] Re: after disabling a display, enabling makes screens go black

2017-01-25 Thread Daniel van Vugt

** Tags added: black-screen

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1638929

Title:
  after disabling a display, enabling makes screens go black

Status in Canonical System Image:
  New
Status in Light Display Manager:
  New
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  turn off then turn on some display (output.used = false then output.used = 
true)

  What happens:
  Turning off works fine, turning it back on does not

  What should happen:
  it should work as expected

  USC log: http://pastebin.ubuntu.com/23420797/
  Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/
  Unity8 log (w debug): http://pastebin.ubuntu.com/23451437/

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

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

[Desktop-packages] [Bug 1659470] [NEW] Nautilus won't start any more

2017-01-25 Thread el_gallo_azul

Public bug reported:

I have been using Nautilus for several hours today. I just tried to
start it then, and it wouldn't start.

1) The release of Ubuntu you are using, via 'lsb_release -rd' or System
-> About Ubuntu

el_gallo_azul@W2600CR-850Pro:~$ lsb_release -rd
Description:Ubuntu 16.04.1 LTS
Release:16.04


2) The version of the package you are using, via 'apt-cache policy pkgname' or 
by checking in Software Center

el_gallo_azul@W2600CR-850Pro:~$ apt-cache policy nautilus
nautilus:
  Installed: 1:3.18.4.is.3.14.3-0ubuntu5
  Candidate: 1:3.18.4.is.3.14.3-0ubuntu5
  Version table:
 *** 1:3.18.4.is.3.14.3-0ubuntu5 500
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial-updates/main amd64 Packages
100 /var/lib/dpkg/status
 1:3.18.4.is.3.14.3-0ubuntu4 500
500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main amd64 
Packages

3) What you expected to happen

When I click on the "Files" icon in the Unity launcher, Nautilus starts

4) What happened instead

When I click on the "Files" icon in the Unity launcher, the icon flashes
for about 30 seconds, then stops flashing without Nautilus starting

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.4
Architecture: amd64
CurrentDesktop: Unity
Date: Thu Jan 26 12:46:27 2017
InstallationDate: Installed on 2014-10-14 (834 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
SourcePackage: nautilus
UpgradeStatus: Upgraded to xenial on 2016-08-26 (152 days ago)

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


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1659470

Title:
  Nautilus won't start any more

Status in nautilus package in Ubuntu:
  New

Bug description:
  I have been using Nautilus for several hours today. I just tried to
  start it then, and it wouldn't start.

  1) The release of Ubuntu you are using, via 'lsb_release -rd' or
  System -> About Ubuntu

  el_gallo_azul@W2600CR-850Pro:~$ lsb_release -rd
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  
  2) The version of the package you are using, via 'apt-cache policy pkgname' 
or by checking in Software Center

  el_gallo_azul@W2600CR-850Pro:~$ apt-cache policy nautilus
  nautilus:
Installed: 1:3.18.4.is.3.14.3-0ubuntu5
Candidate: 1:3.18.4.is.3.14.3-0ubuntu5
Version table:
   *** 1:3.18.4.is.3.14.3-0ubuntu5 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu 
xenial-updates/main amd64 Packages
  100 /var/lib/dpkg/status
   1:3.18.4.is.3.14.3-0ubuntu4 500
  500 http://mirror.internode.on.net/pub/ubuntu/ubuntu xenial/main 
amd64 Packages

  3) What you expected to happen

  When I click on the "Files" icon in the Unity launcher, Nautilus
  starts

  4) What happened instead

  When I click on the "Files" icon in the Unity launcher, the icon
  flashes for about 30 seconds, then stops flashing without Nautilus
  starting

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: nautilus 1:3.18.4.is.3.14.3-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.4
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Thu Jan 26 12:46:27 2017
  InstallationDate: Installed on 2014-10-14 (834 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to xenial on 2016-08-26 (152 days ago)

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

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

[Desktop-packages] [Bug 1536605] Re: Machine freezes locally, Xorg EQ overflow

I don't agree the problem does not only apply to Nvidia drivers, because
it seems that using Nouveau can't trigger this EQ overflow here.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1536605

Title:
  Machine freezes locally, Xorg EQ overflow

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed

Bug description:
  We observe spontaneous and not (yet) reproducible freezes on many of
  our heterogeneous PCs. A machine freezes such that it cannot be
  accessed locally anymore (keyboard dead, screen black or with last
  image, sometimes mouse can be moved but no action on clicks) but we
  have full access via ssh. There are no heavy processes or such
  running. Freeze happens sometime during usage but also during screen-
  lock without background activity.

  We have observed the problem
   * on Ubuntu 12.04 and 14.04, 
   * on PCs running a multitude of graphics adapters (nvidia, ati, intel) 
   * on PCs running different versions of e.g. the nvidia driver

  The only log file with some information related to this is
  /var/log/Xorg.0.log where we find

  ==>>===
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing
  events are processed.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7f1bd1327848]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x22b) [0x7f1bd130983b]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x7f1bd11eaf72]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f1bc8621000+0x57fd)
  [0x7f1bc86267fd]
  (EE) 4: /usr/bin/X (0x7f1bd117e000+0x93518) [0x7f1bd1211518]
  (EE) 5: /usr/bin/X (0x7f1bd117e000+0xbbc90) [0x7f1bd1239c90]
  (EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f1bd027a000+0x10340)
  [0x7f1bd028a340]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__poll+0x10) [0x7f1bced86110]
  (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (0x7f1bcec99000+0x1284a0) 
[0x7f1bcedc14a0]
  (EE) 9: /lib/x86_64-linux-gnu/libnsl.so.1 (0x7f1bc7ff7000+0x515f) 
[0x7f1bc7ffc15f]
  (EE) 10: /lib/x86_64-linux-gnu/libnsl.so.1 (yp_match+0xb2) [0x7f1bc7ffc6a2]
  (EE) 11: /lib/x86_64-linux-gnu/libnss_nis.so.2 (_nss_nis_getpwnam_r+0x68)
  [0x7f1bc7df0a98]
  (EE) 12: /lib/x86_64-linux-gnu/libnss_compat.so.2 (0x7f1bc8211000+0x156c)
  [0x7f1bc821256c]
  (EE) 13: /lib/x86_64-linux-gnu/libnss_compat.so.2 
(_nss_compat_getpwnam_r+0x3f7)
  [0x7f1bc8215617]
  (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (getpwnam_r+0xdd) [0x7f1bced5906d]
  (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (getpwnam+0x7f) [0x7f1bced589ff]
  (EE) 16: /usr/bin/X (0x7f1bd117e000+0x1a7ae5) [0x7f1bd1325ae5]
  (EE) 17: /usr/bin/X (0x7f1bd117e000+0x1a8ac7) [0x7f1bd1326ac7]
  (EE) 18: /usr/bin/X (InvalidHost+0x170) [0x7f1bd1327180]
  (EE) 19: /usr/bin/X (ClientAuthorized+0x125) [0x7f1bd1328905]
  (EE) 20: /usr/bin/X (0x7f1bd117e000+0x559ac) [0x7f1bd11d39ac]
  (EE) 21: /usr/bin/X (0x7f1bd117e000+0x55f0e) [0x7f1bd11d3f0e]
  (EE) 22: /usr/bin/X (0x7f1bd117e000+0x59d9a) [0x7f1bd11d7d9a]
  (EE) 23: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) 
[0x7f1bcecbaec5]
  (EE) 24: /usr/bin/X (0x7f1bd117e000+0x451ee) [0x7f1bd11c31ee]
  (EE)
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the
  stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  ==>>===

  
  That then counts in steps of 100 up to 1000 and then the machine is frozen 
locally. Different to other bug reports on similar issues, it appears here that 
libnss_nis.so.2 and libnss_compat.so.2 are involved (user login is via yp).

  Any workaround would be appreciated. I'm happy to provide more details
  if required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1536605/+subscriptions

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

[Desktop-packages] [Bug 1536605] Re: Machine freezes locally, Xorg EQ overflow

I'm running Ubuntu 16.04 with Nvidia 367.57, but still having this EQ
overflow...

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-331-updates in
Ubuntu.
https://bugs.launchpad.net/bugs/1536605

Title:
  Machine freezes locally, Xorg EQ overflow

Status in nvidia-graphics-drivers-331-updates package in Ubuntu:
  Confirmed

Bug description:
  We observe spontaneous and not (yet) reproducible freezes on many of
  our heterogeneous PCs. A machine freezes such that it cannot be
  accessed locally anymore (keyboard dead, screen black or with last
  image, sometimes mouse can be moved but no action on clicks) but we
  have full access via ssh. There are no heavy processes or such
  running. Freeze happens sometime during usage but also during screen-
  lock without background activity.

  We have observed the problem
   * on Ubuntu 12.04 and 14.04, 
   * on PCs running a multitude of graphics adapters (nvidia, ati, intel) 
   * on PCs running different versions of e.g. the nvidia driver

  The only log file with some information related to this is
  /var/log/Xorg.0.log where we find

  ==>>===
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing
  events are processed.
  (EE)
  (EE) Backtrace:
  (EE) 0: /usr/bin/X (xorg_backtrace+0x48) [0x7f1bd1327848]
  (EE) 1: /usr/bin/X (mieqEnqueue+0x22b) [0x7f1bd130983b]
  (EE) 2: /usr/bin/X (QueuePointerEvents+0x52) [0x7f1bd11eaf72]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f1bc8621000+0x57fd)
  [0x7f1bc86267fd]
  (EE) 4: /usr/bin/X (0x7f1bd117e000+0x93518) [0x7f1bd1211518]
  (EE) 5: /usr/bin/X (0x7f1bd117e000+0xbbc90) [0x7f1bd1239c90]
  (EE) 6: /lib/x86_64-linux-gnu/libpthread.so.0 (0x7f1bd027a000+0x10340)
  [0x7f1bd028a340]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (__poll+0x10) [0x7f1bced86110]
  (EE) 8: /lib/x86_64-linux-gnu/libc.so.6 (0x7f1bcec99000+0x1284a0) 
[0x7f1bcedc14a0]
  (EE) 9: /lib/x86_64-linux-gnu/libnsl.so.1 (0x7f1bc7ff7000+0x515f) 
[0x7f1bc7ffc15f]
  (EE) 10: /lib/x86_64-linux-gnu/libnsl.so.1 (yp_match+0xb2) [0x7f1bc7ffc6a2]
  (EE) 11: /lib/x86_64-linux-gnu/libnss_nis.so.2 (_nss_nis_getpwnam_r+0x68)
  [0x7f1bc7df0a98]
  (EE) 12: /lib/x86_64-linux-gnu/libnss_compat.so.2 (0x7f1bc8211000+0x156c)
  [0x7f1bc821256c]
  (EE) 13: /lib/x86_64-linux-gnu/libnss_compat.so.2 
(_nss_compat_getpwnam_r+0x3f7)
  [0x7f1bc8215617]
  (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (getpwnam_r+0xdd) [0x7f1bced5906d]
  (EE) 15: /lib/x86_64-linux-gnu/libc.so.6 (getpwnam+0x7f) [0x7f1bced589ff]
  (EE) 16: /usr/bin/X (0x7f1bd117e000+0x1a7ae5) [0x7f1bd1325ae5]
  (EE) 17: /usr/bin/X (0x7f1bd117e000+0x1a8ac7) [0x7f1bd1326ac7]
  (EE) 18: /usr/bin/X (InvalidHost+0x170) [0x7f1bd1327180]
  (EE) 19: /usr/bin/X (ClientAuthorized+0x125) [0x7f1bd1328905]
  (EE) 20: /usr/bin/X (0x7f1bd117e000+0x559ac) [0x7f1bd11d39ac]
  (EE) 21: /usr/bin/X (0x7f1bd117e000+0x55f0e) [0x7f1bd11d3f0e]
  (EE) 22: /usr/bin/X (0x7f1bd117e000+0x59d9a) [0x7f1bd11d7d9a]
  (EE) 23: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf5) 
[0x7f1bcecbaec5]
  (EE) 24: /usr/bin/X (0x7f1bd117e000+0x451ee) [0x7f1bd11c31ee]
  (EE)
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the
  stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
  ==>>===

  
  That then counts in steps of 100 up to 1000 and then the machine is frozen 
locally. Different to other bug reports on similar issues, it appears here that 
libnss_nis.so.2 and libnss_compat.so.2 are involved (user login is via yp).

  Any workaround would be appreciated. I'm happy to provide more details
  if required.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-331-updates/+bug/1536605/+subscriptions

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

[Desktop-packages] [Bug 1333206] Re: Cannot print on photo paper

2017-01-25 Thread Alberto Salvia Novella

** Description changed:

  HOW TO REPRODUCE:
  - Print a document setting media type as photo paper.
  
  RESULT:
  - The page is printed completely white.
  
  RELEVANT DETAILS:
+ - With other media type set the ink drips from any glossy paper.
  - Known affected printers are HP Deskjet 916c and 930c.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hplip 3.14.3-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CupsErrorLog:
   W [23/Jun/2014:12:59:16 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'DESKJET-916C-Gray..' 
already exists
   W [23/Jun/2014:12:59:16 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'DESKJET-916C-RGB..' 
already exists
  CurrentDesktop: Unity
  Date: Mon Jun 23 13:15:56 2014
  InstallationDate: Installed on 2013-05-21 (397 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Lpstat: device for Deskjet-916c: hp:/usb/DeskJet_916C?serial=HU22N1N0K13U
  MachineType: MEDIONPC MS-7358
  Papersize: a4
  PpdFiles: Deskjet-916c: HP Deskjet 916c, hpcups 3.14.3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=7c16b6a8-52d3-4e20-94c4-933af64fd891 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to trusty on 2014-04-14 (69 days ago)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1333206

Title:
  Cannot print on photo paper

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE:
  - Print a document setting media type as photo paper.

  RESULT:
  - The page is printed completely white.

  RELEVANT DETAILS:
  - With other media type set the ink drips from any glossy paper.
  - Known affected printers are HP Deskjet 916c and 930c.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hplip 3.14.3-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CupsErrorLog:
   W [23/Jun/2014:12:59:16 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'DESKJET-916C-Gray..' 
already exists
   W [23/Jun/2014:12:59:16 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'DESKJET-916C-RGB..' 
already exists
  CurrentDesktop: Unity
  Date: Mon Jun 23 13:15:56 2014
  InstallationDate: Installed on 2013-05-21 (397 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Lpstat: device for Deskjet-916c: hp:/usb/DeskJet_916C?serial=HU22N1N0K13U
  MachineType: MEDIONPC MS-7358
  Papersize: a4
  PpdFiles: Deskjet-916c: HP Deskjet 916c, hpcups 3.14.3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=7c16b6a8-52d3-4e20-94c4-933af64fd891 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to trusty on 2014-04-14 (69 days ago)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

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

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

[Desktop-packages] [Bug 1540262] Re: Photo printing is not available, ink drips over glossy paper

2017-01-25 Thread Alberto Salvia Novella

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

** This bug has been marked a duplicate of bug 1333206
   Cannot print on photo paper

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to hplip in Ubuntu.
https://bugs.launchpad.net/bugs/1540262

Title:
  Photo printing is not available, ink drips over glossy paper

Status in HPLIP:
  Confirmed
Status in hplip package in Ubuntu:
  Triaged

Bug description:
  HOW TO REPRODUCE
  - Print something, selecting as media type "photo paper".

  RESULT
  - A sheet of paper is expelled from the printer without nothing printer.

  RELEVANT DETAILS
  - If you print as plain paper over any kind of glossy paper, the ink drips.
  - The printer model is HP Deskjet 930c.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: printer-driver-postscript-hp 3.15.7-0ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-25.30-generic 4.2.6
  Uname: Linux 4.2.0-25-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CupsErrorLog:

  CurrentDesktop: Unity
  Date: Mon Feb  1 09:43:09 2016
  InstallationDate: Installed on 2015-11-14 (78 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  Lpstat: device for Deskjet-930c: hp:/usb/DeskJet_930C?serial=CN0CE1R0N3JJ
  MachineType: MEDIONPC MS-7358
  PackageArchitecture: all
  Papersize: a4
  PpdFiles: Error: command ['fgrep', '-H', '*NickName', 
'/etc/cups/ppd/Deskjet-930c.ppd'] failed with exit code 2: grep: 
/etc/cups/ppd/Deskjet-930c.ppd: Permission denied
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-25-generic 
root=UUID=4f6d839c-2f04-43a6-9b2c-b5b3ab7d4d1a ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

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

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

[Desktop-packages] [Bug 1333206] Re: Cannot print on photo paper

2017-01-25 Thread Alberto Salvia Novella

** Summary changed:

- Unable to print in photo paper using HP Deskjet 916c
+ Cannot print on photo paper

** Description changed:

- 
- HOW TO REPRODUCE
- 
+ HOW TO REPRODUCE:
+ - Print setting media type as photo paper.
  
- - Using HP Deskjet 916c, try to print a document setting media type as
- photo paper.
+ RESULT:
+ - The page is printed completely white.
  
- 
- **
- EXPECTED BEHAVIOUR
- **
- 
- - The document to be printed.
- 
- **
- REAL BEHAVIOUR
- **
- 
- - A white page is printed.
- 
- **
- TECHNICAL INFO
- **
+ RELEVANT DETAILS:
+ - Known affected printers are HP Deskjet 916c and 930c.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hplip 3.14.3-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CupsErrorLog:
-  W [23/Jun/2014:12:59:16 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'DESKJET-916C-Gray..' 
already exists
-  W [23/Jun/2014:12:59:16 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'DESKJET-916C-RGB..' 
already exists
+  W [23/Jun/2014:12:59:16 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'DESKJET-916C-Gray..' 
already exists
+  W [23/Jun/2014:12:59:16 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'DESKJET-916C-RGB..' 
already exists
  CurrentDesktop: Unity
  Date: Mon Jun 23 13:15:56 2014
  InstallationDate: Installed on 2013-05-21 (397 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Lpstat: device for Deskjet-916c: hp:/usb/DeskJet_916C?serial=HU22N1N0K13U
  MachineType: MEDIONPC MS-7358
  Papersize: a4
  PpdFiles: Deskjet-916c: HP Deskjet 916c, hpcups 3.14.3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=7c16b6a8-52d3-4e20-94c4-933af64fd891 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to trusty on 2014-04-14 (69 days ago)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

** Tags added: xenial

** No longer affects: hplip

** Also affects: hplip
   Importance: Undecided
   Status: New

** Changed in: hplip
   Status: New => Confirmed

** Changed in: hplip (Ubuntu)
   Status: New => Triaged

** Description changed:

  HOW TO REPRODUCE:
- - Print setting media type as photo paper.
+ - Print a document setting media type as photo paper.
  
  RESULT:
  - The page is printed completely white.
  
  RELEVANT DETAILS:
  - Known affected printers are HP Deskjet 916c and 930c.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: hplip 3.14.3-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2
  Uname: Linux 3.13.0-29-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.2
  Architecture: amd64
  CupsErrorLog:
   W [23/Jun/2014:12:59:16 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'DESKJET-916C-Gray..' 
already exists
   W [23/Jun/2014:12:59:16 +0200] CreateProfile failed: 
org.freedesktop.ColorManager.AlreadyExists:profile id 'DESKJET-916C-RGB..' 
already exists
  CurrentDesktop: Unity
  Date: Mon Jun 23 13:15:56 2014
  InstallationDate: Installed on 2013-05-21 (397 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424)
  Lpstat: device for Deskjet-916c: hp:/usb/DeskJet_916C?serial=HU22N1N0K13U
  MachineType: MEDIONPC MS-7358
  Papersize: a4
  PpdFiles: Deskjet-916c: HP Deskjet 916c, hpcups 3.14.3
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-29-generic 
root=UUID=7c16b6a8-52d3-4e20-94c4-933af64fd891 ro quiet splash vt.handoff=7
  SourcePackage: hplip
  UpgradeStatus: Upgraded to trusty on 2014-04-14 (69 days ago)
  dmi.bios.date: 02/18/2008
  dmi.bios.vendor: Phoenix Technologies, LTD
  dmi.bios.version: 6.00 PG
  dmi.board.name: MS-7358
  dmi.board.vendor: MICRO-STAR INTERNATIONAL CO., LTD
  dmi.board.version: Fab D
  dmi.chassis.type: 3
  dmi.chassis.vendor: OEM
  dmi.chassis.version: OEM
  dmi.modalias: 
dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd02/18/2008:svnMEDIONPC:pnMS-7358:pvrOEM:rvnMICRO-STARINTERNATIONALCO.,LTD:rnMS-7358:rvrFabD:cvnOEM:ct3:cvrOEM:
  dmi.product.name: MS-7358
  dmi.product.version: OEM
  dmi.sys.vendor: MEDIONPC

-- 
You received this bug notification because you are a member of

[Desktop-packages] [Bug 1652564] Re: [i965 gen7][regression][patch]Intel mesa driver raises SIGFPE.

2017-01-25 Thread dnord

Fixed with mesa 12.0.6-0ubuntu0.16.04.1 from proposed on xenial.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1652564

Title:
  [i965 gen7][regression][patch]Intel mesa driver raises SIGFPE.

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Yakkety:
  Fix Released

Bug description:
  There was a regression in intel mesa driver that caused raise of
  SIGFPE signal which resulted in startup error messages (about division
  by zero or invalid floating point operation) in some applications and
  games sensitive to this behavior.

  Currently it resolved in upstream:
  https://bugs.freedesktop.org/show_bug.cgi?id=95419
  By following commit:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=01c89ccc5d1529aa1efbae80c8ef641a59abbd93
  Is it possible to include foregoing patch to avoid bug in current 
distributions?

  Distribution: Ubuntu 16.04
  Video card: Intel HD 4600
  Mesa version: 11.2.0-1ubuntu2.2

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

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

[Desktop-packages] [Bug 1076880] Re: network speed incorrectly reported in System Monitor using VPN

2017-01-25 Thread Bannaz

BTW THE BUG IS 5 YEARS OLD?

THE CAUSE IS TUNNEL TRAFFIC; ITS BEING COUNTED!

DON'T COUNT IT PLEASE!

VERY SIMPLE!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-system-monitor in Ubuntu.
https://bugs.launchpad.net/bugs/1076880

Title:
  network speed incorrectly reported in System Monitor using VPN

Status in gnome-system-monitor package in Ubuntu:
  Confirmed

Bug description:
  looks similar to bug #957617

  When using a VPN and monitoring up and download speeds shown in System
  monitor (ubuntu 12.04), then the indicated speeds are much greater
  than they apparently should be. When VPN is stoped and normal
  connection used, then indicate speeds are as expected.

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

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

[Desktop-packages] [Bug 1438510] Re: [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial and 16.10 yakkety

2017-01-25 Thread Martin

#57 Thank you SO MUCH! That script worked perfectly for me!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1438510

Title:
  [REGRESSION] bluetooth headset no longer supports a2dp in 16.04 xenial
  and 16.10 yakkety

Status in PulseAudio:
  Unknown
Status in bluez package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in bluez source package in Vivid:
  Won't Fix
Status in pulseaudio source package in Vivid:
  Won't Fix

Bug description:
  Just installed 15.04 fresh from the latest ISO (beta2).

  I'm bummed to see my bluetooth headset (Bose Soundlink overear) seems
  to have regressed in functionality.

  In 14.10, I was able to set the output profile either to a2dp or
  hsp/hfp (telephony duplex).

  In 15.04, it only works in telephony duplex mode.  I can't get high
  fidelity sound playback to work at all.

  This thread seems to be related, though the workaround within did not solve 
the problem for me:
  https://bbs.archlinux.org/viewtopic.php?id=194006

  The bug is still present in 16.04 LTS and 16.10.

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

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

[Desktop-packages] [Bug 1641017] Please test proposed package

Hello Boaz, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1641017

Title:
  Mesa 12.0.5 - multiple important fixes, stable branch

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Mesa 12.0.5 is now available as a point release in the stable branch. Mesa 
has MRE for these.

  The release contains multiple fixes amongst which:
  The nouveau vdpau driver performance has been restored. The wayland-egl
  module no longer crashes if the user calls eglDestroySurface and
  wl_egl_window_destroy in the "wrong" order. libEGL correctly advertises
  the EGL platforms available. Multiple fd leaks were addressed, which
  could prevent rmmod of devices such as the DisplayLink drivers. Radeonsi
  has gained noticeable performance by disabling ReZ. Interop between third
  party OpenCL implementations and mesa's libGL/libEGL is back online...
  and many more.

  Full changelog:
  https://lists.freedesktop.org/archives/mesa-dev/2016-November/135027.html

  I am particularly interested in the RadeonSI performance boost:
  https://lists.freedesktop.org/archives/mesa-dev/2016-October/131759.html
  In real-world tests the boost is about 20% (Yay!) :
  
http://www.phoronix.com/scan.php?page=news_item=Mesa-Post-ReZ-Change-Benchmarks

  [Test case]
  Run the default desktop and maybe a game or two.

  This release has been tested on xenial by the certification team on a set of 
machines, covering:
  Intel Haswell
  Intel Broadwell
  Intel Skylake
  AMD Mobility Radeon HD 5430/5450/5470

  and they all passed the tests.

  Once this is in -proposed, the community will be asked to test it on a
  wider range of devices.

  [Regression potential]
  yakkety: the release consists of cherry-picks from master, specifically 
selected as bugfixes. Regression potential should be low.

  xenial: it's a bigger bump for xenial, but since yakkety already ships
  with this series the risk should be low

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

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

[Desktop-packages] [Bug 1641017] Re: Mesa 12.0.5 - multiple important fixes, stable branch

Hello Boaz, or anyone else affected,

Accepted mesa into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1641017

Title:
  Mesa 12.0.5 - multiple important fixes, stable branch

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]
  Mesa 12.0.5 is now available as a point release in the stable branch. Mesa 
has MRE for these.

  The release contains multiple fixes amongst which:
  The nouveau vdpau driver performance has been restored. The wayland-egl
  module no longer crashes if the user calls eglDestroySurface and
  wl_egl_window_destroy in the "wrong" order. libEGL correctly advertises
  the EGL platforms available. Multiple fd leaks were addressed, which
  could prevent rmmod of devices such as the DisplayLink drivers. Radeonsi
  has gained noticeable performance by disabling ReZ. Interop between third
  party OpenCL implementations and mesa's libGL/libEGL is back online...
  and many more.

  Full changelog:
  https://lists.freedesktop.org/archives/mesa-dev/2016-November/135027.html

  I am particularly interested in the RadeonSI performance boost:
  https://lists.freedesktop.org/archives/mesa-dev/2016-October/131759.html
  In real-world tests the boost is about 20% (Yay!) :
  
http://www.phoronix.com/scan.php?page=news_item=Mesa-Post-ReZ-Change-Benchmarks

  [Test case]
  Run the default desktop and maybe a game or two.

  This release has been tested on xenial by the certification team on a set of 
machines, covering:
  Intel Haswell
  Intel Broadwell
  Intel Skylake
  AMD Mobility Radeon HD 5430/5450/5470

  and they all passed the tests.

  Once this is in -proposed, the community will be asked to test it on a
  wider range of devices.

  [Regression potential]
  yakkety: the release consists of cherry-picks from master, specifically 
selected as bugfixes. Regression potential should be low.

  xenial: it's a bigger bump for xenial, but since yakkety already ships
  with this series the risk should be low

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

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

[Desktop-packages] [Bug 1643789] Re: Backport packages for 16.04.2 lts-hwe stack

Hello Timo, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1643789

Title:
  Backport packages for 16.04.2 lts-hwe stack

Status in libclc package in Ubuntu:
  Invalid
Status in libdrm package in Ubuntu:
  Invalid
Status in mesa package in Ubuntu:
  Invalid
Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Invalid
Status in xserver-xorg-video-ati package in Ubuntu:
  Invalid
Status in libclc source package in Xenial:
  Won't Fix
Status in libdrm source package in Xenial:
  Fix Committed
Status in mesa source package in Xenial:
  Fix Committed
Status in xserver-xorg-video-amdgpu source package in Xenial:
  New
Status in xserver-xorg-video-ati source package in Xenial:
  New

Bug description:
  [Impact]
  We need a few packages backported to xenial for lts-hwe X stack.

  Since the xserver is already at 1.18.4, the full stack from 16.10 will
  not be backported as a renamed set of packages. Instead, only the
  drivers with bugfix releases will be backported, plus the libraries
  and mesa that complement the set.

  [Test case]

  Run a desktop session, see that things still work

  [Regression potential]

  libdrm:
  slim to none, changes from 2.4.67..2.4.70:
  - amdgpu: spelling fixes
  - ati: typo-/make check fixes
  - intel: pci-id changes, already SRU'd
  - nouveau: only some android makefile diff
  - core: drmGetDevice fixes for multi-gpu

  mesa:
  included here just to keep the necessary backport bits in the same bug, the 
actual update testing will be handled on bug #1641017. That said:
  - Intel validates new upstream releases on all their hw
  - AMD probably does the same, though it's unverified
  - this release was already tested by cert team on a handful of intel/amd 
machines

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

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

[Desktop-packages] [Bug 1652486] Please test proposed package

Hello undefined, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

Title:
  mesa gpu lockup

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Yakkety:
  Fix Committed

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/mesa/+bug/1652486/+subscriptions

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

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

Hello undefined, or anyone else affected,

Accepted mesa into yakkety-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.10.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

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

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

Title:
  mesa gpu lockup

Status in Mesa:
  Unknown
Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Yakkety:
  Fix Committed

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/mesa/+bug/1652486/+subscriptions

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

[Desktop-packages] [Bug 1652564] Re: [i965 gen7][regression][patch]Intel mesa driver raises SIGFPE.

Hello dnord, or anyone else affected,

Accepted mesa into xenial-proposed. The package will build now and be
available at
https://launchpad.net/ubuntu/+source/mesa/12.0.6-0ubuntu0.16.04.1 in a
few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

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

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1652564

Title:
  [i965 gen7][regression][patch]Intel mesa driver raises SIGFPE.

Status in mesa package in Ubuntu:
  Fix Released
Status in mesa source package in Xenial:
  Fix Committed
Status in mesa source package in Yakkety:
  Fix Released

Bug description:
  There was a regression in intel mesa driver that caused raise of
  SIGFPE signal which resulted in startup error messages (about division
  by zero or invalid floating point operation) in some applications and
  games sensitive to this behavior.

  Currently it resolved in upstream:
  https://bugs.freedesktop.org/show_bug.cgi?id=95419
  By following commit:
  
https://cgit.freedesktop.org/mesa/mesa/commit/?id=01c89ccc5d1529aa1efbae80c8ef641a59abbd93
  Is it possible to include foregoing patch to avoid bug in current 
distributions?

  Distribution: Ubuntu 16.04
  Video card: Intel HD 4600
  Mesa version: 11.2.0-1ubuntu2.2

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

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

[Desktop-packages] [Bug 1601971] Re: update fails, "AppStream cache update failed."

2017-01-25 Thread katsiki

I also get an error with installation to SSD:

sudo apt-get update
Hit:1 http://us.archive.ubuntu.com/ubuntu xenial InRelease  
Get:2 http://us.archive.ubuntu.com/ubuntu xenial-updates InRelease [102 kB] 
Get:3 http://security.ubuntu.com/ubuntu xenial-security InRelease [102 kB]  
  
Hit:4 http://us.archive.ubuntu.com/ubuntu xenial-backports InRelease
   
Fetched 204 kB in 10s (18.6 kB/s)   
   
AppStream cache update completed, but some metadata was ignored due to errors.
Reading package lists... Done

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1601971

Title:
  update fails, "AppStream cache update failed."

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  Booted 16.04 amd64 from DVD, opened a gnome-terminal and ran,

  ubuntu@ubuntu:~$ sudo apt-get update
  Ign:1 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) 
xenial InRelease
  Hit:2 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) 
xenial Release
  Get:4 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]  
 
  Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]   
 
  Get:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:7 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 
[119 kB]
  Get:8 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1,201 kB]
  Get:9 http://archive.ubuntu.com/ubuntu xenial/main Translation-en [568 kB]
   
  Get:10 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en 
[45.3 kB]
  Get:11 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 
Metadata [44.0 kB]
  Get:12 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 
Icons [50.8 kB]
  Get:13 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 
DEP-11 Metadata [158 B]
  Get:14 http://archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 Metadata 
[733 kB]
  Get:15 http://archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons [409 
kB]
  Get:16 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 
[252 kB]
  Get:17 http://archive.ubuntu.com/ubuntu xenial-updates/main Translation-en 
[99.8 kB]
  Get:18 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 
Metadata [186 kB]
  Get:19 http://archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 
Icons [150 kB]
  Get:20 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 
DEP-11 Metadata [157 B]
  Fetched 4,293 kB in 1s (2,360 kB/s) 

  ** (appstreamcli:2593): CRITICAL **: Error while moving old database out of 
the way.
  AppStream cache update failed.
  Reading package lists... Done

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  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
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Mon Jul 11 19:24:40 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1601971] Re: update fails, "AppStream cache update failed."

2017-01-25 Thread katsiki

I forgot to add that installation was with ubuntu-16.04.1-desktop-
amd64.iso.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1601971

Title:
  update fails, "AppStream cache update failed."

Status in appstream package in Ubuntu:
  Confirmed

Bug description:
  Booted 16.04 amd64 from DVD, opened a gnome-terminal and ran,

  ubuntu@ubuntu:~$ sudo apt-get update
  Ign:1 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) 
xenial InRelease
  Hit:2 cdrom://Ubuntu 16.04 LTS _Xenial Xerus_ - Release amd64 (20160420.1) 
xenial Release
  Get:4 http://archive.ubuntu.com/ubuntu xenial InRelease [247 kB]  
 
  Get:5 http://security.ubuntu.com/ubuntu xenial-security InRelease [94.5 kB]   
 
  Get:6 http://archive.ubuntu.com/ubuntu xenial-updates InRelease [94.5 kB]
  Get:7 http://security.ubuntu.com/ubuntu xenial-security/main amd64 Packages 
[119 kB]
  Get:8 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages [1,201 kB]
  Get:9 http://archive.ubuntu.com/ubuntu xenial/main Translation-en [568 kB]
   
  Get:10 http://security.ubuntu.com/ubuntu xenial-security/main Translation-en 
[45.3 kB]
  Get:11 http://security.ubuntu.com/ubuntu xenial-security/main amd64 DEP-11 
Metadata [44.0 kB]
  Get:12 http://security.ubuntu.com/ubuntu xenial-security/main DEP-11 64x64 
Icons [50.8 kB]
  Get:13 http://security.ubuntu.com/ubuntu xenial-security/restricted amd64 
DEP-11 Metadata [158 B]
  Get:14 http://archive.ubuntu.com/ubuntu xenial/main amd64 DEP-11 Metadata 
[733 kB]
  Get:15 http://archive.ubuntu.com/ubuntu xenial/main DEP-11 64x64 Icons [409 
kB]
  Get:16 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages 
[252 kB]
  Get:17 http://archive.ubuntu.com/ubuntu xenial-updates/main Translation-en 
[99.8 kB]
  Get:18 http://archive.ubuntu.com/ubuntu xenial-updates/main amd64 DEP-11 
Metadata [186 kB]
  Get:19 http://archive.ubuntu.com/ubuntu xenial-updates/main DEP-11 64x64 
Icons [150 kB]
  Get:20 http://archive.ubuntu.com/ubuntu xenial-updates/restricted amd64 
DEP-11 Metadata [157 B]
  Fetched 4,293 kB in 1s (2,360 kB/s) 

  ** (appstreamcli:2593): CRITICAL **: Error while moving old database out of 
the way.
  AppStream cache update failed.
  Reading package lists... Done

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1
  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
  CasperVersion: 1.376
  CurrentDesktop: Unity
  Date: Mon Jul 11 19:24:40 2016
  LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: appstream
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1638929] Re: after disabling a display, enabling makes screens go black

2017-01-25 Thread Bill Filler

@jgdx
Can you make sure that silo 2140 is up to date so this can be tested again?

thanks

** Also affects: ubuntu-system-settings (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: ubuntu-system-settings (Ubuntu)
 Assignee: (unassigned) => Jonas G. Drange (jonas-drange)

** Changed in: ubuntu-system-settings (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1638929

Title:
  after disabling a display, enabling makes screens go black

Status in Canonical System Image:
  New
Status in Light Display Manager:
  New
Status in Mir:
  Invalid
Status in QtMir:
  Confirmed
Status in lightdm package in Ubuntu:
  New
Status in ubuntu-system-settings package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Reproduce:
  turn off then turn on some display (output.used = false then output.used = 
true)

  What happens:
  Turning off works fine, turning it back on does not

  What should happen:
  it should work as expected

  USC log: http://pastebin.ubuntu.com/23420797/
  Unity8 log: (see that  mirserver: Disabled works fine) 
http://pastebin.ubuntu.com/23420803/
  Unity8 log (w debug): http://pastebin.ubuntu.com/23451437/

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

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

[Desktop-packages] [Bug 1577197] Re: Pulseaudio bluez5-util.c: TryAcquire() failed - Operation Not Authorized

2017-01-25 Thread Uwe Friebe

I have this problem with my Plantronics BackBeat. Device is connected, but I 
can't use it at all.
a2dp.py does not help. It tells me pulseAudio service does not run.

./a2dp.py
Connection MADE
Selecting device:
1. 0C:E0:E4:9E:73:7C PLT_BBTSENSE
2. 98:FD:B4:0D:74:E7 ThinkPad Bluetooth Laser Mouse
Select device[1]:
1
Device MAC: 0C:E0:E4:9E:73:7C
Command: pacmd list-sinks failed with status: 1
stderr: Es läuft kein PulseAudio-Dienst oder nicht als Sessiondienst.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1577197

Title:
  Pulseaudio bluez5-util.c: TryAcquire() failed  - Operation Not
  Authorized

Status in bluez package in Ubuntu:
  Confirmed
Status in indicator-sound package in Ubuntu:
  Invalid
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  Pulseaudio outright stops audio via Bluetooth after sleep or prolonged period 
of time. Only restart fixes the issue. This started early 2016 in 15.10.
  Issue is discussed here as well 
http://askubuntu.com/questions/763539/bluetooth-speaker-no-sound-in-ubuntu-16-04
 and mentioned in other unrelated bugs.

  Ubuntu Xenial 16.04 LTS

  The log below:

  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] 
module-bluez5-device.c: Default profile not connected, selecting off profile
  May  1 17:18:07 jalexoidmobile bluetoothd[7349]: 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4: fd(35) ready
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 3 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Successfully made thread 
10967 of process 2884 (n/a) owned by '1000' RT at priority 5.
  May  1 17:18:07 jalexoidmobile rtkit-daemon[1794]: Supervising 4 threads of 1 
processes of 1 users.
  May  1 17:18:07 jalexoidmobile pulseaudio[2884]: [pulseaudio] bluez5-util.c: 
Transport TryAcquire() failed for transport 
/org/bluez/hci0/dev_00_02_3C_05_99_F2/fd4 (Operation Not Authorized)
  May  1 17:18:07 jalexoidmobile kernel: [20583.032442] input: 
00:02:3C:05:99:F2 as /devices/virtual/input/input24
  May  1 17:18:19 jalexoidmobile pulseaudio[2884]: [pulseaudio] sink-input.c: 
Failed to create sink input: sink is suspended.


  Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 001 Device 006: ID 04f2:b2da Chicony Electronics Co., Ltd thinkpad t430s 
camera
  Bus 001 Device 008: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 
[ThinkPad]
  Bus 001 Device 004: ID 147e:2020 Upek TouchChip Fingerprint Coprocessor (WBF 
advanced mode)
  Bus 001 Device 003: ID 17ef:1003 Lenovo Integrated Smart Card Reader
  Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
  Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
  Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

  [20388.983474] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
  [20389.070114] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
  [20389.070120] usb 1-1.4: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
  [20389.070122] usb 1-1.4: Product: BCM20702A0
  [20389.070124] usb 1-1.4: Manufacturer: Broadcom Corp
  [20389.070126] usb 1-1.4: SerialNumber: 446D578686DD
  [20389.076232] Bluetooth: hci0: BCM: chip id 63
  [20389.092220] Bluetooth: hci0: BCM20702A
  [20389.093225] Bluetooth: hci0: BCM20702A1 (001.002.014) build 
  [20389.551476] wlan0: authenticate with a0:63:91:2f:3f:ed
  [20389.554391] wlan0: send auth to a0:63:91:2f:3f:ed (try 1/3)
  [20389.557790] wlan0: authenticated
  [20389.558339] wlan0: associate with a0:63:91:2f:3f:ed (try 1/3)
  [20389.562209] wlan0: RX AssocResp from a0:63:91:2f:3f:ed (capab=0x1411 
status=0 aid=2)
  [20389.581260] wlan0: associated
  [20389.581369] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
  [20389.830185] Bluetooth: hci0: BCM20702A1 (001.002.014) build 1669
  [20389.846186] Bluetooth: hci0: Broadcom Bluetooth Device
  [20418.269466] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input23
  [20583.032442] input: 00:02:3C:05:99:F2 as /devices/virtual/input/input24

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

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

[Desktop-packages] [Bug 1659430] Re: x-staging problem report, redux

2017-01-25 Thread Blake Tregre

** Attachment added: "dmesg output"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1659430/+attachment/4809132/+files/dmesg.txt

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1659430

Title:
  x-staging problem report, redux

Status in xorg package in Ubuntu:
  New

Bug description:
  I previously reported a X freeze and screen powering off bug over here
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1655803.  I had
  hoped that some of the fixes in  newer mesa releases would fix it, but
  alas I having the same problem on the latest x-staging mesa.  After
  15-30 minutes of activity (emacs, terminal, chrome) X freezes, the
  screen turns disco colors, and the screen powers down.  My machine is
  usually completely hung (can't ssh in or ping), but I was able to ssh
  in a collect a few logs (possible redundant, included below) this last
  time.  Thanks, I hope this helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Wed Jan 25 13:10:22 2017
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-57-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed
   nvidia-375, 375.26, 4.4.0-57-generic, x86_64: installed
   nvidia-375, 375.26, 4.4.0-59-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT GL [FirePro W9000] 
[1002:6780] (prog-if 00 [VGA controller])
 Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT GL [FirePro 
W9000] [1002:031e]
  MachineType: Dell Inc. Precision WorkStation T7500
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=UUID=4bb35b69-210e-445c-b815-725f1bb7e010 ro radeon.msi=0 quiet splash 
nouveau.blacklist=1 vt.handoff=7
  SourcePackage: xorg
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/21/2011
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A09
  dmi.board.name: 06FW8P
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A01
  dmi.chassis.type: 7
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/21/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA01:cvnDellInc.:ct7:cvr:
  dmi.product.name: Precision WorkStation T7500
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
  version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.3-1ubuntu3~16.04.02
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.3-1ubuntu3~16.04.02
  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: Wed Jan 25 12:44:23 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.version: 2:1.18.4-0ubuntu0.2
  xserver.video_driver: radeon

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

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

[Desktop-packages] [Bug 1659430] [NEW] x-staging problem report, redux

2017-01-25 Thread Blake Tregre

Public bug reported:

I previously reported a X freeze and screen powering off bug over here
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1655803.  I had
hoped that some of the fixes in  newer mesa releases would fix it, but
alas I having the same problem on the latest x-staging mesa.  After
15-30 minutes of activity (emacs, terminal, chrome) X freezes, the
screen turns disco colors, and the screen powers down.  My machine is
usually completely hung (can't ssh in or ping), but I was able to ssh in
a collect a few logs (possible redundant, included below) this last
time.  Thanks, I hope this helps.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
.tmp.unity_support_test.0:
 
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
BootLog:
 
CompizPlugins: 
[core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,unitymtgrabhandles,workarounds,scale,expo,ezoom,unityshell]
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CurrentDesktop: Unity
Date: Wed Jan 25 13:10:22 2017
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-57-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-59-generic, x86_64: installed
 nvidia-375, 375.26, 4.4.0-57-generic, x86_64: installed
 nvidia-375, 375.26, 4.4.0-59-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GraphicsCard:
 Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT GL [FirePro W9000] 
[1002:6780] (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Tahiti XT GL [FirePro 
W9000] [1002:031e]
MachineType: Dell Inc. Precision WorkStation T7500
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-59-generic 
root=UUID=4bb35b69-210e-445c-b815-725f1bb7e010 ro radeon.msi=0 quiet splash 
nouveau.blacklist=1 vt.handoff=7
SourcePackage: xorg
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/21/2011
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 06FW8P
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: 
dmi:bvnDellInc.:bvrA09:bd01/21/2011:svnDellInc.:pnPrecisionWorkStationT7500:pvr:rvnDellInc.:rn06FW8P:rvrA01:cvnDellInc.:ct7:cvr:
dmi.product.name: Precision WorkStation T7500
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.12.2+16.04.20160823-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.70-1~ubuntu16.04.1
version.libgl1-mesa-dri: libgl1-mesa-dri 13.0.3-1ubuntu3~16.04.02
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 13.0.3-1ubuntu3~16.04.02
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: Wed Jan 25 12:44:23 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-0ubuntu0.2
xserver.video_driver: radeon

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


** Tags: amd64 apport-bug compiz-0.9 third-party-packages ubuntu xenial

** Attachment added: "xorg log"
   https://bugs.launchpad.net/bugs/1659430/+attachment/4809108/+files/Xorg.0.log

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1659430

Title:
  x-staging problem report, redux

Status in xorg package in Ubuntu:
  New

Bug description:
  I previously reported a X freeze and screen powering off bug over here
  https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1655803.  I had
  hoped that some of the fixes in  newer mesa releases would fix it, but
  alas I having the same problem on the latest x-staging mesa.  After
  15-30 minutes of activity (emacs, terminal, chrome) X freezes, the
  screen turns disco colors, and the screen powers down.  My machine is
  usually completely hung (can't ssh in or ping), but I was able to ssh
  in a collect a few logs (possible redundant, included below) this last
  time.  Thanks, I hope this helps.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  BootLog:
   
  CompizPlugins:

[Desktop-packages] [Bug 1521987] Re: Sound is not automatically switched back from headphones to speakers

2017-01-25 Thread Bug Watch Updater

** Changed in: pulseaudio
   Status: Fix Released => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1521987

Title:
  Sound is not automatically switched back from headphones to speakers

Status in PulseAudio:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Incomplete

Bug description:
  When plugging in headphones, sound output is correctly switched from
  speakers (line out) to the headphones. When the headphones are
  unplugged, sound is NOT automatically switched back to the speakers.

  This bug started happening on my system after I upgraded from 14.04 to
  15.10 so it is a regression. Attached is pulseaudio log of what
  happens when I plug and unplug my headphones.

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

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

[Desktop-packages] [Bug 1055068] Re: Guest user can use arbitrary MAC addresses

2017-01-25 Thread Tony Espy

Updated the Status to "FixReleased" as it's not possible to do this
anymore on the latest 16.04 LTS release with NetworkManager 1.2.x,  as
guest users no longer have sufficient permission to add new connections.

Retrofitting this to the version of NM in 14.04 might be a challenging as the 
version of NM (and other components) in trusty is currently based on NM 
0.9.8.*.  If this is important to anyone, please first confirm the behavior on 
a 14.04 LTS system and detail your testing in this bug, although it's doubtful 
we'd fix.
 

** Changed in: network-manager (Ubuntu)
   Status: Incomplete => Fix Released

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

Title:
  Guest user can use arbitrary MAC addresses

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  In Quantal, as a guest user you can create a network connection with an 
arbitrary mac address - I take
  that as a security hole (being able to break another machine on the network).

  (actually in this case the guest user you get to register a remote
  desktop account, you can get a terminal in it - that might be another
  security issue)

  Go to the network manager icon and edit connections
Wired network
 Add connection
 Choose the eth0/deault device mac address
  Type in a MAC address of your own evil making in the 'cloned mac 
address' box
   Untick 'available to all users'

  and Save

  Now, you have a new connection, but it's not up

  Open a terminal and use

nmcli con

  to list the network connections, and note the UUID of your new one.
  Now do

nmcli con up uuid .where . is the UUID you just got.

  You're now spoofing someone elses MAC address.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sun Sep 23 16:41:47 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac 
(20120905.2)
  IpRoute:
   default via 192.168.122.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.122.0/24 dev eth0  proto kernel  scope link  src 192.168.122.34  
metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 190a0ede6-43a8-4ad1-a26c-b17a52146725   
802-3-ethernet1348414780   Sun 23 Sep 2012 16:39:40 BST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.6.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1656399] Re: Unable to unlock Xubuntu XFCE session after suspend.

2017-01-25 Thread flocculant

was going to check the budgie greeter - but that uses lightdm-gtk-
greeter and fails the same as with other flavours

** Tags added: budgie

** Summary changed:

- Unable to unlock Xubuntu XFCE session after suspend.
+ Unable to unlock session after suspend using lightdm-gtk-greeter.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1656399

Title:
  Unable to unlock session after suspend using lightdm-gtk-greeter.

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Unable to unlock Xubuntu XFCE session after suspend. I'm presented
  with unlock screen, and entering credentials will redirect to a black
  screen with "This session is locked", and "you will be redirected to
  unlock screen".

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

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

[Desktop-packages] [Bug 1055068] Re: Guest user can use arbitrary MAC addresses

2017-01-25 Thread Tony Espy

** Changed in: network-manager (Ubuntu)
   Status: Triaged => Won't Fix

** Changed in: network-manager (Ubuntu)
   Status: Won't Fix => Fix Released

** Changed in: network-manager (Ubuntu)
   Status: Fix Released => Incomplete

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

Title:
  Guest user can use arbitrary MAC addresses

Status in network-manager package in Ubuntu:
  Fix Released

Bug description:
  In Quantal, as a guest user you can create a network connection with an 
arbitrary mac address - I take
  that as a security hole (being able to break another machine on the network).

  (actually in this case the guest user you get to register a remote
  desktop account, you can get a terminal in it - that might be another
  security issue)

  Go to the network manager icon and edit connections
Wired network
 Add connection
 Choose the eth0/deault device mac address
  Type in a MAC address of your own evil making in the 'cloned mac 
address' box
   Untick 'available to all users'

  and Save

  Now, you have a new connection, but it's not up

  Open a terminal and use

nmcli con

  to list the network connections, and note the UUID of your new one.
  Now do

nmcli con up uuid .where . is the UUID you just got.

  You're now spoofing someone elses MAC address.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: network-manager 0.9.6.0-0ubuntu7
  ProcVersionSignature: Ubuntu 3.5.0-15.22-generic 3.5.4
  Uname: Linux 3.5.0-15-generic x86_64
  ApportVersion: 2.5.2-0ubuntu4
  Architecture: amd64
  CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 
not found.
  Date: Sun Sep 23 16:41:47 2012
  IfupdownConfig:
   auto lo
   iface lo inet loopback
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac 
(20120905.2)
  IpRoute:
   default via 192.168.122.1 dev eth0  proto static 
   169.254.0.0/16 dev eth0  scope link  metric 1000 
   192.168.122.0/24 dev eth0  proto kernel  scope link  src 192.168.122.34  
metric 1
  IwConfig:
   eth0  no wireless extensions.
   
   lono wireless extensions.
  NetworkManager.state:
   [main]
   NetworkingEnabled=true
   WirelessEnabled=true
   WWANEnabled=true
   WimaxEnabled=true
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  RfKill:
   
  SourcePackage: network-manager
  UpgradeStatus: No upgrade log present (probably fresh install)
  nmcli-con:
   NAME  UUID   TYPE
  TIMESTAMPTIMESTAMP-REAL AUTOCONNECT   READONLY   
DBUS-PATH 
   Wired connection 190a0ede6-43a8-4ad1-a26c-b17a52146725   
802-3-ethernet1348414780   Sun 23 Sep 2012 16:39:40 BST   yes   
no /org/freedesktop/NetworkManager/Settings/0
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetconnected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.6.0connected   enabled   enabled 
enabledenabled disabled

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

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

[Desktop-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

2017-01-25 Thread Ernst Sjöstrand

2.76-4.1 should fix this, uploaded a build to my ppa:
https://launchpad.net/~ernstp/+archive/ubuntu/ppa

** Also affects: network-manager via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834722
   Importance: Unknown
   Status: Unknown

** Project changed: network-manager => dnsmasq

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

Title:
  Name resolution stops working after resume from suspend

Status in dnsmasq:
  Unknown
Status in dnsmasq package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

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

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

[Desktop-packages] [Bug 1659331] Re: user background disappears

2017-01-25 Thread Robert Ancell

** Package changed: lightdm (Ubuntu) => lightdm-gtk-greeter (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1659331

Title:
  user background disappears

Status in lightdm-gtk-greeter package in Ubuntu:
  New

Bug description:
  For some users lightdm displays the user's background for a second or two and 
then shows a solid blue background. Login etc. is OK.
  I have seen this behavior for over a year now (so things already started with 
14.04) on several boxes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 25 16:10:20 2017
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

2017-01-25 Thread Ernst Sjöstrand

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

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

Title:
  Name resolution stops working after resume from suspend

Status in dnsmasq:
  Unknown
Status in dnsmasq package in Ubuntu:
  New
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

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

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

[Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

2017-01-25 Thread Tony Espy

Ugh, and then I wake my Thinkpad 410s just now, and I hit the bug on the
201st cycle.  ;(-

Guess I'll go back to dropping the patch again from 1.2.6 and see how
many cycles I can run on it.

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

Title:
  WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
  required to fix it.

Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Description:Ubuntu Yakkety Yak (development branch)
  Release:16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2
  libnm-glib4:amd64   1.2.2-0ubuntu2
  libnm-util2:amd64   1.2.2-0ubuntu2
  libnm0:amd641.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=5 --s3-max-delay=5 
--s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo 
wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1585863/+subscriptions

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

[Desktop-packages] [Bug 1656399] Re: Unable to unlock Xubuntu XFCE session after suspend.

2017-01-25 Thread flocculant

Checked with gnome-screensaver and xscreensaver instead of light-locker.

In both cases -

lock and suspend both work as expected.

lock then login as new user fails to allow you back to original use

downgrading lightdm to 1.21.1-0ubuntu1 allows lock and login as new
user, however both require user to login twice to gain access to locked
desktop

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1656399

Title:
  Unable to unlock Xubuntu XFCE session after suspend.

Status in light-locker package in Ubuntu:
  Confirmed
Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  Unable to unlock Xubuntu XFCE session after suspend. I'm presented
  with unlock screen, and entering credentials will redirect to a black
  screen with "This session is locked", and "you will be redirected to
  unlock screen".

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

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

[Desktop-packages] [Bug 1659415] [NEW] pm-suspend causes computer to shutdown (Dell XPS 15 9550)

2017-01-25 Thread pvh

Public bug reported:

Linux kernel version 4.4.0-59-generic. Since a few weeks ago
(approximately the start of 2017 I think) suspend, whether triggered by
pm-suspend or other means, causes the computer to shutdown, not suspend.

I have tried various kernel options such as "dis_ucode_ldr" and
"acpi_sleep=nonvs", suggestions found in various posts on the web, but
the behaviour persists.

lsb_release -rd:
Description:Ubuntu 16.04.1 LTS
Release:16.04

pm-utils:
  Installed: 1.4.1-16
  Candidate: 1.4.1-16
  Version table:
 *** 1.4.1-16 500
500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
500 http://za.archive.ubuntu.com/ubuntu xenial/main i386 Packages
100 /var/lib/dpkg/status


linux-image-4.4.0-59-generic:
  Installed: 4.4.0-59.80
  Candidate: 4.4.0-59.80
  Version table:
 *** 4.4.0-59.80 500
500 http://za.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
100 /var/lib/dpkg/status

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: pm-utils 1.4.1-16
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jan 25 22:14:11 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2016-08-17 (161 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
PackageArchitecture: all
SourcePackage: pm-utils
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: pm-utils (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pm-utils in Ubuntu.
https://bugs.launchpad.net/bugs/1659415

Title:
  pm-suspend causes computer to shutdown (Dell XPS 15 9550)

Status in pm-utils package in Ubuntu:
  New

Bug description:
  Linux kernel version 4.4.0-59-generic. Since a few weeks ago
  (approximately the start of 2017 I think) suspend, whether triggered
  by pm-suspend or other means, causes the computer to shutdown, not
  suspend.

  I have tried various kernel options such as "dis_ucode_ldr" and
  "acpi_sleep=nonvs", suggestions found in various posts on the web, but
  the behaviour persists.

  lsb_release -rd:
  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  pm-utils:
Installed: 1.4.1-16
Candidate: 1.4.1-16
Version table:
   *** 1.4.1-16 500
  500 http://za.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  500 http://za.archive.ubuntu.com/ubuntu xenial/main i386 Packages
  100 /var/lib/dpkg/status

  
  linux-image-4.4.0-59-generic:
Installed: 4.4.0-59.80
Candidate: 4.4.0-59.80
Version table:
   *** 4.4.0-59.80 500
  500 http://za.archive.ubuntu.com/ubuntu xenial-updates/main amd64 
Packages
  500 http://security.ubuntu.com/ubuntu xenial-security/main amd64 
Packages
  100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: pm-utils 1.4.1-16
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 25 22:14:11 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-08-17 (161 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: pm-utils
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1659412] [NEW] Ubuntu Budgie live session in virtualbox not displayed correctly

2017-01-25 Thread fossfreedom

Public bug reported:

Ubuntu Budgie Alpha 2 AMD64 and i386

see screenshot

Note - this affect virtualbox only.

In QEMU the display of the live-session is ok

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


** Tags: iso-testing zesty

** Attachment added: "ubuntu budgie [Running] - Oracle VM VirtualBox_735.png"
   
https://bugs.launchpad.net/bugs/1659412/+attachment/4809082/+files/ubuntu%20budgie%20%5BRunning%5D%20-%20Oracle%20VM%20VirtualBox_735.png

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1659412

Title:
  Ubuntu Budgie live session in virtualbox not displayed correctly

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu Budgie Alpha 2 AMD64 and i386

  see screenshot

  Note - this affect virtualbox only.

  In QEMU the display of the live-session is ok

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

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

[Desktop-packages] [Bug 1658407] Re: "Ubuntu modification" extension default package disables Multiprocess in Firefox

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1658407

Title:
  "Ubuntu modification" extension default package disables Multiprocess
  in Firefox

Status in firefox package in Ubuntu:
  Confirmed
Status in ubufox package in Ubuntu:
  Confirmed

Bug description:
  Firefox has started making the default state to Multiprocess starting
  with Firefox 48. Right now, at least half the Firefox users have
  Multiprocess enabled by default and the performance and stability
  benefits are quite substantial. More about Multiprocess here -
  https://wiki.mozilla.org/Firefox/multiprocess

  The Ubufox extension that comes installed by default in Ubuntu's
  Firefox disables Multiprocess, due it not being compatible with it
  (check attachment). This leads to all Ubuntu users not benefiting from
  the performance benefits of Firefox multiprocess architecture and also
  the ever increasing benefits as they keep improving it.

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

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

[Desktop-packages] [Bug 1658407] Re: "Ubuntu modification" extension default package disables Multiprocess in Firefox

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to firefox in Ubuntu.
https://bugs.launchpad.net/bugs/1658407

Title:
  "Ubuntu modification" extension default package disables Multiprocess
  in Firefox

Status in firefox package in Ubuntu:
  Confirmed
Status in ubufox package in Ubuntu:
  Confirmed

Bug description:
  Firefox has started making the default state to Multiprocess starting
  with Firefox 48. Right now, at least half the Firefox users have
  Multiprocess enabled by default and the performance and stability
  benefits are quite substantial. More about Multiprocess here -
  https://wiki.mozilla.org/Firefox/multiprocess

  The Ubufox extension that comes installed by default in Ubuntu's
  Firefox disables Multiprocess, due it not being compatible with it
  (check attachment). This leads to all Ubuntu users not benefiting from
  the performance benefits of Firefox multiprocess architecture and also
  the ever increasing benefits as they keep improving it.

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

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

[Desktop-packages] [Bug 1132063] Re: Mouse settings missing from Mouse & Touchpad dialog

2017-01-25 Thread Benedikt Bär

Patch in #75 does work for me as well.
Microsoft Wireless Mouse 2000

⎡ Virtual core pointer  id=2[master pointer  (3)]
⎜   ↳ Virtual core XTEST pointerid=4[slave  pointer  (2)]
⎜   ↳ Microsoft Microsoft® 2.4GHz Transceiver v7.0  id=11   [slave  pointer 
 (2)]
⎜   ↳ Microsoft Microsoft® 2.4GHz Transceiver v7.0  id=12   [slave  pointer 
 (2)]
⎜   ↳ audio-technica AT2020USB+ id=13   [slave  pointer  (2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard   id=5[slave  keyboard (3)]
↳ Power Button  id=6[slave  keyboard (3)]
↳ Power Button  id=7[slave  keyboard (3)]
↳ XI100DUSB-HDMIid=9[slave  keyboard (3)]
↳ Microsoft Microsoft® 2.4GHz Transceiver v7.0  id=10   [slave  
keyboard (3)]

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1132063

Title:
  Mouse settings missing from Mouse & Touchpad dialog

Status in gnome-control-center package in Ubuntu:
  Confirmed
Status in unity-control-center package in Ubuntu:
  Triaged

Bug description:
  On up to date Raring alpha, on System Settings > Mouse & Touchpad the
  Mouse settings are completely missing.  The General and Touchpad
  sections are there but none for mouse.  See attached screenshot.

  xinput --list shows
  ~$ xinput --list
  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ MOSART Semi. 2.4G Keyboard Mouseid=11   [slave  pointer 
 (2)]
  ⎜   ↳ SynPS/2 Synaptics TouchPad  id=14   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ MOSART Semi. 2.4G Keyboard Mouseid=10   [slave  
keyboard (3)]
  ↳ Dell Dell USB Keyboard  id=12   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=13   [slave  
keyboard (3)]

  and from lsusb:
  Bus 003 Device 002: ID 062a:3286 Creative Labs Nano Receiver [Sandstrom Laser 
Mouse SMWLL11]

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: gnome-control-center 1:3.6.3-0ubuntu13
  ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
  Uname: Linux 3.8.0-7-generic i686
  ApportVersion: 2.8-0ubuntu4
  Architecture: i386
  Date: Sat Feb 23 09:40:41 2013
  InstallationDate: Installed on 2012-08-01 (205 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha i386 (20120730.1)
  MarkForUpload: True
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)
  usr_lib_gnome-control-center:
   activity-log-manager-control-center 0.9.4-0ubuntu6.1
   deja-dup25.5-0ubuntu1
   gnome-control-center-signon 0.1.2bzr12.12.05-0ubuntu1
   gnome-control-center-unity  1.2daily13.02.15-0ubuntu1
   indicator-datetime  12.10.3daily13.02.06-0ubuntu1

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

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

[Desktop-packages] [Bug 1633413] Re: Obsolete authenthication requests for WiFi

2017-01-25 Thread Philipp Wendler

I agree that this is very inconvenient. For example, I have a system at
home that I leave unattended but I need it to reconnect automatically to
my wifi, because I need to access it from abroad. If there is a
disconnect and it can't reconnect immediately (e.g., because of a router
reboot), the password dialog will prevent network manager from
connecting to my wifi again, effectively killing my access to this
machine.

So I would say that even if network manager needs to ask for the
password because it can't know whether the password is correct, this
should not block all other operations: network manager should try
connecting to the wifi in the background (and if it succeeds, hide the
dialog).

This is also asked here: https://bugzilla.gnome.org/show_bug.cgi?id=680625
Maybe https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1407907, 
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1316634 and 
https://bugs.launchpad.net/ubuntu/+source/network-manager-applet/+bug/1010745 
are related?
Users have requesting this since 2010: http://askubuntu.com/q/19137/51272

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

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

Title:
  Obsolete authenthication requests for WiFi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When a WiFi connection behaves unstable over longer time (eg. long
  range), sometimes the user is asked for the password again (the
  requester come up already filled), even if it is correct. The request
  can come up at any time, depending on the connection quality, and
  likely force the user to look up the already correctly entered
  password again.

  This is very annoying for kiosk-like systems or when using fullscreen
  apps.

  This bug is stone old and iv'e seens this year by year over a broad
  range of Ubuntu versions as well devices (Intel and ARM platform). It
  still happens as of Ubuntu 16.04.

  So I wonder if this is inevitable by the fact that NetworkManager
  sometimes can't decide between an authetication failed by wrong
  password vs. authentication failed by bad connection. If not, it
  should finally be fixed.

  There may be a security problem, for locked down kiosk applications,
  as the password may be obtained by kiosk users if the request pops up.

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

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

[Desktop-packages] [Bug 1633413] Re: Obsolete authenthication requests for WiFi

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

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

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

Title:
  Obsolete authenthication requests for WiFi

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  When a WiFi connection behaves unstable over longer time (eg. long
  range), sometimes the user is asked for the password again (the
  requester come up already filled), even if it is correct. The request
  can come up at any time, depending on the connection quality, and
  likely force the user to look up the already correctly entered
  password again.

  This is very annoying for kiosk-like systems or when using fullscreen
  apps.

  This bug is stone old and iv'e seens this year by year over a broad
  range of Ubuntu versions as well devices (Intel and ARM platform). It
  still happens as of Ubuntu 16.04.

  So I wonder if this is inevitable by the fact that NetworkManager
  sometimes can't decide between an authetication failed by wrong
  password vs. authentication failed by bad connection. If not, it
  should finally be fixed.

  There may be a security problem, for locked down kiosk applications,
  as the password may be obtained by kiosk users if the request pops up.

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

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

[Desktop-packages] [Bug 1645698] Re: [SRU] Upgrade network-manager to latest point release

2017-01-25 Thread Mathieu Trudel-Lapierre

Given the large number of changes in a "backport" SRU and the changes to
patches (looks like they are upstreamed, but maybe some bits are
missing?), I think this bug is lacking in terms of a comprehensive set
of test cases.

Some time ago I had captured the kind of tests I'd normally do when
uploading NM: https://wiki.ubuntu.com/NetworkManager/DistroTesting. It's
probably out of date, but it ought to be something you can base the test
cases on.

Among other things, I'd carefully check that bridges work, and that
they're not adversely affected when one uses virt-manager or lxd/lxc or
something else on their system -- NM should definitely not mangle them,
it should just ignore them. Similarly, VPNs should be checked carefully
to make sure split tunnelling and "everything through the VPN" works
correctly at least for OpenVPN (given DNS changes). We wouldn't want
behavior worse than it was before.

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

Title:
  [SRU] Upgrade network-manager to latest point release

Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  In Progress
Status in network-manager source package in Yakkety:
  Fix Committed

Bug description:
  [Impact]

  This SRU would try to have the latest well-tested upstream point
  release (1.2.6) of 1.2.x land in Xenial, which is the successor of the
  current 1.2.2 version, fixing quite some bugs that's suitable to land
  in the stable branch.

  https://cgit.freedesktop.org/NetworkManager/NetworkManager/tree/NEWS?h=nm-1-2

  [Test Case]

  After installing the updated version, users should be able to avoid
  some mem leaks in some cases and have generally improved DNS related
  experiences.

  [Regression Potential]

  This is a bug/regression fix for 1.2.2 and 1.2.4, which is quite
  complete.

  [Other Info]
  The first attempt at SRUing this to xenial was for 1.2.4 but it failed 
verification. This second attempt matches yakkety with 1.2.6.

  Parallel building was enabled in xenial to keep the diff between
  xenial and yakkety minimal since they are basically in sync now.
  Parallel building was enabled in the yakkety package in May 2016 so
  it's been working fine for a while.

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

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

[Desktop-packages] [Bug 1659377] [NEW] Internet won't connect or show up after I suspend the computer sometimes.

2017-01-25 Thread simon_peterson

Public bug reported:

Sometimes when I suspend my computer, when I get back on, the internet won't be 
connected and I can't connect to it.
To fix this I have to put the command in terminal:
sudo service network-manager restart
I am currently running Ubuntu 16.04 LTS.

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

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

Title:
  Internet won't connect or show up after I suspend the computer
  sometimes.

Status in network-manager package in Ubuntu:
  New

Bug description:
  Sometimes when I suspend my computer, when I get back on, the internet won't 
be connected and I can't connect to it.
  To fix this I have to put the command in terminal:
  sudo service network-manager restart
  I am currently running Ubuntu 16.04 LTS.

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

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

[Desktop-packages] [Bug 1659191] Re: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also i

2017-01-25 Thread Sebastien Bacher

thank you for your bug report but seems like the distribution/sources you are 
using using different versions from ubuntu
"Unpacking gconf-service (3.2.6-4)"

or Ubuntu has 3.2.6-3ubuntu7

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1659191

Title:
  package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying
  to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-
  evoldap.so', which is also in package gconf-service-backend
  3.2.6-3ubuntu6

Status in gconf package in Ubuntu:
  Invalid

Bug description:
  No idea

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: gconf-service 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Jan 25 11:58:29 2017
  DpkgTerminalLog:
   Preparing to unpack .../gconf-service_3.2.6-4_amd64.deb ...
   Unpacking gconf-service (3.2.6-4) over (3.2.6-3ubuntu6) ...
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/gconf-service_3.2.6-4_amd64.deb (--unpack):
trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also 
in package gconf-service-backend 3.2.6-3ubuntu6
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also 
in package gconf-service-backend 3.2.6-3ubuntu6
  RelatedPackageVersions:
   dpkg 1.18.15kali1
   apt  1.4~beta3
  SourcePackage: gconf
  Title: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying 
to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', 
which is also in package gconf-service-backend 3.2.6-3ubuntu6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1659191] Re: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also i

2017-01-25 Thread Hans Joachim Desserud

** Tags added: package-conflict

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gconf in Ubuntu.
https://bugs.launchpad.net/bugs/1659191

Title:
  package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying
  to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-
  evoldap.so', which is also in package gconf-service-backend
  3.2.6-3ubuntu6

Status in gconf package in Ubuntu:
  New

Bug description:
  No idea

  ProblemType: Package
  DistroRelease: Kali 2016.2
  Package: gconf-service 3.2.6-3ubuntu6
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  Date: Wed Jan 25 11:58:29 2017
  DpkgTerminalLog:
   Preparing to unpack .../gconf-service_3.2.6-4_amd64.deb ...
   Unpacking gconf-service (3.2.6-4) over (3.2.6-3ubuntu6) ...
   [1mdpkg:[0m error processing archive 
/var/cache/apt/archives/gconf-service_3.2.6-4_amd64.deb (--unpack):
trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also 
in package gconf-service-backend 3.2.6-3ubuntu6
  ErrorMessage: trying to overwrite 
'/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', which is also 
in package gconf-service-backend 3.2.6-3ubuntu6
  RelatedPackageVersions:
   dpkg 1.18.15kali1
   apt  1.4~beta3
  SourcePackage: gconf
  Title: package gconf-service 3.2.6-3ubuntu6 failed to install/upgrade: trying 
to overwrite '/usr/lib/x86_64-linux-gnu/gconf/2/libgconfbackend-evoldap.so', 
which is also in package gconf-service-backend 3.2.6-3ubuntu6
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1510203] Re: Bluetooth headset (MDR-XB950BT) detected but playback No sound at all

2017-01-25 Thread FRLinux

I ended up using blueman that you can install from the repos. It just
works. On occasions, I have to unplug my dongle and re-plug to make it
work. So not really fixed, just worked around.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1510203

Title:
  Bluetooth headset (MDR-XB950BT) detected but playback  No sound at all

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Upgraded to Ubuntu 15.10 from 15.04 a few days ago. Following update,
  peering of device is fine but I no longer can select my bluetooth
  headset to output sound. I see it in the list but I cannot switch
  sound to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 26 17:27:39 2015
  InstallationDate: Installed on 2014-03-05 (599 days ago)
  InstallationMedia: It
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: MDR-XB950BT
  Symptom_Type: No sound at all
  Title: [MDR-XB950BT, playback] No sound at all
  UpgradeStatus: Upgraded to wily on 2015-10-23 (2 days ago)
  dmi.bios.date: 12/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1202
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T DELUXE V2
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1202:bd12/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1659316] Re: compiz

2017-01-25 Thread Paul White

nemo, please don't confirm your own bug reports, that's for others to do
if they see the same problem.

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1659316

Title:
  compiz

Status in xorg package in Ubuntu:
  New

Bug description:
  i want start compiz but i have vesa driver installed

  Gathering information about your system...

   Distribution:  Ubuntu 15.10
   Desktop environment:   GNOME
   Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated 
Graphics Controller (rev 07)
   Driver in use: vesa
   Rendering method:  AIGLX

  Checking if it's possible to run Compiz on your system...  [SKIP]

  At least one check had to be skipped:
   Error: vesa driver in use

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Jan 25 15:49:04 2017
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-42-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
  MachineType: Acer TravelMate 5730
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=dbf84782-3125-4254-83ec-9f0a4e9f125b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.19
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd08/05/2008:svnAcer:pnTravelMate5730:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: TravelMate 5730
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  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.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Jan 25 15:07:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   32884 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Desktop-packages] [Bug 1648992] Re: [SRU] Update gnome-calculator to 3.22.2

Can I suggest that "the GNOME Micro Release Exception" statement
includes a link, so those of us ~ubuntu-sru who don't know about it can
look it up? I wouldn't block on this - but still waiting on Brian's
request I think.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-calculator in Ubuntu.
https://bugs.launchpad.net/bugs/1648992

Title:
  [SRU] Update gnome-calculator to 3.22.2

Status in gnome-calculator package in Ubuntu:
  Fix Released
Status in gnome-calculator source package in Yakkety:
  Incomplete

Bug description:
  Impact
  ==
  This update includes the new upstream bugfix 3.22.1 and 3.22.2 releases.

  https://git.gnome.org/browse/gnome-calculator/tree/NEWS?h=gnome-3-22
  https://git.gnome.org/browse/gnome-calculator/log?h=gnome-3-22

  Test Case
  =

  Regression Potential
  
  The uploads are happening under the GNOME Micro Release Exception.

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

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

[Desktop-packages] [Bug 1657909] Re: SSH service should be hidden from Startup Applications too

Wait to accept this.

** Changed in: gnome-keyring (Ubuntu Xenial)
   Status: In Progress => Incomplete

** Changed in: gnome-keyring (Ubuntu Yakkety)
   Status: In Progress => Incomplete

** Changed in: gnome-keyring (Ubuntu Trusty)
   Status: Triaged => Incomplete

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-keyring in Ubuntu.
https://bugs.launchpad.net/bugs/1657909

Title:
  SSH service should be hidden from Startup Applications too

Status in gnome-keyring package in Ubuntu:
  Fix Released
Status in gnome-keyring source package in Trusty:
  Incomplete
Status in gnome-keyring source package in Xenial:
  Incomplete
Status in gnome-keyring source package in Yakkety:
  Incomplete

Bug description:
  SRU Team
  
  Wait to accept this. Showing the SSH service was apparently intentional and 
not just an oversight.
  https://launchpad.net/ubuntu/+source/gnome-keyring/3.10.1-1ubuntu4.2

  Impact
  ==
  Ubuntu has for several years set NoDisplay=true for various services that use 
/etc/xdg/autostart so that users don't open Startup Applications and turn off a 
service that isn't really meant to be disabled that way

  gnome-keyring has a patch to do this, but one service "SSH Key Agent"
  needs to be added to the patch.

  Test Case
  =
  Install the updated gnome-keyring package.
  Open Startup Applications in Ubuntu (Unity) or Ubuntu GNOME
  "SSH Key Agent" should not show up in the list.

  Regression Potential
  
  Low. If someone *did* uncheck the box next to SSH in Startup Applications, it 
will now be a bit more tricky to re-enable that service.

  rm ~/.local/share/autostart/gnome-keyring-ssh.desktop

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

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

[Desktop-packages] [Bug 1659331] [NEW] user background disappears

2017-01-25 Thread DLCBurggraaff

Public bug reported:

For some users lightdm displays the user's background for a second or two and 
then shows a solid blue background. Login etc. is OK.
I have seen this behavior for over a year now (so things already started with 
14.04) on several boxes.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: lightdm 1.18.3-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
Uname: Linux 4.4.0-59-generic x86_64
ApportVersion: 2.20.1-0ubuntu2.5
Architecture: amd64
CurrentDesktop: XFCE
Date: Wed Jan 25 16:10:20 2017
SourcePackage: lightdm
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1659331

Title:
  user background disappears

Status in lightdm package in Ubuntu:
  New

Bug description:
  For some users lightdm displays the user's background for a second or two and 
then shows a solid blue background. Login etc. is OK.
  I have seen this behavior for over a year now (so things already started with 
14.04) on several boxes.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: lightdm 1.18.3-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35
  Uname: Linux 4.4.0-59-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Wed Jan 25 16:10:20 2017
  SourcePackage: lightdm
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1659316] Re: compiz

2017-01-25 Thread nemo

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1659316

Title:
  compiz

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  i want start compiz but i have vesa driver installed

  Gathering information about your system...

   Distribution:  Ubuntu 15.10
   Desktop environment:   GNOME
   Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated 
Graphics Controller (rev 07)
   Driver in use: vesa
   Rendering method:  AIGLX

  Checking if it's possible to run Compiz on your system...  [SKIP]

  At least one check had to be skipped:
   Error: vesa driver in use

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Jan 25 15:49:04 2017
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-42-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
  MachineType: Acer TravelMate 5730
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=dbf84782-3125-4254-83ec-9f0a4e9f125b ro quiet splash vt.handoff=7
  SourcePackage: xorg
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/05/2008
  dmi.bios.vendor: Phoenix Technologies LTD
  dmi.bios.version: V1.19
  dmi.board.name: Homa
  dmi.board.vendor: Acer
  dmi.board.version: Rev
  dmi.chassis.type: 10
  dmi.chassis.vendor: Acer
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd08/05/2008:svnAcer:pnTravelMate5730:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
  dmi.product.name: TravelMate 5730
  dmi.product.version: 0100
  dmi.sys.vendor: Acer
  version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
  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.5.0+git20150819-0ubuntu1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.11-1ubuntu3
  xserver.bootTime: Wed Jan 25 15:07:31 2017
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id   32884 
   vendor AUO
  xserver.version: 2:1.17.2-1ubuntu9.1

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

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

[Desktop-packages] [Bug 1510203] Re: Bluetooth headset (MDR-XB950BT) detected but playback No sound at all

2017-01-25 Thread Mariusz Czapski

I have the same issue on 16.04, so maybe this issue is connected to the
bluetooth dongle. Can you check this issue ones more, because now the
solution is to buy new computer or change linux distro or even linux
because this is now working. Btw on macOsx and Windows my hadset MDR-
XB950BT works fine. My distro is xubuntu 16.04, and my computer is dell
e5320.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1510203

Title:
  Bluetooth headset (MDR-XB950BT) detected but playback  No sound at all

Status in pulseaudio package in Ubuntu:
  Invalid

Bug description:
  Upgraded to Ubuntu 15.10 from 15.04 a few days ago. Following update,
  peering of device is fine but I no longer can select my bluetooth
  headset to output sound. I see it in the list but I cannot switch
  sound to it.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: pulseaudio 1:6.0-0ubuntu13
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.1-0ubuntu3
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Mon Oct 26 17:27:39 2015
  InstallationDate: Installed on 2014-03-05 (599 days ago)
  InstallationMedia: It
  SourcePackage: pulseaudio
  Symptom: audio
  Symptom_Card: MDR-XB950BT
  Symptom_Type: No sound at all
  Title: [MDR-XB950BT, playback] No sound at all
  UpgradeStatus: Upgraded to wily on 2015-10-23 (2 days ago)
  dmi.bios.date: 12/22/2010
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1202
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: P6T DELUXE V2
  dmi.board.vendor: ASUSTeK Computer INC.
  dmi.board.version: Rev 1.xx
  dmi.chassis.asset.tag: Asset-1234567890
  dmi.chassis.type: 3
  dmi.chassis.vendor: Chassis Manufacture
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1202:bd12/22/2010:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP6TDELUXEV2:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: System Product Name
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer

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

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

[Desktop-packages] [Bug 1606974] Re: Quicklist menu action doesn't respect global delay (Zesty)

2017-01-25 Thread Khurshid Alam

** Also affects: hundredpapercuts
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screenshot in Ubuntu.
https://bugs.launchpad.net/bugs/1606974

Title:
  Quicklist menu action doesn't respect global delay (Zesty)

Status in One Hundred Papercuts:
  New
Status in gnome-screenshot package in Ubuntu:
  New

Bug description:
  It doesn't respect global delay. The reason is that it using following
  commands for quicklist actions in
  /usr/share/applications/org.gnome.Screenshot.desktop:

  
  [Desktop Action screen-shot]
  Name=Take a Screenshot of the Whole Screen
  Exec=gnome-screenshot

  [Desktop Action window-shot]
  Name=Take a Screenshot of the Current Window
  Exec=gnome-screenshot -w

  These exec commands can be modified to respect global delay parameter.

  Patch:

  --- a/src/org.gnome.Screenshot.desktop.in
  +++ b/src/org.gnome.Screenshot.desktop.in
  @@ -18,11 +18,11 @@
   
   [Desktop Action screen-shot]
   Name=Take a Screenshot of the Whole Screen
  -Exec=gnome-screenshot
  +Exec=sh -c "gnome-screenshot -d $(gsettings get org.gnome.gnome-screenshot 
delay)"
   
   [Desktop Action window-shot]
   Name=Take a Screenshot of the Current Window
  -Exec=gnome-screenshot -w
  +Exec=sh -c "gnome-screenshot -w -d $(gsettings get 
org.gnome.gnome-screenshot delay)"
   
   [Desktop Action area-shot]
   Name=Take a Screenshot of a Selected Area

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

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

[Desktop-packages] [Bug 1659316] [NEW] compiz

2017-01-25 Thread nemo

Public bug reported:

i want start compiz but i have vesa driver installed

Gathering information about your system...

 Distribution:  Ubuntu 15.10
 Desktop environment:   GNOME
 Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated 
Graphics Controller (rev 07)
 Driver in use: vesa
 Rendering method:  AIGLX

Checking if it's possible to run Compiz on your system...  [SKIP]

At least one check had to be skipped:
 Error: vesa driver in use

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xorg 1:7.7+7ubuntu4
ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
Uname: Linux 4.2.0-42-generic x86_64
ApportVersion: 2.19.1-0ubuntu5
Architecture: amd64
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Wed Jan 25 15:49:04 2017
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
DkmsStatus: virtualbox, 5.0.14, 4.2.0-42-generic, x86_64: installed
GraphicsCard:
 Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
   Subsystem: Acer Incorporated [ALI] Device [1025:013c]
   Subsystem: Acer Incorporated [ALI] Device [1025:013c]
MachineType: Acer TravelMate 5730
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-42-generic 
root=UUID=dbf84782-3125-4254-83ec-9f0a4e9f125b ro quiet splash vt.handoff=7
SourcePackage: xorg
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 08/05/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.19
dmi.board.name: Homa
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: 
dmi:bvnPhoenixTechnologiesLTD:bvrV1.19:bd08/05/2008:svnAcer:pnTravelMate5730:pvr0100:rvnAcer:rnHoma:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: TravelMate 5730
dmi.product.version: 0100
dmi.sys.vendor: Acer
version.compiz: compiz 1:0.9.12.2+15.10.20151202-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9.1
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.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20150808-0ubuntu4
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Wed Jan 25 15:07:31 2017
xserver.configfile: default
xserver.errors:
 
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 product id   32884 
 vendor AUO
xserver.version: 2:1.17.2-1ubuntu9.1

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


** Tags: amd64 apport-bug third-party-packages ubuntu wily

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1659316

Title:
  compiz

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  i want start compiz but i have vesa driver installed

  Gathering information about your system...

   Distribution:  Ubuntu 15.10
   Desktop environment:   GNOME
   Graphics chip: Intel Corporation Mobile 4 Series Chipset Integrated 
Graphics Controller (rev 07)
   Driver in use: vesa
   Rendering method:  AIGLX

  Checking if it's possible to run Compiz on your system...  [SKIP]

  At least one check had to be skipped:
   Error: vesa driver in use

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xorg 1:7.7+7ubuntu4
  ProcVersionSignature: Ubuntu 4.2.0-42.49-generic 4.2.8-ckt12
  Uname: Linux 4.2.0-42-generic x86_64
  ApportVersion: 2.19.1-0ubuntu5
  Architecture: amd64
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Wed Jan 25 15:49:04 2017
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.14, 4.2.0-42-generic, x86_64: installed
  GraphicsCard:
   Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller 
[8086:2a42] (rev 07) (prog-if 00 [VGA controller])
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
 Subsystem: Acer Incorporated [ALI] Device [1025:013c]
  MachineType: Acer TravelMate 5730
  PccardctlIdent:
   Socket 0:
 no product info available
  PccardctlStatus:
   Socket 0:
 no card
  ProcKernelCmdLine:

[Desktop-packages] [Bug 1648534] Re: /usr/bin/gnome-software:5:g_wakeup_new:g_main_context_new:g_dbus_connection_send_message_with_reply_sync:g_dbus_connection_call_sync_internal:g_dbus_connection_cal

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

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1648534

Title:
  /usr/bin/gnome-
  
software:5:g_wakeup_new:g_main_context_new:g_dbus_connection_send_message_with_reply_sync:g_dbus_connection_call_sync_internal:g_dbus_connection_call_sync

Status in gnome-software package in Ubuntu:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem regarding 
gnome-software.  This problem was most recently seen with package version 
3.20.1+git20161013.0.d77d6cf-0ubuntu2~xenial1, the problem page at 
https://errors.ubuntu.com/problem/70c23d0f4e2be24b26672427d4218dc8f0823597 
contains more details, including versions of packages affected, stacktrace or 
traceback, and individual crash reports.
  If you do not have access to the Ubuntu Error Tracker you can request it at 
http://forms.canonical.com/reports/.

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

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

[Desktop-packages] [Bug 1652253] ProcEnviron.txt

2017-01-25 Thread Alexey Bazhin

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1652253

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (68 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: xorg 1:7.7+13ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1652253] JournalErrors.txt

2017-01-25 Thread Alexey Bazhin

apport information

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1652253

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
  --- 
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  DistroRelease: Ubuntu 16.10
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (68 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  Package: xorg 1:7.7+13ubuntu4
  PackageArchitecture: amd64
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Tags:  yakkety
  Uname: Linux 4.8.0-34-generic x86_64
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
  _MarkForUpload: True

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

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

[Desktop-packages] [Bug 1652253] Re: Xorg crash

2017-01-25 Thread Alexey Bazhin

apport information

** Tags added: apport-collected

** Description changed:

  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)
  
  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux 4.8.0-32-generic x86_64
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Fri Dec 23 11:53:30 2016
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-11-18 (34 days ago)
  InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: No upgrade log present (probably fresh install)
+ --- 
+ ApportVersion: 2.20.3-0ubuntu8.2
+ Architecture: amd64
+ CurrentDesktop: XFCE
+ DistroRelease: Ubuntu 16.10
+ EcryptfsInUse: Yes
+ InstallationDate: Installed on 2016-11-18 (68 days ago)
+ InstallationMedia: Xubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2)
+ Package: xorg 1:7.7+13ubuntu4
+ PackageArchitecture: amd64
+ ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
+ Tags:  yakkety
+ Uname: Linux 4.8.0-34-generic x86_64
+ UpgradeStatus: No upgrade log present (probably fresh install)
+ UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo
+ _MarkForUpload: True

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1652253

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  New

Bug description:
  [  3122.921] (EE) 
  [  3122.921] (EE) Backtrace:
  [  3122.922] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4a) [0x559ad2d869fa]
  [  3122.922] (EE) 1: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x1bdd69) 
[0x559ad2d8ad69]
  [  3122.922] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7fcac3f5+0x35860) 
[0x7fcac3f85860]
  [  3122.922] (EE) 3: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(0x7fcac5085000+0x8cb78) [0x7fcac5111b78]
  [  3122.922] (EE) 4: /usr/lib/x86_64-linux-gnu/libpixman-1.so.0 
(pixman_image_composite32+0x451) [0x7fcac508ff81]
  [  3122.922] (EE) 5: /usr/lib/xorg/modules/libfb.so (fbComposite+0x208) 
[0x7fcabfac8ff8]
  [  3122.922] (EE) 6: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15a0a7) [0x7fcac004f0a7]
  [  3122.922] (EE) 7: /usr/lib/xorg/modules/drivers/intel_drv.so 
(0x7fcabfef5000+0x15740a) [0x7fcac004c40a]
  [  3122.922] (EE) 8: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x13efc8) 
[0x559ad2d0bfc8]
  [  3122.922] (EE) 9: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x134633) 
[0x559ad2d01633]
  [  3122.922] (EE) 10: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x533bf) 
[0x559ad2c203bf]
  [  3122.922] (EE) 11: /usr/lib/xorg/Xorg (0x559ad2bcd000+0x57413) 
[0x559ad2c24413]
  [  3122.922] (EE) 12: /lib/x86_64-linux-gnu/libc.so.6 
(__libc_start_main+0xf1) [0x7fcac3f703f1]
  [  3122.922] (EE) 13: /usr/lib/xorg/Xorg (_start+0x2a) [0x559ad2c0e33a]
  [  3122.922] (EE) 
  [  3122.922] (EE) Bus error at address 0x7fcaa65ab400
  [  3122.922] (EE) 
  Fatal server error:
  [  3122.922] (EE) Caught signal 7 (Bus error). Server aborting
  [  3122.922] (EE) 
  [  3122.922] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: xorg 1:7.7+13ubuntu4
  ProcVersionSignature: Ubuntu 4.8.0-32.34-generic 4.8.11
  Uname: Linux

[Desktop-packages] [Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

P.S. mine is also GT710 and Xubuntu 16.04, with kernel 4.4.0-59-generic.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 desktop with all updates up to date
  Gigagyte GA-Z170 motherboard, Intel i7-6700 3.4gHz, 64GB RAM, Samsung 840 
SSD, Gigabyte GEForce GT710 graphics (nvidia chipset)

  Very light load. A few terminal windows, a few Firefox pages,
  Thunderbird, and VirtualBox (with the extension pack loaded) running
  one small Linux VM with 512Mb memory (very lightly loaded as it's only
  running bind9). I think (but don't have perfect certainty on this)
  that some of the crashes have happened without VirtualBox running.
  Also running rsync so that backuppc on a separate machine can back it
  up over the network (backuppc has been a real lifesaver with all the
  reinstallations!)

  After booting the system runs happily for a while then the GUI
  freezes. This can take a few hours or up to a day or two. You can
  still ssh into the system, and if you do "top" it typically shows 100%
  CPU load on systemd-timesync.

  The same happens whether I use nouveau or the proprietary nvidia driver (361)
  I have tried a complete reinstallation (4 times already, starting to get 
quite frustrating) using the proprietary drivers and NOT using the proprietary 
drivers and the same still happens. The most recent time was with nouveau, and 
Xorg.log has a number of entries like this:
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5652cde325ce]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x5652cde14083]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x5652cdcec662]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x61f3) 
[0x7f31f98621f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x6a5d) 
[0x7f31f9862a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x5652cdc8+0x94228) [0x5652cdd14228]
  (EE) 6: /usr/lib/xorg/Xorg (0x5652cdc8+0xb96f2) [0x5652cdd396f2]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 8: /usr/lib/xorg/Xorg (GiveUp+0x0) [0x5652cde37330]
  (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f3202debcf3]
  (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1d7) [0x5652cde2f307]
  (EE) 12: /usr/lib/xorg/Xorg (0x5652cdc8+0x539ee) [0x5652cdcd39ee]
  (EE) 13: /usr/lib/xorg/Xorg (0x5652cdc8+0x57c33) [0x5652cdcd7c33]
  (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f3202d0f830]
  (EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x5652cdcc1f59]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
   
  Then at the end the last few are:

  [  6265.543] [mi] Increasing EQ size to 1024 to prevent dropped events.
  [  6265.543] [mi] EQ processing has resumed after 1070 dropped events.
  [  6265.543] [mi] This may be caused by a misbehaving driver monopolizing the 
server's resources.

  What cna the problem possibly be, especially as 16.04 is meant to be a
  stable release and an Nvidia GT710 card is hardly bleeding-edge? Help
  greatly appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Wed Jun  1 13:22:13 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation Device [10de:128b] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device [1458:36ec]
  InstallationDate: Installed on 2016-06-01 (0 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: Gigabyte Technology Co., Ltd. Z170-D3H
  ProcEnviron:
   LANGUAGE=en_HK:en
   PATH=(custom, no user)
   LANG=en_HK.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-22-generic 
root=UUID=79d1ab40-4431-445f-87bb-6a8d44370cee ro quiet splash vt.handoff=7

[Desktop-packages] [Bug 1587730] Re: graphic system freezes after a while, can still ssh into machine

I'm possibly experiencing this bug, but I'm using the Nvidia proprietary 
driver, particularly the 367.57 version.
I tried to switch the clocksource to acpi_pm, as suggested in some forums, but 
it doesn't help.

While that's EQ overflowing, I couldn't check anything but reboot.

Attached is the Xorg.0.log.old file.

** Attachment added: "Xorg.0.log.old"
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1587730/+attachment/4808950/+files/Xorg.0.log.old

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1587730

Title:
  graphic system freezes after a while, can still ssh into machine

Status in xorg package in Ubuntu:
  New

Bug description:
  Ubuntu 16.04 desktop with all updates up to date
  Gigagyte GA-Z170 motherboard, Intel i7-6700 3.4gHz, 64GB RAM, Samsung 840 
SSD, Gigabyte GEForce GT710 graphics (nvidia chipset)

  Very light load. A few terminal windows, a few Firefox pages,
  Thunderbird, and VirtualBox (with the extension pack loaded) running
  one small Linux VM with 512Mb memory (very lightly loaded as it's only
  running bind9). I think (but don't have perfect certainty on this)
  that some of the crashes have happened without VirtualBox running.
  Also running rsync so that backuppc on a separate machine can back it
  up over the network (backuppc has been a real lifesaver with all the
  reinstallations!)

  After booting the system runs happily for a while then the GUI
  freezes. This can take a few hours or up to a day or two. You can
  still ssh into the system, and if you do "top" it typically shows 100%
  CPU load on systemd-timesync.

  The same happens whether I use nouveau or the proprietary nvidia driver (361)
  I have tried a complete reinstallation (4 times already, starting to get 
quite frustrating) using the proprietary drivers and NOT using the proprietary 
drivers and the same still happens. The most recent time was with nouveau, and 
Xorg.log has a number of entries like this:
  (EE) [mi] EQ overflowing.  Additional events will be discarded until existing 
events are processed.
  (EE) 
  (EE) Backtrace:
  (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5652cde325ce]
  (EE) 1: /usr/lib/xorg/Xorg (mieqEnqueue+0x253) [0x5652cde14083]
  (EE) 2: /usr/lib/xorg/Xorg (QueuePointerEvents+0x52) [0x5652cdcec662]
  (EE) 3: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x61f3) 
[0x7f31f98621f3]
  (EE) 4: /usr/lib/xorg/modules/input/evdev_drv.so (0x7f31f985c000+0x6a5d) 
[0x7f31f9862a5d]
  (EE) 5: /usr/lib/xorg/Xorg (0x5652cdc8+0x94228) [0x5652cdd14228]
  (EE) 6: /usr/lib/xorg/Xorg (0x5652cdc8+0xb96f2) [0x5652cdd396f2]
  (EE) 7: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 8: /usr/lib/xorg/Xorg (GiveUp+0x0) [0x5652cde37330]
  (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (0x7f3202cef000+0x354a0) 
[0x7f3202d244a0]
  (EE) 10: /lib/x86_64-linux-gnu/libc.so.6 (__select+0x13) [0x7f3202debcf3]
  (EE) 11: /usr/lib/xorg/Xorg (WaitForSomething+0x1d7) [0x5652cde2f307]
  (EE) 12: /usr/lib/xorg/Xorg (0x5652cdc8+0x539ee) [0x5652cdcd39ee]
  (EE) 13: /usr/lib/xorg/Xorg (0x5652cdc8+0x57c33) [0x5652cdcd7c33]
  (EE) 14: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f3202d0f830]
  (EE) 15: /usr/lib/xorg/Xorg (_start+0x29) [0x5652cdcc1f59]
  (EE) 
  (EE) [mi] These backtraces from mieqEnqueue may point to a culprit higher up 
the stack.
  (EE) [mi] mieq is *NOT* the cause.  It is a victim.
  (EE) [mi] EQ overflow continuing.  100 events have been dropped.
   
  Then at the end the last few are:

  [  6265.543] [mi] Increasing EQ size to 1024 to prevent dropped events.
  [  6265.543] [mi] EQ processing has resumed after 1070 dropped events.
  [  6265.543] [mi] This may be caused by a misbehaving driver monopolizing the 
server's resources.

  What cna the problem possibly be, especially as 16.04 is meant to be a
  stable release and an Nvidia GT710 card is hardly bleeding-edge? Help
  greatly appreciated!

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-22.40-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.1-0ubuntu2.1
  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: Wed Jun  1 13:22:13 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus: virtualbox, 5.0.18, 4.4.0-22-generic, x86_64: installed
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   NVIDIA Corporation Device [10de:128b] (rev a1) (prog-if 00 [VGA controller])
 Subsystem: Gigabyte Technology Co., Ltd Device

[Desktop-packages] [Bug 1577885] Re: 120sec delay during shutdown or reboot with still mounted cifs (via Wifi)

2017-01-25 Thread Anatoli

Maintainers, please set a priority (severe IMO) and assign this bug to
someone, it's extremely annoying to wait up to 5 minutes for the
computer to shutdown and get some errors during the process.

Network-manager should have some mechanism to instruct it not to
shutdown the network before some signal or other indication. It can't
just cut the network when other processes are using it. Maybe an order
of shutdown could be defined via systemd.

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

Title:
  120sec delay during shutdown or reboot with still mounted cifs (via
  Wifi)

Status in network-manager package in Ubuntu:
  Confirmed
Status in systemd package in Ubuntu:
  Confirmed

Bug description:
  Using Ubuntu 16.04 Desktop with Unity, used the same approach in 14.04
  with no issue.

  I prepare for mounting with the following entry in /etc/fstab my
  Synology NAS :

  //192.168.178.61/data /media/server/server_data cifs
  
users,uid=1000,gid=1000,username=x,passwd=xx,iocharset=utf8,sec=ntlm,noauto,_netdev
  0

  After login to unity, I mount it with a bash-script (mount -a) which
  is called from ~/.config/autostart/myMounts.desktop

  Doing this, and shuting down or rebooting lead into a very delayed
  shutdown (round about 2 minutes) Pressing ESC Key, showed that the
  process stops at the command "umount /media/server ..."

  I have not tested if this also occurs when I am connected via
  ethernet. I think it is because the (Wifi)Network is already disabled
  prior all umounts are done.

  This issue happens even if I type in a shutdown command into a
  Terminal or if I choose shutdown form the menue, also if I use the
  power-button.

  Failure can be avoided if I umount the network-drives manually
  previouse to reboot.

  Interim solution was, to create an alias for "shutdown" like "sh
  /path/to/umount/script.sh && shutdown" in /etc/bash.bashrc.local.

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

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

[Desktop-packages] [Bug 1573959] Re: On-screen text disappears after suspend

2017-01-25 Thread Pushkin Kachroo

I'm using Ubuntu 16.04 LTS, having same problem.

$ lspci -nn | egrep VGA
00:02.0 VGA compatible controller [0300]: Intel Corporation 3rd Gen Core 
processor Graphics Controller [8086:0166] (rev 09)
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF114M [GeForce 
GTX 675M] [10de:1212] (rev a1)

$ uname -a
Linux pushkin-M17xR4 4.4.0-59-generic #80-Ubuntu SMP Fri Jan 6 17:47:47 UTC 
2017 x86_64 x86_64 x86_64 GNU/Linux

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-intel in Ubuntu.
https://bugs.launchpad.net/bugs/1573959

Title:
  On-screen text disappears after suspend

Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  After resuming from a suspend, almost all text on screen is not
  visible.  This includes menu items, text in all three boxes (list of
  folders, list of e-mails, e-mail body) in Thunderbird (with the
  curious exception of "ffl" in the File menu), top menu in Chromium
  (but not the menu obtained by pressing the hamburger button), and the
  menus produced by clicking items in the system tray.  Also, the apport
  dialog had no text except for a few capital letters.

  ADDITIONAL INFORMATION:
  * initctl restart unity-panel-service restarts the panel, but the text is 
still missing
  * suspend and resume does not fix the issue
  * Logging out fixes the issue
  * Other affected applications:
  ** Chromium file select dialog
  ** Terminal (entire window)
  ** ttys 1-6 (Ctrl+Alt+F1, etc.)
  ** Document viewer (menus)
  ** Software Updater
  ** Rhythmbox
  ** The dialog that appears when you take a screenshot with Ctrl+Alt+PrtSc
  ** ubuntu-bug
  ** Nautilus
  ** LibreOffice Calc (spreadsheet text contents)
  ** Firefox
  * Unity dash is not affected.
  * Skype is not affected.
  * Mousing over a button in a dialog correctly shows the text.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: unity 7.4.0+16.04.20160415-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6
  Uname: Linux 4.4.0-21-generic x86_64
  .tmp.unity_support_test.0:

  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  BootLog:

  CompizPlugins: 
[core,bailer,detection,composite,opengl,compiztoolbox,decor,gnomecompat,imgpng,place,move,resize,vpswitch,snap,regex,grid,mousepoll,unitymtgrabhandles,animation,session,wall,workarounds,expo,fade,ezoom,scale,unityshell]
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  Date: Sat Apr 23 12:04:57 2016
  DistUpgraded: 2016-04-22 09:22:44,147 DEBUG icon theme changed, re-reading
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  GraphicsCard:
   Intel Corporation Haswell-ULT Integrated Graphics Controller [8086:0a16] 
(rev 09) (prog-if 00 [VGA controller])
     Subsystem: COMPAL Electronics Inc Haswell-ULT Integrated Graphics 
Controller [14c0:0075]
  InstallationDate: Installed on 2015-01-21 (457 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  MachineType: Compal VAW70
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-21-generic 
root=UUID=8f4bd759-42d2-4828-8470-2aaf6fcb75ff ro quiet splash vt.handoff=7
  SourcePackage: unity
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (1 days ago)
  dmi.bios.date: 07/31/2013
  dmi.bios.vendor: Insyde Corp.
  dmi.bios.version: V1.01T01
  dmi.board.asset.tag: Type2 - Board Asset Tag
  dmi.board.name: Type2 - Board Product Name1
  dmi.board.vendor: Compal
  dmi.board.version: V1.01T01
  dmi.chassis.asset.tag: Chassis Asset Tag
  dmi.chassis.type: 10
  dmi.chassis.vendor: Chassis Manufacturer
  dmi.chassis.version: Chassis Version
  dmi.modalias: 
dmi:bvnInsydeCorp.:bvrV1.01T01:bd07/31/2013:svnCompal:pnVAW70:pvrV1.01T01:rvnCompal:rnType2-BoardProductName1:rvrV1.01T01:cvnChassisManufacturer:ct10:cvrChassisVersion:
  dmi.product.name: VAW70
  dmi.product.version: V1.01T01
  dmi.sys.vendor: Compal
  upstart.unity-panel-service-lockscreen.log:
   (unity-panel-service:14416): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it

   (unity-panel-service:26413): GLib-CRITICAL **: Source ID 4294967295 was not 
found when attempting to remove it
  version.compiz: compiz 1:0.9.12.2+16.04.20160415-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.2.0-1ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.2.0-1ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2
  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
  version.xserver-xorg-video-nouveau:

[Desktop-packages] [Bug 1631241] Re: Name resolution stops working after resume from suspend

2017-01-25 Thread Ernst Sjöstrand

The Redhat patch is the same patch as the one that fixes Debian bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=834722

That patch is already upstream, where the debian package seems to be maintained 
also:
http://thekelleys.org.uk/gitweb/?p=dnsmasq.git;a=commitdiff;h=0682b7795cd0c25553b91de89c2a3b3d3ff17014;hp=b637d7815da89b5fb04c27b1d9a361fe5b2622a0

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

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

Title:
  Name resolution stops working after resume from suspend

Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  After upgrading to Yakkety, when my Ubuntu GNOME laptop resumes from
  suspend DNS resolution stops working.

  After resuming, systemd-resolved is running and libnss-resolve is
  installed, but /etc/resolv.conf contains 127.0.1.1 as the the only
  name server. The dnsmasq-base package is installed since it is pulled
  in by both network-manager and lxc1, and both NM and libvirt have
  spawned instances of dnsmasq:

  >  1155 pts/2S+ 0:00 grep dnsmasq
  >  2724 ?S  0:00 dnsmasq -u lxc-dnsmasq --strict-order 
--bind-interfaces --pid-file=/run/lxc/dnsmasq.pid --listen-address 10.0.3.1 
--dhcp-range 10.0.3.2,10.0.3.254 --dhcp-lease-max=253 --dhcp-no-override 
--except-interface=lo --interface=lxcbr0 
--dhcp-leasefile=/var/lib/misc/dnsmasq.lxcbr0.leases --dhcp-authoritative
  >  2992 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  >  2993 ?S  0:00 /usr/sbin/dnsmasq 
--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro 
--dhcp-script=/usr/lib/libvirt/libvirt_leaseshelper
  > 22879 ?S  0:00 /usr/sbin/dnsmasq --no-resolv 
--keep-in-foreground --no-hosts --bind-interfaces 
--pid-file=/var/run/NetworkManager/dnsmasq.pid --listen-address=127.0.1.1 
--cache-size=0 --conf-file=/dev/null --proxy-dnssec 
--enable-dbus=org.freedesktop.NetworkManager.dnsmasq 
--conf-dir=/etc/NetworkManager/dnsmasq.d

  Let me know if you need any extra info.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: libnss-resolve 231-9git1
  ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7
  Uname: Linux 4.8.0-17-generic x86_64
  ApportVersion: 2.20.3-0ubuntu7
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Fri Oct  7 13:52:40 2016
  InstallationDate: Installed on 2015-07-22 (443 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Release amd64 
(20150422)
  SourcePackage: systemd
  UpgradeStatus: Upgraded to yakkety on 2016-10-05 (1 days ago)

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

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

[Desktop-packages] [Bug 1659300] [NEW] File Conflict dialogue resizes depending on thumbnail size

2017-01-25 Thread Lucas Czech

Public bug reported:

(wishlist)

When copying/moving files and there is a name conflict, the dialogue
shows some information about the two conflicting files, e.g., name,
size, modification time, and an icon (for most file types) or thumbnail
(for images or videos).

This thumbnail uses the aspect ratio of the images/video, which might be
different for different files in the directory. Thus, when there are
multiple conflicting files in one copy/move operation, the size of the
File Conflict dialogue can change for each conflict. This means that the
buttons (e.g., "Cancel", "Skip", "Replace") change their position.

Users that resolve conflicts by clicking those buttons then have to
constantly move the mouse cursor even if they want to hit e.g. "Skip"
for some files in a row.

This problem can be solved by fixing the space taken up by the
thumbnails, that is, always use the maximum size. Of course, the
displayed thumbnail does not need to change (it should still use the
correct aspect ratio) - it just needs to be embedded in a background-
coloured box of fixed size.

Ubuntu 14.04 and 16.04

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nautilus in Ubuntu.
https://bugs.launchpad.net/bugs/1659300

Title:
  File Conflict dialogue resizes depending on thumbnail size

Status in nautilus package in Ubuntu:
  New

Bug description:
  (wishlist)

  When copying/moving files and there is a name conflict, the dialogue
  shows some information about the two conflicting files, e.g., name,
  size, modification time, and an icon (for most file types) or
  thumbnail (for images or videos).

  This thumbnail uses the aspect ratio of the images/video, which might
  be different for different files in the directory. Thus, when there
  are multiple conflicting files in one copy/move operation, the size of
  the File Conflict dialogue can change for each conflict. This means
  that the buttons (e.g., "Cancel", "Skip", "Replace") change their
  position.

  Users that resolve conflicts by clicking those buttons then have to
  constantly move the mouse cursor even if they want to hit e.g. "Skip"
  for some files in a row.

  This problem can be solved by fixing the space taken up by the
  thumbnails, that is, always use the maximum size. Of course, the
  displayed thumbnail does not need to change (it should still use the
  correct aspect ratio) - it just needs to be embedded in a background-
  coloured box of fixed size.

  Ubuntu 14.04 and 16.04

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

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

[Desktop-packages] [Bug 1583861] Re: Keyboard backlight isn't properly restored after idle on systems with hardwired configuration

2017-01-25 Thread Amr Ibrahim

** Changed in: upower (Ubuntu Xenial)
   Status: Fix Committed => Confirmed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1583861

Title:
  Keyboard backlight isn't properly restored after idle on systems with
  hardwired configuration

Status in Dell Sputnik:
  New
Status in Upower:
  Unknown
Status in gnome-settings-daemon package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in upower package in Ubuntu:
  Fix Released
Status in gnome-settings-daemon source package in Xenial:
  Confirmed
Status in unity-settings-daemon source package in Xenial:
  Fix Released
Status in upower source package in Xenial:
  Confirmed

Bug description:
  In Dell or ThinkPad (for these you need a kernel which includes fix
  for lp:1574498) notebooks with keyboard backlight, the keybindings to
  control the keyboard backlight don't emit any event to the userland,
  about the state change, nor they request userland to change it (as it
  happens in other models which emits KEY_KBDILLUM{UP,DOWN,TOGGLE}
  events), this causes unity/gnome-settings daemon not to restore the
  proper backlight after idle.

  Steps to reproduce:
   0) ensure your keyboard backlight is on, and
   gdbus call --system --dest org.freedesktop.UPower \
    --object-path /org/freedesktop/UPower/KbdBacklight \
    --method org.freedesktop.UPower.KbdBacklight.GetBrightness
  returns a value != from 0. If not, just call the SetBrightness
  method with a positive value, to turn on the backlight.

  Now turn off the keyboard backlight (or set it to another level)
  using the laptop keys, and run:
   gsettings set org.gnome.desktop.session idle-delay 1
  to make things easier to test.

   2) Wait one second and the screensaver should start. Wait the screen to
  be turned off. If you just changed the brightness level at the step above,
  once the screen is turned off, also the keyboard backlight should be 
turned off too.

   3) Now press a key or move the mouse.

  Expected behavior:

   4) The keyboard backlight should be set back to the previous level (so it 
should stay off
  or go back to the level you set before the idle timeout happened).

  Actual behavior:

   5) The backlight is set to the level it had at point 0).

  
  To reset the idle-delay, just call
gsettings reset org.gnome.desktop.session idle-delay

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1583861/+subscriptions

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

[Desktop-packages] [Bug 1510344] Re: Keyboard Backlight Turns on at boot

2017-01-25 Thread Amr Ibrahim

** Changed in: hundredpapercuts
   Status: Confirmed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1510344

Title:
  Keyboard Backlight Turns on at boot

Status in Dell Sputnik:
  Confirmed
Status in gnome-settings-daemon:
  Fix Released
Status in One Hundred Papercuts:
  Fix Released
Status in Linux:
  Invalid
Status in unity-settings-daemon package in Ubuntu:
  Fix Released
Status in unity-settings-daemon source package in Xenial:
  Fix Released

Bug description:
  System: Dell XPS 13 9343

  Action: Boot computer

  Expected Behavior: Keyboard backlight would be off when computer is
  booted

  Actual Behavior: Keyboard backlight is on at boot

  This did not happen with Ubuntu 15.04

  There are new files in Ubuntu 15.10 -
  /sys/class/leds/dell::kbd_backlight$

  cat stop_timeout
  60s

   cat start_triggers 
  +keyboard +touchpad

  cat trigger 
  [none] AC-online BAT0-charging-or-full BAT0-charging BAT0-full 
BAT0-charging-blink-full-solid usb-gadget usb-host cpu0 cpu1 cpu2 cpu3 mmc0 
rfkill0

  cat brightness 
  2

  ---

  Unsure if these files are important, but included in the report

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: linux-image-4.1.0-2-generic 4.1.0-2.2
  ProcVersionSignature: Ubuntu 4.1.0-2.2-generic 4.1.3
  Uname: Linux 4.1.0-2-generic x86_64
  ApportVersion: 2.18-0ubuntu5
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC1:  ubuntu 2488 F pulseaudio
   /dev/snd/controlC0:  ubuntu 2488 F pulseaudio
  CasperVersion: 1.362
  CurrentDesktop: Unity
  Date: Tue Oct 27 01:29:47 2015
  IwConfig:
   enx00249b0981e3  no wireless extensions.
   
   lono wireless extensions.
  LiveMediaBuild: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150730)
  MachineType: Dell Inc. XPS 13 9343
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcFB: 0 inteldrmfb
  ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi 
file=/cdrom/preseed/username.seed boot=casper quiet splash --- 
cdrom-detect/try-usb=true noprompt
  RelatedPackageVersions:
   linux-restricted-modules-4.1.0-2-generic N/A
   linux-backports-modules-4.1.0-2-generic  N/A
   linux-firmware   1.145
  RfKill:
   0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
  SourcePackage: linux
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/14/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0TM99H
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd07/14/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0TM99H:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dell-sputnik/+bug/1510344/+subscriptions

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

[Desktop-packages] [Bug 1590590] Re: Touchpad not recognized on Dell Latitude E7470 Ultrabook

2017-01-25 Thread Török Edwin

Apparently 4.8.0-34-generic detects my Latitude E7470 touchpad/stick as
ALPS instead of BYD (4.8.0-32-generic detects as BYD). I don't know
which would be the correct one, but by default ALPS is way too sensitive
and I have to apply those xprops changes before it is usable again
(basically I can't click anything because no matter how much I want to
hold my finger still, it just goes around in circles and the pointer is
not on top of an icon long enough to click it).

There is also something weird about how the touchpad behaves (or maybe I
noticed it now cause I use it more instead of the trackpoint?), is it
supposed to scroll vertically when I move a single finger vertically on
the right half of it? Basically I have to always move my finger
horizontally first, otherwise it accidentally scrolls.

I think it would be useful to make the BYD/ALPS configurable. The BYD
driver works a lot better by default, and I think I actually prefer it
over the ALPS one :)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-input-synaptics in Ubuntu.
https://bugs.launchpad.net/bugs/1590590

Title:
  Touchpad not recognized on Dell Latitude E7470 Ultrabook

Status in linux package in Ubuntu:
  Triaged
Status in xserver-xorg-input-synaptics package in Ubuntu:
  Confirmed

Bug description:
  Expected: Touchpad settings available in Mouse & Touchpad Settings
  dialog

  Actual result: Touchpad settings missing entirely

  
  Details:
  The touchpad on my Dell Ultrabook (Latitude E7470) functions mostly. 

  The settings for the touchpad are not available at all in the Mouse
  and Touchpad settings (see http://i.imgur.com/YRGiOrj.png).

  Two-finger scrolling works as expected except it's using "Natural
  Scrolling" by default and there is no way to change it.

  xinput list does not display a touchpad at all:

  ⎡ Virtual core pointerid=2[master pointer  (3)]
  ⎜   ↳ Virtual core XTEST pointer  id=4[slave  pointer 
 (2)]
  ⎜   ↳ ELAN Touchscreenid=11   [slave  pointer 
 (2)]
  ⎜   ↳ ImPS/2 Generic Wheel Mouse  id=13   [slave  pointer 
 (2)]
  ⎣ Virtual core keyboard   id=3[master keyboard (2)]
  ↳ Virtual core XTEST keyboard id=5[slave  
keyboard (3)]
  ↳ Power Buttonid=6[slave  
keyboard (3)]
  ↳ Video Bus   id=7[slave  
keyboard (3)]
  ↳ Power Buttonid=8[slave  
keyboard (3)]
  ↳ Sleep Buttonid=9[slave  
keyboard (3)]
  ↳ Integrated_Webcam_FHD   id=10   [slave  
keyboard (3)]
  ↳ AT Translated Set 2 keyboardid=12   [slave  
keyboard (3)]
  ↳ Dell WMI hotkeysid=14   [slave  
keyboard (3)]
  ↳ DELL Wireless hotkeys   id=15   [slave  
keyboard (3)]

  
  /proc/bus/input/devices lists the device as a "Generic Wheel Mouse"

  Output of `lsb_release -rd`:
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  xserver-xorg-input-synaptics version information:
  xserver-xorg-input-synaptics:
Installed: 1.8.2-1ubuntu3
Candidate: 1.8.2-1ubuntu3
Version table:
   *** 1.8.2-1ubuntu3 500
  500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
  100 /var/lib/dpkg/status

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

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

[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty

2017-01-25 Thread jazzynico

** Changed in: inkscape
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1638373

Title:
  End marker/start marker drop-down menus are empty

Status in Inkscape:
  Fix Released
Status in inkscape package in Ubuntu:
  Fix Released
Status in inkscape source package in Yakkety:
  Fix Released
Status in inkscape source package in Zesty:
  Fix Released

Bug description:
  [ Impact ]
  The dropdown menus for start marker, end marker and mid markers do not 
contains any arrows to select. I have clean up all local settings and run 
inkscape fresh but the same problem.

  This is caused by scour being called during the build, a change
  inadvertently added in the 0.91-11 upload.  The fix used it to just
  not call scour.

  [ Test case ]
  Compare the file /usr/share/inkscape/markers/markers.svg from the built 
package with upstream's 
http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_91_BRANCH/download/nicoduf%40yahoo.fr-20110829175757-0rzahc4xhhr2l6u5/markers.svg-20091128124040-aej0x7yhxng1m6ly-449/markers.svg
 - it should be at the very least equivalent (if not equal), currently it 
contains only comments.

  [Regression Potential]
  noe really

  
  Seen in in:

  - Inkscape 0.91 r13725 on Ubuntu 16.10
  - Inkscape 0.91-11 r13725 on Ubuntu 16.10 (official package from yakkety)
  - DistroRelease: Ubuntu 16.10, Package: inkscape 0.91-11
  - Inkscape 0.92, ubuntu 16.04 LTS
  - Ubuntu 16.04 - upgrade today to 0.92
  - Kubuntu 14.04, and recently updated Inkscape to version 0.92.0

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

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

[Desktop-packages] [Bug 1659281] [NEW] not appears the button "x" at the window of the browser pane unity

2017-01-25 Thread Александр

Public bug reported:

not appears the button "x" at the window of the browser-yandex pane
unity, but there are menu items such as "file". when you try pulling the
cap window is selected another window (same browser-chromium), it is no
problem.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: evince 3.22.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jan 25 17:55:19 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-27 (516 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: evince
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (98 days ago)

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


** Tags: amd64 apparmor apport-bug yakkety

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1659281

Title:
  not appears the button "x" at the window of the browser pane unity

Status in evince package in Ubuntu:
  New

Bug description:
  not appears the button "x" at the window of the browser-yandex pane
  unity, but there are menu items such as "file". when you try pulling
  the cap window is selected another window (same browser-chromium), it
  is no problem.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evince 3.22.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 25 17:55:19 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-27 (516 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: evince
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (98 days ago)

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

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

[Desktop-packages] [Bug 744619] Re: Screen doesn't unlock; stuck on "Checking"

2017-01-25 Thread Fernando

I had never experienced this bug before until now, on 16.04 and Gnome 3.
Every time I suspend the computer i get start in 'checking' when I try
to log in back again.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/744619

Title:
  Screen doesn't unlock; stuck on "Checking"

Status in gnome-screensaver package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: gnome-screensaver

  When I lock the screen either by using the screensaver, locking
  manually, or returning from a hibernate, when the authentication
  dialog comes up, it doesn't unlock the screen when I enter my
  password. Instead, it just hangs on "Checking..." forever until I
  manually kill gnome-screensaver.

  This is on a Lenovo Ideapad, with Ubuntu 10.10 i386. None of the
  issues listed here (https://wiki.ubuntu.com/DebuggingScreenLocking)
  apply to me.

  ProblemType: Bug
  DistroRelease: Ubuntu 10.10
  Package: gnome-screensaver 2.30.0-1ubuntu1.1
  ProcVersionSignature: Ubuntu 2.6.35-28.49-generic 2.6.35.11
  Uname: Linux 2.6.35-28-generic i686
  NonfreeKernelModules: fglrx
  Architecture: i386
  Date: Tue Mar 29 00:16:59 2011
  EcryptfsInUse: Yes
  GnomeSessionIdleInhibited: No
  GnomeSessionInhibitors: None
  InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
  ProcEnviron:
   LANG=nl_NL.utf8
   SHELL=/bin/bash
  SourcePackage: gnome-screensaver
  WindowManager: compiz

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

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

[Desktop-packages] [Bug 1653420] Re: gnome-terminal output locks up on special character

2017-01-25 Thread Guardfather

Posted and updated at https://bugzilla.gnome.org/show_bug.cgi?id=33

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/1653420

Title:
  gnome-terminal output locks up on special character

Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I wrote a Python 3 script which scans directory trees, and outputs
  various filenames (with path) to the terminal, as the files are being
  hashed. When the following filename was to be printed, gnome-terminal
  stopped printing output with the cursor where the question mark would
  have been printed out:

  ._13 Trapezoid singâ?€.mp3

  When I interrupted the program using keyboard interrupt, much more
  output was displayed, indicating the script had continued to run,
  despite the output stopping after "â".

  I navigated to the directory and tried using ls, which was able to
  print the filename without issue.

  I tried using: find `pwd` -name *Trapezoid*
  This also displayed the filename, with full path, correctly.

  I tried running the script with terminator, which had no problem
  printing the filename and continuing on with the rest of the output as
  expected.

  Terminal output at freeze, and after keyboard interrupt shown in the
  cropped/pixelized screenshots here: http://imgur.com/a/D0XRK

  Gnome Terminal version: 3.18.3
  Ubuntu 64 Gnome Edition

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

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

[Desktop-packages] [Bug 1659271] [NEW] a slider for mouse appears to the right of the window

2017-01-25 Thread Александр

Public bug reported:

A slider for mouse appears to the right of the window, because when you
try to put on him, he disappears. Scroll can only roller. The problem is
with the dialog box flame robin when you try to register the database

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: evince 3.22.0-0ubuntu1
ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
Uname: Linux 4.8.0-34-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.20.3-0ubuntu8.2
Architecture: amd64
CurrentDesktop: Unity
Date: Wed Jan 25 16:46:58 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-08-27 (516 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
SourcePackage: evince
UpgradeStatus: Upgraded to yakkety on 2016-10-19 (98 days ago)

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


** Tags: amd64 apparmor apport-bug yakkety

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1659271

Title:
  a slider for mouse appears to the right of the window

Status in evince package in Ubuntu:
  New

Bug description:
  A slider for mouse appears to the right of the window, because when
  you try to put on him, he disappears. Scroll can only roller. The
  problem is with the dialog box flame robin when you try to register
  the database

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: evince 3.22.0-0ubuntu1
  ProcVersionSignature: Ubuntu 4.8.0-34.36-generic 4.8.11
  Uname: Linux 4.8.0-34-generic x86_64
  NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
  ApportVersion: 2.20.3-0ubuntu8.2
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Wed Jan 25 16:46:58 2017
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2015-08-27 (516 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021)
  SourcePackage: evince
  UpgradeStatus: Upgraded to yakkety on 2016-10-19 (98 days ago)

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

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

[Desktop-packages] [Bug 1638373] Re: End marker/start marker drop-down menus are empty

This bug was fixed in the package inkscape - 0.91-11ubuntu16.10.1

---
inkscape (0.91-11ubuntu16.10.1) yakkety; urgency=medium

  * d/rules: don't run dh_scour, to avoid breaking internal SVGs (markers, …).
LP: #1638373

 -- Mattia Rizzolo   Thu, 12 Jan 2017 09:47:37 +0100

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1638373

Title:
  End marker/start marker drop-down menus are empty

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  Fix Released
Status in inkscape source package in Yakkety:
  Fix Released
Status in inkscape source package in Zesty:
  Fix Released

Bug description:
  [ Impact ]
  The dropdown menus for start marker, end marker and mid markers do not 
contains any arrows to select. I have clean up all local settings and run 
inkscape fresh but the same problem.

  This is caused by scour being called during the build, a change
  inadvertently added in the 0.91-11 upload.  The fix used it to just
  not call scour.

  [ Test case ]
  Compare the file /usr/share/inkscape/markers/markers.svg from the built 
package with upstream's 
http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_91_BRANCH/download/nicoduf%40yahoo.fr-20110829175757-0rzahc4xhhr2l6u5/markers.svg-20091128124040-aej0x7yhxng1m6ly-449/markers.svg
 - it should be at the very least equivalent (if not equal), currently it 
contains only comments.

  [Regression Potential]
  noe really

  
  Seen in in:

  - Inkscape 0.91 r13725 on Ubuntu 16.10
  - Inkscape 0.91-11 r13725 on Ubuntu 16.10 (official package from yakkety)
  - DistroRelease: Ubuntu 16.10, Package: inkscape 0.91-11
  - Inkscape 0.92, ubuntu 16.04 LTS
  - Ubuntu 16.04 - upgrade today to 0.92
  - Kubuntu 14.04, and recently updated Inkscape to version 0.92.0

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

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

[Desktop-packages] [Bug 1638373] Update Released

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to inkscape in Ubuntu.
https://bugs.launchpad.net/bugs/1638373

Title:
  End marker/start marker drop-down menus are empty

Status in Inkscape:
  Triaged
Status in inkscape package in Ubuntu:
  Fix Released
Status in inkscape source package in Yakkety:
  Fix Released
Status in inkscape source package in Zesty:
  Fix Released

Bug description:
  [ Impact ]
  The dropdown menus for start marker, end marker and mid markers do not 
contains any arrows to select. I have clean up all local settings and run 
inkscape fresh but the same problem.

  This is caused by scour being called during the build, a change
  inadvertently added in the 0.91-11 upload.  The fix used it to just
  not call scour.

  [ Test case ]
  Compare the file /usr/share/inkscape/markers/markers.svg from the built 
package with upstream's 
http://bazaar.launchpad.net/~inkscape.dev/inkscape/RELEASE_0_91_BRANCH/download/nicoduf%40yahoo.fr-20110829175757-0rzahc4xhhr2l6u5/markers.svg-20091128124040-aej0x7yhxng1m6ly-449/markers.svg
 - it should be at the very least equivalent (if not equal), currently it 
contains only comments.

  [Regression Potential]
  noe really

  
  Seen in in:

  - Inkscape 0.91 r13725 on Ubuntu 16.10
  - Inkscape 0.91-11 r13725 on Ubuntu 16.10 (official package from yakkety)
  - DistroRelease: Ubuntu 16.10, Package: inkscape 0.91-11
  - Inkscape 0.92, ubuntu 16.04 LTS
  - Ubuntu 16.04 - upgrade today to 0.92
  - Kubuntu 14.04, and recently updated Inkscape to version 0.92.0

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

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

[Desktop-packages] [Bug 1637731] Re: [SRU] Update to 2.48.2 in Xenial

This bug was fixed in the package glib2.0 - 2.48.2-0ubuntu1

---
glib2.0 (2.48.2-0ubuntu1) xenial; urgency=medium

  * New upstream release (LP: #1637731)
  * debian/patches/0001-Fix-trashing-on-overlayfs.patch: Update with new
version from the upsstream report to hopefully fix trashing of files in
directories which are symlinks to different devices. (Closes: #800047)
(LP: #1638245)

 -- Iain Lane   Thu, 24 Nov 2016 17:39:06
+

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

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

Title:
  [SRU] Update to 2.48.2 in Xenial

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

Bug description:
  [Description]
  Upstream have released a new bugfix release 2.48.2.

  [Changes]
  https://git.gnome.org/browse/glib/tree/NEWS?h=glib-2-48

  Bugs fixed:
   547200 g_utf8_find_next_char() issues
   673101 resource compiler dependency generation not working for generated 
files
   700756 GFile.new_for_path arguments misses (type filename) annotation
   725902 build: simplify dtrace configuration
   728207 gsocketservice: Documentation does not mention that is already 
active...
   730187 glocalfileoutputstream: Fix an FD leak in an error path
   746685 Doc: clarify that g_variant_get_data() can be used instead of 
g_varia...
   750257 GSettings changed signal should clearly state the order required
   753231 Memory is potentially used after free
   755439 Memory leak in gdbusproxy.c
   760115 gtestutils: add missing dash in seed argument's --help documentation
   760423 gio-querymodules prints error messages as question marks on some 
locales
   761810 gio: Support using GDBusObjectManagerServer at path ‘/’
   766211 Fix the upper bound in g_unichar_iswide_bsearch
   766899 Superflous HTML/XML comments in GDBusProxyTypeFunc documentation 
string
   766933 GSocketAddress leaks in 
gnetworkmonitornetlink.c:read_netlink_messages()
   767172 docs: Move GIO_USE_VFS to "okay for production" section
   767218 Remove a UTF-8 ellipsis from gsignal.h
   767824 Some UTC timezones incorrectly recognized on Windows 7
   767949 Typos in glib docs
   768453 Gdbus test: compilation fails due to -Werror=format-y2k errors
   768504 keyfile: g_key_file_get_double behavior doesn't follow documentation
   768551 Test failure: test_socket_address_to_string
   768560 gio/tests/gsettings: fix GSettings reference leaks in some tests
   768806 gdbus tool must swallow -- argument
   769027 Docs misleadingly imply G_CHECKSUM_SHA512 is available since 2.16

  Translations updated:
   Indonesian
   Portuguese
   Turkish

  [QA, testing, regression potential]
  Under the GNOME MRE, you can believe all bugs upstream says are fixed are 
really fixed. Just test the system and make sure there are no regressions (e.g. 
look at errors.ubuntu.com).

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

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

[Desktop-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

This bug was fixed in the package glib2.0 - 2.48.2-0ubuntu1

---
glib2.0 (2.48.2-0ubuntu1) xenial; urgency=medium

  * New upstream release (LP: #1637731)
  * debian/patches/0001-Fix-trashing-on-overlayfs.patch: Update with new
version from the upsstream report to hopefully fix trashing of files in
directories which are symlinks to different devices. (Closes: #800047)
(LP: #1638245)

 -- Iain Lane   Thu, 24 Nov 2016 17:39:06
+

** Changed in: glib2.0 (Ubuntu Xenial)
   Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Desktop
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:
  Fix Released
Status in glib2.0 source package in Yakkety:
  Fix Released

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/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1637731] Update Released

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

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

Title:
  [SRU] Update to 2.48.2 in Xenial

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

Bug description:
  [Description]
  Upstream have released a new bugfix release 2.48.2.

  [Changes]
  https://git.gnome.org/browse/glib/tree/NEWS?h=glib-2-48

  Bugs fixed:
   547200 g_utf8_find_next_char() issues
   673101 resource compiler dependency generation not working for generated 
files
   700756 GFile.new_for_path arguments misses (type filename) annotation
   725902 build: simplify dtrace configuration
   728207 gsocketservice: Documentation does not mention that is already 
active...
   730187 glocalfileoutputstream: Fix an FD leak in an error path
   746685 Doc: clarify that g_variant_get_data() can be used instead of 
g_varia...
   750257 GSettings changed signal should clearly state the order required
   753231 Memory is potentially used after free
   755439 Memory leak in gdbusproxy.c
   760115 gtestutils: add missing dash in seed argument's --help documentation
   760423 gio-querymodules prints error messages as question marks on some 
locales
   761810 gio: Support using GDBusObjectManagerServer at path ‘/’
   766211 Fix the upper bound in g_unichar_iswide_bsearch
   766899 Superflous HTML/XML comments in GDBusProxyTypeFunc documentation 
string
   766933 GSocketAddress leaks in 
gnetworkmonitornetlink.c:read_netlink_messages()
   767172 docs: Move GIO_USE_VFS to "okay for production" section
   767218 Remove a UTF-8 ellipsis from gsignal.h
   767824 Some UTC timezones incorrectly recognized on Windows 7
   767949 Typos in glib docs
   768453 Gdbus test: compilation fails due to -Werror=format-y2k errors
   768504 keyfile: g_key_file_get_double behavior doesn't follow documentation
   768551 Test failure: test_socket_address_to_string
   768560 gio/tests/gsettings: fix GSettings reference leaks in some tests
   768806 gdbus tool must swallow -- argument
   769027 Docs misleadingly imply G_CHECKSUM_SHA512 is available since 2.16

  Translations updated:
   Indonesian
   Portuguese
   Turkish

  [QA, testing, regression potential]
  Under the GNOME MRE, you can believe all bugs upstream says are fixed are 
really fixed. Just test the system and make sure there are no regressions (e.g. 
look at errors.ubuntu.com).

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

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

[Desktop-packages] [Bug 1644498] Re: apt-get update returns "AppStream cache update completed, but some metadata was ignored due to errors." periodically

This bug was fixed in the package appstream - 0.9.4-1ubuntu2

---
appstream (0.9.4-1ubuntu2) xenial; urgency=medium

  * yaml-parser-errors.patch: Deal with errors in the YAML structure
in the best way possible.
  * modern-metadata.patch: Recognize and return modern AppStream
component types. (LP: #1644498)

 -- Matthias Klumpp   Thu, 24 Nov 2016 22:42:06 +0100

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

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to appstream in Ubuntu.
https://bugs.launchpad.net/bugs/1644498

Title:
  apt-get update returns "AppStream cache update completed, but some
  metadata was ignored due to errors." periodically

Status in appstream package in Ubuntu:
  Fix Released
Status in appstream source package in Xenial:
  Fix Released

Bug description:
  [Impact]

   * The recent update of the Ubuntu asgen instance yielded it to
  generate modern metadata. While we could tell asgen to generate old-
  style metadata, fixing appstream is the better idea, since we already
  applied similar patches to appstream-glib (and having this package
  hold back updates is a bad idea). Currently, the unknown metadata is
  considered to be broken by appstream and it displays a warning about
  that issue during an `apt update`

   * The attached patch includes a second change to make AppStream more
  robust against broken YAML data, ensuring LP #1579712 can not be
  triggered on purpose or due to broken disks creating damaged YAML
  structure.

  [Test Case 1]

   * apt update
   * Check for errors about metadata being ignored

  [Test Case 2]

   * appstreamcli refresh --force
   * Check for errors about metadata being ignored
   * Check if we ignored data that should be present
 (search for it via `appstreamcli search `)
   * Run `appstreamcli status` and see if we still have information on the same 
amount of components as prior to the update.

  [Regression Potential]

   * Medium; The works case would be KDE Discover and GNOME Software
  loosing information on available software, but this risk is very low
  and the patch to fix this bug is very simple and has almost no
  regression potential. The YAML parser fix patch is a bit more complex,
  but should have no sideeffects.

  [Original report]

  Periodically I get emails from a machine with the subject:

  Cron  if [ -x /etc/munin/plugins/apt_all ]; then
  /etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x
  /etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12
  >/dev/null; fi

  And a body of:

  AppStream cache update completed, but some metadata was ignored due to
  errors.

  I have a machine monitored by Munin.  One of the plugins used on that
  machine is /etc/munin/plugins/apt which periodically counts the number
  of packets that can be upgraded.  This is achieved by a crontab entry
  installed from the package which looks like this:

  #
  # cron-jobs for munin-node
  #

  MAILTO=root

  # If the APT plugin is enabled, update packages databases approx. once
  # an hour (12 invokations an hour, 1 in 12 chance that the update will
  # happen), but ensure that there will never be more than two hour (7200
  # seconds) interval between updates..
  */5 * * * * root if [ -x /etc/munin/plugins/apt_all ]; then 
/etc/munin/plugins/apt_all update 7200 12 >/dev/null; elif [ -x 
/etc/munin/plugins/apt ]; then /etc/munin/plugins/apt update 7200 12 
>/dev/null; fi

  For many months everything has been running smoothly.  On the 23rd
  November 2016 I started getting the "AppStream cache update completed,
  but some metadata was ignored due to errors." messages at a rate of
  about ten a day.

  I did a quick Google search which turned up a handful of bugs from earlier 
this year, such as
  Bug1575248.  That is marked as Fixed Released though, so I am raising this 
new bug.

  If there are any further diagnostic details I can provide, please let
  me know.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: appstream 0.9.4-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-47.68-generic 4.4.24
  Uname: Linux 4.4.0-47-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Thu Nov 24 09:57:18 2016
  InstallationDate: Installed on 2013-05-08 (1295 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Alpha amd64 (20130508)
  JournalErrors:
   -- Logs begin at Wed 2016-11-23 19:25:01 GMT, end at Thu 2016-11-24 09:57:24 
GMT. --
   Nov 24 02:22:17 hostname systemd-tmpfiles[27330]: 
[/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
  ProcEnviron:
   TERM=xterm-256color
   SHELL=/bin/bash
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   LANGUAGE=en_GB:en
  SourcePackage: appstream
  UpgradeStatus: Upgraded to xenial on 2016-08-24 (91 days ago)

To manage notifications about this bug go to:

[Desktop-packages] [Bug 1659231] Re: Unity-control-center (or any other settings module) makes the system unresponsive (Unity7, Zesty)

2017-01-25 Thread Khurshid Alam

** Summary changed:

- Unity-control-center (or any other settings module) makes the system
unresponsive (Unity7, Zesty, 32bit)
+ Unity-control-center (or any other settings module) makes the system
unresponsive (Unity7, Zesty)

** Description changed:

Running ¨Unity-Control-Center¨ makes the system unresponsive for a while
and sometimes forever. Same thing happens if I try to open power or
sound settings from indicators or when I try to add online accounts in
evolution.

I can reproduce same with totem. But all other applications are working
fine. And everything works in Yakkety.

-
- Screencast:
-
+ Screencast:https://youtu.be/69PJZf055V8

System: Custom made (Intel Core2duo, 4GB RAM, Intel Mobile GME965/GLE960
Integrated Graphics)
- Graphics driver: i915
+ Graphics driver: i915
Os: Ubuntu 17.04, 32bit
UCC: 15.04.0+17.04.20161125.1-0ubuntu1

--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to unity-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1659231

Title:
Unity-control-center (or any other settings module) makes the system
unresponsive (Unity7, Zesty)

Status in unity-control-center package in Ubuntu:
New

Bug description:
Running ¨Unity-Control-Center¨ makes the system unresponsive for a
while and sometimes forever. Same thing happens if I try to open power
or sound settings from indicators or when I try to add online accounts
in evolution.

I can reproduce same with totem. But all other applications are
working fine. And everything works in Yakkety.

Screencast:https://youtu.be/69PJZf055V8

System: Custom made (Intel Core2duo, 4GB RAM, Intel Mobile GME965/GLE960
Integrated Graphics)
Graphics driver: i915
Os: Ubuntu 17.04, 32bit
UCC: 15.04.0+17.04.20161125.1-0ubuntu1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1659231/+subscriptions

[Desktop-packages] [Bug 1644498] Update Released