systemsettings > Display Configuration shows bogus monitor
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xorg-server (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
Starting from Kubuntu 14.04, when I open systemsettings > Monitor > Display Configuration, I see, additionally to my built-in monitor on my laptop (Samsung RF511 - monitor displayed as "Seiko Epson Corporation"...) an additional screen named "VGA-1-2" - which is enabled.
This "monitor" is detected despite it does not exist. I discovered that because some apps I started did not appear on screen, and the mouse cursor somehow "vanished" behind the right screen edge, until I found out that they were placed on that second screen - I could "drag" the windows per Alt+LeftClick blindly from somewhere in the right to my actual monitor.
a screnshot of systemsettings is attached.
Then I attached a *real* second monitor to my laptop - systemsettings detects it correctly and expands the screen - but now tells me that I have *three* monitors...
This is really a regression to 13.10, and as the monitor is detected *and* enabled by default, it is not really good to work with, as windows are "vanishing" somwehere.
I can reproduce this behaviour with a Kubuntu live ISO on my system. So it is NOT my misconfiguration ;-)
I before had Kubuntu 13.10 with KDE 4.12.5, running well without this bug.
I am using a laptop with optimus graphics: intel/nvidia card, corresponding lspci lines:
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
01:00.0 3D controller: NVIDIA Corporation GF108M [GeForce GT 540M] (rev a1)
What else (log files etc) do you need from me to help resolve this bug?
---
.tmp.unity.
ApportVersion: 2.17.2-0ubuntu1.5
Architecture: amd64
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
CompositorUnred
CompositorUnred
CurrentDesktop: Unity
DistUpgraded: 2015-05-21 14:12:51,319 DEBUG enabling apt cron job
DistroCodename: vivid
DistroRelease: Ubuntu 15.04
DistroVariant: ubuntu
DkmsStatus:
vboxhost, 4.3.30, 3.19.0-26-generic, x86_64: installed
vboxhost, 4.3.30, 3.19.0-28-generic, x86_64: installed
ExtraDebuggingI
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0116] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Samsung Electronics Co Ltd Device [144d:c0a5]
InstallationDate: Installed on 2015-02-25 (213 days ago)
InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1)
MachineType: SAMSUNG ELECTRONICS CO., LTD. RF511/RF411/RF711
Package: xorg 1:7.7+7ubuntu4
PackageArchitec
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
Tags: vivid ubuntu compiz-0.9
Uname: Linux 3.19.0-28-generic x86_64
UpgradeStatus: Upgraded to vivid on 2015-05-21 (128 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 04/26/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 10HX.M034.
dmi.board.
dmi.board.name: RF511/RF411/RF711
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: 10HX
dmi.chassis.
dmi.chassis.type: 9
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: RF511/RF411/RF711
dmi.product.
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
version.compiz: compiz 1:0.9.12.
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.60-2
version.
version.
version.
version.
version.
version.
version.
version.
xserver.bootTime: Tue Sep 22 11:36:07 2015
xserver.configfile: default
xserver.errors:
Failed to load module "nvidia" (module does not exist, 0)
Failed to load module "nvidia" (module does not exist, 0)
NOUVEAU(G0): [XvMC] Failed to initialize extension.
xserver.logfile: /var/log/Xorg.0.log
xserver.outputs:
product id 13642
vendor SEC
xserver.version: 2:1.17.1-0ubuntu3
description: | updated |
Changed in xorg (Ubuntu): | |
status: | Incomplete → Triaged |
tags: | removed: vivid wily |
Hi there!
Thanks for reporting this bug! Your bug seems to be a problem with the KDE program itself, and not with our KDE packages. While we appreciate your issue, it would be better if it was tracked at https:/ /bugs.kde. org, so that the KDE developers can deal with this speedily and have direct communication with you as the reporter for more effective debugging.
Thanks!