On Fri, 2013-06-21 at 03:43 -0400, Felix Miata wrote:
> On 2013-06-21 03:07 (GMT-0400) Adam Williamson composed:
>
> > KDE has a checkbox for *everything in the world*, so I'm sure you can
> > reverse/reconfigure it somewhere. I haven't used it, but I'm assuming it
> > can set resolution and refre
On Fri, 2013-06-21 at 04:19 -0700, T.C. Hollingsworth wrote:
> On Thu, Jun 20, 2013 at 10:15 PM, Felix Miata wrote:
> > That was it. 'yum remove kscreen' wanted to remove kde-workspace. 'rpm -e
> > --nodeps kscreen' mostly fixed it. There's a strong flicker I can't recall
> > ever seeing before fr
On Fri, Jun 21, 2013 at 12:07 AM, Adam Williamson wrote:
> KDE has a checkbox for *everything in the world*,
KScreen actually "fixes" this. The old display config pretty much
exposed every xrandr option under the sun, and just as tersely. (In
fact, I think it just shelled out to xrandr and only
On Thu, Jun 20, 2013 at 10:15 PM, Felix Miata wrote:
> That was it. 'yum remove kscreen' wanted to remove kde-workspace. 'rpm -e
> --nodeps kscreen' mostly fixed it. There's a strong flicker I can't recall
> ever seeing before from the Radeon's DVI output (also in SUSE) as if running
> below 60 re
On 2013-06-21 03:07 (GMT-0400) Adam Williamson composed:
KDE has a checkbox for *everything in the world*, so I'm sure you can
reverse/reconfigure it somewhere. I haven't used it, but I'm assuming it
can set resolution and refresh rate as well as multi-monitor
positioning, hence useful for singl
On Fri, 2013-06-21 at 01:15 -0400, Felix Miata wrote:
> On 2013-06-20 21:03 (GMT-0700) T.C. Hollingsworth composed:
>
> Thank you!!! :-D
>
> > What desktop are you using, then?
>
> On 2013-06-20 22:56 (GMT-0400) Felix Miata composed:
> ...
> > .fonts
> > .gstreamer-0.10
> > .gtkrc-2.0-kde4
> > .
On 2013-06-20 21:03 (GMT-0700) T.C. Hollingsworth composed:
Thank you!!! :-D
What desktop are you using, then?
On 2013-06-20 22:56 (GMT-0400) Felix Miata composed:
...
.fonts
.gstreamer-0.10
.gtkrc-2.0-kde4
.kde
.kderc
.local
...
KDE moved to kscreen for F19 and that might cause similar is
On Thu, 2013-06-20 at 23:18 -0400, Felix Miata wrote:
> On 2013-06-20 19:58 (GMT-0700) Adam Williamson composed:
>
> >> Is there some material difference there between F18 and F19?
>
> > No, but it's barely possible you somehow set one of those in F19 that
> > you didn't in F18.
>
> >> Would any
On 2013-06-20 19:58 (GMT-0700) Adam Williamson composed:
Is there some material difference there between F18 and F19?
No, but it's barely possible you somehow set one of those in F19 that
you didn't in F18.
Would any of that be in any of these?
No, you'd want to look in dconf-editor at
On Thu, 2013-06-20 at 22:56 -0400, Felix Miata wrote:
> On 2013-06-20 19:33 (GMT-0700) Adam Williamson composed:
>
> > On Thu, 2013-06-20 at 22:31 -0400, Felix Miata wrote:
>
> >> I have F19 on two systems I've been working with for the past two days
> >> trying
> >> to isolate a Nouveau DVI pro
On 2013-06-20 19:33 (GMT-0700) Adam Williamson composed:
On Thu, 2013-06-20 at 22:31 -0400, Felix Miata wrote:
I have F19 on two systems I've been working with for the past two days trying
to isolate a Nouveau DVI problem, and in the process ran across this:
Only on the F19 system most rec
On Thu, 2013-06-20 at 22:31 -0400, Felix Miata wrote:
> I have F19 on two systems I've been working with for the past two days trying
> to isolate a Nouveau DVI problem, and in the process ran across this:
>
> Only on the F19 system most recently updated (Tuesday, server 1.14.1),
> PreferredMode
12 matches
Mail list logo
