Bug 47224

Summary:	background image split over several monitors
Product:	[I don't know] kde	Reporter:	Jesper Pedersen <blackie>
Component:	xinerama	Assignee:	Unassigned bugs <unassigned-bugs-null>
Status:	RESOLVED DUPLICATE
Severity:	wishlist
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	Compiled Sources
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Jesper Pedersen 2002-08-30 13:22:26 UTC

(*** This bug was imported into bugs.kde.org ***)

Package:           xinerama
Version:           KDE 3.0.7 CVS/CVSup/Snapshot
Severity:          wishlist
Installed from:    Compiled sources
Compiler:          any
OS:                Linux
OS/Compiler notes: Not Specified

If I use Xinerama and I have a background image for KDesktop then the image is split over both monitors (in case of two minitors ;-)

This is annoying in the case where my background image is rather small (a cartoon for example) because part of the cartoon is on one monitor and the rest is on the other.

(Submitted via bugs.kde.org)

Comment 1 Dan 2004-02-03 09:35:17 UTC

I'm having the exact same problem.  Here's my suggestion: provide selections so that either the same image or different images can be used on both displays (or all displays, up to the number of displays).  Also, for the "slideshow" mode, allow different images to be displayed on the two (or more) monitors.

Comment 2 p92 2004-03-11 09:55:45 UTC

I agree with comment #1 and vote for this

Comment 3 Christoph 2004-05-09 13:13:14 UTC

It would even help to make unscaled images not centered but begin on
the left of right side of the desktop. One wouldn't even have to care about
Xinerama then

Comment 4 Christoph 2004-05-09 13:16:17 UTC

It would help to make unscaled background-Images not be centered, but
begin on the left or right side. Images with the size of one screen would then
be only on that screen then instead of beeing split because they are displayed in the middle of the Desktop.

Comment 5 Michael Jahn 2004-08-02 19:51:11 UTC


*** This bug has been marked as a duplicate of 42778 ***