Bug 1756028

Summary: running mate-optimus with nvidia-390xx
Product: [Fedora] Fedora Reporter: Wolfgang Ulbrich <raveit65.sun>
Component: mate-optimusAssignee: Artem <ego.cordatus>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 30CC: ego.cordatus
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-26 17:16:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Wolfgang Ulbrich 2019-09-26 16:06:27 UTC
Description of problem:


I got this error message when i try to run mate-optimus-applet

[rave@mother ~]$ mate-optimus-applet 
mate-optimus-applet: launched.
Traceback (most recent call last):
  File "/usr/bin/mate-optimus-applet", line 324, in <module>
    if (prime_capable() and has_nvidia_settings()) or skip_prime_support:
  File "/usr/bin/mate-optimus-applet", line 48, in prime_capable
    prime_supported = subprocess.Popen(['prime-supported'], stdout=PIPE, stderr=DEVNULL)
  File "/usr/lib64/python3.7/subprocess.py", line 775, in __init__
    restore_signals, start_new_session)
  File "/usr/lib64/python3.7/subprocess.py", line 1522, in _execute_child
    raise child_exception_type(errno_num, err_msg, err_filename)
FileNotFoundError: [Errno 2] Datei oder Verzeichnis nicht gefunden: 'prime-supported': 'prime-supported'

Martin Wimpress from ubuntu-mate told me that it should be possible. Only logout after switching gpu is needed for 390xx legacy driver.

Comment 1 Artem 2019-09-26 18:12:15 UTC
I still can't test myself this. Probably we need to package this as well https://github.com/linuxmint/nvidia-prime
But it look like Ubuntu specific so i doubt will it work on Fedora at all or require a lot effort to make it works.

Comment 2 Ben Cotton 2020-04-30 21:03:50 UTC
This message is a reminder that Fedora 30 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 30 on 2020-05-26.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '30'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 30 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 3 Ben Cotton 2020-05-26 17:16:09 UTC
Fedora 30 changed to end-of-life (EOL) status on 2020-05-26. Fedora 30 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.