<hunter0one>
Im using labwc and some of my stuff works fine like xfe and brave browser, but neither xterm nor alacritty will open
<hunter0one>
fresh install and after updating ports and running sysup
<hunter0one>
xterm seems like it tries to open but it doesnt
hunter0one has quit [Remote host closed the connection]
tilman has quit [Ping timeout: 260 seconds]
tilman has joined #crux
lavaball has joined #crux
<cruxbot>
[opt/3.8]: graphviz: updated to version 13.1.0
<cruxbot>
[opt/3.8]: fontconfig: updated to version 2.17.1
ivandi has joined #crux
<braewoods_>
hunter0ne: xterm is X11 only. do you have xwayland functioning?
hunter0one has joined #crux
<hunter0one>
braewoods_: Yes, thats why I tried xterm as a fallback since alacritty wasnt working either. Xfe is also X11 only, unless the FOX toolkit supports Wayland now (I dont think so) but it works.
<braewoods_>
They're both terminals so I wonder if's there something strange going on with PTYs then.
<braewoods_>
Anyway without a log there's not much to go on.
<hunter0one>
I also had another issue I dont remember having in 3.7 where GRUB insists on using /dev/sd* as the root device and it picks the wrong device so the kernel loads but has nothing to initialize. Ive set GRUB_DISABLE_UUID to false, set the default GRUB UUID to the root device, and my fstab uses UUIDs.
<hunter0one>
braewoods_: Yeah its unfortunate without a terminal to actually have a way to generate logs. Im about to get on to see what I can do again.
<braewoods_>
you still have the virtual consoles.
<hunter0one>
Yes but Im not sure how Im supposed to get the logs for either, especially xterm which will run through Xwayland. I set the alacritty menu entry to run alacritty -vvv --print-events | tee alacritty.log but nothing generates.
<hunter0one>
I thought maybe devpts wasnt mounted but it is and just mounted with the defaults that the fstab came with in the install
<cruxbridge>
<tim> hunter0one: you are running a wayland session? Maybe give foot a try and see if that works for you
<hunter0one>
xterm -l -lf ~/xterm.log didnt do anything either
<hunter0one>
tim: will try
<cruxbridge>
<tim> foot is wayland native, no x11 support
<cruxbridge>
<tim> also maybe you need to enable xwayland with labwc?
<hunter0one>
Foot works
<cruxbridge>
<tim> best terminal emulator out there :D
<hunter0one>
Maybe xwayland isnt enabled after all... I thought xfe (a file manager written in FOX toolkit) was X11 only to make me think otherwise lol
<hunter0one>
My port of labwc had to use git to get wlroots 0.18 since 0.19 is the one in the repo, I believe they had released the last version of labwc moments before the next wlroots came out
<hunter0one>
Actually xwayland is in fact enabled
<cruxbridge>
<tim> is your wlroots built with xwayland support as well?
<hunter0one>
All I can think of is theres no permission to access to the x socket
<hunter0one>
tim: Good catch
<hunter0one>
Is there a way to see what it was built with?
<cruxbridge>
<tim> you need to check the path but this is the file it creates if it got xwayland support
<hunter0one>
I was here a few months ago asking y'all about greetd as I was trying to improve Wayland support for PCLOS. I was a packager for that distro and here I am :D
<hunter0one>
tim: It does exist, except its in wlr/xwayland/
<cruxbridge>
<tim> i remember, yeah
<cruxbridge>
<tim> then i suppose your wlroots version was compiled with xwayland support
<cruxbridge>
<tim> with foot working though, you can try and start alacritty or xterm and see whats the reported problem is, if any
<hunter0one>
let me switch to an actual IRC client and not on my phone
hunter0one has quit [Remote host closed the connection]
<remiliascarlet>
cruxbridge: Any chance you're going to put XLibre in core, now that that's the actively maintained fork of Xorg?
<pitillo>
remiliascarlet: do you mean in xorg collection instead of core?
<remiliascarlet>
That works too.
<pitillo>
too or better? I mean, if it's a Xorg fork, it should be in xorg repo, not in core... or were you asking to be in core?
<remiliascarlet>
Whatever works. The point is whether it'll be adapted at all or not. Or whether CRUX goes full Red Hat with blue hair and castration, and dumps Xorg for Wayland instead.
<pitillo>
couldn't they (Xorg/XLibre and wayland) live together? or are they excluding?
<remiliascarlet>
Of course they can live together.
<remiliascarlet>
The thing is, when Xorg got forked into XLibre, a number of distro's at the same time "independently" decided to dump Xorg altogether, and go Wayland-only.
<remiliascarlet>
And it's not only distro's, Gnome and KDE both did that too, also at the same time.
<remiliascarlet>
However, distro's in support of XLibre and those not taking a stance either way (for now) still support both.
<remiliascarlet>
So all I wanted to know is what CRUX will do. Aka, adapt XLibre while also keeping Wayland, dump Xorg and use Wayland only, or keep things as they currently are.
<pitillo>
so may be it's a question of time and resources, I mean, if there are enough ports maintainers who have interest in Xorg/XLibre, they could be kept together with wayland
<pitillo>
I hope we can mantain Xorg/Xlibre with wayland, but at the end, that's a maintainer's responsibility and they are who must take that decission
<pitillo>
if I remember right, some time ago there was a movement from XF86 to Xorg... and we survived, we were adapted and new options raised... so it's a matter of time probably to get an answer/decission
<remiliascarlet>
I see.
hunter0one has joined #crux
<hunter0one>
Have to use my phone again because irssi gives me "Could not verify TLS servers certificate: unable to get local issuer certificate". I tried setting capath to /etc/ssl/certs and /etc/ssl/cert.pem but neither work
<hunter0one>
ca-certificates is installed
<remiliascarlet>
Try Weechat. That's what I'm using, and never have this problem.
<cruxbridge>
<pitillo (@pitillo:crux.nu)> Is your date setup in that computer?
hunter0one has quit [Remote host closed the connection]
hunter has joined #crux
<hunter>
that worked
<hunter>
i wonder why irssi doesnt work :(
<hunter>
Anyway, finally making some small progress lol
<hunter>
Alacritty gives me "Error: Error { raw_code: None, raw_os_message: None, kind: NotSupported("provided display handle is not supported") }"
<hunter>
I also just build qt5 and keepassxc and it wont open because it says "qt.wpa.wayland: EGL not available"
<hunter>
Things should build with wayland, i have xorg-xwayland installed, wayland-protocols, wayland, etc.
<hunter>
I can confirm now that xfe is indeed using xorg, when you run xwininfo it will only turn into a plus sign and be able to click on x11 windows
hunter has quit [Ping timeout: 265 seconds]
SiFuh_ has quit [Remote host closed the connection]
SiFuh_ has joined #crux
hunter0one has joined #crux
<hunter0one>
pitillo: Yes, the date is accurate
<hunter0one>
I managed to fix all but xterm, alacritty and some other things werent working because I didnt have glslang installed when I built mesa and that turned off AMD support
hunter0one has quit [Remote host closed the connection]
_whitelogger has joined #crux
deltahotel has joined #crux
deltahotel has quit [Client Quit]
lavaball has quit [Remote host closed the connection]