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
Task Type Bug Report
Category Packages
Status Closed
Assigned To Sergej Pupykin (sergej)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

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
Comment by Greg (dolby) - Monday, 19 November 2012, 07:41 GMT
Please report this upstream
Comment by René Herman (rene) - Monday, 19 November 2012, 09:10 GMT
I assume that the package maintainer will do so. Not wanting to sound "demanding" or anything, but I can't as a user maintain accounts on hundreds of different bugzilla's for every package that I have installed. Upstream authors moreover tend to very much prefer having their reports filtered through a distribution maintainer as well.
Comment by Greg (dolby) - Monday, 19 November 2012, 10:05 GMT
You are maybe confusing Arch with a non DIY distribution.
Comment by René Herman (rene) - Monday, 19 November 2012, 10:46 GMT
It just makes sense. And I would certainly take "being a conduit between my down- and my upstream" as part of my responsiblities when taking on maintainership of a package. This is both from the downstream- and the upstream-perspective much preferred. For the former case since, as said, N users should not I feel be expected to maintain accounts on M bugzilla's, and in the latter since it's much better for an upstream author to communicate with someone who actually knows what stuff is about.

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.
Comment by Greg (dolby) - Monday, 19 November 2012, 12:33 GMT Comment by René Herman (rene) - Monday, 19 November 2012, 12:50 GMT
So let it be written so let it be done, brother. Amen. Praise the lord.
Comment by Sergej Pupykin (sergej) - Monday, 19 November 2012, 13:09 GMT
Does "rfkill list" work? (you need to install rfkill and load rfkill module)
Comment by René Herman (rene) - Monday, 19 November 2012, 14:49 GMT
Thanks for the suggestion -- but I'm afraid something weird has happened.

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... ;-)
Comment by René Herman (rene) - Thursday, 22 November 2012, 09:18 GMT
It hasn't reappeared. Inexplicable -- but it seems this can be closed :-/

Loading...