Bug 271745 - Disk & data not visible after K3B burn
Summary: Disk & data not visible after K3B burn
Status: RESOLVED WORKSFORME
Alias: None
Product: k3b
Classification: Applications
Component: Burning/Hardware (show other bugs)
Version: 2.0.0
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: ---
Assignee: k3b developers
URL:
Keywords:
: 271744 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-04-26 07:06 UTC by Unknown
Modified: 2023-02-12 03:50 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Unknown 2011-04-26 07:06:24 UTC
Version:           unspecified (using KDE 4.6.2) 
OS:                Linux

I have added a blank DVD and data for burn.  K3B reports all is well through the burn and does not report any problems on verify at the end but when I place the disk back in the drive to check the data, the disk is not mounted and the data is not visible on any other computer.  I have only used the default settings on K3B when making the burn, no error codes or problems are listed during the burn or after.  I have selected obvious options in Groups and Users and manually told fedora to mount the CD but this has not worked.
If possible please email a fix, thank you.

Reproducible: Always

Steps to Reproduce:
I have tried it with 3 DVD disks which has result in the same unable to read disk problem

Actual Results:  
Disk does not mount and data not visible

Expected Results:  
Burnt data to show and disk to mount

Tried it 3 times, searched Google with no result.
Comment 1 Unknown 2011-04-26 07:08:54 UTC
*** Bug 271744 has been marked as a duplicate of this bug. ***
Comment 2 Unknown 2011-05-04 01:15:55 UTC
(In reply to comment #1)
> *** Bug 271744 has been marked as a duplicate of this bug. ***

DO YOU REALIZE THAT YOU HAVE JUST MARKED 271745 AS A DUPLICATE OF 271744 BUT I HAD ALREADY MARKED 271744 AS A DUPLICATE OF 271745, CONFUSING I KNOW.  271745 NEEDS TO BE REACTIVATED AS NEITHER HAVE BEEN ANSWERED.
THANK YOU.
Comment 3 Unknown 2011-05-04 01:17:47 UTC
(In reply to comment #1)
> *** Bug 271744 has been marked as a duplicate of this bug. ***

OR HAVE I BECOME CONFUSED?? SORRY I IF I HAVE!
THANK YOU.
Comment 4 Unknown 2011-05-12 03:23:01 UTC
Hi Any updates on the progress of this error please?
Comment 5 Andrew Crouthamel 2018-11-12 02:55:37 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 6 Andrew Crouthamel 2018-11-21 04:44:43 UTC
Dear Bug Submitter,

This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand.

Thank you for helping us make KDE software even better for everyone!
Comment 7 Justin Zobel 2023-01-13 01:36:56 UTC
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version?

If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
Comment 8 Bug Janitor Service 2023-01-28 05:08:04 UTC
Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least
15 days. Please provide the requested information as soon as
possible and set the bug status as REPORTED. Due to regular bug
tracker maintenance, if the bug is still in NEEDSINFO status with
no change in 30 days the bug will be closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please
mark the bug as REPORTED so that the KDE team knows that the bug is
ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!
Comment 9 Bug Janitor Service 2023-02-12 03:50:08 UTC
This bug has been in NEEDSINFO status with no change for at least
30 days. The bug is now closed as RESOLVED > WORKSFORME
due to lack of needed information.

For more information about our bug triaging procedures please read the
wiki located here:
https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

Thank you for helping us make KDE software even better for everyone!