Bug 108907 - klipper doesn't remember the screen on which it was last used
Summary: klipper doesn't remember the screen on which it was last used
Status: RESOLVED FIXED
Alias: None
Product: kde
Classification: I don't know
Component: dualhead (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-07-11 12:05 UTC by Petteri Räty
Modified: 2008-12-17 19:58 UTC (History)
0 users

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 Petteri Räty 2005-07-11 12:05:00 UTC 
Version:            (using KDE KDE 3.4.1)
Installed from:    Gentoo Packages
Compiler:          i686-pc-linux-gnu-3.4.4 
OS:                Linux

background:
I have a two screens. :0.0 is a CRT and :0.1 is a TFT. This is because of the way the NVidia driver works at the moment. I use the TFT as my main screen. I have xorg-x11 set up to use dual head. 

problem:
I would like to klipper to autostart on my TFT screen. Now I have to always start klipper manually because autostarting klipper puts it to the CRT screen (:0.0). I regularly use actions so I must have the action window on my TFT screen. 

How to correct:
When I close klipper and it asks if I want to automaticly start it with KDE, it should save the $DISPLAY in use and start it on that screen when KDE is started next time.
Comment 1 Petteri Räty 2008-12-17 19:58:05 UTC 
Klipper seems to work ok in KDE 4.1.3.