previous
2022-08-08
09:52:10 <tjay> hello everyone :)
10:16:53 <rwp> Hello tjay! Please join us in #devuan-offtopic for social pleasantries. :-)
10:22:02 <golinux> Technical questions? Post here
10:48:21 <fluffywolf> what does this output? tr 'LnDi xveGaN/uU' '!eh r iyvoeen' </etc/issue
16:41:41 <wikan> can someone share /etc/subgid and /etc/subuid content?
16:41:56 <wikan> i am not sure, maybe I overwrite something
16:44:55 <bradd> https://termbin.com/f7md
16:45:02 <rrq> "man subuid"
16:46:09 <wikan> bradd, so all entries are yours?
16:46:25 <wikan> file was empty befre editing, correct?
16:46:43 <bradd> I did a 'cat /etc/sub?id > t' then a cat t | nc termbin.com 9999
16:46:53 <bradd> i didnt modify anything. its the default for me
16:50:06 <wikan> thanks bradd
18:04:24 <wikan> has anyone any knowledle about lxc?
18:29:21 <cytokine_storm> where is the image of devuan boot splash screen located ?
18:33:08 <cytokine_storm> got it
19:05:01 <fouga> Hello, is Kerberos issue off topic?
20:54:26 <FilipZ> Hi! I have a question. How should I reset the wpa_supplicant?
21:53:59 <___used> Define reset?
22:15:09 <eyalroz> I'm having an issue with my USB earphones, after switcing from Chimaera to Daedalus:
22:15:26 <eyalroz> Only the right side is getting audio, and the left is silent
22:16:08 <eyalroz> These are Logitech H340's
22:22:09 <FilipZ> ___used: My bad. I meant to write restart.
22:22:31 <FilipZ> How to restart wpa_supplicant?
22:33:26 <___used> try: sudo service wicd restart
23:15:42 <FilipZ> Thank you!
---------- 2022-08-09 ----------
04:22:12 <todrik> Hello! 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 that
04:22:21 <todrik> Anyone that can help me?
04:24:56 <golinux> todrik: I wish I could . . . be patient . . .
04:25:02 <fsmithred> todrik, runit will use the sysvinit script if there are no runscripts for it.
04:25:32 <fsmithred> did you install a full desktop from the installer, or did you start with a minimal install and add only what you wanted?
04:26:09 <todrik> :fsmithred minimal install!
04:26:35 <fsmithred> you installed wpasupplicant and wireless-tools?
04:26:43 <gnarface> i think this has come up before and it's possible to accidentally not have the init scripts
04:27:02 <todrik> Ahh I have not
04:27:03 <fsmithred> and you installed the appropriate firmware for your wireless hardware?
04:27:05 <todrik> Ill try that
04:27:33 <fsmithred> and make sure /etc/init.d/network-manager exists
04:28:08 <rwp> Also look at "rfkill list" to ensure nothing is blocked.
04:28:32 <rwp> I sometimes bump the switch on mine and find it blocked by mistake.
04:28:57 <todrik> Both wpa supplicant and wireless tools where installed
04:29:46 <gnarface> was it sysv-rc that was missing last time this happened?
04:29:49 <gnarface> or is that for sysvinit only?
04:30:10 <todrik> and /etc/init.d/network-manager exists
04:30:41 <gnarface> check on the wifi device firmware. some of them need a package from non-free
04:30:41 <todrik> Dumb question: How do I know what driversare needed for my wireless hardware?
04:30:51 <gnarface> you go by vendor generally
04:30:55 <gnarface> the brand
04:30:58 <fsmithred> lspci | grep -i net
04:31:20 <gnarface> and 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 wep
04:32:21 <todrik> AH okay, so how do I get those? Go to intels website and download or something like that?
04:32:26 <gnarface> no no
04:32:35 <gnarface> you just add non-free to your sources.list temporarily
04:32:57 <gnarface> then update and install them as usual (then, i recommend, take non-free back out)
04:33:25 <fsmithred> which intel is it?
04:34:08 <todrik> Intel Wireless 7260 (rev 83) it says
04:34:46 <gnarface> here's an example /etc/apt/sources.list file with the goods: https://paste.debian.net/1249835/
04:34:46 <todrik> so /etc/apt/sources.list and add non-free then apt update and apt upgrade and then back and remove non-free?
04:35:04 <gnarface> here's one without: https://paste.debian.net/1249836/
04:35:11 <fsmithred> you missed 'apt install firmware-...'
04:35:11 <gnarface> no no, don't just upgrade
04:35:31 <fsmithred> I'm checking the debian wiki for your chipset
04:35:50 <todrik> Non free are uncommented!
04:36:03 <gnarface> just 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 stuff
04:36:04 <fsmithred> install firmware-iwlwifi
04:36:24 <todrik> Ahh okay
04:36:34 <gnarface> so that's why i recommend just installing whatever single package you need then removing the contrib/non-free stuff after
04:36:43 <gnarface> (i recommend the same methodology when using backports)
04:37:06 <gnarface> only problem is, if it needs to be updated you have to remember that
04:38:10 <gnarface> backports 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)
04:38:28 <gnarface> but don't resort to that unless the stable one doesn't work
04:38:53 <todrik> Okay so add whats in the pastebin in /etc/apt/sources.list, apt install firmware-iwlwifi and then remove what I added in the first step
04:39:09 <fsmithred> yeah
04:39:17 <gnarface> make sure to remember you have to apt update after every change to sources.list
04:40:27 <todrik> Trying it now, thanks so much
04:49:16 <golinux> Ha! There you are . . . not on the PM
05:00:52 <todrik> It worked
05:00:55 <todrik> Thanks bros
05:01:22 <gnarface> horaay
05:01:26 <fsmithred> cool
05:18:22 <FilipZ> I 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?
05:21:47 <pon> What does it mean that iptables is not installed on my devuan daedalus install?
05:22:29 <fluffywolf> iptables is considered obsolete
05:22:35 <onefang> IPtables is being replaced by NFtables.
05:22:38 <gnarface> FilipZ: might have worked if wicd was installed, not sure. check for something in /etc/init.d/ to restart
05:23:06 <gnarface> FilipZ: (or just straight out kill wpa_supplicant, it will be started again automatically by anything that needs it)
05:23:45 <pon> How can I make blueman use nftables then?
05:24:00 <gnarface> i think you can still just install iptables
05:24:07 <gnarface> it should still be fully functional
05:24:30 <gnarface> unless that changed in daedalus recently
05:25:02 <gnarface> nftables is supposed to be reverse-compatible but reports are mixed on the truth of that
05:27:39 <eyalroz> After 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?
05:28:19 <FilipZ> granface: 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?
05:29:04 <gnarface> FilipZ: something named after your network manager if it's not wicd, or something called "wpasupplicant" or "wpa_supplicant" or the like
05:29:30 <eyalroz> ... and to be more specific: I get krita once in the recommended apps, then 22 times in "other apps"
05:29:44 <gnarface> FilipZ: 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. ymmv
05:30:20 <FilipZ> I am using Connman now. Should I just restart connman, that is here?
05:30:32 <gnarface> FilipZ: worth a try
05:30:51 <gnarface> eyalroz: dunno does krita have 22 separate binaries or something like that? i could only speculate
05:31:51 <eyalroz> gnarface: it has krita and krita_runner
05:33:44 <pon> It 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?
05:35:09 <fluffywolf> I've never been able to make krita work, due to incompetence on the part of their maintainers and packagers.
05:35:26 <eyalroz> gnarface: But apparently, there are a bunch of krita desktop files though
05:35:30 <fluffywolf> so random crap like that is very unsurprising
05:36:20 <gnarface> eyalroz: yea if there's .desktop things or symlinks or something that would be my second list of suspects
05:36:24 <eyalroz> indeed, 23 desktop files in the package. I wonder if I should report that as a bug to the debian package maintainer.
05:37:14 <gnarface> maybe they're important but what the hell are they? a different startup icon for every different translation or something?
05:37:44 <fluffywolf> if you really want fun, try making the version distributed on their website run. :P
05:44:58 <eyalroz> gnarface: So, it turns out they differ mostly by the mime type listed in each of them,
05:45:01 <eyalroz> but the command line is the same
05:45:59 <eyalroz> so, one for each format basically
05:46:15 <eyalroz> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1016921
05:49:13 <FilipZ> gnarface: 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 service
05:49:13 <FilipZ> n 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.
05:50:45 <fluffywolf> the whole .desktop thing is a shitshow that debian never should have bowed to.
05:51:18 <fluffywolf> debian 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.
05:51:37 <gnarface> FilipZ: 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)
05:52:32 <gnarface> FilipZ: 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 properly
05:52:37 <FilipZ> It seems that restarting the connman service does it, but killing the wpa_supplicant does not, or only sometimes.
05:52:52 <gnarface> there might be a time factor involved
05:55:15 <FilipZ> Last 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.
05:56:48 <fluffywolf> I have to unload and reload the wifi modules on this laptop randomly. probably a kernel bug.
05:58:13 <gnarface> yea i had driver issues, i had power issues, i had race condition issues with hostapd
05:58:17 <gnarface> still trying to get to the bottom of it
05:58:18 <gnarface> wifi sucks
05:59:10 <gnarface> FilipZ: maybe connman has some pre/post hooks you can use to run some shell commands to work around the issue for now?
05:59:46 <FilipZ> How can I check it, and what are they?
06:00:00 <gnarface> i don't know enough about connman
06:01:24 <gnarface> but 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)
06:02:06 <gnarface> that was for the host side
06:02:33 <gnarface> on the client side i think i also had to reload the driver module between step 4 and 5
06:03:17 <gnarface> and for whatever reason, it would go longer without problems if i had a running constant ping going through from the client
06:03:25 <gnarface> i believe this is related to a power management bug in the kernel
06:03:53 <gnarface> something that only affects cheap realtek stuff
06:04:21 <gnarface> and only if you're using a linux host (call me paranoid but i believe this is focused sabotage)
06:26:09 <FilipZ> gnarface: 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?
06:26:30 <gnarface> i doubt it
06:27:15 <gnarface> although... maybe if the cause were something about dhcp going off the rails
06:27:19 <FilipZ> As a wireless card I use "Intel Wireless 3165".
06:27:37 <gnarface> does the same dhcp process manage both of them?
06:27:38 <FilipZ> gnarface: How can I check it?
06:27:48 <gnarface> well are you using dhcp for both of them?
06:28:14 <gnarface> there 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 using
06:28:32 <gnarface> basically just look for any conspicuous errors right around the time it disconnects you
06:29:33 <FilipZ> gnarface: I don't know, but it is probably as it would be by default, so then I would use dhcp for both, right?
06:29:54 <gnarface> yea probably
06:30:12 <gnarface> i mean you'd know if you didn't because it would have involved manually typing in an ip address, subnet mask, gateway, etc
06:30:17 <FilipZ> I only used a direct connection when my wireless connections didn't work at all.
06:45:11 <FilipZ> gnarface: 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.
06:45:45 <gnarface> FilipZ: paste.debian.net
06:50:33 <FilipZ> gnarface: Thanks! This is with what happened when I it broke: https://paste.debian.net/1249848/
06:51:46 <FilipZ> gnarface: And this is what happened when I restarted a connman service, to fix it: https://paste.debian.net/1249849/
07:01:02 <gnarface> FilipZ: ah, right away i see something suspicious. you have avahi-daemon installed and it's interfering with stuff.
07:02:18 <gnarface> FilipZ: i dunno why or what or even if it's the problem but i've had enough complications with avahi-daemon that unless you're sure you're using it, i'd recommend uninstalling it before re-evaluating the problem
07:04:54 <gnarface> could be a red herring but the easiest way to know is to just remove it
07:35:06 <FilipZ> gnarface: I removed avahi-daemon, then did the same thing as before, but it still causes the issue.
07:35:38 <FilipZ> Would you like a copy of those logs again?
07:37:01 <gnarface> FilipZ: was that with debugging turned on in dhcpcd and wpa_supplicant?
07:37:16 <gnarface> (or whatever your dhcp client was?)
07:37:26 <FilipZ> I don't think so. Then what should I do and how?
07:37:49 <FilipZ> How do I turn debugging on those?
07:38:01 <gnarface> check the man pages, put the debugging flags in the configs or on the command-line of both those daemons, then capture the log from when it fails
07:38:48 <gnarface> and keep avahi-daemon out of the mix for now
07:39:05 <gnarface> it's probably not even doing anything helpful for you
07:39:15 <FilipZ> It's removed, and then I did sudo killall avahi-daemon, just to be sure.
07:39:47 <gnarface> the use case is fairly contrived and involves spending a lot of time moving between strange new networks that all are 100% other avahi or mac osx clients
07:41:04 <gnarface> also try to take note of if the signal strength is low when it dies on you
07:43:21 <FilipZ> The Wi-Fi is set very close, so it is not for now.
07:44:36 <gnarface> just keep an eye on it, i've noticed sometimes when there's a power management issue it'll reflect in a seemingly unexplained signal strength dip
07:53:20 <FilipZ> I couldn't find a dhcpcd daemon.
07:53:40 <FilipZ> It seems that I don't have such.
07:54:35 <FilipZ> How can it be?
07:54:44 <gnarface> you must
07:54:49 <gnarface> run this: dpkg -l |grep dhc
07:55:39 <gnarface> might not be called dhcpcd
07:56:20 <FilipZ> Thanks! Now I see it. dhcpcd-dbus, isc-dhcp-client and isc-dhcp-common were printed.
07:56:59 <FilipZ> So I have to set these flags on that first?
07:57:12 <gnarface> on isc-dhcp-client
07:57:41 <gnarface> i'm actually not sure dhcpcd-dbus is supposed to be present with isc-dhcp-client
07:58:28 <FilipZ> I don't know how it works, and what exactly are those daemons.
07:59:22 <gnarface> well isc-dhcp-client is the dhcp client daemon in question, isc-dhcp-common is just some cruft that goes with it, and dhcpcd-dbus is supposed to be dbus integration for a different dhcp client, which seems out of place
07:59:32 <gnarface> but i could be wrong about that
07:59:52 <FilipZ> There were no man page for dhcpcd-dbus, what is it?
08:00:10 <FilipZ> Oh, now I see you wrote it, nvm.
08:00:15 <gnarface> dbus integration for a different dhcp client, like i said. not the isc one
08:01:15 <FilipZ> Like what other, different client?
08:01:22 <gnarface> dhcpcd
08:02:05 <gnarface> there's one called isc-dhcp and one called dhcpcd
08:02:21 <FilipZ> $ man isc-dhcp-client
08:02:21 <FilipZ> No manual entry for isc-dhcp-client
08:02:56 <gnarface> i think you might have to go by the name of the config file
08:03:08 <gnarface> just go to their webpage, they have docs online
08:03:39 <gnarface> oh maybe it's called dhclient
08:03:45 <gnarface> try man dhclient or dhclient.conf
08:03:46 <FilipZ> What name exactly?
08:03:53 <gnarface> just look in "ps aux" for the daemon name
08:04:01 <gnarface> there won't be a lot with "dhcp" in the name
08:04:29 <gnarface> yea i think it might be called dhclient, try "man dhclient" first
08:04:55 <FilipZ> There is a page for dhclient, should I set this flag for it?
08:05:15 <gnarface> yes of course
08:05:24 <gnarface> don't forget to do something for wpa_supplicant too
08:05:33 <FilipZ> "Enable verbose log messages"?
08:07:10 <gnarface> also check if anything depends on dhcpcd-dbus, that might not belong on your system
08:07:25 <gnarface> if you were using the other dhcp client before, maybe it got left behind when you switched
08:09:00 <FilipZ> I checked dhcpcd-dbus in the package manager, and it shows that it is not installed. It is marked with a blank square. How can it be?
08:09:23 <gnarface> oh maybe it was removed already but there's just configs left
08:09:48 <gnarface> when you run "dpkg -l |grep dhcpcd-dbus" what is in the left column?
08:10:39 <FilipZ> rc dhcpcd-dbus
08:10:47 <gnarface> eh that's fine then
08:10:58 <FilipZ> What does it mean?
08:11:28 <FilipZ> "rc", is it?
08:11:28 <gnarface> not sure the literal meaning but basically "rc" means that it's been removed but there's still config files or vestigial directories left behind
08:11:43 <gnarface> if you don't want that to happen when removing stuff use "--purge"
08:12:22 <FilipZ> Will making a "complete removal in the gui package manager do the same?
08:12:38 <gnarface> i don't know for sure but it should
08:13:01 <gnarface> anyway nevermind that, it's not related to the problem after all
08:13:33 <FilipZ> Alright. I think it worked out, as the same command prints nothing.
08:18:15 <FilipZ> In the wpa_supplicant man page there is "-d Increase debugging verbosity (-dd even more).", is it enough to just pass this flag?
08:21:07 <FilipZ> Oh, I think it doesn't just work with a flag after the program name. A wall of text got printed out, like the command wasn't complete.
08:22:51 <FilipZ> Then what should I input?
08:42:02 <gnarface> FilipZ: afaik "-d" should work. there should be a file in /etc/default you can put it in
08:42:33 <gnarface> it might have a commented-out example even
08:43:01 <gnarface> it will increase the amount of lines output
2022-08-09
next