On Donnerstag, 21. März 2013 23:40:14 Luca Beltrame wrote:
In data giovedì 21 marzo 2013 22:11:43, Hans-Peter Jansen ha scritto:
Hello,
It makes me really wonder, why on earth you guys you talk shop about elaborated patch handling, while *blatant* bug reports including *easy*
Certainly starting off like this doesn't make anyone more motivated. Have you ever heard of "stop energy"?
big decision to add a current version of LibVNCServer to KR410 for 12.2 in order to get krdc going?
Currently, AFAIK, libvncserver is a link to the package in Factory. I am not sure what is the right approach to handle this issue. And as such, I leave judgment to others more informed in the team.
The bugzilla bug report points to https://bugs.kde.org/show_bug.cgi?id=314504, where I took the time to examine the issue. Starting with 4.10, krdc uses a new authentification scheme, that is dysfunctional with LibVNCServer as delivered by 12.2. Former krdc releases simply didn't use this functionality. Consequently, as both bug reports state, running krdc and connecting to a vnc server will crash krdc. Two possible solutions: downgrade krdc 4.10 to 4.9, or upgrade LibVNCServer to 0.99 (from 12.3).
Will, Raymond, everyone else? What do you think?
really any interest to get such issues fixed on a broader level? What are the reasons for such a slackness?
Again, I don't think such a tone is fitting. No one is "slacking". But given that most of KDE handling is now in the hands of the community, and since we're *still* adjusting our processes, there are still challenges.
but it feels, like *any* other area is better supported than this one..
Given the strides we've done in improving our work, packaging and relationship with upstream, I beg to differ. It doesn't mean it's heaven, but it's certainly not hell.
Luca, I really notice your activities, and I certainly appreciate them. Feel yourself excluded from my harsh words, please. I don't want to reiterate, what's really going wrong in this project as a whole, since it's too late today. In short, it feels, like this project doesn't miss any single opportunity to degrade itself since it approached from version 3. I've a couple of commercial customers, that still stick with openSUSE linux desktops, but you cannot imagine, how hard it is to advocate for Linux, while numerous issues of the KDE Desktop¹·² spoil the users. Well, I'm a bit unfair now, since LibreOffice throws in various rocks of its own. Now combine this with the udev woes, and you get an idea, why it's so hard to describe my issues in kind words. It is also the reason, why I speak up rarely, it's just too upsetting. ¹ Feel free to replace with todays buzz: but again, it feels, like people waste time and energy in all the wrong directions, while the most important issues keep scaring off more and more users day by day. ² A little list: PIM disaster, KDE conceptionally cannot handle malformed (wrongly encoded) file names, that appear every day, the QML parts of the desktop doesn't care about about the usual keyboard handling (no tab indicator, no trigger with blank), but they're sold as improvement, no control about the various pim sources (e.g. when do google addresses and calendars sync), and numerous other small issues... Cheers, Pete -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org