Bug 1128806 - ERROR:core/monitor-xrandr.c:785:meta_monitor_manager_xrandr_apply_configuration: assertion failed: (width > 0 && height > 0)
Summary: ERROR:core/monitor-xrandr.c:785:meta_monitor_manager_xrandr_apply_configurati...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: mutter
Version: 20
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Florian Müllner
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-08-11 15:08 UTC by Bill Nottingham
Modified: 2015-06-29 22:01 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 22:01:22 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Bill Nottingham 2014-08-11 15:08:19 UTC
Description of problem:

When I have an external monitor connected to my laptop (in non-mirror mode), and I do the following:

1) Lock the screen (via hotkey or menu)
2) Close the lid

Mutter then aborts.

Version-Release number of selected component (if applicable):

mutter-3.12.2-1.fc20.x86_64
gnome-shell-3.12.2-2.fc20.x86_64
xorg-x11-server-Xorg-1.14.4-11.fc20.x86_64

(Using gnome-3.12 copr.)

How reproducible:

100%

Steps to Reproduce:
1. Plug in external monitor
2. Lock screen
3. Close lid

Actual results:

Opening lid yields black screen (b/c mutter aborted)

Expected results:

Opening lid yields normal unlock screen.

Additional info:

Relevant settings:
/etc/systemd/logind.conf:
HandleLidSwitch=ignore

Comment 1 Bill Nottingham 2014-08-12 12:35:57 UTC
Further testing seems to show that locking the screen is not a necessary step to reproducing the abort - just closing the lid with the external monitor attached can reproduce this error.

Comment 2 Fedora Admin XMLRPC Client 2015-02-12 11:04:50 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora End Of Life 2015-05-29 12:36:40 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Fedora End Of Life 2015-06-29 22:01:22 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.