Search is case sensitive with cyrillic characters!

Plex Media Server NAS & Devices
1

Old search had and new search has the same bug: it is case sensitive if I use cyrillic characters.
How to reproduce the bug?)
Try to search something with cyrillic for example “Карточный домик” will find house of cards, however, typing “карточный домик” finds nothing.

Please fix this as it should be an easy fix.
“We’ve incorporated an advanced spell-checker into your searches” , Spell checker but case sensitivity… rly???
Ubuntu 14.04.4
plex 0.9.16.4

1 Like
2

Same here. plexmediaserver 0.9.16.4.1911-ee6e505 on Ubuntu 15.10

3

So where we should file a bug report?)

4

Guys from Plex, do you plan to fix this issue?

5

Any updates on this? Played with pms on shield and found this issue there as well as on Ubuntu.

6

Same here. PMS 1.1.4

7

PMS 1.1.4.2757 on Windows/FreeBSD. Problem is still here.

8

Version 2.12.0 in Windows
Same here.

9

Same here Version 1.9.7.4441

10

This should have been fixed long ago when Cyrillic character display was corrected when locales were corrected.

Can you please do the following

  1. Turn on verbose logging (Settings - Server - General)
  2. Repeat the failure
  3. Screen capture the failure
  4. Repeat it working with the other case
  5. Capture the screen again showing success
  6. Go to Settings - Server - Help - Download Logs

Upload the log here and I will submit to Engineering.

Thanks,

11

Here you go!

12

I found a problem.

Nov 18, 2017 15:21:52.530 [0x2b5882a00700] ERROR - Error parsing allowedNetworks 'https:': Invalid argument
Nov 18, 2017 15:21:52.543 [0x2b5882a00700] ERROR - Error parsing allowedNetworks 'https:': Invalid argument
Nov 18, 2017 15:21:52.771 [0x2b5882a00700] ERROR - Error parsing allowedNetworks 'https:': Invalid argument
Nov 18, 2017 15:21:52.780 [0x2b5882a00700] ERROR - Error parsing allowedNetworks 'https:': Invalid argument
Nov 18, 2017 15:21:52.891 [0x2b5882c01700] ERROR - Error parsing allowedNetworks 'https:': Invalid argument
Nov 18, 2017 15:21:52.893 [0x2b5882c01700] ERROR - Error parsing allowedNetworks 'https:': Invalid argument

Only put IP and network addresses in this entry. such as 192.168.0.0/24 (192.168.0.x)

13

Moving to Docker. You are on unRaid but also using Docker.

14

Why does it matter as far as search is concerned?

15

PMS is so busy dealing with the networking failure and resetting itself, nothing can complete in time. When you type in the value correctly, it finds it before the next network retry. You are literally on the edge of nothing working, from what I can see

I do have a bug report ready to submit but we first need to clear up the other errors and give engineering a clearly valid problem. If I submit it now, they will reject it

16

Here are the updated logs

17

That looks great. May I now have, to make sure they don’t need any more data, you repeat one last time with Verbose turned off?

This will give them both levels of information. It should be an easy fix for them. I can see what’s happening.

18

Here you go

19

I’m sorry, that doesn’t demonstrate it again.

Your logs only show:

Nov 19, 2017 08:44:14.571 [0x2b45e4c01700] INFO - Plex Media Server v1.9.7.4460-a39b25852 - ubuntu docker x86_64 - build: linux-ubuntu-x86_64 ubuntu - GMT -08:00
Nov 19, 2017 08:44:14.571 [0x2b45e4c01700] INFO - Linux version: 4.9.30-unRAID (#1 SMP PREEMPT Fri May 26 13:56:36 PDT 2017), language: en-US
Nov 19, 2017 08:44:14.571 [0x2b45e4c01700] INFO - Processor AMD Athlon(tm) X4 860K Quad Core Processor     
Nov 19, 2017 08:44:14.571 [0x2b45e4c01700] INFO - /usr/lib/plexmediaserver/Plex Media Server
Nov 19, 2017 08:44:15.041 [0x2b45e6602700] INFO - Successfully retrieved OCSP response
Nov 19, 2017 08:44:20.041 [0x2b45e8a46700] INFO - Refreshing paths watched by LibraryUpdateManager
Nov 19, 2017 08:44:20.414 [0x2b45eca00700] INFO - Sync: downloaded 0 sync list(s) with 0 sync items(s): 0 new, 0 updated, 0 deleted
Nov 19, 2017 08:44:24.375 [0x2b45ee208700] INFO - AutoUpdate: no updates available
Nov 19, 2017 08:44:29.327 [0x2b45eee16700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (b6c84e89-d180-427b-bce5-1dd4a331d37d, expected 6a22df46-4e84-4f1d-a46b-40f82e7f831b)
Nov 19, 2017 08:44:30.073 [0x2b45eee16700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (3ce7e636-2821-46bf-be7e-b91962cf97fb, expected f30cbaea-486e-4a79-94d6-bf779e9836f5)
Nov 19, 2017 08:44:30.370 [0x2b45eee16700] WARN - PubSub: Received notifyConnectivity event with incorrect async identifier (6a22df46-4e84-4f1d-a46b-40f82e7f831b, expected f30cbaea-486e-4a79-94d6-bf779e9836f5)
Nov 19, 2017 08:45:14.835 [0x2b45ee409700] INFO - AutoUpdate: no updates available
20

How about this one?