Red Hat Bugzilla – Bug 890464
[abrt] spice-gtk-tools-0.15-1.fc19: setcontext: Process /usr/bin/spicy was killed by signal 11 (SIGSEGV)
Last modified: 2013-09-29 21:32:11 EDT
Description of problem:
1. Start spicy program with `/usr/bin/spicy` cmd.
2. Fill host and port info in spicy dialog.
3. Input password for spicy server, then click OK button.
4. spicy crashed.
Version-Release number of selected component:
Thread no. 1 (2 frames)
#0 setcontext at ../sysdeps/unix/sysv/linux/x86_64/setcontext.S:55
#1 __start_context at ../sysdeps/unix/sysv/linux/x86_64/__start_context.S:39
Created attachment 669517 [details]
Created attachment 669518 [details]
Created attachment 669519 [details]
Created attachment 669520 [details]
Created attachment 669521 [details]
Created attachment 669522 [details]
Created attachment 669523 [details]
Created attachment 669524 [details]
Created attachment 669525 [details]
Created attachment 669526 [details]
Created attachment 669527 [details]
build fixing the bug on the way to bodhi
spice-gtk-0.15.3-1.fc18 has been submitted as an update for Fedora 18.
* should fix your issue,
* was pushed to the Fedora 18 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing spice-gtk-0.15.3-1.fc18'
as soon as you are able to.
Please go to the following url:
then log in and leave karma (feedback).
spice-gtk-0.15.3-1.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.