| Summary: | A requested package cannot be installed: plasma-workspace-5.13.4-2.mga7.x86_64 (due to unsatisfied libgps.so.23()(64bit)) | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Ben McMonagle <westel> |
| Component: | RPM Packages | Assignee: | KDE maintainers <kde> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | geiger.david68210, marja11 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | plasma-workspace-5.13.4-2.mga7.x86_64 | CVE: | |
| Status comment: | |||
| Attachments: | install log from install | ||
|
Description
Ben McMonagle
2018-10-09 01:16:42 CEST
Created attachment 10395 [details]
install log from install
attempting to add report.bug.xz fails with:
The file you are trying to attach is empty, does not exist, or you don't have permission to read it.
I have attached the install log, but it may not be very helpful
(In reply to ben mcmonagle from comment #1) > Created attachment 10395 [details] > install log from install > > attempting to add report.bug.xz fails with: > The file you are trying to attach is empty, does not exist, or you don't > have permission to read it. Please file a separate bug report about that issue and also tell what the ouput is of, as root: ls -al /root/drakx/ > > I have attached the install log, but it may not be very helpful If ddebug.log exists (without being empty), then please attach ddebug.log to that separate report. (In reply to ben mcmonagle from comment #0) > Description of problem: after net install of all available desktops via > desktop selection "custom", at reboot plasma5 is unavailable. > > attempting to install task-plasma5 after login results in : > > # urpmi task-plasma5 > A requested package cannot be installed: > plasma-workspace-5.13.4-2.mga7.x86_64 (due to unsatisfied > libgps.so.23()(64bit)) > I'll keep this report for that problem. Assignee:
bugsquad =>
kde Hi, Why report such as bug? Cauldron is in development and we know that we can experience this kind of problem. And this issue was fixed a few hours ago now. Status:
NEW =>
RESOLVED |