Bug 880182 - /lib64/libcacard.so.0: undefined symbol: qemu_parse_fdset
Summary: /lib64/libcacard.so.0: undefined symbol: qemu_parse_fdset
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: libcacard
Version: 18
Hardware: Unspecified
OS: Unspecified
unspecified
urgent
Target Milestone: ---
Assignee: Alon Levy
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-11-26 13:04 UTC by Kamil Páral
Modified: 2014-08-04 22:09 UTC (History)
9 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-06-26 17:57:08 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)
VM screenshot (18.95 KB, image/png)
2012-11-26 13:05 UTC, Kamil Páral 		no flags Details
View All

Description Kamil Páral 2012-11-26 13:04:26 UTC 
Description of problem:
Since I updated to libcacard-1.2.1-1.fc17.x86_64, all my VMs in virt-manager fail to display any graphical output. Error says:

Cannot display graphical console type 'spice': /lib64/libcacard.so.0: undefined symbol: qemu_parse_fdset

After downgrading to libcacard-0.1.2-2.fc17.x86_64 everything works fine again.

Version-Release number of selected component (if applicable):
libcacard-1.2.1-1.fc17.x86_64

How reproducible:
always

Steps to Reproduce:
1. update libcacard
2. run virt-manager
3. make sure you're using spice
4. run a VM
Comment 1 Kamil Páral 2012-11-26 13:05:11 UTC 
Created attachment 651946 [details]
VM screenshot
Comment 2 Alon Levy 2012-11-26 13:59:53 UTC 
Thanks for the prompt testing, I'm on it. will not push :)
Comment 3 Ken Dreyer 2012-11-27 07:00:55 UTC 
Confirmed on F-17, 64-bit.
Comment 4 Dag Odenhall 2012-11-28 04:23:19 UTC 
Confirmed on F17 32 bit.
Comment 5 Elio Maldonado Batiz 2012-11-28 21:08:18 UTC 
A 'yum downgrade libcacard' gave me a temporary workaround.
Comment 6 Marcel Wysocki 2012-11-29 08:55:51 UTC 
confirmed F17 64-bit.
updates-testing is enabled
Comment 7 Hans de Goede 2012-11-29 09:14:04 UTC 
Thanks for reporting this, we are aware of this and are working on a fix in the mean time the update has been unpushed from updates-testing.
Comment 8 Cole Robinson 2013-06-26 17:57:08 UTC 
The unpush fixed this issue I guess.
Note You need to log in before you can comment on or make changes to this bug.