Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Unwatched markers don't work #400

Closed
1 task done
hot36952 opened this issue Aug 18, 2024 · 4 comments
Closed
1 task done

[BUG] Unwatched markers don't work #400

hot36952 opened this issue Aug 18, 2024 · 4 comments

Comments

@hot36952
Copy link

hot36952 commented Aug 18, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

The server is installed on unraid and the client is installed on window10.
Every time I open the client to view unwatched markers, it sometimes works and sometimes doesn't.

Unwatched markers don't work.
0001
0002

Unwatched markers work.
0003

Expected Behavior

No response

Steps To Reproduce

1.open the client.
2.view unwatched markers.
3.It works or it doesn't.

Environment

- OS:Unraid 6.12.10
- How docker service was installed:Unraid Community Applications

CPU architecture

x86-64

Docker creation

0004

Container logs

text  error  warn  system  array  login  

Connection to localhost (127.0.0.1) 32400 port [tcp/*] succeeded!
[migrations] started
[migrations] no migrations found
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    1000
User GID:    1000
───────────────────────────────────────
Linuxserver.io version: 1.40.5.8854-f36c552fd-ls228
Build-date: 2024-08-14T17:32:00+00:00
───────────────────────────────────────
    
**** Server already claimed ****
**** creating video group video47w2 with id 18 ****
**** adding /dev/dri/renderD128 to video group video47w2 with id 18 ****
**** permissions for /dev/dri/card0 are good ****
Docker is used for versioning skip update check
[custom-init] No custom files found, skipping...
Starting Plex Media Server. . . (you can ignore the libusb_init error)
[ls.io-init] done.
Critical: libusb_init failed
Copy link

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@aptalca
Copy link
Member

aptalca commented Aug 18, 2024

That's a Plex issue, not a docker one. You should report to them.

@hot36952
Copy link
Author

That's a Plex issue, not a docker one. You should report to them.

Please look at the picture and description, I think it's plex's problem.

@aptalca
Copy link
Member

aptalca commented Aug 18, 2024

That's what I said. We are not Plex. We do not develop Plex. We package Plex in a docker container. That's all.

Any issue with Plex needs to be reported to Plex, not us

@aptalca aptalca closed this as not planned Won't fix, can't repro, duplicate, stale Aug 18, 2024
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Aug 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

No branches or pull requests

2 participants