SFOS 4.6 (Foreca / MeeCast): How to (re-)enable the weather infos in Events View

General
#8

I implemented the thing :smiley:

10 Likes
#9

For me, restarting homescreen wasn’t necessary.
I did pkcon as root first, then dconf as user…

1 Like
#10

Ah, neat. I assume on a 10iii?

1 Like
#11

Yes on Xperia 10 III and just confirm on 10 plus as well.

1 Like
#12

No on an xperia 10 ii

1 Like
#13

Tested on mine, MeeCast work for me.

It’s a 10 II dual sim

1 Like
#14

Tested on XA2, MeeCast Eventviewer works perfectly again. Thanks!

#15

This should be fixed by
harbour-meecast-event-1.1-2.armv7hl.rpm
(note the -2), which was released at OpenRepos on 25 May 2024.

If it is not fully fixed (i.e. if it does not work “out of the box”, after installing MeeCast Eventview 1.1-2), please report that, preferably in the extant issue thread at GitHub.

2 Likes
#16

Just downloaded this on my xa2 with 4.6 on it but i dont see anything. Am i missing a step to open it?

#17

Well, MeeCast Eventview alone does not do anything: IIRC you have to install MeeCast, meecast-demon and meecast-event in this order; i.e., I remember people running into issues when installing in a different order. If you want to play safe, remove all MeeCast related packages (find which ones are installed by
pkcon search name meecast | fgrep installed
then you can remove them one-by-one by
pkcon remove <package-name_without_version-number_etc>
), then install the recent packages from OpenRepos in aforementioned order (e.g. by Storeman, pkcon install or pkcon install-local) and reboot.

If still nothing is shown on the Eventsview page, please execute as regular user (i.e. nemo or defaultuser, but not root):

dconf write /desktop/lipstick-jolla-home/force_weather_loading true

After that, reboot again. Does it work now?

I assume doing this as root (as the spec file currently does) does not work. This can be fixed, if it is the reason.

6 Likes
#19

Will that be available in arch64 build? Or am I missing something? 10 III here

#20

Apparently not needed for arch64… or it would have been available.

#21

Did the dconf write and install jolla wetter widget commands. Uninstalled meecast packages (meecast, event viewer, daemon) then reinstalled again from Storeman. Restarted the UI from Settings/Utilities. All working like before, as expected, on 10iii.

2 Likes
#22

No, you are not, but Vlad apparently did miss to upload the i486 and aarch64 packages of harbour-meecast-event-1.1-2 at OpenRepos, and I did not see that.

So I asked him to do that, which BTW anybody else could have done, too.

1 Like
#23

Thank you for testing, though that was not really what I intended: I should have provided more concise instructions, hopefully the ones below are sufficient.

  1. Prerequisite: Now harbour-meecast-event-1.1-4 (i.e. release 4 of version 1.1) is available for all three architectures at OpenRepos.
  2. Remove the packages lipstick-jolla-home-qt5-weather-widget-settings, harbour-meecast-event, harbour-meecast-daemon and Meecast proper (harbour-meecast):
    pkcon remove lipstick-jolla-home-qt5-weather-widget-settings harbour-meecast-event harbour-meecast-daemon harbour-meecast
  3. Reset the dconf setting by executing in a terminal as regular user:
    dconf reset /desktop/lipstick-jolla-home/force_weather_loading
    (alternatively a setting it to false is also fine for this test:
    dconf write /desktop/lipstick-jolla-home/force_weather_loading false ).
  4. Install the packages harbour-meecast, harbour-meecast-daemon and harbour-meecast-event (i.e. do not explicitly install lipstick-jolla-home-qt5-weather-widget-settings and do not set the dconf key):
    pkcon install harbour-meecast harbour-meecast-daemon harbour-meecast-event
  5. Restart lipstick (i.e. the SailfishOS GUI) or reboot.
  6. Check if the Meecast widget is displayed in SailfishOS’ Eventsview

Please report your test-results here or at GitHub.

Big thanks to all testers who report back!

3 Likes
#24

@pvuorela, how should one revert this properly?
By resetting this dconf key (i.e. deleting it, AFAICS) or by setting it to false?

I.e.:

  1. dconf reset /desktop/lipstick-jolla-home/force_weather_loading
  2. dconf write /desktop/lipstick-jolla-home/force_weather_loading false
2 Likes
#25

The mentioned reset call could be considered better, though the difference is not big.

2 Likes
#26

Hmm, folowing @olf 's instructions I still can’tmake the widget appear in the Events feed. Perhaps it is something simple I have overlooked.
X10III and SFOS 4.6.0.13 and latest Meecast*
What can I check ?

#27

As addition to @olf procedure:

  1. Should you use Storeman and Chum please check versions of Meecast apps. There is something wrong and they installs interchangeable sometimes in wrong version.
  2. Check if you set Weather widget in SFOS->Settings-Events View
  3. Set at least one location in Meecast app.
1 Like
#28

Please mind that you are on an EA (i.e. beta) release of SailfishOS and hence you implicitly volunteered for testing: This is what we explicitly do here.

Still your feedback and testing is very valuable in order to get MeeCast Eventview into a state again, where it works out-of-the-box (i.e. without additional, manual steps after installing the RPM package), because neither Vasvlad nor I have a device with SailfishOS 4.6.0 on it.

NB: I just “love” Jolla for regularly introducing breaking changes unnecessarily, because they do not care at all about backward compatibility and the SailfishOS software ecosystem beyond their own components. They cause so much tedious work for zero gain, but as it is not them executing this work they obviously do not care; still, this erodes the SailfishOS software ecosystem more and more as developers are giving up this fight against the constant stream of breaking changes and consequently abandon their apps, while Jolla does not update completely outdated and insecure software components as Qt 5.6 from 2016, which is out of security support since March 2019; additionally a newer Qt would make programming much easier, especially of portable apps.

@kan_ibal, technically both Storeman / OpenRepos and the SailfishOS:Chum GUI application / the SailfishOS:Chum repository should be working fine. If you have any indication that this is not the case, please report that, preferably at the corresponding issue tracker at GitHub.
But as you can easily see, the SailfishOS:Chum repository currently contains a long outdated version of MeeCast (see e.g. Show sailfishos:chum / meecast - SailfishOS Open Build Service), which neither Vasvlad nor I submitted there.

To check which versions of MeeCast’s components are installed, execute
pkcon search name meecast | fgrep installed

Thank you @kan_ibal, these are definitely two valid points one has to ensure after installing Meecast Eventview for using or testing it.
May I add:
4. Do not miss to restart Lipstick or reboot after installing the MeeCast Eventview package or performing actions to fix MeeCast not being displayed in SailfishOS’ Eventsview.

@lakeboy: Yes, “latest Meecast” is a bit underspecified (as @kan_ibal already mentioned): Which version(s) from where? As you indicated to have followed my instructions above, I assume you installed the versions I mentioned (harbour-meecast-event-1.1-3, harbour-meecast-1.1.39-2 and harbour-meecast-daemon-1.10-2) from OpenRepos (e.g. by Storeman or pkcon). I have an idea why using these packages may not let Meecast Eventview work out-of-the-box, but as usual there could be many other reasons I do not think of.

In order to pinpoint what the culprit is, please perform two groups of checks:

  1. First examine the MeeCast installation you created by following my instructions to determine what still is not correct:
    • Is the dconf key set correctly? Please execute as regular user:
      dconf read /desktop/lipstick-jolla-home/force_weather_loading
      This should output true . Is it?
      If not, set it manually (by dconf write /desktop/lipstick-jolla-home/force_weather_loading true), restart Lipstick or reboot, and then check if MeeCast is displayed in the Eventsview.
    • Was the package lipstick-jolla-home-qt5-weather-widget-settings automatically installed? I do not believe this can go wrong, but a simple typo would render this belief futile.
      Edit: That was exactly the case! Should be fixed by harbour-meecast-event-1.1-4 at OpenRepos. Please retest then.
      Please execute:
      pkcon search name lipstick-jolla-home-qt5-weather-widget-settings
      If it is not installed, install it (pkcon install lipstick-jolla-home-qt5-weather-widget-settings), restart Lipstick or reboot, and then check if MeeCast is displayed in the Eventsview.
  2. The packages at OpenRepos are compiled for SailfishOS 4.5.0, as there is no Docker image of the Sailfish-SDK for 4.6.0 yet, because SailfishOS 4.6.0 is still in EA (i.e. beta) phase. While this should not make difference, it may. Hence I suggested to Vasvlad to also build the MeeCast packages at the Sailfish-OBS, which he did. Note that this is the first time he used the Sailfish-OBS (which is not trivial to configure correctly), hence these package may have (other) flaws. This is the top level directory for these newly generated packages: Index of /obs/home:/vasvlad To download the packages you need to descend two levels into sailfishos_chum_testing_3.1.0.12_%(arch)/%(arch)/, e.g. for aarch64 to Index of /obs/home:/vasvlad/sailfishos_chum_testing_3.1.0.12_aarch64/aarch64 You do not need to download the debuginfo package and harbour-meecast-lockscreen is a Patch to be utilised with Patchmanager (I wonder if this Patch still works).
    1. Execute steps 2 and 3 of my prior instructions in order to bring the installation in a pristine state, i.e. to remove the traces of former tries to install MeeCast Eventview successfully.
    2. Download the usual three packages (currently and for aarch 64: harbour-meecast-1.1.39.2-1.2.1.jolla.aarch64.rpm,
      harbour-meecast-daemon-1.1.39.2-1.2.1.jolla.aarch64.rpm and
      harbour-meecast-event-1.1.39.2-1.2.1.jolla.aarch64.rpm (Edit: This package does not automatically install lipstick-jolla-home-qt5-weather-widget-settings, a later one with a higher release number (than 1.2.1), but the same version number (1.1.39.2) will do that.)) from the architecture-specific OBS-download-directory into a (preferably freshly created) directory on your device (e.g. by curl -LO <URL>). NB: Yes the version numbers are are all the same, this is Jolla’s wonderful tar_git at the Sailfish-OBS rewriting all %release numbers and setting the %version-%release strings of sub-packages to the one of the primary package. Nevertheless, the package sizes indicate that these packages were built correctly.
    3. Then install these packages by (yes, pkcon install-local requires full RPM file names rsp. paths!):
      pkcon install-local harbour-meecast-1.1.39.2-1.2.1.jolla.aarch64.rpm harbour-meecast-daemon-1.1.39.2-1.2.1.jolla.aarch64.rpm harbour-meecast-event-1.1.39.2-1.2.1.jolla.aarch64.rpm
    4. After restarting Lipstick or rebooting, check if MeeCast is displayed in the Eventsview. If not, please execute the two steps from 1. (the first one in this post) to analyse what did not work.