Bug Tracker

Feature Suggestions
1

It seems some things get lost on the forums. I’ve subscribed to a few threads that have issues that have been outstanding for months. Sometimes a Dev will pop in to request logs or say it is being investigated but I’m not sure if this is the case 100% of time time. For things that are beyond user error, it would be nice to have a bug tracker. This will allow it to be seen how widespread the issue is and it will allow us to see what issues are actively being investigated.

Current Listing:

Player (General):
BUG : New Subtitles search feature not downloading.
Reported: Sep 26, 2018. Acknowledgement Status : Pending. Status : Not fixed.

Player (Android TV):
BUG : Rewind Near End of Video Freezes.
Reported: Apr 7, 2018. Acknowledgement Status : Not able to replicate. Status : Not fixed.

BUG : Playback fails on first attempt (spinning circle).
Reported: May 11, 2018. Acknowledgement Status : None. Status : Not fixed.

BUG : Playback Stopping and Queuing Next Item.
Reported: Feb 17, 2018. Acknowledgement Status : Investigating. Status : Not fixed.

BUG : Scrolling Through Library (Horizontal) Crash.
Reported: Jan 5, 2018. Acknowledgement Status : Not able to replicate. Status : Not fixed.

2

Definite good idea - bugs happen, but it would be good to know that a) they’ve been picked up and b) the current status

3

The android chromecast 2.0 bug I’ve been trying to get noticed
Short version is that Chromecast has taken a dislike to the android app

Ive raised with google as well for what its worth
https://issuetracker.google.com/issues/118331261

1 Like
4

I suggest linking any bug that has been posted (anywhere on the forum) to this thread.

  1. One place and will act as the Bug Tracker in the mean time.
  2. It will keep this request visible and bring attention why this is so important.

BUG: New Subtitles search feature not downloading. Acknowledgement Status: Pending. Status: Not fixed.

1 Like
5

Sounds like a good plan:

1 Like
6

Great Idea. I’ve added a few (I’m sure you can guess my client of choice). I’ll try to keep the initial post updated as others reply.

1 Like
7

great idea. I’m always frustrated how any reports seem to totally go to the wayside

8

I’m a software developer of 20+ years, and I never saw such odd way of handling issues. I have a long list of reasons why the way things are handled by Plex is hard to justify. I guess the bigger point is that there is advantage to motivate your user to report issues. Right now, I believe I’m wasting my time to report easy to fix issues that likely impact high percentage of users. One way to improve this, is to add a tag by the dev team to a thread marked as ‘tracker bug’, or ‘tracked feature’. And the tag is changed to fixed when done. If that was open source and still not free, I would likely fix some of the bugs for free.

6 Likes
9

Screenshot_2020-10-28-04-00-49-612_com.facebook.katana
Screenshot_2020-10-28-04-00-49-612_com.facebook.katana474×1054 212 KB

Nvidia shield crashed after update October 22 synology updated also ..

Happen when trying to mark all tv show as unwatched

10

Here’s an out-and-out bug that would be fixed by simply renaming a field – ignored for over a month despite my tagging of plex employees: [BUG] Webhooks returning multiple `guid` fields of different datatypes

Every functioning software company has bug trackers for their products. What does that make Plex Inc?

11

Here’s the bug I just posted, adding it here to increase visibility and hopefully get some tracking.

(BUG) Rotten Tomatoes Ratings Broken in 1.20.4.3517 - Plex Media Server - Plex Forum

12

This has been driving me NUTS for a couple months now without any indication any plex employee has even seen it

1 Like
13

A forum is NOT, definitely, a good place to report bugs, because they require o totally different workflow, and need to be tracked.

So, any tags or any other workaround will not fix this. A Bug Tracking System is what Plex needs.

It can be so simple as MantisBT, or so complex as Jira, but they are required. Now.

Thanks.

14

Oh my… this feature request is from 2018???

And nothing has been done until now???

Is there any future here?

1 Like
15

If the title contains “null” literal string, it will be lost everything before.
“Bill Gates az energiáról: A nulla szintig újítunk!” --> “a szintig újítunk!”
(Bill Gates on energy: Innovate to zero!)
Version 4.47.3

16

Hello - not sure if I’m posting in the right place, but with new update for Plex for Mac (1.34.1.2590-74ea7099) I’m seeing small white flashing lines on the right and bottom borders when playing any video. Can provide screen shots/recording if needed. In the meantime, is there any way to downgrade to the prior version from an automatic update?

17

Not quite the right spot … but that specific bug has a different thread and looks like devs are on it.

18

Thanks, I appreciate your help!

19

I really don’t understand why Plex doesn’t have a public bug tracker yet, even a read-only one where users can’t post any issues would go a long way for users to see what’s happening with plex development behind the curtain.

Even a git commit log would be better than nothing, so we can be excited to see commits that relate to the problem we’re hopping for a fix.

It’s not news that older users are leaving Plex as free/open source alternatives become more mature (and Jellyfin is getting there really fast, with 757 code contributors today!!), so lack of transparency in this time and age is a dead sentence for any private held product.

Plex is still a really good product, but the lack of transparency and the difficulty to navigate this forums to find feedback from the dev team on issues is just absurd, and to be fair, ages behind a platform like github used by open source projects.

Jellyfin is closing the gap with Plex more and more everyday, and today it’s already a pretty good option to Plex. It may not be as good at Plex YET, but it’s a matter of time! And it’s free. And It’s transparent with a proper bug tracker, git commit log so users can see how the development is going, what’s being fixed and what’s not. Not to mention that someone like me, for example, can dig into the code and fix a problem by itself and share with everyone.

Concluding… from what I read on this forum, all that everybody who’s complaining and leaving Plex want is transparency!
It’s not even about “fixing bugs”, it’s about “what’s happening”.
Just let us know what Plex actually consider as a BUG (because we don’t even know a issue posted here becomes an actual bug!!), what’s being done and what’s not.

And there’s no other way to do that but with a Bug Tracker!

The funny thing to me is that it would go a long way for you guys at Plex as well, so you won’t have to address people on the forum. If someone complains about something, just tell then to look at the bug tracker!

There’s a lot of “friction” happening between users and plex team in this forum, and that’s just the perfect recipe for loose consumers to the free open source competition. And I believe all that could have been avoided years ago (since this thread was suggested 4 years ago) by a simple read only public bug tracker log list!

I really don’t get it…

my 2 cents.
-H

2 Likes
20

bump :fist_right: :fist_left: