Open canoon opened 3 years ago
While using the control center's "popup notifications" applet and keeping a preview notification showing, neither turning off nor removing my secondary monitor affected the notification. Were you displaying the notification on the monitor that was being removed by any chance? I was not
Yeah I had set the monitor to one that was disconnected.
If I move the notification to the secondary monitor, it does indeed disappear rather than move to the primary monitor if I disconnect the secondary monitor, though a terminal running mate-notification-properties to invoke it does not catch any error messages. Not sure where you are seeing those. Anyway, removing a monitor should move the notification to the remaining monitor as everything else moves over
Those messages are from mate-notification-daemon not mate-notification-properties. I was originally just seeing them in ~/.local/share/sddm/xorg-session.log but obviously that depends on what display manager you are using.
I don't have sddm as window manager, didn't get t anything like that error in .xsession-errors so not sure if its the same. Different WMs might respond differently to a monitor being removed
I can't exactly explain why it's changed now but I'm getting the error out of journalctl -f now. It seems like it's now run from dbus???.
-> % sudo journalctl -f
-- Journal begins at Tue 2020-12-15 21:17:59 AEDT. --
[snip]
Jun 25 13:50:28 canoon mate-notificati[188948]: gdk_monitor_get_display: assertion 'GDK_IS_MONITOR (monitor)' failed
Jun 25 13:50:28 canoon mate-notificati[188948]: gdk_display_get_n_monitors: assertion 'GDK_IS_DISPLAY (display)' failed
Jun 25 13:50:28 canoon mate-notificati[188948]: gdk_monitor_get_display: assertion 'GDK_IS_MONITOR (monitor)' failed
Jun 25 13:50:28 canoon mate-notificati[188948]: gdk_display_get_n_monitors: assertion 'GDK_IS_DISPLAY (display)' failed
Jun 25 13:50:28 canoon systemd-coredump[189009]: [🡕] Process 188948 (mate-notificati) of user 1000 dumped core.
Stack trace of thread 188948:
#0 0x0000556e1d7d96ab n/a (mate-notification-daemon + 0xc6ab)
#1 0x0000556e1d7d9f5b notify_stack_add_window (mate-notification-daemon + 0xcf5b)
#2 0x0000556e1d7d7d99 n/a (mate-notification-daemon + 0xad99)
#3 0x00007f5911603acd n/a (libffi.so.7 + 0x6acd)
#4 0x00007f591160303a n/a (libffi.so.7 + 0x603a)
#5 0x00007f5912414d4e g_cclosure_marshal_generic (libgobject-2.0.so.0 + 0x18d4e)
#6 0x00007f591240eddf g_closure_invoke (libgobject-2.0.so.0 + 0x12ddf)
#7 0x00007f5912437fbd n/a (libgobject-2.0.so.0 + 0x3bfbd)
#8 0x0000556e1d7d5d37 n/a (mate-notification-daemon + 0x8d37)
#9 0x00007f591256791d n/a (libgio-2.0.so.0 + 0x11191d)
#10 0x00007f591254d1ad n/a (libgio-2.0.so.0 + 0xf71ad)
#11 0x00007f591231af30 g_main_context_dispatch (libglib-2.0.so.0 + 0x53f30)
#12 0x00007f591236eb59 n/a (libglib-2.0.so.0 + 0xa7b59)
#13 0x00007f591231a593 g_main_loop_run (libglib-2.0.so.0 + 0x53593)
#14 0x00007f591293212f gtk_main (libgtk-3.so.0 + 0x1da12f)
#15 0x0000556e1d7d40b2 main (mate-notification-daemon + 0x70b2)
#16 0x00007f5911fe1b25 __libc_start_main (libc.so.6 + 0x27b25)
#17 0x0000556e1d7d415e _start (mate-notification-daemon + 0x715e)
Stack trace of thread 188950:
#0 0x00007f59120adb2f __poll (libc.so.6 + 0xf3b2f)
#1 0x00007f591236eae8 n/a (libglib-2.0.so.0 + 0xa7ae8)
#2 0x00007f591231a593 g_main_loop_run (libglib-2.0.so.0 + 0x53593)
#3 0x00007f59125585b8 n/a (libgio-2.0.so.0 + 0x1025b8)
#4 0x00007f59123490c1 n/a (libglib-2.0.so.0 + 0x820c1)
#5 0x00007f59118b1259 start_thread (libpthread.so.0 + 0x9259)
#6 0x00007f59120b85e3 __clone (libc.so.6 + 0xfe5e3)
Stack trace of thread 188951:
#0 0x00007f59120adb2f __poll (libc.so.6 + 0xf3b2f)
#1 0x00007f591236eae8 n/a (libglib-2.0.so.0 + 0xa7ae8)
#2 0x00007f5912318781 g_main_context_iteration (libglib-2.0.so.0 + 0x51781)
#3 0x00007f5912f65ebe n/a (libdconfsettings.so + 0x5ebe)
#4 0x00007f59123490c1 n/a (libglib-2.0.so.0 + 0x820c1)
#5 0x00007f59118b1259 start_thread (libpthread.so.0 + 0x9259)
#6 0x00007f59120b85e3 __clone (libc.so.6 + 0xfe5e3)
Stack trace of thread 188949:
#0 0x00007f59120adb2f __poll (libc.so.6 + 0xf3b2f)
#1 0x00007f591236eae8 n/a (libglib-2.0.so.0 + 0xa7ae8)
#2 0x00007f5912318781 g_main_context_iteration (libglib-2.0.so.0 + 0x51781)
#3 0x00007f59123187d2 n/a (libglib-2.0.so.0 + 0x517d2)
#4 0x00007f59123490c1 n/a (libglib-2.0.so.0 + 0x820c1)
#5 0x00007f59118b1259 start_thread (libpthread.so.0 + 0x9259)
#6 0x00007f59120b85e3 __clone (libc.so.6 + 0xfe5e3)
Stack trace of thread 188952:
#0 0x00007f59120b318d syscall (libc.so.6 + 0xf918d)
#1 0x00007f591236906b g_cond_wait_until (libglib-2.0.so.0 + 0xa206b)
#2 0x00007f59122ea8b3 n/a (libglib-2.0.so.0 + 0x238b3)
#3 0x00007f59122eaa44 g_async_queue_timeout_pop (libglib-2.0.so.0 + 0x23a44)
#4 0x00007f591234bd2a n/a (libglib-2.0.so.0 + 0x84d2a)
#5 0x00007f59123490c1 n/a (libglib-2.0.so.0 + 0x820c1)
#6 0x00007f59118b1259 start_thread (libpthread.so.0 + 0x9259)
#7 0x00007f59120b85e3 __clone (libc.so.6 + 0xfe5e3)
Edit: Just to clarify sddm is a display manager afaik I'm just using whatever mate has by default as a wm.
I didn't find any of this in journalctl on my system, in fact outputting it to a file, opening that in Pluma and searching for 'gdk_display_get_n_monitors' returned no matches at all
Weird. Thanks heaps for looking into it anyway. Out of curiosity what are you running?
Debian Unstable, rather hacked. Local builds all of MATE, compiz, the kernel, and some security stuff
@lukefromdc
While using the control center's "popup notifications" applet and keeping a preview notification showing, neither turning off nor removing my secondary monitor affected the notification. Were you displaying the notification on the monitor that was being removed by any chance? I was not
Thank you! I've been struggling for a few days with my broken notifications which worked when second monitor was connected but not when disconnected. Your comment was a great hint.
With second monitor disconnected I opened Ubuntu's Popup Notifications and checked "Use Active Monitor" -> then "Preview" -> it worked (a notification showed up). Without this options checked I encountered the following error message:
gdbus.error.freedesktop.dbus.error.noreply: message recipient disconnected from message bus without replying
I was using my second monitor as primary and "Use Active Monitor" checkbox unchecked because I wanted notifications to show up on this second screen. Notification manager probably remembered this even though I disconnected second monitor. However it should not because when no external monitors are plugged in then the laptop's screen should be a primary monitor.
Thank you, I've just wanted to share my problem and solution in case somebody will have the same problem in the future.
I know for certain I tested that, notifications just came back to my primary screen same as any icon dragged over would
On 12/26/2021 at 6:22 AM, "javaDeveloperKid" @.***> wrote:
@.***
While using the control center's "popup notifications" applet and keeping a preview notification showing, neither turning off nor removing my secondary monitor affected the notification. Were you displaying the notification on the monitor that was being removed by any chance? I was not
Thank you! I've been struggling for a few days with my broken notifications which worked when second monitor was connected but not when disconnected. Your comment was a great hint.
With second monitor disconnected I opened Ubuntu's Popup Notifications and checked "Use Active Monitor" -> then "Preview" -it worked (a notification showed up). Without this options checked I encountered the following error message:
gdbus.error.freedesktop.dbus.error.noreply: message recipient disconnected from message bus without replying
I was using my second monitor as primary and "Use Active Monitor" checkbox unchecked because I wanted notifications to show up on this second screen. Notification manager probably remembered this even though I disconnected second monitor. However it should not because when no external monitors are plugged in then the laptop's screen should be a primary monitor.
Thank you, I've just wanted to share my problem and solution in case somebody will have the same problem in the future.
-- Reply to this email directly or view it on GitHub: https://github.com/mate-desktop/mate-notification- daemon/issues/200#issuecomment-1001159521 You are receiving this because you were mentioned.
Message ID: <mate-desktop/mate-notification- @.***>
Expected behaviour
Not to crash
Actual behaviour
mate-notification-daemon crashes with version 1.24.2, with version 1.25.1 just this message is printed out
(mate-notification-daemon:182258): Gdk-CRITICAL **: 18:15:29.829: gdk_monitor_get_display: assertion 'GDK_IS_MONITOR (monitor)' failed
(mate-notification-daemon:182258): Gdk-CRITICAL **: 18:15:29.829: gdk_display_get_n_monitors: assertion 'GDK_IS_DISPLAY (display)' failed
Which I believe still indicates a bug
Steps to reproduce the behaviour
MATE general version
1.24.1
Package version
1.24.2 Also tried with 1.25.1
Linux Distribution
Arch Linux
Link to bugreport of your Distribution (requirement)
I can raise it if you like but it looks definitively like an upstream issue I suspect this line here should check also if monitor_id is NULL.
This is running with mate-notification-daemon-1.24.2.tar.xz