Bug 15078 - K3b doesn't burn CDs - cdrdao permissions error
Summary: K3b doesn't burn CDs - cdrdao permissions error
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Juan Luis Baptiste
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-01-18 13:16 CET by Marcello Anni
Modified: 2015-10-27 06:58 CET (History)
1 user (show)

See Also:
Source RPM: k3b-2.0.2-12.mga4.tainted
CVE:
Status comment:


Attachments
k3b error (3.74 KB, text/plain)
2015-07-08 15:21 CEST, Marcello Anni
Details

Description Marcello Anni 2015-01-18 13:16:31 CET
Hi,

i've tried to burn a data CD and k3b after starting the burning process hangs and it prompts an error related to cdrdao permissions. this issue has been noticed also by an other italian user. can you help me to fix this issue? thanks


cheers,
Marcello
David Walser 2015-01-18 19:17:28 CET

CC: (none) => shlomif
Assignee: bugsquad => juan.baptiste

Comment 1 Juan Luis Baptiste 2015-01-19 05:09:54 CET
Please at least post the error message, I don't have a cauldron box now to test.
Comment 2 Marcello Anni 2015-07-08 15:21:35 CEST
Created attachment 6824 [details]
k3b error

here it is, i'm sorry for being late..
Samuel Verschelde 2015-09-21 10:19:02 CEST

Attachment 6824 mime type: application/octet-stream => text/plain

Comment 3 Samuel Verschelde 2015-09-21 13:22:02 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 4 Marja Van Waes 2015-10-27 06:58:54 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


Note You need to log in before you can comment on or make changes to this bug.