qBittorrent official forums

Currently installed
v3.1.9.2 (updated per repository ppa:hydr0g3n/qbittorrent-stable)
OS: xubuntu 14.04

I First installed via ubuntu software center (ver 3.1.8.0 I think?), Setup options and downloaded a torrent. Everything worked as expected... although this is causing me to question my recollection of events... the run on completion program was called, correctly passed the folder name and the called program un-RARed, moved and renamed the payload as intended.

The next torrent completed but nothing happened after, no error, but also no evidence that the "run on completion" event fired. After several repeated attempts, and some confusion, restarts and such (remembering the definition of insanity, again and again...), I updated my repository info and upgraded to v3.1.9.2. with no change. After doing some reading on this forum and the bug tracker site, the only relevant issue I could see would be if I were using the temp folder option, which I am not.

The program that should be called is one I wrote in PureBasic

/home/peterr/SouceCode/rar2q %f

and is also available to me on my file manager's (spacefm) context menu. So, I can right click on the individual torrent folder(s) to easily duplicate what "run on completion" should have done and/or do it manually. Doing it manually work flawlessly every time (almost like I knew what I was doing, and feeling a little less insane...).

I figure the issue has got to be on my end, else there would be more recent and prolific entries on the bug tracker site. But I am a bit stumped on what to do next... Any Ideas?

On a side note:

1) It would be extremely useful to have a context menu option within qBitTorrent to fire the "Run On Completion" event/task manually. This would better facilitate testing and provide a way for users to implement new processes retroactively to existing content. 

2) I saw a suggestion on the bug tracker site that asked for a log mechanism for tracking "Run On Completion" events. While the thread suggested creating a launcher to solve the issue, which I agree is a good work around. Depending on what users are attempting to do, introducing an additional layer, for example calling a bash script to call something else, can become problematic when dealing with parameters that include spaces in the path/file names. For this reason alone, at least logging what was called from qBitTorrent, what parameter value was passed and when would be useful for many user imho.

at least logging what was called from qBitTorrent, what parameter value was passed and when would be useful for many user imho.

Does your program do any logging so you can see what is being passed to it?

can become problematic when dealing with parameters that include spaces in the path/file names.

Put quote marks around any variable/parameters that may contain spaces

Update from this ppa(until a setup a new one): https://launchpad.net/~surfernsk/+archi ... t-software
PS: Wait for the user to update to v3.1.11. v3.1.10 has regressions with the search functionality.

Thanks sledgehammer_999! Will do!

[quote="ciaobaby"]
Does your program do any logging so you can see what is being passed to it?

Put quote marks around any variable/parameters that may contain spaces
[/quote]

No logging yet... the app is only about 48 hrs old.. but I suppose that is something I should add, along with a config file before I share it. It will popup an info/status box regardless of what is passed to it, even if just to report that there is nothing to do or to report a processing error. Like I said, there is no evidence that it is actually being called at all.

If you were not logging what your application was doing how did you test that it was performing correctly.

Did your application handle simulated data passing ok?

Have you redirected the command line output from qBitTorrent to a text file, then passed that to your application via command line??