Finish talk-recording geckodriver install or use chromium

[szaimen]

Things that should be done after #2645 is finished

• needs adjust talk-recoding build to get the files from its repo (latest with 28) #3570
• test if using the internal signaling IP also works does not work
• try if chromium works after Chromium recording spreed#9174. If not, see below (should be available with 28) not recommended

geckodriver:

• wait for https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/56841 being merged
  • then change the apk add repository edge/testing to apk add repository edge/community talk-recording - pull geckodriver from community #3907
• wait for alpine v3.xx.1 docker image release (maybe v3.20.1?)
  • update talk image to v3.xx.1
  • then move geckodriver to normal apk add line and remove apk add repository edge/community line

[Zoey2936]

can I improve it a bit?

[szaimen]

Of course :)

[szaimen]

btw, I would wait with the request to move it out of testing until we actually confirmed that it works ...

[szaimen]

Possibly we could alternatively as soon as chromium support comes with nextcloud/spreed#9174 switch to that...

[Zoey2936]

are there differences between chromium and firefox?

[szaimen]

are there differences between chromium and firefox?

I don't know honestly... Possibly RAM and CPU usage could be different...

[szaimen]

Apparently the logs are unrelated. The recording worked nonetheless. But it was not automatically shared into the conversation, I only got a notification.

[szaimen]

• test if using the internal signaling IP also works

Does not work

[Zoey2936]

Apparently the logs are unrelated. The recording worked nonetheless. But it was not automatically shared into the conversation, I only got a notification.

so it works?

[szaimen]

so it works?

yes :)

[Zoey2936]

do you now create the issue on the aports??

[szaimen]

do you now create the issue on the aports??

Ah yes, almost forgot

[szaimen]

https://gitlab.alpinelinux.org/alpine/aports/-/issues/14997

[Zoey2936]

The issue was closed...
So what do you to do now?
do you want to switch to chrome then or should I ask if I can take over the maintance of geckodriver?

[szaimen]

The issue was closed...
So what do you to do now?
do you want to switch to chrome then or should I ask if I can take over the maintance of geckodriver?

I would say lets wait for nextcloud/spreed#9174 to be merged and released. Then update the container to use chromium. If this works, I would say maintaining upstream geckodriver is not needed. If we cannot make it work with chromium then we can think about further steps. And thanks for the huge offer to take over the maintance of geckodriver btw! :)

[szaimen]

It seem there are some blockers for using chromium: nextcloud/spreed#9177 (comment)

[jospoortvliet]

It seem there are some blockers for using chromium: nextcloud/spreed#9177 (comment)

it's now merged ;-)

[nickvergessen]

While chromium recording is there, it is not the recommended solution

[szaimen]

While chromium recording is there, it is not the recommended solution

I see. In that case, @Zoey2936, you offered a few comments above that you could take over the maintainership of the geckodriver package in alpine aports. Is that still the case?

[Zoey2936]

yes

[Zoey2936]

I've created https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/56841

[Zoey2936]

@szaimen can you please change the apk add line?

[szaimen]

@szaimen can you please change the apk add line?

Will it be already available now or do we need to wait e.g. for Alpine 3.19.1?

[Zoey2936]

I think 3.20.0

[szaimen]

I think 3.20.0

Okay, then I'd say lets wait for that

[Zoey2936]

Yes but it moved from testing to community, so this needs to be changed in the apk add line

[szaimen]

Yes but it moved from testing to community, so this needs to be changed in the apk add line

Okay, so we can already change that now or do we still need to wait for 3.19.1 for this to become available?

[Zoey2936]

We still need to pull it from edge, but from the community branch now