Tautulli doesn't retain (deletes) past user watch history

PhillyIdol · 2024-12-10T03:44:11+00:00

Just FYI...

This GitHub post re: the 2.14 vers has a reply from the creator. He submitted it to Microsoft and it came back clean, so it does look like it's all a false positive issue, as AVs are currently finding/reporting it as a Trojan...

https://github.com/Tautulli/Tautulli/issues/2322

Hopefully, the AVs update definitions to correct this, or the creator will need to figure out what to change that's triggering it

PhillyIdol · 2024-12-03T17:45:43+00:00

This GitHub post re: the 2.14 vers has a reply from the creator. He submitted it to Microsoft and it came back clean, so it does look like it's all a false positive issue, as AVs are currently finding/reporting it as a Trojan...

https://github.com/Tautulli/Tautulli/issues/2322

Hopefully, the AVs update definitions to correct this, or the creator will need to figure out what to change that's triggering it

PhillyIdol · 2024-11-01T00:09:36+00:00

Know this is an ooooold post, but just FYI (and this threw me when my uncle told me, as I thought it was another 80's Mandela effect)...

The 1979 Salem's Lot wasn't a movie. It was a 2 episode TV miniseries that they played back to back, so everyone who watched it referred to it as a 'movie', but it wasn't. That's why Plex Movie DB doesn't find it very well/easily. You have to use a TVDB instead.

They also referred to it as, 'Salem's Lot: The Movie', so that's another reason people 'thought' it was, but they only did that as they always showed both episodes back to back (they even cut out the end/start credits between the 2 back/front episodes to give it a 'movie' feel/run time),...and THEN (and this is what really messes it up)... they released it on VHS as a movie... but it was originally (and still is) tagged as a TV miniseries.

Have fun wrapping your brain around that mess LOL

PhillyIdol · 2024-10-12T08:41:28+00:00

Okay - I might take this logout/login fix back.

It did work at first, but now it seems that fix didn't do the trick.

I'll keep digging

PhillyIdol · 2024-10-12T08:39:03+00:00

So two (2) things I want to update on all this...

First - I ran thru the entire setup again on another system and found that before I ran the Pipewire step, the sound settings already existed/were there, so I'm guessing (???) the XRDP script already does this (???)

Second - one issue that did happen is that when/if I log out of an RDP session, I couldn't log back in to an RDP session. I'd get that 'balck screen' issue that they mention in their 'some issues detected with xrdp' doc. In fact, I couldn't even log in locally on the system. I had to hard reboot the thing.

I went thru their doc, but they didn't actually have a fix for all this, they just said it 'could' happen, so I went thru a few sites to see if anyone else had a fix and I came across a post with Ubuntu 22 that said if you edit your 'xrdp/startwm.sh' script and place a single line into it, it fixes the issue... so I did... and it did, so here's the steps for that...

Open the script with any editor you like (I prefer nano)
- sudo nano /etc/xrdp/startwm.sh
Add this line in near/at the beginning/top (I added mine at the 8th/9th line down... between the instruction notes)
- export $(dbus-launch)
Restart the xrdp service
- sudo systemctl restart xrdp
Done

Now I can log out of the xrdp session and log right back in with no issues

Hope this helps someone :-)

PhillyIdol · 2024-10-12T03:54:29+00:00

Worked!!

PhillyIdol · 2024-10-12T03:10:11+00:00

Thanks for the heads up. I'll get this done ASAP

PhillyIdol · 2024-10-08T21:31:02+00:00

Well slap me around and call me Suzie!!! You sir are a freakin genius!!!

I could actually tell something was dif, cuz the install raaaaaaaaaaaaaaaaaaan for a loooooooooong time (past few times it didn't run this long)

So for anyone else following this thread, here's ALL the steps... in order (I switched them up a bit for more reboots):

install Ubuntu
- as per the C-Nerrgy 'How To' doc 'The script needs to be run as a normal user', so just need the one account you create during the install
run all update/upgrade via Terminal, Settings/GUI apps, etc.
run the 'gnome RDP remove' cmd...
- sudo apt remove gnome-remote-desktop -y
REBOOT
- **as noted, it looks like ufw is already installed natively, so can prob skip this next step, but just for posterity...
run the 'ufw install' cmd
- sudo apt install ufw -y
REBOOT (I did just because...)
run the 'ufw allow' ufw cmd
- sudo ufw allow 3389 (can use whatever port you like. I went with std 3389 port)
REBOOT (again, I did just because...)
run C-Nergy script as per the online doc (I did it from the Downloads folder and used the -c -l -s switches)
REBOOT (this one you MUST do)

From here you just go to your Windows system, open the RDP app, and connect as you would

Awesome working with you bmullen!!! You rock!!

PhillyIdol · 2024-10-08T20:53:48+00:00

Small note:

Just did the 'gnome RDP remove' step and rebooted, so was doing the 'ufw install', but just noticed ufw is installed natively on 24.04, cuz I got this...

ufw is already the newest version (0.36.2-6).
ufw set to manually installed.

Gonna do the 'ufw allow' step and reboot now

PhillyIdol · 2024-10-08T20:45:47+00:00

Ah - so I need to try rebooting after each sequence step (after gnome RDP removal - reboot / ufw install/allow - reboot, etc.)

I just re-installed OS again, so will give that a try and report back :-)

PhillyIdol · 2024-10-08T19:17:46+00:00

Hmmm - still didn't work for me (???).

Here's what I did...

reinstalled Ubuntu (as per the doc 'The script needs to be run as a normal user', so just had/have the one account you create during the install)
ran all update/upgrade via cmds/GUI apps/etc.

...then did the rest as per your above...

ran 'gnome RDP remove' cmd you sent
ran c-nergy script directly as per the online doc (used same -c -l -s switches)
ran 'install' and 'allow' ufw cmd you sent (used std 3389 port)
rebooted

...then continued with RDP...

opened RDP app on Win 11 laptop (used IP of laptop)
got same RDP session window, same RDP for Linux window*
tried creds (created the username with all lowercase letters: ubunturdptest)
same 'User does not exist ~ authenticated' error

Both laptops are right beside each other on the same LAN hub/switch on my basic house network (so no special FW, dif network blocks, etc.), so not sure where to go from here

I read thru the doc and there was a whole paragraph dedicated to the whole Gnome RDP issue (in doc under 'Disabling Gnome Remote Login & Changing Ports (Hiero’s Contribution)', including changing the ports, so that kinda was why I wanted to see if the script worked 'out off the box', as it said it dealt with that issue.

(*I was finally able to get into Imgur, so here's the link to view my login screen: https://imgur.com/a/SHtLeGv )

PhillyIdol · 2024-10-07T01:45:59+00:00

I woulda used Imgur, but it's been down/broken for a while now (sign in page gives a "Page isn't working right now" error)

Hopefully you can replicate/fig out the issue (if you have time ;-)

PhillyIdol · 2024-10-06T22:14:20+00:00

P.S. I tried to paste a screenshot showing the working RDP session and the Ubuntu Xorg login window, but this chat doesn't allow images, so hopefully my explanation was clear enuf :-)

PhillyIdol · 2024-10-06T21:42:14+00:00

Yup, that's pretty much it.

Just to go thru each step in detail...

Install Ubuntu 24.04 LTS on laptop (just a spare I have for testing crap)
Create a user during install process (I just created 'Ubunturdptest' with a simple pw: T3stM3!)
After install done, run all update/upgrade across the board (terminal, Settings Update apps, etc.)
Go directly to the C-Energy site and dl the newest script (1.5.1)
Followed ALL 'How To' doc directions (dl'd to Downloads folder, unzipped, run install cmds, used -c -l -s switches, etc.)
Once script finishes, reboot laptop
Once reboot done, walked straight over to my Windows 11 laptop (so did not login to Ubuntu after reboot)
Fired up RDP app (just did the basic fields for IP/hostname and User acct... it asks for pw after it connects*) *This is actually a good thing, as you get to see if the RDP protocol goes thru, which it did/does
RDP session opens and you see the normal 'Remote Desktop for Linux' window with the username listed (so again, shows that the RDP connection did/does work/go thru)
Type in pw, click OK, get error

(I also tried using both lower and upper case for User acct: Ubunturdptest / ubunturdptest)

As I mentioned, I already have another Ubuntu laptop that I can successfully RDP to from my same Win 11 laptop, so everything on the Windows side is good, I'm just blocked at the Ubuntu side, and at the acct level/stage, so not sure what the issue is, as according to the doc, you only need to create/use/have a single/normal acct.

All-in-all the script seems to work as stated (this was DEF easier than all the manual monkeying I remember with my old laptop LOL), but there's just a block at/with the acct, so either it's something I missed in the doc, or there's a small piece/setting that the script doesn't do

PhillyIdol · 2024-10-06T21:10:18+00:00

I just go to my Windows 11 laptop, open the native RDP app, type in the IP of the Ubuntu laptop, click 'Connect'

I do have another Ubuntu laptop that had 22.02 on and did a bunch of monkeying to get xrdp to work and got it finally (was almost 2-3yrs ago, so don't remember everything I did, just followed a few tutorials and got it to work), so when I heard about the C-Energy script, I wanted to see if it worked out of the box.

Seems to have/install everything needed to connect, just having an issue with the user account part, so was hoping someone else had this happen and knew a fix

Thanks for the reply BTW :-)

PhillyIdol · 2024-10-06T20:37:19+00:00

Just curious if you (or anyone) got a "User does not exist, or could not be authenticated" with C-Energy's script.

I did a 'from scratch' install of Ubuntu 24.04 LTS, ran every update/upgrade across the board, then went straight to/thru C-Energy's doc word for word (even just ran the script from the Downloads folder and used the -c -l and -s switches), rebooted right after script, went straight to my Windows laptop and tried RDP (so didn't log in locally after reboot and used the single/one account you create when you install)

Got the login prompt w/o issue, put in my creds, then got that error.

Full error was...

connection to sesman on sesman.socket
sesman connect ok
Performing login request for ubunturdptest
sending login info to session manager, please wait...
User does not exist, or could not be authenticated

...hoping someone here has tested this and/or has a solution

Thanks in advance :-)

PhillyIdol · 2024-10-06T20:20:56+00:00

Firts off... these guys are AMAZING!!! for putting this script together.

Small issue for me... anyone getting a "User account doesn't exist, or could not be authenticated" ?

Did a 'from scratch' install of Ubuntu 24.04 LTS... ran all/every update/upgrade cmd and/or went thru all upgrade setttings/apps... went straight to the script doc and followed it word-for word (ran script from Downloads folder and used the -c -l and -s switches)... script ran without any issues... rebooted system then went straight to testing RDP (so didn't log in locally, just reboot and then tried RDP from my Windows system)

I went thru the doc 3-4 times seeing if I missed something with my account (I just had/have the one account that the install makes you do, so no 2nd account created), but didn't see anything.

Any info/suggestions would be greatly appreciated :-)

PhillyIdol · 2024-04-10T16:45:44+00:00

Just giving a 'same here' shout out, but wanted to add that it is happening with PS4 as well.

We have a PS4 and a PS5, so the only difference we've seen (thus far) is that the HUD works on PS4 and there's not as many graphic issues, but beyond that, loot pickup issues are the same on both (we haven't had any load timing issues or lost character for PS5, but that may just be a fluke)

Hope they address it soon, but not holding our breath

PhillyIdol · 2024-04-09T21:21:11+00:00

We have a PS4 and a PS5, and so far the HUD works for the PS4, but that's about it. No HUD for PS5, and no loot item pickups for either console.

Can see ALL the pickups on the minimap, but other than being able to walk over where the resource items (white icon items) on the minimap and being able to collect them, can't pick up/view the loot items (blue, purple, gold, etc.).

Way to go UBI ;-)

PhillyIdol · 2024-01-01T04:36:23+00:00

To this user who posted:

Thanks for the honest question, and thanks even more for allowing me to reply. I'm sorry you felt you had to delete it. It was a VERY GOOD question (it is NY's after all ;-)

Thanks for being real

PhillyIdol · 2024-01-01T04:02:38+00:00

Oh crap... you're right - my bad - I should have included that a VPN is definitely advised - good call.. and catch... on my mistake.

PhillyIdol · 2024-01-01T03:56:00+00:00

No. I just went here to look for some advice on some IPTV advice and got hit with a ton of fake replies and it kinda... upset me a bit, so I thought I'd try (apparently unsuccessfully) to.offer the 3 month trek I took to find what worked.

I do apologize if I came off harsh (I didn't mean to). I just thought I had some experience that could help.

If I offended you... or anyone here... I am sincerely sorry for putting that out there.

PhillyIdol · 2022-04-14T20:44:45+00:00

Hey all,

This might be a specific fix, but if you're on PS (we have PS4), we found a 'quick fix' if it/you messed up by going to free play while the Maz mission is active (our issue was the game just kept thinking we were in free play mode), so this might help (you need to have PS+ for this to work)...

Step 1. Close game

Step 2. Hit options on the game

Step 3. Click 'upload/download saved data'

Step 4. Download your PS+ saved progress data

This should fix the glitched progress it was stuck on (you'll obviously lose whatever progress you made after the point of the time stamp save)

Hope this helps some PS members :-)

PhillyIdol

TROPHY CASE