We can't set turn_on_external_monitors_at_startup to True again. We
already had that, and it causes external monitors to get powered off.
This means that you can't use a docked laptop with an external monitor
any more, since we don't have any cleverness to detect whether the lid
is closed at startu
Just confirming, for me the bug manifests differently: I have a
1280x1024 external monitor, and X starts in that mode (with a little
help in xorg.conf). However, g-s-d tries to be too clever and switches
it to 1024x768, presumably because xrandr thinks that this is the
highest common resolution wit
No doubt there are many related bugs, some may be duplicates, others
not. I'm certainly not sure.
But we're a few days from iso-testing, and one week from final. Do we
actually plan to release with this bug?
Should we not at least have some coherent reference in the release
notes?
If we release
Feel free to rename the bug title as it doesn't seem to fit anymore. :-)
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu
bug bug #638680 seems similar as well
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://list
which is bug #314057 on launchpad
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ub
one part of the issue could also be
https://bugzilla.gnome.org/show_bug.cgi?id=572502
"gnome-display-properties should pick the preferred xrandr mode"
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a member of U
upstream comment from an IRC discussion about the issue
"I'll happily include a patch that makes the boot-time
configuration conditional
with some use_boot_time_configuration key or something
reasonably-named
use_boot_time_configuration or use_xorg_configuration (the
reverse)?
the gsd-xrandr-manager.c code has
"if (!apply_stored_configuration_at_startup (manager,
GDK_CURRENT_TIME)) /* we don't have a real timestamp at startup anyway */
if (!apply_default_configuration_from_file (manager,
GDK_CURRENT_TIME))
apply_default_
> I'm just trying to show that this effects a lot of different hardware
and I do see this as a true "show-stopper"!
How do you know that? How much hardware did you try? How do you know if
doesn't do better job on some configurations and breaks some others?
What solution do you suggest? Changing t
Subscribing ubuntu-release instead of myself; Erick, I'm no longer the
Ubuntu release manager, so please use the role account instead for
issues such as this.
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a memb
I filed a new one:
https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/654660
Not to be a pain in the rear but I didn't see an exact parallel to what
I've experienced, and I thought it couldn't hurt to gather info.
I'm just trying to show that this effects a lot of different hardware
and I do se
Note also that before bug 646076 gets fixed, the user can not make any
system-wide screen settings.
The recent g-s-d change also made bug 641525, bug 645377 and bug 646474
appear, but I am not marking them as duplicates since I believe xorg is
generating wrong modes in these cases which should be
** Changed in: gnome-settings-daemon (Ubuntu)
Assignee: (unassigned) => Sebastien Bacher (seb128)
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
u
We had a discussion on IRC #ubuntu-x right now, and the consensus was
that by default, g-s-d should not turn external screens on or off, but
leave it the way the X server has set it up. If the user later
configures things on/off these settings will be applied next time.
The issues in this bug repo
First of all, apologies in advance for subscribing Steve Langasek w/o
permission but I have concerns regarding this NOT being included in the
release notes for the RC. Is it ever allowable to edit the release
notes?
You'll notice that I also marked both #643118 and #649534 as duplicates
of this bu
In bug 643118 the consequences are more serious, because g-s-d picks an
unsupported mode instead of the preferred one, and the display is messed
up. I understand the driver should not suggest broken modes, but what is
g-s-d trying to do anyway? Should it not just keep the preferred mode
that the X
Is there anyway I could determine what the default settings are once
I've hit the "wall" in the live CD?
I fiddled around in that "working" Maverick and rolled back all old
kernels:
Start-Date: 2010-09-28 15:55:18
Commandline: /usr/sbin/synaptic
Remove: linux-headers-2.6.35-14:i386 (2.6.35-14.20
happens to me ion the latest .run file from Nvidia
always resets to 60 on the refresh
in var.log.xorg.o.log note last line
37888.571] (II) NVIDIA(0): Setting mode "1600x1200_60"
[ 37945.013] (II) NVIDIA(0): Setting mode "1600x1200_85+0+0"
which one is which one, I see a 60 and I see an 85??
[ 3
Just thought I should add that I currently have no router so I can't ssh
the sick "box" but I should be able to access the sick OS using a chroot
from the same box if that's helpful.
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notificatio
Sorry to be slow but after trying the RC iso-testing i386 Live CD and
seeing the "out-of-range" error I decided to jump into upgrade testing.
I had been going to upgrade a highly modified Lucid, but due to this bug
I decided to spend the extra time to install and update a fresh 10.04.1,
and then pe
Nothing new in the log. I too think that g-s-d isn't the problem but
rather triggering the behavior.
Thing is, without a xorg.conf I only can chose between low/safe
resolutions. With Nvidia's BLOB it's enough to add horizontal and
vertical refresh rates, with Nouveau I also need to provide a model
you can run "sudo touch /var/lib/gdm/gsd-debug-randr" and restart gdm
and you will get a debug log /var/lib/gdm/gsd-debug-randr.log with
details on what g-s-d is doing
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you a
without that option turned on some configurations have no active screens
(ie docked laptop with lid closed for example), the configuration g-s-d
applies should be valid, it seems rather an xorg or xrandr bug
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You rece
** Tags added: iso-testing
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.co
I forgot, you also need to disable this option for the user ('sudo -u
gdm' will only deal with the gdm login screen):
gconftool-2 --type bool -s
"/apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup"
false
I guess the easiest way to find out if you are affected by this bug is,
I have tried several times with todays and 9-24's Live CD's removing
"quiet splash" which then drops me in a TTY, and then very carefully
typing "sudo -u gdm gconftool-2 --type bool -s
"/apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup"
false" followed by "sudo restart gdm" an
Oops, This:
"however I've tried the Live CD with many options including "nomodeset"
and "i915.modeset=1" which both result in the "out-of-range" error, and
also "i915.modeset=1" which drops me to a TTY, and if I try startx I
just get the error "Fatal server error: no screens found"."
Should say:
I'm also effected by this bug, but with quite different symptoms. I also know
this is quite long so I'll try to break things up very well.
First of all the hardware involved is Intel Corporation 82945G/GZ Integrated
Graphics Controller (rev 02) with a Hanns-G 22" LCD. That same hardware has
w
** Changed in: gnome-settings-daemon (Ubuntu)
Status: New => Confirmed
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
u
Ok, so this seems to have been triggered by the change in defaults in
version 2.31.91-0ubuntu3 (turn on ext. monitors).
Setting
'apps/gnome_settings_daemon/xrandr/turn_on_external_monitors_at_startup'
to false for the user gdm made this bug go away in the current version.
That key has been introdu
** Description changed:
Binary package hint: gnome-settings-daemon
- Starting with version 2.31.91-0ubuntu2, my CRT monitor starts with a
+ Starting with version 2.31.91-0ubuntu1, my CRT monitor starts with a
refresh rate of 60 Hz (overriding the 75 Hz set in xorg.conf). Using
nvidia-sett
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/640807/+attachment/1595316/+files/Dependencies.txt
--
Forces low refresh rate on CRT monitor
https://bugs.launchpad.net/bugs/640807
You received this bug notification because you are a member of Ubuntu
Bugs, which is sub
33 matches
Mail list logo
