Bug 17212 - 64bit requires libprimus
Summary: 64bit requires libprimus
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 5
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Rémi Verschelde
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-24 10:11 CET by Luke Jones
Modified: 2015-12-03 10:14 CET (History)
1 user (show)

See Also:
Source RPM: primus-0.1-2.20150201.1.mga5.nonfree.src.rpm
CVE:
Status comment:


Attachments

Description Luke Jones 2015-11-24 10:11:53 CET
Description of problem:

Due to many Steam games being 32bit, when trying to run them with primusrun on a 64bit system they will fail.

To prevent this from happening, primus-nvidia and primus-nouveau should both require libprimus (along with lib64primus) if installed on x86_64.


How reproducible:
Every time.

Steps to Reproduce:
1. Install primus-nvidia and bumblebee for 64bit
2. Remove libprimus if installed
3. Try a 32bit game such as FortressCraft or any 32bit Unity3d powered game

Reproducible: 

Steps to Reproduce:
Comment 1 Thomas Backlund 2015-11-24 10:22:48 CET
No can do... 

x86_64 arch must be selfcontained, so no requires on 32bit allowed.

It can only be done as a  recommends

CC: (none) => tmb

Comment 2 Luke Jones 2015-11-24 10:26:15 CET
(In reply to Thomas Backlund from comment #1)
> No can do... 
> 
> x86_64 arch must be selfcontained, so no requires on 32bit allowed.
> 
> It can only be done as a  recommends

Makes sense. I guess a recommends should be fine. A newbie won't know what causes this issue as there is generally no output whatsoever to give any clues about it.
Comment 3 Rémi Verschelde 2015-11-24 10:28:14 CET
Good point, I'll add a Recommends: libprimus to the primus packages for x86_64.

Assignee: bugsquad => rverschelde

Comment 4 Rémi Verschelde 2015-12-03 10:13:53 CET
Fixed in cauldron, and a fix has been added to the current update candidate for bumblebee on Mageia 5. I'll close this one already to avoid forgetting to close it once the update is validated (should be soon) ;)

Status: NEW => RESOLVED
Resolution: (none) => FIXED

Rémi Verschelde 2015-12-03 10:14:02 CET

Severity: major => normal


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