Bug 168231 - Mouse pointer disappears inside the window of a crashed Kate
Summary: Mouse pointer disappears inside the window of a crashed Kate
Status: RESOLVED WORKSFORME
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-03 17:19 UTC by Torquil Macdonald Sørensen
Modified: 2008-12-19 20:52 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Torquil Macdonald Sørensen 2008-08-03 17:19:41 UTC 
Version:            (using KDE 4.1.0)
Installed from:    Debian testing/unstable Packages

I was running Kate, and it apparently crashed as I was viewing .xsession-errors. But, the problem I'm reporting here is that the mouse pointer was subsequently invisible when it pointed anywhere inside the window of the crashed Kate. I had maximized the kate window earlier, so the mouse pointer was only visible when it was pointing at the titlebar of the kate window, or the panel at the bottom. After starting a konsole on top of the kate window, the mouse was also visible there. It is only the tip of the mouse pointer that determines if the whole mouse pointer is visible or not.

Best regards,
Torquil Sørensen
Comment 1 Dario Andres 2008-12-19 14:31:34 UTC 
Have you experienced this bug again with a recent KDE version? (4.1.3 / 4.2beta(1/2) , 4.2svn) ? Thanks :)
Comment 2 Torquil Macdonald Sørensen 2008-12-19 20:48:33 UTC 
No it happened only that one time. Don't know if it is because kate has not crashed again or if something has been fixed in the mouse pointer area... I have been using KDE4.1.3 and I can not remember anything like this happening there.
Comment 3 Dario Andres 2008-12-19 20:52:36 UTC 
If you can't reproduce this bug and you haven't experienced it in a while I'm marking this bug as resolved as WORKSFORME. If you experience this bug again later you can re-open this bug report :) Thanks :)