[Desktop-packages] [Bug 1609214] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-02 Thread Paul White
*** This bug is a duplicate of bug 1583906 ***
https://bugs.launchpad.net/bugs/1583906

** This bug has been marked a duplicate of bug 1583906
   package tex-common 6.04 failed to install/upgrade: le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Tue Aug  2 17:24:42 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-12-17 (1690 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1609214/+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 1288554] Re: faulty scrolling in launchpad.net

2016-08-02 Thread Launchpad Bug Tracker
[Expired for firefox (Ubuntu) because there has been no activity for 60
days.]

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

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

Title:
  faulty scrolling in launchpad.net

Status in firefox package in Ubuntu:
  Expired

Bug description:
  similar to bug 1286537 (which might be a dupe) I am not sure if this
  is a bug in Firefox or faulty web page programming on the part of
  launchpad.net.  When I open a bug ticket and press the down arrow,
  Firefox jumps to the end of the page instead of advancing only one
  line.

  steps to reproduce
  1) open https://bugs.launchpad.net/bugs/1286537
  2) press arrow-down

  FF jumps to the end of the page when it should have only advanced one
  line.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1288554/+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 857651] Re: Unable to hide users from login screen / user switcher

2016-08-02 Thread pepa65
Set the user to be a SystemUser in /var/lib/AccountsService/users works.
I would be more interested in a whitelist feature, so newly created unworthy 
users don't have to be blacklisted.

Why is there not a simple requirement like: only members of the lightdm
group are allowed to use lightdm??

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

Title:
  Unable to hide users from login screen / user switcher

Status in accountsservice:
  Confirmed
Status in accountsservice package in Ubuntu:
  Triaged
Status in lightdm package in Ubuntu:
  Triaged

Bug description:
  Users that I have appended to the 'hidden-users' field in
  /etc/lightdm/users.conf are not actually hidden. They are still listed
  on the login screen and in Unity's user switching menu.

  ProblemType: Bug
  DistroRelease: Ubuntu 11.10
  Package: lightdm 0.9.7-0ubuntu1
  ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4
  Uname: Linux 3.0.0-11-generic x86_64
  ApportVersion: 1.23-0ubuntu1
  Architecture: amd64
  Date: Fri Sep 23 11:44:29 2011
  InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta amd64 (20110413)
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to oneiric on 2011-09-23 (0 days ago)
  mtime.conffile..etc.lightdm.users.conf: 2011-09-23T08:46:55.039175

To manage notifications about this bug go to:
https://bugs.launchpad.net/accountsservice/+bug/857651/+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 1609214] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-02 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Tue Aug  2 17:24:42 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-12-17 (1690 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1609214/+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 1609214] [NEW] package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-02 Thread eslies
Public bug reported:

package tex-common 6.04 failed to install/upgrade: subprocess installed
post-installation script returned error exit status 1

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: tex-common 6.04
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic i686
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: i386
Date: Tue Aug  2 17:24:42 2016
ErrorMessage: subprocess installed post-installation script returned error exit 
status 1
InstallationDate: Installed on 2011-12-17 (1690 days ago)
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
PackageArchitecture: all
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: tex-common
Title: package tex-common 6.04 failed to install/upgrade: subprocess installed 
post-installation script returned error exit status 1
UpgradeStatus: Upgraded to xenial on 2016-08-02 (0 days ago)

** Affects: tex-common (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic i686
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: i386
  Date: Tue Aug  2 17:24:42 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2011-12-17 (1690 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1609214/+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 1609211] [NEW] [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at all

2016-08-02 Thread adin
Public bug reported:

When the headphones are plugged, they are not detected. All sound comes
from the built in speakers, and none from the headphones.

The jack works on Windows.

This bug seems similar to #1184838. However, I'm posting it as the
hardware is different.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: alsa-base 1.0.25+dfsg-0ubuntu5
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.1-0ubuntu2.1
Architecture: amd64
AudioDevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
 /dev/snd/controlC0:  adin   4035 F pulseaudio
CurrentDesktop: Unity
Date: Tue Aug  2 22:59:12 2016
InstallationDate: Installed on 2016-07-03 (30 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
PackageArchitecture: all
SourcePackage: alsa-driver
Symptom: audio
Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
Symptom_Card: Built-in Audio - HDA Intel PCH
Symptom_DevicesInUse:
 USERPID ACCESS COMMAND
 /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
 /dev/snd/controlC0:  adin   4035 F pulseaudio
  adin  32107 F alsamixer
Symptom_Jack: Green Headphone Out, Front
Symptom_PulsePlaybackTest: PulseAudio playback test successful
Symptom_Type: No sound at all
Title: [Alienware 17 R3, Creative CA0132, Green Headphone Out, Front] No sound 
at all
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/07/2016
dmi.bios.vendor: Alienware
dmi.bios.version: 1.2.15
dmi.board.name: Alienware 17 R3
dmi.board.vendor: Alienware
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Alienware
dmi.chassis.version: Not Specified
dmi.modalias: 
dmi:bvnAlienware:bvr1.2.15:bd07/07/2016:svnAlienware:pnAlienware17R3:pvr1.2.15:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
dmi.product.name: Alienware 17 R3
dmi.product.version: 1.2.15
dmi.sys.vendor: Alienware

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

Title:
  [Alienware 17 R3, Creative CA0132, Headphone Out, Front] No sound at
  all

Status in alsa-driver package in Ubuntu:
  New

Bug description:
  When the headphones are plugged, they are not detected. All sound
  comes from the built in speakers, and none from the headphones.

  The jack works on Windows.

  This bug seems similar to #1184838. However, I'm posting it as the
  hardware is different.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_drm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
  CurrentDesktop: Unity
  Date: Tue Aug  2 22:59:12 2016
  InstallationDate: Installed on 2016-07-03 (30 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful
  Symptom_Card: Built-in Audio - HDA Intel PCH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/pcmC0D0p:   adin   4035 F...m pulseaudio
   /dev/snd/controlC0:  adin   4035 F pulseaudio
adin  32107 F alsamixer
  Symptom_Jack: Green Headphone Out, Front
  Symptom_PulsePlaybackTest: PulseAudio playback test successful
  Symptom_Type: No sound at all
  Title: [Alienware 17 R3, Creative CA0132, Green Headphone Out, Front] No 
sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 07/07/2016
  dmi.bios.vendor: Alienware
  dmi.bios.version: 1.2.15
  dmi.board.name: Alienware 17 R3
  dmi.board.vendor: Alienware
  dmi.board.version: A00
  dmi.chassis.type: 10
  dmi.chassis.vendor: Alienware
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnAlienware:bvr1.2.15:bd07/07/2016:svnAlienware:pnAlienware17R3:pvr1.2.15:rvnAlienware:rnAlienware17R3:rvrA00:cvnAlienware:ct10:cvrNotSpecified:
  dmi.product.name: Alienware 17 R3
  dmi.product.version: 1.2.15
  dmi.sys.vendor: Alienware

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

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

[Desktop-packages] [Bug 1506358] Re: unity8/libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()

2016-08-02 Thread Daniel van Vugt
** Changed in: mir/0.23
   Status: Fix Committed => Fix Released

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

Title:
  unity8/libmirclient gives up and terminates prematurely with
  "std::exception::what: disconnected: no new buffers" via
  ExchangeSemantics::submit()

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Under heavy resizing (stress testing under Valgrind), my Mir client
  (Xmir) crashed with:

  [1444895332.392862]  MirBufferStreamAPI: Caught exception at client 
library boundary (in mir_buffer_stream_swap_buffers): 
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
 Throw in function virtual MirWaitHandle* 
{anonymous}::ExchangeSemantics::submit(const std::function&, 
mir::geometry::Size, MirPixelFormat, int)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: disconnected: no new buffers

  The strange thing is it's only the client that died. The server
  survived and I can connect new clients to it.

  ---
  Duplicate bug reports now show Unity8 is another such client suffering from 
this crash. It's occurring on phones and desktops in the wild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+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 1506358] Re: unity8/libmirclient gives up and terminates prematurely with "std::exception::what: disconnected: no new buffers" via ExchangeSemantics::submit()

2016-08-02 Thread Daniel van Vugt
This bug was fixed in the package mir - 0.23.5+16.10.20160729-0ubuntu1


** Changed in: mir (Ubuntu)
   Status: Triaged => Fix Released

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

Title:
  unity8/libmirclient gives up and terminates prematurely with
  "std::exception::what: disconnected: no new buffers" via
  ExchangeSemantics::submit()

Status in Canonical System Image:
  Confirmed
Status in Mir:
  Fix Committed
Status in Mir 0.23 series:
  Fix Released
Status in mir package in Ubuntu:
  Fix Released
Status in xorg-server package in Ubuntu:
  Invalid

Bug description:
  Under heavy resizing (stress testing under Valgrind), my Mir client
  (Xmir) crashed with:

  [1444895332.392862]  MirBufferStreamAPI: Caught exception at client 
library boundary (in mir_buffer_stream_swap_buffers): 
/build/mir-7io2Aj/mir-0.16.0+15.10.20150921.1/src/client/buffer_stream.cpp(169):
 Throw in function virtual MirWaitHandle* 
{anonymous}::ExchangeSemantics::submit(const std::function&, 
mir::geometry::Size, MirPixelFormat, int)
  Dynamic exception type: 
boost::exception_detail::clone_impl
  std::exception::what: disconnected: no new buffers

  The strange thing is it's only the client that died. The server
  survived and I can connect new clients to it.

  ---
  Duplicate bug reports now show Unity8 is another such client suffering from 
this crash. It's occurring on phones and desktops in the wild.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1506358/+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 1608895] Re: Sometimes Xapps loose keyboard events completely

2016-08-02 Thread Daniel van Vugt
*** This bug is a duplicate of bug 1536279 ***
https://bugs.launchpad.net/bugs/1536279

Oh, I see. This is an old bug and it's very annoying -- some of us are
used to working around it by tapping Ctrl and Alt.

It's just a bug in that Mir doesn't know the modifier state after VT-
switching. So regular key presses don't work till you tap those
modifiers again. Duplicate of bug 1536279

** Also affects: xorg-server (Ubuntu)
   Importance: Undecided
   Status: New

** Tags added: xmir

** Also affects: canonical-devices-system-image
   Importance: Undecided
   Status: New

** Tags added: unity8-desktop

** Changed in: xorg-server (Ubuntu)
 Assignee: (unassigned) => Daniel van Vugt (vanvugt)

** This bug has been marked a duplicate of bug 1536279
   Mir does not reset key states when paused or resumed

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

Title:
  Sometimes Xapps loose keyboard events completely

Status in Canonical System Image:
  New
Status in unity8-desktop-session package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  New

Bug description:
  All Xmir apps I tried sometimes looses keyboard events, but mouse events keep 
working. It happens randomly and suddenly but I found one way to reproduce this:
  1) Open any Xapp
  2) When the app is loaded, foreground and focused, change tty
  3) Come back to tty8

  Result:
  The foreground Xapp looses completely keyboard events, but mouse events still 
works. When this happens, you can recover keyboard events by pressing Ctrl and 
then Alt (Or first press Alt and then Ctrl) if the app is foreground and 
focused.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1608895/+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 1403057] Re: lightdm starts with blank screen

2016-08-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  lightdm starts with blank screen

Status in lightdm package in Ubuntu:
  Confirmed

Bug description:
  laptop boots fine but with blank screen.
  ctrl+alt+f1 switches to terminal 1 with text login

  Then doing trl+alt+f7 switches back to login screen with graphics and has no 
issues.
  Login and everything else works fine afterwards.

  Some mentioned SSD may cause this and I experimented with some delays
  i lightdm.conf but didn't change anything.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: lightdm 1.10.3-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-43.72-generic 3.13.11.11
  Uname: Linux 3.13.0-43-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Dec 16 15:31:24 2014
  InstallationDate: Installed on 2012-11-11 (765 days ago)
  InstallationMedia: Xubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120817.3)
  LightdmConfig:
   [SeatDefaults]
   greeter-session=unity-greeter
   user-session=ubuntu
  SourcePackage: lightdm
  UpgradeStatus: Upgraded to trusty on 2014-10-17 (59 days ago)
  mtime.conffile..etc.init.lightdm.conf: 2014-12-16T13:06:43.188021

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1403057/+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 1576576] Re: [needs-packaging] Update to 3.20 needs work and coordination

2016-08-02 Thread Jeremy Bicha
** Tags removed: needs-packaging

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

Title:
  [needs-packaging] Update to 3.20 needs work and coordination

Status in Mozilla Firefox:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in adwaita-icon-theme package in Ubuntu:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The current upstream stable/Debian version is 3.20 but that includes quite 
some changes in the css handling which means we are going to need to update/fix 
the unity themes and make sure you main application look fine before landing.
  The transition needs to be prepared in a staging ppa before being considered, 
help is welcome since it's likely the desktop team is not going to have lot of 
cycles to work on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1576576/+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 1551003] Re: Xenial Files cannot browse network

2016-08-02 Thread jerrylamos
Zero, what windows/selections/places do you use to do "Network browsing"?
What do you select with mouse and type in?
14.04.3 no problem, I can't get anywhere with xenial.
Thanks much.

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

Title:
  Xenial Files cannot browse network

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Xenial Files can't browse wired local network.

  In a different partition, same pc, 14.04.3 Files can Browse Network,
  both ubuntu and Windows pc's

  Xenial Nemo select "Network" can browse the network fine, display
  photos from Windows pc O.K.

  Xenial Files will not browse, just asks for  server address whatever
  that is and will not proceed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Feb 28 15:35:10 2016
  InstallationDate: Installed on 2016-01-31 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=c38a379f-bb91-4c00-be51-7f4824e0aa0e ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1551003/+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 1609189] [NEW] /usr/sbin/NetworkManager:11:connect_ready:g_simple_async_result_complete:connect_context_complete_and_free:simple_connect_ready:g_task_return_now

2016-08-02 Thread errors.ubuntu.com bug bridge
Public bug reported:

The Ubuntu Error Tracker has been receiving reports about a problem
regarding network-manager.  This problem was most recently seen with
version 1.2.0-0ubuntu0.16.04.3, the problem page at
https://errors.ubuntu.com/problem/277f486a1198ed21b05a2ebbb536d418ae402803
contains more details.

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


** Tags: xenial

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

Title:
  
/usr/sbin/NetworkManager:11:connect_ready:g_simple_async_result_complete:connect_context_complete_and_free:simple_connect_ready:g_task_return_now

Status in network-manager package in Ubuntu:
  New

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding network-manager.  This problem was most recently seen with
  version 1.2.0-0ubuntu0.16.04.3, the problem page at
  https://errors.ubuntu.com/problem/277f486a1198ed21b05a2ebbb536d418ae402803
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1609189/+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 1609186] [NEW] package python3-cairo 1.10.0+dfsg-5build1 failed to install/upgrade: subprocess new pre-removal script returned error exit status 13

2016-08-02 Thread Javier L
Public bug reported:

c

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: python3-cairo 1.10.0+dfsg-5build1
ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
Uname: Linux 3.19.0-65-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.21
Architecture: amd64
Date: Tue Aug  2 15:33:45 2016
Df:
 
DpkgTerminalLog: Log started: 2016-08-02  15:33:31
ErrorMessage: subprocess new pre-removal script returned error exit status 13
InstallationDate: Installed on 2016-01-20 (195 days ago)
InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: py3cairo
Title: package python3-cairo 1.10.0+dfsg-5build1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 13
UpgradeStatus: Upgraded to xenial on 2016-08-02 (0 days ago)

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


** Tags: amd64 apport-package xenial

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

Title:
  package python3-cairo 1.10.0+dfsg-5build1 failed to install/upgrade:
  subprocess new pre-removal script returned error exit status 13

Status in py3cairo package in Ubuntu:
  New

Bug description:
  c

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: python3-cairo 1.10.0+dfsg-5build1
  ProcVersionSignature: Ubuntu 3.19.0-65.73~14.04.1-generic 3.19.8-ckt22
  Uname: Linux 3.19.0-65-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.21
  Architecture: amd64
  Date: Tue Aug  2 15:33:45 2016
  Df:
   
  DpkgTerminalLog: Log started: 2016-08-02  15:33:31
  ErrorMessage: subprocess new pre-removal script returned error exit status 13
  InstallationDate: Installed on 2016-01-20 (195 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: py3cairo
  Title: package python3-cairo 1.10.0+dfsg-5build1 failed to install/upgrade: 
subprocess new pre-removal script returned error exit status 13
  UpgradeStatus: Upgraded to xenial on 2016-08-02 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/py3cairo/+bug/1609186/+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 1576576] Re: [needs-packaging] Update to 3.20 needs work and coordination

2016-08-02 Thread Brian Murray
*** This is an automated message ***

This bug is tagged needs-packaging which identifies it as a request for
a new package in Ubuntu.  As a part of the managing needs-packaging bug
reports specification,
https://wiki.ubuntu.com/QATeam/Specs/NeedsPackagingBugs, all needs-
packaging bug reports have Wishlist importance.  Subsequently, I'm
setting this bug's status to Wishlist.

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

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

Title:
  [needs-packaging] Update to 3.20 needs work and coordination

Status in Mozilla Firefox:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in adwaita-icon-theme package in Ubuntu:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The current upstream stable/Debian version is 3.20 but that includes quite 
some changes in the css handling which means we are going to need to update/fix 
the unity themes and make sure you main application look fine before landing.
  The transition needs to be prepared in a staging ppa before being considered, 
help is welcome since it's likely the desktop team is not going to have lot of 
cycles to work on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1576576/+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 1606774] Re: Xorg crash

2016-08-02 Thread Christopher M. Penalver
** Tags removed: bios-outdated-1.4.4
** Tags added: latest-bios-1.4.4

** Changed in: xorg-server (Ubuntu)
   Importance: Low => Medium

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

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  New

Bug description:
  I get random X server crashes

  The last lines of the Xorg.0.log.old are:

  [  1163.549] (EE) 
  [  1163.549] (EE) Backtrace:
  [  1163.549] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5574057265ce]
  [  1163.549] (EE) 1: /usr/lib/xorg/Xorg (0x557405574000+0x1b6959) 
[0x55740572a959]
  [  1163.550] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f958502f000+0x354a0) 
[0x7f95850644a0]
  [  1163.550] (EE) 3: /usr/lib/xorg/Xorg (0x557405574000+0x129595) 
[0x55740569d595]
  [  1163.550] (EE) 4: /usr/lib/xorg/Xorg (ValidatePicture+0x9) [0x55740569f359]
  [  1163.550] (EE) 5: /usr/lib/xorg/Xorg (CompositePicture+0xb5) 
[0x55740569f435]
  [  1163.550] (EE) 6: /usr/lib/xorg/Xorg (0x557405574000+0x12fc17) 
[0x5574056a3c17]
  [  1163.550] (EE) 7: /usr/lib/xorg/Xorg (0x557405574000+0x53bbf) 
[0x5574055c7bbf]
  [  1163.550] (EE) 8: /usr/lib/xorg/Xorg (0x557405574000+0x57c33) 
[0x5574055cbc33]
  [  1163.551] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f958504f830]
  [  1163.551] (EE) 10: /usr/lib/xorg/Xorg (_start+0x29) [0x5574055b5f59]
  [  1163.551] (EE) 
  [  1163.551] (EE) Segmentation fault at address 0x18
  [  1163.551] (EE) 
  Fatal server error:
  [  1163.551] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1163.551] (EE) 
  [  1163.551] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-lowlatency 4.4.13
  Uname: Linux 4.4.0-28-lowlatency 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: None
  CurrentDesktop: MATE
  Date: Wed Jul 27 07:49:22 2016
  DistUpgraded: 2016-05-30 00:00:15,168 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0704]
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-lowlatency 
root=/dev/mapper/sarvg-rootvol ro rootflags=subvol=@ quiet 
intel_idle.max_cstate=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to xenial on 2016-05-29 (58 days ago)
  dmi.bios.date: 11/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.7
  dmi.board.name: 0VM5NC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.7:bd11/27/2015:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul 27 07:48:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5153 
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1606774/+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 1409032] Re: gvfsd-smb: very high CPU utilisation

2016-08-02 Thread Gary Turnbull
Using Ubuntu 16.04. Issue effects me as well.

I implemented the suggestions in post #29 and #37.

When I open Files, gvfsd-smb-browse maxes out one core at 100% for about
10 minutes.

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

Title:
  gvfsd-smb: very high CPU utilisation

Status in gvfs package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in gvfs package in Fedora:
  Unknown

Bug description:
  Example:

  I use Virtualbox and mount a .vdi on an SMB server. Using gvfsd-smb
  (browsing within Gnome to find the share), gvfsd-smb uses up to 50%
  CPU which slows down the entire system when accessing the network
  share. Mounting using sudo ($ sudo mount -t smbfs -o
  guest,nounix,noperm //server/share /media/share) so that cifs is used
  uses around 8% CPU. The difference is dramatic!

  If I didn't have sudo access my machine would grind to a halt when
  trying to use the remote share.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gvfs-backends 1.12.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Fri Jan  9 14:32:20 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to precise on 2014-12-07 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+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 1605953] Re: skylake Modesetting Driver on X failure

2016-08-02 Thread Timo Aaltonen
just purge amdgpu-pro and you're done, no need to reinstall anything

but if you don't provide logs without it and xorg.conf, there's not much
I can do other than close the bug

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

Title:
  skylake Modesetting Driver on X failure

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  with the change away from the intel driver to modeset I get a lot of
  tearing.

  This video shows the problem.

  https://goo.gl/photos/rXNBQ5KR6ZMnhazB9
  And the video capture is done in 240fps so its possible to see what is 
happening more clearly.

  The test video itself is just a short test video with alternating
  red/green pictures in 60Hz.

  What you should see is a somewhat flickering screen but the color
  should be a consistent orange hue.

  there should be no pulsing of colors that is more green then back to
  more red and so on then something is wrong.

  I have attached the video. if you are uncertain how it should look try to 
play it directly on a TV. that is with the TV own player not with a computer as 
that has a lot higher probability of not having any issues with vsync and frame 
updates.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   /dev/sda2: clean, 770076/2416640 files, 3881571/9647872 blocks
   (K(K
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2016-04-22 23:31:04,108 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7976]
   Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] 
[1002:7300] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon R9 FURY X [1043:04a0]
  InstallationDate: Installed on 2015-10-18 (281 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: MSI MS-7976
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7+ 
root=UUID=75bb5d92-206d-4bb8-a405-150b9b93d6d3 ro quiet splash vt.handoff=7
  Tags:  yakkety ubuntu regression reproducible compiz-0.9
  Uname: Linux 4.7.0-rc7+ x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-04-22 (94 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160714.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.69-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+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 1609009] Re: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead)

2016-08-02 Thread Nikita Yerenkov-Scott
** Also affects: vte (Ubuntu)
   Importance: Undecided
   Status: New

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

** No longer affects: gnome-terminal

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

Title:
  gnome-terminal should allow the disabling of text wrapping (so that
  there is a scroll bar at the bottom instead)

Status in Ubuntu GNOME:
  New
Status in Gnome Virtual Terminal Emulator:
  Unknown
Status in gnome-terminal package in Ubuntu:
  New
Status in vte package in Ubuntu:
  New

Bug description:
  I would find it rather useful, especially with certain types of
  outputs, if gnome-terminal would allow me to disable text wrapping,
  that is so that there would be a horizontal scroll bar that would
  allow me to see the rest of the text.

  I don't know if this should/would include the commands you type it,
  but maybe there could be a separate option for the wrapping of that.

  There are other Terminals which support this, and I think it would be
  really nice if gnome-terminal would too so that one doesn't have to
  put all of the output into another program like 'less' or similar in
  order to disable the wrapping.

  I am running Ubuntu GNOME 16.04 with GNOME 3.20 and would find this a
  very useful feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1609009/+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 1609119] Re: login session timeouts but unable to reactivate with keyboard or mouse input

2016-08-02 Thread Gunnar Hjalmarsson
Thanks for your report. It's not a docs issue, though.

To help debug this, can you please create a new user for test purposes,
disable screenlocking, and let us know if the problem is present also
for that user.

** Package changed: ubuntu-docs (Ubuntu) => lightdm (Ubuntu)

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

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

Title:
  login session timeouts but unable to reactivate with keyboard or mouse
  input

Status in lightdm package in Ubuntu:
  Incomplete

Bug description:
  I recently upgraded my Ubuntu to the latest version:

  Description:  Ubuntu 16.04.1 LTS
  Release:  16.04

  
  When I log in and then let the screen be turned off by inactivity (currently 
set for 5 minutes WITHOUT screenlock) I am unable to resume the session, that 
is typing on the keyboard or moving the 
  mouse does not return my login to an active session.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1609119/+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 1609119] [NEW] login session timeouts but unable to reactivate with keyboard or mouse input

2016-08-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

I recently upgraded my Ubuntu to the latest version:

Description:Ubuntu 16.04.1 LTS
Release:16.04


When I log in and then let the screen be turned off by inactivity (currently 
set for 5 minutes WITHOUT screenlock) I am unable to resume the session, that 
is typing on the keyboard or moving the 
mouse does not return my login to an active session.

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

-- 
login session timeouts but unable to reactivate with keyboard or mouse input
https://bugs.launchpad.net/bugs/1609119
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to lightdm 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 1609135] [NEW] PPC Corrupt display ATI X800 XT

2016-08-02 Thread Scott Thompson
Public bug reported:

System: PowerMac 7,2
Video card: ATI X800 XT
Display: 1440x900

With this video card the display is corrupted on approximately 9 out of 10 
attempts to boot. On one boot out of 10 it works. When the display shows 
corruption it is in the form of a distorted checkerboard. The machine 
apparently locks up as the fans eventually come fully on.
The appended parameters on yaboot are:
radeon.agpmode=-1 video=offb:off video=radeonfb:off radeon.modeset=1

This is the same system as in bug #1605413 except I changed out the
video card.

This card also does not work when trying to boot Ubuntu-mate 16.10 Alpha
1

What I expected to happen:
The system boots to a normal desktop.

What happened instead:
Rarely do I get to a desktop. Usually the display is corrupted and the system 
locks up.

Ubuntu Mate 16.04
lsb_release -rd:

Description: Ubuntu 16.04.1 LTS
Release: 16.04

** Affects: xserver-xorg-video-nouveau (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: ati ppc radeon x800 xorg xt

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

Title:
  PPC Corrupt display ATI X800 XT

Status in xserver-xorg-video-nouveau package in Ubuntu:
  New

Bug description:
  System: PowerMac 7,2
  Video card: ATI X800 XT
  Display: 1440x900

  With this video card the display is corrupted on approximately 9 out of 10 
attempts to boot. On one boot out of 10 it works. When the display shows 
corruption it is in the form of a distorted checkerboard. The machine 
apparently locks up as the fans eventually come fully on.
  The appended parameters on yaboot are:
  radeon.agpmode=-1 video=offb:off video=radeonfb:off radeon.modeset=1

  This is the same system as in bug #1605413 except I changed out the
  video card.

  This card also does not work when trying to boot Ubuntu-mate 16.10
  Alpha 1

  What I expected to happen:
  The system boots to a normal desktop.

  What happened instead:
  Rarely do I get to a desktop. Usually the display is corrupted and the system 
locks up.

  Ubuntu Mate 16.04
  lsb_release -rd:

  Description: Ubuntu 16.04.1 LTS
  Release: 16.04

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-nouveau/+bug/1609135/+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 1021375] Re: Nautilus says the USB stick is read only when it is not

2016-08-02 Thread Djalal
dmesg output, last two lines are colored red:
[267152.527685] usb 2-1.7: New USB device found, idVendor=0951, idProduct=1662
[267152.527693] usb 2-1.7: New USB device strings: Mfr=1, Product=2, 
SerialNumber=3
[267152.527698] usb 2-1.7: Product: DataTraveler 109
[267152.527701] usb 2-1.7: Manufacturer: Kingston
[267152.527705] usb 2-1.7: SerialNumber: 00241D8CE55DBBA0E0CA
[267152.528253] usb-storage 2-1.7:1.0: USB Mass Storage device detected
[267152.530997] scsi host13: usb-storage 2-1.7:1.0
[267153.600714] scsi 13:0:0:0: Direct-Access Kingston DataTraveler 109 PMAP 
PQ: 0 ANSI: 4
[267153.601442] sd 13:0:0:0: Attached scsi generic sg1 type 0
[267154.441965] sd 13:0:0:0: [sdb] 31014912 512-byte logical blocks: (15.9 
GB/14.8 GiB)
[267154.443583] sd 13:0:0:0: [sdb] Write Protect is off
[267154.443594] sd 13:0:0:0: [sdb] Mode Sense: 23 00 00 00
[267154.445041] sd 13:0:0:0: [sdb] No Caching mode page found
[267154.445063] sd 13:0:0:0: [sdb] Assuming drive cache: write through

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

Title:
  Nautilus says the USB stick is read only when it is not

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  First time I use an USB drive since I updated to 12.04 and I found a
  really annoying bug on Nautilus. Nautilus claims that the destination
  drive is read-only when in fact it is not.

  How to reproduce:

  1. Connect a USB stick drive to your competer.
  2. The USB will appear in the desktop.
  3. Open two Nautilus windows one in your home folder, other in the USB stick 
drive.
  4. Select any file from your home folder (small enough to fit the free space 
in the USB drive)
  5. Drag the file and drop it in the USB drive window.

  -- Nautilus will say that it cannot copy the file because the
  destination is read ony --

  If you try the copy the same file with the terminal you will see that
  the file is copied without problem, other programs like gedit or
  LibreOffice can write in the usb stick drive just fine.

  It is not a problem with the USB stick, as shown here:

  [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd
  [ 6232.426378] scsi8 : usb-storage 2-1:1.0
  [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP 
PQ: 0 ANSI: 0 CCS
  [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0
  [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 
GB/1.86 GiB)
  [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off
  [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
  [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.210138]  sdb: sdb1
  [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk

  The permisions on the removable drive are set correctly:

  sergio@shana:/media$ ls -lah
  total 12K
  drwxr-xr-x  3 root   root   4,0K jul  5 10:20 .
  drwxr-xr-x 23 root   root   4,0K jul  3 11:01 ..
  drwx--  5 sergio sergio 4,0K dic 31  1969 DESIGNPLUS

  There is enough free space in the drive:

  sergio@shana:/media/DESIGNPLUS$ df -h
  S.ficheros Tamaño Usado  Disp Uso% Montado en
  /dev/sda2 50G  5,5G   42G  12% /
  udev 1,5G  4,0K  1,5G   1% /dev
  tmpfs579M  872K  579M   1% /run
  none 5,0M 0  5,0M   0% /run/lock
  none 1,5G  1,1M  1,5G   1% /run/shm
  /dev/sda1497M  113M  360M  24% /boot
  /dev/sda5245G  111G  122G  48% /home
  /dev/sdb11,9G  681M  1,2G  36% /media/DESIGNPLUS

  A file can be copied to the USB stick using the cp command for
  example.

  sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS
  sergio@shana:~/Trash$ cd /media/DESIGNPLUS
  sergio@shana:/media/DESIGNPLUS$ ls -lah
  total 204K
  drwx-- 5 sergio sergio 4,0K jul  5 10:38 .
  drwxr-xr-x 3 root   root   4,0K jul  5 10:20 ..
  -rw-r--r-- 1 sergio sergio 117K jul  5 10:14 ._Screen Shot 2012-06-30 at 
8.50.37 AM.png
  -rw-r--r-- 1 sergio sergio  55K jun 30 08:51 Screen Shot 2012-06-30 at 
8.50.37 AM.png
  drwx-- 4 sergio sergio 4,0K jul  5 10:05 .Spotlight-V100
  drwx-- 2 sergio sergio 4,0K jul  5 10:05 .Trashes
  -rw-r--r-- 1 sergio sergio 4,0K jul  5 10:05 ._.Trashes
  -rw-r--r-- 1 sergio sergio   73 jul  5 10:38 wireless.txt

  But nautilus just dennies to copy the file claming that the
  destination is read only, when it is not.

  I tested it with two different USB sticks in two different computers
  running Ubuntu 12.04 and the same result.

To manage notifications 

[Desktop-packages] [Bug 1380480] Re: network disabled after suspend - resume

2016-08-02 Thread Dan Gillmor
Bizarre that something of this kind got through testing and, after all
this time, is unfixed...

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

Title:
  network disabled after suspend - resume

Status in linux-lts-xenial package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed

Bug description:
  Background: 
  this started to happen after the upgrade to Utopic Beta 1

  3) When I close the laptop's lid and open, the wifi should reconnect
  4) Wifi does not reconnect. It says "Wi-Fi networks" - "disconnected" when I 
left-click on NM icon in notif area. However the context menu (right-click) has 
items "Enable networking" and "Enable Wi-Fi" both with checkmarks.

  Workarounds: 
  switch off - on the physical switch on laptop OR  two times go and select 
"Enable networking" in the NM context menu (after first time it removes 
checkmark and the  "Enable Wi-Fi" item - visual feedback of being disabled).

  ProblemType: Bug
  DistroRelease: Ubuntu 14.10
  Package: network-manager 0.9.8.8-0ubuntu27
  ProcVersionSignature: Ubuntu 3.16.0-21.28-generic 3.16.4
  Uname: Linux 3.16.0-21-generic x86_64
  ApportVersion: 2.14.7-0ubuntu5
  Architecture: amd64
  CurrentDesktop: XFCE
  Date: Sat Oct 11 22:33:06 2014
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  InstallationDate: Installed on 2013-07-21 (447 days ago)
  InstallationMedia: Xubuntu 13.04 "Raring Ringtail" - Release amd64 
(20130423.1)
  IpRoute:
   default via 192.168.10.1 dev wlan0  proto static 
   10.9.9.0/24 dev vboxnet0  proto kernel  scope link  src 10.9.9.1 
   192.168.10.0/24 dev wlan0  proto kernel  scope link  src 192.168.10.239  
metric 9
  SourcePackage: network-manager
  UpgradeStatus: Upgraded to utopic on 2014-09-25 (16 days ago)
  mtime.conffile..etc.NetworkManager.NetworkManager.conf: 
2014-07-19T15:03:44.847279
  nmcli-dev:
   DEVICE TYPE  STATE DBUS-PATH 
 
   eth0   802-3-ethernetunavailable   
/org/freedesktop/NetworkManager/Devices/1  
   wlan0  802-11-wireless   connected 
/org/freedesktop/NetworkManager/Devices/0
  nmcli-nm:
   RUNNING VERSIONSTATE   NET-ENABLED   WIFI-HARDWARE   
WIFI   WWAN-HARDWARE   WWAN  
   running 0.9.8.8connected   enabled   enabled 
enabledenabled enabled

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-lts-xenial/+bug/1380480/+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 1574851] Re: libgl not found on nvidia machines (so far)

2016-08-02 Thread Bill Filler
I can also confirm with snapd 2.0.10 that I get the same gl errors so this is 
not fixed.
Also tried the workaround, copy all files from /usr/lib/nvidia-xxx to 
/var/lib/snapd/lib/gl/ and restarted snapd and now things are working.

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

Title:
  libgl not found on nvidia machines (so far)

Status in Snappy:
  Triaged
Status in nvidia-graphics-drivers-361 package in Ubuntu:
  Confirmed

Bug description:
  So I've just had 2 recent complaints on libgl not being found on nvidia.
  here: 
http://askubuntu.com/questions/759647/opengl-error-in-snaps-ubuntu-16-04 
  and on IRC

  I cannot determine if anyone has had success running one of the 
desktop-example apps from the store on an nvidia gpu machine.
  I asked Alberto Aguirre on the mir team (who has a nvidia gpu) to try SDoC 
and install the ubuntu-clock-app from the store - he confirms seeing the exact 
same issue, he can be questioned if debug help is needed.

  Note, from an engagement on IRC earlier, the person confirmed that
  even rebuilding the clock snap locally and sideloading did not address
  the issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/snappy/+bug/1574851/+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 1021375] Re: Nautilus says the USB stick is read only when it is not

2016-08-02 Thread Djalal
Also affects me on Ubuntu 16.04 64 bit, latest Nautilus (package version 
1:3.18.4.is.3.14.3-0ubuntu4). Can write using terminal.
I started experiencing this bug only after mounting a live usb with Linux Mint 
18, as if it where infected..

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

Title:
  Nautilus says the USB stick is read only when it is not

Status in Nautilus:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  First time I use an USB drive since I updated to 12.04 and I found a
  really annoying bug on Nautilus. Nautilus claims that the destination
  drive is read-only when in fact it is not.

  How to reproduce:

  1. Connect a USB stick drive to your competer.
  2. The USB will appear in the desktop.
  3. Open two Nautilus windows one in your home folder, other in the USB stick 
drive.
  4. Select any file from your home folder (small enough to fit the free space 
in the USB drive)
  5. Drag the file and drop it in the USB drive window.

  -- Nautilus will say that it cannot copy the file because the
  destination is read ony --

  If you try the copy the same file with the terminal you will see that
  the file is copied without problem, other programs like gedit or
  LibreOffice can write in the usb stick drive just fine.

  It is not a problem with the USB stick, as shown here:

  [ 6232.288064] usb 2-1: new high-speed USB device number 6 using ehci_hcd
  [ 6232.426378] scsi8 : usb-storage 2-1:1.0
  [ 6233.468489] scsi 8:0:0:0: Direct-Access Kingston DT 101 IIPMAP 
PQ: 0 ANSI: 0 CCS
  [ 6233.469862] sd 8:0:0:0: Attached scsi generic sg2 type 0
  [ 6234.178262] sd 8:0:0:0: [sdb] 3909632 512-byte logical blocks: (2.00 
GB/1.86 GiB)
  [ 6234.178735] sd 8:0:0:0: [sdb] Write Protect is off
  [ 6234.178740] sd 8:0:0:0: [sdb] Mode Sense: 23 00 00 00
  [ 6234.179251] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.179256] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.183369] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.183376] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.210138]  sdb: sdb1
  [ 6234.212732] sd 8:0:0:0: [sdb] No Caching mode page present
  [ 6234.212736] sd 8:0:0:0: [sdb] Assuming drive cache: write through
  [ 6234.212740] sd 8:0:0:0: [sdb] Attached SCSI removable disk

  The permisions on the removable drive are set correctly:

  sergio@shana:/media$ ls -lah
  total 12K
  drwxr-xr-x  3 root   root   4,0K jul  5 10:20 .
  drwxr-xr-x 23 root   root   4,0K jul  3 11:01 ..
  drwx--  5 sergio sergio 4,0K dic 31  1969 DESIGNPLUS

  There is enough free space in the drive:

  sergio@shana:/media/DESIGNPLUS$ df -h
  S.ficheros Tamaño Usado  Disp Uso% Montado en
  /dev/sda2 50G  5,5G   42G  12% /
  udev 1,5G  4,0K  1,5G   1% /dev
  tmpfs579M  872K  579M   1% /run
  none 5,0M 0  5,0M   0% /run/lock
  none 1,5G  1,1M  1,5G   1% /run/shm
  /dev/sda1497M  113M  360M  24% /boot
  /dev/sda5245G  111G  122G  48% /home
  /dev/sdb11,9G  681M  1,2G  36% /media/DESIGNPLUS

  A file can be copied to the USB stick using the cp command for
  example.

  sergio@shana:~/Trash$ cp wireless.txt /media/DESIGNPLUS
  sergio@shana:~/Trash$ cd /media/DESIGNPLUS
  sergio@shana:/media/DESIGNPLUS$ ls -lah
  total 204K
  drwx-- 5 sergio sergio 4,0K jul  5 10:38 .
  drwxr-xr-x 3 root   root   4,0K jul  5 10:20 ..
  -rw-r--r-- 1 sergio sergio 117K jul  5 10:14 ._Screen Shot 2012-06-30 at 
8.50.37 AM.png
  -rw-r--r-- 1 sergio sergio  55K jun 30 08:51 Screen Shot 2012-06-30 at 
8.50.37 AM.png
  drwx-- 4 sergio sergio 4,0K jul  5 10:05 .Spotlight-V100
  drwx-- 2 sergio sergio 4,0K jul  5 10:05 .Trashes
  -rw-r--r-- 1 sergio sergio 4,0K jul  5 10:05 ._.Trashes
  -rw-r--r-- 1 sergio sergio   73 jul  5 10:38 wireless.txt

  But nautilus just dennies to copy the file claming that the
  destination is read only, when it is not.

  I tested it with two different USB sticks in two different computers
  running Ubuntu 12.04 and the same result.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1021375/+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 1605953] Re: skylake Modesetting Driver on X failure

2016-08-02 Thread kenjo
well what settings is there ?? I have no xorg.conf I also deleted the
.drirc file. still same.

Now I have a bit of a hard time testing as I switched over to a AMD R9
card and installed amdgpu-pro package. Not sure I can just switch back
to intel now and still have a working system.

I know it did not work to switch back when I had a nvida card without
reinstalling a lot of packages for intel again. Not sure what the
procedure is for switching amd to intel.

gfx on linux sure sucks compared to windows10 :(

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

Title:
  skylake Modesetting Driver on X failure

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  with the change away from the intel driver to modeset I get a lot of
  tearing.

  This video shows the problem.

  https://goo.gl/photos/rXNBQ5KR6ZMnhazB9
  And the video capture is done in 240fps so its possible to see what is 
happening more clearly.

  The test video itself is just a short test video with alternating
  red/green pictures in 60Hz.

  What you should see is a somewhat flickering screen but the color
  should be a consistent orange hue.

  there should be no pulsing of colors that is more green then back to
  more red and so on then something is wrong.

  I have attached the video. if you are uncertain how it should look try to 
play it directly on a TV. that is with the TV own player not with a computer as 
that has a lot higher probability of not having any issues with vsync and frame 
updates.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   /dev/sda2: clean, 770076/2416640 files, 3881571/9647872 blocks
   (K(K
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2016-04-22 23:31:04,108 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7976]
   Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] 
[1002:7300] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon R9 FURY X [1043:04a0]
  InstallationDate: Installed on 2015-10-18 (281 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: MSI MS-7976
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7+ 
root=UUID=75bb5d92-206d-4bb8-a405-150b9b93d6d3 ro quiet splash vt.handoff=7
  Tags:  yakkety ubuntu regression reproducible compiz-0.9
  Uname: Linux 4.7.0-rc7+ x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-04-22 (94 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160714.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.69-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+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 1250196] Re: sane plustek backend not working on USB 3 root hub

2016-08-02 Thread David Fletcher
Another three months has gone by. It still doesn't work. Seems like
either the relevant person doesn't know, hasn't had time to fix it, is
out of touch or doesn't care.

I have now kind of side stepped the problem. Anther computer that I own
and built is a little server, running 24/7, with an Atom processor. I
connected the scanner to my server instead of my desktop and installed
sane-utils as in a how-to, edited the configs on the server and AMD
desktop, rebooted.

Now I can scan again, via my network. Obviously I shouldn't have to
screw around like this but at least I appear to have a solution unlike
anybody who only has one, AMD based computer.

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

Title:
  sane plustek backend not working on USB 3 root hub

Status in sane-backends package in Ubuntu:
  Fix Committed
Status in sane-backends package in Fedora:
  New
Status in sane-backends package in Gentoo Linux:
  Unknown

Bug description:
  I have a HP Scanject 2100c and a Canoscan LIDE-25 both of which use
  the Sane plustek backend for comms. My PC only has a USB 3 root hub,
  when either of these devices are connected, either directly or via an
  external USB 2 hub, they do not work.

  In general (although not always), 'scanimage -L' will detect the
  scanner ok:

  device `plustek:libusb:001:012' is a Hewlett-Packard Scanjet 2100c
  flatbed scanner

  however there is always about a 30s delay before the shell prompt is
  returned. Scanning always fails however, using the suggested method on
  the sane HOW-TO page:

  scanimage -vvv -format pnm >outfile.pnm
  Calling sane_exit

  is the usual response. By enabling debug on the plustek backend, the
  response I normally get results in the following:

  [plustek] Vendor ID=0x03F0, Product ID=0x0505
  [plustek] usbio_DetectLM983x
  [plustek]  * could not read version register!
  [plustek] open failed: -1
  [plustek] sane_get_devices (0x7fff0686dbc8, 0)

  In an effort to try and diagnose this, I've build the latest SANE
  backends from scratch and tried out the latest libusb none of which
  has resolved the issue. My original kernel was a 3.5.x, I pushed it up
  to 3.8.0-30 this also made no difference.

  My guess based on what I've seen is that this is related to the USB 3
  hub. The HP Scanjet worked ok on my old Linux box (a 2.6.27 kernel
  with USB 2 hub) and I've had the Canon one working (albeit not that
  reliably) on a Raspberry Pi with a 3.6.11 kernel. The key difference
  (aside from this being a 64 bit flavour of Linux) is the USB.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: libsane 1.0.22-7ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-30.44~precise1-generic 3.8.13.6
  Uname: Linux 3.8.0-30-generic x86_64
  ApportVersion: 2.0.1-0ubuntu17.5
  Architecture: amd64
  Date: Mon Nov 11 19:41:08 2013
  InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release 
amd64 (20130214)
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: sane-backends
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/sane-backends/+bug/1250196/+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 1609110] [NEW] Do we still need the mesa or mesa-egl directories in /usr/lib/?

2016-08-02 Thread Bryan Quigley
Public bug reported:

One of our mesa changes means we can't sync Wine packages (or wine-
development stuck in proposed) from Debian.  See bug:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827770

We purposely end up creating in /usr/lib/x86_64-linux-gnu
mesa/ld.so.conf
mesa/libGL.so -> libGL.so.1.2.0
mesa/libGL.so.1 -> libGL.so.1.2.0
mesa/libGL.so.1.2.0
libGL.so -> mesa/libGL.so

Debian on the other hand just creates:
libGL.so.1 -> libGL.so.1.2.0
libGL.so.1.2.0

I haven't found a clear reason for the divergence.  I do see some
comments about making it work with the alternates system. I'm not sure
if that's current though.  Long term libglvnd should help there in a
better way (IIUC).

For reference Fedora does:
/usr/lib64/libGL.so.1
/usr/lib64/libGL.so.1.2.0

Can we drop these Debian differences from mesa for Yakkety?

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

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

Title:
  Do we still need the mesa or mesa-egl directories in /usr/lib/?

Status in mesa package in Ubuntu:
  New

Bug description:
  One of our mesa changes means we can't sync Wine packages (or wine-
  development stuck in proposed) from Debian.  See bug:
  https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=827770

  We purposely end up creating in /usr/lib/x86_64-linux-gnu
  mesa/ld.so.conf
  mesa/libGL.so -> libGL.so.1.2.0
  mesa/libGL.so.1 -> libGL.so.1.2.0
  mesa/libGL.so.1.2.0
  libGL.so -> mesa/libGL.so

  Debian on the other hand just creates:
  libGL.so.1 -> libGL.so.1.2.0
  libGL.so.1.2.0

  I haven't found a clear reason for the divergence.  I do see some
  comments about making it work with the alternates system. I'm not sure
  if that's current though.  Long term libglvnd should help there in a
  better way (IIUC).

  For reference Fedora does:
  /usr/lib64/libGL.so.1
  /usr/lib64/libGL.so.1.2.0

  Can we drop these Debian differences from mesa for Yakkety?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1609110/+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 1574347] Re: [SRU] Re-read the link type if the name changed

2016-08-02 Thread Cno
FYI: From what I experienced, there is a complex of (probably related) problems.
 NB: I'm applying Ubuntu updates continuously.

Somewhere a year ago, I started experiencing a problem when moving in my house, 
when apparently another access/antenna of the router was picked. Suspend/wake 
up was not necessary to have that problem: wifi crashed and no relief of 
networkmanager restart.
The problem in also showed when I was using my smartphone as hotspot.
In other locations, it happened rather seldom.

Now some time after the 16.04 the problem changed: the provious bug
disappeared; the bug described here poped up. Which is less annoying,
since there are work arounds.

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

Title:
  [SRU] Re-read the link type if the name changed

Status in NetworkManager:
  Fix Released
Status in OEM Priority Project:
  Fix Released
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager source package in Xenial:
  Fix Released

Bug description:
  [Impact]
  NM needs to re-read the DEVTYPE after the device name changed, an example is 
that WiFi network list disappears from network manager applet

  [Testcase]
  1. Boot the system. It should include a wireless device.
  2. In a terminal, run 'nmcli dev'.
  3. In the correct case, the line for the wireless device should read "wifi" 
under the TYPE column. In a failure case, it will read "ethernet".

  After upgrading to the new version, the repeating the above steps
  should give expected behavior.

  [Regression Potential]
  Potential of causing regression is relatively small for a one line change to 
re-read a value to be known.

  ---

  Problems:-

  1. The network manager applet does not show the list of WiFI APs it can find.
  2. The network manager applet does not the name of the AP to which it is 
connected
  3. The icon of the applet shows two vertical arrows in opposite direction - 
the wired connection symbol and NOT the wifi connected icon.

  Temporary Workaround:-
  Log out and again log back in.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1574347/+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 1316873] Re: Left mouse button stops working

2016-08-02 Thread Michael
This bug is still very much alive (running on 16.04).

NOTE: A quick way to get your mouse clicks working again is to press
[alt|win] + tab on the keyboard (it works for me at least).

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

Title:
  Left mouse button stops working

Status in xorg package in Ubuntu:
  Confirmed

Bug description:
  This  problem has plagued me for a few years across different laptops
  and Ubuntu versions. Current I am experiencing this on a Dell Inspiron
  15z running Ubuntu 14.04 LTS.

  It typically starts after I have used the chat or call feature in
  gmail, by clicking on the phone icon in the left chat margin. I am a
  Firefox user and have not tested this with chrome etc. It has not
  happened if i dont install google-talkplugin so it is quite possible
  that the plugin is to blame.

  Symptom
  ===
  The left mouse button on all attached mice - USB , Trackpad and touch - will 
not do anything  however the right mouse button continues to work.  This 
happens to all applications and also to the desktop. The keyboard continues to 
function as normal.

  When this occurs , my solution is to Alt-F4 close all windows and log
  out of the X session. When I re-login the left mouse button works as
  normal.

  
  This is an irritant and work disruptor as I have to save all browser and 
desktop applications to  safe state before I logout to reset the mouse. I will 
appreciate any soltion or workaround.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: xorg 1:7.7+1ubuntu8
  ProcVersionSignature: Ubuntu 3.13.0-24.47-generic 3.13.9
  Uname: Linux 3.13.0-24-generic x86_64
  .tmp.unity.support.test.0:
   
  ApportVersion: 2.14.1-0ubuntu3
  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
  CurrentDesktop: Unity
  Date: Tue May  6 21:41:29 2014
  DistUpgraded: Fresh install
  DistroCodename: trusty
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation 3rd Gen Core processor Graphics Controller [8086:0166] 
(rev 09) (prog-if 00 [VGA controller])
 Subsystem: Dell Device [1028:058f]
  InstallationDate: Installed on 2014-04-17 (19 days ago)
  InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
  MachineType: Dell Inc. Inspiron 5523
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic 
root=UUID=f5004b03-b37f-4733-88a8-51c6f3bd0a4d ro quiet splash vt.handoff=7
  SourcePackage: xorg
  Symptom: display
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 05/18/2013
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A05
  dmi.board.name: 0GKGJG
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A05
  dmi.chassis.type: 8
  dmi.chassis.vendor: Dell Inc.
  dmi.chassis.version: Not Specified
  dmi.modalias: 
dmi:bvnDellInc.:bvrA05:bd05/18/2013:svnDellInc.:pnInspiron5523:pvrNotSpecified:rvnDellInc.:rn0GKGJG:rvrA05:cvnDellInc.:ct8:cvrNotSpecified:
  dmi.product.name: Inspiron 5523
  dmi.product.version: Not Specified
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.11+14.04.20140423-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.52-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 10.1.0-4ubuntu5
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 10.1.0-4ubuntu5
  version.xserver-xorg-core: xserver-xorg-core 2:1.15.1-0ubuntu2
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.8.2-1ubuntu2
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.3.0-1ubuntu3
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.910-0ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.10-1ubuntu2
  xserver.bootTime: Tue May  6 21:20:40 2014
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5558 
   vendor CMN
  xserver.version: 2:1.15.1-0ubuntu2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1316873/+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 1395338] Re: package software-center 13.10-0ubuntu4.1 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

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

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

Title:
  package software-center 13.10-0ubuntu4.1 failed to install/upgrade:
  subprocess installed post-installation script returned error exit
  status 1

Status in software-center package in Ubuntu:
  Confirmed

Bug description:
  just for  sudo apt-get upgrade
  I am getting the following error, 

  Traceback (most recent call last):
File "/usr/lib/python2.7/site.py", line 563, in 
  main()
File "/usr/lib/python2.7/site.py", line 545, in main
  known_paths = addusersitepackages(known_paths)
File "/usr/lib/python2.7/site.py", line 278, in addusersitepackages
  user_site = getusersitepackages()
File "/usr/lib/python2.7/site.py", line 253, in getusersitepackages
  user_base = getuserbase() # this will also set USER_BASE
File "/usr/lib/python2.7/site.py", line 243, in getuserbase
  USER_BASE = get_config_var('userbase')
File "/usr/lib/python2.7/sysconfig.py", line 521, in get_config_var
  return get_config_vars().get(name)
File "/usr/lib/python2.7/sysconfig.py", line 420, in get_config_vars
  _init_posix(_CONFIG_VARS)
File "/usr/lib/python2.7/sysconfig.py", line 288, in _init_posix
  raise IOError(msg)
  IOError: invalid Python installation: unable to open 
/usr/lib/python2.7/config/Makefile (No such file or directory)
  dpkg: error processing package software-center (--unpack):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for update-notifier-common (0.154.1ubuntu1) ...
  Traceback (most recent call last):
File "/usr/lib/python2.7/site.py", line 563, in 
  main()
File "/usr/lib/python2.7/site.py", line 545, in main
  known_paths = addusersitepackages(known_paths)
File "/usr/lib/python2.7/site.py", line 278, in addusersitepackages
  user_site = getusersitepackages()
File "/usr/lib/python2.7/site.py", line 253, in getusersitepackages
  user_base = getuserbase() # this will also set USER_BASE
File "/usr/lib/python2.7/site.py", line 243, in getuserbase
  USER_BASE = get_config_var('userbase')
File "/usr/lib/python2.7/sysconfig.py", line 521, in get_config_var
  return get_config_vars().get(name)
File "/usr/lib/python2.7/sysconfig.py", line 420, in get_config_vars
  _init_posix(_CONFIG_VARS)
File "/usr/lib/python2.7/sysconfig.py", line 288, in _init_posix
  raise IOError(msg)
  IOError: invalid Python installation: unable to open 
/usr/lib/python2.7/config/Makefile (No such file or directory)
  dpkg: error processing package update-notifier-common (--unpack):
   subprocess installed post-installation script returned error exit status 1
  Processing triggers for libglib2.0-0:amd64 (2.40.2-0ubuntu1) ...
  Processing triggers for libglib2.0-0:i386 (2.40.2-0ubuntu1) ...
  Processing triggers for gnome-menus (3.10.1-0ubuntu2) ...
  Processing triggers for desktop-file-utils (0.22-1ubuntu1) ...
  Processing triggers for bamfdaemon (0.5.1+14.04.20140409-0ubuntu1) ...
  Rebuilding /usr/share/applications/bamf-2.index...
  Processing triggers for mime-support (3.54ubuntu1) ...
  Processing triggers for menu (2.1.46ubuntu1) ...
  E: Sub-process /usr/bin/dpkg returned an error code (1)

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: software-center 13.10-0ubuntu4.1
  ProcVersionSignature: Ubuntu 3.13.0-39.66-generic 3.13.11.8
  Uname: Linux 3.13.0-39-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.14.1-0ubuntu3.5
  Architecture: amd64
  Date: Sat Nov 22 17:07:51 2014
  DuplicateSignature: package:software-center:13.10-0ubuntu4.1:subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2014-10-07 (46 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  PackageArchitecture: all
  SourcePackage: software-center
  Title: package software-center 13.10-0ubuntu4.1 failed to install/upgrade: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/software-center/+bug/1395338/+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 1608535] Re: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-08-02 Thread Lester Larkin
Error message box during 14.04 to 16.04 upgrade:

Could not install 'fontconfig'

The upgrade will continue but the 'fontconfig' package may not be in a
working state. Please consider submitting a bug report about it.

triggers looping, abandoned

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

Title:
  package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  This error occured when I tried to upgrade my Ubuntu from version
  14.04 to version 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1
  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.1
  Architecture: amd64
  Date: Mon Aug  1 12:17:13 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-10-07 (299 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1608535/+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 589840] Re: thunderbird has black menu text with dark theme

2016-08-02 Thread chfirex
Got the same Bug with Ubuntu MATE 16.04. I've found no solution.

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

Title:
  thunderbird has black menu text with dark theme

Status in gnome-themes-ubuntu package in Ubuntu:
  Confirmed
Status in thunderbird package in Ubuntu:
  Confirmed

Bug description:
  Binary package hint: thunderbird

  Using the theme New Wave, Thunderbird has black text on the dark gray
  menu bar. Firefox and other applications have light text.

  Ubuntu 10.04
  Thunderbrid: 3.0.4+nobinonly-0ubuntu4

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-themes-ubuntu/+bug/589840/+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 1609101] [NEW] Menuebar flickering

2016-08-02 Thread chfirex
Public bug reported:

How to reproduce the Bug:

1.) Start Libreoffice
2.) Go with your Mouse over the Menuebar 
3.) Flickering of the entries start


Systemdata:

libreoffice Version:
Version: 5.1.5.2
Build-ID: 1:5.1.5~rc2-0ubuntu1~xenial1

Ubuntu 16.04 Xenial MATE
Kernel: 4.4.0-31-generic
Nvidia 367.27 (Installed from Nvidia)

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

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

Title:
  Menuebar flickering

Status in libreoffice package in Ubuntu:
  New

Bug description:
  How to reproduce the Bug:

  1.) Start Libreoffice
  2.) Go with your Mouse over the Menuebar 
  3.) Flickering of the entries start

  
  Systemdata:

  libreoffice Version:
  Version: 5.1.5.2
  Build-ID: 1:5.1.5~rc2-0ubuntu1~xenial1

  Ubuntu 16.04 Xenial MATE
  Kernel: 4.4.0-31-generic
  Nvidia 367.27 (Installed from Nvidia)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1609101/+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 1494225] Re: Call audio is not routed to headset with HFP

2016-08-02 Thread Peter Penzes
@John

I think, yes. N-Com BT3 is mono headset.
Other car bt set work properly.

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

Title:
  Call audio is not routed to headset with HFP

Status in Canonical System Image:
  Confirmed
Status in bluez package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Invalid
Status in ofono package in Ubuntu:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed

Bug description:
  With bluez 5.33 on Nexus 4 and silo 43 installed:

  * pair and connect a headset over HFP
  * Establish an outgoing call or accept an incoming one
  * Once the call is established the call audio isn't routed through the 
handsfree device

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1494225/+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 1575867] Re: unity-settings-daemon crashes on start with SIGABRT if xrandr provides two displays with the same name

2016-08-02 Thread Erich E. Hoover
Nevermind, this ended up being that I needed to set the LD_LIBRARY_PATH
to /usr/local/lib when launching unity-control-center.  I'm having other
weird problems with this self-compiled version, but I doubt it has
anything to do with this patch.

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

Title:
  unity-settings-daemon crashes on start with SIGABRT if xrandr provides
  two displays with the same name

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  -- Symptoms --

  I am experiencing this bug after a recent upgrade to Ubuntu 16.04,
  with unity-settings-daemon 15.04.1+16.04.20160209.

  unity-settings-daemon always fails to start (leaving me with a quasi-
  functional desktop); when run from a command-line, it simply outputs:

  **
  ERROR:gsd-rr-config.c:661:gsd_rr_config_load_current: assertion failed: 
(gsd_rr_config_match (config, config))
  Aborted

  and crashes with SIGABRT. This is 100% reproducible on my system.

  I have investigated the cause of this crash, and I can provide a patch
  that solves this bug. I do not know whether I shall help fixing this
  bug here, or if should I work with the upstream directly, a word of
  advice in this matter would be very appreciated.

  -- Bug analysis and proposed solution --

  The mentioned assertion fails even though it compares the same
  configuration with itself. What gsd_rr_config_match does internally is
  that it takes each output from a configuration one by one, and
  searches - by name - for a matching output in the other config. If the
  search fails, or the found output does not match the one from first
  config, the gsd_rr_config_match check fails.

  Because of that, this check should never fail when comparing a
  configuration to itself, with the exception of one (presumably rare)
  care. It happens that, for my multi-monitor setup, libxrandr reports
  that there are two different outputs that share the same name "DP-1".
  In this case, the gsd_rr_config_match fails, because when searching
  for a matching output named "DP-1", it will return the same output
  both times, and therefore one pair will be not matching (the
  find_output function returns the first output that matches requested
  name).

  Therefore it appears that comparing configurations by checking whether
  outputs with matching names are equivalent may be wrong, because the
  output names are not guaranteed to be unique. I propose to modify both
  configuration comparing procedures (gsd_rr_config_match and
  gsd_rr_config_equal) so that they compare outputs matching them by
  their ids, which will always be unique due to their nature. Since the
  find_output function (which takes an output name as an argument) is
  only used by these two comparing functions, it makes sense to modify
  it so that it takes an output id as an argument instead.

  This is a valid solution, because in this case even if output names
  happen to repeat, the output ids will be used to distinguish between
  them, and gsd_rr_config_match will no longer incorrectly fail. Also,
  the proposed change will never cause a configuration comparing
  function to return true where it would otherwise not, because each two
  outputs with a different name will always have a different id as well.

  I attach to this bug report a patch that implements the proposed
  changes. Applying this patch entirely fixed the described symptoms on
  my machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1575867/+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 1577074] Re: AMDGPU driver problems on "Carrizo" APU

2016-08-02 Thread Timo Aaltonen
I need the exact model of the laptop, this might be one that has been
certified in the past and has now regressed.

** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu)

** Changed in: xserver-xorg-video-amdgpu (Ubuntu)
 Assignee: (unassigned) => Timo Aaltonen (tjaalton)

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

Title:
  AMDGPU driver problems on "Carrizo" APU

Status in xserver-xorg-video-amdgpu package in Ubuntu:
  Incomplete

Bug description:
  I'm having a hard time tracing this down.  I updated to Kubuntu 16.04
  (from Kubuntu 15.10 - that was using the Linux Crimson 15.12 driver) a
  couple days ago on my notebook (HP Pavilion, A10-8700P APU), and ever
  since I've been having random black screens.

  I started debugging the driver, then thought it might be a DPMS issue
  (it's not - I have DPMS fully disabled currently), and now I'm back to
  debugging the driver.

  I don't have any remnants of the former closed Crimson display driver
  and never had an xorg.conf file (I made a small one that I'm using at
  the moment consisting of only a server layout to ensure screen savers,
  DPMS, etc are all off).

  The Black screen can happen any time from the login screen until hours
  later.  I can ssh into the system to shut it down.  And just
  discovered that if I unplug the system from it's power brick, I can
  close the lid - the system will goto sleep.  When I flip the screen
  back up, the system wakes up and the screen works again for 1-2
  minutes.

  I don't see any errors in the log files (well, outside some nasty
  looking ACAPI errors in dmesg).

  HOT TO REPRODUCE:
  Boot system and use normally or simply leave system alone.  Blank screen will 
happen any time after x comes up.

  
  EXPECTED RESULT:
  Screen doesn't blank unless a screen saver or power saver kicks in.

  SYSTEM INFO:
  Purchased Dec 2015 (build date from BIOS - Aug 2015), HP Pavilion 15" 
notebook, AMD A10-8700P "Carrizo", 16GB RAM, 960GB SSD

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-amdgpu/+bug/1577074/+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 1609058] Re: Xorg freeze

2016-08-02 Thread Timo Aaltonen
** Package changed: xorg (Ubuntu) => nvidia-graphics-drivers-361
(Ubuntu)

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

Title:
  Xorg freeze

Status in nvidia-graphics-drivers-361 package in Ubuntu:
  New

Bug description:
  There seem to be quite a few instances of this bug occurring with
  other users but no real solution appears to have been found. This
  occurs most commonly when doing processing on the GPU with CUDA
  applications such as TensorFlow and MATLAB. Killing lightdm over SSH
  usually fails and a hard reboot is required, initiating reboot command
  over SSH results in an unresponsive machine.

  I've also had it occur while logging into VNC over SSH in which case
  the machine becomes completely unresponsive and no logs are written to
  indicate what has occurred.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
  .proc.driver.nvidia.registry: Binary: ""
  .proc.driver.nvidia.version:
   NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
   GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
  .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
  CurrentDesktop: Unity
  Date: Tue Aug  2 18:57:25 2016
  DistUpgraded: Fresh install
  DistroCodename: xenial
  DistroVariant: ubuntu
  DkmsStatus:
   bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
   bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
   nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
  ExtraDebuggingInterest: Yes
  GpuHangFrequency: Several times a week
  GpuHangReproducibility: Occurs more often under certain circumstances
  GpuHangStarted: Immediately after installing this version of Ubuntu
  GraphicsCard:
   NVIDIA Corporation GK110 [GeForce GTX 780] [10de:1004] (rev a1) (prog-if 00 
[VGA controller])
 Subsystem: NVIDIA Corporation GK110 [GeForce GTX 780] [10de:104b]
  InstallationDate: Installed on 2016-07-22 (11 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  MachineType: System manufacturer Maximus Formula
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=84f2984d-7ea0-4f4f-bcf7-f142d0e6e8b2 ro quiet splash
  SourcePackage: xorg
  Symptom: display
  Title: Xorg freeze
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 09/10/2009
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1403
  dmi.board.asset.tag: To Be Filled By O.E.M.
  dmi.board.name: Maximus Formula
  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.:bvr1403:bd09/10/2009:svnSystemmanufacturer:pnMaximusFormula:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
  dmi.product.name: Maximus Formula
  dmi.product.version: System Version
  dmi.sys.vendor: System manufacturer
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Tue Aug  2 18:31:51 2016
  xserver.configfile: default
  xserver.devices:
   inputPower Button KEYBOARD, id 6
   inputPower Button KEYBOARD, id 7
   inputSteelSeries SteelSeries Kinzu V3 Gaming Mouse MOUSE, id 8
   inputDell Dell USB Entry Keyboard KEYBOARD, id 9
  xserver.errors: open /dev/fb0: No such file or directory
  xserver.logfile: 

[Desktop-packages] [Bug 1605953] Re: skylake Modesetting Driver on X failure

2016-08-02 Thread Timo Aaltonen
And I have the lowest specced Skylake available on a laptop, default
desktop and all... things are just fine on that too. I blame your
session settings, try with the guest user

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

Title:
  skylake Modesetting Driver on X failure

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  with the change away from the intel driver to modeset I get a lot of
  tearing.

  This video shows the problem.

  https://goo.gl/photos/rXNBQ5KR6ZMnhazB9
  And the video capture is done in 240fps so its possible to see what is 
happening more clearly.

  The test video itself is just a short test video with alternating
  red/green pictures in 60Hz.

  What you should see is a somewhat flickering screen but the color
  should be a consistent orange hue.

  there should be no pulsing of colors that is more green then back to
  more red and so on then something is wrong.

  I have attached the video. if you are uncertain how it should look try to 
play it directly on a TV. that is with the TV own player not with a computer as 
that has a lot higher probability of not having any issues with vsync and frame 
updates.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   /dev/sda2: clean, 770076/2416640 files, 3881571/9647872 blocks
   (K(K
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2016-04-22 23:31:04,108 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7976]
   Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] 
[1002:7300] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon R9 FURY X [1043:04a0]
  InstallationDate: Installed on 2015-10-18 (281 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: MSI MS-7976
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7+ 
root=UUID=75bb5d92-206d-4bb8-a405-150b9b93d6d3 ro quiet splash vt.handoff=7
  Tags:  yakkety ubuntu regression reproducible compiz-0.9
  Uname: Linux 4.7.0-rc7+ x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-04-22 (94 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160714.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.69-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+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 1609088] [NEW] map view is off-center

2016-08-02 Thread Jeremy Bicha
Public bug reported:

[Impact]
Some widgets such as the map view in gnome-maps 3.18.3 are off-center. (The 
upstream bug was originally about polari 3.19, an IRC app from GNOME.)

Screenshot attached.

[Test Case]
1. Install gnome-maps 3.18.3-0ubuntu1 (as of today, in xenial-proposed)
2. Open the maps app. Is there a blank area on one side of the map view?
3. Install the updated gtk-3 packages
4. Open the maps app. The map view should fill the map view space.

[Regression Potential]
The minimal fix has been shipped with GTK since 3.19.10. (Therefore, this bug 
is already fixed in yakkety-proposed.)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: libgtk-3-0 3.18.9-1ubuntu3.1
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.1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Aug  2 14:58:11 2016
InstallationDate: Installed on 2016-07-31 (2 days ago)
InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gtk+3.0
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: gtk
 Importance: Unknown
 Status: Unknown

** Affects: gtk+3.0 (Ubuntu)
 Importance: Medium
 Status: Triaged


** Tags: amd64 apport-bug xenial

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

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

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

Title:
  map view is off-center

Status in GTK+:
  Unknown
Status in gtk+3.0 package in Ubuntu:
  Triaged

Bug description:
  [Impact]
  Some widgets such as the map view in gnome-maps 3.18.3 are off-center. (The 
upstream bug was originally about polari 3.19, an IRC app from GNOME.)

  Screenshot attached.

  [Test Case]
  1. Install gnome-maps 3.18.3-0ubuntu1 (as of today, in xenial-proposed)
  2. Open the maps app. Is there a blank area on one side of the map view?
  3. Install the updated gtk-3 packages
  4. Open the maps app. The map view should fill the map view space.

  [Regression Potential]
  The minimal fix has been shipped with GTK since 3.19.10. (Therefore, this bug 
is already fixed in yakkety-proposed.)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: libgtk-3-0 3.18.9-1ubuntu3.1
  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.1
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue Aug  2 14:58:11 2016
  InstallationDate: Installed on 2016-07-31 (2 days ago)
  InstallationMedia: Ubuntu-GNOME 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160720)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gtk+3.0
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gtk/+bug/1609088/+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 1605953] Re: skylake Modesetting Driver on X failure

2016-08-02 Thread kenjo
No I'm running ubuntu with unity. Standard ubuntu desktop.

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

Title:
  skylake Modesetting Driver on X failure

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  with the change away from the intel driver to modeset I get a lot of
  tearing.

  This video shows the problem.

  https://goo.gl/photos/rXNBQ5KR6ZMnhazB9
  And the video capture is done in 240fps so its possible to see what is 
happening more clearly.

  The test video itself is just a short test video with alternating
  red/green pictures in 60Hz.

  What you should see is a somewhat flickering screen but the color
  should be a consistent orange hue.

  there should be no pulsing of colors that is more green then back to
  more red and so on then something is wrong.

  I have attached the video. if you are uncertain how it should look try to 
play it directly on a TV. that is with the TV own player not with a computer as 
that has a lot higher probability of not having any issues with vsync and frame 
updates.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   /dev/sda2: clean, 770076/2416640 files, 3881571/9647872 blocks
   (K(K
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2016-04-22 23:31:04,108 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7976]
   Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] 
[1002:7300] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon R9 FURY X [1043:04a0]
  InstallationDate: Installed on 2015-10-18 (281 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: MSI MS-7976
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7+ 
root=UUID=75bb5d92-206d-4bb8-a405-150b9b93d6d3 ro quiet splash vt.handoff=7
  Tags:  yakkety ubuntu regression reproducible compiz-0.9
  Uname: Linux 4.7.0-rc7+ x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-04-22 (94 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160714.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.69-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+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 1606774] Re: Xorg crash

2016-08-02 Thread Timo Aaltonen
** Package changed: xorg (Ubuntu) => xorg-server (Ubuntu)

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

Title:
  Xorg crash

Status in xorg-server package in Ubuntu:
  Incomplete

Bug description:
  I get random X server crashes

  The last lines of the Xorg.0.log.old are:

  [  1163.549] (EE) 
  [  1163.549] (EE) Backtrace:
  [  1163.549] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5574057265ce]
  [  1163.549] (EE) 1: /usr/lib/xorg/Xorg (0x557405574000+0x1b6959) 
[0x55740572a959]
  [  1163.550] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f958502f000+0x354a0) 
[0x7f95850644a0]
  [  1163.550] (EE) 3: /usr/lib/xorg/Xorg (0x557405574000+0x129595) 
[0x55740569d595]
  [  1163.550] (EE) 4: /usr/lib/xorg/Xorg (ValidatePicture+0x9) [0x55740569f359]
  [  1163.550] (EE) 5: /usr/lib/xorg/Xorg (CompositePicture+0xb5) 
[0x55740569f435]
  [  1163.550] (EE) 6: /usr/lib/xorg/Xorg (0x557405574000+0x12fc17) 
[0x5574056a3c17]
  [  1163.550] (EE) 7: /usr/lib/xorg/Xorg (0x557405574000+0x53bbf) 
[0x5574055c7bbf]
  [  1163.550] (EE) 8: /usr/lib/xorg/Xorg (0x557405574000+0x57c33) 
[0x5574055cbc33]
  [  1163.551] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f958504f830]
  [  1163.551] (EE) 10: /usr/lib/xorg/Xorg (_start+0x29) [0x5574055b5f59]
  [  1163.551] (EE) 
  [  1163.551] (EE) Segmentation fault at address 0x18
  [  1163.551] (EE) 
  Fatal server error:
  [  1163.551] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1163.551] (EE) 
  [  1163.551] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-lowlatency 4.4.13
  Uname: Linux 4.4.0-28-lowlatency 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: None
  CurrentDesktop: MATE
  Date: Wed Jul 27 07:49:22 2016
  DistUpgraded: 2016-05-30 00:00:15,168 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0704]
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-lowlatency 
root=/dev/mapper/sarvg-rootvol ro rootflags=subvol=@ quiet 
intel_idle.max_cstate=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to xenial on 2016-05-29 (58 days ago)
  dmi.bios.date: 11/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.7
  dmi.board.name: 0VM5NC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.7:bd11/27/2015:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul 27 07:48:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5153 
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1606774/+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 1605953] Re: skylake Modesetting Driver on X failure

2016-08-02 Thread Timo Aaltonen
So I guess you're not running Ubuntu/Kubuntu but something else? What's
the window manager? Could just be a WM bug..

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

Title:
  skylake Modesetting Driver on X failure

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  with the change away from the intel driver to modeset I get a lot of
  tearing.

  This video shows the problem.

  https://goo.gl/photos/rXNBQ5KR6ZMnhazB9
  And the video capture is done in 240fps so its possible to see what is 
happening more clearly.

  The test video itself is just a short test video with alternating
  red/green pictures in 60Hz.

  What you should see is a somewhat flickering screen but the color
  should be a consistent orange hue.

  there should be no pulsing of colors that is more green then back to
  more red and so on then something is wrong.

  I have attached the video. if you are uncertain how it should look try to 
play it directly on a TV. that is with the TV own player not with a computer as 
that has a lot higher probability of not having any issues with vsync and frame 
updates.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   /dev/sda2: clean, 770076/2416640 files, 3881571/9647872 blocks
   (K(K
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2016-04-22 23:31:04,108 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7976]
   Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] 
[1002:7300] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon R9 FURY X [1043:04a0]
  InstallationDate: Installed on 2015-10-18 (281 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: MSI MS-7976
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7+ 
root=UUID=75bb5d92-206d-4bb8-a405-150b9b93d6d3 ro quiet splash vt.handoff=7
  Tags:  yakkety ubuntu regression reproducible compiz-0.9
  Uname: Linux 4.7.0-rc7+ x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-04-22 (94 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160714.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.69-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+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 1443134] Re: package libhogweed2:amd64 2.7.1-1 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configuration

2016-08-02 Thread Magnus Holmgren
This is most probably not a bug in nettle/libhogweed2, but the result of
a somehow aborted earlier operation, and should be possible to resolve
simply by doing as the error message suggests.

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

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

Title:
  package libhogweed2:amd64 2.7.1-1 failed to install/upgrade: package
  is in a very bad inconsistent state; you should  reinstall it before
  attempting configuration

Status in nettle package in Ubuntu:
  Invalid

Bug description:
  installing mpstat  using apt-get . mpstat installed but it through
  error !!

  ProblemType: Package
  DistroRelease: Ubuntu 14.04
  Package: libhogweed2:amd64 2.7.1-1
  ProcVersionSignature: Ubuntu 3.13.0-46.76-generic 3.13.11-ckt15
  Uname: Linux 3.13.0-46-generic x86_64
  ApportVersion: 2.14.1-0ubuntu3.7
  Architecture: amd64
  Date: Sun Apr 12 22:33:03 2015
  DuplicateSignature: package:libhogweed2:amd64:2.7.1-1:package is in a very 
bad inconsistent state; you should  reinstall it before attempting configuration
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-02-24 (46 days ago)
  InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 
(20140722.2)
  SourcePackage: nettle
  Title: package libhogweed2:amd64 2.7.1-1 failed to install/upgrade: package 
is in a very bad inconsistent state; you should  reinstall it before attempting 
configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nettle/+bug/1443134/+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 1605953] Re: skylake Modesetting Driver on X failure

2016-08-02 Thread kenjo
well it's not just vlc and any special setting. its EVERYTHING!!! noting
is synced moving a window playing video in any player. scrolling in
browser playing youtube in browser.

EVERYTHING look like shit you can not miss it.

here is another person having the same issue.

https://whirm.eu/posts/fix-for-xorgs-modesetting-driver-tearing/

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

Title:
  skylake Modesetting Driver on X failure

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  with the change away from the intel driver to modeset I get a lot of
  tearing.

  This video shows the problem.

  https://goo.gl/photos/rXNBQ5KR6ZMnhazB9
  And the video capture is done in 240fps so its possible to see what is 
happening more clearly.

  The test video itself is just a short test video with alternating
  red/green pictures in 60Hz.

  What you should see is a somewhat flickering screen but the color
  should be a consistent orange hue.

  there should be no pulsing of colors that is more green then back to
  more red and so on then something is wrong.

  I have attached the video. if you are uncertain how it should look try to 
play it directly on a TV. that is with the TV own player not with a computer as 
that has a lot higher probability of not having any issues with vsync and frame 
updates.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   /dev/sda2: clean, 770076/2416640 files, 3881571/9647872 blocks
   (K(K
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2016-04-22 23:31:04,108 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7976]
   Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] 
[1002:7300] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon R9 FURY X [1043:04a0]
  InstallationDate: Installed on 2015-10-18 (281 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: MSI MS-7976
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7+ 
root=UUID=75bb5d92-206d-4bb8-a405-150b9b93d6d3 ro quiet splash vt.handoff=7
  Tags:  yakkety ubuntu regression reproducible compiz-0.9
  Uname: Linux 4.7.0-rc7+ x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-04-22 (94 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160714.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.69-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+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 151365] Re: Autosave doesn't work for Unsaved Documents

2016-08-02 Thread Vance Morris
Please implement this... I use gedit all the time and it's pretty damn
annoying that this feature hasn't been added yet.

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

Title:
  Autosave doesn't work for Unsaved Documents

Status in gedit:
  Confirmed
Status in gedit package in Ubuntu:
  Triaged

Bug description:
  Autosave doesn't happen if the document has *never* been saved.  It should,
  since data can be lost if there is a crash while an unsaved document is in the
  editor.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gedit/+bug/151365/+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 1609070] Re: package libllvm3.8:i386 1:3.8-2ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configura

2016-08-02 Thread Apport retracing service
** Tags removed: need-duplicate-check

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

Title:
  package libllvm3.8:i386 1:3.8-2ubuntu4 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in llvm-toolchain-3.8 package in Ubuntu:
  New

Bug description:
  just when i start my notebook

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libllvm3.8:i386 1:3.8-2ubuntu4
  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.1
  Architecture: amd64
  Date: Wed Aug  3 00:16:29 2016
  DpkgHistoryLog:
   Start-Date: 2016-08-03  00:14:45
   Upgrade: virtualbox-dkms:amd64 (5.0.18-dfsg-2build1, 
5.0.24-dfsg-0ubuntu1.16.04.1), compizconfig-settings-manager:amd64 
(1:0.9.12.2+16.04.20160526-0ubuntu1, 1:0.9.12.2+16.04.20160714-0ubuntu1), 
unity-scopes-runner:amd64 (7.1.4+15.10.20151002-0ubuntu2, 
7.1.4+16.04.20160701-0ubuntu1), virtualbox:amd64 (5.0.18-dfsg-2build1, 
5.0.24-dfsg-0ubuntu1.16.04.1), libllvm3.8:amd64 (1:3.8-2ubuntu3, 
1:3.8-2ubuntu4), virtualbox-qt:amd64 (5.0.18-dfsg-2build1, 
5.0.24-dfsg-0ubuntu1.16.04.1), libunity-scopes-json-def-desktop:amd64 
(7.1.4+15.10.20151002-0ubuntu2, 7.1.4+16.04.20160701-0ubuntu1), 
python-compizconfig:amd64 (1:0.9.12.2+16.04.20160526-0ubuntu1, 
1:0.9.12.2+16.04.20160714-0ubuntu1)
  DuplicateSignature:
   package:libllvm3.8:i386:1:3.8-2ubuntu4
   Setting up libllvm3.8:amd64 (1:3.8-2ubuntu4) ...
   dpkg: error processing package libllvm3.8:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-05-18 (442 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: llvm-toolchain-3.8
  Title: package libllvm3.8:i386 1:3.8-2ubuntu4 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.8/+bug/1609070/+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 1609070] [NEW] package libllvm3.8:i386 1:3.8-2ubuntu4 failed to install/upgrade: package is in a very bad inconsistent state; you should reinstall it before attempting configu

2016-08-02 Thread huyadesa...@gmail.com
Public bug reported:

just when i start my notebook

ProblemType: Package
DistroRelease: Ubuntu 16.04
Package: libllvm3.8:i386 1:3.8-2ubuntu4
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.1
Architecture: amd64
Date: Wed Aug  3 00:16:29 2016
DpkgHistoryLog:
 Start-Date: 2016-08-03  00:14:45
 Upgrade: virtualbox-dkms:amd64 (5.0.18-dfsg-2build1, 
5.0.24-dfsg-0ubuntu1.16.04.1), compizconfig-settings-manager:amd64 
(1:0.9.12.2+16.04.20160526-0ubuntu1, 1:0.9.12.2+16.04.20160714-0ubuntu1), 
unity-scopes-runner:amd64 (7.1.4+15.10.20151002-0ubuntu2, 
7.1.4+16.04.20160701-0ubuntu1), virtualbox:amd64 (5.0.18-dfsg-2build1, 
5.0.24-dfsg-0ubuntu1.16.04.1), libllvm3.8:amd64 (1:3.8-2ubuntu3, 
1:3.8-2ubuntu4), virtualbox-qt:amd64 (5.0.18-dfsg-2build1, 
5.0.24-dfsg-0ubuntu1.16.04.1), libunity-scopes-json-def-desktop:amd64 
(7.1.4+15.10.20151002-0ubuntu2, 7.1.4+16.04.20160701-0ubuntu1), 
python-compizconfig:amd64 (1:0.9.12.2+16.04.20160526-0ubuntu1, 
1:0.9.12.2+16.04.20160714-0ubuntu1)
DuplicateSignature:
 package:libllvm3.8:i386:1:3.8-2ubuntu4
 Setting up libllvm3.8:amd64 (1:3.8-2ubuntu4) ...
 dpkg: error processing package libllvm3.8:i386 (--configure):
  package is in a very bad inconsistent state; you should
ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
InstallationDate: Installed on 2015-05-18 (442 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
PackageArchitecture: i386
RelatedPackageVersions:
 dpkg 1.18.4ubuntu1.1
 apt  1.2.12~ubuntu16.04.1
SourcePackage: llvm-toolchain-3.8
Title: package libllvm3.8:i386 1:3.8-2ubuntu4 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
UpgradeStatus: No upgrade log present (probably fresh install)

** Affects: llvm-toolchain-3.8 (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: apport-package i386 xenial

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

Title:
  package libllvm3.8:i386 1:3.8-2ubuntu4 failed to install/upgrade:
  package is in a very bad inconsistent state; you should  reinstall it
  before attempting configuration

Status in llvm-toolchain-3.8 package in Ubuntu:
  New

Bug description:
  just when i start my notebook

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: libllvm3.8:i386 1:3.8-2ubuntu4
  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.1
  Architecture: amd64
  Date: Wed Aug  3 00:16:29 2016
  DpkgHistoryLog:
   Start-Date: 2016-08-03  00:14:45
   Upgrade: virtualbox-dkms:amd64 (5.0.18-dfsg-2build1, 
5.0.24-dfsg-0ubuntu1.16.04.1), compizconfig-settings-manager:amd64 
(1:0.9.12.2+16.04.20160526-0ubuntu1, 1:0.9.12.2+16.04.20160714-0ubuntu1), 
unity-scopes-runner:amd64 (7.1.4+15.10.20151002-0ubuntu2, 
7.1.4+16.04.20160701-0ubuntu1), virtualbox:amd64 (5.0.18-dfsg-2build1, 
5.0.24-dfsg-0ubuntu1.16.04.1), libllvm3.8:amd64 (1:3.8-2ubuntu3, 
1:3.8-2ubuntu4), virtualbox-qt:amd64 (5.0.18-dfsg-2build1, 
5.0.24-dfsg-0ubuntu1.16.04.1), libunity-scopes-json-def-desktop:amd64 
(7.1.4+15.10.20151002-0ubuntu2, 7.1.4+16.04.20160701-0ubuntu1), 
python-compizconfig:amd64 (1:0.9.12.2+16.04.20160526-0ubuntu1, 
1:0.9.12.2+16.04.20160714-0ubuntu1)
  DuplicateSignature:
   package:libllvm3.8:i386:1:3.8-2ubuntu4
   Setting up libllvm3.8:amd64 (1:3.8-2ubuntu4) ...
   dpkg: error processing package libllvm3.8:i386 (--configure):
package is in a very bad inconsistent state; you should
  ErrorMessage: package is in a very bad inconsistent state; you should  
reinstall it before attempting configuration
  InstallationDate: Installed on 2015-05-18 (442 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: i386
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: llvm-toolchain-3.8
  Title: package libllvm3.8:i386 1:3.8-2ubuntu4 failed to install/upgrade: 
package is in a very bad inconsistent state; you should  reinstall it before 
attempting configuration
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/llvm-toolchain-3.8/+bug/1609070/+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 1575867] Re: unity-settings-daemon crashes on start with SIGABRT if xrandr provides two displays with the same name

2016-08-02 Thread Erich E. Hoover
I am trying to apply this fix for someone and, after some fighting
getting everything setup, I was able to get everything installed to
/usr/local and manually run the custom version.  However, it appears
that I still cannot use the Displays panel of unity-control-center to
actually configure the orientation of their monitors.  Is there
something else that needs to be done for this application to work
correctly?

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

Title:
  unity-settings-daemon crashes on start with SIGABRT if xrandr provides
  two displays with the same name

Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  -- Symptoms --

  I am experiencing this bug after a recent upgrade to Ubuntu 16.04,
  with unity-settings-daemon 15.04.1+16.04.20160209.

  unity-settings-daemon always fails to start (leaving me with a quasi-
  functional desktop); when run from a command-line, it simply outputs:

  **
  ERROR:gsd-rr-config.c:661:gsd_rr_config_load_current: assertion failed: 
(gsd_rr_config_match (config, config))
  Aborted

  and crashes with SIGABRT. This is 100% reproducible on my system.

  I have investigated the cause of this crash, and I can provide a patch
  that solves this bug. I do not know whether I shall help fixing this
  bug here, or if should I work with the upstream directly, a word of
  advice in this matter would be very appreciated.

  -- Bug analysis and proposed solution --

  The mentioned assertion fails even though it compares the same
  configuration with itself. What gsd_rr_config_match does internally is
  that it takes each output from a configuration one by one, and
  searches - by name - for a matching output in the other config. If the
  search fails, or the found output does not match the one from first
  config, the gsd_rr_config_match check fails.

  Because of that, this check should never fail when comparing a
  configuration to itself, with the exception of one (presumably rare)
  care. It happens that, for my multi-monitor setup, libxrandr reports
  that there are two different outputs that share the same name "DP-1".
  In this case, the gsd_rr_config_match fails, because when searching
  for a matching output named "DP-1", it will return the same output
  both times, and therefore one pair will be not matching (the
  find_output function returns the first output that matches requested
  name).

  Therefore it appears that comparing configurations by checking whether
  outputs with matching names are equivalent may be wrong, because the
  output names are not guaranteed to be unique. I propose to modify both
  configuration comparing procedures (gsd_rr_config_match and
  gsd_rr_config_equal) so that they compare outputs matching them by
  their ids, which will always be unique due to their nature. Since the
  find_output function (which takes an output name as an argument) is
  only used by these two comparing functions, it makes sense to modify
  it so that it takes an output id as an argument instead.

  This is a valid solution, because in this case even if output names
  happen to repeat, the output ids will be used to distinguish between
  them, and gsd_rr_config_match will no longer incorrectly fail. Also,
  the proposed change will never cause a configuration comparing
  function to return true where it would otherwise not, because each two
  outputs with a different name will always have a different id as well.

  I attach to this bug report a patch that implements the proposed
  changes. Applying this patch entirely fixed the described symptoms on
  my machine.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-settings-daemon/+bug/1575867/+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 1605260] Re: Memory leak in libnl-3 (3.2.21-1ubuntu3) in 14.04

2016-08-02 Thread Robie Basak
** Tags added: server-next

** Tags added: bitesize

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

Title:
  Memory leak in libnl-3 (3.2.21-1ubuntu3) in 14.04

Status in libnl3 package in Ubuntu:
  New

Bug description:
  There is a memory leak in libnl 3.2.21 fixed by upstream here:
  http://lists.infradead.org/pipermail/libnl/2013-April/000985.html and
  released as part of libnl-3.2.22 (git commit rev
  df66b0f267af636848d7f0301d3f5863c58fb313).

  However, this fix doesn't make it into Ubuntu 14.04LTS. Please, apply.

  
  $ lsb_release -rd
  Description:Ubuntu 14.04.4 LTS
  Release:14.04
  $ apt-cache policy libnl-3-200
  libnl-3-200:
Installed: 3.2.21-1ubuntu3
Candidate: 3.2.21-1ubuntu3
Version table:
   *** 3.2.21-1ubuntu3 0
  500 http://ua.archive.ubuntu.com/ubuntu/ trusty-updates/main i386 
Packages
  100 /var/lib/dpkg/status
   3.2.21-1 0
  500 http://ua.archive.ubuntu.com/ubuntu/ trusty/main i386 Packages
  $

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnl3/+bug/1605260/+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 1609058] [NEW] Xorg freeze

2016-08-02 Thread Zander Horn
Public bug reported:

There seem to be quite a few instances of this bug occurring with other
users but no real solution appears to have been found. This occurs most
commonly when doing processing on the GPU with CUDA applications such as
TensorFlow and MATLAB. Killing lightdm over SSH usually fails and a hard
reboot is required, initiating reboot command over SSH results in an
unresponsive machine.

I've also had it occur while logging into VNC over SSH in which case the
machine becomes completely unresponsive and no logs are written to
indicate what has occurred.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: xorg 1:7.7+13ubuntu3
ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
Uname: Linux 4.4.0-31-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
.proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: 
'/proc/driver/nvidia/gpus/:01:00.0'
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.version:
 NVRM version: NVIDIA UNIX x86_64 Kernel Module  361.42  Tue Mar 22 18:10:58 
PDT 2016
 GCC version:  gcc version 5.4.0 20160609 (Ubuntu 5.4.0-6ubuntu1~16.04.1)
.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
CurrentDesktop: Unity
Date: Tue Aug  2 18:57:25 2016
DistUpgraded: Fresh install
DistroCodename: xenial
DistroVariant: ubuntu
DkmsStatus:
 bbswitch, 0.8, 4.4.0-21-generic, x86_64: installed
 bbswitch, 0.8, 4.4.0-31-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-21-generic, x86_64: installed
 nvidia-361, 361.42, 4.4.0-31-generic, x86_64: installed
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Occurs more often under certain circumstances
GpuHangStarted: Immediately after installing this version of Ubuntu
GraphicsCard:
 NVIDIA Corporation GK110 [GeForce GTX 780] [10de:1004] (rev a1) (prog-if 00 
[VGA controller])
   Subsystem: NVIDIA Corporation GK110 [GeForce GTX 780] [10de:104b]
InstallationDate: Installed on 2016-07-22 (11 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1)
MachineType: System manufacturer Maximus Formula
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-31-generic 
root=UUID=84f2984d-7ea0-4f4f-bcf7-f142d0e6e8b2 ro quiet splash
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 09/10/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1403
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: Maximus Formula
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.:bvr1403:bd09/10/2009:svnSystemmanufacturer:pnMaximusFormula:pvrSystemVersion:rvnASUSTeKComputerINC.:rnMaximusFormula:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: Maximus Formula
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:1.18.3-1ubuntu2.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
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-1build2
xserver.bootTime: Tue Aug  2 18:31:51 2016
xserver.configfile: default
xserver.devices:
 inputPower Button KEYBOARD, id 6
 inputPower Button KEYBOARD, id 7
 inputSteelSeries SteelSeries Kinzu V3 Gaming Mouse MOUSE, id 8
 inputDell Dell USB Entry Keyboard KEYBOARD, id 9
xserver.errors: open /dev/fb0: No such file or directory
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.18.3-1ubuntu2.2

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


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

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

Title:
  Xorg freeze

Status in xorg package in Ubuntu:
  New

Bug description:
  There seem to be quite a few instances of this bug occurring with
  other users 

[Desktop-packages] [Bug 1609009] Re: gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead)

2016-08-02 Thread Bug Watch Updater
** Changed in: gnome-terminal
   Status: Unknown => Confirmed

** Changed in: gnome-terminal
   Importance: Unknown => Wishlist

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

Title:
  gnome-terminal should allow the disabling of text wrapping (so that
  there is a scroll bar at the bottom instead)

Status in GNOME Terminal:
  Confirmed
Status in Ubuntu GNOME:
  New
Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I would find it rather useful, especially with certain types of
  outputs, if gnome-terminal would allow me to disable text wrapping,
  that is so that there would be a horizontal scroll bar that would
  allow me to see the rest of the text.

  I don't know if this should/would include the commands you type it,
  but maybe there could be a separate option for the wrapping of that.

  There are other Terminals which support this, and I think it would be
  really nice if gnome-terminal would too so that one doesn't have to
  put all of the output into another program like 'less' or similar in
  order to disable the wrapping.

  I am running Ubuntu GNOME 16.04 with GNOME 3.20 and would find this a
  very useful feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1609009/+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 303604] Re: rhythmbox could not open resource for reading

2016-08-02 Thread M
*** This bug is a duplicate of bug 273294 ***
https://bugs.launchpad.net/bugs/273294

I tryied with terminal and the -d suffix and i got this in my log:

(12:37:24) [0x214d410] [rb_track_transfer_batch_check_profiles] 
rb-track-transfer-batch.c:316: copying entry 
file:///home/gmax/Music/electro/Pegboard%20Nerds/Pegboard%20Nerds%20-%20Self%20Destruct.mp3
(12:37:24) [0x214d410] [start_next] rb-track-transfer-batch.c:628: 1 entries 
remain in the batch
(12:37:24) [0x214d410] [start_next] rb-track-transfer-batch.c:644: attempting 
to transfer 
file:///home/gmax/Music/electro/Pegboard%20Nerds/Pegboard%20Nerds%20-%20Self%20Destruct.mp3
(12:37:24) [0x214d410] [select_profile_for_entry] 
rb-track-transfer-batch.c:247: can use lossy encoding audio/x-aac
(12:37:24) [0x214d410] [select_profile_for_entry] 
rb-track-transfer-batch.c:243: can use preferred encoding audio/x-vorbis
(12:37:24) [0x214d410] [select_profile_for_entry] 
rb-track-transfer-batch.c:238: can use source encoding audio/mpeg
(12:37:24) [0x214d410] [select_profile_for_entry] 
rb-track-transfer-batch.c:250: can use lossless encoding audio/x-flac
(12:37:24) [0x214d410] [rb_transfer_target_build_dest_uri] 
rb-transfer-target.c:101: built dest uri for media type 'audio/mpeg', extension 
'mp3': 
mtp://[usb:001,004]/Phone/Music/Pegboard%20Nerds/www.downsong.com/00%20-%20Self%20Destruct.mp3.mp3
(12:37:24) [0x214d410] [attach_output_pipeline] rb-encoder-gst.c:500: 
attempting to open output file 
mtp://[usb:001,004]/Phone/Music/Pegboard%20Nerds/www.downsong.com/00%20-%20Self%20Destruct.mp3.mp3
(12:37:24) [0x214d410] [attach_output_pipeline] rb-encoder-gst.c:509: 
giostreamsink can't write to 
mtp://[usb:001,004]/Phone/Music/Pegboard%20Nerds/www.downsong.com/00%20-%20Self%20Destruct.mp3.mp3
(12:37:24) [0x214d410] [sync_window_settings] rb-shell.c:1918: paned position 
160
(12:37:24) [0x214d410] [sync_window_settings] rb-shell.c:1925: right_paned 
position 400
(12:37:24) [0x214d410] [sync_window_settings] rb-shell.c:1932: sidebar paned 
position 300
(12:37:24) [0x214d410] [bus_watch_cb] rb-encoder-gst.c:186: received error 
gstgiosink.c(299): gst_gio_sink_get_stream (): 
/GstPipeline:pipeline/GstGioSink:sink:
Could not open location 
mtp://[usb:001,004]/Phone/Music/Pegboard%20Nerds/www.downsong.com/00%20-%20Self%20Destruct.mp3.mp3
 for writing: Operation unsupported
(12:37:24) [0x214d410] [rb_encoder_gst_emit_completed] rb-encoder-gst.c:139: 
couldn't get size of destination 
mtp://[usb:001,004]/Phone/Music/Pegboard%20Nerds/www.downsong.com/00%20-%20Self%20Destruct.mp3.mp3:
 File not found
(12:37:24) [0x214d410] [encoder_completed_cb] rb-track-transfer-batch.c:561: 
encoder finished (error: Could not open resource for writing.)
(12:37:24) [0x214d410] [track_done_cb] rb-transfer-target.c:366: fatal transfer 
error: Could not open resource for writing.
(12:37:24) [0x214d410] [_rb_track_transfer_batch_cancel] 
rb-track-transfer-batch.c:445: batch being cancelled
 im not a programing bomb but whats going on with the **.mp3.mp3 ?

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

Title:
  rhythmbox could not open resource for reading

Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: rhythmbox

  I recently tried to use Rhythmbox to play music files that are on a
  WinXP share, that had previously been added to the Rhythmbox library.
  Each file that I attempt to play generates an "unknown error" message.
  If I try to "Import from a folder", I can browse to the folder, but
  then each file generates the "Could not open resource for reading"
  error. I can browse to WinXP share, successfully mount it, and I can
  double-click files and they will play in the Totem Movie Player. I was
  able to play these MP3 files before. This is the first time I've tried
  playing them since upgrading from Ubuntu 8.04 to 8.10. I have already
  gone back into Synaptic and had it reinstall Rhythmbox, but even after
  restarting I still get these errors.

  Description:  Ubuntu 8.10, Release:   8.10
  Installed Package Version: 0.11.6svn20081008-0ubuntu4.2 (matches Latest 
Version in Synaptic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/303604/+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 1409032] Re: gvfsd-smb: very high CPU utilisation

2016-08-02 Thread Sebastien Bacher
** No longer affects: samba (Fedora)

** Also affects: gvfs (Fedora) via
   https://bugzilla.redhat.com/cgi-bin/bugreport.cgi?bug=1303300
   Importance: Unknown
   Status: Unknown

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

Title:
  gvfsd-smb: very high CPU utilisation

Status in gvfs package in Ubuntu:
  Confirmed
Status in samba package in Ubuntu:
  Confirmed
Status in gvfs package in Fedora:
  Unknown

Bug description:
  Example:

  I use Virtualbox and mount a .vdi on an SMB server. Using gvfsd-smb
  (browsing within Gnome to find the share), gvfsd-smb uses up to 50%
  CPU which slows down the entire system when accessing the network
  share. Mounting using sudo ($ sudo mount -t smbfs -o
  guest,nounix,noperm //server/share /media/share) so that cifs is used
  uses around 8% CPU. The difference is dramatic!

  If I didn't have sudo access my machine would grind to a halt when
  trying to use the remote share.

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gvfs-backends 1.12.1-0ubuntu1.2
  ProcVersionSignature: Ubuntu 3.11.0-26.45~precise1-generic 3.11.10.12
  Uname: Linux 3.11.0-26-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.0.1-0ubuntu17.8
  Architecture: i386
  Date: Fri Jan  9 14:32:20 2015
  MarkForUpload: True
  ProcEnviron:
   LANGUAGE=en_GB:en
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gvfs
  UpgradeStatus: Upgraded to precise on 2014-12-07 (33 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1409032/+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 1390475] Re: error while doing upgrade for tex-common package

2016-08-02 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version.

When you test it and it is still an issue, kindly upload the updated
logs by running only once:

apport-collect 1390475

and any other logs that are relevant for this particular issue.

** Changed in: tex-common (Ubuntu)
   Status: New => Incomplete

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

Title:
  error while doing upgrade for tex-common package

Status in tex-common package in Ubuntu:
  Incomplete

Bug description:
  
  Please refer the attached snapshot for the same.


  
  subprocess installed post-installation script returned error exit status 1

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1390475/+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 303604] Re: rhythmbox could not open resource for reading

2016-08-02 Thread M
*** This bug is a duplicate of bug 273294 ***
https://bugs.launchpad.net/bugs/273294

the same bug applies to when i try to copy files from my HD via
rhythmbox to my samsung galaxy s6...  i can read acces and delete files
with file manager but rhythmbox wont tranfer songs nor podcast

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

Title:
  rhythmbox could not open resource for reading

Status in rhythmbox package in Ubuntu:
  Invalid

Bug description:
  Binary package hint: rhythmbox

  I recently tried to use Rhythmbox to play music files that are on a
  WinXP share, that had previously been added to the Rhythmbox library.
  Each file that I attempt to play generates an "unknown error" message.
  If I try to "Import from a folder", I can browse to the folder, but
  then each file generates the "Could not open resource for reading"
  error. I can browse to WinXP share, successfully mount it, and I can
  double-click files and they will play in the Totem Movie Player. I was
  able to play these MP3 files before. This is the first time I've tried
  playing them since upgrading from Ubuntu 8.04 to 8.10. I have already
  gone back into Synaptic and had it reinstall Rhythmbox, but even after
  restarting I still get these errors.

  Description:  Ubuntu 8.10, Release:   8.10
  Installed Package Version: 0.11.6svn20081008-0ubuntu4.2 (matches Latest 
Version in Synaptic)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/rhythmbox/+bug/303604/+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 938719] Re: some problem in updating ubuntu 10.04

2016-08-02 Thread Paul White
Thank you for taking the time to report this bug and helping to make
Ubuntu better. We are sorry that we do not always have the capacity to
look at all reported bugs in a timely manner. There have been many
changes in Ubuntu since that time you reported the bug and your problem
may have been fixed with some of the updates. It would help us a lot if
you could test it on a currently supported Ubuntu version.

When you test it and it is still an issue, kindly upload the updated
logs by running only once:

apport-collect 938719

and any other logs that are relevant for this particular issue.

** Changed in: tex-common (Ubuntu)
   Status: New => Incomplete

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

Title:
  some problem in updating ubuntu 10.04

Status in tex-common package in Ubuntu:
  Incomplete

Bug description:
  can't open the package

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/938719/+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 1195302] Re: package tex-common 3.15 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-02 Thread Paul White
*** This bug is a duplicate of bug 1241563 ***
https://bugs.launchpad.net/bugs/1241563

** This bug has been marked a duplicate of bug 1241563
   package tex-common 3.15 failed to install/upgrade: ErrorMessage: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  package tex-common 3.15 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  Confirmed

Bug description:
  This is my first time using launchpad.  I just checked
  answers.launchpad.net and didn't find anything. I'll review past
  reports and see if there's some info I can add to this report.

  Description:  Ubuntu 13.04
  Release:  13.04

  tex-common:
Installed: 3.15
Candidate: 3.15
Version table:
   *** 3.15 0
  500 http://us.archive.ubuntu.com/ubuntu/ raring/main i386 Packages
  500 http://ubuntu.mirror.cambrium.nl/ubuntu/ raring/main i386 Packages
  100 /var/lib/dpkg/status

  I expected no post-installation failure.

  There was a post-installation failure.

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: tex-common 3.15
  ProcVersionSignature: Ubuntu 3.8.0-25.37-generic 3.8.13
  Uname: Linux 3.8.0-25-generic i686
  ApportVersion: 2.9.2-0ubuntu8.1
  Architecture: i386
  Date: Thu Jun 27 08:37:01 2013
  DuplicateSignature: package:tex-common:3.15:subprocess installed 
post-installation script returned error exit status 1
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2012-04-16 (437 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 3.15 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to raring on 2013-04-29 (58 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1195302/+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 1176186] Re: package tex-common 3.15 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

2016-08-02 Thread Paul White
*** This bug is a duplicate of bug 1241563 ***
https://bugs.launchpad.net/bugs/1241563

** This bug has been marked a duplicate of bug 1241563
   package tex-common 3.15 failed to install/upgrade: ErrorMessage: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  package tex-common 3.15 failed to install/upgrade: le sous-processus
  script post-installation installé a retourné une erreur de sortie
  d'état 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Every time i try to install a package whatever it belongs to texlive or not. 
  I don't notice this message when installing tex-common but now i can't ignore 
the failure because each time i proceed an install of package, with python 
setup.py install or with synaptic or with aptitude, i've this error message.

  Thanks
  Fred

  ProblemType: Package
  DistroRelease: Ubuntu 13.04
  Package: tex-common 3.15
  ProcVersionSignature: Ubuntu 3.8.0-19.29-generic 3.8.8
  Uname: Linux 3.8.0-19-generic i686
  ApportVersion: 2.9.2-0ubuntu8
  AptOrdering:
   screen: Install
   tex-common: Configure
   screen: Configure
  Architecture: i386
  Date: Fri May  3 22:07:07 2013
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2013-04-27 (6 days ago)
  InstallationMedia: Lubuntu 13.04 "Raring Ringtail" - Release i386 (20130423.1)
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 3.15 failed to install/upgrade: le sous-processus 
script post-installation installé a retourné une erreur de sortie d'état 1
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1176186/+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 1397200] Re: package tex-common 5.02 failed to install/upgrade: le sous-processus script post-installation installé a retourné une erreur de sortie d'état 1

2016-08-02 Thread Paul White
*** This bug is a duplicate of bug 1385235 ***
https://bugs.launchpad.net/bugs/1385235

** This bug has been marked a duplicate of bug 1385235
   package tex-common 5.02 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück

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

Title:
  package tex-common 5.02 failed to install/upgrade: le sous-processus
  script post-installation installé a retourné une erreur de sortie
  d'état 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Same pb than bugs 710933, 774553, 1128301, 1176186, 1236951 but for
  version 5.02.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: tex-common 5.02
  ProcVersionSignature: Ubuntu 3.16.0-25.33-generic 3.16.7
  Uname: Linux 3.16.0-25-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Thu Nov 27 21:31:39 2014
  DuplicateSignature: package:tex-common:5.02:le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1
  ErrorMessage: le sous-processus script post-installation installé a retourné 
une erreur de sortie d'état 1
  InstallationDate: Installed on 2013-05-28 (548 days ago)
  InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 
(20120822.4)
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 5.02 failed to install/upgrade: le sous-processus 
script post-installation installé a retourné une erreur de sortie d'état 1
  UpgradeStatus: Upgraded to utopic on 2014-11-24 (3 days ago)
  modified.conffile..etc.texmf.texmf.d.00debian.cnf: [deleted]

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1397200/+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 1385235] Re: package tex-common 5.02 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück

2016-08-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: tex-common (Ubuntu)
   Status: New => Confirmed

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

Title:
  package tex-common 5.02 failed to install/upgrade: Unterprozess
  installiertes post-installation-Skript gab den Fehlerwert 1 zurück

Status in tex-common package in Ubuntu:
  Confirmed

Bug description:
  This happened during upgrade from 14.04 to 14.10.

  ProblemType: Package
  DistroRelease: Ubuntu 14.10
  Package: tex-common 5.02
  ProcVersionSignature: Ubuntu 3.16.0-23.31-generic 3.16.4
  Uname: Linux 3.16.0-23-generic x86_64
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: amd64
  Date: Fri Oct 24 13:31:04 2014
  DuplicateSignature: package:tex-common:5.02:Unterprozess installiertes 
post-installation-Skript gab den Fehlerwert 1 zurück
  ErrorMessage: Unterprozess installiertes post-installation-Skript gab den 
Fehlerwert 1 zurück
  InstallationDate: Installed on 2013-04-12 (559 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 5.02 failed to install/upgrade: Unterprozess 
installiertes post-installation-Skript gab den Fehlerwert 1 zurück
  UpgradeStatus: Upgraded to utopic on 2014-10-24 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1385235/+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 1270934] Re: package tex-common 3.15 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1

2016-08-02 Thread Paul White
*** This bug is a duplicate of bug 1241563 ***
https://bugs.launchpad.net/bugs/1241563

** This bug has been marked a duplicate of bug 1241563
   package tex-common 3.15 failed to install/upgrade: ErrorMessage: subprocess 
installed post-installation script returned error exit status 1

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

Title:
  package tex-common 3.15 failed to install/upgrade: ErrorMessage:
  subprocess installed post-installation script returned error exit
  status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Package failed to upgrade while upgrading from 13.04 to 13.10

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: tex-common 3.15
  ProcVersionSignature: Ubuntu 3.8.0-35.50-generic 3.8.13.13
  Uname: Linux 3.8.0-35-generic x86_64
  ApportVersion: 2.9.2-0ubuntu8.5
  Architecture: amd64
  Date: Mon Jan 20 12:54:03 2014
  DuplicateSignature: package:tex-common:3.15:ErrorMessage: subprocess 
installed post-installation script returned error exit status 1
  ErrorMessage: ErrorMessage: subprocess installed post-installation script 
returned error exit status 1
  MarkForUpload: True
  PackageArchitecture: all
  SourcePackage: tex-common
  Title: package tex-common 3.15 failed to install/upgrade: ErrorMessage: 
subprocess installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to saucy on 2014-01-20 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1270934/+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 1551003] Re: Xenial Files cannot browse network

2016-08-02 Thread Zero
Network browsing to the default workgroup named "WORKGROUP" is sluggish
but seems to work. Browsing to any other workgroup on the network is
definitely broken. Can only connect to those samba shares by specifying
the physical IP address of the remote machine. I hope this provides devs
a clue where to look.

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

Title:
  Xenial Files cannot browse network

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Xenial Files can't browse wired local network.

  In a different partition, same pc, 14.04.3 Files can Browse Network,
  both ubuntu and Windows pc's

  Xenial Nemo select "Network" can browse the network fine, display
  photos from Windows pc O.K.

  Xenial Files will not browse, just asks for  server address whatever
  that is and will not proceed.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: linux-image-4.4.0-8-generic 4.4.0-8.23
  ProcVersionSignature: Ubuntu 4.4.0-8.23-generic 4.4.2
  Uname: Linux 4.4.0-8-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Sun Feb 28 15:35:10 2016
  InstallationDate: Installed on 2016-01-31 (28 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160130)
  ProcEnviron:
   LANGUAGE=en_US
   TERM=xterm-256color
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-8-generic 
root=UUID=c38a379f-bb91-4c00-be51-7f4824e0aa0e ro quiet splash vt.handoff=7
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 01/10/2011
  dmi.bios.vendor: LENOVO
  dmi.bios.version: 5CKT69AUS
  dmi.board.name: LENOVO
  dmi.chassis.vendor: LENOVO
  dmi.chassis.version: NONE
  dmi.modalias: 
dmi:bvnLENOVO:bvr5CKT69AUS:bd01/10/2011:svnLENOVO:pn6234A1U:pvrThinkCentreM58p:rvnLENOVO:rnLENOVO:rvrNONE:cvnLENOVO:ct3:cvrNONE:
  dmi.product.name: 6234A1U
  dmi.product.version: ThinkCentre M58p
  dmi.sys.vendor: LENOVO

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1551003/+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 1605953] Re: skylake Modesetting Driver on X failure

2016-08-02 Thread Timo Aaltonen
then you need to tell more.. what video player, what settings etc... I
tried VLC and Totem, both worked fine on BDW at least

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

Title:
  skylake Modesetting Driver on X failure

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  with the change away from the intel driver to modeset I get a lot of
  tearing.

  This video shows the problem.

  https://goo.gl/photos/rXNBQ5KR6ZMnhazB9
  And the video capture is done in 240fps so its possible to see what is 
happening more clearly.

  The test video itself is just a short test video with alternating
  red/green pictures in 60Hz.

  What you should see is a somewhat flickering screen but the color
  should be a consistent orange hue.

  there should be no pulsing of colors that is more green then back to
  more red and so on then something is wrong.

  I have attached the video. if you are uncertain how it should look try to 
play it directly on a TV. that is with the TV own player not with a computer as 
that has a lot higher probability of not having any issues with vsync and frame 
updates.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   /dev/sda2: clean, 770076/2416640 files, 3881571/9647872 blocks
   (K(K
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2016-04-22 23:31:04,108 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7976]
   Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] 
[1002:7300] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon R9 FURY X [1043:04a0]
  InstallationDate: Installed on 2015-10-18 (281 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: MSI MS-7976
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7+ 
root=UUID=75bb5d92-206d-4bb8-a405-150b9b93d6d3 ro quiet splash vt.handoff=7
  Tags:  yakkety ubuntu regression reproducible compiz-0.9
  Uname: Linux 4.7.0-rc7+ x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-04-22 (94 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160714.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.69-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+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 1609009] [NEW] gnome-terminal should allow the disabling of text wrapping (so that there is a scroll bar at the bottom instead)

2016-08-02 Thread Nikita Yerenkov-Scott
Public bug reported:

I would find it rather useful, especially with certain types of outputs,
if gnome-terminal would allow me to disable text wrapping, that is so
that there would be a horizontal scroll bar that would allow me to see
the rest of the text.

I don't know if this should/would include the commands you type it, but
maybe there could be a separate option for the wrapping of that.

There are other Terminals which support this, and I think it would be
really nice if gnome-terminal would too so that one doesn't have to put
all of the output into another program like 'less' or similar in order
to disable the wrapping.

I am running Ubuntu GNOME 16.04 with GNOME 3.20 and would find this a
very useful feature.

** Affects: gnome-terminal
 Importance: Unknown
 Status: Unknown

** Affects: ubuntu-gnome
 Importance: Undecided
 Status: New

** Affects: gnome-terminal (Ubuntu)
 Importance: Undecided
 Status: New

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

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

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

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

Title:
  gnome-terminal should allow the disabling of text wrapping (so that
  there is a scroll bar at the bottom instead)

Status in GNOME Terminal:
  Unknown
Status in Ubuntu GNOME:
  New
Status in gnome-terminal package in Ubuntu:
  New

Bug description:
  I would find it rather useful, especially with certain types of
  outputs, if gnome-terminal would allow me to disable text wrapping,
  that is so that there would be a horizontal scroll bar that would
  allow me to see the rest of the text.

  I don't know if this should/would include the commands you type it,
  but maybe there could be a separate option for the wrapping of that.

  There are other Terminals which support this, and I think it would be
  really nice if gnome-terminal would too so that one doesn't have to
  put all of the output into another program like 'less' or similar in
  order to disable the wrapping.

  I am running Ubuntu GNOME 16.04 with GNOME 3.20 and would find this a
  very useful feature.

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-terminal/+bug/1609009/+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 1608637] Re: firefox

2016-08-02 Thread Paul White
Thank you for taking the time to report your problem and helping to make
Ubuntu better. Unfortunately, we cannot work on this issue because your
description didn't include enough information. You may find it helpful
to read "How to report bugs effectively"
http://www.chiark.greenend.org.uk/~sgtatham/bugs.html.

We'd be grateful if you would then provide a more complete description
of the problem.

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

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

Please also change the title of the bug to something more meaningful.

Thanks!

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

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

Title:
  firefox

Status in firefox package in Ubuntu:
  Incomplete

Bug description:
  the firefox-browser is stupid?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: firefox 47.0+build3-0ubuntu0.16.04.1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  AddonCompatCheckDisabled: False
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  marko  3136 F pulseaudio
  BuildID: 20160606113944
  Channel: Unavailable
  CurrentDesktop: XFCE
  Date: Mon Aug  1 20:04:16 2016
  Extensions: extensions.sqlite corrupt or missing
  ForcedLayersAccel: False
  IfupdownConfig:
   # interfaces(5) file used by ifup(8) and ifdown(8)
   auto lo
   iface lo inet loopback
  IncompatibleExtensions: Unavailable (corrupt or non-existant 
compatibility.ini or extensions.sqlite)
  InstallationDate: Installed on 2016-08-01 (0 days ago)
  InstallationMedia: Xubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  IpRoute:
   default via 192.168.0.1 dev wlp2s0  proto static  metric 600 
   169.254.0.0/16 dev wlp2s0  scope link  metric 1000 
   192.168.0.0/24 dev wlp2s0  proto kernel  scope link  src 192.168.0.24  
metric 600
  Locales: extensions.sqlite corrupt or missing
  Plugins: Shockwave Flash - /usr/lib/flashplugin-installer/libflashplayer.so
  PrefSources: prefs.js
  ProcEnviron:
   LANGUAGE=de_DE
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/bash
  Profiles: Profile0 (Default) - LastVersion=47.0/20160606113944 (In use)
  RunningIncompatibleAddons: False
  SourcePackage: firefox
  Themes: extensions.sqlite corrupt or missing
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 08/28/2012
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: R0180V5
  dmi.board.asset.tag: N/A
  dmi.board.name: VAIO
  dmi.board.vendor: Sony Corporation
  dmi.board.version: N/A
  dmi.chassis.asset.tag: N/A
  dmi.chassis.type: 10
  dmi.chassis.vendor: Sony Corporation
  dmi.chassis.version: N/A
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvrR0180V5:bd08/28/2012:svnSonyCorporation:pnSVE14A2M1EP:pvrC60BE3KY:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
  dmi.product.name: SVE14A2M1EP
  dmi.product.version: C60BE3KY
  dmi.sys.vendor: Sony Corporation

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/1608637/+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 1573823] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-02 Thread Paul White
*** This bug is a duplicate of bug 1583906 ***
https://bugs.launchpad.net/bugs/1583906

** This bug has been marked a duplicate of bug 1583906
   package tex-common 6.04 failed to install/upgrade: le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  Happened when purging the tex-gyre (20150923-1) package.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  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
  AptOrdering:
   tex-gyre: Purge
   fonts-texgyre: Install
   fonts-texgyre: Configure
   NULL: ConfigurePending
  Architecture: amd64
  Date: Fri Apr 22 23:08:52 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-04-10 (378 days ago)
  InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 
(20150218.1)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1
   apt  1.2.10ubuntu1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-04-22 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1573823/+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 1606743] Re: Font Viewer desktop file does not launch gnome-font-viewer

2016-08-02 Thread Dimitris Saltos
*** This bug is a duplicate of bug 1607937 ***
https://bugs.launchpad.net/bugs/1607937

Found a temp solution on this...
sudo nano /usr/share/applications/org.gnome.font-viewer.desktop

Change...
DBusActivatable=true
StartupNotify=true
to...
DBusActivatable=false
StartupNotify=false

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

Title:
  Font Viewer desktop file does not launch gnome-font-viewer

Status in gnome-font-viewer package in Ubuntu:
  Confirmed

Bug description:
  Ubuntu 16.04.1
  gnome-font-viewer 3.16.2

  What I expect: When I double-click the Font Viewer icon from the Dash
  Applications scope it should launch the Font Viewer.

  What actually happens: It does not. I get the waiting cursor and the
  Font Viewer tile on the launcher for a few seconds and then the tile
  disappears.

  I can go to a terminal and type "gnome-font-viewer" and it runs
  without any issues.

  Here is the content of the desktop file:

  [Desktop Entry]
  Name=Font Viewer
  Comment=View fonts on your system
  Keywords=fonts;fontface;
  Icon=preferences-desktop-font
  Exec=gnome-font-viewer %u
  Terminal=false
  Type=Application
  DBusActivatable=true
  StartupNotify=true
  Categories=GTK;GNOME;Utility;X-GNOME-Utilities;
  
MimeType=application/x-font-ttf;application/x-font-pcf;application/x-font-type1;application/x-font-otf;
  X-GNOME-Bugzilla-Bugzilla=GNOME
  X-GNOME-Bugzilla-Product=gnome-font-viewer
  X-GNOME-Bugzilla-Component=general
  X-GNOME-Bugzilla-OtherBinaries=gnome-thumbnail-font
  X-GNOME-Bugzilla-Version=3.16.2
  X-Ubuntu-Gettext-Domain=gnome-font-viewer

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-font-viewer/+bug/1606743/+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 1005914] Re: gnome-screenshot produces black screenshot with only the mouse pointer visible

2016-08-02 Thread Dr. Gianluigi "Zane" Zanettini
This is to confirm that the issue is still present with Ubuntu 16.04 as
guest inside VirtualBox 5.0.14.

Disabling 3D acceleration from the VM settings is still an effective
workaround.

** Changed in: gnome-screenshot (Ubuntu)
   Status: Invalid => 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/1005914

Title:
  gnome-screenshot produces black screenshot with only the mouse pointer
  visible

Status in compiz package in Ubuntu:
  Invalid
Status in gnome-screenshot package in Ubuntu:
  New
Status in recordmydesktop package in Ubuntu:
  Confirmed
Status in virtualbox package in Ubuntu:
  Invalid

Bug description:
  I am running Ubuntu 12.04 inside Virtualbox on a Windows host.
  3D acceleration is enabled in Virtualbox and I am using compiz + unity, NOT 
unity2d.

  gnome-screenshot produces black screenshot with only the mouse pointer 
visible.
  it does not matter if I run it by pressing the PrintScreen key or running
  gnome-screenshot -d 5
  in a terminal.

  WORKAROUND:
  use unity2d instead of compiz+unity 

  ProblemType: Bug
  DistroRelease: Ubuntu 12.04
  Package: gnome-screenshot 3.4.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.2.0-24.39-generic 3.2.16
  Uname: Linux 3.2.0-24-generic x86_64
  ApportVersion: 2.0.1-0ubuntu7
  Architecture: amd64
  Date: Tue May 29 15:59:15 2012
  InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 
(2029.1)
  SourcePackage: gnome-screenshot
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/1005914/+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 1608756] Re: package tex-common 6.04 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1

2016-08-02 Thread Paul White
*** This bug is a duplicate of bug 1583906 ***
https://bugs.launchpad.net/bugs/1583906

** This bug has been marked a duplicate of bug 1583906
   package tex-common 6.04 failed to install/upgrade: le sous-processus script 
post-installation installé a retourné une erreur de sortie d'état 1

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

Title:
  package tex-common 6.04 failed to install/upgrade: subprocess
  installed post-installation script returned error exit status 1

Status in tex-common package in Ubuntu:
  New

Bug description:
  tex-common not being able to be downloaded and installed.

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: tex-common 6.04
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  Date: Mon Aug  1 21:24:30 2016
  ErrorMessage: subprocess installed post-installation script returned error 
exit status 1
  InstallationDate: Installed on 2015-07-12 (386 days ago)
  InstallationMedia: Ubuntu 12.04.2 LTS "Precise Pangolin" - Release amd64 
(20130213)
  PackageArchitecture: all
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: tex-common
  Title: package tex-common 6.04 failed to install/upgrade: subprocess 
installed post-installation script returned error exit status 1
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/tex-common/+bug/1608756/+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 1605953] Re: skylake Modesetting Driver on X failure

2016-08-02 Thread kenjo
yes it's the modsetting module that has the problem. should have
mentioned that the log was from after I changed back to old drive.

So the issue is when I run without any xorg.conf file and get the
default. when I create a xorg.conf and load the intel driver it works.
well I have other issues but this particular one is not present.

But this is so bad it basically is unusable.

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

Title:
  skylake Modesetting Driver on X failure

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  with the change away from the intel driver to modeset I get a lot of
  tearing.

  This video shows the problem.

  https://goo.gl/photos/rXNBQ5KR6ZMnhazB9
  And the video capture is done in 240fps so its possible to see what is 
happening more clearly.

  The test video itself is just a short test video with alternating
  red/green pictures in 60Hz.

  What you should see is a somewhat flickering screen but the color
  should be a consistent orange hue.

  there should be no pulsing of colors that is more green then back to
  more red and so on then something is wrong.

  I have attached the video. if you are uncertain how it should look try to 
play it directly on a TV. that is with the TV own player not with a computer as 
that has a lot higher probability of not having any issues with vsync and frame 
updates.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   /dev/sda2: clean, 770076/2416640 files, 3881571/9647872 blocks
   (K(K
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2016-04-22 23:31:04,108 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7976]
   Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] 
[1002:7300] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon R9 FURY X [1043:04a0]
  InstallationDate: Installed on 2015-10-18 (281 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: MSI MS-7976
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7+ 
root=UUID=75bb5d92-206d-4bb8-a405-150b9b93d6d3 ro quiet splash vt.handoff=7
  Tags:  yakkety ubuntu regression reproducible compiz-0.9
  Uname: Linux 4.7.0-rc7+ x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-04-22 (94 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160714.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.69-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+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

2016-08-02 Thread Jeff
Could someone on the ubuntu development team update the bluez package to
5.39?  The bluez website states there are A2DP fixes in the next
release.

http://www.bluez.org/release-of-bluez-5-39/

-- 
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 1572855] Re: libgbm.so.1: cannot open shared object file

2016-08-02 Thread Gaurav Sharma
I have successfully executed the 3 comments mentioned in #4 or #15.
But during re-installation I got below errors:

dpkg: error processing archive 
/var/cache/apt/archives/libgbm1_10.1.3-0ubuntu0.6_amd64.deb (--unpack):
 trying to overwrite '/usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0', which is also 
in package libgbm1-lts-wily:amd64 11.0.2-1ubuntu4~trusty1
Errors were encountered while processing:
 /var/cache/apt/archives/libgbm1_10.1.3-0ubuntu0.6_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)


** Attachment added: "The attachment shows actual errors"
   
https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1572855/+attachment/4712399/+files/Errors.png

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

Title:
  libgbm.so.1: cannot open shared object file

Status in xorg-lts-transitional package in Ubuntu:
  Fix Released

Bug description:
  After upgrading from 14.04 -> 16.04, there are still some dpkg-diverts
  left in place. This stops gdm/gnome-shell from booting up at all.

  Apr 20 23:22:12 ubuntu gnome-session[1018]: gnome-shell: error while loading 
shared libraries: libgbm.so.1: cannot open shared object file: No such file or 
directory
  Apr 20 23:22:12 ubuntu gnome-session[1018]: gnome-session-binary[1018]: 
WARNING: App 'gnome-shell-wayland.desktop' exited with code 127
  Apr 20 23:22:12 ubuntu gnome-session-binary[1018]: WARNING: App 
'gnome-shell-wayland.desktop' exited with code 127
  Apr 20 23:22:13 ubuntu gnome-session[1213]: gnome-shell: error while loading 
shared libraries: libgbm.so.1: cannot open shared 

  $dpkg -L libgbm1
  /usr
  /usr/lib
  /usr/lib/x86_64-linux-gnu
  /usr/lib/x86_64-linux-gnu/libgbm.so.1.0.0
  diverted by libgbm1-lts-wily to: /usr/lib/x86_64-linux-gnu/old.libgbm.so.1.0.0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1572855/+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 1608891] Re: Extra Information Display Incorrectly

2016-08-02 Thread Sebastien Bacher
** Changed in: gnome-system-monitor (Ubuntu)
   Importance: Undecided => Low

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

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

Title:
  Extra Information Display Incorrectly

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

Bug description:
  When I moved my mouse on Process "chrome -type=gpu-broker",the monitor showed 
nothing but a black empty box. However,when I moved my mouse to other 
processes, the monitor showed the correct process command with arguments (like 
it will show "/sbin/init splash" when I moved the mouse on the process 
"systemd")
  (sorry for my poor English

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-system-monitor 3.18.2-1
  ProcVersionSignature: Ubuntu 4.4.0-31.50-generic 4.4.13
  Uname: Linux 4.4.0-31-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2.1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  2 18:30:27 2016
  EcryptfsInUse: Yes
  ExecutablePath: /usr/bin/gnome-system-monitor
  InstallationDate: Installed on 2016-05-08 (86 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  ProcEnviron:
   PATH=(custom, no user)
   SHELL=/bin/bash
   LANG=zh_CN.UTF-8
   LANGUAGE=zh_CN:zh
   XDG_RUNTIME_DIR=
  SourcePackage: gnome-system-monitor
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1608891/+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 875676] Re: Backing up fails with 'IOError CRC check failed'.

2016-08-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: deja-dup (Ubuntu)
   Status: New => Confirmed

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

Title:
  Backing up fails with 'IOError CRC check failed'.

Status in Déjà Dup:
  New
Status in Duplicity:
  New
Status in deja-dup package in Ubuntu:
  Confirmed

Bug description:
  For 4 days déjà dup hasn't been able to perform a backup. It fails
  with the error

  Failed to read /tmp/duplicity-lJcUDl-tempdir/mktemp-o4LYSJ-1: (, IOError('CRC check failed 0x8434f7d2L !=
  0x3d503338L',), )

  There is another similar bug #676767 where deleting ~/.cache/deja-dup
  helps. In this case it doesn't.

  I'm quite certain that my backup drive isn't corrupted. (It's a
  raid5.) I'd be happy to provide any additional information needed.

  --

  System information:
  Ubuntu 11.10
  deja-dup 20.0-0ubuntu3
  duplicity 0.6.15-0ubuntu2

  Logs:
  deja-dup.log: http://pastie.org/2705320
  deja-dup.gsettings: http://pastie.org/2705322

To manage notifications about this bug go to:
https://bugs.launchpad.net/deja-dup/+bug/875676/+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 1608535] Re: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: triggers looping, abandoned

2016-08-02 Thread Sujan Gangadhar
** Description changed:

  This error occured when I tried to upgrade my Ubuntu from version 14.04
  to version 16.04
  
  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1
  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.1
  Architecture: amd64
  Date: Mon Aug  1 12:17:13 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-10-07 (299 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
-  dpkg 1.18.4ubuntu1.1
-  apt  1.2.12~ubuntu16.04.1
+  dpkg 1.18.4ubuntu1.1
+  apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (0 days ago)

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

Title:
  package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade:
  triggers looping, abandoned

Status in fontconfig package in Ubuntu:
  Confirmed

Bug description:
  This error occured when I tried to upgrade my Ubuntu from version
  14.04 to version 16.04

  ProblemType: Package
  DistroRelease: Ubuntu 16.04
  Package: fontconfig 2.11.94-0ubuntu1
  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.1
  Architecture: amd64
  Date: Mon Aug  1 12:17:13 2016
  ErrorMessage: triggers looping, abandoned
  InstallationDate: Installed on 2015-10-07 (299 days ago)
  InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805)
  RelatedPackageVersions:
   dpkg 1.18.4ubuntu1.1
   apt  1.2.12~ubuntu16.04.1
  SourcePackage: fontconfig
  Title: package fontconfig 2.11.94-0ubuntu1 failed to install/upgrade: 
triggers looping, abandoned
  UpgradeStatus: Upgraded to xenial on 2016-08-01 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/1608535/+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 1608954] Re: Performance degradation caused by libica2 library

2016-08-02 Thread Gary Gaydos
** Package changed: libical (Ubuntu) => libica (Ubuntu)

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

Title:
  Performance degradation caused by libica2 library

Status in libica package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Bastian Pfeifer  - 2016-07-29 
09:07:47 ==
  ---Problem Description---
  'Libica' library versions >= 2.6.0 implement a new DRBG (Deterministic Random 
Number Generator) with a unnecessary stiff reseed limit leading to performance 
degradation (factor >20) for RSA encryption via opencryptoki.  
   
  A patch is already upstream and can be found under this commit:
  
https://sourceforge.net/p/opencryptoki/libica/ci/3bcd3efb0aff364515ab9b3c39dd68fbbb1534d0/

  It will fix the issue + we will get a great performance improvement
  for the RSA encryption via opencryptoki's ICA-TOKEN.

  Contact Information = bastian.pfei...@de.ibm.com 
   
  ---uname output---
  Linux s42lp26 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:14:29 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = 2964, 701 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   na
   
  Userspace tool common name: libica version 2.6.1 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: libica2:s390x

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for bastian.pfei...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #2 - Ingo Tuchscherer  -
  2016-08-01 06:53:45 ==

  
  == Comment: #3 - Heinz-Werner Seeck  - 
2016-08-02 08:19:23 ==
  'Libica' library versions >= 2.6.0 implement a new DRBG (Deterministic Random 
Number Generator) with a unnecessary stiff reseed limit leading to performance 
degradation (factor >20) for RSA encryption via opencryptoki.  
   
  A patch is already upstream and can be found under this commit:
  
https://sourceforge.net/p/opencryptoki/libica/ci/3bcd3efb0aff364515ab9b3c39dd68fbbb1534d0/

  Also attached to this bugzilla !

  It will fix the issue + we will get a great performance improvement
  for the RSA encryption via opencryptoki's ICA-TOKEN.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libica/+bug/1608954/+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 1608954] libica RNG performance fix

2016-08-02 Thread bugproxy
Default Comment by Bridge

** Attachment added: "libica RNG performance fix"
   
https://bugs.launchpad.net/bugs/1608954/+attachment/4712375/+files/ica_random_number_generate_performance.patch

** Changed in: ubuntu
 Assignee: (unassigned) => Skipper Bug Screeners (skipper-screen-team)

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

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

Title:
  Performance degradation caused by libica2 library

Status in libica package in Ubuntu:
  New

Bug description:
  == Comment: #0 - Bastian Pfeifer  - 2016-07-29 
09:07:47 ==
  ---Problem Description---
  'Libica' library versions >= 2.6.0 implement a new DRBG (Deterministic Random 
Number Generator) with a unnecessary stiff reseed limit leading to performance 
degradation (factor >20) for RSA encryption via opencryptoki.  
   
  A patch is already upstream and can be found under this commit:
  
https://sourceforge.net/p/opencryptoki/libica/ci/3bcd3efb0aff364515ab9b3c39dd68fbbb1534d0/

  It will fix the issue + we will get a great performance improvement
  for the RSA encryption via opencryptoki's ICA-TOKEN.

  Contact Information = bastian.pfei...@de.ibm.com 
   
  ---uname output---
  Linux s42lp26 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:14:29 UTC 2016 
s390x s390x s390x GNU/Linux
   
  Machine Type = 2964, 701 
   
  ---Debugger---
  A debugger is not configured
   
  ---Steps to Reproduce---
   na
   
  Userspace tool common name: libica version 2.6.1 
   
  The userspace tool has the following bit modes: 64-bit 

  Userspace rpm: libica2:s390x

  Userspace tool obtained from project website:  na 
   
  *Additional Instructions for bastian.pfei...@de.ibm.com:
  -Attach ltrace and strace of userspace application.

  == Comment: #2 - Ingo Tuchscherer  -
  2016-08-01 06:53:45 ==

  
  == Comment: #3 - Heinz-Werner Seeck  - 
2016-08-02 08:19:23 ==
  'Libica' library versions >= 2.6.0 implement a new DRBG (Deterministic Random 
Number Generator) with a unnecessary stiff reseed limit leading to performance 
degradation (factor >20) for RSA encryption via opencryptoki.  
   
  A patch is already upstream and can be found under this commit:
  
https://sourceforge.net/p/opencryptoki/libica/ci/3bcd3efb0aff364515ab9b3c39dd68fbbb1534d0/

  Also attached to this bugzilla !

  It will fix the issue + we will get a great performance improvement
  for the RSA encryption via opencryptoki's ICA-TOKEN.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libica/+bug/1608954/+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 1608954] [NEW] Performance degradation caused by libica2 library

2016-08-02 Thread Launchpad Bug Tracker
You have been subscribed to a public bug:

== Comment: #0 - Bastian Pfeifer  - 2016-07-29 
09:07:47 ==
---Problem Description---
'Libica' library versions >= 2.6.0 implement a new DRBG (Deterministic Random 
Number Generator) with a unnecessary stiff reseed limit leading to performance 
degradation (factor >20) for RSA encryption via opencryptoki.  
 
A patch is already upstream and can be found under this commit:
https://sourceforge.net/p/opencryptoki/libica/ci/3bcd3efb0aff364515ab9b3c39dd68fbbb1534d0/

It will fix the issue + we will get a great performance improvement for
the RSA encryption via opencryptoki's ICA-TOKEN.

Contact Information = bastian.pfei...@de.ibm.com 
 
---uname output---
Linux s42lp26 4.4.0-28-generic #47-Ubuntu SMP Fri Jun 24 10:14:29 UTC 2016 
s390x s390x s390x GNU/Linux
 
Machine Type = 2964, 701 
 
---Debugger---
A debugger is not configured
 
---Steps to Reproduce---
 na
 
Userspace tool common name: libica version 2.6.1 
 
The userspace tool has the following bit modes: 64-bit 

Userspace rpm: libica2:s390x

Userspace tool obtained from project website:  na 
 
*Additional Instructions for bastian.pfei...@de.ibm.com:
-Attach ltrace and strace of userspace application.

== Comment: #2 - Ingo Tuchscherer  -
2016-08-01 06:53:45 ==


== Comment: #3 - Heinz-Werner Seeck  - 
2016-08-02 08:19:23 ==
'Libica' library versions >= 2.6.0 implement a new DRBG (Deterministic Random 
Number Generator) with a unnecessary stiff reseed limit leading to performance 
degradation (factor >20) for RSA encryption via opencryptoki.  
 
A patch is already upstream and can be found under this commit:
https://sourceforge.net/p/opencryptoki/libica/ci/3bcd3efb0aff364515ab9b3c39dd68fbbb1534d0/

Also attached to this bugzilla !

It will fix the issue + we will get a great performance improvement for
the RSA encryption via opencryptoki's ICA-TOKEN.

** Affects: libical (Ubuntu)
 Importance: Undecided
 Assignee: Skipper Bug Screeners (skipper-screen-team)
 Status: New


** Tags: architecture-s39064 bugnameltc-144304 severity-high 
targetmilestone-inin16041
-- 
Performance degradation caused by libica2 library
https://bugs.launchpad.net/bugs/1608954
You received this bug notification because you are a member of Desktop 
Packages, which is subscribed to libical 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 1607799] Re: Dash freezes after U1 login

2016-08-02 Thread Launchpad Bug Tracker
** Branch linked: lp:~ci-train-bot/libsignon-glib/libsignon-glib-ubuntu-
yakkety-landing-005

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

Title:
  Dash freezes after U1 login

Status in Canonical System Image:
  Confirmed
Status in libsignon-glib package in Ubuntu:
  In Progress
Status in unity-scopes-api package in Ubuntu:
  Incomplete
Status in unity-scopes-shell package in Ubuntu:
  Incomplete
Status in unity8 package in Ubuntu:
  Incomplete

Bug description:
  Test case.
  - Without U1 account, go to Ubuntu Store.
  - Tap on an app.
  - Tap on the install button.
  - Introduce credentials.

  Expected result.
  - After credentials, the app is installed.

  Actual result.
  - Dash is frozen. Cannot go back to the scopes. Launcher and indicators do 
work, though. There is no crash.

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607799/+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


Re: [Desktop-packages] [Bug 1577074] Re: AMDGPU driver problems on "Carrizo" APU

2016-08-02 Thread jakedp
Here is my lshw output:

description: Notebook
   product: HP Pavilion Notebook (N5R36UA#ABL)
   vendor: HP
   version: Chassis Version
   serial: 5CD6044W0B
   width: 64 bits
   capabilities: smbios-2.8 dmi-2.8 vsyscall32
   configuration: boot=normal chassis=notebook family=103C_5335KV G=N L=CON
B=HP S=PAV sku=N5R36UA#ABL uuid=35434436-3034-3457-3042-DC
4A3EF51D71
 *-core
  description: Motherboard
  product: 80AF
  vendor: HP
  physical id: 0
  version: 81.29
  serial: PFDTU018J103IL
  slot: Base Board Chassis Location
*-firmware
 description: BIOS
 vendor: American Megatrends Inc.
 physical id: 0
 version: F.16
 date: 11/27/2015
 size: 64KiB
 capacity: 8128KiB
 capabilities: pci upgrade shadowing cdboot bootselect edd
int13floppy1200 int13floppy720 int13floppy2880 int5printscreen int9
keyboard int14serial int17printer acpi usb smartbattery
biosbootspecification netboot uefi
*-cache:0
 description: L1 cache
 physical id: d
 slot: L1 CACHE
 size: 320KiB
 capacity: 320KiB
 clock: 1GHz (1.0ns)
 capabilities: pipeline-burst internal write-back unified
 configuration: level=1
*-cache:1
 description: L2 cache
 physical id: e
 slot: L2 CACHE
 size: 2MiB
 capacity: 2MiB
 clock: 1GHz (1.0ns)
 capabilities: pipeline-burst internal write-back unified
 configuration: level=2
*-memory
 description: System Memory
 physical id: 16
 slot: System board or motherboard
 size: 8GiB
   *-bank:0
description: SODIMM DDR3 Synchronous 1600 MHz (0.6 ns)
product: M471B1G73DB0-YK0
vendor: Samsung
physical id: 0
serial: 14BE9E85
slot: Bottom-Slot 1 (left)
size: 8GiB
width: 64 bits
clock: 1600MHz (0.6ns)
   *-bank:1
description: DDR3 [empty]
product: A1_PartNum1
vendor: A1_Manufacturer1
physical id: 1
serial: A1_SerialNum1
slot: Bottom-Slot 2 (right)
width: 64 bits
*-cpu
 description: CPU
 product: AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G
 vendor: Advanced Micro Devices [AMD]
 physical id: 20
 bus info: cpu@0
 version: AMD A10-8700P Radeon R6, 10 Compute Cores 4C+6G
 slot: P0
 size: 1600MHz
 capacity: 1800MHz
 width: 64 bits
 clock: 100MHz
 capabilities: x86-64 fpu fpu_exception wp vme de pse tsc msr pae
mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxs
r sse sse2 ht syscall nx mmxext fxsr_opt pdpe1gb rdtscp constant_tsc
rep_good nopl nonstop_tsc extd_apicid aperfmperf eagerfpu pni pclm
ulqdq monitor ssse3 fma cx16 sse4_1 sse4_2 movbe popcnt aes xsave avx f16c
lahf_lm cmp_legacy svm extapic cr8_legacy abm sse4a misalign
sse 3dnowprefetch osvw ibs xop skinit wdt lwp fma4 tce nodeid_msr tbm
topoext perfctr_core perfctr_nb bpext mwaitx cpb hw_pstate vmmcal
l fsgsbase bmi1 avx2 smep bmi2 xsaveopt arat npt lbrv svm_lock nrip_save
tsc_scale vmcb_clean flushbyasid decodeassists pausefilter pft
hreshold cpufreq
 configuration: cores=4 enabledcores=4 threads=4
*-pci:0
 description: Host bridge
 product: Advanced Micro Devices, Inc. [AMD]
 vendor: Advanced Micro Devices, Inc. [AMD]
 physical id: 100
 bus info: pci@:00:00.0
 version: 00
 width: 32 bits
 clock: 33MHz
   *-generic:0 UNCLAIMED
description: IOMMU
product: Advanced Micro Devices, Inc. [AMD]
vendor: Advanced Micro Devices, Inc. [AMD]
physical id: 0.2
bus info: pci@:00:00.2
version: 00
width: 32 bits
clock: 33MHz
capabilities: msi ht cap_list
configuration: latency=0
   *-display
description: VGA compatible controller
product: Carrizo
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 1
bus info: pci@:00:01.0
version: c5
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi vga_controller bus_master
cap_list rom
configuration: driver=amdgpu latency=0
resources: irq:47 memory:e000-efff
memory:f000-f07f ioport:f000(size=256) memory:ff70-ff73
memory:
ff74-ff75
   *-multimedia:0
description: Audio device
product: Kabini HDMI/DP Audio
vendor: Advanced Micro Devices, Inc. [AMD/ATI]
physical id: 1.1
bus info: pci@:00:01.1
version: 00
width: 64 bits
clock: 33MHz
capabilities: pm pciexpress msi bus_master cap_list
  

Re: [Desktop-packages] [Bug 1577074] Re: AMDGPU driver problems on "Carrizo" APU

2016-08-02 Thread jakedp
With Linux Mint 18 and KDE Neon the bug changes from random to boot up. It
happens the first time from a cold boot. After a restart, which means
screwing up my hard drive and holding the power button. Then turning it on
and the black screen comes back.

I' am very fustrated like Brian. Canonical doesn' t need AMD to repackage
the driver for the new X Server. Abandoned by AMD and the commercial
distros. Do not advocate AMD, they must have known this problem and ignored
it.

On Sun, Jul 24, 2016 at 5:53 PM, Brian  wrote:

> OK, I tried the "amdgpu.runpm=0" solution with the Ubuntu 16.04 LiveUSB
> and while it booted in high graphics mode, I still got the black screen
> after a few minutes.
>
> Christopher, I have done as you asked in Comment #15 on this thread, and
> the bug report I filed is at
> https://bugs.launchpad.net/ubuntu/+source/xorg/+filebug/34a9fa5a-
> 51e8-11e6-8b1c-68b5996a96c8?
>
> However I don't know how this will do any good, as I'm running Ubuntu
> 15.10, not 16.04 where the problem occurs. I wish AMD or Canonical or
> whoever is responsible for the decision to make fglrx unavailable in
> 16.04 would reconsider and provide for a smoother transition by allowing
> users with graphics cards that are still unsupported by amdgpu to "opt-
> in" to fglrx until AMD works out the all the kinks. It's as if they just
> don't care about end users whatsoever. Man, am I frustrated!
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1577074
>
> Title:
>   AMDGPU driver problems on "Carrizo" APU
>
> Status in xorg package in Ubuntu:
>   Incomplete
>
> Bug description:
>   I'm having a hard time tracing this down.  I updated to Kubuntu 16.04
>   (from Kubuntu 15.10 - that was using the Linux Crimson 15.12 driver) a
>   couple days ago on my notebook (HP Pavilion, A10-8700P APU), and ever
>   since I've been having random black screens.
>
>   I started debugging the driver, then thought it might be a DPMS issue
>   (it's not - I have DPMS fully disabled currently), and now I'm back to
>   debugging the driver.
>
>   I don't have any remnants of the former closed Crimson display driver
>   and never had an xorg.conf file (I made a small one that I'm using at
>   the moment consisting of only a server layout to ensure screen savers,
>   DPMS, etc are all off).
>
>   The Black screen can happen any time from the login screen until hours
>   later.  I can ssh into the system to shut it down.  And just
>   discovered that if I unplug the system from it's power brick, I can
>   close the lid - the system will goto sleep.  When I flip the screen
>   back up, the system wakes up and the screen works again for 1-2
>   minutes.
>
>   I don't see any errors in the log files (well, outside some nasty
>   looking ACAPI errors in dmesg).
>
>   HOT TO REPRODUCE:
>   Boot system and use normally or simply leave system alone.  Blank screen
> will happen any time after x comes up.
>
>
>   EXPECTED RESULT:
>   Screen doesn't blank unless a screen saver or power saver kicks in.
>
>   SYSTEM INFO:
>   Purchased Dec 2015 (build date from BIOS - Aug 2015), HP Pavilion 15"
> notebook, AMD A10-8700P "Carrizo", 16GB RAM, 960GB SSD
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1577074/+subscriptions
>

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

Title:
  AMDGPU driver problems on "Carrizo" APU

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I'm having a hard time tracing this down.  I updated to Kubuntu 16.04
  (from Kubuntu 15.10 - that was using the Linux Crimson 15.12 driver) a
  couple days ago on my notebook (HP Pavilion, A10-8700P APU), and ever
  since I've been having random black screens.

  I started debugging the driver, then thought it might be a DPMS issue
  (it's not - I have DPMS fully disabled currently), and now I'm back to
  debugging the driver.

  I don't have any remnants of the former closed Crimson display driver
  and never had an xorg.conf file (I made a small one that I'm using at
  the moment consisting of only a server layout to ensure screen savers,
  DPMS, etc are all off).

  The Black screen can happen any time from the login screen until hours
  later.  I can ssh into the system to shut it down.  And just
  discovered that if I unplug the system from it's power brick, I can
  close the lid - the system will goto sleep.  When I flip the screen
  back up, the system wakes up and the screen works again for 1-2
  minutes.

  I don't see any errors in the log files (well, outside some nasty
  looking ACAPI errors in dmesg).

  HOT TO REPRODUCE:
  Boot system and use normally or simply leave system alone.  Blank screen will 
happen any time after x comes up.

  
  EXPECTED RESULT:
  Screen doesn't blank unless a 

[Desktop-packages] [Bug 1579531] Re: openConnection: connect: No such file or directory

2016-08-02 Thread dino99
This error is polluting .xsession-errors on yakkety too.

openConnection: connect: No such file or directory
cannot connect to brltty at :0

Glancing at such error , i've found that answer from a Debian dev:

> openConnection: connect: No such file or directory
> cannot connect to brltty at :0

That's no error, they're just debugging messages. They come from xbrlapi which
is trying to connect to a braille display but you have none so it can't. Nothing
to worry about.
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=728947

So what is only needed is to silence this debugging message from xbrlapi.
This may affect most of the users, as they does not have use of braille.

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

** Tags added: yakkety

** Summary changed:

- openConnection: connect: No such file or directory
+ xbrlapi debugging message spamming .xsession-errors; please silence it.

** Tags added: xenial

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

Title:
  xbrlapi debugging message spamming .xsession-errors; please silence
  it.

Status in brltty package in Ubuntu:
  Confirmed

Bug description:
  16.04 amd64.

  $HOME/.xsession-errors contains cryptic messages that do not indicate
  where they come from. They turn out to be harmless but it would be
  good if they at least were prefixed with the source.

  openConnection: connect: No such file or directory
  cannot connect to brltty at :0

  They indicate the absence of a braille tty so how about:

  xbrlapi: Cannot find a Braille Teletype device
  xbrlapi: cannot connect to brltty at :0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1579531/+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 1605797] Re: [ICH - Intel 82801AA-ICH, playback] No sound at all

2016-08-02 Thread Launchpad Bug Tracker
Status changed to 'Confirmed' because the bug affects multiple users.

** Changed in: alsa-driver (Ubuntu)
   Status: New => Confirmed

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

Title:
  [ICH - Intel 82801AA-ICH, playback] No sound at all

Status in ALSA driver:
  New
Status in alsa-driver package in Ubuntu:
  Confirmed

Bug description:
  New ubuntu install on 2016-07-22; latest version.
  Running as virtualbox guest on latest OS X.
  Sound card recognized on mac, but not on guest.
  No sound in or out.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: alsa-base 1.0.25+dfsg-0ubuntu5
  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.1
  Architecture: amd64
  AudioDevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  CurrentDesktop: Unity
  Date: Fri Jul 22 19:00:19 2016
  InstallationDate: Installed on 2016-07-22 (0 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  PackageArchitecture: all
  SourcePackage: alsa-driver
  Symptom: audio
  Symptom_AlsaPlaybackTest: ALSA playback test through plughw:I82801AAICH failed
  Symptom_Card: Built-in Audio - Intel 82801AA-ICH
  Symptom_DevicesInUse:
   USERPID ACCESS COMMAND
   /dev/snd/controlC0:  bobo   2690 F pulseaudio
  Symptom_Type: No sound at all
  Title: [ICH - Intel 82801AA-ICH, playback] No sound at all
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/01/2006
  dmi.bios.vendor: innotek GmbH
  dmi.bios.version: VirtualBox
  dmi.board.name: VirtualBox
  dmi.board.vendor: Oracle Corporation
  dmi.board.version: 1.2
  dmi.chassis.type: 1
  dmi.chassis.vendor: Oracle Corporation
  dmi.modalias: 
dmi:bvninnotekGmbH:bvrVirtualBox:bd12/01/2006:svninnotekGmbH:pnVirtualBox:pvr1.2:rvnOracleCorporation:rnVirtualBox:rvr1.2:cvnOracleCorporation:ct1:cvr:
  dmi.product.name: VirtualBox
  dmi.product.version: 1.2
  dmi.sys.vendor: innotek GmbH

To manage notifications about this bug go to:
https://bugs.launchpad.net/alsa-driver/+bug/1605797/+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 1259635] Re: package at-spi2-core 2.10.1-0ubuntu0.1 failed to install/upgrade: package at-spi2-core is already installed and configured

2016-08-02 Thread dino99
*** This bug is a duplicate of bug 1407757 ***
https://bugs.launchpad.net/bugs/1407757

** This bug has been marked a duplicate of bug 1407757
   multi-arch packages cannot be installed due to dpkg wrongly detecting them 
as already installed

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

Title:
  package at-spi2-core 2.10.1-0ubuntu0.1 failed to install/upgrade:
  package at-spi2-core is already installed and configured

Status in at-spi2-core package in Ubuntu:
  New

Bug description:
  I don't know

  ProblemType: Package
  DistroRelease: Ubuntu 13.10
  Package: at-spi2-core 2.10.1-0ubuntu0.1
  ProcVersionSignature: Ubuntu 3.11.0-14.21-generic 3.11.7
  Uname: Linux 3.11.0-14-generic x86_64
  ApportVersion: 2.12.5-0ubuntu2.1
  Architecture: amd64
  Date: Mon Dec  9 10:50:24 2013
  DuplicateSignature: package:at-spi2-core:2.10.1-0ubuntu0.1:package 
at-spi2-core is already installed and configured
  ErrorMessage: package at-spi2-core is already installed and configured
  InstallationDate: Installed on 2013-10-21 (50 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 
(20131016.1)
  MarkForUpload: True
  SourcePackage: at-spi2-core
  Title: package at-spi2-core 2.10.1-0ubuntu0.1 failed to install/upgrade: 
package at-spi2-core is already installed and configured
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-core/+bug/1259635/+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 1605953] Re: skylake Modesetting Driver on X failure

2016-08-02 Thread Timo Aaltonen
I assume you were running with modesetting and not intel, since the logs
are with intel

anyway, I tried it on Broadwell and it doesn't show anything like your
google photo video. Some frames do show more red/green but there's no
tearing

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

Title:
  skylake Modesetting Driver on X failure

Status in xorg-server package in Ubuntu:
  Confirmed

Bug description:
  with the change away from the intel driver to modeset I get a lot of
  tearing.

  This video shows the problem.

  https://goo.gl/photos/rXNBQ5KR6ZMnhazB9
  And the video capture is done in 240fps so its possible to see what is 
happening more clearly.

  The test video itself is just a short test video with alternating
  red/green pictures in 60Hz.

  What you should see is a somewhat flickering screen but the color
  should be a consistent orange hue.

  there should be no pulsing of colors that is more green then back to
  more red and so on then something is wrong.

  I have attached the video. if you are uncertain how it should look try to 
play it directly on a TV. that is with the TV own player not with a computer as 
that has a lot higher probability of not having any issues with vsync and frame 
updates.
  --- 
  .tmp.unity_support_test.0:
   
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  BootLog:
   /dev/sda2: clean, 770076/2416640 files, 3881571/9647872 blocks
   (K(K
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: compiz
  CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
  CompositorUnredirectFSW: true
  CurrentDesktop: Unity
  DistUpgraded: 2016-04-22 23:31:04,108 DEBUG Running PostInstallScript: 
'./xorg_fix_proprietary.py'
  DistroCodename: yakkety
  DistroRelease: Ubuntu 16.10
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, including running git bisection searches
  GraphicsCard:
   Intel Corporation HD Graphics 530 [8086:1912] (rev 06) (prog-if 00 [VGA 
controller])
 Subsystem: Micro-Star International Co., Ltd. [MSI] HD Graphics 530 
[1462:7976]
   Advanced Micro Devices, Inc. [AMD/ATI] Fiji [Radeon R9 FURY / NANO Series] 
[1002:7300] (rev c8) (prog-if 00 [VGA controller])
 Subsystem: ASUSTeK Computer Inc. Radeon R9 FURY X [1043:04a0]
  InstallationDate: Installed on 2015-10-18 (281 days ago)
  InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150924)
  MachineType: MSI MS-7976
  Package: xorg-server (not installed)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.7.0-rc7+ 
root=UUID=75bb5d92-206d-4bb8-a405-150b9b93d6d3 ro quiet splash vt.handoff=7
  Tags:  yakkety ubuntu regression reproducible compiz-0.9
  Uname: Linux 4.7.0-rc7+ x86_64
  UpgradeStatus: Upgraded to yakkety on 2016-04-22 (94 days ago)
  UserGroups: adm cdrom dip libvirt libvirtd lpadmin plugdev sambashare sudo
  _MarkForUpload: True
  dmi.bios.date: 02/22/2016
  dmi.bios.vendor: American Megatrends Inc.
  dmi.bios.version: 1.B0
  dmi.board.asset.tag: Default string
  dmi.board.name: Z170A GAMING M7 (MS-7976)
  dmi.board.vendor: MSI
  dmi.board.version: 1.0
  dmi.chassis.asset.tag: Default string
  dmi.chassis.type: 3
  dmi.chassis.vendor: MSI
  dmi.chassis.version: 1.0
  dmi.modalias: 
dmi:bvnAmericanMegatrendsInc.:bvr1.B0:bd02/22/2016:svnMSI:pnMS-7976:pvr1.0:rvnMSI:rnZ170AGAMINGM7(MS-7976):rvr1.0:cvnMSI:ct3:cvr1.0:
  dmi.product.name: MS-7976
  dmi.product.version: 1.0
  dmi.sys.vendor: MSI
  version.compiz: compiz 1:0.9.13.0+16.10.20160714.2-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.69-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 12.0.1-3ubuntu2
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 12.0.1-3ubuntu2
  version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu3
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.7.0-1
  version.xserver-xorg-video-intel: xserver-xorg-video-intel 
2:2.99.917+git20160706-1ubuntu1
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.12-2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1605953/+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 1588126] Re: [regression] Adding new wifi networks (with long passwords) never connect at all in OTA-11 and OTA-12

2016-08-02 Thread Jean-Baptiste Lallement
** Changed in: canonical-devices-system-image
   Status: Confirmed => Fix Committed

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

Title:
  [regression] Adding new wifi networks (with long passwords) never
  connect at all in OTA-11 and OTA-12

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Invalid
Status in network-manager package in Ubuntu:
  Fix Committed

Bug description:
  I've just flashed clean images of OTA-11 from the stable channel onto
  a BQ Aquaris E4.5 (krillin) and a Nexus 4 (mako). In both cases the
  phones can see the wifi networks but can't connect to any of them any
  more.

  The wifi networks continue to work for non-Ubuntu devices.

  Also, forcefully flashing a device with OTA-10 fixes the problem. The
  regression began in OTA-11.

  Explanation:
  
https://bugs.launchpad.net/ubuntu/+source/ubuntu-system-settings/+bug/1593686/comments/11

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1588126/+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 1067554] Re: Update to 2.6.1.

2016-08-02 Thread dino99
https://launchpad.net/ubuntu/+source/at-spi2-atk

** Changed in: at-spi2-atk (Ubuntu)
   Status: In Progress => Invalid

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

Title:
  Update to 2.6.1.

Status in at-spi2-atk package in Ubuntu:
  Invalid
Status in at-spi2-core package in Ubuntu:
  Fix Released
Status in at-spi2-atk source package in Quantal:
  Won't Fix
Status in at-spi2-core source package in Quantal:
  Fix Released

Bug description:
  GNOME upstream has released new bugfix releases of the at-spi2 stack,
  version 2.6.1, affecting at-spi2-atk and at-spi2-core. Please consider
  these updates for quantal. This update shoudl be considered under the
  GNOME micro release exception.

  Test case:
  Make sure that at-spi2-core v2.6.1 continues to work as expected.

  Regression potential:
  The chances of regression are extremely low, as this release is a bugfix 
release.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/at-spi2-atk/+bug/1067554/+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 1606774] Re: Xorg crash

2016-08-02 Thread Nito
New crash.

Couldn't attach the core backtrace (it was truncated due not enough
space in /)

the log file is attached.

My feeling (so far) is that it happens less frequently.

Will update with backtrace if I get another error.

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

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

Title:
  Xorg crash

Status in xorg package in Ubuntu:
  Incomplete

Bug description:
  I get random X server crashes

  The last lines of the Xorg.0.log.old are:

  [  1163.549] (EE) 
  [  1163.549] (EE) Backtrace:
  [  1163.549] (EE) 0: /usr/lib/xorg/Xorg (xorg_backtrace+0x4e) [0x5574057265ce]
  [  1163.549] (EE) 1: /usr/lib/xorg/Xorg (0x557405574000+0x1b6959) 
[0x55740572a959]
  [  1163.550] (EE) 2: /lib/x86_64-linux-gnu/libc.so.6 (0x7f958502f000+0x354a0) 
[0x7f95850644a0]
  [  1163.550] (EE) 3: /usr/lib/xorg/Xorg (0x557405574000+0x129595) 
[0x55740569d595]
  [  1163.550] (EE) 4: /usr/lib/xorg/Xorg (ValidatePicture+0x9) [0x55740569f359]
  [  1163.550] (EE) 5: /usr/lib/xorg/Xorg (CompositePicture+0xb5) 
[0x55740569f435]
  [  1163.550] (EE) 6: /usr/lib/xorg/Xorg (0x557405574000+0x12fc17) 
[0x5574056a3c17]
  [  1163.550] (EE) 7: /usr/lib/xorg/Xorg (0x557405574000+0x53bbf) 
[0x5574055c7bbf]
  [  1163.550] (EE) 8: /usr/lib/xorg/Xorg (0x557405574000+0x57c33) 
[0x5574055cbc33]
  [  1163.551] (EE) 9: /lib/x86_64-linux-gnu/libc.so.6 (__libc_start_main+0xf0) 
[0x7f958504f830]
  [  1163.551] (EE) 10: /usr/lib/xorg/Xorg (_start+0x29) [0x5574055b5f59]
  [  1163.551] (EE) 
  [  1163.551] (EE) Segmentation fault at address 0x18
  [  1163.551] (EE) 
  Fatal server error:
  [  1163.551] (EE) Caught signal 11 (Segmentation fault). Server aborting
  [  1163.551] (EE) 
  [  1163.551] (EE)

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: xorg 1:7.7+13ubuntu3
  ProcVersionSignature: Ubuntu 4.4.0-28.47-lowlatency 4.4.13
  Uname: Linux 4.4.0-28-lowlatency 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: None
  CurrentDesktop: MATE
  Date: Wed Jul 27 07:49:22 2016
  DistUpgraded: 2016-05-30 00:00:15,168 ERROR got error from PostInstallScript 
./xorg_fix_proprietary.py (Failed to execute child process 
"./xorg_fix_proprietary.py" (No such file or directory))
  DistroCodename: xenial
  DistroVariant: ubuntu
  EcryptfsInUse: Yes
  ExtraDebuggingInterest: Yes
  GraphicsCard:
   Intel Corporation Sky Lake Integrated Graphics [8086:1916] (rev 07) (prog-if 
00 [VGA controller])
 Subsystem: Dell Skylake Integrated Graphics [1028:0704]
  MachineType: Dell Inc. XPS 13 9350
  ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.4.0-28-lowlatency 
root=/dev/mapper/sarvg-rootvol ro rootflags=subvol=@ quiet 
intel_idle.max_cstate=1
  SourcePackage: xorg
  Symptom: display
  Title: Xorg crash
  UpgradeStatus: Upgraded to xenial on 2016-05-29 (58 days ago)
  dmi.bios.date: 11/27/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: 1.1.7
  dmi.board.name: 0VM5NC
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: 
dmi:bvnDellInc.:bvr1.1.7:bd11/27/2015:svnDellInc.:pnXPS139350:pvr:rvnDellInc.:rn0VM5NC:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9350
  dmi.sys.vendor: Dell Inc.
  version.compiz: compiz 1:0.9.12.2+16.04.20160714-0ubuntu1
  version.ia32-libs: ia32-libs N/A
  version.libdrm2: libdrm2 2.4.67-1ubuntu0.16.04.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.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
  version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 
1:1.0.12-1build2
  xserver.bootTime: Wed Jul 27 07:48:18 2016
  xserver.configfile: default
  xserver.errors:
   
  xserver.logfile: /var/log/Xorg.0.log
  xserver.outputs:
   product id5153 
   vendor SHP
  xserver.version: 2:1.18.3-1ubuntu2.2

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1606774/+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 1608822] Re: signon fails tests on Qt 5.6

2016-08-02 Thread Alberto Mardegan
Filed https://bugreports.qt.io/browse/QTBUG-55087

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

Title:
  signon fails tests on Qt 5.6

Status in signon package in Ubuntu:
  Confirmed

Bug description:
  See build logs at:

  https://launchpadlibrarian.net/276197217/buildlog_ubuntu-yakkety-
  
amd64.signon_8.58+16.04.20151106-0ubuntu2~~testrebuild1~~testrebuild1~1_BUILDING.txt.gz

  Qt 5.6 aims to be landed to the xenial-overlay so this should be
  fixed.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1608822/+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 1589535] Re: nm-applet silently timesout on long 'WPA/WPA2 Personal' password input

2016-08-02 Thread Aron Xu
** Changed in: network-manager-applet (Ubuntu)
 Assignee: (unassigned) => Aron Xu (happyaron)

** Changed in: network-manager-applet (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  nm-applet silently timesout on long 'WPA/WPA2 Personal' password input

Status in Network Manager Applet:
  Confirmed
Status in network-manager-applet package in Ubuntu:
  In Progress

Bug description:
  1)
  ouroumov@Edge:~/Desktop$ lsb_release -rd
  Description:  Ubuntu 16.04 LTS
  Release:  16.04

  2)
  apt-cache policy is unable to locate the package.

  3)
  Upon entering a long WPA/WPA2 Personal password after clicking the network 
icon in the top right panel, the connection should be added to network-manager, 
even if typing the password takes a while.

  4)
  If typing the password takes longer than ~25 seconds, upon clicking the 
"Connect" button in the password prompt dialog: nothing happens

  Steps to reproduce:

  - Install Ubuntu MATE 16.04 LTS (possibly other Ubuntu flavours using 
nm-applet too)
  - Run normal post-install full system update and reboot
  - Click the network icon in the top right corner of the default panel layout
  - Select from the Wi-Fi network list a network using WPA/WPA2 Personal
  - Enter the password, wait 30 seconds to click 'connect'

  Note:

  While this issue might seem trivial (using 'System -> Preferences ->
  Internet and Network -> Network Connections' allows one to correctly
  save the password) (and quickly copy/pasting the password from a text
  file works too) it is a serious usability problem for many people in
  France.

  The default home router Wi-Fi setup in France is WPA/WPA2 Personal
  with a random 26-character hexadecimal password. It takes a while to
  type.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager-applet/+bug/1589535/+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 1278437] Re: can't move link type .desktop files around on desktop

2016-08-02 Thread Ryan
According to the patch comments, it looks like it is fixed from nautilus
3.15.4 onwards. I am running Ubuntu 16.04.1 LTS and the "latest" version
of nautilus I am running is 3.14.3. Sucks.

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

Title:
  can't move link type .desktop files around on desktop

Status in Nautilus:
  Fix Released
Status in nautilus package in Ubuntu:
  Fix Released

Bug description:
  * Impact
  links can't be moved on the desktop

  * Test case

  Save the following as e.g. test.desktop in your ~/Desktop folder and
  try to move it around on the desktop:

  [Desktop Entry]
  Version=1.0
  Type=Link
  Name=test
  URL=https://launchpad.net/index.html

  * Regression potential
  Dnd should keep working

  --

  If I have a .desktop file with Type=Link on my desktop and try to move
  it around it doesn't stay where I drop it but goes back where it was
  before and tries to download the URL it is referring to instead.

  Save the following as e.g. test.desktop in your ~/Desktop folder and
  try to move it around on the desktop:

  [Desktop Entry]
  Version=1.0
  Type=Link
  Name=test
  URL=https://launchpad.net/index.html

  This affects at least 13.10 and 14.04.

   In 13.10 Nautilus crashes if the URL as a file:// URL referring to a
  file on your desktop.

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.13.0-7.26-generic 3.13.1
  Uname: Linux 3.13.0-7-generic i686
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: i386
  CurrentDesktop: Unity
  Date: Mon Feb 10 14:06:24 2014
  GsettingsChanges:

  InstallationDate: Installed on 2013-10-11 (122 days ago)
  InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Beta i386 (20130925.1)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=de_DE.UTF-8
   SHELL=/bin/zsh
  SourcePackage: nautilus
  UpgradeStatus: Upgraded to trusty on 2013-12-07 (64 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/nautilus/+bug/1278437/+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 1605117] Re: Unity greeter indicators don't show on second launch

2016-08-02 Thread seanlano
I can confirm that the 1.18.2-0ubuntu2 version fixes the problem for me
too

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

Title:
  Unity greeter indicators don't show on second launch

Status in Light Display Manager:
  Fix Committed
Status in lightdm package in Ubuntu:
  Fix Committed
Status in lightdm source package in Xenial:
  Fix Committed

Bug description:
  [Impact]
  Unity Greeter indicators don't show second time greeter started.

  [Test Case]
  1. Log in with greeter
  2. Log out

  Expected result:
  Unity greeter is shown with all UI elements as in step 1.

  Observed result:
  Unity greeter is shown but only one indicator shows (accessibility)

  [Regression potential]
  Low. The fix was already present in the Bzr branch (removed some unneeded 
code that would accidentally close stdin). The fix was not released since it 
hadn't been shown to be a problem before this report.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lightdm/+bug/1605117/+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 1608917] [NEW] Headphones not working while speakers do

2016-08-02 Thread Igor Bogoslavskyi
Public bug reported:

I have recently done a clean install of Ubuntu Gnome 16.04, and it seems
that the headphones are not working.

Behavior: I play something through speakers, plug in headphones, and
hear nothing both in headphones or from speakers.

Expected: The sound should switch to headphones.

If I run the following command I can hear the sound from headphones: 
> pacmd set-sink-port 1 analog-output-headphones

I have gathered and attached alsa-info log with command:
> wget http://www.alsa-project.org/alsa-info.sh -O alsa-info.sh && bash 
> alsa-info.sh

Please tell me if I can provide any additional info. I think this is
crucial to fix for an LTS release. The bug did not occur on 14.04 on the
same hardware.

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

** Attachment added: "Alsa info log"
   
https://bugs.launchpad.net/bugs/1608917/+attachment/4712345/+files/alsa-log.txt

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

Title:
  Headphones not working while speakers do

Status in pulseaudio package in Ubuntu:
  New

Bug description:
  I have recently done a clean install of Ubuntu Gnome 16.04, and it
  seems that the headphones are not working.

  Behavior: I play something through speakers, plug in headphones, and
  hear nothing both in headphones or from speakers.

  Expected: The sound should switch to headphones.

  If I run the following command I can hear the sound from headphones: 
  > pacmd set-sink-port 1 analog-output-headphones

  I have gathered and attached alsa-info log with command:
  > wget http://www.alsa-project.org/alsa-info.sh -O alsa-info.sh && bash 
alsa-info.sh

  Please tell me if I can provide any additional info. I think this is
  crucial to fix for an LTS release. The bug did not occur on 14.04 on
  the same hardware.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1608917/+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 1608822] Re: signon fails tests on Qt 5.6

2016-08-02 Thread Alberto Mardegan
Reproduced with silo 24. Investigating...

** Changed in: signon (Ubuntu)
 Assignee: (unassigned) => Alberto Mardegan (mardy)

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

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

Title:
  signon fails tests on Qt 5.6

Status in signon package in Ubuntu:
  Confirmed

Bug description:
  See build logs at:

  https://launchpadlibrarian.net/276197217/buildlog_ubuntu-yakkety-
  
amd64.signon_8.58+16.04.20151106-0ubuntu2~~testrebuild1~~testrebuild1~1_BUILDING.txt.gz

  Qt 5.6 aims to be landed to the xenial-overlay so this should be
  fixed.

  More information about Qt 5.6 at
  https://wiki.ubuntu.com/Touch/QtTesting

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/signon/+bug/1608822/+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 1608908] [NEW] Some UI elements are invisible with GTK 3.20

2016-08-02 Thread Iain Lane
Public bug reported:

1. Have GTK 3.20 and a fixed ubuntu-themes, for example from yakkety-proposed 
or ppa:ubuntu-desktop/gtk320
2. Run `lightdm --test-mode'
3. Enter your password if prompted, and maxmimise the window
4. See Unity Greeter
5. Focus the password prompt and press enter, or get your password wrong
alternative 5. Click the session switcher if you have more than one session 
installed

The password prompt disappears, or a blank box is drawn instead of the
list of sessions. You can scroll (down, up) to get the password prompt
back, or you can click towards the top left of the window to dismiss the
session switcher and get back to the list.

Bisecting throws up
.
Reverting this does not fix things, so it's not the full story, but it
suggests that unity-greeter needs to do its drawing differently somehow.

ProblemType: Bug
DistroRelease: Ubuntu 16.10
Package: unity-greeter 16.10.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
Uname: Linux 4.4.0-33-generic x86_64
ApportVersion: 2.20.2-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Tue Aug  2 12:14:39 2016
InstallationDate: Installed on 2012-10-07 (1394 days ago)
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
SourcePackage: unity-greeter
UpgradeStatus: Upgraded to yakkety on 2013-05-07 (1183 days ago)

** Affects: unity-greeter (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-bug third-party-packages yakkety

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

Title:
  Some UI elements are invisible with GTK 3.20

Status in unity-greeter package in Ubuntu:
  New

Bug description:
  1. Have GTK 3.20 and a fixed ubuntu-themes, for example from yakkety-proposed 
or ppa:ubuntu-desktop/gtk320
  2. Run `lightdm --test-mode'
  3. Enter your password if prompted, and maxmimise the window
  4. See Unity Greeter
  5. Focus the password prompt and press enter, or get your password wrong
  alternative 5. Click the session switcher if you have more than one session 
installed

  The password prompt disappears, or a blank box is drawn instead of the
  list of sessions. You can scroll (down, up) to get the password prompt
  back, or you can click towards the top left of the window to dismiss
  the session switcher and get back to the list.

  Bisecting throws up
  
.
  Reverting this does not fix things, so it's not the full story, but it
  suggests that unity-greeter needs to do its drawing differently
  somehow.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.10
  Package: unity-greeter 16.10.1-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15
  Uname: Linux 4.4.0-33-generic x86_64
  ApportVersion: 2.20.2-0ubuntu1
  Architecture: amd64
  CurrentDesktop: Unity
  Date: Tue Aug  2 12:14:39 2016
  InstallationDate: Installed on 2012-10-07 (1394 days ago)
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Beta amd64 (20121007)
  SourcePackage: unity-greeter
  UpgradeStatus: Upgraded to yakkety on 2013-05-07 (1183 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-greeter/+bug/1608908/+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 1576576] Re: [needs-packaging] Update to 3.20 needs work and coordination

2016-08-02 Thread Iain Lane
I added ubuntu-settings because you get warnings when upgrading
otherwise

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

** Changed in: ubuntu-settings (Ubuntu)
   Status: New => Confirmed

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

Title:
  [needs-packaging] Update to 3.20 needs work and coordination

Status in Mozilla Firefox:
  Fix Released
Status in Ubuntu GNOME:
  Confirmed
Status in adwaita-icon-theme package in Ubuntu:
  Confirmed
Status in gtk+2.0 package in Ubuntu:
  Confirmed
Status in gtk+3.0 package in Ubuntu:
  Confirmed
Status in ubuntu-settings package in Ubuntu:
  Confirmed

Bug description:
  The current upstream stable/Debian version is 3.20 but that includes quite 
some changes in the css handling which means we are going to need to update/fix 
the unity themes and make sure you main application look fine before landing.
  The transition needs to be prepared in a staging ppa before being considered, 
help is welcome since it's likely the desktop team is not going to have lot of 
cycles to work on that.

To manage notifications about this bug go to:
https://bugs.launchpad.net/firefox/+bug/1576576/+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


Re: [Desktop-packages] [Bug 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

2016-08-02 Thread John McAleely
I am not certain, but I believe it is labelled 'nvram'. Describing the
problem in terms of using format & download should be sufficient. BQ
support are aware of the problems the tool has.

On 2 August 2016 at 11:38, Samuel Walladge 
wrote:

> Ok.
>
> "You will have lost your S/N, MAC addresses, and some key
> material the HDMI software expects to find (but does not use)."
>
> What partition(s) keep that data?
> (Asking because I'm trying to gather data for discussing with BQ.)
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1607684
>
> Title:
>   wifi networks not remembered correctly (ubuntu touch, bq M10)
>
> Status in Canonical System Image:
>   Incomplete
> Status in network-manager package in Ubuntu:
>   New
>
> Bug description:
>   I have a M10, on ubuntu touch OTA-12 (and same issue previously on
>   OTA-11).
>
>   The issue is that it doesn't remember wifi networks properly. To
>   explain:
>
>   1. turn on tablet
>   2. select my wifi network from the list
>   3. enter password and click connect
>   4. reboot device
>   5. select my wifi network from the list
>   6. enter password and click connect
>   .
>   .
>   .
>   30. go to wifi settings -> previous networks
>   31. view long list that looks like:
>
>   MyWifinetwork1
>   MyWifinetwork2
>   MyWifinetwork3
>   MyWifinetwork4
>   ...
>
>   What it should do (and did some time ago), is see that MyWifinetwork
>   was saved in previous networks and automatically connect using the
>   saved password/settings.
>
>   So, I'm wondering is this a bug, something badly configured in my wifi
>   network (although other devices remember it fine), or something else?
>
>   Thanks.
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+subscriptions
>

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+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 1607684] Re: wifi networks not remembered correctly (ubuntu touch, bq M10)

2016-08-02 Thread Samuel Walladge
Ok.

"You will have lost your S/N, MAC addresses, and some key
material the HDMI software expects to find (but does not use)."

What partition(s) keep that data? 
(Asking because I'm trying to gather data for discussing with BQ.)

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

Title:
  wifi networks not remembered correctly (ubuntu touch, bq M10)

Status in Canonical System Image:
  Incomplete
Status in network-manager package in Ubuntu:
  New

Bug description:
  I have a M10, on ubuntu touch OTA-12 (and same issue previously on
  OTA-11).

  The issue is that it doesn't remember wifi networks properly. To
  explain:

  1. turn on tablet
  2. select my wifi network from the list
  3. enter password and click connect
  4. reboot device
  5. select my wifi network from the list
  6. enter password and click connect
  .
  .
  .
  30. go to wifi settings -> previous networks
  31. view long list that looks like:

  MyWifinetwork1
  MyWifinetwork2
  MyWifinetwork3
  MyWifinetwork4
  ...

  What it should do (and did some time ago), is see that MyWifinetwork
  was saved in previous networks and automatically connect using the
  saved password/settings.

  So, I'm wondering is this a bug, something badly configured in my wifi
  network (although other devices remember it fine), or something else?

  Thanks.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1607684/+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


  1   2   >