Notifications appear in the middle of the screen

[wout]

Prerequisites

• I have searched open and closed issues for duplicates.

Describe the bug

I've just done a clean install of elementary OS and now notifications show up in the middle of the screen. It is as if a bunch of invisible notifications are created before the actual notification. So the notification slides in from the top but it's slightly phased, just as it would slide in when there is are multiple notifications. And that's also how it disappears.

It happens with notifications for all apps btw, it's not app-specific.

To Reproduce

This is a clean install, nothing unusual, so I'm not sure how to reproduce it.

Expected behavior

Notifications should be in the upper-right corner.

Screenshots or screen recordings

Platform Information

         eeeeeeeeeeeeeeeee            wout@Framey 
      eeeeeeeeeeeeeeeeeeeeeee         ----------- 
    eeeee  eeeeeeeeeeee   eeeee       OS: elementary OS 7 Horus x86_64 
  eeee   eeeee       eee     eeee     Host: Laptop (12th Gen Intel Core) A8 
 eeee   eeee          eee     eeee    Kernel: 6.2.0-26-generic 
eee    eee            eee       eee   Uptime: 1 day, 17 hours, 21 mins 
eee   eee            eee        eee   Packages: 1895 (dpkg), 57 (flatpak) 
ee    eee           eeee       eeee   Shell: bash 5.1.16 
ee    eee         eeeee      eeeeee   Resolution: 3000x2000, 3840x2160 
ee    eee       eeeee      eeeee ee   DE: Pantheon 
eee   eeee   eeeeee      eeeee  eee   WM: Mutter(Gala) 
eee    eeeeeeeeee     eeeeee    eee   Theme: io.elementary.stylesheet.mint [GTK3] 
 eeeeeeeeeeeeeeeeeeeeeeee    eeeee    Icons: elementary [GTK3] 
  eeeeeeee eeeeeeeeeeee      eeee     Terminal: io.elementary.t 
    eeeee                 eeeee       CPU: 12th Gen Intel i7-1280P (20) @ 4.700GHz 
      eeeeeee         eeeeeee         GPU: Intel Alder Lake-P 
         eeeeeeeeeeeeeeeee            Memory: 12543MiB / 64003MiB 

• I'm using the latest version from git that I've manually compiled
• I'm using the latest released stable version

[lenemter]

Can you provide more information on this. Is this happening with every single notification, or randomly? Is there any patterns when this happens?

[wout]

Hi, of course. Yes, it happens with every app. I've replicated it with notify-send in the attached video.

Also, this is coming from the syslog, which looks related:

Aug 26 07:52:58 Framey gala[2489]: NotificationStack.vala:139: NotificationStack: Notification window was null (probably removed during workspace transition?)
Aug 26 07:52:58 Framey gala[2489]: message repeated 6 times: [ NotificationStack.vala:139: NotificationStack: Notification window was null (probably removed during workspace transition?)]
Aug 26 07:52:58 Framey gala[2489]: A transition with name 'entry' already exists for the actor '<unnamed>[<MetaWindowActorX11>:0x5560030e9ed0]'
Aug 26 07:52:58 Framey gala[2489]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 26 07:52:58 Framey gala[2489]: A transition with name 'entry' already exists for the actor '<unnamed>[<MetaWindowActorX11>:0x5560030e9ed0]'
Aug 26 07:52:58 Framey gala[2489]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 26 07:52:58 Framey gala[2489]: A transition with name 'entry' already exists for the actor '<unnamed>[<MetaWindowActorX11>:0x5560030e9ed0]'
Aug 26 07:52:58 Framey gala[2489]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 26 07:52:58 Framey gala[2489]: A transition with name 'entry' already exists for the actor '<unnamed>[<MetaWindowActorX11>:0x5560030e9ed0]'
Aug 26 07:52:58 Framey gala[2489]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 26 07:52:58 Framey gala[2489]: A transition with name 'entry' already exists for the actor '<unnamed>[<MetaWindowActorX11>:0x5560030e9ed0]'
Aug 26 07:52:58 Framey gala[2489]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 26 07:52:58 Framey gala[2489]: A transition with name 'entry' already exists for the actor '<unnamed>[<MetaWindowActorX11>:0x5560030e9ed0]'
Aug 26 07:52:58 Framey gala[2489]: g_object_unref: assertion 'G_IS_OBJECT (object)' failed
Aug 26 07:52:58 Framey gala[2489]: clutter_animatable_get_actor: assertion 'CLUTTER_IS_ANIMATABLE (animatable)' failed
Aug 26 07:52:58 Framey gala[2489]: clutter_animatable_get_actor: assertion 'CLUTTER_IS_ANIMATABLE (animatable)' failed
Aug 26 07:53:02 Framey gala[2489]: clutter_animatable_get_actor: assertion 'CLUTTER_IS_ANIMATABLE (animatable)' failed
Aug 26 07:53:02 Framey gala[2489]: clutter_animatable_get_actor: assertion 'CLUTTER_IS_ANIMATABLE (animatable)' failed

That's for a single notify-send command by the way.

Let me know if you need anything else.

notifications.mkv.tar.gz

[lenemter]

Just installed OS 7 stable, updated it and I cannot reproduce the bug. Have you fully updated your system? What's the output of dpkg -s io.elementary.notifications | grep Version?

[wout]

I've installed the system on Tuesday and it's up-to date:

sudo apt update
...
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
All packages are up to date.

Version:

dpkg -s io.elementary.notifications | grep Version
Version: 7.0.1+r436+pkg9~ubuntu7.1

I have installed the exact same apps as before so nothing unusual there.

[TomiOhl]

I can confirm this is happening to me, too. I have never had such issues with the previous version of elementary/notifications.
It doesn't happen every time, it's mostly random, but today it's pretty constant since I've rebooted my machine

out.mp4

[lenemter]

@Marukesu @leolost2605 Do you have any ideas why this may happen?

[TomiOhl]

Additional info: if I hover over the misplaced notification, nothing happens. However, if I hover over the area where the notification should normally appear, the notification jumps there and i can interact (can be clicked, close button appears, swipe to dismiss works)

out.mp4

[Marukesu]

@lenemter maybe a gala bug? gala is the one handling positioning.

[lenemter]

I managed to reproduce the bug on daily build. I'll look into why the bug happens.

[danirabbit]

Should have been fixed in #1748