Bug 450739
Summary: | k3b: dvd burning requires raising limits | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Nadav Kavalerchik <nadavkav> |
Component: | k3b | Assignee: | Roman Rakus <rrakus> |
Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | 8 | CC: | joachim.backes, rdieter, tsmetana |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-07-14 08:36:26 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Nadav Kavalerchik
2008-06-10 18:59:58 UTC
for now, i have set these parameters in : /etc/scurity/limits.conf root soft memlock unlimited root hard memlock unlimited which worked around this issue BUT i am not sure what impact it has on the system ? :-( ? i have and LTSP server that runs 70 clients and i wonder if i can change these parameters system-wide ? so this issue is half closed :-) Roman, thoughts here? I don't have any dvd's handy to test. Can you confirm? Is this a k3b or wodim issue? I think it's similar to bug #220481. Nadav try to: 1) Start K3b 2) Go to Settings->Configure K3b 3) Selete the Advanced tab in the Writing section 4) Activate "Manual writing buffer size" and set it to 4MB Now I try to burn DVD-RW. With k3b-1.0.4-5.fc8.x86_64.rpm I get error. When I activate Manual buffer size and set it to 4MB, DVD is burn. I try to update to the newest k3b and DVD is also well burn. The easiest way to solve this problem is to update to the new k3b ;) Nadav try new k3b and please give a feedback if problem still persists. i confirm that... updating to latest k3b on fc9 solved this issue :-) since development of fc8 is no longer active, i guess this issue can be considered closed ? Definitely. Closing. Because it is already solved, closing not a bug. *** Bug 436961 has been marked as a duplicate of this bug. *** |