Bug 389927 - if redshift plasmoid enabled, and main redshift package removed, plasmashell fails to start
Summary: if redshift plasmoid enabled, and main redshift package removed, plasmashell ...
Status: VERIFIED WAITINGFORINFO
Alias: None
Product: plasmashell
Classification: Plasma
Component: generic-crash (other bugs)
Version First Reported In: 5.11.5
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-05 20:17 UTC by Tom Chiverton
Modified: 2018-02-10 14:47 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Tom Chiverton 2018-02-05 20:17:23 UTC 
* install redshift and the plasmoid

* place the plasmoid on the task bar.

* logout and back in again

* redshift appears on task bar

* sudo dpkg -r redshift 

(removes package with no errors)

* logout and back in again

no plasma task bar appears (!)

Plasmashell should tolerate plasmoid failures without crashing.
Comment 1 David Edmundson 2018-02-05 20:46:07 UTC 
We can't have plugins without the drawbacks of having plugins. If you have code executing in your process, there is nothing we can do to prevent freezes or blocks.

I do have some WIP on out-of-process plasmoids, but that is not within in the scope of a bug report. 

Please do file a bug with the redshift applet maintainers.
Comment 2 Tom Chiverton 2018-02-10 14:47:30 UTC 
I think you misunderstand ?

Where's the bug tracking a fix ?

You are right you can fix this by out-of-process plasmoids.

But a simpler and maybe more immediate fix would be making the redshift plasmoid explicitly and safely check dependencies and do something safe if they are not met, surely ?