Wireless Keyboard: SHIFT-P suddenly not working

I’m using an old Apple Wireless Keyboard (can’t find model number – it’s the white and clear plastic model).

Yesterday the SHIFT-P (capital ‘P’) functionality suddenly stopped working. I didn’t spill anything or otherwise mess with the keyboard (that I am aware of).

The “p” key works fine but in order to type a capital ‘P’, I need to set the caps lock. I looked at the ‘keyboard viewer’ and SHIFT-P doesn’t trigger an event. No other keys appear to be affected.

Anyone seen this before?

UPDATE ok, so it’s the left SHIFT key which is failing with the letter “P” but the right SHIFT key works fine with it. Weird. I understand total hardware failure but why would the left SHIFT key only fail with the letter “P”?

(the irony here: I am using the wireless keyboard because my MacBook Pro laptop battery swelled up and knocked out the Y, U, I, O keys. I replaced the battery but that didn’t fix the keyboard issue)

Fortigate to Azure – working VPN suddenly stops working

I have a FortiGate 60E that I successfully used to create a VPN to an Azure virtual network (see here). It had the 6.0.4 firmware.

Recently, I updated the Fortigate firmware to 6.2.0 and the VPN came up correctly, but after a few days, it started to not route anything. The VPN was still up on both sides, but I couldn’t see anything. Rebooting the Fortigate had no effect.

So I deleted all the VPN objects on Azure and recreated everything from scratch. It worked again… for a while.

So I decided to downgrade the Fortigate to 6.0.5 (released a few days ago), without changing anything in Azure. It worked again… for around 15 hours. And now it’s down.

I will try downgrading again to 6.0.4, but I am starting to think that may not be it. When I redid everything in Azure, it came back up. The second time I did nothing in Azure, and it came back up. So I am starting to think that it’s something on the Fortigate side that brings up the VPN but then messes up.

On another, older Fortigate I have the exact same setup (but firmware 5.6.8), and it has been working flawlessly for weeks.

— EDIT

On further inspection, I looked at the logs and found a Dead Peer Detection error:

enter image description here

The tunnel_stats events before that show sent and received bytes (bidirectional), but all tunnel_stats events after the dpd_failure only show sent bytes, but received bytes are always zero.

— END EDIT

Any ideas are welcome!

EKS suddenly failing with disk pressure

We have an EKS cluster with two t3.small nodes with 20Gi of emhemeral storage. The cluster runs only two small Nodejs (node:12-alpine) applications for now.

This worked perfectly for a few weeks, and now suddenly we’re getting disk pressure errors.

$   kubectl describe nodes Name:               ip-192-168-101-158.ap-southeast-1.compute.internal Roles:              <none> Labels:             beta.kubernetes.io/arch=amd64                     beta.kubernetes.io/instance-type=t3.small                     beta.kubernetes.io/os=linux                     failure-domain.beta.kubernetes.io/region=ap-southeast-1                     failure-domain.beta.kubernetes.io/zone=ap-southeast-1a                     kubernetes.io/hostname=ip-192-168-101-158.ap-southeast-1.compute.internal Annotations:        node.alpha.kubernetes.io/ttl: 0                     volumes.kubernetes.io/controller-managed-attach-detach: true CreationTimestamp:  Sun, 31 Mar 2019 17:14:58 +0800 Taints:             node.kubernetes.io/disk-pressure:NoSchedule Unschedulable:      false Conditions:   Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message   ----             ------  -----------------                 ------------------                ------                       -------   OutOfDisk        False   Sun, 12 May 2019 12:22:47 +0800   Sun, 31 Mar 2019 17:14:58 +0800   KubeletHasSufficientDisk     kubelet has sufficient disk space available   MemoryPressure   False   Sun, 12 May 2019 12:22:47 +0800   Sun, 31 Mar 2019 17:14:58 +0800   KubeletHasSufficientMemory   kubelet has sufficient memory available   DiskPressure     True    Sun, 12 May 2019 12:22:47 +0800   Sun, 12 May 2019 06:51:38 +0800   KubeletHasDiskPressure       kubelet has disk pressure   PIDPressure      False   Sun, 12 May 2019 12:22:47 +0800   Sun, 31 Mar 2019 17:14:58 +0800   KubeletHasSufficientPID      kubelet has sufficient PID available   Ready            True    Sun, 12 May 2019 12:22:47 +0800   Sun, 31 Mar 2019 17:15:31 +0800   KubeletReady                 kubelet is posting ready status Addresses:   InternalIP:   192.168.101.158   ExternalIP:   54.169.250.255   InternalDNS:  ip-192-168-101-158.ap-southeast-1.compute.internal   ExternalDNS:  ec2-54-169-250-255.ap-southeast-1.compute.amazonaws.com   Hostname:     ip-192-168-101-158.ap-southeast-1.compute.internal Capacity:  attachable-volumes-aws-ebs:  25  cpu:                         2  ephemeral-storage:           20959212Ki  hugepages-1Gi:               0  hugepages-2Mi:               0  memory:                      2002320Ki  pods:                        11 Allocatable:  attachable-volumes-aws-ebs:  25  cpu:                         2  ephemeral-storage:           19316009748  hugepages-1Gi:               0  hugepages-2Mi:               0  memory:                      1899920Ki  pods:                        11 System Info:  Machine ID:                 ec2aa2ecfbbbdd798e2da086fc04afb6  System UUID:                EC2AA2EC-FBBB-DD79-8E2D-A086FC04AFB6  Boot ID:                    62c5eb9d-5f19-4558-8883-2da48ab1969c  Kernel Version:             4.14.106-97.85.amzn2.x86_64  OS Image:                   Amazon Linux 2  Operating System:           linux  Architecture:               amd64  Container Runtime Version:  docker://18.6.1  Kubelet Version:            v1.12.7  Kube-Proxy Version:         v1.12.7 ProviderID:                  aws:///ap-southeast-1a/i-0a38342b60238d83e Non-terminated Pods:         (0 in total)   Namespace                  Name    CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE   ---------                  ----    ------------  ----------  ---------------  -------------  --- Allocated resources:   (Total limits may be over 100 percent, i.e., overcommitted.)   Resource                    Requests  Limits   --------                    --------  ------   cpu                         0 (0%)    0 (0%)   memory                      0 (0%)    0 (0%)   ephemeral-storage           0 (0%)    0 (0%)   attachable-volumes-aws-ebs  0         0 Events:   Type     Reason                Age                    From                                                         Message   ----     ------                ----                   ----                                                         -------   Warning  ImageGCFailed         5m15s (x333 over 40h)  kubelet, ip-192-168-101-158.ap-southeast-1.compute.internal  (combined from similar events): failed to garbage collect required amount of images. Wanted to free 1423169945 bytes, but freed 0 bytes   Warning  EvictionThresholdMet  17s (x2809 over 3d4h)  kubelet, ip-192-168-101-158.ap-southeast-1.compute.internal  Attempting to reclaim ephemeral-storage   Name:               ip-192-168-197-198.ap-southeast-1.compute.internal Roles:              <none> Labels:             beta.kubernetes.io/arch=amd64                     beta.kubernetes.io/instance-type=t3.small                     beta.kubernetes.io/os=linux                     failure-domain.beta.kubernetes.io/region=ap-southeast-1                     failure-domain.beta.kubernetes.io/zone=ap-southeast-1c                     kubernetes.io/hostname=ip-192-168-197-198.ap-southeast-1.compute.internal Annotations:        node.alpha.kubernetes.io/ttl: 0                     volumes.kubernetes.io/controller-managed-attach-detach: true CreationTimestamp:  Sun, 31 Mar 2019 17:15:02 +0800 Taints:             node.kubernetes.io/disk-pressure:NoSchedule Unschedulable:      false Conditions:   Type             Status  LastHeartbeatTime                 LastTransitionTime                Reason                       Message   ----             ------  -----------------                 ------------------                ------                       -------   OutOfDisk        False   Sun, 12 May 2019 12:22:42 +0800   Thu, 09 May 2019 06:50:56 +0800   KubeletHasSufficientDisk     kubelet has sufficient disk space available   MemoryPressure   False   Sun, 12 May 2019 12:22:42 +0800   Thu, 09 May 2019 06:50:56 +0800   KubeletHasSufficientMemory   kubelet has sufficient memory available   DiskPressure     True    Sun, 12 May 2019 12:22:42 +0800   Sat, 11 May 2019 21:53:44 +0800   KubeletHasDiskPressure       kubelet has disk pressure   PIDPressure      False   Sun, 12 May 2019 12:22:42 +0800   Sun, 31 Mar 2019 17:15:02 +0800   KubeletHasSufficientPID      kubelet has sufficient PID available   Ready            True    Sun, 12 May 2019 12:22:42 +0800   Thu, 09 May 2019 06:50:56 +0800   KubeletReady                 kubelet is posting ready status Addresses:   InternalIP:   192.168.197.198   ExternalIP:   13.229.138.38   InternalDNS:  ip-192-168-197-198.ap-southeast-1.compute.internal   ExternalDNS:  ec2-13-229-138-38.ap-southeast-1.compute.amazonaws.com   Hostname:     ip-192-168-197-198.ap-southeast-1.compute.internal Capacity:  attachable-volumes-aws-ebs:  25  cpu:                         2  ephemeral-storage:           20959212Ki  hugepages-1Gi:               0  hugepages-2Mi:               0  memory:                      2002320Ki  pods:                        11 Allocatable:  attachable-volumes-aws-ebs:  25  cpu:                         2  ephemeral-storage:           19316009748  hugepages-1Gi:               0  hugepages-2Mi:               0  memory:                      1899920Ki  pods:                        11 System Info:  Machine ID:                 ec27ee0765e86a14ed63d771073e63fb  System UUID:                EC27EE07-65E8-6A14-ED63-D771073E63FB  Boot ID:                    7869a0ee-dc2f-4082-ae3f-42c5231ab0e3  Kernel Version:             4.14.106-97.85.amzn2.x86_64  OS Image:                   Amazon Linux 2  Operating System:           linux  Architecture:               amd64  Container Runtime Version:  docker://18.6.1  Kubelet Version:            v1.12.7  Kube-Proxy Version:         v1.12.7 ProviderID:                  aws:///ap-southeast-1c/i-0bd4038f4dade284e Non-terminated Pods:         (0 in total)   Namespace                  Name    CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE   ---------                  ----    ------------  ----------  ---------------  -------------  --- Allocated resources:   (Total limits may be over 100 percent, i.e., overcommitted.)   Resource                    Requests  Limits   --------                    --------  ------   cpu                         0 (0%)    0 (0%)   memory                      0 (0%)    0 (0%)   ephemeral-storage           0 (0%)    0 (0%)   attachable-volumes-aws-ebs  0         0 Events:   Type     Reason                Age                      From                                                         Message   ----     ------                ----                     ----                                                         -------   Warning  EvictionThresholdMet  5m40s (x4865 over 3d5h)  kubelet, ip-192-168-197-198.ap-southeast-1.compute.internal  Attempting to reclaim ephemeral-storage   Warning  ImageGCFailed         31s (x451 over 45h)      kubelet, ip-192-168-197-198.ap-southeast-1.compute.internal  (combined from similar events): failed to garbage collect required amount of images. Wanted to free 4006422937 bytes, but freed 0 bytes 

I’m not entirely sure how to debug this issue, but it feels like K8s is not able to delete old unused Docker images on the nodes. Anyway to verify this assumption? Any other thoughts?

Macbook Pro suddenly running extremely slow

I have a 2010 2.66Ghz Intel Core 2 Duo MacBook Pro running Sierra with 8 GB RAM and 128 GB SSD.

The SSD and RAM were changed in 2013.

The macbook pro was running amazingly well for its age and I was quite happy with it until yesterday. When suddenly while I was typing and on battery power, the screen went blank though the Macbook was still on (as I hear the fan humming and see the keyboard lights on).

After that I tried to force restart it using the power button. But it won’t boot. I tried resetting the PRAM, NVRAM, and SMC controllers then restarted. Now it restarts but has become extremely slow.

The SSD is encrypted and as far as the SSD decryption password login screen and apple logo with loading screen after that the macbook pro behaves as expected and is very fast.

But once it goes to desktop it slows down like crazy. I am unable to even launch any programs. Once I was able to launch activity monitor and see that the CPU was running at 95% and kernel_task was taking up 400% or something.

I haven’t been able to check the RAM (but I suppose the RAM should be fine if it boots up and loads the OS?)

I also tried to boot using a USB drive MacOS backup disk and that too is extremely slow and in fact even slower than the inbuilt SSD boot up that I am unable to do anything.

The computer isnt heating up very badly or anything. On switching on the power light blinks 5 times and it doesn’t detect the battery (but that may be because I tried to remove the battery and put it back again and I believe I damaged the battery sensing cable or pins I guess just adjacent to where the battery cable and pins itself go on the mother board) as pressing the button to show power left on battery shows no lights now and I am stil able to run the macbook taking away the external power source only after I boot up.

What could be wrong?

XMind 8 suddenly stopped working on Ubuntu 18.04 LTS after .ini fix

After I upgraded Ubuntu to 18.04 from 16.04, XMind 8 (update8-linux) stopped working so I ran across a fix that consisted in adding a few lines to the .ini file. Everything was working great for a few months (even I created .desktop entry so I could launch the app from the dock). Until last week I couldn’t open XMind anymore. The error prompt says to look at the .log file and this is the output:

!SESSION 2019-04-25 22:01:01.176 ----------------------------------------------- eclipse.buildId=R3.7.8.201807240049 java.version=11.0.2 java.vendor=Oracle Corporation BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US Framework arguments:  -eclipse.keyring @user.home/.xmind/secure_storage_linux Command-line arguments:  -os linux -ws gtk -arch x86_64 -data ../workspace -eclipse.keyring @user.home/.xmind/secure_storage_linux  !ENTRY org.xmind.cathy 1 0 2019-04-25 22:01:03.880 !MESSAGE Skip unrecognized command line argument: '-eclipse.keyring'  !ENTRY org.xmind.cathy 1 0 2019-04-25 22:01:03.881 !MESSAGE Skip unrecognized command line argument: '@user.home/.xmind/secure_storage_linux'  !ENTRY org.eclipse.osgi.compatibility.state.nl_ko 2 0 2019-04-25 22:01:04.019 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_ko [846]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_zh_TW 2 0 2019-04-25 22:01:04.019 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_zh_TW [851]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_fr 2 0 2019-04-25 22:01:04.019 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_fr [843]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_pt_BR 2 0 2019-04-25 22:01:04.019 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_pt_BR [847]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_it 2 0 2019-04-25 22:01:04.019 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_it [844]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_da 2 0 2019-04-25 22:01:04.020 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_da [840]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_ar 2 0 2019-04-25 22:01:04.020 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_ar [839]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_ja 2 0 2019-04-25 22:01:04.020 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_ja [845]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_es 2 0 2019-04-25 22:01:04.020 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_es [842]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_zh 2 0 2019-04-25 22:01:04.020 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_zh [850]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_ru 2 0 2019-04-25 22:01:04.020 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_ru [848]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_de 2 0 2019-04-25 22:01:04.020 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_de [841]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi.compatibility.state.nl_sl 2 0 2019-04-25 22:01:04.021 !MESSAGE Could not resolve module: org.eclipse.osgi.compatibility.state.nl_sl [849]   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   Unresolved requirement: Fragment-Host: org.eclipse.osgi.compatibility.state   !ENTRY org.eclipse.osgi 4 0 2019-04-25 22:01:04.022 !MESSAGE Application error !STACK 1 org.eclipse.e4.core.di.InjectionException: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct     at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:386)     at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:294)     at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)     at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultHeadlessContext(E4Application.java:490)     at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createDefaultContext(E4Application.java:504)     at org.eclipse.e4.ui.internal.workbench.swt.E4Application.createE4Workbench(E4Application.java:203)     at org.eclipse.ui.internal.Workbench$  5.run(Workbench.java:626)     at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)     at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)     at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)     at org.xmind.cathy.internal.CathyApplication.start(CathyApplication.java:137)     at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)     at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:388)     at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)     at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)     at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)     at java.base/java.lang.reflect.Method.invoke(Method.java:566)     at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)     at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)     at org.eclipse.equinox.launcher.Main.run(Main.java:1519)     at org.eclipse.equinox.launcher.Main.main(Main.java:1492) Caused by: java.lang.NoClassDefFoundError: javax/annotation/PostConstruct     at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:151)     at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:375)     ... 23 more Caused by: java.lang.ClassNotFoundException: javax.annotation.PostConstruct cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612     at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398)     at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)     at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)     at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)     at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)     ... 25 more  !ENTRY org.eclipse.e4.ui.workbench 4 0 2019-04-25 22:01:04.033 !MESSAGE FrameworkEvent ERROR !STACK 0 java.lang.NoClassDefFoundError: javax/annotation/PreDestroy     at org.eclipse.e4.core.internal.di.InjectorImpl.disposed(InjectorImpl.java:426)     at org.eclipse.e4.core.internal.di.Requestor.disposed(Requestor.java:154)     at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$  ContextInjectionListener.update(ContextObjectSupplier.java:78)     at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111)     at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.handleInvalid(TrackableComputationExt.java:74)     at org.eclipse.e4.core.internal.contexts.EclipseContext.dispose(EclipseContext.java:176)     at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.dispose(EclipseContextOSGi.java:106)     at org.eclipse.e4.core.internal.contexts.osgi.EclipseContextOSGi.bundleChanged(EclipseContextOSGi.java:139)     at org.eclipse.osgi.internal.framework.BundleContextImpl.dispatchEvent(BundleContextImpl.java:903)     at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)     at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)     at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEventPrivileged(EquinoxEventPublisher.java:213)     at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:120)     at org.eclipse.osgi.internal.framework.EquinoxEventPublisher.publishBundleEvent(EquinoxEventPublisher.java:112)     at org.eclipse.osgi.internal.framework.EquinoxContainerAdaptor.publishModuleEvent(EquinoxContainerAdaptor.java:156)     at org.eclipse.osgi.container.Module.publishEvent(Module.java:476)     at org.eclipse.osgi.container.Module.doStop(Module.java:634)     at org.eclipse.osgi.container.Module.stop(Module.java:498)     at org.eclipse.osgi.container.SystemModule.stop(SystemModule.java:191)     at org.eclipse.osgi.internal.framework.EquinoxBundle$  SystemBundle$  EquinoxSystemModule$  1.run(EquinoxBundle.java:165)     at java.base/java.lang.Thread.run(Thread.java:834) Caused by: java.lang.ClassNotFoundException: javax.annotation.PreDestroy cannot be found by org.eclipse.e4.core.di_1.6.0.v20160319-0612     at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:398)     at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:361)     at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:353)     at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)     at java.base/java.lang.ClassLoader.loadClass(ClassLoader.java:521)     ... 21 more 

I tried changing between JDK versions and distributions (oracle and openjdk) but nothing worked. I tried modifying the .ini file again, and it still didn’t work. Is there any fix to this error? Thanks for your time.

Why Facebook profile images suddenly became so slow

I have an android app that worked well. Users are signing through Facebook. I have a recyclerview showing lists of users profile photos..

Don’t know what happened, suddenly this list is very slow loaded.. very slow up to 20 seconds.. to load 10 photos..

this is the url i’m using.

http://graph.facebook.com/<fbId>/picture?type=square

I really don’t know what happened.. Tried to fetch with small size 100X100, tried to stop using Picasso for loading and develop my own async task. But it is not the loading problem.. it is somehow Facebook.

Anyone ?