black screen with blinking cursor in qemu VM
Page 1 of 1 (8 posts)
Tags:
None
Registered Member 
|
Hello nice people
 Trying to get kde build from source in a QEMU VM (using gnome-boxes or virt-manager). VM works fine before I installed kdesrc-build stuff. After installing the dependencies https://community.kde.org/Guidelines_an ... pendencies and running kdesrc-build as none root user (with install location ~/kde) and a reboot, the VM no longer starts into a GUI and stops at a blank screen with a blinking _ cursor. I can still access the lower virtual consoles. This happend in the developer edition and with the user edition of KDE-neon. I cannot see any errors in the systemd journal or dmesg, /var/log/sddm.log, /var/log/Xorg.0.log. If I sudo startx the desktop starts, but no inputs are possible (system seems to hang completely). I appreciate any ideas how to find any error information or how to solve this. Thank You!  PS: trying to test a potential fix for this bug Bug #372555 (for libinput), without affecting the running system. |
|
Step-by-Step Testing:
1) Boot into non-graphical mode (No 'sddm'): Kernel-option in GrubEntry's 'linux'-line: systemd.unit=multi-user.target 2) X Window System still working? Test: xinit /usr/bin/xterm -- /usr/lib/xorg/Xorg 3) If YES, then start one of Your newly compiled KDE-executables manually from xterm's command line, and examine the result. |
|
Registered Member
|
Thx for the response
 If I run the xinit as user I get:
If I run it with sudo, the xterm shows up, but there are also no inputs possible (system seems to hang completely). Xorg.0.log:
Edit: I enabled the serial console and can still access the system via the text console after X is started. So the system does not hang, but X seems to capture all inputs (including CTRL+ALT+F1) but not doing anything with them. |
|
If You have a visible and movable mouse-cursor,
then You have to position it within the xterm window. Only then the command line will take keyboard input. Or dont't You have any mouse at all? |
|
Registered Member
|
no cursor and not even e.g. CTRL+ALT+F1 working
|
|
Before starting 'X', try
Test Your mouse under pure Linux (Move mouse, end with Control-c): $ sudo cat /dev/input/mouse0 [sudo] password for su0: (�8��8��8��8��8��8��((�(�(�(�(�( ▒▒�▒�▒▒▒�▒�▒�▒�▒�▒�▒�^C Also, try /dev/input/mice. Normally, X detects Linux-mouse automatically. Maybe, You have some Guest-OS extensions installed. Maybe, they have to be started manually. Sometimes called 'mouse/keyboard integration' For example, with Virtual Box You would have: VBoxClient VBoxService or similar. Or, with Qemu, you have to choose a driver using command-line option. Or, within a graphical mouse-settings interface of Your VirtualMachine Manager. Check keyboard, likewise. |
|
Registered Member
|
well ... no, not getting anything from the mouse this way, but I don't know if the mouse input is passed in to the VM before X is running (keyboard works before that). The spice-vdagentd is running.
I guess I'll try to install the build dependencies one by one, and see if I can find the package that breaks it. Thanks for your help. Edit: problem occurs after installing xserver-xorg-dev package from the list here (suprise, suprise  ). I will update this post when I have time to investigate further, but would appreciate infos, if this is a known issue. |
|
Registered Member
|
The problem was that I installed xserver-xorg-dev which removes a bunch of stuff because it is in conflict with the enablement stack that is installed by default.
The correct package to install in this case is:
I did not try to resurrect the broken system however, but started from an older snapshot. (additional steps would probably be required to fix this in a system that has been broken by installing the wrong package) Thanks for the help. Marking this as solved and will try to update the wiki page somehow to mention this problem. |
Page 1 of 1 (8 posts)
Bookmarks
Who is online
Registered users: Bing [Bot], Google [Bot], Sogou [Bot]
