frozen login screen for Fury with xfce

aschiebe
Posts: 19
Joined: Sun Mar 29, 2020 10:43 am
Been thanked: 2 times

frozen login screen for Fury with xfce

Post by aschiebe »

Hi all,
I have since freebsd-update to 12.1 Release p3 from p2 the issue - in a virtualbox vmclient and on old nvidia driven desktop - that all is working fine, but when updating the packages with
pkg update -f; upgrade -f
after the first reboot the gui login screen is frozen. The cursor in the passwd field is blinking shortly and then no keyboard, mouse interaction any more. on the virtual client I can only shut, on the desktop system I can do a remote ssh login and the system is running and I can do a controlled shutdown. But bioth are frozen with the login screen.
When I do only the freebsd-update fetch and install, after a reboot all is fine. But when doing the pkg upgrade, I've tried both with or without -f, the login screen is frozen.
Install is quite default from the downloaded iso from march, no special pkg installed afterwards.
Anyone else having this issue? Maybe a solution for this freeze?
Due to boot environments I can rollback and the system is with 12.1 Rel p3 quite stable running, but as soon as I do the pkg upgrade again and reboot - the login screen is frozen.
Any help appreciated,
Ciao Arnold

little addon - boot into single mode is possible, but where to dig in to solve this freeze?

User avatar
CodeSlinger
Posts: 8
Joined: Thu Mar 26, 2020 12:55 pm

Re: frozen login screen for Fury with xfce

Post by CodeSlinger »

Hi aschiebe,
I do not have a matching setup. I have upgraded to 12.1-RELEASE-p3 with no problems. I have a number of additional packages and ports installed; but have not upgraded in a few weeks. Checking what needs upgrading I see a few suspect packages:

Code: Select all

lightdm*
mesa-*
wayland*
wayland
xf86-*
xfce4-*
xorg-server
I cannot upgrade right this second, I need to review all 133 upgrades before I commit. I will snapshot my system this evening and first upgrade without the above packages to make sure everything is good. If no problems, I'll complete the upgrades and see if I see the same results.

In the mean time, my first check would be for any errors in: /var/log/Xorg.0.log. If you see any try removing xorg.conf. If you have one, you might try moving out of the way. Check for it in both /etc/X11 and /usr/local/etc/X11. Also I had a problem with Xorg recognizing /usr/local/etc/X11/xorg.conf.d as a file and not a directory. If you get an error specific to that directory, rename it to something else.
Just a starting point for troubleshooting...

I'll let you know my results later tonight.
--
CodeSlinger

aschiebe
Posts: 19
Joined: Sun Mar 29, 2020 10:43 am
Been thanked: 2 times

Re: frozen login screen for Fury with xfce

Post by aschiebe »

Tanxs for the first hints, I will try to dig into.
I have made two with excluding these two wayland packages to be upgraded - no change, the login screen freezes after some sec cursor blinking. And the other try was not to upgrade the xorg-server, the result was that X is not startet, you are at a tty login, can login and all works fine, but you are not not able to do a startx from console, some error claiming about I think it was a abi change and the the xorg-server is not compliant, some error like that. So I in this try have upgraded this last pkg xorg-server and after reboot the login screen was froyen again!

aschiebe
Posts: 19
Joined: Sun Mar 29, 2020 10:43 am
Been thanked: 2 times

Re: frozen login screen for Fury with xfce

Post by aschiebe »

I have found no xorg.conf file.

In the Xorg.log I found a difference:

good log:
[ 9.828] (II) VBoxVideo(0): Modeline "640x480"x60.0 18.84 640 642 644 646 480 482 484 486 (29.2 kHz b)
[ 9.828] (II) VBoxVideo(0): Output VGA-0 connected
[ 9.828] (II) VBoxVideo(0): Using exact sizes for initial modes
[ 9.828] (II) VBoxVideo(0): Output VGA-0 using initial mode 800x600 +0+0
[ 9.828] (II) VBoxVideo(0): Using default gamma of (1.0, 1.0, 1.0) unless otherwise stated.
[ 9.828] (II) VBoxVideo(0): RandR 1.2 enabled, ignore the following RandR disabled message.
[ 9.833] (==) VBoxVideo(0): DPMS enabled
[ 9.833] (--) RandR disabled
[ 9.836] (II) AIGLX: Screen 0 is not DRI2 capable
[ 9.836] (EE) AIGLX: reverting to software rendering
[ 10.287] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[ 10.288] (II) AIGLX: Loaded and initialized swrast
[ 10.288] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 10.288] (II) VBoxVideo(0): Setting screen physical size to 211 x 158
[ 10.370] (II) config/devd: probing input devices...
[ 10.370] (II) config/devd: adding input device (null) (/dev/kbdmux)
[ 10.370] (II) LoadModule: "kbd"
[ 10.370] (II) Loading /usr/local/lib/xorg/modules/input/kbd_drv.so
[ 10.371] (II) Module kbd: vendor="X.Org Foundation"
[ 10.371] compiled for 1.18.4, module version = 1.9.0
[ 10.371] Module class: X.Org XInput Driver
[ 10.371] ABI class: X.Org XInput driver, version 22.1
[ 10.371] (II) Using input driver 'kbd' for 'kbdmux'
[ 10.371] (**) kbdmux: always reports core events
[ 10.371] (**) kbdmux: always reports core events
[ 10.371] (**) Option "Protocol" "standard"
[ 10.371] (**) Option "XkbRules" "base"
[ 10.371] (**) Option "XkbModel" "pc105"
[ 10.371] (**) Option "XkbLayout" "us"
[ 10.371] (**) Option "config_info" "devd:kbdmux"
[ 10.371] (II) XINPUT: Adding extended input device "kbdmux" (type: KEYBOARD, id 6)
[ 10.371] (II) config/devd: kbdmux is enabled, ignoring device atkbd0
[ 10.371] (II) config/devd: adding input device (null) (/dev/sysmouse)
[ 10.371] (II) LoadModule: "mouse"
[ 10.371] (II) Loading /usr/local/lib/xorg/modules/input/mouse_drv.so
[ 10.372] (II) Module mouse: vendor="X.Org Foundation"
[ 10.372] compiled for 1.18.4, module version = 1.9.3
[ 10.372] Module class: X.Org XInput Driver
[ 10.372] ABI class: X.Org XInput driver, version 22.1
[ 10.372] (II) Using input driver 'mouse' for 'sysmouse'
[ 10.373] (**) sysmouse: always reports core events
[ 10.373] (**) Option "Device" "/dev/sysmouse"
[ 10.373] (==) sysmouse: Protocol: "Auto"
[ 10.373] (**) sysmouse: always reports core events
[ 10.373] (==) sysmouse: Emulate3Buttons, Emulate3Timeout: 50
[ 10.373] (**) sysmouse: ZAxisMapping: buttons 4 and 5


and in the bad log the RandR will not be enabled and no devices for mouse/keyboard - this lokks for me the section where the error starts:

[ 9.903] (II) VBoxVideo(0): Modeline "640x480"x60.0 18.84 640 642 644 646 480 482 484 486 (29.2 kHz b)
[ 9.903] (II) VBoxVideo(0): Output VGA-0 connected
[ 9.903] (II) VBoxVideo(0): Using exact sizes for initial modes
[ 9.903] (II) VBoxVideo(0): Output VGA-0 using initial mode 800x600 +0+0
[ 9.904] (==) VBoxVideo(0): DPMS enabled
[ 9.904] (II) Initializing extension Generic Event Extension
[ 9.904] (II) Initializing extension SHAPE
[ 9.904] (II) Initializing extension MIT-SHM
[ 9.905] (II) Initializing extension XInputExtension
[ 9.905] (II) Initializing extension XTEST
[ 9.906] (II) Initializing extension BIG-REQUESTS
[ 9.906] (II) Initializing extension SYNC
[ 9.906] (II) Initializing extension XKEYBOARD
[ 9.906] (II) Initializing extension XC-MISC
[ 9.906] (II) Initializing extension SECURITY
[ 9.906] (II) Initializing extension XFIXES
[ 9.906] (II) Initializing extension RENDER
[ 9.907] (II) Initializing extension RANDR
[ 9.907] (II) Initializing extension COMPOSITE
[ 9.907] (II) Initializing extension DAMAGE
[ 9.907] (II) Initializing extension MIT-SCREEN-SAVER
[ 9.907] (II) Initializing extension DOUBLE-BUFFER
[ 9.907] (II) Initializing extension RECORD
[ 9.908] (II) Initializing extension DPMS
[ 9.908] (II) Initializing extension Present
[ 9.908] (II) Initializing extension DRI3
[ 9.908] (II) Initializing extension X-Resource
[ 9.908] (II) Initializing extension XVideo
[ 9.909] (II) Initializing extension XVideo-MotionCompensation
[ 9.909] (II) Initializing extension GLX
[ 9.909] (II) AIGLX: Screen 0 is not DRI2 capable
[ 10.338] (II) IGLX: Loaded and initialized swrast
[ 10.339] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 10.339] (II) Initializing extension XFree86-VidModeExtension
[ 10.339] (II) Initializing extension XFree86-DGA
[ 10.339] (II) Initializing extension XFree86-DRI
[ 10.339] (II) Initializing extension DRI2
[ 10.339] (II) VBoxVideo(0): Setting screen physical size to 211 x 158
[ 10.436] (II) config/udev: Adding input device System keyboard multiplexer (/dev/input/event0)
[ 10.436] (II) No input driver specified, ignoring this device.
[ 10.436] (II) This device may have been added with another device file.
[ 10.436] (II) config/udev: Adding input device System mouse (/dev/input/event1)
[ 10.436] (II) No input driver specified, ignoring this device.
[ 10.436] (II) This device may have been added with another device file.
[ 10.436] (II) config/udev: Adding input device AT keyboard (/dev/input/event2)
[ 10.436] (II) No input driver specified, ignoring this device.
[ 10.436] (II) This device may have been added with another device file.
[ 10.436] (II) config/udev: Adding input device IntelliMouse Explorer (/dev/input/event3)
[ 10.436] (II) No input driver specified, ignoring this device.
[ 10.436] (II) This device may have been added with another device file.
[ 10.436] (II) config/udev: Adding input device (unnamed) (/dev/vboxguest)
[ 10.436] (II) LoadModule: "vboxmouse"
[ 10.436] (II) Loading /usr/local/lib/xorg/modules/input/vboxmouse_drv.so
[ 10.437] (II) Module vboxmouse: vendor="Oracle Corporation"
[ 10.437] compiled for 0.0.0, module version = 1.0.0
[ 10.437] Module class: X.Org XInput Driver
[ 10.437] ABI class: X.Org XInput driver, version 24.1
[ 10.437] (**) Load address of symbol "VBOXMOUSE" is 0x80eca0018
[ 10.437] (II) Using input driver 'vboxmouse' for '(unnamed)'
[ 10.437] (**) (unnamed): always reports core events
[ 10.437] (**) Option "Device" "/dev/vboxguest"
[ 10.437] (**) (unnamed): Device: "/dev/vboxguest"
[ 10.437] (**) Option "config_info" "udev:/dev/vboxguest"
[ 10.437] (II) XINPUT: Adding extended input device "(unnamed)" (type: MOUSE, id 6)
[ 10.437] (**) (unnamed): (accel) keeping acceleration scheme 1
[ 10.437] (**) (unnamed): (accel) acceleration profile 0
[ 10.437] (**) (unnamed): (accel) acceleration factor: 2.000
[ 10.437] (**) (unnamed): (accel) acceleration threshold: 4
[ 10.437] (II) (unnamed): On.
[ 10.437] (II) VBoxVideo(0): EDID vendor "VBX", prod id 0
[ 10.437] (II) VBoxVideo(0): DDCModeFromDetailedTiming: 1024x7

but where to start/enable this randr when I have no xorg.conf file?
any ideas or I am wrong wrong with the reading of the log files?

Any help appreciated,
Tanxs.

aschiebe
Posts: 19
Joined: Sun Mar 29, 2020 10:43 am
Been thanked: 2 times

Re: frozen login screen for Fury with xfce

Post by aschiebe »

if I comment in /etc/rc.conf the line #lightdm_enable="YES" then it boots into tty and I can login on console, so far my findings for this evening.
start lightdm as root from console brings the same freezing login screen.
startx a very puristic x like windowmaker but also no keyboard input, only a moving mouse cursor.
Good evening for today.

User avatar
CodeSlinger
Posts: 8
Joined: Thu Mar 26, 2020 12:55 pm

Re: frozen login screen for Fury with xfce

Post by CodeSlinger »

So I can confirm the same lack of keyboard input after a full package upgrade. Unfortunately, I have not had enough time to do much troubleshooting, this process takes a bit longer for me since I am running in a Virtualbox VM and need to rebuild the virtualbox-ose-additions anytime the ABI version is updated.
I will be reviewing logs later today and let you know what I find.
--
CodeSlinger

User avatar
CodeSlinger
Posts: 8
Joined: Thu Mar 26, 2020 12:55 pm

Re: frozen login screen for Fury with xfce

Post by CodeSlinger »

Okay, I think I found the problem. I'll need to restore my snapshot to confirm, but it looks like the xf86-input-evdev package was removed during the upgrade. I see the evdev kernel module is loaded and ready, but Xorg doesn't have a module to use it on my system.

Code: Select all

sudo pkg install xf86-input-evdev
This fixed my problem. Please test and let me know your results.
--
CodeSlinger

User avatar
CodeSlinger
Posts: 8
Joined: Thu Mar 26, 2020 12:55 pm

Re: frozen login screen for Fury with xfce

Post by CodeSlinger »

Hold off on this option. Now that I look back, I do not think this is needed. I need to do a bit more troubleshooting.
CodeSlinger wrote:
Fri Apr 10, 2020 9:47 am
Okay, I think I found the problem. I'll need to restore my snapshot to confirm, but it looks like the xf86-input-evdev package was removed during the upgrade. I see the evdev kernel module is loaded and ready, but Xorg doesn't have a module to use it on my system.

Code: Select all

sudo pkg install xf86-input-evdev
This fixed my problem. Please test and let me know your results.
--
CodeSlinger

aschiebe
Posts: 19
Joined: Sun Mar 29, 2020 10:43 am
Been thanked: 2 times

Re: frozen login screen for Fury with xfce

Post by aschiebe »

Hi,
no hurry, but it is good feeling that you can confirm this issue and I am not alone with this and TanXs that you look into this.
I have asked on Telegram too, and I got this hint - I try it in a virtualbox first before doing it on my nvidia driven destop:
pkg update -f && pkg upgrade -fy && pkg install -fy xorg lightdm wayland virtualbox-ose-additions
- these actions are just running in my virtualbox vmclient.
For the nvidia system I was told to install the nvidia drivers in the last action too.
I have searched in my good BE, but cannot find this xf86 package you mentioned.
Keep you posted.

aschiebe
Posts: 19
Joined: Sun Mar 29, 2020 10:43 am
Been thanked: 2 times

Re: frozen login screen for Fury with xfce

Post by aschiebe »

Hi again,
I do not why and how the guy on Telegram found this tip, but it works with some little changes and addon in my vbox vmclient.
Next step will be to repeat these steps on my nvidia on prime system.
Here is a short summary of the steps I had done, for sure create first a new BE and boot into the BE to have a rollback option.
Puuh, vbox vmclient seems to be done, now proceed with my nvidia desktop.

# after freebsd-update fetch and install to 12.1Release p3 and pkg upgrade the login screen freeze
# this should fix it, tip received from Telegram group
pkg update -f && pkg upgrade -fy && pkg install -fy xorg lightdm wayland virtualbox-ose-additions
# the command, except pkg update, needs after first upgrade an redo, because only pkg itself was upgraded

# reboot and now keyboard is working again at login screen, no mouse
# do login with success
# after login, look for moused service, ps -ef | grep mouse
# no process found
add moused_enable="YES" to /etc/rc.conf
service moused start
# now keyboard and mouse are back on work!
# first reboot done and keybaord/mouse are working as expected!!

Maybe you can try these actions too and verify if this was a one shot luck or helps you too?
Ciao Arnold

Post Reply