Jump to content


Photo

Strange web UI problems

web ui bug

  • Please log in to reply
5 replies to this topic

#1 mueslo OFFLINE  

mueslo

    Advanced Member

  • Members
  • 43 posts
  • Local time: 09:54 AM

Posted 19 June 2018 - 05:27 AM

So this strange interface bug just started appearing for me. My set-up is a bit convoluted, but essentially I'm running Emby in a FreeBSD jail on FreeNAS, which itself is virtualised on a Proxmox VM host with PCI passthrough of a HBA for HDDs. Yesterday I replaced my HBA with a different one and upgraded Proxmox from version 3.4 to 5.2. Everything and all my numerous other containers and VMs have been running smoothly with absolutely no issues since upgrading. Except Emby.

 

The video playback interface is obviously missing abunch of stuff. Full screen button, subtitle selection, quality selection, artwork, etc. The progress bar and FF buttons are broken too. Volume control and pause work, but have some other bugs. And then when returning to the main menu via the back button (which usually also has the logo of the media, but not anymore), the playing video stays in the background.

Video example: https://webm.xyz/web...91325000fb413a6

 

Since everything else is working fine I don't think there's a problem with my set-up, rather I think maybe Emby got shutdown uncleanly prior to upgrading which triggered these errors?

 

I've ascertained that it's not due to an incorrectly set up reverse proxy, as this also happens locally when directly connecting to Emby. When using my reverse proxy, web socket connections don't work, but locally they do. This happens both with Chromium and Firefox.

 

The Emby server logs show no errors (except the ones regarding TLS1.2 and Github).

 

The Javascript console in the Browser shows a few errors on the main page already:

Edit: this one is actually due to adblock
Loading failed for the <script> with source “http://<localname>/web/bower_components/emby-webcomponents/fullscreen/fullscreen-doubleclick.js?v=3.4.1.0”. index.html:1
RequireJS error: Error: Load failed: bower_components/emby-webcomponents/fullscreen/fullscreen-doubleclick: http://<localname>/web/bower_components/emby-webcomponents/fullscreen/fullscreen-doubleclick.js?v=3.4.1.0. Failed modules: site.js:1:10677
Error: Load failed: bower_components/emby-webcomponents/fullscreen/fullscreen-doubleclick: http://<localname>/web/bower_components/emby-webcomponents/fullscreen/fullscreen-doubleclick.js?v=3.4.1.0 alameda.js:1:10040

I can manually call the above resource URLs and I get javascript returned, so the endpoints are working. Edit: see above, this error is caused by adblock, it is unrelated to the problem though. I'm guessing it gets blocked because it has 'doubleclick' in the name though, so you should consider renaming it ;)

 

The following error additionally occurs when starting a video:

TypeError: newValue is null[Learn More] index.html:32:21

Any ideas?

VM126:32 Uncaught (in promise) TypeError: Cannot read property 'data' of null
    at Object.set (<anonymous>:32:88)
    at hideMediaControls (mediasession.js?v=3.4.1.0:1)
    at updatePlayerState (mediasession.js?v=3.4.1.0:1)
    at bindToPlayer (mediasession.js?v=3.4.1.0:1)
    at PlaybackManager.<anonymous> (mediasession.js?v=3.4.1.0:1)
    at events.js?v=3.4.1.0:1
    at Array.forEach (<anonymous>)
    at Object.trigger (events.js?v=3.4.1.0:1)
    at triggerPlayerChange (playbackmanager.js?v=3.4.1.0:1)
    at setCurrentPlayerInternal (playbackmanager.js?v=3.4.1.0:1)
set @ VM126:32
hideMediaControls @ mediasession.js?v=3.4.1.0:1
updatePlayerState @ mediasession.js?v=3.4.1.0:1
bindToPlayer @ mediasession.js?v=3.4.1.0:1
(anonymous) @ mediasession.js?v=3.4.1.0:1
(anonymous) @ events.js?v=3.4.1.0:1
trigger @ events.js?v=3.4.1.0:1
triggerPlayerChange @ playbackmanager.js?v=3.4.1.0:1
setCurrentPlayerInternal @ playbackmanager.js?v=3.4.1.0:1
onPlaybackStarted @ playbackmanager.js?v=3.4.1.0:2
(anonymous) @ playbackmanager.js?v=3.4.1.0:1

Edit: some more playback javascript errors when attempting to use the few buttons that are still there


TypeError: getPlayerData(...).streamInfo is undefined[Learn More] playbackmanager.js:1:15323
    canPlayerSeek http://<localname>/web/bower_components/emby-webcomponents/playback/playbackmanager.js:1:15323
    changeStream http://<localname>/web/bower_components/emby-webcomponents/playback/playbackmanager.js:1:15539
    PlaybackManager/self.seek http://<localname>/web/bower_components/emby-webcomponents/playback/playbackmanager.js:2:22416
    PlaybackManager.prototype.seekPercent http://<localname>/web/bower_components/emby-webcomponents/playback/playbackmanager.js:3:2233
    <anonymous> http://<localname>/web/scripts/videoosd.js:1:29295
TypeError: getPlayerData(...).streamInfo is undefined[Learn More] 3 playbackmanager.js:1:15323
    canPlayerSeek http://<localname>/web/bower_components/emby-webcomponents/playback/playbackmanager.js:1:15323
    changeStream http://<localname>/web/bower_components/emby-webcomponents/playback/playbackmanager.js:1:15539
    PlaybackManager/self.seek http://<localname>/web/bower_components/emby-webcomponents/playback/playbackmanager.js:2:22416
    PlaybackManager/self.seekRelative http://<localname>/web/bower_components/emby-webcomponents/playback/playbackmanager.js:2:22736
    PlaybackManager.prototype.rewind http://<localname>/web/bower_components/emby-webcomponents/playback/playbackmanager.js:3:2033
    <anonymous> http://<localname>/web/scripts/videoosd.js:1:30466
Source map error: request failed with status 404
Resource URL: http://<localname>/web/bower_components/hlsjs/dist/hls.min.js?v=3.4.1.0
Source Map URL: hls.min.js.map[Learn More]

Edited by mueslo, 19 June 2018 - 06:18 AM.


#2 themenezes OFFLINE  

themenezes

    Newbie

  • Members
  • 2 posts
  • Local time: 06:54 AM

Posted 19 June 2018 - 09:06 AM

I'm running emby on a windows 10 machine and i'm having the same problem. It started recently (las time i used the web ui was around last thuesday ? maybe friday?).

I've tried accessing the app.emby on chrome and firefox (using linux) and the problem persists:

 

looking at the javascript console the following errors appear:

TypeError: newValue is null[Learn More]
app.emby.media:32:21

Loading failed for the <script> with source “http://app.emby.media/bower_components/emby-webcomponents/fullscreen/fullscreen-doubleclick.js?v=3.4.1.17”.
app.emby.media:1

Error: Load failed: bower_components/emby-webcomponents/fullscreen/fullscreen-doubleclick: http://app.emby.media/bower_components/emby-webcomponents/fullscreen/fullscreen-doubleclick.js?v=3.4.1.17
alameda.js:1:10040

RequireJS error: Error: Load failed: bower_components/emby-webcomponents/fullscreen/fullscreen-doubleclick: http://app.emby.media/bower_components/emby-webcomponents/fullscreen/fullscreen-doubleclick.js?v=3.4.1.17. Failed modules: 
site.js:1:10402

ConnectionManager request failed to url: http://192.168.25.3:8096/emby/system/info/public
connectionmanager.js:1:2852

 



#3 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142291 posts
  • Local time: 03:54 AM

Posted 19 June 2018 - 09:38 AM

I haven't seen any of this before. Sounds like more resources getting blocked.

#4 mueslo OFFLINE  

mueslo

    Advanced Member

  • Members
  • 43 posts
  • Local time: 09:54 AM

Posted 19 June 2018 - 09:49 AM

I haven't seen any of this before. Sounds like more resources getting blocked.

 

You seem to be right. I just tried it with a third browser (which I usually never use, Konqueror), there it works. However, both with Firefox and Chromium with all blocking addons disabled, it doesn't. That seems strange. It's definitely something that just started happening recently.

 

This is on Firefox 61.0b14/60.0 and Chromium 67.0 on Linux. I#m

 

Edit: I've solved it. It is due to the new KDE Plasma Browser integration (in my case). I'm guessing themenezes is also running KDE Plasma 5.13

 

See also: https://www.kde.org/...asma-5.13.0.php


Edited by mueslo, 19 June 2018 - 10:19 AM.

  • Baenwort and themenezes like this

#5 themenezes OFFLINE  

themenezes

    Newbie

  • Members
  • 2 posts
  • Local time: 06:54 AM

Posted 19 June 2018 - 04:08 PM

You seem to be right. I just tried it with a third browser (which I usually never use, Konqueror), there it works. However, both with Firefox and Chromium with all blocking addons disabled, it doesn't. That seems strange. It's definitely something that just started happening recently.

 

This is on Firefox 61.0b14/60.0 and Chromium 67.0 on Linux. I#m

 

Edit: I've solved it. It is due to the new KDE Plasma Browser integration (in my case). I'm guessing themenezes is also running KDE Plasma 5.13

 

See also: https://www.kde.org/...asma-5.13.0.php

 

Yep that was my issue as well. If i disable the kde plugin, everything works, thanks!



#6 Luke OFFLINE  

Luke

    System Architect

  • Administrators
  • 142291 posts
  • Local time: 03:54 AM

Posted 19 June 2018 - 04:14 PM

Well done. Great investigation !







Also tagged with one or more of these keywords: web, ui, bug

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users