-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
Handle rfcomm_list failing #2018
Conversation
I would not display anything and not put much thought in the log message either. The more important question to me is if this is enough to actually make things work on RFCOMM-disabled systems. By the way, I don't think the |
It's a kernel module on arch so I should be able to easily test this.
Yeah, hadn't put much thought into it and just grepped for the edit: removed the module and I can actually catch it. I'll just log the error message and if at some point we need more we can deal with it then. from _blueman import rfcomm_list
rfcomm_list()
Traceback (most recent call last):
File "<pyshell#1>", line 1, in <module>
rfcomm_list()
File "_blueman.pyx", line 144, in _blueman.rfcomm_list
Exception: ERR_SOCKET_FAILED
try:rfcomm_list()
except Exception as e:
print(e)
ERR_SOCKET_FAILED |
Yeah, this is enough to handle rfcomm missing. Pushed update with
|
eeeuh, this just showed up in the infobar when I tried to connect serial port and made the window 2million pixels wide 🤣 . It's probably a good idea to hide it :-)
|
To be used when RFCOMM is not available and we need to handle it.
Otherwise blueman-manager crashes as seen in blueman-project#2016
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Just quick draft so we can discuss if we need to display something to the user or not. And logging the exception may be too much, perhaps just the error message with or without the error number?