-
Notifications
You must be signed in to change notification settings - Fork 261
Crashes upon open in Mac OS Mojave #668
Comments
Im having the same issue but I do get an error. Flash Player (Radiant Player Internet plug-in) quit unexpectedly. At the bottom of the player I also see Plug-In Failure. If you need a stack trace please let me know |
Great (well kind of) to see this isn't just me. |
Im using this in the meantime, works fine, pretty much the same thing |
I found that that devoured my CPU, consistently using >30% at times, on a high powered MacBook, so had to remove it unfortunately. |
Radiant player crashed once or twice after upgrading to Mojave. It now launches, but this error message "Blocked Plug-In" immediately pops up. If you press the play button on an album, it doesn't play music. I then visited the Adobe Flash site and installed the lates Flash, 31.0.0, but the result was the same with Radiant Player. |
@ryofurue Install the Flash plugin with |
@tjanson that brew formula is dead |
Thanks. I found that |
I.e. you still get the "Blocked plugin" message? Or crash on startup? |
The former. Radiant player launches without crashing. But, the "Blocked Plug-In" message pops up right away; and when I press the play button on any of the songs, the notification pops up at the upper right corner of the screen (not the Radiant-Player window) indicating the song, which is normal; but the song doesn't play; soon, the song is skipped and the Player tries to play the next song; and it repeats this cycle. The songs do play on Google Play Music opened on Google Chrome. |
@ryofurue I'm seeing the exact same thing on High Sierra, even after updating flash (and google play working in Safari) it is functioning the same way. |
Ah, that means it's not a Mojave thing. Something happened to Flash or to Radiant Player. |
There was a big update with Google Suite a few weeks back, a similar time to Mojave updating & Radiant Player crashing. Could this be the issue, perhaps Google have changes some things on their end? |
I’m getting the Blocked Plugin now too (on High Sierra). Is it still crashing on startup for you @Lusken? Maybe we should open a separate issue since it’s two (presumably) unrelated problems. As for the Blocked Plugin, I can’t help but notice that it coincided with the upgrade to |
Any updates, since updating to Mojave, I have the blocked plug-in. Further on inspecting the element, all I see is below:
|
I still is not working for me, and unfortunately Google Music Desktop Player launch three of the same app when you listen to it so devours the computer's processing speeds. Are people still working on Radiant Player? |
I've submitted a PR #670 with a workaround that seems to fix the issue in my Mojave machine. Some additional tests and improvements may be needed to see if it doesn't negatively affects previous macOS versions. |
Fixes issues with plugins not loading in macOS Mojave (issue #668)
@Lusken @jacobwgillespie Should we close this issue? |
I don't get the blocked plugin issue anymore when I run on high sierra but on my Mojave computer it crashes immediately upon startup (the window briefly appears with nothing loaded on it and then crash).
|
So I got that when I first booted up the older version. Got the update,
then upon restart it crashed. That is to say there was no opportunity to update as it crashed immediately. Didn't get the error log but it was the same
behaviour. So I uninstalled and re-installed from brew and got the above.
I'll try downloading from the release page.
From: Tom Janson <[email protected]> <[email protected]>
Reply: radiant-player/radiant-player-mac
<[email protected]>
<[email protected]>
Date: November 29, 2018 at 1:12:08 PM
To: radiant-player/radiant-player-mac
<[email protected]>
<[email protected]>
Cc: Christopher Kolmatycki <[email protected]> <[email protected]>,
Mention <[email protected]> <[email protected]>
Subject: Re: [radiant-player/radiant-player-mac] Crashes upon open in Mac
OS Mojave (#668)
@chriskol <https://github.com/chriskol> There’s a newer release of Radiant
Player (that’s not in Brew yet), 1.11.7, which includes the fix mentioned
above. (But there’s still #675
<#675>.)
Should get it through the menu: Radiant Player → Check for updates
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#668 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AE-XU94mILgVfAuPAibZgzX8dmGHnkHyks5u0BVogaJpZM4W7tXa>
.
|
Just downloaded from the project page and no dice. Same as above except I don't get an opportunity to send to apple and can't get the error log. |
As noted by chriskol, I see the same behaviour on Mojave. Player will flash for a split second before crashing. |
I was able to fix this issue by going into System Preferences>Security & Privacy>Accessibility and removing radiant player from the applications listed there with the minus button, then dragging radiant player back into the list from my applications folder. |
I tried above as per @adepssimius but still got the same thing EXCEPT this time I was able to get an error report!
|
Whoa I just fiddled around further as per @adepssimius' suggestion and I got it to work with one slight modification. When dragging Radiant player back as per above, I also had to uncheck it (it came in checked by default). When I started Radiant Player, it warned me saying I needed to enable accessibility. I THEN checked the box and restarted Radiant and it works! |
I was successful in getting the Player work again in a somewhat different way from yours:
|
Identical experience as @adepssimius, I did not have to do what @chriskol and @ryofurue had to. If it makes a difference, I dragged the application file from the User/Application Folder not the Dock. |
Since updating to Mac OS Mojave the application crashes immediately upon startup, with no explanation as to why.
Would be great to get it working again, as there is no other decent platform that does this :).
EDIT: The issue may have arisen from Google updating their online platforms at a similar time to Mojave being released... Could there be linked causes to this issue?
The text was updated successfully, but these errors were encountered: