FS#32743 - [blueman] KillSwitch.py Exception
Attached to Project:
Community Packages
Opened by René Herman (rene) - Sunday, 18 November 2012, 05:01 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 22 November 2012, 12:51 GMT
Opened by René Herman (rene) - Sunday, 18 November 2012, 05:01 GMT
Last edited by Sergej Pupykin (sergej) - Thursday, 22 November 2012, 12:51 GMT
|
Details
blueman-1.23-5:
On every startup of Xfce, the Blueman KillSwitch plugin spits the following message into the logs: === Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/blueman/plugins/BasePlugin.py", line 65, in _load self.on_load(parent) File "/usr/lib/python2.7/site-packages/blueman/plugins/applet/KillSwitch.py", line 52, in on_load raise Exception("Failed to initialize killswitch manager") === Now, I do not in fact have the KillSwitch plugin enabled (in the rightclick->Plugins menu on the bluetooth system-tray icon) but it seems that the only way to avoid this message is to delete/rename the KillSwitch.py file -- and do it again on every update. Is there a better/expected way of avoiding this exception and/or the KillSwitch plugin? |
This task depends upon
Closed by Sergej Pupykin (sergej)
Thursday, 22 November 2012, 12:51 GMT
Reason for closing: Not a bug
Thursday, 22 November 2012, 12:51 GMT
Reason for closing: Not a bug
This is not intended as a merely argumentative "do this for me" sort of thing. It's just that having every Joe Random User (me, in this case) be responsible for packages that already have a maintainer makes no sense to me, from any perspective.
After trying this (rfkill does work) the error message was absent upon restarting X, so I thought something had fixed itself. However, even after rebooting and even shutting down the machine, I can't get the problem to resurface and in fact, when I check the journalctl log, I see that the last time that I DID get it was yesterday.
This is really exceedingly weird because this error has been present for me literally for years. I just rebuilt an archlinux system a week or so ago and thought I'd this time get rid of all of these kinds of oddities... which seems to have happened, but I'm completely flabbergasted as to how. The only thing I did yesterday was fix "slim" (display manager) not shutting down nicely, but I don't believe this issue could involve stale lock-files or anything like that which could maybe somehow explain this.
Urgh. I'm fairly sure it will resurface. Could you for now ignore me but keep this open? I'll request closure if in a few days it hasn't reappeared. Sorry for the bother -- I'm really uncertain how/why this all of a sudden disappeared just after reporting.
Bit unfortunate this, just after getting rowdy with Greg... ;-)