search

manjaro / release-plan

Roadmap for our Manjaro install media releases
85 stars 7 forks source link

XFCE-GTK3 takes longer to load desktop #197

Closed philmmanjaro closed 6 years ago

philmmanjaro commented 6 years ago

In live-session I detected that the destkop loads longer than usual. However this also happens with TTY ...

oberon-manjaro commented 6 years ago

Kernel related maybe? You're using 417, right?

philmmanjaro commented 6 years ago

Happens also with 416 ...

oberon-manjaro commented 6 years ago

Hm. 414? ;-)

philmmanjaro commented 6 years ago

We will see what it is. We are still in the alpha state anyway ...

oberon-manjaro commented 6 years ago

I appear to have a similar issue with a current i3 unstable ISO with linux417 in vbox. Will try to compare to kernel 414 now.

oberon-manjaro commented 6 years ago

We also should check if switching to regular gtk3 instead of gtk3-classic makes a difference!

oberon-manjaro commented 6 years ago

gtk3 vs gtk3-classic makes no difference.

oberon-manjaro commented 6 years ago

To me it appears that the loading of the i3 desktop is normal while using linux414 and slowed down with 416 or 417. Also with the newest kernels about every other time lightdm-slick-greeter refuses to start. I haven't found an error message in the logs, yet. System simply hangs without either the DM showing up (when trying to re-log) or when autologin is supposed to be happening. Will try to find out if the same problem exists with lightdm-gtk-greeter for me.

oberon-manjaro commented 6 years ago

Same issue with lightdm-gtk-greeter and linux417. Since this problem is not present on my installed system, which also uses linux416, my best guess currently is that the issue is related to the virtualbox-modules for linux416 and 417. Also this strange observation could be caused by linux416-virtualbox-modules (this bspwm build uses 416)

NuclearPhoenixx commented 6 years ago

Also with the newest kernels about every other time lightdm-slick-greeter refuses to start. I haven't found an error message in the logs, yet. System simply hangs without either the DM showing up (when trying to re-log) or when autologin is supposed to be happening. @oberon2007

Does this only concern 4.17 and the latest testing lightdm/VBox version? Because I'm using lightdm-gtk-greeter from stable branch with kernel 4.16 and the virtualbox-host-modules and everything is perfectly fine.

philmmanjaro commented 6 years ago

Seems also KDE seems to be affected. Only our Gnome edition seems to be kinda fine. I've to see how it will act in a later state. linux417 is still in early development ...

oberon-manjaro commented 6 years ago

Meanwhile at least with i3 the issue seems to have disappeared with linux416-4.16.4.

philmmanjaro commented 6 years ago

Seems linux417 4.17.r180429.cdface5-2 fixes this, however we have still weird issues within CAL not able to click on dialogs with mouse. Maybe a VBox issue. Didn't had time to test on real HW.

philmmanjaro commented 6 years ago

Also linux416 4.16.5 has no issue with this anymore. Also less regressions than linux417 as of now ...

philmmanjaro commented 6 years ago

Here is another workaround:

sudo pacman -S haveged
sudo systemctl enable haveged
sudo systemctl start haveged
philmmanjaro commented 6 years ago

Seems to be related to an old friend: https://github.com/systemd/systemd/issues/4167