cannot start bumblebee after last update about bumblebee-status HOT 6 CLOSED

Damn, that was a bad change from my side. Sorry for the inconvenience! :-( I have a patch ready, but I'm on the road right now. Will fix this today in the evening.

Default will be to log into ~/, with the option to specify the file path, as suggested by @dumyan .

from bumblebee-status.

@zetxx I had the same issue and manually changed that the logs are written in my home folder. Just look for /usr/share/bumblebee-status/debug.log in the code and change accordingly.

It looks like there are differences between the permissions of /usr/share/ on different distros, but I'm almost certain that users should not have write access there. I'm running Arch, what do you use @zetxx and @tobi-wan-kenobi? I have installed bumblebee-status from AUR, but I don't think that's much relevant here.

@tobi-wan-kenobi do you think that adding an optional flag when running bublebee-status that the user can use to specify a file where the log will be written is a good idea?

EDIT:

turns out that the installation method is important because currently the log file is being written to the folder where the executable is. This means that the logging will only work for those who keep the bar into a folder where the user have permissions to write ( aka devs :)) )

from bumblebee-status.

same story
dist: arch
changed log destination in order to run properly

from bumblebee-status.

fix works

from bumblebee-status.

Yay, thanks for the quick testing! And sorry again for the bug ;-(

from bumblebee-status.

no worries :)

from bumblebee-status.