Bug 883669 - system-config-kdump fails with undefined symbol message
Summary: system-config-kdump fails with undefined symbol message
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: gtk2
Version: 18
Hardware: s390x
OS: All
unspecified
high
Target Milestone: ---
Assignee: Matthias Clasen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 883666 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-05 05:43 UTC by IBM Bug Proxy
Modified: 2013-06-06 13:03 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-06-06 13:03:28 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
SOS Report (433.60 KB, application/x-xz)
2012-12-05 05:43 UTC, IBM Bug Proxy 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
IBM Linux Technology Center 87140 0 None None None Never

Description IBM Bug Proxy 2012-12-05 05:43:25 UTC 
Steps to recreate the problem.
1) Install F18 with GNOME desktop
2) over a vnc session invoke system-config-kdump

Expected result - To be able to use the GUI panels.
Actual result -

$  system-config-kdump 
Traceback (most recent call last):
  File "/usr/share/system-config-kdump/system-config-kdump.py", line 22, in <module>
    import gtk
  File "/usr/lib64/python2.7/site-packages/gtk-2.0/gtk/__init__.py", line 40, in <module>
    from gtk import _gtk
ImportError: /lib64/libEGL.so.1: undefined symbol: wl_display_sync

$ rpm -qa | grep system-config-kdump
system-config-kdump-2.0.9-1.fc18.noarch

An SOS report is attached.
Comment 1 IBM Bug Proxy 2012-12-05 05:43:49 UTC 
Created attachment 657976 [details]
SOS Report
Comment 2 IBM Bug Proxy 2013-06-06 05:51:10 UTC 
------- Comment From vaish123.com 2013-06-06 05:48 EDT-------
Fixed with F19 build. Closing bug on IBM side.
Comment 3 Dan Horák 2013-06-06 13:00:27 UTC 
*** Bug 883666 has been marked as a duplicate of this bug. ***
Comment 4 Dan Horák 2013-06-06 13:03:28 UTC 
IIRC the F18 pre-GA repos were out of sync.
Note You need to log in before you can comment on or make changes to this bug.