mate-screensaver crashes

[Rami Hakim]

Hello ,

This is the second time happening , at the first time I thought it simply crashed because whatever happened to it ,
But when it happens (I am not at keyboard when it happens) , I see 2 notifications , the first one that pop-up has crashed , the second one mate-screensaver has crashed , and I have no prompt for password when both of them crash

ERROR: apport (pid 19117) Mon Jul 22 14:32:02 2019: called for pid 19055, signal 5, core limit 0, dump mode 1
ERROR: apport (pid 19117) Mon Jul 22 14:32:02 2019: executable: /usr/lib/mate-notification-daemon/mate-notification-daemon (command line "/usr/lib/mate-notification-daemon/mate-notification-daemon")
ERROR: apport (pid 19117) Mon Jul 22 14:32:02 2019: debug: session gdbus call: (true,)

ERROR: apport (pid 19117) Mon Jul 22 14:32:03 2019: wrote report /var/crash/_usr_lib_mate-notification-daemon_mate-notification-daemon.1000.crash
ERROR: apport (pid 19187) Mon Jul 22 14:32:03 2019: called for pid 5169, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 19187) Mon Jul 22 14:32:03 2019: executable: /usr/bin/mate-screensaver (command line "/usr/bin/mate-screensaver --no-daemon")
ERROR: apport (pid 19187) Mon Jul 22 14:32:03 2019: debug: session gdbus call: (true,)

ERROR: apport (pid 19187) Mon Jul 22 14:32:12 2019: wrote report /var/crash/_usr_bin_mate-screensaver.1000.crash
ERROR: apport (pid 21680) Mon Jul 22 14:59:21 2019: called for pid 5771, signal 5, core limit 0, dump mode 1

ERROR: apport (pid 5036) Fri Jul 19 15:28:08 2019: called for pid 4971, signal 5, core limit 0, dump mode 1
ERROR: apport (pid 5036) Fri Jul 19 15:28:08 2019: executable: /usr/lib/mate-notification-daemon/mate-notification-daemon (command line "/usr/lib/mate-notification-daemon/mate-notification-daemon")
ERROR: apport (pid 5036) Fri Jul 19 15:28:08 2019: debug: session gdbus call: (true,)

ERROR: apport (pid 5036) Fri Jul 19 15:28:09 2019: wrote report /var/crash/_usr_lib_mate-notification-daemon_mate-notification-daemon.1000.crash
ERROR: apport (pid 5107) Fri Jul 19 15:28:09 2019: called for pid 2797, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 5107) Fri Jul 19 15:28:09 2019: executable: /usr/bin/mate-screensaver (command line "mate-screensaver")
ERROR: apport (pid 5107) Fri Jul 19 15:28:09 2019: debug: session gdbus call: (true,)

ERROR: apport (pid 5107) Fri Jul 19 15:28:17 2019: wrote report /var/crash/_usr_bin_mate-screensaver.1000.crash

I have the crash files if you need them , Or you could tell me what exactly you need from me or how to send you the dump crashes and whether they contain private information or not , please tell me
I set this as Security risk because once it crashes , you are free to go with the PC , and I don't know if someone manages to crash it will be able to bypass the login screen.

Screensaver crashes and it allows you to have control over the PC with no need for password or anything else.

Release 18.04.2 LTS (Bionic Beaver) 64-bit
Kernel Linux 4.18.0-25-generic x86_64
MATE 1.20.1
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.7
Architecture: amd64
CurrentDesktop: MATE
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-06-11 (48 days ago)
InstallationMedia: Ubuntu-MATE 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210)
Package: mate-screensaver 1.20.0-1
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 4.18.0-25.26~18.04.1-generic 4.18.20
Tags: bionic
Uname: Linux 4.18.0-25-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True

[Rami Hakim (ramihakim)]

I've been using 18.04 for about a year if that helps , it never happened , it only happened on those dates that are provided with the first post , I didn't add anything critical to the system , I don't know if the screensaver is crashing due to having 2 monitors (I've recently added a new monitor) , before about a month of the crashes

[Mike Salvatore (mikesalvatore)]

Hi Rami,

Can you use `apport-collect 1837389` to attach the logs to this bug report?

Thanks!

[Rami Hakim (ramihakim)]

apport information

[Rami Hakim (ramihakim)]

apport information

[Rami Hakim (ramihakim)]

apport information

[Rami Hakim (ramihakim)]

Hello Mike,

I have sent the bug report , in the bug report it says that my machine is 48 days old only , Indeed , I have switched PCs and installed a fresh install that day, but for usage I've been using it for about a year and so , Also the older PC was an Intel CPU if that makes any difference.

Thank you , inform me if you need more information.

[Mike Salvatore (mikesalvatore)]

Hi Rami,

Can you also use "apport-bug <CRASH_FILE>" to submit the crash file? This will create another bug, which I'll reference here once it's created.

Thanks,
Mike

[Rami Hakim (ramihakim)]

Hello again

I was only able to send the pop-up notification daemon as the log for the screen saver is not available , I get no such file or directory when trying to upload them , it's weird , where did that go ?

[Rami Hakim (ramihakim)]

I've tried to browse and see and yes they are gone , how could that happen ?

[Rami Hakim (ramihakim)]

I am sorry but somehow the crash files has disappeared from my PC , do you think it's something intentional ? or my system is compromised somehow? I only provided the pop-up notification crash file , mate-screensaver crash file is not there.

[Mike Salvatore (mikesalvatore)]

Hi Rami,

Apport cleans up crash files about every 7 days. If the crash file is older than 7 days, it's possible that it was automatically removed. Have you checked in /var/crash to ensure it's not still there?

[Rami Hakim (ramihakim)]

Hey Mike,

I believe so they have been removed , and yes they are older than 7 days by now of the events
I have checked indeed and I didn't find

Is there any way I could recover it?

Thank you

[Mike Salvatore (mikesalvatore)]

Short of using forensic tools, I'm not aware of any way to recover it. Just send the crash files the next time it happens.

[Rami Hakim (ramihakim)]

I will sure do that , thank you Mike for your assistance.
And I am sorry for the disappearance of the log , lesson learned.

[Eduardo Barretto (ebarretto)]

Marking it Incomplete. If the issue happens again, please update the status.

[Rami Hakim (ramihakim)]

Thank you , will do.

[Rami Hakim (ramihakim)]

It happened again I have attached the file and uploaded it
thanks.

[Rami Hakim (ramihakim)]

I have reported the file using apport.

[Rami Hakim (ramihakim)]

And also pop-up notification daemon has crashed along the screensaver like before.

[Marc Deslauriers (mdeslaur)]

Can I make this bug public so the MATE developers can see it?

[Rami Hakim (ramihakim)]

BUMP

[Seth Arnold (seth-arnold)]

You can see the attachments on the web version of the bug:

https://bugs.launchpad.net/ubuntu-mate/+bug/1837389

Look for the box "Bug attachments" in the right column.

Thanks

[Rami Hakim (ramihakim)]

It's happening more and more frequently , now it's happening different , one screen is locked , the second is open , but unclickable but you could see everything on screen and switch between Windows

You can't lock the second screen unless you open the first one(it might be black screen)
So one screen is locked with security and the second is not locked , or half locked.

[Rami Hakim (ramihakim)]

It's crashing more and more , while the PC is locked , app notification indicator crashes , screen-saver crashes , it opens the way for anyone , the timer of the screensaver stop working also

Today it happened differently as I explained in the earlier post , one screen is blacked out , the second is open , clicking whatever on the keyboard doesn't bring the blacked out to a state where you can put the password even though the second screen is opened , but yet the first one is locked out

So I had to put the password while the second one is blacked out , inorder to be able to lock the system again.

[Rami Hakim (ramihakim)]

Thanks.