Bug 2280977

Created attachment 2033700 [details]
File: proc_pid_status

Created attachment 2033701 [details]
File: maps

Created attachment 2033702 [details]
File: limits

Created attachment 2033703 [details]
File: environ

Created attachment 2033704 [details]
File: open_fds

Created attachment 2033705 [details]
File: mountinfo

Created attachment 2033706 [details]
File: os_info

Created attachment 2033707 [details]
File: cpuinfo

Created attachment 2033708 [details]
File: core_backtrace

Created attachment 2033709 [details]
File: exploitable

Created attachment 2033710 [details]
File: dso_list

Created attachment 2033711 [details]
File: backtrace

Error seemed to occur while cold booting.  No noted effects during normal computer usage.


reporter:       libreport-2.17.15
type:           CCpp
journald_cursor: s=e32019fdc99c417c8cea200d9f564641;i=8bb82;b=9572023e4d4b4bbda4b94bac7743e096;m=512fb2a09;t=61655130ed552;x=c1346fa1b3067907
executable:     /usr/libexec/mate-notification-daemon
cmdline:        /usr/libexec/mate-notification-daemon --idle-exit
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/app-dbus\x2d:1.2\x2dorg.freedesktop.Notifications.slice/dbus-:1.2-org.freedesktop.Notifications
rootdir:        /
uid:            1000
kernel:         6.8.5-301.fc40.x86_64
package:        mate-notification-daemon-1.28.0-1.fc40
runlevel:       N 5
comment:        Error seemed to occur while cold booting.  No noted effects during normal computer usage.
reason:         mate-notification-daemon killed by SIGSEGV
backtrace_rating: 4
crash_function: g_type_check_instance_is_fundamentally_a

Touchpad right-button click does not behave as it should, and I have experienced that the computer freeze up, using it. May get mouse-right-click with exteral mouse, but that doesn't always behave either. 


reporter:       libreport-2.17.15
comment:        Touchpad right-button click does not behave as it should, and I have experienced that the computer freeze up, using it. May get mouse-right-click with exteral mouse, but that doesn't always behave either. 
kernel:         6.9.5-200.fc40.x86_64
crash_function: g_type_check_instance_is_fundamentally_a
type:           CCpp
rootdir:        /
executable:     /usr/libexec/mate-notification-daemon
uid:            1000
cmdline:        /usr/libexec/mate-notification-daemon
reason:         mate-notification-daemon killed by SIGSEGV
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
runlevel:       N 5
backtrace_rating: 4
journald_cursor: s=918f663c7b164d6b81b991f36b388e80;i=4334e;b=a8c26a6d85f2485eb7eb86459e762251;m=8e29109;t=61bc06e733b60;x=406f163f72ec7474
package:        mate-notification-daemon-1.28.0-1.fc40

Touchpad seem to be under control now, after changing a lot of settings - but dnfdragora update notification and a bunch of other mate-settings-daemon, also a lot of thing that have not been invoked or touched, like system-config-printer, compizConfig settings, color of the screen, randomly freeze the desktop. By removing dnfdagora from the panel, made me finally view movies, youtube, etc. uninterruptet or crashing for hours. 
 


reporter:       libreport-2.17.15
kernel:         6.9.5-200.fc40.x86_64
crash_function: g_type_check_instance_is_fundamentally_a
type:           CCpp
rootdir:        /
executable:     /usr/libexec/mate-notification-daemon
uid:            1000
cmdline:        /usr/libexec/mate-notification-daemon
reason:         mate-notification-daemon killed by SIGSEGV
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
runlevel:       N 5
backtrace_rating: 4
journald_cursor: s=918f663c7b164d6b81b991f36b388e80;i=4334e;b=a8c26a6d85f2485eb7eb86459e762251;m=8e29109;t=61bc06e733b60;x=406f163f72ec7474
package:        mate-notification-daemon-1.28.0-1.fc40

Upstream changed behaviour of m-n-d with mate-1.28 to support wayland session.
M-n-d is started now with session login via auto-start. Since this time i noticed very often abrt alarms.
But the old behaviour to start m-n-d via dbus session by application which send the notification is still active too.
For this reason the m-n-d will start again after a crash of the daemon.
So you can try to disable the auto-start in session with mate-session-properties tool.
This should improve the situation. The auto-start with session option is only needed for a wayland session in theory.
I filed out an upstream report already in september 2023 https://github.com/mate-desktop/mate-notification-daemon/issues/218
Here the daemon crashes when switching the desktop when a notification is running.
Apart from this i suggest to file out a report at upstream to ask them for a bug fix.

(In reply to Fred Erickson from comment #13)
> Error seemed to occur while cold booting.  No noted effects during normal
> computer usage.
> 
No, this is because abrt sends all crashes of previous session when booting again.
Abrt tries to confuse you, but a of users are thinking crashes are happen during boot ;-)

FEDORA-2024-3a1f1eeffa (mate-notification-daemon-1.28.0-2.fc40) has been submitted as an update to Fedora 40.
https://bodhi.fedoraproject.org/updates/FEDORA-2024-3a1f1eeffa

FEDORA-2024-3a1f1eeffa has been pushed to the Fedora 40 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-3a1f1eeffa`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-3a1f1eeffa

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

FEDORA-2024-3a1f1eeffa (mate-notification-daemon-1.28.0-2.fc40) has been pushed to the Fedora 40 stable repository.
If problem still persists, please make note of it in this bug report.

This is a recurrent chrash. I've had it hundreds of times already. Though I don't really know what may cause it.


reporter:       libreport-2.17.15
type:           CCpp
reason:         mate-notification-daemon killed by SIGSEGV
journald_cursor: s=d1328158102d4da4ae9b7e2ec79670e6;i=38a0;b=8a69c01a5c924dbb8528b189d67e9d72;m=6ca1028b84;t=623a1979cc245;x=5a3560a6e88dff67
executable:     /usr/libexec/mate-notification-daemon
cmdline:        /usr/libexec/mate-notification-daemon --idle-exit
cgroup:         0::/user.slice/user-1000.slice/user/app.slice/dbus-:1.2-org.freedesktop.Notifications
rootdir:        /
uid:            1000
kernel:         6.10.11-200.fc40.x86_64
package:        mate-notification-daemon-1.28.0-2.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: g_type_check_instance_is_fundamentally_a
comment:        This is a recurrent chrash. I've had it hundreds of times already. Though I don't really know what may cause it.

Just entered password after boot and whoops.


reporter:       libreport-2.17.15
type:           CCpp
reason:         mate-notification-daemon killed by SIGSEGV
journald_cursor: s=fc89ef0b00fc4dfeafe061f451de7446;i=8abd;b=aad95b020ed4474a9eee34e06ad8a52a;m=60f8b04f49;t=626c2fba4fc8f;x=1247d1f071c21469
executable:     /usr/libexec/mate-notification-daemon
cmdline:        /usr/libexec/mate-notification-daemon
cgroup:         0::/user.slice/user-1000.slice/session-2.scope
rootdir:        /
uid:            1000
kernel:         6.11.5-200.fc40.x86_64
package:        mate-notification-daemon-1.28.0-2.fc40
runlevel:       N 5
backtrace_rating: 4
crash_function: g_type_check_instance_is_fundamentally_a
comment:        Just entered password after boot and whoops.