Bug 2701

Summary:	KRandRTray doesn't write a correct xorg.conf file
Product:	Mageia	Reporter:	Koos Uys <uyskoos>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Normal	CC:	balcaen.john, marja11
Version:	1	Keywords:	UPSTREAM
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	kdebase4-workspace-4.6.5-1.4.mga1	CVE:
Status comment:

Description Koos Uys 2011-09-11 05:05:42 CEST

Description of problem:

This is a bit of a multiple problem and I will try to explain why I have put them together in this bug report.

I am using a dual monitor setup. One of the problems that I always had on avery Linux Distro I tried, was that KRandrTray was never able to configure the 2 displays correctly and I had to manually edit the xorg.conf file to make two monitors work on my Mandriva 2008. I then used the onboard screen card to drive one monitor and my Nvidia card to drive the other.

However, after Mandriva 2008 I could never make the dual monitors work again by configuring xorg.conf and I was stuck with Mandriva 2008 since.

When I made a new installation of Mageia, at least the two monitors worked out out the box, but the second monitor had a problem that the windows had no decorations. See the bug reported below about how I solved that.

https://bugs.mageia.org/show_bug.cgi?id=2626

Do note that KRandRTray was not able to store the configuration and at the next boot, I had to config the two screens again after every boot.

I then installed the propriety Nvidia driver

Right, with the Nvidia drivers the above problems was solved but now I had the much reported issue of the Nvidia card making a lot of artefacts. Also, my computer froze often. Then the screens would both go black for a second or two like it is resetting and when it came back on, I could work again. This freezing became worse when I adjusted the output quality on the Nvidia package to a higher value, and when playing DVD's.

Well, it now seems that I could solve the above problem by editing the xorg.conf file and I changed the Driver to "nouveau" instead of the "nvidia" driver. The screens are now stable and I have no artefacts. When I started KRandRtray again, it was for the first time showing everything in the way I expected to see it for my configuration but I don't want to mess with it.

This comes down to the following:

1. The Nvidia propriety software writes the xorg.conf file correctly.
2. However, the latest Nvidia propriety driver itself if buggered.
3. KRandRTray was unable to detect the hardware correctly and write the xorg.conf file correctly, but it worked correctly once it had the correct xorg.conf file written by Nvidia.

To summarise:

1. At initial install, my dual monitors was not configured correctly and KRandRTray could not sort it out. It wrote a poor xorg.cong file.
2. I installed the Nvidia propriety drivers and using that to config the hardware worked and it wrote a good xorg.conf file. However, the Navidia propriety driver is unstable.
3. I then simply edited the xorg.conf file written by the Nvidia propriety software by changing the driver from "nvidia" to "nouveau"
4. Stability issues was solved and KRandRTray now showed the correct parameters of the config although I do not want to take another change to see what happens if I change configs on KRandRTray

So there is definitely an issue with KRandRTray and of course, the Nvidia Driver.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.
2.
3.

Comment 1 John Balcaen 2011-09-11 10:21:09 CEST

Nothing can be done on the nvidia driver part (it's a proprietary driver.) & i'm not sure krandtray can deal with it (nvidia proprietary driver come with his own tool).
You should try configure your two monitors with krandtray & nouveau as the graphic drivers to see if everything is ok.
If there's a problem with this setup than you should report the bug upstream against krandtray.

Regards,

CC: (none) => balcaen.john

Manuel Hiebel 2011-09-11 10:44:12 CEST

Component: Release (media, process) => RPM Packages

Comment 2 Koos Uys 2011-09-11 11:01:33 CEST

I suppose it was like that, since Mageia installed the nouveau driver by default. So I reckon it is then a KrantRTray report.

Comment 3 Marja Van Waes 2011-11-25 15:15:36 CET

@ Koos

Did you report upstream? If so, could you please put a link to the upstream bug report in the Bug URLs field of this report?

Keywords: (none) => UPSTREAM
CC: (none) => marja11
Summary: Multiple Issue: Nvidia Driver Artefacts and Krandrtray Config => KRandRTray doesn't write a correct xorg.conf file
Source RPM: (none) => kdebase4-workspace

Comment 4 Marja Van Waes 2012-01-22 19:33:43 CET

@ Koos

Can you please reply to comment 3?

Comment 5 Koos Uys 2012-01-22 19:42:03 CET

No, I did not report this one upstream back then. I just stepped into a new job then with the  resultant grinding to get on top.

Comment 6 Marja Van Waes 2012-01-23 00:07:30 CET

(In reply to comment #5)
> No, I did not report this one upstream back then. I just stepped into a new job
> then with the  resultant grinding to get on top.

:)

A quicksearch shows one or two bugs that remind me of yours. 
https://bugs.kde.org/buglist.cgi?quicksearch=KRandRTray

Do you agree on closing this bug for now as worksforme, since you found a workaround? It can then be reopened when it got fixed upstream.

Comment 7 Marja Van Waes 2012-04-13 16:59:42 CEST

@ Koos

If this problem wasn't solved by an update, did you happen to try whether it also exists in cauldron?

Comment 8 Koos Uys 2012-04-13 17:19:46 CEST

Nope. My main monitor finally went dead and I replaced it with a 24" Samsung, so I am not currently running dual monitor.

Comment 9 Marja Van Waes 2012-04-13 18:46:43 CEST

(In reply to comment #8)
> Nope. My main monitor finally went dead and I replaced it with a 24" Samsung,
> so I am not currently running dual monitor.

OK, thanks for telling us. 

KRandRTray (kdebase4-workspace) is still on the same version as end of november (4.6.5-1.4.mga1), so it is not likely this got solved in Mageia 1

Source RPM: kdebase4-workspace => kdebase4-workspace-4.6.5-1.4.mga1

Comment 10 Manuel Hiebel 2012-11-05 16:54:23 CET

This message is a reminder that Mageia 1 is nearing its end of life. 
In approximately 25 days from now, Mageia will stop maintaining and issuing 
updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it 
remains open with a Mageia 'version' of '1'.

Package Maintainer: If you wish for this bug to remain open because you plan to 
fix it in a currently maintained version, simply change the 'version' to a later 
Mageia version prior to Mageia 1's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not 
be able to fix it before Mageia 1 is end of life.  If you would still like to see 
this bug fixed and are able to reproduce it against a later version of Mageia, 
you are encouraged to click on "Version" and change it against that version 
of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, 
sometimes those efforts are overtaken by events. Often a more recent Mageia 
release includes newer upstream software that fixes bugs or makes them obsolete.

--
Mageia Bugsquad

Comment 11 Manuel Hiebel 2012-12-02 14:36:39 CET

Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 is no 
longer maintained, which means that it will not receive any further security or 
bug fix updates. As a result we are closing this bug. 

If you can reproduce this bug against a currently maintained version of Mageia 
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => WONTFIX