Bug 2293675

Summary: Error while updating from Plasma 6.0.5 to Plasma 6.1
Product: [Fedora] Fedora Reporter: Joelson Jr <joelson.ejr>
Component: plasma-workspaceAssignee: KDE SIG <kde-sig>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 40CC: jgrulich, kde-sig, kevin, rdieter, than
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-21 22:23:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File containing the error messages received during the update process none

Description Joelson Jr 2024-06-21 17:16:50 UTC
Created attachment 2037957 [details]
File containing the error messages received during the update process

Description of problem:
I was trying to updade from kde-plasma 6.0.5, using Discover, when the transaction was interrupted and the following error messagem appeared:

<html>Internal error:<br/><br/>Error running transaction: file /usr/share/locale/ar/LC_MESSAGES/plasma_engine_devicenotifications.mo from install of plasma5support-6.1.0-1.fc40.x86_64 conflicts with file from package plasma-workspace-6.0.5.1-2.fc40.x86_64
... </html>

I received the 34 errors like the one above (please see the attached file).

Version-Release number of selected component (if applicable):
6.0.5.1-2.fc40.x86_64


How reproducible:


Steps to Reproduce:
1. Open Discover, and head to the Updates section. 
2. If there is a System Update avaliable, click in "Update All". If the update isn ´t showing, try to Refresh the update list. 

Actual results:
The update gets interrupted by this error message, and stops immediately.

Expected results:
The upate procecure woul finish without any error.

Additional info:

Comment 1 Kevin Kofler 2024-06-21 22:23:38 UTC

*** This bug has been marked as a duplicate of bug 2293246 ***