| Summary: | Mageia 7 - LXQt with Onlinemedia installs Nvidia Nsight (Bloat) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | psyca <linux> |
| Component: | Installer | Assignee: | Mageia tools maintainers <mageiatools> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | doktor5000, mageia |
| Version: | 7 | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | CVE: | ||
| Status comment: | |||
| Attachments: | Desktop selection | ||
|
Description
psyca
2020-06-26 18:18:33 CEST
Created attachment 11719 [details]
Desktop selection
Just for info : this was also with MGA 7 > I do not choose developement tools
Psyca is right in that nvidia-nsight is in Group: Development/Other, so would not be expected otherwise.
task-lxqt itself does not require it, so unsure where the responsibility lies.
Assigning to tools group for installer; CC'ing Florian for LxQt (which I do not think matters; would this not happen with any other single desktop similarly installed?).Component:
RPM Packages =>
Installer I can see why this might happen in Mageia 7 - 'urpmq --provides nvidia-nsight' lists some unexpected things, e.g. libhyphen.so.0()(64bit). But that seems to have been fixed in cauldron. I tried to reproduce, using the same package selection as psyca, but nvidia-nsight wasn't installed. @psyca, please attach /root/drakx/report.bug.xz from the installed system, which should show us why nvidia-nsight was selected. CC:
(none) =>
mageia Have to change it. Its not MGA 8, its MGA 7 only. I installed from the wrong iso. Resolution:
(none) =>
OLD |