| FilipZ | gnarface: Hi! Could you check those logs https://paste.debian.net/1250714/ ? I set the dhclient and wpa_supplicant verbosity flags here, as you asked earlier. | 00:51 |
|---|---|---|
| FilipZ | If there is anything that could suggest that there is something wrong with my wireless connection, I mean. | 00:53 |
| gnarface | this FilipZ guy has to stick around longer | 01:04 |
| gnarface | and also someone needs to tell him i don't have any idea what is wrong | 01:05 |
| gnarface | i fixed mine by changing devices and kernels both entirely | 01:05 |
| gnarface | oh and power supplies | 01:06 |
| gnarface | the old device still doesn't work | 01:06 |
| gnarface | not reliably | 01:06 |
| gnarface | very similiar to this | 01:06 |
| gnarface | i have to presume a lot of the realtek ones just aren't working | 01:06 |
| gnarface | maybe some internal power management issue | 01:06 |
| FilipZ | Thank you for the answer. The Realtek network adapter I use is only for the wired connection, like I mentioned earlier. I use an Intel's network adapter for the wireless connection. | 01:27 |
| gnarface | oh yea, i forgot | 01:56 |
| gnarface | hmm | 01:57 |
| gnarface | maybe it's not just realtek ones then | 01:57 |
| gnarface | but it's not all of them either | 01:57 |
| joerg | looks like a mess | 01:57 |
| gnarface | only thing weird i see that i don't have is the thing about /proc/net/pnp but i also don't have connman | 01:58 |
| joerg | wlan logs often looks like a mess, but this! | 01:58 |
| joerg | eventually I thought "where's avahi? I'd expect avahi in this mess, causing it" then I felt nausea | 01:59 |
| joerg | why does it look like every daemon and then a few were constantly fighting about routing and power management and DHCP leases and VPN? | 02:04 |
| joerg | tried to understand what's going on there bit it gives me headache | 02:04 |
| FilipZ | I decided to change connman back to the NetworkManager, but semething didn't worked out, and I cannot connect yo the internet, even though nm-tray shows a working connection. | 04:10 |
| FilipZ | Could someone help? | 04:11 |
| gnarface | did you remove connman first? | 04:13 |
| FilipZ | No.I installed the NetworkManager first, and then stopped the connman, and then removed it, and restarted the NetworkManager. | 04:16 |
| gnarface | i can't imagine what went wrong | 04:18 |
| gnarface | but i would have removed connman first | 04:18 |
| gnarface | just in case they share some dependencies | 04:18 |
| gnarface | like accidentally | 04:18 |
| gnarface | someone has probably run into this before | 04:20 |
| FilipZ | Then could reinstallation help? | 04:20 |
| gnarface | i would "apt-get --purge autoremove" once first, then re-install network manager, see if it helps yea | 04:21 |
| gnarface | but their entanglement might be worse; connman could have left behind some configs or something that networkmanager is choking on | 04:22 |
| brocashelm | iirc, swapping connman with network-manager (and the other way around) messes with some configs like in /etc/network/interfaces | 04:22 |
| gnarface | i don't use either one but i would expect it's a known issue when switching between them | 04:22 |
| brocashelm | i know it was impossible to connect to the internet when i switched out of connman and back to network-manager | 04:23 |
| FilipZ | What exactly does the --purge autoremove do? It tells that it would free nearly 1.5 GB | 04:23 |
| gnarface | oh wow | 04:23 |
| gnarface | it removes packages that are supposedly orphaned | 04:24 |
| brocashelm | autoremove removes all packages associated with a package that you removed previously, whereas autopurge does that plus remove their configs | 04:24 |
| brocashelm | check orphaned packages with deborphan --guess-all | 04:24 |
| brocashelm | i don't have any packages for autoremoval, but deborphan/orphaner shows a couple of orphaned packages | 04:24 |
| gnarface | it's a good idea to run this after big updates; usually at the command-line it will tell you that | 04:24 |
| gnarface | they have to be orphaned and also not have been manually requested to be installed themselves by name directly | 04:25 |
| FilipZ | Apt already prints all those packages it tell that it would remove. | 04:25 |
| brocashelm | what i usually do is apt update && apt upgrade && apt autopurge && apt autoclean to clean and sanitize things automagically | 04:25 |
| gnarface | it only removes packages it knows are in conflict with the new ones; some times there are spare packages left over that aren't marked as in direct conflict with anything but sometimes they are actually causing problems. at the very least they're also wasting space. | 04:26 |
| brocashelm | autoclean is good for that | 04:26 |
| gnarface | and i think networkmanager wants to find something very specific in /etc/network/interfaces | 04:27 |
| gnarface | maybe nothing, or maybe just localhost, i really don't know | 04:27 |
| gnarface | but if there's actual configuration in there it can cause problems | 04:28 |
| FilipZ | "Before uninstall, this module version was ACTIVE on this kernel." - why would it print things like this? | 04:37 |
| gnarface | uh, the module was loaded i think? | 04:40 |
| gnarface | seems self-explanatory | 04:40 |
| FilipZ | I got an error while doing " apt autopurge && apt autoclean". "Could not open lock file /var/cache/apt/archives/lock - open (13: Permission denied)" | 04:42 |
| gnarface | well you have to be root | 04:42 |
| gnarface | or using sudo | 04:43 |
| FilipZ | I did use sudo | 04:43 |
| gnarface | try using sudo on each command, that's two in a row | 04:43 |
| FilipZ | I did "sudo apt autopurge && apt autoclean". | 04:44 |
| gnarface | right, which is only using sudo on one of the two commands | 04:44 |
| FilipZ | Should I now do sudo apt autoclean | 04:44 |
| gnarface | yes | 04:44 |
| brocashelm | sorry about that. i assumed you were already in a root shell | 04:45 |
| FilipZ | Alright. I did this, and then network-manager reinstallation, but it didn't fix the issue. | 04:48 |
| brocashelm | yeah, something in your configs got corrupted due to connman being replaced | 04:48 |
| FilipZ | How should I fix it? | 04:49 |
| FilipZ | Do I need to remove it completely and then install this again, using ifup/ifdown to connect to the internet? | 04:52 |
| brocashelm | do you get any connection to the internet if you run sudo dhclient? | 04:54 |
| brocashelm | i don't think i fixed this problem myself other than going back to my last imaged backup | 04:54 |
| FilipZ | brocashelm If I do this now I get an error about /etc/resolv.conf not being a symbolic link to /run/resolvconf/resolv.conf | 04:58 |
| brocashelm | i think that was the one | 04:59 |
| brocashelm | try to create a symlink | 04:59 |
| FilipZ | "/etc/resolvconf/update.d/libc: Warning: /etc/resolv.conf is not a symbolic link to /run/resolvconf/resolv.conf" | 05:01 |
| brocashelm | sudo ln -s /run/resolvconf/resolv.conf /etc/resolv.conf | 05:01 |
| brocashelm | that should solve it for you | 05:01 |
| brocashelm | then try sudo service network-manager restart | 05:03 |
| brocashelm | (doesn't matter the init) | 05:03 |
| FilipZ | Now that I look at it, it is a link to some connman related folder | 05:05 |
| FilipZ | Directory, it is | 05:05 |
| FilipZ | It works! | 05:11 |
| FilipZ | Thank you. :) | 05:11 |
| brocashelm | np :) | 05:13 |
| xisop | oh interesting, service will call init.d scripts if that's what you use? | 10:43 |
| xisop | very cool | 10:43 |
| FilipZ | Hi! Something strange happened to my system. Login screen look changed from the blue one, to the primitive looking with white and gray colors, on the left and right sides of the screen. When I entered login in the login field, It responded that "login failed", and the login text field didn't change instead to the password text field, how it | 14:41 |
| FilipZ | happened earlier. After I entered a correct password to this field however(after "rejected" login), I could log-in. I didn't even update the system in the previous session, but only did apt autopurge & apt autoclean. What could have happened, and how to fix it? | 14:41 |
| FilipZ | I also see that the connection managing software ceased to work too. | 14:44 |
| FilipZ | It worked after I changed it in the previous session. | 14:45 |
| FilipZ | Probably because the resolv.conf symbolic link that incorrectly pointed to /run/connman/resolv.conf, before I changed it, now points there again. Why would it change back to its previous state? | 14:50 |
| sabasedigh | hello devuan | 19:33 |
| gnarface | FilipZ: there obviously has to be some parts of connman still doing that | 19:45 |
| gnarface | you must have missed something | 19:45 |
| golinux | sabasedigh: Just ask your question. :) | 19:56 |
| rwp | FilipZ, I think you were upgrading? If so then the "xdm" (X Display Manger) may have changed from "lightdm" to "slim". The description sounds like it to me. Maybe. | 20:06 |
| rwp | FilipZ, As for the networking... It doesn't seem like it should be complicated but unfortunately things have become complicated with regards to all of the things that touch the system. | 20:07 |
| rwp | For example /etc/resolv.conf is a symlink if resolvconf is installed. And I think also if network-manager is installed. And they can fight over things. | 20:08 |
| rwp | And there is both IPv4 and IPv6 as a "dual stack" parallel configuration. It's messy. | 20:08 |
| rwp | Sometimes one just needs to reboot, log in, then very carefully walk through the small parts of it individually to figure things out. | 20:09 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!