KDE-Forum.org

Guys,

I had posted this query on the Distributions/Redhat & Fedora Core 1 forum, however, since I received no replies, I thought I would try this forum. Who knows, we may get lucky!
-----
First - the systems involved: one desktop and one laptop using FC1.
Second - the problem: since updating to KDE version 3.1.5, we have noticed a dramatic increase in the way the cursor grabs icons by mistake when using Konqeror! All that is necessary to have this happen is to move the cursor over an icon and the icon is picked up by mistake. (BTW, we use double-click action, not single-click!)

This occurs with both a mouse and a laptop's touchpad and it doesn't happen all times but it does indeed happen way too often. So far we have been lucky in that nothing was moved out of place but it just a matter of time!!!

I have seen this problem mentioned in another post on the 'net (not here!) but have never come across a fix, or even a reason why it occurs.
-----
Since making the original post, we have tried changing the mouse settings with no better results.

Any ideas???

Thanks in advance...

Guys!

The above post is no joke!

When I first started to experience this phenomenon I was using a laptop which was new to me at the time so I just put this on me, tapping the touchpad twice without really knowing I did, thereby grabbing the icon. However, this idea was dropped when a friend told me he was having the same problem with his desktop and trackball! We are both using FC1 and we are roughly on the same linux learning curve - for what it's worth.

The hell of it is this didn't happen until we updated from FC1's version of KDE (v-3.1.4) to KDE's version 3.1.5 and it happens only in konqueror. The more I think about this, the more I think maybe it's just something with konqueror!?! We just don't know what's going on here but it does happen with some regularity.

Any one with any ideas what is going on here???

hypercube, thanks for responding to my post!

While this whole thing is a pain in the butt, I'm glad to hear we are not alone. And you're right, it's the folder icons in the tree are what's grabbed and I apologize for not stating this. So far my friend and I have been lucky in that no folders have been moved from the tree (when using the su konqueror is especially scarey).

Any one else out there who has noticed this??? Hell, any one out there who has a fix, feel free...

Thanks for the info. I will ad mine to the mix as well...

Yeah, you may be right! Although, there have been some using v-3.2 that have reported this same problem is still persisting. It seems to be very indiscriminate as well as you never know when it will strike. For instance, my friend and I have never seen this bug until we updated to v-3.1.5 in FC1. And we have tried out just about all of the major distros over the last couple of years. Hell, we even have a HDD install of Knoppix on our systems and the bug has never come to light!!! But it sure in hell is active here in our FC1 installs...

For as many times as I have tried to update to version 3.2.1 of KDE (from v-3.1.5), I run into dependency problems with, ultimately, gtk+-1-1.2.10-28.1.fdr.3.1.i386.rpm. There are other packages I need to remove even to get to *this* point in the update process! I had used yum to update KDE to version 3.1.5 and now I'm a little hesitant in trying to go further without additional info on this package and it's deps. Since it was installed with the v-3.1.5 updates I don't know how to handle things from here on out. Just saying the hell with it and remove it anyway doesn't seem quite right at this point. Just dawned on me, maybe the repo I use for the v-3.1.5 updates now have the v-3.2.1 updates! If it does, the deps issues should be nulled!!! Hmmm...

As I have said many times in the past, I know just enough about Linux to screw things up but good without really trying ;-)

Ain't Linus Fun!?!

hypercube,

I finally got version 3.2 installed! Got all but 2 packages via yum, taglib I got right from KDE but valgrind I had to go to Dag's repo. I'm glad he had it available. Thanks Dag!

Now the testing begins. I will keep this thread updated, especially if I find that the bug is still 'alive'...

Ciao,

Hey guy!

Well, so far so good! And I did go with version 3.2.0 for a couple of reasons...first, less work involved with deps and second, I wanted to see for myself if it was present in this version. And so far I have NOT come across this bug! With just a single day's usage, there is no way I can say that the bug isn't present - just that I haven't come across it yet. But it does look good - FOR THIS SYSTEM AND ONLY THIS SYSTEM! I cannot be in agreement with those other guys in saying it's fixed - no, not at all!

FYI - I did run into a problem with being unable to log into any other desktop, only KDE would it let me log into! I did 'fix' this however. I found that the update tp v-3.2.0 added a second line to /etc/sysconfig/desktop. This is a script which normally contains but a single line: DESKTOP=KDE (or GNOME). The update added this line: DISPLAYMANAGER=KDE thereby forcing KDM to log into KDE regardless of the selection made by the user. Once I rem'ed out this line, I was then able to log into my other desktops. My buddy calls me 'fickle'...I tell him I'm 'curious' ;-)

hypercube, I will surely let you, and the world, know if the topic of this thread should crop up on me in this version. And, btw, I agree with what you say in your last post. We shall see...

Hey hypercube,

Have you seen the latest @

http://bugs.kde.org/show_bug.cgi?id=59113

It looks like this bug is still present in V-3.2.1 in Debian but it occurs less then it did, according to it's author.

As for me, so far I haven't seen it since I update to v-3.2.0 and believe me, I have tried to cause it!