Version: 1.1.1 (using KDE 3.4.2 Level "b" , SUSE 10.0) Compiler: Target: i586-suse-linux OS: Linux (i686) release 2.6.13-15.7-default This happened on 1st run. The cursor is missing from the sky display. (invisible) This invisible cursor will tag any items that it runs over while moving the mouse; a right-click will show the pointer and the description box...the next click will render the pointer invisible again. The cursor becomes visible at the borders of the sky, but disappear again upon reentry. Same problem on restarting the program for the second time- no cursor except on toolbars and borders.
Hmm, this seems pretty bizarre to me. Does this happen every time you use KStars, or only on the first and second time? Did you happen to compile from source, or are you using Suse packages? I'm tempted to say that this is probably an X11/video driver issue. What version of X are you using, and what video card (and driver)? thanks for the report.
This bug has never been confirmed, and it sounds like a video driver issue. No reply from reporter, closing WORKSFORME.
Hi, I'm new to bug reporting, so hopefully adding a comment to this resolved bug is acceptable. Sorry if not. While reporting what I thought to be a new bug, this one came up as a potential duplicate. I can confirm that this bug does indeed describe the behaviour that I have experienced. I am running: Ubuntu 8.10, kernel 2.6.27-9-generic, GNOME 2.24.1. I am running KStars version 1.4.1. KStars was operating fine in Ubuntu 8.04, but since upgrading to 8.10 the problem has occurred. I am aware of another user experiencing the same problems. He is using the same OS and KStars versions, but is using different hardware. If any further system information is required to assist fault finding please let me know. p.s. Thanks for kstars - it really is great stuff.
confirming this bug. It has been happening ever since I switched to kde4.x I have experienced this on two systems with two different graphics cards.
I don't understand why this is marked as resolved. I have just installed kstars on ubuntu 8.10 and don't have the mouse visible when over the sky. It worked fine in 8.04, but not now. I do hope this can be rectified somehow. If it is a driver problem, what is the driver solution?
@jonobe This issue was reported long back and seems to be marked as resolved around the same time. I have a opened a new issue (# 178152) for the (what I think is) a newer problem.
*** Bug 178152 has been marked as a duplicate of this bug. ***
*** Bug 178438 has been marked as a duplicate of this bug. ***
Created attachment 29628 [details] Proposed change
Could someone using Qt compiled with warnings and experiencing this problem confirm if any warnings related to QPixmap::setMask() are printed?
According to https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-driver-i810/+bug/260630 this is a bug in the i810/intel driver.
The bug is also present with open source radeon driver when EXA is enabled: https://bugs.freedesktop.org/show_bug.cgi?id=18710
Seems to be no kstars bug at all.
Is there any chance of getting a workaround? For example an option to use the plain and standard "arrowhead cursor" in the star map display. I am just starting to use Kstars now on my EeePC 900 (Ubuntu 8.10 w/ array lean kernel 2.6.27-8-eeepc-lean and I have fetched the latest Kstars from the ubuntu stable repositories. I have not seen the standard behaviour but I get the impression that it would be a cross-hairs with higher precision than the standard (system/theme/... dependent) arrowhead cursor, however the standard cursor has much higher precision than no cursor at all. I really like the program, but it is nearly useless without being able to select stars on the star map. /Johan
@ Johan The workaround already exists: switch the accelleration mode of Xorg from EXA to XAA by editing the /etc/X11/xorg.conf file. And to get this fixed properly as soon as possible be sure to CC to the bug at https://bugs.freedesktop.org/show_bug.cgi?id=18710 and add more information about your system.
Just started using Linux after a long absence and just loaded KStars. I too am having the vanishing cursor problem. My xorg.conf file doesn't have an acceleration mode section. What do I do now??? Jim
(In reply to comment #16) > Just started using Linux after a long absence and just loaded KStars. I too am > having the vanishing cursor problem. My xorg.conf file doesn't have an > acceleration mode section. What do I do now??? Just open xorg.conf, find the section Device and inside it add the line: Option "AccelMethod" "XAA" Oh and, especially if you have a graphics card that is not ati or intel, please do add info about your hardware and drivers here: https://bugs.freedesktop.org/show_bug.cgi?id=18710
Freedesktop is not going anywhere with this bug. How about a KDE-specific workaround. Sure, _I_ can work around the problem but many users cannot. I am experiencing the bug on an ATI-powered laptop, KDE 4.3 beta2.
Dotan, the bug has to be fixed in the drivers. Then no workaround is needed by anyone. The bug should be fixed for ATI using a recent driver version according to the freedesktop bug report. Perhaps your driver is not up to date. When you update it the fix should be there. Otherwise ping the X people.
Since this bug has been left resolved in upstream, I think we should apply our local fix on KStars as Dotan points out - although I completely agree that there is no reason to do so. I understand that this bug is really painful (I had this problem with someone's laptop yesterday) for users, and if we can work around it within KStars, why not? What do you think, Médéric? If the workaround makes things work just fine, now that upstream has resolved the bug, we don't have reason to leave it as it is, right?
If the upstream bug will filter down to end users in a reasonable time frame (say, before KDE 4.3 is released) then I agree that it would be a waste of resources to patch Kstars. But if KDe 4.3 is to be released before the drivers hit the end user, then Kstars should take the steps necessary to work around the issue.
While i deeply hate the idea to put workarounds in the code to avoid upstream bugs it might be a good idea to put it in 4.3 to help end users. However i prefer it not to be applied in trunk, just to make sure the bug is indeed fixed with newer versions of the drivers. As end users do not use trunk anyway, that should not be a problem. So what do you think about this compromise?
Yes. That looks like a reasonable compromise.
> So what do you think about this compromise? Great! Thanks!
SVN commit 989844 by asimha: Applying a fix for bug 120581 in the KDE 4.3 branch. This is an upstream issue, which we however decided to work-around in the KDE 4.3 branch, so that users could benefit. Many thanks to Eckhart Woerner for the patch. CCBUG: 120581 CCMAIL: kstars-devel@kde.org M +2 -2 skymap.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=989844
*** Bug 189000 has been marked as a duplicate of this bug. ***