No content displayed / no request is made

[husjon]

Hi

Using the latest obs-linuxbrowser-bin from AUR

╭─ husjon in ~ on (master)✘✘✘  
╰─(ﾉ˚Д˚)ﾉ  pikaur -Q obs-linuxbrowser-bin 
obs-linuxbrowser-bin 0.6.1-1

╭─ husjon in ~ on (master)✘✘✘  
╰─(ﾉ˚Д˚)ﾉ  pacman -Q obs-studio 
obs-studio 23.2.1-2

I'm not getting any content being displayed in the source.

Using the default settings of http://www.obsproject.com, I'm expecting to see the content from that page, however nothing is shown.

I've tried letting it fetch content from one of my own servers, but no request is made.

I've attached the log from OBS for reference.
OBS Log

If I've missed anything, please do let me know.

[1stian]

Having the exact same issue.... Tried to reinstall CEF minimal and even tried to use the standard one available, no luck.

[NexAdn]

My first guess would be, that this is another occurence of #63 which I thought had been fixed. Is there CEF still installed despite you using the binary release? Also, does the problem occur, if you build obs-linuxbrowser from source (or install obs-linuxbrowser from AUR)?

[1stian]

I've installed it with AUR. package name: obs-linuxbrowser-bin.
The package with only "obs-linuxbrowser" fails on make..(Error 1)

But i'll try from binary release as well.

[1stian]

My first guess would be, that this is another occurence of #63 which I thought had been fixed. Is there CEF still installed despite you using the binary release? Also, does the problem occur, if you build obs-linuxbrowser from source (or install obs-linuxbrowser from AUR)?

Hello, I am getting the same error by trying to build it from source...
https://pastebin.com/zNfYnJ8k

[NexAdn]

Okay, so building it from source doesn't work with latest CEF versions due to #108. I'll have to fix that first, before we can check if it's related to the binary release or CEF in general.

[1stian]

Okay, so building it from source doesn't work with latest CEF versions due to #108. I'll have to fix that first, before we can check if it's related to the binary release or CEF in general.

OKaay. the "obs-linuxbrowser-bin" is not working for me at all... Do you got any ETA for it? This is the only part I am missing from my OBS.. I've just switched from Windows to Linux(Manjaro)..

[NexAdn]

Well, it seems they have changed the api (and even the version numbering) heavily and I haven't had time to investigate what exactly they changed, but tomorrow I can start looking into this.

[1stian]

Well, it seems they have changed the api (and even the version numbering) heavily and I haven't had time to investigate what exactly they changed, but tomorrow I can start looking into this.

Okay, awesome! But what version do you recommend to use in the mean while then? If I can find an earlier version of CEF

[NexAdn]

Earlier versions of CEF can be found on the official binary release download page (see README). In the past, version 3359 worked well. You can also try using the binary release without having CEF installed separetely.

[AlexWayfer]

Wow, it's breaking all things bug.

Sadly to experience it.

I hope somebody will have a time for making obs-linuxbrowser working again.

[AlexWayfer]

Earlier versions of CEF can be found on the official binary release download page (see README). In the past, version 3359 worked well. You can also try using the binary release without having CEF installed separetely.

I confirm: the 68.0.3440.106 version of CEF, master version of obs-linuxbrowser and compiling by instructions in README on Arch Linux makes this plugin working. Thank you.

[AlexWayfer]

minimal builds work too.

75.0.1+gb5e74dd+chromium-75.0.3770.80 works too.

76.1.5+gd8a577c+chromium-76.0.3809.87 works.

Even the latest 64-bit 77.1.12+gc63c001+chromium-77.0.3865.90 works…

So, maybe the problem in the build?

[NexAdn]

There was a similar issue (#63) some time ago, causing only certain CEF builds to work with obs-linuxbrowser. To this day, however I have no clue why that might be, although it seemed to have been working for a while after merging #79. Apparently, this either was not the issue or there is some new issue with similar symptoms. Nonetheless, we most probably just have to keep track of the versions which are known to be working. I'll merge the fix-new-cef-api-108-110 branch as soon as I have time testing these CEF builds myself.