KLV-Airedale-rc3 with Void Linux Kernel is Available!

[Sofiya]

after reading the post viewtopic.php?p=75954#p75954 . @rockedge that you can log in as a user spot
I decide to do further research on pulseaudio-equalizer-ladspa
I leave the session and enter as a spot
I see that Pulseaudio did not start in the system tray
checking why: missing file "pulseaudio --start " /etc/xdg/autostart/
I create a launch file and exit the session and enter, pulseaudio started
next check the run output run-as-spot pulseaudio-equalizer enable
run passed the output in the terminal is correct
I go to applications> multimedia> Pulse Audio Equalizer I choose, I see that it is turned off, although the terminal output showed that it turned on
and I understand that it does not work.I take the source and compile my pulseaudio-equalizer-ladspa
I remove the installed one from the box. I see that it is removed along with swh-plugins
I had it saved at one time, I install my pulseaudio-equalizer-ladspa and the native swh-plugins plugin
I run it and voila everything works.

how to run it as root user
I see that they have 2 different ID 0 and 1001

launch browser as run-as-spot in root session, browser has no sound

spot session does not have a command to run .sh scripts in Thunar so the file start_pulseaudio does not start

[rockedge]

@Sofiya Excellent work! Very helpful since it's time to work on the getting user spot working correctly. I have noticed the pulseaudio autostart when logging in as user spot has not worked yet as it should.

We need to add the ability to click on XXX.sh scripts in Thunar to launch them and the /home/spot/Startup directory needs the same configuration as it is with the root user. @fredx181 set that up to work with /root/Startup

Then there is the Void Linux updates of xfce4......it has changed somethings that will need to be adjusted or configured again it appears at first looks.

Screenshot(11).jpg (59.78 KiB) Viewed 1396 times

First thing I noticed is some different wallpapers are included and a Rox launcher on the desktop needs the work directory set to open up in /root.

I have an rc4 ready to test if the team feels ready to look at it. Or run a system update/upgrade and see how it goes.
KLV-Airedale-rc4.iso

So far I have only run rc4 in a QEMU virtual machine.

[geo_c]

Then there is the Void Linux updates of xfce4......it has changed somethings that will need to be adjusted or configured again it appears at first looks.
Screenshot(11).jpg

It seems like the Void updates may be an ongoing issue once KLV is out as an official release. As far as I can tell there's just no knowing what it's going to do ahead of time.

Just looking out for you and your workload.

As with any updates I suppose it's an "update at your own risk" kind of situation.

[rockedge]

@geo_c Good thing is so far KLV is continuing to operate well and only the difference in Rox opening up /root/desktop unless specified differently because Rox-filer is supposed to do that.

Also to this point all of the updates I have done on running systems seem to not have had any negative impact. More testing to find the subtle differences is needed.

I think we can try to start pulseaudio as a global system service so all users can connect to it. But it might be better to stay as is, and make the adjustments needed to auto start a pulseaudio instance for the user logging in. Goal is to get the /home/spot/Startup directory functioning to make it more convenient to manage auto starting custom scripts and daemons on this per user basis.

[geo_c]

@geo_c Good thing is so far KLV is continuing to operate well and only the difference in Rox opening up /root/desktop unless specified differently because Rox-filer is supposed to do that.

Also to this point all of the updates I have done on running systems seem to not have had any negative impact. More testing to find the subtle differences is needed.

I think we can try to start pulseaudio as a global system service so all users can connect to it. But it might be better to stay as is, and make the adjustments needed to auto start a pulseaudio instance for the user logging in. Goal is to get the /home/spot/Startup directory functioning to make it more convenient to manage auto starting custom scripts and daemons on this per user basis.

Right, I was planning to edit my comment and add that so far updates are mostly minor Xfce annoyances. I haven't any problems except when python updated awhile back and killed frescobaldi. But that's mostly due to that package's limitations and the fact that it wasn't installed from the void repo or recompiled in the updated system.

My browsers that run as root all work with pulse audio, but I can confirm that the portables I've used that run as spot don't have working audio. I don't tend to run things as spot on my own. But I've thought about learning how to use it more effectively. Up to this point I've viewed it as an extra layer of complication, but in the future I plan to get a better handle on the multi-user capability of KLV.

[rockedge]

@geo_c While looking over @Sofiya 's work on getting the pulseaudio equalizer working and I found that there was a depreciated command in the launch .desktop file that starts pulseaudio in /etc/xdg/autostart. I fixed that and now it looks like the pulseaudio start up is finally working as expected. That will be in rc4 and can be fixed now in rc3 by:

open /etc/xdg/autostart/pulseaudio.desktop and change the Exec line to:

Code: Select all

Exec=pulseaudio --start

I am repacking KLV-Airedale-rc4 with this change (fix) included and will upload it with in the next 20 minutes

[rockedge]

it also appears that /root/Startup/start_pulseaudio script can be deleted from the system.

I have to actually test rc4 on a system that has audio capabilities next to see if the browsers make sounds.

[Sofiya]

open /etc/xdg/autostart/pulseaudio.desktop and change the Exec line to:

Code: Select all

Exec=pulseaudio --start

I am repacking KLV-Airedale-rc4 with this change (fix) included and will upload it with in the next 20 minutes

in file pulseaudio start.desktop I have in the xbps package Exec=pulseaudio --start

and /pulseaudio.desktop is not mine

[rockedge]

I have uploaded the adjusted rc4!

@Sofiya I will add these 2 packages to the small KLV repo I have that will be used by the PLUG file and build scripts to construct KLV's from scratch. All of the customization of the FirstRib build into a KLV will be .xbps packages that the recipe PLUG can download and install to perform the customization.

Also anyone working with an older version can use them to add the features.

[rockedge]

I am testing rc4 on a DELL Inspiron 15 laptop and Firefox audio (YouTube) works both in user root and spot and I am assuming as weedog.

Except now the xfce4 wall paper is default but we can change that again

UPDATE: audio works with both users root and spot.

[Sofiya]

I run yandex-browser-beta --no-sandbox -- there is a sound in root
and run-as-spot yandex-browser-beta --- no sound in root
and yandex-browser-beta --no-sandbox --- there is a sound spot

Code: Select all

┌──[ root@void-live ] [  22:18:26 ]
├── ~
└>yandex-browser-beta
Found ffmpeg: /opt/yandex/browser-beta/libffmpeg.so
	avcodec: 3873892
	avformat: 3872868
	avutil: 3741797
Ffmpeg version is OK! Let's use it.
[4086:4086:1219/221829.745179:ERROR:zygote_host_impl_linux.cc(90)] Running as root without --no-sandbox is not supported. See https://crbug.com/638180.
┌──[ root@void-live ] [  22:18:29 ]
├── ~
└>

chrome browser also requires --no-sandbox

[wiak]

@Sofiya, regarding pulseaudio-equalizer use when logged in to desktop as user root. You do need to run the application pulseaudio-equalizer-gtk as normal user such as spot, but there are a few tricks to get sound to work correctly as spot (from root desktop) and what I think is a pulseaudio misconfiguration currently in provided KLV-airedale (runit should not enable pulseaudio service). See here for my own successful test:

viewtopic.php?p=76072#p76072

Note that I started with pristine KLV-airedale install since easy otherwise to mess things up...

[rockedge]

@wiak I adjusted rc4 by removing the pulseaudio service symlink. Tested and the audio seemed to work.

The repackaged version KLV-Airedale-rc4 has been uploaded and is ready for testing that includes the fix.

[Clarity]

The pristine boot yields some interesting messages shown in DMESG. Enclosed

Code: Select all

[    0.000000] Linux version 6.0.12_1 (voidlinux@voidlinux) (gcc (GCC) 10.2.1 20201203, GNU ld (GNU Binutils) 2.35.1) #1 SMP PREEMPT_DYNAMIC Sun Dec 11 13:34:32 UTC 2022
[    0.000000] Command line: BOOT_IMAGE=/vmlinuz w_bootfrom=/boot-isos/KLV-Airedale-rc3.iso net.ifnames=0 w_changes=LABEL=Persistence=/Sessions w_changes=RAM1 w_copy2ram
[    0.000000] x86/fpu: x87 FPU will use FXSAVE
[    0.000000] signal: max sigframe size: 1440
	o
	o
[   20.827169] input: HDA NVidia HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input9
[   20.827195] input: HDA NVidia HDMI/DP,pcm=7 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input10
[   20.827217] input: HDA NVidia HDMI/DP,pcm=8 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input11
[   20.827240] input: HDA NVidia HDMI/DP,pcm=9 as /devices/pci0000:00/0000:00:03.0/0000:01:00.1/sound/card1/input12
	o
	o
[    0.046755] Policy zone: Normal
[    0.046756] Kernel command line: BOOT_IMAGE=/vmlinuz w_bootfrom=/boot-isos/KLV-Airedale-rc3.iso net.ifnames=0 w_changes=LABEL=Persistence=/Sessions w_changes=RAM1 w_copy2ram
[    0.046900] Unknown kernel command line parameters "w_copy2ram BOOT_IMAGE=/vmlinuz w_bootfrom=/boot-isos/KLV-Airedale-rc3.iso w_changes=RAM1", will be passed to user space.
	o
	o
[   21.081892] kvm: VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL does not work properly. Using workaround
[   21.190284] firewire_core 0000:03:00.0: created device fw0: GUID 0025648000e4408f, S400
[   21.219340] nouveau 0000:01:00.0: vgaarb: deactivate vga console
[   21.220403] Console: switching to colour dummy device 80x25
[   21.220542] nouveau 0000:01:00.0: NVIDIA GT218 (0a8280a2)
[   21.340587] nouveau 0000:01:00.0: bios: version 70.18.36.00.00
[   21.340864] nouveau 0000:01:00.0: bios: OOB 1 d7500086 d7500086
[   21.341144] nouveau 0000:01:00.0: fb: 512 MiB DDR2
[   21.910564] nouveau 0000:01:00.0: DRM: VRAM: 512 MiB
[   21.910569] nouveau 0000:01:00.0: DRM: GART: 1048576 MiB
[   21.910572] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[   21.910574] nouveau 0000:01:00.0: DRM: DCB version 4.0
[   21.910575] nouveau 0000:01:00.0: DRM: DCB outp 00: 01000302 00020030
[   21.910577] nouveau 0000:01:00.0: DRM: DCB outp 01: 02000300 00000000
[   21.910579] nouveau 0000:01:00.0: DRM: DCB outp 03: 02011362 00020010
[   21.910581] nouveau 0000:01:00.0: DRM: DCB outp 04: 01022310 00000000
[   21.910583] nouveau 0000:01:00.0: DRM: DCB conn 00: 00001030
[   21.910584] nouveau 0000:01:00.0: DRM: DCB conn 01: 00202161
[   21.910585] nouveau 0000:01:00.0: DRM: DCB conn 02: 00000200
[   21.913011] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer copies
[   21.955612] nouveau 0000:01:00.0: DRM: allocated 1600x1200 fb: 0x70000, bo 000000000449acbe
[   21.955769] fbcon: nouveaudrmfb (fb0) is primary device
[   21.994491] Console: switching to colour frame buffer device 200x75
[   21.996554] nouveau 0000:01:00.0: [drm] fb0: nouveaudrmfb frame buffer device
[   22.002910] [drm] Initialized nouveau 1.3.1 20120801 for 0000:01:00.0 on minor 0

@rockedge, notice the KVM line in the log. Not sure if it is a result of kvm hardware unit attached to the PC or if it is a result of the KVM load module for the CPU in the kernel.

[wiak]

@rockedge, notice the KVM line in the log. Not sure if it is a result of kvm hardware unit attached to the PC or if it is a result of the KVM load module for the CPU in the kernel.

Apparently not important. See foot of this page: https://bugzilla.redhat.com/show_bug.cgi?id=808806#c4
Whether it is or not, I'd have no clue. It is also noted here, and I've seen it in other dmesg reports with no one saying anything bad about it. https://bbs.archlinux.org/viewtopic.php?id=203840
Fixing such an error would be above our pay-grades I imagine, unless a documented fix or need for one is found by someone.

[Clarity]

Thanks @wiak
It was mentioned as I remembered that @rockedge added KVM to the kernel build.

Moving on from RC3 to testing RC4

[wiak]

@wiak I adjusted rc4 by removing the pulseaudio service symlink. Tested and the audio seemed to work.

The repackaged version KLV-Airedale-rc4 has been uploaded and is ready for testing that includes the fix.

Did you remember to add users spot and weedog to the pulse-access group? For example:

Code: Select all

usermod -a -G pulse-access spot

That seemed to be required for it all to work. I didn't know that previously but read it in some wiki or other (can't remember if in Arch wiki or Void docs). Of course maybe all works without that, but then again maybe not (I haven't tested the combinations - just reported what worked for me).

[rockedge]

usermod -a -G pulse-access spot

I forgot in the excitement to add the users! I will take care of that and upload a replacement rc4

I have not tested the equalizer installation process yet.....

[dancytron]

@wiak I adjusted rc4 by removing the pulseaudio service symlink. Tested and the audio seemed to work.

The repackaged version KLV-Airedale-rc4 has been uploaded and is ready for testing that includes the fix.

Did you remember to add users spot and weedog to the pulse-access group? For example:

Code: Select all

usermod -a -G pulse-access spot

That seemed to be required for it all to work. I didn't know that previously but read it in some wiki or other (can't remember if in Arch wiki or Void docs). Of course maybe all works without that, but then again maybe not (I haven't tested the combinations - just reported what worked for me).

I don't know if it helps, but I documented the way I set up the users and groups for pulseaudio in Debian Dog and got it to work as the "system" user, which seems to me to be an intended configuration for running as root. I made a sample iso...

viewtopic.php?p=52790#p52790

[rockedge]

My Internet connection is out and while waiting for the technician to come get back online, I found I needed to try a USB tether to a mobile phone.

Worked right away. I enabled usb tethering on the phone and plugged in the usb cable to the blade server. I booted into KLV-Airedale-rc4 and Networkmanager found the device immediately and chose it. I started Firefox and the connection to the Internet was working.

Connecting to the tethered hotspot was very easy and works rather nicely and will fill in enough while I wait for my Internet service provider to fix their mistake.

[wiak]

I don't know if it helps, but I documented the way I set up the users and groups for pulseaudio in Debian Dog and got it to work as the "system" user, which seems to me to be an intended configuration for running as root. I made a sample iso...

viewtopic.php?p=52790#p52790

Yes, worth studying how you did that for systemd, Dancytron. I note your method also assigned users to group pulse-access, which is what I've requested rockedge to arrange though I wasn't sure if necessary to make it all work or not. I actually don't know much myself about using pulseaudio - just googled and read freedesktop comment:

https://www.freedesktop.org/wiki/Softwa ... ystemWide/

All users that need access to PulseAudio have to be in the pulse-access group, even root.

My quick 'make it work' thereafter was simply to sudo to user spot and start a pulseaudio daemon to simply see if would work, but final best way to configure for systemwide already set up and working I wouldn't myself know about so perhaps converting your systemd service file to runit may or may not indeed provide better final working configuration with Void (the issue is to do with XDG already provided Void Linux mechanisms - see below for details). Definitely warrants further work for final KLV release anyway.

In my simple test I used, but modified, command suggested in Void docs and also noted their comment:

https://docs.voidlinux.org/config/media/pulseaudio.html

The PulseAudio package comes with a service file, which is not necessary in most setups - the PulseAudio maintainers discourage using a system-wide setup. Instead, PulseAudio will automatically start when needed. If it is not starting automatically, it can be started manually by invoking pulseaudio(1) from the terminal as follows:
$ pulseaudio --daemonize=no --exit-idle-time=-1

So you can see that in my simple usage test that is all I did, though I actually used --daemonize=yes, simply because I wanted to background the task whilst I typed other commands into the terminal. I expect main approach should be, as in your systemd service file, to use --daemonize=no, though I don't know if it matters or not.

NOTE WELL: that main purpose of my own simple (manual) test was not to see if logging in to desktop as user spot correctly used pulseaudio, but rather to see if pulseaudio-equalizer (which requires working pulseaudio of course) could be used by someone who has autologged in as root user. My hope is the autologging in as, say, spot user, will now work correctly without any further manual commands via the /etc/xdg/autostart mechanism Void Linux provides by default (which runit service seemed, to me, to conflict with), but I can't remember if I've tested that yet so needs checked thoroughly and pulse config files may or may not need further work in the end.

However, in investigating the way Void Linux installs and pre-configures PulseAudio I noted that they use /etc/xdg/autostart to do the actual service starting, and that rockedge was previously also using a runit service to start a daemon. The result seemed to me that there ended up being TWO pulseaudio daemons running and in such a way that if you became non-root user things were messed up and didn't work. My test remedy was to disable the runit service rather than interfere with Void Linux official configuration that, as I say, seems to rely instead on XDG system to start up that particular daemon. Definitely more investigation required. However, if my suggestion of simply disabling the runit service rockedge had previously activated works when also logging into normal user spot (I have to do quick test to see if that is true - i.e. if XDG does in fact start up daemon that works out of the box Void Linux config way for normal users) then best not to try also to use runit to start additional system-wide daemon but rather rely on that XDG-oriented mechanism provided by default Void. So more testing required to decide if all now already well or if runit service mechanism needs to be re-considered (which may be complicated by having to make sure then there is no conflict between that method and xdg doing it).

I definitely am not myself suggesting the matter is solved. It might be, but needs further thought and a lot more testing, in addition to the manual commands way I myself demonstrated a working method, so thanks for your systemd service file approach since that will in any case help determine what the appropriate pulse configuration files should include (assuming defaults end up needing changed).

[wiak]

By the way, I forgot to mention in my immediately above post that Void Linux, instead of using a runit service, instead seems to auto-start pulseaudio via the file /etc/xdg/autostart/pulseaudio.desktop

If you look inside that desktop file you will see that it runs a special configuration shell script called start-pulseaudio-x11

Not on KLV at the moment so can't remember if I found that in /usr/bin or not (probably), but just run command:

Code: Select all

which start-pulseaudio-x11

and you can thereafter use less or geany to examine its details, which is what I briefly did yesterday.

EDIT: Just booted into KLV now, and did a Logout from root desktop and then re-logged in as user spot (pw: spot), started firefox and visited youtube and audio was working fine. I probably did try the same yesterday. Pullseaudio thus seems to be working fine for normal users (via that official Void /etc/xdg/autostart mechanism) so I'd suggest just leaving that as it is for now unless issues come up or better configuration is determined during later tests.

[Sofiya]

By the way, I forgot to mention in my immediately above post that Void Linux, instead of using a runit service, instead seems to auto-start pulseaudio via the file /etc/xdg/autostart/pulseaudio.desktop

If you look inside that desktop file you will see that it runs a special configuration shell script called start-pulseaudio-x11

Not on KLV at the moment so can't remember if I found that in /usr/bin or not (probably), but just run command:

Code: Select all

which start-pulseaudio-x11

and you can thereafter use less or geany to examine its details, which is what I briefly did yesterday.

@rockedge He changed him to Exec=pulseaudio --start

[wiak]

By the way, I forgot to mention in my immediately above post that Void Linux, instead of using a runit service, instead seems to auto-start pulseaudio via the file /etc/xdg/autostart/pulseaudio.desktop

If you look inside that desktop file you will see that it runs a special configuration shell script called start-pulseaudio-x11

Not on KLV at the moment so can't remember if I found that in /usr/bin or not (probably), but just run command:

Code: Select all

which start-pulseaudio-x11

and you can thereafter use less or geany to examine its details, which is what I briefly did yesterday.

@rockedge He changed him to Exec=pulseaudio --start

Sorry, I don't understand what you mean here Sofiya. Who changed what to "Exec=pulseaudio --start"?

I haven't downloaded RC4 yet, but on my system /etc/xdg/autostart/pulseaudio.desktop continues to use Exec=start-purlseaudio-x11, and that works for me. I suggest leaving that alone since official Void installed mechanism.

[Sofiya]

Sorry, I don't understand what you mean here Sofiya. Who changed what to "Exec=pulseaudio --start"?

I haven't downloaded RC4 yet, but on my system /etc/xdg/autostart/pulseaudio.desktop continues to use Exec=start-purlseaudio-x11, and that works for me. I suggest leaving that alone since official Void installed mechanism.

changed in Re: KLV-Airedale-rc4 on Exec=pulseaudio --start

He will not start Exec=start-pulseaudio-x11
He used to be started with /root/Startup/start-pulseaudio on KLV-Эрдельтерьер-rc3

[rockedge]

@wiak for some reason using Exec=start-pulseaudio-x11 in the /etc/xdg/autostart/pulseaudio.desktop will only start the audio for the root user but needs to be started manually if logged in as any other user. When I switch to Exec=pulseaudio --start all the users have a pulseaudio instance that starts at login.

So right now the /etc/xdg/autostart/pulseaudio.desktop looks like this :

Code: Select all

[Desktop Entry]
Version=1.0
Name=PulseAudio Sound System
Comment=Start the PulseAudio Sound System
Exec=pulseaudio --start
Terminal=false
Type=Application
X-GNOME-Autostart-Phase=Initialization
X-GNOME-HiddenUnderSystemd=true
X-KDE-autostart-phase=1

[wiak]

Sorry, I don't understand what you mean here Sofiya. Who changed what to "Exec=pulseaudio --start"?

I haven't downloaded RC4 yet, but on my system /etc/xdg/autostart/pulseaudio.desktop continues to use Exec=start-purlseaudio-x11, and that works for me. I suggest leaving that alone since official Void installed mechanism.

changed in Re: KLV-Airedale-rc4 on Exec=pulseaudio --start

He will not start Exec=start-pulseaudio-x11
He used to be started with /root/Startup/start-pulseaudio on KLV-Эрдельтерьер-rc3

Ah, yes, yesterday at some stage I removed that /root/Startup/start-pulseaudio file. I can't remember if it remains needed for pulseaudio to work for special case of using audio when root user. I still have that /root/Startup/start-pulseaudio file on my current system, but that may be wrong. Rather, instead it may be correct to delete that old Startup/start-pulseaudio method and instead just leave Void's /etc/xdg/autostart/pulse-audio.desktop, which calls up start-pulseaudio--x11 as the only start pulse mechanism. According to the freedesktop pulseaudio page, root user may also need to be added to the pulse-access group via command:

Code: Select all

usermod -a -G pulse-access root

I haven't test that and am just going out just now so maybe someone else could test and confirm. i.e. try deleting /root/Startup/start-pulseaudio and add root user to pulse-access group and then reboot and see if audio works for root in firefox as well as then re-logging in as user spot to double-check sound is also working for spot in firefox.

[wiak]

@wiak for some reason using start-pulseaudio-x11 in the /etc/xdg/autostart/pulseaudio.desktop will only start the audio for the root user but needs to be started manually if logged in as any other user. When I switch to Exec=pulseaudio --start all the users have a pulseaudio instance that starts at login.

So right now the /etc/xdg/autostart/pulseaudio.desktop looks like this :

Code: Select all

[Desktop Entry]
Version=1.0
Name=PulseAudio Sound System
Comment=Start the PulseAudio Sound System
Exec=pulseaudio --start
Terminal=false
Type=Application
X-GNOME-Autostart-Phase=Initialization
X-GNOME-HiddenUnderSystemd=true
X-KDE-autostart-phase=1

Oh I see. That needs to be investigated further. I don't like messing about with official Void Linux scripts if that is what you have found needed thus far? I don't myself know, but I am assuming start-pulseaudio-x11 was the official Void Linux provided mechanism on installing pulse audio? As I say above, there is also the issue of /root/Startup/start-pulseaudio to be further investigated - my gut feeling is we shouldn't start up pulse by alternative to official mechanisms at all, but of course, getting it all to work is a priority since sometimes such hacks are necessary...

Oddly, on my system, which still has Exec=start-pulseaudio-x11, audio worked fine via firefox using youtube when auto-logged in as user spot, so more investigation definitely required.

[rockedge]

@wiak Yes I think we can delete the /root/Startup/start_pulseaudio script.

Perhaps if the root, spot and weedog user are in the audio group then we can return to using Exec=start-pulseaudio-x11 in the /etc/xdg/autostart/pulseaudio.desktop and also eliminate the pulseaudio --start

It's really the first time fully focusing on this part of the configuration but looks like we are close to the correct setup. I also agree we should stay as close as possible to upstream official Void configurations so the system updates remain smooth in operation.

[wiak]

Oddly, on my system, which still has Exec=start-pulseaudio-x11, audio worked fine via firefox using youtube when auto-logged in as user spot, so more investigation definitely required.

In case you missed by above post that crossed over with your own posting.