Clementine icon indicating copy to clipboard operation
Clementine copied to clipboard

Clementine crashes upon launch on Mac Mini M1 running Big Sur 11.3

Open rsmacleod opened this issue 3 years ago • 4 comments

Before posting

Please follow the steps below and check the boxes with [x] once you did the step.

  • [ X] I checked the issue tracker for similar issues
  • [ X] I checked the changelog if the issue is already resolved
  • [X ] I tried the latest Clementine build from here

System information

Please provide information about your system and the version of Clementine used.

  • Operating System: OXS 11.3
  • Clementine version: 1.3.1 (4096.1.3.1.1)

Expected behaviour / actual behaviour

Was supposed to launch /. crashed.

Steps to reproduce the problem (only for bugs)

Easy, just double click on the app. clementine-crash.log

rsmacleod avatar Apr 29 '21 01:04 rsmacleod

Looks like others have run into this and solved it with permissions settings. https://groups.google.com/g/clementine-player/c/rSxKHtpbX-4

You could also try a newer version, but the crash points to an included 3rd party library that hasn't been touched in a long time. https://github.com/clementine-player/Clementine/releases/tag/1.4.0rc1-586-g20647e8a9

jbroadus avatar Apr 29 '21 03:04 jbroadus

The problem fix with @jbroadus link. Thanks

adc91 avatar Jul 22 '21 20:07 adc91

The same with Monterey 12.3 (Apple Silicon, FWIW). The fix in the Google Groups thread (Preferences > Security & Privacy > Privacy > Accessibility > tick clementine.app) worked. I had recently installed another open-source player, and it explicitly asked for this permission. Would it make sense to do the same?

halilim avatar Mar 19 '22 16:03 halilim

@halilim Great idea. Unless, of course, it's a test to assure only the worthy become Clementine users.

bhyde avatar May 06 '22 13:05 bhyde

It's interesting, if you run /Applications/clementine.app/MacOS/Contents/clementine the app launches just fine as well. Though it kicks the warning 21:28:52.644 WARN unknown QPainter::begin: Paint device returned engine == 0, type: 2

I'm not sure what's going on here.

txoof avatar Oct 20 '22 19:10 txoof

Looks like others have run into this and solved it with permissions settings. https://groups.google.com/g/clementine-player/c/rSxKHtpbX-4

You could also try a newer version, but the crash points to an included 3rd party library that hasn't been touched in a long time. https://github.com/clementine-player/Clementine/releases/tag/1.4.0rc1-586-g20647e8a9

Installed the suggested stable version from the homepage on current macOS 12.6.1 21G217 x86_64 on a 2015 MacBook Air.

Giving Clementine accessability permissons allowed it to run. 👍

Thanks 🙏

insasquatchcountry avatar Dec 03 '22 07:12 insasquatchcountry

QPainter::begin: Paint device returned engine == 0, type: 2

I found this an explanation for when that error is thrown.

"When you get a message from QPainter saying that the engine returned 0, this means that for some reason it is unable to paint on the paint device in question. Pretty much all the times you see this it would be in relation to a QPixmap or a QImage. In the case of QPixmap/QImage it means that it is null, meaning that it has no size set which is why it cannot paint to it. This is either because no size was specified for it or because the size requested was too big that it would have caused an overflow which meant that it ended up not having that size set. If you call isNull() then most of the time it will return true, but sometimes it is possible that QPixmap will not return true but will still have a problem if the size of the pixmap was too large. Reducing the size will make it work."

¯_(ツ)_/¯

insasquatchcountry avatar Dec 03 '22 07:12 insasquatchcountry