Bug 861698 - /lib64/libQtGui.so.4 is truncated
Summary: /lib64/libQtGui.so.4 is truncated
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Fedora
Classification: Fedora
Component: qt
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-09-30 04:44 UTC by Lee Marshall
Modified: 2012-09-30 16:31 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-09-30 16:31:21 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Lee Marshall 2012-09-30 04:44:17 UTC
Description of problem:
Since Upgrade to qt-x11.i686 1:4.8.2-4.fc17 3 applications that utilize Qt have stopped working - all terminate immediately with segfault

Version-Release number of selected component (if applicable):

3 apps that appear to be effected are: 
VLC
Stellarium
VirtualBox


How reproducible:
always

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

I appears that the library that is at fault is /lib64/libQtGui.so.4
Yum just happens to report the following errors during install:
# yum install qt-x11.i686
/sbin/ldconfig: file /lib64/libQtGui.so.4.8 is truncated
/sbin/ldconfig: file /lib64/libQtGui.so.4 is truncated
/sbin/ldconfig: file /lib64/libQtGui.so.4.8.2 is truncated

Suspect that could be the root cause.

Comment 1 Kevin Kofler 2012-09-30 14:34:18 UTC
Did you run out of disk space?

Comment 2 Lee Marshall 2012-09-30 16:20:59 UTC
(In reply to comment #1)
> Did you run out of disk space?

Not even close...

Comment 3 Lee Marshall 2012-09-30 16:25:53 UTC
Further investigations to reproduce the Yum error are underway.  However,
somehow, the i686 package was getting installed, NOT the x86_64 package.

A manual reinstall of the proper qt-X11.x86_64 package does appear to solve the problem.  If I can recreate the issue I'll update...


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