[Desktop-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic

[Erick Brunzell]

Documentation is horribly insufficient in this regard. To quote the link
given, "Ubuntu Desktop flavour now always tracks HWE kernel (hardware
enablement). It means that from 20.04.2 release Ubuntu Desktop will gain
new major kernel versions every 6 months through to summer of 2022".

The words "from 20.04.2 release Ubuntu Desktop will gain new major
kernel versions every 6 months" speak volumes, sadly incorrect volumes.
20.04.2 is not even due for release until next month but we've been
getting HWE kernel updates for a couple of weeks already!

All of the following documentation needs serious updating and must
include methods to remain on the GA kernel if one wishes:

The first, also from the release notes, states clearly "Ubuntu 20.04 LTS
is based on the long-term supported Linux release series 5.4":

https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Updated_Packages

None of these have been updated to adequately reflect the change to opt-
out of HWE rather than opt-in if using original (20.04) or first point
release (20.04.1) installation media as had always been the case
previously.

https://wiki.ubuntu.com/Kernel/LTSEnablementStack
https://wiki.ubuntu.com/Kernel/RollingLTSEnablementStack
https://ubuntu.com/kernel/lifecycle

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

Title:
  Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of
  linux-generic

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Beginning about January 8th Focal users that installed Focal using
  either the Ubuntu 20.04 or 20.04.1 installation media began getting
  updated to the 5.8 series linux kernel. Those who had installed using
  the Ubuntu Focal Beta were not effected. This is because Focal Beta
  was properly built with ‘linux-generic’ but the 20.04 and 20.04.1
  images were built with ‘linux-generic-hwe-20.04‘. This can be easily
  verified by looking at the iso manifest:

  https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop-
  amd64.manifest

  Note: old-release manifests (where 20.04 Beta and 20.04 reside) must
  be downloaded here:

  https://old-releases.ubuntu.com/releases/20.04/

  The expected behavior is for Ubuntu Focal users to remain on the 5.4
  series kernel unless they install with 20.04.2 or later images as
  indicated here:

  https://wiki.ubuntu.com/Kernel/LTSEnablementStack

  While not entirely updated it says “if one wants to remain on the
  original GA (General Availability) stacks, the options [include];
  Install from a previous
  12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point
  release and update”.

  Jump just below that to the Focal specific notes and it says “The
  20.04.2 and newer point releases will ship with an updated kernel and
  X stack by default for the desktop”. Since 20.04.2 is not even due for
  release until next month it makes no sense for updates to the 5.8
  series kernel to be occurring unless the focal-proposed repos are
  enabled even if HWE protocols had been changed.

  It’s also worth noting that thankfully no accompanying HWE X stack is
  yet available in the repos. I say thankfully because my efforts at
  downgrading the X stack in 16.04 and 18.04 were never successful! But
  the lack of a matching X stack may explain the many complaints on the
  forums about broken graphics???

  It’s also worth noting that even the release notes say that “Ubuntu
  20.04 LTS is based on the long-term supported Linux release series
  5.4“.

  https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel

  Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1
  are supposed to be supported with the 5.4 series kernel for the entire
  5 year life span:

  https://ubuntu.com/kernel/lifecycle

  The other flavors’ 20.04 and 20.04.1 images were all built correctly
  with ‘linux-generic’ with the possible exception of Ubuntu Studio
  which uses a kernel stack I’m not familiar with. I’m also uncertain
  about Ubuntu server because I’m simply not familiar with it.

  Original bug description below:

  ##

  Just as the title says, the 20.04 and 20.04.1 images use the HWE
  version of linux-generic resulting in upgrades to the 5.8 series
  kernel. This seems to effect Ubuntu only, or I should say I checked
  the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all
  correctly list linux-generic. Also HWE is not truly complete without
  the accompanying HWE Xstack.

  I checked all the documentation I could find and this was clearly not
  intentional. In fact the manifest for Ubuntu Focal Beta still used
  linux-generic, so this got messed up some time between April 3, 2020
  and April 23, 2020. Here's just one example of the documentation for
  kernel support in Focal LTS:

  

[Desktop-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic

[Erick Brunzell]

I filed bug #1912032 concerning the failure of nvidia drivers to install
during a fresh installation of Ubuntu 20.04.1 because when download
updates is selected it auto-updates to a 5.8 series kernel during
installation.

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

Title:
  Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of
  linux-generic

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Beginning about January 8th Focal users that installed Focal using
  either the Ubuntu 20.04 or 20.04.1 installation media began getting
  updated to the 5.8 series linux kernel. Those who had installed using
  the Ubuntu Focal Beta were not effected. This is because Focal Beta
  was properly built with ‘linux-generic’ but the 20.04 and 20.04.1
  images were built with ‘linux-generic-hwe-20.04‘. This can be easily
  verified by looking at the iso manifest:

  https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop-
  amd64.manifest

  Note: old-release manifests (where 20.04 Beta and 20.04 reside) must
  be downloaded here:

  https://old-releases.ubuntu.com/releases/20.04/

  The expected behavior is for Ubuntu Focal users to remain on the 5.4
  series kernel unless they install with 20.04.2 or later images as
  indicated here:

  https://wiki.ubuntu.com/Kernel/LTSEnablementStack

  While not entirely updated it says “if one wants to remain on the
  original GA (General Availability) stacks, the options [include];
  Install from a previous
  12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point
  release and update”.

  Jump just below that to the Focal specific notes and it says “The
  20.04.2 and newer point releases will ship with an updated kernel and
  X stack by default for the desktop”. Since 20.04.2 is not even due for
  release until next month it makes no sense for updates to the 5.8
  series kernel to be occurring unless the focal-proposed repos are
  enabled even if HWE protocols had been changed.

  It’s also worth noting that thankfully no accompanying HWE X stack is
  yet available in the repos. I say thankfully because my efforts at
  downgrading the X stack in 16.04 and 18.04 were never successful! But
  the lack of a matching X stack may explain the many complaints on the
  forums about broken graphics???

  It’s also worth noting that even the release notes say that “Ubuntu
  20.04 LTS is based on the long-term supported Linux release series
  5.4“.

  https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel

  Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1
  are supposed to be supported with the 5.4 series kernel for the entire
  5 year life span:

  https://ubuntu.com/kernel/lifecycle

  The other flavors’ 20.04 and 20.04.1 images were all built correctly
  with ‘linux-generic’ with the possible exception of Ubuntu Studio
  which uses a kernel stack I’m not familiar with. I’m also uncertain
  about Ubuntu server because I’m simply not familiar with it.

  Original bug description below:

  ##

  Just as the title says, the 20.04 and 20.04.1 images use the HWE
  version of linux-generic resulting in upgrades to the 5.8 series
  kernel. This seems to effect Ubuntu only, or I should say I checked
  the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all
  correctly list linux-generic. Also HWE is not truly complete without
  the accompanying HWE Xstack.

  I checked all the documentation I could find and this was clearly not
  intentional. In fact the manifest for Ubuntu Focal Beta still used
  linux-generic, so this got messed up some time between April 3, 2020
  and April 23, 2020. Here's just one example of the documentation for
  kernel support in Focal LTS:

  https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle

  Installations performed with 20.04 and 20.04.1 media were supposed to
  remain on the 5.4 series kernel throughout Focal's 5 year lifespan as
  had been the case since HWE was introduced. The first step in fixing
  this needs to be stopping fresh installs of Focal using the 20.04 and
  20.04.1 media from immediately upgrading to the 5.8 series kernel.

  It might be a little tricky to revert users from 5.8 to 5.4, but there
  have been reports of breakage, particularly concerning Broadcom wifi
  drivers and some graphics problems. But the graphics problems could
  also be exacerbated by the lack of the matching HWE Xstack? At any
  rate it's a bug.

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

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

[Desktop-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic

[Erick Brunzell]

I updated the bug description to better explain why I believe this is a
bug, but I left the original content below the break.

** Description changed:

  Beginning about January 8th Focal users that installed Focal using
  either the Ubuntu 20.04 or 20.04.1 installation media began getting
  updated to the 5.8 series linux kernel. Those who had installed using
  the Ubuntu Focal Beta were not effected. This is because Focal Beta was
  properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images
  were built with ‘linux-generic-hwe-20.04‘. This can be easily verified
  by looking at the iso manifest:
  
  https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop-
  amd64.manifest
  
  Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be
  downloaded here:
  
  https://old-releases.ubuntu.com/releases/20.04/
  
  The expected behavior is for Ubuntu Focal users to remain on the 5.4
  series kernel unless they install with 20.04.2 or later images as
  indicated here:
  
  https://wiki.ubuntu.com/Kernel/LTSEnablementStack
  
  While not entirely updated it says “if one wants to remain on the
  original GA (General Availability) stacks, the options [include];
  Install from a previous
  12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point
  release and update”.
  
  Jump just below that to the Focal specific notes and it says “The
  20.04.2 and newer point releases will ship with an updated kernel and X
  stack by default for the desktop”. Since 20.04.2 is not even due for
  release until next month it makes no sense for updates to the 5.8 series
  kernel to be occurring unless the focal-proposed repos are enabled even
  if HWE protocols had been changed.
  
  It’s also worth noting that thankfully no accompanying HWE X stack is
  yet available in the repos. I say thankfully because my efforts at
- downgrading the X stack in 16.04 and 18.04 were always successful! But
+ downgrading the X stack in 16.04 and 18.04 were never successful! But
  the lack of a matching X stack may explain the many complaints on the
  forums about broken graphics???
  
  It’s also worth noting that even the release notes say that “Ubuntu
  20.04 LTS is based on the long-term supported Linux release series 5.4“.
  
  https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel
  
  Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are
  supposed to be supported with the 5.4 series kernel for the entire 5
  year life span:
  
  https://ubuntu.com/kernel/lifecycle
  
  The other flavors’ 20.04 and 20.04.1 images were all built correctly
  with ‘linux-generic’ with the possible exception of Ubuntu Studio which
  uses a kernel stack I’m not familiar with. I’m also uncertain about
  Ubuntu server because I’m simply not familiar with it.
  
  Original bug description below:
  
  ##
  
  Just as the title says, the 20.04 and 20.04.1 images use the HWE version
  of linux-generic resulting in upgrades to the 5.8 series kernel. This
  seems to effect Ubuntu only, or I should say I checked the Kubuntu,
  Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list
  linux-generic. Also HWE is not truly complete without the accompanying
  HWE Xstack.
  
  I checked all the documentation I could find and this was clearly not
  intentional. In fact the manifest for Ubuntu Focal Beta still used
  linux-generic, so this got messed up some time between April 3, 2020 and
  April 23, 2020. Here's just one example of the documentation for kernel
  support in Focal LTS:
  
  https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle
  
  Installations performed with 20.04 and 20.04.1 media were supposed to
  remain on the 5.4 series kernel throughout Focal's 5 year lifespan as
  had been the case since HWE was introduced. The first step in fixing
  this needs to be stopping fresh installs of Focal using the 20.04 and
  20.04.1 media from immediately upgrading to the 5.8 series kernel.
  
  It might be a little tricky to revert users from 5.8 to 5.4, but there
  have been reports of breakage, particularly concerning Broadcom wifi
  drivers and some graphics problems. But the graphics problems could also
  be exacerbated by the lack of the matching HWE Xstack? At any rate it's
  a bug.

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

Title:
  Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of
  linux-generic

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Beginning about January 8th Focal users that installed Focal using
  either the Ubuntu 20.04 or 20.04.1 installation media began getting
  updated to the 5.8 series linux kernel. Those who had installed using
  the Ubuntu Focal Beta were not effected. This is because Focal Beta
  was properly 

[Desktop-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic

[Erick Brunzell]

I added the packaging tag because this was a packaging error in the
20.04 and 20.04.1 images.

** Tags added: packaging

** Description changed:

+ Beginning about January 8th Focal users that installed Focal using
+ either the Ubuntu 20.04 or 20.04.1 installation media began getting
+ updated to the 5.8 series linux kernel. Those who had installed using
+ the Ubuntu Focal Beta were not effected. This is because Focal Beta was
+ properly built with ‘linux-generic’ but the 20.04 and 20.04.1 images
+ were built with ‘linux-generic-hwe-20.04‘. This can be easily verified
+ by looking at the iso manifest:
+ 
+ https://releases.ubuntu.com/20.04.1/ubuntu-20.04.1-desktop-
+ amd64.manifest
+ 
+ Note: old-release manifests (where 20.04 Beta and 20.04 reside) must be
+ downloaded here:
+ 
+ https://old-releases.ubuntu.com/releases/20.04/
+ 
+ The expected behavior is for Ubuntu Focal users to remain on the 5.4
+ series kernel unless they install with 20.04.2 or later images as
+ indicated here:
+ 
+ https://wiki.ubuntu.com/Kernel/LTSEnablementStack
+ 
+ While not entirely updated it says “if one wants to remain on the
+ original GA (General Availability) stacks, the options [include];
+ Install from a previous
+ 12.04.0/12.04.1/14.04.0/14.04.1/16.04.0/16.04.1/18.04.0/18.04.1 point
+ release and update”.
+ 
+ Jump just below that to the Focal specific notes and it says “The
+ 20.04.2 and newer point releases will ship with an updated kernel and X
+ stack by default for the desktop”. Since 20.04.2 is not even due for
+ release until next month it makes no sense for updates to the 5.8 series
+ kernel to be occurring unless the focal-proposed repos are enabled even
+ if HWE protocols had been changed.
+ 
+ It’s also worth noting that thankfully no accompanying HWE X stack is
+ yet available in the repos. I say thankfully because my efforts at
+ downgrading the X stack in 16.04 and 18.04 were always successful! But
+ the lack of a matching X stack may explain the many complaints on the
+ forums about broken graphics???
+ 
+ It’s also worth noting that even the release notes say that “Ubuntu
+ 20.04 LTS is based on the long-term supported Linux release series 5.4“.
+ 
+ https://wiki.ubuntu.com/FocalFossa/ReleaseNotes#Linux_Kernel
+ 
+ Scroll to the bottom here and you’ll also see that 20.04 and 20.04.1 are
+ supposed to be supported with the 5.4 series kernel for the entire 5
+ year life span:
+ 
+ https://ubuntu.com/kernel/lifecycle
+ 
+ The other flavors’ 20.04 and 20.04.1 images were all built correctly
+ with ‘linux-generic’ with the possible exception of Ubuntu Studio which
+ uses a kernel stack I’m not familiar with. I’m also uncertain about
+ Ubuntu server because I’m simply not familiar with it.
+ 
+ Original bug description below:
+ 
+ ##
+ 
  Just as the title says, the 20.04 and 20.04.1 images use the HWE version
  of linux-generic resulting in upgrades to the 5.8 series kernel. This
  seems to effect Ubuntu only, or I should say I checked the Kubuntu,
  Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list
  linux-generic. Also HWE is not truly complete without the accompanying
  HWE Xstack.
  
  I checked all the documentation I could find and this was clearly not
  intentional. In fact the manifest for Ubuntu Focal Beta still used
  linux-generic, so this got messed up some time between April 3, 2020 and
  April 23, 2020. Here's just one example of the documentation for kernel
  support in Focal LTS:
  
  https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle
  
  Installations performed with 20.04 and 20.04.1 media were supposed to
  remain on the 5.4 series kernel throughout Focal's 5 year lifespan as
  had been the case since HWE was introduced. The first step in fixing
  this needs to be stopping fresh installs of Focal using the 20.04 and
  20.04.1 media from immediately upgrading to the 5.8 series kernel.
  
  It might be a little tricky to revert users from 5.8 to 5.4, but there
  have been reports of breakage, particularly concerning Broadcom wifi
  drivers and some graphics problems. But the graphics problems could also
  be exacerbated by the lack of the matching HWE Xstack? At any rate it's
  a bug.

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

Title:
  Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of
  linux-generic

Status in ubuntu-meta package in Ubuntu:
  Confirmed

Bug description:
  Beginning about January 8th Focal users that installed Focal using
  either the Ubuntu 20.04 or 20.04.1 installation media began getting
  updated to the 5.8 series linux kernel. Those who had installed using
  the Ubuntu Focal Beta were not effected. This is because Focal Beta
  was properly built with ‘linux-generic’ but the 20.04 and 20.04.1
  images were built with 

[Desktop-packages] [Bug 1911614] Re: Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic

[Erick Brunzell]

Unfortunately apport-collect just says "no additional info collected"
(see pic added). I presume because 'ubuntu-meta' is not an installed
package? I struggled a bit trying to decide what the best way was to
report a bug like this because it's not actually a bug in the kernel
itself, it's just that I believe the 5.8 series kernel should not be
installed without specific user action to do so.

That had been the case in the past. LTS installs using the original iso
or the first point release iso would remain on the original GA (General
Availability) throughout the duration of the 5 year support cycle. In
fact I see the HWE Wiki has been updated to say "The 20.04.2 and newer
point releases will ship with an updated kernel and X stack by default
for the desktop":

https://wiki.ubuntu.com/Kernel/LTSEnablementStack

And 20.04.2 is not due for release until early February. It's worth
mentioning that LTS point releases are frequently delayed by a week or
two if bugs are encountered. Anyway I would expect an installation
performed with 20.04.2 media to include the HWE kernel. You'll also
notice that they do say "kernel and X stack" and as mentioned above the
HWE X stack is not yet even in the repos!

I will probably be testing the 20.04.2 daily build very soon and I'll
then report a bug against 'linux-generic-hwe-20.04' making note that the
accompanying X stack is missing. And yes, this does effect only Ubuntu
Desktop because as mentioned above I checked some of the other flavors
manifests. Only the Ubuntu isos have the HWE version of kinux-generic
installed.

** Attachment added: "Screenshot from 2021-01-14 19-45-49.png"
   
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+attachment/5453132/+files/Screenshot%20from%202021-01-14%2019-45-49.png

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

Title:
  Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of
  linux-generic

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Just as the title says, the 20.04 and 20.04.1 images use the HWE
  version of linux-generic resulting in upgrades to the 5.8 series
  kernel. This seems to effect Ubuntu only, or I should say I checked
  the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all
  correctly list linux-generic. Also HWE is not truly complete without
  the accompanying HWE Xstack.

  I checked all the documentation I could find and this was clearly not
  intentional. In fact the manifest for Ubuntu Focal Beta still used
  linux-generic, so this got messed up some time between April 3, 2020
  and April 23, 2020. Here's just one example of the documentation for
  kernel support in Focal LTS:

  https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle

  Installations performed with 20.04 and 20.04.1 media were supposed to
  remain on the 5.4 series kernel throughout Focal's 5 year lifespan as
  had been the case since HWE was introduced. The first step in fixing
  this needs to be stopping fresh installs of Focal using the 20.04 and
  20.04.1 media from immediately upgrading to the 5.8 series kernel.

  It might be a little tricky to revert users from 5.8 to 5.4, but there
  have been reports of breakage, particularly concerning Broadcom wifi
  drivers and some graphics problems. But the graphics problems could
  also be exacerbated by the lack of the matching HWE Xstack? At any
  rate it's a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+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 1911614] [NEW] Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of linux-generic

[Erick Brunzell]

Public bug reported:

Just as the title says, the 20.04 and 20.04.1 images use the HWE version
of linux-generic resulting in upgrades to the 5.8 series kernel. This
seems to effect Ubuntu only, or I should say I checked the Kubuntu,
Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all correctly list
linux-generic. Also HWE is not truly complete without the accompanying
HWE Xstack.

I checked all the documentation I could find and this was clearly not
intentional. In fact the manifest for Ubuntu Focal Beta still used
linux-generic, so this got messed up some time between April 3, 2020 and
April 23, 2020. Here's just one example of the documentation for kernel
support in Focal LTS:

https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle

Installations performed with 20.04 and 20.04.1 media were supposed to
remain on the 5.4 series kernel throughout Focal's 5 year lifespan as
had been the case since HWE was introduced. The first step in fixing
this needs to be stopping fresh installs of Focal using the 20.04 and
20.04.1 media from immediately upgrading to the 5.8 series kernel.

It might be a little tricky to revert users from 5.8 to 5.4, but there
have been reports of breakage, particularly concerning Broadcom wifi
drivers and some graphics problems. But the graphics problems could also
be exacerbated by the lack of the matching HWE Xstack? At any rate it's
a bug.

** Affects: ubuntu-meta (Ubuntu)
 Importance: Undecided
 Status: New

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

Title:
  Ubuntu 20.04 and 20.04.1 images use linux-generic-hwe-20.04 instead of
  linux-generic

Status in ubuntu-meta package in Ubuntu:
  New

Bug description:
  Just as the title says, the 20.04 and 20.04.1 images use the HWE
  version of linux-generic resulting in upgrades to the 5.8 series
  kernel. This seems to effect Ubuntu only, or I should say I checked
  the Kubuntu, Ubuntu Mate, Xubuntu, and Lubuntu iso manifests which all
  correctly list linux-generic. Also HWE is not truly complete without
  the accompanying HWE Xstack.

  I checked all the documentation I could find and this was clearly not
  intentional. In fact the manifest for Ubuntu Focal Beta still used
  linux-generic, so this got messed up some time between April 3, 2020
  and April 23, 2020. Here's just one example of the documentation for
  kernel support in Focal LTS:

  https://ubuntu.com/about/release-cycle#ubuntu-kernel-release-cycle

  Installations performed with 20.04 and 20.04.1 media were supposed to
  remain on the 5.4 series kernel throughout Focal's 5 year lifespan as
  had been the case since HWE was introduced. The first step in fixing
  this needs to be stopping fresh installs of Focal using the 20.04 and
  20.04.1 media from immediately upgrading to the 5.8 series kernel.

  It might be a little tricky to revert users from 5.8 to 5.4, but there
  have been reports of breakage, particularly concerning Broadcom wifi
  drivers and some graphics problems. But the graphics problems could
  also be exacerbated by the lack of the matching HWE Xstack? At any
  rate it's a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1911614/+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 1845898] Re: Unable to set touchpad Edge Scrolling in Eoan

[Erick Brunzell]

Sorry I lumped so much text into one box. I must have been asleep at the
wheel.

I was just setting up another of these today with 18.04.1 and it's also
effected but I know Xenial worked fine out-of-box so I'm just guessing
(with inadequate studying) that the change to GNOME as default resulted
in slightly different dependencies?

It is indeed a low priority bug, or I'm almost hesitant to call it a
true bug since apparently it effects a very limited number of older
laptops.

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

Title:
  Unable to set touchpad Edge Scrolling in Eoan

Status in gnome-control-center package in Ubuntu:
  Incomplete

Bug description:
  After installing the Eoan Beta on a Dell Latitude E6400 attempting to
  set touchpad Edge Scrolling was unsuccessful. It actually seemed to
  work as long as the System Settings window was left open but as soon
  as the window is closed the Edge Scrolling setting reverts to off.

  I did however find that simply installing the package 'xserver-xorg-
  input-synaptics' solves the problem. In fact it adds the additional
  setting option of Two Finger Scrolling to the control center UI. I'm
  not sure if that package should be installed by default or not?

  Steps to reproduce are simple:
  (1) Install Ubuntu Eoan on a laptop (could possibly work with a keyboard with 
an incorporated touchpad).
  (2) Open Gnome Control Center (System Settings) and go to Devices > Mouse & 
Touchpad.
  (3) Select Edge Scrolling and you'll notice the "button" turn green. Close 
System Settings. 
  (4) Reopen System Settings and you'll see Edge Scrolling has turned off again.
  (5) Install 'xserver-xorg-input-synaptics' and then reboot.
  (6) Repeat the above steps and you'll find that setting Edge Scrolling is 
successful even after closing System Settings. Additionally you'll find that a 
new Two Finger Scrolling option has been added to the UI.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.0.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 22:15:09 2019
  InstallationDate: Installed on 2019-09-30 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845898/+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 1845898] Re: Unable to set touchpad Edge Scrolling in Eoan

[Erick Brunzell]

Sorry for the delay. I performed a fresh install of 20191014 last night,
then updated it this AM so we'd be working with an out-of-box
experience. After the update and a reboot I opened System Settings >
Devices > Mouse & Touchpad and changed Natural Scrolling and Tap-to-
click to off while also changing Edge Scrolling to ON.

Opening Test Your Settings indicates that the changes were applied
correctly but immediately after closing System Settings the Edge
Scrolling setting reverts to off. That can be verified both by the
touchpad behavior and reopening the Mouse & Touchpad settings UI. The
other settings changes "stick" as they should.

lance@lance-e6400:~$ journalctl -b 0
-- Logs begin at Mon 2019-10-14 22:46:09 CDT, end at Tue 2019-10-15 15:42:44 CDT
Oct 15 15:33:49 lance-e6400 kernel: microcode: microcode updated early to revisi
Oct 15 15:33:49 lance-e6400 kernel: Linux version 5.3.0-18-generic (buildd@lcy01
Oct 15 15:33:49 lance-e6400 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.3.0
Oct 15 15:33:49 lance-e6400 kernel: KERNEL supported cpus:
Oct 15 15:33:49 lance-e6400 kernel:   Intel GenuineIntel
Oct 15 15:33:49 lance-e6400 kernel:   AMD AuthenticAMD
Oct 15 15:33:49 lance-e6400 kernel:   Hygon HygonGenuine
Oct 15 15:33:49 lance-e6400 kernel:   Centaur CentaurHauls
Oct 15 15:33:49 lance-e6400 kernel:   zhaoxin   Shanghai  
Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x8
Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SS
Oct 15 15:33:49 lance-e6400 kernel: x86/fpu: Enabled xstate features 0x3, contex
Oct 15 15:33:49 lance-e6400 kernel: BIOS-provided physical RAM map:
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x0009f000-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0x0010-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xdd04d400-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xdd04f400-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xf800-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfec0-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfed18000-0x000
Oct 15 15:33:49 lance-e6400 kernel: BIOS-e820: [mem 0xfed2-0x000
 
For the rest of this I attached a Logitech M317 mouse. Here's the requested 
output with out-of-box settings:

lance@lance-e6400:~$ sudo libinput list-devices
[sudo] password for lance: 
Device:   Video Bus
Kernel:   /dev/input/event8
Group:1
Seat: seat0, default
Capabilities: keyboard 
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation: n/a

Device:   Power Button
Kernel:   /dev/input/event1
Group:2
Seat: seat0, default
Capabilities: keyboard 
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation: n/a

Device:   Lid Switch
Kernel:   /dev/input/event0
Group:3
Seat: seat0, default
Capabilities: switch
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation: n/a

Device:   Sleep Button
Kernel:   /dev/input/event2
Group:4
Seat: seat0, default
Capabilities: keyboard 
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation: n/a

Device:   HID 413c:8157
Kernel:   /dev/input/event4
Group:5
Seat: seat0, default
Capabilities: keyboard 
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none
Disable-w-typing: n/a
Accel profiles:   n/a
Rotation: n/a

Device:   HDA Intel Dock Mic
Kernel:   /dev/input/event9
Group:6
Seat: seat0, default
Capabilities: 
Tap-to-click: n/a
Tap-and-drag: n/a
Tap drag lock:n/a
Left-handed:  n/a
Nat.scrolling:n/a
Middle emulation: n/a
Calibration:  n/a
Scroll methods:   none
Click methods:none

[Desktop-packages] [Bug 1743686] Re: File system folder in nautilus Artful/Bionic flashback session does nothing

[Erick Brunzell]

** Tags added: eoan gnome-panel

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

Title:
  File system folder in nautilus Artful/Bionic flashback session does
  nothing

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Go to Places > Computer, left-click to open "Files", then select File
  System either by double-click or right-click + open and nothing
  happens. If you go Places > Home > Other locations and select Computer
  the file system opens as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Tue Jan 16 21:54:39 2018
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock', 'cpu-freq-applet', 'indicator-applet', 
'inhibit-applet', 'menu-button', 'multi-load-applet', 'trash-applet', 
'launcher', 'launcher-0', 'launcher-1']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
   b'org.gnome.gnome-panel.run-dialog' b'history' b"['gufw']"
  InstallationDate: Installed on 2018-01-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1743686/+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 1845898] [NEW] Unable to set touchpad Edge Scrolling in Eoan

[Erick Brunzell]

Public bug reported:

After installing the Eoan Beta on a Dell Latitude E6400 attempting to
set touchpad Edge Scrolling was unsuccessful. It actually seemed to work
as long as the System Settings window was left open but as soon as the
window is closed the Edge Scrolling setting reverts to off.

I did however find that simply installing the package 'xserver-xorg-
input-synaptics' solves the problem. In fact it adds the additional
setting option of Two Finger Scrolling to the control center UI. I'm not
sure if that package should be installed by default or not?

Steps to reproduce are simple:
(1) Install Ubuntu Eoan on a laptop (could possibly work with a keyboard with 
an incorporated touchpad).
(2) Open Gnome Control Center (System Settings) and go to Devices > Mouse & 
Touchpad.
(3) Select Edge Scrolling and you'll notice the "button" turn green. Close 
System Settings. 
(4) Reopen System Settings and you'll see Edge Scrolling has turned off again.
(5) Install 'xserver-xorg-input-synaptics' and then reboot.
(6) Repeat the above steps and you'll find that setting Edge Scrolling is 
successful even after closing System Settings. Additionally you'll find that a 
new Two Finger Scrolling option has been added to the UI.

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: gnome-control-center 1:3.34.0.1-1ubuntu2
ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
Uname: Linux 5.3.0-13-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.20.11-0ubuntu7
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Sun Sep 29 22:15:09 2019
InstallationDate: Installed on 2019-09-30 (0 days ago)
InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug eoan

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

Title:
  Unable to set touchpad Edge Scrolling in Eoan

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  After installing the Eoan Beta on a Dell Latitude E6400 attempting to
  set touchpad Edge Scrolling was unsuccessful. It actually seemed to
  work as long as the System Settings window was left open but as soon
  as the window is closed the Edge Scrolling setting reverts to off.

  I did however find that simply installing the package 'xserver-xorg-
  input-synaptics' solves the problem. In fact it adds the additional
  setting option of Two Finger Scrolling to the control center UI. I'm
  not sure if that package should be installed by default or not?

  Steps to reproduce are simple:
  (1) Install Ubuntu Eoan on a laptop (could possibly work with a keyboard with 
an incorporated touchpad).
  (2) Open Gnome Control Center (System Settings) and go to Devices > Mouse & 
Touchpad.
  (3) Select Edge Scrolling and you'll notice the "button" turn green. Close 
System Settings. 
  (4) Reopen System Settings and you'll see Edge Scrolling has turned off again.
  (5) Install 'xserver-xorg-input-synaptics' and then reboot.
  (6) Repeat the above steps and you'll find that setting Edge Scrolling is 
successful even after closing System Settings. Additionally you'll find that a 
new Two Finger Scrolling option has been added to the UI.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.10
  Package: gnome-control-center 1:3.34.0.1-1ubuntu2
  ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0
  Uname: Linux 5.3.0-13-generic x86_64
  NonfreeKernelModules: wl
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Sun Sep 29 22:15:09 2019
  InstallationDate: Installed on 2019-09-30 (0 days ago)
  InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Beta amd64 (20190926.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1845898/+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 1824588] [NEW] Ubuntu Disco logs out to black screen

[Erick Brunzell]

Public bug reported:

Just testing Disco and wanted to see what login options are available
after adding 'gnome-shell-extensions' and found that logging out lands
me on a black screen that's unresponsive to any keyboard input. I'll
test on some slightly different hardware soon.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gdm3 3.32.0-1ubuntu1
ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
Uname: Linux 5.0.0-8-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 12 16:18:56 2019
InstallationDate: Installed on 2019-04-12 (0 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm3
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm3.custom.conf: 2019-04-12T01:05:45.138523

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


** Tags: amd64 apport-bug disco

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

Title:
  Ubuntu Disco logs out to black screen

Status in gdm3 package in Ubuntu:
  New

Bug description:
  Just testing Disco and wanted to see what login options are available
  after adding 'gnome-shell-extensions' and found that logging out lands
  me on a black screen that's unresponsive to any keyboard input. I'll
  test on some slightly different hardware soon.

  ProblemType: Bug
  DistroRelease: Ubuntu 19.04
  Package: gdm3 3.32.0-1ubuntu1
  ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1
  Uname: Linux 5.0.0-8-generic x86_64
  ApportVersion: 2.20.10-0ubuntu27
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Fri Apr 12 16:18:56 2019
  InstallationDate: Installed on 2019-04-12 (0 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm3
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm3.custom.conf: 2019-04-12T01:05:45.138523

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1824588/+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 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider

[Erick Brunzell]

** Description changed:

  This is intentionally a duplicate of bug #1817485 to collect info on a
  fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
  default session is also effected. I just wanted to collect all pertinent
  logs to prove that this was in fact an unmolested install.
  
  As in the previously filed bug report once over-amplification is
  switched on only the volume slider in the top panel actually increases
- the sound above 100%. Neither the slider in the sound settings UI or the
- keyboard volume hot keys will increase the sound above 100%.
+ the sound above 100%. The slider in the sound settings UI will not
+ increase the sound above 100%. The keyboard hot-keys are also effected
+ in the flashback session, but NOT the default Ubuntu session.
  
- So, in use as an HTPC, if you're streaming content in full screen and
- have the sound set above 100%, when a blaring loud commercial comes on
- and you turn the volume down with the keyboard hot keys you can't use
- the keyboard hot-keys to return to that over-amplified state.
+ So if using the flashback session, in use as an HTPC, if you're
+ streaming content in full screen and have the sound set above 100%, when
+ a blaring loud commercial comes on and you turn the volume down with the
+ keyboard hot keys you can't use the keyboard hot-keys to return to that
+ over-amplified state. In the default Ubuntu session the hot-keys
+ function as expected.
  
  I'm attaching a screenshot. A logout is necessary for the over-
  amplification setting to take effect so the steps to reproduce are as
  follows:
  
  (1) Open System Settings > Sound
  (2) Toggle Over-Amplification to On
  (3) logout and then log back into the default session (this is required)
  (4) Open System Settings > Sound and toggle the volume slider to the left, 
then all the way to the right.
  (5) Click on the volume icon in the top panel and you'll see that it's only 
at about 66% - obviously the two should "sync" but do not
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 25 14:25:01 2019
  InstallationDate: Installed on 2019-02-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Bionic "amplified" sound controls do not sync with volume slider

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  This is intentionally a duplicate of bug #1817485 to collect info on a
  fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
  default session is also effected. I just wanted to collect all
  pertinent logs to prove that this was in fact an unmolested install.

  As in the previously filed bug report once over-amplification is
  switched on only the volume slider in the top panel actually increases
  the sound above 100%. The slider in the sound settings UI will not
  increase the sound above 100%. The keyboard hot-keys are also effected
  in the flashback session, but NOT the default Ubuntu session.

  So if using the flashback session, in use as an HTPC, if you're
  streaming content in full screen and have the sound set above 100%,
  when a blaring loud commercial comes on and you turn the volume down
  with the keyboard hot keys you can't use the keyboard hot-keys to
  return to that over-amplified state. In the default Ubuntu session the
  hot-keys function as expected.

  I'm attaching a screenshot. A logout is necessary for the over-
  amplification setting to take effect so the steps to reproduce are as
  follows:

  (1) Open System Settings > Sound
  (2) Toggle Over-Amplification to On
  (3) logout and then log back into the default session (this is required)
  (4) Open System Settings > Sound and toggle the volume slider to the left, 
then all the way to the right.
  (5) Click on the volume icon in the top panel and you'll see that it's only 
at about 66% - obviously the two should "sync" but do not

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 25 14:25:01 2019
  InstallationDate: Installed on 2019-02-25 (0 days ago)
  

[Desktop-packages] [Bug 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider

[Erick Brunzell]

One more difference between the default and flashback sessions is that
the keyboard hot-keys DO work in the default Ubuntu session, but NOT in
the flashback session. So that makes this even a lower priority, and
passes part of the responsibility onto the flashback devs.

** Tags added: gnome-panel

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

Title:
  Bionic "amplified" sound controls do not sync with volume slider

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  This is intentionally a duplicate of bug #1817485 to collect info on a
  fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
  default session is also effected. I just wanted to collect all
  pertinent logs to prove that this was in fact an unmolested install.

  As in the previously filed bug report once over-amplification is
  switched on only the volume slider in the top panel actually increases
  the sound above 100%. The slider in the sound settings UI will not
  increase the sound above 100%. The keyboard hot-keys are also effected
  in the flashback session, but NOT the default Ubuntu session.

  So if using the flashback session, in use as an HTPC, if you're
  streaming content in full screen and have the sound set above 100%,
  when a blaring loud commercial comes on and you turn the volume down
  with the keyboard hot keys you can't use the keyboard hot-keys to
  return to that over-amplified state. In the default Ubuntu session the
  hot-keys function as expected.

  I'm attaching a screenshot. A logout is necessary for the over-
  amplification setting to take effect so the steps to reproduce are as
  follows:

  (1) Open System Settings > Sound
  (2) Toggle Over-Amplification to On
  (3) logout and then log back into the default session (this is required)
  (4) Open System Settings > Sound and toggle the volume slider to the left, 
then all the way to the right.
  (5) Click on the volume icon in the top panel and you'll see that it's only 
at about 66% - obviously the two should "sync" but do not

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 25 14:25:01 2019
  InstallationDate: Installed on 2019-02-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+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 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider

[Erick Brunzell]

** Description changed:

  This is intentionally a duplicate of bug #1817485 to collect info on a
  fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
  default session is also effected. I just wanted to collect all pertinent
  logs to prove that this was in fact an unmolested install.
  
  As in the previously filed bug report once over-amplification is
  switched on only the volume slider in the top panel actually increases
  the sound above 100%. Neither the slider in the sound settings UI or the
  keyboard volume hot keys will increase the sound above 100%.
  
  So, in use as an HTPC, if you're streaming content in full screen and
  have the sound set above 100%, when a blaring loud commercial comes on
  and you turn the volume down with the keyboard hot keys you can't use
  the keyboard hot-keys to return to that over-amplified state.
  
- I'm attaching a screenshot and I'll also update this with a full step by
- step process to reproduce the bug. Either a reboot or logout is required
- for the changes to take effect after switching over-amplification on (or
- maybe off too). I just need to rinse-n-repeat a few times to be sure so
- you won't have to waste time trying to reproduce.
+ I'm attaching a screenshot. A logout is necessary for the over-
+ amplification setting to take effect so the steps to reproduce are as
+ follows:
+ 
+ (1) Open System Settings > Sound
+ (2) Toggle Over-Amplification to On
+ (3) logout and then log back into the default session (this is required)
+ (4) Open System Settings > Sound and toggle the volume slider to the left, 
then all the way to the right.
+ (5) Click on the volume icon in the top panel and you'll see that it's only 
at about 66% - obviously the two should "sync" but do not
  
  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 25 14:25:01 2019
  InstallationDate: Installed on 2019-02-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Bionic "amplified" sound controls do not sync with volume slider

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  This is intentionally a duplicate of bug #1817485 to collect info on a
  fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
  default session is also effected. I just wanted to collect all
  pertinent logs to prove that this was in fact an unmolested install.

  As in the previously filed bug report once over-amplification is
  switched on only the volume slider in the top panel actually increases
  the sound above 100%. Neither the slider in the sound settings UI or
  the keyboard volume hot keys will increase the sound above 100%.

  So, in use as an HTPC, if you're streaming content in full screen and
  have the sound set above 100%, when a blaring loud commercial comes on
  and you turn the volume down with the keyboard hot keys you can't use
  the keyboard hot-keys to return to that over-amplified state.

  I'm attaching a screenshot. A logout is necessary for the over-
  amplification setting to take effect so the steps to reproduce are as
  follows:

  (1) Open System Settings > Sound
  (2) Toggle Over-Amplification to On
  (3) logout and then log back into the default session (this is required)
  (4) Open System Settings > Sound and toggle the volume slider to the left, 
then all the way to the right.
  (5) Click on the volume icon in the top panel and you'll see that it's only 
at about 66% - obviously the two should "sync" but do not

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 25 14:25:01 2019
  InstallationDate: Installed on 2019-02-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably 

[Desktop-packages] [Bug 1817625] Re: Bionic "amplified" sound controls do not sync with volume slider

[Erick Brunzell]

Actually only a logout is necessary for the UI and volume slider to
respond to the amp change. So I'll add steps to reproduce.

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

Title:
  Bionic "amplified" sound controls do not sync with volume slider

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  This is intentionally a duplicate of bug #1817485 to collect info on a
  fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
  default session is also effected. I just wanted to collect all
  pertinent logs to prove that this was in fact an unmolested install.

  As in the previously filed bug report once over-amplification is
  switched on only the volume slider in the top panel actually increases
  the sound above 100%. Neither the slider in the sound settings UI or
  the keyboard volume hot keys will increase the sound above 100%.

  So, in use as an HTPC, if you're streaming content in full screen and
  have the sound set above 100%, when a blaring loud commercial comes on
  and you turn the volume down with the keyboard hot keys you can't use
  the keyboard hot-keys to return to that over-amplified state.

  I'm attaching a screenshot and I'll also update this with a full step
  by step process to reproduce the bug. Either a reboot or logout is
  required for the changes to take effect after switching over-
  amplification on (or maybe off too). I just need to rinse-n-repeat a
  few times to be sure so you won't have to waste time trying to
  reproduce.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 25 14:25:01 2019
  InstallationDate: Installed on 2019-02-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+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 1817485] Re: Bionic "amplified" sound controls do not sync with volume slider

[Erick Brunzell]

Actually this specific issue effects the default Ubuntu session as well.
I did a fresh install of 18.04.2, installed updates, rebooted, and
checked it out to be sure. Then I filed bug #1817625 so one or the other
needs to be marked a duplicate (and changed back to "new" rather than
"invalid"). I just wanted to collect all the logs so you could see I'm
not pulling your leg about the default Ubuntu session being effected.

I had not realized that the default Ubuntu session had a UI for over-
amplification whereas flashback session does not. Since it can be set
via dconf I'm unlikely to file a new bug report just for that. I should
however check to be sure flashback doesn't "break" things in a default
session. I just got lazy yesterday and filed this bug report from my
workhorse PC rather than using my friends new HTPC.

I'm going to rinse-n-repeat the steps to reproduce this in that
unmolested install of Bionic. It seems that either a reboot or logout is
needed after selecting over-amplification = on.

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

Title:
  Bionic "amplified" sound controls do not sync with volume slider

Status in gnome-control-center package in Ubuntu:
  Invalid

Bug description:
  I'm just setting up my first Bionic HTPC and I notice that if you
  select allow-amplified-volume in dconf that change only applies to the
  volume slider, not to the sound control UI. This results in the volume
  hot-keys not controlling sound above 100%.

  So if you're watching video content in full screen you must ESC, then
  use the volume slider, and then go back to full screen. It makes for
  an unwieldy process so using a different DE becomes a temptation.

  You can see what I'm talking about in the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Sun Feb 24 14:10:03 2019
  InstallationDate: Installed on 2018-01-28 (391 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (193 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817485/+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 1817625] [NEW] Bionic "amplified" sound controls do not sync with volume slider

[Erick Brunzell]

Public bug reported:

This is intentionally a duplicate of bug #1817485 to collect info on a
fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
default session is also effected. I just wanted to collect all pertinent
logs to prove that this was in fact an unmolested install.

As in the previously filed bug report once over-amplification is
switched on only the volume slider in the top panel actually increases
the sound above 100%. Neither the slider in the sound settings UI or the
keyboard volume hot keys will increase the sound above 100%.

So, in use as an HTPC, if you're streaming content in full screen and
have the sound set above 100%, when a blaring loud commercial comes on
and you turn the volume down with the keyboard hot keys you can't use
the keyboard hot-keys to return to that over-amplified state.

I'm attaching a screenshot and I'll also update this with a full step by
step process to reproduce the bug. Either a reboot or logout is required
for the changes to take effect after switching over-amplification on (or
maybe off too). I just need to rinse-n-repeat a few times to be sure so
you won't have to waste time trying to reproduce.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Feb 25 14:25:01 2019
InstallationDate: Installed on 2019-02-25 (0 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-control-center
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug bionic

** Attachment added: "Screenshot from 2019-02-25 14-18-10.png"
   
https://bugs.launchpad.net/bugs/1817625/+attachment/5241665/+files/Screenshot%20from%202019-02-25%2014-18-10.png

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

Title:
  Bionic "amplified" sound controls do not sync with volume slider

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  This is intentionally a duplicate of bug #1817485 to collect info on a
  fresh vanilla install of 18.04.2 after updating to prove that Ubuntu's
  default session is also effected. I just wanted to collect all
  pertinent logs to prove that this was in fact an unmolested install.

  As in the previously filed bug report once over-amplification is
  switched on only the volume slider in the top panel actually increases
  the sound above 100%. Neither the slider in the sound settings UI or
  the keyboard volume hot keys will increase the sound above 100%.

  So, in use as an HTPC, if you're streaming content in full screen and
  have the sound set above 100%, when a blaring loud commercial comes on
  and you turn the volume down with the keyboard hot keys you can't use
  the keyboard hot-keys to return to that over-amplified state.

  I'm attaching a screenshot and I'll also update this with a full step
  by step process to reproduce the bug. Either a reboot or logout is
  required for the changes to take effect after switching over-
  amplification on (or maybe off too). I just need to rinse-n-repeat a
  few times to be sure so you won't have to waste time trying to
  reproduce.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.18.0-15.16~18.04.1-generic 4.18.20
  Uname: Linux 4.18.0-15-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Mon Feb 25 14:25:01 2019
  InstallationDate: Installed on 2019-02-25 (0 days ago)
  InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 
(20190210)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-control-center
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817625/+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 1817485] Re: Bionic "amplified" sound controls do not sync with volume slider

[Erick Brunzell]

Bionic no longer displays allow above 100% in the sound settings UI.

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

Title:
  Bionic "amplified" sound controls do not sync with volume slider

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I'm just setting up my first Bionic HTPC and I notice that if you
  select allow-amplified-volume in dconf that change only applies to the
  volume slider, not to the sound control UI. This results in the volume
  hot-keys not controlling sound above 100%.

  So if you're watching video content in full screen you must ESC, then
  use the volume slider, and then go back to full screen. It makes for
  an unwieldy process so using a different DE becomes a temptation.

  You can see what I'm talking about in the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Sun Feb 24 14:10:03 2019
  InstallationDate: Installed on 2018-01-28 (391 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (193 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817485/+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 1817485] [NEW] Bionic "amplified" sound controls do not sync with volume slider

[Erick Brunzell]

Public bug reported:

I'm just setting up my first Bionic HTPC and I notice that if you select
allow-amplified-volume in dconf that change only applies to the volume
slider, not to the sound control UI. This results in the volume hot-keys
not controlling sound above 100%.

So if you're watching video content in full screen you must ESC, then
use the volume slider, and then go back to full screen. It makes for an
unwieldy process so using a different DE becomes a temptation.

You can see what I'm talking about in the attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
Uname: Linux 4.15.0-45-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
CurrentDesktop: GNOME-Flashback:GNOME
Date: Sun Feb 24 14:10:03 2019
InstallationDate: Installed on 2018-01-28 (391 days ago)
InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
SourcePackage: gnome-control-center
UpgradeStatus: Upgraded to bionic on 2018-08-15 (193 days ago)

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


** Tags: amd64 apport-bug bionic third-party-packages

** Attachment added: "Screenshot from 2019-02-24 14-27-44.png"
   
https://bugs.launchpad.net/bugs/1817485/+attachment/5241405/+files/Screenshot%20from%202019-02-24%2014-27-44.png

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

Title:
  Bionic "amplified" sound controls do not sync with volume slider

Status in gnome-control-center package in Ubuntu:
  New

Bug description:
  I'm just setting up my first Bionic HTPC and I notice that if you
  select allow-amplified-volume in dconf that change only applies to the
  volume slider, not to the sound control UI. This results in the volume
  hot-keys not controlling sound above 100%.

  So if you're watching video content in full screen you must ESC, then
  use the volume slider, and then go back to full screen. It makes for
  an unwieldy process so using a different DE becomes a temptation.

  You can see what I'm talking about in the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2
  ProcVersionSignature: Ubuntu 4.15.0-45.48-generic 4.15.18
  Uname: Linux 4.15.0-45-generic x86_64
  ApportVersion: 2.20.9-0ubuntu7.5
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Sun Feb 24 14:10:03 2019
  InstallationDate: Installed on 2018-01-28 (391 days ago)
  InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 
(20160719)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to bionic on 2018-08-15 (193 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1817485/+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 1743686] Re: File system folder in nautilus Artful/Bionic flashback session does nothing

[Erick Brunzell]

It seems to me that the most sensible approach would be to just remove
the Computer button from the Places menu. Then you'd just open Home and
select Other Locations. I think that would be more in keeping with the
latest Nautilus redesign.

I'm not at all sure but we may want to do likewise with the Network
button in the Places menu because it's now also accessible via Home ->
Other Locations.

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

Title:
  File system folder in nautilus Artful/Bionic flashback session does
  nothing

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Go to Places > Computer, left-click to open "Files", then select File
  System either by double-click or right-click + open and nothing
  happens. If you go Places > Home > Other locations and select Computer
  the file system opens as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Tue Jan 16 21:54:39 2018
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock', 'cpu-freq-applet', 'indicator-applet', 
'inhibit-applet', 'menu-button', 'multi-load-applet', 'trash-applet', 
'launcher', 'launcher-0', 'launcher-1']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
   b'org.gnome.gnome-panel.run-dialog' b'history' b"['gufw']"
  InstallationDate: Installed on 2018-01-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1743686/+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 1749481] Re: Wrong session marked as selected in session dropdown on login screen

[Erick Brunzell]

This may or may not be worth mentioning but the reason I totally purged
lightdm was just using dpkg to change to gdm3 returns an error:

lance@lance-conroe:~$ sudo dpkg-reconfigure gdm3
[sudo] password for lance: 
gdm.service is not active, cannot reload.
invoke-rc.d: initscript gdm3, action "reload" failed.

Of course I could also have run sudo dpkg-reconfigure lightdm and
accomplished the same thing.

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

Title:
  Wrong session marked as selected in session dropdown on login screen

Status in gdm:
  Invalid
Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  My usual session is "Ubuntu" (/usr/share/xsessions/ubuntu.desktop).
  When I reboot my machine, on the login screen if I click the cog icon
  to show the list of sessions available, a dot is displayed to the left
  of the first session in the list ("GNOME"), instead of "Ubuntu".

  If I don't click on a session to change it, when I log in the session
  used is "Ubuntu" as expected, not "GNOME".

  So the greeter fails to reflect which session is actually selected
  when first displaying the dropdown, but internally it doesn't mess up
  with session selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.26.2.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:00:38 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (591 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1749481/+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 1749481] Re: Wrong session marked as selected in session dropdown on login screen

[Erick Brunzell]

I tested again this AM beginning with a fresh install of 20180227,
applying updates, and then installing gnome-panel. During installation I
chose to auto-login so after initially logging out and selecting
flashback w/metacity I still booted the default DE.

But that was expected behavior based on prior testing of Bionic. So I
rebooted, then tried logging out again and selecting flashback
w/metacity and still I just get the default DE. Next I opened the Users
window and turned auto-login off, rebooted and selected flashback
w/metacity but still I just get the default DE.

Those initial results from last night were based on a slightly older
install where I had been using lightdm with the unity greeter, but I
purged lightdm and then autoremoved all leftover depends. Clearly that
didn't give me a clean enough install to produce a reliable result.

Bottom line = it's not fixed.

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

Title:
  Wrong session marked as selected in session dropdown on login screen

Status in gdm:
  Invalid
Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  My usual session is "Ubuntu" (/usr/share/xsessions/ubuntu.desktop).
  When I reboot my machine, on the login screen if I click the cog icon
  to show the list of sessions available, a dot is displayed to the left
  of the first session in the list ("GNOME"), instead of "Ubuntu".

  If I don't click on a session to change it, when I log in the session
  used is "Ubuntu" as expected, not "GNOME".

  So the greeter fails to reflect which session is actually selected
  when first displaying the dropdown, but internally it doesn't mess up
  with session selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.26.2.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:00:38 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (591 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1749481/+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 1749481] Re: Wrong session marked as selected in session dropdown on login screen

[Erick Brunzell]

Works properly to boot both the flashback w/metacity and GNOME Classic
sessions now.

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

Title:
  Wrong session marked as selected in session dropdown on login screen

Status in gdm:
  Invalid
Status in gdm3 package in Ubuntu:
  Incomplete
Status in gnome-session package in Ubuntu:
  Incomplete

Bug description:
  My usual session is "Ubuntu" (/usr/share/xsessions/ubuntu.desktop).
  When I reboot my machine, on the login screen if I click the cog icon
  to show the list of sessions available, a dot is displayed to the left
  of the first session in the list ("GNOME"), instead of "Ubuntu".

  If I don't click on a session to change it, when I log in the session
  used is "Ubuntu" as expected, not "GNOME".

  So the greeter fails to reflect which session is actually selected
  when first displaying the dropdown, but internally it doesn't mess up
  with session selection.

  ProblemType: Bug
  DistroRelease: Ubuntu 18.04
  Package: gdm3 3.26.2.1-2ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
  Uname: Linux 4.13.0-32-generic x86_64
  NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
  ApportVersion: 2.20.8-0ubuntu10
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Wed Feb 14 16:00:38 2018
  EcryptfsInUse: Yes
  InstallationDate: Installed on 2016-07-02 (591 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 
(20160420.1)
  SourcePackage: gdm3
  UpgradeStatus: Upgraded to bionic on 2018-01-29 (16 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/gdm/+bug/1749481/+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 1737836] Re: Standard clock applet is oversized in Artful

[Erick Brunzell]

** Tags added: bionic gnome-applets

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

Title:
  Standard clock applet is oversized in Artful

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  In Artful if the standard clock applet is used there is a dead-space
  to the left of it. In my first screenshot you can see the dead-space
  between the indicator-applet and the clock applet. In the second
  screenshot you can see I've moved the clock applet to the left and the
  same dead-space exists between it and the inhibit-applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Tue Dec 12 15:19:25 2017
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 
'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
  InstallationDate: Installed on 2017-12-11 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+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 1743686] [NEW] File system folder in nautilus Artful/Bionic flashback session does nothing

[Erick Brunzell]

Public bug reported:

Go to Places > Computer, left-click to open "Files", then select File
System either by double-click or right-click + open and nothing happens.
If you go Places > Home > Other locations and select Computer the file
system opens as expected.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-panel 1:3.24.1-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
Uname: Linux 4.13.0-25-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.7
Architecture: amd64
CurrentDesktop: GNOME-Flashback:GNOME
Date: Tue Jan 16 21:54:39 2018
GsettingsChanges:
 b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock', 'cpu-freq-applet', 'indicator-applet', 
'inhibit-applet', 'menu-button', 'multi-load-applet', 'trash-applet', 
'launcher', 'launcher-0', 'launcher-1']"
 b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
 b'org.gnome.gnome-panel.run-dialog' b'history' b"['gufw']"
InstallationDate: Installed on 2018-01-16 (0 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful bionic nautilus

** Tags added: bionic nautilus

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

Title:
  File system folder in nautilus Artful/Bionic flashback session does
  nothing

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  Go to Places > Computer, left-click to open "Files", then select File
  System either by double-click or right-click + open and nothing
  happens. If you go Places > Home > Other locations and select Computer
  the file system opens as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-25.29-generic 4.13.13
  Uname: Linux 4.13.0-25-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.7
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Tue Jan 16 21:54:39 2018
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock', 'cpu-freq-applet', 'indicator-applet', 
'inhibit-applet', 'menu-button', 'multi-load-applet', 'trash-applet', 
'launcher', 'launcher-0', 'launcher-1']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
   b'org.gnome.gnome-panel.run-dialog' b'history' b"['gufw']"
  InstallationDate: Installed on 2018-01-16 (0 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1743686/+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 1737836] Re: Standard clock applet is oversized in Artful

[Erick Brunzell]

Second screenshot.

** Attachment added: "Screenshot from 2017-12-12 15-23-53.png"
   
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+attachment/5021860/+files/Screenshot%20from%202017-12-12%2015-23-53.png

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

Title:
  Standard clock applet is oversized in Artful

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  In Artful if the standard clock applet is used there is a dead-space
  to the left of it. In my first screenshot you can see the dead-space
  between the indicator-applet and the clock applet. In the second
  screenshot you can see I've moved the clock applet to the left and the
  same dead-space exists between it and the inhibit-applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Tue Dec 12 15:19:25 2017
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 
'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
  InstallationDate: Installed on 2017-12-11 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+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 1737836] [NEW] Standard clock applet is oversized in Artful

[Erick Brunzell]

Public bug reported:

In Artful if the standard clock applet is used there is a dead-space to
the left of it. In my first screenshot you can see the dead-space
between the indicator-applet and the clock applet. In the second
screenshot you can see I've moved the clock applet to the left and the
same dead-space exists between it and the inhibit-applet.

ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: gnome-panel 1:3.24.1-1ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
Uname: Linux 4.13.0-19-generic x86_64
ApportVersion: 2.20.7-0ubuntu3.6
Architecture: amd64
CurrentDesktop: GNOME-Flashback:GNOME
Date: Tue Dec 12 15:19:25 2017
GsettingsChanges:
 b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 
'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']"
 b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
InstallationDate: Installed on 2017-12-11 (1 days ago)
InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-panel
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug artful

** Attachment added: "Screenshot from 2017-12-12 15-23-24.png"
   
https://bugs.launchpad.net/bugs/1737836/+attachment/5021856/+files/Screenshot%20from%202017-12-12%2015-23-24.png

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

Title:
  Standard clock applet is oversized in Artful

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  In Artful if the standard clock applet is used there is a dead-space
  to the left of it. In my first screenshot you can see the dead-space
  between the indicator-applet and the clock applet. In the second
  screenshot you can see I've moved the clock applet to the left and the
  same dead-space exists between it and the inhibit-applet.

  ProblemType: Bug
  DistroRelease: Ubuntu 17.10
  Package: gnome-panel 1:3.24.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.13.0-19.22-generic 4.13.13
  Uname: Linux 4.13.0-19-generic x86_64
  ApportVersion: 2.20.7-0ubuntu3.6
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:GNOME
  Date: Tue Dec 12 15:19:25 2017
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock', 'indicator-applet', 'inhibit-applet', 
'menu-button', 'trash-applet', 'launcher', 'launcher-0', 'launcher-1']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
  InstallationDate: Installed on 2017-12-11 (1 days ago)
  InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1737836/+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 1610434] Re: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial

[Erick Brunzell]

"This is because you didn't first upgrade update-manager."

I figured something like that. I was convinced that it must have been an
error on my part after repeating several more tests with no issue. Chalk
that up to either too little (or too much) coffee.

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

Title:
  Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-
  lts-xenial

Status in update-manager package in Ubuntu:
  New
Status in xorg-lts-xenial package in Ubuntu:
  Won't Fix
Status in update-manager source package in Trusty:
  Fix Committed
Status in xorg-lts-xenial source package in Trusty:
  Won't Fix

Bug description:
  Test Case
  -
  1) Install libwayland-egl1-mesa-lts-(utopic|vivid)
  2) Install update-manager from Trusty -proposed
  3) Run hwe-support-status --show-replacements
  4) Ensure libwayland-egl1-mesa-lts-xenial shows up as a replacement

  We should also verify that if libwayland-egl1-mesa-lts-(utopic|vivid)
  is not installed that the equivalent -xenial version is not shown as a
  replacement or installed.

  Updated info; You should be able to reproduce this as follows:

  Step #1: Install Ubuntu GNOME 14.04.2, 14.04.3, or 14.04.4. Boot into
  the fresh installation when complete and apply all available updates
  via UI, then reboot when instructed. It seems important to apply the
  post-install updates via UI rather than using the terminal!

  Step #2: Enable trusty-proposed, update the cache and run "apt-get
  install update-manager". (That will update the components needed to
  display HWE EOL notifications). Then disable trusty-proposed, set
  Notify me of a new release to Never, and update the apt cache again.

  Step #3: Based on recent tests completing step #2 should be enough to
  launch the HWE EOL upgrade notification in which case you just need to
  choose to install the HWE upgrade and reboot when prompted.

  If the HWE EOL notification fails to appear close any open update or
  notifier UI, then from terminal run "apt-get update" followed by
  "update-manager". If the HWE EOL notification still fails to appear
  then I'll have to go back to the drawing board.

  Original content begins here:

  Having updated update-manager from trusty-proposed yesterday I booted
  into Ubuntu GNOME Trusty w/Utopic HWE and update-notifier told me that
  my HWE was EOL so I accepted the upgrade. Everything seemed to
  complete successfully and I was notified to reboot. Upon doing so boot
  freezes with the message "Restoring resolver state". I was unsure what
  package to file this against and since I can't boot that install I was
  unable to file using ubuntu-bug anyway. This freeze occurs whether
  trying to boot the lts-xenial kernel or the older lts-utopic kernel.

  I can collect info as needed, the only useful info I see in the logs
  in from apt/history beginning with the update-manager update yesterday
  and ending with the HWE EOL upgrade just a short time ago:

  Start-Date: 2016-08-04  19:23:23
  Commandline: apt-get install update-manager
  Upgrade: update-manager:i386 (0.196.14, 0.196.15), 
python3-update-manager:i386 (0.196.14, 0.196.15), update-manager-core:i386 
(0.196.14, 0.196.15)
  End-Date: 2016-08-04  19:23:35

  Start-Date: 2016-08-05  13:57:56
  Commandline: aptdaemon role='role-commit-packages' sender=':1.50'
  Install: xserver-xorg-input-synaptics-lts-xenial:i386 
(1.8.2-1ubuntu3~trusty1, automatic), libgl1-mesa-dri-lts-xenial:i386 
(11.2.0-1ubuntu2~trusty1, automatic), xserver-xorg-video-amdgpu-lts-xenial:i386 
(1.1.0-1~trusty1, automatic), libgles2-mesa-lts-xenial:i386 
(11.2.0-1ubuntu2~trusty1), linux-headers-4.4.0-31-generic:i386 
(4.4.0-31.50~14.04.1, automatic), xserver-xorg-video-qxl-lts-xenial:i386 
(0.1.4-3ubuntu3~trusty1, automatic), xserver-xorg-video-savage-lts-xenial:i386 
(2.3.8-1ubuntu3~trusty1, automatic), linux-image-4.4.0-31-generic:i386 
(4.4.0-31.50~14.04.1, automatic), xserver-xorg-video-trident-lts-xenial:i386 
(1.3.7-1build2~trusty1, automatic), 
xserver-xorg-video-siliconmotion-lts-xenial:i386 (1.7.8-1ubuntu6~trusty1, 
automatic), libegl1-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1), 
xserver-xorg-lts-xenial:i386 (7.7+13ubuntu3~trusty2), 
xserver-xorg-input-vmmouse-lts-xenial:i386 (13.1.0-1ubuntu2~trusty1, 
automatic), libglapi-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1, a
 utomatic), xserver-xorg-video-nouveau-lts-xenial:i386 (1.0.12-1build2~trusty1, 
automatic), xserver-xorg-input-wacom-lts-xenial:i386 (0.32.0-0ubuntu3~trusty1, 
automatic), linux-generic-lts-xenial:i386 (4.4.0.31.21), 
xserver-xorg-video-openchrome-lts-xenial:i386 (0.3.3+git20160310-1~trusty1, 
automatic), xserver-xorg-input-all-lts-xenial:i386 (7.7+13ubuntu3~trusty2), 
xserver-xorg-video-neomagic-lts-xenial:i386 (1.2.9-1build2~trusty1, automatic), 
xserver-xorg-video-vesa-lts-xenial:i386 

[Desktop-packages] [Bug 1610434] Re: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial

[Erick Brunzell]

I've run several more tests today and all seems well. I can only assume
that the failure in comment #17 was an error on my part. So I think
we're good to go.

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

Title:
  Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-
  lts-xenial

Status in update-manager package in Ubuntu:
  New
Status in xorg-lts-xenial package in Ubuntu:
  Won't Fix
Status in update-manager source package in Trusty:
  Fix Committed
Status in xorg-lts-xenial source package in Trusty:
  Won't Fix

Bug description:
  Test Case
  -
  1) Install libwayland-egl1-mesa-lts-(utopic|vivid)
  2) Install update-manager from Trusty -proposed
  3) Run hwe-support-status --show-replacements
  4) Ensure libwayland-egl1-mesa-lts-xenial shows up as a replacement

  We should also verify that if libwayland-egl1-mesa-lts-(utopic|vivid)
  is not installed that the equivalent -xenial version is not shown as a
  replacement or installed.

  Updated info; You should be able to reproduce this as follows:

  Step #1: Install Ubuntu GNOME 14.04.2, 14.04.3, or 14.04.4. Boot into
  the fresh installation when complete and apply all available updates
  via UI, then reboot when instructed. It seems important to apply the
  post-install updates via UI rather than using the terminal!

  Step #2: Enable trusty-proposed, update the cache and run "apt-get
  install update-manager". (That will update the components needed to
  display HWE EOL notifications). Then disable trusty-proposed, set
  Notify me of a new release to Never, and update the apt cache again.

  Step #3: Based on recent tests completing step #2 should be enough to
  launch the HWE EOL upgrade notification in which case you just need to
  choose to install the HWE upgrade and reboot when prompted.

  If the HWE EOL notification fails to appear close any open update or
  notifier UI, then from terminal run "apt-get update" followed by
  "update-manager". If the HWE EOL notification still fails to appear
  then I'll have to go back to the drawing board.

  Original content begins here:

  Having updated update-manager from trusty-proposed yesterday I booted
  into Ubuntu GNOME Trusty w/Utopic HWE and update-notifier told me that
  my HWE was EOL so I accepted the upgrade. Everything seemed to
  complete successfully and I was notified to reboot. Upon doing so boot
  freezes with the message "Restoring resolver state". I was unsure what
  package to file this against and since I can't boot that install I was
  unable to file using ubuntu-bug anyway. This freeze occurs whether
  trying to boot the lts-xenial kernel or the older lts-utopic kernel.

  I can collect info as needed, the only useful info I see in the logs
  in from apt/history beginning with the update-manager update yesterday
  and ending with the HWE EOL upgrade just a short time ago:

  Start-Date: 2016-08-04  19:23:23
  Commandline: apt-get install update-manager
  Upgrade: update-manager:i386 (0.196.14, 0.196.15), 
python3-update-manager:i386 (0.196.14, 0.196.15), update-manager-core:i386 
(0.196.14, 0.196.15)
  End-Date: 2016-08-04  19:23:35

  Start-Date: 2016-08-05  13:57:56
  Commandline: aptdaemon role='role-commit-packages' sender=':1.50'
  Install: xserver-xorg-input-synaptics-lts-xenial:i386 
(1.8.2-1ubuntu3~trusty1, automatic), libgl1-mesa-dri-lts-xenial:i386 
(11.2.0-1ubuntu2~trusty1, automatic), xserver-xorg-video-amdgpu-lts-xenial:i386 
(1.1.0-1~trusty1, automatic), libgles2-mesa-lts-xenial:i386 
(11.2.0-1ubuntu2~trusty1), linux-headers-4.4.0-31-generic:i386 
(4.4.0-31.50~14.04.1, automatic), xserver-xorg-video-qxl-lts-xenial:i386 
(0.1.4-3ubuntu3~trusty1, automatic), xserver-xorg-video-savage-lts-xenial:i386 
(2.3.8-1ubuntu3~trusty1, automatic), linux-image-4.4.0-31-generic:i386 
(4.4.0-31.50~14.04.1, automatic), xserver-xorg-video-trident-lts-xenial:i386 
(1.3.7-1build2~trusty1, automatic), 
xserver-xorg-video-siliconmotion-lts-xenial:i386 (1.7.8-1ubuntu6~trusty1, 
automatic), libegl1-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1), 
xserver-xorg-lts-xenial:i386 (7.7+13ubuntu3~trusty2), 
xserver-xorg-input-vmmouse-lts-xenial:i386 (13.1.0-1ubuntu2~trusty1, 
automatic), libglapi-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1, a
 utomatic), xserver-xorg-video-nouveau-lts-xenial:i386 (1.0.12-1build2~trusty1, 
automatic), xserver-xorg-input-wacom-lts-xenial:i386 (0.32.0-0ubuntu3~trusty1, 
automatic), linux-generic-lts-xenial:i386 (4.4.0.31.21), 
xserver-xorg-video-openchrome-lts-xenial:i386 (0.3.3+git20160310-1~trusty1, 
automatic), xserver-xorg-input-all-lts-xenial:i386 (7.7+13ubuntu3~trusty2), 
xserver-xorg-video-neomagic-lts-xenial:i386 (1.2.9-1build2~trusty1, automatic), 
xserver-xorg-video-vesa-lts-xenial:i386 (2.3.4-1build2~trusty1, automatic), 
xserver-xorg-input-evdev-lts-xenial:i386 (2.10.1-1ubuntu2~trusty1, automatic), 

[Desktop-packages] [Bug 1610434] Re: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial

[Erick Brunzell]

I have no idea why I had that previous failure. I've since run two more
tests. One was a repeat test beginning with a fresh install of Ubuntu
GNOME 14.04.3 i386 (just like above) and it worked fine. I ran another
test beginning with a fresh install of Ubuntu GNOME 14.04.2 amd64 and it
also worked just fine. I'm going to run one additional test beginning
with 14.04.4 just to be sure, but I think that one failure must have
been a fluke - or something I did wrong.

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

Title:
  Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-
  lts-xenial

Status in update-manager package in Ubuntu:
  New
Status in xorg-lts-xenial package in Ubuntu:
  Won't Fix
Status in update-manager source package in Trusty:
  Fix Committed
Status in xorg-lts-xenial source package in Trusty:
  Won't Fix

Bug description:
  Test Case
  -
  1) Install libwayland-egl1-mesa-lts-(utopic|vivid)
  2) Install update-manager from Trusty -proposed
  3) Run hwe-support-status --show-replacements
  4) Ensure libwayland-egl1-mesa-lts-xenial shows up as a replacement

  We should also verify that if libwayland-egl1-mesa-lts-(utopic|vivid)
  is not installed that the equivalent -xenial version is not shown as a
  replacement or installed.

  Updated info; You should be able to reproduce this as follows:

  Step #1: Install Ubuntu GNOME 14.04.2, 14.04.3, or 14.04.4. Boot into
  the fresh installation when complete and apply all available updates
  via UI, then reboot when instructed. It seems important to apply the
  post-install updates via UI rather than using the terminal!

  Step #2: Enable trusty-proposed, update the cache and run "apt-get
  install update-manager". (That will update the components needed to
  display HWE EOL notifications). Then disable trusty-proposed, set
  Notify me of a new release to Never, and update the apt cache again.

  Step #3: Based on recent tests completing step #2 should be enough to
  launch the HWE EOL upgrade notification in which case you just need to
  choose to install the HWE upgrade and reboot when prompted.

  If the HWE EOL notification fails to appear close any open update or
  notifier UI, then from terminal run "apt-get update" followed by
  "update-manager". If the HWE EOL notification still fails to appear
  then I'll have to go back to the drawing board.

  Original content begins here:

  Having updated update-manager from trusty-proposed yesterday I booted
  into Ubuntu GNOME Trusty w/Utopic HWE and update-notifier told me that
  my HWE was EOL so I accepted the upgrade. Everything seemed to
  complete successfully and I was notified to reboot. Upon doing so boot
  freezes with the message "Restoring resolver state". I was unsure what
  package to file this against and since I can't boot that install I was
  unable to file using ubuntu-bug anyway. This freeze occurs whether
  trying to boot the lts-xenial kernel or the older lts-utopic kernel.

  I can collect info as needed, the only useful info I see in the logs
  in from apt/history beginning with the update-manager update yesterday
  and ending with the HWE EOL upgrade just a short time ago:

  Start-Date: 2016-08-04  19:23:23
  Commandline: apt-get install update-manager
  Upgrade: update-manager:i386 (0.196.14, 0.196.15), 
python3-update-manager:i386 (0.196.14, 0.196.15), update-manager-core:i386 
(0.196.14, 0.196.15)
  End-Date: 2016-08-04  19:23:35

  Start-Date: 2016-08-05  13:57:56
  Commandline: aptdaemon role='role-commit-packages' sender=':1.50'
  Install: xserver-xorg-input-synaptics-lts-xenial:i386 
(1.8.2-1ubuntu3~trusty1, automatic), libgl1-mesa-dri-lts-xenial:i386 
(11.2.0-1ubuntu2~trusty1, automatic), xserver-xorg-video-amdgpu-lts-xenial:i386 
(1.1.0-1~trusty1, automatic), libgles2-mesa-lts-xenial:i386 
(11.2.0-1ubuntu2~trusty1), linux-headers-4.4.0-31-generic:i386 
(4.4.0-31.50~14.04.1, automatic), xserver-xorg-video-qxl-lts-xenial:i386 
(0.1.4-3ubuntu3~trusty1, automatic), xserver-xorg-video-savage-lts-xenial:i386 
(2.3.8-1ubuntu3~trusty1, automatic), linux-image-4.4.0-31-generic:i386 
(4.4.0-31.50~14.04.1, automatic), xserver-xorg-video-trident-lts-xenial:i386 
(1.3.7-1build2~trusty1, automatic), 
xserver-xorg-video-siliconmotion-lts-xenial:i386 (1.7.8-1ubuntu6~trusty1, 
automatic), libegl1-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1), 
xserver-xorg-lts-xenial:i386 (7.7+13ubuntu3~trusty2), 
xserver-xorg-input-vmmouse-lts-xenial:i386 (13.1.0-1ubuntu2~trusty1, 
automatic), libglapi-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1, a
 utomatic), xserver-xorg-video-nouveau-lts-xenial:i386 (1.0.12-1build2~trusty1, 
automatic), xserver-xorg-input-wacom-lts-xenial:i386 (0.32.0-0ubuntu3~trusty1, 
automatic), linux-generic-lts-xenial:i386 (4.4.0.31.21), 
xserver-xorg-video-openchrome-lts-xenial:i386 (0.3.3+git20160310-1~trusty1, 

[Desktop-packages] [Bug 1610434] Re: Ubuntu GNOME Trusty HWE upgrade fails to install libwayland-egl1-mesa-lts-xenial

[Erick Brunzell]

I still encountered a failure beginning with Ubuntu GNOME Trusty i386
w/Vivid HWE. There was a kernel upgrade prior to performing the HWE
upgrade (most recent prior updates performed on 2016-08-07 followed by
installing update-manager from proposed):

Start-Date: 2016-08-13  09:58:41
Commandline: apt-get dist-upgrade
Install: linux-headers-3.19.0-66:i386 (3.19.0-66.74~14.04.1, automatic), 
linux-headers-3.19.0-66-generic:i386 (3.19.0-66.74~14.04.1, automatic), 
linux-image-3.19.0-66-generic:i386 (3.19.0-66.74~14.04.1, automatic), 
linux-image-extra-3.19.0-66-generic:i386 (3.19.0-66.74~14.04.1, automatic)
Upgrade: nautilus-data:i386 (3.10.1-0ubuntu9.9, 3.10.1-0ubuntu9.11), 
modemmanager:i386 (1.0.0-2ubuntu1, 1.0.0-2ubuntu1.1), initramfs-tools:i386 
(0.103ubuntu4.3, 0.103ubuntu4.4), linux-generic-lts-vivid:i386 (3.19.0.65.47, 
3.19.0.66.48), libmm-glib0:i386 (1.0.0-2ubuntu1, 1.0.0-2ubuntu1.1), 
firefox:i386 (47.0+build3-0ubuntu0.14.04.1, 48.0+build2-0ubuntu0.14.04.1), 
libgd3:i386 (2.1.0-3ubuntu0.2, 2.1.0-3ubuntu0.3), libdrm-intel1:i386 
(2.4.64-1~ubuntu14.04.1, 2.4.67-1ubuntu0.14.04.1), avahi-autoipd:i386 
(0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), libcurl3:i386 (7.35.0-1ubuntu2.6, 
7.35.0-1ubuntu2.8), oxideqt-codecs-extra:i386 (1.15.8-0ubuntu0.14.04.1, 
1.16.5-0ubuntu0.14.04.1), grub-common:i386 (2.02~beta2-9ubuntu1.11, 
2.02~beta2-9ubuntu1.12), libdrm-radeon1:i386 (2.4.64-1~ubuntu14.04.1, 
2.4.67-1ubuntu0.14.04.1), nautilus:i386 (3.10.1-0ubuntu9.9, 
3.10.1-0ubuntu9.11), isc-dhcp-client:i386 (4.2.4-7ubuntu12.4, 
4.2.4-7ubuntu12.5), grub-pc:i386 (2.02~beta2-9ubuntu1.11, 
2.02~beta2-9ubuntu1.12), libnaut
 ilus-extension1a:i386 (3.10.1-0ubuntu9.9, 3.10.1-0ubuntu9.11), 
libavahi-common-data:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), libxrandr2:i386 
(1.4.2-1, 1.5.0-1~trusty1), libavahi-client3:i386 (0.6.31-4ubuntu1, 
0.6.31-4ubuntu1.1), libdrm2:i386 (2.4.64-1~ubuntu14.04.1, 
2.4.67-1ubuntu0.14.04.1), base-files:i386 (7.2ubuntu5.4, 7.2ubuntu5.5), 
language-pack-gnome-en:i386 (14.04+20150219, 14.04+20160720), 
libavahi-common3:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), 
libdrm-nouveau2:i386 (2.4.64-1~ubuntu14.04.1, 2.4.67-1ubuntu0.14.04.1), 
language-pack-en:i386 (14.04+20150219, 14.04+20160720), linux-libc-dev:i386 
(3.13.0-92.139, 3.13.0-93.140), avahi-utils:i386 (0.6.31-4ubuntu1, 
0.6.31-4ubuntu1.1), grub2-common:i386 (2.02~beta2-9ubuntu1.11, 
2.02~beta2-9ubuntu1.12), avahi-daemon:i386 (0.6.31-4ubuntu1, 
0.6.31-4ubuntu1.1), grub-pc-bin:i386 (2.02~beta2-9ubuntu1.11, 
2.02~beta2-9ubuntu1.12), libavahi-gobject0:i386 (0.6.31-4ubuntu1, 
0.6.31-4ubuntu1.1), libcurl3-gnutls:i386 (7.35.0-1ubuntu2.6, 7.35.0
 -1ubuntu2.8), libavahi-glib1:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1), 
language-pack-en-base:i386 (14.04+20150219, 14.04+20160720), 
initramfs-tools-bin:i386 (0.103ubuntu4.3, 0.103ubuntu4.4), 
firefox-locale-en:i386 (47.0+build3-0ubuntu0.14.04.1, 
48.0+build2-0ubuntu0.14.04.1), isc-dhcp-common:i386 (4.2.4-7ubuntu12.4, 
4.2.4-7ubuntu12.5), linux-headers-generic-lts-vivid:i386 (3.19.0.65.47, 
3.19.0.66.48), linux-image-generic-lts-vivid:i386 (3.19.0.65.47, 3.19.0.66.48), 
language-pack-gnome-en-base:i386 (14.04+20150219, 14.04+20160720), 
libavahi-core7:i386 (0.6.31-4ubuntu1, 0.6.31-4ubuntu1.1)
End-Date: 2016-08-13  10:31:06

I didn't see anything odd in hwe-support-status so accepted the upgrade:

Start-Date: 2016-08-13  11:02:05
Commandline: aptdaemon role='role-commit-packages' sender=':1.82'
Install: xserver-xorg-input-synaptics-lts-xenial:i386 (1.8.2-1ubuntu3~trusty1, 
automatic), libgl1-mesa-dri-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1, 
automatic), xserver-xorg-video-amdgpu-lts-xenial:i386 (1.1.0-1~trusty1, 
automatic), linux-headers-4.4.0-34-generic:i386 (4.4.0-34.53~14.04.1, 
automatic), libgles2-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1), 
xserver-xorg-video-qxl-lts-xenial:i386 (0.1.4-3ubuntu3~trusty1, automatic), 
xserver-xorg-video-savage-lts-xenial:i386 (2.3.8-1ubuntu3~trusty1, automatic), 
xserver-xorg-video-trident-lts-xenial:i386 (1.3.7-1build2~trusty1, automatic), 
xserver-xorg-video-siliconmotion-lts-xenial:i386 (1.7.8-1ubuntu6~trusty1, 
automatic), libegl1-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~trusty1), 
xserver-xorg-lts-xenial:i386 (7.7+13ubuntu3~trusty2), 
xserver-xorg-input-vmmouse-lts-xenial:i386 (13.1.0-1ubuntu2~trusty1, 
automatic), xserver-xorg-video-r128-lts-xenial:i386 (6.10.0-1build2~trusty1, 
automatic), libglapi-mesa-lts-xenial:i386 (11.2.0-1ubuntu2~tru
 sty1, automatic), xserver-xorg-video-nouveau-lts-xenial:i386 
(1.0.12-1build2~trusty1, automatic), xserver-xorg-input-wacom-lts-xenial:i386 
(0.32.0-0ubuntu3~trusty1, automatic), linux-generic-lts-xenial:i386 
(4.4.0.34.24), xserver-xorg-video-openchrome-lts-xenial:i386 
(0.3.3+git20160310-1~trusty1, automatic), 
xserver-xorg-input-all-lts-xenial:i386 (7.7+13ubuntu3~trusty2), 
xserver-xorg-video-neomagic-lts-xenial:i386 (1.2.9-1build2~trusty1, automatic), 
xserver-xorg-video-vesa-lts-xenial:i386 (2.3.4-1build2~trusty1, automatic), 

[Desktop-packages] [Bug 1539597] Re: nvidia-304 fails to install properly causing unity-control-center to crash

[Erick Brunzell]

@ andyczerwonka, you need to file a new bug report. Since you mention
both nVidia and Intel I assume you have hybrid graphics which presents a
whole different situation.

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

Title:
  nvidia-304 fails to install properly causing unity-control-center to
  crash

Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  I get this crash trying to open System Settings in Xenial. The System
  Settings UI fails to open and apport takes over.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160119-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jan 29 07:27:47 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-11-10 (80 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  ProcCmdline: unity-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc5ad919809:mov0xd8(%rdi),%rbx
   PC (0x7fc5ad919809) ok
   source "0xd8(%rdi)" (0x00d8) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: unity-control-center crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1539597/+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 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)

[Erick Brunzell]

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

** This bug has been marked a duplicate of bug 1584509
   hybrid CDs/DVDs not mounted in xenial

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

Title:
  16.04 some dvd do not mount automatically (but do in 14.04)

Status in gvfs package in Ubuntu:
  Invalid
Status in nautilus package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  here is a dvd. And ubuntu 16.04.

  When I insert that dvd, it does not show anywhere, neither in launcher
  nor in nautilus.

  But I'm able to read that dvd using vlc through menu media / open a
  disc.

  I can manually mount that dvd with

  sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/

  Once mounted there's a dvd icon in launcher and it appears also in
  nautilus left panel.

  That same dvd automatically mounts when running ubuntu 14.04 on the
  same computer.

  I have also tested other dvd's on ubuntu 16.04 and *most* of them show
  / mount as expected.

  But *all* of them automatically show / mount in ubuntu 14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1577768/+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 1539597] Re: nvidia-304 fails to install properly causing unity-control-center to crash

[Erick Brunzell]

This has no longer been an issue since 16.04 final was released so
marking it invalid.

** Changed in: unity-control-center (Ubuntu)
   Status: New => Invalid

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

Title:
  nvidia-304 fails to install properly causing unity-control-center to
  crash

Status in unity-control-center package in Ubuntu:
  Invalid

Bug description:
  I get this crash trying to open System Settings in Xenial. The System
  Settings UI fails to open and apport takes over.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160119-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jan 29 07:27:47 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-11-10 (80 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  ProcCmdline: unity-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc5ad919809:mov0xd8(%rdi),%rbx
   PC (0x7fc5ad919809) ok
   source "0xd8(%rdi)" (0x00d8) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: unity-control-center crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1539597/+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 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)

[Erick Brunzell]

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

** Changed in: util-linux (Ubuntu)
   Status: New => Confirmed

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

Title:
  16.04 some dvd do not mount automatically (but do in 14.04)

Status in gvfs package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed
Status in util-linux package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here is a dvd. And ubuntu 16.04.

  When I insert that dvd, it does not show anywhere, neither in launcher
  nor in nautilus.

  But I'm able to read that dvd using vlc through menu media / open a
  disc.

  I can manually mount that dvd with

  sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/

  Once mounted there's a dvd icon in launcher and it appears also in
  nautilus left panel.

  That same dvd automatically mounts when running ubuntu 14.04 on the
  same computer.

  I have also tested other dvd's on ubuntu 16.04 and *most* of them show
  / mount as expected.

  But *all* of them automatically show / mount in ubuntu 14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1577768/+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 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)

[Erick Brunzell]

** Tags added: util-linux

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

Title:
  16.04 some dvd do not mount automatically (but do in 14.04)

Status in gvfs package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here is a dvd. And ubuntu 16.04.

  When I insert that dvd, it does not show anywhere, neither in launcher
  nor in nautilus.

  But I'm able to read that dvd using vlc through menu media / open a
  disc.

  I can manually mount that dvd with

  sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/

  Once mounted there's a dvd icon in launcher and it appears also in
  nautilus left panel.

  That same dvd automatically mounts when running ubuntu 14.04 on the
  same computer.

  I have also tested other dvd's on ubuntu 16.04 and *most* of them show
  / mount as expected.

  But *all* of them automatically show / mount in ubuntu 14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1577768/+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 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)

[Erick Brunzell]

I wonder why we stopped checking regular mtab:

util-linux (2.27.1-1) unstable; urgency=medium

  * Imported Upstream version 2.27.1
- among other things includes these fixes:
  libmount: fix uid= and gid= translation (Closes: #801527)
  libmount: (monitor) don't check for regular mtab

 -- Andreas Henriksson   Mon, 02 Nov 2015 12:41:58
+0100

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

Title:
  16.04 some dvd do not mount automatically (but do in 14.04)

Status in gvfs package in Ubuntu:
  Confirmed
Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here is a dvd. And ubuntu 16.04.

  When I insert that dvd, it does not show anywhere, neither in launcher
  nor in nautilus.

  But I'm able to read that dvd using vlc through menu media / open a
  disc.

  I can manually mount that dvd with

  sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/

  Once mounted there's a dvd icon in launcher and it appears also in
  nautilus left panel.

  That same dvd automatically mounts when running ubuntu 14.04 on the
  same computer.

  I have also tested other dvd's on ubuntu 16.04 and *most* of them show
  / mount as expected.

  But *all* of them automatically show / mount in ubuntu 14.04.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1577768/+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 1577768] Re: 16.04 some dvd do not mount automatically (but do in 14.04)

[Erick Brunzell]

Might this be a duplicate of bug 1537918?

I'm far from having anything figured out but wonder if there is an issue
with UDF support in both the 4.2 and 4.4 series kernels? Or maybe this
is just a gvfs or fuse problem?

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

Title:
  16.04 some dvd do not mount automatically (but do in 14.04)

Status in gvfs package in Ubuntu:
  Confirmed

Bug description:
  Hi,

  here is a dvd. And ubuntu 16.04.

  When I insert that dvd, it does not show anywhere, neither in launcher
  nor in nautilus.

  But I'm able to read that dvd using vlc through menu media / open a
  disc.

  I can manually mount that dvd with

  sudo mount -t iso9660 -o ro /dev/sr0 ~/Bureau/dvd/

  Once mounted there's a dvd icon in launcher and it appears also in
  nautilus left panel.

  That same dvd automatically mounts when running ubuntu 14.04 on the
  same computer.

  I have also tested other dvd's on ubuntu 16.04 and *most* of them show
  / mount as expected.

  But *all* of them automatically show / mount in ubuntu 14.04.

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

[Erick Brunzell]

It's an umbrella rather than a specific package, so:

lance@lance-AMD-desktop:~$ apt-cache policy xorg-lts*
xserver-xorg-lts-vivid:
  Installed: (none)
  Candidate: 3:10
  Version table:
 3:10 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
xserver-xorg-lts-wily:
  Installed: (none)
  Candidate: 3:10
  Version table:
 3:10 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
xserver-xorg-lts-utopic:
  Installed: (none)
  Candidate: 3:10
  Version table:
 3:10 500
500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages

-- 
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 1571677] Re: upgrading caused a broken apt cache due to *-lts-vivid packages conflicting with current X packages

[Erick Brunzell]

I suspect bug 1561420 is also a duplicate.

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

Title:
  upgrading caused a broken apt cache due to *-lts-vivid packages
  conflicting with current X packages

Status in xorg-lts-transitional package in Ubuntu:
  Incomplete

Bug description:
  I upgraded from a 14.04 release that had the various *-lts-vivid
  packages installed to 16.04 using do-release-upgrade -d.

  After upgrading the apt cache is busted because none of the meta and
  xorg-core packages can get installed.

  t@t-XPS-13-9350:/var/crash$ sudo apt upgrade
  [sudo] password for t: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  Calculating upgrade... Done
  Some packages could not be installed. This may mean that you have
  requested an impossible situation or if you are using the unstable
  distribution that some required packages have not yet been created
  or been moved out of Incoming.
  The following information may help to resolve the situation:

  The following packages have unmet dependencies:
   libgl1-mesa-dri-lts-vivid : Conflicts: libgl1-mesa-dri
   xserver-xorg-core-lts-vivid : Conflicts: xserver-xorg-core
 Conflicts: xserver-xorg-video-modesetting
   xserver-xorg-lts-vivid : Conflicts: libgl1-mesa-dri (>= 0~)
Conflicts: libxatracker2 (>= 0~)
Conflicts: xserver-xorg
Conflicts: xserver-xorg-core (>= 0~)
Conflicts: xserver-xorg-video-all (>= 0~) but 
1:7.7+13ubuntu3 is to be installed
Recommends: xserver-xorg-input-all-lts-vivid but it 
is not installable
Recommends: xserver-xorg-video-all-lts-vivid but it 
is not installable
Recommends: libegl1-mesa-drivers-lts-vivid but it 
is not installable
Recommends: libgles2-mesa-lts-vivid but it is not 
installable
Recommends: libgles1-mesa-lts-vivid but it is not 
installable
  E: Broken packages

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: ubuntu-release-upgrader-core 1:16.04.11
  ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
  Uname: Linux 4.4.0-18-generic x86_64
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CrashDB: ubuntu
  CurrentDesktop: Unity
  Date: Mon Apr 18 09:14:22 2016
  DistributionChannelDescriptor:
   # This is a distribution channel descriptor
   # For more information see 
http://wiki.ubuntu.com/DistributionChannelDescriptor
   canonical-oem-somerville-trusty-amd64-osp1-20150720-0
  InstallationDate: Installed on 2016-04-03 (14 days ago)
  InstallationMedia: Ubuntu 14.04 "Trusty" - Build amd64 LIVE Binary 
20150720-04:06
  PackageArchitecture: all
  SourcePackage: ubuntu-release-upgrader
  Symptom: ubuntu-release-upgrader
  UpgradeStatus: Upgraded to xenial on 2016-04-18 (0 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-lts-transitional/+bug/1571677/+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 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

** Changed in: xserver-xorg-video-intel (Ubuntu)
 Assignee: Kyle Brophy (kylebrophy) => (unassigned)

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  version.xserver-xorg-video-ati: xserver-xorg-video-ati 

[Desktop-packages] [Bug 1274740] Re: Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too

[Erick Brunzell]

I opened bug 1565780 to address the missing nautilus preferences menu in
Xenial.

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

Title:
  Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hello and thank you for maintaining Nautilus packages,

  I'm using Ubuntu on a Cairo-Dock session. With the latest version of 
Nautilus, we have the new titlebar (CSD) specially made for Gnome-Shell.
  Is it maybe possible to re-enable the traditional titlebar on 
'gnome-but-not-shell' sessions too? (and then only use the new titlebar on 
Gnome-Shell sessions)

  On my session, XDG_CURRENT_DESKTOP=GNOME but DESKTOP_SESSION=cairo-
  dock

  Best Regards,

  Matt

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 30 23:43:46 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'where', 'group', 'permissions', 
'owner', 'mime_type']"
  InstallationDate: Installed on 2011-08-10 (904 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1274740/+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 1565780] [NEW] Xenial flashback session lacks access to nautilus preferences menu

[Erick Brunzell]

Public bug reported:

As the title says, the nautilus preferences menu can't be accessed in
the flashback session. You can't edit a number of settings without going
to dconf-editor of playing with gsettings. Just a few examples:

#1: Can't change sort folders before files setting
#2: Can't change number of clicks needed to open files/folders
#3: Can't change icon caption settings
#4: Can't change order of information settings for list view
#5: Can't change preview settings

In a GNOME Shell session the preferences menu is accessed by right
clicking the nautilus tab in the window list while nautilus is open. In
Unity it's accessed by clicking on Edit in the menu bar. Flashback lacks
the ability to do either.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-panel 1:3.18.2-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
Uname: Linux 4.4.0-16-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Mon Apr  4 07:50:27 2016
GsettingsChanges:
 b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock-applet', 'sensors-applet', 'indicator-applet', 
'menu-button', 'trash-applet', 'inhibit-applet', 'launcher', 'launcher-0', 
'launcher-1', 'cpu-freq-applet']"
 b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
 b'org.gnome.gnome-panel.run-dialog' b'show-program-list' b'true'
 b'org.gnome.gnome-panel.run-dialog' b'history' b"['xrandr']"
InstallationDate: Installed on 2015-11-10 (146 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
SourcePackage: gnome-panel
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug third-party-packages xenial

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

Title:
  Xenial flashback session lacks access to nautilus preferences menu

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  As the title says, the nautilus preferences menu can't be accessed in
  the flashback session. You can't edit a number of settings without
  going to dconf-editor of playing with gsettings. Just a few examples:

  #1: Can't change sort folders before files setting
  #2: Can't change number of clicks needed to open files/folders
  #3: Can't change icon caption settings
  #4: Can't change order of information settings for list view
  #5: Can't change preview settings

  In a GNOME Shell session the preferences menu is accessed by right
  clicking the nautilus tab in the window list while nautilus is open.
  In Unity it's accessed by clicking on Edit in the menu bar. Flashback
  lacks the ability to do either.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-panel 1:3.18.2-1ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-16.32-generic 4.4.6
  Uname: Linux 4.4.0-16-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.20.1-0ubuntu1
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Mon Apr  4 07:50:27 2016
  GsettingsChanges:
   b'org.gnome.gnome-panel.layout' b'object-id-list' b"['window-list', 
'workspace-switcher', 'clock-applet', 'sensors-applet', 'indicator-applet', 
'menu-button', 'trash-applet', 'inhibit-applet', 'launcher', 'launcher-0', 
'launcher-1', 'cpu-freq-applet']"
   b'org.gnome.gnome-panel.layout' b'toplevel-id-list' b"['bottom-panel']"
   b'org.gnome.gnome-panel.run-dialog' b'show-program-list' b'true'
   b'org.gnome.gnome-panel.run-dialog' b'history' b"['xrandr']"
  InstallationDate: Installed on 2015-11-10 (146 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1565780/+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 1487819] Re: Wily user UI shows auto-login off after selecting on during install

[Erick Brunzell]

In Wily if you set auto login to on during installation the first boot
would ask for a password. Then if you checked the user UI in System
Settings it said it was turned on but it wasn't. So if you toggled it
off, then rebooted, then opened the user UI again and toggled it on the
auto login would begin working.

In Xenial it just doesn't work at all.

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

Title:
  Wily user UI shows auto-login off after selecting on during install

Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  Just testing Ubuntu GNOME Wily 20150822 i386 and I've noticed that in
  spite of selecting auto-login = on during installation when the
  installation is complete and after first boot opening Settings > Users
  the UI shows off, but auto-login is working properly and if you toggle
  the UI back and forth from off to on a couple of times it seems to
  start working properly.

  I also installed Ubuntu 20150822 i386 and it's not affected so I
  suspect this is either a bug in gdm or possibly in g-c-c or g-s-d.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gdm 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic i686
  ApportVersion: 2.18-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Aug 22 23:04:29 2015
  InstallationDate: Installed on 2015-08-23 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 (20150822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.custom.conf: 2015-08-22T21:20:12.826508

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1487819/+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 1059872] Re: Error formatting disk using disk utility

[Erick Brunzell]

@ Phillip Susi, if that's an indication that this bug won't be fixed in
Trusty then please change the status from Triaged to Won't fix.

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

Title:
  Error formatting disk using disk utility

Status in DarGUI:
  New
Status in OEM Priority Project:
  New
Status in udisks2 package in Ubuntu:
  Invalid
Status in util-linux package in Ubuntu:
  Fix Released
Status in util-linux source package in Trusty:
  Triaged
Status in util-linux package in Debian:
  Fix Released

Bug description:
  [Impact]

  Formatting a SD card using the disk utility fails with an error
  message

  "Error formatting disk - Error synchronizing after initial wipe: Timed
  out waiting for object (udisks-error-quark, 0)"

  The underlying problem is that the "wipefs" tool from util-linux does
  not work any more.

  You can work around this bug in gnome-disk-utility using these steps:

  * After selecting the SD card, instead of clicking the gear icon to format,
click the partition in the "Volumes" section.

  * Delete the partition ("minus" icon)

  * Create a new partition

  [Test Case]

  $ sudo modprobe scsi_debug dev_size_mb=200
  # this creates a new /dev/sdX, usually /dev/sdb; check dmesg!

  # now create a partition table
  $ cat 

[Desktop-packages] [Bug 1487819] Re: Wily user UI shows auto-login off after selecting on during install

[Erick Brunzell]

It's OK in Ubuntu Xenial. Do I really need to install and check Ubuntu
Wily?

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

Title:
  Wily user UI shows auto-login off after selecting on during install

Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  Just testing Ubuntu GNOME Wily 20150822 i386 and I've noticed that in
  spite of selecting auto-login = on during installation when the
  installation is complete and after first boot opening Settings > Users
  the UI shows off, but auto-login is working properly and if you toggle
  the UI back and forth from off to on a couple of times it seems to
  start working properly.

  I also installed Ubuntu 20150822 i386 and it's not affected so I
  suspect this is either a bug in gdm or possibly in g-c-c or g-s-d.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gdm 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic i686
  ApportVersion: 2.18-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Aug 22 23:04:29 2015
  InstallationDate: Installed on 2015-08-23 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 (20150822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.custom.conf: 2015-08-22T21:20:12.826508

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1487819/+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 1274740] Re: Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too

[Erick Brunzell]

Since in a normal GNOME session you access "preferences" and some other
things by right-clicking on the nautilus tab in the top bar when
nautilus is open, how would that be accessible in gnome-flashback?

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

Title:
  Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hello and thank you for maintaining Nautilus packages,

  I'm using Ubuntu on a Cairo-Dock session. With the latest version of 
Nautilus, we have the new titlebar (CSD) specially made for Gnome-Shell.
  Is it maybe possible to re-enable the traditional titlebar on 
'gnome-but-not-shell' sessions too? (and then only use the new titlebar on 
Gnome-Shell sessions)

  On my session, XDG_CURRENT_DESKTOP=GNOME but DESKTOP_SESSION=cairo-
  dock

  Best Regards,

  Matt

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 30 23:43:46 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'where', 'group', 'permissions', 
'owner', 'mime_type']"
  InstallationDate: Installed on 2011-08-10 (904 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1274740/+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 1274740] Re: Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too

[Erick Brunzell]

@ Tim Lunn, there is another nautilus bug that affects both gnome-shell
and gnome-flashback, bug #1554171.

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

Title:
  Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hello and thank you for maintaining Nautilus packages,

  I'm using Ubuntu on a Cairo-Dock session. With the latest version of 
Nautilus, we have the new titlebar (CSD) specially made for Gnome-Shell.
  Is it maybe possible to re-enable the traditional titlebar on 
'gnome-but-not-shell' sessions too? (and then only use the new titlebar on 
Gnome-Shell sessions)

  On my session, XDG_CURRENT_DESKTOP=GNOME but DESKTOP_SESSION=cairo-
  dock

  Best Regards,

  Matt

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 30 23:43:46 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'where', 'group', 'permissions', 
'owner', 'mime_type']"
  InstallationDate: Installed on 2011-08-10 (904 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1274740/+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 1274740] Re: Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too

[Erick Brunzell]

Sorry Tim, I forgot to mention this is a flashback problem. I brought
the issue up on their mailing list.

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

Title:
  Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hello and thank you for maintaining Nautilus packages,

  I'm using Ubuntu on a Cairo-Dock session. With the latest version of 
Nautilus, we have the new titlebar (CSD) specially made for Gnome-Shell.
  Is it maybe possible to re-enable the traditional titlebar on 
'gnome-but-not-shell' sessions too? (and then only use the new titlebar on 
Gnome-Shell sessions)

  On my session, XDG_CURRENT_DESKTOP=GNOME but DESKTOP_SESSION=cairo-
  dock

  Best Regards,

  Matt

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 30 23:43:46 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'where', 'group', 'permissions', 
'owner', 'mime_type']"
  InstallationDate: Installed on 2011-08-10 (904 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1274740/+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 1274740] Re: Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too

[Erick Brunzell]

I notice that Nautilus > preferences can't be accessed in Xenial, sort
of like Nautilus should be using the Unity style menus rather than those
used by gnome-shell???

As far as I've seen ATM only Nautilus is affected by that in Xenial but
I need to have a closer look at some of the other GNOME specific apps to
be certain of that.

** Tags added: xenial

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

Title:
  Re-enable traditional titlebar on 'gnome-but-not-shell' sessions too

Status in nautilus package in Ubuntu:
  Confirmed

Bug description:
  Hello and thank you for maintaining Nautilus packages,

  I'm using Ubuntu on a Cairo-Dock session. With the latest version of 
Nautilus, we have the new titlebar (CSD) specially made for Gnome-Shell.
  Is it maybe possible to re-enable the traditional titlebar on 
'gnome-but-not-shell' sessions too? (and then only use the new titlebar on 
Gnome-Shell sessions)

  On my session, XDG_CURRENT_DESKTOP=GNOME but DESKTOP_SESSION=cairo-
  dock

  Best Regards,

  Matt

  ProblemType: Bug
  DistroRelease: Ubuntu 14.04
  Package: nautilus 1:3.10.1-0ubuntu2
  ProcVersionSignature: Ubuntu 3.13.0-5.20-generic 3.13.0
  Uname: Linux 3.13.0-5-generic x86_64
  ApportVersion: 2.13.2-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Thu Jan 30 23:43:46 2014
  GsettingsChanges: b'org.gnome.nautilus.list-view' b'default-column-order' 
b"['name', 'size', 'type', 'date_modified', 'where', 'group', 'permissions', 
'owner', 'mime_type']"
  InstallationDate: Installed on 2011-08-10 (904 days ago)
  InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110803.1)
  SourcePackage: nautilus
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1274740/+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 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

@ jerrylamos, which HWE stack is in use? It mostly depends on what
installation media is used (unless physical action is taken to upgrade
the HWE stack):

https://wiki.ubuntu.com/Kernel/LTSEnablementStack#Kernel.2FSupport.A14.04.x_Ubuntu_Kernel_Support

Based on my most recent results it seemed to be more of a kernel issue
than X itself.

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Fix Released

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: 

[Desktop-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs

[Erick Brunzell]

** Tags added: xenial

** Tags added: gvfs

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating "Unable to mount Blank disc. Location is
  already mounted". Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+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 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

Xenial looks good testing Ubuntu GNOME 20160218 amd64:

ubuntu-gnome@ubuntu-gnome:~$ uname -a
Linux ubuntu-gnome 4.4.0-6-generic #21-Ubuntu SMP Tue Feb 16 20:32:27 UTC 2016 
x86_64 x86_64 x86_64 GNU/Linux
ubuntu-gnome@ubuntu-gnome:~$ apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.99.917+git20160127-1ubuntu1
  Candidate: 2:2.99.917+git20160127-1ubuntu1
  Version table:
 *** 2:2.99.917+git20160127-1ubuntu1 500
500 http://archive.ubuntu.com/ubuntu xenial/main amd64 Packages
100 /var/lib/dpkg/status
ubuntu-gnome@ubuntu-gnome:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:Ubuntu Xenial Xerus (development branch)
Release:16.04
Codename:   xenial

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  

[Desktop-packages] [Bug 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

It took a considerable amount of searching but the sna vs uxa issue does
have at least two upstream bug reports:

https://bugzilla.redhat.com/show_bug.cgi?id=1226531

https://bugzilla.redhat.com/show_bug.cgi?id=1226743

I believe that should be sufficient. It's a known issue. I'll have to
look at these newer (proposed) kernel changelogs to see if I can figure
what exactly they changed.

** Bug watch added: Red Hat Bugzilla #1226531
   https://bugzilla.redhat.com/show_bug.cgi?id=1226531

** Bug watch added: Red Hat Bugzilla #1226743
   https://bugzilla.redhat.com/show_bug.cgi?id=1226743

** Changed in: xserver-xorg-video-intel (Ubuntu)
   Status: Incomplete => Confirmed

** Tags added: linux

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Confirmed

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 

[Desktop-packages] [Bug 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

Ubuntu Trusty 20160217 amd64 is still affected so I doubt that a fix
will land for 14.04.4. That will be problematic for less advanced users
affected because both the Wily and the updated Trusty images offered
from the main download page(s) will fail to work.

To me the obvious simple "workaround" is to recommend using the archived
14.04.1 images that still use the 3.13 series kernel as these are not
affected. The one caveat that those writing release notes and/or release
announcements is when we recommend using the archived 14.04.1 images we
must be certain to warn of ubiquity bug #1265192 so users don't
inadvertently wipe out existing data.

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 

[Desktop-packages] [Bug 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

As far as reporting upstream to move the status from incomplete back to
confirmed - I have no idea what I'm doing :^(

Is this an X bug as originally thought? Or a kernel bug as now seems to
be the case? I clearly can't create a new bugzilla account and file a
bug report when I have no idea what I'm doing.

AFAIK incomplete bugs expire? Why should we let this expire just because
I lack the tech know-how to file upstream?

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  

[Desktop-packages] [Bug 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

I took time to check Wily and the results are similar. This bug is
present with the 4.2.0-27.30 kernel but the 4.2.0-29.31 kernel is OK.

So I'm guessing the updated intel driver fails to build properly with
kernels prior to 4.2.0-29

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  

[Desktop-packages] [Bug 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

Looking at the 14.04.4 RC again this AM I find that the 4.2.0-29.23
kernel is OK, but this bug is present with 4.2.0-27.21. So this is
apparently not so much an X bug as a kernel bug??

AFAIK Xenial is (or at least has been) affected by this also and I'll be
testing the Beta 1 candidates next week. I haven't tried testing Wily
any further but it's time for me to revisit that and see if a kernel
upgrade in Wily fixes the issue or not.

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  

[Desktop-packages] [Bug 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

Lubuntu Trusty is affected to a much lesser degree so I was at least
able to install it. I'm going to try the newest kernel from proposed
tomorrow.

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
  

[Desktop-packages] [Bug 1539597] Re: nvidia-304 fails to install properly causing unity-control-center to crash

[Erick Brunzell]

I changed the title to more properly represent the underlying problem.
As mentioned above I suspect this is a duplicate of (or related to)
either bug 1477593 or bug 1498146. In fact one or the other of those
might be a duplicate of the other. Currently the Wily HWE stack seems to
be working OK in 14.04.4 but I'll have to verify that after trusty-
proposed is switched off and the 14.04.4 release candidates build. I'll
then follow up testing the current state of Xenial and Wily ASAP.

** Summary changed:

- unity-control-center crashed with SIGSEGV in 
_cogl_renderer_handle_native_event()
+ nvidia-304 fails to install properly causing unity-control-center to crash

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

Title:
  nvidia-304 fails to install properly causing unity-control-center to
  crash

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  I get this crash trying to open System Settings in Xenial. The System
  Settings UI fails to open and apport takes over.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160119-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jan 29 07:27:47 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-11-10 (80 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  ProcCmdline: unity-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc5ad919809:mov0xd8(%rdi),%rbx
   PC (0x7fc5ad919809) ok
   source "0xd8(%rdi)" (0x00d8) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: unity-control-center crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1539597/+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 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

I was surprised testing the Trusty Daily Ubuntu GNOME 20160207 amd64
image to find that it works OK in a live session so just making a note
for my own use regarding version:

xserver-xorg-video-intel-lts-wily
2:2.99.917+git20150808-0ubuntu4~trusty2

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  

[Desktop-packages] [Bug 1539597] Re: unity-control-center crashed with SIGSEGV in _cogl_renderer_handle_native_event()

[Erick Brunzell]

I believe this is just a side-effect of the nvidia driver not installing
properly with the 4.2, 4.3, or 4.4 series kernels. I found this in
JournalErrors:

Jan 29 07:26:56 username-AMD-desktop kernel: nvidia: module license 'NVIDIA' 
taints kernel.
Jan 29 07:26:56 username-AMD-desktop kernel: Disabling lock debugging due to 
kernel taint
Jan 29 07:26:56 username-AMD-desktop kernel: nvidia: Unknown symbol mtrr_del 
(err 0)
Jan 29 07:26:56 username-AMD-desktop kernel: nvidia: Unknown symbol mtrr_add 
(err 0) 

So currently it affects Wily, Xenial, and the Trusty dailies w/Wily
kernel. I'm not tech savvy enough to know which bug(s) may be the actual
culprit, but I think either bug 1477593 or 1498146. I realize those are
for different nvidia driver versions but there are duplicates that point
to nvidia-304.

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

Title:
  unity-control-center crashed with SIGSEGV in
  _cogl_renderer_handle_native_event()

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  I get this crash trying to open System Settings in Xenial. The System
  Settings UI fails to open and apport takes over.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160119-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jan 29 07:27:47 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-11-10 (80 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  ProcCmdline: unity-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc5ad919809:mov0xd8(%rdi),%rbx
   PC (0x7fc5ad919809) ok
   source "0xd8(%rdi)" (0x00d8) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: unity-control-center crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1539597/+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 1539597] Re: unity-control-center crashed with SIGSEGV in gdk_display_get_event()

[Erick Brunzell]

This only occurs if using the nvidia-304 graphics driver. It does not
occur if I use the nouveau driver. The nvidia driver also fails to
provide the proper screen resolution.

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

Title:
  unity-control-center crashed with SIGSEGV in gdk_display_get_event()

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  I get this crash trying to open System Settings in Xenial. The System
  Settings UI fails to open and apport takes over.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160119-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jan 29 07:27:47 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-11-10 (80 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  ProcCmdline: unity-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc5ad919809:mov0xd8(%rdi),%rbx
   PC (0x7fc5ad919809) ok
   source "0xd8(%rdi)" (0x00d8) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: unity-control-center crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1539597/+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 1539597] [NEW] unity-control-center crashed with SIGSEGV in gdk_display_get_event()

[Erick Brunzell]

Public bug reported:

I get this crash trying to open System Settings in Xenial. The System
Settings UI fails to open and apport takes over.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: unity-control-center 15.04.0+16.04.20160119-0ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
Uname: Linux 4.4.0-2-generic x86_64
ApportVersion: 2.19.4-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: GNOME-Flashback:Unity
Date: Fri Jan 29 07:27:47 2016
ExecutablePath: /usr/bin/unity-control-center
InstallationDate: Installed on 2015-11-10 (80 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
ProcCmdline: unity-control-center --overview
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc5ad919809:  mov0xd8(%rdi),%rbx
 PC (0x7fc5ad919809) ok
 source "0xd8(%rdi)" (0x00d8) not located in a known VMA region (needed 
readable region)!
 destination "%rbx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity-control-center
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
 ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
 gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
Title: unity-control-center crashed with SIGSEGV in gdk_display_get_event()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

** Affects: unity-control-center (Ubuntu)
 Importance: Undecided
 Status: New


** Tags: amd64 apport-crash need-amd64-retrace third-party-packages xenial

** Information type changed from Private to Public

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

Title:
  unity-control-center crashed with SIGSEGV in gdk_display_get_event()

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  I get this crash trying to open System Settings in Xenial. The System
  Settings UI fails to open and apport takes over.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160119-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jan 29 07:27:47 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-11-10 (80 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  ProcCmdline: unity-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc5ad919809:mov0xd8(%rdi),%rbx
   PC (0x7fc5ad919809) ok
   source "0xd8(%rdi)" (0x00d8) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: unity-control-center crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1539597/+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 1539597] Re: unity-control-center crashed with SIGSEGV in gdk_display_get_event()

[Erick Brunzell]

I'll try Unity after switching back to the nvidia driver. I've had to
use flashback w/metacity with the nouveau driver because the Unity DE
freezes within just a minute or two while using the nouveau driver.

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

Title:
  unity-control-center crashed with SIGSEGV in gdk_display_get_event()

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  I get this crash trying to open System Settings in Xenial. The System
  Settings UI fails to open and apport takes over.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160119-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jan 29 07:27:47 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-11-10 (80 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  ProcCmdline: unity-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc5ad919809:mov0xd8(%rdi),%rbx
   PC (0x7fc5ad919809) ok
   source "0xd8(%rdi)" (0x00d8) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: unity-control-center crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1539597/+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 1539597] Re: unity-control-center crashed with SIGSEGV in gdk_display_get_event()

[Erick Brunzell]

The default Unity DE fails to load altogether with the nvidia driver, it
just bounces right back to the login screen. Unity does load with the
nouveau driver activated but it slows to a crawl and eventually just
freezes. But that hardware has never been able to run Unity w/nouveau
(llvmpipe / Gallium 0.4 on NV4C).

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

Title:
  unity-control-center crashed with SIGSEGV in gdk_display_get_event()

Status in unity-control-center package in Ubuntu:
  New

Bug description:
  I get this crash trying to open System Settings in Xenial. The System
  Settings UI fails to open and apport takes over.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: unity-control-center 15.04.0+16.04.20160119-0ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-2.16-generic 4.4.0
  Uname: Linux 4.4.0-2-generic x86_64
  ApportVersion: 2.19.4-0ubuntu1
  Architecture: amd64
  CrashCounter: 1
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Fri Jan 29 07:27:47 2016
  ExecutablePath: /usr/bin/unity-control-center
  InstallationDate: Installed on 2015-11-10 (80 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  ProcCmdline: unity-control-center --overview
  ProcEnviron:
   LANGUAGE=en_US
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SegvAnalysis:
   Segfault happened at: 0x7fc5ad919809:mov0xd8(%rdi),%rbx
   PC (0x7fc5ad919809) ok
   source "0xd8(%rdi)" (0x00d8) not located in a known VMA region (needed 
readable region)!
   destination "%rbx" ok
  SegvReason: reading NULL VMA
  Signal: 11
  SourcePackage: unity-control-center
  StacktraceTop:
   ?? () from /usr/lib/x86_64-linux-gnu/libcogl.so.20
   ?? () from /usr/lib/x86_64-linux-gnu/libclutter-1.0.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
   gdk_display_get_event () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
  Title: unity-control-center crashed with SIGSEGV in gdk_display_get_event()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-control-center/+bug/1539597/+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 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

Not surprisingly this also affects the Trusty dailies based on testing
Ubuntu GNOME Trusty 20160124 amd64 since they have the Wily HWE. So the
flavors participating may want to mention it in their release notes,
recommending that users affected use the archived 14.04.1 images.

** Tags added: 14.04.4

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  

[Desktop-packages] [Bug 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

Still affects Ubuntu GNOME Xenial 20160121 amd64. So I guess I'll have
to create a Bugzilla account and try to figure out their bug filing
process when I have time.

** Tags added: amd64 xenial

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

Title:
  Garbled graphics in Wily with Intel GMA4500 chip

Status in One Hundred Papercuts:
  Incomplete
Status in xf86-video-intel:
  New
Status in xserver-xorg-video-intel package in Ubuntu:
  Incomplete

Bug description:
  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The
  graphics are so badly garbled I can only file this bug on an
  unaffected OS where I've held back the update on just that one package
  to about Beta 1 status:

  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
    Installed: 2:2.99.917-1ubuntu1
    Candidate: 2:2.99.917+git20150808-0ubuntu4
    Version table:
   2:2.99.917+git20150808-0ubuntu4 0
  500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
   *** 2:2.99.917-1ubuntu1 0
  100 /var/lib/dpkg/status

  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected
  OS displays perfectly OK in the unaffected OS so I used my camera.

  The info provided by lspci may not be very helpful:

  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device 0025
   Flags: bus master, fast devsel, latency 0, IRQ 27
   Memory at d000 (64-bit, non-prefetchable) [size=4M]
   Memory at c000 (64-bit, prefetchable) [size=256M]
   I/O ports at f1c0 [size=8]
   Expansion ROM at  [disabled]
   Capabilities: 
   Kernel driver in use: i915

  The tech specs show:

  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)

  I'm just using VGA ATM.

  Something else worth mentioning is this warning displayed while filing
  the bug report:

  Your system is providing 3D via software rendering rather than
  hardware rendering.  This is a compatibility mode which should display
  3D graphics properly but the performance may be very poor.  If the
  problem you're reporting is related to graphics performance, your real
  question may be why X didn't use hardware acceleration for your
  system.

  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
   Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
     Subsystem: Intel Corporation Device [8086:0025]
     Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
  dmi.board.asset.tag: To be filled by O.E.M.
  dmi.board.name: DB43LD
  dmi.board.vendor: Intel Corporation
  dmi.board.version: AAE60577-202
  dmi.chassis.type: 3
  dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
  version.compiz: compiz N/A
  version.libdrm2: libdrm2 2.4.64-1
  version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
  version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
  version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
  version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
  version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 

[Desktop-packages] [Bug 1443723] Re: GNOME clock displays improper date format for US/EN locale

[Erick Brunzell]

Yes, I think this is (or at least was) fixed in Xenial. I can't be
certain because I haven't been able to use any iso since the 4.3 series
kernel rolled out and I really need to get a fresh install working at
some point because the testing install I'm using is long in the tooth
and has been modified far too much to be certain of anything.

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

Title:
  GNOME clock displays improper date format for US/EN locale

Status in Ubuntu GNOME:
  Triaged
Status in gnome-desktop3 package in Ubuntu:
  Confirmed

Bug description:
  I've actually noticed this for some time and decided to file a bug
  report in hopes of getting this fixed by 16.04 (or sooner).

  In the standard GNOME desktop (with US/EN locale set) the date in the
  clock displays day of week, day of month, month before the time rather
  than day of week, month, day of month - eg; Mon 13 Apr, 8:06 PM rather
  than Mon Apr 13, 8:06 PM.

  The proper format is used both in the screen-lock and the Date & Time
  settings dialog (see screenshot).

  This also effects the clock applet in gnome-panel as of Vivid,
  possibly it's now following g-s-d rather than u-s-d?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-settings-daemon 3.14.2-3ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic i686
  ApportVersion: 2.17-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Apr 13 19:57:57 2015
  InstallationDate: Installed on 2015-04-01 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta i386 (20150331)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1443723/+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 1516323] Re: With compositing off some apps have a huge black border

[Erick Brunzell]

Thanks Alberts, I see now that it's OK using the Ambiance theme but
borked in Numix so I'll give them time to catch up.

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

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

Title:
  With compositing off some apps have a huge black border

Status in metacity package in Ubuntu:
  Invalid

Bug description:
  In Xenial I notice with compositing switched off several apps
  (nautilus, gedit, totem, gnome-tweak-tool, system-monitor & empathy)
  have a huge black border as shown in the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: metacity 1:3.18.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Nov 14 17:56:19 2015
  InstallationDate: Installed on 2015-11-10 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  SourcePackage: metacity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1516323/+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 1516316] [NEW] Username in flashback menu tree displays empty limb

[Erick Brunzell]

Public bug reported:

This is an extremely minor issue but I notice in Xenial when using the
main menu button rather than the standard Menu Bar the username
displayed in the menu tree just displays a blank limb when you mouse
over it. A picture is worth a thousand words in this instance so I'm
attaching a screenshot composition with the Xenial behavior on the left
and the Trusty behavior on the right.

It looks to me like even the username displayed in indicator-applet-
complete is rather useless and redundant so maybe the Unity devs would
consider changing that entire behavior? I mean clicking on the username
will lock the screen but there is also a Lock button so why even have
the username displayed?

Also the System Settings button is displayed in System Tools as well as
being displayed by indicator-applet-complete if used so it's just more
redundancy. Can anyone think of a valid reason why the username need
even be displayed?

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: gnome-panel 1:3.18.1-1ubuntu3
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.2-0ubuntu6
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sat Nov 14 15:46:48 2015
GsettingsChanges:
 
InstallationDate: Installed on 2015-11-10 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
SourcePackage: gnome-panel
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "username_comp.png"
   
https://bugs.launchpad.net/bugs/1516316/+attachment/4519156/+files/username_comp.png

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

Title:
  Username in flashback menu tree displays empty limb

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  This is an extremely minor issue but I notice in Xenial when using the
  main menu button rather than the standard Menu Bar the username
  displayed in the menu tree just displays a blank limb when you mouse
  over it. A picture is worth a thousand words in this instance so I'm
  attaching a screenshot composition with the Xenial behavior on the
  left and the Trusty behavior on the right.

  It looks to me like even the username displayed in indicator-applet-
  complete is rather useless and redundant so maybe the Unity devs would
  consider changing that entire behavior? I mean clicking on the
  username will lock the screen but there is also a Lock button so why
  even have the username displayed?

  Also the System Settings button is displayed in System Tools as well
  as being displayed by indicator-applet-complete if used so it's just
  more redundancy. Can anyone think of a valid reason why the username
  need even be displayed?

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: gnome-panel 1:3.18.1-1ubuntu3
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Nov 14 15:46:48 2015
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-11-10 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1516316/+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 1516323] [NEW] With compositing off some apps have a huge black border

[Erick Brunzell]

Public bug reported:

In Xenial I notice with compositing switched off several apps (nautilus,
gedit, totem, gnome-tweak-tool, system-monitor & empathy) have a huge
black border as shown in the attached screenshot.

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: metacity 1:3.18.1-1ubuntu2
ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
Uname: Linux 4.2.0-19-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.19.2-0ubuntu6
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Sat Nov 14 17:56:19 2015
InstallationDate: Installed on 2015-11-10 (4 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
SourcePackage: metacity
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug xenial

** Attachment added: "black_border.png"
   
https://bugs.launchpad.net/bugs/1516323/+attachment/4519218/+files/black_border.png

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

Title:
  With compositing off some apps have a huge black border

Status in metacity package in Ubuntu:
  New

Bug description:
  In Xenial I notice with compositing switched off several apps
  (nautilus, gedit, totem, gnome-tweak-tool, system-monitor & empathy)
  have a huge black border as shown in the attached screenshot.

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: metacity 1:3.18.1-1ubuntu2
  ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6
  Uname: Linux 4.2.0-19-generic x86_64
  NonfreeKernelModules: nvidia
  ApportVersion: 2.19.2-0ubuntu6
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Sat Nov 14 17:56:19 2015
  InstallationDate: Installed on 2015-11-10 (4 days ago)
  InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151109)
  SourcePackage: metacity
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/metacity/+bug/1516323/+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 1487819] Re: Wily user UI shows auto-login off after selecting on during install

[Erick Brunzell]

Still affecting Ubuntu GNOME 20151020 Wily installs.

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

Title:
  Wily user UI shows auto-login off after selecting on during install

Status in gdm package in Ubuntu:
  Confirmed

Bug description:
  Just testing Ubuntu GNOME Wily 20150822 i386 and I've noticed that in
  spite of selecting auto-login = on during installation when the
  installation is complete and after first boot opening Settings > Users
  the UI shows off, but auto-login is working properly and if you toggle
  the UI back and forth from off to on a couple of times it seems to
  start working properly.

  I also installed Ubuntu 20150822 i386 and it's not affected so I
  suspect this is either a bug in gdm or possibly in g-c-c or g-s-d.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gdm 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic i686
  ApportVersion: 2.18-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Aug 22 23:04:29 2015
  InstallationDate: Installed on 2015-08-23 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 (20150822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.custom.conf: 2015-08-22T21:20:12.826508

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1487819/+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 1507255] Re: Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

I incorrectly staed above:

"The graphics are so badly garbled I can only file this bug on an
unaffected OS where I've held back the update on just that one package
to about Alpha 2 status"

That should have said "Beta 1 status" so I'll correct that accordingly.

** Description changed:

  This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The graphics
  are so badly garbled I can only file this bug on an unaffected OS where
- I've held back the update on just that one package to about Alpha 2
+ I've held back the update on just that one package to about Beta 1
  status:
  
  lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
  xserver-xorg-video-intel:
-   Installed: 2:2.99.917-1ubuntu1
-   Candidate: 2:2.99.917+git20150808-0ubuntu4
-   Version table:
-  2:2.99.917+git20150808-0ubuntu4 0
- 500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
-  *** 2:2.99.917-1ubuntu1 0
- 100 /var/lib/dpkg/status
+   Installed: 2:2.99.917-1ubuntu1
+   Candidate: 2:2.99.917+git20150808-0ubuntu4
+   Version table:
+  2:2.99.917+git20150808-0ubuntu4 0
+ 500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
+  *** 2:2.99.917-1ubuntu1 0
+ 100 /var/lib/dpkg/status
  
  I'll attach a picture of the garbled screen with the updated xserver-
  xorg-video-intel package. Oddly a screenshot taken from the affected OS
  displays perfectly OK in the unaffected OS so I used my camera.
  
  The info provided by lspci may not be very helpful:
  
  lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
  00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
-   Subsystem: Intel Corporation Device 0025
-   Flags: bus master, fast devsel, latency 0, IRQ 27
-   Memory at d000 (64-bit, non-prefetchable) [size=4M]
-   Memory at c000 (64-bit, prefetchable) [size=256M]
-   I/O ports at f1c0 [size=8]
-   Expansion ROM at  [disabled]
-   Capabilities: 
-   Kernel driver in use: i915
+  Subsystem: Intel Corporation Device 0025
+  Flags: bus master, fast devsel, latency 0, IRQ 27
+  Memory at d000 (64-bit, non-prefetchable) [size=4M]
+  Memory at c000 (64-bit, prefetchable) [size=256M]
+  I/O ports at f1c0 [size=8]
+  Expansion ROM at  [disabled]
+  Capabilities: 
+  Kernel driver in use: i915
  
  The tech specs show:
  
  Internal Graphics:
  • Intel ® GMA4500 onboard graphics subsystem with support for:
  ― Analog displays (VGA)
  ― Digital displays (DVI-D)
  
  I'm just using VGA ATM.
  
  Something else worth mentioning is this warning displayed while filing
  the bug report:
  
  Your system is providing 3D via software rendering rather than hardware
  rendering.  This is a compatibility mode which should display 3D
  graphics properly but the performance may be very poor.  If the problem
  you're reporting is related to graphics performance, your real question
  may be why X didn't use hardware acceleration for your system.
  
  I did try booting an earlier kernel to no avail, but holding back just
  this one update prevents the borkage.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
  ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
  Uname: Linux 4.2.0-16-generic i686
  ApportVersion: 2.19.1-0ubuntu2
  Architecture: i386
  CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
  CompositorRunning: None
  CurrentDesktop: GNOME
  Date: Sun Oct 18 00:17:35 2015
  DistUpgraded: Fresh install
  DistroCodename: wily
  DistroVariant: ubuntu
  ExtraDebuggingInterest: Yes, if not too technical
  GraphicsCard:
-  Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
-Subsystem: Intel Corporation Device [8086:0025]
-Subsystem: Intel Corporation Device [8086:0025]
+  Intel Corporation 4 Series Chipset Integrated Graphics Controller 
[8086:2e42] (rev 03) (prog-if 00 [VGA controller])
+    Subsystem: Intel Corporation Device [8086:0025]
+    Subsystem: Intel Corporation Device [8086:0025]
  InstallationDate: Installed on 2015-08-26 (52 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 
(20150826.1)
  ProcEnviron:
-  TERM=xterm-256color
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm-256color
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
  Renderer: Software
  SourcePackage: xserver-xorg-video-intel
  UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/23/2010
  dmi.bios.vendor: Intel Corp.
  

[Desktop-packages] [Bug 1507255] [NEW] Garbled graphics in Wily with Intel GMA4500 chip

[Erick Brunzell]

Public bug reported:

This affects both Ubuntu GNOME and Ubuntu Wily 20151017.1. The graphics
are so badly garbled I can only file this bug on an unaffected OS where
I've held back the update on just that one package to about Alpha 2
status:

lance@lance-INTEL-desktop:~$ apt-cache policy xserver-xorg-video-intel
xserver-xorg-video-intel:
  Installed: 2:2.99.917-1ubuntu1
  Candidate: 2:2.99.917+git20150808-0ubuntu4
  Version table:
 2:2.99.917+git20150808-0ubuntu4 0
500 http://us.archive.ubuntu.com/ubuntu/ wily/main i386 Packages
 *** 2:2.99.917-1ubuntu1 0
100 /var/lib/dpkg/status

I'll attach a picture of the garbled screen with the updated xserver-
xorg-video-intel package. Oddly a screenshot taken from the affected OS
displays perfectly OK in the unaffected OS so I used my camera.

The info provided by lspci may not be very helpful:

lance@lance-INTEL-desktop:~$ lspci -v -s `lspci | awk '/VGA/{print $1}'`
00:02.0 VGA compatible controller: Intel Corporation 4 Series Chipset 
Integrated Graphics Controller (rev 03) (prog-if 00 [VGA controller])
Subsystem: Intel Corporation Device 0025
Flags: bus master, fast devsel, latency 0, IRQ 27
Memory at d000 (64-bit, non-prefetchable) [size=4M]
Memory at c000 (64-bit, prefetchable) [size=256M]
I/O ports at f1c0 [size=8]
Expansion ROM at  [disabled]
Capabilities: 
Kernel driver in use: i915

The tech specs show:

Internal Graphics:
• Intel ® GMA4500 onboard graphics subsystem with support for:
― Analog displays (VGA)
― Digital displays (DVI-D)

I'm just using VGA ATM.

Something else worth mentioning is this warning displayed while filing
the bug report:

Your system is providing 3D via software rendering rather than hardware
rendering.  This is a compatibility mode which should display 3D
graphics properly but the performance may be very poor.  If the problem
you're reporting is related to graphics performance, your real question
may be why X didn't use hardware acceleration for your system.

I did try booting an earlier kernel to no avail, but holding back just
this one update prevents the borkage.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
ProcVersionSignature: Ubuntu 4.2.0-16.19-generic 4.2.3
Uname: Linux 4.2.0-16-generic i686
ApportVersion: 2.19.1-0ubuntu2
Architecture: i386
CompizPlugins: No value set for 
`/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: None
CurrentDesktop: GNOME
Date: Sun Oct 18 00:17:35 2015
DistUpgraded: Fresh install
DistroCodename: wily
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e42] 
(rev 03) (prog-if 00 [VGA controller])
   Subsystem: Intel Corporation Device [8086:0025]
   Subsystem: Intel Corporation Device [8086:0025]
InstallationDate: Installed on 2015-08-26 (52 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 "Wily Werewolf" - Alpha i386 (20150826.1)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-16-generic 
root=UUID=39597a1e-90b6-4e81-ae29-4c01d28f7f17 ro quiet splash vt.handoff=7
Renderer: Software
SourcePackage: xserver-xorg-video-intel
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2010
dmi.bios.vendor: Intel Corp.
dmi.bios.version: LDB4310H.86A.0037.2010.1223.1121
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: DB43LD
dmi.board.vendor: Intel Corporation
dmi.board.version: AAE60577-202
dmi.chassis.type: 3
dmi.modalias: 
dmi:bvnIntelCorp.:bvrLDB4310H.86A.0037.2010.1223.1121:bd12/23/2010:svn:pn:pvr:rvnIntelCorporation:rnDB43LD:rvrAAE60577-202:cvn:ct3:cvr:
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.64-1
version.libgl1-mesa-dri: libgl1-mesa-dri 11.0.2-1ubuntu4
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 11.0.2-1ubuntu4
version.xserver-xorg-core: xserver-xorg-core 2:1.17.2-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.9.2-1ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 
1:7.5.0+git20150819-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu3
xserver.bootTime: Sat Oct 17 23:58:59 2015
xserver.configfile: default
xserver.errors:
 AIGLX error: Calling driver entry point failed
 AIGLX: reverting to software rendering
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
 
xserver.version: 2:1.17.2-1ubuntu9

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


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

** Attachment added: 

[Desktop-packages] [Bug 1502570] Re: gnome-panel indirectly installs evolution

[Erick Brunzell]

This was actually a duplicate of bug #1381232.

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

Title:
  gnome-panel indirectly installs evolution

Status in gnome-panel package in Ubuntu:
  Fix Released

Bug description:
  http://packages.ubuntu.com/wily/gnome-panel
  gnome-panel Recommends: evolution-common
  ...which in turn Recommends: evolution

  Is this on purpose?
  Could you please lower the "Recommends" to "Suggests"?
  Gnome-flashback isn't a flavor with a live CD etc, so it makes more sense to 
keep the vanilla Ubuntu defaults, i.e. thunderbird as the mailer...

  If evolution-common is necessary for gnome-flashback, but evolution
  isn't, please mention it so that we ask them instead to lower their
  Recommends to Suggests.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1502570/+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 1443723] Re: GNOME clock displays improper date format for US/EN locale

[Erick Brunzell]

Still affects Wily.

** Tags added: wily

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

Title:
  GNOME clock displays improper date format for US/EN locale

Status in Ubuntu GNOME:
  New
Status in gnome-desktop3 package in Ubuntu:
  New

Bug description:
  I've actually noticed this for some time and decided to file a bug
  report in hopes of getting this fixed by 16.04 (or sooner).

  In the standard GNOME desktop (with US/EN locale set) the date in the
  clock displays day of week, day of month, month before the time rather
  than day of week, month, day of month - eg; Mon 13 Apr, 8:06 PM rather
  than Mon Apr 13, 8:06 PM.

  The proper format is used both in the screen-lock and the Date & Time
  settings dialog (see screenshot).

  This also effects the clock applet in gnome-panel as of Vivid,
  possibly it's now following g-s-d rather than u-s-d?

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-settings-daemon 3.14.2-3ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-13.13-generic 3.19.3
  Uname: Linux 3.19.0-13-generic i686
  ApportVersion: 2.17-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Mon Apr 13 19:57:57 2015
  InstallationDate: Installed on 2015-04-01 (13 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 "Vivid Vervet" - Beta i386 (20150331)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1443723/+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 1381232] Re: Utopic version of gnome-panel depends on evolution-common

[Erick Brunzell]

Still effects Wily so I updated the title and tags.

** Tags removed: utopic
** Tags added: vivid wily

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

Title:
  Utopic version of gnome-panel depends on evolution-common

Status in gnome-panel package in Ubuntu:
  Confirmed

Bug description:
  Not sure when or why this changed but installing gnome-session-
  flashback in Ubuntu Utopic now wants to install evolution:

  lance@lance-desktop:~$ sudo apt-get install gnome-panel
  [sudo] password for lance: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
alacarte evolution evolution-common evolution-plugins gir1.2-gconf-2.0
gir1.2-panelapplet-4.0 gnome-applets gnome-applets-data gnome-media
gnome-panel-data gnome-session-flashback gstreamer0.10-gconf
indicator-applet-complete libcpufreq0 libencode-locale-perl liberror-perl
libevolution libfile-listing-perl libfont-afm-perl
libgnome-media-profiles-3.0-0 libgtkhtml-4.0-0 libgtkhtml-4.0-common
libgtkhtml-editor-4.0-0 libgtkspell3-3-0 libhtml-form-perl
libhtml-format-perl libhtml-parser-perl libhtml-tagset-perl
libhtml-tree-perl libhttp-cookies-perl libhttp-daemon-perl libhttp-date-perl
libhttp-message-perl libhttp-negotiate-perl libio-html-perl
liblwp-mediatypes-perl liblwp-protocol-https-perl libmail-spf-perl
libnet-http-perl libnetaddr-ip-perl libpanel-applet-4-0 libpst4
libsys-hostname-long-perl libwww-perl libwww-robotrules-perl libytnef0
metacity notification-daemon re2c sa-compile spamassassin spamc
  Suggested packages:
evolution-ews evolution-plugins-experimental tomboy desktop-base
libdata-dump-perl libcrypt-ssleay-perl libauthen-ntlm-perl
gnome-control-center razor libdbi-perl pyzor libmail-dkim-perl
  The following NEW packages will be installed:
alacarte evolution evolution-common evolution-plugins gir1.2-gconf-2.0
gir1.2-panelapplet-4.0 gnome-applets gnome-applets-data gnome-media
gnome-panel gnome-panel-data gnome-session-flashback gstreamer0.10-gconf
indicator-applet-complete libcpufreq0 libencode-locale-perl liberror-perl
libevolution libfile-listing-perl libfont-afm-perl
libgnome-media-profiles-3.0-0 libgtkhtml-4.0-0 libgtkhtml-4.0-common
libgtkhtml-editor-4.0-0 libgtkspell3-3-0 libhtml-form-perl
libhtml-format-perl libhtml-parser-perl libhtml-tagset-perl
libhtml-tree-perl libhttp-cookies-perl libhttp-daemon-perl libhttp-date-perl
libhttp-message-perl libhttp-negotiate-perl libio-html-perl
liblwp-mediatypes-perl liblwp-protocol-https-perl libmail-spf-perl
libnet-http-perl libnetaddr-ip-perl libpanel-applet-4-0 libpst4
libsys-hostname-long-perl libwww-perl libwww-robotrules-perl libytnef0
metacity notification-daemon re2c sa-compile spamassassin spamc
  0 upgraded, 53 newly installed, 0 to remove and 3 not upgraded.
  Need to get 15.3 MB of archives.
  After this operation, 79.3 MB of additional disk space will be used.
  Do you want to continue? [Y/n] n
  Abort.

  Even without recommends evolution wanted to be installed:

  lance@lance-desktop:~$ sudo apt-get install gnome-panel 
--no-install-recommends -s
  [sudo] password for lance: 
  Reading package lists... Done
  Building dependency tree   
  Reading state information... Done
  The following extra packages will be installed:
evolution-common gnome-panel-data libpanel-applet-4-0
  Recommended packages:
evolution alacarte gnome-applets gnome-session-flashback
indicator-applet-complete
  The following NEW packages will be installed:
evolution-common gnome-panel gnome-panel-data libpanel-applet-4-0
  0 upgraded, 4 newly installed, 0 to remove and 10 not upgraded.
  Inst evolution-common (3.12.7-0ubuntu1 Ubuntu:14.10/utopic [all])
  Inst gnome-panel-data (1:3.8.1-2ubuntu4 Ubuntu:14.10/utopic [all])
  Inst libpanel-applet-4-0 (1:3.8.1-2ubuntu4 Ubuntu:14.10/utopic [i386])
  Inst gnome-panel (1:3.8.1-2ubuntu4 Ubuntu:14.10/utopic [i386])
  Conf evolution-common (3.12.7-0ubuntu1 Ubuntu:14.10/utopic [all])
  Conf gnome-panel-data (1:3.8.1-2ubuntu4 Ubuntu:14.10/utopic [all])
  Conf libpanel-applet-4-0 (1:3.8.1-2ubuntu4 Ubuntu:14.10/utopic [i386])
  Conf gnome-panel (1:3.8.1-2ubuntu4 Ubuntu:14.10/utopic [i386])

  But I see evolution-common is now listed as a depend:

  lance@lance-desktop:~$ apt-cache show gnome-panel 
  Package: gnome-panel
  Priority: optional
  Section: universe/gnome
  Installed-Size: 1494
  Maintainer: Ubuntu Developers 
  Original-Maintainer: Debian GNOME Maintainers 

  Architecture: i386
  Version: 1:3.8.1-2ubuntu4
  Replaces: gnome-panel-data (<< 2.91)
  Depends: evolution-common (>= 3.4.3), gnome-icon-theme-symbolic (>= 

[Desktop-packages] [Bug 1412602] Re: No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

[Erick Brunzell]

** Changed in: linux (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: linux (Ubuntu Trusty)
   Status: Confirmed = Fix Released

** Changed in: linux (Ubuntu Utopic)
   Status: Confirmed = Fix Released

** Changed in: linux (Ubuntu Vivid)
   Status: Confirmed = Fix Released

** Changed in: xserver-xorg-video-nouveau (Ubuntu)
   Status: New = Fix Released

** Changed in: xserver-xorg-video-nouveau (Ubuntu Trusty)
   Status: New = Fix Released

** Changed in: xserver-xorg-video-nouveau (Ubuntu Utopic)
   Status: New = Fix Released

** Changed in: xserver-xorg-video-nouveau (Ubuntu Vivid)
   Status: New = Fix Released

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

Title:
  No live DE in Vivid using nouveau w/GeForce 7025/nForce 630a

Status in Nouveau Xorg driver:
  Unknown
Status in linux package in Ubuntu:
  Fix Released
Status in xserver-xorg-video-nouveau package in Ubuntu:
  Fix Released
Status in linux source package in Trusty:
  Fix Released
Status in xserver-xorg-video-nouveau source package in Trusty:
  Fix Released
Status in linux source package in Utopic:
  Fix Released
Status in xserver-xorg-video-nouveau source package in Utopic:
  Fix Released
Status in linux source package in Vivid:
  Fix Released
Status in xserver-xorg-video-nouveau source package in Vivid:
  Fix Released

Bug description:
  I've been testing the Ubuntu GNOME Vivid daily images in anticipation
  of Alpha 2 and I noticed that with this specific hardware I get no
  graphics at all other than a blank screen (see attached photo):

  AMD Sempron Processor LE-1250 @ 2.2 GHz
  nVidia C61 [GeForce 7025 / nForce 630a] (rev a2)
  nVidia MCP61 High Definition Audio (rev a2)
  nVidia MCP61 Ethernet (rev a2)
  2GB DDR2 RAM

  In fact I never even get as far as the screen offering to Try or
  Install, but I can enter the Advanced Boot Options screen and select
  either Try or Install from there, but with both options I still get
  the same blank screen.

  Further testing reveals the same results with Ubuntu and Ubuntu GNOME
  but I found that both the Xubuntu and Lubuntu images will boot
  properly on this box so I installed Lubuntu and then installed the
  ubuntu-desktop, ubuntu-gnome-desktop, and gnome-session-flashback
  meta-packages just to try some things.

  After doing so I found that the Unity, GNOME Shell, Gnome Classic, and
  Flashback w/Compiz sessions produce broken graphics just as the Ubuntu
  GNOME and Ubuntu live images do. So basically Compiz and Mutter both
  fail to display any usable UI. OTOH both the Lubuntu and Flashback
  w/Metacity sessions work just fine.

  I next opened the Additional drivers UI and chose nvidia-304.125
  (current) and all DE's perform quite well with the proprietary drivers
  so I deduced that nouveau might be the culprit.

  The last known working Ubuntu and Ubuntu GNOME live images are
  14.04.1. I hadn't tried Utopic on this box yet but it's also a fail.
  I'll try the proposed 14.04.2 images ASAP (probably after Vivid Alpha
  2 is released).

  But I see no point in trying to fix this for Utopic (or even 14.04.2
  if it's effected) because of the 9 month life-cycle for Utopic and the
  continued availability of the 14.04.1 images. In fact I'd be cool with
  this not being fixed until 16.04 as long as it's documented so people
  know what versions will and will not work.

  I'm probably forgetting something but that's all I can think of ATM.
  Sorry in advance if I did this totally wrong.

  ###  Additional workaround and debug info ###

  The focus of this bug report is limited to screen corruption and
  X-freezes that either prevent the installation of Ubuntu (or other
  flavors) and/or booting the installed system even long enough to
  enable the third party nvidia driver. There are almost certainly other
  instances of screen corruption and hard (or soft) lockups that may
  also be related to the nouveau driver but those are beyond the scope
  of this specific bug report.

  To workaround this bug, or to see if you're affected by it you can
  boot using this boot parameter:

  nouveau.config=NvMSI=0

  You'll find general instructions for using custom boot parameters at
  these links:

  https://help.ubuntu.com/community/BootOptions

  https://wiki.ubuntu.com/Kernel/KernelBootParameters

  In addition to what's said at the latter link about temporarily adding
  a kernel boot parameter to an installed system; after using the arrow
  keys to navigate to the line beginning with linux /boot you'll
  notice that line ends with quiet splash $vt_handoff. The boot
  parameter belongs between the quiet splash and $vt_handoff like
  this:

  quiet splash nouveau.config=NvMSI=0 $vt_handoff

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-video-nouveau 1:1.0.11-1ubuntu2
  

[Desktop-packages] [Bug 1487819] Re: Wily user UI shows auto-login off after selecting on during install

[Erick Brunzell]

I wonder if this could be an accountsservice issue as Sebastien Bacher
discovered in bug #1245915?

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

Title:
  Wily user UI shows auto-login off after selecting on during install

Status in gdm package in Ubuntu:
  New

Bug description:
  Just testing Ubuntu GNOME Wily 20150822 i386 and I've noticed that in
  spite of selecting auto-login = on during installation when the
  installation is complete and after first boot opening Settings  Users
  the UI shows off, but auto-login is working properly and if you toggle
  the UI back and forth from off to on a couple of times it seems to
  start working properly.

  I also installed Ubuntu 20150822 i386 and it's not affected so I
  suspect this is either a bug in gdm or possibly in g-c-c or g-s-d.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gdm 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic i686
  ApportVersion: 2.18-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Aug 22 23:04:29 2015
  InstallationDate: Installed on 2015-08-23 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 Wily Werewolf - Alpha i386 (20150822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.custom.conf: 2015-08-22T21:20:12.826508

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1487819/+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 1487819] [NEW] Wily user UI shows auto-login off after selecting on during install

[Erick Brunzell]

Public bug reported:

Just testing Ubuntu GNOME Wily 20150822 i386 and I've noticed that in
spite of selecting auto-login = on during installation when the
installation is complete and after first boot opening Settings  Users
the UI shows off, but auto-login is working properly and if you toggle
the UI back and forth from off to on a couple of times it seems to start
working properly.

I also installed Ubuntu 20150822 i386 and it's not affected so I suspect
this is either a bug in gdm or possibly in g-c-c or g-s-d.

ProblemType: Bug
DistroRelease: Ubuntu 15.10
Package: gdm 3.16.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
Uname: Linux 4.1.0-3-generic i686
ApportVersion: 2.18-0ubuntu7
Architecture: i386
CurrentDesktop: GNOME
Date: Sat Aug 22 23:04:29 2015
InstallationDate: Installed on 2015-08-23 (0 days ago)
InstallationMedia: Ubuntu-GNOME 15.10 Wily Werewolf - Alpha i386 (20150822)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=set
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gdm
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.gdm.custom.conf: 2015-08-22T21:20:12.826508

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


** Tags: apport-bug i386 wily

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

Title:
  Wily user UI shows auto-login off after selecting on during install

Status in gdm package in Ubuntu:
  New

Bug description:
  Just testing Ubuntu GNOME Wily 20150822 i386 and I've noticed that in
  spite of selecting auto-login = on during installation when the
  installation is complete and after first boot opening Settings  Users
  the UI shows off, but auto-login is working properly and if you toggle
  the UI back and forth from off to on a couple of times it seems to
  start working properly.

  I also installed Ubuntu 20150822 i386 and it's not affected so I
  suspect this is either a bug in gdm or possibly in g-c-c or g-s-d.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.10
  Package: gdm 3.16.2-0ubuntu2
  ProcVersionSignature: Ubuntu 4.1.0-3.3-generic 4.1.3
  Uname: Linux 4.1.0-3-generic i686
  ApportVersion: 2.18-0ubuntu7
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Sat Aug 22 23:04:29 2015
  InstallationDate: Installed on 2015-08-23 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.10 Wily Werewolf - Alpha i386 (20150822)
  ProcEnviron:
   TERM=xterm-256color
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.custom.conf: 2015-08-22T21:20:12.826508

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1487819/+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 1069964] Re: Two processes attempt to mount blank optical discs

[Erick Brunzell]

This does still effect Ubuntu  Ubuntu Mate Wily as well as Debian Mate
Jessie. I'll try to file a Debian bug report ASAP (it'll be my first).

Anyone that has suggestions might find my forum post useful:

http://ubuntuforums.org/showthread.php?t=2280658

The challenge is trying to figure out what process in addition to the
file manager is mounting the blank media.

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating Unable to mount Blank disc. Location is
  already mounted. Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+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 1069964] Re: Two processes attempt to mount blank optical discs

[Erick Brunzell]

Hi Tim, I assume that Nautilus (or Caja in the case of Ubuntu Mate) is
actually responsible for the media already mounted warning because if
you open dconf-editor and go to org/gnome/desktop/media-handling (or
org/mate/desktop/media-handling) and change both automount and
automount-open to false then the media already mounted warning goes
away. The downside is that doing so interferes with mounting usb drives,
cameras, etc so it's not a truly viable workaround.

The descriptions in dconf certainly mention Nautilus and Caja
specifically:

If set to true, then Nautilus will automatically mount media such as
user-visible hard disks and removable media on start-up and media
insertion.

If set to true, then Nautilus will automatically open a folder when
media is automounted. This only applies to media where no known
x-content/* type was detected; for media where a known x-content type is
detected, the user configurable action will be taken instead.

If set to true, then Caja will automatically mount media such as user-
visible hard disks and removable media on start-up and media insertion.

If set to true, then Caja will automatically open a folder when media is
automounted. This only applies to media where no known x-content/* type
was detected; for media where a known x-content type is detected, the
user configurable action will be taken instead.

So I really assume that some file managers (Nautilus, Caja, and possibly
Nemo) attempt to mount the blank media after gvfs has already mounted it
and therefore produce that warning. I'll grant you that it's only a
cosmetic issue but it's certainly one of those bugs that just shouts
not ready for prime time and sends users looking elsewhere for a
reliable distro.

I'd think there'd be a way to have Nautilus and Caja just see if media
is already mounted by gvfs and if so say nothing rather than displaying
a useless and meaningless warning.

Since this does also effect the Mate DE I took the liberty of
subscribing Martin Wimpress, so apologies in advance to Martin. My
intention is not to be pushy but only to inform.

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating Unable to mount Blank disc. Location is
  already mounted. Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

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

[Desktop-packages] [Bug 1069964] Re: Two processes attempt to mount blank optical discs

[Erick Brunzell]

** Tags added: caja ubuntu-mate wily

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating Unable to mount Blank disc. Location is
  already mounted. Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+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 1069964] Re: Two processes attempt to mount blank optical discs

[Erick Brunzell]

** Summary changed:

- Unable to mount Blank CD-R disc. Location is already mounted.
+ Two processes attempt to mount blank optical discs

** Description changed:

+ This behavior can be reproduced using either a live USB or an installed
+ version of the effected flavors. Simply insert a blank optical disc in
+ the drive.
+ 
+ The behavior differs slightly in Ubuntu GNOME as the notification to
+ either Open with CD/DVD Creator or Eject is displayed twice - that is
+ after simply clicking on the X to close that notification it closes but
+ a new duplicate notification appaers immediately. The GNOME Classic
+ session is not effected at all.
+ 
+ In all other effected flavors and/or desktop environments a notification
+ appears stating Unable to mount Blank disc. Location is already
+ mounted. Effected flavors and DE's include Ubuntu w/Unity, gnome-
+ session-flashback, and Ubuntu MATE.
+ 
+ Versions effected include Trusty, Utopic, and Vivid. I assume that two
+ separate processes are actually attempting to mount the blank optical
+ media, rather than just the file manager attemting to do so, because
+ both Nautilus and Caja are effected (based on some of the comments below
+ possibly also Nemo).
+ 
+ While purely cosmetic in nature I'd certainly be willing to try and
+ troubleshoot this if someone more tech savvy would provide some
+ debugging instructions.
+ 
+ Original content begins below:
+ 
  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png
  
  Burner: LG HL-DT-ST DVDRAM GH24NS90
  
  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcEnviron:
-  LANGUAGE=en_GB:en
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_GB.UTF-8
-  SHELL=/bin/bash
+  LANGUAGE=en_GB:en
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_GB.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Two processes attempt to mount blank optical discs

Status in OEM Priority Project:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This behavior can be reproduced using either a live USB or an
  installed version of the effected flavors. Simply insert a blank
  optical disc in the drive.

  The behavior differs slightly in Ubuntu GNOME as the notification to
  either Open with CD/DVD Creator or Eject is displayed twice - that is
  after simply clicking on the X to close that notification it closes
  but a new duplicate notification appaers immediately. The GNOME
  Classic session is not effected at all.

  In all other effected flavors and/or desktop environments a
  notification appears stating Unable to mount Blank disc. Location is
  already mounted. Effected flavors and DE's include Ubuntu w/Unity,
  gnome-session-flashback, and Ubuntu MATE.

  Versions effected include Trusty, Utopic, and Vivid. I assume that two
  separate processes are actually attempting to mount the blank optical
  media, rather than just the file manager attemting to do so, because
  both Nautilus and Caja are effected (based on some of the comments
  below possibly also Nemo).

  While purely cosmetic in nature I'd certainly be willing to try and
  troubleshoot this if someone more tech savvy would provide some
  debugging instructions.

  Original content begins below:

  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: 

[Desktop-packages] [Bug 1432843] Re: Lubuntu failed to boot

[Erick Brunzell]

I've tested both the Lubuntu 20150330 i386 and amd64 images on two
totally different sets of hardware.

Both fail to boot to the live DE on this hardware:

Intel Atom CPU  230 @ 1.60GHz
Intel 82945G/GZ Integrated Graphics Controller (rev 02)
Intel N10/ICH 7 Family High Definition Audio Controller (rev 01)
Realtek RTL8101E/RTL8102E PCI Express Fast Ethernet controller (rev 02)
2GB DDR2 RAM

The i386 image fails to boot to the live DE, but the amd64 image does
boot to the live DE while producing bug #1438605 on this hardware:

AMD Sempron Processor LE-1250 @ 2.2 GHz
nVidia C61 [GeForce 7025 / nForce 630a] (rev a2)
nVidia MCP61 High Definition Audio (rev a2)
nVidia MCP61 Ethernet (rev a2)
2GB DDR2 RAM

But the installation freezes at the second screen on that second set of
hardware.

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

Title:
  Lubuntu failed to boot

Status in X.Org X server:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged

Bug description:
  The daily build of Lubuntu 20150316 failed to boot into the live
  session, and fails to install. During the boot session, the Lubuntu
  splash screen appears indicating that Lubuntu was loading. What
  follows next was a blank screen.

  Unfortunately, I cannot sumit the exact version of syslinux since the
  daily build could not boot into an interactive session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar 16 17:19:35 2015
  Dependencies:
   gcc-5-base 5-20150228-1ubuntu1
   libc6 2.19-15ubuntu2
   libgcc1 1:5-20150228-1ubuntu1
   mtools 4.0.18-2
   multiarch-support 2.19-15ubuntu2
  InstallationDate: Installed on 2015-03-05 (11 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303)
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1432843] Re: Lubuntu failed to boot

[Erick Brunzell]

No idea why the explanatory text disappeared with comment #24 but that's
a pic of what the screen displays when the i386 image freezes.

This pic is what the screen displays when the amd64 image freezes.

** Attachment added: freeze_amd64.JPG
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432843/+attachment/4361871/+files/freeze_amd64.JPG

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

Title:
  Lubuntu failed to boot

Status in X.Org X server:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged

Bug description:
  The daily build of Lubuntu 20150316 failed to boot into the live
  session, and fails to install. During the boot session, the Lubuntu
  splash screen appears indicating that Lubuntu was loading. What
  follows next was a blank screen.

  Unfortunately, I cannot sumit the exact version of syslinux since the
  daily build could not boot into an interactive session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar 16 17:19:35 2015
  Dependencies:
   gcc-5-base 5-20150228-1ubuntu1
   libc6 2.19-15ubuntu2
   libgcc1 1:5-20150228-1ubuntu1
   mtools 4.0.18-2
   multiarch-support 2.19-15ubuntu2
  InstallationDate: Installed on 2015-03-05 (11 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303)
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1432843] Re: Lubuntu failed to boot

[Erick Brunzell]

** Attachment added: freeze_i386.JPG
   
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/1432843/+attachment/4361870/+files/freeze_i386.JPG

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

Title:
  Lubuntu failed to boot

Status in X.Org X server:
  Confirmed
Status in lubuntu-meta package in Ubuntu:
  Triaged
Status in xorg package in Ubuntu:
  Triaged

Bug description:
  The daily build of Lubuntu 20150316 failed to boot into the live
  session, and fails to install. During the boot session, the Lubuntu
  splash screen appears indicating that Lubuntu was loading. What
  follows next was a blank screen.

  Unfortunately, I cannot sumit the exact version of syslinux since the
  daily build could not boot into an interactive session.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: syslinux 3:6.03~pre18+dfsg-1ubuntu1
  ProcVersionSignature: Ubuntu 3.19.0-7.7-generic 3.19.0
  Uname: Linux 3.19.0-7-generic i686
  ApportVersion: 2.16.2-0ubuntu1
  Architecture: i386
  Date: Mon Mar 16 17:19:35 2015
  Dependencies:
   gcc-5-base 5-20150228-1ubuntu1
   libc6 2.19-15ubuntu2
   libgcc1 1:5-20150228-1ubuntu1
   mtools 4.0.18-2
   multiarch-support 2.19-15ubuntu2
  InstallationDate: Installed on 2015-03-05 (11 days ago)
  InstallationMedia: Lubuntu 15.04 Vivid Vervet - Alpha i386 (20150303)
  SourcePackage: syslinux
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/xorg-server/+bug/1432843/+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 1438605] [NEW] Apport reports xorg crash after booting Vivid live image

[Erick Brunzell]

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

Public bug reported:

Apport just asked if I wanted to file this report after booting the
Lubuntu Vivid image. I said yes in hopes that some info may be provided
in regards to bug #1432843.

ProblemType: Crash
DistroRelease: Ubuntu 15.04
Package: xserver-xorg-core 2:1.17.1-0ubuntu3
ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
Uname: Linux 3.19.0-10-generic x86_64
ApportVersion: 2.16.2-0ubuntu5
Architecture: amd64
CasperVersion: 1.357
Date: Mon Mar 30 22:36:48 2015
ExecutablePath: /usr/bin/Xorg
LiveMediaBuild: Lubuntu 15.04 Vivid Vervet - Beta amd64 (20150330)
ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
ProcEnviron:
 
Signal: 6
SourcePackage: xorg-server
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

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


** Tags: amd64 apport-crash vivid

** Information type changed from Private to Public

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

Title:
  Apport reports xorg crash after booting Vivid live image

Status in xorg-server package in Ubuntu:
  New

Bug description:
  Apport just asked if I wanted to file this report after booting the
  Lubuntu Vivid image. I said yes in hopes that some info may be
  provided in regards to bug #1432843.

  ProblemType: Crash
  DistroRelease: Ubuntu 15.04
  Package: xserver-xorg-core 2:1.17.1-0ubuntu3
  ProcVersionSignature: Ubuntu 3.19.0-10.10-generic 3.19.2
  Uname: Linux 3.19.0-10-generic x86_64
  ApportVersion: 2.16.2-0ubuntu5
  Architecture: amd64
  CasperVersion: 1.357
  Date: Mon Mar 30 22:36:48 2015
  ExecutablePath: /usr/bin/Xorg
  LiveMediaBuild: Lubuntu 15.04 Vivid Vervet - Beta amd64 (20150330)
  ProcCmdline: /usr/bin/X -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 
-nolisten tcp vt7 -novtswitch
  ProcEnviron:
   
  Signal: 6
  SourcePackage: xorg-server
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1438605/+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 1069964] Re: Unable to mount Blank CD-R disc. Location is already mounted.

[Erick Brunzell]

Actually a variant of this still exists in Ubuntu GNOME Vivid (as of
20150318) the difference being that, instead of getting the already
mounted warning as you do in a flashback session, in a GNOME Shell
session if you click the close button on the Open with CD/DVD creator or
Eject notification as soon as it closes it pops right back up until you
click it a second time.

I haven't checked the flashback session in Vivid yet but I will in the
next few days. I suspect that more than one process is attempting to
handle this, one being Nautilus . I'm clueless what the
other might be.

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

Title:
  Unable to mount Blank CD-R disc. Location is already mounted.

Status in OEM Priority Project:
  New
Status in glib2.0 package in Ubuntu:
  Confirmed
Status in unity-settings-daemon package in Ubuntu:
  Confirmed

Bug description:
  This error message comes up, while still able to burn, read/write etc. It 
occurs in quantal when inserting a CD/DVD into the drive, but it did not happen 
in precice.
  Screenshot:
  http://i47.tinypic.com/4v0aj6.png

  Burner: LG HL-DT-ST DVDRAM GH24NS90

  ProblemType: Bug
  DistroRelease: Ubuntu 12.10
  Package: gnome-settings-daemon 3.4.2-0ubuntu14
  ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
  Uname: Linux 3.5.0-17-generic x86_64
  NonfreeKernelModules: fglrx
  ApportVersion: 2.6.1-0ubuntu3
  Architecture: amd64
  Date: Mon Oct 22 19:50:35 2012
  ExecutablePath: /usr/lib/gnome-settings-daemon/gnome-fallback-mount-helper
  InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5)
  ProcEnviron:
   LANGUAGE=en_GB:en
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_GB.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-settings-daemon
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1069964/+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 1433246] [NEW] Menus in gnome-session-flashback following improper schema?

[Erick Brunzell]

Public bug reported:

The menus in flashback appear bloated and can't be properly edited.
Even the menus and buttons have icons settings aren't applied as they
should be. Also the Power Off and Restart menu buttons don't work so I
suspect that we're using the wrong schema?

This may be somewhat of a regression to bug #1380850 and bug #1267787
but I don't recall either of them also effecting the Power Off and
Restart menu buttons.

This testing was done on a fresh install of Ubuntu 20150317.1 amd64.

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: gnome-panel 1:3.14.0-1~ubuntu2
ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
Uname: Linux 3.19.0-9-generic x86_64
ApportVersion: 2.16.2-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME-Flashback:Unity
Date: Tue Mar 17 12:49:44 2015
GsettingsChanges:
 
InstallationDate: Installed on 2015-03-17 (0 days ago)
InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150317.1)
SourcePackage: gnome-panel
UpgradeStatus: No upgrade log present (probably fresh install)

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


** Tags: amd64 apport-bug vivid

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

Title:
  Menus in gnome-session-flashback following improper schema?

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  The menus in flashback appear bloated and can't be properly edited.
  Even the menus and buttons have icons settings aren't applied as they
  should be. Also the Power Off and Restart menu buttons don't work so I
  suspect that we're using the wrong schema?

  This may be somewhat of a regression to bug #1380850 and bug #1267787
  but I don't recall either of them also effecting the Power Off and
  Restart menu buttons.

  This testing was done on a fresh install of Ubuntu 20150317.1 amd64.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-panel 1:3.14.0-1~ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Mar 17 12:49:44 2015
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-03-17 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150317.1)
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1433246/+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 1433246] Re: Menus in gnome-session-flashback following improper schema?

[Erick Brunzell]

Other way to fix is simply to patch gnome-panel and set it to always
show images in menus.

I think that would be preferable. To me it always just looks odd that
those few objects in the tree view have no icons whereas all the other
objects do. Of course that was a change made in GNOME 2 some months or
years prior to the release of GNOME 3.

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

Title:
  Menus in gnome-session-flashback following improper schema?

Status in gnome-panel package in Ubuntu:
  New

Bug description:
  The menus in flashback appear bloated and can't be properly edited.
  Even the menus and buttons have icons settings aren't applied as they
  should be. Also the Power Off and Restart menu buttons don't work so I
  suspect that we're using the wrong schema?

  This may be somewhat of a regression to bug #1380850 and bug #1267787
  but I don't recall either of them also effecting the Power Off and
  Restart menu buttons.

  This testing was done on a fresh install of Ubuntu 20150317.1 amd64.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-panel 1:3.14.0-1~ubuntu2
  ProcVersionSignature: Ubuntu 3.19.0-9.9-generic 3.19.1
  Uname: Linux 3.19.0-9-generic x86_64
  ApportVersion: 2.16.2-0ubuntu3
  Architecture: amd64
  CurrentDesktop: GNOME-Flashback:Unity
  Date: Tue Mar 17 12:49:44 2015
  GsettingsChanges:
   
  InstallationDate: Installed on 2015-03-17 (0 days ago)
  InstallationMedia: Ubuntu 15.04 Vivid Vervet - Alpha amd64 (20150317.1)
  SourcePackage: gnome-panel
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-panel/+bug/1433246/+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 1425350] Re: Ubuntu GNOME Vivid - password won't unlock screen

[Erick Brunzell]

It looks good now. I even started with a fresh install of the 20150302
amd64 image and tried every display manager test I could imagine. This
also fixes bug #1425779.

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

Title:
  Ubuntu GNOME Vivid - password won't unlock screen

Status in Ubuntu GNOME:
  New
Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  I'm testing Ubuntu GNOME Vivid 20150224 i386 and performed an
  encrypted LVM install which appeared to complete successfully but when
  I let the screen lock my password is not accepted. I repeated the test
  to be sure it wasn't an error on my part. To reproduce follow these
  steps:

  (1) Install Ubuntu GNOME Vivid using any method. Be sure to choose
  auto-login = yes (I'm not sure that matters but at this point).

  (2) Once the installation is complete boot the new system and wait +5
  minutes for the screen to lock.

  (3) Attempt to unlock the screen and you'll find your password is not
  accepted.

  (4) Press Ctrl + Alt + F1 to open a TTY, enter your user name, and
  then your password which you'll find is accepted.

  (5) Type sudo-reboot and the system reboots as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-session 3.14.0-2ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 24 19:46:42 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha i386 (20150224)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-gnome/+bug/1425350/+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 1425779] Re: Ubuntu GNOME Vivid logs out to a blank screen

[Erick Brunzell]

Logout works fine if I boot using the systemd boot option from the
advanced grub menu.

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

Title:
  Ubuntu GNOME Vivid logs out to a blank screen

Status in gdm package in Ubuntu:
  New

Bug description:
  I'm testing Ubuntu GNOME Vivid 20150224 and I'm doing some follow up
  testing possibly related to bug #1425350.

  I find that simply choosing to log out results in a nearly blank
  screen and it's not possible to call a TTY, so a hard reset is needed
  to reboot and start over.

  Switching to lightdm with the lightdm-gtk-greeter makes logging out
  work OK but then the screensaver stops working altogether.

  Screenshot attached of the nearly blank screen - only the top
  panel appears and both mouse and keyboard appear to be locked.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gdm 3.14.1-0ubuntu1
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  NonfreeKernelModules: nvidia
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Wed Feb 25 19:41:39 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha i386 (20150224)
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gdm
  UpgradeStatus: No upgrade log present (probably fresh install)
  mtime.conffile..etc.gdm.custom.conf: 2015-02-25T12:08:35.021904

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/1425779/+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 1425350] Re: Ubuntu GNOME Vivid - password won't unlock screen

[Erick Brunzell]

Unlocking screen works fine if I boot using the systemd boot option from
the advanced grub menu.

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

Title:
  Ubuntu GNOME Vivid - password won't unlock screen

Status in gnome-session package in Ubuntu:
  Confirmed

Bug description:
  I'm testing Ubuntu GNOME Vivid 20150224 i386 and performed an
  encrypted LVM install which appeared to complete successfully but when
  I let the screen lock my password is not accepted. I repeated the test
  to be sure it wasn't an error on my part. To reproduce follow these
  steps:

  (1) Install Ubuntu GNOME Vivid using any method. Be sure to choose
  auto-login = yes (I'm not sure that matters but at this point).

  (2) Once the installation is complete boot the new system and wait +5
  minutes for the screen to lock.

  (3) Attempt to unlock the screen and you'll find your password is not
  accepted.

  (4) Press Ctrl + Alt + F1 to open a TTY, enter your user name, and
  then your password which you'll find is accepted.

  (5) Type sudo-reboot and the system reboots as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-session 3.14.0-2ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 24 19:46:42 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha i386 (20150224)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1425350/+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 1425350] Re: Ubuntu GNOME Vivid - password won't unlock screen

[Erick Brunzell]

BTW it's not hardware related as I've done two bare metal installs on
totally different hardware - one being an encrypted/LVM install and the
other using manual partitioning.

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

Title:
  Ubuntu GNOME Vivid - password won't unlock screen

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I'm testing Ubuntu GNOME Vivid 20150224 i386 and performed an
  encrypted LVM install which appeared to complete successfully but when
  I let the screen lock my password is not accepted. I repeated the test
  to be sure it wasn't an error on my part. To reproduce follow these
  steps:

  (1) Install Ubuntu GNOME Vivid using any method. Be sure to choose
  auto-login = yes (I'm not sure that matters but at this point).

  (2) Once the installation is complete boot the new system and wait +5
  minutes for the screen to lock.

  (3) Attempt to unlock the screen and you'll find your password is not
  accepted.

  (4) Press Ctrl + Alt + F1 to open a TTY, enter your user name, and
  then your password which you'll find is accepted.

  (5) Type sudo-reboot and the system reboots as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-session 3.14.0-2ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 24 19:46:42 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha i386 (20150224)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1425350/+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 1425350] Re: Ubuntu GNOME Vivid - password won't unlock screen

[Erick Brunzell]

This is not limited to encrypted installs. I just did a plain manual
install and got the same thing.

** Summary changed:

- Ubuntu GNOME encrypted install - password won't unlock screen
+ Ubuntu GNOME Vivid - password won't unlock screen

** Description changed:

  I'm testing Ubuntu GNOME Vivid 20150224 i386 and performed an encrypted
  LVM install which appeared to complete successfully but when I let the
  screen lock my password is not accepted. I repeated the test to be sure
  it wasn't an error on my part. To reproduce follow these steps:
  
- (1) Install Ubuntu GNOME Vivid using entire disc with LVM  encryption.
- Be sure to choose auto-login = yes (I'm not sure that matters but I see
- no point in having to enter both the encryption password and the login
- password on each boot).
+ (1) Install Ubuntu GNOME Vivid using any method. Be sure to choose auto-
+ login = yes (I'm not sure that matters but at this point).
  
  (2) Once the installation is complete boot the new system and wait +5
  minutes for the screen to lock.
  
  (3) Attempt to unlock the screen and you'll find your password is not
- accepted (neither is the encryption password - I checked).
+ accepted.
  
  (4) Press Ctrl + Alt + F1 to open a TTY, enter your user name, and then
  your password which you'll find is accepted.
  
  (5) Type sudo-reboot and the system reboots as expected.
  
  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-session 3.14.0-2ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 24 19:46:42 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha i386 (20150224)
  PackageArchitecture: all
  ProcEnviron:
-  TERM=xterm
-  PATH=(custom, no user)
-  XDG_RUNTIME_DIR=set
-  LANG=en_US.UTF-8
-  SHELL=/bin/bash
+  TERM=xterm
+  PATH=(custom, no user)
+  XDG_RUNTIME_DIR=set
+  LANG=en_US.UTF-8
+  SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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

Title:
  Ubuntu GNOME Vivid - password won't unlock screen

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I'm testing Ubuntu GNOME Vivid 20150224 i386 and performed an
  encrypted LVM install which appeared to complete successfully but when
  I let the screen lock my password is not accepted. I repeated the test
  to be sure it wasn't an error on my part. To reproduce follow these
  steps:

  (1) Install Ubuntu GNOME Vivid using any method. Be sure to choose
  auto-login = yes (I'm not sure that matters but at this point).

  (2) Once the installation is complete boot the new system and wait +5
  minutes for the screen to lock.

  (3) Attempt to unlock the screen and you'll find your password is not
  accepted.

  (4) Press Ctrl + Alt + F1 to open a TTY, enter your user name, and
  then your password which you'll find is accepted.

  (5) Type sudo-reboot and the system reboots as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-session 3.14.0-2ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 24 19:46:42 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha i386 (20150224)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1425350/+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 1425350] Re: Ubuntu GNOME Vivid - password won't unlock screen

[Erick Brunzell]

Additionally if I select logout I just go to a nearly blank screen and
can't even call a TTY, and if auto-login is turned off after entering
the password apport tries to report a bug but it's un-reportable:

lance@lance-AMD-desktop:~$ ls /var/crash
_usr_sbin_gdm.0.crash

Could bug #1421991 be related?

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

Title:
  Ubuntu GNOME Vivid - password won't unlock screen

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I'm testing Ubuntu GNOME Vivid 20150224 i386 and performed an
  encrypted LVM install which appeared to complete successfully but when
  I let the screen lock my password is not accepted. I repeated the test
  to be sure it wasn't an error on my part. To reproduce follow these
  steps:

  (1) Install Ubuntu GNOME Vivid using any method. Be sure to choose
  auto-login = yes (I'm not sure that matters but at this point).

  (2) Once the installation is complete boot the new system and wait +5
  minutes for the screen to lock.

  (3) Attempt to unlock the screen and you'll find your password is not
  accepted.

  (4) Press Ctrl + Alt + F1 to open a TTY, enter your user name, and
  then your password which you'll find is accepted.

  (5) Type sudo-reboot and the system reboots as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-session 3.14.0-2ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 24 19:46:42 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha i386 (20150224)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1425350/+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 1425350] Re: Ubuntu GNOME Vivid - password won't unlock screen

[Erick Brunzell]

Additionally if I select logout I just go to a nearly blank screen and
can't even call a TTY, and if auto-login is turned off after entering
the password aport tries to report a bug but it's un-reportable:

lance@lance-AMD-desktop:~$ ls /var/crash
_usr_sbin_gdm.0.crash

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

Title:
  Ubuntu GNOME Vivid - password won't unlock screen

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I'm testing Ubuntu GNOME Vivid 20150224 i386 and performed an
  encrypted LVM install which appeared to complete successfully but when
  I let the screen lock my password is not accepted. I repeated the test
  to be sure it wasn't an error on my part. To reproduce follow these
  steps:

  (1) Install Ubuntu GNOME Vivid using any method. Be sure to choose
  auto-login = yes (I'm not sure that matters but at this point).

  (2) Once the installation is complete boot the new system and wait +5
  minutes for the screen to lock.

  (3) Attempt to unlock the screen and you'll find your password is not
  accepted.

  (4) Press Ctrl + Alt + F1 to open a TTY, enter your user name, and
  then your password which you'll find is accepted.

  (5) Type sudo-reboot and the system reboots as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-session 3.14.0-2ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 24 19:46:42 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha i386 (20150224)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1425350/+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 1425350] Re: Ubuntu GNOME Vivid - password won't unlock screen

[Erick Brunzell]

Oops, didn't know some content had been auto-saved.

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

Title:
  Ubuntu GNOME Vivid - password won't unlock screen

Status in gnome-session package in Ubuntu:
  New

Bug description:
  I'm testing Ubuntu GNOME Vivid 20150224 i386 and performed an
  encrypted LVM install which appeared to complete successfully but when
  I let the screen lock my password is not accepted. I repeated the test
  to be sure it wasn't an error on my part. To reproduce follow these
  steps:

  (1) Install Ubuntu GNOME Vivid using any method. Be sure to choose
  auto-login = yes (I'm not sure that matters but at this point).

  (2) Once the installation is complete boot the new system and wait +5
  minutes for the screen to lock.

  (3) Attempt to unlock the screen and you'll find your password is not
  accepted.

  (4) Press Ctrl + Alt + F1 to open a TTY, enter your user name, and
  then your password which you'll find is accepted.

  (5) Type sudo-reboot and the system reboots as expected.

  ProblemType: Bug
  DistroRelease: Ubuntu 15.04
  Package: gnome-session 3.14.0-2ubuntu3
  ProcVersionSignature: Ubuntu 3.18.0-13.14-generic 3.18.5
  Uname: Linux 3.18.0-13-generic i686
  ApportVersion: 2.16.1-0ubuntu2
  Architecture: i386
  CurrentDesktop: GNOME
  Date: Tue Feb 24 19:46:42 2015
  InstallationDate: Installed on 2015-02-25 (0 days ago)
  InstallationMedia: Ubuntu-GNOME 15.04 Vivid Vervet - Alpha i386 (20150224)
  PackageArchitecture: all
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=set
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: gnome-session
  UpgradeStatus: No upgrade log present (probably fresh install)

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