| onefang | Figured out what I did wrong before when trying to access IRC via the biboumi bridge, used from psi-plus XMPP client. The biboumi IRC wrapper syntax is a bit arcane, didn't know I needed to add a : before the actual message to nickserv when IDENTIFYing. Luckily I spotted those two tiny dots in an example. | 02:12 |
|---|---|---|
| rustyaxe | raw commands? makes sense; last argument beginning with : means to stop splitting parameters on ' ' characters ;) | 02:22 |
| onefang | No idea why. shrugs | 02:24 |
| rustyaxe | Just way IRC protocol works for last ~40 yers :P | 02:32 |
| onefang | Ah, that's from IRC, not from biboumi. | 02:33 |
| avir327 | Is this a place to talk about kernel panics? | 11:10 |
| avir327 | (good morning!) | 11:11 |
| Xenguy | avir327, I don't see why not, but be patient in waiting for a reply | 12:50 |
| adhoc | avir327: how about you start with a little bit more info ... | 12:53 |
| al1r4d | avir327, yes | 13:29 |
| avir327 | Xenguy, adhoc, al1r4d: Not sure if this is serious, but (most probably) my sshd caused a kernel panic on login. Just wanted to let you know in case there are more people affected. | 14:57 |
| avir327 | I'll just leave this here, definitely no problem for me (my Linux-playground in vbox, not exposed to anything but its host). | 14:59 |
| CueXXIII | avir327: that sounds strange, but without the actual panic log i doubt that would be of any use :( | 15:04 |
| systemdlete | I can work around this, actually, but I am very curious why it is not working. I run ssh to system A and it reads my .bashrc but if I run ssh to system B, it does not read my .bashrc on that system. | 15:36 |
| systemdlete | system A is daedalus and system B is chimaera. | 15:36 |
| systemdlete | the sshd_config is more or less the same on both systems | 15:36 |
| systemdlete | I can see from the script I am running on the remotes that the envars I need are being set or not. | 15:37 |
| systemdlete | I put a "echo hello" nonce in the /etc/profile on both systems just to see if they get read. | 15:37 |
| systemdlete | so, I think, if I am analyzing this correctly, that /etc/profile is getting read by sshd on A but not on B? | 15:38 |
| systemdlete | idk. Why I'm here... | 15:38 |
| systemdlete | It would be nice if .bashrc got read on both systems so I don't have to fudge it | 15:39 |
| systemdlete | let me correct myself: I meant that /etc/bash.bashrc is getting read on both systems when invoked from ssh, but the ~/.bashrc is not getting read on the chimaera system. | 15:56 |
| gnarface | systemdlete: you have to reference ~/.bashrc from ~/.bash_profile (or one of the other optional names for ~/.profile) | 15:56 |
| systemdlete | I put the nonce in /etc/profile and in /etc/bash.bashrc | 15:56 |
| gnarface | i think .login or... i forget now, the man page lists the names of files it looks for, ~/.bashrc isn't one of them | 15:57 |
| systemdlete | I only see the echo message from /etc/bash.bashrc on both, but not the /etc/profile for both | 15:57 |
| gnarface | hmm, actually it may be more complicated than i'm thinking, but the man page does explain it | 15:57 |
| systemdlete | well, yes, it does. It just doesn't seem to /actually/ work the way they claim, at least not for bullseye/chimaera. | 15:58 |
| gnarface | hmm, odd | 15:58 |
| systemdlete | right here, on another daedalus system, I have .bashrc but not .bash_profile in my home. | 15:58 |
| gnarface | is that system running a GUI? | 15:58 |
| systemdlete | the .bashrc does get read in at login, or when running from script (without ssh) | 15:59 |
| systemdlete | you mean xfce4? | 15:59 |
| systemdlete | yes | 15:59 |
| systemdlete | in fact, every one of the systems mentioned is running xfce | 15:59 |
| gnarface | i have a comment in mine that says to read /usr/share/doc/bash/examples/startup-files | 16:00 |
| systemdlete | I am guessing I'll have to do a lot more drilling down to figure this out | 16:00 |
| systemdlete | funny thing, gnarface, is that I really haven't changed anything in /etc for profile and bashrc configuration | 16:00 |
| gnarface | i guess i don't use this file much for the systems i access by ssh so if it wasn't working i'm not sure i'd have noticed | 16:00 |
| * systemdlete goes back to drilling down | 16:03 | |
| gnarface | i just know that for some dumb reason several GUIs stopped even reading the user's profile, so i had to do workarounds for that, but that doesn't sound related to your issue | 16:04 |
| gnarface | my existing assumption was just that the user's profile (available by 3 names) is supposed to be read for login shells, and ~/.bashrc is supposed to be read for login shells, so you have to reference it from the profile so they both get read for login shells | 16:06 |
| gnarface | ....~/.bashrc is supposed to be read for non-login shells i meant to type | 16:06 |
| systemdlete | (right, that's how I undestand it also) | 16:08 |
| systemdlete | but .bashrc can be read in from another startup file if needed | 16:08 |
| gnarface | only thing i could think is, maybe you have the profile under one of the other names in there doing nothing ? | 16:08 |
| systemdlete | I'll double-check but I don't think so. hold on | 16:08 |
| gnarface | according to the man page: ~/.bash_profile, ~/.bash_login, or ~/.profile. | 16:08 |
| gnarface | but there also seems to be some command-line options to override whether bash considers itself a login or non-login shell mentioned... not sure where they'd go but maybe check for one of them... | 16:09 |
| gnarface | for some reason i remember those 3 names not being an exhaustive list and that stuff like ~/.login would also work, but maybe i'm getting some other system confused here | 16:10 |
| systemdlete | and then there is BASH_ENV which can be set to read and set envars... | 16:16 |
| systemdlete | yeah, a ton of different ways. | 16:16 |
| systemdlete | well, I've checked, and I don't see a clue (yet) as to why it is working differently. | 16:16 |
| systemdlete | my local bashrc on the chimaera system is DEFINITELY not getting read, bc I don't see my echo meesages | 16:17 |
| systemdlete | (but I do when I run ssh to the daedalus system) | 16:18 |
| systemdlete | as far as login/non-login shell distinctions, afaik, I am not purposely trying to invoke the shells one way or the other; I leave it up to ssh and sshd to figure that out | 16:21 |
| systemdlete | (btw, I DID look at that also. Thanks for the reminder though) | 16:22 |
| systemdlete | I wonder if either openssh or the bash packages were modified between C and D? | 16:24 |
| systemdlete | (possibly to address some of these very concerns about ordering of startup scripts, etc) | 16:25 |
| systemdlete | thanks for the help again. bbl (bfast time) | 16:25 |
| gnarface | this issue seems to ring a bell but i can't remember what solution if any was discovered... i wonder if it's some security bandaid | 16:38 |
| gnarface | or maybe some virtualization snafu? hmm.... | 16:39 |
| al1r4d | avir327, drop the log | 18:00 |
| al1r4d | ah, he's gone | 18:00 |
| mason | systemdlete: Just to throw a wrench into the works, remember that the traditional files work too - .profile and .shrc | 18:19 |
| mason | I use those, as I don't always use Bash. | 18:19 |
| rwp | One of the worst design choices bash ever made was to not read the .bashrc file in a login shell and requiring it to be sourced explicitly from the .profile/.bash_profile instead. | 18:46 |
| mason | Agreed. | 19:01 |
| rwp | I used to keep one .profile and it would work for sh, ksh, bash, and so on. But that became cluttered. Now I keep a very simple .profile for sh and a bash specific .bash_profile with more stuff in it which also sources the .bashrc file. Both are easier to read now. | 19:13 |
| fsmithred | systemdlete, on my systems, ssh uses ~/.profile which sources ~/.bashrc. It's the same on beowulf, chimaera and excalibur. (current local machine is chimaera) | 19:22 |
| systemdlete | fsmithred, mason, rwp, gnarface: I just ran a simple test. I added a line at the top of /etc/profile: echo hello from /etc/profile > /tmp/profile.out | 19:41 |
| systemdlete | Then, I ran the ssh invocation on each system--locally (meaning, from that system TO that same system)-- and there was no output from either. | 19:42 |
| systemdlete | Now, I don't know if, perhaps, somehow the stdout is being trapped or diverted or snuffed out cmopletely, but those are the results. | 19:42 |
| systemdlete | (clarification: I added that line to the top of /etc/profile on both C and D systems) | 19:44 |
| systemdlete | furthermore, it seems that even if I invoke a local shell directly--no ssh--that message does not appear. | 19:48 |
| systemdlete | btw, I changed the test to "echo hello from /etc/profile | tee /tmp/profile.out" hoping to get to see the message either on the stdout or the file capture | 19:48 |
| gnarface | systemdlete: you sure the default shell is still bash on those systems? | 19:49 |
| systemdlete | default shell... I don't recall changing it. Where is that set? | 19:49 |
| gnarface | symlink from /bin/sh | 19:50 |
| systemdlete | do you mean chsh? | 19:50 |
| systemdlete | oh, let me check. | 19:50 |
| gnarface | used to be bash, these days it's dash, which is kinda like "bash lite," but there's so many options | 19:51 |
| systemdlete | points at /bin/dash on both C and D | 19:51 |
| gnarface | what about the value of $SHELL to the user | 19:52 |
| gnarface | after logging in via ssh and from a local console | 19:52 |
| systemdlete | I had checked that earlier, but then tore it out. Hold on, checking... | 19:52 |
| gnarface | per-user shell setting is in /etc/passwd | 19:52 |
| gnarface | also maybe worth making a new user and seeing if it's getting the same returns on all these checks | 19:53 |
| systemdlete | shell seems to be /bin/bash. The script I am running (set by ForceCommand in sshd_config) is #!/bin/bash, but that's the same on both systems too | 19:54 |
| gnarface | hmm, weird | 19:54 |
| gnarface | these are VMs? or bare metal? | 19:55 |
| systemdlete | VMs, both | 19:55 |
| gnarface | vbox still? | 19:55 |
| systemdlete | yep | 19:55 |
| systemdlete | (sorry about that) | 19:55 |
| gnarface | i wonder if vbox could be doing something weird | 19:55 |
| systemdlete | (I know that doesn't ingratiate myself with anyone here) | 19:55 |
| systemdlete | in only one VM and not the other? | 19:55 |
| systemdlete | I'd say that's unlikely | 19:55 |
| gnarface | well one is daedalus and one is chimaera you said right? | 19:56 |
| systemdlete | although, vbox does offer options to configure VM for specific distros | 19:56 |
| systemdlete | yes, one is C and one is D | 19:56 |
| gnarface | i was thinking maybe a vbox bug that only affects one distro or something like that | 19:56 |
| gnarface | one release, rather | 19:56 |
| systemdlete | LOL That might be it. | 19:57 |
| systemdlete | C is configured for Linux 2.4/2.6/blah and D is configured for Debian | 19:57 |
| systemdlete | let me change C to Debian and see if that makes a diff | 19:58 |
| gnarface | is there a reason you didn't set them both to debian? | 19:58 |
| systemdlete | I created them at different times. D was cloned from a "Daedalus Template VM" | 19:58 |
| gnarface | ah | 19:58 |
| systemdlete | I don't remember how C was created. years ago now | 19:59 |
| systemdlete | but let me try that. | 19:59 |
| systemdlete | they should be the same anyway | 19:59 |
| systemdlete | OK, so I changed both of them to be for the specific releases (Bullseye and Bookworm) | 20:03 |
| systemdlete | same results, though. :( | 20:04 |
| systemdlete | also, I don't remember now if I used the devuan ISO to create the C VM, or maybe a variant like refracta | 20:05 |
| fsmithred | look for /var/log/refractainstaller.log | 20:05 |
| systemdlete | not that that should make much difference w/r/t shell behavior, but I thought I would mention it | 20:05 |
| systemdlete | ah, fsmithred , thanks | 20:05 |
| asz09 | Hey! I'm new here.. i'm not sure if i can ask for help in this chat. | 20:05 |
| fsmithred | also 'cat /etc/issue' usually says refracta | 20:05 |
| fsmithred | yeah, this is the help channel | 20:06 |
| fsmithred | ask and wait - could be seconds, minutes or hours before an answer comes | 20:06 |
| systemdlete | no log and I checked earlier in /etc/os-release. Neither hint of refracta, so probably I installed from standard ISOs | 20:06 |
| fsmithred | which release is the host? | 20:07 |
| systemdlete | fsmithred, you said your systems use /bin/sh for ssh? | 20:07 |
| systemdlete | host is D | 20:07 |
| fsmithred | I said ssh uses .profile | 20:07 |
| systemdlete | sorry, I meant that | 20:07 |
| systemdlete | how do you know? | 20:07 |
| fsmithred | good, I'm on daedalus now | 20:07 |
| systemdlete | did you set something in your sshd_config? | 20:08 |
| fsmithred | I defined a variable in .profile on the remote and then logged out and in again to echo $var | 20:08 |
| fsmithred | logge out/in ssh, not the remote desktop | 20:08 |
| fsmithred | I'm about to fire up vbox | 20:09 |
| systemdlete | sorry to do that to you fsmithred. I consider you a friend. | 20:09 |
| fsmithred | what did you do to me? | 20:10 |
| systemdlete | I don't have .profile's in my C or D | 20:10 |
| systemdlete | (made you boot vbox) | 20:10 |
| asz09 | thank you so much. I did a fresh install and configured my kernel, did my security tweaks as I normally do but i'm having a problem with my xfce GUI... Network manager says its not running, i cant access audio, and i cant shutdown or suspend nor switch user. The option appear greyinsh. I can do all the latter using the terminal. I suspect it has something to do with DBus. The error message i got in | 20:10 |
| fsmithred | lol | 20:10 |
| asz09 | syslog was "dbus-daemon[1557]: [system] Activated service 'org.freedesktop.PolicyKit1' failed: Launch helper exited with unknown return code 1" | 20:10 |
| systemdlete | omg | 20:11 |
| fsmithred | asz09, make sure policykit-1-gnome is installed | 20:11 |
| * systemdlete hits self hard. Really hard. | 20:11 | |
| systemdlete | there IS a .profile on the D sysstem, just not on C | 20:12 |
| fsmithred | weird. How did that happen? | 20:12 |
| systemdlete | I think I accidentally did my test on the host (which is D) when I meant to pull up the C VM | 20:12 |
| systemdlete | so all I need to do is get a .profile and this should be ok | 20:13 |
| asz09 | I checked, it was... it's weird because i wasnt happening before. I tried rebooting, restarting services and everything... | 20:14 |
| fsmithred | systemdlete, I get same result on excalibur VM | 20:15 |
| systemdlete | same result as... ? | 20:18 |
| fsmithred | asz09, is this daedalus or excalibur? Did you use one of the installer isos or desktop-live? | 20:19 |
| fsmithred | ssh reads .profile | 20:19 |
| systemdlete | on mine, .profile does not seem to be running at all | 20:19 |
| systemdlete | i put an echo near the top of .profile, but it does not echo | 20:19 |
| fsmithred | I put a var def at the end | 20:19 |
| asz09 | fsmithred, i'm using daedalus, used netinstall (which worked perfectly) | 20:20 |
| systemdlete | on the other hand, I don't get .profile output on my D VM either | 20:20 |
| systemdlete | otooh, these are in xfce4-terminals, so .profile will not be read anyway (per docs) | 20:29 |
| systemdlete | .profile is only for login shells | 20:29 |
| systemdlete | but $0 is -bash, not bash, which means it IS a login shell after all (on D at least) | 20:31 |
| fsmithred | .profile is not read when you open the terminal. It does get read if you ssh localhost | 20:35 |
| fsmithred | in that same terminal | 20:35 |
| systemdlete | supposedly. Not here though | 20:38 |
| systemdlete | There, on yours, yes | 20:38 |
| systemdlete | (apparently) | 20:38 |
| systemdlete | what is confusing me even more is that on some of my system, echo $0 in the terminal gives me -bash (interative shell) and some give me /bin/bash (non-interactive shell) | 20:39 |
| systemdlete | even across D systems... so I've got something hosed up here | 20:39 |
| systemdlete | it is only adding to my confusion | 20:39 |
| fsmithred | I get bash in a desktop terminal and -bash in the ssh login | 20:43 |
| systemdlete | ssh user@remote 'echo $0' gives me "bash", not "-bash" | 20:54 |
| systemdlete | (D) | 20:54 |
| gnarface | asz09: run the command "groups" as your user and make sure you're in the audio group. as for the other stuff... just kinda sounds like you're missing a couple packages or have the wrong combination of packages for permissions backend and login manager... do you know which login manager you're using (sorry i'm not sure what the defaults are) | 20:55 |
| gnarface | ? | 20:56 |
| fsmithred | dpkg -l | grep -E "policykit|polkit|login|consolekit|libpam" | 20:58 |
| systemdlete | fsmithred: me? | 20:58 |
| fsmithred | ^^^ asz09 and put the results on paste.debian.net | 20:59 |
| systemdlete | (oh) | 20:59 |
| systemdlete | fsmithred, when you "ssh user@remote 'echo $0'" what do you get? "bash" or "-bash"? | 20:59 |
| fsmithred | I might have forgotten something in that list | 20:59 |
| systemdlete | (on Daedalus) | 20:59 |
| fsmithred | -bash over ssh | 20:59 |
| fsmithred | uh that was from daedalus to excalibur/ceres VM | 21:00 |
| systemdlete | wonder how I am getting such a different result | 21:00 |
| systemdlete | can you do it from localhost to localhost? | 21:00 |
| systemdlete | so | 21:00 |
| systemdlete | ssh localuser@localhost 'echo $0' | 21:00 |
| fsmithred | I get -bash with that | 21:01 |
| systemdlete | huh | 21:01 |
| fsmithred | in the same terminal where I got just bash before the ssh | 21:01 |
| systemdlete | right, ok... | 21:01 |
| systemdlete | weird | 21:01 |
| systemdlete | wth is going on here | 21:01 |
| fsmithred | what does -bash mean? | 21:01 |
| fsmithred | what't the minus? | 21:01 |
| systemdlete | it indicates login shell | 21:01 |
| systemdlete | same as bash --login | 21:02 |
| systemdlete | or -l | 21:02 |
| fsmithred | ok | 21:02 |
| systemdlete | (lower L) | 21:02 |
| fsmithred | you looked in /etc/sshd_config for something related? | 21:02 |
| asz09 | fsmithred, thank you for the attention. https://paste.debian.net/1322978 | 21:02 |
| systemdlete | so with login shell, the .profile gets read, and from there, the .bashrc | 21:02 |
| systemdlete | fsmithred, yes | 21:02 |
| systemdlete | I think I'm going to settle for setting variables explicitly. I was hoping to avoid that, but it's not that big a deal really. I am just totally perplexed why my shells and reading startup files are so out of whack. | 21:03 |
| systemdlete | why they are diff from yours, e.g. | 21:04 |
| systemdlete | or why my chimaera is different from my daedalus | 21:04 |
| systemdlete | what is really odd is that on the test D system, I get "bash" (not -bash) running ssh, yet the .bashrc is getting read and vars inside are being set! | 21:06 |
| systemdlete | per the docs and specs, that shouldn't be happening yet it is | 21:06 |
| systemdlete | OTOOOOOOOH, it is a testbox with test VMs that do get some changes for my testing purposes. | 21:07 |
| systemdlete | so maybe something I've mod in the past is biting me now | 21:07 |
| systemdlete | I can do a reset to find out for sure | 21:08 |
| systemdlete | I have learned a few interesting things here today, but I feel like this is starting to drag on our limited support resources. So I might just let this rest. | 21:08 |
| fsmithred | asz09, that output looks the same as mine. | 21:08 |
| asz09 | gnarface, it appears "asz09 cdrom floppy audio dip video plugdev users netdev bluetooth lpadmin scanner". I'm not sure what's happening either, but i'm convinced it might have something to do with the error message I posted. My display manager seems to be lightdm. Than you for the attention | 21:09 |
| fsmithred | I can't figure out how your problems are connected. | 21:09 |
| systemdlete | thanks for the help, all. | 21:10 |
| systemdlete | I'll be paying more attention to shell configs from now on. | 21:10 |
| fsmithred | systemdlete, my money is on you messede with something | 21:10 |
| fsmithred | messed | 21:10 |
| systemdlete | mine too | 21:10 |
| systemdlete | (well, let's hope that's all it is) | 21:10 |
| asz09 | fsmithred, it might be related to this? https://paste.debian.net/1322980 | 21:11 |
| fsmithred | asz09, try this in a terminal: /usr/sbin/xfpm-power-backlight-helper --get-brightness | 21:22 |
| asz09 | fsmithred, i got 6818 | 21:26 |
| fsmithred | ok, I was curious to see if you got an error message. I got 11 when I run it. | 21:26 |
| fsmithred | on an old thinkpad with the brightness turned down | 21:26 |
| fsmithred | is dbus-daemon running? | 21:27 |
| fsmithred | ps ax | grep dbus | 21:27 |
| asz09 | seems like it is https://paste.debian.net/1322981 . Using an old thinkpad too ;) haha | 21:29 |
| fsmithred | I'm really just guessing now. Maybe apply microsoft logic: aptitude reinstall <stuff> | 21:30 |
| fsmithred | maybe start with xfce4-power-manager | 21:31 |
| fsmithred | or the policykit stuff | 21:31 |
| asz09 | I tried it already, dont know what to do anymore. Just got this tho, from a troubleshoot: update-rc.d: error: initscript does not exist: /etc/init.d/polkit | 21:34 |
| gnarface | asz09: i'm guessing the audio problem is separate, and common, but there's so many of them | 21:36 |
| gnarface | first thing would be to try some simple tests, like "speaker-test -c 2 -t wav" | 21:37 |
| fsmithred | I don't have that init script, either | 21:37 |
| fsmithred | apt-file find init.d/polkit returns nothing. | 21:38 |
| fsmithred | what is looking for the non-existent file? | 21:39 |
| gnarface | frankly i've generally had abysmal luck with slim and usually the first thing i do is switch to something else like lightdm | 21:39 |
| fsmithred | ^^^ good suggestion | 21:40 |
| fsmithred | that init script doesn't exit on my beowulf, either | 21:40 |
| asz09 | Thank you so much guys.. I'll try to use another manager maybe. Hopefully its something related to Apparmor or something | 21:41 |
| gnarface | asz09: wait, are you using sysvinit, or did you pick a different one? | 21:41 |
| fsmithred | This comes up on a search for part of the error message. I don't know if it will help, but I've gotten good answers from ToZ before: https://forum.xfce.org/viewtopic.php?id=11190 | 21:42 |
| fsmithred | I think you can boot with apparmor=0 in the boot command to disable it | 21:43 |
| gnarface | asz09: also, just as a minor diversion, did you get anything from that speaker-test? | 21:44 |
| asz09 | Sysvinit. Speakers not working either! | 21:47 |
| gnarface | asz09: need more detail. does it throw an error, or does it say it's working but just not make sound? | 21:48 |
| asz09 | I will try to disable apparmor and some other stuff I configured. I will be back on after a reboot | 21:48 |
| asz09 | https://paste.debian.net/1322982 | 21:49 |
| fsmithred | aplay -l | 21:54 |
| gnarface | hmm, alsa errors are sometimes a bit obtuse, but "no such file or directory" generally actually means it can't support the format, which... for this format probably means that what it picked as the default soundcard isn't actually a soundcard | 22:05 |
| gnarface | (or if it is the driver isn't loaded, anyway) | 22:06 |
| gnarface | yea, i'd check "aplay -l" and "aplay -L" next | 22:06 |
| fsmithred | I'm starting to remember a problem where a bunch of modules didn't get loaded and it looked like devices were missing | 22:24 |
| gnarface | well, it could be loading and just badly broken too | 22:50 |
| gnarface | we have to do a bunch more tests to be sure | 22:50 |
| rrq | this line "ALSA lib confmisc.c:855:(parse_card) cannot find card '0' | 22:50 |
| rrq | somewhere in the config it declares "card" as a string "0" rather than a number 0 | 22:51 |
| rrq | most likely in ~/.asoundrc | 22:52 |
| rrq | (In system config only /usr/share/alsa/cards/Maestro3.conf stands out as a [unlikely] candidate problem source) | 23:03 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!