I’ve been struggling to re-build my Manjaro system on a new computer for the past ½ year.
While a few minor enhancements came with the updates, they’ve broken a lot of more important functionality.
I have a separate installation on my notebook computer, which still works as desired.
But it seems impossible to clone that one onto the new machine, so I keep trying to get it into a new install.
After several months during which unified folders of Thunderbird had been broken (since update from version 102 to 115), it has “repaired” itself (by a silent update?) about a week ago: the (~15th) de- and re-install now shows the accounts and folders of the copied profile correctly.
But the system refuses to let Birdtray work:
(the “protocol” is nothing more than the 1-liner in the error message
~ “the panel cannot be controlled by this Add-on”)
I vaguely remember to have seen a similar message some years ago and that it had been easy to fix but don’t remember how.
Differences between the new system / the “reference” on the notebook:
Linux 66 / 65
Gnome 45 / 44
Wayland / X-Windows
That’s why I put that question mark - I don’t understand why it suddenly works after so many same unsuccessful tries - without additional manual changes or interventions (except for 3 re-boots - which I had tried earlier as well).
Until now it had been sufficient to adjust its basic .json-file.
And I don’t expect “official” support - this is rather an appeal for help to the community.
I know that Gnome-Shell-Extensions are broken by updates - currently 4, for which I hope for updates.
But Birdtray is not a Gnome-Shell-Extension, is it?
Sure, but … got lost in there, didn’t understand enough of it.
Sure - but it might be time to try that again … (and yes Wayland is the new default - X now breaks other details) … will take 15 minutes to store open work, etc.
(Wondering if installing “trayer” could fix it ←note to myself, because I’ll loose that open window on re-boot.)
Birdtray doesn’t have proper Wayland support. Typing “birdtray wayland” into a search engine finds articles like this one;
What worked in my tests (on Ubuntu with GNOME running on Wayland, Kubuntu with Wayland and Manjaro KDE with Wayland) was to start Birdtray using env XDG_SESSION_TYPE=x11 birdtray, and in the Birdtray settings have the Thunderbird command line option (on the Advanced tab) set to /usr/bin/env GDK_BACKEND=x11 /usr/bin/thunderbird.
… had really lived up to its name - destroyed its “progenitor” like a Supernova.
As stated directly above, Thunderbird has been revived after some months - current version is 115.4.2
Since my system currently uses Xorg - which doesn’t restore Birdtray’s functionality but gives a more detailed error message, I doubt that looking for a solution of Wayland-specific issues would help.
And - I don’t know how to use “env XDG_SESSION_TYPE=x11 birdtray”. Would that have to be written into the app starter for Birdtray?
Oh! Never read about mailbird - that might be the solution after the failure of Birdtray.
Will try it after de-installing Birdtray, which brought a huge pile of Qt- and related components as dependencies.
edit: my pamac doesn’t find a “mailbird” package.
Well, it’s an MS-Windows App and the only Linux alternatives I haven’t tried so far seem to be Vivaldi Mail and Betterbird. Will have a look at these.
Or - wait a minute - how did you persuade pamac to build mailbird?
Never mind - the ornithology of mail clients has become increasingly confusing.
And you made me find Betterbird / Vivaldi as potential replacements for Thunderbird / Mozilla.
… which look interesting but leave concerns about their life expectancy - after 25+ years with the Mozilla apps.
A possible difference between your test installation and mine might come from its starting point: I have started it from a “minimal” iso image hoping to avoid some of the bloat that comes with it. Wouldn’t be the first time that it just lacks a small helper function that had been “forgotten” in the dependencies. (iirc, something like that was the reason why I have seen a similar error message some years ago - but had no difficulty to find the “missing ink” back then)
Took some time - hard time - to clarify the(se) issue(s).
Had forgotten the passphrase for my parallel test installation on a separate partition.
Re-installing without formatting seemed restore the access to that (not yet encrypted) installation, but … corrupted the (somewhat productive) main installation on access to its home folder. Restoring that per Timeshift made the test installation again unusable.
So I had to re-make the test installation from scratch: 1 full day and still much left to be amended.
But I have, again, learned a lot during this exhausting proceedure.
Answers to above open questions:
Installation of current Thunderbird and using the copied profile of the reference installation works absolutely smoothly.
Birdtray works on the current “standard” installation (the bloated one), but not on “minimal”. (Do not (yet?) know which component of the bloat is needed for Birdtray. Perhaps I’d have to invest another week to re-create the main installation from the “standard” rather than minimal ISO.) The old configuration (.json file) does not work but is now more easily re-configured manually.
Some really hard hours: Firefox freezes in a minimal window when trying to use the profile of the reference (same FF version) - the new install needs the extensions folder in the parent of (rather than inside) the profile folders.
New and “re-arising” questions about Timeshift, cronjob, setting up a virtual machine, …
Meanwhile, i.e. since Wednesday to Thursday night, it has become clear that the only missing part was the “AppIndicator and KStatusNotifierItem Support”-extension. And I think that it had been exactly the one “I vaguely remembered” - but had forgotten its name and its paramount significance for a usable Gnome.
Back then it had been easy to find in the “system-extensions” from which it has meanwhile been removed for inexplicable reasons.
This also solved the most important of the next (planned) topics: Dropbox and Telegram which had worked rudimentarily, but didn’t allow access to their settings, i.e. were not really usable.