Bug 960692 - [abrt] roxterm-2.2.2-3.fc18: strcmp: Process /usr/bin/roxterm-config was killed by signal 11 (SIGSEGV)
Summary: [abrt] roxterm-2.2.2-3.fc18: strcmp: Process /usr/bin/roxterm-config was kill...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: roxterm
Version: 18
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Dan Horák
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d9767a50cb48bc23a8f593dda4f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-05-07 17:10 UTC by mock
Modified: 2013-07-03 01:33 UTC (History)
2 users (show)

Fixed In Version: roxterm-2.7.2-2.fc19
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-07-03 01:33:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (60.31 KB, text/plain)
2013-05-07 17:10 UTC, mock
no flags Details
File: cgroup (127 bytes, text/plain)
2013-05-07 17:10 UTC, mock
no flags Details
File: core_backtrace (3.79 KB, text/plain)
2013-05-07 17:10 UTC, mock
no flags Details
File: dso_list (8.35 KB, text/plain)
2013-05-07 17:10 UTC, mock
no flags Details
File: environ (1.60 KB, text/plain)
2013-05-07 17:10 UTC, mock
no flags Details
File: limits (1.29 KB, text/plain)
2013-05-07 17:10 UTC, mock
no flags Details
File: maps (41.74 KB, text/plain)
2013-05-07 17:10 UTC, mock
no flags Details
File: open_fds (813 bytes, text/plain)
2013-05-07 17:10 UTC, mock
no flags Details
File: proc_pid_status (931 bytes, text/plain)
2013-05-07 17:10 UTC, mock
no flags Details
File: var_log_messages (316 bytes, text/plain)
2013-05-07 17:10 UTC, mock
no flags Details
File: xsession_errors (730 bytes, text/plain)
2013-05-07 17:10 UTC, mock
no flags Details

Description mock 2013-05-07 17:10:37 UTC
Description of problem:
when creating a color profile, i clicked to edit the properties and it crashed. the property name had a hyphen in the name. green-black.

Version-Release number of selected component:
roxterm-2.2.2-3.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/bin/roxterm-config --display=:0.0 Configlet
crash_function: strcmp
executable:     /usr/bin/roxterm-config
kernel:         3.8.9-200.fc18.x86_64
uid:            1000
ureports_counter: 2

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 strcmp at ../sysdeps/x86_64/multiarch/strcmp-sse42.S:162
 #1 options_file_open at optsfile.c:239
 #2 options_reload_keyfile at options.c:35
 #3 options_open at options.c:46
 #4 dynamic_options_lookup_and_ref at dynopts.c:67
 #5 colour_scheme_lookup_and_ref at colourscheme.c:72
 #6 colourgui_open at colourgui.c:625
 #7 edit_thing_by_name at configlet.c:697
 #8 edit_selected_thing at configlet.c:738
 #9 _g_closure_invoke_va at gclosure.c:840

Comment 1 mock 2013-05-07 17:10:40 UTC
Created attachment 744832 [details]
File: backtrace

Comment 2 mock 2013-05-07 17:10:42 UTC
Created attachment 744833 [details]
File: cgroup

Comment 3 mock 2013-05-07 17:10:44 UTC
Created attachment 744834 [details]
File: core_backtrace

Comment 4 mock 2013-05-07 17:10:45 UTC
Created attachment 744835 [details]
File: dso_list

Comment 5 mock 2013-05-07 17:10:47 UTC
Created attachment 744836 [details]
File: environ

Comment 6 mock 2013-05-07 17:10:48 UTC
Created attachment 744837 [details]
File: limits

Comment 7 mock 2013-05-07 17:10:50 UTC
Created attachment 744838 [details]
File: maps

Comment 8 mock 2013-05-07 17:10:52 UTC
Created attachment 744839 [details]
File: open_fds

Comment 9 mock 2013-05-07 17:10:54 UTC
Created attachment 744840 [details]
File: proc_pid_status

Comment 10 mock 2013-05-07 17:10:56 UTC
Created attachment 744841 [details]
File: var_log_messages

Comment 11 mock 2013-05-07 17:10:58 UTC
Created attachment 744842 [details]
File: xsession_errors

Comment 12 mock 2013-05-08 13:06:32 UTC
apparently, color profiles, either creating or switching, can cause it to crash. i've had it happen in both cases.

backtrace_rating: 4
cmdline:        roxterm
crash_function: strcmp
executable:     /usr/bin/roxterm
kernel:         3.8.11-200.fc18.x86_64
package:        roxterm-2.2.2-3.fc18
reason:         Process /usr/bin/roxterm was killed by signal 11 (SIGSEGV)
uid:            1000
ureports_counter: 1

Comment 13 Fedora Update System 2013-06-17 02:56:04 UTC
roxterm-2.7.2-1.fc19 has been submitted as an update for Fedora 19.
https://admin.fedoraproject.org/updates/roxterm-2.7.2-1.fc19

Comment 14 Fedora Update System 2013-06-17 17:02:52 UTC
Package roxterm-2.7.2-1.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing roxterm-2.7.2-1.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-11053/roxterm-2.7.2-1.fc19
then log in and leave karma (feedback).

Comment 15 Fedora Update System 2013-06-24 18:48:06 UTC
Package roxterm-2.7.2-2.fc19:
* should fix your issue,
* was pushed to the Fedora 19 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing roxterm-2.7.2-2.fc19'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2013-11053/roxterm-2.7.2-2.fc19
then log in and leave karma (feedback).

Comment 16 Fedora Update System 2013-07-03 01:33:48 UTC
roxterm-2.7.2-2.fc19 has been pushed to the Fedora 19 stable repository.  If problems still persist, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.