gnome-control-center crashed when switching to mirror mode and monitors don't have matched resolution
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
Fix Released
|
High
|
Dirk Su | ||
gnome-control-center (Ubuntu) |
Fix Released
|
Low
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Dirk Su | ||
Kinetic |
Won't Fix
|
Undecided
|
Unassigned | ||
Lunar |
Fix Released
|
Undecided
|
Dirk Su |
Bug Description
[Impact]
gnome-control-
[Test case]
Mirror mode is only an option if there are only 2 monitors connected even if one monitor is disabled. A laptop's internal screen counts as one of the monitors.
This particular bug requires two screens that have a screen resolution that they don't both share. (See comment 12 for an example).
1. Connect the monitors
2. Open the GNOME Settings app (gnome-
3. On the left sidebar, click Displays to switch to the Display panel
4. Switch to mirror mode
3. gnome-control-
[Where problems could occur]
This only modifies the code related to mirror mode in Displays panel.
For Lunar, check variable (best_mode) before using it. This patch is backported from GNOME 45 Alpha.
For Jammy, include the Lunar patch and update the way to find cloning mode. These 2 additional patches are backported from gnome-control-
[Other info]
Two Merge Request are related
1. Check best_mode exist before adding flag (https:/
2. Use virtual clone modes when mirroring (https:/
description: | updated |
description: | updated |
Changed in gnome-control-center (Ubuntu Lunar): | |
status: | Confirmed → In Progress |
Changed in gnome-control-center (Ubuntu Jammy): | |
status: | New → In Progress |
assignee: | nobody → Dirk Su (dirksu) |
Changed in oem-priority: | |
status: | Confirmed → Fix Released |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps:
1. Look in /var/crash for crash files and if found run:
ubuntu-bug YOURFILE.crash
Then tell us the ID of the newly-created bug.
2. If step 1 failed then look at https:/ /errors. ubuntu. com/user/ ID where ID is the content of file /var/lib/ whoopsie/ whoopsie- id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us.
Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself.