You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
On XFCE, Mintreport-tray intermittently shows the "[!]" icon, but once I click on it, it has nothing to report. I found out a while ago that this is remedied by introducing a startup delay.
The delay is actually requested by /etc/xdg/autostart/mintreport.desktop for two other desktop environments, like this:
As you can see, the delay is not applied in XFCE, and I am afraid XFCE has no such option.
So I ended up modifying /etc/xdg/autostart/mintreport.desktop by changing from
Exec=mintreport-tray
to
Exec=/bin/bash -c "sleep 40 && mintreport-tray"
but I had to redo it after upgrading to 21.3 (Virginia) because the upgrade renamed the file.
Perhaps it is possible to make the Exec line conditional depending on desktop environment, but I don't know how to accomplish this. Any ideas?
A better solution would be for mintreport to wait a while after startup, before hastily reporting nonexistent issues. Either way, this is a manual workaround.
The text was updated successfully, but these errors were encountered:
On XFCE, Mintreport-tray intermittently shows the "[!]" icon, but once I click on it, it has nothing to report. I found out a while ago that this is remedied by introducing a startup delay.
The delay is actually requested by
/etc/xdg/autostart/mintreport.desktop
for two other desktop environments, like this:As you can see, the delay is not applied in XFCE, and I am afraid XFCE has no such option.
So I ended up modifying
/etc/xdg/autostart/mintreport.desktop
by changing fromto
but I had to redo it after upgrading to 21.3 (Virginia) because the upgrade renamed the file.
Perhaps it is possible to make the Exec line conditional depending on desktop environment, but I don't know how to accomplish this. Any ideas?
A better solution would be for mintreport to wait a while after startup, before hastily reporting nonexistent issues. Either way, this is a manual workaround.
The text was updated successfully, but these errors were encountered: