So these packages then “appear” to be installed in ``/usr` just as if they had been in the core image?
I doubt that Plasma is running in some sort of container but even if it where it would need access to your home directory.
Exactly!
That is the default location of all application desktop files.
It would have a very empty launcher menu if it didn’t look into that.
That flag is provided from the C++ part of the widget.
I.e. ApplicationIntegration is a C++ object that was made available to QML.
That object is then also called when the calendar application needs to be launched, so just removing the flag check wouldn’t get you any closer to your goal.
Have you logged out and logged in again?
As far as I understand the flag will only be evaluated once and so installing during a session will not make it recheck again during the same session.
Looks like it. Since the OS is provided as a whole with each update, my guess is that the layered packages are stored separately and re-added to each updated image. Not 100% on that though.
I phrased this poorly. I meant that it would be different for an atomic distro because Plasma would cross the threshold of the “immutable” OS image and the rest of the filesystem.
Multiple times.
Is this code available? I would love to see how this flag is evaluated and if being in a read-only environment is stopping it from doing so properly.
the reason it has the merkuro icon is because it’s actually a hardlink of the merkuro desktop, but it needed the korganizer name so the digital clock would recognize it.
it should work equally well for the actual korganizer desktop file, as long as you have the kdepim-addons installed as well as korganizer.
Thanks for the link! I was struggling to find it. Although in the interim i did some testing and got it working!
I removed KOrganizer (and the symlink i had made earlier) and installed Merkuro and the widget got the button! However, it doesn’t work. Running Merkuro from terminal gets me this.
I then installed both in the same layered package and now clicking + Add ... opens KOrganizer! It only opens on today’s date though, even when selecting a date in the future/past. As a separate feature suggestion I would recommend adding support for that. (Also it’s not really an “add” button so much as an “edit” button, although I’m splitting hairs there)
After poking in the settings i got the calender events read up and it all works! Merkuro still doesn’t open though.
Thank you so much for your help! I do hope this illustrates my initial point though. This was very convoluted. I’ll keep this thread in mind and ping it again if i encounter any issues in the next week or so.
if you want it to use merkuro instead of korganizer then you need to spoof it as described in my notes.
korganizer installs a bunch of other things and one of those you still need (i think it was kaddressbook, don’t remember), but it will leave those essentials behind when you just uninstall korganizer.
i suppose if you left korganizer installed and just deleted the desktop file, that might work too since the hardlink operation just needs the link file (korganizer) to not exist in order to make the hardlink from the target (merkuro).
That is difficult in the current approach when you launch an application.
The application might not be able to do that from its command line and it might be different between the applications that can be launched.
As you said at least simple “add” function should be right in there, maybe with an option to launch a real organizer for editing of a selected event.
Which is hopefully easier to do cross-app.
The error suggests an unfulfilled dependency.
One of its UI files is attempting to load the QtLocation module but it is not found.
Probably a missing package dependency.
Debian/Ubuntu has the qml-module-qtlocation package for this, you’ll need to check how Fedora calls this
Maybe also report this to the Fedora packagers and even Bazzite.
An atomic distribution should probably have all modules of its main UI library installed by default.
No, that is because you have a version in which the check looks for the old name of Merkuro but Merkuro has already its new name.
@RocksoC is on a version in which these two names align.
I’m aware this would be an actual undertaking, as it would need to be implemented in KOrganizer/Merkuro and not just the widget. But doing so as a launch argument doesn’t seem like the biggest undertaking. Even if it was different between Merkuro and KOrganizer, you’d just need to check which one before tacking a launch argument onto it right?
In any case this is far from critical. Just a humble request
The package came from fedora’s repository. If that’s the case I should definitely report that. Thanks for the tip!
