On Thu, 2013-01-17 at 13:14 +0100, Martin Sourada wrote:
> Yes, the .xsession-errors (quoted under the message) was it. I feel
> stupid now. I looked into running services and indeed polkit and upower
> had "failed" state.
>
> # yum reinstall polkit\* upower
> # reboot
>
> fixed the issue complet
Yes, the .xsession-errors (quoted under the message) was it. I feel
stupid now. I looked into running services and indeed polkit and upower
had "failed" state.
# yum reinstall polkit\* upower
# reboot
fixed the issue completely. Sorry for the "spam". I hope at least that
this helps someone, shoul
On Wed, 16 Jan 2013 14:00:21 +0100
Martin Sourada wrote:
> The FedoraUpgrade [1] one, neither direct yum-upgrade nor fedup-cli.
>
> Martin
>
> [1] https://fedoraproject.org/wiki/Features/FedoraUpgrade
I've done some more digging and testing and this is what does not work:
* shutdown, restart (
On Wed, 16 Jan 2013 11:33:09 +
Frank Murphy wrote:
> On Wed, 16 Jan 2013 12:27:28 +0100
> Martin Sourada wrote:
>
> > Hi all,
> >
> > I upgraded F17 -> F18 using the fedora-upgrade method.
>
> Do yuo mean you did a yum-upgrade as per Subject,
> or fedup-cli (fedora-upgrade method)
The Fe
On Wed, 16 Jan 2013 12:27:28 +0100
Martin Sourada wrote:
> Hi all,
>
> I upgraded F17 -> F18 using the fedora-upgrade method.
Do yuo mean you did a yum-upgrade as per Subject,
or fedup-cli (fedora-upgrade method)
either case a yum distro-sync,
may not go astray,
even if just for checking por
Hi all,
I upgraded F17 -> F18 using the fedora-upgrade method. It had one
issue: stopped after doing the upgrade, so I had to do the rest of the
steps (rebuild rpmdb, update services, groupupdate minimal installation,
etc) by hand, maybe it timed out as I ran the upgrade over night. But
so far so
