| onefang | systemdlete: needrestart is available on Devuan, I use it, works fine. Restarts services, and tells you if you need to restart other things, or if you need to reboot. | 00:19 |
|---|---|---|
| onefang | Features: | 00:20 |
| onefang | - supports (but does not require) systemd | 00:20 |
| onefang | - fully integrated into apt/dpkg using hooks | 00:20 |
| onefang | And other features. | 00:20 |
| systemdlete | doesn't seem to be available on my chimaera system. | 00:21 |
| onefang | I'm using it on chimaera. lol | 00:21 |
| systemdlete | so, which package is it part of, so I can install it too? | 00:21 |
| onefang | needrestart is the package. | 00:21 |
| systemdlete | I tried apt install needrestart, but it comes back empty | 00:22 |
| systemdlete | (doesn't find anything to install) | 00:22 |
| onefang | 3.5-4+deb11u1 (stable-security) is the version I have. | 00:22 |
| systemdlete | apt install needrestart doesn't work for me | 00:24 |
| onefang | 3.5-4+deb11u2 (stable) also available. | 00:24 |
| onefang | Odd. | 00:24 |
| onefang | https://packages.debian.org/bullseye/needrestart | 00:29 |
| onefang | https://lists.dyne.org/lurker/message/20221223.094016.f392eac7.es.html so I'm not the only one using it on Devuan. | 00:32 |
| onefang | You get output like this - | 00:35 |
| onefang | Running kernel seems to be up-to-date. | 00:35 |
| onefang | 00:35 | |
| onefang | The processor microcode seems to be up-to-date. | 00:35 |
| onefang | 00:35 | |
| onefang | No services need to be restarted. | 00:36 |
| onefang | 00:36 | |
| onefang | No containers need to be restarted. | 00:36 |
| onefang | 00:36 | |
| onefang | No user sessions are running outdated binaries. | 00:36 |
| onefang | Though if you do need to restart something, it'll tell you what. And for services you get a dialog so you can decide to not restart some if you need to, then it restarts those you said yes to. | 00:38 |
| systemdlete | https://pastebin.com/xisfaJW7 | 00:39 |
| onefang | chimaera main is where I got mine from. | 00:41 |
| onefang | I gotta pop out for a bit, before this next heatwave kicks in later today. | 00:45 |
| systemdlete | https://pastebin.com/iQExsTs5 | 00:51 |
| systemdlete | somehow my sources.list had references to pkgmaster for one of the repos | 01:31 |
| systemdlete | fixed that and now I can install needrestart | 01:31 |
| JFaulk | golinux paging Golinux, come in golinux, cleanup on isle #offtopic in dev1 forums | 02:33 |
| JFaulk | or ralph, either is fine | 02:34 |
| rwp | +1 for needrestart which is very good! I only ever use it in -b batch mode though. | 03:21 |
| rwp | It's great in general but it is annoying when it wants to wall to users who have a bash that it thinks needs to be restarted. | 03:22 |
| onefang | That is annoying, though usually it's the thing that bash is running that needs a restart. | 07:52 |
| Afdal | What does it mean when a Devuan desktop environment randomly and spontaneously closes everything and boots you to a display manager? | 08:11 |
| Afdal | It's exceedingly rare but I've had this happen more than once now | 08:11 |
| Afdal | Completely baffling to me what's causing it | 08:11 |
| Afdal | Could it be... a display driver crashing or something? And kicking one to a display manager login is its failsafe behavior? | 08:12 |
| onefang | Obvious questions first. Which desktop environment? Which display manager? Which graphics card? Which display driver? | 08:14 |
| Afdal | Xfce and whatever the default display manager is | 08:14 |
| onefang | Less obvious question. Did you check the X11 logs? | 08:14 |
| Afdal | think it might be lightdm | 08:15 |
| Afdal | AMD RX560 | 08:15 |
| Afdal | open source drivers... I think | 08:15 |
| Afdal | Where do I check my X11 logs | 08:15 |
| brocashelm | i got the same gpu. no issues here. using ceres | 08:15 |
| brocashelm | and i think devuan xfce ships with lxdm | 08:15 |
| onefang | I don't use xfce, so I can't help with that. | 08:16 |
| brocashelm | user-specific xfce logs are usually in ~/.local/share/xorg | 08:17 |
| brocashelm | for the rest of the system, check in /var/log | 08:17 |
| Afdal | hmm don't have that directory | 08:17 |
| onefang | The X11 system logs should be in /var/log/Xorg.0.log | 08:17 |
| Afdal | hmm lotta gibberish in here | 08:18 |
| Afdal | What kind of thing might I be looking for... | 08:18 |
| brocashelm | have you tried disabling the display manager and using tty, startx method? | 08:19 |
| brocashelm | did you create x11 configs for your amd/radeon gpu? | 08:19 |
| Afdal | No the former | 08:19 |
| Afdal | For what purpose? | 08:19 |
| Afdal | And no, not sure what X11 configs for my gpu even are | 08:20 |
| onefang | Any lines that have (EE) near the beginning are errors, so they might be informative. (WW) are warnings. | 08:21 |
| Afdal | hmm I don't have lines with either of those | 08:22 |
| Afdal | oh wait there's one | 08:22 |
| Afdal | no (EE)'s | 08:23 |
| Afdal | [ 9.264] (WW) Falling back to old probe method for modesetting | 08:23 |
| Afdal | [ 9.264] (WW) Falling back to old probe method for fbdev | 08:23 |
| Afdal | there's these, but I don't think they're that suspicious | 08:23 |
| onefang | Only (WW) I have is warning my a directory for a cyrrilic font doesn't exist. I'm fine with that, I don't know the language. | 08:24 |
| Afdal | Yeah I have that cyrrilic warning too | 08:24 |
| Afdal | Well let me ask this | 08:24 |
| Afdal | Does this sound like a generalized X11 crash | 08:25 |
| Afdal | or a desktop environment crash? | 08:25 |
| brocashelm | well, so you could see if it's still your desktop environment or your display manager is causing problems | 08:25 |
| brocashelm | IME, display managers are unreliable and never work as they should | 08:25 |
| Afdal | I don't even use my display manager anyway | 08:25 |
| Afdal | Only time I ever see it is when something like this happens | 08:25 |
| brocashelm | then it could be your desktop environment | 08:26 |
| onefang | It's sunset on Saturday and so for this weekend I haven't done any weekending. So I'll leave you in the hands of brocashelm and whoever else might pipe up. | 08:26 |
| * onefang gets back to his music. | 08:26 | |
| Afdal | {: | 08:26 |
| brocashelm | as for the gpu config files, i find they're helpful depending on your hardware or some other limitations to work around with them | 08:26 |
| brocashelm | do you have anything under /etc/X11/xorg.conf.d? | 08:27 |
| Afdal | nope, empty | 08:27 |
| brocashelm | i wonder if it's some acpi-related error | 08:32 |
| brocashelm | what does this command say? pgrep -l acpi | 08:32 |
| Afdal | 100 acpi_thermal_pm | 08:35 |
| Afdal | 1436 acpi_fakekeyd | 08:35 |
| Afdal | 1551 acpid | 08:35 |
| Afdal | Whatever those mean... | 08:35 |
| brocashelm | how about: ps -eaf | grep acpi | 08:37 |
| brocashelm | just to confirm if it's running | 08:37 |
| Afdal | What would confirm it? | 08:37 |
| Afdal | root 100 2 0 00:08 ? 00:00:00 [acpi_thermal_pm] | 08:37 |
| Afdal | root 1436 1 0 00:08 ? 00:00:00 /usr/sbin/acpi_fakekeyd | 08:37 |
| Afdal | root 1551 1 0 00:08 ? 00:00:00 /usr/sbin/acpid | 08:37 |
| Afdal | afdal 3369 3357 0 00:37 pts/0 00:00:00 grep --color=auto acpi | 08:37 |
| brocashelm | if not, you can try to force it during the system boot by adding this to your grub line for the kernel you've selected (i.e. when you reboot): apci=force | 08:38 |
| brocashelm | looks like it's running | 08:38 |
| brocashelm | have you tested running devuan without a gpu, or a different gpu? and still the same errors? | 08:38 |
| Afdal | hmm | 08:39 |
| Afdal | How would I do that... | 08:39 |
| Afdal | Without pulling my GPU out | 08:39 |
| brocashelm | if it is the gpu, you might be able to manually configure it for xorg. archwiki has a basic guide on that | 08:39 |
| brocashelm | https://wiki.archlinux.org/title/AMDGPU#Xorg_configuration | 08:39 |
| brocashelm | this section in particular | 08:39 |
| Afdal | I don't see why any of this would be necessary | 08:39 |
| Afdal | I've got a standard GPU with pretty standard settings | 08:40 |
| brocashelm | maybe you could try seeing if it is the gpu or the amdgpu driver is not being loaded correctly | 08:41 |
| Afdal | You know now that my memory is coming back | 08:41 |
| Afdal | I think I had this thing happen back on Ubuntu too | 08:41 |
| Afdal | years ago | 08:42 |
| Afdal | Extremely rare | 08:43 |
| brocashelm | i think it could be some modprobe issue | 08:44 |
| brocashelm | have you run sudo sensors-detect and reviewed all prompts to be sure? | 08:44 |
| onefang | Might also be a hardware issue. Something's not quite up to spec, and fails sometimes. | 08:44 |
| brocashelm | gpu could be failing or not installed properly | 08:45 |
| brocashelm | what cpu are you using again? | 08:46 |
| Afdal | FX-8350 | 08:46 |
| Afdal | old AM3+ Piledriver CPU | 08:47 |
| brocashelm | i think the pairing might've been part of the problem, just checking around some bottlenecking sites | 08:50 |
| Afdal | My CPU with my GPU? | 08:50 |
| brocashelm | yes | 08:50 |
| Afdal | seems sus... | 08:50 |
| brocashelm | i've used rx 560 with ryzen 5 3600 (am4) and had no issues | 08:51 |
| brocashelm | then again, my rx 560 also works with i7-3770 (came out in 2013 iirc) | 08:51 |
| Afdal | I generally have no issues too | 08:51 |
| Afdal | this is very, very rare... | 08:51 |
| brocashelm | maybe it is some modesetting or modprobe error in your graphical session | 08:51 |
| brocashelm | something isn't properly configured | 08:51 |
| Afdal | hmm | 08:52 |
| brocashelm | i still recommend giving the amdgpu and radeon configs a try for xorg | 08:52 |
| Afdal | From the arch wiki? | 08:52 |
| brocashelm | yeah, there are some options you can choose | 08:52 |
| Afdal | I guess I'll have a look at that later... | 08:52 |
| brocashelm | have you tried using a backported kernel? | 08:54 |
| Afdal | Eh? No... | 08:54 |
| brocashelm | assuming you are using stable and thus the non-backported kernel, you could try checking if your issues persist on a backported kernel... | 08:55 |
| Afdal | lol yeah I mean | 08:56 |
| Afdal | I could... | 08:56 |
| Afdal | but this is so incredibly rare | 08:56 |
| brocashelm | and if issues still persist, then we can go back to considering some hardware/gpu/cpu problems | 08:56 |
| Afdal | It could never happen again in the next six months and I wouldn't really know if it's been solved or not | 08:56 |
| brocashelm | hmmm... yeah | 08:57 |
| brocashelm | i have had xorg crap on me with unhelpful error messages, but that was usually due to bad drivers that i reverted afterwards or got a fix for | 08:57 |
| Afdal | Every time this happens I get scared that I've been pwned | 08:58 |
| Afdal | and someone is trying to phish for my user password | 08:59 |
| brocashelm | oh. there are tools like lynis if you are worried about security | 09:00 |
| brocashelm | but it's usually not the case | 09:00 |
| brocashelm | just some bad mismatch in hardware/drivers/modules/etc. | 09:00 |
| brocashelm | and as you said, your issue is very rare, so you might not know for sure if it's been fixed or not | 09:00 |
| brocashelm | you can only try to apply workarounds and wait and see | 09:00 |
| xisop | i just did an apt-get upgrade which installed a newer kernel.. 5.10.0-21 from 5.10.0-9-amd64 | 09:30 |
| xisop | as a result, i can no longer boot my system as mdadm is blocking it | 09:30 |
| xisop | i am unaware of an active raid in my system.. from what i can tell, i have 2 partitions on one driv.e. a boot and a root partition | 09:31 |
| gnarface | the old kernel might still be installed | 09:32 |
| gnarface | check the grub menu | 09:32 |
| xisop | well it is, it's the only way i can boot into this | 09:32 |
| xisop | mdadm: no devices listed in conf file were found | 09:33 |
| gnarface | hmm | 09:34 |
| gnarface | is there a /etc/defaults/mdadm? | 09:34 |
| xisop | yes | 09:34 |
| gnarface | open it in a text editor; see if it has a option to disable | 09:34 |
| user24037 | hey, what is start_daemon -p $THIS $THAT $THEOTHER in /etc/init.d/cron ? that's not the /sbin/start-stop-daemon...hmm | 09:35 |
| xisop | gnarface: k, time to reboot. i | 09:35 |
| user24037 | the variables i understand. but what is the command start_daemon -p in /etc/init.d/cron around line 80. tyty :] | 09:37 |
| user24037 | some kind of legacy thing? i notcied shellcheck has complaints about the script | 09:38 |
| user24037 | i want to to run cron in its own network namespace. my isp blocks port 25. | 09:40 |
| gnarface | user24037: they're defined at the top of the file starting around like 20 | 10:01 |
| gnarface | the second question doesn't make sense, you should only need to communicate with cron locally | 10:02 |
| user24037 | yes, the variables are definied at the top. those are fine. but what is 'start_daemon'? i don't find that in my path | 10:03 |
| user24037 | thank you for the help | 10:05 |
| user24037 | cron will run sendmail, but sendmail wont work with my default interface | 10:06 |
| gnarface | ah, start_daemon is a shell function, something near the top is including a library of shell script functions too | 10:07 |
| gnarface | and in a default installation, cron is probably actually running the sendmail command-line emulation wrapper script from exim4, so if you need to make cron mail off the system from a different port besides 25 then you need to edit the exim4 configuration | 10:07 |
| user24037 | oh, i knew this. start_daemon is sourced from /lib/lsb/init-functions | 10:09 |
| user24037 | tyty again | 10:09 |
| gnarface | note that you don't want to edit the exim4 config directly. it is auto-generated. you edit the file /etc/exim4/update-exim4.conf.conf then run update-exim4.conf (yes, those extra .confs aren't typos) | 10:10 |
| gnarface | if that doesn't let you do what you want, try "dpkg-reconfigure exim4-config" as root | 10:12 |
| gnarface | and if that still doesn't let you do what you want, try editing the /etc/defaults/exim4 file | 10:12 |
| gnarface | editing the generated config should be a last resort | 10:13 |
| gnarface | pretty sure one of the first options will work though | 10:13 |
| user24037 | thank you. i'll have to see what this is for bsd sendmail. ill have a look | 10:14 |
| gnarface | if it's actually sendmail and not just a exim4 script to make it look like sendmail, the config will be completely different | 10:15 |
| user24037 | ye sendmail is my mta | 10:15 |
| gnarface | something like dpkg-reconfigure sendmail might work | 10:15 |
| user24037 | with my isp blocking port 25, it doesn't matter what source port i use. | 10:24 |
| user24037 | my mta can't reach out on that network. but ye :] i'll just make another network for it | 10:25 |
| user24037 | or ill try >_< | 10:33 |
| onefang | Does your ISP block the SSL email port? | 10:54 |
| user24037 | good thinking >_< it does not, and i can get the server's 220 SMTPD message. | 11:07 |
| onefang | bb|hcb suggested I use the timeout command for apt-panopticon, which I've been trying out since yesterday. The docs say it returns a status of "124" if it had to TERM the process, but "128+9" if you used the -k option to KILL it if the TERM didn't work. I'm getting 124 and 0 respectively. | 13:28 |
| onefang | The "128+9" notation is odd, why not just say "137"? Or is it implying it's returning a string somewhere, and the return status I'm checking isn't getting that? | 13:30 |
| onefang | Or maybe it's just that my test case isn't triggering the KILL option, coz the TERM option is actually working. | 13:31 |
| onefang | Ah the KILL does send 137. | 13:34 |
| phogg | notation like "127+9" is sometimes used to express a series of base exit codes plus offsets, to make their relationship with each other more clear. I wouldn't call it common, but it's not novel. It does just mean 137. | 14:58 |
| RhineDevil | I'm on devuan testing and plasma doesn't lock the screen after few minutes pass, what can I do? | 16:37 |
| gnarface | never used it, did you check the settings? | 16:43 |
| RhineDevil | gnarface: yeah I didn't find a clue about why happens | 17:11 |
| RhineDevil | in fact I didn't even find a setting properly saying "screen locks" | 17:12 |
| gnarface | maybe you need to install some optional package? | 17:13 |
| RhineDevil | gnarface: honestly I have no idea | 17:13 |
| gnarface | apt-cache search ^kde | 17:13 |
| gnarface | maybe? | 17:13 |
| RhineDevil | gnarface: little issue: it doesn't show packages who aren't installed | 17:26 |
| gnarface | apt-cache search certainly will | 17:26 |
| gnarface | run "apt-get update" once | 17:26 |
| fsmithred | System setting, Power Management, Energy Saving, Suspend Session, Automaticall... Lock Screen | 17:37 |
| fsmithred | RhineDevil, ^^^ | 17:37 |
| brocashelm | i've had problems using plasma on ceres | 23:34 |
| brocashelm | (to rhinedevil's question above) | 23:35 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!