View previous topic :: View next topic |
Author |
Message |
MrZammler Tux's lil' helper
Joined: 24 Jun 2003 Posts: 128 Location: The Island of Crete
|
Posted: Tue May 04, 2021 3:04 pm Post subject: |
|
|
Nope, it doesn't want to work....
I'm running wlroots 0.13.0 now, and the latest from 0.7.x branch (EGIT_OVERRIDE_BRANCH_WAYFIREWM_WAYFIRE="0.7.x") so basically 0.7.1.
When I turn the monitor off now, all apps crash. I get some:
Code: | II 04-05-21 17:55:44.609 - [wayfire-9999/src/core/output-layout.cpp:1034] remove output: HDMI-A-1
II 04-05-21 17:55:44.609 - [wayfire-9999/src/core/output-layout.cpp:980] new output: NOOP-1
II 04-05-21 17:55:44.609 - [wayfire-9999/src/core/output-layout.cpp:388] loaded mode 2560x1440@60000
II 04-05-21 17:55:44.609 - [wayfire-9999/src/core/output-layout.cpp:577] Couldn't find matching mode 2560x1440@60 for output NOOP-1. Trying to use custom mode(might not work)
(type equals variant: [type: string, value: toplevel] | (type equals variant: [type: string, value: x-or] & focusable equals variant: [type: bool, value: 1]))
type equals variant: [type: string, value: overlay]
false
false
false
false
EE 04-05-21 17:55:44.610 - [wayfire-9999/src/core/output-layout.cpp:467] disabling output: HDMI-A-1
II 04-05-21 17:55:44.610 - [wayfire-9999/src/core/output-layout.cpp:140] transfer views from HDMI-A-1 -> NOOP-1
(EE)
(EE) Backtrace:
(EE) 0: Xwayland (xorg_backtrace+0x53) [0x555660bbd6b3]
(EE) 1: Xwayland (0x555660a1b000+0x1a61f5) [0x555660bc11f5]
(EE) 2: /lib64/libpthread.so.0 (0x7f8bcae91000+0x12bc0) [0x7f8bcaea3bc0]
(EE) 3: Xwayland (RRModeDestroy+0x0) [0x555660b05f20]
(EE) 4: Xwayland (RROutputSetModes+0x5c) [0x555660b0839c]
(EE) 5: Xwayland (0x555660a1b000+0x49a98) [0x555660a64a98]
(EE) 6: /usr/lib64/libffi.so.7 (0x7f8bcacab000+0x6ded) [0x7f8bcacb1ded]
(EE) 7: /usr/lib64/libffi.so.7 (0x7f8bcacab000+0x634c) [0x7f8bcacb134c]
(EE) 8: /usr/lib64/libwayland-client.so.0 (0x7f8bcb2d8000+0x9200) [0x7f8bcb2e1200]
(EE) 9: /usr/lib64/libwayland-client.so.0 (0x7f8bcb2d8000+0x5b38) [0x7f8bcb2ddb38]
(EE) 10: /usr/lib64/libwayland-client.so.0 (wl_display_dispatch_queue_pending+0x7c) [0x7f8bcb2df12c]
(EE) 11: Xwayland (0x555660a1b000+0x41ceb) [0x555660a5cceb]
(EE) 12: Xwayland (0x555660a1b000+0x1a6bd1) [0x555660bc1bd1]
(EE) 13: Xwayland (WaitForSomething+0x193) [0x555660bbb353]
(EE) 14: Xwayland (0x555660a1b000+0x16edb3) [0x555660b89db3]
(EE) 15: Xwayland (0x555660a1b000+0x1731a3) [0x555660b8e1a3]
(EE) 16: /lib64/libc.so.6 (__libc_start_main+0xeb) [0x7f8bcacf4eab]
(EE) 17: Xwayland (_start+0x2a) [0x555660a5c85a]
(EE)
(EE) Segmentation fault at address 0x555337606e37
(EE)
Fatal server error:
(EE) Caught signal 11 (Segmentation fault). Server aborting
(EE)
II 04-05-21 17:55:44.662 - [xwayland/server.c:211] Restarting Xwayland
II 04-05-21 17:55:44.664 - [xwayland/server.c:99] WAYLAND_SOCKET=26 Xwayland :0 -rootless -terminate -core -listenfd 20 -listenfd 21 -wm 46
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning: Unsupported maximum keycode 569, clipping.
> X11 cannot support keycodes above 255.
Errors from xkbcomp are not fatal to the X server
II 04-05-21 17:55:45.226 - [backend/drm/drm.c:1221] Scanning DRM connectors on /dev/dri/card0
II 04-05-21 17:55:45.227 - [backend/drm/drm.c:1315] 'HDMI-A-1' connected |
|
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Tue May 04, 2021 4:20 pm Post subject: |
|
|
I created a sets package for wayfire
Code: | $ cat /etc/portage/sets/wf
gui-libs/wlroots
gui-libs/wf-config
gui-wm/wayfire
gui-libs/wayfire-plugins-extra
gui-apps/wcm
gui-apps/waybar |
I've had problems with wf-config or the plugins not being 100% in sync, so I just compile the set when I update either wlroots or wayfire.
You might try that.
Edit to add: I'm also running the standalone version of xwayland, though I'm not sure how many changes there are between the xserver version and the standalone. _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
MrZammler Tux's lil' helper
Joined: 24 Jun 2003 Posts: 128 Location: The Island of Crete
|
Posted: Tue May 04, 2021 4:49 pm Post subject: |
|
|
Quote: | Edit to add: I'm also running the standalone version of xwayland, though I'm not sure how many changes there are between the xserver version and the standalone. |
Hmm, what do you mean by that?
Btw, on the whole wayfire thing... It's really nice, and ticks a lot of boxes of what I'm looking for in a wm... For me it only misses a way to switch to a workspace (<super>+num, pressing <super>, releasing and then pressing a key is hard!), a back_and_forth shortcut, and I'm set |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Tue May 04, 2021 5:01 pm Post subject: |
|
|
MrZammler wrote: | Quote: | Edit to add: I'm also running the standalone version of xwayland, though I'm not sure how many changes there are between the xserver version and the standalone. |
Hmm, what do you mean by that? |
Many of the wayland devs that had patches for xorg-server xwayland, have been whining over the last year or so, and RH/FDO and company worked on spliting it out as a separate package. The theory being that patches would/could be applied faster than going through Xorg.
I just downloaded a tarball, compiled it (meson makes it easy), it produces one binary Xwayland, which I put in my personal bin directory and then point to it before starting wayland => export WLR_XWAYLAND="/home/don/bin/Xwayland". I've had no crashes from running it. _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Tue May 04, 2021 5:05 pm Post subject: |
|
|
I think I've seen a request from someone else asking about a shortcut key.
What would work for me, would be to enhance the fast switcher to not just work on the current workspace, but all of them, the I could find the window/app I wanted by just holding the key and swapping till I found it. Not quite as nice as swapping from wsp 1 app 2 to wsp 4 app7, but a lot easier to program. _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
mv Watchman
Joined: 20 Apr 2005 Posts: 6780
|
Posted: Tue May 04, 2021 5:14 pm Post subject: |
|
|
MrZammler wrote: | For me it only misses a way to switch to a workspace (<super>+num, pressing <super>, releasing and then pressing a key is hard!), a back_and_forth shortcut, and I'm set :-) |
I am using a 2x2 layout, since more than 4 workspaces do more harm than good to me. And then I configured vswitch with <super>+KEY_{DOWN,UP,LEFT,RIGHT} correspondingly (of course, switching off the effects by setting the timeout to 0) - so switching from any (existing) workspace to any other is a quick no-brainer. I did this already with fvwm, only that with wayfire it actually works even if windows get half-shifted into another workspace.
The only ugly thing is when I press TAB in switcher (with speed=0 and view_thumbnail_scale=0 to get rid of the effects), I still see a "blank" screen before the next application is activated, that is the "effects" cannot really be avoided here. |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Tue May 04, 2021 5:29 pm Post subject: |
|
|
I swapped the keystrokes for fast-switcher and switcher, as I don't care about the display effects.
I had been intending to cut down the number of workspaces, I seldom use more than 3 or 4. _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Mon Jul 05, 2021 8:30 pm Post subject: |
|
|
I had serious amdgpu driver crashes on Sway which required hard reset, so I was forced to try Wayfire and switch to it.
It's ok, but I prefer tiling WM's, can't get used to pressing super key and then release it and then pressing the workspace number.
I tried dwl and hikari, problem with those is the status panel or bar, Waybar works but it can't deal with workspaces, otherwise I think I would use one of them.
Overall Wayland is ready I guess, there are problems but yeah, if you're not going for gnome or plasma information is sparse, other WM's are lacking features and I feel like they are always racing something, some new feature, trying to get to the point where some X11 WM's are, you have to be on 9999's which then require 9999 of some system lib etc.
It's definitely usable, but I don't know, will live in it for one more week and then decide if I'll go back to X11
I would use Sway for sure and I like it, but for some reason it doesn't handle amdgpu well, I tried many things, people say downgrading linux-firmware solves that problem, but in my case that didn't help, stable and latest mesa, stable and latest kernel ... it still happens, and it happens only on Sway, really weird. |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Mon Jul 05, 2021 8:45 pm Post subject: |
|
|
Which version of sway? Kernel version? amd card?
I run 9999 versions of at least wlroots, wayfire and waybar, just to keep them on the same page.
Wayland is very much changing, it's too new (in the scheme of things) to be stable, as features get tried, refined or dropped.
It's similar in quality to when Xfree86 was around and was moving to merge with xorg-server.
Lots of crashes, apps weren't that plentiful, etc.
I'm on radeon, the reason being, I got tired of the nvidia card hard freezing X and having to power it off to get control.
I've had a few problems with wayland stuff, especially before going 9999 versions, but no hard locks, a few crashes where you're magically back at the console a refusal of the monitor to wake back up once it went to sleep, ssh'd in and got it to work (fixed by later 9999 sync). A few problems, nothing major.
I like it so well, I've long removed xorg-server, just wayland, Xwayland and the X libs and apps. _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Mon Jul 05, 2021 8:50 pm Post subject: |
|
|
No matter which one, kernel I tried stable and latest 5.13, amd card is internal vega raven
I tried to solve it, found this today , and several other threads, that guy gave some links as well, where he discovered a solution for him (linux-firmware)
I'll keep trying but not much else I can do |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Mon Jul 05, 2021 9:31 pm Post subject: |
|
|
Don't know much about the vega series, I'm running an older RX 550.
Might be firmware related, as those are new enough to not have all the bugs worked out of the drivers (firmware)
Could be mesa related too, since they get fixes for lots of the amd stuff from amd itself.
Which version of mesa are you running?
I've swapped to the latest 21.1.4, no problems so far.
Edit to add: From one of of the links off of the link GPU reset fixes
https://patchwork.kernel.org/project/dri-devel/patch/20210520022500.4023-1-alexander.deucher@amd.com/
From the patch it looks like it might be kernel driver related. _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Mon Jul 05, 2021 10:00 pm Post subject: |
|
|
Thing is, I went back to stable yesterday I think, or the day before, anyway I just found out today about linux-firmware, so I used downgraded firmware but with all else stable.
Wasn't in the mood to go unstable again, even though it's not that time consuming, and thinking that doesn't even matter, since those users didn't mention that's important.
Right now I'm on mesa 21.0.3 and kernel 5.10.27 , and on latest firmware (i think firmware is always unmasked)
I did try kernel 5.13 so I guess that patch didn't work in my case, or I don't know if that's even merged or not
Again, if you're not running Sway it won't happen, I don't get that in Wayfire or other compositors , let alone X11
Problem is I can't even test that easily, sometimes it happens quick, sometimes it needs hours, and when it does happen it's always while watching some video or in a video game.
It's not just Ryzen Vega, dedicated cards as well from what I can tell, RX 580 in this link, scroll all the way down, 3rd post from the bottom, from Florian, 2 weeks ago
https://gitlab.freedesktop.org/drm/amd/-/issues/934
Edit :
and here's the latest crash details, from today
https://pastebin.com/AXfcV9ZM |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Mon Jul 05, 2021 10:35 pm Post subject: |
|
|
Interesting.
I see some people went back to 21.0.2 and some patch and things seemed to work.
I didn't see anyone say anything about earlier versions such as mesa-20.3.5.
Some of the people were even having crashes in X. _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Mon Jul 05, 2021 10:50 pm Post subject: |
|
|
Yeah, in my case it's only Sway, screen will go black, freeze like, not entirely black, some artifacts are shown, and the audio still works, it goes like that for maybe ten seconds, then the monitor turns off, at which point hard reset is the only option.
Well, never mind, I'll keep an eye on it and try it again from time to time.
Had crash in Wayfire today, though this is different, I use Zathura for PDF's, it doesn't happen always, but today I had to read few of them and when I closed one the Wayfire just crashed and I was back to tty
What is this in the config exactly, can you tell me ?
And do I need gui-libs/xdg-desktop-portal-wlr ? Because I don't have that one installed.
Code: | portal = /usr/libexec/xdg-desktop-portal |
I mean I guess it's related because when that happened this was logged :
Code: | Jul 5 20:02:13 theMainMachine kernel: pool-/usr/libex[24657]: segfault at 8 ip 00005bd19bac4293 sp 00007aff2998e750 error 4 in xdg-desktop-portal[5bd19bab5000+74000]
Jul 5 20:02:13 theMainMachine kernel: Code: 24 18 4c 8d 74 24 20 eb 56 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 48 8b 44 24 18 48 8d 15 74 6f 06 00 be 10 00 00 00 31 ff <48> 8b 48 08 31 c0 e8 a2 12 ff ff 48 8b 7c 24 20 48 85 ff 74 05 e8 |
Maybe it was decorations plugin, I turned that off later, regardless of that crash, anyway this didn't happen in Sway, there's always something somewhere in the Wayland land |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Mon Jul 05, 2021 11:55 pm Post subject: |
|
|
No you don't need the xdg-desktop. It's being looked at in conjunction with things like pipewire for video broadcasting, ie sharing your desktop, etc.
Just comment it out, like you would in a shell script with #
I did have it installed once upon a time, but I didn't like the way it made things slow on the system.
For config file, at least a relatively good explanation of things.
https://github.com/WayfireWM/wayfire/wiki/Configuration
And there should be a sample one at /usr/share/wayfire/wayfire.ini _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Tue Jul 06, 2021 12:11 am Post subject: |
|
|
I asked about the other one, xdg-desktop-portal is dep of flatpak, so I had that one already installed.
Anyhow, thanks for the Wiki page, yeah it's good, I read that earlier while I was configuring Wayfire, took me awhile to figure out how to restart Wayfire until I realized it does that auto on every change
It doesn't mention xdg-desktop-portal though.
Never mind, who knows why that happened, main thing is that I don't have those gpu resets, those are nasty, Wayfire crashing happened only once on a different matter.
btw I just synced portage, lots of new updates for stable gentoo, mesa, xwayland, libdrm (which required of me to enable radeon use flag)
Getting used to Wayfire slowly, it's not that bad, but still, years of using tiling WM's .... it takes time to adjust
Would be much easier for me if there was workspace support on Waybar, Expo is nice but slower for me, I guess I'll get used to it
Thing is I don't care much for eye candy, I overgrown Compiz years ago
I would pick Sway for sure in Wayland, Wayfire is second best for me and will have to do.
Will not give up on Wayland, not yet.
If Sway was working for me, I wouldn't for sure, I already had xorg completely removed. |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Tue Jul 06, 2021 12:39 am Post subject: |
|
|
I meant the portal, I forgot there was the desktop and the portal. I don't use it, even uninstalled it as I've no interest in whole sharing desktop end of wayland, at least for now. Plus it's all basically experimental at this point, ie lots of breakage
I know that wayfire has some rudimentary tiling, but I haven't used or even read much about it.
As far as effects, I shut most off. I just prefer a stacking WM. *shrugs*
As far as the crash, amd problems, I would imagine that the problem will be fixed sooner or later, since there are so many reports. _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Tue Jul 06, 2021 12:50 am Post subject: |
|
|
It has 'Simple Tile' plugin , and it tiles indeed, but I turned it off.
btw Wayfire should be bumped to 0.7.2 , it's out now for 2 weeks already
Wayland stuff should be maintained regularly IMHO |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Tue Jul 06, 2021 10:19 am Post subject: |
|
|
kajzer wrote: | It has 'Simple Tile' plugin , and it tiles indeed, but I turned it off.
btw Wayfire should be bumped to 0.7.2 , it's out now for 2 weeks already
Wayland stuff should be maintained regularly IMHO |
Indeed.
As I mentioned I run the 9999 versions of "the compositor toolchain".
wayland and wayland-protocols, move slower.
wlroots, changes almos daily and when it changes then anything depending on it changes, which is most compositors except kde and gnome.
ETA2: and for kde, I know that there is some un-official work on kwinft, a faster version than kwin, that is looking at using wlroots.
So I check the github every day or two to see what commits have been done and any potential merges for problems.
https://github.com/swaywm/wlroots/
https://github.com/WayfireWM
https://github.com/Alexays/Waybar
https://gitlab.freedesktop.org/xorg/xserver/-/tree/xwayland-21.1 -- standalone
https://gitlab.freedesktop.org/wayland
https://codeberg.org/dnkl/ -- foot term, fuzzel, etc
Edit to add: 2 other compositors that I follow,
https://github.com/johanmalm/labwc -- openbox style clone (much reduced from the X version, but a WIP) - I have it setup to play with but haven't messed with it lately.
https://hikari.acmelabs.space/ -- bsd based/developed, claims to be a stacking/tiling hybrid. On my system, but I haven't done anything testing yet. _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Tue Jul 06, 2021 11:09 am Post subject: |
|
|
I run 9999 as well (wlroots, wlsunset, mako, wayfire, wf-config) and Sway, but I think I'll remove Sway today, Wayfire is working great.
I just realized that configuring it via config manager is better than editing config manually, had some trouble with keybindings editing it manually, gtk app made that easy.
btw hikari needs a bump as well, plus it doesn't even compile with layershell use flag enabled |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Tue Jul 06, 2021 11:47 am Post subject: |
|
|
kajzer wrote: | I run 9999 as well (wlroots, wlsunset, mako, wayfire, wf-config) and Sway, but I think I'll remove Sway today, Wayfire is working great.
I just realized that configuring it via config manager is better than editing config manually, had some trouble with keybindings editing it manually, gtk app made that easy.
btw hikari needs a bump as well, plus it doesn't even compile with layershell use flag enabled |
I usually keep a copy of the 9999 stuff in my local repo, along with pkgs like hikari, and I just change the version of the ebuild name and do a digest.
New version good to go. all without waiting for the gentoo devs to get around to it, if it's even in the regular repo.
Edit to add: just looked hikari is out of date by about 4 revs in the main gentoo. But I compiled the 2.3.1 version at the end of June, no problem.
The only use flag I didn't enable was the virtual-io.
Should be able to copy hikari-2.2.2-r1.ebuild from gentoo repo to hikari-2.3.1.ebuild in your local repo, without changing anything other than the ebuild name and should compile, any problems holler. After it's in your local then an "ebuild hikari-2.3.1.ebuild digest" should make it good to go.
ETA2: You will need to remove one line if using 2.2.2-r1 as a template
Code: | PATCHES=( "${FILESDIR}"/${PN}-2.2.1-pkgconfig.patch ) |
I removed it when I created a 2.2.2 version a while back and haven't needed it since.
I did have some patches for hikar-2.3.0 but they weren't needed for 2.3.1 _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland
Last edited by Anon-E-moose on Tue Jul 06, 2021 12:18 pm; edited 1 time in total |
|
Back to top |
|
|
CaptainBlood Advocate
Joined: 24 Jan 2010 Posts: 3880
|
Posted: Tue Jul 06, 2021 12:07 pm Post subject: |
|
|
kajzer wrote: | I run 9999 as well (..., wlsunset, ...) | Thks for pointing that app, as I was unaware it exists.
Same 4 another 1 u mentionned elsewhere in the thread, I can't recall the name of (EDIT: hikari).
Thks 4 ur attention, interest & support. _________________ USE="-* ..." in /etc/portage/make.conf here, i.e. a countermeasure to portage implicit braces, belt & diaper paradigm
LT: "I've been doing a passable imitation of the Fontana di Trevi, except my medium is mucus. Sooo much mucus. " |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Tue Jul 06, 2021 1:26 pm Post subject: |
|
|
Yeah, that one should be in the tree, as well as wofi
Biggest problem for me in Wayfire is the lack of workspaces in the bar, if I'm working with the mouse, with browser for example and want to switch to another workspace it was easy to do that with the mouse, sometimes I'm lazy to go for keyboard, problem here was that Waybar doesn't support Wayfire, anyway I got an idea to made a module for Waybar, and on click it would simulate 'Super' key which would give me that expo plugin.
Now, luckily there's a replacement tool for xdetool in Wayland, called wtype, so all that worked great in the end, pretty happy now with Wayfire!
I don't care about Sway anymore, besides I'm pretty sure that gpu reset problem isn't going away anytime soon. |
|
Back to top |
|
|
Anon-E-moose Watchman
Joined: 23 May 2008 Posts: 6152 Location: Dallas area
|
Posted: Tue Jul 06, 2021 1:29 pm Post subject: |
|
|
wtype escaped my wayland radar. Nice.
Just in case someone wants to grab newer ebuilds, my git copy of my local repo is in my sig.
Edit to add: I do like waybar, but I wish they would expand beyond sway.
Though part of it is sway has a nice build in IPC mechanism for sending it commands.
I know that wayfire has been asked by users to implement IPC for wayfire, it's not done yet.
ETA2: re amdgpu locking up problems, there is a patch added to mesa 21.1.4, that is supposed to fix the problem, at least the common problem.
radeonsi: skip instance_count==0 draws on <= GFX9
https://gitlab.freedesktop.org/mesa/mesa/-/commit/9f5576771a712bcf64acb9cc6469345b3a21fa23 _________________ UM780, 6.1 zen kernel, gcc 13, profile 17.0 (custom bare multilib), openrc, wayland |
|
Back to top |
|
|
The Main Man Veteran
Joined: 27 Nov 2014 Posts: 1171 Location: /run/user/1000
|
Posted: Tue Jul 06, 2021 6:45 pm Post subject: |
|
|
Thanks for the patch info, I'll try that later
It happened in Wayfire as well unfortunately , it took way longer though, I guess it doesn't like wlroot, because seriously that never happened in X, but I realized just now that I have amdgpu built in kernel, that requires specifying all the blobs in it, so when I downgraded linux-firmware I didn't build the kernel again, so I guess that's why downgrading didn't help in my case.
What I did just now is compiled amdgpu as a module, with downgraded linux-firmare to the oldest possible (20201218) and I will try with that. |
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|