| FlibberTGibbet | Hi Golinux! I was off in MX Linux land for a while, but I'm back now :) | 00:43 |
|---|---|---|
| golinux | FlibberTGibbet: Welcome home! | 00:45 |
| FlibberTGibbet | Thanks! Raising a glass to OSes that don't accidently change init systems without warning... | 00:46 |
| brocashelm | flibbertgibbet: daedalus is excellent; been with it since switching out of ceres (right around the freeze) | 02:18 |
| brocashelm | backports already has 6.4 kernel, and upstream lts is 6.5 or 6.6 by now | 02:18 |
| fluffywolf | my daedalus laptop has X and/or xfce crash on suspend, haven't troubleshooted why yet | 02:19 |
| brocashelm | a fair middle ground between stability and newer packages | 02:19 |
| brocashelm | my lappies have no issues with suspend; it's hibernate and the hybrids that fail | 02:19 |
| brocashelm | have you checked your xorg logs? | 02:19 |
| fluffywolf | no, that would be a step of troubleshooting why. | 02:23 |
| fluffywolf | which, as I said, I haven't done yet. lol | 02:23 |
| fluffywolf | is hibernate failing, or simply not working? | 02:25 |
| fluffywolf | I learned a couple weeks ago that modern kernels won't hibernate if secureboot is on. | 02:26 |
| brocashelm | it tries to hibernate, then displays my desktop, then "displays off"; i turn it back on again and it's back to the boot (shut down) | 02:26 |
| brocashelm | so i don't fuck with it anymore, even after adding adequate swap | 02:26 |
| brocashelm | doesn't matter the distro or init (devuan with runit or salix with sysvinit; all the same) | 02:26 |
| brocashelm | maybe that's a "pro" of systemd (hibernate working as it should), but it ain't worth it | 02:27 |
| brocashelm | i always disable secureboot and enable legacy/bios whenever possible | 02:27 |
| brocashelm | my salix lappy is uefi-locked, but secureboot is off | 02:27 |
| D-HUND | here Daedalus works really well IF it's a fresh install. any upgraded from Chimaera installation has some odd issues. one of them, I am unable to compile FGFS. this happens on several test istallations on my laptop as well as inside a VM on my dsktop PC. | 02:36 |
| fsmithred | fluffywolf, try xserver-xorg-core from daedalus-proposed-updates | 02:36 |
| fsmithred | 2:21.1.7-3devuan2 | 02:37 |
| D-HUND | this VM is explicitly made for compiling FGFS so there's no special ćonfiguration on my part and only the std. install plus the FGFS dependencies. | 02:37 |
| brocashelm | i started on beowulf and went straight to chimaera (when it was testing) and right after that ceres, then waited for daedalus to go stable, and simply checked my package versions to meet the correct repo | 02:39 |
| D-HUND | that's what I do, too | 02:40 |
| D-HUND | oh, wait, no. no testing involved here | 02:41 |
| brocashelm | i didn't want to have to go through the rituals of reinstalling and carefully checking which configs i wanted to change | 02:43 |
| brocashelm | but, it works after all those major upgrade bumps | 02:43 |
| brocashelm | i might return to ceres when things are more sorted out next year, and then wait for excalibur's freeze | 02:44 |
| oz4ga | Is it me ? or is there no xrdp in chimera ? | 17:56 |
| oz4ga | if so why? | 17:56 |
| fsmithred | oz4ga, 0.9.12-1.1+devuan2 should be there in chimaera main. | 18:15 |
| oz4ga | "some body" has fiddeled with my sources.list <-- of cause | 18:22 |
| oz4ga | DOH ! | 18:22 |
| oz4ga | yes sir. I\ve shot my self in the foot. problem solved now | 18:29 |
| oz4ga | most anoying having to think your self :D | 18:30 |
| catchthemonster | Hi, sorry to intrude. Just installed devuan daedalus. I have zwave USB dongle and tty device is constantly changing on soft reset of the device! udev rules is an issue but I downloaded /usr/lib/udev/rules.d/60-serial.rules and reloaded the rules and still /dev/serial/by-id/device is diapering and reappearing linked to different soft link | 19:14 |
| catchthemonster | (/dev/ttyACM0 or 1) I do have latest udev. What is the fix for this issue, as I can use dongle at this point ... | 19:14 |
| rwp | catchthemonster, If I read you correctly the device just sitting there is resetting, detaching from the USB bus, attaching to the USB bus, frequently? This is causing the device name to bounce around? | 19:42 |
| rwp | That sounds like a hardware problem to me. Are there any clues as to the issue in the /var/log/syslog file? | 19:43 |
| rwp | Even if you were to create specific rules to lock it to a specific name it seems to me it would still be a problem because that specific name would be disappearing and appearing and unavailable when dissappeared. | 19:43 |
| rwp | catchthemonster, A quick web wisdom search turned up this. Is this the same problem, or similar problem, you are having? https://github.com/openhab/org.openhab.binding.zwave/issues/1059 | 19:49 |
| catchthemonster | rwp, device is despairing and repairing as different device, it is legit issue on Debian, According to The commit is backported to v252 as systemd/systemd-stable@dafd733, which is included in v252.1. but I am not interested in that (systemd) | 19:58 |
| rwp | Since Devuan *is* Debian for all packages that are not required to be forked due to systemd then if this is a known problem in Debian then that problem will be inherited into Devuan too. | 20:00 |
| catchthemonster | and definitely is not an issue with device... it is udev issue ... | 20:00 |
| rwp | When the problem is fixed in Debian it will result in being fixed in Devuan too. | 20:00 |
| rwp | If it is a udev bug then that might be different due to the (e)udev forking. | 20:01 |
| catchthemonster | it is fixed for systemd, as I pointed out v252, but that will never go into devuan, right. So what is going to give. I really don't want back to systemd... | 20:03 |
| rwp | None of us want to use systemd. That's why we are here. Do not despair. | 20:04 |
| catchthemonster | Do I go to udev list to ask...? I mean I run automation of the house, and I am housed right now as I can't get the device to work, period ... this is what some did but it does not work for me https://www.thushanfernando.com/posts/2023/missing-serial-by-id/ | 20:06 |
| rwp | That report is talking about a /dev/serial/by-id feature. Is that actually what you are needing? Instead of preventing the USB device detaching and attaching? | 20:10 |
| rwp | First let me say that I don't know. I am just someone who is reading what you are typing and trying to help give you someone to discuss this problem. | 20:11 |
| rwp | But I don't really understand what problem you are having and I don't know a fix for it. I am simply a long time user, admin, developer, who is trying to give you some help. | 20:11 |
| rwp | Help for a problem I have never heard of before you mentioned it a few moments ago for a device I have never seen or touched. | 20:11 |
| rwp | Please do not despair if I don't have an answer for you immediately. I'll probably not ever have an answer for you. But someone else might. You might be able to figure it out for yourself. | 20:12 |
| rwp | Also IRC is just a room full of people who are chatting *at this moment*. The people here arrive and depart from the channel as their timezones and schedules apply. The knowledge base of people active is constantly changing. | 20:14 |
| rwp | A more persistent source of knowledge and wisdom is traditionally the mailing lists and web forums. Since those are more persistent by nature. Asking on a mailing list would be my suggestion. | 20:15 |
| catchthemonster | rwp, thank no worries ... The problem is issue is more complex due to udev, but will see, hopefully I will be able to fix it on my own. i did mailing list too ... thanks | 20:16 |
| rwp | The usual protocol on IRC is that if someone does not know at this hour of the day then wait an hour or two and then ask your question again. Different people will be in the channel by then and those different people will have different skills and knowledge and might know then. | 20:17 |
| rwp | For others who wish to help I suggest starting here: https://github.com/systemd/systemd/pull/25246 | 20:19 |
| rwp | Also it appears another user is experiencing the same problem and it is as yet unresolved: https://github.com/systemd/systemd/issues/29201 | 20:25 |
| bb|hcb | rwp: That patch for rules.d/60-serial.rules should be applicable to eudev, if catchthemonster appears again, ask them to test with this patch | 23:01 |
| rwp | bb|hcb, At :14 catchthemonster said they tried it and it did not work for them. So... I don't know anything more. | 23:06 |
| rwp | If the device is detaching and attaching that seems bad though even if the device name is fixed. Definitely not good anyway. | 23:07 |
| rwp | Heads up for Ceres Unstable: munin-node: logrotate.d/munin-node should call invoke-rc.d https://bugs.debian.org/1053379 | 23:29 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!