https://bugs.kde.org/show_bug.cgi?id=513448

            Bug ID: 513448
           Summary: Missing Dependency qt6-webengine on upgrade to Plasma
                    6.5.3 KDE Neon
    Classification: KDE Neon
           Product: neon
      Version First unspecified
       Reported In:
          Platform: KDE Linux
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: Packages User Edition
          Assignee: [email protected]
          Reporter: [email protected]
                CC: [email protected], [email protected]
  Target Milestone: ---

Created attachment 187706
  --> https://bugs.kde.org/attachment.cgi?id=187706&action=edit
Neon missing dependency notice

SUMMARY

I am having trouble updating KDE Neon on 3 different Linux computers -
involving two different laptop hardware.

STEPS TO REPRODUCE
1.  Attempt normal Discover software update.
2.  Start update manually.  Informed 361 packages will be updated.  Package
count differs slightly with the 3.
3.  Observe attached screenshot within a second or two BEFORE I can select
"restart" at bottom of window.

OBSERVED RESULT

Attached screenshot.
Dependency resolution failed:

The following packages have unmet dependencies: plasma-widgets-addons:
Deppends: qt6-webengine (>=6.10.1) but
6.0.2-0zneon+24.04+noble+release+build35 to be installed

Note -- possible that one of these said build 34.  See screenshots.  I
consolidated 3 screenshots - dependency notice + hardware / software
configuration since I can only select one file to attach.

EXPECTED RESULT

Completion of update verified after reboot.

SOFTWARE/OS VERSIONS

Three different computers Info attached.
All KDE Plasma 6.5.1
KDE Frameworks Version 6.19.0
Qt Version 6.9.2
two different Kernal versions:
6.14.0-34-generic (64-bit) and 6.14.0-35-generic (64 bit)

ADDITIONAL INFORMATION

I think issue is long delay on my part updating software vs. frequent
incremental updates.
I have other hardware I update more frequently, and I can get past this issue. 
One similar issue resolved itself so it must have been a temporary file
availability issue.  I'm reporting this since I think it may be persistent
without your intervention.

Looks like duplicate of 512669 and 512739
Please add me to cc for resolution.

Thanks so much.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to