Bug 1287718

Summary: [abrt] xfce4-settings: convert_xfce_output_info(): xfce4-display-settings killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Vitor <vitorjr81>
Component: xfce4-settingsAssignee: Kevin Fenzi <kevin>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: kevin, nonamedotc, rjones
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a8347abb2aea444b5ea52dbd540124189647d84d
Whiteboard: abrt_hash:41546a25327b7a3796ed5360aac1738d1198934b;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-19 11:05:53 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: limits
none
File: maps
none
File: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Vitor 2015-12-02 14:23:44 UTC 
Description of problem:
Trying to open display option.

Version-Release number of selected component:
xfce4-settings-4.12.0-5.fc22

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        xfce4-display-settings
crash_function: convert_xfce_output_info
executable:     /usr/bin/xfce4-display-settings
global_pid:     14783
kernel:         4.2.6-200.fc22.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 convert_xfce_output_info at main.c:1618
 #1 list_connected_outputs at main.c:1786
 #2 on_area_paint at main.c:2589
 #7 foo_scroll_area_expose at scrollarea.c:522
 #8 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
 #13 gtk_widget_event_internal at gtkwidget.c:5017
 #14 gtk_widget_send_expose at gtkwidget.c:4846
 #15 gtk_container_propagate_expose at gtkcontainer.c:2757
 #16 gtk_container_expose at gtkcontainer.c:2661
 #17 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
Comment 1 Vitor 2015-12-02 14:23:49 UTC 
Created attachment 1101492 [details]
File: backtrace
Comment 2 Vitor 2015-12-02 14:23:51 UTC 
Created attachment 1101494 [details]
File: cgroup
Comment 3 Vitor 2015-12-02 14:23:53 UTC 
Created attachment 1101497 [details]
File: core_backtrace
Comment 4 Vitor 2015-12-02 14:23:54 UTC 
Created attachment 1101499 [details]
File: dso_list
Comment 5 Vitor 2015-12-02 14:23:56 UTC 
Created attachment 1101501 [details]
File: environ
Comment 6 Vitor 2015-12-02 14:23:57 UTC 
Created attachment 1101503 [details]
File: limits
Comment 7 Vitor 2015-12-02 14:23:59 UTC 
Created attachment 1101504 [details]
File: maps
Comment 8 Vitor 2015-12-02 14:24:00 UTC 
Created attachment 1101505 [details]
File: mountinfo
Comment 9 Vitor 2015-12-02 14:24:02 UTC 
Created attachment 1101506 [details]
File: namespaces
Comment 10 Vitor 2015-12-02 14:24:03 UTC 
Created attachment 1101507 [details]
File: open_fds
Comment 11 Vitor 2015-12-02 14:24:04 UTC 
Created attachment 1101508 [details]
File: proc_pid_status
Comment 12 Vitor 2015-12-02 14:24:06 UTC 
Created attachment 1101509 [details]
File: var_log_messages
Comment 13 Kevin Fenzi 2015-12-02 16:18:30 UTC 
This happens everytime? 

Did it work as expected in the past?

Do you have multiple monitors? docking station?
Comment 14 Vitor 2015-12-02 16:27:32 UTC 
(In reply to Kevin Fenzi from comment #13)
> This happens everytime? 
> 
> Did it work as expected in the past?
> 
> Do you have multiple monitors? docking station?

Yes, everytime.

Never tried before. Just tried to open Display options.

No monitor on PC. Connecting through VNC, but on my laptop I have dock and multiple monitors.

Regards
Vitor Jr.
Comment 15 Kevin Fenzi 2015-12-02 22:45:19 UTC 
ok, to be clear: this is in the vnc session? Or locally?
Comment 16 Richard W.M. Jones 2016-05-19 11:05:53 UTC 
Closing as duplicate of a newer bug that has more details.

*** This bug has been marked as a duplicate of bug 1317382 ***