-
Notifications
You must be signed in to change notification settings - Fork 62
Stopped working #160
Comments
Andrew, what reaction do you expect from me, by posting twice a very bad review on AMO ? Do you think I'll take it as an encouragement for keeping working, especially on your problem ? |
Yes that's exactly what I would expect and exactly what I would do if I On 01/15/2015 09:15 AM, foudfou wrote:
Andrew DeFaria |
Oh I see. Motivation with a stick... We both agree on wanting to make a good job. The essential part is when somebody wants to share a critic, how it is done, and why it is done so. For instance, I don't think I did a bad job with v0.5.4. In fact I brought FireTray to Unity and Plasma5 users (#130), while keeping it working for most Linux and all Windows users, and although I did not really want to do it. So cool down, read the issues, and downgrade to v0.5.3 while the issue is being solved. It's not about being sensitive about my skills, which are certainly very limited, I grant you that. It's about your attitude toward me. Slapping someone in the face has never really motivated anyone. You'll see positive attitudes all around in this issue system: people trying to help find a solution. I also see a contradiction in bad reviews as yours. You obviously appreciate the addon, or you have. But this does not appear in your reviews. And you obviously want to continue to use it, urgently. So you probably value the addon. Why the worst grade then (twice) ? While we are speaking of motivation, here is a nice talk from Dan Pink I'd like to share here. |
Go to about:config. Search for with_indicator, set it to false. Restart Thunderbird. This fixed it for me on XFCE. |
Thanks. That worked. Although it was with_appindicator, not with_indicator. On 01/15/2015 11:04 AM, Trent McPheron wrote:
Andrew DeFaria |
Right, my bad. |
I'm on Ubuntu 14.04 with TB 31.3.0. FT is 0.5.4. Stopped working. Now does nothing. When I minimize or close TB TB just goes away. FT does nothing. HELP!
Please email me at adefaria@gmail.com as I probably will never come back here to check to see if this is updated.
The text was updated successfully, but these errors were encountered: