So I've completed copied over my home directory from my updated and fully
working desktop to my new desktop including .gtkrc-2.0, but it didn't fully
resolve the problem.

Yeah, it fixed GTK windows being different (such as chrome), but menu bars
and title bars in KDE still switch to KDE classic cursors.

On Sat, Sep 2, 2017, 12:52 PM Theofilos Intzoglou <int....@gmail.com> wrote:

> I believe gtk-cursor-theme-name="breeze_cursors" is missing from the
> .gtkrc-2.0
>
> Στις Σάβ, 2 Σεπ 2017 στις 1:38 π.μ., ο/η Jerrod Frost <
> piroisl...@gmail.com> έγραψε:
>
>> Does anyone else use KDE? I'm trying to locate the source of an issue
>> with the latest KDE dailies using 2 different cursor themes. hovering over
>> titles bars and menus or gtk stuff changes cursor to KDE_classic, but
>> everywhere else seems to be basic breeze themed cursors? Can anyone explain
>> this? I've been hunting for hours and its not within the home directory
>> either as scrapping home and starting over results in same scenario.
>>
>> On Fri, Sep 1, 2017 at 5:06 PM Mitch Harder <
>> mitch.har...@sabayonlinux.org> wrote:
>>
>>> On Wed, Aug 30, 2017 at 2:39 PM, Jerrod Frost <piroisl...@gmail.com>
>>> wrote:
>>> > I just tested a USB3 128G mushkin flashdrive. DD works like a boss. We
>>> do
>>> > have some odd issue though. I get lag and a black screen for a while
>>> upon
>>> > boot. When testing Manjaro, it was instant. Even systemd loaded
>>> quicker..
>>> >
>>> > Anywho, USB drive issue has been solved.  I've also robbed the scripts
>>> for
>>> > calamares out of Manjaro. Calamares worked like a boss! Installed on
>>> NVMe
>>> > drive and worked excellently.
>>> >
>>> >
>>>
>>> This sounds like the Sabayon Live version is having difficulty
>>> displaying in the framebuffer during the boot phase.
>>>
>>> I've run into this before.  The TTY's are blank, but Xorg will work fine.
>>>
>>> If the screen is blank when you hit <Ctrl><Alt><F1> after Xorg has
>>> started, that's a good sign Sabayon is having trouble displaying to
>>> the framebuffer.
>>>
>>>
>>
>


Reply via email to