Description of problem: I've attached another monitor (HDMI cable) to my laptop. When I plug it in, systemsettings>Hardware>Display and Monitor pops up a window for choosing how the new monitor is to be used (to the left, to the right, etc) but after making a choice, nothing happens. The monitor doesn't get the signal and its presence is not shown at systemsettings. This is a hybrid graphics laptop. I've installed mageia-prime but, as reported at bug 24545, had to do mageia-prime-uninstall. In another laptop, without mageia, the attached monitor worked just fine. Steps to Reproduce: What I did was to connect via HDMI the new monitor and tried to configured it in Systemsettings.
After updating kernel to 5.0.3-2, I could again use mageia-prime-install to have the dedicated GPU support. In this case, with nvidia support, the second monitor is working just fine. Thus, I guess, the problem seems to be related to some configuration in xorg.conf mageia-prime-uninstall uses to return to use the integrated GPU. That is, I can use a second monitor only I do mageia-prime-install. If I use mageia-prime-uninstall I loose the second monitor and also receive this annoying message before X server load: "Detected loaded display driver kernel module which conflicts with the driver the X server is configured to use. Startup of the X server may now fail." Should I file a bug about mageia-prime at MGA7 beta2?
Well, I think it would be better to close this bug and to open another one, more clearly stated, about mageia-prime with integrated GPU and how it prevents using an attached second monitor. How do I close this or simply change its scope/focus/title? Thanks
(In reply to Adelson Oliveira from comment #2) > Well, I think it would be better to close this bug and to open another one, > more clearly stated, about mageia-prime with integrated GPU and how it > prevents using an attached second monitor. How do I close this or simply > change its scope/focus/title? > > Thanks I'm not sure it should be closed, systemsettings>Hardware>Display and Monitor should either not show options that aren't available, or show a message when it can't change the settings. Assigning to the KDE maintainers.
Source RPM: (none) => systemsettingsAssignee: bugsquad => kdeCC: (none) => marja11
In fact, the window showing options on how to use the second monitor pops up as soon as I plug the second monitor. It doesn't matter if systemsettings is open or not. So, I'm not sure this window has anything to do with KDE or Xorg, sorry for this misleading info.
(In reply to Adelson Oliveira from comment #4) > In fact, > > the window showing options on how to use the second monitor pops up as soon > as I plug the second monitor. It doesn't matter if systemsettings is open or > not. So, I'm not sure this window has anything to do with KDE or Xorg, sorry > for this misleading info. I think it is desktop-dependant, but to be sure you can test what happens when you use e.g. Xfce instead of Plasma5, does the exact same window with options for the second monitor pop up, or a different window with such options, or... ?
Tried with IceWM, don't have Xfce. First, if the second monitor is plugged in before booting, the SDDM already sees it. It seems to be a configuration of the system that a regular user made (?). If the second monitor is plugged in after boot and login in Plasma, the X11 is refreshed (not restarted) and my configuration takes place. Second monitor has signal then. If the second monitor is plugged in after boot and login in IceWM, the X11 is not refreshed, no signal goes to the second monitor. If the second monitor is plugged in before boot and I login in IceWM, the second monitor shows the IceWM too but not as a left extension of the main monitor. Somehow the configuration is not holding. That configuration window does not pops up any more. It may be that once I configured it (as regular user...) it holds for the whole system...
Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Resolution: (none) => OLDStatus: NEW => RESOLVED