[opensuse-kde] Bug 803534 - KRDC crashes when connecting to a VNC server
Hi, It makes me really wonder, why on earth you guys you talk shop about elaborated patch handling, while *blatant* bug reports including *easy* fixes, hanging around as submit requests, gets ignored. Is that on purpose? Of course, everybody is busy nowadays, but is it such a big decision to add a current version of LibVNCServer to KR410 for 12.2 in order to get krdc going? The SR (159256) from 7 days ago is now bit rotten, of course. I could stick my head in the sand, since I'm a happy krdc camper again (*several* dozen times a day) to get my job done, but I ask myself, is there really any interest to get such issues fixed on a broader level? What are the reasons for such a slackness? Being in the SuSE business since its dawn (started around 1995), and after the demise of SuSE Beta, one is accustomed to ignored bugzilla bug reports for long periods.. Lately, I try to support the project by SR'ing stuff, but it feels, like *any* other area is better supported than this one.. Cheers, Pete -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
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. 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 Beltrame - KDE Forums team KDE Science supporter GPG key ID: 6E1A4E79
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
On Fri, Mar 22, 2013 at 01:52:23AM +0100, Hans-Peter Jansen wrote:
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.
What "udev woes"? -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Donnerstag, 21. März 2013 18:22:06 Greg KH wrote:
On Fri, Mar 22, 2013 at 01:52:23AM +0100, Hans-Peter Jansen wrote:
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.
What "udev woes"?
Those, that might or might not show new storage devices (but show up under XP VM just nice), no access to scanners after upgrade, usb headsets, that that are available sometimes and sometimes not, no usb for virtualbox, raid1 mds not assembled properly (that resulted in data loss due to *changing* the devices between boots). To be fair, this collection spans issues of 12.1 and 12.2. I do not search for these issues, that's just those, that I had to deal with related to udev. Please don't take this personal, Greg, I know, that you're one of those rare linux protagonists, that usually get the work of 3-5 normal workers done. Pete -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Thursday 21 March 2013 22:11:43 Hans-Peter Jansen wrote:
It makes me really wonder, why on earth you guys you talk shop about elaborated patch handling, while *blatant* bug reports including *easy* fixes, hanging around as submit requests, gets ignored.
Is that on purpose? Of course, everybody is busy nowadays, but is it such a big decision to add a current version of LibVNCServer to KR410 for 12.2 in order to get krdc going?
As Luca already indicated my motivation goes down when I read this, especially since that you do not seem to care about distro dependencies on this package. If you would have searched, then you know that the following packages are depending on LibVNCServer: DirectFB kdenetwork4 (which is krdc) remmina virtualbox xen If we now start providing an updated LibVNCServer, then I really wonder what will happen with the above packages in 12.2. They might still work, they might also not work. Or maybe your idea is to provide also these packages in KR410 ?? Of course it is easy to provide a fix for a single bug, but I believe that it is also our duty to keep an eye on other non-KDE packages that might get into troubles if we start providing updates that could cause issues in other areas. The KDE team has always been very carefull with providing updates of system related packages in KDE repositories due to the described effect. Regards Raymond -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Samstag, 23. März 2013 09:37:48 Raymond Wooninck wrote:
On Thursday 21 March 2013 22:11:43 Hans-Peter Jansen wrote:
It makes me really wonder, why on earth you guys you talk shop about elaborated patch handling, while *blatant* bug reports including *easy* fixes, hanging around as submit requests, gets ignored.
Is that on purpose? Of course, everybody is busy nowadays, but is it such a big decision to add a current version of LibVNCServer to KR410 for 12.2 in order to get krdc going?
As Luca already indicated my motivation goes down when I read this, especially since that you do not seem to care about distro dependencies on this package. If you would have searched, then you know that the following packages are depending on LibVNCServer:
DirectFB kdenetwork4 (which is krdc) remmina virtualbox xen
If we now start providing an updated LibVNCServer, then I really wonder what will happen with the above packages in 12.2. They might still work, they might also not work. Or maybe your idea is to provide also these packages in KR410 ??
Of course it is easy to provide a fix for a single bug, but I believe that it is also our duty to keep an eye on other non-KDE packages that might get into troubles if we start providing updates that could cause issues in other areas.
The KDE team has always been very carefull with providing updates of system related packages in KDE repositories due to the described effect.
Okay, I stand corrected, and you're right. It's not possible to simply replace that module in 12.2. OTOH, krdc is crashing since 4.10. It might be related to a LibVNCServer update, as people have tested the *release* version positively. Coolo has added some patches, that probably just not work, if exercised (which are not with krdc < 4.10). What I can offer is a revert of krdc 4.10 to krdc 4.9.5, which is attached at the upstream bug report. That compiles and build fine with openSUSE 12.2, and even work as expected. Pete -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Montag, 25. März 2013 13:06:40 Hans-Peter Jansen wrote:
On Samstag, 23. März 2013 09:37:48 Raymond Wooninck wrote: [...]
Of course it is easy to provide a fix for a single bug, but I believe that it is also our duty to keep an eye on other non-KDE packages that might get into troubles if we start providing updates that could cause issues in other areas.
The KDE team has always been very carefull with providing updates of system related packages in KDE repositories due to the described effect.
Okay, I stand corrected, and you're right. It's not possible to simply replace that module in 12.2. OTOH, krdc is crashing since 4.10. It might be related to a LibVNCServer update, as people have tested the *release* version positively.
Coolo has added some patches, that probably just not work, if exercised (which are not with krdc < 4.10).
This one I got wrong again: it looks like gber@opensuse.org enabled gnutls in the LibVNCServer package at Nov 12, 2012, which was released as an updated package then and that change seems to be responsible for krdc 4.10 crashes.
What I can offer is a revert of krdc 4.10 to krdc 4.9.5, which is attached at the upstream bug report. That compiles and build fine with openSUSE 12.2, and even work as expected.
Pete -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
On Dienstag, 26. März 2013 14:13:18 Hans-Peter Jansen wrote:
it looks like gber@opensuse.org enabled gnutls in the LibVNCServer package at Nov 12, 2012, which was released as an updated package then and that change seems to be responsible for krdc 4.10 crashes.
https://bugzilla.novell.com/show_bug.cgi?id=812222
Pete -- To unsubscribe, e-mail: opensuse-kde+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-kde+owner@opensuse.org
participants (4)
-
Greg KH -
Hans-Peter Jansen -
Luca Beltrame -
Raymond Wooninck