askiw | hi, i have a problem. when i plug in headphones, my laptop microphone stops working. where could be a problem? | 01:13 |
---|---|---|
gnarface | askiw: try disabling auto-mute mode in alsamixer and pavucontrol | 01:22 |
gnarface | askiw: the side effect is the speakers will stay on unless you mute them then | 01:23 |
askiw | gnarface, you mean the sound will go through both speakers and headphones? | 01:24 |
gnarface | askiw: yea, no volumes will change anymore as a result of analog jack hotplug detection events. you'll have to manage them manually | 01:25 |
gnarface | askiw: it's definitely a problem with your driver, but this might be a realistic way to work around it (getting it actually fixed is probably not realistic, and definitely will take much longer, so you'll want to try this first either way as a temporary solution) | 01:26 |
gnarface | askiw: if you're not using pulseaudio, you won't need to mess around with pavucontrol, but if you are using it, you will have to stop it before launching alsamixer | 01:28 |
askiw | gonna try that, thanks | 01:29 |
gnarface | no problem, good luck | 01:30 |
askiw | getting it actually fixed would need to edit the driver? | 01:30 |
gnarface | yea, if you want to explore that route, register for the alsa-devel mailing list and start hanging out in #alsa | 01:30 |
gnarface | just properly filing a bug report they could conceivably take action upon will require you to do some work on your own first, too, including but not limited to compiling a fresh copy of the latest kernel with debugging on | 01:31 |
askiw | sounds fun:) | 01:31 |
gnarface | if it's the snd_hda_intel driver though, sometimes you can improve behavior by overriding hardware model auto-detection with a module parameter | 01:33 |
gnarface | that's more likely in cases where it never worked | 01:33 |
gnarface | if it used to work and this is a regression, the matter is probably stickier | 01:33 |
gnarface | in that case though if you have the previous kernel installed still, you can usually reboot to it to verify | 01:33 |
Wafficus | hey there, can anyone help me figure out how to make my Focusrite Solo Interface (gen 2) audio interface work via the alsa config in ~/.asoundrc? | 04:37 |
Wafficus | I had it before, but my previous dot file got overwritten since.. I'm an idiot | 04:37 |
Wafficus | anyway, I know it involves aplay -l for starters though | 04:37 |
gnarface | defaults.pcm.!card | 04:39 |
gnarface | defaults.ctl.!card | 04:39 |
gnarface | defaults.pcm.!device | 04:39 |
gnarface | if this is just about changing the default, just just define those 3 lines ^ | 04:39 |
gnarface | my example has a string for the first two (the same string, the short version of the card name) and a integer for the device # | 04:40 |
gnarface | numbers probably work for both | 04:40 |
gnarface | but the string is less likely to change | 04:41 |
Wafficus | yeah its just to change the defaults | 04:45 |
Wafficus | my default card is 1 | 04:46 |
Wafficus | rather | 04:46 |
Wafficus | whoops, its card 2 | 04:46 |
gnarface | the numbers start at 0 | 04:46 |
gnarface | usb stuff is rarely in a predictable order though | 04:47 |
Wafficus | yeah its in card 2 though | 04:50 |
Wafficus | so I just need: defaults.pcm 2 | 04:53 |
Wafficus | defaults.ctl 2 | 04:53 |
Wafficus | defaults.pcm 2 | 04:53 |
Wafficus | is that correct? | 04:53 |
gnarface | the "!" is important | 04:54 |
gnarface | oh | 04:54 |
gnarface | you're missing the whole last part | 04:54 |
gnarface | defaults.pcm.!card | 04:55 |
gnarface | defaults.ctl.!card | 04:55 |
gnarface | defaults.pcm.!device | 04:55 |
gnarface | so maybe !card 2 and !device 0 | 04:57 |
gnarface | ? | 04:57 |
gnarface | i usually use the name for !card | 04:57 |
gnarface | usually it's something like SB or Intel or PCM | 04:57 |
gnarface | or maybe HDMI | 04:57 |
gnarface | you should be able to get the info from aplay -l | 04:57 |
gnarface | but what you need to understand is that every card has one or more devices on it | 04:58 |
gnarface | and while you usually use the first device on the first card (0,0) you'll need to set both here, probably to something different | 04:58 |
gnarface | sigh | 04:58 |
gnarface | ...and you don't have to reboot for changes to take effect | 04:59 |
sauron- | gnarface Wafficus is gone | 04:59 |
gnarface | yea it was sarcasm | 04:59 |
sauron- | lol | 04:59 |
Wafficus | back sorry, my powerstrip got disconnected | 04:59 |
gnarface | oh, i thought you rebooted | 05:00 |
gnarface | on purpose | 05:00 |
Wafficus | nah, by accident sorry | 05:00 |
gnarface | https://paste.debian.net/1184476/ | 05:00 |
gnarface | that example uses "Inte" as the card name, here, the card name would just be "SB": card 0: SB [HDA ATI SB], device 0: ALC892 Analog [ALC892 Analog] | 05:01 |
gnarface | er, "Intel" | 05:01 |
gnarface | follow me? | 05:01 |
Wafficus | gotcha | 05:01 |
Wafficus | I'll have to look at the aplay -l output and see if I can modify it | 05:01 |
Wafficus | one sec | 05:01 |
gnarface | aplay -l|grep card\ 1|cut -d ' ' -f 3 | 05:04 |
gnarface | er, actually: aplay -l|grep card\ 2|cut -d ' ' -f 3 | 05:04 |
gnarface | you said card 2 | 05:04 |
Wafficus | yep | 05:05 |
gnarface | you won't have to restart the computer, but you will have to restart pulseaudio if you're using it, and possibly the window manager and login manager too | 05:05 |
Wafficus | card 2: USB [Scarlett Solo USB], device: 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0 | 05:06 |
Wafficus | so with that in mind, is it: | 05:07 |
Wafficus | defaults.pcm.!card Scarlett | 05:07 |
Wafficus | defaults.ctl.!card Scarlett | 05:07 |
Wafficus | defaults.pcm.!device 2 | 05:07 |
sauron- | worked? | 05:14 |
gnarface | Wafficus: no, it's defaults.pcm.!card USB | 05:20 |
gnarface | seems dumb, but that's the way i do it | 05:20 |
gnarface | and device 0 i guess | 05:20 |
gnarface | 0 should be the default | 05:20 |
* Xenguy likes the dumb way too | 05:23 | |
Wafficus | so it would be: | 05:24 |
Xenguy | tada! | 05:24 |
Wafficus | defaults.pcm.!card USB | 05:24 |
Wafficus | defaults.ctl.!card USB | 05:24 |
Wafficus | defaults.pcm.!device 0 | 05:24 |
Wafficus | right? | 05:24 |
gnarface | yea, that should work | 05:24 |
gnarface | if the driver is behaving itself, anyway | 05:24 |
Wafficus | ok cool I'll try that thanks | 05:24 |
danuan | doing src builds with 100k - 500k of files over nfs is 5 -10 times slower then localy , isci can be faster but cannot be shared to multiple clients, anyone have any other ideas ? | 17:32 |
mason | danuan: distcc? | 18:54 |
danuan | compiling is not the problem , its access for 100k - 500k small files | 18:59 |
r3boot | mostly read? If so, you might be better off with some shared filesystem (ocfs, gluster etc) over iscsi | 19:02 |
DHE | maybe we don't understand the problem. are you trying to do clustered compiling? | 19:02 |
r3boot | If you also write a lot, distcc might be a better option tho | 19:03 |
danuan | compile over a shared network filesystem that has too many small files | 19:03 |
DHE | you're compiling with `make -jX` or equivalent for your toolset? maybe increase X? | 19:05 |
DHE | it's not a great solution, but it's probably low effort | 19:05 |
r3boot | Another option would be to separate reads from writes, and have your iscsi share ro-mounted on all boxen | 19:05 |
danuan | again isci is not an option since it is not a shared filesystem , and nfs has trouble with a shitload off small files | 19:06 |
r3boot | If you mount the iscsi share readonly, you can get past the requirement for the single target | 19:08 |
danuan | problem is not with compilation but accesss over netwrok to load of small files , zfs with sync=disabled is the best so far | 19:08 |
r3boot | That way, you dont need a shared filesystem on it, and you're limited to the speed of passing packets to/from your SAN | 19:09 |
danuan | but then again only one client can write | 19:10 |
r3boot | You can two-tier it | 19:10 |
r3boot | Have one iscsi share for reading, with (eg) ext4 on it, and another one with some shared filesystem on it for the writes | 19:10 |
r3boot | That will mean that you would need to patch the build process tho | 19:11 |
r3boot | The biggest issue with shares is the global lock which needs to be acquired on all servers participating in the (write) share before you can write. But, you only need that lock for writes, not for reads (assuming you dont rewrite the sourcecode during build) | 19:14 |
gnarface | why not just set the build directory to be local so the nfs share is only doing reads during the compilation process? | 19:57 |
gnarface | also i suspect that the problem nfs has with a flurry of small files would evaporate if it was backed by xfs instead | 19:58 |
mns` | Guys, do we have any wallpaper for devuan chimaera? | 20:07 |
gnarface | golinux: there's wallpaper already, isn't there? | 20:07 |
gnarface | mns`: i know they have colors already. i doubt a wallpaper could be far behind | 20:08 |
mns` | gnarface: oh, thx | 20:13 |
mns` | kde is flying here :D | 20:14 |
fsmithred | yeah we have wallpaper for chimaera. I'll see if I can find it. | 20:25 |
mns` | fsmithred: please!!!! | 20:45 |
fsmithred | working on it | 20:47 |
golinux | https://git.devuan.org/devuan/documentation/src/branch/master/art/graphics | 20:47 |
golinux | WM theme is also completed too. | 20:47 |
mns` | fsmithred: nice! | 20:47 |
mns` | golinux: thx! | 20:48 |
golinux | Look for "deepsea" for Chimaera theme | 20:48 |
fsmithred | https://git.devuan.org/devuan/documentation/src/branch/master/art/graphics/chimaera-deepsea/backgrounds | 20:48 |
fsmithred | colors are final on the theme? | 20:49 |
golinux | Except for openbox. | 20:49 |
golinux | I keep fogetting because it is such a pain to do. | 20:49 |
fsmithred | ok, I won't build it yet | 20:50 |
golinux | I need to go down the hex rabbit hole later today | 20:51 |
mns` | \o/ | 20:51 |
mns` | brb | 20:51 |
golinux | And who knows how many more | 20:51 |
danuan | mns: if your major concern is wallpaper vs actual functionality of the distro then i would recommend you try ubuntu | 20:51 |
gnarface | don't be mean | 20:52 |
fsmithred | damn, one of the first things I do after an install is change the wallpaper | 20:52 |
fsmithred | (don't tell golinux) | 20:52 |
mns` | danuan: as i said already. My devuan chimaera with kde is flying ... | 20:52 |
* golinux is insulted that the hours of work aren't appreciated by danuan | 20:53 | |
golinux | If I don't like the way it looks, I won't use it. Period. | 20:53 |
mns` | danuan: also, i guess you are not a very good contribute right? cuz you have time to talk silly things with me | 20:54 |
mns` | bbl | 20:54 |
fsmithred | other way to look at it: If all we have to worry about is the background image, devuan must be working pretty well. | 20:54 |
gnarface | well that's my take on it | 20:58 |
gnarface | it's pretty quiet this morning, so i think there was room for volunteers to help test the theme on testing | 20:59 |
gnarface | it's not the highest priority, but it needs to get done and nothing else apparently is broken at the moment so i'd say the timing is appropriate | 20:59 |
gnarface | also, i'm pretty sure Ubuntu ships all the same exact wallpapers except for this one | 21:00 |
mason | My background image is always a parchment map of Middle Earth. Doesn't matter if I'm using Devuan, FreeBSD, RHEL, Slackware, MacOS. It's weird how it just follows me around. | 21:00 |
danuan | gnarface: is there particular areas where help is needed ? | 21:01 |
* mason heads off to the post office. | 21:01 | |
gnarface | danuan: like i said, other than this theme at the moment nothing comes to mind, but i don't claim to be an authority on the matter, either. maybe ask around. | 21:01 |
gnarface | danuan> i can give you multiple backgrounds , but i do not think it is what devuan needs , its actual oldscool unix administrators support that matters | 21:07 |
gnarface | ^ i don't disagree, but trying to pick a fight with me in private isn't going to convince me that you're being honest with me or yourself about your stated goal here | 21:08 |
gnarface | you straight up told someone to install Ubuntu | 21:08 |
gnarface | screw your head on straight | 21:08 |
danuan | then what does devuan need ? | 21:11 |
gnarface | right now? probably what we need most is more testing of ARM images | 21:11 |
gnarface | but if you wanted to test chimera instead of just bagging on other people for your disapproval of their testing, i'm sure that would not be entirely wasted effort, either | 21:12 |
gnarface | in general, the forumla should be "Am I helping, or am I stopping someone else from helping?" | 21:13 |
gnarface | if you should ever come up with the latter as an answer, redirect your focus | 21:13 |
danuan | then if it takes you only a second to respond does it mean you actually thinking about the response ? | 21:14 |
gnarface | are you trying to test if i have op privileges to ban you? because i would have already if i did. | 21:14 |
danuan | go ahead ! | 21:15 |
gnarface | your reading comprehension is pretty low, too, is my analysis. re-read my last sentence. | 21:15 |
gnarface | in fact, considering how badly wrong you got that one, i think you should re-read EVERYTHING i said this morning, and then spend a few hours thinking about your actions and what motivated you to behave this way. chances are you're projecting. | 21:16 |
danuan | geesz , egoos flyin | 21:17 |
gnarface | you're beneath me | 21:17 |
danuan | please ban me | 21:17 |
gnarface | <danuan> just showed yourself for a kiddies that you are , didnt you ? | 21:30 |
gnarface | ^ danuan stop harassing me | 21:30 |
gnarface | you didn't win an argument, what you're doing is burning through the quiet good will of the people watching this channel who actually are in charge | 21:30 |
gnarface | and it's not relevant to support, so no, i'm not going to keep engaging you about it | 21:31 |
gnarface | and fix your fucking grammer | 21:31 |
gnarface | grammar* | 21:31 |
debdog | are these irc-bash thingies still a thing? | 21:33 |
gnarface | danuan: stop whispering me, i mean ti | 21:41 |
gnarface | danuan: you're proving that you know you lost the argument by trying to continue to provoke me in private, and frankly it's pretty stupid | 21:41 |
danuan | :) | 21:41 |
danuan | go call you parents about your abusing you ! | 21:42 |
fsmithred | done now? If not, take it to OT | 21:43 |
Chakpapa | How usable is chimaera? | 21:56 |
Chakpapa | bullseye is reaching Freeze. | 21:56 |
danuan | like a hooker you pay up front | 21:56 |
mns` | Chakpapa: I have a full working kde desktop | 21:57 |
mns` | So far so good | 21:57 |
gnarface | Chakpapa: everything is done except for the wallpaper :) | 21:57 |
mns` | So ... there's no op here? | 21:57 |
gnarface | Chakpapa: (no, i don't know, but a bunch of people are using it already) | 21:57 |
Chakpapa | Lol @ wallpaper. Well I got mine. | 21:57 |
Chakpapa | Well, will openrc-init be functional this time around? | 21:58 |
fsmithred | a lot of stuff is already devuanized, so chimaera is in pretty good shape | 21:58 |
gnarface | wasn't openrc functional last time around? or do you mean without depending on sysvinit parts? | 21:58 |
Chakpapa | I am talking about openrc-init as PID0 | 21:59 |
Chakpapa | OpenRC+openrc-init combination | 21:59 |
Chakpapa | works in Gentoo | 21:59 |
fsmithred | I think that's what it does when you install openrc | 21:59 |
Chakpapa | in Devuan buster it was not compiled with the necessary scripts | 21:59 |
Chakpapa | I am talking about this https://wiki.gentoo.org/wiki/OpenRC#openrc-init | 21:59 |
Chakpapa | https://wiki.gentoo.org/wiki/OpenRC/openrc-init | 22:00 |
gnarface | Chakpapa: in buster people were just replacing the debian one with the gentoo one, i dunno if the work to switch over to it ever got done. there was talk of it then there wasn't... | 22:00 |
Chakpapa | This completely replaces and bypasses sysvinit | 22:00 |
Chakpapa | This was the only thing I would like to see in Devuan. I mean of course "optionally" when someone selects the openrc option during installation | 22:01 |
gnarface | Chakpapa: anyway i know that unofficial packages were built and floating around, building it yourself wasn't known to be a hard task, and i think someone demonstrated a simple file move or rename fix to the existing package to make it do the same | 22:01 |
fsmithred | yeah, I just booted a beowulf openrc live-iso and /proc/1/comm is init | 22:01 |
fsmithred | if you install runit, you get runit as pid 1 | 22:01 |
fsmithred | but it still uses the sysvinit scripts | 22:02 |
* Chakpapa is talking about /sbin/openrc-init as PID1 :P | 22:02 | |
Chakpapa | I mean its not a critical thing as such. Was just wondering if anyone looked into it | 22:02 |
Chakpapa | Although in the long run I would definitely like to see s6 getting adapted more | 22:03 |
Chakpapa | Seems promising | 22:03 |
fsmithred | I'm not aware of anyone doing much work on openrc in devuan | 22:03 |
fsmithred | I know parazyd did some work on it, but that was probably two years ago | 22:03 |
Chakpapa | So most people just stick to sysvinit? | 22:03 |
gnarface | people definitely looked into it, just nothing officially got done. people did build and install the gentoo implementation though. i think not just in beowulf, also in ascii | 22:03 |
gnarface | most people do just stick to sysvinit, or the openrc+sysvinit combo which debian did have good reasons for | 22:04 |
gnarface | and we do provide support for sysvinit here, it's not a complex beast | 22:04 |
fsmithred | I know there are some people using openrc and there are some using runit | 22:04 |
fsmithred | and there's some work being done on s6 | 22:05 |
Chakpapa | I mean the sysvinit+OpenRC (As the helper) is definitely the predominant even in Gentoo. OpenRC+openrc-init is relatively new | 22:05 |
fsmithred | if you have an itch, scratch it | 22:05 |
gnarface | Chakpapa: if you want to test someone else's openrc-init build, hang around and someone usually will present theirs eventually | 22:06 |
fsmithred | does it need something to replace the init scripts? | 22:06 |
gnarface | doesn't it just use some sort of condensed start list like BSD rc? | 22:07 |
fsmithred | I haven't played with openrc at all, despite the fact that I've made live-isos that use it. I didn't have to do anything different. | 22:07 |
gnarface | i don't remember how it works anymore, i used it for a little on gentoo in 2006 | 22:08 |
fsmithred | with runit, each service gets a directory with run files | 22:08 |
fsmithred | and I've only seen the ones for the gettys. They are short. | 22:09 |
gnarface | i also really thought someone had simple hack to make the native openrc build behave like the gentoo one just by replacing the init binary with a symlink or something like that. anyone remember? | 22:09 |
Chakpapa | openrc-init Doesn't exactly "replaces" init scripts. It expects them to be in /etc/init.d ... It just replaces sysvinit as PID0 and takes over completely. shutdown / reboot is handled by openrc-shutdown in that case | 22:09 |
gnarface | <danuan> if you need an ego boost go an jog or something , but misinforming people about few command you looked up on google is not it | 22:13 |
Chakpapa | Debian should have made systemd as "optional" instead of the other way around. Similar to Gentoo. : / | 22:13 |
gnarface | ^ danuan. i mean it. stop whispering me. you lost the fucking argument now deal with it | 22:13 |
mns` | cmd: Distributor ID:Devuan | 22:22 |
mns` | cmd: Description:Devuan GNU/Linux 4 (chimaera/ceres) | 22:22 |
mns` | cmd: Release:testing/unstable | 22:22 |
mns` | cmd: Codename:n/a | 22:22 |
mns` | for the jealous | 22:22 |
* mns` screams! | 22:23 | |
Chakpapa | mns`, use "SID" + "Experimental" :P | 22:29 |
Chakpapa | lmao | 22:29 |
mns` | Chakpapa: sure, in a vm :D | 22:31 |
Chakpapa | lol | 22:31 |
xinomilo | experimental isn't a real dist | 22:32 |
Chakpapa | I know. Was just joking | 22:32 |
xinomilo | :) | 22:32 |
Chakpapa | Its more like a staging area before SID | 22:32 |
n4dir | experimental can be interesting if the freeze is so cold that even Sid feels static. But i don't recall ever installed anything from it | 22:33 |
gnarface | i needed it once for a couple weeks for nvidia drivers that World of Warcraft required that were crashing everything else | 22:34 |
n4dir | yeah, like that. it can happen | 22:34 |
gnarface | (discovered the hard way why they were not in unstable yet) | 22:34 |
n4dir | if it wouldn't have been mentioned here right now, i probably would not even think of it. You hear of it like twice a year, if at all | 22:35 |
tuxd3v | hello all, I need the plugin for geany, to debug software | 22:36 |
tuxd3v | I installed packages: geany geany-common geany-plugin-addons geany-plugins-common | 22:37 |
systemdlete | https://support.mozilla.org/en-US/questions/982480 | 22:37 |
tuxd3v | but when i go to tools > plugin Manager, I on't find the debugger :/ | 22:38 |
systemdlete | This makes me want to scream! The mozilla person seems to refuse to acknowledge that the bug is in firefox code. Just admit it, then proceed to fix it. The poor reporter has to reiterate the same info at least 3 times. | 22:38 |
systemdlete | I am so ready for a different browser that is not firefox/mozilla based. I just might switch to chromium, but that also has its own issues... | 22:39 |
systemdlete | I have to wonder if mozilla devs understand the concept of test-before-release. | 22:39 |
systemdlete | (this problem did not exist before the latest firefox upgrade) | 22:40 |
systemdlete | fix one, break two | 22:40 |
nemo | systemdlete: yeah, their whole new DoH system was specifically designed to avoid ISPs snooping on DNS requests. buuut it's supposed to detect when one is on "corporate" and disable itself | 22:40 |
nemo | systemdlete: I guess the issue is sometimes corporate not being detected | 22:41 |
nemo | in any case fix is simple, just turn off DoH | 22:41 |
nemo | similar to my corporation deliberately MitMing everything on enter on their land. Firefox detects this, you get a brief error hitting an external site then it immediately turns off cert protections with an "enterprise mitm" flag | 22:42 |
systemdlete | DNS over http is not enabled. | 22:42 |
systemdlete | ie, it seems to already be disabled | 22:43 |
systemdlete | ?? | 22:43 |
nemo | systemdlete: ah. I should've read https://bugzilla.mozilla.org/show_bug.cgi?id=408669 | 22:43 |
nemo | I understand the issue better now | 22:43 |
nemo | I haven't used anything but VPNs and such in years. | 22:43 |
nemo | I see | 22:44 |
nemo | "this is by design - there is not one unified view of DNS, and when you are using a proxy you are proxying the DNS to that view. | 22:44 |
nemo | You can however use DNS explicitly within a .PAC script" | 22:44 |
nemo | I have no idea if that is a legitimate thing to say or not | 22:44 |
nemo | I'm totally unfamiliar with this subject area, so no idea if you're right or if Patrick is | 22:44 |
nemo | I do know "works in other browsers" does have some weight with them sometimes. maybe file a new bug with this angle? | 22:45 |
systemdlete | I'm not on a VPN. | 22:45 |
systemdlete | This is my own home desktop PC. | 22:45 |
systemdlete | It was working yesterday. | 22:45 |
nemo | systemdlete: but using SOCKS or somesuch right? | 22:45 |
systemdlete | not sure | 22:45 |
nemo | that seems to be what that bug is all about | 22:45 |
systemdlete | I am using dnsmasq on openwrt router | 22:45 |
nemo | that's not a problem | 22:46 |
systemdlete | shouldn't be, no | 22:46 |
systemdlete | how to check if I'm using socks? | 22:46 |
systemdlete | presence of library? | 22:46 |
nemo | heh. if you aren't sure, you almost certainly aren't | 22:46 |
systemdlete | I do not recall doing anything specifically when I installed this machine. | 22:47 |
gnarface | tuxd3v: did you try installing package "geany-plugin-debugger" or running "apt-cache search ^geany-" ...? | 22:47 |
nemo | systemdlete: ≡→Preferences→General→Network Settings | 22:47 |
nemo | systemdlete: same place you'd go to make sure DoH is turned off | 22:47 |
systemdlete | yeah. Like I said, DoH is disabled (not checked) | 22:47 |
nemo | systemdlete: interesting. there's even a "proxy dns" flag in there, so that bug is probably way out of date | 22:47 |
tuxd3v | gnarface, doesn't exist at least with that name :/ | 22:48 |
nemo | systemdlete: and "no proxy" set? | 22:48 |
systemdlete | right | 22:48 |
systemdlete | lol | 22:48 |
gnarface | tuxd3v: oh. i see it on ceres. maybe check backports? | 22:48 |
systemdlete | hey nemo, thanks for responding. Appreciate it. | 22:48 |
nemo | systemdlete: and, this is a bit silly, but if you just do "dig" or "ping" everything is fine right? and your dnsmasq doesn't have any bugs w/ AAAA requests? | 22:48 |
systemdlete | oh yeah. Works from command line, chromium browser, etc | 22:49 |
systemdlete | and I can enter the IP explicitly and it works | 22:49 |
nemo | systemdlete: I had issues years ago in firefox due to defaulting to IPv6 plus severely buggy corporate DNS | 22:49 |
tuxd3v | nope, not it backports | 22:49 |
tuxd3v | :( | 22:49 |
nemo | systemdlete: network.dns.disableIPv6;true would take care of that | 22:49 |
systemdlete | Are you saying you believe that I am running into a ipv6 problem? Or is that to correct a different problem? | 22:50 |
gnarface | tuxd3v: i'm not seeing it at pkginfo.devuan.org either, but i don't know if that's a bug with pkginfo.devuan.org or not, because i see it here in my local package cache for ceres. | 22:51 |
gnarface | tuxd3v: either way, you might end up having to build it yourself | 22:51 |
nemo | systemdlete: I do not know... maybe test with dig, and with that flag set | 22:51 |
nemo | systemdlete: I'm trying to think of anything that could explain differing behaviour w/ proxy and DoH disabled | 22:52 |
nemo | systemdlete: at that point it really should just be using system DNS - IPv4 vs IPv6 is typically the only variation | 22:52 |
systemdlete | I'm trying to think of anything that could explain differing behavior from yesterday! | 22:52 |
nemo | systemdlete: firefox version update? ☺ | 22:52 |
systemdlete | The only thing I can think of is the upgrade. | 22:52 |
systemdlete | (yes) | 22:52 |
nemo | systemdlete: ok. well that's easy enough to test, just try an older firefox zip | 22:53 |
nemo | systemdlete: there's tons of them on the firefox website | 22:53 |
systemdlete | ugh. | 22:53 |
nemo | systemdlete: http://ftp.mozilla.org/pub/firefox/nightly/ grab one from a year ago, unzip it | 22:53 |
nemo | no need to even bisect at least at first | 22:53 |
systemdlete | nah | 22:53 |
systemdlete | I am certain that is the issue. | 22:53 |
tuxd3v | its a problem in pkginfo.devuan.org | 22:53 |
systemdlete | They "fixed" something. | 22:53 |
tuxd3v | it exists in amd64 | 22:53 |
tuxd3v | but not in i386 | 22:53 |
tuxd3v | https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=geany-plugin-debugger | 22:54 |
nemo | systemdlete: ok, well, only flag I can think to try is that IPv6 thing. and maybe check the changelog | 22:54 |
nemo | systemdlete: I *have* gotten things fixed in past by reporting a problem after having bisected. it's a little tedious to do, but they have a tool for it | 22:54 |
nemo | https://github.com/mozilla/mozregression | 22:54 |
nemo | usually just takes like a dozen tries even with a broad range | 22:55 |
nemo | yay binary searches | 22:55 |
systemdlete | Yeah, it looks like the mozilla tech has filed a bug already | 22:55 |
nemo | systemdlete: oh? link? now I'm curious | 22:55 |
systemdlete | and there will be yay more no doubt | 22:55 |
systemdlete | look at the end of the link I gave above | 22:55 |
nemo | I did | 22:55 |
nemo | that's the one I was referencing | 22:55 |
nemo | that's an old ticket | 22:56 |
systemdlete | did you see where the tech offered to file a bug for it? | 22:56 |
nemo | closed WONTFIX | 22:56 |
systemdlete | not that old | 22:56 |
nemo | ok. then wrong reference | 22:56 |
nemo | link me to right one? | 22:56 |
systemdlete | Oh you are right -- I was looking at the january part -- didn't notice the year (7 years ago) | 22:56 |
nemo | yeah. and that is probably addressed by that "Proxy DNS requests" checkbox in the dialog you were in | 22:56 |
systemdlete | but still, the bug was fixed... and now re-appears | 22:57 |
nemo | might be something totally and wildly different. | 22:57 |
nemo | for one thing you aren't using proxy | 22:57 |
systemdlete | nemo: What I want to do is get away from constant buggy releases. | 22:57 |
nemo | nature of software dev... I can't get too upset about it. they broke all my internet at work due to the MitM they were doing corrupting SSL | 22:58 |
systemdlete | It seems like every time they release a new version, it introduces new problems. I wish I could just get security updates and experiment with new features at my own discretion. | 22:58 |
nemo | that's hardly Firefox' fault | 22:58 |
systemdlete | no it's not the nature of software dev | 22:58 |
nemo | then there was the browser crashing because Cylance was injecting itself into the process | 22:58 |
systemdlete | I've worked in environments where such releases would never be allowed. | 22:58 |
nemo | systemdlete: the problem (for you) is that it works for absolutely everyone else 😝 | 22:58 |
nemo | systemdlete: mozilla has one of the largest test systems out there. | 22:58 |
systemdlete | But this is going to be a philosophical, not technical, disagreement. | 22:58 |
systemdlete | (yeah, right) | 22:59 |
nemo | yes. right. | 22:59 |
tuxd3v | gnarface, ouch... its not in beowulf | 22:59 |
nemo | systemdlete: $ unzip -l mozilla_try-2021-01-08.zip | wc -l | 22:59 |
nemo | 286555 | 22:59 |
tuxd3v | I can't find it also on debian-buster | 23:00 |
nemo | a quarter of a million tests run each time they push something. not counting the tests run on nightly users | 23:00 |
systemdlete | no, thanks. | 23:00 |
systemdlete | so if they do all this testing, how did this (old!) bug creep back in? | 23:00 |
tuxd3v | How can this guys compile a tool suite, for compiling code, and forget about the most important thing in the hole process... yeah the debugger :/ | 23:00 |
nemo | systemdlete: because it's a different bug | 23:00 |
systemdlete | not impressed here... sorry | 23:00 |
nemo | systemdlete: with similar symptoms | 23:00 |
nemo | systemdlete: have you tried the IPv6 thing yet? | 23:01 |
nemo | systemdlete: file a new bug. do a quick bisect to give them a regression range. test in a clean profile, test with alternate DNS servers | 23:01 |
systemdlete | it's the symptoms that are tested normally. At least that is how the regression testing I've worked with. | 23:01 |
nemo | systemdlete: give them all of this, I bet you'll get a quick fix | 23:01 |
nemo | systemdlete: problem for you is it is fine for rest of us | 23:01 |
nemo | systemdlete: my local DNS using gentoo + tinydns + dnscachex works just fine | 23:02 |
nemo | local and remote | 23:02 |
systemdlete | You are able to access local systems in firefox 78.7.0? | 23:02 |
nemo | yes | 23:02 |
nemo | systemdlete: both at work and home | 23:02 |
nemo | all versions of firefox | 23:02 |
systemdlete | why is it that chromium works then? | 23:02 |
gnarface | tuxd3v: i gotta assume debian maintainers operating independently of the upstream project pulled it for whatever support related reason. | 23:02 |
nemo | systemdlete: well. test clean profile. test different browser versions. | 23:02 |
nemo | systemdlete: chrome could be doing DNS through google for all you know 😝 | 23:02 |
gnarface | tuxd3v: try to build it yourself and maybe you'll run into the same problem, maybe not | 23:02 |
systemdlete | how would google know the IP addresses of my local systems? | 23:03 |
tuxd3v | gnarface, humm, I don't really have much options here , I will try to build it.. | 23:03 |
systemdlete | No, chromium is using the same dns resolver as firefox ever has. | 23:03 |
systemdlete | it has to be. | 23:03 |
tuxd3v | many thanks for the heal, as usual :) | 23:03 |
nemo | systemdlete: yeah, I just retested in a nightly firefox. hit internal unpublished no problem | 23:04 |
nemo | HTTP, HTTPS | 23:04 |
nemo | worked same, apart from HTTPS erroring ofc | 23:04 |
systemdlete | and if it doesn't work for ipv4 or ipv6, it wouldn't likely work for the other. Also, I only have ipv4 addresses defined in my openwrt. | 23:04 |
nemo | systemdlete: yeah. I just use IPv4 too | 23:04 |
systemdlete | I'll just use the ip addresses for now. | 23:04 |
nemo | systemdlete: on the other hand firefox does do IPv6 by default | 23:04 |
systemdlete | Or maybe I'll switch to chromium. | 23:04 |
nemo | systemdlete: have you tested in a clean profile yet? | 23:04 |
nemo | systemdlete: have you tried turning off that IPv6 yet? | 23:05 |
systemdlete | ^ | 23:05 |
systemdlete | Or maybe I should just power down the computer and read a book instead... ! | 23:06 |
systemdlete | sorry nemo. I'm just tired of chasing down bugs for the moment. I'll just wait until ff fixes it. It shouldnt' be very long | 23:06 |
nemo | systemdlete: it'll get fixed a lot faster if you help. 'cause, yeah, it's fine for rest of us 😝 | 23:07 |
nemo | oh well. whatev | 23:07 |
systemdlete | are you using 78.7.0esr? | 23:07 |
nemo | systemdlete: yes. and *I* unlike you, used a clean profile 😝 | 23:08 |
nemo | well in part 'cause I usually don't use ESR | 23:08 |
systemdlete | yes, a new profile works | 23:09 |
systemdlete | I'd rather not have to reset it all though | 23:10 |
systemdlete | is there a way to sort of "export/import" the settings from one profile to another? | 23:11 |
systemdlete | (I doubt it ofc) | 23:11 |
nemo | systemdlete: there's a few ways | 23:11 |
nemo | systemdlete: there's the profile sync feature | 23:11 |
nemo | systemdlete: there's copying over key files (like prefs.js) | 23:11 |
systemdlete | actually, prefs.js should be enough right? | 23:11 |
nemo | systemdlete: but really, if one works and the other doesn't, usual suspect is extensions or config settings | 23:11 |
nemo | I'd definitely start with prefs.js | 23:12 |
nemo | bonus if it breaks new one, it gives you a reduced set to check | 23:12 |
nemo | systemdlete: depends what you want in the new profile really | 23:12 |
systemdlete | ah, thank you nemo! I forgot all about those extensions | 23:13 |
nemo | O_o | 23:13 |
systemdlete | I have a few, and they might even be conflicting with each other! | 23:13 |
* systemdlete hits himself, hard! | 23:13 | |
nemo | that's why first step in #firefox support is "test in clean profile" | 23:13 |
nemo | avoids extension and pref config issues due to years of customisation | 23:13 |
nemo | which isn't to say they didn't break something in a new release | 23:13 |
nemo | but usually explains why no one else ran into it | 23:13 |
systemdlete | I have decentraleyes, privacybadger, ublock origin, AND ddg privacy | 23:14 |
nemo | hmmm | 23:14 |
nemo | I use those too | 23:14 |
systemdlete | all 4? | 23:14 |
nemo | well... haven't used privacybadger in a while | 23:14 |
systemdlete | OK, I'll disable that | 23:14 |
nemo | I use decentraleyes, umatrix, and noscript. | 23:14 |
nemo | I've never used ublock origin | 23:14 |
nemo | ok. I don't use *all* of them ☺ | 23:14 |
nemo | but also they are pretty major projects.. | 23:14 |
nemo | systemdlete: you mean https://addons.mozilla.org/fr/firefox/addon/duckduckgo-for-firefox/ right? | 23:15 |
nemo | I do have that one in a profile, but obv not in an ESR one. hm. | 23:15 |
systemdlete | "duckduckgo privacy essentials" | 23:15 |
nemo | umm sorry for the /fr/ link | 23:15 |
systemdlete | yep. privacy badger | 23:16 |
nemo | systemdlete: interesting. I haven't used privacybadger in a while | 23:16 |
systemdlete | now it works. ty again for your patience with this old pita | 23:16 |
* nemo shrugs | 23:16 | |
systemdlete | I think the others will provide enough protection for my tastes | 23:16 |
nemo | systemdlete: maybe report bug against privacy badger? | 23:17 |
systemdlete | or maybe I just need to do an update for it? | 23:17 |
tuxd3v | heal-> help | 23:17 |
systemdlete | (tuxd3v: Help *is* healing!) | 23:18 |
systemdlete | (so it's ok) | 23:18 |
nemo | systemdlete: I'd been kinda relying on firefox built-in tracking protection and noscript/umatrix these days. | 23:18 |
systemdlete | and nemo: Thank you for helping me "heal" MY system. | 23:18 |
tuxd3v | systemdlete, indeed hehe :) | 23:18 |
systemdlete | nemo: So I disabled the addon, enabled auto updates, re-enabled the addon, restarted browser, and now all is working like yesterday! | 23:21 |
nemo | systemdlete: oh. you had auto updates of addons turned off too? | 23:21 |
systemdlete | so it seems more likely that there was a problem with the update of privacy badger from Feb 2 (last update) | 23:22 |
nemo | I guess that's a good paranoia measure, but I mean... mozilla *does* do review of extensions at least... ☺ | 23:22 |
systemdlete | but it is still showing feb 2 last update | 23:22 |
systemdlete | hmmm. | 23:22 |
systemdlete | maybe when I did all that disabling and re-enabling, it updated some data? | 23:23 |
systemdlete | or otherwise reset itself | 23:23 |
nemo | orrr they did a bugfix release same day.. | 23:23 |
nemo | "Remove pixel cookie sharing detection for now " | 23:24 |
nemo | no idea what that was, but "remove for now" is never a good sign ☺ | 23:24 |
systemdlete | what is pixel cookie sharing? | 23:24 |
systemdlete | where is that? | 23:25 |
nemo | systemdlete: I guess they mean tracking pixels + cookies | 23:25 |
nemo | https://github.com/EFForg/privacybadger/commits/master | 23:25 |
nemo | systemdlete: I was just looking for commits same day as the release | 23:25 |
systemdlete | oh, I see. | 23:25 |
systemdlete | in the source, right. | 23:25 |
systemdlete | again, thank you so much for pointing me to a solution, whatever crazy thing it ends up being. | 23:26 |
systemdlete | and sorry for being such a crab about it all | 23:26 |
systemdlete | you don't deserve that. You are trying to help. | 23:26 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!