| Afdal | hey guise does anyone have a easy way to make my desktop alert me when my CPU temperatures are too high | 00:14 |
|---|---|---|
| Afdal | running Xfce now | 00:14 |
| brocashelm | i think psensor does that | 00:16 |
| brocashelm | ^ afdal | 00:16 |
| buZz | sensors | grep Package | cowsay - | 00:17 |
| Afdal | givin it a look... | 00:17 |
| buZz | lol | 00:17 |
| Afdal | that's terminal | 00:17 |
| Afdal | which I'd need to keep looking at | 00:17 |
| buZz | life is terminal | 00:17 |
| Afdal | I need a desktop pop-up | 00:17 |
| buZz | you can popup from terminal | 00:17 |
| Afdal | to get in my face and tell me to cease the risky activity | 00:17 |
| buZz | i liked that 'growl' ecosystem, you can get notifications from multiple hosts on network to one display | 00:18 |
| Afdal | ah right, I've used psensor before | 00:18 |
| plasma41 | Afdal: There's probably a better existing tool, but you could make use of xfce4-genmon-plugin to periodically call a program to query the temperature and display the result in the panel. | 00:19 |
| buZz | gkrellm used to be popular too | 00:19 |
| buZz | or conky | 00:19 |
| Afdal | what's a simple desktop alarm that can play an audio file... | 00:20 |
| plasma41 | Afdal: You could right a custom script that calls aplay when it needs to sound the alarm | 00:21 |
| plasma41 | s/right/write/ | 00:21 |
| Afdal | ah yes aplay | 00:21 |
| Afdal | that'll work | 00:21 |
| Afdal | and psensor already has a feature to run a command on alert :) | 00:21 |
| buZz | :) | 00:21 |
| buZz | many roads to rome ;) | 00:22 |
| brocashelm | alarm-clock-applet :D | 00:22 |
| Afdal | alarm clock generally runs its own thing | 00:22 |
| Afdal | probably not suited to being called by other programs | 00:22 |
| * plasma41 actually knows how to spell but tends to accidentally lapse into writing phonetically when trying to quickly type a message on IRC. | 00:23 | |
| Afdal | hmm I don't see a setting in psensors for actually determining what the alarm threshold should be though @_@ | 00:24 |
| plasma41 | Sounds like a job for a shell script | 00:25 |
| brocashelm | i see it in "psensor preferences" menu | 00:26 |
| buZz | in /sys/class/thermal/ you have files for every sensor your kernel sees | 00:26 |
| brocashelm | in the alarm section | 00:27 |
| Afdal | oh, aha | 00:27 |
| Afdal | thx | 00:27 |
| buZz | a bash file can read a file and compare the number ez | 00:27 |
| brocashelm | it allows for high and low | 00:27 |
| Afdal | excellent | 00:28 |
| Afdal | this'll work | 00:28 |
| Afdal | thanks for the tips :) | 00:28 |
| brocashelm | no problem | 00:28 |
| Afdal | now if I could just get some new thermal paste and a better cooler -.- | 00:28 |
| plasma41 | :-) | 00:28 |
| brocashelm | have you also tried using the ondemand or powersave cpu governors with cpufreq? | 00:29 |
| brocashelm | but better cooler and new thermal paste could be the solution | 00:29 |
| Afdal | I honestly don't even know if overheating is the problem yet | 00:30 |
| Afdal | it's so frustrating to diagnose problems like this :( | 00:30 |
| brocashelm | i plan on replacing my stock coolers with noctua coolers | 00:30 |
| brocashelm | each cpu core stays at roughly 28-42 C on idle in a slightly cool room during a 100+ F summer day | 00:31 |
| brocashelm | which isn't terrible, but a cooler replacement would do wonders | 00:31 |
| brocashelm | so try that | 00:31 |
| Afdal | part of the issue | 00:32 |
| Afdal | I think... | 00:32 |
| brocashelm | or you can also check your bios diagnostics to see if there's a faulty connection with the fans | 00:32 |
| brocashelm | it happened a few times so i just reconnected them and it worked | 00:32 |
| Afdal | is that AMD's temperature sensor for this class of CPUs is always overreporting the value >:/ | 00:32 |
| brocashelm | which amd cpu are you using? | 00:32 |
| brocashelm | ryzen? | 00:32 |
| Afdal | FX-8350 | 00:32 |
| brocashelm | oh | 00:32 |
| brocashelm | i know my 3rd/4th gen intel i7 cpus are prone to high temps (55-65 C per core) if under load, but i can get them down to 30 C or 45 C if on laptops, so might just be a matter of checking your cpu governors and whatever else the kernel allows if on the software side | 00:33 |
| Afdal | I mean it's either that or I've been running this CPU chronically too hot for years since I installed it :( | 00:34 |
| brocashelm | cpufrequtils lets you set minimum and maximum frequencies for the cpu governor | 00:34 |
| Afdal | I don't even know what a cpu governor is | 00:34 |
| Afdal | ur talkin gibberish to me | 00:34 |
| brocashelm | is there any process in htop or similar you can vet for high cpu usage? | 00:34 |
| brocashelm | lol | 00:34 |
| brocashelm | it's part of what the linux kernel uses for setting frequencies on your cpu clock speeds | 00:35 |
| Afdal | where does htop monitor temp again... | 00:35 |
| brocashelm | i meant cpu usage in %, but htop does also track temps if you enable that (just per core, not per process) | 00:35 |
| brocashelm | you could also keep an open process of watch sensors while troubleshooting your cpu during boot | 00:36 |
| Afdal | ah there we go | 00:36 |
| Afdal | yeah htop lists dramatically different temperatures compared to lm-sensor output | 00:36 |
| Afdal | and psensors, sensors applet, etc. | 00:37 |
| Afdal | I don't understand why | 00:37 |
| brocashelm | i recommend installing cpupower if you want to keep your usage more controlled | 00:37 |
| brocashelm | that and thermald | 00:37 |
| Afdal | I'm very hesitant to do anything to try and control my CPU clock speeds | 00:37 |
| Afdal | I think I ruined my last CPU due to clocking stuff | 00:37 |
| brocashelm | yeah, just be careful if clocking too high/low | 00:38 |
| brocashelm | the governors should take care of sane values automatically if you check them | 00:38 |
| brocashelm | i always recommend using ondemand on a desktop and powersave on a laptop | 00:38 |
| brocashelm | stay within the allowable clock range and you should be safe | 00:39 |
| plasma41 | I have a circa-2010 Acer Aspire 5740 laptop which frequently crashed and overheated. I eventually deduced that the root cause was a manufacturing defect in that the plastic housing lacked intake vent holes over the fan, despite having vent-hole-shaped impressions at that location on the plastic housing. | 00:39 |
| plasma41 | Only time I've used a dremel to fix a computer habitually crashing. :-) | 00:40 |
| Afdal | :o | 00:40 |
| brocashelm | my core2 duos and quads still operate at respectably cooler speeds (e.g. 35 C per core if in a cooled room on idle) | 00:40 |
| brocashelm | probably a combination of hardware and software compatibility | 00:40 |
| brocashelm | those older amd processors sounded like they had too many issues until the ryzens (which are more temp-controlled and less power-hungry than some intels) | 00:41 |
| Afdal | yeah the FX processors were known for being inefficient | 00:41 |
| brocashelm | but you can work with you got from the software side to at least mitigate those high (i.e. anything above 60 C per core) temps | 00:42 |
| buZz | my desktop xeon e3 is constant 45C at idle but thats mostly because i put in some superquiet fan with shitpoor airflow | 00:42 |
| buZz | and its fine | 00:42 |
| buZz | helps my heat a bit in winter | 00:42 |
| Afdal | Sadly they are also the last fastest amd64 processors ever made before all the major manufacturers started inserting NSA backdoors | 00:42 |
| buZz | at max it ramps up a lot and still wouldnt overpower my music if playing, but in quiet i can hear it get a lot louder | 00:43 |
| Afdal | So I personally am using this until someone makes a good RISC replacement -_- | 00:43 |
| brocashelm | i got external usb cooling fans that i can only have outside the cases (motherboard doesn't support additional fans being placed, although can connect if given the 5-pin-to-4-pin connector) | 00:43 |
| buZz | Afdal: at least on some later cpus you can disable all payloads | 00:43 |
| Afdal | there's no way to be absolutely sure | 00:44 |
| brocashelm | so i would say consider new cooler and repasting, and then try again | 00:44 |
| buZz | plus you could always hunt for the special highlevelclearance only versions that lacked webcam and IntelME | 00:44 |
| Afdal | LOL | 00:44 |
| buZz | but those are superrare | 00:44 |
| buZz | you can see them existing in the X201 HMM pdf from lenovo ;) go through SKU lists for the motherboard | 00:44 |
| Afdal | well my cpu goes above 60 C regularly | 00:44 |
| Afdal | if sensor numbers are to be believed | 00:45 |
| buZz | i'd say anything under 75 is fine , lower is better but lower than environment gets you condensation ;) | 00:45 |
| Afdal | And I spotted an 82 C last night before my computer shut off again | 00:45 |
| brocashelm | ouch | 00:46 |
| buZz | yeah thats pretty high | 00:46 |
| buZz | have you checked if anything might be wrong mechanically? | 00:46 |
| Afdal | fans seem fine | 00:46 |
| buZz | like a cable hitting the fan, or big dust bunnies | 00:46 |
| Afdal | I did a little dusting | 00:46 |
| buZz | or heatsink not really touching cpu? | 00:46 |
| Afdal | not sure if it actually helped | 00:46 |
| Afdal | that's not something one can just check | 00:47 |
| buZz | or thermal transfer medium dried out? | 00:47 |
| Afdal | without full paste replacement | 00:47 |
| Afdal | so I'd need to get some more paste before that | 00:47 |
| buZz | yeah, or pads | 00:47 |
| buZz | but if its there for a long time already? it can dry out and loose effectiveness | 00:48 |
| buZz | btw 'heatsing not touching cpu' , you can test by slightly wobbling the heatsink | 00:48 |
| Afdal | it's been a few years | 00:48 |
| Afdal | lol no | 00:48 |
| buZz | ok | 00:48 |
| Afdal | if you do that you'll mess up the paste job | 00:48 |
| Afdal | why would that be a test? | 00:48 |
| buZz | if there's a corner that doesnt touch it, you'd feel it hit when wobbling | 00:49 |
| buZz | like a uneven chair or table | 00:49 |
| Afdal | you can't fix paste once it's been ruined, you've gotta wipe it all off and re-apply -_- | 00:50 |
| buZz | Afdal: right, but thats a seperate problem | 00:50 |
| buZz | and highly offtopic, i thought this was #hardware, sry ;) | 00:50 |
| Afdal | that channel suxxxx | 00:50 |
| Afdal | :) | 00:50 |
| Afdal | if it's the one I remember | 00:51 |
| Afdal | anywho, time to go back to pretending I don't have a problem | 00:51 |
| buZz | ^_^ | 00:51 |
| brocashelm | to get back on-topic, then just have a look at your cpufreq settings if you think you can cool down temps in the meantime | 00:53 |
| Afdal | nope, not messing with clockspeed ._. | 00:53 |
| brocashelm | ok | 00:53 |
| Afdal | just gonna have to cease my activities when I get a high temp warning | 00:54 |
| onefang | Soooo, if I understand correctly, I'm NOT about to screw up my complex networking by bringing down this particular VM that is now surplus to requirements. If I suddenly vanish, assume I'm swearing loudly and trying to fix it. | 01:57 |
| onefang | So far so good. B-) | 01:58 |
| systemdlete | can openssh-server be backported for chimaera? Currently it is at 8.4 and I'd like to get a more recent version | 02:15 |
| systemdlete | does that fall to debian? | 02:15 |
| Afdal | had the recent ssh vulnerability been patched at least? | 02:15 |
| Afdal | this one: https://www.openwall.com/lists/oss-security/2024/07/01/3 | 02:15 |
| systemdlete | not sure, but the 8.4 version is rather buggy | 02:16 |
| plasma41 | systemdlete: You can always try downloading daedalus's openssh source package and seeing if it will build on chimaera. | 03:28 |
| systemdlete | I know. I was just hoping someone else had already done this and shared it with the rest of the planet. | 03:29 |
| systemdlete | :D | 03:29 |
| systemdlete | I might try that. | 03:29 |
| plasma41 | I have several hand-rolled backports on my system, but openssh isn't one of them. | 03:31 |
| rwp | What's buggy about openssh 8.4? | 03:33 |
| fsmithred | Afdal, this shows which versions have been fixed: https://security-tracker.debian.org/tracker/CVE-2024-6387 | 03:35 |
| rwp | Hmm... Bookworm/Chimaera has no patch for it. :-( However it is harder to exploit and fail2ban should mitigate it too. | 03:36 |
| systemdlete | rwp: The SetEnv, when used within a block, does not work at all. Outside of a block, yes, but not within. Which makes it difficult to dial it in for specific users, etc. | 03:38 |
| systemdlete | not a huge problem but it would be nice to see it fixed | 03:38 |
| systemdlete | later versions do not seem to suffer this problem | 03:38 |
| rwp | Oh! I read that wrong. Bookworm/Chimaera has been patched for it with 1:9.2p1-2+deb12u3 so it's fixed there. | 03:38 |
| fsmithred | bookworm is daedalus | 03:40 |
| fsmithred | well, daedalus is bookworm, really. chimaera is bullseye, beowulf is buster and I will never forgive debian for naming three B's in a row. | 03:41 |
| brocashelm | the ABCs are easier to memorize | 03:41 |
| fsmithred | yeah, what a concept! | 03:42 |
| rwp | I also look at my chimaera system and it has 1:8.4p1-5+deb11u3 with a date of 21 Dec 2023 which is NOT the fixed version. | 03:42 |
| brocashelm | i think one of beowulf's last updates was for openssh | 03:43 |
| fsmithred | bullseye (security), bullseye1:8.4p1-5+deb11u3fixed | 03:43 |
| fsmithred | down where it shows the source, it says bullseye is not affected | 03:44 |
| brocashelm | for beowulf: Package: openssh-client (1:7.9p1-10+deb10u4) [security] | 03:44 |
| rwp | Log into your chimaera system and "zless /usr/share/doc/openssh-client/changelog.Debian.gz" and see what it says there. Mine says 1:8.4p1-5+deb11u3 -- 21 Dec 2023 which is well before this. | 03:44 |
| brocashelm | i could have sworn i saw it in a recent apt update | 03:44 |
| rwp | beowulf at 7.9 is earlier than the regression. So it would not be vulnerable. | 03:45 |
| rwp | "As mentioned in the advisory, the 32-bit sshd took around 10,000 guesses to hit a successful execution on average." so that's quite a high attack rate against a system's sshd port. | 03:47 |
| rwp | With a botnet it is possible to snowshoe attack a system at a rate below a fail2ban trigger limit. But... That still will take some days to successfully hit on a system. | 03:48 |
| fsmithred | I've had attacks that change ip address for every attempt. | 03:49 |
| fsmithred | before that I used the alternative to fail2ban | 03:50 |
| fsmithred | denyhosts | 03:50 |
| rwp | Since it is easy to patch I am surprised not to see a patch for oldstable already. | 03:50 |
| rwp | https://sources.debian.org/src/openssh/1:9.2p1-2+deb12u3/debian/patches/Disable-async-signal-unsafe-code-from-the-sshsigdie-.patch/ | 03:51 |
| brocashelm | maybe report it to the LTS team? | 03:52 |
| rwp | Seems straight forward. Me says jokingly since they simply ifdef out the problematic log call. | 03:52 |
| fsmithred | This regression was introduced in October 2020 (OpenSSH 8.5p1) | 03:53 |
| fsmithred | chimaera has 8.4 | 03:53 |
| Afdal | whew, good to know | 03:55 |
| rwp | Oh! Then that's it. Chimaera should not be listed as fixed but listed as not vulnerable. | 03:55 |
| Afdal | I did a softwhere update recently specifically hoping this ssh exploit was fixed | 03:55 |
| fsmithred | yeah, it says that down below on the source, but on the package the "fixed" is misleading | 03:56 |
| rwp | "Versions 4.4p1 up to, but not including 8.5p1 are not vulnerable to CVE-2024-6387 thanks to a patch for CVE-2006-5051, which secured a previously unsafe function." | 03:56 |
| systemdlete | rwp: Just a note--my issue is not related to the security issue. | 03:56 |
| systemdlete | Mine is a feature support issue, just to be clear. | 03:56 |
| systemdlete | minor, but annoying | 03:56 |
| rwp | systemdlete, So... Not buggy as stated but not yet including a newer feature? | 03:57 |
| systemdlete | no | 03:57 |
| * rwp glares over my glasses glaringly | 03:57 | |
| systemdlete | feature existed prior to 8.4 | 03:57 |
| systemdlete | buggy though, that's all | 03:57 |
| brocashelm | makes sense | 03:58 |
| systemdlete | what I am saying is that just because chimaera's version of ssh is not vulnerable to the security issue, I would still like to get newer ssh for the feature support | 03:58 |
| rwp | What's the bug? | 03:58 |
| brocashelm | so beowulf and chimaera use older, unaffected versions and didn't/don't need the patch | 03:58 |
| rwp | Yes. | 03:58 |
| systemdlete | within a match block, SetEnv does not work | 03:58 |
| systemdlete | (and that's SetEnv in sshd_config, not SendEnv in ssh_config) | 03:59 |
| systemdlete | it has been fixed in the 9.2 version we use on D. | 03:59 |
| brocashelm | just as the xz vulnerability bug didn't make its way into daedalus or older, but remained awhile in ceres/excalibur until it was found out | 03:59 |
| brocashelm | seems like a matter of timing on when the cve was a risk factor | 04:00 |
| rwp | I am trying to imagine what I would use SetEnv for inside of a Match block. I do use Match rather aggressively in an ssh firewall using ForcedCommand. | 04:00 |
| systemdlete | In my case, I want to override a default variable in a script, but only on a few systems. | 04:01 |
| systemdlete | There are other ways to accomplish this, but I like this one. | 04:02 |
| systemdlete | It works on D and forward(apparently) | 04:02 |
| systemdlete | I am also using forcedcommand | 04:03 |
| rwp | Quite often ssh is available in a backport. | 04:03 |
| systemdlete | this time not | 04:03 |
| systemdlete | but, if you find one, let me know :) | 04:04 |
| rwp | I am looking now... | 04:04 |
| systemdlete | I searched the devuan and debian packages and did not see one | 04:04 |
| systemdlete | but your eyes may be sharper | 04:04 |
| rwp | Nope. None available at this time. | 04:04 |
| systemdlete | like I said... | 04:05 |
| systemdlete | thanks for looking anyway. | 04:05 |
| systemdlete | I may try building my own | 04:05 |
| systemdlete | Is there a way to request a backport at Debian? I mean, without starting war | 04:06 |
| rwp | I might in the ForceCommand use "/usr/bin/env VARIABLE=VALUE theactualcommand" and workaround it that way? | 04:06 |
| systemdlete | hmmm. can you do that? | 04:07 |
| systemdlete | If so, that would be sufficient | 04:07 |
| rwp | Yes. But I could also imagine that the SetEnv was off to the side and not in the same matchblock as the ForceCommand, making that workaround less convenient because it still requires restructuring around the problem. | 04:07 |
| systemdlete | I thought forcecommand had to be one token | 04:07 |
| systemdlete | ? | 04:08 |
| systemdlete | off to the side? | 04:08 |
| rwp | Hmm... Looking... | 04:08 |
| rwp | If matching on a host then that might be separated from the setting of the ForceCommand. That's what I meant by off to the side. | 04:09 |
| systemdlete | I only wanted setenv varname=yada for a forced command in one block | 04:09 |
| systemdlete | match user soandso | 04:09 |
| rwp | I guess the way I am using ForceCommand it is always one token. Reading the docs... | 04:09 |
| systemdlete | setenv JACK=shhhht | 04:09 |
| systemdlete | ForceCommand /some/path/to/a/command | 04:10 |
| rwp | I had in my head that it was a full command line. You can tell me that it doesn't work that way and I will believe you. I need to test it but I had it in my head that a full command was placed there. | 04:11 |
| rwp | I'll try it but have to afk or a few minutes first due to stuff happening here. | 04:11 |
| systemdlete | nw | 04:11 |
| systemdlete | appreciate you looking into it | 04:11 |
| systemdlete | good to get a 2nd set of eyes on any problem | 04:11 |
| systemdlete | guess what rwp? You were right--it does seem to work | 04:15 |
| systemdlete | Yep. Just tried it in an actual scenario and it works. Thanks. | 04:18 |
| systemdlete | Because ForceCommand replaces whatever was requested (as per $SSH_ORIGINAL_COMMAND) that all parameters to the command were replaced with the one token. I think I got that notion because the docs say you can use $SSH_ORIGINAL_COMMAND to get the original parameters passed to the program originally requested. I got things jumbled a bit in my head | 04:22 |
| rwp | Oh good! And as far as jumbled goes, you just saw me get all jumbled up about which ssh versions were vulnable and that confused me greatly when the cve tracker said chimeara was "fixed" instead of not vulnerable and I went down the rabbit hole head first on that one. So no worries! :-) | 04:26 |
| srjose | Hi! Iǜe just upgraded to excalibur. | 11:15 |
| srjose | It has uninstalled virt-manager. It needs libvirt0 >= 10.2, but only 10.0 is avaiable | 11:17 |
| srjose | I see libvirt0 10.5 in debian testing repository, | 11:19 |
| sanitar | i was following this tutorial on configuring grub to boot the devuan-live iso on my hard drive (https://www.youtube.com/watch?v=oSW3xCN1_Yo&t=96). the iso wasn't able to boot and it sent me to a prompt where i had limited commands. it also said to use "debug" parameter to enable error messages. i thought that i had to change how grub boots the iso so it can boot properly. | 19:12 |
| sanitar | should i post the error messages or is there something up with my configuration on how grub boots the iso? | 19:14 |
| gnarface | well, the error message might help but i'm sure as hell not clicking on that | 19:14 |
| gnarface | someone here might know how to do what you're trying to do though, so stick around | 19:15 |
| fsmithred | sanitar, can you post your menuentry for the iso on paste.debian.net please? | 19:26 |
| fsmithred | I'll go look for a discussion on the forum that has examples. | 19:26 |
| sanitar | fsmithred: https://paste.debian.net/hidden/d290e56b/ | 19:28 |
| fsmithred | try this: https://dev1galaxy.org/viewtopic.php?pid=6176#p6176 | 19:31 |
| AlexLikeRock | hi people | 19:33 |
| AlexLikeRock | when start X11 , not work keyboar and mouse, at my OLD devuan . BUT they work fine at TTY . | 19:34 |
| AlexLikeRock | suggestions ? | 19:34 |
| fsmithred | xserver-xorg-input-all xserver-xorg-libinput | 19:36 |
| fsmithred | ^^^ install those | 19:36 |
| AlexLikeRock | ok , | 19:36 |
| fsmithred | did you do some kind of minimal install and then add xorg stuff? | 19:36 |
| AlexLikeRock | no | 19:37 |
| fsmithred | uh, were these things working before in the old devuan and then they stopped working? | 19:37 |
| AlexLikeRock | they are a fail upgrade/downgrade | 19:37 |
| fsmithred | then you need to check versions of all the xorg stuff and probably anything else related to graphical system | 19:38 |
| fsmithred | you tried to upgrade to excalibur and then downgrade to daedalus? | 19:39 |
| AlexLikeRock | old devuan = chiamera | 19:39 |
| fsmithred | ok so what was the upgrade/downgrade? | 19:39 |
| AlexLikeRock | i candt move to another vertion , i have alot problems with APT | 19:39 |
| AlexLikeRock | in this moment , i feeld stable with APT :-D | 19:40 |
| AlexLikeRock | I prefer to fix the keyboard problem manually than to fix APT. | 19:40 |
| AlexLikeRock | :-D | 19:40 |
| fsmithred | what did you try to upgrade? what did you try to downgrade? | 19:40 |
| fsmithred | ok, without knowing more about what you did, all I can say is undo what you did. | 19:42 |
| AlexLikeRock | i all ready did that "undo what i did "! | 19:45 |
| AlexLikeRock | you found the problem , | 19:59 |
| AlexLikeRock | aptitude purge xserver-xorg-input-all xserver-xorg-libinput | 19:59 |
| AlexLikeRock | No se puede encontrar ningún paquete cuyo nombre o descripción coincida con "xserver-xorg-libinput" | 19:59 |
| AlexLikeRock | its not installed | 19:59 |
| AlexLikeRock | apt : not found to install . | 20:02 |
| AlexLikeRock | "xserver-xorg-libinput" | 20:02 |
| AlexLikeRock | :-/ | 20:02 |
| fsmithred | I'm still curious about what you did. Was this just a normal upgrade within chimaera or were you trying to upgrade to daedalus and then back down again? | 20:02 |
| fsmithred | apt is not installed? | 20:02 |
| AlexLikeRock | yes | 20:03 |
| AlexLikeRock | its instaled , working 90% | 20:03 |
| AlexLikeRock | its in the repos of chimaera ? | 20:03 |
| fsmithred | what is? | 20:04 |
| AlexLikeRock | "xserver-xorg-libinput" | 20:04 |
| AlexLikeRock | xserver-xorg-libinput | 20:04 |
| fsmithred | xserver-xorg-input-libinput 1.2.1-1+b1 | 20:05 |
| AlexLikeRock | https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=xserver-xorg-libinput&x=submit | 20:05 |
| AlexLikeRock | not found at web page | 20:05 |
| AlexLikeRock | ¡? | 20:06 |
| fsmithred | oh, wrong version. I'm in daedalus. | 20:06 |
| AlexLikeRock | where you found ? | 20:06 |
| AlexLikeRock | yes | 20:06 |
| AlexLikeRock | im chimaera ! | 20:06 |
| fsmithred | apt search xserver-xorg | 20:06 |
| fsmithred | there might be some others you want | 20:06 |
| fsmithred | but I'm just guessing since I still don't know what you did. | 20:06 |
| AlexLikeRock | no xserver-xorg | 20:07 |
| AlexLikeRock | i need server-xorg-libinput | 20:07 |
| fsmithred | maybe you don't have any sources in sources.list? | 20:07 |
| AlexLikeRock | yes, i have | 20:07 |
| AlexLikeRock | well | 20:07 |
| AlexLikeRock | i think : the name change | 20:08 |
| fsmithred | in daedalus there are 53 packages in the repo that begin with "xserver-xorg" | 20:08 |
| fsmithred | there should be close to that number in chimaera | 20:09 |
| AlexLikeRock | from xserver-xorg-libinput to xserver-xorg-input-libinput{a} | 20:09 |
| AlexLikeRock | take a look | 20:09 |
| fsmithred | apt-cache search xserver- | 20:09 |
| AlexLikeRock | . | 20:09 |
| AlexLikeRock | aptitude install xserver-xorg-input-all xserver-xorg-libinput | 20:09 |
| AlexLikeRock | No se puede encontrar ningún paquete cuyo nombre o descripción coincida con "xserver-xorg-libinput" | 20:09 |
| AlexLikeRock | Unable to apply some actions, aborting | 20:09 |
| AlexLikeRock | root@DELL:~# aptitude install xserver-xorg-input-all | 20:09 |
| AlexLikeRock | Se instalarán los siguiente paquetes NUEVOS: | 20:09 |
| AlexLikeRock | xserver-xorg-input-all xserver-xorg-input-libinput{a} xserver-xorg-input-wacom{a} | 20:09 |
| AlexLikeRock | 0 paquetes actualizados, 3 nuevos instalados, 0 para eliminar y 0 sin actualizar. | 20:09 |
| AlexLikeRock | Necesito descargar 0 B/197 kB de ficheros. Después de desempaquetar se usarán 483 kB. | 20:09 |
| AlexLikeRock | ¿Quiere continuar? [Y/n/?] | 20:09 |
| fsmithred | don't paste many lines here | 20:09 |
| AlexLikeRock | ok, fine | 20:10 |
| fsmithred | use paste.debian.net | 20:10 |
| AlexLikeRock | ok, its intalled : xserver-xorg-input-libinput ya está instalado en la versión solicitada (0.30.0-1) | 20:10 |
| AlexLikeRock | xserver-xorg-input-all ya está instalado en la versión solicitada (1:7.7+22) | 20:11 |
| AlexLikeRock | , reboot and test the OLD DEVUAN | 20:11 |
| AlexLikeRock | INIT 6 | 20:11 |
| * AlexLikeRock command not found ! | 20:11 | |
| AlexLikeRock | init 6 | 20:11 |
| AlexLikeRock | hi | 20:47 |
| AlexLikeRock | fsmithred : not work keyboard with root user | 20:47 |
| fatal | # halt | 20:49 |
| AlexLikeRock | fsmithred, what do you think if we check the root permission s ? | 20:50 |
| AlexLikeRock | or check the log by chroot ? | 20:52 |
| fsmithred | I'll try asking my question a different way and maybe I'll get an answer. | 20:57 |
| fsmithred | AlexLikeRock, when was the last time you edited /etc/apt/sources.list? (Important note: answer the question, don't edit anything.) | 20:57 |
| AlexLikeRock | hahahahah | 20:59 |
| AlexLikeRock | ok, loading .... | 20:59 |
| AlexLikeRock | fsmithred, I came from jessie, upgraded to ASCII, then to BEOWOLF, | 21:03 |
| AlexLikeRock | then to chimaera, but I had a problem. | 21:03 |
| AlexLikeRock | so I upgraded to deadalus, but the problem persisted and I went back to chimaera, where it was more stable. | 21:03 |
| AlexLikeRock | all people : question ! : | 21:08 |
| AlexLikeRock | i can run KWIN witout Xorg ? | 21:08 |
| AlexLikeRock | my question come from : https://es.m.wikipedia.org/wiki/Archivo:Esquema_de_las_capas_de_la_interfaz_gr%C3%A1fica_de_usuario.svg | 21:09 |
| golinux | Did you do the usrmerge before moving to Daedalus? | 22:04 |
| golinux | https://www.devuan.org/os/announce/excalibur-usrmerge-announce-2024-02-20.html | 22:04 |
| golinux | Oops . . . scratch that . . . LOL! | 22:05 |
| AlexLikeRock | golinux, nop | 22:31 |
| AlexLikeRock | but im at chimaera | 22:31 |
| AlexLikeRock | its not problem , if merge at cimaera ? | 22:38 |
| fsmithred | AlexLikeRock, are you sure you don't have any daedalus packages installed? How did you downgrade? | 22:38 |
| AlexLikeRock | fsmithred, i dont now , | 22:38 |
| AlexLikeRock | how to check ? | 22:38 |
| AlexLikeRock | apt downgrade -force ?? | 22:38 |
| AlexLikeRock | hehehehe | 22:38 |
| fsmithred | you don't know how you un-did the upgrade to daedalus? | 22:40 |
| AlexLikeRock | just , edit sources.lst from Daedalus to chimaera | 22:44 |
| AlexLikeRock | and reinstall some ones pakages | 22:44 |
| fsmithred | aptitude search "?narrow(?installed,?not(?archive(oldstable)))" | 22:48 |
| fsmithred | ^^^ That will give you a list of installed packages that are not from chimaera. | 22:48 |
| fsmithred | Whatever is in that list, check some versions at pkginfo.devuan.org to see if they are from daedalus. | 22:49 |
| AlexLikeRock | i dond get it | 22:49 |
| AlexLikeRock | i dont get it | 22:49 |
| fsmithred | If you tried to upgrade to daedalus and then downgrade to chimaera, you may still have some daedalus packages installed. | 22:49 |
| AlexLikeRock | what its the exact comand | 22:49 |
| fsmithred | exact command to do what? | 22:50 |
| AlexLikeRock | yes | 22:50 |
| AlexLikeRock | ?narrow | 22:50 |
| fsmithred | to get the versions? | 22:50 |
| fsmithred | I don't know. See 'man aptitude' | 22:50 |
| AlexLikeRock | yes, get vertions of deadlua or chimaera | 22:50 |
| fsmithred | go to pkginfo.devuan.org and put the package name in the search bar. | 22:51 |
| fsmithred | on your system, 'dpkg -l <package name>' will show you the installed version. | 22:51 |
| AlexLikeRock | come on !!! pkginfo.devuan.org !!!!! | 22:52 |
| fsmithred | Do you know about pinning? You should pin chimaera to a priority of 1001 then update and upgrade. | 22:52 |
| AlexLikeRock | yes, pinning | 22:52 |
| AlexLikeRock | that its the solution | 22:52 |
| AlexLikeRock | let me test KDE | 22:53 |
| AlexLikeRock | fsmithred, its little confused | 23:41 |
| AlexLikeRock | https://wiki.debian.org/AptConfiguration | 23:41 |
| AlexLikeRock | http://paste.debian.net/1323214/ | 23:43 |
| AlexLikeRock | so... | 23:45 |
| AlexLikeRock | the example its : | 23:45 |
| AlexLikeRock | Package: claws-mail | 23:45 |
| AlexLikeRock | Pin: release a=stretch-backports | 23:45 |
| AlexLikeRock | Pin-Priority: 900 | 23:45 |
| AlexLikeRock | so... | 23:45 |
| AlexLikeRock | i must to do : | 23:45 |
| AlexLikeRock | Package: * | 23:46 |
| AlexLikeRock | Pin: release a=oldstable | 23:46 |
| AlexLikeRock | Pin-Priority: 1001 | 23:46 |
| AlexLikeRock | thats rigth ? fsmithred | 23:46 |
| fsmithred | not sure. I'd have to look at the man page, but if it's not right, it's very close to right. | 23:49 |
| fsmithred | I would use n=chimaera instead of a=oldstable | 23:51 |
| fsmithred | based on what I have in my preferences | 23:51 |
| AlexLikeRock | nano /etc/apt/preferences | 23:56 |
| fsmithred | you could put it in a file in preferences.d/ | 23:57 |
| AlexLikeRock | Package: * | 23:58 |
| AlexLikeRock | Pin: release a=oldstable | 23:58 |
| AlexLikeRock | Pin-Priority: 900 | 23:58 |
| AlexLikeRock | Package: * | 23:58 |
| AlexLikeRock | Pin: release a=stable | 23:58 |
| AlexLikeRock | Pin-Priority: 600 | 23:58 |
| fsmithred | I don't know if that will work. | 23:58 |
| fsmithred | I think that will prevent installation of anything from daedalus, but it won't remove anything from daedalus. | 23:59 |
| AlexLikeRock | me too, i dont now | 23:59 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!
