Open ahmadraniri1994 opened 2 years ago
I launched it from TTY, other Wayland compositor and X window manager, still have same behaviours.
I'll try to install greeter and see what will happen.
I'll try to install greeter and see what will happen.
Still same.
Please also post your config. If you installed the latest master, you're on v0.3alpha. Did you use v0.3 branch before?
O, Sorry for that.
I install it with pip3 install git+https://github.com/jbuchermn/newm
Here my config .
Note : I comment some lines.
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?
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 .
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?
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.
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..
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 :
anim
to False
.
background = {
'path': os.path.dirname(os.path.realpath(__file__)) + '/resources/wallpaper.jpg',
'anim': False
}
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.
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?
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) :
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.
Sure, yeah, no need to rush. Thanks @jbuchermn .
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 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.
@pedrotrschneider I kind of giving up on version 3, version 2 works like a charm, so I stay there.
This is really hard to debug for me as I cannot reproduce and have very little information. What I gather is
newm-panel-basic
takes up a lot of CPUSome more questions:
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?outputs
section) - does anything change?grim
or take a recording using wf-recorder
- anything showing up?newm-panel-basic
?@jbuchermn I'll try to answer all your questions in the order you asked for them:
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.pywm-fullscreen -e firefox
gives me a completely black screen. Tried running it with other programs as well, with the same result.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 :)
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-fullscreen
doesn'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
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 .