Bug 878143

Summary: [abrt] xfce4-settings-4.8.3-4.fc17: vasprintf: Process /usr/bin/xfce4-display-settings was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Diego <diego.ml>
Component: xfce4-settingsAssignee: Kevin Fenzi <kevin>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 17CC: admiller, kevin
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:3fa6bb314f4109d6c5eba3ddecacdda0b3a0c650
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-08-01 17:37:04 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: core_backtrace
none
File: environ
none
File: backtrace
none
File: limits
none
File: cgroup
none
File: smolt_data
none
File: executable
none
File: maps
none
File: dso_list
none
File: proc_pid_status
none
File: var_log_messages
none
File: open_fds none

Description Diego 2012-11-19 18:02:21 UTC 
Description of problem:
I changed resolution from 1024x768 to 1152x864 and the process crashed.

Version-Release number of selected component:
xfce4-settings-4.8.3-4.fc17

Additional info:
libreport version: 2.0.18
abrt_version:   2.0.18
backtrace_rating: 4
cmdline:        xfce4-display-settings
crash_function: vasprintf
kernel:         3.6.6-1.fc17.i686

truncated backtrace:
:Thread no. 1 (10 frames)
: #2 vasprintf at /usr/include/bits/stdio2.h:199
: #3 g_vasprintf at gprintf.c:314
: #4 g_strdup_vprintf at gstrfuncs.c:509
: #5 g_strdup_printf at gstrfuncs.c:535
: #6 display_settings_update_time_label at main.c:172
: #12 gtk_dialog_run at gtkdialog.c:1094
: #13 display_setting_timed_confirmation at main.c:218
: #14 display_setting_refresh_rates_changed at main.c:446
: #15 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115
: #16 _g_closure_invoke_va at gclosure.c:840
Comment 1 Diego 2012-11-19 18:02:24 UTC 
Created attachment 647919 [details]
File: core_backtrace
Comment 2 Diego 2012-11-19 18:02:26 UTC 
Created attachment 647920 [details]
File: environ
Comment 3 Diego 2012-11-19 18:02:34 UTC 
Created attachment 647921 [details]
File: backtrace
Comment 4 Diego 2012-11-19 18:02:37 UTC 
Created attachment 647922 [details]
File: limits
Comment 5 Diego 2012-11-19 18:02:39 UTC 
Created attachment 647923 [details]
File: cgroup
Comment 6 Diego 2012-11-19 18:02:41 UTC 
Created attachment 647924 [details]
File: smolt_data
Comment 7 Diego 2012-11-19 18:02:44 UTC 
Created attachment 647925 [details]
File: executable
Comment 8 Diego 2012-11-19 18:02:47 UTC 
Created attachment 647926 [details]
File: maps
Comment 9 Diego 2012-11-19 18:02:50 UTC 
Created attachment 647927 [details]
File: dso_list
Comment 10 Diego 2012-11-19 18:02:52 UTC 
Created attachment 647928 [details]
File: proc_pid_status
Comment 11 Diego 2012-11-19 18:02:54 UTC 
Created attachment 647929 [details]
File: var_log_messages
Comment 12 Diego 2012-11-19 18:02:57 UTC 
Created attachment 647930 [details]
File: open_fds
Comment 13 Kevin Fenzi 2012-11-19 20:21:12 UTC 
What were you doing when this happened?

Can you duplicate it?
Comment 14 Diego 2012-11-21 10:08:37 UTC 
(In reply to comment #13)
> What were you doing when this happened?
> 

I was changing resolution inside an XFCE session with xfce4-display-settings.

> Can you duplicate it?

Yes, I can reproduce it every time. I just need to change resolution and I get the crash. It happens after the resolution has actually changed and just after the confirm window pops up.
Comment 15 Kevin Fenzi 2012-11-21 20:54:19 UTC 
ok. 

I'll see what I can make of the backtrace. 
Would you be willing to file this upstream (bugzilla.xfce.org) or would you like me to do so?

Also, could you attach a copy of your /var/log/Xorg.0.log ?
Comment 16 Diego 2012-11-22 07:46:55 UTC 
(In reply to comment #15)
> ok. 
> 
> I'll see what I can make of the backtrace. 
> Would you be willing to file this upstream (bugzilla.xfce.org) or would you
> like me to do so?
> 
> Also, could you attach a copy of your /var/log/Xorg.0.log ?

Ok, I'll do both things this weekend.
Comment 17 Fedora End Of Life 2013-07-04 06:09:15 UTC 
This message is a reminder that Fedora 17 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 17. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '17'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 17's end of life.

Bug Reporter:  Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 17 is end of life. If you 
would still like  to see this bug fixed and are able to reproduce it 
against a later version  of Fedora, you are encouraged  change the 
'version' to a later Fedora version prior to Fedora 17's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 18 Fedora End Of Life 2013-08-01 17:37:09 UTC 
Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.