This is getting comical. On 06.06.2016 00:26, Dmitry Smirnov wrote: > If you reasonably suspect that Raspberry is not powerful enough for > Xpra then why did you submit your bug in first place?
You crack me up. Now, where did I say that? You seem to be hallucinating. I'm merely observing that the CPU is saturated. And it's well-known that the CPU on the Raspberry isn't the beefiest. That doesn't mean I'd expect extended CPU hogging. Quite the contrary, especially since I can run graphical apps over ssh X forwarding without any problem and with maybe 3-10% CPU consumption. But then again, what do I know what xpra is doing in the background? And indeed maybe there is a good explanation and it's likely not to change. Then this would be something that should be documented in README.Debian if there is no way to improve performance. Again, we know really nothing at this point. We merely have an observation of an odd behaviour. You stopped the bug triage in its tracks. OK... > Too bad if you expected (much) more than this as I can't satisfy your > expectations... I'm only asking you to care enough for a package you claim you want to maintain to actually maintain it. And that means for example bug triage, not ticket closing. > There some reasons why your bug was closed: > * No actionable tasks for maintainer. Nonsense. Apparently neither you nor I have any idea at this point if the CPU or some other part of the RPi is indeed underpowered for xpra. Or if this is somehow a mismatch of versions/platforms/$whatnot. Or PEBKAC. Or if it used to be a problem and no longer is in backports/testing/unstable. Just to name a few possibilities. All I know is that you don't seem to care to find out. And that it's your job as maintainer to _want_ to find out, during bug triage. And that's why you are not a good maintainer, even if you do not like to hear this valid criticism. > * Unsupported client from unsupported operating system. Nonsense. By the same token a critical security vulnerability in the Debian Apache package isn't even a bug if it is triggered from a remote windows client? Or a segfault in a package because of malformed input that the program didn't validate/discard? How did you ever manage to become DD? Seems like you missed the point again that the problem occurred in a fully up-to-date Jessie system (not the Ubuntu system)?! You've made it amply clear that you consider the version in Jessie ancient and unsupported. It hasn't really sunk in to your conscience apparently that this disregard for stable still disqualifies you as maintainer. And obviously, you don't like to hear it, but I'll still repeat it as that's simply the truth. You signed up to be maintainer, then be it, not only for unstable. > * Not really a bug report but support request. Buahahaha. I think we've exchanged our points of view and it seems I won't be able to convince you to take your job seriously. Oh, well... Have a great day.
