Missing UI elements and a disappearing cursor
See original GitHub issueFirst, thank you to all of the contributors for your hard work on this innovative project.
I had been trying out newm for a couple of days with only minor issues, but I ran into a few substantive problems after updating my system. Upon starting newm for the first time after the update, I ran into the following problems, which still persist at the time of my opening this issue (I’m only opening one issue because it seems quite plausible that they’re related, but please let me know if I should open two separate issues):
- UI elements like corners and borders were missing.
- My mouse cursor initially appeared on screen normally, but after mousing over my terminal (foot), it mysteriously disappeared and refused to reappear (even after I closed the terminal). My mouse was still working and I could still click on things by “dead reckoning” the location of the cursor, it’s just that the cursor itself was invisible.
- A similar issue occurs if I start newm and then mouse over Firefox.
- However, if I start newm and mouse over Alacritty, my cursor doesn’t disappear. If I then start foot and mouse over it, my cursor disappears as before.
The following are probably worth mentioning:
- The above issues occur both when I use my own configuration file and when I use the default configuration file.
- I use NixOS on the
nixos-unstable
channel. - I installed newm using
nix build "github:jbuchermn/newm#newm"
. I tried reinstalling newm today via that same command and the same issues occurred.
Here is a log file produced by a short newm session, launched with the default configuration file from a tty using the command start-newm
: log file. During this session, I launched Alacritty (via MOD4 + Enter
), launched foot via Alacritty, moused over foot (and watched my cursor disappear), and killed newm from foot via pkill newm
. When I moused over foot, the following error message was printed to the Alacritty terminal (among various other informational and warning messages): err: render.c:3808: failed to load xcursor pointer 'text'
. Because I used the default configuration file, there is a BacklightManager error near the beginning of the log file, but this doesn’t appear to be related to the issues above (in fact, the error does not appear if I use my own configuration file, which doesn’t make use of BacklightManager).
The log file linked above contains the following seemingly relevant lines:
00:00:00.007 [ERROR] [render/egl.c:183] EGL_EXT_platform_base not supported
00:00:00.007 [ERROR] [render/egl.c:473] Failed to create EGL context
00:00:00.007 [ERROR] [render/gles2/renderer.c:698] Could not initialize EGL
00:00:00.684 [ERROR] [types/output/cursor.c:269] Failed to pick cursor format
00:00:00.685 [ERROR] [types/output/cursor.c:354] Failed to render cursor buffer
00:00:00.785 [INFO] [../src/wm/wm_renderer.c:288] Could not find primitive shader 'corner' - defaulting
00:00:00.801 [INFO] [../src/wm/wm_renderer.c:288] Could not find primitive shader 'rounded_corners_border' - defaulting
Please let me know if there’s any additional useful information I can provide.
Issue Analytics
- State:
- Created a year ago
- Comments:7 (5 by maintainers)
Top GitHub Comments
So the issue seems to have been the divergent nixpkgs commits; updating the flake.lock file seems to have fixed the problem! For posterity: I cloned the newm repository, ran
nix flake lock --update-input nixpkgs
to bring the version ofnixos-unstable
used by the newm flake to the version ofnixos-unstable
I used to build the current version of my system, and rebuilt newm usingnix build .#newm
. This new version of newm works as intended—none of the issues described in the original post appeared.Just in case it’s useful information, before updating the flake.lock, I tried setting
pywm.renderer_mode
to"wlr"
as per @Pandademic’s suggestion, but the same issues seemed to appear. I was in the process of figuring out how to install version 2 of newm on NixOS when @jbuchermn suggested that the problem might be due to divergent nixpkgs commits.Huge thanks to both of you for your help!
@mcs0042 yep , your on 0.3. I do see some similarity between this and #111.
Can you try adding:
in the
pywm
section.Also , just checking but , the config is inside a python file … right?
That obviously isn’t the cause of the issue , but it never hurt to check.
Finally , do you mind trying newm 0.2 , and seeing if it works?
Thanks!