KDE Startup - Black Screen
Tags:
None
Registered Member 
|
Yes, for some reason I can run these just fine, in XFCE through X2Go: kwrite, system-settings (kde), kdiff3, konqueror, kopete, kid3-qt, konsole, ksysguard, kuser, and KWalletManager.
KWin is still furiously crashing and restarting several times a second. I've rebooted, and no change. No screen flicker or flicker of any apps. Starting a KDE X2Go session, still takes forever on the splash screen K, and eventually comes to the black screen with (working) cursor. /var/log/kdm.log:
It is not creating an ~/.xsession-errors file for some reason. Here is the most recent /var/log/Xorg.0.log: https://pastee.org/fh2ah I do have KDE running fine on another machine, but find it impossible to get OpenGL running for some reason. I wonder if that same issue may be contributing to the problem on the bad machine? |
Administrator
|
Please provide the full output of "glxinfo", so we can rule out any GL related issues on your system?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Sure.
I have to give this command in XFCE through X2Go. I'm seeing some AMD and ATI references in there, although I don't know whether they refer to AMD video cards. I used to have an AMD card in that machine, but have changed the motherboard and now use an Intel CPU-based GPU. (E3-1265L v3) Since I removed the fglrx GLX driver, I find that now on the main console I can <alt><f2> to a console and <ctrl><alt><f1> to the main console. And from KDM I can still choose XFCE and boot into that, but when I select KDE I still get the black screen with (working) cursor. And the cursor is cyan-colored, as it should be, Yesterday I saved the dmesg from boot and went though it carefully. (below) I deleted all the early lines as they are irrelevant and show no errors.
Another thing: audio is not working on this machine. Whenever I try to play an mp3 song in XFCE it says:
Notice in /var/log/Xorg.0.log above that it notices the audio device for some reason. (but doesn't load drivers) Personally, I suspect this is a dbus problem of some sort. dbus is definitely contributing to my audio problems. I can run KDE systemsettings in XFCE and it runs fine, but when I choose Multimedia and AudioVideoSettings, it sits there forever. When I run systemsettings from the command-line:
... and even when I <ctrl>c it, I still get these dbus timeouts. I have to kill -9 all processes related to systemsettings for the messages to stop.
|
|
Administrator
|
First problem - your system is running compositing through llvmpipe, which has extremely poor performance. Are you accessing this system directly, or remotely? If it is directly, then please check your /etc/X11/xorg.conf - it may be configured to not use the Intel driver. Otherwise, please verify your X11 installation, as it appears the Intel driver may be missing.
As for audio, is Pulseaudio present on your system? With regards to D-Bus - does this only occur when accessing the Phonon module in System Settings, or do other modules trigger it as well? Also, for D-Bus - are other applications other than System Settings affected by this?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Yes I did run those commands through XFCE, and no I didn't have the intel driver specified, and no I didn't have Pulse installed. I didn't think Pulse needed to be installed (no one's ever explained it), but I installed it. Then I set up /etc/X11/xorg.conf.d/20-intel.conf to specify the intel driver.
I rebooted the system and controlled it from its console, intending to run the tests again. It booted to a point, then black screen. I booted into recovery mode and removed 'quiet' from the kernel command line and rebooted. It booted to a certain point and then gave these as fast as it could, ad infinitum: "skip ordering cycle found, skipping d-bus system message bus socket" According to G**gle, there is no such incomprehensible error. I give up. I've been down for almost a week and this is my main server. I'm doing a complete reinstall with XFCE. KDE has fallen to pieces. |
|
You changed something on the setup between the first post and the second last.
The original post includes
and the glxinfo says you're running llvmpip (that is, no hardware acceleration is loaded) However, this is not the main issue (kwin would simply turn off compositing on the SW renderer or after crashing "too often in a row". The reason is on a lower level, a broken installation and more severe. I suspect that this:
points the core of it - apparently /tmp is ro, what likely means there will be no "/tmp/ksocket-`whoami` resp. the relevant sockets in it (when logging into KDE) Overmore I wonder whether /var/(run|cache|tmp|lock) would then be ro as well. |
|
Administrator
|
Please post the output of "mount".
In terms of why llvmpipe is being used, this is probably due to either kernel options disabling it, or installation problems. Can you also provide the content of /proc/cmdline?
KDE Sysadmin
[img]content/bcooksley_sig.png[/img] |
|
Registered Member
|
Neither.
|
|
/tmp isn't mounted and not a tmpfs (hint: systemd does not like that at all)
Can you
Also have a look around in there, it could be that clean-up is attempted before remounting / rw, thus fails and therefore gets you trouble. |
|
Registered Member
|
I am able to touch /tmp/ksocket-bill/dummy and the file is created, although this is after I'm booted and x2go-ed in by xfce, since I get only a black screen in kde. Yes I see that /tmp isn't mounted, but I think that's because it's part of the regular filesystem on /. It's definitely operational and touchable.
Twice over the past week, I've deleted everything in /tmp and /var/tmp. No improvement. The system boots perfectly, including my custom .service files for unbound, dnscrypt, mysqld, and mythtvd which are mutually interdependent. The first thing that I can see in the boot process that is disturbing is in /var/log/Xorg.0.log:
It appears that I am not getting OpenGL, and nothing I've done has fixed it, and G**gle has never heard of this error. All the relevant OpenGL packages are installed. This is a new motherboard, an ASUS H87M-Pro, with Intel CPU GPU. an E3-1265L v3. All brand new and the latest technology, running the latest Debian Testing. I am seeing indications that several processes are segfaulting (above) for reasons that I don't understand. I've run Debian for 15 years (including many years on KDE) and have never, never had this kind of problem. |
|
Registered Member
|
Upto now I only saw such messages about "undefined symbol: _glapi_tls_Dispatch" when the proprietary nvidia driver is installed (fglrx maybe too, I don't know). They are caused by the fact that that driver overrides Xorg's libglx and Mesa's libGL with its own versions. So do you have that driver installed? (you said you switched the mainboard. maybe you had an nvidia card before?) You have to remove/uninstall it completely for the intel driver to fully work. |
|
Registered Member
|
Originally yes, I'd swapped out the mobo without reinstalling the OS, and yes it had an AMD card. But I'd deinstalled everything fglrx that I could find before swapping the mobo. But when I got desperate to get -something- working in KDE, I did a complete new install of Debian Testing. (Net install, Expert Mode, KDE desktop) No change in the symptom.
In doing a Synaptic search I find that I have installed: libvdpau-dev, libvdpau1, nvidia-installer-cleanup, and xserver-xorg-video-nouveau. These were installed by default, as I haven't ever had an nVidia card in this machine nor chose to install these. Marking nvidia-installer-cleanup for complete removal also marked numerous OpenGL packages for removal as dependencies, which I can't remember now. I also have libfglrx, apparently installed by default. I've removed these now, and nothing is installed when I search on nvidia or fglrx, but am unable to reboot to test as I'm still restoring files to this system. |
|
Registered Member
|
Well, then you have some version mismatch there between the Mesa, Xorg and intel driver packages, I would say. I don't use Debian, so cannot really tell you which packages that would be.
Those are not part of the nvidia driver and should not have any negative impact (libvdpau1 is for using VDPAU also with other drivers/cards, and nouveau is even a completely different driver, based on Mesa). nvidia-installer-cleanup would be there to completely remove the nvidia driver if installed I guess. But then I'd think you won't miss them either.
Hm. I'm not sure whether this was a good idea... Depending on what OpenGL packages that have been.
Hm. That package's description is apparently "non-free ATI/AMD RadeonHD display driver (runtime libraries)", so it might indeed have caused the problem. Although by a closer look at the package, it doesn't look dangerous. |
|
Either
* a non-mesa libGL (nvidia/fglrx) is resolved or * the mesa package is (very much < 7.xx) too old or * MESA was build with shared libglapi, but that library isn't present now -> No binary that links OpenGL will start (inc. kwin and plasma-desktop) --> Which MESA package is installed? (please refer to http://packages.debian.org) What's the output of
Please notice that this is an additional issue, since the original post had a same MESA installation and kwin did start according to the posted .xsession-errors |
|
Registered Member
|
I don't want to interrupt my data restore as it's massive, but I terminated all my x2go windows, and sshed in to systemctl restart kdm, on the theory that that would restart X after I'd deinstalled the nvidia and fglrx packages. Then tried KDE in an x2go window again -- black screen.
These packages are installed and at version 10.1.0-4: libgl1-mesa-glx, libglapi-mesa, libglu1-mesa-dri, libosmesa6, libwayland-egl1-mesa, libopenvg1-mesa, libegl1-mesa, libgbm1, libgles2-mesa, libegl1-mesa-drivers. I haven't included the -dev files here. Also installed are these packages: mesa-utils: 8.1.0-2+b1 libglu1-mesa: 9.0.0-2 I have to enter this in XFCE through x2go:
|
Bookmarks
Who is online
Registered users: Bing [Bot], Google [Bot], Sogou [Bot], Yahoo [Bot]
