e3d3 | I'm a Devuan fan for years but after a new Chimaera net-install (after a HD-crash) I saw so much default installed primitive & childish games & nonsense that I didn't trust it any more & de-installed it. | 00:48 |
---|---|---|
e3d3 | What is the reason for the choice of this default installed software ? | 00:48 |
rwp | e3d3, What choices did you make at the software installation step? Whatever those choices were drove the installation. | 00:49 |
rwp | I personally uncheck everything, including "standard system" things, to avoid exim being installed. And then just install what I want after the first boot. | 00:50 |
rwp | Also most of those are meta-packages such as task-desktop and though the dependencies the task-* packages pull in other packages. | 00:52 |
e3d3 | rwp The only extra software that I selected during installating was CLI productivity tools, not cli dungeon games that start by asking your sexual preferences, fortune-cookies, cowsay, matrix-simulator and more of this very primitive stuff | 00:52 |
fluffywolf | somehow I've never had a game ask my sexual preferences, so I have no idea what you've been installing. lol | 00:53 |
e3d3 | I didn't installed this, maybe it was part of the cli productivity tools ? Previous Chimeara installs didn't had this kind of stuff | 00:54 |
rwp | I would "apt-get purge -s foo" replacing foo with whatever package you think is frivolous and then seeing what else it would purge that is depending upon it. | 00:59 |
e3d3 | I've read a little on the forum & know that the team have put a lot of thought in selecting the default software (e.g. an alternative for the locate command) but seeing this kind of very primitive & strange software made me worried about thoroughness of it. | 00:59 |
rwp | The -s is simulate and won't actually do anything but show what it would do it if did. | 00:59 |
fsmithred_ | task-productiviey or whatever it's called hasn't changed since ascii | 00:59 |
fsmithred_ | if you want to be selective about packages, don't install task-whatever | 01:00 |
e3d3 | I just bought a new pc, and will do a new install, now without CLI "productivity" tools. | 01:00 |
fsmithred_ | you might want to include the standard system utilities, but they aren't necessary | 01:01 |
fsmithred_ | less, whois, a few others like that | 01:01 |
e3d3 | This was the first time I selected the cli productivity tools during installation. Didn't expect this kind of software, which made a really bad almost shocking impression. | 01:03 |
fluffywolf | blame debian. lol. devuan doesn't manage tasksel... | 01:04 |
fluffywolf | most of those tasks drag in a whole lot of worthless shit. I've complained about this before. | 01:04 |
fsmithred_ | uhhh, the console-productivity task is one of ours | 01:04 |
fsmithred_ | pretty sure | 01:04 |
fluffywolf | I had to file a bug with debian when I complained that one of the things in it broke my house. :P | 01:05 |
fluffywolf | it drags in some braille terminal stuff that attempts to autodetect braille terminals by writing crap to every serial port it can find... even if the port goes to something that is not a braille terminal. like, for example, the monitoring port on my solar system. which responds to the garbage data by powering off the inverters and shutting off the power to my house. | 01:06 |
rwp | Since I prefer postfix over exim4 but exim4 is listed as standard the "standard system" checkbox installs exim4 which I then purge off when installing postfix. So for me that is simply a tuning step. | 01:07 |
fluffywolf | but, hrmm, yep, it does seem to be a devuan package now. | 01:08 |
fluffywolf | why the heck is something labeled productivity about 50% things that decrease productivity? :) | 01:08 |
rwp | Because trains stop at a train station therefore work stops at a workstation! | 01:09 |
fsmithred_ | yeah, I always thought it had a weird collection of non-productive stuff. | 01:10 |
e3d3 | for example the 3 installed morse & 2 advanced math-prog's | 01:11 |
fluffywolf | looks like it still installs brltty... which means that installing that task on my laptop would probably still immediately cause the power to my house to turn off. | 01:11 |
* fluffywolf checks the brltty bug tracker, and they still insist sending garbage to every serial device is an acceptable behavior | 01:17 | |
fluffywolf | I vote we put golinux in charge of task- packages. | 01:21 |
fsmithred_ | file a bug report on task-console-productivity with suggestions for changes in the Recommends. | 01:25 |
fluffywolf | didn't I do that in like 2019? but that was for debian, I think. | 01:25 |
fsmithred_ | I can't find that package. Got a correct spelling? | 01:27 |
fsmithred_ | no britty or brtty | 01:27 |
fluffywolf | brltty | 01:28 |
fsmithred_ | apt-cache doesn't know it | 01:28 |
fluffywolf | do you have a font where i and l look the same? :) | 01:28 |
brocashelm | i see a couple, like brltty-x11 | 01:29 |
brocashelm | brltty/unstable 6.5-7 amd64 | 01:29 |
brocashelm | i'm on ceres, so already went through the fontconfig fun | 01:29 |
fsmithred_ | no, I have eyes that make i and l look the same | 01:29 |
fluffywolf | lol | 01:30 |
rrq | ioi? | 01:32 |
fsmithred_ | oi | 01:32 |
fsmithred_ | oh, I'm gonna lose my tail. brb. | 01:32 |
fluffywolf | but tails are good! | 01:34 |
fsmithred | lol | 01:34 |
fsmithred | sorry, no offence meant. | 01:34 |
fsmithred | offense? | 01:34 |
_ds_ | Offence if you speak normal English; offense if you're American. | 01:37 |
brocashelm | offensce | 01:37 |
fluffywolf | Offence, eh? if you're Canadian? | 01:37 |
e3d3 | Now I know that the strange installed software belongs to the CLI productivity tools (what I never expected) I'll try a new Devuan install. | 01:47 |
e3d3 | Another question: How is it possible that ssh-server was installed although I didn't select this during install ? | 01:48 |
e3d3 | The previous Devuan version had the same issue, if I remember well | 01:49 |
fluffywolf | task-console-productivity also installs openssh-server | 01:50 |
fluffywolf | which is probably one of the things that actually should be in it. heh. | 01:50 |
e3d3 | I've just read the package list and could have known. Sorry & thanks | 01:51 |
fsmithred | another way to avoid extra stuff is to install without recommends | 01:57 |
fsmithred | apt --no-install-recommends install <package> | 01:57 |
e3d3 | I'll never follow blindly the recommends again ;) I expected as CLI productivity tools tools like fzf, ranger, kitty terminal, ripgrep etc. A description during install is essential for this package. | 01:59 |
fluffywolf | I'm not a fan of the tasks in general, and don't install them. | 02:00 |
e3d3 | I normally don't install collections and prefer a minimal start, but I'm lazy & tired of endless reading about to low-level stuff when installing everything myself, so I try to pick the best defaults. Devuan never disappointed me, so I'll try to consider the productivity-suite as a really bad monday-morning package, and try a new & cleaner install. | 02:14 |
e3d3 | I hope to join the fan-club soon again. Thanks all & good night/day | 02:14 |
AzumaHazuki | that guy sounds like an HOA mom >>; | 02:26 |
AlexLikeRock | hi | 06:12 |
AlexLikeRock | anyone can help me ? | 06:12 |
AlexLikeRock | rfkill list | 06:12 |
AlexLikeRock | 0: ideapad_wlan: Wireless LAN | 06:12 |
AlexLikeRock | Soft blocked: no | 06:12 |
AlexLikeRock | Hard blocked: no | 06:12 |
AlexLikeRock | 1: ideapad_bluetooth: Bluetooth | 06:12 |
AlexLikeRock | Soft blocked: yes | 06:12 |
AlexLikeRock | Hard blocked: no | 06:12 |
AlexLikeRock | what mean "hard block " or "soft blocked ? | 06:13 |
gnarface | i think soft blocked just means the driver configuration | 06:17 |
gnarface | not sure | 06:17 |
gnarface | maybe a userspace tool | 06:18 |
AzumaHazuki | softblocked means you need to use "rfkill unblock 0" (or 1) to unblock it | 06:21 |
AzumaHazuki | it means the physical hardware can transmit, but it's been locked down in software | 06:22 |
AlexLikeRock | i did | 06:26 |
AlexLikeRock | "rfkill unblock 1" | 06:26 |
AlexLikeRock | and noting happen | 06:26 |
AzumaHazuki | might need to do it as root or with sudo? | 06:27 |
* joerg does wild guessing: soft blocked = by UI, hard blocked = a switch or pushbutton on the laptop | 06:28 | |
AlexLikeRock | yes: as root | 06:29 |
AlexLikeRock | https://paste.debian.net/1278829/ | 06:30 |
gnarface | i think i've run into the issue as a symptom of driver problems | 06:31 |
gnarface | i don't recall if i ever fixed it. i think i just changed kernel versions to an older kernel for as long as i could manage then eventually gave up on that hardware. | 06:32 |
AzumaHazuki | try sudo rfkill unblock all | 06:32 |
AlexLikeRock | rfkill unblock all : not work | 06:34 |
gnarface | which kernel, AlexLikeRock? | 06:35 |
AlexLikeRock | Linux thinkpad 5.10.0-16-686-pae #1 SMP Debian 5.10.127-1 (2022-06-30) i686 GNU/Linux | 06:36 |
AlexLikeRock | the problem , its no new kernel | 06:36 |
AlexLikeRock | its NEW LAPTOP | 06:36 |
gnarface | hmm, well try the backports kernel | 06:37 |
gnarface | maybe if it's newer hardware you just need a newer kernel | 06:37 |
AlexLikeRock | daaam | 06:38 |
gnarface | it's not that hard to test | 06:39 |
gnarface | the old kernel won't be uninstalled | 06:39 |
gnarface | you'll still be able to select it at boot | 06:39 |
AlexLikeRock | yes i now that gnarface | 06:40 |
joerg | dmesg/syslog should show a few details at least | 06:40 |
AlexLikeRock | dmesg ---> https://paste.debian.net/1278830/ | 06:42 |
AlexLikeRock | how to detect the missing firmware ? | 06:48 |
AlexLikeRock | to install | 06:48 |
AlexLikeRock | it | 06:48 |
rrq | search on idVendor=8087, idProduct=07dc | 06:50 |
joerg | [ 111.382624] Bluetooth: hci0: command 0x0c03 tx timeout | 06:55 |
joerg | [ 119.382933] Bluetooth: hci0: sending initial HCI reset command failed (-110) | 06:55 |
joerg | USB port broken? you got another port to try? (assuming this is a USB BT dongle) | 06:55 |
AzumaHazuki | wait, why a 32 bit kernel on new hardware? | 06:55 |
plasma41 | Looking at https://h-node.org/bluetooth/view/en/2046/Intel-Bluetooth-Device--7260- it doesn't appear that Bluetooth adapter requires any external firmware, though I could be wrong about that. | 06:57 |
plasma41 | Is the necessary kernel module loaded? `lsmod | grep btusb` should produce output if it is. | 07:00 |
plasma41 | ^ AlexLikeRock | 07:01 |
AlexLikeRock | joerg, it is bluetooth module is internal in the laptop | 07:02 |
AlexLikeRock | AzumaHazuki, i like more 32 bit, its hard UPGRADE 32 bits to 64 bits by run manual DPKG at terminal | 07:04 |
plasma41 | AlexLikeRock: What is it that you like about it? Lack of 64-bit pointers? If so, are you familiar with the x32 ABI? | 07:06 |
AlexLikeRock | AzumaHazuki, I already did it once and I didn't feel like making the change again | 07:06 |
joerg | I wouldn't be too surprised to learn that not all drivers work in 32bit | 07:09 |
AlexLikeRock_ | hi | 07:12 |
AlexLikeRock_ | im back | 07:12 |
AlexLikeRock_ | # lsmod | grep btusb | 07:13 |
AlexLikeRock_ | btusb 49152 0 | 07:13 |
AlexLikeRock_ | btrtl 24576 2 hci_uart,btusb | 07:13 |
AlexLikeRock_ | btbcm 16384 2 hci_uart,btusb | 07:13 |
AlexLikeRock_ | btintel 24576 2 hci_uart,btusb | 07:13 |
AlexLikeRock_ | bluetooth 483328 15 btrtl,hci_uart,btintel,btqca,bnep,btbcm,btusb | 07:13 |
AlexLikeRock_ | usbcore 208896 5 uvcvideo,xhci_pci,rtsx_usb,btusb,xhci_hcd | 07:13 |
gnarface | using the backports kernel? | 07:14 |
joerg | note that the BT seems to disconnect or get disconnected from BT on receiving the "initial HCI reset command 0x0c03 tx", reconnects to USB ("new full-speed USB device...") and 2s later the same game repeats from beginning | 07:20 |
joerg | note that the BT seems to disconnect or get disconnected from *USB* [sorry] on receiving the "initial HCI reset command 0x0c03 tx", reconnects to USB ("new full-speed USB device...") and 2s later the same game repeats from beginning | 07:21 |
joerg | also relevant: "[ 109.360396] usbcore: registered new interface driver btusb" which means the kernel module gets loaded, right? | 07:25 |
gnarface | hmm.... | 07:39 |
gnarface | AlexLikeRock_: try disabling power management for bluetooth. there might be a module option to do it. | 07:40 |
gnarface | i've seen this pattern of timeouts/disconnects before | 07:40 |
gnarface | with other usb devices | 07:40 |
gnarface | webcams and wifi stuff | 07:40 |
gnarface | but might be the same issue | 07:41 |
gnarface | (someone please tell him when he comes back) | 07:41 |
AlexLikeRock | im back | 08:03 |
AlexLikeRock | trying : https://www.cyberciti.biz/faq/intel-wifi-on-debian-linux-when-you-get-firmware-failed-to-load-iwlwifi-8265-36-error/ | 08:07 |
AlexLikeRock | just need wifi firmware | 09:12 |
AlexLikeRock | the solution https://slimbook.es/tutoriales/linux/73-instalar-driver-wifi-en-linux | 09:13 |
AlexLikeRock | now its wifi fix-it | 09:13 |
AlexLikeRock | lest test bt again | 09:13 |
gnarface | so the bluetooth doesn't work without the wifi firmware? | 10:07 |
gnarface | must be one of those dumb combo chips | 10:08 |
schillingklaus | bluetooth is a huge security gap, anyways | 10:12 |
jiggawatt | yeah disable bluetooth everywhere | 10:31 |
jiggawatt | 0 needed | 10:31 |
AlexLikeRock | how? | 10:36 |
brocashelm | i think the bluetooth service(s) should be listed under service --status-all | 10:37 |
brocashelm | then when you find the bluetooth service, issue service bluetooth stop | 10:38 |
AlexLikeRock | [ + ] bluetooth | 10:39 |
AlexLikeRock | looks , its on | 10:39 |
AlexLikeRock | service bluetooth status | 10:40 |
AlexLikeRock | [ ok ] bluetooth is running. | 10:40 |
brocashelm | service bluetooth stop | 10:41 |
brocashelm | then check again | 10:41 |
AlexLikeRock | instaling bluetooth and blueman .... | 10:44 |
AlexLikeRock | https://paste.debian.net/1278836/ | 10:50 |
AlexLikeRock | they not area at conflict bluetoothctl and bluetoothd ? | 11:05 |
rrq | no they go together | 11:10 |
AlexLikeRock | tanks | 11:10 |
rrq | but isn't your h/w is a combined wireless/bluetooth device? or is the wireless device tunneled over a local bluetooth link? | 11:12 |
dan9er[m] | Why do I suddenly have 109 upgradable packages | 18:44 |
dan9er[m] | Did something happen? | 18:44 |
fsmithred | dan9er[m], which release are you running and when did you last upgrade? | 18:56 |
dan9er[m] | I'm running Chimaera and I update & upgrade every day | 18:57 |
dan9er[m] | All my Devuan sources point to the onion service | 18:58 |
fsmithred | I can't do an update right now to see if anything has changed. That does sound like something is wrong. | 19:03 |
fsmithred | slow internet and doing a download that will take about 40 more minutes. | 19:04 |
rwp | dan9er[m], Pick one package sample, run "apt-cache policy foo", see where it is installed from? | 19:05 |
* debdog had 96 right now | 19:06 | |
rwp | I don't see any large changes in chimaera in the past few days on my systems. | 19:07 |
dan9er[m] | bruh, ok so it's not just me | 19:07 |
n4dir | quite some upgrades here too, most are libs though | 19:09 |
rwp | Just loaded today's upgrade and there are upgrades to quite a few things today. apache2 isc-dhcp libc mariadb postfix tzdata and so on | 19:09 |
rwp | Which feels like Debian released a point release and we should soon be seeing an announcement to that effect. | 19:10 |
dan9er[m] | rwp: I working on that cache policy, just my usual pastebin is being difficult | 19:10 |
rwp | dan9er[m], It's okay. That's just my usual go-to tool to see if the sources.list is pointing to Ceres/Unstable or something by accident. | 19:11 |
dan9er[m] | here https://paste.ec/paste/eB6VsqAk#KiXYfpRX-bxnL0fKrhIz/JOoB/9K9s55rQIC2QKQz4/ | 19:12 |
rwp | dan9er[m], Looking at your paste that matches what I see for libreoffice-common too. You have 1:7.0.4-4+deb11u4 installed and 1:7.0.4-4+deb11u6 is now available. | 19:14 |
dan9er[m] | Btw, the date in the changelog for ^ is 2023-03-25 | 19:14 |
rwp | I also see that you have chimaera-backports/main and daedalus/main and unstable/main in your sources.list too though. | 19:14 |
unixman_home | Yup. I can has updates too: "81 packages can be upgraded. Run 'apt list --upgradable' to see them." | 19:14 |
rwp | Which will make me wonder if they are pinned appropriately because otherwise you will get all of Unstable offered for upgrade. | 19:15 |
dan9er[m] | I believe I've configed my priories correctly, besides others here are getting mass upgrades too | 19:16 |
dan9er[m] | s/priories/priorities/ | 19:16 |
dan9er[m] | Is it normal for a package to be uploaded to sources a month after the date in the changelog? | 19:17 |
dan9er[m] | My concern is a Amphora malfunction | 19:17 |
rwp | If this is a normal point release then it is not abnormal to have a bunch of things released all at once on the quarterly cycle and therefore some of those will have gone through unstable perhaps quite some time previously. | 19:19 |
rwp | Take a look at a *previous* point release announcement https://www.debian.org/News/2022/20221217 | 19:20 |
dan9er[m] | Ha, found it https://www.debian.org/News/2023/20230429 | 19:24 |
dan9er[m] | I guess creating a new year folder for all the news/announce stuff gave them a bit of trouble | 19:25 |
dan9er[m] | >Those who frequently install updates from security.debian.org won't have to update many packages | 19:26 |
dan9er[m] | lol bs | 19:26 |
rwp | No, it's true. A bunch of those point release packages were already distributed through security. | 19:27 |
dan9er[m] | Well I still have 109 upgrades | 19:28 |
n4dir | fun fact: me not caring at all about what gets upgraded for what reasons ... works too | 19:28 |
dan9er[m] | Well wouldn't 109 at once give you pause? | 19:29 |
n4dir | i don't think so | 19:29 |
dan9er[m] | k den | 19:30 |
dan9er[m] | Seems off-topic now, so i'll stop there | 19:30 |
n4dir | dan9er[m]: i didn't say you shouldn't. Or it wouldn't make sense. I just said what my approach is, which may well be seen as a bit very naive to many | 19:31 |
n4dir | but in thos 15+ years it kinda worked for me | 19:32 |
rwp | I currently install all available upgrades every day automatically by cron. | 19:34 |
n4dir | but then what do you do if you are bored? | 19:35 |
rwp | When the total size of the repos used to be smaller I have previously pipelined it so that I had canary machines install immediately and production machines install things three days later. The repos is so large now making that pipeline more difficult to maintain. | 19:35 |
rwp | Bored? Who has time to be bored! | 19:36 |
n4dir | old people :-) | 19:36 |
tom-1 | Hi all . I would appreciate any help or advice.... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/e456f5031b968622d1d516b4c69ff1a81e33dfdc>) | 19:46 |
rwp | tom-1, >Correctly, I understand that from a security point of view, I should always have this answer "echo $DISPLAY" :0 If I do not receive such a response, how can I correct the situation? | 19:49 |
rwp | tom-1, That answer assumes that your display is :0 and on my system it is almost always :1 instead as I am typically operating on a secondary X Window display. | 19:49 |
rwp | In other words... It all depends upon what you are doing. And this is X Windows. A lot of people have switched to Wayland, which I understand is quite different. I have not used Wayland myself yet. | 19:49 |
n4dir | export DISPLAY=localhost:0.0 ; is what the web says. | 19:50 |
rwp | But having said that... DISPLAY is simply an environment variable. You can set it as you desire. | 19:50 |
rwp | The "localhost" and ".0" parts are defaults which will be assumed if not set explicitly. | 19:51 |
rwp | Some people forward X through ssh with "ssh -X" and that will use a different display number, usually localhost:10.0, when forwarding the display. | 19:52 |
rwp | I fail so far to see a *specific* security issue from this yet so tom-1 if you have a concern please ask it. | 19:53 |
tom-1 | n4dir: rwp Thank you very much for your explanation. I'll read a little more to better understand this topic. | 20:16 |
n4dir | you probably meant rwp | 20:17 |
rwp | n4dir, You also helped with your comments about setting DISPLAY! Don't sell yourself short. :-) | 20:41 |
n4dir | yeah, but i didn't explain anything. | 20:41 |
n4dir | well, anyway, good he seems to have it kinda sorted | 20:41 |
rwp | The rule is "See one. Do one. Teach one." Having been helped a lot ourselves we must "pay it forward". :-) | 20:42 |
n4dir | :-) | 20:43 |
n4dir | i only ran in DISPLAY once, when fiddling with live-isos and configuring them via xhost or xnest or such | 20:43 |
n4dir | it was very interesting, funny. | 20:43 |
n4dir | but with refractasnapshot such wild things are not needed anymore. | 20:44 |
tom-1 | Actually I installed OpenBSD but it doesn't apply to this group and got this message ;... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/3ded48cf9d911ebdaef433e02852f2d2de2d8396>) | 20:44 |
rwp | It is unusual to need to touch DISPLAY in any way as it is normally all handled correctly automatically. | 20:44 |
n4dir | yup, else i really never ran in it | 20:45 |
rwp | tom-1, That is dealing with xauth which deals with ~/.Xauthority file containing the authorization cookie. Usually called the MIT X Magic Cookie. | 20:46 |
rwp | It's OpenBSD so maybe on #openbsd you would get better more OS specific help. Such as why it is causing this permission error for you. | 20:47 |
rwp | Having said that I have run into similar problems due to the, ahem systemd folks, messing with things. And can force it. | 20:47 |
rwp | If the .Xauthority file is not created automatically then "xauth generate $DISPLAY" will create it and set a cookie. | 20:47 |
rwp | And then restart X Windows which should read the new cookie and allow use of it for access. | 20:48 |
rwp | IIRC the systemd folks move the .Xauthority file out of the $HOME directory and into a /run/user/$uid tmpfs location. | 20:49 |
tom-1 | unfortunately their chat is absolutely not friendly unlike Devuan) This chat has very friendly people in my experience, I almost always get answers. Sometimes I think it's better to be kind than smart ))) | 20:49 |
rwp | That causes me problems in those rare situations where I want to log into a system remotely over ssh and then use the remote display. | 20:49 |
rwp | Being easy to work with is a massively underrated career skill. | 20:50 |
rwp | I also remember needing to unset XAUTHORITY when the systemd folks set it to their private location in order to have it default back to $HOME/.Xauthority and have things operate normally. | 20:51 |
rwp | So with all of that I suggest a thorough reading of "man xauth" on your OpenBSD system and see if things make sense then. | 20:52 |
n4dir | not sure, and right now no one complains here anyway, but for - in this case - OpenBSD questions you might try #devuan-offtopic | 20:53 |
n4dir | doesn't seem offtopic there to me. | 20:53 |
rwp | For those wondering about remote control of systems... My TV is connected to a system. I log in with ssh and play Youtube videos on the TV screen. | 20:53 |
tom-1 | rwp: thanks for your comments, I'll go study the topic)) I need to resolve the issue🤝 | 20:54 |
rwp | My opinion is that as long as this channel is technical discussion then it is okay. And move random social chatter to -offtopic works. | 20:54 |
n4dir | the one time were X didn't start for me i just deleted .Xauthority. Might be then startx just recreates it, might also be the above command "xaucht generate $DISPLAY" does the same. I wouldn't know. I am the sledgehammer kinda guy, not the understand-things guy | 20:55 |
n4dir | delete: mv to .Xauthority_Backup, duh | 20:55 |
n4dir | rwp: yup, sure. I only mentioned it as tom-1 had a few little doubts. As an option | 20:56 |
rwp | "xauth list" should list out the contents of the binary $HOME/.Xauthority file in a human readable format. | 20:57 |
rwp | That file accumulates cookies but never discards them. So there might be ancient cookies from other randomly used display numbers. | 20:57 |
n4dir | i sure don't remember how on earth i could screw my .Xauthority. Didn't know it back then either. Did nothing (nothing i knew about) | 20:58 |
rwp | There are an infinite number of ways to break things. But usually only one way for things to work correctly. :-) | 20:59 |
rwp | tom-1, I am reminded that the X Windows communication socket will usually be an on file system Unix domain socket. | 21:01 |
rwp | Traditionally and in my case with XAUTHORITY unset it is /tmp/.X11-unix/X0 but on legacy systems might be a TCP networking socket. | 21:01 |
rwp | That is the difference in the xauth cookies between localhost/unix:0 and localhost:0 which denotes the two different types. | 21:02 |
rwp | We now launch Xorg with the -nolisten option to disable the TCP socket by default as a security measure. | 21:03 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!