Page MenuHomeSolus

Mailspring broken
Open, Needs More InfoPublic


Version mailspring-1.10.3-41-1-x86_64.eopkg won't open. Had to downgrade to previous version.

Related Objects

Event Timeline

raenk created this task.Jun 1 2022, 4:06 PM
Staudey added a subscriber: Staudey.Jun 1 2022, 4:56 PM

Hmm, I could get it to work by passing the --disable-gpu argument, so it might be related to this fix:

That is, if we're talking about the same issue. In my case I couldn't click through the "Getting Started" screens, because either the buttons wouldn't do anything, or I'd end up on a screen with a spinning "loading wheel" and no progress.

raenk added a comment.Jun 2 2022, 12:21 AM

I don't have the exact errors (log) right now as I have downgraded it. But, executing it from CLI, I do remember a bunch of complaints regarding GPU.
In my case, the app simply didn't show. It does execute because the tray icon is there, although not visible (empty space). But I can right click on it and get the options and can quit it from there.

So, the only way is to execute it with that flag?

brent added a subscriber: brent.Jun 3 2022, 12:39 AM

can confirm what raenk said. complete blackout when I auditioned email clients this week. terminal threw a lot of errors. launches from menu black, launches from terminal black. unusable. so uninstalled. if bypass works then disregard, I only posted to say I could replicate OP's problem.

Mailspring 1.10.3-41 has no issues on my laptop. What hardware are you using?

brent added a comment.Jun 4 2022, 3:45 PM

@brucehankins older intel quad core with mt 430 and MSI board. First thing I thought of every time blank, black Mailspring launched unusable was "theming." (Qogir Darl and Korla on Budgie). I wonder if @raenk shares any of these similar variables?

Okay, tested against Lenovo w/newer AMD, 2014 dual core Intel/HP, and 7th gen Intel/Nvidia combo. Mailspring runs fine on all my configurations.

Themes Orchis Dark/Solus Dark/Sweet/Beauty line icons on plasma, Orchis Dark/Korla on budgie, and arc darker/Korla on budgie.

brent added a comment.Jun 4 2022, 7:29 PM

bruce, I may have auditioned mailspring before the last 2 updates. so trying it again in realtime.

$ mailspring
Running database migrations
App load time: 271ms
[7184:0604/] Passthrough is not supported, GL is angle, ANGLE is 

Running Setup
Manual update check ( returned 503
Error Downloading Update: Unexpected end of JSON input
Pretty harmless output. It's launched. I have the Welcome to Mailspring greeting. Hitting the "getting started" button, drum roll, wow, actually got another window for the first time "Compose with Context." Hitting Next: more tutorial. Next: Window with white screen and spinning ball.

--i've returned to this dispatch after 5 minutes. Still spinning (see attached?).
Other factors I did not mention via neofetch:
nvidia 390's and Intel I5.

The updates (to the 390s?) fixed something. I went three slides in this time.
Will defer to OP and hopefully he/she chimes in. I moved on. Will keep it installed a while if you need me to test/try anything--will gladly help.
raenk added a comment.Jun 7 2022, 4:13 PM

I have this issue in at least a couple of machines. These are the specs of one of them:

AMD FX(tm)-6300 Six-Core Processor
GT218 [GeForce 210]

I don't have the other one at hand, but is older hardware (Intel Core 2 Duo and 4GB I believe, not sure about graphics, but should be nvidia old card).

joebonrichie triaged this task as Needs More Info priority.Aug 16 2022, 2:37 PM
joebonrichie added a subscriber: joebonrichie.

Is this still an issue? Probably a bug between electron / mesa / driver combinations. We can update mesa to the latest version and/or hope a newer electron version solves the issue.

brent added a comment.Aug 16 2022, 3:36 PM

can't speak for others but non-issue for me. couldn't get it to work and moved on. did not try any further than the output above*

This might be fixed by D13483 which updates the version of Electron used by Mailspring. I also undid some graphics library linking that the package was doing which none of our other Electron packages were doing (I couldn't find anything about why it was doing that in the first place, and the person who made that change no longer seems to contribute to Solus).

Hopefully one or both of these helps with the issue, but I will say that as far as I can tell Mailspring is doing something custom/funky with GPU init which could also be the culprit.

BTW with the current version after starting mailspring and seeing nothing show up does running killall mailspring in a terminal and then restarting it help? You may need to do this a couple of times until it launches.