8:43 p.m.
Hi,
There are a couple of scenarios with multiple displays etc, that don't
work that well in F8, in particular when the situation changes. Eg:
notebook (hp compaq nx6320):
- lcd panel: 1024x768
- vga out: {connected to sony crt 1400x1050), or some lcd.
- svideo/composite OP: different pins are used on the connector and a
converter cable can be ysed to pckup the composite video pins.
If I boot up, adjust the connectors {plug different bits in} then
login, for the most part that output will be activated. The following work:
- lcd panel only
- lcd and crt
- crt only
- lcd and svideo
- lcd and composite
, which is great. However, changing a display connection while logged in
doesn't adjust the outputs that are activated.
=====
Use case:
Flo started her laptop when she arrived at work in the morning, and by
lunch time she has 15 apps open {eg pdfs, spreadsheets, documents,
program editors, web pages, email, and the presentation she has been
working on}.
She needs to move the laptop in the meeting room, so that she can give
the presentation. While the battery keeps the unit going, and
networkmanager takes care of getting the unit re-connected to the
company network, she finds the image wont show on the boardroom
projector via the vga output.
She tries the Fn F4 {panel|panel+vga|vga} key combo. The panel screen
flickers black for a micro second, but the image is not sent out the vga
port. She tries the system-config-display, but isn't willing to restart
X to activate the changes as suggested by the applet (because she would
waste so much time to get her materials reopened).
Since she has been watching DVD's on her SVideo TV at home she plugs the
SVideo into the large screen TV, and again can't get an image to be
displayed. Composite is no go as well. At this moment the sweat drips
from her brow and the heart starts pounding as the first meeting guests
arrive...
=====
Or perhaps I am simply missing the fedora howto or correct application,
or key stroke to either cycle through different inputs, or auto activate
them as they are plugged in. {intel 945GM driver}
DaveT.
2:30 a.m.
On Sat, 2008-03-29 at 12:43 +1100, David Timms wrote:
<snipped statement of laptop + projector use case>
=====
Or perhaps I am simply missing the fedora howto or correct application,
or key stroke to either cycle through different inputs, or auto activate
them as they are plugged in. {intel 945GM driver}
You want:
http://fedoraproject.org/wiki/Features/RandrSupport
Keith.
7:04 a.m.
Keith Sharp wrote:
On Sat, 2008-03-29 at 12:43 +1100, David Timms wrote:
<snipped statement of laptop + projector use case>
> =====
>
> Or perhaps I am simply missing the fedora howto or correct application,
> or key stroke to either cycle through different inputs, or auto activate
> them as they are plugged in. {intel 945GM driver}
You want:
http://fedoraproject.org/wiki/Features/RandrSupport
So, much in F9 to be.
Perhaps it's time go a-beta'n on the work notebook
;-) I'll start with the live cd.
DaveT.
7:24 a.m.
On Sat, 2008-03-29 at 23:04 +1100, David Timms wrote:
Keith Sharp wrote:
> On Sat, 2008-03-29 at 12:43 +1100, David Timms wrote:
>
> <snipped statement of laptop + projector use case>
>
>> =====
>>
>> Or perhaps I am simply missing the fedora howto or correct application,
>> or key stroke to either cycle through different inputs, or auto activate
>> them as they are plugged in. {intel 945GM driver}
>
> You want:
>
> http://fedoraproject.org/wiki/Features/RandrSupport
So, much in F9 to be. Perhaps it's time go a-beta'n on the work notebook
;-) I'll start with the live cd.
You can use it in F-8 too, only no graphical utility exists. Use
xrandr --auto
to activate the external monitor, that's the basic functionality. You'll
find more examples on the man page, and on the net.
DaveT.
ciao
andrea
--
Andrea Dell'Amico - <http://www.link.it/>
8:05 a.m.
Andrea Dell'Amico wrote:
You can use it in F-8 too, only no graphical utility exists. Use
xrandr --auto
to activate the external monitor, that's the basic functionality. You'll
find more examples on the man page, and on the net.
OK, on F8, xrandr --verbose
--auto does it to turn clone of the vga OP
connector on off depending on whether it is plugged in.
How would I tie that command to Fn-F4 ?
DaveT.
8:23 a.m.
On Sun, 2008-03-30 at 00:05 +1100, David Timms wrote:
OK, on F8, xrandr --verbose --auto does it to turn clone of the vga
OP
connector on off depending on whether it is plugged in.
How would I tie that command to Fn-F4 ?
I don't think you can. With F8 you're stuck with the shell. You don't
need to be root.
DaveT.
ciao
andrea
--
Andrea Dell'Amico - <http://www.link.it/>
9:32 a.m.
On Sun, 2008-03-30 at 00:05 +1100, David Timms wrote:
Andrea Dell'Amico wrote:
> You can use it in F-8 too, only no graphical utility exists. Use
>
> xrandr --auto
>
> to activate the external monitor, that's the basic functionality. You'll
> find more examples on the man page, and on the net.
OK, on F8, xrandr --verbose --auto does it to turn clone of the vga OP
connector on off depending on whether it is plugged in.
How would I tie that command to Fn-F4 ?
By hand:
http://live.gnome.org/ControlCenter/CustomKeybindings
Cheers
7:57 a.m.
New subject: notebook / multiple visual displays - Fn-Video_cycle button
Bastien Nocera wrote:
On Sun, 2008-03-30 at 00:05 +1100, David Timms wrote:
> OK, on F8, xrandr --verbose --auto does [x it to x] turn clone of the vga OP
> connector on off depending on whether it is plugged in.
>
> How would I tie that command to Fn-F4 ?
By hand:
http://live.gnome.org/ControlCenter/CustomKeybindings
Is it a possibility that this
can just work for every notebook ?
Is it a reasonable goal ?
Pressing the monitor cycle key combo didn't seem to cause any
/var/log/messages indications when I tried other keys on this notebook
{Keymap Quirk Debugger}
3:51 p.m.
New subject: notebook / multiple visual displays - Fn-Video_cycle button
On Sun, 2008-03-30 at 23:57 +1100, David Timms wrote:
Bastien Nocera wrote:
> On Sun, 2008-03-30 at 00:05 +1100, David Timms wrote:
>> OK, on F8, xrandr --verbose --auto does [x it to x] turn clone of the vga OP
>> connector on off depending on whether it is plugged in.
>>
>> How would I tie that command to Fn-F4 ?
>
> By hand:
> http://live.gnome.org/ControlCenter/CustomKeybindings
Is it a possibility that this can just work for every notebook ?
Is it a reasonable goal ?
Pressing the monitor cycle key combo didn't seem to cause any
/var/log/messages indications when I tried other keys on this notebook
{Keymap Quirk Debugger}
It's already in F9 done correctly. You asked "how do I do it on F8", and
I answered.
7:47 a.m.
New subject: notebook / multiple visual displays - Fn-Video_cycle button
Bastien Nocera wrote:
On Sun, 2008-03-30 at 23:57 +1100, David Timms wrote:
> Bastien Nocera wrote:
>> On Sun, 2008-03-30 at 00:05 +1100, David Timms wrote:
>>> OK, on F8, xrandr --verbose --auto does [x it to x] turn clone of the vga OP
>>> connector on off depending on whether it is plugged in.
>>>
>>> How would I tie that command to Fn-F4 ?
>> By hand:
>> http://live.gnome.org/ControlCenter/CustomKeybindings
> Is it a possibility that this can just work for every notebook ?
> Is it a reasonable goal ?
>
> Pressing the monitor cycle key combo didn't seem to cause any
> /var/log/messages indications when I tried other keys on this notebook
> {Keymap Quirk Debugger}
It's already in F9 done correctly.
Thanks Bastien,
OK, it's a bug {rather than an RFE} on F9-2008-03-27 live x86_64 then
since the key combo doesn't work on at least my specific hardware. I'll
search/file bug tomorrow.
Any hints on what component ? xorg-x11-?
How about activation of of the Svideo/composite output {that isn't
working from the gui tools} - should it be working - and hence need to
bug it ?
DaveT.
4:39 a.m.
>>>> "DT" == David Timms writes:
[...]
DT> She tries the Fn F4 {panel|panel+vga|vga} key combo. The panel
DT> screen flickers black for a micro second, but the image is not
DT> sent out the vga port. She tries the system-config-display, but
DT> isn't willing to restart X to activate the changes as suggested by
DT> the applet (because she would waste so much time to get her
DT> materials reopened).
DT> Since she has been watching DVD's on her SVideo TV at home she
DT> plugs the SVideo into the large screen TV, and again can't get an
DT> image to be displayed. Composite is no go as well. At this moment
DT> the sweat drips from her brow and the heart starts pounding as the
DT> first meeting guests arrive...
Heh, I actually went through an almost identical scenario you just
painted today. I've found that with F-8, the only way to make sure
that the output VGA is sent with the correct resolution, is to reboot
the computer with the projector/external monitor plugged. In
addition, this also presupposes that I've manually tweaked my
xorg.conf to specifically ask for this setup beforehead. My laptop is
1280x800 but most video projectors only accept 1024x768 VGA input.
It used to work OK in F-7, that is I could boot without it plugged in,
the have the output appear with the correct resolution when I plugged
it into the projector some time later.
DT> Or perhaps I am simply missing the fedora howto or correct
DT> application, or key stroke to either cycle through different
DT> inputs, or auto activate them as they are plugged in. {intel 945GM
DT> driver}
This is with an Intel 915GM.
Alex
4 p.m.
On Sat, 2008-03-29 at 02:39 -0700, Alex Lancaster wrote:
>>>>> "DT" == David Timms writes:
[...]
DT> She tries the Fn F4 {panel|panel+vga|vga} key combo. The panel
DT> screen flickers black for a micro second, but the image is not
DT> sent out the vga port. She tries the system-config-display, but
DT> isn't willing to restart X to activate the changes as suggested by
DT> the applet (because she would waste so much time to get her
DT> materials reopened).
DT> Since she has been watching DVD's on her SVideo TV at home she
DT> plugs the SVideo into the large screen TV, and again can't get an
DT> image to be displayed. Composite is no go as well. At this moment
DT> the sweat drips from her brow and the heart starts pounding as the
DT> first meeting guests arrive...
Heh, I actually went through an almost identical scenario you just
painted today. I've found that with F-8, the only way to make sure
that the output VGA is sent with the correct resolution, is to reboot
the computer with the projector/external monitor plugged. In
addition, this also presupposes that I've manually tweaked my
xorg.conf to specifically ask for this setup beforehead. My laptop is
1280x800 but most video projectors only accept 1024x768 VGA input.
I've done this too. With my laptop and my wifes. It's nice to think it
might be getting fixed.
My laptop has a 1900x1200 display, so I'm also hoping that using an
external monitor might be handled a little gracefully too (resolutions
set to something meaningful)
I've often wondered is the new composite rendering stuff couldn't be
used to send the display to external projectors and screens in a
meaningful way.
R.
--
"It's a fine line between denial and faith.
It's much better on my side"
11:26 a.m.
On Saturday, March 29, 2008 2:39 am Alex Lancaster wrote:
Heh, I actually went through an almost identical scenario you just
painted today. I've found that with F-8, the only way to make sure
that the output VGA is sent with the correct resolution, is to reboot
the computer with the projector/external monitor plugged. In
addition, this also presupposes that I've manually tweaked my
xorg.conf to specifically ask for this setup beforehead. My laptop is
1280x800 but most video projectors only accept 1024x768 VGA input.
That's weird, when you run 'xrandr' it should re-probe the outputs and get a
list of valid resolutions from whatever is attached to VGA. What happens for
you in that case?
Jesse
11:35 a.m.
On Mon, Mar 31, 2008 at 9:26 AM, Jesse Barnes <jbarnes(a)virtuousgeek.org> wrote:
On Saturday, March 29, 2008 2:39 am Alex Lancaster wrote:
> Heh, I actually went through an almost identical scenario you just
> painted today. I've found that with F-8, the only way to make sure
> that the output VGA is sent with the correct resolution, is to reboot
> the computer with the projector/external monitor plugged. In
> addition, this also presupposes that I've manually tweaked my
> xorg.conf to specifically ask for this setup beforehead. My laptop is
> 1280x800 but most video projectors only accept 1024x768 VGA input.
That's weird, when you run 'xrandr' it should re-probe the outputs and get
a
list of valid resolutions from whatever is attached to VGA. What happens for
you in that case?
Jesse
xrandr probing sometimes appears to "not work right", at least for me.
I have a Thinkpad X60 with intel 945 graphics, 1024x768 LCD. When
booting with just the builtin monitor, all works fine.
When booting with 2 different 19" monitors and with the laptop screen
"shut", X/gdm boots up in a funny hybrid mode, where the interface is
actually in 1280x1024 (max supported by interface and monitors), but X
thinks its in 1920x1080 or 1920x1024. I have to manually enter
"xrandr --size 1280x1024" each login to get system configured right.
Here is output of xrandr with non-functioning modes, but after running
"xrandr --size 1280x1024".
[tbl@localhost ~]$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1920 x 1920
VGA connected 1280x1024+0+0 (normal left inverted right x axis y axis)
376mm x 301mm
1280x1024 60.0 + 75.0* 60.0 60.0
1920x1080 59.9
1680x1050 59.9
1600x1024 60.2
1400x1050 60.0
1440x900 59.9
1280x960 60.0
1360x768 59.8 60.0
1280x800 75.0 70.0 60.0
1152x864 75.0 75.0 70.0 60.0
1280x768 75.0 70.0 60.0
1280x720 75.0 70.0 60.0
1152x768 54.8
1024x768 75.1 75.0 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 75.0 72.8 72.8 75.0 60.0 59.9
720x400 70.1
LVDS connected (normal left inverted right x axis y axis)
1024x768 50.0 + 60.0 40.0
800x600 60.3
640x480 60.0 59.9
[tbl@localhost ~]$
tom
--
Tom London
12:35 p.m.
On Monday, March 31, 2008 9:35 am Tom London wrote:
xrandr probing sometimes appears to "not work right", at
least for me.
I have a Thinkpad X60 with intel 945 graphics, 1024x768 LCD. When
booting with just the builtin monitor, all works fine.
When booting with 2 different 19" monitors and with the laptop screen
"shut", X/gdm boots up in a funny hybrid mode, where the interface is
actually in 1280x1024 (max supported by interface and monitors), but X
thinks its in 1920x1080 or 1920x1024. I have to manually enter
"xrandr --size 1280x1024" each login to get system configured right.
I think that's X failing to setup a reasonable default. ajax fixed that
recently though, iirc.
Here is output of xrandr with non-functioning modes, but after
running
"xrandr --size 1280x1024".
[tbl@localhost ~]$ xrandr
Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1920 x 1920
VGA connected 1280x1024+0+0 (normal left inverted right x axis y axis)
376mm x 301mm
1280x1024 60.0 + 75.0* 60.0 60.0
1920x1080 59.9
1680x1050 59.9
1600x1024 60.2
1400x1050 60.0
1440x900 59.9
1280x960 60.0
1360x768 59.8 60.0
1280x800 75.0 70.0 60.0
1152x864 75.0 75.0 70.0 60.0
1280x768 75.0 70.0 60.0
1280x720 75.0 70.0 60.0
1152x768 54.8
1024x768 75.1 75.0 70.1 60.0
832x624 74.6
800x600 72.2 75.0 60.3 56.2
640x480 75.0 72.8 72.8 75.0 60.0 59.9
720x400 70.1
LVDS connected (normal left inverted right x axis y axis)
1024x768 50.0 + 60.0 40.0
800x600 60.3
640x480 60.0 59.9
[tbl@localhost ~]$
This looks like it's detecting your monitor's modes properly though, are you
just having problems with your startup configuration if the monitor is
attached?
Jesse
12:48 p.m.
On Mon, Mar 31, 2008 at 10:35 AM, Jesse Barnes <jbarnes(a)virtuousgeek.org> wrote:
On Monday, March 31, 2008 9:35 am Tom London wrote:
> xrandr probing sometimes appears to "not work right", at least for me.
>
> I have a Thinkpad X60 with intel 945 graphics, 1024x768 LCD. When
> booting with just the builtin monitor, all works fine.
>
> When booting with 2 different 19" monitors and with the laptop screen
> "shut", X/gdm boots up in a funny hybrid mode, where the interface is
> actually in 1280x1024 (max supported by interface and monitors), but X
> thinks its in 1920x1080 or 1920x1024. I have to manually enter
> "xrandr --size 1280x1024" each login to get system configured right.
I think that's X failing to setup a reasonable default. ajax fixed that
recently though, iirc.
> Here is output of xrandr with non-functioning modes, but after running
> "xrandr --size 1280x1024".
>
> [tbl@localhost ~]$ xrandr
> Screen 0: minimum 320 x 200, current 1280 x 1024, maximum 1920 x 1920
> VGA connected 1280x1024+0+0 (normal left inverted right x axis y axis)
> 376mm x 301mm
> 1280x1024 60.0 + 75.0* 60.0 60.0
> 1920x1080 59.9
> 1680x1050 59.9
> 1600x1024 60.2
> 1400x1050 60.0
> 1440x900 59.9
> 1280x960 60.0
> 1360x768 59.8 60.0
> 1280x800 75.0 70.0 60.0
> 1152x864 75.0 75.0 70.0 60.0
> 1280x768 75.0 70.0 60.0
> 1280x720 75.0 70.0 60.0
> 1152x768 54.8
> 1024x768 75.1 75.0 70.1 60.0
> 832x624 74.6
> 800x600 72.2 75.0 60.3 56.2
> 640x480 75.0 72.8 72.8 75.0 60.0 59.9
> 720x400 70.1
> LVDS connected (normal left inverted right x axis y axis)
> 1024x768 50.0 + 60.0 40.0
> 800x600 60.3
> 640x480 60.0 59.9
> [tbl@localhost ~]$
This looks like it's detecting your monitor's modes properly though, are you
just having problems with your startup configuration if the monitor is
attached?
Jesse
Uhh.... not sure I understand what you mean.
I have tested only 2 "use cases":
1. boot laptop with no external monitor (just builtin LCD). This works fine.
2. boot laptop with internal monitor "shut" and system connected to
external monitors. This goes through what seems to me to be a "funny"
boot sequence:
a. gdmgreeter comes up in 1024x768
b. after presenting password, display "re-sizes" to 1280x1024 (per
display "info" buttons"), but the screen shows a "tiled" version
of
the "blue curve" background (I get one complete copy in the upper left
corner, partial tiles in the other 3 "slots").
c. after a few more seconds, the tiling vanishes, but I briefly
get a "deformed" background (for about 5 seconds).
d. background becomes normal, any my startup windows appear;
e. "xdpyinfo" says the dimension is 1920x1024, as does "xrandr".
Some displays are all messed up (e.g., firefox)
f. running "xrandr --size 1280x1024" repairs. gnome-terminal
windows actually don't change, but the messed up ones now are fixed.
Use case 2 behaves exactly the same if I boot directly to X (via
startx) instead of gdm.
I've logged this all here: https://bugzilla.redhat.com/show_bug.cgi?id=437654
Not sure why I'm the only lucky one ;) Any hints/fixes gladly welcome.
tom
--
Tom London
1:05 p.m.
On Monday, March 31, 2008 10:48 am Tom London wrote:
Uhh.... not sure I understand what you mean.
I have tested only 2 "use cases":
1. boot laptop with no external monitor (just builtin LCD). This works
fine.
2. boot laptop with internal monitor "shut" and system connected to
external monitors. This goes through what seems to me to be a "funny"
boot sequence:
a. gdmgreeter comes up in 1024x768
b. after presenting password, display "re-sizes" to 1280x1024 (per
display "info" buttons"), but the screen shows a "tiled" version
of
the "blue curve" background (I get one complete copy in the upper left
corner, partial tiles in the other 3 "slots").
c. after a few more seconds, the tiling vanishes, but I briefly
get a "deformed" background (for about 5 seconds).
d. background becomes normal, any my startup windows appear;
e. "xdpyinfo" says the dimension is 1920x1024, as does "xrandr".
Some displays are all messed up (e.g., firefox)
f. running "xrandr --size 1280x1024" repairs. gnome-terminal
windows actually don't change, but the messed up ones now are fixed.
Use case 2 behaves exactly the same if I boot directly to X (via
startx) instead of gdm.
I've logged this all here:
https://bugzilla.redhat.com/show_bug.cgi?id=437654
Not sure why I'm the only lucky one ;) Any hints/fixes gladly welcome.
Ok, I was just trying to figure out if you also had problems hotplugging
displays (i.e. booting with nothing attached, then trying to plug in & enable
an external display); sounds like you're only complaining about the "boot up
with VGA connected" case here though.
I think there are at least a couple of problems:
1) we don't do lid switch detection very well in the Intel driver
this will cause X to enable both screens at boot time, picking a bad
default
2) the X "pick a default configuration" mode isn't very good
for one thing, it tries to clone the displays instead of setting up
an extended desktop, but beyond that the cloned configuration often
isn't what you want. I think this is what ajax fixed (and he's working
on (1) also, unfortunately that's a hard problem).
Jesse
1:53 p.m.
On Mon, Mar 31, 2008 at 11:05 AM, Jesse Barnes <jbarnes(a)virtuousgeek.org> wrote:
On Monday, March 31, 2008 10:48 am Tom London wrote:
> Uhh.... not sure I understand what you mean.
>
> I have tested only 2 "use cases":
> 1. boot laptop with no external monitor (just builtin LCD). This works
> fine.
>
> 2. boot laptop with internal monitor "shut" and system connected to
> external monitors. This goes through what seems to me to be a "funny"
> boot sequence:
> a. gdmgreeter comes up in 1024x768
> b. after presenting password, display "re-sizes" to 1280x1024 (per
> display "info" buttons"), but the screen shows a "tiled"
version of
> the "blue curve" background (I get one complete copy in the upper left
> corner, partial tiles in the other 3 "slots").
> c. after a few more seconds, the tiling vanishes, but I briefly
> get a "deformed" background (for about 5 seconds).
> d. background becomes normal, any my startup windows appear;
> e. "xdpyinfo" says the dimension is 1920x1024, as does
"xrandr".
> Some displays are all messed up (e.g., firefox)
> f. running "xrandr --size 1280x1024" repairs. gnome-terminal
> windows actually don't change, but the messed up ones now are fixed.
>
> Use case 2 behaves exactly the same if I boot directly to X (via
> startx) instead of gdm.
>
> I've logged this all here:
> https://bugzilla.redhat.com/show_bug.cgi?id=437654
>
> Not sure why I'm the only lucky one ;) Any hints/fixes gladly welcome.
Ok, I was just trying to figure out if you also had problems hotplugging
displays (i.e. booting with nothing attached, then trying to plug in & enable
an external display); sounds like you're only complaining about the "boot up
with VGA connected" case here though.
I think there are at least a couple of problems:
1) we don't do lid switch detection very well in the Intel driver
this will cause X to enable both screens at boot time, picking a bad
default
2) the X "pick a default configuration" mode isn't very good
for one thing, it tries to clone the displays instead of setting up
an extended desktop, but beyond that the cloned configuration often
isn't what you want. I think this is what ajax fixed (and he's working
on (1) also, unfortunately that's a hard problem).
Jesse
Thanks for the info.
No, haven't tested hotplugging.
What confuses me about 2) above is that X/xrandr seems to be
displaying and selecting modes that are just not supported by my
hardware. For example, 1600x1024 is listed by xrandr, and it appears
to willing try to set that mode ("xrandr --size 1600x1024"). But doing
so does not cause happiness (the monitor's "display info" button still
insists its in 1280x1024, and the screen is "all messed up").
[This monitor's specs (HP L1906) list 1280x1024@60 as the max
supported resolution:
http://h10010.www1.hp.com/wwpc/us/en/sm/WF06a/382087-382087-64283-72270-4...
]
I'll continue to test Rawhide version of X and report when this changes.
tom
--
Tom London
2:55 a.m.
2008/3/29, David Timms <dtimms(a)iinet.net.au>:
Hi,
There are a couple of scenarios with multiple displays etc, that don't
work that well in F8, in particular when the situation changes. Eg:
notebook (hp compaq nx6320):
- lcd panel: 1024x768
- vga out: {connected to sony crt 1400x1050), or some lcd.
- svideo/composite OP: different pins are used on the connector and a
converter cable can be ysed to pckup the composite video pins.
[...]
Although I know that many of these issues are resolved in F9, and that
there are ways to handle it from the command line in F8, there are a
couple of issues that I would like to mention:
1. On samsung monitors (I've tried three different) the correct
display settings are not detected when connected to the VGA output.
Where should this bug be filed?
2. The resolution of my lcd is only 1024x768, but the connected
monitors are all larger than this. But the intel card (915) apparently
does not want to set a higher resolution than this. Any ideas?
If someone could point the to the correct destination for a bug report
I will provide more information.
Regards,
--
Trond Danielsen
5868
days inactive
5870
days old
18 comments
9 participants
participants (9)
-
Alex Lancaster -
Andrea Dell'Amico -
Bastien Nocera -
Development discussions related to Fedora -
Jesse Barnes -
Keith Sharp -
Rodd Clarkson -
Tom London -
Trond Danielsen