[SOLVED] Update problem with Kwrite & Hugin

This forum is dedicated to basic help and support :

Ask here your questions about basic installation and usage of Mageia. For example you may post here all your questions about getting Mageia isos and installing it, configuring your printer, using your word processor etc.

Try to ask your questions in the right sub-forum with as much details as you can gather. the more precise the question will be, the more likely you are to get a useful answer

[SOLVED] Update problem with Kwrite & Hugin

Postby kensor » Aug 20th, '11, 17:18

This morning I noticed on-screen a white exclamation mark in a red circle, indicating an available update. So I started Mageia Control Center, clicked Updates, and received a message with a window title that said:
One package cannot be installed

and the dialog box message said:
Sorry, the following package cannot be selected:


- kipi-plugins-expoblending-1.9.0-3.1.mga1.i586 (due to unsatisfied hugin)

Aside from the vague humor in the image of two concentric circles of people rotating with respect to one another frustrated by inability to hug one another, apparently due to a misspelled, and therefor unsatisfied plugin, I don't know how to remedy the situation that caused the message.

By the way:
While the this message was on the screen I highlighted and copied it, then attempted to open Kwrite to paste it into a file to save. Unfortunately, Kwrite crashed with the following message in a window titled KDE Crash Handler:

Application: KWrite (kdeinit4 (deleted)), signal: Segmentation fault
[Current thread is 1 (process 20573)]
Thread 1 (process 20573):
#0 0xffffe424 in ?? ()
#1 0xb769650e in ?? ()
#2 0xb77b9820 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

When I attempt to restart Kwrite I receive an error message titled Error - KWrite that states:
A KDE text-editor component could not be found.
Please check your KDE installation.

Needless to say, this is not an acceptable update outcome – even if I had been noticed in advance that an update of 404 packages requiring the better part of an hour to download and install was about to take place.

Suggestion: the notice of available update needs to state clearly, on a screen that does not require scrolling to the bottom of a list of updates, a summary of how many packages, how much space they will consume, how much download capacity they will require, and how long the download and installation process likely will take. Even with the notorious inaccuracy of the times in such messages, it still would be useful to know a large, long update (an hour) as opposed to a small, short one (a minute) is requesting permission to take place on the local machine.

So, two questions: 1) how do I recover my Kwrite? 2) how to I remedy the plugin problem?
kensor
 
Posts: 24
Joined: Jun 12th, '11, 12:31

Re: Update problem leads to KWrite loss

Postby djennings » Aug 21st, '11, 11:34

hugin is a separate application kipi-plugins-expoblending now depends on hugin so hugin must be installed before kipi-plugins-expoblending will install.
Due to a bug in the update process the updater will not automatically install hugin because it is in the main core repository not the update repository. Install hugin first with the Software Install GUI and you will then be able to complete your update.

The 404 packages installed were mostly KDE packages. KDE 4.6.5 has been released as an update, so of course there are a LOT of packages to install. You will need to log out and in again after updating KDE because of the updated libraries. The problem you had with kwrite was because the libraries in your running system did not match the new kwrite version.
User avatar
djennings
 
Posts: 613
Joined: Jun 2nd, '11, 23:51
Location: Wokingham, UK

Re: Update problem leads to KWrite loss

Postby kensor » Aug 21st, '11, 19:50

Thank you, indeed. Logging out and then back in returned KWrite functionality, and no sooner had KWrite appeared the update icon appeared with only kipi-plugins-expoblending in the list. The update completed without further messages, so all is well for this incident.
kensor
 
Posts: 24
Joined: Jun 12th, '11, 12:31


Return to Basic support

Who is online

Users browsing this forum: No registered users and 1 guest

cron