Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[whoareyou]

I installed bullseye on an old 32bit laptop and MC30 was running great with this setup.  I used machine mostly as a client connected to my main library for remote control of my main listening zone.  Been running this setup since MC30 was released.

I hadn't used machine for a while, so I decided to update to the latest build .48. 
Now, when I start MC the entire interface is frozen.  I can't start logging because it's frozen.

I suspect it has something to do with an update, but I'm not that great with linux builds and I'm a little lost with the troubleshooting.

I've tried reinstalling MC, but the freeze remains.  A little more explanation of what I mean by freezing.  The UI is actually responding but it is moving so slow as to be unusable.  Click on an option and it responds very slowly over the course of the next 5 or 10 minutes. 

It's only app on the bullseye install that is behaving in this manner.

What is best way to install older version of MC over current version?  I'd like to rule out that the issue isn't related to the .48 build.

Any other suggestions how to troubleshoot this one?

Thanks

[whoareyou]

Reverting to version 40 fixed the issue for me.  Not sure of exact release when this started, but 48 definitely gives issue.

Once version 48 is started my only option is to kill it.

Edit:
Any chance the code base is shared and could have same issue as was encountered in Windows release?
https://yabb.jriver.com/interact/index.php/topic,134851.msg934120.html#msg934120
Thanks.

[bob]

It does share code but that bug should have been fixed by Linux build 30.0.48.
Can you grab a log?

[whoareyou]

Problem is that I can't access any of the menu options when running 48 .

Guess I can enable logging in version 40 and then reinstall 48 (which should carry over the logging setting?).  I'll give that a try.

[bob]

Problem is that I can't access any of the menu options when running 48 .

Guess I can enable logging in version 40 and then reinstall 48 (which should carry over the logging setting?).  I'll give that a try.

Yes

[whoareyou]

Ok.  Think I have the logfile.  Can I e-mail to you?
Thanks

[JimH]

Bob at jriver.  Include a link.

[whoareyou]

e-mail sent.
Thanks

[bob]

Seems to be related to syncing back to the server, some of which happens automatically.
Turning off auth should prevent the slowdown for now.

[whoareyou]

Seems to be related to syncing back to the server, some of which happens automatically.
Turning off auth should prevent the slowdown for now.

This seemed to work for me, but unfortunately also started to hang.  48 was going great for a while and I stopped listening.  I put JRiver server to sleep (it's just a windows 11 Pro install), came back woke it up and when client connected the UI was hung.

I reverted back to 40, and I'll run that for a while just to make sure something else isn't going on.

[whoareyou]

Just like it says.... release 51 has resolved the issue

Bob, thanks for the quick turnaround