You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I use a toml config file to define all of my parameters. The problematic ones in this case, are the pulsectl pretty name params. The parameter key gets converted to lower case (presumably during toml parsing), while the pulsectl lib returns the properly capitalized name. The pulsectl module then fails to look up the params, cause the names don't match. Adding a .lower() call on the output from pulsectl fixes this issue, but breaks parameters passed in through the command line.
Just adjust the device name to one on your own machine that has capital letters.
Starting bumblebee with this config, will still show the original name.
The text was updated successfully, but these errors were encountered:
looks like ConfigParser, the module that is used by bumblebee-status, is case insensitive by default. There are ways around that, I hope I can investigate during the weekend.
Bug Report
Description
Affected module: config
Version used: latest git
I use a toml config file to define all of my parameters. The problematic ones in this case, are the pulsectl pretty name params. The parameter key gets converted to lower case (presumably during toml parsing), while the pulsectl lib returns the properly capitalized name. The pulsectl module then fails to look up the params, cause the names don't match. Adding a
.lower()
call on the output from pulsectl fixes this issue, but breaks parameters passed in through the command line.Related issue
How to reproduce
Create a toml config for bumblebee, similar to this:
Just adjust the device name to one on your own machine that has capital letters.
Starting bumblebee with this config, will still show the original name.
The text was updated successfully, but these errors were encountered: