eclipse.platform.swt
eclipse.platform.swt copied to clipboard
eclipse-platform
GTK4: Eclipse crashes after installing webkit.
Environment: Red Hat Enterprise Linux 10.0 (Coughlan) Windowing System: Wayland GTK: GTK4
Initially i did not had webkit. Eclipse was running fine but it was complaining missing webkit and Notification View has error part control.
https://github.com/user-attachments/assets/2fc33299-a1f3-47c8-9b58-c15eff35191d
So I installed webkit.
rpm -qa | sort | grep webkit
webkit2gtk4.1-2.47.3-2.el10_0.x86_64
webkit2gtk4.1-devel-2.47.3-2.el10_0.x86_64
webkitgtk6.0-2.47.3-2.el10_0.x86_64
webkitgtk6.0-devel-2.47.3-2.el10_0.x86_64
BrowserExample seems to work. Though it did not render default URL on startup if i enter other URL it renders content.
https://github.com/user-attachments/assets/8754be6b-a786-489e-9b45-adf3fcc6ddf9
But when I launch eclipse and it tries to open Notification View it crashes the eclipse completely.
https://github.com/user-attachments/assets/fc053ced-e1ee-4980-8260-400927e712de
Log from console.
./eclipse &
[1] 152621
WARNING: SWT_GTK4 does not support splash screen yet. Therefore it has been disabled. To suppress this message launch with -nosplash
user@localhost:~/Downloads/eclipse-committers-2025-06-R-linux-gtk-x86_64/eclipse$ CompileCommand: exclude org/eclipse/jdt/internal/core/dom/rewrite/ASTRewriteAnalyzer.getExtendedRange bool exclude = true
Aug 29, 2025 1:49:26 PM org.apache.aries.spifly.BaseActivator log
INFO: Registered provider org.slf4j.simple.SimpleServiceProvider of service org.slf4j.spi.SLF4JServiceProvider in bundle slf4j.simple
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.645: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.646: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.646: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.646: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.844: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.846: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.850: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.850: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.851: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.851: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.851: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.851: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.851: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.851: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.851: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.851: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.941: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.941: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.941: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.941: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.942: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.942: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.942: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:27.942: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:29.630: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:29.630: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:29.630: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:29.630: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:29.630: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:29.630: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:29.956: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:29.956: gtk_widget_compute_point: assertion 'GTK_IS_WIDGET (widget)' failed
** (Eclipse:152641): CRITICAL **: 13:49:33.337: swt_fixed_remove: assertion 'GTK_IS_WIDGET(widget)' failed
** (Eclipse:152641): CRITICAL **: 13:49:33.662: swt_fixed_remove: assertion 'GTK_IS_WIDGET(widget)' failed
** (Eclipse:152641): CRITICAL **: 13:49:33.942: swt_fixed_remove: assertion 'GTK_IS_WIDGET(widget)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:35.275: invalid (NULL) pointer instance
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:35.275: g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
** (Eclipse:152641): CRITICAL **: 13:49:35.433: swt_fixed_remove: assertion 'GTK_IS_WIDGET(widget)' failed
** (Eclipse:152641): CRITICAL **: 13:49:35.502: swt_fixed_remove: assertion 'GTK_IS_WIDGET(widget)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:35.794: invalid (NULL) pointer instance
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:35.796: g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(Eclipse:152641): Atk-CRITICAL **: 13:49:35.796: atk_object_notify_state_change: assertion 'ATK_IS_OBJECT (accessible)' failed
Warning: NLS missing message: MarketplacePage_favorites in: org.eclipse.epp.internal.mpc.ui.wizards.messages
(Eclipse:152641): Gtk-WARNING **: 13:49:36.578: Trying to snapshot SwtFixed 0x7f7e320b7190 without a current allocation
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_ref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.449: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.450: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.450: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.450: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.450: invalid (NULL) pointer instance
(Eclipse:152641): GLib-GObject-CRITICAL **: 13:49:41.450: g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed
(Eclipse:152641): Atk-CRITICAL **: 13:49:41.450: atk_object_notify_state_change: assertion 'ATK_IS_OBJECT (accessible)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:41.628: gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:41.629: gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:41.629: gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:41.630: gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:41.630: gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:41.631: gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:41.631: gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:41.631: gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed
(Eclipse:152641): Gtk-CRITICAL **: 13:49:41.632: gtk_widget_unparent: assertion 'GTK_IS_WIDGET (widget)' failed
** (Eclipse:152641): CRITICAL **: 13:49:41.634: swt_fixed_remove: assertion 'GTK_IS_WIDGET(widget)' failed
** (Eclipse:152641): CRITICAL **: 13:49:42.392: swt_fixed_remove: assertion 'GTK_IS_WIDGET(widget)' failed
** (Eclipse:152641): CRITICAL **: 13:49:42.734: swt_fixed_remove: assertion 'GTK_IS_WIDGET(widget)' failed
** (Eclipse:152641): CRITICAL **: 13:49:44.035: swt_fixed_remove: assertion 'GTK_IS_WIDGET(widget)' failed
** (Eclipse:152641): CRITICAL **: 13:49:45.254: swt_fixed_remove: assertion 'GTK_IS_WIDGET(widget)' failed
(process:2): Gtk-WARNING **: 13:49:45.404: Failed to open display
** (Eclipse:152641): ERROR **: 13:49:45.447: readPIDFromPeer: Unexpected short read from PID socket
I don't know if I miss some dependency here or is it a bug.
Via -Dorg.eclipse.oomph.setup.notification=false in the eclipse.ini (on a line all by itself after the line with -vmargs) you can suppress notifications. Of course that doesn't fix the issue, e.g., it's likely that Javadoc hovers won't work.
Are you really running the latest version of Eclipse/SWT? Can you provide details about exactly what you've downloaded, i.e., what version you have installed?
I am running below eclipse package:
Eclipse IDE for Eclipse Committers (includes Incubating components)
Version: 2025-06 (4.36.0)
Build id: 20250605-1316
On GTK3 everything works fine.. This happens only when I set SWT_GTK4=1.
@merks Thank you.. Your disable notification option worked. It no longer opens Notification View on startup and I can keep eclipse alive now.. Background: I have installed a fresh RHEL-10 VM and started trying out eclipse enabling GTK4. My doubt is I may be missing some dependent package(On OS) also but I don't know what it is.. My plan is to check what are all working/not working on GTK4 so that I can report/fix them.
Also the OS i am using is hosted on Virtual Machine Manager-4.1.0. I am not sure If it can have any influence.
Also the OS i am using is hosted on Virtual Machine Manager-4.1.0. I am not sure If it can have any influence.
If the GTK3 + webkit works and GTK4 + webkit crashes, it is most likely not VM issue, but some native code or dependency issue related to the specific installed GTK4 + webkit versions.
I don't know what Notification view is, but I would recommend to look at the code of it, extract related pieces to a standalone SWT snippet and attach here so we can see what could be the problem and which part of the Notification view code causes the trouble.
It's quite a basic implementation using the browser:
https://github.com/eclipse-oomph/oomph/blob/a4fd02c80a50c0312e2ac26559a32c25de978d38/plugins/org.eclipse.oomph.setup.editor/src/org/eclipse/oomph/setup/presentation/NotificationViewPart.java#L172-L215
Eventually it sets a URL:
https://github.com/eclipse-oomph/oomph/blob/a4fd02c80a50c0312e2ac26559a32c25de978d38/plugins/org.eclipse.oomph.setup.editor/src/org/eclipse/oomph/setup/presentation/NotificationViewPart.java#L168
Given @akurtakov is doing lots of GTK4 work it would be in everyone's best interest to use the very latest Eclipse. Given you get this notification you are definitely not using the latest Eclipse so do not have the latest GTK4 support.
Eventually it sets a URL:
@raghucssit : can you please comment out this line & test? I've seen in the past that webkit sometimes fails to render specific html constructs because of missing native support of some functionality on the graphics card driver & related code.
Which display driver is installed? NVidia closed source or nouveau?
it would be in everyone's best interest to use the very latest Eclipse.
Correct. Raghu, for all GTK4 related work please always use latest nightly SDK build you can get from https://download.eclipse.org/eclipse/downloads/
FYI, here is an example of the URL is would open (with URL query parameters depending the host IDE):
https://www.eclipse.org/setups/notification/milestone/?product-id=org.eclipse.epp.package.committers.product&product-name=Eclipse%20IDE&application-id=org.eclipse.ui.ide.workbench&bundle-id=org.eclipse.epp.package.committers&bundle-version=4.37.0.20250821-0636&java.vendor=Eclipse%20Adoptium&java.version=21.0.4&color=%23000000ff&background-color=%23f8f8f8ff
As per https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/10.0_release_notes/removed-features -
WebKitGTK is removed in RHEL 10
The WebKitGTK web browser engine is removed in RHEL 10. As a consequence, you can no longer build applications that depend on WebKitGTK. Desktop applications other than Mozilla Firefox can no longer display web content. There is no alternative web browser engine provided in RHEL 10.
This puts a big question - how does one installs webkitgtk there (as there is no official one), how uptodate the installed version is, does the installed version has proper integration for any customizations that RHEL could have done in components webkitgtk depends on and so on. Aka that would be very long story that will dedicate someone to deep dive into RHEL 10 system to figure out. From my side - there are plenty of other issues that apply to all distros thus more important to get fixed. P.S. One might be experiencing on RHEL 10 a bug that happens on all systems too but as RHEL 10 is not easy to try system such a statement has to be proven first.
Aka that would be very long story that will dedicate someone to deep dive into RHEL 10 system to figure out.
As a paid enterprise user of RHEL I would expect that we should get support from Red Hat and we will escalate the problem if it will be not solved.
Desktop applications other than Mozilla Firefox can no longer display web content. There is no alternative web browser engine provided in RHEL 10.
Btw, do you know how GTK4 applications are supposed to embed browsers in RHEL 10? The link only says Firefox is to be used on desktop but doesn't say if it is supposed to be used also as embedded engine in GTK4.
AFAIK the recommended way is to ship your desktop app as Flatpak .
Hmm. We have a native Linux ~5 GB application that consists of ~10.000.000 lines of code and ~100 of different binaries (not only Eclipse), all closely tied to a specific RHEL version with specific rpm's on top and has its own way to install / update / redistribute etc. I doubt we will want to convert deployment to Flatpack only because of the browser engine is missing in RHEL 10.
A while back there was an attempt to bring chromium to SWT (natively) and it seems there are example to use it with GTK3/4 here:
- https://github.com/chromiumembedded/cef/issues/3922
So maybe that would be an alternative for REHL 10 system, of course it is some efforts but basically similar to IE11 versus Edge on Windows if this means WebKit will not be supported anymore on the long run.
But of course it will require some dedicated support from some people to implement/support it.
I would like to set expectations right without any preference on the browser engine - as long as you ship a browser engine be ready to ship updates to users/customers on weekly basis ( https://app.opencve.io/cve/?product=chrome&vendor=google , https://app.opencve.io/cve/?vendor=mozilla , https://app.opencve.io/cve/?vendor=microsoft&product=edge ) . Everything is doable (given enough resources) but is there any one ready to invest that much into delivering embedded browser engine with Eclipse/SWT ?
Providing an embeddable browser engine is a task for the Operating System nowadays as they are almost an operating system themselves IMO.
P.S. I'm putting aside the questions of installation size - embedding chromium (back when it was tried) literally made the whole Eclipse SDK be less than half of the tarball (https://www.eclipse.org/lists/platform-swt-dev/msg08385.html) and the question about system integration of such browser (e.g. access to certificates, crypto, .....) and on and on.
Providing an embeddable browser engine is a task for the Operating System nowadays as they are almost an operating system themselves IMO
But isn't the discussion often to have "free of choice" for a browser? So one would need a generic (embedded) API and the OS then would need to allow plug into this different engines, what does not sound like it would be the case here. And it seems REHL 10 is actually going in the other direction with dropping webkit from the OS.
What makes me wonder if one could not compile an own version of libwebkit2gtk for SWT usage on such system, does i really needs to be provided by the OS (independent of the issues with bugfixes you mentioned of course).
For example we have the JustJ project that is shipping embedable JVM (that's also quite large and getting many updates) so maybe a similar approach for a browser engine would be suitable so it does not have to live in SWT project I think.
As per https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/10/html/10.0_release_notes/removed-features -
WebKitGTK is removed in RHEL 10 The WebKitGTK web browser engine is removed in RHEL 10. As a consequence, you can no longer build applications that depend on WebKitGTK. Desktop applications other than Mozilla Firefox can no longer display web content. There is no alternative web browser engine provided in RHEL 10.This puts a big question - how does one installs webkitgtk there (as there is no official one), how uptodate the installed version is, does the installed version has proper integration for any customizations that RHEL could have done in components webkitgtk depends on and so on. Aka that would be very long story that will dedicate someone to deep dive into RHEL 10 system to figure out. From my side - there are plenty of other issues that apply to all distros thus more important to get fixed. P.S. One might be experiencing on RHEL 10 a bug that happens on all systems too but as RHEL 10 is not easy to try system such a statement has to be proven first.
Yes. webkit is removed from RHEL main repos but it is available from EPEL repo. I configured EPEL repo and installed it from there.. I did not specifically install any other dependencies. Below are the steps to install webkit on RHEL-10.
sudo dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-10.noarch.rpm
sudo dnf update
dnf search webkit (This search should show webkit)
sudo dnf install webkit2gtk
sudo dnf install webkitgtk6.0 webkitgtk6.0-devel
sudo dnf install webkit2gtk4.1 webkit2gtk4.1-devel
I downloaded latest nightly build and installed oomph. Notification View does not come up automatically when i launch eclipse in GTK3 and GTK4 both. Build:
On GTK3 I can explicitly open the Notification View from Show View dialog but it remains empty.
On GTK4, I cannot use eclipse at all. No toolbar icons does any action, No menu items does any action and they don't print any log also. But when I tries to open Quick Access there is an error in log.
java.lang.UnsatisfiedLinkError: 'long org.eclipse.swt.internal.gtk3.GTK3.gtk_bin_get_child(long)'
at org.eclipse.swt.internal.gtk3.GTK3.gtk_bin_get_child(Native Method)
at org.eclipse.swt.widgets.ToolItem.updateStyle(ToolItem.java:1594)
at org.eclipse.swt.widgets.ToolBar.setForegroundGdkRGBA(ToolBar.java:686)
at org.eclipse.swt.widgets.Control.setForeground(Control.java:5564)
at org.eclipse.jface.dialogs.PopupDialog.applyForegroundColor(PopupDialog.java:1462)
at org.eclipse.jface.dialogs.PopupDialog.applyForegroundColor(PopupDialog.java:1467)
at org.eclipse.jface.dialogs.PopupDialog.applyForegroundColor(PopupDialog.java:1467)
at org.eclipse.jface.dialogs.PopupDialog.applyColors(PopupDialog.java:1358)
at org.eclipse.jface.dialogs.PopupDialog.createContents(PopupDialog.java:712)
at org.eclipse.jface.window.Window.create(Window.java:431)
at org.eclipse.ui.internal.quickaccess.QuickAccessDialog.lambda$0(QuickAccessDialog.java:224)
Another important thing is browser works fine on GTK4 eclipse. And the Notification URL also loads. It looks like Browser itself works.. I will debug this Notification View and check later.