Package Details: nbfc 1.6.3-1

Git Clone URL: (read-only, click to copy)
Package Base: nbfc
Description: Cross-platform fan control service for notebooks (STABLE & BETA releases)
Upstream URL:
Licenses: GPL3
Conflicts: nbfc-beta, nbfc-git
Provides: ec-probe, nbfc
Submitter: erkexzcx
Maintainer: erkexzcx
Last Packager: erkexzcx
Votes: 6
Popularity: 0.000877
First Submitted: 2017-09-11 08:15
Last Updated: 2019-05-06 04:46

Latest Comments

1 2 Next › Last »

resadent commented on 2019-05-06 11:52

Just wanted to say thank you for the fast updates. Keep up the good job.

erkexzcx commented on 2019-05-06 04:48

New update is out.

erkexzcx commented on 2019-03-11 06:19

@Reden - On my Asus UX430UQ this package works fantastically. No issues. I believe this is your broken system's fault.

Reden commented on 2019-03-10 23:13

[redacted about session] Failed to activate service 'org.freedesktop.Notifications': timed out ... and my fan speed does not change. There's a warning about pam opening and immediately closing a session, too. Please help.

erkexzcx commented on 2019-03-06 23:26

Done. Will update nbfc-git as well in a few minutes. EDIT: Both updated.

nik123true commented on 2019-03-06 23:14

can you just update the nbfc file as it has no shell interpreter definition by default which causes issues on some shells like fish

if you don't understand what i mean just add a "#!/bin/sh" as the first line of the included nbfc script so I don't have to manually modify it, cheers!

erkexzcx commented on 2018-10-07 21:40

Update! :) I am back to maintain this package.

erkexzcx commented on 2018-06-16 22:06

I disowned this package simply because there is no logic for me to support it. I understand that this is "stable" release, but the last release was like 1 year ago and I had so many issues with it, which were proactively solved in development version nbfc-git. I wouldn't recommend installing this version to anyone as it has no advantages over nbfc-git.

erkexzcx commented on 2018-03-02 10:45

See nbfc-git for issues and how to solve them.

caleb commented on 2018-02-28 12:20

@erkexzcx That's the wrong approach. Having a -git package is fine and that can even be the recommended usage, but dropping a normal release package is not appropriate. This should stay as is, and recommend to upstream doing periodic tags. If you don't want to maintain the package, orphan it.