Bug 1390541 - mate-session killed by SIGSEGV - Live ISO Fedora-MATE_Compiz-Live-x86_64-25-20161031
Summary: mate-session killed by SIGSEGV - Live ISO Fedora-MATE_Compiz-Live-x86_64-25-2...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: mate-session-manager
Version: 25
Hardware: x86_64
OS: Linux
unspecified
low
Target Milestone: ---
Assignee: Wolfgang Ulbrich
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-01 10:58 UTC by Mike Simms
Modified: 2017-02-05 09:07 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-02-05 09:07:09 UTC
Type: Bug

Attachments (Terms of Use)
data directory contents for the issue (612.95 KB, application/x-gzip)
2016-11-01 10:58 UTC, Mike Simms 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Description Mike Simms 2016-11-01 10:58:42 UTC 
Created attachment 1216066 [details]
data directory contents for the issue

Description of problem: sigsegv kills mate-session-manager after logging into the live user session. doesn't affect overall operation of the Live ISO and anaconda installs the OS fine. so very low priority but a bug none the less.


Version-Release number of selected component (if applicable):mate-session-manager-1.16.0-1.fc25


How reproducible:consistently


Steps to Reproduce:
1.burn the ISO to DVD or flash to USB
2.verify the boot media using the test this media option
3.boot to the desktop from either grub entry

Actual results:system works okay but that error message is flashed up by the notification daemon and logged by ABRT


Expected results:no sigserv intervention


Additional info:possibly the attached is of no use. remote report and backtrace fails. I tried creating the offline report and it failed due to file lock errors after downloading and extracting the necessary devel files.
Comment 1 Wolfgang Ulbrich 2017-02-05 09:07:09 UTC 
I guess we can close this :-)
Note You need to log in before you can comment on or make changes to this bug.