lirios / lirios/shell

Does not start on some hardware, and has unreadable error messages

Open
#119 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C++
Stars
247
Forks
15
PR merge metrics
No merged PRs in 30d

Description

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?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing liri-shell through liri-session on the reported NVIDIA, Intel/i915, and Radeon triple-head setups while preserving complete terminal output. Compare the failures with the QtWayland and eglfs possibilities named in the report; done means identifying a reproducible cause and documenting a targeted fix or diagnostic path.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
desktop, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.