Blank, no cursor, no working shortcuts.

[ahmadraniri1994]

I'm trying the latest of newm and getting blank appearance, no cursor, and no working shortcuts. Log said about backlight stuffs and when I disable it, still no effect. Thanks. Log I got .

[ahmadraniri1994]

I launched it from TTY, other Wayland compositor and X window manager, still have same behaviours.

[ahmadraniri1994]

I'll try to install greeter and see what will happen.

[ahmadraniri1994]

I'll try to install greeter and see what will happen.

Still same.

[jbuchermn]

Please also post your config. If you installed the latest master, you're on v0.3alpha. Did you use v0.3 branch before?

[ahmadraniri1994]

O, Sorry for that. I install it with pip3 install git+https://github.com/jbuchermn/newm Here my config . Note : I comment some lines.

[jbuchermn]

Can you try changing the path in

background = {
    'path': os.path.dirname(os.path.realpath(__file__)) + '/resources/wallpaper.jpg',
    'anim': True
}

to something that certainly exists? This default config does not work in all cases. I just want to see if anything gets rendered.

Also please test

pywm = {
    'renderer_mode': 'wlr'
}

does this change anything?

[ahmadraniri1994]

Unfortunately, it's still same. I try to change the background path to :

background = {
    'path': '/home/ahmad/somewp.jpg',
    'anim': True
}

And add :

pywm = {
    'renderer_mode': 'wlr'
}

But it gives no change. I'll probably stick to v0.2 .

[jbuchermn]

Okay, thanks. It appears the renderer is not the issue...

You don't set your keyboard layout in the config - could that be the reason for keychords not working? Obviously you won't see anything, but working keychords should at least show up in the log, if it starts alacritty e.g..

Does it work on v0.2?

[ahmadraniri1994]

You don't set your keyboard layout in the config ?

I set it up and the shortcuts still don't work, cursor still gone.

Newm v0.2 works for me.

[jbuchermn]

Yeah this wouldn't change the rendering issues. But does anything show up in the logs if you press keybindings?

It's interesting that v0.2 works..

[ahmadraniri1994]

But does anything show up in the logs if you press keybindings?

unfortunately nothing show up in the logs.

Update what I tried and got on newm v0.3 :

• Background will show up when I change the anim to False.

  background = {
  'path': os.path.dirname(os.path.realpath(__file__)) + '/resources/wallpaper.jpg',
  'anim': False
  }

• Cursor still doesn't show.
• Keybinds still don't work though I set the keyboard layout :

  pywm = {
  "xkb_model": "pc104",
  "xkb_layout": "us",
  }

I want to stick with v0.2 for now, btw, how to prevent high cpu usage when using newm v0.2 ? the fan spins and make noise when I'm using newm, it's not like the other wayland compositors.

[jbuchermn]

Can you post a current log with the config that shows Blythe background?

Regarding v0.2, what you can do is debug and submit a PR. I'm no longer going to actively work on old versions, but I'm always happy about contributions.

However, high cpu usage is not something that's ever popped up before, so I think there might be something bigger going wrong (possibly the same issue preventing rendering on v0.3...)

Does the behaviour change in any way if launched inside sway, or another compositor instead of from tty?

[lidgnulinux]

Can you post a current log with the config that shows Blythe background?

sure, this is the log.

Does the behaviour change in any way if launched inside sway, or another compositor instead of from tty?

Both (launch from tty and from other wayland compositor) give same behaviour (high cpu usage on v0.2, blank and no cursor for v0.3). Pic (sometimes, it's almost 100% on one of the cpu, I don't know why) :

[jbuchermn]

I haven't had time to take a detailed look, but from a quick glance at the screenshot it seems like cpu usage stems from newm_panel_basic instead of newm, right?

How about disabling it?

I'll take a look at your v0.3 log as soon as I have time - fixing the current version is my priority.

[ahmadraniri1994]

Sure, yeah, no need to rush. Thanks @jbuchermn .

[pedrotrschneider]

I seem to be having the same issue. Reproduced exactly what was described. At first, no wallpaper, no mouse cursor and no keybindings were working. Tried adding

pywm = {
    'renderer_mode': 'wlr'
}

to no avail. Disabling wallpaper animations made the wallpaper appear, but it remained unresponsive otherwise. My config file and logs are attached (had to attach both as .txt because github, sorry for that).

newm_log config

Newm was installed from pip, and the distro is Fedora 36 with kernel 5.18 (if it matters at all). Newm was launched from the TTY with

start-newm -d

Other wayland compositors work just fine, such as Hyperland and Sway.

[ahmadraniri1994]

@pedrotrschneider I kind of giving up on version 3, version 2 works like a charm, so I stay there.

[jbuchermn]

This is really hard to debug for me as I cannot reproduce and have very little information. What I gather is

• Nothing interesting in the logs, no errors appear
• The desktop remains black, nothing is ever rendered (neither windows, nor background, mouse, ...)
• Disabling wallpaper animations makes the wallpaper show up. Does it show up properly? Or blurred / low-quality / distorted?
• newm-panel-basic takes up a lot of CPU

Some more questions:

• Can you do some more checks on keybindings - if you bind e.g. Mod-Enter to alacritty and hit Mod-Enter nothing shows up. But switching to a different vterm and running ps ax (or similar) - is alacritty running?
• Can you try to disable animations for your whole screen (in the outputs section) - does anything change?
• Can you try pywm-fullscreen - anything showing up?
• Can you take a screenshot using grim or take a recording using wf-recorder - anything showing up?
• What happens if you disable newm-panel-basic?

[pedrotrschneider]

@jbuchermn I'll try to answer all your questions in the order you asked for them:

• The wallpaper is mostly fine, except for four black squares in the four corners of the screen, each taking about 4% of the width of the screen (I'm on a laptop and can't test with other monitors at the moment, so that's the best I can do). I also can't show it to you, because no screenshot tool works.
• Tried to check if alacritty was running after pressing Mod-Enter but it seems to not be running (or at least ps ax doesn't see it, and killall says no process named alacritty is running.
• Disabling animations for the whole screen seems to not change anything.
• pywm-fullscreen -e firefox gives me a completely black screen. Tried running it with other programs as well, with the same result.
• As I mentioned above, I can't get any screenshot tool to work.
• The high cpu usage with newm-panel-basic is not an issue on my machine, probably a different issue related to something else. I tried disabling it all the same and nothing changed.

If there is anything else you want me to check, feel free to ask. I really want to make it work :)

[jbuchermn]

Thanks for the detailed feedback.

The black squares should be the rounded corners - it's very interesting that they are rendered, but completely wrong.

The fact that pywm-fullscreendoesn't work is very important. It means this is a lower-level issue in pywm, not newm. I opened an issue for it - if you have got some time, I'd like to debug some more over there: https://github.com/jbuchermn/pywm/issues/16

[Cherro59]

Have also such problems. My log