-
-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Does not start on some hardware, and has unreadable error messages #119
Comments
Can you list the hardware components on these machines such as CPU, GPU (integraded or descrete?), RAM, distro, kernel version, mesa version, and the output of |
Recreated this repeatedly on Arch linux 4.13.11-1, 8GB RAM, Core i3-6000, AMD RX470, Mesa 17.4.0-devel (git-1a61a8b9a7). This is using the precompiled liri-shell-git pacman package from the Liri repo. qtdiag on X11 returns this: gnome-logs found a few more interesting errors related to Liri (this is from mutliple attempts):
Liri run through the X11 windowed session also fails but for completely different reasons:
Since Liri doesn't seem to manually dump logs anywhere, I'll have to get an output from a normal session later. |
Hello. I have similar problem, does not starts on arch. I'm using i7-3770S CPU and Nvidia GTX 1080 with nouveau driver. Trying to start liri from tty |
Arch
linux-4.13.10-1
mesa 17.2.4-1
liri-shell-git 20171014.8ca7e54f-1
I have laptop with an NVIDIA chipset, GeForce 7150M / nForce 630M, that seems to run liri-shell without problem. But then, I have other machines on which liri-shell will not run. liri-shell seems to start, showing the spinning circle for a moment, and then quits, with an error message that over-writes the last line on the terminal display.
On another laptop machine with an Intel GPU using the i915 driver module, running "liri-session" from the virtual terminal, "liri-shell" returns with two different error messages. The circumstances that vary the error message are not clear.
The error message appears to over-writes the last informational line, which itself is truncated. Sometimes, the message is: 'Aborted (core dumped) cannot be mixed with others. Hzd_pixels_minmax GL_MESA_window_pos GL_EXT_multi_draw_arrays GL_EXT_stencil_wrap GL_ARB_sync GL_ARB_clear_texture GL_A'
At other times, the truncated message is:
'Abortedfailure in QList::take: "index out of range", file /usr/include/qt/QtCore/qlist.h, line 557rt.desktop"boprint-monitor.desktop"ARB_texture_non_power_of_two GL'
followed by the prompt, and then:
could not connect to wayland server
(EE)
Fatal server error:
(EE) Couldn't add screen
(EE)
On a desktop machine with a radeon card and a triple head display, the error messages are like:
[376033.507252] [drm:atombios_crtc_mode_fixup [radeon]] ERROR unable to allocate a PPLL
[376033.507265] [drm:drm_crtc_helper_set_config [drm_kms_helper]] ERROR failed to set mode on [CRTC:39:crtc-1]
where the driver fails to properly configure the graphics device for three simultaneous outputs.
Any thoughts about troubleshooting? Is there a way to get readable debugging output? Are these QtWayland or eglfs problems, as opposed to being liri-shell problems, per se?
The text was updated successfully, but these errors were encountered: