Community Packages

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#42266 - [bumblebee] Nvidia 340xx legacy branch conflicts with bumblebee

Attached to Project: Community Packages
Opened by Max (MasterMax) - Monday, 06 October 2014, 15:16 GMT
Last edited by Doug Newgard (Scimmia) - Wednesday, 22 October 2014, 15:15 GMT
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sven-Hendrik Haase (Svenstaro)
Architecture All
Severity High
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description:
With the latest changes to nvidia, I think I now have to use the legacy drivers. (GPU is Geforce 310M). Bumblebee and nvidia-340-libgl (which is required by bumblebee) are in conflict.

Steps to reproduce:
Try to install nvidia-340xx and bumblebee at the same time.
This task depends upon

Closed by  Doug Newgard (Scimmia)
Wednesday, 22 October 2014, 15:15 GMT
Reason for closing:  Fixed
Additional comments about closing:  Re-opener requested: it is fixed for me... I messed up nvidia-340 and nvidia-304; my bad. it now works perfectly with nvidia-340 and bumblebee
Comment by Onur Kavaklı (PipiX) - Tuesday, 07 October 2014, 20:26 GMT
I would like to add that people having this problem and not updating their nvidia versions from 340.32-2 should also refrain from updating to the linux 3.16.4-1 kernel.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 08 October 2014, 00:14 GMT
Frankly I think this is a flaw in pacman's package resolution. I'm investigating.
Comment by Doug Newgard (Scimmia) - Wednesday, 08 October 2014, 01:34 GMT
The problem seems to be that the bumblebee package provides nvidia-libgl but not nvidia-340xx-libgl. Since it's required by nvidia-340xx, it tries to pull in both nvidia-340xx-libgl and mesa-libgl which fails.
Comment by Sven-Hendrik Haase (Svenstaro) - Wednesday, 08 October 2014, 01:47 GMT
Good catch. Of course. I didn't see that.
Comment by Max (MasterMax) - Thursday, 16 October 2014, 13:26 GMT
  • Field changed: Percent Complete (100% → 0%)
it does not seem fixed for me:
Imax@notebook:~% pacman -Q | grep nvidia
lib32-nvidia-340xx-utils 340.46-1
lib32-nvidia-cg-toolkit 3.1-4
nvidia-304xx-utils 304.123-1
nvidia-cg-toolkit 3.1-3

Imax@notebook:~% sudo pacman -S nvidia-304xx
resolving dependencies...
looking for inter-conflicts...
:: nvidia-304xx-libgl and mesa-libgl are in conflict (libgl). Remove mesa-libgl? [y/N] y
:: nvidia-304xx-libgl and bumblebee are in conflict (nvidia-libgl). Remove bumblebee? [y/N] y

Packages (4): bumblebee-3.2.1-5 [removal] mesa-libgl-10.3.0-3 [removal] nvidia-304xx-libgl-304.123-1 nvidia-304xx-304.123-7

Total Installed Size: 4.54 MiB
Net Upgrade Size: 4.34 MiB

:: Proceed with installation? [Y/n] n

Loading...