HumanG33k | hi i fuck up my upgrade. | 00:22 |
---|---|---|
HumanG33k | i can't login anymore through x session | 00:23 |
rrq | from what to what? | 00:23 |
HumanG33k | from devuan to devuan | 00:24 |
rrq | a devuan chimaera upgrade? | 00:24 |
HumanG33k | i know i m stupid because i try last stable from stable - 2 | 00:24 |
HumanG33k | slim says issue with login | 00:25 |
rrq | hmm a devuan daedalus upgrade.. and ran into problems? | 00:25 |
HumanG33k | i found a post on devuan forum about using other session manager and i try to use lghtdm instead of slim but same "issue" | 00:26 |
HumanG33k | yep | 00:26 |
HumanG33k | i guess | 00:26 |
rrq | righ so you also installed lightdm? | 00:28 |
HumanG33k | yep | 00:28 |
HumanG33k | and purge slim | 00:28 |
rrq | ok. so "slim says issue with login" means "lightdm says issue with login"? | 00:29 |
HumanG33k | no light only not connect | 00:30 |
rrq | is that a verbatim compy of an actual output? | 00:31 |
rrq | copy | 00:32 |
HumanG33k | https://dev1galaxy.org/viewtopic.php?id=757 | 00:34 |
HumanG33k | contain the exact message from slim | 00:35 |
rrq | the installation of a desktop would need "apt install task-xfce-desktop" or "task-lxde-desktop" or something... have you done that? | 00:37 |
HumanG33k | yes | 00:38 |
rrq | which one? | 00:38 |
HumanG33k | xfce | 00:38 |
rrq | ok. and then you got the same issue as Simplicio upon reboot... which you tried to rememdy by purging slim and installing lightdm ... is that exact? | 00:41 |
HumanG33k | yes | 00:41 |
HumanG33k | i not touch at .xinit file | 00:41 |
HumanG33k | not really sure to what put in it and not sure it's really necessary | 00:42 |
HumanG33k | as it work without before | 00:42 |
rrq | no shouldn't need an .xinit | 00:42 |
rrq | do you have seatd installed? or elogind and dbus? | 00:44 |
rrq | (should have been dependencies) | 00:44 |
HumanG33k | no seatd, it's a new package never heard of it before ? | 00:45 |
rrq | but you have elogind and dbus-x11 (seatd is an alternative input stream mediation, without dbus and logind) | 00:46 |
HumanG33k | elogind and dbus-x11 | 00:47 |
HumanG33k | are install i just lauch a --reinstall --purge | 00:48 |
rrq | xorg needs some input stream mediation, and currently the alterantives are seatd or logind+dbus | 00:49 |
rrq | running as daemons | 00:49 |
rrq | fursther, the user needs to be in "video" group, and must be the owner of the /dev/ttyN for the vtN in use | 00:50 |
HumanG33k | how to check the owner of tty7 ? | 00:51 |
HumanG33k | user is in video group | 00:51 |
rrq | ls -l /dev/tty7 | 00:51 |
HumanG33k | make sense :D | 00:52 |
rrq | I suppose the login managers (slim or lightdm) typically run as root so might not be problem | 00:52 |
HumanG33k | tty7 is run by the user i try to log to | 00:53 |
HumanG33k | slim is run by root | 00:53 |
rrq | ok.. this might concern the graphics driver ... which I know only some little about | 00:56 |
HumanG33k | humm | 00:57 |
rrq | you may need to hang around for assistance with that; you have nvidia I suppose ? | 00:57 |
HumanG33k | think not | 00:58 |
HumanG33k | ok new message | 00:58 |
HumanG33k | find in the xsession | 00:58 |
rrq | when you install, is that with or without recommends? | 00:59 |
HumanG33k | which part ? | 00:59 |
rrq | well, firstly for task-xfce-desktop | 01:00 |
rrq | did you install that with all its "Recommends" dependencies? | 01:00 |
HumanG33k | dbus[3467]: Failed to start message bus: Circular inclusion of file '/etc/dbus-1/session.conf' EOF in dbus-launch reading address from bus daemon | 01:01 |
rrq | right. good find. xorg with logind mediation needs dbus running | 01:02 |
rrq | what's in that file? | 01:03 |
rrq | (I don't have that file) | 01:03 |
rrq | hmm comes from dbus-session-bus-common | 01:03 |
HumanG33k | humm lots of stuff in that file | 01:05 |
rrq | which package does it come from (dbus-session-bus-common has /usr/share/dbus-1/session.conf rather) | 01:07 |
rrq | maybe move it away, say, to /root/, and see if things improve | 01:08 |
rrq | you should have /usr/share/dbus-1/session.conf ... and maybe that's the same file ? | 01:09 |
rrq | the latter esp has: <include ignore_missing="yes">/etc/dbus-1/session.conf</include> | 01:10 |
rrq | and that would be bad to have in /etc/dbus-1/session.conf | 01:10 |
rrq | btw to find owner packages you'd do: dpkg-S dbus-1/session.conf | 01:11 |
rrq | btw to find owner packages you'd do: dpkg -S dbus-1/session.conf | 01:12 |
HumanG33k | ok moving and restart fix the issue for what i see | 01:15 |
rrq | good :) happy xfce-ing | 01:16 |
HumanG33k | yep' thx for your precious help | 01:17 |
D-HUND | what could be wrong when connman shows "1 Found, 1 Powered" for WiFi but there are no available networks listed and the "Rescan" button is greyed out? | 14:06 |
D-HUND | Wifi worked fine during installation (daedalus) and it also works when booting the live CD | 14:07 |
D-HUND | it also worked properly on chimaera | 14:07 |
D-HUND | lspci says Kernel driver in use: ath9k | 14:08 |
D-HUND | non-free-firmware enabled | 14:09 |
D-HUND | dmesg: http://paste.debian.net/plain/1307062 | 14:14 |
gnarface | good question, i have a vague theory... the justification would sound too crazy to bother repeating, but just as a test try downgrading to linux-image-6.1.0-17-amd64 | 14:14 |
gnarface | if the firmware was updated between then and the next kernel, downgrade that too if the old one is still in the repos | 14:16 |
D-HUND | gnarface: rgrwillco | 14:16 |
D-HUND | its afresh install, wiped the old installation because of other issues | 14:17 |
D-HUND | <-- debdog | 14:17 |
D-HUND | kernel is 6.1.0-10 | 14:19 |
gnarface | oh, huh, so you haven't even updated it after the install? | 14:20 |
D-HUND | hmm, I thought I did... | 14:20 |
D-HUND | but then I've been fighting the network the past few hours and might have gotten sidetracked | 14:20 |
gnarface | current should be 6.1.0-18, but fair warning nvidia broke it on purpose | 14:20 |
gnarface | if you're using nvidia hardware don't go past 6.1.0-17 for now | 14:21 |
D-HUND | oy vey | 14:21 |
D-HUND | aptitude update does not show any available update. same for synaptics and apt-get | 14:22 |
D-HUND | hmm | 14:22 |
gnarface | the log message basically says you disconnected it yourself immediately after connecting, which is such a stupid error i've seen caused by so many things as to be basically meaningless... possibly a race condition due to your wifi router being too slow but nothing would explain a change there except a change to the device itself or the kernel or wpasupplicant | 14:22 |
D-HUND | plus I had issues with deb.devuan.org. had to put a de. in front of it | 14:23 |
gnarface | hmmm | 14:24 |
gnarface | using a proxy? | 14:24 |
gnarface | https://pkginfo.devuan.org/cgi-bin/policy-query.html?c=package&q=%5Elinux%5C-image%5C-6%5C.1%5C.0%5C-17.*&x=submit | 14:26 |
gnarface | pkginfo definitely still shows it present, and -18 too | 14:26 |
gnarface | oh! but the kernel wouldn't have automatically updated if you didn't have the generic meta-package for your architecture installed (such as linux-image-amd64) | 14:27 |
D-HUND | ok, now it lists a lot of available updates after I've changed it back to just deb.devuan.org | 14:27 |
D-HUND | this may take a while | 14:28 |
gnarface | your wifi router isn't a hostapd instance, is it? | 14:29 |
D-HUND | I don't know what that means. it's a vodafone thingy | 14:29 |
gnarface | probably not then | 14:29 |
gnarface | uh, if you're using samba for anything, don't use 6.1.0-17 either | 14:30 |
gnarface | but pkginfo shows the several previous kernels to that all still present, and all still newer than what you've got installed | 14:30 |
gnarface | ... and it might not be important, but i thought the ath9k devices' firmware was actually in main, in the package "firmware-linux-free" but i don't know that for sure | 14:32 |
gnarface | it doesn't seem to have changed since chimaera, so that's unlikely to be the issue | 14:32 |
D-HUND | I have installed firmware-atheros now, maybe that helps... | 14:36 |
D-HUND | no | 14:38 |
D-HUND | but an issue with the kernel seems likely. the old daedalus that was running there still had the chimaera kernel. | 14:40 |
gnarface | it will probably still actually work with that chimaera kernel | 14:43 |
gnarface | worth a try | 14:43 |
D-HUND | oh, I do not use the meta package for kernel, just FYI | 14:43 |
gnarface | i frequently purge mine so the kernel won't update without my explicit manual selection of a specific one, but if you do that you gotta remember you did it... | 14:45 |
D-HUND | hmm, in case I fetch the chimaera kernel I have to get the matching nvidia packages as well, right? | 14:46 |
gnarface | sadly, yes | 14:46 |
gnarface | but unless you play a certain handful of badly behaved video games it probably isn't a big deal | 14:47 |
D-HUND | ok, I'll have a look a the backup to seem which packages I've had back then | 14:47 |
D-HUND | well, my experience with nouveau are not very good | 14:48 |
D-HUND | hmm, maybe it's easier to just install chimaera | 14:48 |
gnarface | well, theoretically since they use dkms any nvidia driver version should work with a wide array of kernels, but i don't think non-standard combinations are very well tested so your luck might be hit and miss... best to use the version that originally shipped with that kernel on debian if possible, but it's not a waste of time to try something newer as evidenced by someone a few months back in here who managed to manually | 14:49 |
gnarface | build a (i think) 525.* nvidia driver package for beowulf using nvidia's own devkit | 14:49 |
D-HUND | this laptop is not used for gaming, so performance is not the issue. | 14:50 |
D-HUND | but the nivida driver has just better colours and still is a tad faster | 14:51 |
gnarface | yea i don't blame you | 14:52 |
D-HUND | well, I do know how to express myself properly there | 14:52 |
gnarface | i'm not suggesting to use nouveau, i'm just warning you that World of Warcraft isn't gonna let you in without the bleeding edge version because they're assholes | 14:52 |
D-HUND | hehe | 14:52 |
ted-ious | I saw that debian made an update to bookworm 12.5. | 15:24 |
ted-ious | Is devuan going to get new live or installer iso's at some point? | 15:24 |
* D-HUND is a lilo guy ho has to learn grub now | 15:32 | |
D-HUND | how do I tell grub to use /boot/vmlinuz-6.1.0-10-amd instead of -17? | 15:32 |
cousin_luigi | D-HUND: You could create a custom entry. | 15:32 |
D-HUND | where? there are so many conf files. grubd defaults/somethingsomething | 15:33 |
cousin_luigi | D-HUND: The easiest way would be to simply take the current entry from /boot/grub/grub.cfg and copying it into /etc/grub.d/40_custom | 15:33 |
cousin_luigi | Modified to your needs. | 15:33 |
cousin_luigi | Then run update-grub | 15:33 |
cousin_luigi | If you want -10 to be default, then change GRUB_DEFAULT in /etc/default/grub accordingly | 15:34 |
cousin_luigi | again, run update-grub after each change, or it won't be detected | 15:35 |
D-HUND | cousin_luigi: it says GRUB_DEFAULT=0. how to figure out which number to put there? | 15:43 |
cousin_luigi | D-HUND: I think one has to count the menuentry items. | 15:44 |
D-HUND | booting the -10 kernel did not make any difference, still no dice with connman. the live CD uses the same kernel and there I have no issues. but the live CD uses nm-applet, so it prolly is not kernel related | 15:44 |
D-HUND | ok, cousin_luigi | 15:45 |
cousin_luigi | D-HUND: What's the problem btw? | 15:45 |
cousin_luigi | D-HUND: Scrolling up, I suggest #linux-wireless | 15:45 |
D-HUND | wifi not working in daedalus with connman | 15:45 |
gnarface | hmm, if it's the race condition issue i was seeing then a change to the connman version might be just as suspect as the kernel or wpasupplicant... have you tried just typing the info into /etc/network/interfaces and using ifup? | 15:47 |
gnarface | that would rule out a couple extra things | 15:47 |
D-HUND | gnarface: I gave up on editing wpawhatever 15 years ago | 15:48 |
gnarface | i can tell you which fields you need | 15:48 |
gnarface | it's not as hard as it sounds usually | 15:48 |
cousin_luigi | D-HUND: Does it work with networkmanager? | 15:49 |
cousin_luigi | And any chance rfkill might be on? | 15:49 |
D-HUND | hmm, in /etc/network/interfaces the ssid and psk seem correct | 15:51 |
D-HUND | one moment... | 15:51 |
gnarface | i think the name of the actual password field changes depending on the type of encryption you're using | 15:52 |
D-HUND | that's what it looks like now: http://paste.debian.net/plain/1307080 | 15:52 |
cousin_luigi | D-HUND: By the way, do you use wpa_supplicant or iwd? | 15:53 |
D-HUND | *shrug* I am using the defaults, have insalled this system today | 15:54 |
gnarface | D-HUND: looks right except you need to quote the ssid | 15:54 |
gnarface | (not the password though, not sure why) | 15:54 |
* D-HUND adds quotes and reboots the laptop... | 15:55 | |
gnarface | you shouldn't need to reboot for that. you should only have had to run "ifup wlan0" | 15:56 |
gnarface | (as root) | 15:56 |
gnarface | also you'll want to make that file only readable by root if you're gonna keep your password in it | 15:57 |
D-HUND | no dice | 15:57 |
D-HUND | will try nm-applet now | 15:57 |
* D-HUND feels like a 12 year old school girl | 15:58 | |
gnarface | it'll be really weird if networkmanager works but a bare interfaces file didn't | 15:58 |
D-HUND | hmm | 15:58 |
gnarface | but if it does work, that suggests there is probably some additional flag you can provide in the interfaces file to make it also work (i've had to do such things rarely only to force certain conditions for buggy drivers or routers) | 15:59 |
D-HUND | what about DHCP or DNS? | 15:59 |
gnarface | dhcp failure of some sort maybe suspect, if the router disconnects you for not accepting an ip right away, but dns failure wouldn't cause this | 16:00 |
D-HUND | the wired connection shows a DNS but the wireless doesn't show anything – in connman's "Details" tab | 16:00 |
gnarface | dhcp would have to work first for the wifi to see the dns | 16:00 |
D-HUND | right | 16:01 |
gnarface | if you have the option of telling the router to let you specify an ip manually though, that would be a way to eliminate that possibility | 16:01 |
D-HUND | and during installation I've chosen DHCP | 16:01 |
gnarface | hmm, which dhcp client are you using? | 16:01 |
D-HUND | uhm | 16:02 |
D-HUND | default? | 16:02 |
D-HUND | how do I check? | 16:02 |
gnarface | the default i think is dhcpcd still, which i have occasionally seen cause compatibility problems. you could try switching to isc-dhcp-client | 16:02 |
gnarface | (still in debian, though discontinued, isc-dhcp-client is the closest thing there ever was to an official reference implementation) | 16:03 |
omo | ping | 16:06 |
omo | ok, I am D-HUND on the freshly installed laptop | 16:07 |
gnarface | changing to isc-dhcp-client fixed it? | 16:08 |
omo | # aptitude search dhcp | grep ^i | 16:08 |
omo | i isc-dhcp-client - DHCP client for automatically obtaining an IP address | 16:08 |
omo | i isc-dhcp-common - Handbuchseiten mit Bedeutung für alle »ISC DHCP«-Pakete | 16:08 |
omo | no, this is the eth0 connection | 16:08 |
gnarface | oh | 16:08 |
gnarface | the other popular one is dhcpcd | 16:09 |
omo | what still puzzles me is that connman still hAS THAT GREYED OUT "rESCAN" BUTTON | 16:09 |
omo | OOPS | 16:09 |
omo | opps | 16:10 |
gnarface | i'm not sure it could be relevant though, seems like a bit of a stretch, usually if there was a dhcp problem in my experience it just connects and stays connected but doesn't work | 16:10 |
omo | I'll unplug the cable now I try to connect to the router with the IP address... | 16:10 |
D-HUND | not even that works | 16:13 |
D-HUND | so it's not DHCP or DNS | 16:13 |
gnarface | D-HUND: what does "rfkill list" say? | 16:15 |
gnarface | D-HUND: also, make sure you have wireless-regdb installed | 16:17 |
omo_ | # LANG=C rfkill | 16:18 |
omo_ | -bash: rfkill: Kommando nicht gefunden. | 16:18 |
gnarface | well, you'll have to install it | 16:18 |
omo_ | why does it print the german message with LANG=C? | 16:19 |
gnarface | i don't know | 16:19 |
omo_ | this is weired | 16:19 |
omo_ | that may indicate the problem why I even reinstalled that laptop. locale not working properly | 16:19 |
omo | just in case you remeber my rant on saturday about pcmanfm-qt not properly displaying german menus | 16:21 |
gnarface | do you have the locales package installed? | 16:21 |
omo | i locales | 16:21 |
gnarface | hmm, you can "dpkg-reconfigure locales" to make sure it's set right but i don't know what else to do besides file a bug report against it or the misbehaving program | 16:23 |
gnarface | most the problems i've seen caused by that originated with people trying to force locales with environment variables and missing some | 16:23 |
gnarface | but i definitely haven't tested other languages | 16:24 |
omo | this is even more weired. I am able to chat here, so some network has to work, but... | 16:26 |
omo | http://paste.debian.net/plain/1307088 | 16:28 |
gnarface | hmm, maybe it's a dns failure after all, but that doesn't explain the disconnect message in your pasted log snippet... | 16:28 |
gnarface | oh! maybe the static ip gambit worked, but you forgot to actually manually populate /etc/resolv.conf at the same time, so only irc is working | 16:29 |
omo | browser seems to work properly | 16:30 |
gnarface | but not apt? very strange | 16:30 |
gnarface | what are you using for dns? just your isp's dns servers? | 16:30 |
omo | yes, ISP's | 16:31 |
gnarface | i would recommend you run your own, but as a temporary measure you can use google's (8.8.8.8) | 16:32 |
omo | changed deb.devuan.org to de.deb.devuan.org and now its working | 16:32 |
gnarface | alright, so there might be more than one issue at hand | 16:32 |
omo | rfkill: http://paste.debian.net/plain/1307089 | 16:33 |
gnarface | uh... i think that's saying you have two wifi devices, which might be part of the problem, but they're both on so... | 16:34 |
omo | hmm, connman only lists one | 16:35 |
omo | so does network/interfCES | 16:35 |
omo | http://paste.debian.net/plain/1307090 | 16:36 |
gnarface | weird | 16:36 |
omo | IPv4 vs. IP6 issue? since eth0 is IPv4 and wlan0 is IPv6? | 16:38 |
gnarface | hmm, seems possible, i was going to ask if you were using ipv6 actually | 16:39 |
gnarface | can you force the wlan back to ipv4 to see if it helps? | 16:39 |
gnarface | i can't imagine any possible benefit to using ipv6 on a private wifi, you'd run out of spectrum long before you ran out of ipv4 addresses, and giving wifi devices a public ip is insane | 16:40 |
omo | I have to take a breake | 16:48 |
djph | gnarface: because NAT sucks . | 16:53 |
omo | how would I force it to use IPv4? | 17:12 |
omo | the router is shitty. it doesn't tell me whether it connects to web via 4 or 6 | 17:12 |
gnarface | to be honest, i thought using "inet" instead of "inet6" in your interfaces file should have been enough | 17:13 |
omo | but the router says this laptop is connected via wifi | 17:14 |
gnarface | are you able to ping the router from the laptop? | 17:14 |
omo | PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data. | 17:15 |
omo | 64 bytes from 192.168.0.1: icmp_seq=1 ttl=64 time=1.90 ms | 17:15 |
gnarface | looks fine, doesn't explain the disconnect earlier though | 17:15 |
D-HUND | duh, eth0 was connected | 17:15 |
gnarface | oh, that was a eth0 ping? | 17:16 |
gnarface | yea i meant wifi | 17:16 |
D-HUND | without that connection still works but IRC went town | 17:16 |
D-HUND | *ping still works | 17:17 |
D-HUND | so it might be an IPv4 DNS issue? | 17:17 |
gnarface | if you're seeing ipv4 addresses in the ping output then it's using ipv4 | 17:17 |
gnarface | at the moment it does seem like a DNS issue, but again that doesn't explain the disconnect earlier that we started debugging originally | 17:17 |
gnarface | it's unclear to me right now whether you're also experiencing a dhcp issue or not too | 17:18 |
gnarface | dhcp failure can lead to dns failure, since the dhcp server is typically what provides the dns address too | 17:19 |
gnarface | usually that can all fail while wifi still being "connected" technically | 17:19 |
gnarface | losing the irc connection after disconnecting the ethernet wire seems like expected behavior though, there's no reason to expect it would be smart enough to switch network interfaces on the fly | 17:21 |
D-HUND | I am tired right now. but the router says the laptop is connect via wifi IPv4. connman still does not like to show available networks | 17:33 |
D-HUND | and the browser does not connect to the internet | 17:33 |
D-HUND | but I can connect to the router with its IPv4 address | 17:34 |
D-HUND | I'll postpone this for now. brain fried. | 17:34 |
D-HUND | I'll try static configuration next | 17:36 |
omo | huh, with nm it works just fine | 17:57 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!