Bug 995873

Summary: [abrt] mate-screensaver-1.6.0-2.fc19: _dbus_header_get_byte_order: Process /usr/libexec/mate-screensaver-dialog was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: John Lewis <jlewis>
Component: mate-screensaverAssignee: Dan Mashal <dan.mashal>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: bugzilla, dan.mashal, derstaz, glad08, phr-redhat, raveit65.sun, rdieter, rhack, samtygier, shanemikel1, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:ee58fe87073d75413a8dbd4437bbed4545c48ced
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-12 08:48:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
core_backtrace from screensaver crash none

Description John Lewis 2013-08-11 17:16:44 UTC 
Version-Release number of selected component:
mate-screensaver-1.6.0-2.fc19

Additional info:
reporter:       libreport-2.1.6
backtrace_rating: 4
cmdline:        /usr/libexec/mate-screensaver-dialog --status-message= --enable-switch
crash_function: _dbus_header_get_byte_order
executable:     /usr/libexec/mate-screensaver-dialog
kernel:         3.10.5-201.fc19.x86_64
runlevel:       N 5
uid:            1000
var_log_messages: Aug 11 01:57:48 john-samsung-550-chromebook abrt[14805]: Saved core dump of pid 14801 (/usr/libexec/mate-screensaver-dialog) to /var/tmp/abrt/ccpp-2013-08-11-01:57:48-14801 (28962816 bytes)

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _dbus_header_get_byte_order at dbus-marshal-header.c:178
 #1 _dbus_header_get_field_basic at dbus-marshal-header.c:1370
 #2 dbus_message_get_reply_serial at dbus-message.c:1091
 #3 _dbus_connection_queue_received_message_link at dbus-connection.c:501
 #4 _dbus_transport_queue_messages at dbus-transport.c:1157
 #5 do_reading at dbus-transport-socket.c:851
 #6 socket_do_iteration at dbus-transport-socket.c:1162
 #7 _dbus_transport_do_iteration at dbus-transport.c:976
 #8 _dbus_connection_do_iteration_unlocked at dbus-connection.c:1234
 #9 _dbus_connection_block_pending_call at dbus-connection.c:2415
Comment 1 John Lewis 2013-08-11 17:16:50 UTC 
Created attachment 785421 [details]
File: backtrace
Comment 2 John Lewis 2013-08-11 17:16:53 UTC 
Created attachment 785422 [details]
File: cgroup
Comment 3 John Lewis 2013-08-11 17:16:57 UTC 
Created attachment 785423 [details]
File: core_backtrace
Comment 4 John Lewis 2013-08-11 17:17:01 UTC 
Created attachment 785424 [details]
File: dso_list
Comment 5 John Lewis 2013-08-11 17:17:04 UTC 
Created attachment 785425 [details]
File: environ
Comment 6 John Lewis 2013-08-11 17:17:07 UTC 
Created attachment 785426 [details]
File: exploitable
Comment 7 John Lewis 2013-08-11 17:17:12 UTC 
Created attachment 785427 [details]
File: limits
Comment 8 John Lewis 2013-08-11 17:17:18 UTC 
Created attachment 785428 [details]
File: maps
Comment 9 John Lewis 2013-08-11 17:17:21 UTC 
Created attachment 785429 [details]
File: open_fds
Comment 10 John Lewis 2013-08-11 17:17:25 UTC 
Created attachment 785430 [details]
File: proc_pid_status
Comment 11 Dan Mashal 2013-08-12 08:48:46 UTC 
Please try yum update to mate-screensaver 1.6.1 and reopen this bug if you are still having issues and let us know what was going on when you had this issue.
Comment 12 glad08 2013-12-11 15:12:47 UTC 
I got this bug again on mate-screensaver 1.6.1.
How to reopen this bug?
Comment 13 Wolfgang Ulbrich 2013-12-11 15:35:31 UTC 
Shure, i can.
It would be helpful if you give us a discription like..
.. how to reproduce
.. does mate-screensaver every time
.. your screensaver settings
-- etc.
Also, pls attach backtrace, etc which are in /var/tmp/abrt/<your-bug>/
Comment 14 Need Real Name 2015-02-28 17:58:54 UTC 
Created attachment 996491 [details]
core_backtrace from screensaver crash
Comment 15 Need Real Name 2015-02-28 18:00:05 UTC 
I just had this happen to me.  Haven't experienced it before as far as I remember.  I just uploaded a backtrace.  The reporting tool also mentions similar bug #1104091 as well as this bug.
Comment 16 Wolfgang Ulbrich 2015-02-28 19:05:39 UTC 
this repo(In reply to Need Real Name from comment #15)
> I just had this happen to me.  Haven't experienced it before as far as I
> remember.  I just uploaded a backtrace.  The reporting tool also mentions
> similar bug #1104091 as well as this bug.

This report is from f19 with mate-screensaver-1.6.x. and both are obsolete.
Please update your fedora version or use the other report when you're using f20+.