Bug 2293675 - Error while updating from Plasma 6.0.5 to Plasma 6.1
Summary: Error while updating from Plasma 6.0.5 to Plasma 6.1
Keywords:
Status: CLOSED DUPLICATE of bug 2293246
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 40
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-06-21 17:16 UTC by Joelson Jr
Modified: 2024-06-21 22:23 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2024-06-21 22:23:38 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
File containing the error messages received during the update process (6.79 KB, text/html)
2024-06-21 17:16 UTC, Joelson Jr
no flags Details

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 ***


Note You need to log in before you can comment on or make changes to this bug.