Not working - manjaro 6.3.5 #26
Comments
|
Can you check what's on |
|
|
That's literally the same error I get when I first ran the script but didn't restart. I'd say restart your PC but I assume you've done that already lol Give me a day or two so I can install Manjaro to my XPS 13 Plus and see what's what |
|
@naps62 Out of topic: how did you install Manjaro to your laptop? I used dd to copy Manjaro ISO to my flash drive as directed by Manjaro Wiki but it's not showing up on my UEFI boot options :/ |
|
@striczkof i used to have similar issues. Nowadays I have a usb stick with Ventoy installed (https://www.ventoy.net/en/index.html) It makes it so you can just copy iso files into it, and it handles all the boot complexities (and gives you a menu, so you can keep multiple distros ready to boot) And yes, I did restart :) |
|
@naps62 so ye I just gave up and used ventoy because idk why ISO won't work with cp nor dd. Funny thing now though, my webcam is working after installing and restarting, no tinkering done other than install git and linux61-header (using linux61 since it came with manjaro fresh install) so now I am totally clueless what happened to both @hinricht 's (#21 ) and your setup. Edit: works on I'm wondering, are you using 12th gen or 13th gen XPS 13 Plus? Highly doubt that should matter but dunno My environment:
Working on Firefox and Discord after restart install.shtest.sh (before restart)test.sh (after restart)ffmpeg -f v4l2 -framerate 25 -video_size 640x480 -i /dev/video0 -t 5 output.mkvv4l2-ctl --list-devicessystemctl status v4l2-relayd.service |
|
@striczkof I just realized I failed to mention a probably important detail. I'm also using hyprland as wm instead of sway, although I tested booting with sway again with the same result |
|
Same for me, I'm also using manajro-sway with Wayland (Kernel 6.3.5-2-MANJARO). Manjaro-sway is a rolling release so I don't have any version number for it. |
|
Never used a tiling DE before, give me a bit lol But this installer works on my GNOME and KDE Wayland DEs so wayland part should be irrelevant |
|
So uh, @hinricht think I might need more details from you lol like the full install logs even if it is successful (don't forget to run uninstall.sh, delete, then clone the repo again) since i manage to get test.sh working. Also do you happen to have your webcam enabled in your BIOS? Funny thing now though, I am experiencing exactly the same problem as @naps62 with Firefox not detecting my camera and v4l2-relayd showing "gst_element_set_state: assertion 'GST_IS_ELEMENT (element)' failed" Might be missing some plugins or so that somehow present on most Arch installation but not for manjaro-sway. Doing some more testing. |
|
YOOO @naps62 I managed to fix it! Thanks to @stefanpartheym post in https://bbs.archlinux.org/viewtopic.php?id=277462&p=3 (hey if you see this can you merge our PRs xd)
Confirmed working on Discord and Firefox with --workaround. The kernel is |
|
@striczkof 🎊 🎊 🎊
webcam tested on Chrome / Slack / Discord / Firefox. this next part is offtopic, but other people may end up here through google: my last hanging fruit was the microphone, which also worked on Ubuntu, but only recorded white noise in Arch.
|
|
Great! That means one fewer dependency to install. Updated the PR already. I guess conversion might affect the latency a bit? The only way to find out is to compare them quality-wise really. Remove it if you don't need the work around I guess. It now works without the workaround for Firefox 115 so it's not even needed for that. Problem is my Discord clients (Regular, Arch Electron, and Canary) are still not working without the workaround. @naps62 what client are you using? |
|
I use he regular one, just with this config change (but I'm pretty sure it's irrelevant for this)
|
Not working on both Arch and Manjaro and with and without options :( |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
kernel:
6.3.5-2-MANJAROlaptop:
Dell XPS 13 PlusAfter going through the setup in this repo, the
test.shscript works, but everything else seems to fail (chrome, firefox, obs).This is both before and after trying the
--workaroundv4l2 shows me the devices:
and ffmpeg:
The text was updated successfully, but these errors were encountered: