Clock applet has stopped showing weather information

Thanks for the warning, I thought that my weather applet had been compromised! I will wait patiently to hear from you experts to send out a notice letting us know when things will be back to normal...Glad I came here to see if anyone had info on what had happened. Thank you.

Hi, is the My-weather-indicator also on the list? It's stops almost daily and crashes with the start.

1 Like

May be related to this issue, as Atareo has declared NOAA weather source in the source code:

NOAA_WEATHER_URL = 'http://forecast.weather.gov/MapClick.php?lat=%s&lon=%s&FcstType=dwml'

but it may not used.
For example on my system the default source was OpenWeatherMap:

and application does not crash on my Ubuntu MATE 16.04 LTS system.

Try to select other weather source in the Preferences or move the config file to other directory with

 mv ~/.config/my-weather-indicator/my-weather-indicator.conf ~

and then restart the indicator by

/opt/extras.ubuntu.com/my-weather-indicator/bin/my-weather-indicator

Thank you for suggesting My Weather Indicator as alternative.


About weather in Clock applet we are still waiting for a fix on the aviationweather server side.

1 Like

I don't think post number 3 solved your issue. It just recognizes the issue and acknowledges a solution is being developed.

My Weather Indicator works fine on UM 18.04, but crashes after the start in UM 20.04. I don’t have currently a crash report, I deleted it.

Update 2020-06-24: problem is solved on server-side. No additional manual actions required.


For those who do not want to wait for a server-side fix, you can patch the MATE Weather library on binary level with single command below:

  • for 64-bit

    sudo sed -i 's|https://www.aviationweather.gov/adds/dataserver_current/httpparam|https://www.aviationweather.gov/adds/dataserver1_3/httpparam\x0\x0\x0\x0\x0|' $(readlink -f /usr/lib/x86_64-linux-gnu/libmateweather.so.1)

  • for 32-bit

    sudo sed -i 's|https://www.aviationweather.gov/adds/dataserver_current/httpparam|https://www.aviationweather.gov/adds/dataserver1_3/httpparam\x0\x0\x0\x0\x0|' $(readlink -f /usr/lib/i386-linux-gnu/libmateweather.so.1)

To revert the patch one can reinstall the corresponding package:

sudo apt-get install --reinstall libmateweather1
8 Likes

Hi @Norbert_X The crash stopped on its own at some point.

Do you also have a solution for the problem that the clock is hiding? I have enabled Show Widget, but it disappears after opening a program like behind a layer. I would have to choose "On Top" to have it visible, which is not practicable for me.

@Norbert_X: Since the system was updated 3 days ago, my Weather Indicator doesn't launch any more and crashes. I have copied some parts of it. Yesterday, it worked once, and today, it crashes again.

Can you tell me what Clock applet with weather report you use? I couldn't find it in Software Boutique and that other Software Install thing.

This is why the My-Weather-Indicator doesn't load. I have the impression that 20.04 is not good for my systems. 18.04 worked all marvellous, but there is something dodgy about 20.04.

ProblemType: Crash
CrashCounter: 1
CurrentDesktop: MATE
Date: Fri Dec 4 05:11:03 2020
ExecutablePath: /opt/extras.ubuntu.com/my-weather-indicator/bin/my-weather-indicator
ExecutableTimestamp: 1587923035
InterpreterPath: /usr/bin/python3.8
ProcCmdline: python3 /opt/extras.ubuntu.com/my-weather-indicator/bin/my-weather-indicator
ProcCwd: /home/mate
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcMaps:
00400000-00423000 r--p 00000000 08:02 11929634 /usr/bin/python3.8
00423000-006b7000 r-xp 00023000 08:02 11929634 /usr/bin/python3.8
006b7000-008f3000 r--p 002b7000 08:02 11929634 /usr/bin/python3.8
008f4000-008f5000 r--p 004f3000 08:02 11929634 /usr/bin/python3.8
008f5000-0093c000 rw-p 004f4000 08:02 11929634 /usr/bin/python3.8
0093c000-0095f000 rw-p 00000000 00:00 0
026f1000-031e3000 rw-p 00000000 00:00 0 [heap]

...

InstallationMedia: Ubuntu-MATE 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731)
JournalErrors:
-- Logs begin at Fri 2020-09-04 23:44:25 BST, end at Fri 2020-12-04 05:10:50 GMT. --
Dec 04 05:06:18 mate-K55VD kernel: MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details.
Dec 04 05:06:18 mate-K55VD kernel: #3
Dec 04 05:06:18 mate-K55VD kernel: pmd_set_huge: Cannot satisfy [mem 0xf8000000-0xf8200000] with a huge-page mapping due to MTRR override.
Dec 04 05:06:18 mate-K55VD kernel: ENERGY_PERF_BIAS: Set to 'normal', was 'performance'
Dec 04 05:06:18 mate-K55VD kernel: ACPI Error: Needed type [Reference], found [Integer] 0000000058e90d16 (20190816/exresop-66)
Dec 04 05:06:18 mate-K55VD kernel: ACPI Error: AE_AML_OPERAND_TYPE, While resolving operands for [Store] (20190816/dswexec-431)
Dec 04 05:06:18 mate-K55VD kernel: No Local Variables are initialized for Method [_PDC]
Dec 04 05:06:18 mate-K55VD kernel: Initialized Arguments for Method [_PDC]: (1 arguments defined for method invocation)
Dec 04 05:06:18 mate-K55VD kernel: Arg0: 00000000d7e96364 Buffer(12) 01 00 00 00 01 00 00 00
Dec 04 05:06:18 mate-K55VD kernel: ACPI Error: Aborting method _PR.CPU0._PDC due to previous error (AE_AML_OPERAND_TYPE) (20190816/psparse-529)
Dec 04 05:06:18 mate-K55VD kernel: Initramfs unpacking failed: Decoding failed
Dec 04 05:06:18 mate-K55VD kernel: platform eisa.0: EISA: Cannot allocate resource for mainboard
Dec 04 05:06:18 mate-K55VD kernel: platform eisa.0: Cannot allocate resource for EISA slot 1
Dec 04 05:06:18 mate-K55VD kernel: platform eisa.0: Cannot allocate resource for EISA slot 2
Dec 04 05:06:18 mate-K55VD kernel: platform eisa.0: Cannot allocate resource for EISA slot 3
Dec 04 05:06:18 mate-K55VD kernel: platform eisa.0: Cannot allocate resource for EISA slot 4
Dec 04 05:06:18 mate-K55VD kernel: platform eisa.0: Cannot allocate resource for EISA slot 5
Dec 04 05:06:18 mate-K55VD kernel: platform eisa.0: Cannot allocate resource for EISA slot 6
Dec 04 05:06:18 mate-K55VD kernel: platform eisa.0: Cannot allocate resource for EISA slot 7
Dec 04 05:06:18 mate-K55VD kernel: platform eisa.0: Cannot allocate resource for EISA slot 8
Dec 04 05:06:18 mate-K55VD kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000044F (\GPIS) (20190816/utaddress-204)
Dec 04 05:06:18 mate-K55VD kernel: ACPI Warning: SystemIO range 0x0000000000000428-0x000000000000042F conflicts with OpRegion 0x0000000000000400-0x000000000000047F (\PMIO) (20190816/utaddress-204)
Dec 04 05:06:18 mate-K55VD kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20190816/utaddress-204)
Dec 04 05:06:18 mate-K55VD kernel: ACPI Warning: SystemIO range 0x0000000000000540-0x000000000000054F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20190816/utaddress-204)
Dec 04 05:06:18 mate-K55VD kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20190816/utaddress-204)
Dec 04 05:06:18 mate-K55VD kernel: ACPI Warning: SystemIO range 0x0000000000000530-0x000000000000053F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20190816/utaddress-204)
Dec 04 05:06:18 mate-K55VD kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x000000000000057F (\GPIO) (20190816/utaddress-204)
Dec 04 05:06:18 mate-K55VD kernel: ACPI Warning: SystemIO range 0x0000000000000500-0x000000000000052F conflicts with OpRegion 0x0000000000000500-0x0000000000000563 (\GP01) (20190816/utaddress-204)
Dec 04 05:06:18 mate-K55VD kernel: lpc_ich: Resource conflict(s) found affecting gpio_ich
Dec 04 05:06:18 mate-K55VD kernel: r8169 0000:04:00.2: can't disable ASPM; OS doesn't have ASPM control
Dec 04 05:06:29 mate-K55VD kernel: nvidia: loading out-of-tree module taints kernel.
Dec 04 05:06:29 mate-K55VD kernel: nvidia: module license 'NVIDIA' taints kernel.
Dec 04 05:06:29 mate-K55VD kernel: Disabling lock debugging due to kernel taint
Dec 04 05:06:29 mate-K55VD kernel: NVRM: loading NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 (using threaded interrupts)
Dec 04 05:06:29 mate-K55VD kernel: ACPI Warning: _SB.PCI0.PEG0.PEGP._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20190816/nsarguments-59)
Dec 04 05:06:44 mate-K55VD udisksd[729]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
Dec 04 05:06:45 mate-K55VD kernel: kauditd_printk_skb: 25 callbacks suppressed
Dec 04 05:06:45 mate-K55VD lightdm[848]: Seat type 'xlocal' is deprecated, use 'type=local' instead
Dec 04 05:06:46 mate-K55VD udisksd[729]: Failed to load the 'mdraid' libblockdev plugin
Dec 04 05:06:50 mate-K55VD NetworkManager[711]: [1607058410.7425] sup-iface: failed to cancel p2p connect: P2P cancel failed
Dec 04 05:06:54 mate-K55VD systemd[1]: kerneloops.service: Found left-over process 968 (kerneloops) in control group while starting unit. Ignoring.
Dec 04 05:06:54 mate-K55VD systemd[1]: This usually indicates unclean termination of a previous run, or service implementation deficiencies.
Dec 04 05:06:58 mate-K55VD blueman-mechani[706]: gtk_icon_theme_get_for_screen: assertion 'GDK_IS_SCREEN (screen)' failed
Dec 04 05:07:01 mate-K55VD systemd-resolved[634]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Dec 04 05:07:01 mate-K55VD systemd-resolved[634]: Server returned error NXDOMAIN, mitigating potential DNS violation DVE-2018-0001, retrying transaction with reduced feature level UDP.
Dec 04 05:07:05 mate-K55VD lightdm[1048]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Dec 04 05:07:05 mate-K55VD lightdm[1048]: PAM adding faulty module: pam_kwallet.so
Dec 04 05:07:05 mate-K55VD lightdm[1048]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Dec 04 05:07:05 mate-K55VD lightdm[1048]: PAM adding faulty module: pam_kwallet5.so
Dec 04 05:07:13 mate-K55VD lightdm[1136]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or directory
Dec 04 05:07:13 mate-K55VD lightdm[1136]: PAM adding faulty module: pam_kwallet.so
Dec 04 05:07:13 mate-K55VD lightdm[1136]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or directory
Dec 04 05:07:13 mate-K55VD lightdm[1136]: PAM adding faulty module: pam_kwallet5.so
Dec 04 05:07:35 mate-K55VD pulseaudio[1059]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Dec 04 05:08:16 mate-K55VD lightdm[1136]: gkr-pam: unable to locate daemon control file
Dec 04 05:08:16 mate-K55VD pulseaudio[1059]: Error opening PCM device front:0: No such file or directory
Dec 04 05:08:21 mate-K55VD mate-session[1198]: WARNING: Unable to find provider '' of required component 'dock'
Dec 04 05:08:28 mate-K55VD notification-ar[1505]: GDBus.Error:org.freedesktop.DBus.GLib.ErrorError: Method invoked for RegisterStatusNotifierHost returned FALSE but did not set error
Dec 04 05:08:29 mate-K55VD clock-applet[1587]: Negative content width -7 (allocation 1, extents 4x4) while allocating gadget (node button, owner GtkToggleButton)
Dec 04 05:08:42 mate-K55VD pulseaudio[1192]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
NonfreeKernelModules: nvidia_modeset nvidia
Package: my-weather-indicator 0.9.5-0extras20.04.09 [origin: LP-PPA-atareao-atareao]

My main system is still Ubuntu MATE 16.04.7 LTS.
Here I see that My-Weather-Indicator did not load about for a week.
But at time of writing it loaded and shows the weather.

The Clock applet is a part of default installation of any Ubuntu MATE version.
To add Clock applet to MATE panel you have to:

  1. do right mouse click on MATE Panel,
  2. select Add to Panel, choose Clock
  3. do right mouse click on just added Clock applet
  4. select Preferences
  5. on General tab check Show weather checkbox
  6. on Location add needed location
  7. wait weather data to be shown in left side of applet (or click on Clock applet and them unfold Locations section)

On my test Ubuntu MATE 20.04 LTS VM with all updates installed both applets show weather normally.

2 Likes

Thanks @Norbert_X: it's the same clock that I already have added to show weekday and date, because since 20.04, you have only the time in the default applet.
I tried this one before, but it only finds locations in the US. [Update]: it found Bristol in England, but then the clock crashed with unknown region. After a restart, it worked with Bristol shown. Only problem is that Bristol is half an hour down the road and weather changes quickly here on the isles :slight_smile:

The My-Weather-Indication also worked fine in 18.04, but has got a problem with 20.04.

It looks like the Weather-Indicator update this morning fixed the issue. Hasn't disappeared so far. If that is true, than a big thank to who ever this fixed. Made my day :slight_smile:

I hate to revive this topic, but it seems the problem is back. Using Linux Mint Mate 21.2 (Linux 6.2.0-34-generic x86_64) and since a couple days the weather indicator is all blank. It used to work before. De-/reactivating the option within the clock panel did not help.

1 Like

Welcome @ubuntumatrose to the community!

The problem is as before - aviationweather.gov have reorganized their servers yet again, so the stream of metar data is now coming from a different place.

2 Likes

Welcome @z11 to the community!

You're right.
Luckily there is a patch for it. We're discussing that at the moment in this thread

You still have to apply the patch manually but I think that a fix will be in the updates within reasonable time because all ubuntu-MATE versions from 22.04 to 23.10 are affected.

2 Likes

The 20.04 here at home, and the 18.04 I have at work are also effected, and this is not recent for me, it's been going on for over a month. I just didn't feel like being the squeaky wheel that revived the topic.

I understand.

The problem is that the URL of the weatherstation (where the weather-app gets its info from) has changed. There is nothing that the Ubuntu-MATE devs can do about that. There has been a whole discussion about it that you can find here

The other problem is that this URL is hardcoded in the weather-app (actually, in its library libmateweather.so) and not in a config file.

That means that you either need an updated libmateweather.so file
or patch it manually.

Another problem is that 18.04 and 20.04 are no longer supported so there will not be an update of libmateweather.so for neither 18.04 nor 20.04

That leaves manually patching the libmateweather.so as only option.

Manually patching the libmateweather.so is discussed in the earlier mentioned link. You could try that if you feel you're up to it.

If you don't feel comfortable to manually patch that file then the only solution is to disable/uninstall the mate weather app and find a different app to replace it (which I think, reading from another thread, you already did :wink: )

2 Likes

Hi @psfal,

If you find a patch for 20.04 that works I'm looking for same. Anyone? Please let us know.

I know the sed command patch works on 22.04, 23.10 and even Debian 11 with Mate 1.24.1.

But not 20.04 and I tried everything I could think of. I don't have an 18.04 to test but I bet it's the same as 20.04.

2 Likes

Hi, @Bill_MI,

the workaround for Ubuntu MATE 20.04 is to remove the www. part from the new URL string.

If you are explicitly looking for a sed patch, try editing your patch string accordingly (remove www. --> 4 symbols AND append \x0\x0\x0\x0 --> 4 null characters), something like:
sudo sed -i 's|https://www.aviationweather.gov/adds/dataserver_current/httpparam|https://aviationweather.gov/cgi-bin/data/dataserver.php\x0\x0\x0\x0\x0\x0\x0\x0\x0\x0|' /usr/lib/x86_64-linux-gnu/libmateweather.so.1.6.9

I hope this helps

5 Likes