4 ms·
Let's hope so. What they were asking me to do was to rewrite a small portion of Rhythmbox as a QT app to expose the bug. I still think it was more reasonable
by jda2000 16y ago
Let's hope so.
What they were asking me to do was to rewrite a small portion of Rhythmbox as a QT app to expose the bug. I still think it was more reasonable for them to just get Rhythmbox from the repository and run qdbusviewer under a debugger.
Did I mention that I am not a QT programmer?
- dkersten 16y agoI get that and understand that (if they're on a debian based system) they can probably just apt-get install rythembox and test it for themselves (I don't use a debian-based system, but I imagine I can get it just as easily with yaourt -S rythembox). That would be the easiest. But, for whatever reason they cannot or will not install it and I don't think we can criticize them for that decision. Anyway, since you were saying that it is definitely not rythemboxes fault, I would suggest you 1) show the dbus-monitor trace of the d-feet so that they can see that rythembox and d-feet do work perfectly and 2) show them, again, the dbus-monitor output for qdbusviewer, in as much detail as you can and clearly highlighting where it diverges from the expected. If that isn't enough for them, then they definitely are being stubborn... The sad thing is, even if you do as they ask and write a Qt program, it really won't give them anything over what they'd have if you give them logs, since, as you say, the problem is not with rythembox. Sigh. In any case, good luck.
- jda2000 16y agoOK. Thank you very much and sincerely for your time and thought. It looks like your opinion is going to be unanimous. ;-)