Re: [SOLVED] Re: Yum Upgrade -- A couple of issues
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 completely. Sorry for the spam. I hope at least that this helps someone, should they encounter the same problem. It sounds like you missed the instruction to do the upgrade with SELinux disabled (though I thought we'd fixed that bug - apparently not). -- Adam Williamson Fedora QA Community Monkey IRC: adamw | Twitter: AdamW_Fedora | identi.ca: adamwfedora http://www.happyassassin.net -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
[SOLVED] Re: Yum Upgrade -- A couple of issues
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, should they encounter the same problem. Thanks, Martin On Thu, 17 Jan 2013 12:44:03 +0100 Martin Sourada wrote: I suspect all these issues have one cause, but I'm not sure what exactly goes wrong. Some probably relevant lines from .xsession-errors: Error creating proxy: Error calling StartServiceByName for org.gtk.Private.UDisks2VolumeMonitor: Timeout was reached (g-io-error-quark, 24) (xfdesktop:1172): GVFS-RemoteVolumeMonitor-WARNING **: remote volume monitor with dbus name org.gtk.Private.UDisks2VolumeMonitor is not supported (polkit-gnome-authentication-agent-1:1241): polkit-gnome-1-WARNING **: Error getting authority: Error initializing authority: Error calling StartServiceByName for org.freedesktop.PolicyKit1: GDBus.Error:org.freedesktop.DBus.Error.TimedOut: Activation of org.freedesktop.PolicyKit1 timed out (xfce4-session:1163): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Unable to read response from sudo helper: Unknown error xfce4-session: Querying CanRestart failed, Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (xfce4-session:1163): GLib-WARNING **: GError set over the top of a previous GError or uninitialized memory. This indicates a bug in someone's code. You must ensure an error is NULL before it's set. The overwriting error message was: Unable to read response from sudo helper: Unknown error xfce4-session: Querying CanShutdown failed. Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. xfce4-session: Querying suspend failed: Message did not receive a reply (timeout by message bus) DBusException: org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus) Unable to mount card (Error code: 1) ERROR:dbus.proxies:Introspect error on :1.217:/org/freedesktop/UDisks: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Yum Upgrade -- A couple of issues
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 good, the real issue comes after reboot: Login related functions terribly slow for no apparent reason. Looks like they're waiting for something until timing out (no HDD nor CPU is being used during the process). Affected are DM start-up (I tried lightdm, kdm), DE start-up (XFCE), XFCE log-out dialog start-up, cannot shut-down, reboot, sleep, hibernate. (Well reboot as root from CLI works...) Pointers to what might be wrong (configuration issue or bug?) welcome. Martin signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Yum Upgrade -- A couple of issues
On Wed, 16 Jan 2013 12:27:28 +0100 Martin Sourada martin.sour...@gmail.com 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 porpoises. -- Regards, Frank Byte my kernel --me . -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
Re: Yum Upgrade -- A couple of issues
On Wed, 16 Jan 2013 11:33:09 + Frank Murphy wrote: On Wed, 16 Jan 2013 12:27:28 +0100 Martin Sourada martin.sour...@gmail.com 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 FedoraUpgrade [1] one, neither direct yum-upgrade nor fedup-cli. Martin [1] https://fedoraproject.org/wiki/Features/FedoraUpgrade signature.asc Description: PGP signature -- test mailing list test@lists.fedoraproject.org To unsubscribe: https://admin.fedoraproject.org/mailman/listinfo/test
