| bb|hcb | rwp: Oh, I missed that. I am not sure if eudev will reread the rules, unless told so. About the reconnecting device - that is another problem by itself. The bad things with such issues is that there is no way to reproduce and debug what is happening :( | 00:09 |
|---|---|---|
| rrq | isn't it the same as removing and reinserting a mounted USB disk? basically any USB device that does like that will be re-enumerated as a new device | 00:13 |
| rwp | I have never had good luck with long term mounting of USB disks. They always freak out at some point. And removing a mounted device is not good. | 00:43 |
| rwp | But conversely USB network adaptors have been awesomely rock solid. So odd they are on opposite ends of the problem. | 00:43 |
| AlexLikeRock | where can change the name of my WIFI device ? | 01:01 |
| AlexLikeRock | they appear like "wlx00e04cb66705" | 01:01 |
| rwp | I have learned to live with those names. But all of the detail on device naming is here: https://wiki.debian.org/NetworkInterfaceNames | 01:08 |
| rrq | AlexLikeRock: one way might be, if you have a file /lib/udev/rules.d/73-usb-net-by-mac.rules you may create an emptu file /etc/udev/rules.d/73-usb-net-by-mac.rules sos as to disarm that goodness | 01:09 |
| AlexLikeRock | yes m its the way ... | 01:10 |
| AlexLikeRock | i found : /etc/udev/rules.d 70-persistent-net.rules | 01:11 |
| rwp | I am pretty sure that the USB WiFi adaptors create wlx00e04cb66705 types of names even with net.ifnames=0 set in the kernel command line. | 01:11 |
| rwp | But the traditional name would have been wlan0 for it. | 01:12 |
| rrq | yes, possibly the kernl module invents that name by itself | 01:12 |
| AlexLikeRock | ok, thanks | 01:12 |
| rwp | Check dmesg and look to see if it is being renamed: dmesg | grep -e wlan -e eth | 01:13 |
| rrq | generally speaking, the kernel module always invents some name, and then udev tries to improve on that; the first naming is decided by the module developer(s) the second but the (e)udev developer(s) | 01:14 |
| rwp | In any case if needed you would set kernel command line options in /etc/default/grub such as GRUB_CMDLINE_LINUX="net.ifnames=0" and then run "update-grub" afterward to propagate. | 01:14 |
| rwp | Example of one of my hostapd Access Point systems with two USB WiFi adaptors attached: https://paste.debian.net/plain/1293846 | 01:18 |
| rwp | One at a time the adapter is enumerated as wlan0 and renamed. Which frees wlan0 for the next one. So each in turn starts as wlan0 and then is renamed. | 01:19 |
| AlexLikeRock | dmesg | grep -e wlan -e eth , they are good new info , thaks dude's !! | 01:24 |
| bb|hcb | rrq: It should be the same for all usb devices. I have a PL2303 serial-to-usb and both the /dev/serial/by-path and /dev/serial/by-id seems to be created in a sane manner. But no matter how many times I did plug/unplug it is constantly /dev/ttyUSB0 (eudev 3.2.12-4+deb11u1) | 17:38 |
| bb|hcb | Changing the main device name most probably means that the old name was not deleted while the problematic device appeared again (before the previous one got deleted). I'd guess there may be way too many reasons like: power problems, bad device, bad driver... Who knows? | 17:42 |
| scaniatrucker | I know for a fact that the Devuan forum administration promotes Nazism, covers Nazis, promotes their activities and possibly covers war criminals. This is done by ralph.ronnquist and some obscure person whose nickname is golinux. Stupid Nazi pigs. There will come a time when you will deeply regret your actions. Nazism will be stopped! | 17:53 |
| scaniatrucker | If the administration of the Devuan forum cares so much about the Ukrainian refugees (it's very strange what they do at the computer. Instead of writing nonsense, why don't they fight for their country), maybe they could look into why the USA is promoting the war in Ukraine? Or is the entire administration of the so-called Devuan distributor cooperating with US intelligence structures? | 18:02 |
| scaniatrucker | | 18:02 |
| miojo | there's a troll in the room | 18:02 |
| scaniatrucker | no, miojo i am not a troll. I protest against manifestations of Nazism in the devuan forum | 18:03 |
| joerg | how about taking it to that forum then? | 18:03 |
| [-_-] | Hiii | 18:52 |
| [-_-] | guys, anyone tried this : https://slackfa.blogspot.com/2014/02/use-any-tabletsmartphone-as-extended.html | 18:52 |
| [-_-] | can the sorry rebooting, brb | 18:55 |
| [-_-] | is it possible to use xserver-xorg-video-dummy along side of normal drivers? | 18:57 |
| [-_-] | I get a blank screen | 18:57 |
| [-_-] | /etc/X11/xorg.conf.d/00-xorg.conf: http://vpaste.net/OAGlo | 18:58 |
| [-_-] | /etc/X11/xorg.conf.d/01-vnc.conf: https://termbin.com/tpj6 | 18:59 |
| [-_-] | if I have modesetting disabled usig modprobe, the system freezes in tty | 19:00 |
| [-_-] | I can get out by changing tty, or ctrl+alt+backspace | 19:00 |
| [-_-] | if modesetting is enabled, then I get a blank screen | 19:00 |
| [-_-] | I can't get out with ctrl+alt+backspace or change tty, nothing, straight reboot | 19:01 |
| [-_-] | also any easy way to share mpv video from linux to android? | 19:06 |
| dokma | TeamViewer refuses to start on my Devuan. Seems like: | 20:51 |
| dokma | loginctl list-sessions | 20:52 |
| dokma | No sessions. | 20:52 |
| dokma | is the culprit. | 20:52 |
| dokma | Am I getting this correct: PAM is supposed to notify elogind that there was a new login and then elogind is supposed to create the session in response? | 20:56 |
| dokma | rwp: you around? | 21:05 |
| amesser | did you install libpam-elogind? | 21:06 |
| dokma | dpkg -l | grep libpam-elogin | 21:07 |
| dokma | ii libpam-elogind:amd64 246.10-2 amd64 elogind PAM module | 21:07 |
| dokma | it is also configured in pam: | 21:07 |
| amesser | hmm, then it should work out of the box. | 21:07 |
| dokma | grep -r elogind | 21:07 |
| dokma | elogind-user:# This file is part of elogind. | 21:07 |
| dokma | elogind-user:session optional pam_elogind.so | 21:07 |
| amesser | how you log into the system? | 21:08 |
| dokma | From a virtual console | 21:08 |
| dokma | I don't use a login manager | 21:08 |
| dokma | Then I use exec startx to go into GUI | 21:08 |
| amesser | uhh | 21:08 |
| dokma | I know that something about that is the problem because TeamViewer works when I use a login manager but when I login from the Virtual Console them TeamViewer doesn't work | 21:09 |
| amesser | could you check if /etc/pam.d/common-session contains elogind ? | 21:10 |
| dokma | it does not | 21:11 |
| amesser | then run as root "pam-auth-update" | 21:11 |
| DelTomix | strange - is "teamviewer" a browser app? a binary? - are there perhaps versions with different dependencies? | 21:11 |
| dokma | See that grep -r elogind above? It shows the only mention of elogind in /etc/pam.d | 21:11 |
| dokma | DelTomix: teamviewer is a gui app for remote windows display. | 21:12 |
| amesser | "/etc/pamd.d/elogind-user" is not used by default | 21:12 |
| dokma | ?? | 21:12 |
| amesser | so please run "pam-auth-update" and check the box for elogind | 21:12 |
| dokma | what do you mean? | 21:12 |
| amesser | pam-auth-update should then persist the settings across updates, upgrades etc. | 21:13 |
| dokma | When I run pam-auth-update PAM asks: 1. Unix authentication 2. Create home directory on login 3. elogind Session Management 4. none of the above | 21:13 |
| amesser | when i run pam-auth-update, i get a dialog. | 21:13 |
| amesser | a can then check the settings | 21:13 |
| dokma | It is a terminal dialog | 21:14 |
| dokma | Which of these profiles should I enable? | 21:14 |
| amesser | at least 1) and 3) | 21:14 |
| dokma | Did it. This requires a reboot? | 21:15 |
| amesser | common-session should now contain a line with elogind | 21:15 |
| dokma | Let's see | 21:15 |
| amesser | should be sufficent to log out and log in again, could be another terminal. | 21:15 |
| dokma | grep -r elogin * | 21:15 |
| dokma | common-session:sessionoptionalpam_elogind.so | 21:15 |
| dokma | elogind-user:# This file is part of elogind. | 21:15 |
| dokma | elogind-user:session optional pam_elogind.so | 21:15 |
| dokma | So it does. | 21:16 |
| amesser | looks ok. | 21:16 |
| dokma | Does this need a reboot? | 21:16 |
| amesser | after log out/in " loginctl list-sessions should show something. | 21:16 |
| amesser | no, just log out and log in again. | 21:16 |
| dokma | Thanks. Will be back. | 21:16 |
| dokma | Ok, now I've got: | 21:20 |
| dokma | loginctl list-sessions | 21:20 |
| dokma | SESSION UID USER SEAT TTY | 21:20 |
| dokma | 1173 1000 vlatko seat0 tty1 | 21:20 |
| dokma | 21:20 | |
| dokma | 1 sessions listed. | 21:20 |
| dokma | 21:20 | |
| dokma | So sessions seem to work properly now. | 21:20 |
| amesser | fine | 21:20 |
| dokma | TeamViewer however is still not operational | 21:20 |
| amesser | hmm ok. actually the session thing is need for several permission related things. What dies TeamViewer tell now? | 21:21 |
| dokma | It says: SysSessionInfoManager: observing sessions from logind is marked as reliable | 21:21 |
| dokma | but then: SysSessionInfoManager::GetOwnProcessSession: No session found!, Errorcode=11 | 21:21 |
| amesser | Hmm. I believe there is a difference between running startx from terminal compared to using a display manager | 21:23 |
| dokma | I think so too | 21:23 |
| amesser | is dbus working? | 21:23 |
| amesser | I have some vars here: | 21:24 |
| dokma | It's running and I'm seeing functionality that depends on it. For example erc is displaying popup notifications which, I believe, go via dbus | 21:24 |
| amesser | declare -x XDG_SEAT_PATH="/org/freedesktop/DisplayManager/Seat0" | 21:24 |
| amesser | declare -x XDG_SESSION_CLASS="user" | 21:24 |
| amesser | declare -x XDG_SESSION_DESKTOP="budgie-desktop" | 21:24 |
| amesser | declare -x XDG_SESSION_PATH="/org/freedesktop/DisplayManager/Session0" | 21:24 |
| amesser | declare -x XDG_SESSION_TYPE="x11" | 21:25 |
| amesser | could you run "export" in a terminal of your x-server? | 21:25 |
| amesser | and compare | 21:25 |
| dokma | I've declared all the vars you listed. No change... | 21:26 |
| dokma | Which paste does this chan favour? | 21:27 |
| dokma | I'll just pastebin | 21:27 |
| DelTomix | https://paste.debian.net/ | 21:27 |
| dokma | Thank you for your massive time investment in this | 21:27 |
| amesser | hmm | 21:28 |
| dokma | http://paste.debian.net/1293932/ | 21:28 |
| amesser | no worries, glad to help | 21:31 |
| amesser | could you run "loginctl show-session $(loginctl | grep $(whoami) | awk '{print $1}')" | 21:31 |
| amesser | and paste.d.n the output? | 21:31 |
| dokma | http://paste.debian.net/1293933/ | 21:33 |
| amesser | I have "Type=x11" here | 21:34 |
| dokma | Hmmm... interesting | 21:34 |
| dokma | This is TeamViewer log: http://paste.debian.net/1293934/ | 21:34 |
| amesser | Hmm, some people had success with running teamviewer like "XDG_SESSION_TYPE=x11 teamviewer" | 21:38 |
| dokma | Just ran into that | 21:38 |
| dokma | Let me try | 21:38 |
| amesser | its probably the way how your window manager is started | 21:40 |
| amesser | do you use ".xinitrc" or ".xsession" ? | 21:40 |
| amesser | https://wiki.gentoo.org/wiki/Elogind#startx_D-Bus_integration | 21:42 |
| dokma | I use .xinitrc | 21:42 |
| amesser | could you try to modify it as in the gentoo link described. | 21:43 |
| dokma | Still stuck at Type=tty | 21:56 |
| dokma | But I think that we are digging in the right direction | 21:56 |
| dokma | New discovery is that this variable gets set to tty as soon as I login on the Virtual Console | 21:57 |
| dokma | It obviously needs to be set correctly during startx execution | 21:57 |
| amesser | Not sure. could be that teamviewer wont work with startx. Seems to be a known issue, not fixed since years: https://community.teamviewer.com/English/discussion/comment/32597#Comment_32597 | 22:00 |
| amesser | The point is, from view of session management system, if you login on normal terminal (tty) its a terminal session. | 22:00 |
| amesser | using startx does not make your terminal session an x11 session since its still run from a terminal. | 22:01 |
| dokma | Hmmm... that unfortunately makes sense to a degree. On the other hand, using startx should logically change the session type. | 22:04 |
| amesser | I think its related to the "owner" of the session. IT does not change by calling startx | 22:07 |
| amesser | however, speculation :-) | 22:07 |
| amesser | you might consider an alternative to teamviewer | 22:07 |
| amesser | I was using it for a long time but had to switch also. Was annoyed by the advertising and periodically changing gui. ( Actually my grandma was annoyed :-) | 22:09 |
| amesser | sorry, i have to leave now. hope you get it fixed. good luck! | 22:14 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!