00:00.00 | fsmithred | check anto's version too. (hezeh) It might be fixed there. He backports mate and cinnamon for devuan. |
00:00.02 | systemdlete | yes, I have had decent luck with xfce nearly everywhere. lxde and lxqt have been somewhat less reliable. Sometimes I found they didn't have all the pieces |
00:00.14 | systemdlete | ok, will do. |
00:01.01 | systemdlete | fsmithred: Is the fact I installed using star not devuan matter? I'm thinking that's mainly installer choice. They all use the same repos, right? |
00:01.28 | fsmithred | afaik |
00:01.36 | fsmithred | look in sources.list |
00:02.11 | fsmithred | yeah, I do know. Star is just devuan. |
00:02.33 | systemdlete | they are the same. |
00:02.57 | systemdlete | I'll give hezeh a go |
00:03.06 | systemdlete | thanks for your patience again fsmithred! |
00:03.08 | fsmithred | dpkg -l task-mate-desktop |
00:03.15 | fsmithred | see if the metapackage is installed |
00:03.52 | systemdlete | dpkg-query: no packages found matching task-mate-desktop |
00:04.08 | systemdlete | I think I might have installed it differently, but idr now |
00:04.28 | fsmithred | cool |
00:04.37 | fsmithred | that'll make it easier to remove stuff |
00:09.05 | systemdlete | antofox-keyrings is missing? |
00:09.15 | systemdlete | do I need to contact the dev? |
00:09.43 | systemdlete | apt-get install antofox-keyrings --allow-unauthenticated |
00:09.54 | systemdlete | (instructions on page at hezeh.org) |
00:10.06 | systemdlete | btw, there is no www.hezeh.org, only hezeh.org, it seems |
00:10.30 | systemdlete | other than that, the update worked, but gave me the error about needing the key. So I did that and got this error |
00:10.53 | fsmithred | add the key and then apt update again |
00:11.21 | systemdlete | can I use the keyserver instead of his instructions? |
00:11.43 | fsmithred | use what keyserver? |
00:11.55 | systemdlete | keys.gnupg.net |
00:12.12 | fsmithred | I think I downloaded it from his site directly |
00:12.37 | systemdlete | well, the instructions at his page are not working for me. I'll try adding the key with the method I know |
00:13.15 | fsmithred | http://hezeh.org/packages/pool/main/a/antofox-keyrings/ |
00:13.32 | fsmithred | download the .deb and install with dpkg |
00:19.02 | systemdlete | that worked to fix the key issue. Thanks. |
00:19.15 | systemdlete | But following his instructions doesn't seem to work. Yours do. |
00:20.36 | systemdlete | he wants me to install mate-desktop-environment, but after the apt update, apt already knows I want to update all the mate packages. |
00:20.58 | systemdlete | Can I just do the update, and skip the mate-desktop-environment? |
00:21.04 | fsmithred | probably |
00:21.11 | fsmithred | is that package already installed? |
00:21.12 | systemdlete | I see that apt wants to install all the 1.22 packages anyway |
00:21.16 | systemdlete | not sure |
00:21.36 | fsmithred | dpkg -l |grep mate |
00:21.42 | systemdlete | yes. It says it already has latest version |
00:21.52 | fsmithred | will show you all the installed packages with mate in the name |
00:22.15 | fsmithred | gotta go. bbl. |
00:35.32 | *** join/#devuan n4dir (~n4dir@mue-88-130-57-211.dsl.tropolys.de) |
00:49.39 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
01:16.32 | *** join/#devuan tarbz2 (~Thunderbi@unaffiliated/targz) |
01:40.45 | systemdlete | fsmithred: I upgraded one of my 2 star VM's and running my memory leak script for a few hours |
01:43.00 | systemdlete | and re-enabled the "show seconds" just to be sure that works right now. |
01:43.19 | systemdlete | and I am seeing 132 byte increases in memory by the panel again. |
01:44.14 | Xenguy | systemdlete: How do you typically monitor the memory leakage in MATE. I confess I haven't been able to detect any memory problems with MATE, but I'm only looking on Ascii so far |
01:44.21 | systemdlete | Looks like about once every 1m 20s |
01:44.30 | Xenguy | er, leakage in mate-panel |
01:44.40 | systemdlete | Xenguy: I have a memory leak script I wrote myself. |
01:44.54 | Xenguy | huh, ok |
01:46.18 | systemdlete | Xenguy: The leak is very tiny, so it is mostly unnoticeable. Trouble is, over a day or so, that can amount to several 100MBs of growth. After a few days or maybe weeks, it creates an OOM condition and all heck follows |
01:47.20 | Xenguy | OK, will keep an eye on it as best I can, but so far so good |
01:50.06 | systemdlete | (it could just be something local here, though so many others have reported it also, so it is not likely) |
01:55.41 | *** join/#devuan pablocastellanos (~emergency@li79-248.members.linode.com) |
01:58.46 | systemdlete | Interesting to note that both mate-panel AND the clock applet are increasing by these 132 byte increments, though the clock not as frequently. |
01:59.30 | systemdlete | More interesting yet is that the increases are not coming on the minute, but at varying times (number of seconds after the minute). |
01:59.54 | systemdlete | So one has to wonder how/why these tiny memory increases are occurring. |
02:02.34 | mason | systemdlete: Bad programming. |
02:03.31 | *** join/#devuan fifiobarun (~monsieur@cpc80981-perr17-2-0-cust753.19-1.cable.virginm.net) |
02:05.53 | systemdlete | mason: y'think? lol. yeah |
02:06.04 | n4dir | did you shellcheck it? |
02:07.15 | n4dir | if it is bash or such. didn't fully understand it. But sure ain't hard to screw such |
02:07.33 | mason | systemdlete: It can be hard to track that sort of thing. Might be an actual memory leak, or it could be bookkeeping without realistic self-awareness. |
02:10.08 | *** join/#devuan tallship__ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
02:10.09 | systemdlete | what does that mean? |
02:10.54 | systemdlete | I would hope that frameworks for building things like desktop environments would offer some sort of memory use profiling. If nothing else, aren't there linters out there to do that sort of thing? |
02:12.40 | systemdlete | n4dir: This is a perl script, and it is not the target we are looking at. My script scans ps output every so many seconds |
02:13.11 | systemdlete | the target is mate-panel, and this is a known problem up until at least 1.24 (the latest according to mate devs) |
02:13.27 | systemdlete | mate-panel is part of the MATE DE |
02:13.27 | n4dir | get rid of mate panel then? |
02:14.26 | systemdlete | Or just get rid of computers altogether why don't we. That is CERTAIN to eliminate all bugs and security problems, right? |
02:14.44 | n4dir | you sure can use different panels or none at all in other DE's. iirc |
02:14.44 | systemdlete | :p |
02:15.24 | systemdlete | In that case, I'd rather just turn to a different DE altogether. But this is an interesting issue, and I kinda like MATE, ok? |
02:15.50 | n4dir | and why investigate a known problem? |
02:16.35 | n4dir | to me Mate didn't look outstanding ressource friendly in general |
02:17.17 | mason | systemdlete: What I mean is, it might not be a memory leak in the sense of an error. It might be bad design insofar as it doesn't consider memory over time for little book-keeping details. I don't know - I don't use the stuff. |
02:49.44 | systemdlete | I still don't follow. A memory leak is caused by not ensuring that memory is released once it is no longer needed. |
02:50.41 | systemdlete | Or are you saying that the panel needs 132 more bytes of memory every few minutes because it is keeping a log of some sort internally? |
02:57.09 | systemdlete | I agree with you that there is a basic design and/or implementation problem with it. |
02:58.08 | *** join/#devuan n4dir (~n4dir@88.130.152.196) |
02:58.28 | systemdlete | n4dir: We were not investigating a known problem per se. We were investigating whether the 1.22 version had the corrections their devs referred to. It was worth a try. |
03:07.16 | *** join/#devuan maggotbrain (~maggotbra@c-73-254-248-250.hsd1.wa.comcast.net) |
03:07.56 | *** join/#devuan disillusion (disillusio@gateway/vpn/privateinternetaccess/disillusion) |
03:08.41 | clort | sorry i missed your question n4dir |
03:09.17 | clort | new youtube-dl works for me |
03:13.25 | n4dir | i could give you the link, if you need: Kunst in Aktion. It is quite ok |
03:15.20 | *** join/#devuan RamboCommando (~lain@2603-7080-823b-f283-39cc-6719-dbc7-eebc.res6.spectrum.com) |
03:31.42 | *** join/#devuan D-HUND (~debdog@2a00:79c0:612:1a00:7a24:afff:fe8a:d04d) |
03:45.49 | mason | systemdlete: That's the possibility, yeah, it's tracking something legitimately and not ever considering the impact over time. But I don't know. It's one of the possibilities. |
03:46.48 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
04:01.17 | *** join/#devuan bru (~bru@181.169.14.209) |
04:14.44 | *** join/#devuan GNUmoon (~GNUmoon@gateway/tor-sasl/gnumoon) |
04:20.59 | *** join/#devuan nyov (~nyov@unaffiliated/nyov) |
04:30.08 | *** join/#devuan arnoldoree (~arnoldore@113.210.106.231) |
04:54.37 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
05:29.25 | *** join/#devuan tallship__ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
05:36.26 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
05:51.33 | *** join/#devuan tallship__ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
05:55.00 | *** join/#devuan m4rley (~m4rley@207.148.96.120) |
05:56.47 | *** join/#devuan DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
06:15.02 | *** join/#devuan dagelf (~quassel@dsl-197-245-56-57.voxdsl.co.za) |
06:17.12 | *** join/#devuan kreyren[m] (~kreyren@unaffiliated/kreyren) |
06:25.03 | *** join/#devuan disillusion- (disillusio@gateway/vpn/privateinternetaccess/disillusion) |
06:30.34 | *** join/#devuan kreyren[m] (~kreyren@unaffiliated/kreyren) |
06:34.58 | *** join/#devuan RamboCommando (~lain@2603-7080-823b-f283-39cc-6719-dbc7-eebc.res6.spectrum.com) |
06:55.18 | *** join/#devuan alv (~alv@mob-5-90-129-150.net.vodafone.it) |
07:45.29 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
07:57.57 | *** join/#devuan tallship__ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
08:18.35 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
08:20.15 | *** join/#devuan lava2 (~quassel@dsl-197-245-38-56.voxdsl.co.za) |
08:46.30 | *** join/#devuan kreyren[m] (~kreyren@unaffiliated/kreyren) |
08:57.07 | *** join/#devuan tallship__ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
09:25.05 | *** join/#devuan drmbls (~marius@78-56-83-14.static.zebra.lt) |
09:45.47 | *** join/#devuan xes (~xes@unaffiliated/xes) |
10:19.07 | *** join/#devuan hooway (~q@87.110.26.40) |
10:24.51 | *** join/#devuan ar3itrary (~hacker@2a03:4000:6:8177:2::1) |
11:00.15 | *** join/#devuan Achylles (~Achylles@191.254.130.93) |
11:05.54 | *** join/#devuan cocoadaemon (~foo@2a01:e0a:4e1:97e0:a69c:dc6e:df01:d357) |
11:16.19 | *** join/#devuan arnoldoree (~arnoldore@113.210.120.47) |
11:30.06 | *** join/#devuan n4dir (~n4dir@88.130.152.196) |
11:51.52 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
11:53.46 | *** join/#devuan tallship (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
11:57.45 | *** join/#devuan postal (50fdeb0c@80.253.235.12) |
12:01.44 | postal | hi guys how to fix this error. tried everything, nothing helps https://0bin.net/paste/af9BIbep#uXUv5kKSnrMI58qDJ5AUX3hJizJMNAt9UzKG7bxjhbY |
12:02.07 | *** join/#devuan fifiobarun (~monsieur@cpc80981-perr17-2-0-cust753.19-1.cable.virginm.net) |
12:02.56 | gnarface | postal: use paste.debian.net and i'll look at it |
12:07.43 | clort | hi postal |
12:07.57 | clort | can you describe the problem |
12:16.50 | *** join/#devuan xrogaan (~xrogaan@unaffiliated/xrogaan) |
12:16.58 | postal | gnarface http://paste.debian.net/1177700 |
12:17.39 | postal | I can't apt upgrade for this error "Hash Sum mismatch" |
12:19.28 | gnarface | postal: well you have deb-multimedia in there, which you shouldn't do and may also be causing problems, but my best guess is that you started this when "stable" was different, and now it's hosed because they changed which release is called "stable" out from underneath you |
12:20.10 | gnarface | postal: use the proper release names and get deb-multimedia crap out of there and it should be able to complete the upgrade with a little massaging |
12:20.40 | gnarface | postal: (you might have to manually remove some packages, finish updating from the old release, then complete an upgrade to the new release) |
12:21.12 | fsmithred | could be that the mirror is in the middle of updating. Try again in an hour or two. |
12:22.25 | fsmithred | using third-party repos is a crap shoot and using "stable" instead of the current codename "beowulf" may cause problems when the debian stable changes and devuan does not. |
12:26.35 | gnarface | yea it might be relevant how long it has been since this started happening but i guess in my head i assumed "tried everything" included waiting a day |
12:27.15 | gnarface | same error occasionally comes out of my proxy when the server updates between the proxy cache refresh interval |
12:27.52 | gnarface | (clears itself within 5 minutes usually, or if i manually run an update without it) |
12:41.51 | *** join/#devuan shibboleth (~shibbolet@gateway/tor-sasl/shibboleth) |
12:42.15 | postal | still doesn't work even with current codename "beowulf" instead of "stable" and without deb-multimedia and other repos in sources.list.d http://paste.debian.net/1177701 |
12:43.50 | gnarface | postal: did you try it once with ascii first? |
12:43.57 | gnarface | postal: ascii instead of beowulf |
12:48.09 | *** join/#devuan Pali (~pali@Maemo/community/contributor/Pali) |
12:53.13 | postal | I installed clean beowulf, although I don't remember much, since this is not my laptop, but my mother's, I just update it from time to time |
12:55.02 | gnarface | oh, it's not an update from a previous version? |
12:55.33 | gnarface | could you paste your /etc/apt/sources.list and the contents of anything in /etc/apt/sources.list.d/ ? |
12:55.45 | gnarface | i'll just sanity check it for you |
13:02.47 | gnarface | or, you could just remove it all and use this example instead: https://paste.debian.net/1177702/ |
13:04.42 | *** join/#devuan Debluk (~0x343750@233.33.253.84.static.wline.lns.sme.cust.swisscom.ch) |
13:08.19 | *** join/#devuan ac_laptop (~ac_laptop@186.2.247.129) |
13:17.07 | postal | My sources.list and sources.list.d repos https://paste.debian.net/1177703/ |
13:21.44 | gnarface | postal: and you're not running an apt proxy, right? then i'd say yea probably just wait and speak up again if it's not cleared in a few hours |
13:22.16 | gnarface | usually doesn't need more than a half hour or so but i think it can regularly take 2? |
13:22.22 | gnarface | don't quote me on that |
13:28.47 | postal | i don't use apt proxy |
13:29.21 | gnarface | just making sure |
13:29.28 | fsmithred | https://sledjhamr.org/apt-panopticon/results/Report-web.html |
13:29.44 | fsmithred | some mirrors are down |
13:33.14 | fsmithred | postal, here's a possible fix for the problem: https://dev1galaxy.org/viewtopic.php?pid=11331#p11331 |
13:36.37 | *** join/#devuan rsx (~rsx@ppp-188-174-145-249.dynamic.mnet-online.de) |
13:47.38 | *** join/#devuan shibboleth (~shibbolet@gateway/tor-sasl/shibboleth) |
13:48.14 | postal | unfortunately i do "rm -rf /var/lib/apt/lists/*" before apt update constantly, but doesn't help. |
13:49.36 | *** join/#devuan Deknos (~deknos@unaffiliated/menace) |
14:05.14 | *** join/#devuan arnoldoree (~arnoldore@113.210.103.175) |
14:05.46 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
14:08.57 | *** join/#devuan tallship__ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
14:23.33 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
14:28.35 | *** join/#devuan targz (~Thunderbi@unaffiliated/targz) |
14:33.26 | *** join/#devuan tallship__ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
14:34.54 | *** join/#devuan tallship (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
14:38.11 | *** join/#devuan MasterdonX (~masterdon@45.9.249.244) |
14:55.29 | *** join/#devuan gast0n (~g4570n@unaffiliated/g4570n) |
15:15.51 | *** join/#devuan tarbz2 (~Thunderbi@unaffiliated/targz) |
15:20.16 | *** join/#devuan Akuli (~akuli@87-94-110-168.bb.dnainternet.fi) |
15:31.22 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
15:31.30 | *** join/#devuan RamboCommando (~lain@2603-7080-823b-f283-39cc-6719-dbc7-eebc.res6.spectrum.com) |
15:33.01 | *** join/#devuan tallship__ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
15:36.40 | *** join/#devuan tallship (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
15:46.35 | *** join/#devuan tallship_ (~tallship@75.111.2.213) |
15:49.23 | *** join/#devuan fifiobarun (~monsieur@cpc80981-perr17-2-0-cust753.19-1.cable.virginm.net) |
16:04.27 | *** join/#devuan alv (~alv@mob-5-90-129-150.net.vodafone.it) |
16:10.15 | *** join/#devuan kreyren[m] (~kreyren@unaffiliated/kreyren) |
16:11.05 | *** join/#devuan tomtastic (~tomtastic@90.207.28.145) |
16:11.58 | *** join/#devuan seb95 (~sebastien@2a01cb000fb6200008ad8bbb56ad118e.ipv6.abo.wanadoo.fr) |
16:18.12 | *** join/#devuan Uberius (~uberius@gateway/tor-sasl/uberius) |
16:18.34 | *** join/#devuan I_am_nobody777 (~I_am_nobo@157.46.92.234) |
16:19.22 | *** join/#devuan kreyren[m] (~kreyren@unaffiliated/kreyren) |
16:47.42 | *** join/#devuan Kruppt (~Kruppt@50-111-56-201.drhm.nc.frontiernet.net) |
16:50.07 | *** join/#devuan captainfixerpc14 (~joanne@unaffiliated/captainfixerpc14) |
16:57.28 | captainfixerpc14 | model t car drawing |
16:57.47 | captainfixerpc14 | oops |
17:00.31 | *** join/#devuan amesser (~amesser@p57bcf098.dip0.t-ipconnect.de) |
17:01.47 | fsmithred | can it run linux? |
17:02.34 | *** join/#devuan bsd4me (~usingbsd@95-105-74-65.gci.net) |
17:05.52 | captainfixerpc14 | working on that :P |
17:14.35 | captainfixerpc14 | lsb_release -a |
17:14.41 | captainfixerpc14 | arggggggg |
17:14.44 | captainfixerpc14 | too many keyboards |
17:15.18 | captainfixerpc14 | sorry |
17:24.00 | *** join/#devuan GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon) |
17:28.48 | *** join/#devuan redd1 (~redd1@104.238.58.117) |
18:06.55 | *** join/#devuan cd (~cd@unaffiliated/cd) |
18:14.17 | *** join/#devuan shibboleth (~shibbolet@gateway/tor-sasl/shibboleth) |
18:19.46 | *** join/#devuan Ignotum (~Ignotum@unaffiliated/ignotum) |
18:25.54 | *** join/#devuan blizzow (~blizzow@71-33-134-157.hlrn.qwest.net) |
18:51.33 | *** join/#devuan lagfra_ (~fra@193.9.112.123) |
19:03.07 | systemdlete | lightdm: PAM adding faulty module: pam_systemd.so |
19:03.20 | systemdlete | lightdm: PAM unable to dlopen(pam_systemd.so): /lib/security/pam_systemd.so: cannot open shared object file: No such file or directory |
19:03.43 | systemdlete | hehehheh... there is no escaping it, is there? |
19:04.34 | systemdlete | (it's EVERYwhere) |
19:05.44 | systemdlete | fsmithred: Thanks for the suggestion of the mate 1.22 repo. Sadly, though, it did not help. Apparently the fixes are only in 1.24+. Still, thanks for trying. |
19:06.26 | fsmithred | yw |
19:06.30 | systemdlete | I could try filing for a backport, but since this is a library dependency problem, I doubt there will be much enthusiasm to do such. Better for me to wait for chimaera I think. |
19:07.04 | fsmithred | how critical is this system? You might do ok with chimaera or chimaera/ceres |
19:07.30 | *** join/#devuan shibboleth (~shibbolet@gateway/tor-sasl/shibboleth) |
19:07.54 | systemdlete | fsmithred: Probably NOTHING I *ever* do is really "critical" per se. Mostly my own stuff. But I really detest instability. I'm funny like that. |
19:08.03 | fsmithred | people are reporting very stable systems (I'm one of the people) |
19:08.44 | fsmithred | I'm running chimaera xfce on an old thinkpad. Don't do a whole lot with it, but it's working. |
19:09.06 | fsmithred | I do jitsi with it, I ssh into it to check stuff 'cause I'm too lazy to turn around. |
19:09.30 | systemdlete | So devuan project is waiting on debian to release theirs before devuan releases ours? |
19:09.43 | systemdlete | (summer '21) |
19:09.58 | fsmithred | yeah, we follow them. They have not even begun freeze on bullseye. |
19:10.13 | fsmithred | however, most of the forked packages are already forked and working. |
19:11.08 | fsmithred | and the list of forked packages does grow as time goes on. Latest thing is for upstream to drop init scripts from the package. |
19:11.26 | systemdlete | So, one could say that Bullseye is a moving target (see what I did there?) |
19:11.35 | fsmithred | lol, yeah |
19:13.23 | systemdlete | "Latest thing is for upstream to drop init scripts from the package." Does this mean debian has agreed to clean up their packaging to support multiple boot and runtime systems? Or am I reading too much in there? |
19:15.29 | fsmithred | I think you're reading it backward. |
19:16.21 | systemdlete | So more like "The package drops init scripts for upstream's latest thing?" |
19:16.22 | fsmithred | some debian devs are not interested in compatibiity with other init systems |
19:16.59 | systemdlete | Actually, fsmithred, it is probably surprising that there is any interest there at all! |
19:17.23 | fsmithred | brb need food |
19:17.38 | systemdlete | So what did that mean then? |
19:43.55 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
19:47.44 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
19:53.43 | fsmithred | what? |
19:58.01 | mason | systemdlete: Have you followed the recent/relevant Debian bug? https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=975075 |
20:57.10 | rwp | systemdlete, Well before the creation of Devuan I decided that pam_systemd.so did things I did not want, and therefore have since removed it from the PAM configuration files. |
20:57.39 | rwp | Among other things pam_systemd.so is responsible for creating the /run/user/$(id -u) files. |
20:58.18 | rwp | Among other things pam_systemd.so breaks starting X with a permission denied error. X tries to start, clears the screen, then gets stuck. |
20:58.47 | rwp | This might be a problem due to the resulting cgroup non-configuration that I imposed by removing it. |
20:59.23 | rwp | So I do the Luddite thing and remove it and revert to starting X the old ways. |
20:59.30 | rwp | YMMV! |
21:01.48 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
21:17.36 | *** join/#devuan tallship_ (~tallship@75.111.2.213) |
21:24.18 | *** join/#devuan disillusion- (disillusio@gateway/vpn/privateinternetaccess/disillusion) |
21:25.25 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
21:37.10 | *** join/#devuan GNUmoon2 (~GNUmoon@gateway/tor-sasl/gnumoon) |
22:05.51 | *** join/#devuan Acacia (~Acacia@unaffiliated/acacia) |
22:15.47 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
22:39.14 | *** join/#devuan tallship__ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
22:56.47 | *** join/#devuan aitor_ (~aitor@30.85-87-182.dynamic.clientes.euskaltel.es) |
22:59.41 | aitor_ | hi |
23:01.41 | aitor_ | there is something new in apt, apt-get install doesn't work without libudev.so.1, only dpkg |
23:01.46 | aitor_ | that's new for me |
23:03.24 | aitor_ | today i've been able to build the sources of vdev in beowulf, but my images didn't boot neither in live mode nor after a hard disk installation |
23:06.24 | aitor_ | if apt doesn't work without libudev.so.1, then it'll be quite complicate to change from udev to any other *dev and vice versa |
23:08.22 | aitor_ | nobody here... ok, time to bed |
23:08.24 | aitor_ | bye |
23:23.54 | *** join/#devuan tallship_ (~tallship@75-111-2-213.erkacmtk05.res.dyn.suddenlink.net) |
23:34.24 | *** join/#devuan Uberius (~uberius@gateway/tor-sasl/uberius) |