mirror of
https://github.com/hirschmann/nbfc.git
synced 2026-04-26 17:15:58 +03:00
[GH-ISSUE #1369] NBFC UI Flickering When Attempting to Use Custom Configuration #1177
Labels
No labels
Stale
bug
config
discussion
duplicate
enhancement
experimental
feature
help-wanted
info
invalid
invalid
pull-request
question
up-for-grabs
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nbfc-hirschmann#1177
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ngynlaam on GitHub (Oct 18, 2023).
Original GitHub issue: https://github.com/hirschmann/nbfc/issues/1369
Hi, I am using NBFC as a replacement for Omen Gaming Hub, and I wanted to try this configuration after switching my OS to Linux (I am currently on Windows). However, when I use my custom configuration, I am unable to enable it, and the UI continues to flicker.
System information
time;level;message;exception;callsite;stacktrace
2023-10-16 00:00:00.5186;Info;Starting NoteBookFanControlService;;NbfcService.NoteBookFanControlService.OnStart;ThreadPoolWorkQueue.Dispatch => QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem => ExecutionContext.Run => ExecutionContext.RunInternal => ServiceBase.ServiceQueuedMainCallback => NoteBookFanControlService.OnStart
2023-10-16 00:00:00.8159;Fatal;An unhandled exception occurred;Failed to access CPU temperature sensors(s).;NbfcService.NoteBookFanControlService+<>c.<.ctor>b__3_0;TimerQueue.FireNextTimers => TimerQueueTimer.Fire => TimerQueueTimer.CallCallback => ExecutionContext.Run => ExecutionContext.RunInternal => FanControl.TimerCallback => CpuTemperatureMonitor.GetTemperature => HardwareMonitor.get_CpuTemperatures => HardwareMonitor.InitializeCpuSensors => <>c.<.ctor>b__3_0
@TheMychenik commented on GitHub (Jan 29, 2024):
Hi, did you fix it?
@github-actions[bot] commented on GitHub (Jul 29, 2024):
This issue is stale because it has been open more than 180 days with no activity. If nobody comments within 7 days, this issue will be closed