Bug 308196

Summary:	always starts on display:0 even if command issued from display:1 --- systems has two separate x-windows
Product:	[I don't know] kde	Reporter:	Bill Turner <bt.kde>
Component:	dualhead	Assignee:	Unassigned bugs mailing-list <unassigned-bugs>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	andrew.crouthamel, cfeck
Priority:	NOR
Version:	4.8
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Bill Turner 2012-10-10 20:06:08 UTC

I have two separate x-screens defined. (Geforce 8600 dual port card) If I try to start Konqueror, Konsole and a few other products on Display:1 -- they always start on display:0

Reproducible: Always

Steps to Reproduce:
1. Define two x-screens on a system with a dual port video card
2. Try to start  Konqueror or Konsole on display:1    It will always start on display:0
3.  This generally does not happen with gnome products


Expected Results:  
It should have started on Display:1

A number of KDS products operate this way.  It totally invalidates having two separate x-screens...

Comment 1 Christoph Feck 2012-10-10 23:39:47 UTC

How do you start the applications? Using "DISPLAY=:1 command"  in Konsole?

Comment 2 Christoph Feck 2012-10-10 23:42:35 UTC

For Konqueror, disable preloading or instance sharing. For other applications, that use a single process for multiple invocations, such as Konsole, try running with "--nofork".

Comment 3 Bill Turner 2012-10-15 14:31:36 UTC

Sorry for the delay in responding - I have been out of town.

When I get home, I will check to see how they are being started. I beleive I was using each screens Application Launcher Menu under the assumption that the applications would "inherit" the display Id from the screen they were started on.  (Each x-window has its own copy of the Application Launcher Menu)...

I will post what I discover.  Thanks for the hints!!!

Comment 4 Andrew Crouthamel 2018-11-09 00:52:26 UTC

Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!

Comment 5 Bill Turner 2018-11-10 00:34:57 UTC

I have no idea if this bug still exists.

I do not run KDE any more, and haven't for years.

Comment 6 Andrew Crouthamel 2018-11-10 01:31:03 UTC

Thanks for the update!