Bug 4689

Summary:	Something ate my Xvnc ( vnc / tigervnc ) server configuration from xorg.conf
Product:	Mageia	Reporter:	Morgan Leijström <fri>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	Normal
Version:	1
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	Drakxtools	CVE:
Status comment:

Description Morgan Leijström 2012-02-25 02:03:34 CET

Sorry i do not know much yet, but i post it here to add later if i can catch it - or someone else can.

__Background
I mostly have physically connected keyboard and monitor to home server, but i plan to use vnc. I set up tigervnc server including necessary manual configuration in xorg.conf on 2012-01-11, but realised last week it did not work anymore.

__Symptom:
On the client, tigervnc viewer say after i enter the password:
"No password configured for VNC Auth"

However that is misleading;

__Damage:
What actually happened is that on the server configuration had gone missing in xorg.conf:
The vnc line under Modules section is intact,
but all three Option lines in section Screen had vanished.

__Cause:
Something (XFdrake?) that massages xorg.conf wrecked it.
But what initialises massaging of xorg.conf?
I do not remember fiddling with graphic settings...
... but i maybe changed screen resolution as i changed monitor.
Can an update trigger some work on xorg.conf?
Something massaged xorg.conf on 2012.01.30 as i see it differs slightly from current xorg.conf, but only difference is that two successive lines changed places.

So my settings vanished between 2012-01-11 and 2012-01-30

Top line in xorg.conf say it was created by XFdrake rev 262502
Drakxtools installed is currently 13.58

I found someone else who found same problem, and his theory:
http://article.gmane.org/gmane.network.vnc.tigervnc.user/142 with copy at
http://www.mail-archive.com/tigervnc-users@lists.sourceforge.net/msg00141.html

There you also see the exact three lines i also found missing.

Comment 1 Manuel Hiebel 2012-11-05 16:51:40 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 2 Manuel Hiebel 2012-12-02 14:31:37 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