libera/#devuan/ Tuesday, 2022-08-09

tjayhello everyone :)02:52
rwpHello tjay!  Please join us in #devuan-offtopic for social pleasantries. :-)03:16
golinuxTechnical questions? Post here03:22
fluffywolfwhat does this output?  tr 'LnDi xveGaN/uU' '!eh r  iyvoeen' </etc/issue03:48
dbbsEDRGA+08:04
dbbs+08:07
wikancan someone share /etc/subgid and /etc/subuid content?09:41
wikani am not sure, maybe I overwrite something09:41
braddhttps://termbin.com/f7md09:44
rrq"man subuid"09:45
wikanbradd, so all entries are yours?09:46
wikanfile was empty befre editing, correct?09:46
braddI did a 'cat /etc/sub?id > t' then a cat t | nc termbin.com 999909:46
braddi didnt modify anything. its the default for me09:46
wikanhmmm09:47
wikanthanks bradd09:50
braddnp09:50
wikanhas anyone any knowledle about lxc?11:04
cytokine_stormwhere is the image of devuan boot splash screen located ?11:29
cytokine_stormgot it11:33
fougaHello, is Kerberos issue off topic?12:05
fougaThanks12:05
FilipZHi! I have a question. How should I reset the wpa_supplicant?13:54
___usedDefine reset?14:53
eyalrozI'm having an issue with my USB earphones, after switcing from Chimaera to Daedalus:15:15
eyalrozOnly the right side is getting audio, and the left is silent15:15
eyalrozThese are Logitech H340's15:16
FilipZ___used: My bad. I meant to write restart.15:22
FilipZHow to restart wpa_supplicant?15:22
___usedtry: sudo service wicd restart15:33
FilipZThank you!16:15
todrikHello! I am using a fresh netinstall of devuan with runit and have just downloaded network manager using apt, however, nmtui wonth search the wifinetworks, it will just show an empty list. My guess was that I have to enable networkmanager daemon, but I cant really figure out how to do that21:22
todrikAnyone that can help me?21:22
golinuxtodrik: I wish I could . . . be patient . . .21:24
fsmithredtodrik, runit will use the sysvinit script if there are no runscripts for it.21:25
fsmithreddid you install a full desktop from the installer, or did you start with a minimal install and add only what you wanted?21:25
todrik:fsmithred minimal install!21:26
fsmithredyou installed wpasupplicant and wireless-tools?21:26
gnarfacei think this has come up before and it's possible to accidentally not have the init scripts21:26
todrikAhh I have not21:27
fsmithredand you installed the appropriate firmware for your wireless hardware?21:27
todrikIll try that21:27
fsmithredand make sure /etc/init.d/network-manager exists21:27
rwpAlso look at "rfkill list" to ensure nothing is blocked.21:28
rwpI sometimes bump the switch on mine and find it blocked by mistake.21:28
todrikBoth wpa supplicant and wireless tools where installed21:28
gnarfacewas it sysv-rc that was missing last time this happened?21:29
gnarfaceor is that for sysvinit only?21:29
todrikand /etc/init.d/network-manager exists21:30
gnarfacecheck on the wifi device firmware. some of them need a package from non-free21:30
todrikDumb question: How do I know what driversare needed for my wireless hardware?21:30
gnarfaceyou go by vendor generally21:30
gnarfacethe brand21:30
fsmithredlspci | grep -i net21:30
gnarfaceand all the drivers are already installed by default, what you might be missing though is that non-free firmware package, without which you'd only be able to use unencrypted wifi or possibly wep21:31
todrikAH okay, so how do I get those? Go to intels website and download or something like that?21:32
gnarfaceno no21:32
fsmithredno21:32
fsmithredlol21:32
gnarfaceyou just add non-free to your sources.list temporarily21:32
gnarfacethen update and install them as usual (then, i recommend, take non-free back out)21:32
fsmithredwhich intel is it?21:33
todrikIntel Wireless 7260 (rev 83) it says21:34
gnarfacehere's an example /etc/apt/sources.list file with the goods: https://paste.debian.net/1249835/21:34
todrikso /etc/apt/sources.list and add non-free then apt update and apt upgrade and then back and remove non-free?21:34
gnarfacehere's one without: https://paste.debian.net/1249836/21:35
fsmithredyou missed 'apt install firmware-...'21:35
gnarfaceno no, don't just upgrade21:35
fsmithredI'm checking the debian wiki for your chipset21:35
todrikNon free are uncommented!21:35
gnarfacejust doing an upgrade will get *everything* non-free that might be potentially relevant to your existing install, which frankly i would just recommend not doing because it's not all as well quality controlled as the free stuff21:36
fsmithredinstall firmware-iwlwifi21:36
todrikAhh okay21:36
gnarfaceso that's why i recommend just installing whatever single package you need then removing the contrib/non-free stuff after21:36
gnarface(i recommend the same methodology when using backports)21:36
gnarfaceonly problem is, if it needs to be updated you have to remember that21:37
gnarfacebackports might be relevant because if it's a *very* new device, you might need the newer firmware and kernel versions from backports (chimaera-backports to be specific)21:38
gnarfacebut don't resort to that unless the stable one doesn't work21:38
todrikOkay so add whats in the pastebin in /etc/apt/sources.list, apt install firmware-iwlwifi and then remove what I added in the first step21:38
fsmithredyeah21:39
gnarfacemake sure to remember you have to apt update after every change to sources.list21:39
todrikOkay!21:39
todrikTrying it now, thanks so much21:40
golinuxHa! There you are . . . not on the PM21:49
todrikIt worked22:00
todrikThanks bros22:00
gnarfacehoraay22:01
fsmithredcool22:01
FilipZI was recommended earlier to use "sudo service wicd restart" to restart the wpa_supplicant, but I only get the answer "unrecognized service". I checked for it, and see that I didn't even have this package installed. What does it have to do with a wpa_supplicant?22:18
ponWhat does it mean that iptables is not installed on my devuan daedalus install?22:21
fluffywolfiptables is considered obsolete22:22
onefangIPtables is being replaced by NFtables.22:22
gnarfaceFilipZ: might have worked if wicd was installed, not sure. check for something in /etc/init.d/ to restart22:22
gnarfaceFilipZ: (or just straight out kill wpa_supplicant, it will be started again automatically by anything that needs it)22:23
ponHow can I make blueman use nftables then?22:23
gnarfacei think you can still just install iptables22:24
gnarfaceit should still be fully functional22:24
gnarfaceunless that changed in daedalus recently22:24
gnarfacenftables is supposed to be reverse-compatible but reports are mixed on the truth of that22:25
eyalrozAfter installing daedalus, and when selecting an app to open an image file format (say JPG), I get lots and lots of entries for krita. Like 10 or so. Any idea why that could be?22:27
FilipZgranface: I went to the /etc/init.d/, and see a lot of different services services here. How do I know what "something" should I restart?22:28
gnarfaceFilipZ: something named after your network manager if it's not wicd, or something called "wpasupplicant" or "wpa_supplicant" or the like22:29
eyalroz... and to be more specific: I get krita once in the recommended apps, then 22 times in "other apps"22:29
gnarfaceFilipZ: maybe just something called "networking" but frankly i've had a lot of cases where wpa_supplicant doesn't restart right until i kill it anyway. ymmv22:29
FilipZI am using Connman now. Should I just restart connman, that is here?22:30
gnarfaceFilipZ: worth a try22:30
gnarfaceeyalroz: dunno does krita have 22 separate binaries or something like that? i could only speculate22:30
eyalrozgnarface: it has krita and krita_runner22:31
ponIt looks like blueman is supposed to be able to handle connections without network-manager using something called dhclient, does this make it not use iptables?22:33
fluffywolfI've never been able to make krita work, due to incompetence on the part of their maintainers and packagers.22:35
eyalrozgnarface: But apparently, there are a bunch of krita desktop files though22:35
fluffywolfso random crap like that is very unsurprising22:35
gnarfaceeyalroz: yea if there's .desktop things or symlinks or something that would be my second list of suspects22:36
eyalrozindeed, 23 desktop files in the package. I wonder if I should report that as a bug to the debian package maintainer.22:36
gnarfacemaybe they're important but what the hell are they? a different startup icon for every different translation or something?22:37
fluffywolfif you really want fun, try making the version distributed on their website run.  :P22:37
eyalrozgnarface: So, it turns out they differ mostly by the mime type listed in each of them,22:44
eyalrozbut the command line is the same22:45
eyalrozso, one for each format basically22:45
eyalrozhttps://bugs.debian.org/cgi-bin/bugreport.cgi?bug=101692122:46
gnarfacehmmm22:48
FilipZgnarface: I did sudo "killall wpa_supplicant", and it seemed to restart, as the list of wi-fi connections in the connman GUI dissapeared, and later reappeared, but later when I did it again, it somehow didn't restart, by what I mean is that this wi-fi list dissapeared and didn't appear. It didn't do anything after I triggered this connection error(by switching wi-fi interface off, and on, in Connman). I tried to do a "sudo service22:49
FilipZn restart" then, and that indeed helped, just as restarting the system does. It however is only a symptomatic treatment, and I still need to know how can I fix remove the cause.22:49
fluffywolfthe whole .desktop thing is a shitshow that debian never should have bowed to.22:50
fluffywolfdebian used to use their own system of menus and mime types, but the gnome/kde people forced them to switch to the .desktop crap, which is vastly inferior.22:51
gnarfaceFilipZ: i'm not sure i have a solution to that either. in my testing i've frequently had to kill wpa_supplicant so that whatever else i'm using that needs it can start it again itself (like you say - similar to a full reboot)22:51
gnarfaceFilipZ: when something goes wrong it simply seems to just hang and not get restarted properly, i wasn't able to narrow down why because i was having various other issues with my attempted wifi setup that prevented it from working properly22:52
FilipZIt seems that restarting the connman service does it, but killing the wpa_supplicant does not, or only sometimes.22:52
gnarfacethere might be a time factor involved22:52
FilipZLast time I had an issue with my connection manager disconnecting and connecting from a wi-fi connection, or just restarting in what seemed to be about regular time intervals, so maybe it somehow is like that.22:55
fluffywolfI have to unload and reload the wifi modules on this laptop randomly.  probably a kernel bug.22:56
gnarfaceyea i had driver issues, i had power issues, i had race condition issues with hostapd22:58
gnarfacestill trying to get to the bottom of it22:58
gnarfacewifi sucks22:58
gnarfaceFilipZ: maybe connman has some pre/post hooks you can use to run some shell commands to work around the issue for now?22:59
FilipZHow can I check it, and what are they?22:59
gnarfacei don't know enough about connman23:00
gnarfacebut what i was doing in my case was, 1) kill wpa_supplicant 2) ifdown the interface 3) ifconfig [interface] down if ifdown didn't work 4) down the network service (hostapd in this case, ymmv) 5) start the network service again, which started the other stuff normally (iirc)23:01
gnarfacethat was for the host side23:02
gnarfaceon the client side i think i also had to reload the driver module between step 4 and 523:02
gnarfaceand for whatever reason, it would go longer without problems if i had a running constant ping going through from the client23:03
gnarfacei believe this is related to a power management bug in the kernel23:03
gnarfacesomething that only affects cheap realtek stuff23:03
gnarfaceand only if you're using a linux host (call me paranoid but i believe this is focused sabotage)23:04
FilipZgnarface: I do have a Realtek RTL8111/8168/8411 ethernet controller, but it is for the wired connection use. Could it somehow cause bugs with the wireless connections, that are managed by the wireless card?23:26
gnarfacei doubt it23:26
gnarfacealthough... maybe if the cause were something about dhcp going off the rails23:27
FilipZAs a wireless card I use "Intel Wireless 3165".23:27
gnarfacedoes the same dhcp process manage both of them?23:27
FilipZgnarface: How can I check it?23:27
gnarfacewell are you using dhcp for both of them?23:27
gnarfacethere should be a way to get more debugging info dumped into /var/log/daemon.log both from wpa_supplicant and from whatever dhcp client you're using23:28
gnarfacebasically just look for any conspicuous errors right around the time it disconnects you23:28
FilipZgnarface: I don't know, but it is probably as it would be by default, so then I would use dhcp for both, right?23:29
gnarfaceyea probably23:29
gnarfacei mean you'd know if you didn't because it would have involved manually typing in an ip address, subnet mask, gateway, etc23:30
FilipZI only used a direct connection when my wireless connections didn't work at all.23:30
FilipZgnarface: So I make it break, and then restarted Connman, and copied logs of what was happening at this time. Could you please share a link of that pastebin-like site? I would send links to those logs on it, then.23:45
gnarfaceFilipZ: paste.debian.net23:45
FilipZgnarface: Thanks! This is with what happened when I it broke: https://paste.debian.net/1249848/23:50
FilipZgnarface: And this is what happened when I restarted a connman service, to fix it: https://paste.debian.net/1249849/23:51

Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!