jaeger changed the topic of #crux to: CRUX 3.6 | Homepage: https://crux.nu/ | Ports: https://crux.nu/portdb/ https://crux.ninja/portdb/ | Logs: https://libera.irclog.whitequark.org/crux/
<elderK> What's the deal with wayland these days anyway?
<elderK> I've heard a lot about it but know very little.
<elderK> From what I understand, it requires changing pretty much everything.
<elderK> Happy with i3? Well, you're stuck on X11.
<elderK> Like, are there any actual benefits of using Wayland at this point?
<elderK> I can see a purpose if it like, you know, noticeably increases graphics performance or something...
<elderK> Pipewire doesn't seem to suffer the issues that Pulse was, so that is a change worth making.
ocb has quit [Remote host closed the connection]
ocb has joined #crux
ocb has quit [Remote host closed the connection]
ocb has joined #crux
<brian|lfs> whats gtk+-wayland-3.0
<brian|lfs> don't see a port for it
<brian|lfs> firefox 102 is looking for it
<jaeger> Probably just need to rebuild gtk3 after installing wayland, I'd guess
<elderK> :P No more info on why you'd want to use Wayland?
ocb has quit [Remote host closed the connection]
<brian|lfs> thanks compiling now
ocb has joined #crux
<brian|lfs> I dohn't want to use wayland firefox was reuquiring it to build
<brian|lfs> I looked on google didn't see a switch to disable it
<elderK> I wonder why Firefox requires wayland to build. That's kind of meh.
<elderK> Some Vulkan tests require Wayland, too.
<brian|lfs> I imagine that everythign will requrie wayland eventally I read GTK 5 amybe only support wayland
<brian|lfs> ya compiled and ins talled
<brian|lfs> firefox-bin took forever to open compiling it seems to be much faster response
ocb has quit [Ping timeout: 268 seconds]
ocb has joined #crux
brian|lfs has quit [Quit: Leaving]
brian|lfs has joined #crux
<brian|lfs> brian@crux:/usr/ports/local/linux$ sudo pkgmk -d -um
<brian|lfs> =======> ERROR: File '.md5sum' is not writable.
<brian|lfs> wtf I'm confsued
<brian|lfs> pkgmkg and prt-get started acting up after install firefox
<jaeger> elderK: I don't know enough about it to say
<jaeger> As for your comment about i3 and x11, sway is a very similar experience to i3 for wayland
<brian|lfs> =======> ERROR: File '.md5sum' is not writable.
<brian|lfs> not sure wtf I broke lol
<jaeger> That error comes from the check_file function in pkgmk... maybe run it through strace to see what's up
_moth_ has quit [Ping timeout: 252 seconds]
<jaeger> odd that you wouldn't be able to write .md5sum with sudo
<brian|lfs> or files for that matter
<brian|lfs> to compile packages
<jaeger> What does your pkgmk.conf look like?
<brian|lfs> sorry was looking at things
<jaeger> Nothing stands out there
<brian|lfs> ya I know thats the rejected file from upgraing CRUX
<brian|lfs> even though I didn't see nothing wrong with my pkgmk.conf file I repalced the pkgmk.conf file
<brian|lfs> should I mount the crux 3.7 iso and reisntall pkgutils
<jaeger> What about the permissions in /usr/ports/local/linux? Can you write to .md5sum or other files there outside of pkgmk?
<brian|lfs> yes tried that
<brian|lfs> and it seems to be all ports folder I pkgmk can't write to doesnt' matter the folder
<jaeger> Hrmm, sorry, don't know without more info about what's different from the default setup... sounds very strange
<brian|lfs> ya it started aftter installing firefox its weird
<brian|lfs> sudo mount crux-3.6-updated.iso /mnt/crux/
<brian|lfs> mount: /mnt/crux/: mount failed: Operation not permitted.
<brian|lfs> do I need DOSFSTOOLS or something
<jaeger> you need loopback support
<jaeger> if you have it built into the kernel as a module, maybe as simple as 'modprobe loop'
<jaeger> I would be surprised if building firefox was actually the cause, that would be extremely funky
<brian|lfs> thanks ya I've been playing with a custom kernel
<brian|lfs> so using an initrd and stuff
<brian|lfs> oh I don't think it was the cause just thats when stuff was still working
<jaeger> If you copy a port to another location can you update or recreate its md5sum as root?
<brian|lfs> I'll try that in a second jsut reinstall pkgutils
<brian|lfs> now that I was able to mount an iso
<brian|lfs> odd reinstalling pkgutils fixed pkgmk
<jaeger> Had you altered pkgmk at all?
<brian|lfs> yes I had turned off all my opitzation to get firefox to compile
<jaeger> I mean pkgmk itself, not just pkgmk.conf
<brian|lfs> I had a ton of optomzation falgs before
<brian|lfs> no didn't touch pkgmk
<jaeger> Hrmm... maybe those optimization flags broke pkgmk
<jaeger> somehow
<brian|lfs> but looked at it after it started erroring out but didn't see anything wrong
<jaeger> Not sure how that could be, though, since it's a shell script
<jaeger> Unless bash was somehow broken, heh... but that's off in the weeds
<brian|lfs> ya lol
<brian|lfs> I'll paste my modified pkgmk.conf I was using when stuff went nuts
<brian|lfs> lot of flags https://pastebin.com/A3VMn1H1
<jaeger> wow, heh
<brian|lfs> ya gentoo has a program you can run and it wil tell you everything your processor supports
<jaeger> And have you seen any tangible benefit from enabling all that?
<brian|lfs> hoestly not sure
<brian|lfs> so leaving it off for now
<jaeger> Probably hard to test outside of synthetic benchmarks
<brian|lfs> I"m using that guys kernel prot he made
<brian|lfs> port
<brian|lfs> just changed the name to CRUX Linux 3.7 instead of Vernom Linux
<brian|lfs> I really think CRUX should have a kernel compiled as a port that people can use that works on 99.9% of hardware
<brian|lfs> I also wasn't using a pkgmk user before so who knows what happened
<brian|lfs> after all that I'm using a pkgmk user now
<jaeger> I use my own user for it
<brian|lfs> ah ok that works also
<brian|lfs> I imagine if I reinstall the nvidia driver now it will try building for the kernel I"m running not the one I just installed
<brian|lfs> probably need to reboot first
brian|lfs has quit [Quit: Leaving]
<cruxbot> [contrib.git/3.6]: python3-zipp: updated to version 3.8.1
<cruxbot> [contrib.git/3.6]: python3-jsonschema: updated to version 4.7.2
brian|lfs has joined #crux
<brian|lfs> wooops it never made a new initrd image
ppetrov^ has joined #crux
elderK has quit [Quit: Connection closed for inactivity]
guido_rokepo has joined #crux
ty3r0x has joined #crux
_moth_ has joined #crux
ppetrov^ has quit [Quit: Leaving]
guido_rokepo has quit [Ping timeout: 245 seconds]
ocb has quit [Remote host closed the connection]
guido_rokepo has joined #crux
ocb has joined #crux
groovy2shoes has quit [Ping timeout: 244 seconds]
_moth_ has quit [Remote host closed the connection]
_moth_ has joined #crux
groovy2shoes has joined #crux
ppetrov^ has joined #crux
ocb has quit [Remote host closed the connection]
ocb_ has joined #crux
ocb_ is now known as monero
monero is now known as ocb
guido_rokepo has quit [Quit: guido_rokepo]
ocb has quit [Remote host closed the connection]
ocb has joined #crux
seer has quit [Quit: quit]
seer has joined #crux
_moth_ has quit [Quit: _moth_]
_moth_ has joined #crux
ty3r0x has quit [Quit: Konversation terminated!]
<cruxbot> [compat-32.git/3.6]: xorg-xcb-proto-32: updated to version 1.15.2
<cruxbot> [compat-32.git/3.6]: xorg-libx11-32: updated to version 1.8.1
<cruxbot> [compat-32.git/3.6]: wayland-32: updated to version 1.21.0
<cruxbot> [compat-32.git/3.6]: vulkan-validation-layers-32: updated to version 1.3.216.0
<cruxbot> [compat-32.git/3.6]: vulkan-tools-32: updated to version 1.3.216.0
<cruxbot> [compat-32.git/3.6]: vulkan-loader-32: updated to version 1.3.216.0
<cruxbot> [compat-32.git/3.6]: vkd3d-32: updated to version 1.4
<cruxbot> [compat-32.git/3.6]: sqlite3-32: updated to version 3.39.2
<cruxbot> [compat-32.git/3.6]: speexdsp-32: updated to version 1.2.1
<cruxbot> [compat-32.git/3.6]: pulseaudio-32: updated to version 16.1
<cruxbot> [compat-32.git/3.6]: pipewire-32: updated to version 0.3.56
<cruxbot> [compat-32.git/3.6]: pango-32: updated to version 1.50.8
<cruxbot> [compat-32.git/3.6]: openssl-32: updated to version 1.1.1q
<cruxbot> [compat-32.git/3.6]: openldap-32: updated to version 2.6.3
<cruxbot> [compat-32.git/3.6]: openal-32: updated to version 1.22.2
<cruxbot> [compat-32.git/3.6]: nss-32: updated to version 3.81
<cruxbot> [compat-32.git/3.6]: nspr-32: updated to version 4.34
<cruxbot> [compat-32.git/3.6]: nettle-32: updated to version 3.8
<cruxbot> [compat-32.git/3.6]: cups-32: updated to version 2.4.2
<cruxbot> [compat-32.git/3.6]: alsa-plugins-32: updated to version 1.2.7.1
ocb has quit [Remote host closed the connection]
ocb has joined #crux
groovy3shoes has joined #crux
groovy2shoes has quit [Read error: Connection reset by peer]
_moth_ has quit [Quit: _moth_]
_moth_ has joined #crux
_moth_ has quit [Remote host closed the connection]
_moth_ has joined #crux
elderK has joined #crux
<elderK> Hey guys, I was wondering if any of you use a display manager like lightDM or SLIM.
<elderK> If so, why.
<elderK> I usually just login and issue startx.
<elderK> I have a weird monitor setup that differs so I'm concerned about the monitors being correctly set up.
<elderK> I use autorandr to manage that but I'm unsure how it will interact with a display manager.
<jaeger> I use slim in some cases just because it's simple... but it doesn't play well with some pam stuff like setting up nofile limits for wine esync
<jaeger> The login manager shouldn't mess with your display setup, I'd imagine
<jaeger> Maybe a display manager would but not the login manager if it's being nice
<elderK> What's the difference between a login manager and display manager?
<elderK> From what I understand, they are the same?
<elderK> I used Slim a long time ago - I heard that it is no longer maintained?
<jaeger> Maybe just a terminology thing... I was thinking of desktop environments' tools for managing displays... I get what you're talking about, though
<jaeger> Not sure if it's maintained but it generally still works
ocb has quit [Ping timeout: 268 seconds]
<elderK> I do like that it is relatively simple.
<elderK> Everything else seems to do a bunch of stuff I don't care about.
<elderK> Or require a bunch of other stuff.
<elderK> I could just use XDM :P
<jaeger> probably :)
<elderK> I don't really need anything super fancy.
<elderK> One thing that is a concern though, is that I have a lot of custom stuff for my .bashrc / .bash_login.
<elderK> It works a lot like /etc/rc.d and /etc/rc.conf in a way.
<elderK> So, I'll have to make sure the proper scripts are run and stuff when the DM starts my X11 session or whatever.
<elderK> For now, it seems like more effort than it is worth.
<jaeger> If you're happy with logging in and running startx, might as well stick with that
<jaeger> You could even make it automatic if you felt like it
<elderK> Aye, I could: bash_profile could just invoke startx
<elderK> Iono. I like the freedom of being able to stay in the terminal if I need to.
<jaeger> Yeah, and you can add an auto setting in inittab for a user if you want to
<jaeger> I use that for my HTPC to start up kodi automatically from power on
<elderK> Interesting - would that bypass login?
<jaeger> yes
<elderK> That's neat but I will keep the login. :)
<jaeger> Obviously not something you'd want on a public system
ocb has joined #crux
ppetrov^ has quit [Quit: Leaving]
<farkuhar> elderK: you could consider moving some of the custom stuff from .bashrc / .bash_login to a separate script, which gets sourced whether you authenticate with xdm/slim or the usual tty login. That way you're not duplicating all the custom stuff across multiple files.
ocb has quit [Remote host closed the connection]
ocb has joined #crux
<farkuhar> I wish I could give you a more compelling reason to try Wayland, apart from what brian|lfs said about everything eventually requiring it. Wayland is advertised as having a much simpler architecture than X11, but the end user experience depends so greatly on your choice of compositor / window manager that you can hardly perceive the effect of low-level design decisions.
<farkuhar> For instance, just by switching between sway and cagebreak as my wayland compositor, I can trigger a bug that introduces a noticeable delay in processing keyboard/mouse events, but only in firefox. You'll find such lack of polish in a number of bare-bones wayland compositors, but those that come from a major desktop environment like GNOME or KDE Plasma will generally offer the same polished experience you get in X11.
<cruxbot> [contrib.git/3.6]: python3-jsonschema: updated to version 4.8.0
<jaeger> My experience with wayland so far has been that it MOSTLY works just fine. Sometimes copy/paste between wayland and xwayland stuff is weird but not enough to ruin it, in my opinion
<jaeger> I like KDE plasma pretty well, though haven't tried to build/run it on crux yet.
<jaeger> I also have not yet investigated if MATE and wayland play nicely, that's on my list after 3.7 is ready
<jaeger> MATE 1.26 has "initial wayland support" but I haven't dug into what that means
<cruxbot> [opt.git/3.6]: thunderbird-bin: updated to version 102.1.0
<farkuhar> I'm keeping an eye out for FLTK 1.4 to lose its "active development" status and become the stable branch. That's the branch where all wayland support is being implemented.
<jaeger> nice
_moth_ has quit [Remote host closed the connection]
_moth_ has joined #crux
<elderK> I'll move to Wayland whenever i3 moves to it :P
<elderK> Or, when it becomes truly necessary.
tilman has quit [Ping timeout: 245 seconds]
tilman has joined #crux