#795384 mate-control-center: can only use mirror with two monitors

Package:
mate-control-center
Source:
mate-control-center
Description:
utilities to configure the MATE desktop
Submitter:
Francesco Potortì
Date:
2015-08-13 20:15:10 UTC
Severity:
normal
#795384#5
Date:
2015-08-13 15:09:26 UTC
From:
To:
While version 1.8.3 of mate-display-properties crashed as soon as
called, this version does not crash.  However, the problem persists: I
cannot use any more my two-monitor config.

When mate-display-properties is called, it shows two monitors, but
apparently cannot detect their properties and proposes a mirror conf.
When forced to use both, and the different resolutions are manually set,
nothing happnes even after pressing the Apply button.  Moreover, if I
press the Make default button, it says

Error creating textual authentication agent: Error opening current
controlling terminal for the process (`/dev/tty'): No such device or
address

The latter error also happens when detaching the second monitor and
using one only (as I am forced to do now).

#795384#10
Date:
2015-08-13 15:19:23 UTC
From:
To:
Can you please stop reporting bugs while we are currently working on uploading MATE 1.10?

This is currently work-in-progress and hence bugs are to be expected. It's called "unstable" for a reason and you should refrain from using it unlesd you can fix such issues yourself.

FFS, do you really think we maintainers wouldn't notice such apparent bugs like applications crashing immediately under normaö conditions? Those bugs reports are an annoyance and completely unnecessary.

End of rant.

Adrian

#795384#15
Date:
2015-08-13 15:48:21 UTC
From:
To:
[ rant moved below to concentrate on the important things ]

The latest version of mate-control-center DOES NOT CRASH.  The problem
is the application is *not able to detect the monitor properties* and is
*not able to save* the manually-defined properties.  My bug report
contains a detailed description (from a user's point of view).

The version that crashes for me is the one in testing, which is supposed
to be stable enough but is not for me.  Should I report the crash
against 1.8.3 or is it unnecessary?

[ end of important things, rant follows moved from above ]

I just sent one, and I have no idea what you are working on.  While I
and others are grateful for your work, I certainly do not follow it
closely enough to know what you are doing :)

I expect them and I am willing to report those, hoping that it's useful
for you to know.  If it is not, just ignore them, but I think you'd
better read them before discarding them...

I think you are wrong, but thanks for your work anyway.