gnome-control-center does not respond after we set the resolution 320x180

Bug #1772831 reported by Leon Liao
18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OEM Priority Project
Fix Released
Critical
Leon Liao
gnome-control-center
Fix Released
Medium
mutter (Ubuntu)
Fix Released
High
Andrea Azzarone
Bionic
Fix Released
Undecided
Unassigned

Bug Description

[ Description ]

gnome-control-center does not respond after we set the resolution 320x180

[ Test case ]

Open gnome-control-center -> Displays
Low resolutions (such as 320x180) should not be listed.

Trying to set the lowst listed resolution, should just apply without breaking gnome-control-center.

[ Regression potential ]

No alternative resolutions are shown in g-c-c

---

Expected results: shows the countdown dialog
Actual results: the countdown dialog doesn't show. Only mouse cursor can move. All of the buttons/icons don't respond.

Note1: When I executed "gnome-settings-daemon -o -v | tee gcc.log", the count-down dialog shows up!

Notebook: Dell XPS 13

Revision history for this message
Leon Liao (lihow731) wrote :

The attached movie shows how to reproduce this bug.

Changed in oem-priority:
importance: Undecided → Critical
Changed in oem-priority:
status: New → Confirmed
Revision history for this message
Will Cooke (willcooke) wrote :

Does it work at 800 x 600?

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you attach your journal log after getting the issue?

Revision history for this message
Will Cooke (willcooke) wrote :

Leon mentioned by email that resolutions < 800 x 600 are not shown under Xenial.

Revision history for this message
Leon Liao (lihow731) wrote :

@Will,

The OS works well in the resolution 800x600.

@Sebastien,

The attached file is the output of "journalctl".

Revision history for this message
Sebastien Bacher (seb128) wrote :

Could you install gnome-session and see if you get the same issue in an GNOME session (instead of Ubuntu), the log has those errors

gnome-shell[3484]: clutter-actor.c:10049: Actor 'dashtodockDashScrollview' tried to allocate a size of 132.00 x -3.00
gnome-control-c[5021]: Error calling GetCurrentState: Timeout was reached
gsd-xsettings[3602]: Failed to get current display configuration state: Timeout was reached

could be a dashtodock issue...

Revision history for this message
Leon Liao (lihow731) wrote :

I installed the gnome-session and select the gdm3.

At first, The resolution can be set to 320x180, the countdown dialog show up.
But, I fail to set the resolution to 320x180 at second time.

The error message looks different.

The attached file is the output of journalctl with gnome-session.

Changed in gnome-control-center (Ubuntu):
importance: Undecided → High
status: New → In Progress
Changed in gnome-control-center:
importance: Unknown → Medium
status: Unknown → Confirmed
Andrea Azzarone (azzar1)
Changed in gnome-control-center (Ubuntu):
assignee: nobody → Andrea Azzarone (azzar1)
Revision history for this message
Andrea Azzarone (azzar1) wrote :
Changed in gnome-control-center:
status: Confirmed → Fix Released
Changed in oem-priority:
assignee: nobody → Leon Liao (lihow731)
Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

This will be fixed in mutter (3.29.90-1)

description: updated
Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

The fix for this is included in mutter 3.29.90-1

affects: gnome-control-center (Ubuntu) → mutter (Ubuntu)
Changed in mutter (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 3.29.90-1

---------------
mutter (3.29.90-1) experimental; urgency=medium

  * Team upload
  * New upstream release
    - Don't try to use an invalid monitor mode to figure out scaling
      (LP: #1723615)
  * d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch,
    d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch,
    d/p/wayland-Nullify-monitor-resources-when-updating-outputs.patch,
    d/p/monitor-manager-Filter-out-low-screen-resolutions.patch,
    d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch,
    d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch:
    Drop patches that were applied upstream
  * d/libmutter-3-0.symbols: Update
    - Ignore ABI change in experimental: removal of
      meta_prefs_override_preference_schema()
    - Add Breaks on previous experimental gnome-shell

 -- Simon McVittie <email address hidden> Wed, 01 Aug 2018 09:03:19 +0100

Changed in mutter (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Please test proposed package

Hello Leon, or anyone else affected,

Accepted mutter into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/mutter/3.28.3-2~ubuntu18.04.1 in a few hours, and then in the -proposed repository.

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

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

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

Changed in mutter (Ubuntu Bionic):
status: New → Fix Committed
tags: added: verification-needed verification-needed-bionic
Revision history for this message
Leon Liao (lihow731) wrote :

I verified the mutter=3.28.3-2~ubuntu18.04.1 on Dell Inspiron 5480.
The resolutions is keeped larger than 800x512.

tags: added: verification-done-bionic
removed: verification-needed-bionic
Leon Liao (lihow731)
Changed in oem-priority:
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package mutter - 3.28.3-2~ubuntu18.04.1

---------------
mutter (3.28.3-2~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport from unstable to bionic

mutter (3.28.3-2) unstable; urgency=medium

  * Team upload

  [ Iain Lane ]
  * debian/gbp.conf: Set the upstream branch to upstream/3.28.x, since we've
    branched for experimental now.

  [ Marco Trevisan (Treviño) ]
  * d/p/native-gpu-Handle-drmModeSetCrtc-failing-gracefully.patch:
    - Avoid crashing when warning about wrongly set crtc mode
      (LP: #1754949)
  * d/p/gpu-kms-Don-t-crash-if-drmModeGetResources-returns-N.patch:
    - Don't crash if drmModeGetResources returns NULL (LP: #1767956)
  * d/p/window-wayland-Always-update-monitor-for-non-user-ops.patch:
    - Always update monitor in wayland, avoiding crash (LP: #1784398)
  * d/p/monitor-manager-Filter-out-low-screen-resolutions.patch:
    - Don't return screen resolutions that can't be applied (LP: #1772831)
  * d/p/window-Don-t-refuse-to-move-focus-to-the-grab-window.patch,
    d/p/window-Explicitly-exclude-unmanaging-window-from-focus-ag.patch:
    - Don't crash if a modal dialog closes while being dragged
      (LP: #1422253)
  * d/p/monitor-Use-current-monitor-mode-to-check-whether-active.patch:
    - Don't try to use an invalid monitor mode to figure out scaling
      (LP: #1723615)

  [ Simon McVittie ]
  * Sort patch series in upstream order, with patches applied upstream
    first
  * d/copyright: Remove obsolete FSF postal addresses
  * Standards-Version: 4.1.5 (no changes required)
  * Set Rules-Requires-Root to no
  * Update symbols file

mutter (3.28.3-1~ubuntu18.04.1) bionic; urgency=medium

  * No-change backport to bionic (LP: #1783311)

mutter (3.28.3-1) unstable; urgency=medium

  * New upstream release
  * d/p/backends-Add-logical-monitor-monitor-output-crtc-ref-chai.patch,
    d/p/backends-Move-MetaOutput-crtc-field-into-private-struct.patch,
    d/p/clutter-device-evdev-Get-devices-from-main-seat-if-no-rea.patch,
    d/p/clutter-evdev-Don-t-ignore-CAPS-lock-as-modifier.patch,
    d/p/clutter-evdev-ignore-injected-events-from-IM.patch,
    d/p/clutter-seat-evdev-Add-function-to-get-device-by-id.patch,
    d/p/device-manager-evdev-Add-main-seat-to-seats-by-default.patch,
    d/p/device-manager-evdev-Free-the-main-seat-on-finalize.patch,
    d/p/device-manager-evdev-Set-and-unset-the-stage-for-the-main.patch,
    d/p/frames-Allow-for-unknown-mouse-buttons.patch,
    d/p/frames-Handle-touch-events.patch,
    d/p/frames-Make-1st-button-motion-handlers-take-generic-event.patch,
    d/p/renderer-native-Don-t-crash-if-the-FB-surface-can-t-be-lo.patch,
    d/p/wayland-Compare-geometries-after-chaining-up.patch,
    d/p/wayland-Don-t-reset-input-focus-on-text-commit.patch,
    d/p/wayland-Use-cursor-position-in-logical-monitor.patch,
    d/p/wayland-update-enter-leave-output-after-effects.patch,
    d/p/window-actor-add-new-signal-effects-completed.patch:
    Remove patches already applied on 3.28 branch

 -- Marco Trevisan (Treviño) <email address hidden> Fri, 03 Aug 2018 05:20:10 +0100

Changed in mutter (Ubuntu Bionic):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

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

Changed in oem-priority:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.