systemdlete | a/v problems on refracta beowulf VM, with all the latest updates applied. webcam led comes on when running cheese, but no video appears. For comparison, I tried this on an old ascii VM, and it works. | 08:18 |
---|---|---|
systemdlete | I cannot get the mic on the webcam to pick up sound; I tried testing the webcam at onlinemictest.com. | 08:19 |
systemdlete | Interestingly, this same webcam USED to work, and still seems to, on ascii VM, and I may have had it work on a regular devuan beowulf VM at some point, but idk now. | 08:20 |
systemdlete | I've gone into alsamixer (there is no pulseaudio on any system here, I made sure of that!) and set the mic select, made sure the mic gain was up, etc. I'm pretty sure it LOOKS like it is in order, but it doesn't work. | 08:21 |
systemdlete | Oh. New mainboard since it last worked, so that might be related. But I'd hope not. I checked the system logs and saw no sign of a problem. | 08:22 |
systemdlete | dang. I just noticed some errors after all... let me investigate. | 08:23 |
systemdlete | ah! that's it. | 08:23 |
systemdlete | https://bbs.archlinux.org/viewtopic.php?id=259134 | 08:24 |
systemdlete | Narrowing it down: The webcam works fine on the ascii host, but not in any of the VMs I've tried. Again, in the VMs, the led comes on when I fire up cheese. On the host, I'll see a video of me, but not when I run it in a guest. | 08:42 |
systemdlete | (and, no, I am not trying to run them at the same time on the host and guest!) | 08:42 |
systemdlete | Those error messages still appear in the messages log, but on the host, it doesn't seem to matter. cheese still works. | 08:43 |
xinomilo | f*cking great...: "wontfix" attitude established in debian for good... https://lists.debian.org/debian-ctte/2021/02/msg00008.html | 11:05 |
Wonka | xinomilo: well yeah, they've been removing sysvinit scripts left and right for some time now | 11:09 |
msiism | I've discovered a little problem with my Bash prompt since the upgrade to Beowulf. And that problem is that it will expand the tilde symbolizing $HOME as soon as you change directories. See https://paste.debian.net/plainh/849ab27e | 16:51 |
nemo | huh... WFM | 16:52 |
nemo | ${debian_chroot:+($debian_chroot)}\u@\h:\w\$ | 16:52 |
nemo | which is probably the default | 16:52 |
msiism | It even does that when I use `cd ~`. | 16:53 |
nemo | worked even when I copied your PS1 from your pastebin | 16:53 |
nemo | msiism: what version of bash? | 16:53 |
nemo | bash --version | 16:53 |
nemo | GNU bash, version 5.0.3(1)-release (x86_64-pc-linux-gnu) | 16:53 |
msiism | nemo: Yeah, I remember that. root's ~/.bashrc on this system has this and it doesn't have the problem. | 16:53 |
msiism | nemo: 5.0.3(1)-release | 16:53 |
nemo | so... something in your bashrc? | 16:54 |
msiism | nemo: Well, I deliberately set PS1 to \u@\h:\w\$ a while back and that worked just fine. | 16:54 |
msiism | Let me try the default. | 16:55 |
n4dir | i'd also grep for PS1 in home. Perhaps you got it somewhere else | 16:59 |
msiism | In home? | 16:59 |
n4dir | the hidden configs in hoe | 16:59 |
n4dir | damn: home | 16:59 |
msiism | Well, let me move my own ~/.bashrc out of the way for a second… | 16:59 |
n4dir | probably something like grep -r PS1 .[!.]* ; something like that | 17:00 |
msiism | Ha, it still occurs with my ~/.bashrc not being read at all. | 17:00 |
n4dir | took me ages to figure out Void didn't use .bashrc (or was it .profile)? Something like that i would check | 17:00 |
n4dir | what bash related is to be found in home, thats what i would investigate. Good luck, sounds shitty | 17:01 |
msiism | n4dir: You probably mean ~/.profile vs. ~/.bash_profile. | 17:01 |
msiism | But you can really choose which one to use. | 17:01 |
n4dir | yeah, such | 17:01 |
msiism | So, what do I do now… | 17:02 |
msiism | Well, maybe look into the system-wide configuration. | 17:02 |
n4dir | grep for PS1 won't hurt. But if everything which happened was an upgrade ... | 17:02 |
msiism | I'm not setting PS1 in ~/.profile, though. (And I don't use ~/.bash_profile. | 17:03 |
nemo | msiism: what about .bashrc ? | 17:30 |
msiism | I've moved my .bashrc out of the way already. Same result. | 17:30 |
msiism | And the things in /etc/ are all vanilla Debian configs because I upgraded by reinstalling. | 17:31 |
n4dir | well, if this is a new installation and you didn't copy configs around and there is no chance there is a weird config somewhere, then there is no need to grep for anything. I would do it to be sure to have that out of the way | 17:32 |
msiism | Let me try without reading ~/.profile, just to be sure. | 17:33 |
n4dir | i sure ran in it two or three times a config i didn't have in mind got in my way. | 17:33 |
n4dir | like usual: adduser testuser; see if he has the same problem | 17:34 |
n4dir | well; what i would do is probably: PS1=' $' and call it a day. :-) | 17:34 |
n4dir | aliases. Aliases to a lot of weird shit too | 17:36 |
n4dir | and obivously: ask in #bash or if one of the masters is around in #linux. What get's sourced when for bash is quite complex and confusing, as far it's me | 17:37 |
msiism | I don't have a lot of aliases. Just 15 of them. | 17:37 |
n4dir | not saying any of that is your problem, i doubt that. But i ran in what i said the last weeks with others. | 17:38 |
n4dir | as in: shooting obvious ideas | 17:38 |
msiism | For example: alias cls='clear' | 17:40 |
msiism | So, there's something that DOS did do better, after all. :) | 17:40 |
n4dir | i think we can agree that one is not the source of the problem :-) | 17:40 |
n4dir | if "testuser" has the same problem, it is in the systemwide settings or a bug or such. If he hasn't, it must be a config somewhere in ~ | 17:41 |
msiism | Probably not. | 17:41 |
msiism | Right. | 17:41 |
msiism | Let's see. | 17:41 |
msiism | Okay, primary user does not have the problem. 8| | 17:41 |
n4dir | Oh. So it should be a config or such in ~, right? | 17:42 |
msiism | Now this is funny. | 17:43 |
Guest64 | hey after a recent update it seems like wicd was removed, so my internet doesn't work | 17:46 |
Guest64 | i had issues resolving from deb.devuan.org | 17:46 |
gnarface | Guest64: which release? | 17:49 |
msiism | Hm… this doesn't seemt to be related to ~/.bashrc at all. I just copied the file from the other use that didn't have the problem and ran a session using it with my current user. Same result. | 17:49 |
n4dir | this will be time-consuming and not much fun. been there. | 17:50 |
Guest64 | ceres | 17:50 |
n4dir | anything unusual regarding the logging in? | 17:50 |
Guest64 | no | 17:50 |
n4dir | else i'd assume all related should be found with ls .bash* and ls .profile* | 17:51 |
gnarface | Guest64: packages disappearing temporarily from ceres is not very uncommon, i would just wait a day or two it'll probably come back | 17:51 |
Guest64 | hm | 17:51 |
n4dir | some come up with the idea to put stuff in .local | 17:51 |
Guest64 | i will check out .profile | 17:51 |
Guest64 | i use dash as my main shell | 17:52 |
msiism | Guest64: I think n4dir was talking to me. | 17:52 |
Guest64 | oh ok | 17:52 |
Guest64 | lol | 17:52 |
n4dir | Guest64: i was speaking to msiism . Sorry if i screwed it | 17:52 |
msiism | :) | 17:52 |
n4dir | big sorry | 17:52 |
gnarface | Guest64: i doubt that dash is your issue here, though, completely separately, i really don't recommend using it for a login shell | 17:53 |
Guest64 | why not? | 17:53 |
gnarface | Guest64: the description of your problem statistically is more likely to match a issue on the repo end you have no control over | 17:54 |
Guest64 | yeah i think it's probably a wicd issue bc w3m and dig don't work very well | 17:54 |
Guest64 | ok | 17:54 |
Guest64 | so i should just wait for the ceres repo to get sorted? | 17:54 |
gnarface | probably | 17:55 |
Guest64 | i should be able to change to a mirror then right? | 17:55 |
Guest64 | if there are any | 17:55 |
gnarface | deb.devuan.org should already be pointing to all the mirrors; it's a dns round-robin | 17:55 |
Guest64 | oh | 17:55 |
gnarface | if you just try again you'll get a different one | 17:55 |
Guest64 | i've tried a few times and the issue comes with resolving deb.devuan.org | 17:56 |
Guest64 | so i assume i'll have to bear without internet | 17:56 |
Guest64 | which isn't a big deal | 17:56 |
gnarface | well, if wicd got removed, it probably took your network with it, but you don't need wicd to get a network connection | 17:56 |
gnarface | you just need to reconfigure your network manually, or install one of the other gui network config tools | 17:57 |
Guest64 | ok | 17:57 |
onefang | Selecting a mirror manually from https://pkgmaster.devuan.org/mirror_list.txt might help. | 17:57 |
gnarface | the old wicd package you were using might still be in /var/cache/apt/ too | 17:57 |
gnarface | though it's a long shot | 17:58 |
Guest64 | onefang, that's what i thought initially but apparently deb.devuan.org will point to mirrors anyways | 17:58 |
onefang | deb.devuan.org only points to some of those mirrors. | 17:58 |
msiism | n4dir: I've created another new user. That user didn't have the problem. This is beginning to be strange. | 17:59 |
n4dir | msiism: i would ask in #bash. And be it only for the chance to get all the love of greycat | 18:00 |
msiism | n4dir: It's kind of a rule for me not to visit #bash, though. | 18:00 |
n4dir | nah. Well. You will get it sorted. The time consuming is the shitty part | 18:01 |
msiism | Yeah, I'll put the new findings in my notebook. Will poke at it again later. | 18:01 |
gnarface | msiism: it couldn't be expanding to match some other directory you forgot you left in /home/ or /etc/passwd, could it? | 18:07 |
msiism | gnarface: How do you mean, exactly? | 18:09 |
msiism | echo-ing $HOME gives the correct result. | 18:09 |
msiism | Oh, I get it. | 18:10 |
gnarface | msiism: i don't know how, exactly. but my suspicion is that if you actually look, it would be obvious if i'm right or not | 18:10 |
gnarface | unless you have like a thousand users or something... | 18:11 |
gnarface | usually i only have 1 | 18:11 |
msiism | Ohoh… | 18:11 |
msiism | Found it, I think. | 18:11 |
msiism | Yeah, welcome to Unix… | 18:11 |
msiism | gnarface: https://paste.debian.net/plainh/8b180b7d | 18:14 |
john2 | Upgraded to chimaera, xfce 4.16 seemed to be acting up a little bit. The regular application menu says it unexpectedly left the panel and when I press execute, the dialog box comes up again. (At least the whisker menu works though) On the Desktop certain icons like home, Trash and file system won't function normally but the file manager works | 18:14 |
msiism | There were some remnants from when I tested how solely numeric user names will break things on Unix-like systems. | 18:14 |
msiism | This is in /home | 18:15 |
gnarface | msiism: also check the contents of /etc/passwd - directories defined in there as home directories i think also get ~-expanded | 18:15 |
gnarface | (not all of them will be in /home, or even exist, necessarily) | 18:15 |
Guest64 | john2 do your desktop icons have parts of themselves cropped out? i'm on ceres and i just noticed this today | 18:16 |
gnarface | don't paste it in herw | 18:16 |
gnarface | here* | 18:16 |
john2 | I'm not sure about cropped out | 18:16 |
msiism | gnarface: Sure. I mean, those things should all have been wiped when I installed this system. I only left /home intact. | 18:16 |
john2 | they look normal they just don't function | 18:16 |
Guest64 | xfce might keep logs | 18:17 |
Guest64 | i know lxde did that | 18:17 |
john2 | I hear this may be a debian problem too | 18:17 |
msiism | gnarface: Okay, I had to fix two things in /etc/passwd as well. Thanks for the pointer. | 18:33 |
msiism | It works now. | 18:33 |
msiism | Makes me wonder, though, because I used adduser to create that user with no unusal parameters as far as I recall. | 18:34 |
gnarface | no problem | 18:36 |
gnarface | i could only speculate really | 18:37 |
gnarface | once you start to see large enough chunks of the pattern, you can just predict where the gaps will appear | 18:37 |
John2 | alright if by cut off you mean the dock icons, right click, click properties and adjust the size up | 18:37 |
John2 | I fixed my issue by manually updating xfce packages | 18:38 |
msiism | gnarface: :) | 18:38 |
Guest64 | John2 thanks, i fixed my issue with lxde by doing the same but i thought your packages were up-to-date, so i didn't mention that | 18:40 |
John2 | I thought it would've done it automatically with apt update and apt upgrade | 18:40 |
John2 | but I had to read which packages were kept back | 18:41 |
Guest4 | is there anything similar to udev in devuan? i'm trying to do manual wifi config for ethernet | 20:25 |
Guest4 | *network config | 20:25 |
john2 | whenever I try to start rc-service, bash says command not found | 20:27 |
john2 | im on openrc | 20:27 |
john2 | john2:i also tried /etc/init.d but that didn't seem to work either | 20:28 |
john2 | start-stop-daemon: not found | 20:45 |
mason | Guest4: eudev, but manual wifi config should be possible with just ifupdown. | 20:46 |
Guest4 | ok | 20:47 |
mason | Guest4: You'll want to make sure you have any necessary firmware packages. For instance, on my laptop I need firmware-iwlwifi. | 20:47 |
Guest4 | so lspci -v works right? | 20:47 |
mason | Guest4: And you'll want to make sure you have wpasupplicant. Not thinking there's much else that won't be pulled in automatically. | 20:48 |
mason | Guest4: Works on my T420. Shows me my wifi, and its loaded driver. | 20:48 |
Guest4 | alr | 20:48 |
gnarface | Guest4: have you read the release notes? make sure you're not running into the permission backend conflict with your login manager issue | 21:05 |
gnarface | Guest4: you shouldn't be missing udev functionality. it should be there, whether it's named udev, systemd-udevd, or eudev | 21:05 |
Guest4 | ok | 21:05 |
Guest4 | i wasn't sure bc devuan doesn't use systemd | 21:05 |
gnarface | Guest4: yea it doesn't, but some jerks renamed udev "systemd-udevd" anyway | 21:05 |
Guest4 | i didn't get an error was just reading the archwiki for help | 21:06 |
gnarface | Guest4: (the primary reason why it got a fork to eudev was just to rename it) | 21:06 |
gnarface | you'll still need wpasupplicant if you're using wireless | 21:08 |
gnarface | once started up, all this stuff should work the same on devuan as debian | 21:08 |
gnarface | some configs will just be in different places maybe for certain things... like if you're not using dhcp then i think you'll still need a /etc/resolv.conf or the resolvconf package | 21:10 |
gnarface | (systemd i think absorbed that config file on debian) | 21:10 |
gnarface | but anything that didn't get replaced should function more or less the same on devuan as it did before systemd in debian | 21:11 |
gnarface | - to the point that often just looking up old Wheezy documentation is sufficient where the devuan documentation is missing | 21:11 |
Guest4 | i believe i used dhcp the first time i installed but wicd is gone bc i was stupid | 21:12 |
Guest4 | i think i have a resolv.conf | 21:12 |
gnarface | a dhcp client will auto-generate a resolv.conf for you, so you won't have to mess with it. this is just in case you end up doing manual configuration | 21:14 |
gnarface | all things being equal, it's actually usually much easier to do a manual configuration once you know how to do it both ways | 21:14 |
Guest4 | alright | 21:19 |
Guest4 | thanks | 21:19 |
Generated by irclog2html.py 2.17.0 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!