Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A sane place for Additional Drivers [$125 awarded] #12

Closed
elementaryBot opened this issue Mar 16, 2017 · 6 comments
Closed

A sane place for Additional Drivers [$125 awarded] #12

elementaryBot opened this issue Mar 16, 2017 · 6 comments
Labels
Priority: Wishlist Not a bug. A new feature or enhancement
Milestone

Comments

@elementaryBot
Copy link
Contributor

elementaryBot commented Mar 16, 2017

There was a question about this : https://answers.launchpad.net/elementaryos/+question/268252
The answer is correct but confusing for users who need this tool.

As requested i would make a blueprint but a bug seems more logical now.
because the feature is there only not on the place people would suspect.

Launchpad Details: #LP1469733 kay van der Zander - 2015-06-29 14:05:02 +0000


The $125 bounty on this issue has been claimed at Bountysource.

@elementaryBot
Copy link
Contributor Author

Another place to consider is to present drivers as updates in AppCenter, an idea that Cody and I both had independently

Launchpad Details: #LPC Daniel Fore - 2015-12-14 18:39:06 +0000

@elementaryBot elementaryBot added the Priority: Wishlist Not a bug. A new feature or enhancement label Mar 16, 2017
@elementaryBot
Copy link
Contributor Author

Drivers is more related to Hardware than to Software. I think drivers in the AppCenter might be the wrong place. It should be in Hardware plug.

Launchpad Details: #LPC swizzle - 2015-12-29 12:40:11 +0000

@elementaryBot
Copy link
Contributor Author

Adding drivers to AppCenter is following the gnome software and ubuntu software pattern.

On the other hand if somebody is testing on an external drive and switches to the nonfree driver stack they're going to get a rude awakening* if they move to another machine with a different hardware setup (or just get a bad or broken driver for their specific device).

It might pay to put drivers out of band from regular software updates to stop people who don't know what they're doing from messing with them, regardless of whether they're in AppCenter or Switchboard.

*rollbacks from nvidia blobs require going into a VT to purge configs and reinstall xorg.

Launchpad Details: #LPC Aneurin Hall - 2016-02-04 03:10:41 +0000

@elementaryBot
Copy link
Contributor Author

I'm gonna confirm this for AppCenter.

It seems kind of overkill to have a whole plug with basically one button: "Install proprietary driver?". I think it probably makes the most sense to a regular end user to just present it as an available update.

Launchpad Details: #LPC Daniel Fore - 2016-04-05 04:15:48 +0000

@elementaryBot
Copy link
Contributor Author

So I don't forget again, gotta make a note of using ubuntu-drivers-common for detection

Launchpad Details: #LPC Daniel Fore - 2016-04-05 04:16:15 +0000

@elementaryBot
Copy link
Contributor Author

Adam has started working on this and has a branch that he will attach soon.

https://www.bountysource.com/issues/29116369-a-sane-place-for-additional-drivers

Launchpad Details: #LPC Daniel Fore - 2016-08-12 20:59:24 +0000

@danirabbit danirabbit added this to the juno-beta1 milestone Mar 21, 2017
@danirabbit danirabbit changed the title A sane place for Additional Drivers [$100] A sane place for Additional Drivers Mar 23, 2017
@danirabbit danirabbit changed the title A sane place for Additional Drivers A sane place for Additional Drivers [$125] Mar 30, 2017
@danirabbit danirabbit changed the title A sane place for Additional Drivers [$125] A sane place for Additional Drivers [$125 awarded] Jul 29, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Wishlist Not a bug. A new feature or enhancement
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants