*** This bug is a duplicate of bug 240916 ***
https://bugs.launchpad.net/bugs/240916
** This bug has been marked a duplicate of bug 240916
can't configure display resolution (monitor, graphics card) manually in gui
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.l
Glad I could help 3vil. It's a shame that there's no mechanism for
ordinary people to achieve the same thing, for whom manually editing
xorg.conf is a step too far.
After all it only takes three gui fields and a go button! All the other
tools are already in place - gtf, gnome resolution config, et
@Cefn:
Thank you very much for posting the gtf command and xorg changes! I ran
into this issue today while attaching a machine to a KVM and could not
get it to work until I saw your workaround.
It's pretty frustrating when the GUI gives you no options other than
320x240 and 640x480 because DPMS
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Wishlist
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubun
Sebastien,
I disagree that this is an xorg issue, since xorg can handle the
scenario fine.
When autodetection works, it reports the valid modes which are detected.
When autodetection doesn't work, it's got no choice but to await a
manual specification of a valid mode since it has no way of knowi
Hi reduzio,
Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log
(and maybe Xorg.0.log.old) file from after reproducing this issue. If you've
made any customizations to your /etc/X11/xorg.conf please attach that as well.
[This is an automated message. Apologies if i
if the xrandr command line doesn't list those modes too the issue is
rather an xorg one, the xrand interface should list some choices which
make sense in such cases, that's not specific to the GNOME GUI
** Changed in: xorg-server (Ubuntu)
Sourcepackagename: gnome-control-center => xorg-server
The graphical tools DO list the same options as the xrandr command. That
means that if the autodetection has failed to identify a valid mode by
autodetection, you are screwed unless you like to edit xorg.conf. Then
these options show up in xrandr and in the graphical tool.
To fix the problem I had
the bug has been closed because it lacks informations to be worked
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
> It's for this reason I'd like to keep the bug open and provide any maintainer
> with more information about the request.
Agreed. It's not because I can't reproduce it any more that the bug is
invalid.
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/2
could you run xrandr or a command line and copy the log to the bug? what
xorg change did you do? the graphical tools should list the same option
than the xrandr command
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received this bug notific
I'm referring to your request a few hours ago...
"can you force the resolution using the xrandr command line tool?"
Yes you can force it using xrandr, assuming that you have edited
xorg.conf properly. I've carried out these steps and proven that you can
force the correct resolution regardless of a
what do you call "xrandr invocations needed"
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@list
Could you reopen this bug. I can reproduce it and still have a KVM which
prevents the autodetection capability from working.
My suggestion that this should remain open is based on Bryce's
interpretation of the bug/feature request earlier in this thread...
https://bugs.launchpad.net/ubuntu/+source
closing the bug since it lacks details to be worked
** Changed in: gnome-control-center (Ubuntu)
Status: Confirmed => Invalid
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received this bug notification because you are a member of U
I can't reproduce it again since I don't have the splitter any more.
Sorry.
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bug
can you force the resolution using the xrandr command line tool?
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing l
Possibly this is a dupe of 240916
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
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.co
As you say, with a splitter and multiple monitors attached, this is
beyond X's autodetection capabilities. It sounds like your request is
to have a functionality in the GUI tool for manually specifying settings
in this case, so I'm reassigning to the GUI tool.
** Changed in: gnome-control-center
@db0 your issue sounds unrelated to this bug report.
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-b
I have a very similar problem but with an HDTV in my case which is not
always on when the system boots. I've opened a question in the forum
about this here as well:
http://ubuntuforums.org/showthread.php?p=6657378#post6657378
I don't even mind hacking the xorg.conf but even that does not seem to
h
I'm very much in agreement. The graphical tools in Ubuntu are very
important to make system configuration changes available to ordinary
users.
I'm here looking at a 1440x900 screen which I know for sure is capable
of that resolution, but because the auto-detect doesn't work, (through a
KVM), I'm u
** Changed in: xorg (Ubuntu)
Importance: Undecided => Wishlist
Status: Incomplete => Confirmed
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscrib
I've copied the old xorg.conf with my ModeLine to 1600x1200 and now I
can select it from the list. But I think this is going in the opposite
direction than the Xorg is going, isn't it?
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received
I have the same issue and the list on Gnome's screen resolution
configuration doesn't have my option (1600x1200). Directly connected to
the monitor is fine, but on the KVM it doesn't detect nor allow me to
change.
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.
[This is an automated message]
Hi reduzio,
Thank you for taking the time to report this bug and helping to make Ubuntu
better. You reported this bug a while ago and there hasn't been any activity in
it recently. We were wondering is this still an issue for you? Can you try with
the latest dev
** Changed in: xorg (Ubuntu)
Sourcepackagename: None => xorg
--
Unable to force screen resolution with vtswitch/splitter
https://bugs.launchpad.net/bugs/260436
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
27 matches
Mail list logo
