Bug 502168

Summary: Title of the CD loaded for ripping is that of the previous CD
Product: [Applications] k3b Reporter: Henry Pfeil <hpfeil>
Component: Audio ProjectAssignee: K3b Bugs <k3b-bugs-null>
Status: RESOLVED FIXED    
Severity: task CC: aacid, jjm, michalm, trueg
Priority: NOR    
Version First Reported In: 23.08.5   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Title of currently loaded CD with title of previous CD displayed

Description Henry Pfeil 2025-03-29 18:36:19 UTC
SUMMARY
While digitizing decades-old CDs before bit rot sets in, the banner displays the title of the previous CD.

STEPS TO REPRODUCE
1.  Load next audio CD for Ripping 
2.  Wait for Analyzing to complete
3.  Click Start Ripping button

OBSERVED RESULT
The title of the CD at the top of the track info panel is out of sync with the title of the current CD as displayed at the top of the left panel above the $HOME list.

EXPECTED RESULT
The title displayed should be the same as the title of the CD currently loaded into the drive.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma:  
KDE Plasma Version: 5.27.12
KDE Frameworks Version:  5.116.0
Qt Version:  5.15.16

ADDITIONAL INFORMATION
More of a design flaw than a bug.
Comment 1 Henry Pfeil 2025-03-30 02:20:24 UTC
Created attachment 179855 [details]
Title of currently loaded CD with title of previous CD displayed
Comment 2 Albert Astals Cid 2025-03-31 18:29:00 UTC
Jonathan, Is this what you fixed in 78de789dc15078f1f1c99704eb303f8c4256868c ?
Comment 3 Jonathan Marten 2025-04-09 11:32:53 UTC
The description seems to fit the same symptoms as I was experiencing before the fix.

Note that the fix is only in the master branch (KF6) and the 24.08, 24.12 and 25.04 releases.  The original reporter seems to be still using KF5 and therefore release 24.05 at the latest.
Comment 4 Albert Astals Cid 2025-04-09 18:05:10 UTC
Ok, let's mark it as fixed then.

Henry if you update to version >= 24.08 and it still happens to you please reopen the bug.