date:20220130

[Desktop-packages] [Bug 1686081] Re: If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't work

2022-01-30 Thread Daniel van Vugt

Pretty sure this was fixed a few years ago, and regardless it is not
important anymore.

** Package changed: gtk+3.0 (Ubuntu) => ubuntu

** Changed in: ubuntu
   Status: In Progress => Fix Released

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

Title:
  If -synaptics is installed, GNOME Mouse & Touchpad Settings doesn't
  work

Status in Release Notes for Ubuntu:
  Fix Released
Status in Ubuntu:
  Fix Released
Status in gnome-control-center package in Ubuntu:
  Fix Released
Status in mutter package in Ubuntu:
  Fix Released
Status in xorg package in Ubuntu:
  Invalid
Status in xubuntu-meta package in Ubuntu:
  Fix Released
Status in gnome-control-center source package in Artful:
  Confirmed
Status in mutter source package in Artful:
  Confirmed
Status in xorg source package in Artful:
  Invalid
Status in xubuntu-meta source package in Artful:
  Fix Released

Bug description:
  I'm splitting this issue off from LP: #1685542 (which made xserver-
  xorg-input-all no longer recommend xserver-xorg-input-synaptics) for
  tracking the remaining issues.

  gnome-control-center only supports libinput. If xserver-xorg-input-
  synaptics is installed (because it's used by some desktops which
  haven't been ported to libinput yet), synaptics overrides libinput.
  That makes gnome-control-center's Mouse & Touchpad settings panel only
  show basic settings and important configurations don't work.

  Questions
  -
  1. Which desktops/apps still need -synaptics?
  - Unity
  - Xfce?
  - LXDE? LXQt?
  All the other major desktops have already been ported (LP: #1417980)

  2. Can these apps be ported or removed before 18.04 LTS is released?

  3. Can the desktops be ported and how bad is it if they are not ported
  and -synaptics is no longer available?

  4. If -synaptics can't be removed completely from 18.04 LTS, does it
  make sense to have gnome-control-center Conflicts: xserver-xorg-input-
  synaptics?

  5. Is there any other way we can fix this conflict?

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-release-notes/+bug/1686081/+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 1958673] Re: SRU Request for upgrade to X-Server 1.20.14 in focal/20.04-LTS

2022-01-30 Thread Daniel van Vugt

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

** Also affects: psychtoolbox-3 (Ubuntu Jammy)
   Importance: Undecided
   Status: New

** Changed in: xorg-server (Ubuntu Jammy)
   Status: New => Fix Released

** No longer affects: psychtoolbox-3 (Ubuntu Jammy)

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

Title:
  SRU Request for upgrade to X-Server 1.20.14 in focal/20.04-LTS

Status in psychtoolbox-3 package in Ubuntu:
  New
Status in xorg-server package in Ubuntu:
  Fix Released
Status in xorg-server source package in Jammy:
  Fix Released

Bug description:
  I was asked by one of your X-Server maintainers (Timo) to file a bug
  report here to request an upgrade to the current X-Server 1.20.14 for
  focal / Ubuntu 20.04-LTS from X-Server 1.20.13. I think this is called
  a SRU?

  The 1.20.14 version contains patches to fix some recent CVE's which
  are already in your 1.20.13 server, and additionally two patches from
  myself, cfe. the following merge request for the backport:

  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/778

  Therefore an upgrade to 1.20.14 would add my two patches from that
  merge request. These are trivial backports from master and X-Server
  21.1, which did not need any adaptation of the patches.

  One patch is a bug fix for a bug present in server 1.20 since day one.

  The other patch can be considered a regression fix for Ubuntu
  20.04-LTS on hybrid graphics laptops with Intel iGPU + some other
  dGPU, although this is not a regression in the X-Server itself, but
  how the video driver selection by current Ubuntu interacts with the
  server. See explanation below why i consider it a regression fix.

  One patch fixes a bug: "Fix RandR leasing for more than 1
  simultaneously active lease."

  The bug is a trivial code bug, which was there since RandR leasing was
  introduced into the 1.20 server by Keith Packard. Keith has reviewed
  my bug description and fix and agreed that it is indeed a bug and that
  my fix is correct. See the following merge request for the master
  branch with Keith's R-b in the discussion:

  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/767

  The bug triggers whenever more than one RandR output gets leased out
  simultaneously during a session. It doesn't matter if multiple outputs
  get leased to a single client application, or if multiple separate
  client applications each lease out one output, or any mix of these.

  Only the very last output leased in a session can be released back to
  the server by the corresponding client (voluntarily or due to client
  exit, crash etc.). All other previously leased out outputs by the same
  or other clients will be completely dead and unusable until the
  X-Session is terminated and the X-Server restarted. So this can be
  seen as a denial of service bug.

  Typically affected applications would be Vulkan applications using the
  direct display extension, e.g., the octave-psychtoolbox-3 package in
  Ubuntu for scientific/medical research, or high end video games which
  may use this functionality, and probably most prominently VR
  applications built with SteamVR or the OpenXR Monado runtime and VR
  compositor.

  It has been tested extensively by myself on single X-Screen and dual
  X-Screen setups with 1, 2 and three displays, leasing out 1, 2 or 3
  outputs.

  
  The second patch is "modesetting: Allow Present flips with mismatched stride 
on atomic drivers."

  It applies to the xorg-video-modesetting ddx.

  It does not fix a bug in the strict sense, but it does improve the
  quality and performance of unredirected fullscreen applications like
  video games or scientific software like octave-psychtoolbox-3 under
  PRIME render offload in a way that turns them from "technically
  correct behavior, but unusable in practice" to "good". The patch is
  based on a tip by Michel Daenzer from AMD. See the following original
  merge request for X-Server master for details:

  https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/740

  On modern kernels and atomic modesetting drivers, the patch allows the
  modesetting-ddx to use page flipping for fullscreen applications even
  if the Pixmap stride between the display gpu (iGPU, e.g., Intel, AMD)
  and the render offload gpu (e.g., AMD, NVidia) is mismatched, as
  atomic modesetting drivers can easily handle that.

  Without the patch, on such mismatched stride configurations, rejecting
  the pageflip, normally the X-Server and modesetting-ddx would fall
  back to a fullscreen copy swap, executed via glamor and therefore Mesa
  as a framebuffer copy from application backbuffer to system/X-Server
  frontbuffer. This increases required memory bandwidth and thereby
  reduces cpu and gpu performance, increases latency and the potential
  for skipped

[Desktop-packages] [Bug 1846205] Re: Please add configuration option to show / hide mounted drives in Ubuntu Dock

2022-01-30 Thread Launchpad Bug Tracker

This bug was fixed in the package gnome-control-center - 1:41.1-1ubuntu3

---
gnome-control-center (1:41.1-1ubuntu3) jammy; urgency=medium

  [ Marco Trevisan (Treviño) ]
  * debian/patches: Refresh
  * d/p/u/display-Allow-fractional-scaling-to-be-enabled.patch:
Ensure renderer is initialized.
It may not be the case when running with non-patched mutter, so not a
bug, but this helps in development scenarios.
  * d/p/u/Allow-tweaking-some-settings-for-Ubuntu-Dock.patch:
- Do not crash if gedit is not installed
  * ubuntu-panel: Save dock monitor by connector and support primary monitor
Dash to dock used to use the shell's monitor ID to pick the monitor in
which should be used, however this is not something that worked well
in case one switches configuration or uses a laptop in different
scenarios as the dock may be moved to the wrong display.
As per this:
 - Add a "Primary monitor" item, to bind the dock position to the
   primary monitor (whatever it is)
 - Store the selected monitor by its connector
 - Add backward compatibility support for the old 'preferred-monitor'
   key, and migrate to it.
Related to: https://github.com/micheleg/dash-to-dock/pull/1630
  * multitasking-panel: Sync workspace and monitor isolation dock settings.
When using ubuntu-dock the multitasking panel setting doesn't fully
apply, because even though the user selects to isolate workspaces, the
dock may still continue to show icons from all the workspaces.
As per this, ensure that the settings are applied also to the dock, plus
include dock-specifc settings to control multi-monitor behavior.
  * ubuntu-panel: Use libhandy widgets for the dock section.
This will help with Gtk and libadwaita porting in future, so let's just
such widgets that are also more integrated with the current g-c-c design
  * ubuntu-panel: Use more modern libadwaita widgets for dock settings.
This should make gtk4 porting even easier, plus we can be more consitent
with the majority of other g-c-c panels.
  * ubuntu-panel: Add dock specific dialog to control.
Add a dock settings dialog to control some more specific settings.
So far we only support toggling the visualization of device and trash
icons, but this could be extended more in future. (LP: #1846205)

  [ Muqtxdir ]
  * ubuntu-panel: Improve appearance-page to use more consistent look
- Make use of HdyPrefrencesPage for Appearance-panel.
- Make use of HdyPrefrencesGroup for Window colors.
- Make use of custom css style classes from appearance.css
- Update the light/dark variant preview images (LP: #1943849)

 -- Marco Trevisan (Treviño)   Mon, 31 Jan 2022
03:42:47 +0100

** Changed in: gnome-control-center (Ubuntu)
   Status: In Progress => Fix Released

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

Title:
  Please add configuration option to show / hide mounted drives in
  Ubuntu Dock

Status in gnome-control-center package in Ubuntu:
  Fix Released

Bug description:
  Reference this forum thread:
  https://ubuntuforums.org/showthread.php?t=2427998

  I have upgraded from Disco to Eoan Beta and have found that the dock
  permanently displays and icon for my Google Account's shared files. I
  can make the icon disappear from the dock via Gnome Settings -> Online
  Accounts -> Google -> Untick 'Files'. USB devices also show up in this
  way.

  It appears that this is a new Dock feature which can only be turned
  off / on via the command line thus:

  gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false
  gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts true

  I believe average users should be able to configure this via a GUI, so
  can this be incorporated into the Gnome Control Center for the 20.04
  LTS release?

  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
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 13:27:05 2019
  InstallationDate: Installed on 2019-09-23 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1846205/+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 1943849] Re: [FFe] improve the appearance-page in gnome-control-center

2022-01-30 Thread Launchpad Bug Tracker

This bug was fixed in the package gnome-control-center - 1:41.1-1ubuntu3

---
gnome-control-center (1:41.1-1ubuntu3) jammy; urgency=medium

[ Marco Trevisan (Treviño) ]
* debian/patches: Refresh
* d/p/u/display-Allow-fractional-scaling-to-be-enabled.patch:
Ensure renderer is initialized.
It may not be the case when running with non-patched mutter, so not a
bug, but this helps in development scenarios.
* d/p/u/Allow-tweaking-some-settings-for-Ubuntu-Dock.patch:
- Do not crash if gedit is not installed
* ubuntu-panel: Save dock monitor by connector and support primary monitor
Dash to dock used to use the shell's monitor ID to pick the monitor in
which should be used, however this is not something that worked well
in case one switches configuration or uses a laptop in different
scenarios as the dock may be moved to the wrong display.
As per this:
- Add a "Primary monitor" item, to bind the dock position to the
primary monitor (whatever it is)
- Store the selected monitor by its connector
- Add backward compatibility support for the old 'preferred-monitor'
key, and migrate to it.
Related to: https://github.com/micheleg/dash-to-dock/pull/1630
* multitasking-panel: Sync workspace and monitor isolation dock settings.
When using ubuntu-dock the multitasking panel setting doesn't fully
apply, because even though the user selects to isolate workspaces, the
dock may still continue to show icons from all the workspaces.
As per this, ensure that the settings are applied also to the dock, plus
include dock-specifc settings to control multi-monitor behavior.
* ubuntu-panel: Use libhandy widgets for the dock section.
This will help with Gtk and libadwaita porting in future, so let's just
such widgets that are also more integrated with the current g-c-c design
* ubuntu-panel: Use more modern libadwaita widgets for dock settings.
This should make gtk4 porting even easier, plus we can be more consitent
with the majority of other g-c-c panels.
* ubuntu-panel: Add dock specific dialog to control.
Add a dock settings dialog to control some more specific settings.
So far we only support toggling the visualization of device and trash
icons, but this could be extended more in future. (LP: #1846205)

[ Muqtxdir ]
* ubuntu-panel: Improve appearance-page to use more consistent look
- Make use of HdyPrefrencesPage for Appearance-panel.
- Make use of HdyPrefrencesGroup for Window colors.
- Make use of custom css style classes from appearance.css
- Update the light/dark variant preview images (LP: #1943849)

-- Marco Trevisan (Treviño) Mon, 31 Jan 2022
03:42:47 +0100

** Changed in: gnome-control-center (Ubuntu)
Status: Fix Committed => Fix Released

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

Title:
[FFe] improve the appearance-page in gnome-control-center

Status in gnome-control-center package in Ubuntu:
Fix Released

Bug description:
[Changes:]

1. The Appearance-panel in gnome-control-center uses 2 GtkBox to
center the Windows color one at the start and one at end. The problem
in behavior arises when the window is resized one of the
GtkFlowBoxChild moves to next line even though there is plenty of
space in the current line or when the Window is maximized. Specially
noticed with lower-resolution dispalys

With the use of HdyPrefrencesPage and HdyPrefrencesGroup, the Window
colors section stays fixed even when the window is resized or
maximized.

2. The Appearance-panel has extra border around the Page,
HdyPrefrencesPage removes the extra-border

3. The Window colors section uses thumbnails that do not resemble with
current Yaru's look offered in 21.10 and have purple-gradient color as
the background.

With the use of style=content-view and icon-dropshadow the thumbnails
stand out better in the absence of purple gardient background.

4. The Window colors section has orange as the color for the selected
GtkFlowBoxChild, With the use of margin as 2px the selected
GtkFlowBoxChild has a 2px orange-color border.

5. The Dock-section makes use of rounded corners around GtkListBox by using
style=content

6. The Dock-section makes use of HdyActionRow to replace the use of
GtkGrid, GtkLabel, GtkListBoxRow.

Orignal-issue:
https://gitlab.gnome.org/Community/Ubuntu/gnome-control-center/-/issues/3

MR: https://gitlab.gnome.org/Community/Ubuntu/gnome-control-
center/-/merge_requests/4

see: screenshots and screen-recordings below for before and after

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

--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packag

[Desktop-packages] [Bug 1954724] Re: Removing unattended-upgrades removes ubuntu-server-minimal

2022-01-30 Thread Matthew Ruffell

This has been fixed as of ubuntu-meta 1.474
https://launchpad.net/ubuntu/+source/ubuntu-meta/1.474

$ sudo apt rdepends unattended-upgrades
unattended-upgrades
Reverse Depends:
  Recommends: python3-software-properties
  Recommends: ubuntu-mate-desktop
  Recommends: ubuntu-mate-core
  Depends: freedombox
  Recommends: fbx-all
  Recommends: ubuntu-server-minimal
  Recommends: ubuntu-server

** Changed in: ubuntu-meta (Ubuntu Jammy)
   Status: Confirmed => Fix Released

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

Title:
  Removing unattended-upgrades removes ubuntu-server-minimal

Status in ubuntu-meta package in Ubuntu:
  Fix Released
Status in ubuntu-meta source package in Impish:
  Confirmed
Status in ubuntu-meta source package in Jammy:
  Fix Released

Bug description:
  On Impish and later, removing unattended-upgrades also removes ubuntu-
  server-minimal due to ubuntu-server-minimal depending on unattended-
  upgrades

  $ sudo apt remove unattended-upgrades
  ...
  The following packages will be REMOVED:
    ubuntu-server-minimal unattended-upgrades
  0 upgraded, 0 newly installed, 2 to remove and 0 not upgraded.

  This behaviour has changed since ubuntu-meta 1.471 [1] when the
  ubuntu-server-minimal metapackage was introduced, declaring
  unattended-upgrades as Depends.

  [1] https://launchpadlibrarian.net/550345392/ubuntu-
  meta_1.470_1.471.diff.gz

  On Focal, there was no such behaviour on a fresh ubuntu-server
  install:

  $ sudo apt remove unattended-upgrades
  ...
  The following packages will be REMOVED:
    unattended-upgrades
  0 upgraded, 0 newly installed, 1 to remove and 9 not upgraded.

  Removing unattended-upgrades is quite popular amongst our users, and
  they should be allowed to remove the package without removing the
  ubuntu-server-minimal metapackage.

  Looking at the source package for ubuntu-meta, unattended-upgrades is
  only Depends for ubuntu-server-minimal, maybe we should simply remove
  it, or instead, change to recommends?

  $ grep -Rin "unattended-upgrades" .
  ./server-minimal-armhf:23:unattended-upgrades
  ./server-minimal-riscv64:23:unattended-upgrades
  ./server-minimal-arm64:23:unattended-upgrades
  ./server-minimal-ppc64el:23:unattended-upgrades
  ./server-minimal-s390x:24:unattended-upgrades
  ./server-minimal-amd64:23:unattended-upgrades

  $ sudo apt rdepends unattended-upgrades
  unattended-upgrades
  Reverse Depends:
    Recommends: python3-software-properties
    Recommends: ubuntu-mate-desktop
    Recommends: ubuntu-mate-core
    Depends: freedombox
    Recommends: fbx-all
    Depends: ubuntu-server-minimal

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/1954724/+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 1846205] Re: Please add configuration option to show / hide mounted drives in Ubuntu Dock

2022-01-30 Thread Treviño

** Changed in: gnome-control-center (Ubuntu)
   Status: Triaged => In Progress

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

Title:
  Please add configuration option to show / hide mounted drives in
  Ubuntu Dock

Status in gnome-control-center package in Ubuntu:
  In Progress

Bug description:
  Reference this forum thread:
  https://ubuntuforums.org/showthread.php?t=2427998

  I have upgraded from Disco to Eoan Beta and have found that the dock
  permanently displays and icon for my Google Account's shared files. I
  can make the icon disappear from the dock via Gnome Settings -> Online
  Accounts -> Google -> Untick 'Files'. USB devices also show up in this
  way.

  It appears that this is a new Dock feature which can only be turned
  off / on via the command line thus:

  gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts false
  gsettings set org.gnome.shell.extensions.dash-to-dock show-mounts true

  I believe average users should be able to configure this via a GUI, so
  can this be incorporated into the Gnome Control Center for the 20.04
  LTS release?

  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
  ApportVersion: 2.20.11-0ubuntu7
  Architecture: amd64
  CurrentDesktop: ubuntu:GNOME
  Date: Tue Oct  1 13:27:05 2019
  InstallationDate: Installed on 2019-09-23 (7 days ago)
  InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
  SourcePackage: gnome-control-center
  UpgradeStatus: Upgraded to eoan on 2019-09-27 (3 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1846205/+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 1943849] Re: [FFe] improve the appearance-page in gnome-control-center

2022-01-30 Thread Treviño

** Changed in: gnome-control-center (Ubuntu)
Status: In Progress => Fix Committed

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

Title:
[FFe] improve the appearance-page in gnome-control-center

Status in gnome-control-center package in Ubuntu:
Fix Committed