| gnarface | hyrcanus: a quick glance at the urxvt manpage suggests maybe you just have the format of that -fn option wrong, it might need a prefix to tell it what font type like x: or xft: ... otf: ? not sure. not sure about viznut either but the people who made terminology hang out in #e on this irc network | 00:07 |
|---|---|---|
| gnarface | hyrcanus: if you tell them about the rendering issues in panfrost they might actually care | 00:08 |
| hyrcanus | i just tried eepin-terminal gnome-terminal kitty lxterminal mate-terminal sakura termit terminology | 00:08 |
| gnarface | hyrcanus: just out of curiosity though, did you try terminology only in X or have you also tried it on a bare framebuffer? | 00:09 |
| hyrcanus | terminology is the only one with the rendering error under panfrost, but other programs also cause it | 00:09 |
| hyrcanus | x | 00:09 |
| gnarface | it might behave better on a bare framebuffer | 00:09 |
| hyrcanus | doom3 also has the issue | 00:09 |
| gnarface | hmm, interesting... that might be a clue | 00:09 |
| hyrcanus | it's just a couple people developing the drivers. i shouldn't complain | 00:09 |
| hyrcanus | they have enough to work on | 00:10 |
| hyrcanus | but i am curious if some people in #e know about the rendering | 00:10 |
| gnarface | well, a good screenshot of both programs glitching out might actually narrow down which function call is misbehaved in panfrost, and i have a feeling raster might actually be interested in panfrost compatibility | 00:10 |
| gnarface | but you should test it outside of X too just to help narrow down the target surface3 | 00:11 |
| gnarface | surface* | 00:11 |
| gnarface | (... since the panfrost issue you see could actually be an issue in X or in mesa at this point) | 00:12 |
| gnarface | the overlap of doom3 and [everything else open source] is gonna be fairly narrow | 00:13 |
| gnarface | so that could be very good evidence | 00:13 |
| gnarface | i can't guarantee they're gonna help or even care, but i can promise they're more likely to help instead of pretending not to care if you bring good evidence | 00:13 |
| hyrcanus | it's kind of neat in a way. one wonders and marvels | 00:16 |
| hyrcanus | http://0x0.st/-dGR.png | 00:16 |
| gnarface | just fyi i haven't looked at a single link you've posted other than the paste.debian.net ones | 00:17 |
| gnarface | i'll look at the image if you post it to imgur | 00:18 |
| gnarface | i don't really like adding new domains to mental list of trusted domains, it's nothing personal | 00:18 |
| gnarface | (and no i don't really trust imgur or debian.org either, it's more about lowering attack surface) | 00:19 |
| hyrcanus | i get it. it is only interesting to arm gpu nerds at most | 00:19 |
| hyrcanus | 0x0 is run by lachs0r who comes from the nokia/maemo community | 00:19 |
| gnarface | well, that's why i think they'll care about it in #e, or at least i think raster will care | 00:20 |
| hyrcanus | oh if raster is there he might be interested | 00:20 |
| gnarface | they're slow over there too, just be patient | 00:21 |
| hyrcanus | i have to nap a bit then get back to gimp bughunting | 00:22 |
| hyrcanus | nice chatting | 00:22 |
| fluffywolf | doing a chimaera upgrade... apt-get dist-upgrade wants to remove excessive packages. any suggestions for where I should start poking at it? | 03:04 |
| fluffywolf | freecad, wicd, php, gcc,... lol | 03:05 |
| fluffywolf | looks like the problem is python, as fucking always. | 03:05 |
| fluffywolf | why oh why can't python just fucking die? | 03:06 |
| fluffywolf | lol, trying to upgrade freecad separately tries removing a full screenful of packages... | 03:07 |
| fluffywolf | aptitude also makes it clear the problem is python, but doesn't seem able to figure out how to fix it either. | 03:09 |
| fluffywolf | why is it that every single god damn time I upgrade anything python is always a fucking nightmare? why do people keep writing software in any language that the devs completely break every single fucking version bump? | 03:11 |
| fluffywolf | irqbalance wants you to configure it with systemd | 03:24 |
| * fluffywolf is updating things that don't cause breakage so there's less noise when trying to troubleshoot the breakage | 03:26 | |
| fluffywolf | now I'm hitting libelogind0 : Conflicts: libsystemd0:i386 | 03:35 |
| fluffywolf | too | 03:35 |
| fluffywolf | and trying to remove that causes breakage... | 03:36 |
| fluffywolf | upgrading to chimaera with i386 packages installed too was tested at least once, right? heh | 03:39 |
| fluffywolf | that last one seems like a devuan-specific breakage | 03:40 |
| barrett9h | hi | 03:41 |
| fluffywolf | aptitude's solutions all involve uninstalling wine | 03:41 |
| barrett9h | I upgrade from beowulf to chimaera (which I rarelly do, I usually just save the relevant /etc files, reformat and reinstall), and now the sound is acting strange. | 03:42 |
| barrett9h | Sometimes it doesn't work at all, and when it works it's distorted. | 03:43 |
| fluffywolf | grrrr, this all started because I wanted to install one newer package, and now I'm wasting all night fucking with dependency idiocy! | 03:47 |
| barrett9h | I feel your pain. Dependency hell is.... well, hell. | 03:55 |
| barrett9h | It was more common in the past, but I feel a little sad to se that it's still not solved. | 03:56 |
| * fluffywolf starts getting frustrated. upgrades should not be this broken. | 04:35 | |
| fluffywolf | I'm beginning to think I should have waited longer before upgrading to chimaera. | 04:35 |
| lfluffywof | grrrr. and now somehow I killed sound. | 04:53 |
| rwp | fluffywolf is motivating me to test the upgrades on a victim desktop system before doing my main desktop system. | 06:44 |
| fluffywolf | I was able to make the upgrade work by repeatedly switching between upgrade and dist-upgrade, letting it remove wine32, specifically upgrading a few things with their dependencies, more upgrade and dist-upgrade switching, and finally reinstalling wine32. | 06:48 |
| fluffywolf | it was definitely not a smooth upgrade, but I seem to have a working, upgraded box now. | 06:49 |
| error144 | Hello! Could someone help me using devuan-installer-iso? | 08:09 |
| error144 | I get this error: [kernel.mk:18:/build/amd64/netinstall/boot/isolinux/initrd.gz] Error 1 | 08:10 |
| error144 | What I am trying to do is to make an Iso file out of my custom distro for installing | 08:14 |
| rrq | might be possible; the only build method currently in uses is "./build-sudo.sh" with 1, 2 or 3 arguments | 08:16 |
| error144 | what are these arguements? | 08:18 |
| onefang | Isn't that the sort of thing Refracta is good for? And did I spell it right? | 08:22 |
| rrq | the first is suite to build for, which also defines the debootstrap suite that is set up for building the iso "in" | 08:23 |
| rrq | the second is the iso choice; either one of them ar "all" | 08:23 |
| rrq | the third is the distribution version code, which gets stamped into the iso in some places | 08:24 |
| error144 | rrq thank you for explaining, I just want to know one last thing: how to get the .fs file? | 08:25 |
| rrq | that's the file system tree set up by debootstrap; which becomes the chroot in which the iso gets built | 08:27 |
| rrq | gets named as $SUITE.fs | 08:27 |
| error144 | ohh yah, I understand now, THANK YOU SOOOOO MUCH <3 | 08:28 |
| trmin | Back to the monitor / keyboard / mouse freeze. Probably it was a xorg crash. Seems to be fixed by disabling xscreensaver & dpms via xset. Computer ran overnight for about 13 hrs. | 09:14 |
| buZz | xscreensaver has a ton of screensavers that could be called cpu killers | 09:15 |
| buZz | trmin: is this by chance one of those portable computers with the poor cooling? | 09:16 |
| trmin | No, it's a cool one (desktop). | 09:17 |
| buZz | ah well, maybe you could analyze logs? | 09:19 |
| buZz | a light replacement for 'xscreensaver' that i like , is 'slock' by suckless | 09:19 |
| buZz | zero fancy bouncing things, just a plain and simple screenlocker | 09:20 |
| GyrosGeier | I can recommend xtrlock | 09:22 |
| GyrosGeier | that just grabs all input devices and changed the mouse pointer to a lock symbol | 09:23 |
| trmin | I'm not using any screensaver. It was just installed. It also was no question but an update to the discussion 2 days ago. | 09:23 |
| GyrosGeier | and optionally blanks | 09:23 |
| buZz | GyrosGeier: cute, never heard of | 09:23 |
| buZz | i'll stick to slock though :P | 09:24 |
| trmin | Bye. | 09:24 |
| buZz | ciao | 09:25 |
| buZz | 'xscreensaver is crashing my system' , sounds still unfixed | 09:26 |
| buZz | i'd bet they're just running nouveau on some barely supported nvidia card :P | 09:26 |
| error144 | Hello again, I have been trying to make devuan-installer-iso work using build-sudo.sh, but for some unkown reason (possibly a bug) It gives two errors: | 09:32 |
| error144 | runbuild:16 make: commend not found | 09:32 |
| error144 | and if I run the commend manually it returns:[kernel.mk:18:/build/amd64/netinstall/boot/isolinux/initrd.gz] Error 1 | 09:33 |
| error144 | is this a bug or I am doing something wrong? | 09:33 |
| buZz | or both ;) | 09:38 |
| error144 | buZz :( | 09:39 |
| error144 | --help | 09:41 |
| error144 | there is nothing worst then having a problem that can't be found on the internet | 09:57 |
| rrq | which suite are you building for? | 09:59 |
| error144 | I didn't put any arguments, (defualt) | 10:00 |
| error144 | adding arguments cause more problems, and I only want to make it work for now. | 10:01 |
| rrq | ok. which suite are you running ./build-sudo.sh on? | 10:01 |
| error144 | you mean which devuan? then it is chimaera | 10:02 |
| error144 | customized with window manager, minimal. | 10:03 |
| rrq | ok. I guess you did set the daedalus link for debootstrap? | 10:03 |
| error144 | I didn't set anything, it is all defualt. | 10:04 |
| gour | morning | 10:04 |
| error144 | gour welcome | 10:05 |
| gour | both appimage & *.deb version of viber crash on my devaun/ceres install. any hint? | 10:05 |
| error144 | gour what past the errors you are getting | 10:06 |
| gour | i simply need it as well as ability to have speakers as my default sound device...those two are main obstacles to migrate from devuan | 10:06 |
| gour | just "Aborted" | 10:06 |
| gour | trying now with flatpak version which i'd like to avoid... | 10:06 |
| error144 | rrq sorry, I mistakenly closed the hex chat, I said I didn't customize anything, it is all default. | 10:08 |
| gour | after i try flatpak will try *.deb under gdb if it is goingto reveal something... | 10:09 |
| error144 | gour flatpak will sure work, even tho Is not the best way to install something | 10:09 |
| gour | error144: when i was playing with debian before, viber was working via *.deb package, but i had the problem that every time i launched it it went through 'setup' procedure which was really cumbersome :sad: | 10:11 |
| error144 | gour are you installing the .deb file? | 10:11 |
| rrq | error144: just checking that you use the current git software, the master branch. | 10:23 |
| error144 | rrd yes I did | 10:23 |
| rrq | the default operation is to set up an iso-building chroot for daedalus, populate with all required packages, and then build | 10:24 |
| rrq | that's what the script does | 10:24 |
| rrq | you might try with arguments "chimaera netinstall 4.0" to see if thatworks | 10:25 |
| error144 | ok let me try your idea first | 10:27 |
| error144 | rrq no success, return this weird error: | 10:33 |
| error144 | make build ISO=netinstall DISTNAME=chimaera DISTVERSION=4.0 | 10:33 |
| error144 | ./runbuild.sh: line ##: make: command not found | 10:33 |
| error144 | note: ## is not the defualt one as I tried to see what goes wrong inside the script | 10:34 |
| error144 | it seems to work fine if you run it menually, but throw the script, it just doesn't work? | 10:34 |
| error144 | thought* | 10:34 |
| rrq | you do have sudo installed? | 10:35 |
| error144 | I am in root account | 10:36 |
| error144 | no sudo needed | 10:36 |
| error144 | rrq . | 10:37 |
| rrq | well build-sudo.sh uses the command "sudo" | 10:38 |
| error144 | rrq that shouldn't break it? ok let me try with user account then. | 10:39 |
| rrq | it m ight work running as root if you remove all those sudo words | 10:39 |
| rrq | yes it breaks the script | 10:39 |
| rrq | because those commands fail | 10:39 |
| rrq | but if your remove all sude from the script, then it might work for root | 10:40 |
| error144 | rrq weird, if it works, then I will try removing all sudos. | 10:41 |
| error144 | and try it with root to see | 10:41 |
| error144 | rrq no luck, same error | 10:44 |
| error144 | oh wait | 10:44 |
| gour | error144: i tried flatpak - it does work, but same problem of relaunching setup procedure after restart. tried with *.deb again and here is what i got under gdb: https://paste.debian.net/1216907 | 10:44 |
| error144 | rrq let me try with your arguements | 10:45 |
| gour | the same version does work under debian/sid on my main desktop machine, so wonder if migraion to devuan is posible at this point of time | 10:45 |
| error144 | gour that error made me wonder if viber needs systemd | 10:46 |
| error144 | gour have you ever get it to work before? | 10:47 |
| gour | error144: not under devuan. so flatpak version can embed it? | 10:47 |
| gour | actually it worked, but was always relaunching setup, but now it simply crashes | 10:48 |
| error144 | gour tell me what's your setup? | 10:48 |
| gour | devuan/ceres/runit | 10:49 |
| error144 | gour did you use runit knowing how it works? | 10:50 |
| error144 | rrq same error, seems like both make commends inside runbuild.sh are not found? | 10:50 |
| gour | error144: i used it in the past when running voidlinux for some time | 10:50 |
| error144 | gour ok, I will try running viber on my end using devuan sysv | 10:51 |
| gour | error144: thanks a lot! | 10:53 |
| rrq | error144: very peculiar since the debootstrap should populate the building chroot will everything required ... I'll need to spin up a pristine system to see if I can replicate this problem. | 10:55 |
| rrq | you do have rsync installed? | 10:56 |
| error144 | rrq yes | 10:57 |
| error144 | gour do you have xss and pulse installed? | 10:57 |
| gour | error144: i've pulse, what do you mean by 'xss' ? | 11:00 |
| error144 | gour all pkgs that start xss | 11:01 |
| error144 | just go apt-get install xss* | 11:02 |
| rrq | error144: you do have dpkg-dev installed? | 11:06 |
| gour | error144: i did and same problem | 11:06 |
| error144 | rrq yes | 11:06 |
| error144 | gour ok how about xdg? | 11:06 |
| error144 | gour sorry for not filtering what pkgs do you need or don't, I am using a test VM, there for I just go apt-get install xdg* | 11:07 |
| gour | error144: and it does work for you? | 11:11 |
| error144 | gour It says: | 11:12 |
| error144 | No protocol specified | 11:12 |
| error144 | Aborted | 11:12 |
| error144 | so lets see what is this protocol? | 11:12 |
| error144 | gour I managed to make it work, here are the steps: | 11:17 |
| rrq | error144: no luck with replicating your problem :( | 11:17 |
| error144 | su | 11:17 |
| error144 | xhost + | 11:17 |
| error144 | su user | 11:17 |
| error144 | ./viber.ImageApp | 11:17 |
| error144 | ./viber.AppImage (what a mistake) | 11:17 |
| gour | error144: hmm...let me explore it here... | 11:18 |
| error144 | rrq I guess I am alone at this fight, It seems weird to me that adding an ainstaller to you custom distro is hard, giving the fact there are so many distors outthere | 11:18 |
| error144 | gour did it work? | 11:20 |
| error144 | gour this is a link in case you didn't know what to do: https://www.youtube.com/watch?v=ue7D6K9cFys | 11:26 |
| hyrcanus | when people build a thing, it's not possible to cover all use-cases | 11:54 |
| error144 | gour any news | 12:23 |
| gour | error144: it didn't work...installing debian on my netbook now... | 12:39 |
| error144 | gour why did you surrendered too quickly? :( | 12:40 |
| error144 | anyway, I guess that fixes your problem | 12:40 |
| gour | error144: well, i simply do not have so enough time to spend on such trivialites...these days...and want to be sure it whether it does work on the same hardware | 12:41 |
| error144 | gour I understand, well, good luck! | 12:42 |
| gour | error144: thank you for your assistance. i'll report back 😉 | 12:43 |
| error144 | gour sure | 12:43 |
| error144 | rrq hey again, remember that first error, I managed to fix it, what I did was I made each step of the commend in a line by itself. | 12:57 |
| error144 | now the only problem left is this: | 12:57 |
| error144 | [kernel.mk:18: build/amd64/netinstall/boot/isolinux/initrd.gz] Error 1 | 12:59 |
| error144 | I can't found file named kernel.mk? | 12:59 |
| rrq | hmm I really can't guess on what you have there :) it does not seem to me that you are running ./build-sudo.sh in the worpspace with unaltered sources. | 13:17 |
| error144 | rrq my distro being minimal is the closest thing to the statement you said | 13:23 |
| error144 | but I have installed all dependencies found in the git page of the scripts | 13:23 |
| error144 | they were one missing dependenciy that I found out with you, which was debootstrap | 13:24 |
| rrq | the iso building does require chroot, zsh, debootstrap, rsync and dpkg-dev in order to set up the chroot in which the iso is built, That chroot will be fully populated for the building quite independent of what the initial system is. | 13:24 |
| error144 | rrq I have a question, why does this tool downloads stuff and not uses already existing stuff to build the iso? | 13:34 |
| error144 | isn't my target to package my custom distro and not use any external packages? | 13:34 |
| rrq | the scripting builds a build system, which then is used to build the iso; the content of the iso comes separately and that is configured in the pool/ Makefile and lists | 13:36 |
| error144 | rrq understood, thank you, I will keep trying everything to make it work, I will report in case of a success. | 13:38 |
| rrq | The first stage downloads are fore the build system, and it needs those packages mentioned in b uild-sudo.sh in addition to that which comes with debootstrap. But basically none of that ends up on the iso. | 13:41 |
| rrq | The second stage downloads happen for populating the installer initramfs, and the third is for the on-iso pool | 13:42 |
| error144 | rrq I asked that because the error happens after the second package start downloading, so I wanted to know if there is a way to simply skip already existing packages | 13:44 |
| rrq | the third stage is handled via "packages.mk", which goes into the pool/ directory to make the desired contents list depending on which "ISO" is targeted | 13:46 |
| rrq | each of the ISO types have targets in pool/Makefile that define which packages are included. You could eg change the SKIPLIST for the desired target to be your list of packages to skip... | 13:48 |
| rrq | the current netinstall includes the installer packages (some of which get unpacked during installation), and then all required and important packages | 13:50 |
| rrq | so you can also change the contents of the included lists, although the all-* are created from the available package collections | 13:55 |
| error144 | rrq that seem to be a good idea! | 13:57 |
| error144 | rrq ok here is an update, I get back to try using build.sh, it says: | 14:02 |
| error144 | debootstrap returns 1 | 14:02 |
| error144 | exist 1 | 14:02 |
| error144 | above that it says: | 14:02 |
| error144 | Tried to extract package, but file already exists | 14:02 |
| error144 | does this mean it worked or not? | 14:02 |
| rrq | you'll need to use the build-sudo.sh script; I just earlier made a patch for root that you could check out (it merely aliases "sudo" to nothing). The script "build.sh" is not currently maintained. | 14:04 |
| error144 | rrq ok I will use the updated script | 14:06 |
| rrq | note also that debootsrap for chimaera is missing the setup for daedalus, which you can fix by setting a link: ln -s ceres /usr/share/debootstrap/scipts/daedalus | 14:08 |
| error144_ | rrq this time it runs differently, it downloaded alot of stuff then: said these | 14:25 |
| error144_ | Make: *** No rule to make target 'boot/isolinux/pics/devuan-chimaera-bootscreen.iso-640x480.png' ... | 14:26 |
| error144_ | and most importantly | 14:26 |
| error144_ | rsync: [sender] link_stat "chimaera.fs/installer-iso/content" failed: no such file or directory | 14:27 |
| error144_ | rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1333) [sender=3.2.3] | 14:27 |
| error144_ | what now? | 14:28 |
| error144_ | did it work or failed? | 14:29 |
| rrq | good. that's a bug in the installer; use the following command and build again: | 14:31 |
| rrq | mv boot/isolinux/pics/devuan-chimaera{-deepsea,}-bootscreen-iso-640x480.png | 14:31 |
| rrq | btw when it succeeds, it leaves the iso in chimaera.fs/installer-iso/ named by type name, eg netinstall-amd64.iso | 14:35 |
| error144__ | rrq It worked!!! Thank you so much <3 | 15:39 |
| error144__ | without you, I wouldn't of known how to do it | 15:40 |
| error144__ | I may make an article explaining how to use this tool in order for people to know how to make custom distro out of devuan | 15:40 |
| error144__ | Thank you again! | 15:41 |
| hyrcanus_ | i think 'wouldnt of' should result in revocation of a license to use a keyboard | 15:43 |
| fluffywolf | why the hell did the chimaera upgrade downgrade my kernel, and why does it no longer wake up correctly once it blanks the screen? grrrr | 17:17 |
| fluffywolf | this is the worst upgrade I've had in many years of debian and debian-based usage. | 17:17 |
| fluffywolf | apparantly auto-removing all your kernels is now a "feature"?! | 17:19 |
| sadoon_albader[m | o_o | 17:56 |
| sadoon_albader[m | He/she left but | 17:57 |
| sadoon_albader[m | I've never had devaun or debian remove my older kernels | 17:57 |
| sadoon_albader[m | And the sleep thing is probably his device is messed up on a newer kernel | 17:57 |
| DPA | I like the automatic removal of old kernels. It's not unusual to /boot/ filling up with kernels eventually, which can be hard to fix for less experienced users. And if I want to keep one, I can just apt-mark hold it. | 18:43 |
| DPA | Also, they won't be removed without an apt-get autoremove, will they? | 18:43 |
| hyrcanus_ | defaulting to at least one previous seems wiser | 18:46 |
| rwp | I think kernels (and other packages) are only removed automatically with autoremove. Which I routinely do. (apt-get autoremove --purge; with --purge to avoid an rc state) | 19:32 |
| rwp | With kernels I have seen an annoying trend for security upgrade kernels to not roll forward the package name version. Causing an in place replacement. | 19:33 |
| critr | i was so surprised that i couldn't install devuan (or any other linux) on a lenovo nitro 5 gaming 3 a5ach5 that i bought. i returned it. | 19:37 |
| critr | (15ach6) | 19:38 |
| buZz | uefi and secure boot enabled in bios, i bet | 19:50 |
| sadoon_albader[m | Pros of using (even slightly) older laptops: you can run almost any OS you want :) | 19:53 |
| critr | nope. i turned off secure boot and every other security feature i could find in the dumbed-down bios settings. it was the old 'cant find medium with a live filesystem' thing but made invincible. | 19:53 |
| sadoon_albader[m | And even when you can't, there's probably enough documentation and a good used market | 19:53 |
| critr | agreed, sadoon_albader[m | 19:54 |
| sadoon_albader[m | <rwp> "I think kernels (and other..." <- Yup I think this is correct | 19:54 |
| sadoon_albader[m | I upgraded from beowulf to chimaera and kernel 4.19 stayed along with 5.10 | 19:54 |
| fsmithred | you don't have the kernel metapackage installed | 19:54 |
| sadoon_albader[m | And it does prompt you to autoremove | 19:54 |
| sadoon_albader[m | s/prompt/advice | 19:54 |
| fsmithred | autoremove what? | 19:54 |
| sadoon_albader[m | s/advice/advise lmao | 19:55 |
| sadoon_albader[m | fsmithred: Older kernels | 19:55 |
| fsmithred | did new kernel get installe automatically? | 19:55 |
| fsmithred | installed | 19:55 |
| sadoon_albader[m | When upgrading from beowulf to chimaera? | 19:55 |
| sadoon_albader[m | Yes | 19:55 |
| fsmithred | ok, so you do have the metapackage. Kernels don't get removed automatically. | 19:55 |
| fsmithred | in case you need the old one to boot. | 19:56 |
| sadoon_albader[m | This was specifically about someone who came here complaining that his upgrade removed older kernels automatically | 19:56 |
| fsmithred | I don't believe it. | 19:56 |
| sadoon_albader[m | Me neither | 19:56 |
| fsmithred | sadoon_albader[m, I read the log for this channel, and the person who reported a kernel removal is someone whose word I trust. This might be a new "feature". | 20:33 |
| sadoon_albader[m | Wish he/she had given more info then | 20:35 |
| sadoon_albader[m | I never had that issue and I've done multiple beowulf > chimaera upgrades | 20:36 |
| fsmithred | Afdal, there were changes in some of the xfce config files, and you probably still have the old one in your home configs. Looks at ~/.config/xfce4/xfconf/xfce-perchannel-xml/xsettings.xml | 20:41 |
| fsmithred | ld be able to delete that file, log out of desktop and log in again. You might need to re-select some desktop settings. | 20:42 |
| Afdal | That might be true, and it could be causing some other problems I haven't noticed yet, but it turns out the Xfce devs actually removed icons from window menus for some strange reason | 20:42 |
| Afdal | It's upsetting other people so we might see them bring it back eventually | 20:43 |
| fsmithred | there's a thread on the forum about this. | 20:43 |
| fsmithred | there are still icons in the panel menu | 20:43 |
| fsmithred | applications menu | 20:43 |
| Afdal | Yeah I'm not talking about the applications menu | 20:43 |
| Afdal | talking about the generic universal window menu | 20:43 |
| Afdal | when you click the top left on a window or right-click a window button on the panel | 20:44 |
| Afdal | both of those have had their icons removed | 20:44 |
| fsmithred | ok, I'm not in chimaera right now. Will have to check later. | 20:44 |
| fsmithred | maybe it's just part of the trend to have floating words in light gray on lighter gray with no borders on the buttons. | 20:45 |
| fsmithred | those visual boundaries are just clutter | 20:46 |
| fsmithred | [/sarcasm] | 20:46 |
| golinux | Afdal: Are you using the deepsea theme? | 20:48 |
| Afdal | Using Greybird | 20:49 |
| golinux | You have met the GTK3 apocalypse | 20:50 |
| golinux | Try the Clearlooks-Phenix-Deepsea theme and see if those problems go away | 20:50 |
| golinux | Ah, yes . . . I remember you told me that before. | 20:51 |
| golinux | Just switch it out for giggles. | 20:51 |
| golinux | In any case, I strongly suspect that's a greybird problem . . . | 20:52 |
| critr | you can customize any theme to put a better title bar at the top of windows. i always just use the windows one. | 20:52 |
| golinux | Clearlooks-phenix was the only theme I could get to work that still looked "classic" | 20:52 |
| critr | at least in mate.... | 20:52 |
| golinux | and that's why it's the default. | 20:53 |
| Afdal | nah it's a problem with all my themes | 20:59 |
| Afdal | it's theme agnostic | 21:00 |
| Afdal | Like I explained, this is an actual change made by an Xfce dev | 21:00 |
| Afdal | let me find the diff again | 21:00 |
| Afdal | https://gitlab.xfce.org/xfce/xfwm4/-/commit/8a16ca2e6b49679b4d217032d9bcf56692f51218 | 21:01 |
| Afdal | Anyway it's upsetting more people after I pointed it out in #xfce, so maybe we'll see a revert back at some point | 21:01 |
| Afdal | someone said they'd support me if I filed a bug report about it | 21:03 |
| sadoon_albader[m | Who's dissing greybird | 21:05 |
| sadoon_albader[m | It's surprisingly the only theme I've used with xfce that hasn't caused any issues for over a year and half now :D | 21:07 |
| sadoon_albader[m | I'd really love to use something like chicago95 but it breaks things | 21:07 |
| Joy-Unit | if xfce causes problems, going to a simple WM can solve them. | 21:09 |
| Joy-Unit | it's a bit like losing weight. you feel better afterwards. | 21:10 |
| Joy-Unit | dropping the 'desktop environment' concept | 21:11 |
| Afdal | We can love both WMs and DEs can't we :} | 21:17 |
| Afdal | I am both an avid Openbox fan and an Xfce fan, depending on the device | 21:17 |
| Joy-Unit | i'm more like the dog that doesn't like half the guests | 21:18 |
| critr | real men don't use X | 21:19 |
| peterrooney | the only thing I use xfce for is to download & compile the latest e16 | 22:33 |
| gnarface | hah, nice | 22:34 |
| peterrooney | simplicity is my joy | 22:34 |
| nemo | I'm kinda stuck on MATE just due to laziness. WM is mostly for me about running a decentish terminal, and there's plenty of documentation and widgets and whatnot out there for it | 22:35 |
| nemo | much like using debian/devuan, I like a large userbase so I don't have to search much for support and probably my issues have been addressed already | 22:36 |
| nemo | plus, MATE is pretty darn memory efficient, about the same as XFCE apparently. | 22:36 |
| nemo | that said, it seems XFCE has gotten a lot better recently in terms of features, consistent UI, and basic functionality from last time I used it at work. Still not gonna bother changing my defaults though | 22:36 |
| * gnarface would still be using e16 too if it hadn't started to cause game compatibility issues for me | 22:38 | |
| nemo | gnarface: does e16 require hardware compositing? | 22:39 |
| nemo | gnarface: that's the only game-related issue I've ever had with WMs | 22:39 |
| nemo | gnome3 and KDE were unusable on my old laptop due to that. only MATE worked | 22:40 |
| gnarface | nemo: last i used it, you could still disable compositing, but i'm not sure if that was related to the issue i had... it was a nvidia driver specific problem that for some reason would only crash wine in e16... if e16 is still getting patches today maybe i should try it again but i was assuming it was pretty much EOL'd | 22:41 |
| gnarface | nemo: (this was a few years back when the 3rd party maintainer's fork of it got pulled from the repos | 22:41 |
| gnarface | ) | 22:41 |
| peterrooney | gnarface: kwo is still maintaining it, latest update was september 17 | 22:42 |
| gnarface | peterrooney: september this year or september 2017? | 22:43 |
| peterrooney | this year. | 22:43 |
| Joy-Unit | it is eternal september :/ | 22:43 |
| peterrooney | before that was mid-april, and gosh my life is boring if i can remember these things | 22:43 |
| gnarface | peterrooney: hmm, very compelling information, thank you. i'm also not using nvidia hardware on this machine anymore so maybe i should check it out | 22:43 |
| gnarface | it is slowly getting more and more difficult to functionally replicate my e16 desktop in current versions | 22:44 |
| gnarface | i wonder why it's not still in the repos? | 22:45 |
| peterrooney | gnarface: probably libimlib {1,2} issues and you and me not volunteering to maintain for the distro. | 22:49 |
| gnarface | ah, possibly, that sounds familiar | 23:07 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
