Bug 416543

Summary: Krunner doesn't respect theme after reboots.
Product: [Plasma] krunner Reporter: Dashon <dashonwwIII>
Component: generalAssignee: Kai Uwe Broulik <kde>
Status: RESOLVED WORKSFORME    
Severity: normal CC: nate
Priority: NOR    
Version First Reported In: 5.17.5   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Picture of dolphin when krunner opens a folder after reboot.

Description Dashon 2020-01-21 16:51:48 UTC
Created attachment 125285 [details]
Picture of dolphin when krunner opens a folder after reboot.

SUMMARY
Opening dolphin, text files, and application through launchers or shortcuts work fine, but opening them with krunner specifically after rebooting seems to ignore the theme for varying amounts of time. I say varying amounts of time because sometimes it is just once other times it does it until it feels like stopping.

STEPS TO REPRODUCE
1. Reboot machine.
2. Open a file or folder or program such as system settings on your machine with krunner.

OBSERVED RESULT
Whatever it opens does not have the correct theme and instead defaults to breeze light.

EXPECTED RESULT
Whatever it opens, opens with the correct dark theme I have selected.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 31 
(available in About System)
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.64.0
Qt Version: 5.13.2

ADDITIONAL INFORMATION
After some degree of time or trying to open things with it, it eventually gets it right and everything is fine from that point onward.
Comment 1 Nate Graham 2020-01-21 18:12:55 UTC
I *think* this has already been fixed in Plasma 5.18 or Frameworks 5.66. Is there any chance you can try with Fedora Rawhide or another method to get slightly newer KDE packages?
Comment 2 Dashon 2020-01-21 19:38:29 UTC
(In reply to Nate Graham from comment #1)
> I *think* this has already been fixed in Plasma 5.18 or Frameworks 5.66. Is
> there any chance you can try with Fedora Rawhide or another method to get
> slightly newer KDE packages?

Sure I'll set up a virtual machine when I get out of classes later thanks for the reply.
Comment 3 Dashon 2020-01-22 01:23:12 UTC
(In reply to Nate Graham from comment #1)
> I *think* this has already been fixed in Plasma 5.18 or Frameworks 5.66. Is
> there any chance you can try with Fedora Rawhide or another method to get
> slightly newer KDE packages?

I'll try to get back to this tomorrow when I have more time just updating progress.
Comment 4 Dashon 2020-01-22 05:33:29 UTC
(In reply to Nate Graham from comment #1)
> I *think* this has already been fixed in Plasma 5.18 or Frameworks 5.66. Is
> there any chance you can try with Fedora Rawhide or another method to get
> slightly newer KDE packages?

I did end up getting around to using that vm of fedora rawhide and you are correct frameworks 5.66 does fix this issue. Thanks for the info. I guess it will be fixed for me when fedora workstation offers the package for update.
Comment 5 Nate Graham 2020-01-22 14:15:21 UTC
Great, thanks for verifying!
Comment 6 Dashon 2020-01-28 17:55:35 UTC
Wanted to reopen this because after the update to frameworks 5.66 on host machine the problem persists. However on a fresh install in a virtual machine the problem was not present. May be a problem on host machine.
Comment 7 Dashon 2020-02-26 21:38:43 UTC
The solution was to remove a package called Lmod