xrogaan | So I noticed on Chimaera, with xfce and elogind, xscreensaver isn't responsive when resuming from hibernation. I have to wait some 20 seconds before it prompts me with the unlock screen. | 01:03 |
---|---|---|
Walex2 | xrogaan: that looks like some DNS timeout... | 01:17 |
xrogaan | why would it make requests? | 01:18 |
Walex2 | xrogaan: is that system internet connected? | 01:19 |
xrogaan | yeah | 01:20 |
Walex2 | xrogaan: it can make requests for a million reasons, e.g. to resolver the system name and or to connect to a Kerberos server etc. etc. depending on what else is configured. | 01:20 |
xrogaan | alright, but what does? | 01:21 |
Walex2 | xrogaan: a first check would be 'grep $(uname -n) /etc/hosts' | 01:21 |
xrogaan | that's my local hosts | 01:22 |
Walex2 | xrogaan: it is just just a guess. You can get quite y bit of info with 'xscreensaver -verbose' | 01:22 |
Walex2 | xrogaan: what does that command say? | 01:23 |
xrogaan | that I have to kill the one already running? | 01:24 |
Walex2 | xrogaan: 'elogind --verbose' | 01:24 |
Walex2 | xrogaan: what does the 'grep' say? Does it return a plausible line? | 01:25 |
xrogaan | there is no elogind | 01:25 |
Walex2 | xrogaan: for 'xscreensaver' yes you have to kill the one already running, or start a new X session on another console | 01:25 |
xrogaan | there are just loopbacks addresses in my hosts files | 01:26 |
Walex2 | xrogaan: you wrote above " with xfce and elogind, xscreensaver" | 01:26 |
xrogaan | yes, 'elogind' doesn't exists as a software | 01:26 |
xrogaan | there is 'loginctl' | 01:26 |
xrogaan | and elogind-inhibit | 01:27 |
Walex2 | xrogaan: also hibernation is know to cause issues, and in particular to networking. | 01:27 |
xrogaan | xscreensaver-systemd: 01:31:11: uninhibited by "My SDL application" with cookie 40CD9813 | 01:32 |
xrogaan | that's kind of weird | 01:32 |
xrogaan | I'd assume the xscreensaver-systemd is forcing xscreensaver to not "restore" after resume. | 01:33 |
xrogaan | It has 1 minutes intervals between the xscreensaver-systemd: 01:32:12: exec: xscreensaver-command -verbose -deactivate | 01:34 |
xrogaan | I believe that comes from the steam client though | 01:41 |
xrogaan | I disabled xfce's "lock screen when hibernate". | 01:57 |
xrogaan | It might be xfce that's badly configured and doesn't know how to unlock. | 01:57 |
UsL | is devuan still using "flat-volumes = yes" in pulse audio daemon conf file, btw? I think the user friendly setting "flat-volumes = no" should be standard. Since devuan defaults to use PA anyway. | 11:52 |
schillingklaus | i avoid pulse wholesale, as it is also a redhatted beast | 11:54 |
humpelstilzchen[ | I don't even have the daemon installed | 11:57 |
UsL | granted, but as a default setting it should be "flat-volumes = no" I think. I recommended devuan to a friend and he was happy until kodi blew his ears out. | 11:58 |
UsL | as he did a "default" installation just clicking yes to all. Like 97 % out there does. | 11:59 |
schillingklaus | i hate default installations | 12:02 |
UsL | ah, I see debian has a bug for it. From 2009... https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=541538 | 12:03 |
UsL | That's funny.. Like they really can't be bothered with the plebs | 12:05 |
schillingklaus | poettering can't get bothered with bug reports | 12:07 |
UsL | either can debian it seems. | 12:07 |
UsL | perhaps devuan can illuminate the path to sanity | 12:08 |
UsL | but that would perhaps be a devuan without out PA at all | 12:09 |
schillingklaus | since debian adopted systemd, its maintainers also adopted Poettering's attitude | 12:10 |
jiggie | its poison | 12:14 |
UsL | even more the reason devuan should use flat-volumes = no. Found a rant: https://old.reddit.com/r/linux/comments/2rjiaa/horrible_decisions_flat_volumes_in_pulseaudio_a/ Some of the examples are pretty scary. Loosing some of your hearing because "poettering"... | 12:15 |
UsL | oh well, I should maybe make a post about it so devuan maintainers can change it. | 12:16 |
Wonka | uh, removing PA from devuan would also remove sound from Chromium and Firefox. | 12:19 |
schillingklaus | there's apulse | 12:19 |
Wonka | ok, didn't know about that. | 12:21 |
luna-is-here | apulse is not working reliably, though. I tried it for some time and it caused a lot of trouble. | 12:30 |
luna-is-here | I'd agreed that "flat-volumes = no" is a sane default. | 12:31 |
luna-is-here | * should be. | 12:31 |
fsmithred | flat-volumes = no is the default in Bullseye/Chimaera | 13:25 |
UsL | fsmithred: that's good to hear! (about flat-volumes = no, I got disconnected). I explained it to my friend and he wondered about alternative audio mixers and I said I only knew about jack but that I hadn't used it. | 14:50 |
Katje | anyone had issues using a /31 address (ipv4) and the /etc/network/interfaces system ? | 14:58 |
szutt | so you have only two addresses ? the broadcast address and the network ? | 15:02 |
GyrosGeier | no, that has been special-cased | 15:15 |
GyrosGeier | but it depends on the IP stack if that special case is implemented | 15:15 |
GyrosGeier | back when I was a regular on anonet, I used /31 networks for BGP peering and that was fine | 15:16 |
GyrosGeier | but IIRC I configured them with quagga | 15:16 |
GyrosGeier | I don't see why it shouldn't work through ifupdown though | 15:16 |
mason | Interesting: https://docs.netgate.com/pfsense/en/latest/network/cidr.html "The use of /31 networks is a special case defined by RFC 3021 where the two IP addresses in the subnet are usable for point-to-point links to conserve IPv4 address space. Not all operating systems support RFC 3021, so use it with caution." | 15:47 |
mason | Katje: GyrosGeier: ^ | 15:47 |
Katje | had to specify the broad cast as 45.255.255.255 | 15:47 |
Katje | works now tho | 15:47 |
mason | Katje: That's interesting and a bit weird. Be worth exploring whether it's intended in De*an. Having to specify a funny broadcast when the subnet doesn't have space for one would make me nervous. | 15:49 |
GyrosGeier | there shouldn't be a broadcast address on those networks at all | 15:52 |
GyrosGeier | IIRC you can just leave it out | 15:53 |
mason | https://datatracker.ietf.org/doc/html/rfc3021 agrees | 15:53 |
mason | Hm, no, I guess section 3.3 says to use 255.255.255.255 | 15:53 |
mason | Katje: ^ I'd try that for more potential correctness. | 15:54 |
mason | and hence futureproofing | 15:54 |
Katje | it won't configure the device if you leave the broadcast out | 15:55 |
GyrosGeier | ow | 15:56 |
mason | Katje: No, the RFC is evidently suggesting 255.255.255.255 as a broadcast. | 15:56 |
mason | section 3.3, talking about amending https://datatracker.ietf.org/doc/html/rfc2644 | 15:57 |
Katje | mason: thanks | 16:20 |
Katje | will ifx | 16:20 |
mason | Katje: Test anyway. It seems like it'd be the correct broadcast address based on what I linked, but that doesn't strictly mean it'd work. But it's worth testing. | 16:21 |
Katje | will do | 16:22 |
UsL | why is lynx so hard to setup? I'm trying to set it to use a proxy but whatever I try it will not use it. I've set ~/.lynxrc to use http(s)_proxy:127.0.0.1/localhost:numbers/port to no avail. I tested what I guess is an old method of putting /etc/lynx-sites.cfg with the same parameters in lynxrc. Nothing works. Does anyone have some experience with this? | 16:47 |
Katje | export http_proxy ? | 16:52 |
UsL | will that set it for all my stuff? I only want kynx to use proxy. Not wget or curl for example | 16:54 |
UsL | *lynkx | 16:54 |
UsL | ... | 16:54 |
UsL | or is there a better ncurses browser perhaps that makes sense.. I didn't think to look for that yet. | 16:55 |
schillingklaus | maybe w3m | 16:56 |
UsL | thanks. I'll look into it | 16:57 |
UsL | seems like w3m only does if environment is set to it. I guess I can give up on this. I'm not too keen to set my environment to globally use a Tor exit node if I can't control what will use it if that environment variable is set. | 17:18 |
UsL | makes me mad that setting "http_proxy:http://your.proxy.com:8080 to C:\Program Files (x86)\Lynx - web browser\lynx.cfg" works great for windows users. Good for them. Is lynx made for windows perhaps. | 17:33 |
sadsnork | UsL, could you start w3m [or lynx] with "export http_proxy=blahblah && w3m" and then it only applies to that browser? | 17:36 |
UsL | well, that did somethng. But gave me: "lynx: Can't access startfile" | 17:41 |
sadsnork | ohhh, is that because you need to specify the url on the command line? | 17:42 |
UsL | I guess so. SO, that is perhaps not ideal.. I guess I could do a switch for the environment to set http_ https_ on and off. Seems like the viable thing left to do | 17:44 |
user__ | What's the latest security update about? Reading headlines, something about Debian updates? | 17:44 |
user__ | Reading lwn.net: SEVEN new kernels? Wow? | 17:45 |
user__ | Do they really maintain seven kernels in parallel? | 17:45 |
user__ | [yes they do?!] | 17:53 |
pitriss | UsL: and how about creating alias in your shell config with "http_proxy=blahblah lynx" so it will always pass correct proxy variable just for that one command? | 18:20 |
UsL | yes, thanks. I am investigating which method would suit me best. Aliases or setting a switch for environment or what not. Well, the best would of course for .lunxrc do actually do what it claims here: https://lynx.invisible-island.net/lynx2.8.5/lynx_help/body.html#HTTP_PROXY but as that seems not to work for me in anyway or iteration... | 18:37 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!