Hello,
my desktop was completely broken this morning because my startup scripts
rely on xrandr utility. An older update from this summer which I applied
recently changed it's output so device ids now contain dash characters
(e.g. instead VGA0 I see VGA-1).
I just wonder why this landed into
On Tue, 2014-11-25 at 09:14 +0100, Lukas Zapletal wrote:
Hello,
my desktop was completely broken this morning because my startup scripts
rely on xrandr utility. An older update from this summer which I applied
recently changed it's output so device ids now contain dash characters
(e.g.
Lukas Zapletal composed on 2014-11-25 09:14 (UTC+0100):
my desktop was completely broken this morning because my startup scripts
rely on xrandr utility. An older update from this summer which I applied
recently changed it's output so device ids now contain dash characters
(e.g. instead VGA0 I
Using what gfxchip? VGA0 I don't remember ever seeing. Most I remember seeing:
Yeah, that was a typo. It's actually DP-1 and LVDS-0 (Thinkpad T403s
with Intel). Anyway, this changed from DP1 and LVDS0.
--
Later,
Lukas #lzap Zapletal
--
devel mailing list
devel@lists.fedoraproject.org
On Tue, Nov 25, 2014 at 9:14 AM, Lukas Zapletal l...@redhat.com wrote:
Hello,
my desktop was completely broken this morning because my startup scripts
rely on xrandr utility. An older update from this summer which I applied
recently changed it's output so device ids now contain dash
On 25/11/14 09:26, drago01 wrote:
Which desktop are you using? You shouldn't have to mess with startup
scripts that call xrandr to get a monitor setup working.
Here's one example: Intel drv, monitor with broken EDID, Gnome 3.12.
This is limited to either 800x60 or 1024x768 (forget which).
On Tue, Nov 25, 2014 at 10:26:43AM +0100, drago01 wrote:
On Tue, Nov 25, 2014 at 9:14 AM, Lukas Zapletal l...@redhat.com wrote:
Hello,
my desktop was completely broken this morning because my startup scripts
rely on xrandr utility. An older update from this summer which I applied
Anyhow, I hit the same thing this morning, with LVDS1 changing
to LVDS-0, HDMI3 to HDMI-2 and VGA1 to VGA-0. This was on an
Intel adapter.
Exactly. I use i3wm and I use xrandr to determine if I have my laptop
docked with IPS panel, docked with VGA monitor or standalone. Then I
setup all my
On 25 November 2014 at 13:20, Lukas Zapletal l...@redhat.com wrote:
I don't understand why I noticed this today, it looks like the latest
update was a Critical Path one (???) when Fedora 20 was stable for six
months.
There's an intel driver from 18th november, for example:
https://admin.fedoraproject.org/updates/FEDORA-2014-15384/xorg-x11-drv-intel-2.21.15-9.fc20
This seems to be much more related to your issues. I don't had any output
renaming recently in the past year (Nouveau here).
That answers
- Original Message -
There's an intel driver from 18th november, for example:
https://admin.fedoraproject.org/updates/FEDORA-2014-15384/xorg-x11-drv-intel-2.21.15-9.fc20
This seems to be much more related to your issues. I don't had any output
renaming recently in the past
Am 25.11.2014 um 14:31 schrieb Lukas Zapletal:
There's an intel driver from 18th november, for example:
https://admin.fedoraproject.org/updates/FEDORA-2014-15384/xorg-x11-drv-intel-2.21.15-9.fc20
This seems to be much more related to your issues. I don't had any output
renaming recently in
On Tue, 2014-11-25 at 09:14 +0100, Lukas Zapletal wrote:
my desktop was completely broken this morning because my startup scripts
rely on xrandr utility. An older update from this summer which I applied
recently changed it's output so device ids now contain dash characters
(e.g. instead VGA0
On 25/11/14 15:32, Adam Jackson wrote:
But when I say come from the server I really mean the 2D X driver
makes up the name and the server just reports it. And indeed, between
xorg-x11-drv-intel-2.21.15-4 and -9 output naming was changed to include
a dash (if using UXA), which happened because
On Tue, 2014-11-25 at 15:57 +, Tom Hughes wrote:
I thought multi-gpu randr was supported in 1.4? I certainly see one
provider for each of the two gpus in this machine, and can see five
connectors across the two with three monitors connected. It looks like
it just adds an extra digit to
On 25/11/14 16:55, Adam Jackson wrote:
On Tue, 2014-11-25 at 15:57 +, Tom Hughes wrote:
I thought multi-gpu randr was supported in 1.4? I certainly see one
provider for each of the two gpus in this machine, and can see five
connectors across the two with three monitors connected. It looks
On Tue, Nov 25, 2014 at 6:15 PM, Tom Hughes t...@compton.nu wrote:
On 25/11/14 16:55, Adam Jackson wrote:
On Tue, 2014-11-25 at 15:57 +, Tom Hughes wrote:
I thought multi-gpu randr was supported in 1.4? I certainly see one
provider for each of the two gpus in this machine, and can see
On Tue, 2014-11-25 at 14:04 +0100, Simone Caronni wrote:
On 25 November 2014 at 13:20, Lukas Zapletal l...@redhat.com wrote:
I don't understand why I noticed this today, it looks like the
latest
update was a Critical Path one (???) when Fedora 20 was stable
for
On Tue, Nov 25, 2014 at 10:32:27AM -0500, Adam Jackson wrote:
want two outputs both named VGA-0. And caring about the names is
somewhat futile anyway since what you're usually more concerned with is
the _monitor_, which is why all sane desktops save configurations based
on EDIDs not on
19 matches
Mail list logo
