Bug 6369

Summary:	display stop With Catalyst when the network cable is out
Product:	Mageia	Reporter:	A de Saint Mont <contact>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	Normal	CC:	anssi.hannula, jquelin, marja11, rwobben
Version:	2	Keywords:	NEEDINFO
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:	catalyst	CVE:
Status comment:

Description A de Saint Mont 2012-06-07 10:16:43 CEST

Description of problem:
With Catalyst only, display stop when the network is on start with the session and no cable conected. No problem when the cable is conected or when the network service is config on don't start the conexion with the session. That probleme is notoced with 3 differents computers and 3 differents AMD videocarts.

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


How reproducible:
When the network cable is out

Steps to Reproduce:
1.Install Mageia2 + Catalyst in x86_64
2.Make the network cable out
3. Start the computer and start a session (Lxde, Gnome, and so long)

Comment 1 Marja Van Waes 2012-11-29 21:44:32 CET

CC'ing catalyst maintainer

@ jquelin

Is this expected behaviour or a bug?

CC: sysadmin-bugs => jquelin, marja11
Component: Release (media or process) => RPM Packages
Source RPM: (none) => catalyst

Comment 2 Jerome Quelin 2012-11-30 10:42:59 CET

Sorry, wrong maintainer. I guess the reporter speaks about catalyst-the-proprietary-amd-driver, not catalyst-the-perl-module.

I'm only maintaining the latter, not the former. I cannot find the catalyst rpm, so i don't know who the maintainer is - I guess that's Anssi, though.

Comment 3 Marja Van Waes 2012-11-30 10:50:43 CET

(In reply to comment #2)
> Sorry, wrong maintainer. I guess the reporter speaks about
> catalyst-the-proprietary-amd-driver, not catalyst-the-perl-module.
> 
> I'm only maintaining the latter, not the former. I cannot find the catalyst
> rpm, so i don't know who the maintainer is - I guess that's Anssi, though.

Thx, JerÃ´me

The only catalyst I could find, were your packages, so I guess we don't have that driver in our repositories (which would make this bug invalid)

@ A de Saint Mont

Where did you find the catalyst you installed?

@ anssi

Feel free to comment :)

Keywords: (none) => NEEDINFO
CC: (none) => anssi.hannula

Comment 4 roelof Wobben 2013-01-05 20:46:22 CET

@ A de Saint Mont

Can you give a answer to comment 3. Otherwise we have to close this bug

@ anssi.

Can you shine a light on this matter ?

Roelof

CC: (none) => r.wobben

Comment 5 Manuel Hiebel 2013-10-22 12:09:04 CEST

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

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 2'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 2 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.

-- 
The Mageia Bugsquad

Comment 6 A de Saint Mont 2013-10-22 13:38:29 CEST

No problem. With Mageia 3 ther are not bugs !
The solution was to make wait X start 3s.

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