Bug 23851

Summary:	regionset is broken
Product:	Mageia	Reporter:	Franz Holzinger <flink>
Component:	RPM Packages	Assignee:	Barry Jackson <zen25000>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	marja11, ouaurelien
Version:	6
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	regionset-0.2-1.mga6.src.rpm	CVE:
Status comment:

Description Franz Holzinger 2018-11-16 22:52:54 CET

Description of problem:

I have bought a new DVD MDISC writer where the region code has not been set. When I use the command shell and type regionset, then it aborts with an error message.

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


Steps to Reproduce:
1. Insert DVD into the DVD drive.
2. Open a command shell and type:

[root@localhost regionset]# sudo regionset /dev/sr1  
Current drive parameters for /dev/sr1:
  RPC Type: Phase II (Hardware)
  RPC Status: no region code set (bitmask=0xFF)
  Vendor may reset the RPC 4 times
  User is allowed change the region setting 5 times
Would you like to change the region setting for this drive? [y/n]: y
Enter the new region number for your drive [1..8]: 2 

3. This result is shown:
New RPC bitmask is 0xFD, ok? [y/n]: [root@localhost regionset]# 
You could not even press the 'y' button here.

However no regional code has been set.

Comment 1 Marja Van Waes 2018-11-17 09:54:24 CET

Assigning to the registered maintainer.

CC: (none) => marja11
Assignee: bugsquad => zen25000

Comment 2 Aurelien Oudelet 2020-08-16 21:49:50 CEST

Does this still valid in Mageia 7 or Cauldron ?

CC: (none) => ouaurelien

Comment 3 Aurelien Oudelet 2020-08-26 11:27:12 CEST

Since we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of our 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.

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