After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 590019 - disables compiz and does not return properly
disables compiz and does not return properly
Status: RESOLVED NOTGNOME
Product: gnome-control-center
Classification: Core
Component: Display
2.26.x
Other All
: Normal minor
: ---
Assigned To: Soren Sandmann Pedersen
Control-Center Maintainers
Depends on:
Blocks: randr-tracker
 
 
Reported: 2009-07-28 14:17 UTC by Uwe Dippel
Modified: 2011-02-01 03:30 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26



Description Uwe Dippel 2009-07-28 14:17:56 UTC
Please describe the problem:
Attaching a monitor to the notebook, and configuring it to not mirror (2 screens side by side), I am asked to log off and log on again. Then, both displays were available, as expected, but unaccelerated. Maybe this is the correct case with 'intel' driver?
Whatever. I unplugged the second monitor, set the display properties to a single display, and logged off. It came back, without compiz. Whatever I did, it would not work. Even 'compiz' on the command line would get stuck.
In the end, I removed /etc/X11/xorg.conf, started from scratch, and then it worked. But still, I always need to start compiz separately; Gnome does not remember the settings

Steps to reproduce:
1. Attach second monitor
2. Log off and on
3. Compiz is lost


Actual results:
compiz doesn't run and can't be started

Expected results:
compiz running on both screens (?)

Does this happen every time?
Tried once only

Other information:
Comment 1 André Klapper 2009-07-29 17:45:07 UTC
So does this also happen without Compiz?
Comment 2 Uwe Dippel 2009-07-30 04:49:33 UTC
No, I actually found what happened: It had asked me if I wanted to auto-update the virtual desktop size (1600 + 1024 pixel width); and I had answered 'yes'. And then that other Xorg-bug came in (Ubuntu only??), that doesn't handle virtual sizes above 2048 properly; and then compiz would not start, until the user removes the extended virtual desktop size.

But the 'thing' is still buggy, and doesn't work with no-EDID monitors here. Should I file a different request?
Here FYI what goes on: The external 1600x1200 is not found. So I have to 
% xrandr --newmode "1600x1200" 234.76  1600 1720 1896 2192  1200 1201 1204 1260  -HSync +Vsync
% xrandr --addmode VGA 1600x1200
after each and every logon, then only the 'Display' will allow me to set the 'unknown' monitor to 1600x1200, 85 Hz, then only can I set the laptop monitor to 85 Hz as well, place the laptop monitor underneath the external one (1200 + 768 is just below 2048), and 'apply' and confirm I want to keep those.
At each logon. Here I'd expect gnome-display-properties to remember the settings; maybe even the modeline (?). So that - at least after the xrandr commands as above, I find back my old settings and positionings of the earlier setups.

Comment 3 Bastien Nocera 2011-02-01 03:30:59 UTC
(In reply to comment #2)
> No, I actually found what happened: It had asked me if I wanted to auto-update
> the virtual desktop size (1600 + 1024 pixel width); and I had answered 'yes'.
> And then that other Xorg-bug came in (Ubuntu only??),
<snip>

This is definitely not the display panel shipped by GNOME, but a tool shipped by your distribution. You'll need to go to them for support.