Bug 31928

seems similar to this bug: https://bugs.mageia.org/show_bug.cgi?id=31908

CC: (none) => geiger.david68210

Marc, please say what desktop(s) you have installed.
And say whether 32|64-bit.

CC: (none) => lewyssmith

Trying on a multi-desktop Cauldron x64 system, Mate, confirm what Marc says.
 $ mate-notification-properties
does, after clicking 'Preview', indeed throw this in the journal:
 Mai 16 09:29:07 kernel: mate-notificati[5139]: segfault at 7f0a24dd0967 ip 00007f0de2500efd sp 00007ffcfa95a518 error 4 in libgobject-2.0.so.0.7600.2[7f0de24d7000+32000] likely on CPU 0 (core 0, socket 0)

However, I cannot confirm it only happens when clicking 'Preview'. I did not check the journal sooner.
BUT the application stays up, and the example notification displays correctly. Once; just the first time.
On closing it (not easily), it eventually popped a message:
"Error while displaying notification. Error calling StartServiceByName for org.freedesktop.Notifications: Timeout was reached. [Close button]".

After dismissing the error dialogue, the Close button works to dismiss the GUI, but leaves the console command ongoing (after the Preview error) for a long time before returning to the command prompt.

On re-launching it, and re-doing the Preview test, that does not work any more, and ends in the error dialogue. But no more segfaults - only the first.

The Close button works directly & correctly if used straight away.

since the process died there are no more crashes. if you start it manually, you get the same crash again.

I re-launched it repeatedly from the console. What do you mean by 'manually' if not that?
Please also answer comment 2 (re comment 1): desktop(s), architecture.
This is to see whether there is any connection between the two bugs.

Keywords: (none) => FOR_ERRATA9

we had an over the air collission.

I use mate and it is 64-bit.

We need to get this fixed, as mail notifications and others, like push-notifications use this feature.

For the moment, this does not look like comment 1, so assigning it as 'new' globally, since mate-notification-daemon is updated by different people.

CC: lewyssmith => (none)
Summary: mate notifications: crash => mate-notification-properties crash after Preview
Assignee: bugsquad => pkg-bugs

but in both cases the error is triggered by libgobject - and I'm pretty sure that it had worked a few weeks before.

Marc, is this still the case after the latest batch of updates to MATE around the end of last month?

CC: (none) => smelror

I have to restart the mashine for a complete verification, but it looks like it is fixed.

fixed

Status: NEW => RESOLVED
Resolution: (none) => FIXED

So nothing for errata.

Keywords: FOR_ERRATA9 => (none)
CC: (none) => fri

mate-notification daemon keeps crashing:

Aug 03 08:56:53 localhost.localdomain kernel: Code: 02 48 8d 05 c5 68 02 00 48 8b 34 e8 eb bc 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 48 85 ff 74 4b 48 8b 07 48 8>
Aug 03 08:56:53 localhost.localdomain kernel: mate-notificati[2493]: segfault at 7f4dcca3a6a2 ip 00007f4a47a59efd sp 00007ffdadc224f8 error 4 in libgobject-2.0.so.0.76>


This is really anoying, since I don't get any mail notifications if it crashes

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

The package lib64glib2.0_0 is on the live iso images, mate-notification-daemon
is not so it's only available on the classical iso images.

While important to get fixed, this can be fixed by an update post release,
so this is not a release blocker.

CC: (none) => davidwhodgins
Severity: normal => major

Added to errata, just in case this is not fixed prior to release.

Keywords: (none) => IN_ERRATA9

if this is relevant - it looks like mate-notification crashes, everytime mgaapplet-update-checker is executed. Maybe some bad notice is passed to the daemon and it crashes on that??