On 03/14/2015 10:34 AM, José Matos wrote:

On Saturday 14 March 2015 06:33:07 bitlord wrote:

...

I'm not 100% sure about this, I was testing some tc/rc images for alpha, there was a missing package/s, and if I remember it correctly trace looked like yours, can you check if you have 'plasma-desktop' installed, if not try installing it.

You are right, thank you. :-)

...

If this fixes it, please report how did you install/update/upgrade to f22? Maybe something else also need fixing, missing package was added to live image creation "scripts"/spin-kickstarts (I just checked and cannot find it, maybe it wasn't, or I don't know where).

Short version:

I have used "dnf upgrade".

Long version: I tried to use fedup but it did not work because of bug https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=1185604

that can be found referenced in http://fedoraproject.org/wiki/Common_F22_bugs

So I did it by stages:

# dnf upgrade --releasever=22 fedora-release* dnf rpm*

and later

# dnf distro-sync

At this stage it broke at some point where dnf was stuck.

The only option was to reboot and repeat the procedure.

Later since there were lots of duplicates, those that were not

cleaned, I had to call

# package-cleanup --clean-dupes

And then I had to fix some small inconsistencies that remained.

That was it. :-)

Again thank you for your assistance. :-)

FWIW, I experienced a similar situation. A `dnf distro-sync` hung (I believe the system became unresponsive because a change in NetworkManager during the transaction was not compatible with my bonded eth config) and dnf was usable in only a very tedious way, with lots of reported conflicts and problems. I used `package-cleanup --cleandupes` and was able to finish my distro-sync transaction, but discovered many of my installed packages were gone, things I use regularly like packaging tools, publican, firefox, etc. I would not be surprised if your problem was due to missing packages.

--Pete

On Sunday 15 March 2015 08:47:43 Pete Travis wrote:

FWIW, I experienced a similar situation. A `dnf distro-sync` hung (I believe the system became unresponsive because a change in NetworkManager during the transaction was not compatible with my bonded eth config) and dnf was usable in only a very tedious way, with lots of reported conflicts and problems. I used `package-cleanup --cleandupes` and was able to finish my distro-sync transaction, but discovered many of my installed packages were gone, things I use regularly like packaging tools, publican, firefox, etc. I would not be surprised if your problem was due to missing packages.

I was aware of that, so I tried I decided to finish the distro-sync first and only then to clean the duplicate packages.

Since I noticed that there were packages from F22 that were removed I installed those again. I took advantage that package-cleanup uses yum so that the transaction is record in yum's history.

From the last transaction (number 438 in this case) I have reverted the erase packages from F22:

# dnf install $(yum history info 438 | grep -i erase | grep fc22 | awk '{print $2}')

I am aware that it is not the same thing as before but in any case I tried to minimize the changes.