| 00:00.06 | systemdlete | I just rebooted a couple of times and I have not seen errors from fsck on the way up |
| 00:00.27 | systemdlete | I guess I could force a fsck on root, in case that was missed |
| 00:00.55 | fsmithred | to always get the newest kernel for the release, install linux-image-amd64 (or other arch) |
| 00:01.03 | fsmithred | same for headers |
| 00:01.10 | systemdlete | That is already the case, thanks |
| 00:01.16 | systemdlete | so that is not it |
| 00:01.35 | fsmithred | maybe it has to be dist-upgrade to get a newer version |
| 00:02.19 | systemdlete | but anyway, I am more concerned about the usb problem. I can see from my system logs that the system was rebooted (by me) on Apr 27 and Apr 28. The dmesg log for the 27th and prior do NOT show this error (usb endpoint missing), but 28th forward all show it. |
| 00:02.35 | systemdlete | No packages were added or upgraded in the time in between. |
| 00:03.26 | systemdlete | The only thing I can think of is the usb kvm switch. I may have installed it right around that time, but I don't remember exactly when that was now. |
| 00:04.58 | systemdlete | Maybe the introduction of that switch is generating the reference to the mouse... the information about this switch says it does not support wireless mouse. But I don't see how that can matter given that the mouse is running off the keyboard. But it does say that. Funny how I have not had any problems with *usb* until today (other than the usual usb weirdness that does no harm) |
| 00:05.20 | systemdlete | sorry, it says |
| 00:05.29 | systemdlete | does not support keyboard mouse... hmmm. |
| 00:05.48 | systemdlete | I wonder if that is what they mean. Does this imply I must use a wired mouse to the keyboard? |
| 00:06.04 | systemdlete | is asking a bit rhetorically here |
| 00:07.03 | systemdlete | https://www.amazon.com/dp/B075KBCPKZ?tag=duckduckgo-ffab-20&linkCode=osi&th=1&psc=1 |
| 00:07.13 | *** join/#devuan amarsh04 (~amarsh04@2001:44b8:249:fe00:214:85ff:feee:bcc5) |
| 00:07.14 | systemdlete | "FJGEAR 4 Ports USB 2.0 HDMI KVM Switch Keyboard Mouse Switcher for PC, Windows, ï¼Wireless mouse keyboard is not supportedï¼No powerï¼" |
| 00:07.58 | systemdlete | my keyboard is wired. The mouse is not. The mouse dongle is plugged into the keyboard. |
| 00:08.15 | systemdlete | So I am not sure if I am in violation or not. |
| 00:08.58 | systemdlete | It depends on how "wireless mouse keyboard" is defined. |
| 00:09.21 | systemdlete | The thing is... it works. Had not noticed the boot error until today |
| 00:10.07 | systemdlete | Was investigating a different problem that was occurring in a VM, which may be related to Zoom. |
| 00:10.39 | ullet | try swapping mouse |
| 00:10.41 | systemdlete | The VM, btw, is running Ascii also, so maybe you can help me there, or at least give a listen. |
| 00:10.49 | systemdlete | ullet: ooh ooh. Good idea! |
| 00:10.55 | systemdlete | (but I'll have to reboot) |
| 00:11.04 | systemdlete | +1 |
| 00:11.15 | systemdlete | I have another wireless mouse around here I think |
| 00:11.37 | systemdlete | And a wired mouse also |
| 00:12.09 | fsmithred | can you plug the dongle directly into the computer instead of into the keyboard? |
| 00:12.30 | systemdlete | anyway, Zoom was crashing badly and kern.log shows stack traces |
| 00:12.37 | systemdlete | Oh, the mouse works |
| 00:12.55 | ullet | zoom appears to be a new thing |
| 00:12.55 | systemdlete | and it works through the switch. What are you trying to have me test, fsmithred? |
| 00:12.57 | ullet | therefore it is bad |
| 00:13.10 | systemdlete | LOL. You are probably right, ullet. |
| 00:13.20 | ullet | :) |
| 00:13.32 | fsmithred | test to see if it makes the warning go away |
| 00:13.36 | systemdlete | It *is* proprietary, so... |
| 00:14.01 | systemdlete | ok, fsmithred. I can try that also when I reboot. I'll be sure to take notes on all these tests. |
| 00:14.26 | systemdlete | But if I solve the riddle, then I deserve to help solve the Covid problem. |
| 00:14.39 | systemdlete | because it seems to be almost as difficult. |
| 00:14.47 | ullet | that is in people's heads |
| 00:15.12 | systemdlete | What is it about lsusb? The tree option doesn't show the device descriptions. That would be helpful right now. |
| 00:15.22 | systemdlete | and usbtree no longer works. |
| 00:15.37 | systemdlete | ullet: More in the chest and lungs, actually. |
| 00:17.26 | onefang | Some of these switches fake info, so that when you switch your mouse and keyboard to another computer, the original still thinks it has them plugged in. |
| 00:18.35 | systemdlete | onefang: Exactly, yes. That is so the quiescent boxes won't think they've lost the head. |
| 00:20.02 | systemdlete | thinks deeply about wireless mouse attached to keyboard, via the switch... |
| 00:21.03 | systemdlete | This actually makes some sense, now that I think about it. Linux tries to find an endpoint for the mouse, but the actual mouse is in front of the switch; I am thinking maybe it cannot query it -- it will query the "fake" kb and mouse. |
| 00:21.24 | systemdlete | Howeer, it is worth noting that lsusb does show the wireless mouse and correctly identifies it as a logitech, etc |
| 00:22.29 | systemdlete | well, I'll know more after these tests |
| 00:24.25 | fsmithred | so the fake info contains real content |
| 00:26.23 | systemdlete | apparently copied from the real "content" |
| 00:27.08 | systemdlete | but Linux does not squawk about the keyboard |
| 00:27.42 | systemdlete | but first, lunch |
| 00:27.45 | systemdlete | or dinner |
| 00:27.52 | systemdlete | then more testing |
| 00:28.04 | systemdlete | thanks for all the suggestions -- that's very helpful |
| 00:32.54 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
| 00:44.04 | *** join/#devuan bpmedley (~bpm@2601:240:d:18af:4c0:4a9c:c3a6:cbce) |
| 00:59.40 | *** join/#devuan amarsh04 (~amarsh04@2001:44b8:249:fe00:214:85ff:feee:bcc5) |
| 01:02.16 | *** join/#devuan gnu_srs (~srs@2-248-159-26-no549.tbcn.telia.com) |
| 01:15.54 | *** join/#devuan ar3itrary (~hacker@v22016101923038440.bestsrv.de) |
| 01:26.46 | *** join/#devuan amarsh04 (~amarsh04@2001:44b8:249:fe00:214:85ff:feee:bcc5) |
| 01:28.01 | *** join/#devuan Peregrinus_ (~peregrinu@178.239.173.252) |
| 01:47.35 | *** join/#devuan xrogaan (~xrogaan@unaffiliated/xrogaan) |
| 02:08.32 | *** join/#devuan tuxd3v (~tuxd3v@78-130-62-250.net.novis.pt) |
| 02:10.12 | *** join/#devuan amarsh04 (~amarsh04@2001:44b8:249:fe00:214:85ff:feee:bcc5) |
| 02:10.13 | *** join/#devuan tuxd3v (~tuxd3v@78-130-62-250.net.novis.pt) |
| 02:11.14 | *** join/#devuan debdog (~debdog@194.140.113.85) |
| 02:22.04 | *** join/#devuan systemdlete (~systemdle@c-76-105-3-38.hsd1.ca.comcast.net) |
| 02:24.05 | systemdlete | So... I tried a number of different combinations of different mice connected to the kb, the pc, and so forth, and one thing I noticed was that, no matter which combination, I ALWAYS got the boot error about missing endpoint for the mouse. But how could it be just any mouse, wired, wireless, directly connected, etc... so then I got to thinking |
| 02:24.19 | systemdlete | I booted the pc without ANY mice attached whatsoever! |
| 02:24.30 | systemdlete | And STILL the error message appears. |
| 02:24.52 | gnarface | usb mice? |
| 02:24.54 | systemdlete | Soooooo. I think I conclude that the switchbox itself is the issue, though apparently not fatal. |
| 02:25.02 | systemdlete | yes, all usb mice |
| 02:25.12 | gnarface | oh, and a usb switch? mabye |
| 02:25.26 | systemdlete | the problem is on a usb switchbox, so yes, usb mice. all. |
| 02:25.30 | systemdlete | usb switch yes |
| 02:26.08 | systemdlete | gnarface: On the amazon web page for it, it even says does not work with wireless mouse keyboard, though I am not sure what that means precisely |
| 02:26.23 | systemdlete | wireless mouse attached to kb, or wireless mouse+kb |
| 02:26.42 | systemdlete | but either way, I am guessing I can look forward to this issue for the near future. |
| 02:27.02 | systemdlete | Not sure if kernel devs can handle this or not. It could be an actual hw flaw. |
| 02:27.27 | systemdlete | But I feel a little more sane now that I've narrowed it down to the switch and/or kernel |
| 02:28.16 | systemdlete | I think I will write to the mfr and see if they can offer some insight or confirm this |
| 02:29.01 | *** join/#devuan sunshavi (~user@190.236.255.201) |
| 02:36.35 | gnarface | systemdlete: i do recall hearing of some type of fakey cheap usb kvm switches that were on the market that needed specifically a windows-only feature to work right, but i don't recall much specifically about it |
| 02:37.15 | gnarface | it wouldn't fail completely, it would just critically fail at the one feature that made it useful |
| 02:37.16 | systemdlete | Well, this one was recommended by a fellow Linux user and it was not cheap. |
| 02:37.25 | gnarface | oh hmm. well that is maybe not the issue then |
| 02:37.27 | systemdlete | OTOH, I also figured something out |
| 02:37.55 | systemdlete | the ad says "no power" -- so I think what they are saying is that since the switch is not powered, it can't talk to a wireless kb/mouse |
| 02:37.56 | gnarface | oh is this ascii? maybe it's a kernel version issue, maybe there's quirks and they've been added to a newer kernel but not the ascii one |
| 02:38.20 | systemdlete | So I think my hardware config is fine -- it must be, since it does work... |
| 02:38.46 | gnarface | it *might* just mean that since it's unpowered some wireless devices might not work? |
| 02:38.47 | systemdlete | the mouse supplies its own power by its battery. |
| 02:38.57 | systemdlete | right |
| 02:39.21 | systemdlete | there is some risidual power in usb that can power a keyboard I think |
| 02:40.16 | gnarface | yea, i don't know the numbers, but it's probably not a good idea to try to use it to charge anything |
| 02:40.51 | onefang | If the switch is unpowered, then it gets it's power from the computer, and it can ask for more power and distribute that downstream to devices. Assuming the computer can supply extra power. |
| 02:41.22 | onefang | It might not do that if it's just assuming typical mouse and keyboard. |
| 02:41.30 | gnarface | i would worry about frying stuff accidentally |
| 02:41.48 | gnarface | it should be safe, one would think, but it seems risky |
| 02:42.28 | gnarface | like, if it tried to charge a iphone would it trickle or would the wires get hot? |
| 02:42.44 | gnarface | i would assume the former but also not risk it |
| 02:42.57 | onefang | Modern USB stuff sorta negotiates power levels, but it's tricky with all the various versions, and cables may or may not support some of that. |
| 02:44.25 | onefang | My keyboard isn't powered, but has a small USB hub in the back to support two other devices, like a mouse and graphics tablet. Should be plenty of juice for that sort of thing. |
| 03:16.47 | *** join/#devuan infobot (ibot@c-174-52-60-165.hsd1.ut.comcast.net) |
| 03:16.47 | *** topic/#devuan is Welcome to Devuan! https://devuan.org | Releases: https://files.devuan.org (Jessie 1.0 old-stable, ASCII 2.1 stable) | | Conference (2019) https://www.dyne.org/the-first-devuan-conference/ | Forum https://dev1galaxy.org | Chanlogs http://maemo.cloud-7.de/irclogs/freenode/_devuan/ | take offtopic chat to #debianfork |
| 03:16.48 | *** mode/#devuan [+v infobot] by ChanServ |
| 03:35.43 | *** join/#devuan nyov (~nyov@unaffiliated/nyov) |
| 03:48.18 | *** join/#devuan sedrosken (~sedrosken@216.146.235.121) |
| 04:10.35 | *** join/#devuan xcm (~xcm@ipd114.250.tellas.gr) |
| 04:18.11 | systemdlete | Yeah, I have a Happy Hacker (my 2nd one after 20 years with the first!) and this new one has 2 USB ports. I attach the wireless mouse to the kb, since the mouse is powered by a battery. |
| 04:18.28 | *** join/#devuan arnoldoree (~arnoldore@113.210.74.128) |
| 04:19.38 | systemdlete | The KVM does have a (5mV?) power port, but the adapter does not come with it. However, I have not needed additional power so far, and hopefully I won't. |
| 04:20.58 | systemdlete | I found a matching adapter I have here, just in case I need it. |
| 04:21.33 | onefang | Mines a Happy Hacker Lite 2. B-) |
| 04:21.38 | systemdlete | mine too! |
| 04:21.42 | systemdlete | $200 |
| 04:22.22 | systemdlete | I got 20 years out of the first one. The letters on the keys had become worn, and the keys themselves had sort of melted a bit... |
| 04:22.32 | systemdlete | I think I got my moneys worth from it. |
| 04:22.35 | systemdlete | heheheh |
| 04:22.46 | systemdlete | I only paid $100 for the first one |
| 04:23.17 | systemdlete | I cleaned the old one about 3x over the years, and it still worked like new. Just couldn't see the keys anymore |
| 04:23.20 | systemdlete | letters |
| 04:26.43 | *** join/#devuan ac_laptop (~ac_laptop@186.2.247.129) |
| 04:28.00 | *** join/#devuan xcm (~xcm@ipd114.250.tellas.gr) |
| 04:57.04 | *** join/#devuan DocScrutinizer05 (~saturn@openmoko/engineers/joerg) |
| 05:09.16 | *** join/#devuan coagen (~coagen@unaffiliated/coagen) |
| 05:13.27 | *** join/#devuan gavlee (~gav@unaffiliated/gavlee) |
| 05:14.07 | *** join/#devuan arnoldoree (~arnoldore@113.210.74.128) |
| 05:19.36 | *** join/#devuan xcm (~xcm@ipd114.250.tellas.gr) |
| 05:35.32 | *** join/#devuan morruth (~quassel@77.244.126.248) |
| 05:38.12 | *** join/#devuan xcm (~xcm@ipd114.250.tellas.gr) |
| 05:48.07 | *** join/#devuan markizano (markizano@2600:3c00::f03c:91ff:fec8:382d) |
| 05:49.15 | *** join/#devuan Kizano (markizano@2600:3c00::f03c:91ff:fec8:382d) |
| 06:09.05 | *** join/#devuan KnoP (~KnoP@business-176-095-149-105.static.arcor-ip.net) |
| 06:11.41 | *** join/#devuan silentjet (~jet@staticline-31-182-193-145.toya.net.pl) |
| 06:17.30 | *** join/#devuan sb35 (~sb35@23.111.78.42) |
| 06:19.15 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
| 06:39.54 | *** join/#devuan phyre (~phyre___@78.30.23.107) |
| 07:20.10 | *** join/#devuan xinomilo (~xinomilo@gateway/tor-sasl/xinomilo) |
| 07:27.31 | *** join/#devuan bpmedley (~bpm@2601:240:a:8dca:d5bc:3a29:e059:2e08) |
| 07:29.35 | *** join/#devuan systemdlete (~systemdle@c-76-105-3-38.hsd1.ca.comcast.net) |
| 07:52.14 | *** join/#devuan Pali (~pali@Maemo/community/contributor/Pali) |
| 08:08.20 | *** join/#devuan bleb_ (~cm@unaffiliated/bleb) |
| 08:10.55 | *** join/#devuan GuntherD1 (~guntherdw@quadran.system33.be) |
| 08:11.07 | *** join/#devuan openbsdt1i123 (openbsdtai@gateway/shell/ircnow/x-freduprtfkytxkcd) |
| 08:11.17 | *** join/#devuan surrealpie (~centos@237.ip-144-217-95.net) |
| 08:15.40 | *** join/#devuan danielg4 (tAm0O@april-fools/2014/runnerup/danielg4) |
| 08:15.57 | *** join/#devuan Unit193 (ukikie@freenode/staff/ubuntu.member.unit193) |
| 08:16.00 | *** join/#devuan xes_ (~xes@unaffiliated/xes) |
| 08:17.03 | *** join/#devuan man_in_shack (~chat@unaffiliated/man-in-shack/x-4279753) |
| 08:17.05 | *** join/#devuan hplar (~ralph@147.87.5.199) |
| 08:18.31 | *** join/#devuan cocoadaemon (~foo@2a01:e0a:4e1:97e0:179d:1cc6:8854:4d5c) |
| 08:26.41 | *** join/#devuan joeytwiddle (~joeytwidd@162.243.115.31) |
| 08:54.06 | *** join/#devuan rsx (~rsx@ppp-188-174-142-8.dynamic.mnet-online.de) |
| 09:02.12 | *** join/#devuan gnarf (~ck@static.184.34.12.49.clients.your-server.de) |
| 09:10.01 | *** join/#devuan Joril (~joril@host-217-194-188-145.sbs.redder.net) |
| 10:03.27 | *** join/#devuan gnarf (~ck@static.184.34.12.49.clients.your-server.de) |
| 10:04.42 | *** join/#devuan gnarf (~ck@static.184.34.12.49.clients.your-server.de) |
| 10:05.41 | *** join/#devuan tierce (~raoulzeca@2a02:578:857c:c01:e6b3:18ff:fef6:fbc1) |
| 10:31.43 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
| 10:41.32 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
| 10:49.00 | *** join/#devuan AntoFox (~Thunderbi@net-2-44-133-197.cust.vodafonedsl.it) |
| 11:04.10 | *** join/#devuan Unit193 (ukikie@freenode/staff/ubuntu.member.unit193) |
| 11:07.48 | *** join/#devuan xcm (~xcm@ipd114.250.tellas.gr) |
| 11:22.34 | *** join/#devuan ac_laptop (~ac_laptop@186.2.247.129) |
| 11:51.47 | *** join/#devuan tierce (~raoulzeca@77.109.101.14) |
| 12:12.06 | *** join/#devuan cocoadaemon (~foo@88.123.134.95) |
| 12:28.39 | *** join/#devuan bpmedley (~bpm@2601:240:2:9ccb:409b:f867:86bf:1cb0) |
| 12:54.37 | *** join/#devuan Soo_Slow (Soo_Slow@gateway/vpn/privateinternetaccess/sooslow/x-31376162) |
| 13:03.28 | *** join/#devuan bpmedley (~bpm@2601:240:d:5ebc:bc34:b71c:7871:594d) |
| 13:08.46 | *** join/#devuan james1138 (~james1138@71-222-133-42.albq.qwest.net) |
| 14:13.28 | *** join/#devuan Xenguy (~Xenguy@devuan/community/Xenguy) |
| 14:19.29 | *** join/#devuan bsd4me (~me@98-106-74-65.gci.net) |
| 14:27.09 | *** join/#devuan g4570n (~g4570n@unaffiliated/g4570n) |
| 14:41.29 | *** join/#devuan IoFran (~Thunderbi@189.154.81.28) |
| 14:43.46 | *** join/#devuan KnoP (~KnoP@business-176-095-149-105.static.arcor-ip.net) |
| 14:57.45 | *** join/#devuan st3ma (~st3ma@185.31.62.101) |
| 15:02.19 | *** join/#devuan Oldmoss (~Oldmoss@2001:67c:1350:100::4) |
| 15:04.48 | *** join/#devuan engidea (~damiano@46.141.120.243) |
| 15:32.14 | nemo | hmmm I'm on a beowulf devuan, and I was trying to build chafa |
| 15:32.33 | nemo | so I installed libmagick++-d |
| 15:32.35 | nemo | ev |
| 15:32.40 | nemo | everything built and linked correctly |
| 15:33.39 | *** part/#devuan Joril (~joril@host-217-194-188-145.sbs.redder.net) |
| 15:34.31 | nemo | but, on run it claims the libs are missing |
| 15:34.57 | nemo | checking in symaptic I see there's a couple of variants of libmagick++ |
| 15:35.04 | slvr | maybe build and execute are using different paths |
| 15:35.21 | slvr | I think you can run ldd on the bin and see the paths to all linked libs, and if they are missing. |
| 15:35.32 | nemo | I appear to be using libmagick++-6.q16-8 |
| 15:35.43 | nemo | the linker expects libMagickWand-6.Q16.so.3 |
| 15:36.26 | nemo | q16-8 provides: |
| 15:36.27 | nemo | /usr/lib/x86_64-linux-gnu/libMagick++-6.Q16.so.8 |
| 15:36.28 | nemo | /usr/lib/x86_64-linux-gnu/libMagick++-6.Q16.so.8.0.0 |
| 15:36.43 | nemo | I see there's a q16-7 (probably provides so.7) |
| 15:37.03 | nemo | aaaand a libmagickcore-6.q16-3 which might have something to do with 3 |
| 15:37.24 | nemo | slvr: I was just puzzled how I got into this situation in first place. normally debian/devuan ensures libs I'm linking to actually exist |
| 15:37.34 | nemo | eh. lemme do a purge and rebuild |
| 15:37.51 | nemo | maybe some stale cache |
| 15:42.43 | nemo | yep. guess it was that. nevermind |
| 15:43.13 | slvr | woot |
| 15:51.54 | ullet | it seems more fun to move to ceres, for me |
| 16:03.10 | *** join/#devuan AntoFox (~Thunderbi@net-2-44-133-197.cust.vodafonedsl.it) |
| 16:05.46 | *** join/#devuan bpmedley (~bpm@2601:240:e:e90e:3496:f0b2:8111:b68d) |
| 16:12.38 | *** join/#devuan targz (~Thunderbi@unaffiliated/targz) |
| 16:41.19 | *** join/#devuan Akuli (~akuli@mobile-access-bcee51-127.dhcp.inet.fi) |
| 17:01.04 | *** join/#devuan bpmedley (~bpm@2601:240:7:392f:1931:f6bb:65af:dec3) |
| 17:01.04 | *** join/#devuan gnu_srs (~srs@2-248-159-26-no549.tbcn.telia.com) |
| 17:03.39 | *** join/#devuan OldMoss (~oldmoss@anon-35-78.vpn.ipredator.se) |
| 17:22.23 | *** join/#devuan spheremint (~Jayde@2605:a000:121e:c999:0:9690:3f73:8079) |
| 17:34.15 | *** join/#devuan xcm (~xcm@ipd114.250.tellas.gr) |
| 18:11.47 | *** join/#devuan ejr (~ejr@178.165.128.238.wireless.dyn.drei.com) |
| 18:12.40 | *** join/#devuan shibboleth (~shibbolet@gateway/tor-sasl/shibboleth) |
| 18:27.14 | *** join/#devuan engidea (~damiano@46.141.120.243) |
| 18:30.22 | *** join/#devuan blizzow (~blizzow@97-122-221-232.hlrn.qwest.net) |
| 18:32.44 | *** join/#devuan Uberius (~Uberius@gateway/tor-sasl/uberius) |
| 18:35.08 | *** join/#devuan Uberius (~Uberius@gateway/tor-sasl/uberius) |
| 18:45.56 | mason | For the life of me I can't get LightDM to show a background, either per-user or global. The config is straightforward, but the convoluted pile is fighting me. |
| 18:51.27 | fsmithred | what convoluted pile? |
| 18:51.37 | fsmithred | can't you just set the bg image in the config file? |
| 18:51.53 | mason | fsmithred: I tried with a couple syntax examples I found. |
| 18:52.07 | fsmithred | are you messing with the alternatives system? |
| 18:52.19 | mason | Evidently it can/does/? depend on an AccountsService thing I'd never heard of before today. |
| 18:52.36 | fsmithred | that name sounds familiar |
| 18:52.36 | mason | No, I've left all the package-installed stuff untouched. |
| 18:52.42 | fsmithred | cool |
| 18:52.48 | mason | I found this that seemed applicable: https://github.com/linuxmint/slick-greeter/issues/94 |
| 18:53.17 | mason | (LightDM/slick-greeter I should say.) |
| 18:53.27 | mason | I'll try again with the gtk-greeter and see if that does any better. |
| 18:54.30 | fsmithred | I've never done per user bg. Don't see how that would work. |
| 18:54.44 | fsmithred | how would it know which user is going to log in before they log in? |
| 18:55.10 | mason | According to one creation myth, there's a per-user file in /var/lib/AccountsService/users/ that is populated with this, but I've not dug into what yet, largely because even with it set properly it doesn't display an image. |
| 18:55.27 | *** part/#devuan james1138 (~james1138@71-222-133-42.albq.qwest.net) |
| 18:55.44 | mason | fsmithred: So, with slick-greeter, the user list is all there in a list, and whichever one is selected is the one whose background shows. It's slick when it works - Ubuntu does it. |
| 18:55.56 | mason | It's not so slick when it doesn't work. :P |
| 18:56.25 | mason | For myself, I use xdm, and my background pattern is the standard grey X stipple as God intended, but the kids like more bling. |
| 18:56.53 | fsmithred | for lightdm, I've always changed it in the config file |
| 18:57.10 | fsmithred | there's a line for background_image |
| 18:57.19 | fsmithred | probably in the greeter config |
| 18:57.32 | mason | Yeah. I'm trying again with lightdm-gtk-greeter and we'll see if that obeys. |
| 18:57.38 | mason | It won't show the user list, but that's okay. |
| 18:57.52 | fsmithred | there's a setting to show or not show user list |
| 18:58.10 | mason | My four year old isn't reading just yet, so the theory was that seeing her background would help her figure it out. Starting with her typing in a simple password will be task enough. :) |
| 18:58.32 | mason | In the gtk greeter, that works, but it controls a pop-up menu, not a list with everyone there on-screen at once. |
| 18:58.41 | fsmithred | oh |
| 19:01.02 | mason | fsmithred: Does setting background= work for you? It seems not to work here, regardless of whether I have it set in /etc/lightdm/lightdm-gtk-greeter.conf or /etc/lightdm/lightdm.conf.d/foo |
| 19:01.44 | fsmithred | trying to find a VM that has lightdm |
| 19:02.04 | fsmithred | in the past, it has always worked for me to just list the path to the bg image |
| 19:03.08 | mason | This is on Beowulf, FWIW, as I expect they're different versions. |
| 19:06.54 | mason | Hm, even if I install lightdm-gtk-greeter-settings and have it set the image via the gui, no love. |
| 19:12.50 | fsmithred | installing lightdm now |
| 19:13.02 | mason | Ah, cool - I'll be interested in seeing how it goes. |
| 19:16.42 | fsmithred | ok, after install it uses the desktop-base bg without my doing anything other than selecting lightdm as default dm |
| 19:17.15 | *** join/#devuan fleeky (~fleeky@2601:645:4300:6580:315c:801b:2f2e:457f) |
| 19:17.37 | fsmithred | and now it's stuck and I have to start over |
| 19:17.47 | fsmithred | don't restart dm in qemu |
| 19:18.00 | fsmithred | use init 1 instead |
| 19:21.00 | fsmithred | yeah, it works. I got a different bg |
| 19:21.57 | fsmithred | my guess is you changed it near the top of the file instead of in the section that starts with [greeter] |
| 19:26.22 | mason | doh |
| 19:26.39 | mason | Which file? |
| 19:27.08 | mason | trying lightdm.conf itself |
| 19:34.12 | *** join/#devuan blizzow (~blizzow@97-122-221-232.hlrn.qwest.net) |
| 19:41.03 | mason | Even putting it there, at the end, no luck. I'll purge and try again with a fresh config, just that one line added. |
| 19:41.15 | mason | fsmithred: Which config file did you amend? |
| 19:42.32 | *** join/#devuan eyalroz (~quassel@5.29.46.33) |
| 19:44.14 | eyalroz | Hello devuaners, |
| 19:44.14 | eyalroz | How do I get rid of the message "udevd: Error running install command for nvidia" which I get on every boot of Beowulf? |
| 19:44.14 | eyalroz | I've been led to believe I might need to disable something in /etc/modprobe.d/nvidia.conf, but I'm not sure what line. Or - perhaps I need to do something else entirely? |
| 19:46.06 | ullet | idk. maybe a setup script |
| 19:46.13 | ullet | a kernel module generally doesn't handle installing |
| 19:47.07 | eyalroz | ullet: I should mention my nvidia card works fine (although I don't use it as a display adapter) |
| 19:47.26 | eyalroz | I'm just annoyed by the error message. |
| 19:49.48 | *** join/#devuan james1138 (~james1138@71-222-133-42.albq.qwest.net) |
| 19:50.31 | *** join/#devuan lyubov (~lyubov@172-3-143-10.lightspeed.sntcca.sbcglobal.net) |
| 19:53.26 | *** join/#devuan IoFran2 (~Thunderbi@189.154.81.28) |
| 20:00.36 | gnarface | eyalroz: best guess is that nouveau and nvidia are both fighting over the card. you have to pick one then blacklist the other. |
| 20:01.10 | eyalroz | I have a "blacklist nouveau" in another .conf file in modprobe.d ... |
| 20:01.30 | eyalroz | Also - none of that stuff was done manually by me, nor by a manual nVIDIA installer... |
| 20:01.39 | eyalroz | I think those files came with the distro, |
| 20:02.05 | eyalroz | ... so it's not exactly about what I have to do personally. IIANM. |
| 20:02.10 | fsmithred | mason /etc/lightdm/lightdm-gtk-greeter.conf |
| 20:02.28 | gnarface | eyalroz: oh, hmmm.... well the nvidia official drivers are in non-free, so if you didn't include non-free you wouldn't have got them even by accident. but if you're blacklisting nouveau already then my hypothesis is probably wrong. |
| 20:03.02 | gnarface | eyalroz: (to be clear, my hypothesis was that nouveau was already loaded and then it was blocking nvidia's attempt to load after that) |
| 20:03.39 | gnarface | eyalroz: is it a very old card? perhaps the error is about using the new drivers with a legacy card. there's also a legacy nvidia driver package in there for older cards |
| 20:03.41 | *** join/#devuan Venker (~unknown@158.red-88-4-96.dynamicip.rima-tde.net) |
| 20:03.45 | Venker | hi people |
| 20:04.09 | gnarface | eyalroz: or, alternately, if you're on ascii and it's a very new card, you might need to get the drivers&kernel from backports |
| 20:05.03 | gnarface | Venker: hi, just ask |
| 20:05.52 | ullet | my vote for next release name is PETSCII |
| 20:06.03 | Venker | I was coding a pull request or something like that for https://git.devuan.org/devuan-packages/openstack-devuan-images |
| 20:06.19 | Venker | but I can't get it to work |
| 20:06.31 | *** join/#devuan shibboleth (~shibbolet@gateway/tor-sasl/shibboleth) |
| 20:06.45 | Venker | it complains about extlinux package not found, but it is |
| 20:08.49 | mason | fsmithred: Alright, that did work, so now I need to pick apart how I was doing it to see what was breaking. Difference this time, I purged all the related packages and put them back in pristine, freshly installed state. Thank you. |
| 20:09.25 | fsmithred | yw |
| 20:09.45 | fsmithred | you saw what I meant about the right place to edit the file? |
| 20:09.52 | fsmithred | it's a common mistake |
| 20:09.54 | mason | Yes. |
| 20:12.58 | eyalroz | gnarface: I do include non-free. But - maybe nouveau is being blacklisted "too late"? |
| 20:13.30 | eyalroz | gnarface: I'm on Beowulf and it's a GTX 1050 Ti, so not that new. |
| 20:13.40 | eyalroz | ... but not that old either. |
| 20:16.49 | Venker | https://gist.github.com/pgmartinez/c5c8ae2ecf7d21aff53fdaadef4b1679 |
| 20:19.23 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
| 20:30.51 | eyalroz | gnarface: perhaps I should try an unload command for nouveau in the same file as the nvidia load commands, on an earlier line? |
| 20:30.52 | gnarface | eyalroz: uh... well maybe. it's easy to check by looking in the output of lsmod. afaik only one or the other can be loaded, though it's possible you've managed to end up with neither working right. fyi the 1050 *is* too old though for the stock ascii versions, i'm pretty sure |
| 20:31.10 | eyalroz | gnarface: The nvidia drivers are what actually get loaded. |
| 20:31.24 | gnarface | eyalroz: sorry i mean that the 1050 *is* too new for the stock ascii versions |
| 20:32.31 | eyalroz | gnarface: But why would the stock ascii version matter, if I'm running Beowulf? ... and with CUDA 10.1 being installed? |
| 20:33.00 | eyalroz | Also, GTX 1050 Ti was released in late 2016. |
| 20:33.04 | gnarface | eyalroz: oh, sorry i missed that you said that. and actually if you're just using this for cuda and not using it as a display, i don't think it matters |
| 20:33.21 | eyalroz | Using it just for computation. |
| 20:33.47 | ullet | are you good with ze NN's eyalroz |
| 20:34.36 | ullet | i'd like to upgrade old videos but it's OT here. sorry. |
| 20:35.53 | gnarface | eyalroz: but fyi according to this, 1050 support wasn't added to the linux version of the driver until version 375.20, in november of 2016: https://www.nvidia.com/Download/driverResults.aspx/111596/en-us |
| 20:36.33 | gnarface | eyalroz: (and the ascii version is frozen at 340.something, which is why i thought that was relevant) |
| 20:36.35 | eyalroz | ullet: I'm actually exploring other aspects of GPU computing. NN's are very fashionable, I think they're not very challening in terms of putting the GPU to new uses. They work too well without you having to break a sweat, design-wise. |
| 20:37.10 | ullet | i'd be happy if i could operate them properly. oh well. i can write shadertoys. |
| 20:37.46 | eyalroz | gnarface: Luckily, beowulf has CUDA 10.1 with driver version 430.50 ... |
| 20:38.39 | gnarface | eyalroz: did you get CUDA from the beowulf repo or is that something you have to install from nvidia's shell script thingy directly? |
| 20:38.47 | eyalroz | ullet: I can't do NN work myself. I just know that it's not a challenge getting them to run efficiently on GPUs. Analytic databases, however, are a different story... |
| 20:39.03 | eyalroz | gnarface: beowulf repo - I'm 95% certain. |
| 20:39.17 | gnarface | eyalroz: beowulf is at 418.something, mabye you have some of two versions installed and that's the conflict? |
| 20:39.45 | gnarface | eyalroz: do a "dpkg -l |grep nvidia -i" and see if you see 418.xx cruft mixed in there |
| 20:40.57 | eyalroz | I see the two different versions in the apt package cache |
| 20:41.10 | gnarface | we only care about installed versions |
| 20:41.25 | eyalroz | the installed version is 430.50-1 |
| 20:41.55 | eyalroz | Status: install ok installed |
| 20:42.04 | gnarface | eyalroz: i'm not seeing any sign of version 430 in the devuan repos |
| 20:42.28 | eyalroz | Maybe it's another sign of me having a somewhat messed up apt state again :-( |
| 20:42.48 | mason | fsmithred: Ah, found one issue with accountsservice - it only provides a systemd service unit. |
| 20:42.55 | gnarface | eyalroz: well, or mabye you got some stuff directly from nvidia and forgot? |
| 20:43.14 | eyalroz | gnarface: Nope, the package maintainer is "Debian NVIDIA Maintainers" |
| 20:43.19 | gnarface | hmm, weird |
| 20:43.47 | eyalroz | and when I get stuff directly from nvidia, I get CUDA+drivers together and install CUDA to /usr/local/cuda-X.Y ; yet CUDA 10.1 is installed under /usr |
| 20:46.11 | gnarface | eyalroz: but pkginfo.devuan.org says you should have cuda 9.2.x, i think. can you confirm? https://pkginfo.devuan.org/cgi-bin/d1pkgweb-query?search=cuda&release=beowulf |
| 20:46.11 | gnarface | eyalroz: oh, 10.1 may have come from beowulf-backports... |
| 20:46.17 | gnarface | eyalroz: i'm seeing it here: https://packages.debian.org/search?keywords=cuda&searchon=names§ion=all&suite=buster-backports |
| 20:46.44 | eyalroz | gnarface: Very possibly. |
| 20:46.45 | *** join/#devuan Centurion_Dan (~Thunderbi@devuan/developer/centuriondan) |
| 20:46.54 | gnarface | eyalroz: but nvidia-driver in beowulf backports should be 440 now not 430, so maybe your backports are just out of date |
| 20:47.23 | gnarface | eyalroz: remember to add "-t beowulf-backports" or it will ignore backported packages during upgrades |
| 20:47.23 | eyalroz | My backports are out of date, since I commented them out at some point to resolve some apt issues you helped me with :-) |
| 20:47.42 | eyalroz | Ok, apt-get upgrade time |
| 20:48.06 | gnarface | eyalroz: yea that happens to often for me to remember the specific issue, sorry, but i would have definitely recommended to NOT just "apt-get -t beowulf-backports upgrade" |
| 20:48.08 | eyalroz | gnarface: Sorry I took you on a bit of a wilf goose chase again |
| 20:48.36 | gnarface | eyalroz: no worries, just don't apt-get upgrade all of backports. uncomment it, then upgrade just the nvidia packages (with -t beowulf backports), then comment it out again |
| 20:49.07 | gnarface | eyalroz: (mabye add a comment about this in the sources.list so you remember next time) |
| 20:49.53 | gnarface | eyalroz: what kernel do you have? you might need that too, not sure. the backports one should be at 5.4 and the stock one is 4.19 |
| 20:50.23 | eyalroz | 5.2.0-3 |
| 20:50.37 | gnarface | yea, so that's definitely also an out-of-date backports kernel |
| 20:53.05 | eyalroz | gnarface: Turns out I also have a libc6 from backports. Ouch. |
| 20:53.56 | gnarface | eyalroz: ouch. yea, that's specifically why i would have said not to just blindly apt-get upgrade the whole thing from beowulf and only just get the kernel and nvidia packages specifically (and any related firmware if relevant) |
| 20:54.08 | gnarface | eyalroz: from beowulf-backports* |
| 20:56.15 | eyalroz | gnarface: I had enabled backports when I first installed beowulf - a mistake on my part. Well, it looks like I'm going to have to lie in this bed after I've made it. |
| 20:58.22 | fsmithred | you could pin beowulf-backports to -1 to downgrade |
| 20:58.40 | fsmithred | dpkg -l |grep bpo |
| 20:58.57 | fsmithred | to see what's from backports (plus a few false positives) |
| 21:01.57 | eyalroz | fsmithred: Can I actually downgrade everything from backports to the non-backports versions? When that includes downgrading libc6 and all of its dependent packages? |
| 21:03.56 | gnarface | eyalroz: according to Debian, downgrades aren't officially supported, however you can probably make it happen |
| 21:04.23 | eyalroz | gnarface: Not sure it's worth the trouble at this point, but it's good to know. |
| 21:05.49 | eyalroz | fsmithred: How to I do the pinning, exactly? |
| 21:10.13 | *** join/#devuan Kizano (markizano@2600:3c00::f03c:91ff:fec8:382d) |
| 21:11.47 | *** join/#devuan Kizano (markizano@2600:3c00::f03c:91ff:fec8:382d) |
| 21:15.07 | fsmithred | eyalroz, I don't know what happens if libc6 is from backports |
| 21:15.23 | fsmithred | I'll get you an example |
| 21:15.59 | fsmithred | three lines in a file in /etc/apt/preferences.d |
| 21:16.04 | fsmithred | Package: * |
| 21:16.19 | fsmithred | Pin: release a=beowulf-backports |
| 21:16.27 | fsmithred | Pin-Priority: -1 |
| 21:16.32 | fsmithred | oh |
| 21:16.33 | fsmithred | no |
| 21:16.40 | eyalroz | no? |
| 21:16.43 | fsmithred | pin beowulf to 1001 |
| 21:16.52 | fsmithred | sorry - got a fever and toothache right now |
| 21:17.05 | eyalroz | oh... I'm sorry to hear that! |
| 21:17.08 | fsmithred | anything I say could be from another dimension |
| 21:17.19 | fsmithred | first line is same - all packages |
| 21:17.27 | fsmithred | Pin: release n=beowulf |
| 21:17.39 | fsmithred | Pin-Priority: 1001 |
| 21:17.40 | eyalroz | fsmithred: shouldn't I also pin beowulf-updates and beowulf-security to something higher then? |
| 21:17.49 | fsmithred | probably |
| 21:17.57 | fsmithred | yeah, that makes sense |
| 21:18.15 | fsmithred | use n=beowulf, a=beowulf-whatever |
| 21:18.18 | fsmithred | I think |
| 21:18.35 | eyalroz | So, a 3-line entry for each repo? |
| 21:18.40 | fsmithred | yes |
| 21:18.47 | fsmithred | can all be in same file |
| 21:19.16 | fsmithred | not sure if you need the -1 on bpo |
| 21:19.21 | fsmithred | I'd try without that first |
| 21:19.36 | fsmithred | apt -s upgrade to see what will happen |
| 21:20.01 | fsmithred | how many backports packages did you end up with? |
| 21:20.15 | eyalroz | fsmithred: Apparently, nothing happens when I apt-s upgrade |
| 21:20.30 | eyalroz | oh, wait |
| 21:21.14 | eyalroz | for the beowulf repo, should it be "n=beowulf, a=beowulf" ? |
| 21:21.52 | fsmithred | n for name |
| 21:22.03 | fsmithred | a for almost a name? |
| 21:22.34 | eyalroz | fsmithred: I don't follow. Do I need an n= and an a= for each of three repos? |
| 21:22.53 | fsmithred | no |
| 21:23.15 | fsmithred | plain beowulf gets 'Pin: release n=beowulf' |
| 21:23.31 | fsmithred | anything that's not exactly a codename gets a= |
| 21:23.56 | fsmithred | that would be the other three |
| 21:24.11 | fsmithred | -backports, -security, -updates |
| 21:24.51 | eyalroz | Ah, ok. |
| 21:25.46 | eyalroz | So, apt -s upgrade gives: |
| 21:25.46 | eyalroz | <PROTECTED> |
| 21:25.46 | eyalroz | <PROTECTED> |
| 21:25.46 | eyalroz | <PROTECTED> |
| 21:25.46 | eyalroz | E: Broken packages |
| 21:26.11 | eyalroz | I could just remove these, maybe? |
| 21:26.20 | fsmithred | maybe |
| 21:26.23 | gnarface | it might work |
| 21:26.36 | fsmithred | another thing that might work is to use aptitude |
| 21:26.43 | fsmithred | it might give you alternatives |
| 21:26.51 | gnarface | yea, it's made for figuring out this type of thing |
| 21:27.08 | eyalroz | when I apt -s upgrade after the removal it comes up with another broken package |
| 21:27.40 | fsmithred | that could go on for some time |
| 21:27.42 | eyalroz | oh, but after removing that, apt -s upgrade has a super-long output |
| 21:28.02 | eyalroz | with a zillion downgrades. success! |
| 21:28.06 | eyalroz | Let's do this thing. |
| 21:28.13 | fsmithred | cool |
| 21:28.16 | eyalroz | and hope I don't get hosed. |
| 21:28.31 | gnarface | make sure you have a live image ready on usb or cd |
| 21:28.45 | fsmithred | yeah, good idea |
| 21:29.12 | Venker | seeU |
| 21:29.54 | eyalroz | gnarface: I think I have one somewhere; plus I have a laptop if push comes to shove. Now just need to wait for some 4.5 GB of downgrade package downloads. Thank you both (gnarface and fsmithred). |
| 21:30.01 | gnarface | Venker: did anyone address your concern? i don't know the answer, sorry. maybe ask in #devuan-dev |
| 21:30.55 | Venker | gnarface: I will, thanks. I think I did some progress regarding that code |
| 21:44.54 | systemdlete | So I installed tlp, and that brought with it network-manager, which I do NOT want; I use wicd. So I uninstalled network-manager. But /etc/init.d/network-manager lingers. ??? |
| 21:45.36 | systemdlete | It's not enabled, but still, why is it still there, even after I removed it with the apt tools? |
| 21:45.49 | systemdlete | I tried re-installing it and uninstalling it. No dice. |
| 21:46.51 | systemdlete | and why does installing tlp, which is power-related, drag a tool like network-mangler along with it? |
| 21:49.26 | *** join/#devuan tierce (~raoulzeca@77.109.101.14) |
| 21:55.55 | mason | systemdlete: When you delete things, you can purge them as well... apt purge foo, or apt --purge autoremove, etc. |
| 21:57.02 | systemdlete | oh yes. I forgot about that. But why does it tell me that /etc/init.d/network-manager is owned by network-manager? Normally, if a package is not installed, I don't expect it to know anything about files owned by the package. |
| 21:59.00 | systemdlete | but to my primary question: Why network-manager for tlp? |
| 22:05.57 | *** join/#devuan pekman (~pekman@unaffiliated/pekman) |
| 22:07.30 | *** join/#devuan bpmedley (~bpm@2601:240:d:a0a0:9c:b4ad:e74c:438a) |
| 22:09.02 | *** join/#devuan phyre (~phyre___@78.30.23.107) |
| 22:19.19 | *** join/#devuan blizzow (~blizzow@97-122-221-232.hlrn.qwest.net) |
| 22:25.26 | *** join/#devuan fleeky (~fleeky@2601:645:4300:6580:315c:801b:2f2e:457f) |
| 22:30.23 | *** join/#devuan xcm (~xcm@ipd114.250.tellas.gr) |
| 22:34.30 | *** join/#devuan gnu_srs (~srs@2-248-159-26-no549.tbcn.telia.com) |
| 22:39.57 | *** join/#devuan frabbit (~free_rabb@unaffiliated/free-rabbit/x-8401877) |
| 22:40.17 | frabbit | hi people. what ports are open by default? |
| 22:41.06 | ullet | a 'your mom' joke would be inappropriate i suppose |
| 22:41.41 | frabbit | ullet: your dad jokes are welcome 0P |
| 22:41.45 | frabbit | =P |
| 22:42.04 | ullet | :) sorry. I don't know the answer frabbit - i'm not sure any firewal comes configured with devuan |
| 22:42.17 | ullet | i think they're all 'open' just not listened-to |
| 22:42.46 | frabbit | iv runned a portscan on my publich ip adress and get 3 open ports there |
| 22:42.55 | frabbit | *public |
| 22:43.06 | ullet | sshd might be started by default. |
| 22:43.24 | frabbit | and it says Not shown: 997 closed ports |
| 22:43.28 | ullet | but your public ip is normally served by a router |
| 22:44.07 | frabbit | the three are ftp, somain and sip |
| 22:44.12 | frabbit | *domain |
| 22:59.43 | *** join/#devuan bpmedley (~bpm@2601:240:8:7099:455b:a4b2:88a7:b819) |
| 23:17.40 | *** join/#devuan Xelraa (~xelra@2a02:418:6a04:178:209:51:137:1) |
| 23:17.40 | *** join/#devuan Xelraa (~xelra@unaffiliated/xelraa) |
| 23:29.15 | *** join/#devuan Xenguy (~Xenguy@devuan/community/Xenguy) |
| 23:49.06 | *** join/#devuan some_alex (~alex@188.239.60.41) |
| 23:50.02 | some_alex | hi, I'm going to install X now. I see 2 packages: xserver-xorg and xorg. Which one should I install? |