Bug 250270

Summary:	Updating data from burned CD Or DVD
Product:	[Unmaintained] kio	Reporter:	William <asemann>
Component:	general	Assignee:	David Faure <faure>
Status:	RESOLVED WORKSFORME
Severity:	minor	CC:	markg85, nate
Priority:	NOR	Keywords:	triaged
Version First Reported In:	4.4
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description William 2010-09-05 14:40:13 UTC

Version:           unspecified (using KDE 4.4.4) 
OS:                Linux

After burning a media (CD or DVD) with K3B, the media is read well with K3B, but not by Dolphin. Noway to update Dolphin without loading twice this new media (CD or DVD).
After ejecting/loading the new media newly burned, Dolphin see always a virgin media.
Another ejecting/loading, Dolphin can read it.

Reproducible: Always

Steps to Reproduce:
Burning a media. Ejecting/Loading this newly burned media twice to read it.

Actual Results:  
I can use / read the burned media.

Expected Results:  
Updating data after burning rom / media (like K3B done)

OS: Linux (x86_64) release 2.6.34-12-desktop
Compiler: gcc

Comment 1 Mark 2010-09-16 03:03:19 UTC

Is this still an issue on KDE 4.5.x? 

Let me get this right. These are the steps you do:
1. burn some data to some cd/dvd with k3b
2. once completed you eject the cd
3. then you load/insert the cd and then dolphin reports a virgin media?
4. then you eject the cd
5. then you insert it again
6. now dolphin does show data?

Are those the steps to reproduce this?

Comment 2 William 2010-09-16 19:44:25 UTC

I didn't try on KDE 4.5. I'm still on KDE 4.4.4 (2nd release). I didn't have yet stable package to update KDE on my operating system.

Yes, it's the right process to reproduce the bug. I can add these steps to be more comprehensive :

0.      insert a virgin media - dolphin and K3b reports a virgin media
1 bis.  after completed and before ejecting - k3b show data
3.      (...) and k3b still show data

Thanks

Comment 3 Nate Graham 2018-04-24 18:43:37 UTC

Is this still relevant or applicable with KDE Frameworks 5.45 and/or Dolphin 18.04?

Comment 4 Andrew Crouthamel 2018-09-28 03:15:00 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 set the bug status 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 5 Andrew Crouthamel 2018-10-29 02:03:24 UTC

Dear Bug Submitter,

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!