Bug 14118

Summary: With Mageia 4 K3b sees only one of two installed optical device
Product: Mageia Reporter: Sohel Fares <sohel>
Component: RPM PackagesAssignee: Juan Luis Baptiste <juan.baptiste>
Status: RESOLVED OLD QA Contact:
Severity: normal    
Priority: Normal    
Version: 4   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: K3B 12.mga4 x86_64 and 12.mga4.tainted (K3b is 2.0.2) CVE:
Status comment:

Description Sohel Fares 2014-09-18 23:08:34 CEST
Description of problem:

Mageia 4 was installed as an additional OS in a multiple boot system along with Mandriva 10 and Windows 7. System is a x86_64. The following problem does not appear with Mandriva 10.

System includes 2 optical devices used to be able to duplicate CD or DVD.
Optical devices are both Optiarc DVD RW A-7240s
Processor AMD Phenom II X4 955
Motherboard is ASUS M4A79TXDEVO AMD 790X 

K3b only reports and displays all about dev/sr1. dev/sr0 is not seen at all even in the K3b configuration device window. I could not find any way to activate it. Other programs like Kaffeine or VLC that deal is the optical devices can deal with any of sr1 or sr0. 

This problem is not present when I boot Mandiva 10 on the same computer. Problem persisted even when I displaced one of the devices SATA cable to a free input on the motherboard.

Search on internet did not yield any similar problem. I removed/re-installed K3b in both x86_64 or 586 format with same behaviour.

The problem is there all the time so 100% reproductible.

Until fixed is there any manual intervention that allows me to activate the ignored device?

Thanks


Reproducible: 

Steps to Reproduce:
Comment 1 Sohel Fares 2014-09-18 23:10:08 CEST
Actually it is Mandriva 2010 not Mandriva 10.
David Walser 2014-10-08 00:59:17 CEST

Assignee: bugsquad => juan.baptiste

Comment 2 Samuel Verschelde 2015-09-21 13:21:35 CEST
Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer 
maintained, which means that it will not receive any further security or bug 
fix updates.

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.

Bug Reporter: Thank you for reporting this issue and we are sorry that we weren't 
able to fix it before Mageia 4's end of life. If you 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. If it's valid in several versions, 
select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.

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.

If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].

[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/
Comment 3 Marja Van Waes 2015-10-27 06:58:33 CET
As announced over a month ago, Mageia 4 changed to end-of-life (EOL) status on 2015-09-19. It is is no longer maintained, which means that it will not receive any further security or bug fix updates.

This issue may have been fixed in a later Mageia release, so, if you still see it and didn't already do so: please upgrade to Mageia 5 (or, if you read this much later than this is written: make sure you run a currently maintained Mageia version)

If you are able to reproduce it against a maintained version of Mageia, you are encouraged to 
1. reopen this bug report, by changing the "Status" from "RESOLVED - OLD" to "REOPENED"
2. click on "Version" and change it against that version of Mageia. If you know it's valid in several versions, select the highest and add MGAxTOO in whiteboard for each other valid release.
Example: it's valid in cauldron and Mageia 5, set to cauldron and add MGA5TOO.
3. give as much relevant information as possible. If you're not an experienced bug reporter and have some time: please read this page:
https://wiki.mageia.org/en/How_to_report_a_bug_properly

If you see a similar issue, but are _not_sure_ it is the same, with the same cause, then please file a new bug report and mention this one in it (please include the bug number, too). 


If you would like to help fixing bugs in the future, don't hesitate to join the
packager team via our mentoring program [1] or join the teams that fit you 
most [2].
[1] https://wiki.mageia.org/en/Becoming_a_Mageia_Packager
[2] http://www.mageia.org/contribute/

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